Bit frustrated by lack of support, still for power management even in the patched kernel .. so grabbed a 2.5.75 kernel ..and also a 2.6.0test4 kernel from kernel.org .. compiled ok and installed to grub loader .. .. root=LABEL=/
That doesn't look like the right syntax to me root=LABEL is fine, if you've set a label on the partition already. the extra =/ looks wrong tho
but it won't mount root and hangs at this point. I tried changing root to /dev/hda2 .. which is
So you tried "root=/dev/hda2" ? Also, the full grub entry should look something like: title Debian GNU/Linux, kernel 2.4.22-pre7-smp-1 (recovery mode) root (hd0,0) kernel /vmlinuz-2.4.22-pre7-smp-1 root=/dev/hda3 ro single Does the 'root (hd0,0)' entry in your grub config point at the correct partition? hd0,0 == first harddisk, first partition. hd0,2 == first harddisk, third partition
where I put linux (hda0 is the dell maintainance partition and hda1 is xp .. yes got it to load and even recompiled to get ntfs support .. successfully)
I'm not 100% sure, but I suspect that there is no such thing as hda0. Partitions start from hda1. So if you have the Dell maintenance partition ,and then the XP partition, then linux should be on hda3? Note that the (hd0,0) notation is different to the /dev/hda1 notation. Just to confuse you Now, the wonderful thing about grub, is that you can edit its configuration at boot time. Instead of booting with one of the boot options, you can hit c or e, I forget which, to change the boot entry. You can change any line, so you can tweak the partition number and so on, and it will boot with those changes that time only. Also, grub understands linux filesystems, so you can do tab completion on kernel names
I presume this is some arcane problem with LVM .. any ideas .. next step might be to start from scratch and get rid of LVM.
That might also work, but its possible there is any easier fix :). I've not used LVM, but I'd have thought it resulted in a different partition name (ie, not /dev/hda2...) ? Daniel