Updated Athlon kernel and vmware 4.05
I am running SuSE 9.0 Professional. I recently applied the updated Athlon kernel and source via YOU. Currently running 2.4.21-166-athlon. Naturally when I started up vmware it told me to run vmware-config.pl. Previously when I ran vmware-config.pl it would compile new modules, BUT ASK ME IF I WANTED TO OVERWRITE THE EXISTING ONES. Either I was asleep or it overwrote them without asking. In any event, vmmon.o and vmnet.o got overwritten. I SWEAR I HAD BACKUPS, but of course i can't find them. Is there an easy way to get the vmmon.o and vmnet.o modules that came with the default ahtlon kernel of 9.0. Do I ahve to install the default kernel from the DVD/ Is there someone who could simply email me the appropriate modules as an attachment. Any thoughts would be appreciated. Mike -- Michael A. Coan Woodlawn Foundation 524 North Avenue, Suite 203 New Rochelle, NY 10801-3410 tel 914-632-3778 fax 914-632-5502
-----Original Message-----
From: Michael A Coan
I am running SuSE 9.0 Professional. I recently applied the updated Athlon kernel and source via YOU. Currently running 2.4.21-166-athlon.
Naturally when I started up vmware it told me to run vmware-config.pl.
Previously when I ran vmware-config.pl it would compile new modules, BUT ASK ME IF I WANTED TO OVERWRITE THE EXISTING ONES. Either I was asleep or it overwrote them without asking. In any event, vmmon.o and vmnet.o got overwritten. I SWEAR I HAD BACKUPS, but of course i can't find them.
Simply reinstall the current running kernel and you will have the modules back. I have done this a couple of times. I have also found that if you delete the not_configured file in /etc/vmware you may get away without having to run the config program. Ken
Ken,
I am running SuSE 9.0 Professional. I recently applied the updated Athlon kernel and source via YOU. Currently running 2.4.21-166-athlon.
Naturally when I started up vmware it told me to run vmware-config.pl.
Previously when I ran vmware-config.pl it would compile new modules, BUT ASK ME IF I WANTED TO OVERWRITE THE EXISTING ONES. Either I was asleep or it overwrote them without asking. In any event, vmmon.o and vmnet.o got overwritten. I SWEAR I HAD BACKUPS, but of course i can't find them.
Simply reinstall the current running kernel and you will have the modules back. I have done this a couple of times. I have also found that if you delete the not_configured file in /etc/vmware you may get away without having to run the config program.
Thanks for the reply. I have YOU remove the downloaded files after I install updates and patches. I downloaded the file k_athlon_2.4.21-166.i586.rpm and installed it with YAST. Everything went fine, except that /lib/modules/misc/ NO LONGER CONTAINS vmmon.o and vmnet.o This would explain why i was not prompted as to whether I wanted to overwrite the existing vmmon.o or vmnet.o because they didn't exist after the update to 2.4.21-166. Quite likely I have made some other goof. if I read your answer correctly, installing k_athlon_2.4.21-166.i586.rpm should ahve restored vmmon.o and vmnet.o Thanks Mike -- Michael A. Coan Woodlawn Foundation 524 North Avenue, Suite 203 New Rochelle, NY 10801-3410 tel 914-632-3778 fax 914-632-5502
Michael A Coan wrote:
Quite likely I have made some other goof. if I read your answer correctly, installing k_athlon_2.4.21-166.i586.rpm should ahve restored vmmon.o and vmnet.o
Say again why don't you let vmware-config compile new modules?
On Wed, Jan 07, 2004 at 09:18:01AM +0200, Silviu Marin-Caea wrote:
Michael A Coan wrote:
Quite likely I have made some other goof. if I read your answer correctly, installing k_athlon_2.4.21-166.i586.rpm should ahve restored vmmon.o and vmnet.o
Say again why don't you let vmware-config compile new modules?
I am not the original poster but am having the same problem with k_deflt-2.4.21-166 kernel. If I let vmware-config.pl to compile new modules, it overwrites the old ones WITHOUT asking any confirmation. Actually, it leaves a copy of old modules with .old.0 extension. The problem with the modules compiled by vmware-config.pl is that they cause kernel oops when I boot NT in virtual machine. If I try to force modules from -144 kernel into misc directory, vmware startup script just fails. The solution to my problem was to run vmware-config.pl and let it create new vmmon.o and vmnet.o files in /lib/modules/2.4.21-166-default/misc directory. Then I stopped vmware (/etc/init.d/vmware stop) and compiled vm modules from km_vmware-3.1.1-326 package. cd /usr/src/kernel-modules/vmware make -f Makefile.module install Then I made sure new modules were present in /lib/modules/2.4.21-166/default/misc, ran depmod -a and started vmware (/etc/init.d/vmware start) Vmware version I am using is VMwareworkstation 4.0.5 build 6030. No more kernel oops, NT4 boots and runs fine in virtual machine. Regards, -Kastus
On Sunday 11 January 2004 23:51, Kastus wrote: snip
Kastus, Someone mentioned this on the list yesterday: http://kerneltrap.org/node/view/1804 The VMware patch applies to 2.4 and 2.6 kernels. I applies the patch and now VMWare is rock steady. Also the info on how to get your NVidia cards working on 2.6 may also be helpful. David -- David Bottrill Registered Linux user number 330730 www.bottrill.org
participants (5)
-
David Bottrill -
Kastus -
Ken Schneider -
Michael A Coan -
Silviu Marin-Caea