Comment 12 for bug 871344

The installation of the post-release updates through jockey failed. I've
attached the new log. Attempting to revert to the original package.

Jockey claimed to revert to the original driver successfully, but I was
unable to test the jockey based installation due (I believe) to some
unreleated problems I was having with compiz. After deleting my compiz
configurations (again, unrelated) and manually installing fglrx-updates, my
system is up and running with fglrx enabled. It appears to me that the main
issue here is that fglrx is lacking the kernel source/header dependencies.

Regards,
Jon

On Thu, Oct 13, 2011 at 11:09 AM, <email address hidden> <email address hidden> wrote:

> After installing linux-source-3.0.0 and linux-headers-3.0.0-12-generic, the
> apt-get completed successfully and jockey is currently displaying a green
> "activated" icon besides the (non post-update) fglrx driver. I haven't
> tried restarting to test it yet because I'm going to install the
> post-release updates first.
>
> On Thu, Oct 13, 2011 at 10:44 AM, <email address hidden> <email address hidden>wrote:
>
>> I'm not sure if this is because of my chroot environment or not, but while
>> attempting to reinstall fglrx with the command you suggested, I get several
>> hundred lines of this:
>>
>> FATAL: Could not load /lib/modules/2.6.35-30-generic/modules.dep: No such
>> file or directory
>>
>> Followed immediately by
>>
>> Loading new fglrx-8.881 DKMS files...
>> It is likely that 2.6.35-30-generic belongs to a chroot's host
>> Building only for 3.0.0-12-generic
>> Building for architecture x86_64
>> Module build for the currently running kernel was skipped since the
>> kernel source for this kernel does not seem to be installed.
>> update-initramfs: deferring update (trigger activated)
>> Processing triggers for bamfdaemon ...
>> Rebuilding /usr/share/applications/bamf.index...
>> Processing triggers for gnome-menus ...
>> Setting up fglrx-amdcccle (2:8.881-0ubuntu3) ...
>> Processing triggers for initramfs-tools ...
>> update-initramfs: Generating /boot/initrd.img-3.0.0-12-generic
>> Processing triggers for libc-bin ...
>> ldconfig deferred processing now taking place
>>
>>
>> Because of the Kernel complaints, I decided to do a bit more digging.
>> Clearly CHRoot is causing the kernel version issue listed above.
>> root@Hercules:/# uname -r
>> 2.6.35-30-generic
>> root@Hercules:/# ls /boot
>> abi-3.0.0-11-generic config-3.0.0-12-generic
>> initrd.img-3.0.0-11-generic memtest86+.bin
>> System.map-3.0.0-12-generic vmlinuz-3.0.0-11-generic
>> abi-3.0.0-12-generic grub
>> initrd.img-3.0.0-12-generic memtest86+_multiboot.bin
>> vmcoreinfo-3.0.0-11-generic vmlinuz-3.0.0-12-generic
>> config-3.0.0-11-generic initrd.img-2.6.35-30-generic
>> lost+found System.map-3.0.0-11-generic
>> vmcoreinfo-3.0.0-12-generic
>>
>> However, it looks like it's still attempting to build for the 3.0 kernel,
>> but fglrx appears to be missing the dependency for linux-source-3.0.0, so
>> I'll attempt to install the sources for 3.0 and report back.
>>
>> On Wed, Oct 12, 2011 at 11:04 PM, Daniel van Vugt <email address hidden>wrote:
>>
>>> To clarify, I'm trying to remove Jockey from the equation. Installing
>>> fglrx directly and getting a copy of make.log will tell us exactly why
>>> fglrx is failing to install.
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https://bugs.launchpad.net/bugs/871344
>>>
>>> Title:
>>> Jockey cannot install FGLRX (AMD Graphics Driver)
>>>
>>> To manage notifications about this bug go to:
>>>
>>> https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/871344/+subscriptions
>>>
>>
>>
>