Date: Fri, 5 Jun 1998 08:24:45 -0700 (PDT) From: Bryan Mann <bmann@whistle.com> To: freebsd-small@FreeBSD.ORG Subject: P-n-P Message-ID: <Pine.BSI.3.95.980605080657.4745A-100000@chaco.whistle.com>
next in thread | raw e-mail | index | archive | help
Hello all, Issue: I'd like to be able to hand people a couple of picoBSD floppies with a Java capable browser, possibly a trimmed communicator, have them install it on on their DOS/Win3.1 machines and just work similar to some Linux distributions. The goal is to demonstrate how much power their old machine has when using a better OS. Question: How hard is it to get the boot process to do a brute force analysis of a system of unknown IRQs put together a working config and boot successfully without user intervention? Here is the situation that brings this to the fore: So yesterday I installed 2.2.6 on some hardware of unknown origin. It consists of a P75, IDE controller with unknown harddrive, floppy, unknown NIC card, unknown video adapter, and 16MB of main memory. The reason these are unknown is that the controllers weren't name brand and in the case of the NIC card it was inherited from some other "functioning system". The plan was to use the distribution sitting on a local ftp server to do the install. All kernel device probes detected the hardware fine. Problem occurred when the install actually wanted to use the NIC. It timed out because the kernel used the wrong IRQ(5). After several re-attempts setting the IRQ for the NIC by hand each time IRQ 9 worked. Can anyone steer me to a solution or is anyone already working on this problem? Bryan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.95.980605080657.4745A-100000>