Master Kernel Thread

**Klondikes** · March 9th, 2010

I would start by uninstalling VirtualBox and then download the latest version of VirtualBox 3.1.4 from http://www.virtualbox.org/wiki/Linux_Downloads.

**Chikitulfo** · March 11th, 2010

It worked!
I thought I was using the last version...

**Klondikes** · March 12th, 2010

VirtualBox should have added a line to /etc/apt/sources.list such as

Code:

deb http://download.virtualbox.org/virtualbox/debian karmic non-free #virtualbox

With that line in sources.list, you should be notified of any VirtualBox updates when you update your system through apt.

**serein** · March 23rd, 2010

i'm having problem with the latest 2.6.33-kernel. i grab it from git, and it's now on 2.6.33.1 and this is the output i get installing the packages:

Code:

Examining /etc/kernel/preinst.d/
Done.
Packar upp ersättande linux-image-2.6.33.1-dude ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs
Running postrm hook script /usr/sbin/update-grub.
Generating grub.cfg ...
Found Debian background: ubuntu_grub2_splash.tga
Found linux image: /boot/vmlinuz-2.6.33.1-dude
Found linux image: /boot/vmlinuz-2.6.32.9-dude
Found initrd image: /boot/initrd.img-2.6.32.9-dude
Found linux image: /boot/vmlinuz-2.6.32.8-dude
Found initrd image: /boot/initrd.img-2.6.32.8-dude
Found linux image: /boot/vmlinuz-2.6.32.7-dude
Found linux image: /boot/vmlinuz-2.6.31-20-generic
Found initrd image: /boot/initrd.img-2.6.31-20-generic
Found linux image: /boot/vmlinuz-2.6.31-19-generic
Found initrd image: /boot/initrd.img-2.6.31-19-generic
Found linux image: /boot/vmlinuz-2.6.31-17-generic
Found initrd image: /boot/initrd.img-2.6.31-17-generic
Found memtest86+ image: /memtest86+.bin
Found unknown Linux distribution on /dev/sdb2
done
Ställer in linux-headers-2.6.33.1-dude (2.6.33.1-dude-10.00.Custom) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms
 * Running DKMS auto installation service for kernel 2.6.33.1-dude

 *  nvidia (185.18.36)...
nvidia (185.18.36): Installing module.
.......(bad exit status: 10)
  Build failed.  Installation skipped.
   ...fail!
 *  vboxdrv (3.0.12)...
vboxdrv (3.0.12): Installing module.
.......(bad exit status: 10)
  Build failed.  Installation skipped.
   ...fail!
 *  vboxnetadp (3.0.12)...
vboxnetadp (3.0.12): Installing module.
.......(bad exit status: 10)
  Build failed.  Installation skipped.
   ...fail!
 *  vboxnetflt (3.0.12)...
vboxnetflt (3.0.12): Installing module.
.......(bad exit status: 10)
  Build failed.  Installation skipped.
   ...fail!

Ställer in linux-image-2.6.33.1-dude (2.6.33.1-dude-10.00.Custom) ...
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms
run-parts: executing /etc/kernel/postinst.d/initramfs
Running postinst hook script update-grub.
Generating grub.cfg ...
Found Debian background: ubuntu_grub2_splash.tga
Found linux image: /boot/vmlinuz-2.6.33.1-dude
Found initrd image: /boot/initrd.img-2.6.33.1-dude
Found linux image: /boot/vmlinuz-2.6.32.9-dude
Found initrd image: /boot/initrd.img-2.6.32.9-dude
Found linux image: /boot/vmlinuz-2.6.32.8-dude
Found initrd image: /boot/initrd.img-2.6.32.8-dude
Found linux image: /boot/vmlinuz-2.6.32.7-dude
Found linux image: /boot/vmlinuz-2.6.31-20-generic
Found initrd image: /boot/initrd.img-2.6.31-20-generic
Found linux image: /boot/vmlinuz-2.6.31-19-generic
Found initrd image: /boot/initrd.img-2.6.31-19-generic
Found linux image: /boot/vmlinuz-2.6.31-17-generic
Found initrd image: /boot/initrd.img-2.6.31-17-generic
Found memtest86+ image: /memtest86+.bin
Found unknown Linux distribution on /dev/sdb2
done

