On Sun, 16 Mar 2003 21:46:50 +0000 richard terry <[EMAIL PROTECTED]> wrote:
> I'm booted up into kde, via the gentoo kernel, and I'm doing all this
> stuff in a terminal within kde. [ I had previously compiled a win4lin
> kernel from the sources and that boots up ok (minus a couple of things
> like ide-scsi support), but dies when it can't load the NVdriver.]
>
> So I'm now correctly linked from win4lin sources > /usr/src/linux: ie:
>
> lrwxr-xr-x 1 root root 33 Mar 16 21:33 linux ->
> /usr/src/linux-2.4.20-win4lin-r1/
>
Looks fine.
>
> So are you saying that I have to go right through the kernel compile
> thing again for win4lin ( ie run menuconfig, save this, then do the
> dep, make clean, maek bzImage, make modules, modules-install etc),
> before typing:
>
Yep. Like somebody said, just doing 'make menuconfig' and then
'make dep' should do it.
> emerge nvidia-kernel?.
>
Right.
>
> If so, that could be the problem as I accidently trashed all my
> sources and had to copy a backup copy I had made prior to trying all
> this. If so, does the kernel have to be called bzImage cause I had
> renamed it to remember it was a win4lin one.
>
No, mine for instance are called 'vmlinuz-<kernel version>'. As long
as your boot loader knows which one to use ...
As for nvidia-kernel ... it really just need the kernel headers from
the source tree, so the name of the kernel image do not matter.
> Does the emerge nvidia-kernel patch the kernel I have compiled
> previously. If so, its obviously going to fail as it now only is on
> /boot.
>
It does not touch the kernel. What it does well do, is install:
/lib/modules/<your kernel version>/video/NVdriver.o
Thus if you compile a new kernel, it will obviously not have that,
and thus the need to remerge nvidia-kernel. Currently there is still
a problem that nvidia-kernel removes its module (the NVdriver.o file)
from the older kernel module dir .. for example:
Say you have linux-2.4.19 with nvidia-kernel installed. Thus you
have:
/lib/modules/2.4.19/video/NVdriver.o
Now you install linux-2.4.20, and remerge nvidia-kernel. Emerge
will now install:
/lib/modules/2.4.20/video/NVdriver.o
and remove:
/lib/modules/2.4.19/video/NVdriver.o
Which will break things if you do boot 2.4.19 again ...
A way to 'fix' this if you take the previous example, is to
just before you remerge nvidia-kernel for the new kernel,
touch the old kernel's NVdriver module like so:
# touch /lib/modules/2.4.19/video/NVdriver.o
and then emerge nvidia-kernel for linux-2.4.20. Because the
old kernel's module's mtime have changed, portage will not
remove it, and allow you to have it installed for both kernels.
But this is beside your problem. From what I have seen from
the post before this one, it still have problems with modversions.h.
Do you actually have this file ? My 2.4.20 kernel does:
nosferatu linux-2.4.20 # ls include/linux/modversions.h
include/linux/modversions.h
nosferatu linux-2.4.20 #
What happens when you do:
# ls /usr/src/linux/include/linux/modversions.h
? If it does not exist, please include the output of 'make dep' as
run in /usr/src/linux (which is a symlink to
/usr/src/linux-2.4.20-win4lin-r1).
Also note that even if you are booted with the gentoo-sources kernel,
the nvidia-kernel ebuild will compile NVdriver for win4lin-sources as
long as /usr/src/linux symlink points to the win4lin-sources directory
...
Regards,
--
Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa
pgp00000.pgp
Description: PGP signature
