Bug 111853 - nouveau kernel module won't load (not available) on Sony laptop with NVIDIA G86M [GeForce 8400M GT] ID: 10de:0426
Summary: nouveau kernel module won't load (not available) on Sony laptop with NVIDIA G...
Status: NEW
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: not set major
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-29 14:14 UTC by Felix Miata
Modified: 2019-10-19 01:09 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg using vanilla 5.2.14 and acpi=off on openSUSE Tumbleweed (52.76 KB, text/plain)
2019-09-29 14:14 UTC, Felix Miata
no flags Details
dmesg following modprobe nouveau running vanilla kernel 5.3.1 (52.76 KB, text/plain)
2019-09-29 22:15 UTC, Felix Miata
no flags Details
dmesg without vga= & with nouveau.debug=trace (53.07 KB, text/plain)
2019-09-30 08:02 UTC, Felix Miata
no flags Details
Xorg.0.log from live LMDE 2 Betsy boot (65.08 KB, text/plain)
2019-10-16 16:44 UTC, Felix Miata
no flags Details
Xorg.0.log from live Knoppix 7.6.1 (67.41 KB, text/plain)
2019-10-16 16:44 UTC, Felix Miata
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Miata 2019-09-29 14:14:35 UTC
Created attachment 145577 [details]
dmesg using vanilla 5.2.14 and acpi=off on openSUSE Tumbleweed

Original summary:
nouveau won't load (not available) on Sony laptop with NVIDIA G86M [GeForce 8400M GT] ID: 10de:0426 

This is mostly copied from https://bugzilla.kernel.org/show_bug.cgi?id=204851

This errant behavior is similarly exhibited by openSUSE Tumbleweed, 15.0, 13.1 and 12.2; Linuxmint 19.0 live installation media; Knoppix 8.2 and 8.6 live media; antiX 17.4. Using vanilla kernel 5.2.14 on Tumbleweed doesn't help.

Actual behavior:
1-nouveau kernel module doesn't load
2-ttys limited to 1024x768 mode
3-X runs only with VESA or FBDEV drivers and limited to 1024x768 mode
4-/dev/dri/card0 is absent
5-hwinfo reports HDTV display supports maximum VESA 1024x768 mode
6-GeForce 8400M gfx reported by lspci is not found by Xorg
7-[drm] Failed to open DRM device for pci:0000:01:00.0: -19
8-hwinfo improperly detects display
9-laptop locks up (requires poweroff reset) unless cmdline includes acpi=off
10-/sys/kernel/debug/dri/ is empty

Expected behavior:
1-ttys use display's native 1920x1080 mode
2-X uses modesetting DDX or nouveau DDX and native 1920x1080 mode

# inxi -GxxSMaz
System:    Host: vaio Kernel: 5.2.11-1-default x86_64 bits: 64 compiler: gcc v: 9.2.1 
           parameters: root=/dev/sda9 ipv6.disable=1 net.ifnames=0 noresume mitigations=auto consoleblank=0 
           drm.debug=0x1e log_buf_len=1M acpi=off vga=791 video=1280x720@60 video=1024x768@60 video=1440x900@60 3 acpi=off 
           Console: tty 3 dm: N/A Distro: openSUSE Tumbleweed 20190907 
Machine:   Type: Laptop System: Sony product: VGN-AR730E v: C3LR1E11 serial: <filter> Chassis: type: 10 serial: N/A 
           Mobo: Sony model: VAIO serial: N/A BIOS: Phoenix v: R2090J8 date: 02/26/2008 
Graphics:  Device-1: NVIDIA G86M [GeForce 8400M GT] vendor: Sony driver: N/A bus ID: 01:00.0 chip ID: 10de:0426 
           Display: server: X.org 1.20.5 driver: nouveau,vesa unloaded: fbdev,modesetting alternate: nv,nvidia tty: 128x48 
           Message: Advanced graphics data unavailable in console for root. 
# lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation G86M [GeForce 8400M GT] (rev a1)
# lspci -vv -d 10de:0426
01:00.0 VGA compatible controller: NVIDIA Corporation G86M [GeForce 8400M GT] (rev a1) (prog-if 00 [VGA controller])
	Subsystem: Sony Corporation Device 9016
	Physical Slot: 1
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 5
	Region 0: Memory at ce000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at d0000000 (64-bit, prefetchable) [size=256M]
	Region 3: Memory at cc000000 (64-bit, non-prefetchable) [size=32M]
	Region 5: I/O ports at 2000 [size=128]
	[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [78] Express (v1) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <4us
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 75.000W
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <512ns, L1 <4us
			ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
		LnkCtl:	ASPM L0s L1 Enabled; RCB 128 bytes Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s (ok), Width x16 (ok)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
	Kernel modules: nouveau
# dmesg | grep veau
# journalctl -b | grep veau
# lsmod | grep veau
# lsmod | grep video
uvcvideo              118784  0
videobuf2_vmalloc      20480  1 uvcvideo
videobuf2_memops       20480  1 videobuf2_vmalloc
video                  53248  0
videobuf2_v4l2         28672  1 uvcvideo
videobuf2_common       57344  2 videobuf2_v4l2,uvcvideo
videodev              233472  3 videobuf2_v4l2,uvcvideo,videobuf2_common
media                  57344  4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common
usbcore               303104  5 ehci_pci,usbhid,uvcvideo,ehci_hcd,uhci_hcd
# modprobe nouveau
modprobe: ERROR: could not insert 'nouveau': No such device
# hwinfo --monitor
31: None 00.0: 10000 Monitor
  [Created at fb.71]
  Unique ID: rdCR.EY_qmtb9YY0
  Hardware Class: monitor
  Model: "Generic Monitor"
  Vendor: "Generic"
  Device: "Monitor"
  Resolution: 1024x768@76Hz
  Year of Manufacture: 0
  Week of Manufacture: 0
  Driver Info #0:
    Max. Resolution: 1024x768
    Vert. Sync Range: 50-90 Hz
    Hor. Sync Range: 31-61 kHz
  Config Status: cfg=new, avail=yes, need=no, active=unknown
# hwinfo --gfxcard
16: PCI 100.0: 0300 VGA compatible controller (VGA)
  [Created at pci.386]
  Unique ID: VCu0.3ZIBFiHqnhE
  Parent ID: vSkL.__4Fox8chd3
  SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
  SysFS BusID: 0000:01:00.0
  Hardware Class: graphics card
  Model: "nVidia GeForce 8400M GT"
  Vendor: pci 0x10de "nVidia Corporation"
  Device: pci 0x0426 "GeForce 8400M GT"
  SubVendor: pci 0x104d "Sony Corporation"
  SubDevice: pci 0x9016 
  Revision: 0xa1
  Memory Range: 0xce000000-0xceffffff (rw,non-prefetchable)
  Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable)
  Memory Range: 0xcc000000-0xcdffffff (rw,non-prefetchable)
  I/O Ports: 0x2000-0x2fff (rw)
  Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled)
  IRQ: 5 (no events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v000010DEd00000426sv0000104Dsd00009016bc03sc00i00"
  Driver Info #0:
    XFree86 v4 Server Module: nv
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #12 (PCI bridge)
Primary display adapter: #16
# egrep 'dri|ailed|veau' /var/log/Xorg.0.log | grep -v 't driver'
[  2155.322] (II) Scanning /etc/X11/xorg_pci_ids directory for additional PCI ID's supported by the drivers
[  2155.322] (==) Matched nvidia as autoconfigured driver 0
[  2155.322] (==) Matched nouveau as autoconfigured driver 1
[  2155.322] (==) Matched nv as autoconfigured driver 2
[  2155.322] (==) Matched modesetting as autoconfigured driver 3
[  2155.322] (==) Matched fbdev as autoconfigured driver 4
[  2155.322] (==) Matched vesa as autoconfigured driver 5
[  2155.322] (==) Assigned the driver to the xf86ConfigLayout
[  2155.322] (EE) Failed to load module "nvidia" (module does not exist, 0)
[  2155.322] (II) LoadModule: "nouveau"
[  2155.323] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so
[  2155.323] (II) Module nouveau: vendor="X.Org Foundation"
[  2155.323] (EE) Failed to load module "nv" (module does not exist, 0)
[  2155.323] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[  2155.323] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
[  2155.324] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[  2155.324] (II) NOUVEAU driver 
[  2155.324] (II) NOUVEAU driver for NVIDIA chipset families :
[  2155.324] (II) FBDEV: driver for framebuffer: fbdev
[  2155.324] (II) VESA: driver for VESA chipsets: vesa
[  2155.535] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19
[  2155.536] (EE) open /dev/dri/card0: No such file or directory
[  2155.536] (EE) open /dev/dri/card0: No such file or directory
[  2156.135] (II) VESA(0): VESA VBE DDC read failed
[  2156.135] (II) VESA(0): VESA VBE PanelID read failed
Comment 1 Ilia Mirkin 2019-09-29 14:36:56 UTC
I see no record of nouveau loading in the kernel logs. This most likely means that it's blacklisted somehow.
Comment 2 Felix Miata 2019-09-29 20:41:13 UTC
How?
e.g. on Tumbleweed:
Nothing in /etc/mo*/ contains veau
Nothing in /etc/ is named *veau*
# lspci | grep -i vidia
01:00.0 VGA compatible controller: NVIDIA Corporation G86M [GeForce 8400M GT] (rev a1)
# uname -a
Linux vaio 5.3.1-2.g3354216-vanilla #1 SMP Thu Sep 26 06:05:47 UTC 2019 (3354216) x86_64 x86_64 x86_64 GNU/Linux
# cat /proc/cmdline
root=/dev/sda9 ipv6.disable=1 net.ifnames=0 noresume mitigations=auto consoleblank=0 drm.debug=0x1e log_buf_len=1M acpi=off 3
# pwd
/lib/modules/5.3.1-2.g3354216-vanilla/kernel/drivers/gpu/drm/nouveau
ls -l | grep veau
-rw-r--r-- 1 root root 645980 Sep 27 05:03 nouveau.ko.xz
# zcat /proc/config.gz | grep -i veau
CONFIG_DRM_NOUVEAU=m
# CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT is not set
CONFIG_NOUVEAU_DEBUG=5
CONFIG_NOUVEAU_DEBUG_DEFAULT=3
# CONFIG_NOUVEAU_DEBUG_MMU is not set
CONFIG_DRM_NOUVEAU_BACKLIGHT=y
CONFIG_DRM_NOUVEAU_SVM=y
# modprobe nouveau
modprobe: ERROR: could not insert 'nouveau': No such device

How could it be blacklisted, and why does modprobe claim there is no such device?
Comment 3 kherbst 2019-09-29 21:01:13 UTC
does anything in dmesg show the reason?

On Sun, Sep 29, 2019 at 10:41 PM <bugzilla-daemon@freedesktop.org> wrote:
>
> Comment # 2 on bug 111853 from Felix Miata
>
> How?
> e.g. on Tumbleweed:
> Nothing in /etc/mo*/ contains veau
> Nothing in /etc/ is named *veau*
> # lspci | grep -i vidia
> 01:00.0 VGA compatible controller: NVIDIA Corporation G86M [GeForce 8400M GT]
> (rev a1)
> # uname -a
> Linux vaio 5.3.1-2.g3354216-vanilla #1 SMP Thu Sep 26 06:05:47 UTC 2019
> (3354216) x86_64 x86_64 x86_64 GNU/Linux
> # cat /proc/cmdline
> root=/dev/sda9 ipv6.disable=1 net.ifnames=0 noresume mitigations=auto
> consoleblank=0 drm.debug=0x1e log_buf_len=1M acpi=off 3
> # pwd
> /lib/modules/5.3.1-2.g3354216-vanilla/kernel/drivers/gpu/drm/nouveau
> ls -l | grep veau
> -rw-r--r-- 1 root root 645980 Sep 27 05:03 nouveau.ko.xz
> # zcat /proc/config.gz | grep -i veau
> CONFIG_DRM_NOUVEAU=m
> # CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT is not set
> CONFIG_NOUVEAU_DEBUG=5
> CONFIG_NOUVEAU_DEBUG_DEFAULT=3
> # CONFIG_NOUVEAU_DEBUG_MMU is not set
> CONFIG_DRM_NOUVEAU_BACKLIGHT=y
> CONFIG_DRM_NOUVEAU_SVM=y
> # modprobe nouveau
> modprobe: ERROR: could not insert 'nouveau': No such device
>
> How could it be blacklisted, and why does modprobe claim there is no such
> device?
>
> ________________________________
> You are receiving this mail because:
>
> You are the assignee for the bug.
>
> _______________________________________________
> Nouveau mailing list
> Nouveau@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/nouveau
Comment 4 Felix Miata 2019-09-29 22:15:49 UTC
Created attachment 145584 [details]
dmesg following modprobe nouveau running vanilla kernel 5.3.1

(In reply to kherbst from comment #3)
> does anything in dmesg show the reason?

Not only is nothing showing any reason, but nothing showing modprobe nouveau was even attempted. Last line in journal ls initial login, and in dmesg, sky2 0000:02:00.0 eth0: Link is up at 1000 Mbps, full duplex, flow control both
Comment 5 Ilia Mirkin 2019-09-29 23:01:38 UTC
The only thing I can think of is the vesafb usage. However I thought there was a mechanism for us to kick out such a driver. But perhaps not, and perhaps it broke somehow. Can you try not booting with video=?

Also, perhaps something's VERY wrong with the device, s.t. something fails very early in nouveau's attempts -- try loading nouveau with

debug=trace (or, if putting into the kernel cmdline, nouveau.debug=trace)

which should spam the kernel log pretty hard.
Comment 6 Felix Miata 2019-09-30 07:54:29 UTC
(In reply to Ilia Mirkin from comment #5)
> The only thing I can think of is the vesafb usage. However I thought there
> was a mechanism for us to kick out such a driver. But perhaps not, and
> perhaps it broke somehow. Can you try not booting with video=? 
That results in use of 80x25 text mode that is corrupted, random letters get shifted by one character from what they should have been, e.g. "t" drawn where "s" should be, or "d" drawn where "c" should be, and many clearly wrong characters, such as 15-30% of a screen full of "!!". The BIOS logo also has vertical lines through the SONY image, and the !! pairs appear on the otherwise black screen between BIOS splash and GFX Grub menu, and plain text mode Grub.

> Also, perhaps something's VERY wrong with the device, s.t. something fails
> very early in nouveau's attempts -- try loading nouveau with

> debug=trace (or, if putting into the kernel cmdline, nouveau.debug=trace)

> which should spam the kernel log pretty hard.
It didn't, 331 bytes less than that of comment 4, only two lines containing "veau", both included on Kernel command line.

This laptop isn't mine. It belongs to my church. It came to me to repair because of video corruption in Windows 7 that appeared only after warmup. I took out its HD and put in my SSD to facilitate troubleshooting after having the same trouble with Knoppix as is happening in openSUSE, and taking a long time to boot each time from Knoppix DVD.

I quickly decided the Windows video corruption seemed to be nothing but overheating, so I've been running it most of the time with a 4" fan blowing on its bottom after having blown through its airways with compressed air when I first got it. Without the 4" fan, I can't tell if the heat coming from the vent is simply radiation, or from its fan.

In 1024x768 VESA mode (with vga=) the video output doesn't get corrupted either on vttys or in Xorg. When I plug in a display to its HDMI port, the external display wakes up only to report "no HDMI signal", which it repeats going into or out of Xorg.
Comment 7 Felix Miata 2019-09-30 08:02:48 UTC
Created attachment 145591 [details]
dmesg without vga= & with nouveau.debug=trace
Comment 8 Felix Miata 2019-10-10 05:18:45 UTC
A fresh installation of Windows 7 uses the panel's native 1440x900 mode via its "VGA" driver, though the HDMI port sends nothing to a display more than what's necessary to make it complain mode not supported.
Comment 9 Ilia Mirkin 2019-10-10 05:27:17 UTC
This is weird:

[    0.519104] pci 0000:01:00.0: BAR 6: no space for [mem size 0x00020000 pref]
[    0.519109] pci 0000:01:00.0: BAR 6: failed to assign [mem size 0x00020000 pref]

Not sure if it's related.
Comment 10 Felix Miata 2019-10-16 16:44:08 UTC
Created attachment 145757 [details]
Xorg.0.log from live LMDE 2 Betsy boot

# uname -a
Linux stresslinux 2.6.37.6-0.5-default #1 SMP 2011-04-25 21:48:33 +0200 x86_64 x86_64 x86_64 GNU/Linux
# lsmod | sort | grep veau
button                  6797  1 nouveau
drm                   229676  3 nouveau,ttm,drm_kms_helper
drm_kms_helper         36630  1 nouveau
i2c_algo_bit            6342  1 nouveau
nouveau               678496  1 
ttm                    72581  1 nouveau
video                  15865  1 nouveau

But Stresslinux 0.7.106 has no X :-(

# uname -a
Linux mint 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) x86_64 GNU/Linux
# lsmod | sort | grep veau
button                 12944  1 nouveau
drm                   249955  3 ttm,drm_kms_helper,nouveau
drm_kms_helper         49210  1 nouveau
i2c_algo_bit           12751  1 nouveau
i2c_core               46012  7 drm,i2c_i801,drm_kms_helper,i2c_algo_bit,v4l2_common,nouveau,videodev
mxm_wmi                12515  1 nouveau
nouveau              1122419  0 
ttm                    77862  1 nouveau
video                  18096  1 nouveau
wmi                    17339  2 mxm_wmi,nouveau
# inxi -GxxS
System:    Host: mint Kernel: 3.16.0-4-amd64 x86_64 (64 bit gcc: 4.8.4)
           Desktop: MATE 1.8.1 (Gtk 3.14.5+4) dm: mdm Distro: LinuxMint 2 betsy
Graphics:  Card: NVIDIA G86M [GeForce 8400M GT] bus-ID: 01:00.0 chip-ID: 10de:0426
           Display Server: X.Org 1.16.4 drivers: fbdev,vesa,nouveau Resolution: 1024x768@61.00hz
           GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits)
           GLX Version: 3.0 Mesa 10.3.2 Direct Rendering: Yes

With this old live distro, nouveau loads, but there's no /dev/dri/card0 or /dev/fb0, so it's stuck in VESA 1024x768.
Comment 11 Felix Miata 2019-10-16 16:44:39 UTC
Created attachment 145758 [details]
Xorg.0.log from live Knoppix 7.6.1

# lsmod | sort | grep veau
drm_kms_helper         70712  1 nouveau
mxm_wmi                 1635  1 nouveau
nouveau              1033769  0
ttm                    60685  1 nouveau
wmi                     7363  2 mxm_wmi,nouveau
# inxi -c0 -GxxSM
System:    Host: Microknoppix Kernel: 4.2.6-64 x86_64 (64 bit gcc: 5.2.1)
           Console: tty 3 dm: kdm Distro: Debian GNU/Linux stretch/sid
Machine:   System: Sony (portable) product: VGN-AR730E v: C3LR1E11 serial: 28272434-3101919
           Mobo: Sony model: VAIO Bios: Phoenix v: R2090J8 date: 02/26/2008
           Chassis: type: 10
Graphics:  Card: NVIDIA G86M [GeForce 8400M GT]
           bus-ID: 01:00.0 chip-ID: 10de:0426
           Display Server: X.org 1.17.3 drivers: vesa,nouveau (unloaded: fbdev)
           tty size: 80x25 Advanced Data: N/A for root out of X
# dmesg | grep ailed
[    0.770863] acpi PNP0A08:00: _OSC failed (AE_SUPPORT); disabling ASPM
[    0.849357] pci 0000:01:00.0: BAR 6: failed to assign [mem size 0x00020000 pref]
[    1.607734] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SATA.PRT0._SDD] (Node ffff8800bf08f338), AE_NOT_FOUND (20150619/psparse-536)
[    1.609103] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SATA.PRT0._SDD] (Node ffff8800bf08f338), AE_NOT_FOUND (20150619/psparse-536)
[   37.465961] systemd-udevd[2004]: Process '/usr/sbin/alsactl -E HOME=/var/run/alsa restore 0' failed with exit code 99.
[   38.226541] systemd-udevd[2008]: Process '/sbin/crda' failed with exit code 249.
[   38.229603] systemd-udevd[2008]: Process '/sbin/crda' failed with exit code 249.
[   42.469065] systemd-udevd[2086]: Process '/usr/sbin/alsactl -E HOME=/var/run/alsa restore 0' failed with exit code 99.
[   69.564168] systemd-logind[2229]: Failed to start user service, ignoring: Unknown unit: user@1000.service
[  100.435441] uvcvideo: Failed to query (129) UVC probe control : -32 (exp. 26).
[  100.435443] uvcvideo: Failed to initialize the device (-5).

Again, nouveau loads, but X video is scrambled VESA, again with no /dev/dri/card0 or /dev/fb0.
Comment 12 Felix Miata 2019-10-19 01:09:34 UTC
AFAICT, the last or nearly the last tty message before screen stops responding without acpi=off follows this line:

fb: switching to nouveaufb from VESA VGA

at least, it does if I include vga=791 to try to get a reasonable text size on the vttys, and avoid all the !!!!!s.

In the currently installed (on owner's HD alongside Win7) openSUSE 15.1 I tried disabling the built-in video camera with:

module_blacklist=uvcvideo,videobuf2_core,videobuf2_memops,videobuf2_v4l2,videobuf2_vmalloc,videodev

on cmdline instead of acpi=off, but it had no apparent impact.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.