"Matthew N. Dodd" wrote:
>
> Using the boot configuration screen can you disable all devices that are
> not installed?
>
> I suspect something is clobbering the board after it is identified.
>
> --
> | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD |
> | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL | ix86,sparc,pmax |
> | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever |
I tried that. It worked. Thanks a lot! Looks like the fe0 driver was
the
one messing it up for my ep0. Now back to the install.
Another weird thing: as you could see in the boot dump, a Seagate UDMA2
drive
has been detected. After sysinstall starts, I see the following
messages
on vty1:
ad0: ad_timeout: lost disk contact - resetting
ata0: resetting devices .. ata0-master: timeout waiting for command=ef
s=fc e=00
ata0-master: timeout waiting to give command=ef s=fc e=00
ata0-master: timeout waiting to give command=ef s=fc e=00
ad0: ad_timeout: lost disk contact - resetting
ata0: resetting devices .. ata0-master: timeout waiting for command=ef
s=fc e=00
ata0-master: timeout waiting to give command=ef s=fc e=00
ata0-master: timeout waiting to give command=ef s=fc e=00
ad0: ad_timeout: lost disk contact - resetting
ata0: resetting devices .. ata0-master: timeout waiting for command=ef
s=fc e=00
ata0-master: timeout waiting to give command=ef s=fc e=00
ata0-master: timeout waiting to give command=ef s=fc e=00
ad0: ad_timeout: lost disk contact - resetting
ata0-master: timeout waiting for command=ef s=fc e=00
ad0: ad_timeout: trying fallback to PIO mode
ata0: resetting devices .. done
and the setup continues as if nothing has happened. The drive is
configured as PIO mode 4 in the BIOS (the BIOS does not support UDMA,
the chipset apparently does). Any pointers?
Edwin Mons
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
