Date: Mon, 27 Jun 2005 18:49:23 -0400 From: Mike Meyer <mwm@mired.org> To: hackers@freebsd.org Subject: /boot/loader bug? Message-ID: <17088.33395.356858.72172@bhuda.mired.org>
next in thread | raw e-mail | index | archive | help
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? Thanks, <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17088.33395.356858.72172>