Umm... Use the control device.

On Sun, 3 Dec 2000, Greywolf wrote:

> Is it just me, or does it seem odd to anyone else that a MTIOCGET call
> [working from memory; forgive me if that's off a tad] would return
> ENODEV due to missing media?  My EXB-8200 doesn't do that.
> 
> Oddly enough, too, the EXB-4200c,217 seems to be matched at attach time,
> but if I read the st code right, it is printing out "rogue" which indicates
> a quirk entry which didn't quite match, thus leaving a null quirk entry
> for the driver to work with, which means the driver will return all
> attempts to do anything as ENODEV.
> 
> I note, too, that the dmesg buffer is small enough such that if you're
> debugging a target with SD1|SD2|SD3, you lose the first half of the
> dmesg output, even into /var/run/dmesg.boot.
> 
> 				--*greywolf;
> --
> *BSD: The Final Frontier.
>