Date: Tue, 14 Dec 1999 09:40:39 -0600 (CST) From: "M. L. Dodson" <bdodson@scms.utmb.EDU> To: Doug White <dwhite@resnet.uoregon.edu> Cc: The Utz Family <utz@serv.net>, Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE>, multimedia@FreeBSD.ORG Subject: Re: pcm0 Message-ID: <199912141540.JAA26537@histidine.utmb.edu> In-Reply-To: <Pine.BSF.4.21.9912131910360.80605-100000@resnet.uoregon.edu> References: <199912132110.PAA24080@histidine.utmb.edu> <Pine.BSF.4.21.9912131910360.80605-100000@resnet.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug White writes: > On Mon, 13 Dec 1999, M. L. Dodson wrote: > > > > > The quick and easy solution to this is to go into the BIOS and set the > > > > 'PnP OS' options to 'no' or 'other'. > > > > I've seen this quick and easy solution posted several times to > > the list. However, I have a workstation motherboard which will > > not boot with PnP OS set to 'no'. Panics during/just after > > probing the disks. > > Which panic? > > > Am I missing something here? > > That would smell like a nasty BIOS bug. > I'll have to turn it back off in the BIOS tonight when I get home and write down the panic message. I think you are very probably right: really cheap noname MB with "VX-Pro" chipset, whatever that is. Even needed a special PCI driver under Win95 when it was in my wife's machine. However, it would make a really convenient test box for, e.g., CURRENT, automated network installs, netboot testing, etc., so I would like to understand this aspect of using it with FBSD. Thanks, Bud Dodson > Doug White | FreeBSD: The Power to Serve > dwhite@resnet.uoregon.edu | www.FreeBSD.org > > -- M. L. Dodson bdodson@scms.utmb.edu 409-772-2178 FAX: 409-772-1790 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912141540.JAA26537>