Win4Lin 5.1.11 (Manual Install) & 2.6.0 Stable Kernel

BliZZZard

Just a note to people who may be attempting to install the Win4Lin version that "supports" the 2.6.0 test11 kernel.... there are a few things you should note as a bug that I become aware of:

Both the mki-adapter26.*patch and the Kernel*2.6.0-test11*patch work on the stable kernel EXCEPT you MUST make sure that you remove SMP from the kernel OR state within the configuration manually that Win4Lin only see's one processor... Otherwise the Win4Lin init script will fail in load all of the merge drivers properly and you will get an error about Win4Lin not being installed properly...

Hope this helps anyone who tries Win4Lin on the new kernel..

Oh... an another note VMWare in ~x86 works fine for me other than a pop up saying that it doesn't formally support 2.6.0 stable yet... (I think it's build 6030)

derk · Posted: Sat Dec 20, 2003 10:32 am Post subject:

i've kludged up some ebuilds for those interested.
available under Bug 32952 in bugzilla

Derk

derk · Posted: Mon Dec 22, 2003 6:04 pm Post subject:

addendeum for the noob's: to use the ebuilds you need to do download the required file from www.netraverse.com manually at the moment. I.e. register etc. this is not a beta build at all really but very early alpha. (when you register do the win4lin scripted install to download the required files) also use the gentoo user registration point

you also need to creat the digests once the required files are downloaded.
command of the form below in the proper /usr/local/portage/... etc directory tree that you have created.

as root# ebuild build-name.ebuild digest

see the gentoo docs on personal or modified ebuilds for more details

you mileage may vary as i've just upgraded over top of my existing install (fourth time once from standard win4lin install to gentoo version then from version 4 to 5 and now from version 5 to 5.1 and kernel-2.6 to boot first did the convert from 5.04 to 5.1 then from 2.4 kernel to 2.6 kernel. Regular win4lin below 5.1 will not run on 2.6 kernel.

note: the information in the bug above on the registration key problem .. the key filename exists in the ebuild .. if you run the build without saving your registration key it clobbers it with a temporary 15 day key .. be sure you read the ebuild and back-up that file somewhere else if you are a registered user. once the ebuild has completed just write your saved key file (with the correct name) over top of the temporary one.

derk

ps it also works with udev on a linux-2.6.0-test11 level kernel for the really adventurous...

derk · Posted: Mon Dec 29, 2003 9:00 pm Post subject:

FYI: new win4lin ebuild for 2.6.0 kernel available in bugzilla #36747

airspirit · n00b Joined: 02 Sep 2003 Posts: 41 Location: Moscow, ID

https://www.netraverse.com/member/downloads/miscfiles/Win4Lin-5.5.12h-d.i386.rpm

this is where I got my version of Win4Lin 5.1+. I edited the ebuild to account for the higher filename (5.5.12h-d) and then ran it. Upon booting into 2.6 (which I manually patched) I get the "drivers not loaded/not installed properly/you suck" message and Win4Lin refuses to start. Is there anything I'm missing? As far as the kernel config I've removed SMP support, and the Win4Lin support IS compiled in. This is quite annoying, and the only reason I'm still running 2.4.23 ....

Notes: under lsmod the mki-adapter modules IS listed. It is also listed under kallsyms ....

derk · Posted: Tue Dec 30, 2003 12:58 am Post subject:

If the drivers are not loaded -- then something possibly went awry in your patching .. I know the ebuild I submitted for the vanilla kernel patch works ..
as I've just run it. I'm currently using the 5.5.11 win4lin install version.

I've never run across the kallsyms problem. I'm running the latest gcc/glibc/2.6.0 linux headers etc. you might want to check your kernel memory settings .. If I remember correctly win4lin does not work if greater than 3Gb memory is flagged.. YMMV

have you added win4lin to default run level using rc-update?

airspirit · n00b Joined: 02 Sep 2003 Posts: 41 Location: Moscow, ID

Win4Lin is in default ... no problems there. Win4Lin 5.5.4 runs well under 2.4.23 as well as 5.5.12 (though there is a weird bug upon loading that takes resizing of the Windows window to get it to draw the full desktop). I'm going to try your win4lin-sources ebuild and see what happens there.

