I followed your howto word for word, and i am now using my 2.6.11 kernel. thank you so much for writing it! however, i have lost all sound support. when i run alsaconf, it picks up my card and loads modules, but when i run alsamixer, i can't turn up the master volume level.

i get this error when i try and run xmms:

libmikmod.so.2: cannot open shared object file: No such file or directory
Inconsistency detected by ld.so: ../sysdeps/generic/dl-tls.c: 72: _dl_next_tls_modid: Assertion `result <= _rtld_local._dl_tls_max_dtv_idx' failed!

i double checked, and all the sound options in the xconf were compiled and installed as modules, like they were on the kernel that was installed with debian. any ideas?

The xmms problem is described here:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=219352

and here:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=219962

I think if you run: It will fix it, but I am not certain of that.

i followd your instructions, and installed libmikmod2, and now xmms will start up and play songs....but still no sound. none of the installed mixers will let me adjust the master volume setting, it's not muted...just isnt available.

any ideas?

I've never seen that. You may be better off posting the question as a new thread. More people will look at it that way.

one question...is there anyway I can install the logo without recompiling the kernel?

As far as I know, you have to patch the kernel to get the Debian logo. However, there is a neat package called "boot-icons" that will show boot progress graphically. You can install it with: For it to work, the kernel framebuffer display has to be working properly, but it doesn't require recompiling the kernel.

Hi stuck right at the start of this tutorial with the first command I receieve this error

debian:/home/flebber# apt-get -t unstable install kernel-image-2.6.11-6-386
Reading Package Lists... Done
Building Dependency Tree... Done
E: Couldn't find package kernel-image-2.6.11-6-386
debian:/home/flebber# apt-get -t unstable install kernel-image-2.6.11-1-386
Reading Package Lists... Done
Building Dependency Tree... Done
E: Couldn't find package kernel-image-2.6.11-1-386
debian:/home/flebber# apt-get -t unstable install kernel-image-2.6.10-1-386
Reading Package Lists... Done
Building Dependency Tree... Done
E: Couldn't find package kernel-image-2.6.10-1-386
debian:/home/flebber# apt-get -t unstable install kernel-image-2.6.7-1-386
Reading Package Lists... Done
Building Dependency Tree... Done
E: Couldn't find package kernel-image-2.6.7-1-386

Make sure you have "unstable" sources available. Add a line in /etc/apt/sources.list Then do:If you then run: It will tell you what 2.6.x kernels are available. To install kernel 2.6.11, run: Note you don't need to add the -6-386.

does anyone know if someone has built packages with the kernel logo?

I've followed the 2.6 kernel upgrade thread and upgraded the kernel with no problems. However my boot logo is a little odd. The screen is definetly in the res I want, with a decent level of colours, but only the debian logo shows - no text - which is obviously a pain.

I *did* compile in VGA 8x8 font and VGA 8x16 font and have tried vesa and vesafb. Both give me the debian logo but no text.

I'm not sure where to head next with this one, any ideas?

i have a simple question that i can not figure out (based on this thread and 2.6 kernel). why not compile ide / filesystem support for your system directly into the kernel, as opposed to modules and the need for initrd?

I have a simple question that i can not figure out (based on this thread and 2.6 kernel): why not compile ide / filesystem support for your system directly into the kernel, as opposed to modules and the need for initrd?

There is nothing stopping you from compiling everything you need into the kernel and eliminating the initrd. You just need to be sure that you do in fact have everything you need, otherwise the kernel won't boot. I just felt like there was not anything really to be gained by NOT having the initrd.

i see. time for me to move up to a 2.6 kernel. thanks for the reply and post!

Nice guide, vavoum also helped me sort out my problem with the framebuffer console.

For some reason, even though I was using the .config file of a working 2.6.8 kernel, compiling a new one with the same config file gave me a blank screen on reboot. Blank screen only when using a vga mode for fbconsole naturally.

Had to use what was suggested in original post plus only support for rivatnt module.