X hangs at startup (segfault in fglrx?) after Natty beta upgrade

Bug #763130 reported by Jon Bailey
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Just did Natty beta upgrade, rebooted. System hung during X startup. Had
to use Alt+SysRq+R to get keyboard control back and switch to another
virtual console. Xorg.0.log mentioned that fglrx had segfaulted.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: fglrx (not installed)
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
Date: Sat Apr 16 15:50:24 2011
DistUpgraded: Log time: 2011-04-16 10:38:56.096193
DistroCodename: natty
DistroVariant: ubuntu
DkmsStatus:
 virtualbox-ose, 4.0.4, 2.6.38-8-generic, x86_64: installed
 virtualbox-ose, 4.0.4, 2.6.35-28-generic, x86_64: installed
 fglrx, 8.831.2, 2.6.35-28-generic, x86_64: installed
GraphicsCard:
 ATI Technologies Inc 760G [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8388]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: System manufacturer System Product Name
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=16e9bee0-f4e6-4299-a27f-d3247f88fbc9 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
Renderer: Unknown
SourcePackage: fglrx-installer
UpgradeStatus: Upgraded to natty on 2011-04-16 (0 days ago)
dmi.bios.date: 08/24/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0802
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A78LT-M
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd08/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78LT-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu12
version.libdrm2: libdrm2 2.4.23-1ubuntu6
version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu1
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7

Revision history for this message
Jon Bailey (hobart) wrote :
Revision history for this message
Jon Bailey (hobart) wrote :

Worked around problem by purging all 'fglrx' packages, then using updatedb/locate to find all files on the filesystem containing the string "fglrx", checking to see which of them were actually owned by packages with:

for filename in $(locate fglrx); do dpkg-query -S $filename; done

and renaming out every file that wasn't part of a package (the only two that were were:
app-install-data: /usr/share/app-install/desktop/fglrx-driver.desktop
x11-common: /usr/share/apport/package-hooks/source_fglrx-installer.py
)

With all of those renamed out, X started OK (non-accelerated, using the 'radeon' driver)

Revision history for this message
Steffen Rusitschka (rusi) wrote :

I've had the same issue on my Upgrade from Maverick to Natty. I didn't use fglrx on Maverick, but had it installed once. Mainly removing /usr/lib/fglrx and /usr/lib32/fglrx manually solved the problem. I guess those where some leftovers from an incomplete Maverick fglrx uninstall.

Revision history for this message
Christian Roessner (christian-roessner-net) wrote :

I can confirm this bug, too. But I would need the fglrx driver working, because the radeon-HDMI-sound output does not work. It did in Maverick.

Changed in fglrx-installer (Ubuntu):
status: New → Confirmed
Revision history for this message
Michael B (a-launchpad-bretterklieber-com) wrote :

same problem here, after upgrade from 10.10 X doesent start, fglrx driver crashed:

Revision history for this message
Michael B (a-launchpad-bretterklieber-com) wrote :

I had to completely remove the fglrx, removed xorg.conf, rebootet with opensource radeon driver, and than I did a fresh install with jockey, this solved the problem.

It looks like a problem with the upgrade procedure, the fglrx kernel module was not build

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

Hey hobart,

You filed this bug report against natty, but I see it's still open and
doesn't appear to have much activity recently. So, now that oneiric
is released and stable, this may be a good point for you to upgrade
and re-test if this issue is still present there.

If it's solved in the new release and you think it's worth backporting
the fix, please indicate that. Or if having the fix in the new release
is good enough, feel free to close out the bug (or let us know and we'll
close it.)

If it's not solved, leave the bug report open. I can't promise we'll
get to it (we get way more bugs filed than we can usually get to), but
your testing and feedback can help out if and when we do.

Changed in fglrx-installer (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
bugbot (bugbot) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in fglrx-installer (Ubuntu):
status: Incomplete → Expired
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.