AW: FC3 - vmware not working after upgrade to kernel andkernel-devel 2.6.12-1.1372_FC3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi there,


I use vmware since several years with SuSE 7.x - SuSE9, FC3 and FC4 as
host systems.
Most probs occur after kernelupdates. All the probs i have solved with
the "any-any" patch. The actual version 5 of vmware needs the last
any-any patch with the actual kernel too.




Kind regards from germany


Andreas



-----Ursprüngliche Nachricht-----
Von: fedora-list-bounces@xxxxxxxxxx
[mailto:fedora-list-bounces@xxxxxxxxxx] Im Auftrag von Gerald Thompson
Gesendet: Samstag, 16. Juli 2005 09:20
An: For users of Fedora Core releases
Betreff: Re: FC3 - vmware not working after upgrade to kernel
andkernel-devel 2.6.12-1.1372_FC3


On Sat, 2005-16-07 at 05:59 +0300, Vitaliy Ivanov wrote:
> On Saturday 16 July 2005 05:47, Gerald Thompson wrote:
> > Current Problem:
> > - So now my situation is that vmware can build the module
> > - the module appears to install correctly
> > - bridged networking fails to start
> > - when I try to run vmware it says it is not configured correctly 
> > and that I have to run /usr/bin/vmware-config.pl
> > - when I run it again it says the module is fine
> > - when I try to restart the computer it fails to shutdown - it times

> > out and just sits there
> > - I can't see where it is failing because I am not getting to see 
> > the shutdown messages after upgrading the new kernel.
> > - on boot up it continues to say that vmware bridged networking has 
> > failed or that vmware is not configured properly
> > - I decided to try telinit 3 so I could see the shut down messages
> > - the computer seems to be locking up on shutting down system logger
> > - if I uninstall vmware the computer is able to reboot properly.
> >
> > I was wondering if anyone else was having a problem like this, I am 
> > thinking that there may be a corrupted file for the vmware 
> > configuration somewhere on the system.  It may have resulted from my

> > switching back and forth between kernels while I was trying to 
> > determine the issue with kernel-devel
snip
> 
> I had the same issue with FC4. I found the solution on the vmware 
> forum: 
>
http://www.vmware.com/community/thread.jspa?forumID=19&threadID=15583&me
ssageID=166268#166268
> So I installed vmware-any-any-update and it solved the issue.
> But it's FC4....
> 
> Best regards.
> 

Thanks Vitaliy;

That has definitely solved the problem with vmware.  I did several tests
with rebooting and no errors or lockups now either.  It was probably
locking up trying to shutdown the bridged network.

Thanks very much for the suggestion, although the page you gave actually
says to go to this page:

https://www.vmware.com/community/thread.jspa?threadID=18088&tstart=0

Sincerely,
-- 
Gerald Thompson
geraldlt@xxxxxxxxx
http://www.gltechsolutions.com

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list



[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux