When you build your own kernel, then all you have to do (and must do) is
apply the appropriate Win4Lin patch and then enable the Win4Lin feature
in the config.
The Win4Lin replacement kernels are for replacing the "standard"
pre-built kernels that come with the "supported" distributions.
So when you build a kernel yourself, by definition is is not a
distribution's standard kernel, so none of the pre-built win4lin
kernels will match. For people that build their own kernels,
doing the patch on a fairly pure (from Linus) kernel source
is usually the easiest thing to do. The patches get harder
when called upon to patch a certain distribution's source that has
all sorts of other patches and changes already applied for you.
-David
"Mark W. Knecht" wrote:
>
> Question to those that know....
>
> Is it possible to patch a kernel.org 2.2.16 source code tree with
> anything from NeTraverse so that when I build my own kernel I just compile
> in their stuff too? I understand that they aren't going to give me source
> code, but do they have some sort of process for linking in their part of the
> executable?
>
> I've put off this question for a long time, but I'd like to build in 1394
> support (not for using in Windows, but because I have some 1394 peripherals
> I'm using under Linux) and I would really like to get to a single kernel
> that does both.
>
> Still working on everything below....
>
> Thanks,
> Mark
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Larry
> Marshall
> Sent: Saturday, January 20, 2001 6:21 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [Win4Lin-users] Problems getting Win4Lin installed
>
> > 1) I never rebooted. The failure happened immediately after hitting Y on
> the
> > keyboard. I think that the install never happened and it never did
> anything.
>
> Ok...then what's happened (I'm pretty sure), is that script has
> compared /proc/version to its list of possible kernels and come up
> without a match. I suspect the reason for that may be the sub-version
> of 2.2.16 you're running. The script is a bit limited in this
> regard. What I'd try is editing that script so that it does match and
> download the 2.2.16 win4lin kernel and install it for you.
>
> If that doesn't work, you can always go to the site and download it
> yourself. Since you've already dealt with lilo.conf and such you know
> how to set things up.
>
> > 2) The machine is remote on the network with no monitor. I can't choose a
> > specific kernel at boot time, short of editing lilo.conf and rerunning
> lilo
>
> Ok...then you have to set the win4lin kernel as the default. I
> suspect you must have done this with your previous setup and the real
> problem is that you don't have a win4lin kernel. What' hard to follow
> is why you didn't have a real problem with booting if your lilo.conf
> was trying to boot a win4lin kernel that wasn't there.
>
> > 4) /etc/lilo.conf still has a Win4Lin option in it. I suspect that it was
> > not removed by NeTraverse's removal scripts, but I do not know this for
> > sure. Default boot is still 2.2.16 following my kernel build last night.
>
> If that the win4lin option is the default, what kernel is it using if
> the download script failed to download one?
>
> > 5) There's nothing in the /opt directory....
>
> I think that's because the install script says you don't have a
> win4lin kernel.
>
> > 6) There is a file called win4lin in /boot dated Mar. 29, 2000. I suspect
> > that this was from my 2.2.14 installation, but I do not know for sure. I'm
> > not clear whether this is the kernel that used to boot, and wasn't
> removed,
> > or was this some other file.
>
> This would be my guess as well and answers my question above. I
> didn't realize that you hadn't eliminated your old installation before
> proceeding.
>
> > ANY THOUGHTS??????
>
> Hard to know from afar but my guess is that your best bet is to
> download the win4lin kernel and replace the one that's in your /boot
> with it. Then, make sure that lilo.conf defaults to that kernel when
> it boots. My only experience with 'you ain't running a valid kernel'
> msgs have been due to:
>
> 1) didn't have a valid kernel
> 2) didn't boot using the valid kernel
>
> Wish I could provide more help.
>
> Cheers --- Larry
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