As for the version, I'm wondering if 5.5.12 isn't compatible ... unfortunately, when I do the update it updates me to the latest version of Win4Lin 4.0 for some stupid reason (and now it won't update at all!) ... I have a 5.0 key but it won't update to the latest 5.0 so I'm assuming that 5.5.12 is the latest and greatest. I'll let you know what happens after I use your ebuild ... be back later.

(oh, and I've done a full emerge -u world already to get my background stuff up to date and running KDE3.2beta2 if that matters ... I have noticed that win4lin draws much faster under it if anyone is interested).

airspirit · n00b Joined: 02 Sep 2003 Posts: 41 Location: Moscow, ID

No dice. Nothing. Nada. Still says the drivers can not be found. I'm going to try to find a way to get a hold of the exact win4lin package you're using and give that a whirl ... god knows I haven't had any luck so far ....

EDIT: they don't have the 5.5.1a-d package on their server for download anymore. I think I'm screwed.

derk · Posted: Tue Dec 30, 2003 9:01 pm Post subject:

have you checked to make sure your registration key did not get clobbered?

derk · Posted: Tue Dec 30, 2003 9:46 pm Post subject:

ok I've played arround with the 5.5.12 version now .. I blanked out the key file echo line in a modified build and then installed after using the manual installer script to pull in the file .. if you blank out the echo that installs the key file. the install seems not to complete properly .. lost the menus etc. /bin/win did not exist .. uncommented the echo line, saved a copy of my registered key file somewhere else, reran the build, reinstalled my key file, touched the keyfile to update the time stamp and all works again .. I did restart /etc/init.d/Win4Lin prior to rerunning the ebuild/emerge.

so I suspect either a 2.6 kernel config issue or your keyfile being clobbered ..

hope this helps else post a more complete description of your error messages.

derk

PS there is now a win4lin 2.6.0 kernel ebuild in portage

make sure that the netraverse modules are selected in your make config

airspirit · n00b Joined: 02 Sep 2003 Posts: 41 Location: Moscow, ID

Okay, as I said earlier, I have the netraverse module selected in the kernel. That isn't the issue. Similarly, I always backup and replace my key file after an emerge, so that isn't the problem.

I don't know what you mean by /bin/win ... my /win directory is in my /home directory ... is this a problem?

I'm tempted to remove win4lin from my system altogether and start from scratch ... do you know if this would bork my current windows install (assuming I backup the /home/user/win dir)? Also, could that be the issue: that I'm using a windows install from a previous win4lin version (5.5.4)?

derk · Posted: Wed Dec 31, 2003 9:25 pm Post subject:

at this point more info is required.

Can you include all the error messages or approximations of them?
perhaps running /etc/init.d/Win4Lin stop then w/ start or just using restart
and direct the output to a file

/etc/init.d/Win4Lin start > file.txt

if it runs with a 2.4 kernel the win4lin install itself is fine don't bother with removing and reinstalling. I've installed once and updated at least 5 times now with no ill effects.

your problem appears to be kernel related so .. have you used the new ebuild to make your kernel? (are you using the linux-headers-2.6.0 ? I know I am I don't think this should be the problem, but you should at least be at the most up to date 2.4.20 or 2.4.21-r1 headers)

are you letting the make routine install the kernel?
Here's how I built mine.

make sure you mount /boot prior to building any 2.6 kernel, can be after
make menuconfig or make config (your preference I prefer the first one)

I use the following line typically once I've configured as desired:

make ; make modules ; make modules_install; make install ; emerge nvidia-kernel

then I'll edit grub.conf if needed .. typically the make installer places a
vmlinuz-2.6.0-win4lin kernel copy in boot and adds a link to vmlinuz
it also automaticaly renames your old vmlinuz-2.6.0-win4lin to vmlinuz-2.6.0-win4lin.old and creates a link to it as vmlinuz.old

it also creates system.map and config files for each kernel it installs.

so you can use the short name in your grub conf or lilo conf and not have to edit it after every upgrade/ recompile .. making sure you also have an entry for vmlinuz.old or another kernel you know works.

after you have adjusted your grub or lilo configs (rerunning lilo) accordingly and rebooted etc.

( of course making sure /etc/init.d/win4lin has been added to the default run level or is run on demand prior to starting the executable) (i know you've done this, this is an aside for others )

by the way: /bin/win is where the executable is that is called by the menu selection/icon etc. to start win4lin (actually it's a link to the executable in /opt/win4lin/publicbin/win)

airspirit · n00b Joined: 02 Sep 2003 Posts: 41 Location: Moscow, ID

Okay, this is what I get as an error:

MERGE_NL: win: ERROR: Win4Lin drivers are not loaded or not available for use. Cannot run DOW or Windows. Either Win4Lin is not fully installed on your system, or the drivers cannot load, or too many simultaneous users.

When I emerge your ebuild (I have done both, and the win4lin ebuild was done inside of a freshly booted linux-2.6.0-win4lin environment as per your instructions) I get the following errors:

airspirit · n00b Joined: 02 Sep 2003 Posts: 41 Location: Moscow, ID

I manually made the symlinks and directories and it still doesn't work ... I don't get it at all. Frustrated, I am. lsmod out:

derk · Posted: Wed Dec 31, 2003 11:49 pm Post subject:

okay from your config and description the problem is not the kernel ..

somewhere you are running into a problem with the non-kernel portion of the install

the fact that your get all these linking problems says that you have an incomplete install .. have you tried doing the manual install using the netraverse installer as the root user?

also check for things like enough disk free space in /var and /opt and /var/tmp.

win4lin stores files in /var/win4lin as well as /opt/win4lin
portage uses /var/tmp so if all these are on your root partition and it's getting full your can have odd problems like this happening

do a little house cleaning if needed in /var/tmp .. i.e. empty it out completely

the command

df

will give you the diskfree info.. if you have lots of space .. then maybe a complete uninstall of win4lin is necessary .. but I suspect you can leave your /home/username/win directories as is just check to see where any links are pointing before ..

does it still work with the 2.4 kernel at the moment? if so and you are a registered user .. try asking netraverse what the problem might be .. but only after using a manual install first as they probably will not support the gentoo ebuild style install.

airspirit · n00b Joined: 02 Sep 2003 Posts: 41 Location: Moscow, ID

It still works under 2.4.23 and 2.4.22. I'm going to try the whiz-bang unemerge then emerge method and see if that helps. If not, then I may be screwed. Please check your /usr/portage/home/win4lin/files dir and see if the files it couldn't copy above are there. If they are, that may explain part of my problem.

LATER:

I couldn't unmerge your win4lin ebuild (wasn't listed or some such nonsense) but I could unmerge the old 5.0.4 ebuild it was built upon. Once that was done, I killed every vestige of win4lin from my system. Everything got wiped, though I backed up my windows directory. Once done, I reinstalled via your ebuild I modified to use 5.5.12 and it did NOT do a full install. I discovered that many critical parts of the program are NOT included in that package, such as the infamous win4lin.initd.new, it does NOT install anything into rc.d or init.d, and in the end I had only half an installation. I think that is the reason: without the FULL package (which they don't list for download anymore) for 5.1.11+ I can't do anything. I tried using their updater, and after pounding on it a while it finally downloaded an upgrade package for v4 ... not v5. I'm tired of trying: I don't have the right files and can't get them, so I'm back to trying to make it work in 2.4.23 now (since the unmerge killed my WinME install).

derk · Posted: Thu Jan 01, 2004 1:18 am Post subject:

mmm ... to unmerge the ebuild you had to be in the directory it resides in.
It's a quirk of using PORTDIR_OVERLAY=/usr/local/portage in your /etc/make.conf files any placed there sometimes seems to be auto-masked unless it is installed. you may have left-over cruft in your /var/dp/pkg directories related to win4lin

I don't understand why netraverse would release an incomplete rpm I've still got 5.5.4d-d, 5.5.11a-d, 5.5.12h-d and each successive one is bigger than the previous version. But then they may be upgrade versions only so that means installing a win4lin version 4 version first then installing the version 5 upgrades.

If you have a version 5 win4lin registration code then you should be able to download a complete version and install it without the ebuild directly from the netraverse installer run as root .. If that does not work take it up with netraverse as you are a registered user .. if you create an /etc/rc.d/init.d directory prior to your install the win4lin start-up script will install there then you can symlink to it from /etc/init.d or add a reference to it in /etc/conf.d/local.start , I 've used both approaches in the time before ebuilds for win4lin even existed in portage. You should be able to install amd get this working without the ebuild .. the ebuild is just a help-ful way to manage the install process ..

by the way the netraverse_installer will also let you know if your kernel is done properly .. it'll want to down load a kernel package as well or some such alternative.

derk · Posted: Thu Jan 01, 2004 5:59 am Post subject:

okay in retrospect and further reflection the following may have been the problem: in /var/win4lin/drivers there is the kernel module built by the win4lin-XXX.ebuild "Win4Lin.ko" in the case of a 2.6.0 kernel this is loaded by
/etc/init.d/Win4Lin start
There is a log file mentioned in this script /tmp/win4lin_init.log you might want to see if it still exists and examine it's contents it may offer a few clues. (which unfortunately for you I just noticed)

I suspect that the 2.4.0 kernel built module Win4Lin.o existed but not a 2.6.0 kernel version.

I think the two are not compatible but as I've already ditched my 2.4.xx kernels I am unable to verify this.

I speculate that the script may load the 2.4.0 module into a 2.6.0 kernel properly with out error flags but it may be unable to function correctly due to kernel differences thus it does not work. building win4lin in a 2.6.0 environment without reloading the win4lin module results in failure to function. An /etc/init.d/Win4Lin restart after the build may have solved the mystery..but maybe you did this.. then I do not have an answer for you.
On the other hand examining the /etc/rc.d/init.d/Win4Lin script shows that it does not unload any modules on being stopped so either a reboot will load the new correct module for a 2.6.0 kernel or you have to do an explicit modprobe -r Win4Lin and then reload the correct one with modprobe /var/Win4Lin/drivers/Win4Lin .. not tested by the way

Try a complete rebuild of your win4lin in the 2.6.0-win4lin kernel enviroment using the netraverse_installer grabbing all the updates etc.
also read their help files they may also offer a clue as to what was going on.

I know mine just works .. although at the start I had to fight with it a bit .. as noted above and in another thread on this topic. Maybe mine works now because I rebooted for some other reason before checking for function.

I hope this discussion helps someone else avoid your misery. I hope you have a better new year. Let us know if you succeed. I suspect your saved
files are still okay and once untarred will function fine. I think I did strip the install completely once in the distant past as well. I lost my root partition and had to rebuild it I left my home partition alone and rebuilt my whole install from ground zero. once win4lin was installed with the root install and set-up completed again. everything previously installed as a user just worked once any drive reference changes had been made. So you have not lost everything just the core.

derk

derk · Posted: Thu Jan 01, 2004 3:10 pm Post subject:

as you have discovered the following is very true ..

An expert is a person who has made all the mistakes that can be made in a very narrow field. Niels Bohr (1885 - 1962)

so if you get win4lin working again after all this .. you may be able to call yourself an expert ...
:wink:

Have a happy new year.

airspirit · n00b Joined: 02 Sep 2003 Posts: 41 Location: Moscow, ID

Do you know where I can download the version of the RPM you have? I've contacted Netraverse and they say "use the updater" which allows you to use the .12 version I have to update ... unfortunately it only downloads the 4.0 version update for me! Help!

derk · Posted: Tue Jan 06, 2004 6:57 pm Post subject:

as stated above you may have to do this in two parts first install the 4.0 version then the 5.1.12 version .. check to make sure you have the most recent netraverse_installer it is version 5.1.2.

derk

airspirit · n00b Joined: 02 Sep 2003 Posts: 41 Location: Moscow, ID

I have done that. Trust me. Multiple times. It just doesn't want to upgrade.

What I have done is both a 4.0 and 5.0 install to start with. I have also tried starting with 5.0.4 to start. Then I try to upgrade to 5.1.12 and it barfs. There are files that have to be missing that are in the 11 package and are not in the 12 package.

derk · Posted: Tue Jan 06, 2004 9:14 pm Post subject:

okay I still have the 5.5.11 rpm file how do you propose I get it to you ? I'll need to upload it somewhere for you to obtain it. Can you handle a 5 MB file in your mail box?

derk · Posted: Tue Jan 06, 2004 9:21 pm Post subject:

when you mean it barfs does it not run under a 2.4 kernel?! or is it only with a 2.6 kernel?

derk

airspirit · n00b Joined: 02 Sep 2003 Posts: 41 Location: Moscow, ID

It runs under 2.4, but the files that let it run under 2.6 are NOT in the .12 package.