[Bug 1207516] New: No modesetting with Zen4 integrated graphics or rx6950 XT
https://bugzilla.suse.com/show_bug.cgi?id=1207516 Bug ID: 1207516 Summary: No modesetting with Zen4 integrated graphics or rx6950 XT Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: rguenther@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- The Alpha from late December doesn't perform graphic install and listing pci IDs and corresponding kernel drivers shows nothing. X startup complains that no modesetting is possible. Plugged to monitor during install: 39:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] Flags: bus master, fast devsel, latency 0, IRQ 255 Memory at 80000000 (64-bit, prefetchable) [size=256M] Memory at 90000000 (64-bit, prefetchable) [size=2M] I/O ports at e000 [disabled] [size=256] Memory at ece00000 (32-bit, non-prefetchable) [size=512K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/4 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable- Count=4 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [270] #19 Capabilities: [2a0] Access Control Services Capabilities: [2b0] Address Translation Service (ATS) Capabilities: [2c0] Page Request Interface (PRI) Capabilities: [2d0] Process Address Space ID (PASID) Capabilities: [410] #26 Capabilities: [450] #27 Also installed: 03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6950 XT] [1002:73a5] (rev c0) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3955] Flags: bus master, fast devsel, latency 0, IRQ 255 Memory at a0000000 (64-bit, prefetchable) [size=256M] Memory at b0000000 (64-bit, prefetchable) [size=2M] I/O ports at f000 [disabled] [size=256] Memory at ecf00000 (32-bit, non-prefetchable) [size=1M] Expansion ROM at ed000000 [disabled] [size=128K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [200] #15 Capabilities: [240] Power Budgeting <?> Capabilities: [270] #19 Capabilities: [2a0] Access Control Services Capabilities: [2d0] Process Address Space ID (PASID) Capabilities: [320] Latency Tolerance Reporting Capabilities: [410] #26 Capabilities: [440] #27 gdm-Xorg doesn't even try to load the readeon module but ultimatively fails as Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (--) PCI: (3@0:0:0) 1002:73a5:1462:3955 rev 192, Mem @ 0xa0000000/268435456, 0xb0000000/2097152, 0xecf00000/1048576, I/O @ 0x0000f000/256, BIOS @ 0x????????/131072 Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (--) PCI:*(57@0:0:0) 1002:164e:1458:d000 rev 194, Mem @ 0x80000000/268435456, 0x90000000/2097152, 0xece00000/524288, I/O @ 0x0000e000/256 Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) LoadModule: "glx" Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) Module glx: vendor="X.Org Foundation" Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: compiled for 1.21.1.4, module version = 1.0.0 Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: ABI class: X.Org Server Extension, version 10.0 Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) Scanning /usr/share/X11/xorg_pci_ids directory for additional PCI ID's supported by the drivers Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (==) Matched ati as autoconfigured driver 0 Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (==) Matched modesetting as autoconfigured driver 1 Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (==) Matched fbdev as autoconfigured driver 2 Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (==) Matched vesa as autoconfigured driver 3 Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (==) Assigned the driver to the xf86ConfigLayout Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) LoadModule: "ati" Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (WW) Warning, couldn't open module ati Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) Failed to load module "ati" (module does not exist, 0) Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) LoadModule: "modesetting" Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) Module modesetting: vendor="X.Org Foundation" Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: compiled for 1.21.1.4, module version = 1.21.1 Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: Module class: X.Org Video Driver Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: ABI class: X.Org Video Driver, version 25.2 Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) LoadModule: "fbdev" Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) Failed to load /usr/lib64/xorg/modules/drivers/fbdev_drv.so: /usr/lib64/xorg/modules/drivers/fbdev_drv.so: undefined symbol: fbdevHWSave Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) Failed to load module "fbdev" (loader failed, 0) Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) LoadModule: "vesa" Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) Failed to load /usr/lib64/xorg/modules/drivers/vesa_drv.so: /usr/lib64/xorg/modules/drivers/vesa_drv.so: undefined symbol: VBESetModeParameters Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) Failed to load module "vesa" (loader failed, 0) Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) modesetting: Driver for Modesetting Kernel Drivers: kms Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) open /dev/dri/card0: No such file or directory Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (WW) Falling back to old probe method for modesetting Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) open /dev/dri/card0: No such file or directory Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) Screen 0 deleted because of no matching config section. Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) UnloadModule: "modesetting" Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) Device(s) detected, but none match those in the config file. Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: Fatal server error: Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) no screens found(EE) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 Richard Biener <rguenther@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 https://bugzilla.suse.com/show_bug.cgi?id=1207516#c1 --- Comment #1 from Richard Biener <rguenther@suse.com> --- Installed packages are xorg-x11-server-21.1.4-150500.2.1.x86_64 kernel-default-5.14.21-150500.35.3.x86_64 kernel-firmware-amdgpu-20221031-150500.1.1.noarch kernel-firmware-radeon-^^^ I suspect missing PCI-IDs and firmware. There's more recent SLE 15 SP5 snapshots that I did not test yet. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 Richard Biener <rguenther@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 https://bugzilla.suse.com/show_bug.cgi?id=1207516#c2 --- Comment #2 from Richard Biener <rguenther@suse.com> --- SP5 sources have newer kernel-firmware than /mounts/dist/install/SLP/SLE-15-SP5-Full-LATEST/x86_64/DVD1/Module-Basesystem/noarch/kernel-firmware-radeon-20221031-150500.1.1.noarch.rpm, so that might fix that part. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 https://bugzilla.suse.com/show_bug.cgi?id=1207516#c3 --- Comment #3 from Richard Biener <rguenther@suse.com> --- With Beta3 of SLE15 SP5 we get a little bit further (KMS seems to work), but then Xorg still complains a lot and eventually segfaults, same when plugging the monitor into the 6950 XT. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 https://bugzilla.suse.com/show_bug.cgi?id=1207516#c4 --- Comment #4 from Richard Biener <rguenther@suse.com> --- Using the Tumbleweed install media X based install works fine (openSUSE-Tumbleweed-NET-x86_64-Snapshot20230123-Media.iso). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 https://bugzilla.suse.com/show_bug.cgi?id=1207516#c5 --- Comment #5 from Takashi Iwai <tiwai@suse.com> --- Try the latest package of kernel-firmware-* for SLE15-SP5 as well as the latest kernel package (the best would be from OBS Kernel:SLE15-SP5 repo). The DRM backports came fairly late, and the AMDGPU firmware update was included in the last week. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 https://bugzilla.suse.com/show_bug.cgi?id=1207516#c6 --- Comment #6 from Stefan Dirsch <sndirsch@suse.com> --- Hmm. This undefined symbols issue should have been fixed with ------------------------------------------------------------------- Sat May 14 10:44:09 UTC 2022 - Stefan Dirsch <sndirsch@suse.com> - set SUSE_ZNOW to 0 (boo#1197994) in xf86-video-fbdev package (check with "rpm --changelog -q xf86-video-fbdev"). But there is no need to still use fbdev driver, if there is a KMS driver active. Then you can just use "modesetting" driver (being our default). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 Darren Davis <ddavis@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ddavis@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 https://bugzilla.suse.com/show_bug.cgi?id=1207516#c7 --- Comment #7 from Richard Biener <rguenther@suse.com> --- (In reply to Takashi Iwai from comment #5)
Try the latest package of kernel-firmware-* for SLE15-SP5 as well as the latest kernel package (the best would be from OBS Kernel:SLE15-SP5 repo). The DRM backports came fairly late, and the AMDGPU firmware update was included in the last week.
OK, so with SP5 Beta3 _installed_ the X server starts up but it uses the modesetting driver, it also considers "ati" but that driver doesn't exist. The machine is up and running at 10.168.4.27. It seems that Beta3 still misses the kernel-firmware update which I can see in the source tree already. I've installed the newly built -amdgpu and -radeon firmware packages, now I see glamorgl initialized for the RX 6950 XT but still modeset for the rest (guess that's OK). The amdgpu driver is loaded. That means Beta4 will be good here, the installer X crash still remains to be investigated but as I can't reproduce from an installed system I'm not sure what I can provide. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 https://bugzilla.suse.com/show_bug.cgi?id=1207516#c8 --- Comment #8 from Stefan Dirsch <sndirsch@suse.com> --- Yeah. modeset + glamor is our default meanwhile. Absolutely fine. No need o experiment with amdgpu or radeon X driver. As long as you have no special needs. I would expect with the new firmware on the installation system the X crash will go away as well. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 https://bugzilla.suse.com/show_bug.cgi?id=1207516#c9 --- Comment #9 from Richard Biener <rguenther@suse.com> --- I've tried the NET install of Leap 15.5 Build395.1 but that wants to download a matching image and then stops on re-starting with that with a black screen (whatever it should do here and whether it is supposed to do this is unknown). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 https://bugzilla.suse.com/show_bug.cgi?id=1207516#c10 --- Comment #10 from Richard Biener <rguenther@suse.com> --- With the public beta the installer now has the firmware files that make the graphics work in the installed system from the previous beta. But the X server still crashes in the installer (nomodeset works). I've put a core file of the X server crashing at /suse/rguenther/SLE15-SP5-PublicBeta-X.org-core -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 https://bugzilla.suse.com/show_bug.cgi?id=1207516#c11 --- Comment #11 from Richard Biener <rguenther@suse.com> --- Created attachment 865052 --> https://bugzilla.suse.com/attachment.cgi?id=865052&action=edit Xorg logfile showing the crash Logfile from the X server -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 https://bugzilla.suse.com/show_bug.cgi?id=1207516#c12 --- Comment #12 from Richard Biener <rguenther@suse.com> --- Graphics in the installed system works fine. The firmware package in the public beta is of the version 20230110, the same version that made the previous beta work when installed manually. md5sums of the amdgpu files in the installer are the same as those in this version. The changes done in Februrary to the kernel-firmware source package are not yet reflected in the public beta. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 https://bugzilla.suse.com/show_bug.cgi?id=1207516#c13 --- Comment #13 from Stefan Dirsch <sndirsch@suse.com> --- # gdb /usr/bin/Xorg SLE15-SP5-PublicBeta-X.org-core [...] Reading symbols from /usr/bin/Xorg... Reading symbols from /usr/lib/debug/usr/bin/Xorg-21.1.4-150500.3.1.x86_64.debug... warning: Can't open file /dev/dri/card1 during file-backed mapping note processing [New LWP 6027] [New LWP 6032] [New LWP 6030] [New LWP 6033] [New LWP 6031] [New LWP 6029] warning: Section `.reg-xstate/6027' in core file too small. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `X'. Program terminated with signal SIGABRT, Aborted. warning: Section `.reg-xstate/6027' in core file too small. #0 __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:51 51 } [Current thread is 1 (Thread 0x7fe543daf980 (LWP 6027))] (gdb) bt #0 __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x00007fe541f44355 in __GI_abort () at abort.c:79 #2 0x000055a34531264a in OsAbort () at utils.c:1352 #3 0x000055a345318193 in AbortServer () at log.c:879 #4 0x000055a345318fb5 in FatalError (f=f@entry=0x55a3453495d0 "Caught signal %d (%s). Server aborting\n") at log.c:1017 #5 0x000055a34530f543 in OsSigHandler (signo=11, sip=<optimized out>, unused=<optimized out>) at osinit.c:156 #6 <signal handler called> #7 0x000055a3451e8e3e in InitOutput (pScreenInfo=pScreenInfo@entry=0x55a3453dd320 <screenInfo>, argc=argc@entry=1, argv=argv@entry=0x7fffdc7a5958) at xf86Init.c:884 #8 0x000055a3451aad25 in dix_main (argc=1, argv=0x7fffdc7a5958, envp=<optimized out>) at main.c:192 #9 0x00007fe541f2d29d in __libc_start_main (main=0x55a345194790 <main>, argc=1, argv=0x7fffdc7a5958, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffdc7a5948) at ../csu/libc-start.c:308 #10 0x000055a3451947ca in _start () at ../sysdeps/x86_64/start.S:120 (gdb) frame 7 #7 0x000055a3451e8e3e in InitOutput (pScreenInfo=pScreenInfo@entry=0x55a3453dd320 <screenInfo>, argc=argc@entry=1, argv=argv@entry=0x7fffdc7a5958) at xf86Init.c:884 884 AttachUnboundGPU(xf86Screens[scrnum]->pScreen, xf86GPUScreens[i]->pScreen); (gdb) p xf86Screens[scrnum]->pScreen Cannot access memory at address 0x10 (gdb) p xf86Screens[scrnum] $1 = (ScrnInfoPtr) 0x0 (gdb) p scrnum $2 = 2 (gdb) l 879 } 880 } 881 882 for (i = 0; i < xf86NumGPUScreens; i++) { 883 int scrnum = xf86GPUScreens[i]->confScreen->screennum; 884 AttachUnboundGPU(xf86Screens[scrnum]->pScreen, xf86GPUScreens[i]->pScreen); 885 } 886 887 xf86AutoConfigOutputDevices(); 888 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 https://bugzilla.suse.com/show_bug.cgi?id=1207516#c14 --- Comment #14 from Stefan Dirsch <sndirsch@suse.com> --- 3 screens? Weird. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 https://bugzilla.suse.com/show_bug.cgi?id=1207516#c15 --- Comment #15 from Stefan Dirsch <sndirsch@suse.com> --- Hmm. Can you reproduce this issue in installed system when using this /etc/X11/xorg.conf (which is being used during installation) Section "Device" Identifier "modesetting" Driver "modesetting" Option "PreferCloneMode" "true" Option "AccelMethod" "none" EndSection Section "Screen" Identifier "modesetting" Device "modesetting" EndSection Section "Device" Identifier "fbdev" Driver "fbdev" EndSection Section "Screen" Identifier "fbdev" Device "fbdev" EndSection Section "Device" Identifier "vesa" Driver "vesa" EndSection Section "Screen" Identifier "vesa" Device "vesa" EndSection Section "ServerLayout" Identifier "Layout" Screen "modesetting" Screen "fbdev" Screen "vesa" EndSection -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 https://bugzilla.suse.com/show_bug.cgi?id=1207516#c16 --- Comment #16 from Stefan Dirsch <sndirsch@suse.com> --- Ok. This is for TW. On sle15-sp5 it's this one: Section "Device" Identifier "vboxvideo" Driver "vboxvideo" EndSection Section "Screen" Identifier "vboxvideo" Device "vboxvideo" EndSection Section "Device" Identifier "vmware" Driver "vmware" EndSection Section "Screen" Identifier "vmware" Device "vmware" EndSection Section "Device" Identifier "modesetting" Driver "modesetting" Option "PreferCloneMode" "true" Option "AccelMethod" "none" EndSection Section "Screen" Identifier "modesetting" Device "modesetting" EndSection Section "Device" Identifier "fbdev" Driver "fbdev" EndSection Section "Screen" Identifier "fbdev" Device "fbdev" EndSection Section "Device" Identifier "vesa" Driver "vesa" EndSection Section "Screen" Identifier "vesa" Device "vesa" EndSection Section "ServerLayout" Identifier "Layout" Screen "vboxvideo" Screen "vmware" Screen "modesetting" Screen "fbdev" Screen "vesa" EndSection -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |IN_PROGRESS CC| |rguenther@suse.com Component|Kernel |X.Org Assignee|kernel-bugs@opensuse.org |gfx-bugs@suse.de QA Contact|qa-bugs@suse.de |gfx-bugs@suse.de Flags| |needinfo?(rguenther@suse.co | |m) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 https://bugzilla.suse.com/show_bug.cgi?id=1207516#c17 Richard Biener <rguenther@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(rguenther@suse.co | |m) | --- Comment #17 from Richard Biener <rguenther@suse.com> --- Created attachment 865061 --> https://bugzilla.suse.com/attachment.cgi?id=865061&action=edit xorg.conf from the installer(?) I can indeed reproduce the segfault with the /etc/X11/xorg.conf.install file that's left behind (attached) and that looks remarkably similar to the snippet you quote. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207516 https://bugzilla.suse.com/show_bug.cgi?id=1207516#c18 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(rguenther@suse.co | |m) --- Comment #18 from Stefan Dirsch <sndirsch@suse.com> --- Yeah. It's /etc/X11/xorg.conf.install ! :-) Ok. I think it's boo#1192678 Fix: https://github.com/openSUSE/installation-images/pull/543 Remove vboxvideo and vmware entries in this installer xorg.conf. And try again with it. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com