Comment 7 for bug 719446

> Well, if you could get the exact text of that error it might help;

I think the text I sent was it, barring the code; but I'll try to get that too using one of methods you suggested.

Log files not available, so I'll try the other methods you suggest next week.

......<snip>.....

> Please be sure to confirm this issue exists with the latest
> development release of Ubuntu. ISO CD images are available from
> http://cdimage.ubuntu.com/daily/current/ .

Can I pick your brain on this? (But tell me to go away and google if that's best for you).

As said in previous posts I'm pretty new to ubunu/linux. I'm trying to beat laptop into something that can do most of the things I do on my windows machines, which means running win versions in VirtualBox VMs for for forseeable future. In my experience VirtualBox is very sensitive to which kernel version (and presumably release) of ubuntu I'm using, and I've already got a slew of other software installed on my current version that may or may not work with latest release.

So is best approach to install development release and kernel in a new partition, and multibooting? If I install development release I assume it will notice existing grub stuff and just add itself to existing grub menu?

......<snip>......

> Also, if you could test the latest upstream kernel available that
> would be great. It will allow additional upstream developers to
> examine the issue. Refer to
> https://wiki.ubuntu.com/KernelMainlineBuilds .

I guess I want current version, pointed to as

http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ ?

I assume I apply that to existing Maverick install, not on? or also on? development release install?

Thanks for any help.