RE: port-i386/46247: 6.0 Beta boot fails on generic i386 architecture machine

["John Refling" <netbsdrat%gmail.com@localhost>]

I had a look at the boot console using the command you mentioned
and nothing was unusual:

File system:         /dev/wd0a
Boot options:        timeout 5, flags 0, speed 9600, ioaddr 0, console pc

I also hooked up an rs-232 cable and terminal to com0 to see if anything
was output.  It was silent.

Also, hooked up the HDD LED and there was absolutely no disk activity
after:

 NetBSD MBR boot
 NetBSD/x86 ffsv2 Primary Bootstrap
 [silence]

I'm wondering if bootstrap being confused by the SATA channels (which have
no disks).  Maybe starting off with the PATA interface (where the disk is)
then thinking to use the SATA later in the boot process ???

John Refling


-----Original Message-----
From: David Laight [mailto:david%l8s.co.uk@localhost] 
Sent: Friday, March 23, 2012 1:00 AM
To: port-i386-maintainer%netbsd.org@localhost; gnats-admin%netbsd.org@localhost;
netbsd-bugs%netbsd.org@localhost; netbsdrat%gmail.com@localhost
Subject: Re: port-i386/46247: 6.0 Beta boot fails on generic i386
architecture machine

The following reply was made to PR port-i386/46247; it has been noted by
GNATS.

From: David Laight <david%l8s.co.uk@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: port-i386/46247: 6.0 Beta boot fails on generic i386
architecture machine
Date: Fri, 23 Mar 2012 07:52:38 +0000

 On Fri, Mar 23, 2012 at 12:15:00AM +0000, netbsdrat%gmail.com@localhost wrote:
 > >Number:         46247
 > >Category:       port-i386
 > >Synopsis:       6.0 Beta boot fails on generic i386 architecture machine
 ...
 > I installed 6.0 beta on a rather generic i386 machine:
 > 
 > p4m800pro-m v2.0 by ECS
 > 
 >
http://www.ecsusa.com/ECSWebSite/Product/Product_Detail.aspx?DetailID=673&Ca
tegoryID=1&DetailName=Feature&MenuID=16&LanID=9
 > 
 > and the install went OK, but it would not successfully boot from hard
disk, halting after:
 > 
 > NetBSD MBR boot
 > NetBSD/x86 ffsv2 Primary Bootstrap
 > [silence]
 > 
 > The install complained once that the disk geometry could not be uniquely
matched:
 > Bios: 1024/16/63
 > Prob: 1023/255/63
 
 If it got as far as showing the ffs2 message then the chs values won't
matter.
 
 I had an issue booting via grub where the console was getting set to
 com0 instead pc by default.
 
 Try booting from the install cd, and exit to shell (^C will do).
 Then run 'installboot -e -v wd0' to look at the options, and maybe
 force the console with '-o console-pc'.
 (Commands from memory).
 You might need to mount the root fs and chroot into it.
 
        David
 
 -- 
 David Laight: david%l8s.co.uk@localhost