Legatus wrote:
On 12/22/06, rbw <[EMAIL PROTECTED]> wrote:
>
>
> Next it is time to get VMWare back up and running...
> I wonder if VMWare guests and hosts can do SMB/NMB/CIFS through the
> wireless connection...
>
> I'll post what happens next...
>
You will have to use NAT, not bridged networking in VMWare. The WiFi
card/driver won't let you bridge across it. It will work though, I
have done
it quite a bit.
--
JD Runyan
Ah ha...
I will look at that NAT choice again...
The big deal I had for getting VMWare up and running again besides
reinstalling this:
VMware-server-1.0.1-29996.i386.rpm
was a discussion/foobar/confusion about this error message that I also got:
"/usr/lib/vmware/bin/vmware:
/usr/lib/vmware/lib/libpng12.so.0/libpng12.so.0: no version information
available (required by /usr/lib/libcairo.so.2)"
After reading what everyone said and suggested I backed up
"/usr/lib/vmware/lib/libpng12.so.0/libpng12.so.0" which is the culprit
and recreated it as a symlink to the same lib file that the system has
and which is the good file, like so:
$ pwd
/usr/lib/vmware/lib/libpng12.so.0
[ libpng12.so.0]$ ls -al
total 212
drwxr-xr-x 2 root root 4096 Dec 22 12:05 .
drwxr-xr-x 41 root root 4096 Dec 22 09:14 ..
lrwxrwxrwx 1 root root 22 Dec 22 12:05 libpng12.so.0 ->
/usr/lib/libpng12.so.0
-r--r--r-- 1 root root 186048 Dec 22 12:01 libpng12.so.0.orig
[ libpng12.so.0]$
Everything came back to life after that... connect to local server
vmware instance... reopen and launch guests...
maybe these steps will help someone when they need a tip later...
I know they will probably come in handy for me at some point ;^)
Post FC6 weirdness:
1.) I have had a runaway repeating character in my console sessions a
couple times. That means I get a repeating character that will not stop.
I always have multiple sessions open so I can close the session that has
gone south...
2.) In the course of "hotplugging" the wpc55ag card and rerunning the
little script of commands to reinitialize that wifi card I have had a
couple HARD system lockups.
The first one is annoying but I use Linux in part so I don't have to be
familiar with things like the second item above and the hard lockups and
other typical nastiness found in that majority OS. The problem in both
the cases above seems to be the hardware and driver actions in the
wireless subsystem. I'm going to look into how the -Dwext vs the
-Dmadwifi methods differ and if one makes more sense for ath0 than the
other.
rbw
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
