On Fri, 2004-01-30 at 04:56, David Bottrill wrote:
kbonasia@mclink.net said:
yes, download vmware and next as root start the vmware-config.pl,
say "no"
when it ask if you desire to "update" the vmnet modules (first install the right kernel patch for vmware, from Yast...), then, login as user and write vmware &... then ... insert the right serial code (trial or buy...) and go!
This does not work is you have an Athlon Kernel that you have updated online using YAST. If you are running the 2.4.21-199 kernel this does not work as SuSE have not provided VMWare drivers with this kernel and if you allow vmware to compile it's own kernel modules they will fail. The any-any-update is the best way to get VMWare running.
Using the k_deflt kernel for intel I have been able to use the modules from the 121 kernel with the 166 kernel. Install the 121 kernel copy the modules from /lib/modules/2.4.21-121-default/misc/ to someplace safe install the newer kernel copy the modules back to /lib/modules/2.4.21-121-default/misc/ run depmod -a run vmware-config.pl -but- do not over right the modules. If the config program does overwrite the modules run /etc/init.d/vmware stop, copy the modules again and then /etc/init.d/vmware start. run vmware I have done this successfully on three different boxes without problem. I have also found that after the initial configuration of vmware if you have a problem and it wants to force you to run the configuration program look in /etc/vmware for a file called not-installed and delete it. You should be able to start the vmware processes after that. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)