Jockey cannot install FGLRX (AMD Graphics Driver)

It's likely this failure to install is caused by a DKMS build failure. Could you please find the make.log file using this command in a terminal?:

find /var/lib/dkms/fglrx -name make.log

Then please attach the file to this bug and change the status back to New. Thanks in advance...

In fact, you may need to use this command to find the log file:

find /var/lib/dkms/fglrx* -name make.log

Hey,

Sorry for the late response. I was on an extended vacation. I won't have
physical access to the computer for a few hours, and because of this bug I'm
currently still running Ubuntu 10.10. However, I ssh'd into the computer
and managed to run the search command you provided on Sunday.
Unfortunately, it didn't find anything. I can only assume that the files
were cleared when I shut down the computer? What do I need to do to
correctly generate that log file?

alaric@Hercules:/media$ sudo mount /dev/sdb7 sdb7
alaric@Hercules:/media$ cd sdb7
alaric@Hercules:/media/sdb7$ for x in sys proc dev ; do sudo mount -B /$x $x
; done
alaric@Hercules:/media/sdb7$ find var/lib/dkms/fglrx* -name make.log^C
alaric@Hercules:/media/sdb7$ sudo chroot .
root@Hercules:/# find /var/lib/dkms/fglrx -name make.log
find: `/var/lib/dkms/fglrx': No such file or directory
root@Hercules:/# find /var/lib/dkms/fglrx* -name make.log

Regards,
Jon Roose

P.S., I have not had a chance to re-test fglrx installation since my
original post.

On Sun, Oct 9, 2011 at 10:37 PM, Daniel van Vugt <email address hidden> wrote:

> In fact, you may need to use this command to find the log file:
>
> find /var/lib/dkms/fglrx* -name make.log
>
> --
> 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
>

Also, Let me add that the entire build folder appears to be empty.

alaric@Hercules:/media/sdb7/var/lib/dkms/fglrx-updates/8.881/build$ ls -a
. ..

On Wed, Oct 12, 2011 at 9:29 AM, <email address hidden> <email address hidden> wrote:

> Hey,
>
> Sorry for the late response. I was on an extended vacation. I won't have
> physical access to the computer for a few hours, and because of this bug I'm
> currently still running Ubuntu 10.10. However, I ssh'd into the computer
> and managed to run the search command you provided on Sunday.
> Unfortunately, it didn't find anything. I can only assume that the files
> were cleared when I shut down the computer? What do I need to do to
> correctly generate that log file?
>
> alaric@Hercules:/media$ sudo mount /dev/sdb7 sdb7
> alaric@Hercules:/media$ cd sdb7
> alaric@Hercules:/media/sdb7$ for x in sys proc dev ; do sudo mount -B /$x
> $x ; done
> alaric@Hercules:/media/sdb7$ find var/lib/dkms/fglrx* -name make.log^C
> alaric@Hercules:/media/sdb7$ sudo chroot .
> root@Hercules:/# find /var/lib/dkms/fglrx -name make.log
> find: `/var/lib/dkms/fglrx': No such file or directory
> root@Hercules:/# find /var/lib/dkms/fglrx* -name make.log
>
> Regards,
> Jon Roose
>
> P.S., I have not had a chance to re-test fglrx installation since my
> original post.
>
>
> On Sun, Oct 9, 2011 at 10:37 PM, Daniel van Vugt <email address hidden>wrote:
>
>> In fact, you may need to use this command to find the log file:
>>
>> find /var/lib/dkms/fglrx* -name make.log
>>
>> --
>> 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
>>
>
>

Having a similar issue and I see the same entries in your jockey.log file
cat /var/log/jockey.log | tail showed me this:

2011-10-12 09:56:33,157 DEBUG: fglrx_updates is not the alternative in use
2011-10-12 09:56:33,213 DEBUG: fglrx.enabled(fglrx_updates): target_alt None current_alt /usr/lib/fglrx/ld.so.conf other target alt None other current alt /usr/lib/fglrx/alt_ld.so.conf

