I have been following this EXCELLENT guide: http://www.linuxquestions.org/questi...threadid=73436

I made the image and I didn't make a initrd-2.6.6.img file as I don't have any SCSI devices.

When I reboot the system and chose my new Kernel at the LILO menu, it said "COULDNT FIND INIT IMG...TRY PASSING INIT= TO KERNEL"

I then made the initrd-2.6.6img but the same prompt came up :/

Any ideas?

bump

did you edit your grub.conf or lilo.conf file to tell it where to find that initrd.img file? if you scroll down in that EXCELLENT guide you will notice a section about editing your bootloader configuration file. don't forget to save and update grub/lilo with /sbin/grub-install or /sbin/lilo.

hope this helps.

Nope

I tried again, I even tried using my old initrd but it keeps saying the same thing:

Kernel Panic: No init found. Try passing init = to the kernel.


Please help!

so you are able to boot into your old kernel? if so, please post your bootloader config file (/etc/lilo.conf or /etc/grub.conf), as well as the results of

Yes, I'm able to boot into my old kernel.

Ok, well when I run the command you gave me this pops up:

drwxr-xr-x 3 root root 4096 Jun 2 17:34 ./
drwxr-xr-x 20 root root 4096 Jun 2 17:34 ../
-rw-r--r-- 1 root root 512 May 31 10:32 boot.0300
-rw-r--r-- 1 root root 1429627 May 31 22:43 bzImage
-rw-r--r-- 1 root root 1429628 May 31 22:00 bzImage.new
lrwxrwxrwx 1 root root 29 Jun 2 17:34 config -> config-2.6.3-7mdk-p3-smp-64GB
-rw-r--r-- 1 root root 54087 Mar 17 15:58 config-2.6.3-7mdk
-rw-r--r-- 1 root root 54189 Mar 17 15:19 config-2.6.3-7mdk-i686-up-4GB
-rw-r--r-- 1 root root 52029 Mar 17 15:36 config-2.6.3-7mdk-p3-smp-64GB
-rw-r--r-- 1 root root 51912 Mar 17 14:26 config-2.6.3-7mdksmp
-rw-r--r-- 1 root root 5032 Feb 19 18:03 diag1.img
-rw-r--r-- 1 root root 16796 Feb 19 18:03 diag2.img
drwxr-xr-x 2 root root 4096 Jun 2 08:19 grub/
-rw-r--r-- 1 root root 194709 May 31 10:32 initrd-2.6.3-7mdk-i686-up-4GB.img
-rw-r--r-- 1 root root 221534 May 31 10:32 initrd-2.6.3-7mdk.img
-rw-r--r-- 1 root root 200242 May 31 10:32 initrd-2.6.3-7mdk-p3-smp-64GB.img
-rw-r--r-- 1 root root 196036 May 31 10:32 initrd-2.6.3-7mdksmp.img
lrwxrwxrwx 1 root root 33 May 31 10:32 initrd-i686-up-4GB.img -> initrd-2.6.3-7mdk-i686-up-4GB.img
lrwxrwxrwx 1 root root 21 May 31 10:32 initrd.img -> initrd-2.6.3-7mdk.img
lrwxrwxrwx 1 root root 33 May 31 10:32 initrd-p3-smp-64GB.img -> initrd-2.6.3-7mdk-p3-smp-64GB.img
lrwxrwxrwx 1 root root 24 May 31 10:32 initrd-smp.img -> initrd-2.6.3-7mdksmp.img
lrwxrwxrwx 1 root root 37 Jun 2 17:34 kernel.h -> /boot/kernel.h-2.6.3-7mdk-p3-smp-64GB
-rw-r--r-- 1 root root 537 May 31 23:02 kernel.h-2.6.3-7mdk
-rw-r--r-- 1 root root 537 May 31 10:38 kernel.h-2.6.3-7mdk-p3-smp-64GB
-rw------- 1 root root 604672 Jun 2 17:25 map
lrwxrwxrwx 1 root root 15 Jun 2 08:20 message -> message-graphic
-rw-r--r-- 1 root root 442273 May 31 10:32 message-graphic
-rw-r--r-- 1 root root 116 May 31 10:32 message-text
lrwxrwxrwx 1 root root 33 Jun 2 08:16 System.map -> System.map-2.6.3-7mdk-p3-smp-64GB
-rw-r--r-- 1 root root 898908 Mar 17 15:58 System.map-2.6.3-7mdk
-rw-r--r-- 1 root root 900900 Mar 17 15:19 System.map-2.6.3-7mdk-i686-up-4GB
-rw-r--r-- 1 root root 902877 Mar 17 15:36 System.map-2.6.3-7mdk-p3-smp-64GB
-rw-r--r-- 1 root root 900767 Mar 17 14:26 System.map-2.6.3-7mdksmp
-rw-r--r-- 1 root root 929813 Jun 2 07:58 System.map-2.6.6
-rw-r--r-- 1 root root 256 May 31 10:32 us.klt
lrwxrwxrwx 1 root root 19 Jun 2 07:58 vmlinuz -> /boot/vmlinuz-2.6.6
-rw-r--r-- 1 root root 1440198 Mar 17 15:58 vmlinuz-2.6.3-7mdk
-rw-r--r-- 1 root root 1468886 Mar 17 15:19 vmlinuz-2.6.3-7mdk-i686-up-4GB
-rw-r--r-- 1 root root 1527883 Mar 17 15:36 vmlinuz-2.6.3-7mdk-p3-smp-64GB
-rw-r--r-- 1 root root 1490541 Mar 17 14:26 vmlinuz-2.6.3-7mdksmp
-rw-r--r-- 1 root root 1486023 Jun 2 07:58 vmlinuz-2.6.6
lrwxrwxrwx 1 root root 30 May 31 10:32 vmlinuz-i686-up-4GB -> vmlinuz-2.6.3-7mdk-i686-up-4GB
lrwxrwxrwx 1 root root 30 May 31 10:32 vmlinuz-p3-smp-64GB -> vmlinuz-2.6.3-7mdk-p3-smp-64GB
lrwxrwxrwx 1 root root 21 May 31 10:32 vmlinuz-smp -> vmlinuz-2.6.3-7mdksmp


Here is my lilo.conf:

# File generated by DrakX/drakboot
# WARNING: do not forget to run lilo after modifying this file

boot=/dev/hda
default="linux-p3-smp-64GB"
prompt
nowarn
timeout=100
message=/boot/message
menu-scheme=wb:bw:wb:bw
image=/boot/vmlinuz-2.6.6
label="Linux"
root=/dev/hda1
initrd=/boot/initrd-p3-smp-64GB.img
append="devfs=mount acpi=ht resume=/dev/hda5 splash=silent"
vga=788
read-only
image=/boot/vmlinuz-2.6.6
label="linux-nonfb"
root=/dev/hda1
initrd=/boot/initrd.img
append="devfs=mount acpi=ht resume=/dev/hda5"
read-only
image=/boot/vmlinuz-i686-up-4GB
label="linux-i686-up-4GB"
root=/dev/hda1
initrd=/boot/initrd-i686-up-4GB.img
append="devfs=mount acpi=ht resume=/dev/hda5 splash=silent"
read-only
image=/boot/vmlinuz-p3-smp-64GB
label="linux-p3-smp-64GB"
root=/dev/hda1
initrd=/boot/initrd-p3-smp-64GB.img
append="devfs=mount acpi=ht resume=/dev/hda5 splash=silent"
read-only
image=/boot/vmlinuz-2.6.3-7mdk
label="263-7"
root=/dev/hda1
initrd=/boot/initrd-2.6.3-7mdk.img
append="devfs=mount acpi=ht resume=/dev/hda5 splash=silent"
read-only
image=/boot/vmlinuz-smp
label="linux-smp"
root=/dev/hda1
initrd=/boot/initrd-smp.img
append="devfs=mount acpi=ht resume=/dev/hda5 splash=silent"
read-only
image=/boot/vmlinuz-2.6.6
label="failsafe"
root=/dev/hda1
initrd=/boot/initrd.img
append="failsafe acpi=ht resume=/dev/hda5 devfs=nomount"
read-only
other=/dev/fd0
label="floppy"
unsafe
image=/boot/bzImage
label="test"
root=/dev/hda1
read-only

Thanks in advance,

Neal

Bumpski I want my new Kernel because

New Kernel == New ATI Drivers == 100FPS on CS

Are you guys serious? No one can help a poor user in need?

Third consecutive bump

Hi,

I'm afraid that this is unlikely to be any use to you, but here goes anyway...


I had exactly the same problem as you, and I didn't know how to create the RAMdisk image before I bumped into your post and the tutorial it referred to (I'm stll very much learning Linux sys admin!).

So, I went off and created a new initrd image with the following cmd line:

/sbin/mkinitrd /boot/initrd-2.6.6-dom.img 2.6.6

I then did:

ln -sf /boot/initrd-2.6.6-dom.img /boot/initrd.img

Finally I modified my lilo conf so that the entry for the new kernel was identical to the default one for 'linux' (as provided by my Mandrake 10.0 installation), naturally modified so that it pointed to the new kernel and gave the new kernel a new label in lilo.conf.

This removed the problem of kernel panic, but I do have new problems since updating to the 2.6.6 kernel from 2.6.3.

The new problems are:

1) I have two ethernet cards, in my 2.6.3 config they were (as you'd expect) named eth0 and eth1. In the 2.6.6 config there are now eth0, eth1 and eth2. eth0 fails to initialise on startup, though after the system has booted it appears to have the same IP as eth1, eth2 starts up OK (this used to be eth1 in 2.6.3). Things work but I don't know why it happened and that concerns me - any advice would be appreciated!
2) My DVD-ROM drive (the only optical drive in the system) no longer mounts disks in the 2.6.6 config (though it does if I go back to 2.6.3). I've no idea why this is happening but it is very frustrating - again advice would be appreciated. If I try to manually mount, I get:

mount: wrong fs type, bad option, bad superblock on /dev/hdg, or too many mounted file systems

please check and/or post your /proc/filesystems file. this is where you will find the filesystems that your system supports. if your system does not recognize cd's it is most likely that you did not include support for the iso9660 filesystem which is what most cd-roms use. you might have included this as a module, rather than compiled in, which wouldn't be too bad, as you could set it up to load when you boot (if you don't really feel like recompiling, which i understand).

hope this helps.

also, i'm not sure what command you gave to mount the cd but something similar to: should work, of course correcting paths where necessary.

Thanks lyceum,

I viewed the /proc/filesystems file (I can still post it if that will help) and found that iso9660 only appears in the file when a CD is actually mounted which seems a bit strange.

On the CDROM support side of things I compiled ISO9660 support directly into the kernel , under File systems->CD-ROM/DVD Filesystems->ISO 9660 CDROM file system support - I actually added everything under that option to the kernel (rather than as modules).

I've since compiled Kernel 2.6.7 and have the same issues but...

The command line you suggested did allow me to mount a CD on 2.6.6 and 2.6.7, I modified it slightly to be:

In the 2.6.3 config, if I insert a CD-ROM it gets mounted automatically, but doesn't on 2.6.6/2.6.7 (presumably due to whatever I've done to make the standard mount command not work). Should I be editing my fstab to allow automounting again, and if so how? the current entry for the DVD drive is as follows:

Thanks again

OK,

The CD problem seems to be solved. After reading this post:

http://www.linuxquestions.org/questi...hreadid=186220

I removed the part of the entry from the DVD's entry in /etc/fstab and now mounting/automounting seems to work fine.

I would be very interested to know why this made a difference (what does/should codepage=850 actually do?) and why it worked with the shipping 2.6.3 kernel but not the 2.6.6/2.6.7 ones that I compiled? I'm just curious now and its an opportunity to learn if anyone knows the answer.

The networking issue is still there, but again is more of a curiosity thing now since it works - just a bit odd that there is a 'phantom' interface.

this is from nls_cp850.c from the kernel sources. i've also found this link where a guy seems to have the same problem with a 2.6 kernel and gets the same error message. if you read through the thread he eventually finds that he compiled cp852 and not cp850, so the codepage=850 returned an error.

hope this helps.