Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
i've tried with slackware, gentoo, and debian. i always get errors when trying to boot to hdb2. even when i put hdb as my primary with grub or lilo on the MBR there. with grub i get error 17, with lilo i just get L 99 99 99 .... etc. i tried putting hdb into a friends computer and booting it, and it worked fine! i even tried flashing my BIOS and all sorts of things. none of them worked. what's going on here?? why wont it work? i tried removing my hard ware to just the bare minimum and booting and i still got the error. =/
by the way there doesnt ever appear to be anything wrong with my linux itself. i used slackware for about a year just fine, but i had to boot from the slack install disk every time because of these problems i described above.
my hd's are fine. there is an option for reinstalling grub, but i've tried those. i've tried it for slackware, gentoo, and debian so far. here's a copy of my menu.lst:
Code:
default 0
timeout 5
color cyan/blue white/blue
title Linux
root (hd1,1)
kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hdb2 ro
initrd /boot/initrd.img-2.4.27-2-386
savedefault
boot
when i looked at it at first it was saying "root (hd0,1)" and "root=/dev/hda2" but i changed those to teh values above and it still doesnt work right. =/
I think it is because the MBR doesn't point to where grub is. You will need to rebuild the MBR, and maybe grub, too. If Slackware/Gentoo (Debian doesn't) has a 'Repair MBR' option on the boot CD, use it. If not, use a live CD. I'd reccommend UBCD .
This is probably caused by you moving the boot partition, or changing it's number. If you can (from a live CD or Partition Magic) easily undo the partition operations, that might fix it, but you probably can't just move it back to where it was before.
i used the windows xp recovery console and "fixmbr" and "fixboot" on both my hard drives. is that the same as rebuilding my mbr? in any case, it never worked. after grub kept erroring, i tried lilo. it loaded fine without errors, but when i select Linux, it says "EBDA is big; kernel setup stack overlaps lilo second stage." when i select windows from the lilo list, however, it loads fine. somewhere along the line i had used a boot floppy to load linux. i used the slack boot disk to load debian and it loaded fine. the only problem was the kernel mismatch. =/
not sure if this would help or if you have done so already,
have you checked to make sure lilo and/or grub are pointing to correct kernel image? i'm pretty sure i got a similiar error when i misspelled something and had grub pointing to a kernel that didn't exist
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.