On Tue, 2004-12-07 at 17:43 -0500, Matthew Saltzman wrote: > On Tue, 7 Dec 2004, Cyber Source wrote: > > > I have the same relationship problem with haldaemon and vmware, that's > > why I posted originally. I initially thought it was a timing sequence > > thing on boot, it says it is starting haldaemon but when I check after > > it boots up, it's not running. If I restart haldaemon after the pc comes > > up, all is ok to reboot the machine, no hangs. However, I cannot shut > > the pc down, then it hangs. I then noticed that there is no script for > > vmware in rc.0, so I made a link for vmware in rc.0 and it can then shut > > down but then hangs at the end (shuts all down but does not power off). > > This only happens with AMD cpus and can then be corrected with acpi=off > > in the grub line, not needed with Intel cpus, or so I have seen. Bitter > > sweet when the new releases come out, exciting and yet a pain to work > > out the bugs, lol. > > So far, it is working after the following steps: > > (1) Install VMwareWorkstation-4.5.2-8848.i386.rpm. Do *not* install > vmware-any-any-update84. > > (2) Run vmware-config.pl to build modules for the running kernel. Don't forget to "cp -p /dev/vm* /etc/udev/devices" after doing this for the first time. > (3) Run "chkconfig vmware reset" to create the proper symlinks. > > (4) Things appear to work (so far). Note that "service vmware status" > lies about whether vmmon and vmnet modules are insmodded, but > functionality doesn't appear to be affected. > > So the problem appears to have been in both the original RPM (improper > symlinks) and the update84 (something else broken). I'll report back if I > see any more problems, otherwise, I think it's solved. I'll see what > VMware newsgoups have to say about fixing the next update. Paul. -- Paul Howarth <paul@xxxxxxxxxxxx>
