Further research and Ive come up with this ( and im way out my depth
here !!!)

$ sudo modinfo -F vermagic -k 2.6.24-16-386 fglrx 
2.6.24-16-386 mod_unload 486 
$ sudo modinfo -F vermagic -k 2.6.24-17-386 fglrx 
2.6.24-16-386 mod_unload 486 
$ sudo modinfo -F vermagic -k 2.6.24-18-386 fglrx 
2.6.24-16-386 mod_unload 486 
$ sudo modinfo -F vermagic -k 2.6.24-19-386 fglrx 

Vermagic isnt changing with each compilation of the module, it seems to
be stuck on -16. The module was initially compiled from the ati package
against a running -16 kernel, then installed against the different
kernel versions  using dkms build and dkms install with the -k parameter
. Is this part of the problem ??

build of module for -19 is ......
sudo dkms build -m fglrx -k 2.6.24-19-386 -v 8.501

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area....
pushd /var/lib/dkms/fglrx/8.501/build; sh make.sh --nohints; popd.....
cleaning build area....

DKMS: build Completed.

$ sudo dkms install -m fglrx -k 2.6.24-19-386 -v 8.501
Running module version sanity check.

fglrx.ko:
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/2.6.24-19-386/updates/dkms/

depmod....

DKMS: install Completed.

-- 
Kernel update 2.6.24-17 gives white screen on log in
https://bugs.launchpad.net/bugs/235262
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to