![](https://seccdn.libravatar.org/avatar/3cbac7dcf1f56f37fafd539ab1534b4b.jpg?s=120&d=mm&r=g)
Hi Dave, On Fri, Mar 27, 1998 at 20:51 -0500, dedwards@technologist.com wrote:
On 26 Mar, Hubert Mantel wrote:
Hi,
On Tue, 24 Mar 1998 dedwards@technologist.com wrote:
[...]
hdb: probing with STATUS instead of ALTSTATUS hdb: probing with STATUS instead of ALTSTATUS
Is this bad?? - what can I do to get rid of these messages??
AFAIK this is just a workaround for some old harddrives. Do you have ancient Seagate drives? I think it's just informational and should not cause any problems.
Dave E.
Hubert
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
No, Actually, what I *did* have was a Maxtor 2.1g drive on the first onboard EIDE controller, with my 24x CDRom drive as a slave (which skips on audio tracks - but thats another question :->). I re-compiled my kernel to take advantage of my 2nd onboard EIDE controller, set my CDRom up as a Master and put it onto the @nd controller. The CDRom works, the Maxtor 2.1g drive works, but now I get the above messages - looks like the boot is expecting something in the slave position of the 1st controller (/dev/hdb) which *used* to be my CDRom. Maybe there is some unusual (for me anyways) setting I have failed to make or unset.
I've just had a look at an installation guide of my old Maxtor HD. It says there are three possible settings for the Master/Slave configuration: 1) Only drive in single drive system 2) Master in dual drive system 3) Slave in dual drive system. Could it be that your HD uses similar settings and is set to (2)? If so, you might try setting it to (1). Ciao Stefan -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e