I prefer kernels with better timer resolution for music applications. There's a good low latency kernel available for ubuntu 'natty' which seems to work very well for me on my Mint 10 KDE install. I followed the instructions here: http://longspine.com/how-to/real-time-k ... k-meerkat/
uname -a then shows:Linux asus 2.6.38-5-lowlatency #32~ppa1-Ubuntu SMP PREEMPT Wed Feb 23 11:08:30 UTC 2011 x86_64 GNU/Linux
I have a couple of kernel modules. One was installed for the fairly recent proprietary nVidia graphics card driver and the other for VirtualBox. So I installed the kernel headers too (mentioned in the article as "Optional").
Without fixing the new kernel for the nVidia driver the computer will not fully boot to the desktop. The Grub boot manager offers an option to boot the new kernel in 'recovery mode' so I chose that and then chose the 'netroot' option.
It may be worth trying the 'failsafeX' recovery mode, but it hasn't worked for me. I have a proper root user account, so I typed my root password, but your normal user password should work just as well (if the root account isn't set up). Leave the 'sudo' off of the following commands if you are root:
- Code: Select all
sudo cp xorg.conf xorg.conf.OLD
sudo cp xorg.conf.failsafe xorg.conf
No need to use recovery mode this time. The desktop should come up, although it will probably be smaller than usual (everything on your desktop may look bigger). Now go to System - Additional Drivers and select the (version current) 'Recommended' driver and Activate it. Reboot in the usual way when it has finished and your new Low-latency kernel should now work with the graphics driver you were previously using.
Now to fix VirtualBox. When I tried to run a virtual machine, it came up with a dialog saying "The VirtualBox Linux driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing (as root):
so that's what I did:
- Code: Select all
[root@asus john]# /etc/init.d/vboxdrv setup
* Stopping VirtualBox kernel modules * done.
* Uninstalling old VirtualBox DKMS kernel modules
Error! There are no instances of module: vboxhost
4.0.2 located in the DKMS tree. * done.
* Trying to register the VirtualBox kernel modules using DKMS
Error! Bad return status for module build on kernel: 2.6.38-5-lowlatency (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/vboxhost/4.0.2/build/ for more information.
Traceback (most recent call last):
File "/usr/share/apport/package-hooks/dkms.py", line 57, in <module>
IOError: [Errno 2] No such file or directory: '/var/crash/virtualbox-4.0.0.crash'
* Failed, trying without DKMS
* Recompiling VirtualBox kernel modules
* Look at /var/log/vbox-install.log to find out what went wrong
I didn't bother. Virtual Box versions are released quite often, so I simply un-installed the old and installed a new (4.04) version and then upgraded the Guest Additions on my VMs. Everything is now working just great and even seems a little faster than before.