after update to 9.10 ati mobillty rad. HD 3470 driver does not work
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fglrx-installer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
After update ubuntu from ver 9.04 to 9.10 don`t work ati driver HD 3470. Looks like driver is not install.
ProblemType: Crash
Architecture: i386
AssertionMessage: amdcccle: ../../src/
CrashCounter: 1
Date: Sun Nov 1 12:31:12 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/amdcccle
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: ASUSTeK Computer Inc. M50SA
Package: fglrx-amdcccle 2:8.660-0ubuntu4
ProcCmdLine: root=UUID=
ProcCmdline: amdcccle
ProcEnviron:
LANGUAGE=
LANG=ru_RU.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
xserver-xorg 1:7.4+3ubuntu7
libgl1-mesa-glx 7.6.0-1ubuntu4
libdrm2 2.4.14-1ubuntu1
xserver-
xserver-
Signal: 6
SourcePackage: fglrx-installer
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/tls/
abort () from /lib/tls/
__assert_fail () from /lib/tls/
_XRead () from /usr/lib/
Title: amdcccle assert failure: amdcccle: ../../src/
Uname: Linux 2.6.28-15-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(gnome-
(gnome-
(polkit-
(nautilus:2500): Eel-CRITICAL **: eel_preferences
(gnome-
dmi.bios.date: 01/14/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 202
dmi.board.
dmi.board.name: M50SA
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: M50SA
dmi.product.
dmi.sys.vendor: ASUSTeK Computer Inc.
fglrx: Not loaded
system:
distro: Ubuntu
architecture: i686kernel: 2.6.28-15-generic
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #452028, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.