2011-10-12 09:56:33,213 DEBUG: fglrx_updates is not the alternative in use
2011-10-12 09:56:33,243 DEBUG: fglrx.enabled(fglrx_updates): target_alt None current_alt /usr/lib/fglrx/ld.so.conf other target alt None other current alt /usr/lib/fglrx/alt_ld.so.conf

Yesterday I upgraded to 11.10 from 11.04 and tried to activate the "post-release updates" proprietary driver and got the same error message about the installation of the driver has failed. I'm going to try to boot off an older kernel and see if I can activate the driver.

Restarted in 2.6.38-11 and was able to install the flgrx driver (NOT the post-release driver)
the post-release driver gave the same error. when I was on the 3.0.0-12 kernel I was not able to install either driver.

##Here I think is where I tried the post-release driver
2011-10-12 10:38:50,986 DEBUG: fglrx_updates is not the alternative in use
2011-10-12 10:38:51,025 DEBUG: fglrx.enabled(fglrx): target_alt /usr/lib/fglrx/ld.so.conf current_alt /usr/lib/fglrx/ld.so.conf other target alt /usr/lib/fglrx/alt_ld.so.conf other current alt /usr/lib/fglrx/alt_ld.so.conf

##here is where I tried the old driver on the old kernel
2011-10-12 10:38:51,025 DEBUG: XorgDriverHandler(%s, %s).enabled(): No X.org driver set, not checking
2011-10-12 10:38:51,115 DEBUG: fglrx.enabled(fglrx): target_alt /usr/lib/fglrx/ld.so.conf current_alt /usr/lib/fglrx/ld.so.conf other target alt /usr/lib/fglrx/alt_ld.so.conf other current alt /usr/lib/fglrx/alt_ld.so.conf
2011-10-12 10:38:51,115 DEBUG: XorgDriverHandler(%s, %s).enabled(): No X.org driver set, not checking
2011-10-12 10:38:59,781 DEBUG: Shutting down

Could jockey have a mismatch with the kernel version and the available drivers?

If make.log is missing, please try reinstalling fglrx with this command:

  sudo apt-get install fglrx --reinstall

You should be able to do that in any terminal, including SSH.

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.

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
>

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
>>
>
>

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 t...

Please attach make.log which can be found with this command:
    find /var/lib/dkms/fglrx* -name make.log
But only if you continue to have problems. A log file from a working machine will not be useful.

There are several bugs already logged against fglrx regarding its compatibility with different kernels. I really just want to see make.log so we can identify which of the known bugs this one is. Because it is almost certainly a duplicate of an existing bug.

If this command succeeds, then you should have a working system:
   sudo apt-get install fglrx --reinstall

If that command fails however, please find and attach make.log as requested above.

Please ignore Jockey and its GUI while we are diagnosing this bug.

Unfortunately I got it working through apt-get before receiving this
message. I'm convinced that most of the problems were caused by the fact
that the 3.0.0 kernel sources and headers were not a dependency of the fglrx
or fglrx-updates packages. After installing them the apt-get commands you
suggested completed successfully. Before installing them, apt complained
about not having the sources available.

Thanks for your help. If I find time this weekend, I'll reinstall 11.10 and
try to replicate the bug on a clean system.

Jon

On Thu, Oct 13, 2011 at 11:00 PM, Daniel van Vugt <email address hidden> wrote:

> Please attach make.log which can be found with this command:
> find /var/lib/dkms/fglrx* -name make.log
> But only if you continue to have problems. A log file from a working
> machine will not be useful.
>
> There are several bugs already logged against fglrx regarding its
> compatibility with different kernels. I really just want to see make.log
> so we can identify which of the known bugs this one is. Because it is
> almost certainly a duplicate of an existing bug.
>
> If this command succeeds, then you should have a working system:
> sudo apt-get install fglrx --reinstall
>
> If that command fails however, please find and attach make.log as
> requested above.
>
> Please ignore Jockey and its GUI while we are diagnosing this bug.
>
> --
> 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
>

