Date: Fri, 17 Jan 2003 16:17:36 -0800 From: David Schultz <dschultz@uclink.Berkeley.EDU> To: jjramsey@pobox.com Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: Possible bugs in setting UDMA speed (Re: Semirandom bug in FreeBSD's ATA querying) Message-ID: <20030118001736.GC5908@HAL9000.homeunix.com> In-Reply-To: <20030117011923.98991.qmail@web10708.mail.yahoo.com> References: <20030117011923.98991.qmail@web10708.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake James J. Ramsey <jjramsey_6x9eq42@yahoo.com>: > > The following kernel message is from a FreeBSD > > install. I captured it by pressing Scroll Lock and > > pressing the Page Up key to get to the text: > > > > ad0: 8866663634010175MB > > <?U}O|U}!~IEzA~M~!|M~1.5?!?!~!~!?!?!~!?!> > > [16955114026566160/17/63] at ata0-master PIO4 > > > > The garbage between the angle brackets should be the > > name of the hard drive [namely "QUANTUM FIREBALLP > LM20.5"] > > I've managed to figure out how to get FreeBSD to > recognize my drive correctly, and in the process, I > think I've found more-or-less what FreeBSD has been > doing wrong: ... > 1) Kept the hard drive as primary master, but changed > the CD-ROM from primary slave to secondary master. > > 2) Used an IDE cable fit for UDMA66 for the primary > master (hard disk) and used my old IDE cable, which > probably was not for ATA66 use, for the secondary > master (CD-ROM). > > Lo and behold, FreeBSD no longer was getting garbage > cylinder counts nor a garbage hard disk name; it > reported the name as "QUANTUM FIREBALLP LM20.5" just > as it should be. I did the "begin the install but > abort before committing routine" three times, and > three times, FreeBSD handled the hard drive correctly. > (This is with the 5.0-RC3 install floppies.) I have seen misbehaving CDROM drives on the same IDE channel as a hard drive cause problems even on Windows machines. I don't know enough about the IDE spec to be able to say whether there's an easy fix, but it could still be a timing issue as Bruce suggested. If you were using a 40-conductor cable, that should have been detected, and the driver should have downgraded to UDMA33. My guess is that the CDROM was the problem. Maybe you could find out by trying the old cable with the drive. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030118001736.GC5908>