Upgrading Kernel Troubles

[Markus]

Hmm, do you actually need initrd. You also have 2 ramdisk sizes. Try with:

image=/boot/vmlinuz-2.6.5-1-k7
label="Linux(2.6.5)-1"
# initrd=/boot/initrd.img-2.6.5-1-k7
append="lang=us ramdisk_size=129000 dma apm=power-off hda=scsi nomce "
read-only

Umm, no. I meant the creating of an initrd but if you already have one it's ok.
Does /boot/System.map point to System.map-2.6.x?

[Linuxshark]

I did all that you said above and still the same dilio.

It says:

VFS:Connot open root device "302" or unknown-block(3,2)

Maybe I have to try to manually copy the Knoppix 2.6.5 kernel off the 04-05-10 CD

[Markus]

I'm getting out of ideas here
How about appending root for 2.6 in lilo and leaving initrd as it was:

image=/boot/vmlinuz-2.6.5-1-k7
label="Linux(2.6.5)-1"
initrd=/boot/initrd.img-2.6.5-1-k7
append="root=/dev/hda2 lang=us ramdisk_size=129000 dma apm=power-off hda=scsi nomce "
read-only

BTW, 2.6 kernels don't really make a speed difference if you aren't running some cluster server. For a desktop 2.4 is fine, unless it's one of those gotta have things

[Frost]

I've been messing around with the settings but without result. I really need a 2.6 kernel because my tv tuner card doesn't seem to work with older kernels .

Same error with or without initrd. Seems it can't access the HD or something like that...damn...I really need a new kernel...I want lirc to work...

Would it be possible to use the initrd from my 2.6.5 kernel when booting 2.6.6? Kernel 2.6.5 is booting fine (it's the knopix one).

Here's the part for the 2.6.6 kernel from lilo.conf:

image=/boot/vmlinuz-2.6.6-1-k7
        label="Linux226"
        #initrd=/boot/initrd-2.6.6-1-k7.img
        append="lang=nl keyboard=be ramdisk_size=129000 dma apm=power-off nomce "
        read-only

thx for your assistance so far,
Frost

[Markus]

Well as I said I'm getting out of ideas. Starting to look like the kernel-image has some difference in ide or filesystem for say ext3 compiled into the kernel. Module support won't do much good when booting up a disk.
I don't think you can use a different initrd from another kernel, but I've never tried it either.
If someone has installed a 2.6.6 debian kernel-image, could you post lilo.conf incl. appends?
Worst case scenario, you have to compile your own kernel. Install the source and headers, copy the config from /boot to /usr/src/linux/.config , run make oldconfig and make menuconfig.
Here's some links for that:
http://www.osnews.com/story.php?news_id=2949&page=1
http://newbiedoc.sourceforge.net/tut...el-pkg.html.en
http://kerneltrap.org/node/view/799

[Linuxshark]

oh, I should have mentioned that my root partition is a ReiserFS. Maybe that causes the trouble?

I will today try to install the Knoppix custom 2.6.5 kernel. Maybe this will do the trick.

As for kernel-compiling... here comes my next issue (I've tried it before ): I followed the steps in a kernel compiling tutorial. When I typed "make menuconfig" or "make xconfig" I get this:

root@dkserver:/usr/src/linux# make xconfig
  HOSTCC  scripts/basic/fixdep
In Datei, eingef?gt von /usr/include/sys/socket.h:35,
                    von /usr/include/netinet/in.h:24,
                    von scripts/basic/fixdep.c:107:
/usr/include/bits/socket.h:305:24: asm/socket.h: Datei oder Verzeichnis nicht gefunden
make[1]: *** [scripts/basic/fixdep] Fehler 1
make: *** [scripts_basic] Fehler 2
root@dkserver:/usr/src/linux#

("In Datei, eingefügt von" means "In file, inserted by"; "Datei oder Verzeichnis nicht gefunden" mean "file or directory not found"; "Fehler" means "error").

You see, my machine is really screwed up.

[Frost]

try

ln -s asm-i386 asm

in your includes directory, that helped for me.

I'll check what the installer makes of the lilo.conf, but because of windows etc, I don't let it overwrite my old one, so I'll backup it and reinstall the kernel-image...and then I'll tell you what it has created.

btw, my hd is ide Ext3 formatted. Woulnd't it be kind of stupid when the kernel-image wouldn't support that?

[Linuxshark]

Thanks again for all your help. First off, I now have another problem that occured during the kernel changes. When my system boots (whatever kernel), it does not mount my partitions (VFAT, NTFS) anymore. When I do "mount -a" after boot, I get an error saying "mount: no medium found", just as if the system didn't find my hda anymore. Yet, if i manually do "mount - vfat /dev/hda3 /mnt/hda3" it works! What could this be due to?

As for compiling a new kernel, thank you Frost, your hint worked, but I get another error: when making the modules I get

CC [M]  fs/reiser4/as_ops.o
fs/reiser4/as_ops.c: In Funktion >>move_inode_out_from_sync_inodes_loop<<:
fs/reiser4/as_ops.c:570: error: structure has no member named `dirtied_when'
make[2]: *** [fs/reiser4/as_ops.o] Fehler 1
make[1]: *** [fs/reiser4] Fehler 2
make: *** [fs] Fehler 2

.

Although I have patched the raw 2.6.5 kernel by the textbook (instrutions from reiser website), this error occurs.

As for other kernels, I got the 2.6.5 knoppix kernel that I downloaded from linuxtag to run successfully, but this version did/does not support Reiser4.

I think I'll have to wait until an official kernel (debian or knoppix) comes out that supports Reiser4.

[Markus]

The filesystem support not built into the kernel was just a guess while I can't think of anything else to try for booting up. Yes, they most probably are built in.

[Linuxshark]

As I wrote above, I now have a new/related issue:

First off, I now have another problem that occured during the kernel changes. When my system boots (whatever kernel), it does not mount my partitions (VFAT, NTFS) anymore. When I do "mount -a" after boot, I get an error saying "mount: no medium found", just as if the system didn't find my hda anymore. Yet, if i manually do "mount - vfat /dev/hda3 /mnt/hda3" it works! What could this be due to?

This heppens even if I use my old, initial Knoppix 3.4, 2.6.6 kernel. Everything works smoothly as before, it's just that my partitions won't mount anymore.

Is there still hope for my system?