[Bug 593878] New: X-Server could not start with fglrx-driver and auto-configuration
http://bugzilla.novell.com/show_bug.cgi?id=593878 http://bugzilla.novell.com/show_bug.cgi?id=593878#c0 Summary: X-Server could not start with fglrx-driver and auto-configuration Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs@forge.provo.novell.com ReportedBy: freespacer@gmx.de QAContact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- Created an attachment (id=352480) --> (http://bugzilla.novell.com/attachment.cgi?id=352480) Patch for X-Server package (xorg-x11-server) User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.3) Gecko/20100401 SUSE/3.6.3-1.1 Firefox/3.6.3 Hi, in the past I always installed the proprietary fglrx-driver. If I start the X-Server with the auto-configuration, it failed. This also happens with openSUSE 11.2. Why it fails? I looked in the logfile /var/log/Xorg.0.log: .. (II) Module vgahw: vendor="X.Org Foundation" compiled for 1.6.5, module version = 0.1.0 ABI class: X.Org Video Driver, version 5.0 (II) fglrx(0): PCI bus 1 card 0 func 0 (II) fglrx(0): Creating default Display subsection in Screen section "Builtin Default fglrx Screen 0" for depth/fbbpp 8/8 (EE) fglrx(0): Given depth (8) is not supported by fglrx driver (EE) fglrx(0): PreInitVisual failed (EE) fglrx(0): PreInit failed (II) fglrx(0): === [atiddxPreInit] === end SetVBEMode failed (II) UnloadModule: "fglrx" (II) UnloadModule: "vgahw" (II) Unloading /usr/lib64/xorg/modules//libvgahw.so (II) UnloadModule: "fglrxdrm" (EE) Screen(s) found, but none have a usable configuration. We see here that the X-Server attempts to initialize the fglrx-driver with a screen depth of 8bit. But the fglrx-driver does not want to be initialized with 8bit or 16bit screen depth. If you read the 9th question in the FAQ from AMD/ATI, the fglrx-driver supports only 24bit screen depth: http://ati.amd.com/products/catalyst/linux.html#9 If I have patched the X server, then the X-Server runs without any issues with the driver in 24bit mode. I add a patch to solve this issue. The new auto-configuration is as follows: (==) --- Start of built-in configuration --- Section "Device" Identifier "Builtin Default fglrx Device 0" Driver "fglrx" EndSection Section "Screen" Identifier "Builtin Default fglrx Screen 0" Device "Builtin Default fglrx Device 0" DefaultDepth 24 EndSection Section "Device" Identifier "Builtin Default radeonhd Device 0" Driver "radeonhd" EndSection Section "Screen" Identifier "Builtin Default radeonhd Screen 0" Device "Builtin Default radeonhd Device 0" EndSection Section "Device" Identifier "Builtin Default ati Device 0" Driver "ati" EndSection Section "Screen" Identifier "Builtin Default ati Screen 0" Device "Builtin Default ati Device 0" EndSection Section "Device" Identifier "Builtin Default fbdev Device 0" Driver "fbdev" EndSection Section "Screen" Identifier "Builtin Default fbdev Screen 0" Device "Builtin Default fbdev Device 0" EndSection Section "Device" Identifier "Builtin Default vesa Device 0" Driver "vesa" EndSection Section "Screen" Identifier "Builtin Default vesa Screen 0" Device "Builtin Default vesa Device 0" EndSection Section "ServerLayout" Identifier "Builtin Default Layout" Screen "Builtin Default fglrx Screen 0" Screen "Builtin Default radeonhd Screen 0" Screen "Builtin Default ati Screen 0" Screen "Builtin Default fbdev Screen 0" Screen "Builtin Default vesa Screen 0" EndSection (==) --- End of built-in configuration --- https://build.opensuse.org/request/diff/36958 Regards, Sebastian Reproducible: Always Steps to Reproduce: 1. installed the proprietary fglrx-driver 2. start the X-Server without any file of configuration 3. Actual Results: X-Server crashed with auto-configuration. Expected Results: X-Server start with auto-configuration -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=593878 http://bugzilla.novell.com/show_bug.cgi?id=593878#c Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED AssignedTo|bnc-team-xorg-bugs@forge.pr |sndirsch@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=593878 http://bugzilla.novell.com/show_bug.cgi?id=593878#c1 Matthias Hopf <mhopf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mhopf@novell.com --- Comment #1 from Matthias Hopf <mhopf@novell.com> 2010-04-06 13:14:49 UTC --- I assume the driver doesn't call xf86SetDepthBpp() in the appropriate way - that would select 24bit as default depth. I would argue against patching the Xserver to work around a driver issue, especially as the driver works with an xorg.conf (which is the usual case for fglrx) - and you wouldn't get this patch upstream in any case. However, whether we take it or not is Stefan's call. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=593878 http://bugzilla.novell.com/show_bug.cgi?id=593878#c2 --- Comment #2 from Sebastian Siebert <freespacer@gmx.de> 2010-04-06 15:14:19 UTC --- @Matthias: It's good, if you have an own opinion. We should thoroughly discuss it. I look a little further, because our newbees in openSUSE can not deal with the console. So, the X-Server runs with this patch out of the box. The user can still create a configuration file, if he so wishes. If you read this news of today (06.04.2010): h-open.com (english): http://www.h-online.com/open/news/item/X-Server-1-8-with-new-configuration-m... heise.de (german): http://www.heise.de/newsticker/meldung/X-Server-1-8-bringt-neue-Konfiguratio... Quote from h-online.com: "AMD's proprietary drivers are not as current and fail to even support series 1.7 of X Server. AMD apparently intends to remedy this situation in the coming weeks but it is unknown whether the planned modifications will also provide X Server 1.8 support." If AMD / ATI has completed the support for the X server, then we can remove the patch. But we know that we are unfortunately not able to rely on AMD / ATI. Hmmm, what do you think? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=593878 http://bugzilla.novell.com/show_bug.cgi?id=593878#c3 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED Target Milestone|--- |Milestone 5 --- Comment #3 from Stefan Dirsch <sndirsch@novell.com> 2010-04-06 16:24:33 UTC --- I believe the patch makes sense and applied it for openSUSE 11.3. Nevertheless it's a driver bug ... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=593878 http://bugzilla.novell.com/show_bug.cgi?id=593878#c4 --- Comment #4 from Matthias Hopf <mhopf@novell.com> 2010-04-07 12:11:36 UTC --- (In reply to comment #2)
patch. But we know that we are unfortunately not able to rely on AMD / ATI.
I perfectly agree with that. :-/ -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com