Date: Thu, 11 May 2000 08:22:53 +0200 From: Erik Trulsson <ertr1013@student.csd.uu.se> To: Mark Johnston <mark.johnston@home.com> Cc: Conrad Sabatier <conrads@home.com>, questions@FreeBSD.ORG Subject: Re: 4.0-RELEASE installation: can't see my hard drive Message-ID: <20000511082253.A1289@student.csd.uu.se> In-Reply-To: <006301bfbb0b$187023e0$79646c18@burows1.mb.wave.home.com>; from mark.johnston@home.com on Thu, May 11, 2000 at 12:38:11AM -0500 References: <XFMail.000510202622.conrads@home.com> <006301bfbb0b$187023e0$79646c18@burows1.mb.wave.home.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 11, 2000 at 12:38:11AM -0500, Mark Johnston wrote: > From: "Conrad Sabatier" <conrads@home.com> > To: "Mark Johnston" <mark.johnston@home.com> > Sent: Wednesday, May 10, 2000 8:26 PM > > > > > > On 10-May-00 Mark Johnston wrote: > > > I'm having trouble installing 4.0-RELEASE - I get through the bootup and > > > kernel setup, but the "Probing..." screen hangs for about 10-15 minutes. > > > The installation screen comes up after that, but when I try to start > > > setup, > > > it tells me that no hard drives are found. The kernel options I have > > > enabled are: > (long info cut) > > > The debug console shows some > > > errors about timeouts waiting to send commands to ata0-master and read > > > timeouts on ad0 - it also says that the device has disappeared. > > > > > > This system has run Win95 and Linux, and both found the hard drive > > > without any trouble - I've also booted the OpenBSD install floppy, > > > which found the HD OK. Where am I going wrong? > > > > Sorry, not an answer, just a "me too" here. > > > > I was trying to install FreeBSD 4.0 from CD on a friend's machine and saw > > pretty much the same behavior. Try as we might, we just could not figure > > out a workaround. Baffling, really. > > > > Hmm.. do you know what kind of onboard IDE he has? I've done some checking > around, trying to figure out the problem, and noticed that my IDE > controller - a SiS 5513 - was shown in OpenBSD's dev logs as having had its > support "recently fixed". I'm not sure if this means something in terms of > FreeBSD's support for it, but I also noticed that while booting Linux, the > system says "not 100% native mode, DMA disabled." I'm thinking that FBSD > may not know that DMA may cause problems and might use it anyway - I'm going > to make my BIOS settings really conservative, maybe rearrange my drives or > disconnect the CD-ROM. I think it's safe to rule out oft-blamed Cyrix in > the problem - I'm using an Intel P166. > I have got that controller too. And no, it is not working quite as well as it should be under 4.0. (While it works fine under 3.4) (Something that might be related to the problem is that FBSD (mis)detects it as a SiS 5591 controller. I think SiS reused the chip-id from the 5513 when they made the 5591 but I don't know if they are actually 100% compatible.) I have got it working fine but that involved using the 'wd' driver instead of the default new 'ata' driver. (And a small hack in the source to persuade it not to try to use UDMA.) I did get it to work with the 'ata' driver too by rearranging the disks a bit but that meant no DMA on my big, fast disk :-( A tip that might (or might not) work. Put some disk that is *not* UDMA capable as primary master, and the CDROM on the secondary controller. (something like that worked for me.) (No, I haven't sent in a PR yet. I intend to do so (with a more detailed bug report) RSN.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000511082253.A1289>