9 messages in org.freebsd.freebsd-questionsRe: booting from primary wd on wdc1| From | Sent On | Attachments |
|---|---|---|
| Doug White | Feb 18, 1996 9:36 pm | |
| invalid opcode | Feb 18, 1996 10:58 pm | |
| Marty Leisner | Feb 19, 1996 9:10 am | |
| Doug White | Feb 19, 1996 10:14 am | |
| Peter Stubbs | Feb 19, 1996 11:28 am | |
| Peter Stubbs | Feb 19, 1996 6:11 pm | |
| Peter Stubbs | Feb 20, 1996 2:37 pm | |
| Terry Lambert | Feb 21, 1996 10:46 am | |
| Peter Stubbs | Feb 21, 1996 11:26 am |
| Subject: | Re: booting from primary wd on wdc1 | |
|---|---|---|
| From: | Terry Lambert (ter...@lambert.org) | |
| Date: | Feb 21, 1996 10:46:01 am | |
| List: | org.freebsd.freebsd-questions | |
finds wdc0 irq 14 finds wd0 (geometry is correct) finds wdc1 irq 15 finds wd2 (geometry is correct) finds aha0 finds cd0 finds npx0 panic cannot mount / reboot in 15 sec, ....
The messages are similar if I put it on the first controler, only the second drive is wd1, not wd2. In either case at boot time it comes up with wd(1,a)/kernel, boots, but can't mount root when on wdc1. The motherboard is an ASUS PCI 486, and the CPU is an AMD DX4-100
The root is assumed to be on the first controller in the file: /sys/i386/i386/userconfig.c.
Perhaps your BIOS is (incorrectly) leaving 0x80 instead of 0x81 in the unit number.
Have you tried booting -c and changing the boot device at the config prompt so that it will modify the kernel image for subsequent attempts?
This is different than booting the floppy and specifying the device as other than the floppy at the boot prompt.
If the floppy kernel and the one on the disk do not match, you will be screwed.
It should be possible to boot from the second controler on the newer motherboards, and it can't be too unusual.
Booting requires that the BIOS drive number be correctly passed.
The motherboard BIOS is only going to know about 0x00 (A:), 0x01 (B:), 0x80 (C:), and 0x81 (D:).
You can not boot from a drive other than that.
Since the problem is that you can't mount root, I suspect you have one of those bogus BIOS that doesn't correctly set the unit number in the d register.
Terry Lambert ter...@lambert.org
--- Any opinions in this posting are my own and not those of my present or previous employers.