I'm having the same problem. Here is my make.log file:

DKMS make.log for fglrx-updates-8.881 for kernel 3.0.0-12-generic (x86_64)
Fri Oct 21 13:28:26 CST 2011
/usr/sbin/dkms: line 73: cd: /var/lib/dkms/fglrx/8.881/build: No such file or directory
AMD kernel module generator version 2.1
doing Makefile based build for kernel 2.6.x and higher
rm -rf *.c *.h *.o *.ko *.a .??* *.symvers
make -C /lib/modules/3.0.0-12-generic/build SUBDIRS=/var/lib/dkms/fglrx-updates/8.881/build/2.6.x modules
make[1]: Entering directory `/usr/src/linux-headers-3.0.0-12-generic'
  CC [M] /var/lib/dkms/fglrx-updates/8.881/build/2.6.x/firegl_public.o
  CC [M] /var/lib/dkms/fglrx-updates/8.881/build/2.6.x/kcl_acpi.o
  CC [M] /var/lib/dkms/fglrx-updates/8.881/build/2.6.x/kcl_agp.o
  CC [M] /var/lib/dkms/fglrx-updates/8.881/build/2.6.x/kcl_debug.o
  CC [M] /var/lib/dkms/fglrx-updates/8.881/build/2.6.x/kcl_ioctl.o
  CC [M] /var/lib/dkms/fglrx-updates/8.881/build/2.6.x/kcl_io.o
  CC [M] /var/lib/dkms/fglrx-updates/8.881/build/2.6.x/kcl_pci.o
  CC [M] /var/lib/dkms/fglrx-updates/8.881/build/2.6.x/kcl_str.o
  CC [M] /var/lib/dkms/fglrx-updates/8.881/build/2.6.x/kcl_iommu.o
  CC [M] /var/lib/dkms/fglrx-updates/8.881/build/2.6.x/kcl.o
  CC [M] /var/lib/dkms/fglrx-updates/8.881/build/2.6.x/kcl_wait.o
  LD [M] /var/lib/dkms/fglrx-updates/8.881/build/2.6.x/fglrx.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC /var/lib/dkms/fglrx-updates/8.881/build/2.6.x/fglrx.mod.o
  LD [M] /var/lib/dkms/fglrx-updates/8.881/build/2.6.x/fglrx.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.0.0-12-generic'
build succeeded with return value 0
duplication skipped - generator was not called from regular lib tree
done.

How would I specify the post-release fglrx from apt-get install ?
I also have the problem that I can install the older (pre-release I guess) driver, but the post-release fails.

I believe the "post-release" version of fglrx is the package called "fglrx-updates" in Ubuntu 11.10.

In Ubuntu 11.10 presently,
fglrx is version 2:8.881-0ubuntu4
fglrx-updates is version 2:8.881-0ubuntu6

So you're unlikely to see any difference right now. Perhaps later when fglrx-updates gets upgraded to a higher version than fglrx, but it hasn't yet...

[Expired for fglrx-installer (Ubuntu) because there has been no activity for 60 days.]

I'm having same problem in Precise. The log shows the following errors:

2012-06-16 17:38:55,786 ERROR: enabling xorg:fglrx_updates: Unable to install kernel header package linux-headers-
2012-06-16 17:38:56,544 ERROR: Binary package fglrx-updates has no trusted origin, rejecting
2012-06-16 17:38:56,953 WARNING: modinfo for module fglrx_updates failed: ERROR: modinfo: could not find module fglrx_updates
2012-06-16 17:38:56,954 ERROR: XorgDriverHandler.enable(): package or module not installed, aborting

This looks like the same bug as #873058, which is marked against fglrx (not fglrx-installer).