Gfx driver install after dev repo kernel update

[Carbon6]

Was having a few wireless card issues (not coming back up) with the original kernel as i had to run pci=noacpi to boot,
So updated the kernel from the dev repo (2.6.34) and now i don't need to disable pci acpi as the cisco card raises nicely.
So, although i appreciate its not really essential, having the nvidia driver in, it would be a bonus, as the fonts look nasty on the laptop screen without.
Which leads me to..

Unable to get the nvidia 96.43.09 drivers to go in.
linux-source-2.6.34, linux-headers-2.6.34 & nvidia-96.43.09 are all in /usr/src/
But 'dkms build -m nvidia -v 96.43.09' gives me..

Building module:
cleaning build area....
make KERNELRELEASE=2.6.34 module KERNDIR=/lib/modules/2.6.34 IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/2.6.34/build....(bad exit status: 2)

Error! Bad return status for module build on kernel: 2.6.34 (i686)
Consult the make.log in the build directory
/var/lib/dkms/nvidia/96.43.09/build/ for more information.

And the log is...

DKMS make.log for nvidia-96.43.09 for kernel 2.6.34 (i686)
Mon Jun 28 03:09:23 BST 2010
If you are using a Linux 2.4 kernel, please make sure
you either have configured kernel sources matching your
kernel or the correct set of kernel headers installed
on your system.

If you are using a Linux 2.6 kernel, please make sure
you have configured kernel sources matching your kernel
installed on your system. If you specified a separate
output directory using either the "KBUILD_OUTPUT" or
the "O" KBUILD parameter, make sure to specify this
directory with the SYSOUT environment variable or with
the equivalent nvidia-installer command line option.

Depending on where and how the kernel sources (or the
kernel headers) were installed, you may need to specify
their location with the SYSSRC environment variable or
the equivalent nvidia-installer command line option.

*** Unable to determine the target kernel version. ***

make: *** [select_makefile] Error 1

I have updated dkms as after some googlepower, as i read a few bug reports describing a similar issue, but i made no difference.

any ideas? thanks.

[hhmatt]

Was having a few wireless card issues (not coming back up) with the original kernel as i had to run pci=noacpi to boot,
So updated the kernel from the dev repo (2.6.34) and now i don't need to disable pci acpi as the cisco card raises nicely.
So, although i appreciate its not really essential, having the nvidia driver in, it would be a bonus, as the fonts look nasty on the laptop screen without.
Which leads me to..

Unable to get the nvidia 96.43.09 drivers to go in.
linux-source-2.6.34, linux-headers-2.6.34 & nvidia-96.43.09 are all in /usr/src/
But 'dkms build -m nvidia -v 96.43.09' gives me..

Building module:
cleaning build area....
make KERNELRELEASE=2.6.34 module KERNDIR=/lib/modules/2.6.34 IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/2.6.34/build....(bad exit status: 2)

Error! Bad return status for module build on kernel: 2.6.34 (i686)
Consult the make.log in the build directory
/var/lib/dkms/nvidia/96.43.09/build/ for more information.

And the log is...

DKMS make.log for nvidia-96.43.09 for kernel 2.6.34 (i686)
Mon Jun 28 03:09:23 BST 2010
If you are using a Linux 2.4 kernel, please make sure
you either have configured kernel sources matching your
kernel or the correct set of kernel headers installed
on your system.

If you are using a Linux 2.6 kernel, please make sure
you have configured kernel sources matching your kernel
installed on your system. If you specified a separate
output directory using either the "KBUILD_OUTPUT" or
the "O" KBUILD parameter, make sure to specify this
directory with the SYSOUT environment variable or with
the equivalent nvidia-installer command line option.

Depending on where and how the kernel sources (or the
kernel headers) were installed, you may need to specify
their location with the SYSSRC environment variable or
the equivalent nvidia-installer command line option.

*** Unable to determine the target kernel version. ***

make: *** [select_makefile] Error 1

I have updated dkms as after some googlepower, as i read a few bug reports describing a similar issue, but i made no difference.

any ideas? thanks.

It's probably that your SYSSRC is pointing to the wrong location. Verify that /lib/modules/2.6.34 is infact the proper path to the system source files.

Depending on where and how the kernel sources (or the
kernel headers) were installed, you may need to specify
their location with the SYSSRC environment variable or
the equivalent nvidia-installer command line option.

[Carbon6]

/lib/modules/2.6.34 is present.
Is the folder expected to contain a replica of /usr/src/linux-kernel-2.3.64 or just the build files?
as it only contain about 1500 files compared to 33,00 ish of /usr/src/linux-kernel-2.6.34

Although that's a bit of a rhetorical question, as a symb link would be in place i guess...

Anything else i may have overlooked? thanks.

[hhmatt]

The logfile seems to be complaining of either the output file location or the input folder location. Although this maybe just a side effect of another issue. Since BT is using a custom built kernel you may have to wait until a developer can give you a better idea of what you need to do. I in the meantime would restart after reading as much as I could on the dkms build process. It's probably an error in your configuration file though.

The location /lib/modules/2.6.34 should be where the kernel build and source files are.

Good Luck.

[joker5bb]

/lib/modules/2.6.34 should have a symlink to the source

[Carbon6]

Well, after more head-scratching & a crash course in dkms followed by more hardcore google-fu,
it turns out its a issue after kernel 2.6.33, as a selection of headers were moved from linux-headers-2.6.xx/include/linux to include/generated.
Also, it seems there is a patch that needs applying for some changed ACPI functions, some of the patches have been posted for the more newer chipsets, but not for mine that i can find.

As this is slipping out of my realms of wisdom, it looks like i'm going to have to live with unreadable fonts if i want a pcmcia card i can wake up

Maybe the dev team can up a interim kernel (pre 2.3.33) or better still work the magic with the drivers?
Just a thought!

[Archangel-Amael]

A few options come to mind. From best to worst recommended.
1. Try the r1 development release.
2. File a bug with upstream.
3. Upgrade and or recompile your kernel.
Unless you are sure with what you are doing I recommend not messing with number 3. Not to mention you may unintentionally break other packages, cause more headaches.