It seems Andrew Gallatin wrote:
> > It seems that the 0xa5 value means "no device" too, on lots of
> > controllers, and its not valid anyways, so it wouldn't hurt..."
>
> That works! The pause is gone and the reboot time is more than cut in
> half. I urge you to commit this ;-)
I will, its
Soren Schmidt writes:
> > ata1: mask=03 status0=a5 status1=a5
> > <..30+ seconds>
> > ata1: mask=00 status0=ffa5 status1=ffa5
>
> Hmm, you could try to change the probe to something like:
> ...
> status1 = inb(scp->ioaddr + ATA_STATUS);
> if ((status0 & 0xf8) != 0xf8 &&
It seems Andrew Gallatin wrote:
> Is there any way to tell the driver not to reduce the timeout to
> something less than 31s? Or would it be easier for me to just #if 0
> the lun1 (iobase_2..) code in ata_pciattach()?
>
> I'm asking because we have about 20 boxes like this. All of which are
> "
Soren Schmidt [[EMAIL PROTECTED]] wrote:
> It seems Dan Langille wrote:
> > I have one box which is slow to boot under -current (mind you, I've never
<...>
> BUT if the second channel is enabled in the BIOS and the hardware plays
> foul on probe, it will be probed for devices for the std timeout
On 14 Feb 00, at 13:51, Soren Schmidt wrote:
> It seems Dan Langille wrote:
> > I have one box which is slow to boot under -current (mind you, I've never
> > run anything but -current on this box). In my previous message, there
> > were two excessively long pauses. One after ata0 appears and an
It seems Dan Langille wrote:
> I have one box which is slow to boot under -current (mind you, I've never
> run anything but -current on this box). In my previous message, there
> were two excessively long pauses. One after ata0 appears and another
> after ata-isa0 appears. I've been able to
On 7 Feb 00, at 18:12, Dan Langille wrote:
> I have one box which is slow to boot under -current (mind you, I've never
> run anything but -current on this box). There are two pauses. One after
> ata0 appears and another after ata-isa0 appears.
I'm reposting this as there has been no response
On 14 Feb 00, at 11:15, Soren Schmidt wrote:
> It seems Dan Langille wrote:
> > On 14 Feb 00, at 22:02, Dan Langille wrote:
> >
> > > On 7 Feb 00, at 18:12, Dan Langille wrote:
> > >
> > > > I have one box which is slow to boot under -current (mind you, I've
> > > > never run anything but -curr
It seems Dan Langille wrote:
> On 14 Feb 00, at 22:02, Dan Langille wrote:
>
> > On 7 Feb 00, at 18:12, Dan Langille wrote:
> >
> > > I have one box which is slow to boot under -current (mind you, I've never
> > > run anything but -current on this box). There are two pauses. One after
> > > at
On 14 Feb 00, at 22:02, Dan Langille wrote:
> On 7 Feb 00, at 18:12, Dan Langille wrote:
>
> > I have one box which is slow to boot under -current (mind you, I've never
> > run anything but -current on this box). There are two pauses. One after
> > ata0 appears and another after ata-isa0 appea
On 7 Feb 00, at 18:12, Dan Langille wrote:
> I have one box which is slow to boot under -current (mind you, I've never
> run anything but -current on this box). There are two pauses. One after
> ata0 appears and another after ata-isa0 appears.
I'm reposting this as there has been no response a
11 matches
Mail list logo
