----- Original Message ----- From: "Ian Perry" <[EMAIL PROTECTED]> To: "'Michael Mueller'" <[EMAIL PROTECTED]>; <debian-user@lists.debian.org> Sent: Friday, August 10, 2001 1:59 AM Subject: RE: dselect and hda:irq timeout
> > > > > From: Michael Mueller [mailto:[EMAIL PROTECTED] > > > > Sent: Friday, August 10, 2001 2:36 PM > > > > > > > > While dselect is installing, I get intermittent errors. The > > > > dselect process > > > > continues to completion and I seem to be able to use what has been > > > > installed. > > > > > > > > The error messages are as follows: > > > > > > > > hda: irq timeout: status = 0x0d { Busy } > > > > ide0: reset: success > > > > > > > > Any ideas on why these messages appear? > > > > > > > > I've been experimenting with loading 2.2.r3. THis is a brand > > > > new machine: > > > > Duron 700Mhz, 128Mb DRAM, 10Gb HDD, 50x CDROM, AMD > > approved Biostar > > > > Mainboard. > > > > > > > > TIA, > > > > Mike > > > > > > I had a similar message while loading from CD. I had configured the > > machine > > > with the HD as primary master, and the CD as primary slave. > > The fix was > > to > > > put the CD onto the secondary slave. > > > > > > Ian > > > > That seems to help quite a bit. The messages were greatly > > reduced, but not > > wholly eliminated. The process took much less time > > altogether, because of > > less hda timeouts I presume. > > > > HDD is hda > > CDROM is hdd > > I had to remove the master/slave/cable select jumpers from > > the two drives. > > I guess the jumpers are needed only if there is a > > primary/secondary actually > > on the IDE cable. > > > > I actually have 2 identical twin new-born machines as > > described above. I > > tried the change on the second machine. I got additional > > messages that were > > more worrisome: > > > > ide0: reset timed out; status = 0x0d > > > > and > > > > ide0: <something the drive being busy> > > > > I'll have to wait until AM to get another IDE cable to try out the > > configuration on the first machine. > > Although the bios recognising the drives should tell whether the cable is > good. I have had a troublesome drive once which was because of a noisy P/S. > Took ages to find. > > You haven't overclocked them by any chance ? > > Ian I double checked - there is no way to set CPU clk speed on Biostar M7VKB rev 1 board. It must be set by a Duron-Mainboard interaction. I'll try some kernel compiling and different cables to see if the problem pops up with something other than dselect. I also loaded and ran another distro one of the boxes with no reported problems on hda. Mike
