FGLRX crashed after upgrading the kernel from 2.6.38-8-generic to 2.6.39-0-generic

[ali110ali]

after upgrading the kernel from 2.6.38-8-generic to 2.6.39-0-generic this problem accured.
and system not booted properly.i have to starup system in recovery mode (failgraphic) and remove FGLRX package.
after this operation system start up normaly.
my Notebook is MSI CX620-H that have two graphic card.
in windows seven i am able to change between intel and RADEON Graphic card for power saving.
can i do this operation in ubuntu ?

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: fglrx 2:8.840-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic-pae 2.6.39-rc5
Uname: Linux 2.6.39-0-generic-pae i686
Architecture: i386
Date: Fri Jun 3 18:13:02 2011
DistUpgraded: Fresh install
DistroCodename: natty
DistroVariant: ubuntu
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
PackageVersion: 2:8.840-0ubuntu4
SourcePackage: fglrx-installer
Title: package fglrx 2:8.840-0ubuntu4 failed to install/upgrade: fglrx kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2
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 1:6.14.0-0ubuntu4
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

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 790482, so it 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. Feel free to continue to report any other bugs you may find.