the essential is the failure of building nvidia-module (and i get a "no suitable fs found in /proc/mount, is it mounted blahblahblah"). now, is there any way of fixing this? or am i doomed to use older kernels?

**master_kernel** · March 29th, 2010

Originally Posted by serein

about the initrd: http://linuxagora.com/vbforum/showthread.php?t=1126
trying this one right now. brb.

EDIT: it fixed it.

I just ran into this problem. I'm bookmarking it for myself to use with KernelCheck

**master_kernel** · March 30th, 2010

Originally Posted by Klondikes

i follow and reference your master kernel thread post frequently. i must say, this post is priceless! thank you!

i was wondering, why not use fakeroot for the make-kpkg command? use of root to compile code is considered unwise, possibly dangerous, etc.

here are some discussions on the use of root to compile code:
http://www.mail-archive.com/debian-u...msg332985.html
http://www.owlriver.com/tips/non-root/

by using fakeroot, users can compile the kernel and create the debian packages without root privileges.

one benefit to this is the ability to store the linux source in their home directory. e.g., i now have my source in ~/src.

the changes to the guide would be

1. add fakeroot to the build command:

Code:

INSTALL_MOD_STRIP=1 CONCURRENCY_LEVEL=3 fakeroot make-kpkg --initrd --append-to-version=-mk kernel_image kernel_headers modules_image

2. remove the unnecessary command:

Code:

sudo -s

3. use sudo to install the new kernel packages

Code:

cd .. && sudo dpkg -i linux*2.6.32*.deb

4. since /usr/src is a root owned directory, change appropriate paths to ~/src (or similar)

thoughts?

Noted.

**wbar2** · April 27th, 2010

I used both the instructions on this thread and the KernelCheck program to attempt to install 33. But, after installing I get the following errors when loading the new kernel:

Code:

pci 0000:09:00.0: no compatible bridge window for [mem 0xffff0000-0xffffffff pref]
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

After this it won't load.

I think the second error has to due with it not point to the correct partition? Is this right? If so, how do I fix this?

**master_kernel** · April 27th, 2010

Looks like missing SATA drivers in the kernel. You have to recompile with SATA drivers enabled - you probably disabled them by accident.

**wbar2** · April 28th, 2010

That's odd, because I just tried this again on another machine and I made absolutely sure I changed none of the options. Is my current config file not being copied properly? I'm using KernelCheck.

EDIT: I also tried on my laptop again, making sure to enable SATA options. It booted once, but after I restarted I got locked out with all kinds of errors. I'm missing something here.

EDIT-SOLVED

!: For some reason when I follow the instructions on this thread, or when I use KernelCheck an initrd image is not generated. Therefore none of my modules would load, including SATA. I ran this in terminal and now 2.6.33.3 is up and running one at least one machine:

Code:

sudo update-initramfs -c -k 2.6.33.3-mk

I found that it may actually be related to a bug? https://bugs.launchpad.net/initramfs-tools/+bug/220094

**master_kernel** · April 28th, 2010

Originally Posted by wbar2

That's odd, because I just tried this again on another machine and I made absolutely sure I changed none of the options. Is my current config file not being copied properly? I'm using KernelCheck.

EDIT: I also tried on my laptop again, making sure to enable SATA options. It booted once, but after I restarted I got locked out with all kinds of errors. I'm missing something here.

EDIT-SOLVED

!: For some reason when I follow the instructions on this thread, or when I use KernelCheck an initrd image is not generated. Therefore none of my modules would load, including SATA. I ran this in terminal and now 2.6.33.3 is up and running one at least one machine:

Code: