Printable View
im trying to upgrade from 2.4.20-8 to 2.6.6
i have all the required dependencies
but i cant get lilo to accept the initrd-2.6.6.img file
its kinda late here so i cant give much details but il give more tomorrow
i tried going though the instructions here and got lost...not much on google or the RH site * im using redhat9*
Hmmm.
I would advise using GRUB as a bootloader instead, but if you are intent on using LILO I'll see what I can do...
Reinstall LILO. It has to be done after every kernel upgrade. (patches don't count)
Oh yeah, just to add, since this is about the 2.6.6 kernel, the YaST kernel configuration utility has to be updated befor it can configure the 2.6.6 kernel, 2.6.5 is all it supports right now.
Isnt YAST only with SUSE? (Or have I had too much crack today?)Quote:
Originally posted here by D0pp139an93r
Oh yeah, just to add, since this is about the 2.6.6 kernel, the YaST kernel configuration utility has to be updated befor it can configure the 2.6.6 kernel, 2.6.5 is all it supports right now.
Yeah, I thought I mentioned that, I guess not. I just went to 9.1 today.
ok..been busy but his is everything ive done....
i went to google and and searched and downloaded the 2.6.6 kernel from kernel.org and i got the sys requirements from http://kerneltrap.org/node/view/799 ...ive done the compiling and untaring and unbziping and now i have the system pat 2.6.6, vmlinuz2.6.6 and initrd2.6.6.img files in my /boot dir....i did rewrite lilo.../sbin/lilo -v -v...it gives me the error "syntax error on line 12 which is the line with initrd2.6.6.img....i dont no if i typed something wrong or what but everything looks normal
im going to try that YaST upgrade now....and so you know, when i installed RH i just click custom install/everything..so if its on the cd its on my comp if that helps any
il get back to you if i get anyware
still nothing.... :( it seems that anytime i try to do something with linux..it doesnt go right...took me months to get sound to work....took me a week to install lilo so i could dual boot linux/win98se...im getting very discouraged but im not giving up hope...as soon as summer comes and i start working im buying every single *nix manual from barns and nobel books and downloading every single bit and byte of text their is on *nix....
#mount /boot
make sure you type before copying in the image file and the initrd files. Otherwise you system will not find the kernel image file.
Don't be encouraged. Kernels and bootloaders can be very tricky, but once you get the hang of it, you'll play with it.
Do a /sbin/lilo and give the output here.
Also gimme your /etc/lilo.conf.
Anyway an initrdfile is not needed for a kernel to boot proper. It's just a surplus.
Make sure your system boots ok and then try tweak it with splash files and stuff.
I wrote a tut a while ago on 2.6 kernels. It might help you.
http://www.antionline.com/showthread...hreadid=251230
right now its 10:33pm and im trying to download fredora but im in windows xp home and im quite impressed actualy...no crashes yet and if their is a giltch it bounces back fairly well...*knocks on wood* il get thoes files to u asap but to keep the thread going....id like to know...who all here as tried fredora and how do you like it? ive heard good reviews and bad ones ...just like to know a little information to see if it is worth the 4 hour download per iso *cant find a fast server here :(*
ok the following are my lilo.conf file, lilo output and fstab *might be usefull*, if their is anything else u might need just ask
*lilo output *
LILO version 21.4-4, Copyright (C) 1992-1998 Werner Almesberger
'lba32' extensions Copyright (C) 1999,2000 John Coffman
Reading boot sector from /dev/hda
Merging with /boot/boot.b
Secondary loader: 11 sectors.
Mapping message file /boot/message
Message: 46 sectors.
Boot image: /boot/vmlinuz-2.6.6
Setup length is 10 sectors.
Mapped 2248 sectors.
Added linux *
Removed temporary file /boot/map~
*lilo.conf*
prompt
timeout=150
default=linux
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
image=/boot/vmlinuz-2.6.6
label=linux 2.6.6
initrd=/boot/initrd-2.6.6.img
read-only
append="hdd=ide-scsi root=LABEL=/"
image=/boot/vmlinuz-2.4.20-8
label=kernel 2.4.20-8
initrd=/boot/initrd-2.4.20-8.img
read-only
append="hdd=ide-scsi root=LABEL=/"
other=/dev/hdb1
label=win98se
table=/dev/hdb
map-drive = 0x80
to = 0x81
map-drive = 0x81
to = 0x80
*fstab*
LABEL=/ / ext3 defaults 1 1
none /dev/pts devpts gid=5,mode=620 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/hda2 swap swap defaults 0 0
/dev/cdrom1 /mnt/cdrom1 udf,iso9660 noauto,owner,kudzu,ro 0 0
/dev/sda1 /mnt/hd-usb auto auto,user 1 2
/dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0
/dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0
/dev/hdb1 /mnt/windows ntfs defaults 0 0
Remove the initrd line and see if it boots. The initrd isn't really required for the kernel to boot as shrekkie said.
Cheers,
cgkanchi
do the next in a shell and give us the output. That way we can compare your conf against what really is in the dir.
I'm sure you already know the commands, but here are they anyway.
#mount /boot
#cd /boot
#ls -la
Greetz
i tried mount /boot...nothing, i didnt set it up as a partation the only linux partations i have are an ext3 and a swap
ok this is what has happened as of late
i accidently deleted something prowling around as root and i had to reinstall *not good enough at linux to know how to repair*
so im going of a fresh install
what i was doing before was correct but i was just doing stuff in the wrong order or something
but i did install the 2.6.6 kernel and it will boot to it but when i do i get a kernel panic that their is no init found
but when i boot to linux.current *2.4.20-31.9* or linux.failsafe *2.4.20-8* it will say init V 2.84 booting
do i have to edit my init file to include the new kernel?
Like i said before, drop the init-line in your bootloader config. Its not necessary to boot, but it can break up stuff if not configed properly.
Your bootsplash will not be as pretty, but at least it'll work.
didnt work
this is the output
vfs: cannot open root device "label=/" or unknown-block (0,0)
please append a correct "root=/" boot option
kernel panic: vfs: unable to mount root fs on unknown-block (0,0)
this is my lilo.conf file
prompt
timeout=150
default=linux.good
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
lba32
image=/boot/vmlinuz-2.4.20-31.9
label=linux.good
initrd=/boot/initrd-2.4.20-31.9.img
read-only
append="hdc=ide-scsi hde=ide-scsi root=LABEL=/"
image=/boot/vmlinuz-2.6.6
label=linux.testing
read-only
append="hdc=ide-scsi hde=ide-scsi root=LABEL=/"
image=/boot/vmlinuz-2.4.20-8
label=linux.failsafe
initrd=/boot/initrd-2.4.20-8.img
read-only
append="hdc=ide-scsi hde=ide-scsi root=LABEL=/"
other=/dev/hdb1
optional
label=XPHome
table=/dev/hdb
map-drive = 0x80
to = 0x81
map-drive = 0x81
to = 0x80