Date: Sun, 22 Nov 2009 21:09:01 -0500 From: Zaphod Beeblebrox <zbeeble@gmail.com> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.x hang-on-boot on Dell 1950 Message-ID: <5f67a8c40911221809h25253009od8a83d058f68ad9c@mail.gmail.com> In-Reply-To: <20091114024438.GA93630@icarus.home.lan> References: <5f67a8c40911121246m144ba07w707a1c268fb2102c@mail.gmail.com> <4AFD6D69.7090109@thekeelecentre.com> <5f67a8c40911131757s48a57d9by11c74a417324e48c@mail.gmail.com> <20091114024438.GA93630@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 13, 2009 at 9:44 PM, Jeremy Chadwick <freebsd@jdc.parodius.com>wrote: > > > This 1950 may predate that a bit, but I'm not sure how to nail it down > > exactly, other than by it's hardware components. Anyways, 7.0 does the > same > > thing --- still wedged. > > I haven't seen anyone recommend this as a test method yet -- disabling > fdc prior to the kernel booting via the loader prompt: > > - Press 6 at the menu, > - At the loader prompt, type: > > set hint.fdc.0.disabled="1" > boot -v (or without -v; your choice) > > You shouldn't need to set hint.fd.0.disabled="1", since fd0 would > normally bind to fdc0; disable the latter and you disable the lesser. > > The intention here is to rule out the device attachment failures from > fdc as the source of the deadlock. > Entertainingly, it does not. Aparently that hint doesn't stop the code from trying to attach fdc0 when acpi says so. I suppose I need to know the console command to disable acpi and fdc. but it still wedges at "device_attach: fdc0 attach returned 6" with the above.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5f67a8c40911221809h25253009od8a83d058f68ad9c>