On Monday 27 June 2005 06:49 pm, Mike Meyer wrote: > As reported here (I hope - the moderator got the message) and in > -questions, I have a motherboard that installs just fine, but gets a > "Can't work out which disk we are booting fromm" message when the > installed os boots. > > Hacking boot/i386/loader/main.c to wire the proper values into > new_currdev fixed the problem. At this point, I'm considering filing a > bug report - but I'm not sure where the bug is. > > Is this a /boot/loader bug, and it should have known what was going > on? Is this a BIOS bug, in that it reported the wrong thing to > /boot/loader? Is it a bug in one of the earlier boot stages? > > Anyone got any opinions on this? Any suggestions for things to look at > to determine what component is actually buggy?
Your BIOS most likely. The output of 'lsdev' from your loader prompt might be helpful though. Also, what did you have to wire new_currdev to? -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
