The Win4Lin ebuild seems to be broken on 2.6.1 kernels. Notably, one of the scripts relies on /dev/ksyms (which I believe was removed from the kernel during the 2.5 phase, correct me if I'm wrong), and also expects /sbin/insmod_ver to be installed - but it isn't. The script seems to indicate that insmod by itself may be sufficient to load the modules, but linking /sbin/insmod_ver to /sbin/insmod results in an unrecognized module format error. Possibly built for 2.4? Very detailed information about my testing process can be found in the URL submitted with this bug report. Reproducible: Always Steps to Reproduce: 1. emerge win4lin 2. Start /etc/init.d/Win4Lin just to be safe 3. ebuild /var/db/pkg/app-emulation/win4lin-5.0.4/win4lin-5.0.4.ebuild config 4. Provide needed Windows boot floppy and Windows CD Actual Results: After copying the files in step 4, the setup will fail because the necessary drivers are not loaded and exit. Expected Results: No error I'll go ahead and admit the following discrediting criteria for the bug: since Netraverse has a patch for the the 2.6.1 kernel already but the most recent netraverse-sources is 2.6.0, I emerged development sources, did an emerge inject of win4lin-sources-2.6.0-r1, applied the two netraverse patches manually and build the kernel. I used the correct patches, including the specific mki patch for the 2.6 kernel. This should not effect the broken script's operation unless the Gentoo patches add /proc/ksyms back to the kernel, but there are other problems as well.
From Netraverse's website: If you are planning to use a 2.6 kernel, you must be running Win4Lin 5.1.10/WTS 2.5.10 or higher. Win4Lin 3.0, 4.0, and NSSE 1.1/WTS 2.0 are NOT compatible with Linux 2.6. If you have Win4Lin 5.0 or WTS 2.5, make sure you update to the latest version, using the graphical installer. The Win4Lin 5.0 version from the boxed CDROM will not work with kernel 2.6 - be sure to update to the latest using the graphical installer. Also, you must apply the mki-adapter26*.patch file. For 2.4 kernels, continue using mki-adapter.patch. The latest ebuild is version 5.0.8. Consequently this is not a real bug.
