Subject: Re: satalink(4): trouble detecting harddisk if booting "too fast"
To: None <tech-kern@NetBSD.org>
From: Manuel Bouyer <bouyer@antioche.lip6.fr>
List: tech-kern
Date: 04/10/2004 20:57:33
On Fri, Apr 09, 2004 at 11:45:52PM +0200, Thomas Klausner wrote:
> Hi!
> 
> I am using a Samsung harddisk on a satalink(4) controller
> on a 2.0C/i386; it's plugged into the second port.
> 
> Recently I added another Samsung hard disk in the primary port.
> Now, when booting, I have to wait 10-15s in the GRUB boot loader
> screen and the NetBSD boot loader screen (combined) before allowing
> the kernel to boot, otherwise NetBSD only detects the hard disk
> in the second port.
> 
> Any ideas what could be causing this? Is this a bug in satalink?
> Or does the hard disk in the primary port just need longer to
> spin up? Are there any debugging flags I could try to find out more?

Yes, you can try to set wdcdebug_mask and wdcdebug_wd_mask to 0x10

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--