cannot boot from new kernel

[pooh9038]

Sorry to use English since my harddisk was damaged yesterday. I just reinstall Debian and still configuring the Chinese environment.

I upgrade my kernel to 2.4.20-k7 and follow Mr.Moto's manual and run
"ln -s /boot/initrd-.img-2.4.20-k7 /boot/initrd"

Then I amend the lilo.conf according to the manual.

However when I ran "lilo -v -v -v" the following error is seen:

debian:/home/pooh# lilo -v -v -v
LILO version 22.3.3, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2002 John Coffman
Released 30-Aug-2002 and compiled at 15:38:21 on Sep 1 2002.

raid_setup returns offset = 00000000 ndisk = 0
Reading boot sector from /dev/hda
bios_dev: device 0308
bios_dev: masked device 0300, which is /dev/hda
bios_dev: geometry check found 0 matches
bios_dev: PT match found 1 match (0x80)
Device 0x0308: BIOS drive 0x80, 255 heads, 7297 cylinders,
63 sectors. Partition offset: 17976798 sectors.
Using MENU secondary loader
Calling map_insert_data
Secondary loader: 16 sectors (0x3000 dataend).

Boot image: /vmlinuz -> boot/vmlinuz-2.4.20-k7
bios_dev: device 0308
bios_dev: masked device 0300, which is /dev/hda
bios_dev: geometry check found 0 matches
bios_dev: PT match found 1 match (0x80)
Device 0x0308: BIOS drive 0x80, 255 heads, 7297 cylinders,
63 sectors. Partition offset: 17976798 sectors.
Setup length is 10 sectors.
Mapped 1317 sectors.
Mapping RAM disk /boot/initrd -> /boot/initrd-.img-2.4.20-k7
Fatal: open /boot/initrd: No such file or directory
Removed temporary file /boot/map~


The relevant part of my lilo.conf is as follows:

default=Linux
image=/vmlinuz
label=Linux
initrd=/boot/initrd
read-only
# restricted
# alias=1

image=/vmlinuz.old
label=LinuxOLD
read-only
append="hdc=scsi "
optional
# restricted
# alias=2

[pooh9038]

Continued

My boot directory is as follows:

debian:/boot# ls -la
total 5848
drwxr-xr-x 2 root root 4096 Jan 13 18:03 .
drwxr-xr-x 20 root root 4096 Jan 13 16:06 ..
-rw-r--r-- 1 root root 559088 Jan 14 2003 System.map-2.4.18-bf2.4
-rw-r--r-- 1 root root 438204 Jan 11 21:21 System.map-2.4.20-k7
-rw-r--r-- 1 root root 512 Jan 14 2003 boot.0300
-rw-r--r-- 1 root root 16984 Jan 14 2003 config-2.4.18-bf2.4
-rw-r--r-- 1 root root 39644 Jan 11 19:41 config-2.4.20-k7
lrwxrwxrwx 1 root root 27 Jan 13 16:40 initrd -> /boot/initrd-.img-2.4.20-k7
-rw-r--r-- 1 root root 2904064 Jan 13 16:06 initrd.img-2.4.20-k7
-rw------- 1 root root 46080 Jan 13 16:07 map
-rw-r--r-- 1 root root 1263339 Jan 14 2003 vmlinuz-2.4.18-bf2.4
-rw-r--r-- 1 root root 673092 Jan 11 21:21 vmlinuz-2.4.20-k7

Since the initrd is inside so I can't understand why there is an message "Fatal: open /boot/initrd: No such file or directory ".

[jesse.sung]

lrwxrwxrwx 1 root root 27 Jan 13 16:40 initrd -> /boot/initrd-.img-2.4.20-k7
-rw-r--r-- 1 root root 2904064 Jan 13 16:06 initrd.img-2.4.20-k7

initrd link 到的檔名多了一個 '-' 喔....

[pooh9038]

多謝指導，你們真是明察秋毫，真不愧為大師。小弟老眼昏花，真是汗顏不已。

升級至2.4.20後，懸而未決的ide-scsi emulation的問題亦一併解決。 （但現在最新版本的cdrecord可在沒有ide-scsi emulation的情況下燒錄，可惜效果不大理想和穩定）

我發現unstable中有關2.4.20的kernel header 只有一種，不像2.4.19的有給K7,K6,i368,i686等不同機種使用。是不是還有一些2.4.20的kernel header 未進入unstable?我擔心用這版本的header 來編譯 nvidia kernel src的時候又再出現unresolved symbols 的問題。

[阿信]

不會的，kernel-headers-2.4.20會順便安裝kernel-build。

然後系統會編譯了k7 k6 i386 sparc等kernel-headers...大約120m，不知道為甚麼maintainer要這樣作，很浪費空間和時間的作法。

安裝好之後，就會在/usr/src下面出現給所有cpu的kernel-headers。