Date: Fri, 30 Apr 1999 13:26:35 +0200 (CEST) From: Soren Schmidt <sos@freebsd.dk> To: sos@freebsd.dk (Soren Schmidt) Cc: abial@webgiro.com, green@unixhelp.org, tseidmann@SIMULTAN.CH, current@FreeBSD.ORG, shocking@prth.pgs.com Subject: Re: New ATA drivers problem? (Was: New kernels won't boot) Message-ID: <199904301126.NAA08416@freebsd.dk> In-Reply-To: <199904301104.NAA08369@freebsd.dk> from Soren Schmidt at "Apr 30, 1999 1: 4:52 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
It seems Soren Schmidt wrote: > > > > As I said before, I can make some tests, but unfortunately my machine > > doesn't want to mount disks at all with the new ATA code... Please take a > > look at the message I sent about a week ago. > > Unfortunately they dont tell me much :( > > I'll have to rearrange some disks here and try to make some new installs > see if I can get the problem to appear then.. Meanwhile, could you try this patch to boot2.c and ata-disk.c and install the new bootblocks created by this and see if it works with a genuine "ad" device set. You should then use ad?? in fstab of cause. Boot directly ie like 0:ad(0,a)/kernel from the boot promt, as the /boot/loader doesn't know about "ad" devices... Another thing to try is to dump down ata-disk.c so it doesn't use either multi-sector mode or DMA, as that might confuse some disks, notably WD but also Quantum has had some marginal disks... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904301126.NAA08416>