Bugzilla – Bug 66
No network interface found
Last modified: 2008-01-22 19:47:55 UTC
You need to log in before you can comment on or make changes to this bug.
Vmware 6. Project Indiana Developer Preview networking doesn't work. I think the network adapter is not found. Details: I disabled NWAM per the project page instructions[1], and no network interface is found in the network GUI. This is unusual because SXCE has always found a network interface automatically when installed with vmware. I've also used NWAM phase 0 successfully on SXCE with this vmware configuration. [1] http://opensolaris.org/os/project/nwam/phase0/nwamd_1m/
It seems it might be caused by the fact that by default network adapters are handled by "pcn" driver. This one is not being delivered with Indiana preview, since it is not redistributable. Following workarounds exists in order to solve the problem: [1] Install Solaris VMware Tools After tools are installed, vmxnet driver is attached to the network adapter. [2] Choose explicitly e1000g driver in VMware configuration file Add following option into *.vmx configuration file ethernet0.virtualDev = "e1000" Verify that following option is also present: ethernet0.present = "TRUE" If it is not, configure your adapter correctly in VMware. I have verified that e1000g0 then shows up in network GUI after nwam is disabled.
After install solaris vmware tools and reboot the vmware system, you may run into another issue: you'll get a crazy keyboard, the whole key map is wrong. If you encountered this case(like I did), just remove /etc/X11/xorg.conf and reboot the system, everything will be fine. BTW, be patient to remove that file, you have to type letter one by one on your mad keyboard, ;-)
(In reply to comment #2) > After install solaris vmware tools and reboot the vmware system, you may run > into another issue: you'll get a crazy keyboard, the whole key map is wrong. If > you encountered this case(like I did), just remove /etc/X11/xorg.conf and > reboot the system, everything will be fine. > > BTW, be patient to remove that file, you have to type letter one by one on your > mad keyboard, ;-) Could you elaborate on how you did this with a keyboard that's not functioning? Did you spend hours guessing at letters? I'm having this problem and I'm utterly stumpted at a way around it. If I can't get my keyboard to work, I can't do anything to xorg.conf
(In reply to comment #3) > (In reply to comment #2) > > After install solaris vmware tools and reboot the vmware system, you may run > > into another issue: you'll get a crazy keyboard, the whole key map is wrong. If > > you encountered this case(like I did), just remove /etc/X11/xorg.conf and > > reboot the system, everything will be fine. > > > > BTW, be patient to remove that file, you have to type letter one by one on your > > mad keyboard, ;-) > > Could you elaborate on how you did this with a keyboard that's not functioning? > Did you spend hours guessing at letters? > > I'm having this problem and I'm utterly stumpted at a way around it. If I can't > get my keyboard to work, I can't do anything to xorg.conf I have to open a terminal and try to press all of the keys, not too hard, you'll find the rule. On my side, 1) numeral key is ok as normal 2) the first and the second row of alphabetical key is shifted one bit to the right. That is, if you want to get "you", you should press "upi". And press "fhk", you'll get "dgj". 3) the third row of alphabetical key is shifted two bits to the right. That means press "b", you'll get c. 4) press "\" to get "enter" 5) press "tab" to get "backspace" 6) "F3" is "space" if I recall correctly 7) ...(sorry for the short memory, but it ought to be enough) Good luck, ;-)
I'd like to close this bug out although I could be persuaded to change it to an RFE for a redistributable pcn(7D) driver. Thoughts from the submitter?
(In reply to comment #5) > I'd like to close this bug out although I could be persuaded to change it to an > RFE for a redistributable pcn(7D) driver. Thoughts from the submitter? I can't speak to the merit of requesting an open pcn driver, largely because I don't know what it is or who it effects. :o) I can say that as long as the e1000 emulation and driver works, that will be enough for Vmware users, even if it takes a little vmx config editing to get it going at the start. Just plop that in an installation FAQ. I expect that the e1000 emulation in Vmware is newer than the default "pcn" one, so if I am correct, the e1000 will probably be the default in new vms at some point anyway. YOU HAVE THE HELM, MISTER COMAY!
Given there's a perfectly valid workaround for VMware users, I'm closing this out.