On 03/09/10 21:13, Jonathon Fernyhough wrote: > On 3 September 2010 21:09, Rob Beard<[email protected]> wrote: >> >> VirtualBox is a reasonably easy way of trying it out if you have a half >> decent spec machine (Pentium 4/Athlon 64 or higher with say 1GB ram or >> higher). This way if it screws up you only screw up the virtual machine. > > Normally I'd agree wholeheartedly - but on this occasion a couple of > things. One, you can't check if your own hardware works fully > (principally graphics card).
You can set the option for 3D passthrough in virtualbox - admittedly it isn't as good as running it bare metal, but it's less messing around, especially if it turns out not to work. If it isn't working but you still want to test the rest of Maverick, disable it in the VM settings. > Two, VirtualBox's guest additions (3.2.8) > don't work properly with the latest Xorg and server in Maverick. Make sure your install is updated. Make sure you have the correct packages from the Maverick repos installed for it to work - specifically: build-essential dkms virtualbox-ose-guest-x11 virtualbox-ose virtualbox-ose-guest-utils virtualbox-ose-qt virtualbox-ose-guest-dkms virtualbox-guest-additions Do not confuse virtualbox-ose-guest-dkms with virtualbox-ose-dkms. If you tried installing the guest additions from outside the Maverick repos, uninstall like this from the virtual CD, ideally before you install the above (substituting for your machine architecture if necessary): sudo ./VBoxLinuxAdditions-x86.run uninstall That works here, and should work on your VM as long as you don't mind losing some of the graphics candy. -- JimP -- [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
