Maybe I've done something wrong, but after getting ATI drivers straight from their website - ver. 11.2 and after building the package with parameter Ubuntu/natty, I've become a message about incompatibility of kernel, or something... then after restart, I've become the same message from gnome too. I' sorry about my enlglish and about my "noob" terms. If I try to use the standard aditional driver installation from menu, than I've became only a black screen state after reboot. After some reboots I've become just a state in which has Ubuntu booted, 3D acceleration was working, but any change of resolution, or connecting of secondary screen device, or fullscreen mode of a game has come to a dead state with black screen.
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: fglrx 2:8.821-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Sat May 21 17:13:27 2011
DistUpgraded: Log time: 2011-05-19 11:20:32.141300
DistroCodename: natty
DistroVariant: ubuntu
ErrorMessage: fglrx kernel module failed to build
PackageVersion: N/A
SourcePackage: fglrx-installer
Title: package fglrx 2:8.821-0ubuntu1 failed to install/upgrade: fglrx kernel module failed to build
UpgradeStatus: Upgraded to natty on 2011-05-19 (2 days ago)
version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2
version.ia32-libs: ia32-libs 20090808ubuntu13
version.libdrm2: libdrm2 2.4.23-1ubuntu6
version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7
Hey ludek-witz,
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.