Boot Failure

[pnunn]

Hi Guys,

Just rebooted into the latest 3.3 kernel and had Nvidia and virboxadditions fail to build. Then booted back into the 2.9 kernal that was working and tried to turn on the nvidia drivers again (Which I did see load). Now however when I rebooted I'm thrown into grub befor I can select a Kernel... Help please.. how do I get this booting again?

Desperate

Peter

[pnunn]

I Just tried "rescue a system" from the MG2B disk. I Get to

proceeding, please wait.....
Failed to open /dev/kmsg for logging: No such file or directory
Failed to mount /dev/shm: No such fire or directory

on terminal3

* creating symlink /tmp/stage2/usr -> /usr
* killed shell
* stage1: disconnedting life support systems

on terminal 4

<6>loop: module loaded
<6>squashfs: version 4.0 (2009/01/31) Phillip Lougher

Then it hangs.. Am I stuffed??

Peter

[pnunn]

Well, sorry to say that I had te reinstall (not complaining, I'm on the bleeding edge and know it), but in the process of trying to recover the system I booted to a live Kubuntu distro (12.04 beta) and discovered that both bluetooth andt multi touch on the track pad worked out of the box... so.. I've installed that instead.

I'll keep a VM running this distro, because I want to come back to it some time.. but not until these things are sorted.. sorry.

Peter.

[wilcal]

FWIW my M2B1 install got so buggy and slow during boot-up
I did a complete re-install. After that all seems fine.
There was a kernel update in the last days and something
may have happened from that. Looks good for me now.

Also FWIW Vbox installs and real hardware installs are
close but not the same. Especially for video. At least
that's my experience. Gnome seems to be more
effected by a Vbox install.

I'm looking forward to M2B2 next week as things should
settle down considerably after that.