Date: Thu, 25 May 2000 13:38:20 -0400 (EDT) From: mi@privatelabs.com To: Jim Weeks <jim@siteplus.net> Cc: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>, freebsd-stable@FreeBSD.ORG Subject: Re: ad0 drivers revisited Message-ID: <200005251738.NAA04349@misha.privatelabs.com> In-Reply-To: <Pine.BSF.4.21.0005251122160.536-100000@veager.siteplus.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25 May, Jim Weeks wrote: = = > In message <392C1D76.45133616@3-cities.com>, Kent Stewart writes: = > = > The sysctl code in rc IMO needs to be executed earlier. If one is = > having problems reading from an ATA boot disk, e.g. cannot load init = > or rc, these modes need to be set earlier. Why not a boot flag that = > sets atamodes to be as conservative as possible, that could be set = > in loader.conf. I see in the loader(8) man page that some sysctl = > variables can be set in loader.conf. Can atamodes be set in = > loader.conf? If not, maybe it should. = = Yes, this is it in a nutshell. All of the suggestions so far are good, = but they come to late in the boot sequence to fix this problem. May be, it is time to make PIO the default until the later sysctl switches it to dma? Or are there drives that will freak in PIO mode? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005251738.NAA04349>