DKMS missing on Kubuntu netbook / Virtualbox not working

[KubuntuTrouble]

You're probably not getting the menu because of the error. I see on the internet that 13.04 supports chromebooks so it should be able to work.

The only thing I'm worried about is leaving your computer un-bootable. Can you boot to a LiveUSB image OK? If yes, then let's tear into it...

Try re-installing GRUB manually. From a Kubuntu terminal, type this:

ls /boot/grub

This is just to make sure GRUB is installed there. You should have a bunch of files in that location. If so, then:

sudo grub-install --boot-directory=/boot /dev/sda
sudo update-grub
sudo reboot

This should put GRUB on your ssd and update it. Let me know what happens next.

sudo grub-install --boot-directory=/boot /dev/sda gives an error:

/usr/sbin/grub-setup: warn: This GPT partition label has no BIOS Boot Partition; embedding won't be possible!.
/usr/sbin/grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
/usr/sbin/grub-setup: error: will not proceed with blocklists.

EDIT: Also grub is installed correctly according to: ls /boot/grub

[KubuntuTrouble]

I`m Google-ing my eyes out now, to, atleast, get Grub working.

[oshunluvr]

You're probably not getting the menu because of the error. I see on the internet that 13.04 supports chromebooks so it should be able to work.

The only thing I'm worried about is leaving your computer un-bootable. Can you boot to a LiveUSB image OK? If yes, then let's tear into it...

Try re-installing GRUB manually. From a Kubuntu terminal, type this:

ls /boot/grub

This is just to make sure GRUB is installed there. You should have a bunch of files in that location. If so, then:

sudo grub-install --boot-directory=/boot /dev/sda
sudo update-grub
sudo reboot

This should put GRUB on your ssd and update it. Let me know what happens next.

[KubuntuTrouble]

Damn! did everything, but still I get the "Chrome OS" missing warning and after Cntrl+D Kubuntu just normally loads...

[KubuntuTrouble]

Okay! Changed the "GRUB_HIDDEN_TIMEOUT=0" to "#GRUB_HIDDEN_TIMEOUT=10"
and "GRUB_HIDDEN_TIMEOUT_QUIET=true" to "#GRUB_HIDDEN_TIMEOUT_QUIET=false"

now I will run update-grub and reboot.

[oshunluvr]

I wouldn't mess with those other partitions yet - lets get you running Kubuntu proper first.

[oshunluvr]

GRUB, if installed properly should allow you to boot to either chrome or Kubuntu. I've never messed with a chromebook, but maybe you just need to adjust GRUB a bit so you can see the menu. Edit the file /etc/default/grub and comment out

GRUB_HIDDEN_TIMEOUT=10
GRUB_HIDDEN_TIMEOUT_QUIET=false

by placing a # in front of each of these lines. Then re-run update-grub and reboot.

To edit the file, you can use "sudo nano /etc/default/grub" in a terminal, or if you prefer a normal text editor, type "kdesudo kate /etc/default/grub" in a terminal and Kate will pop open.

[KubuntuTrouble]

1st my partition manager

2nd is the install log from virtualbox.

[KubuntuTrouble]

Also, what I did WAS messy. because using the terminal that was built in my chromebook, I downloaded and installed ChrUbuntu, but as I did not like it, I switched to the regular Ubuntu with KDE (Kubuntu) and deleted the previous version. and here I am....

After I rebooted and used: Sudo apt-get autoremove I saw all the old packages from the 3.2 kernel, so that did a trick atleast!

[KubuntuTrouble]

That explains a lot. The Chromebooks came with 3.4 kernel. (K)Ubuntu never did.

The "image" part is: kernels for Ubuntu exist in three parts; Image - what you boot and run from, Headers - files needed by some drivers and programs (like virtualbox and dkms), and Source - actual kernel data needed to compile the kernel.

You have the Headers for 3.5 installed, but not the Image. Therefore, you cannot boot to 3.5 because you don't have the Image. Open Muon, search for linux-image and install.

However, I don't think this will help much because it sounds like your install is a mess. Did you leave the Chrome OS on it and then install without formatting? What error message? How did you do your install? It's really hard to offer any advice without any details.

I managed to do the 3.5 part..
Hah, it may be true my install is a mess. I partitioned my harddrive so Chrome OS is still on it, but has only 1 GB of movement space, ( I recall it being on /dev/sda3 or something) and Kubuntu on /dev/sda7. and on dev/sda8 sits OEM.

I did not know how to remove Chrome OS that time, and I didn`t want to format it because it had that scary "ROOT-A" label. is it okay if I format sda3? furthermore I have a lot of other dev/sda`s all taking up spaces as big as 16mb`s... I`ll post a screenshot after I rebooted. (To get 3.5 in effect I guess.)

Also, sorry for not mentioning it earlier, I did not really think it was relevant.

Cheers

[oshunluvr]

That explains a lot. The Chromebooks came with 3.4 kernel. (K)Ubuntu never did.

The "image" part is: kernels for Ubuntu exist in three parts; Image - what you boot and run from, Headers - files needed by some drivers and programs (like virtualbox and dkms), and Source - actual kernel data needed to compile the kernel.

You have the Headers for 3.5 installed, but not the Image. Therefore, you cannot boot to 3.5 because you don't have the Image. Open Muon, search for linux-image and install.

However, I don't think this will help much because it sounds like your install is a mess. Did you leave the Chrome OS on it and then install without formatting? What error message? How did you do your install? It's really hard to offer any advice without any details.

[KubuntuTrouble]

Well, the only thing I can think of that would cause this is you have somehow gotten a copy of the kernel version 3.4 but didn't install it. Grub has detected is and is booting to it. It's not in your /boot folder.

Let's try this:

sudo update-grub



you should see a list of all the kernel images GRUB finds. Then, reboot and select a kernel other than 3.4. Hopefully, 3.2.0-40 will be available. Once you're running that (or any other kernel than 3.4) look for the errant kernel image and delete it.

Another oddity is you've got the headers for 3.5 but no image. You might want to install the 3.5 image using muon before you do the above. GRUB should default to the newest kernel when booting so 3.5 would boot rather than 3.2 or 3.4.

Okay.. I ran into a wall here, I did the update GRUB part.. but I don`t understand the image 3.5 part, and I can`t seem to access Grub, when I boot my netbook, It always boots to an error message ( I am on a Chromebook) and I have to Cntrl+D it, then Kubuntu starts to boot, when I get past the error screen I tried pressing Shift, and tapping esc, but to no avail.

so the main question now: how to get the 3.5 image? and how to access grub? is there a command to force grub to boot?

[oshunluvr]

Well, the only thing I can think of that would cause this is you have somehow gotten a copy of the kernel version 3.4 but didn't install it. Grub has detected is and is booting to it. It's not in your /boot folder.

Let's try this:

sudo update-grub

you should see a list of all the kernel images GRUB finds. Then, reboot and select a kernel other than 3.4. Hopefully, 3.2.0-40 will be available. Once you're running that (or any other kernel than 3.4) look for the errant kernel image and delete it.

Another oddity is you've got the headers for 3.5 but no image. You might want to install the 3.5 image using muon before you do the above. GRUB should default to the newest kernel when booting so 3.5 would boot rather than 3.2 or 3.4.

[KubuntuTrouble]

Weird that your uname -r output says 3.4.0 and you have no kernels like that.

What's uname -a show and how about ls /boot

Hmmm, that would explain why my commands alway give "can`t find 3.4.0 headers" back.

uname -a = Linux Trouble 3.4.0 #1 SMP Mon Aug 27 02:12:50 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux

ls /boot =

abi-3.2.0-23-generic config-3.2.0-39-generic initrd.img-3.2.0-40-generic System.map-3.2.0-40-generic
abi-3.2.0-24-generic config-3.2.0-40-generic memtest86+.bin vmlinuz-3.2.0-23-generic
abi-3.2.0-39-generic grub memtest86+_multiboot.bin vmlinuz-3.2.0-24-generic
abi-3.2.0-40-generic initrd.img-3.2.0-23-generic System.map-3.2.0-23-generic vmlinuz-3.2.0-39-generic
config-3.2.0-23-generic initrd.img-3.2.0-24-generic System.map-3.2.0-24-generic vmlinuz-3.2.0-40-generic
config-3.2.0-24-generic initrd.img-3.2.0-39-generic System.map-3.2.0-39-generic

I guess I have 3.2.0 headers as it looks like this...

[oshunluvr]

Weird that your uname -r output says 3.4.0 and you have no kernels like that.

What's uname -a show and how about ls /boot