Date: Tue, 24 Dec 1996 22:33:15 +0100 (MET) From: J Wunsch <j@uriah.heep.sax.de> To: mishania@demos.su Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: 2.1.6/boot.flp/EISA Message-ID: <199612242133.WAA13516@uriah.heep.sax.de> In-Reply-To: <199612241913.WAA20078@megillah.demos.su> from "Mikhail A. Sokolov" at "Dec 24, 96 10:13:42 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
As Mikhail A. Sokolov wrote: > taking a look at god *(&^% NetServer LC (HP) we notice that it's full of EISA > slot's and EISA'ish itself. Correct me if I am wrong, but why doesn't > boot.flp kernel contain controller eisa0 line ? j@uriah 195% cvs co -rRELENG_2_1_6_1_RELEASE -d. src/sys/i386/conf/GENERIC U ./GENERIC j@uriah 196% fgrep eisa GENERIC controller eisa0 It does. Your problem is another. FreeBSD 2.1.5R was the first release that indeed shipped with EISA code enabled (2.1R had it disabled and buggy). However, the EISA per slot memory for slots >= 10 conflicts with the PCI address range, therefore the device probing is limited to slots 0 through 9. Unfortunately, the on-board AHA2740 in the EISA Netservers is at slot # 11. If you can bootstrap your system with another controller, you can work around this by changing the #define in sys/i386/eisa/eisaconf.h, and rebuilding your kernel. I've found a hack to allow bootstrapping a 2.2 system, it's already in the new BETA which is about to be announced every minute now. There you can tell ``eisa 12'' in the command-line UserConfig screen, to extend the number of slots to be probed. This allows you installing the system, so you could continue as described above. All this is described in the (updated) FAQ, topic 3.16. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612242133.WAA13516>