If you are not using vmware anywhere else, i'd give VirtualBox a shot - it's free and probably a bit snappier than vmware.
On Tue, Feb 24, 2009 at 2:52 AM, Brendon Costa <brendon.j.costa at gmail.com> wrote: > Hi all, > > I just installed OpenSolaris 2008.11 in vmware on my Linux box as I want to > try compiling some code with opensolaris. > > Now when I boot the installed image i have problems. After booting into text > mode, i am initially presented with the console login prompt, then the boot > sequence seems to try and start the X server. After the boot has tried (and > failed) to start the X server, if i then try to type anything at the command > prompt (to login) it seems to generate a lot of control characters. For > example attempting to login as root, i.e. typing the word "root" produces > lines like: > > ^...@^@^...@^@^A^(^...@mr ............ > > A few other bits of background information that may help with this problem: > > Upon booting i get the following warnings: > > WARNING: Time-of-day chip unresponsive; dead batteries? > WARNING: /pci at 0,0/pci15ad,1976 at 7,2 (uhci): No SOF interrupts have been > recieved, this USB UHCI host controller is unusable (This one i only get > sometimes) > > NOTICE: MPO is disab;led because memory is interleaved > > WARNING: BIOS microcode patch for AMD Athlon(tm) 64/Opteron(tm) processor > erratum 131 was not detected; updating your systems BIOS to a version > containing this microcode patch is HIGHLY recommended or erroneous system > operation may occur. > > Also I noticed that after trying to enter a few things on the command > prompt, i got a warning: > ttymon: Warning -- speed of (console) may not be supported by the system > > I am not sure if this is the cause of the problem or a symptom of it > > Now, the system works fine when I boot from the live cd. > > Now if during the boot i attempt to login as soon as possible, it logs in > fine (key mapping seem to be working fine until X is attempted to be > started). Note after a small time, the boot procedure attempts to start X > which fails. After failing to start X is when the keyboard stops working. > > Now if i login quickly and run startx before the boot process attempts to > start X, then i get the following errors: > > (EE) Unable to locate/open config file > Drivers to try are: "vmware" "fbdev" "vesa" "vga" > (II) Module "ramdac" already built-in > (EE) AIGLX: Screen 0 is not DRI capable > The XKEYBOARD keymap compiler (xkbcomp) reports: >> Warning: Symbol map for key <BKSP> redefined > ??????????????????? Using last definition for conflicting fields > .... more key map warnings > Errors from xkbcomp are not fatal to the X server > > Fatal server error: > could not open default font 'fixed' > XIO: fatal IO error 146 (Connection refused) on X server ":0.0" > after 0 requests (0 known processed) with 0 events remaining > > Anyhow, I am just asking to see if anyone has any idea what is going on and > how i can fix it? > > Thanks, > Brendon. > > _______________________________________________ > opensolaris-help mailing list > opensolaris-help at opensolaris.org >
