dell d610 kernel 2.4.27 -> 2.6.15 transition boot problem
Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
here is /boot/grub/menu.lst excerpts for the 2.6.15 part and the WinXP part:
title Debian GNU/Linux, kernel 2.6.15
kernel /boot/vmlinuz-2.6.15 root=/dev/hda4 ro
title Microsoft Windows XP Professional
and here is /boot/grub/device.map:
Do I need to make a hd to sd transition for sata? What do I do about the WinXP boot info in menu.lst, leave it as is ?
Do I need to modify menu.lst, fstab and device.map files to get this 2.6.15 working?
then I run update-grub and reboot?
(I don't want to lose boot option to Windows if modifying Grub - this is my machine for work!)
If GRUB crashes what does one do - use a LiveCD to Boot and try to repair Grub?
for those not read top post, boots OK on 2.4.27 using /dev/hda4
message is for 2.6.15 VFS: cannot open root device sda4 on unknown-block(0,0)
kernel panic unable to mount root fs
this is after modifying following in /boot/grub and /etc/
I manage to rescue, and revert back to 2.4.27, via a Knoppix LiveCD (kernel 2.6.11) which itself sees all partitions as /dev/sdax
This is really just changing /dev/hda instances to /dev/sda ones (that's what most of my google searches show up as necessary,
modify device.map menu.lst, fstab for kernel sata support..?)
# kopt=root=/dev/sda4 ro
title Debian GNU/Linux, kernel 2.6.15
kernel /boot/vmlinuz-2.6.15 root=/dev/sda4 ro
## following will boot OK if I reset fstab "sda" back to "hda"
title Debian GNU/Linux, kernel 2.4.27-2-386
kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hda4 ro
points on above:
does kopt field need changing?
Is an initrd necessary , see the 2.4 kernel uses one.
I've checked, there is a /boot/vmlinuz-2.5.15 file there
Got it to Boot finally
hidden in .config file , following needs setting:
# CONFIG_BLK_DEV_IDE_SATA is not set
then of course in /boot/grub/menu.lst change all root=/dev/hda instances to root=/dev/sda (for the 2.6.x kernel you're booting)
also change "hda" instances in /etc/fstab to sda
(when certain versions failed to boot, I rescued via a Knoppix liveCD via which you can re-edit fstab back to hda to get the old 2.4 kernel version working (probably there's a more elegant way - sometimes I got into 2.4 console mode without having to do this). As this was 2.6.11 based this also let you see how it mounts all the partitions)
I am experiencing the same issue at the moment. I've been having it for a whle, but I was never able to fix it. So I was very happy to find out that you figured out what the actual problem is. Unfortunately I'm not as knowledgeable about my dear Debian as you seem to be. So I don't really know how to use your case to solve mine. Maybe you could help on this. My Linux partition is /dev/hdb1 mounted on /mnt/hdb1 (sda is my external HD only containing data).
0000:00:00.0 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
0000:00:00.1 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
0000:00:00.2 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
0000:00:00.3 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
0000:00:00.4 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
0000:00:00.7 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South]
0000:00:0a.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
0000:00:0b.0 USB Controller: NEC Corporation USB (rev 43)
0000:00:0b.1 USB Controller: NEC Corporation USB (rev 43)
0000:00:0b.2 USB Controller: NEC Corporation USB 2.0 (rev 04)
0000:00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
0000:00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
0000:01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev a1)