Bug 34487
| Summary: | FreeBSD >= 4.4 cannot boot / install on ASUS P2B-DS Motherboard | ||
|---|---|---|---|
| Product: | Documentation | Reporter: | Xavier Beaudouin <kiwi> |
| Component: | Books & Articles | Assignee: | freebsd-doc (Nobody) <doc> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Xavier Beaudouin
2002-01-31 13:50:01 UTC
On Thu, 31 Jan 2002 14:48:41 +0100, Xavier Beaudouin wrote:
> But starting with FreeBSD 4.4 or 4.5, the kernel will lock itself (waiting
> maybe for something it cannot found) just after unsuccesfull probing of ppc0
> port.
Can you use boot -v to provide more detail on exactly where the lockup
occurs?
Note the following open PRs relating to ASUS motherboards:
kern/25909
kern/28418
kern/31233
See also PR misc/33398, which suggests toggling the "Plug'n'Play OS"
option in the BIOS.
Also, PR kern/30715 suggests that a bug tickled by the use of PCI slot
#4 on P3B boards was resolved in 4.5-RELEASE.
Ciao,
Sheldon.
Le Thu, 31 Jan 2002, Sheldon Hearn a écrit : > On Thu, 31 Jan 2002 14:48:41 +0100, Xavier Beaudouin wrote: > > > But starting with FreeBSD 4.4 or 4.5, the kernel will lock itself (waiting > > maybe for something it cannot found) just after unsuccesfull probing of ppc0 > > port. > > Can you use boot -v to provide more detail on exactly where the lockup > occurs? Yes sure (using FreeBSD 4.5-RELEASE) floppies : [...] ppc0: parallel port found at 0x378 ppc0: using extended I/O range ppc0: SPP ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: <PLIP network interface> on ppbus0 bpf0: lp0 attached ed0 failed to probe at port 0x280-0x29f iomem 0xd8000 irq 10 on isa0 fe0 failed to probe at port 0x300-0x31f on isa0 ie0 failed to probe at port 0x300 iomem 0xd0000 irq 10 on isa0 lnc0 failed to probe at port 0x280 irq 10 drq 0 on isa0 cs0 failed to probe at port 0x300-0x31f on isa0 sn0 failed to probe at port 0x300-0x30f irq 10 on isa0 isa_probe_children: probing PnP devices [ Sometimes the kernel locks a this point even if PNP OS is enabled or disabled in the bios... Sometimes it continue and locks on ahc0 card just after "Waiting 15 seconds for SCIS devices to settle" ] > Note the following open PRs relating to ASUS motherboards: > > kern/25909 > kern/28418 > kern/31233 > > See also PR misc/33398, which suggests toggling the "Plug'n'Play OS" > option in the BIOS. > > Also, PR kern/30715 suggests that a bug tickled by the use of PCI slot > #4 on P3B boards was resolved in 4.5-RELEASE. Tryed what thoses PR suggests... but they didn't help me... ;( Thanks again, Don't hesitate to ask me more question and/or tests about the p2b-ds... :) /Xavier -- Xavier Beaudouin - Unix System Administrator & Projects Leader. For mail address, please check header of this mails. Spams are not accepted. Caudium: http://caudium.net/, CAMAS webmail: http://camas.caudium.net/ [ Little fortune now ] Those who don't understand UNIX are doomed to reinvent it, poorly. --Henry Spencer OK, The following might not help and it does sound stupid :) but I used to get this kind of problem with 4.4, but it wasn't related to FreeBSD. First of all, if you haven't, I suggest that you download the firmware updates. The below URL should help. It is located at the bottom of the page. http://www.asus.com.tw/download/mbdriver/slot1-440bx.htm Also have a look at the below URL, which contains some more fixes for your particular BIOS. Look for the P2B-DS Motherboard, which is somewhere down the page: http://www.abios.com/asus/asus-440bx.html Does your PNP Scan become slow, before this problem, as in, do you get time stops between the PNP Scan. But, putting this in a nutshell, I know that this problem is not related to FreeBSD, though I may be wrong. :) Regards, - Hiten Pandya - <hiten@uk.FreeBSD.org> Hi Hiten, > > OK, The following might not help and it does sound stupid :) but I used > to get this kind of problem with 4.4, but it wasn't related to FreeBSD. > > First of all, if you haven't, I suggest that you download the firmware > updates. The below URL should help. It is located at the bottom of the > page. > > http://www.asus.com.tw/download/mbdriver/slot1-440bx.htm > > Also have a look at the below URL, which contains some more fixes for > your particular BIOS. Look for the P2B-DS Motherboard, which is somewhere > down the page: > > http://www.abios.com/asus/asus-440bx.html Ok I did some hunting.... and found BIOS release 1013 that does update the Adaptec BIOS... (I was using 1012B from a previous update 3 days ago because I was suspecting something like this...). So now with BIOS 1013 the install boot disk boots and install :) Great :) > Does your PNP Scan become slow, before this problem, as in, do you > get time stops between the PNP Scan. > > But, putting this in a nutshell, I know that this problem is not > related to FreeBSD, though I may be wrong. :) > Yes you are totaly right... I just didn't notice this update :) Thanks for the support :) You are were very helpfull :) Sincerly, /Xavier -- Xavier Beaudouin - Unix System Administrator & Projects Leader. For mail address, please check header of this mails. Spams are not accepted. Caudium: http://caudium.net/, CAMAS webmail: http://camas.caudium.net/ [ Little fortune now ] Those who don't understand UNIX are doomed to reinvent it, poorly. --Henry Spencer Hi, As agreed above, by the originator, the problem/issue is resolved, and all neccessary *new* firmware updates were applied. If the originator agrees, this PR can be successfully closed, and I will take the point to document this problem in the Handbook, as my next patch to the FreeBSD-Doc list. This also suggests that we put up a "Troubleshooting" section in the installation chapter of the handbook. This goes to murray and the -doc team ;) Thanks, Regards, - Hiten Pandya - <hiten@uk.FreeBSD.org> Responsible Changed From-To: freebsd-bugs->freebsd-doc Hiten is going to come up with a Handbook / FAQ entry for this. State Changed From-To: open->closed Superseded by docs/34524. Hi ! > > As agreed above, by the originator, the problem/issue is > resolved, and all neccessary *new* firmware updates were > applied. > > If the originator agrees, this PR can be successfully closed, > and I will take the point to document this problem in the > Handbook, as my next patch to the FreeBSD-Doc list. This is ok for me, the upgrade of the SCSI bios with v1013 of the bios totaly solve this problem... > This also suggests that we put up a "Troubleshooting" section > in the installation chapter of the handbook. This goes to > murray and the -doc team ;) This is maybe a good idea... because I wasn't able to find anything about this specific motherboard problem... and a little note about upgrading the bios should help people :) Thanks again :) /Xavier -- Xavier Beaudouin - Unix System Administrator & Projects Leader. For mail address, please check header of this mails. Spams are not accepted. Caudium: http://caudium.net/, CAMAS webmail: http://camas.caudium.net/ [ Little fortune now ] Those who don't understand UNIX are doomed to reinvent it, poorly. --Henry Spencer |
