Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA46 ; Wed, 27 Jan 93 19:00:08 EST Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!olivea!sgigate!sgiblab!sti!dgreen From: dgreen@sti.com (Dan R. Greening) Newsgroups: comp.unix.bsd Subject: [386BSD] BUG in 0.1/0.2: How to configure IRQ on NE1000 boards? Message-ID: <1k1oafINNrl4@smurf.sti.com> Date: 25 Jan 93 22:07:11 GMT Organization: Software Transformation, Inc. Lines: 31 NNTP-Posting-Host: jeff.sti.com I have 386BSD 0.1 running on my little 386, my initial kernel is from dist.fs-patchkit-0.2, though dist.fs works the same way. Unfortunately I cannot get it to run correctly on the NE1000 or NE2000 boards that I have tried. Each time it comes up with ne0 ethernet address xx:xx:xx:xx:xx:xx at 0x300 irq 9 on isa The xx:xx:xx:xx:xx:xx comes up with the correct number. 0x300 is right. The IRQ number is crazy because ne1000 and ne2000 boards from Novell CANNOT be set to IRQ 9. The default is IRQ 3, which is what we leave it at in every 386 we have (and we have tons). Is there a way to configure 386bsd to default to IRQ 3 for NE 1000/2000 boards? I have the bindist, and after hunting around I think that bindist doesn't come with configuration files (at least not where "man config" tells me they should be). Can you give me a way to patch the kernel to stick the NE1000/2000 at IRQ 3? Could someone actually fix this in the next release so at least the IRQ number used is feasible? (Really you *ought* to put the NEx000 at IRQ 3 address 0x300, where it is set at the factory.) As far as I'm concerned, this is a bug (and a very annoying one, at that, since you can't use the network to download the rest of your distribution). Thanks for your help. -- ____ \ /Dan Greening Software Transformation 1601 Saratoga-Sunnyvale Rd, #100 \/dgreen@sti.com (408) 973-8081 x313 Cupertino, CA 95014