I get the bktr device usurping its own cdevsw[] as well - I was
told it was "most likely" benign, so I've been waiting for
others' comments.
I also get the keyboard problem periodically, and I've been
trying to isolate just what I do to cause it. Generally, if I
reboot and don't hit a key before
CD-RW, test write
acd0: Audio: play, 128 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: no/blank disc inside, unlocked, lock protected
changing root device to wd0s1a
changing root device to wd0a
--- Soren Schmidt <[EMAIL PROTECTED]> wrote:
> It seems Geoff Rehmet wrote:
> &
r
the primary slave stays on as well, but goes off on the first
access to the primary master (which does -not- fail).
--- Kevin Street <[EMAIL PROTECTED]> wrote:
> Brian McGroarty <[EMAIL PROTECTED]> writes:
>
> > In using the ATA driver, I'm unable to automatically
In using the ATA driver, I'm unable to automatically mount a
partition on a master drive on the secondary controller. fsck
complains that device rwd2s1e isn't configured and exists.
Immediately mounting by hand works perfectly.
Compiling the kernel with wd instead of ata eliminates the
problem.
FWIW - I enabled APM over the weekend, configuring drives to
spin down when not used for a good period of time. I get the
message you list below, alternately with status 50 and 58, any
time a drive needs to spin up.
Myself, I'm curious about why the access light stays on on just
one of the three
