At 12:31 PM 6/14/2001 -0400, Alok K. Dhir wrote:
>Problem is, the patch does not apply clean to the kernel, one of the
>hunks for arch/i386/kernel/entry.S fails. I manually applied using my
>best judgement, and the kernel complied and booted fine. But I got a
>problem when the init script for Win4Lin ran in the boot process -
>something to do with vnet - something to the effect of "found kernel
>BUG" with a stack dump following. Once booted, attempting to start
>win4lin results in an 'vm86 process died'.
i ran into the same thing. apparently between 2.4.5 and 2.4.6, major changes
were made to the kmem_alloc code (constants changed all over the place,
resulting in an assertion failure in slab.c)
>So - any chance of a working 2.4.6-pre3 patch?
>
>Also, I realize this may be an ignorant question - but it deserves
>asking and serious thought by the developers: Is there a critical
>reason why Win4Lin needs to patch the kernel in order to work? If there
>was any way for it to build kernel modules and simply load those w/o
>patching the kernel directly (a la vmware) it would be a pretty
>important change for the better IMHO. It would definitely make it
>possible for a much wider audience to use the product.
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
