distro: rh9.0 upgraded to kernel 2.4.22 but kept the default kernel 2.4.20-8 (you never know).

I installed wine just fine wine-20030618 built.rpm on RH9.0 with the default kernel 2.4.20-8.

Then, I decided to get the latest kernel 2.4.22. For some reason, wine doesn't see to work like before. I didn't mess with the linux config file. When compiling new kernel I just did 'make oldconfig'.

From 2.4.22 environment:
$wine notepad.exe

wine: Unhandled exception, starting debugger...
Could not start /mnt/floppy (No such file or directory), ignoring drive A:

then the exact same statement repeats for ever. I have to stop it by doing Ctrl+Z.

BUT...when I boot to my old kernel 2.4.20-8, everything is beautiful.

Is there any flags or switches I need to pass along to wine when executing on 2.4.22 environment?

Any other tips?


Thanks.
randomX

did you try re-installing using the new kernel? sometimes things may have to get re-installed after a kernel update....you never know, so give it a try...

yeah, I tried installing wine on the new kernel 2.4.22. From both the latest RPM wine-20030911.rpm and source tarball.

Still no joy.

When you did "make oldconfig" then it wont automatically detect your old settings. It will just used the .config file in the directory. Check to see if there's a config-2.4.20 (or something like that) file in /boot and then use that to "load configuration from file".

Is the new kernel a stock kernel from kernel.org, or one from Redhat?

If it is from kernel.org, then it doesn't have nptl in it, and if I remember right, wine has to have nptl support compiled in to work on an nptl kernel properly and vice/versa.
The redhat 9 kernels from redhat have nptl backported in from 2.5 development.


You might just try compiling wine yourself for the new kernel, rather than using the one from the rpm.

_john_

I actually compiled wine from source after I upgraded to linux 2.4.22.

I got the latest wine 20030911.tgz from winehq and linux 2.4.22 from kernel.org that I compiled myself. Everything else works just fine and better with the new kernel but no joy on the wine thing.

Somebody else told me that I should avoid nptl --contrary to the above suggestion.

He suggested also to configure wine this way:

./configure -C --prefix=/usr/local, and then starting
./tools/wineinstall

NOTE: "make depend && make" crashed on audio.c, though. Only wineinstall made it through.

Now I don't the stupid endless lines "Unhandled exception, starting debugger...". Now it won't even start up.

When I just type wine from console, I get nothing....I see some activity going on in the hard drive BUT...after a few minutes...
I get an error saying "Wine terminated".

contents of /usr/local/lib look ok to me.
total 3328
lrwxrwxrwx 1 root root 17 Sep 19 18:42 libntdll.dll.so -> wine/ntdll.dll.so
lrwxrwxrwx 1 root root 12 Sep 19 18:42 libwine.so -> libwine.so.1
-rwxr-xr-x 1 root root 243234 Sep 19 18:42 libwine.so.1
lrwxrwxrwx 1 root root 20 Sep 19 18:42 libwine_unicode.so -> libwine_unicode.so.1
-rwxr-xr-x 1 root root 1274073 Sep 19 18:42 libwine_unicode.so.1
-rw-r--r-- 1 root root 1863028 Sep 19 18:42 libwine_uuid.a
drwxr-xr-x 2 root root 8192 Sep 19 18:42 wine


So...it looks like I got it going but wine can't get to the libraries or something.
I double checked /etc/ld.so.conf and /usr/local/lib/ line is at the end where is supposed to be.

bottom line: libraries are ok. At least Wine doesn't bitch that it can't find them. The ld.so.conf file looks ok and it's pointing to the right directory holding the libraries.

any ideas?

thanks bro.