Feisty crashes at login screen after enabling the proprietay driver

Bug #96652 reported by Emiliano
6
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.20 (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: xorg-driver-fglrx

Once enabling the proprietary driver, after the required shutdown, feisty crashes at login screen. I can write login and password but the gnome session doesn't start. I can only hear the startup music just a few moment before the crash
I guess this depends on a misconfiguration in xorg.conf generated by feisty once the driver is enabled.

Revision history for this message
RealMurphy (carsten-welcomes-you) wrote :
Download full text (3.6 KiB)

I'll add some info to this, since I experience the same behaviour. Might be related to bugs #98684, #98721 and/or #99003 and/or more.

I'm using kubuntu feisty beta ("release") with latest updates from today. Running with xorg driver "ati" is fine, using fglrx is not.

xorg.conf (part):

Section "Device"
  identifier "ATI Technologies Inc Radeon R300 NE [Radeon 9500 Pro]"
  boardname "ati"
  busid "PCI:2:0:0"
  driver "fglrx"
  screen 0
EndSection

Hardware:
02:00.0 VGA compatible controller: ATI Technologies Inc Radeon R300 NE [Radeon 9500 Pro] (prog-if 00 [VGA])
        Subsystem: ATI Technologies Inc Radeon R300 NE [Radeon 9500 Pro]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 255 (2000ns min), Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 19
        Region 0: Memory at d0000000 (32-bit, prefetchable) [size=128M]
        Region 1: I/O ports at d000 [size=256]
        Region 2: Memory at e5000000 (32-bit, non-prefetchable) [size=64K]
        [virtual] Expansion ROM at e4000000 [disabled] [size=128K]
        Capabilities: [58] AGP version 3.0
                Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
                Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit- FW- Rate=<none>
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

02:00.1 Display controller: ATI Technologies Inc Radeon R300 [Radeon 9500 Pro] (Secondary)
        Subsystem: ATI Technologies Inc Radeon R300 NE [Radeon 9500 Pro]
        Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Region 0: Memory at d8000000 (32-bit, prefetchable) [disabled] [size=128M]
        Region 1: Memory at e5010000 (32-bit, non-prefetchable) [disabled] [size=64K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Error message from /var/log/Xorg.0.log:

II) fglrx(0): Primary Controller - CRT on primary DAC
(II) fglrx(0): Internal Desktop Setting: 0x00000008
(II) fglrx(0): POWERplay not supported on this hardware
(EE) fglrx(0): === [swlDalHelperAddCustomizeMode] === CWDDEDI_DisplayGetSetModeTimingOverride failed: 7
(EE) fglrx(0): === [swlDalHelperAddCustomizeMode] === CWDDEDI_DisplayGetSetModeTimingOverride failed: 7
(EE) fglrx(0): === [swlDalHelperAddCustomizeMode] === CWDDEDI_DisplayGetSetModeTimingOverride failed: 7

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c5d91]
1: [0xffffe420]
2: /usr/lib/xorg/modules/drivers//fglrx_drv.so [0xb7567e5f]
3: /usr/lib/xorg/modules/drivers//fglrx_drv.so(DALCWDDE+0x1a2) [0xb75664a2]
4: /usr/lib/xorg/modules/drivers//fglrx_drv.so(swlDalHelperAddCustomizeMod...

Read more...

Revision history for this message
Bryce Harrington (bryce) wrote :

This is reported fixed in the latest fglrx driver, which will be rolled out in Gutsy soonish.

   - Resolved issues since 8.34.8:
      + In certain AGP graphics cards the system no longer ceases to
        respond when switching from the X-Server display to a text console.
      + The screen no longer turns black if the X-Server is terminated
        from the text console. This condition was known to occur only on
        certain laptop configurations. [ATI# 737-26829].
      + Logging out of a session to the graphical login manager no longer
        crashes the Xserver

Changed in linux-restricted-modules-2.6.20:
importance: Undecided → High
status: Unconfirmed → In Progress
Revision history for this message
Bryce Harrington (bryce) wrote :

I've packaged the fglrx driver, and put the debs up for testing:

    http://people.ubuntu.com/~bryce/Testing/

These are the packages I installed in my tests: fglrx-control, xorg-driver-fglrx, fglrx-kernel-source, linux-restricted-modules-common, linux-restricted-modules-2.6.22

Also turn off Composite if you have it on (fglrx doesn't support it)
fglrxinfo and glxgears are useful to verify its working

Please report back if the new fglrx reports this login screen crash. I suspect it will, but haven't reproduced this issue on my own system so am not sure.

Changed in linux-restricted-modules-2.6.20:
status: In Progress → Fix Committed
Revision history for this message
Bryce Harrington (bryce) wrote :

This bug was fixed in newer versions of fglrx, which is now available
in Gutsy.

There are no plans to add fglrx 8.37.6 to Feisty officially, but I've
created .debs for Feisty users needing this fix. These are available
at http://people.ubuntu.com/~bryce/Testing/fglrx-8.37.6-Feisty/
Despite being unofficial, please feel welcome to report new bugs with
these packages to launchpad.

Please help spread word and help fellow users in installing it!

Changed in linux-restricted-modules-2.6.20:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.