unit3 wrote:
> It's good to know the older kernel will work for backwards compatibility
> reasons. I'm still surprisedd at all the problems you've been having
> though, as I have a few machines running Feisty stably with the latest
> amd64 genreic kernel, and it has in fact fixed some sleep-related
> crashes on my notoriously buggy laptop.
The only major caveat is that I have the old 2.6.17 installed with the
old restricted modules. I figured I could simply compile + use the
provided nVidia kernel shim module. The trouble is that this module is
installed to
/lib/modules/2.6.17-11-generic/kernel/drivers/video/nvidia.ko
While another module (which is either 76xx or 81xx, depending on the
boot) shows up in
/lib/modules/2.6.17-11-generic/volatile/nvidia.ko
I can delete it all I want; it'll just come back like a dirty habit.
Even if I replace it with the newer module, it's replaced. Not very
friendly! I've taken a look at the initrd, and it's no inside there.
So I don't know where/why/how Ubuntu is destroying a legit module and
putting an older one in (which then won't load X, so each boot requires
I rmmod, delete, insmod, startx).
Anyone familiar with this behaviour quirk of Ubuntu?
Received on Sun Apr 29 23:02:56 2007
This archive was generated by hypermail 2.1.8 : Sun Apr 29 2007 - 23:03:05 CST