_____
Hanif,
Quote:> Now I have a couple of Intel Pro/10 nics (I have tried 3com 509,
> EtherExpress 16,) for my 486 DX2 66, 16Mb RAM, 814Mb HD. One day I would
> like to have OBSD on it...
> Anyhow... the GENERIC file (which I am assuming is used for the floppy
> kernel???) uses irq 5 and port 0x320 for the ex0 interface.
> I downloaded a DOS utility from Intel to configure the nic. I was able to
> programe the card with the above irq and io address. Alas, the install
> process still does not recognise the card.
> I do not see any relevant message during the boot process and when
> configuring the network, no interface is detected.
> I have also tried installing FBSD 4.1 and I get a conflict with the pcic0
> device (this is apparently the PC-Controller card). I know this is not the
> FBSD group. But can someone elaborate on this.
> Any tips to overcome the above would be appreciated.
> Maybe I should try the 2.8 snapshot floppy...
_____
I can't comment on the FBSD question.
This kind of problem comes up a lot more than it should with OpenBSD.
You most likely have some address/irq conflicts with these cards and
your particular hardware. This card was already supported on the
earlier releases, including 2.6. I don't have experience with the ISA
bus Intel EtherExpress PRO/10, only ISA NE2000 clones. But the parallel
may be the same. I had address conflicts with the NEs and with trial
and error established that 0x300 was not useable. Unfortunately, in
your case the kernel recognises only one Intel card at the address/irq
value stated in the GENERIC file. The long way around would be to get
another OBSD 2.7 box working, compile additional address/irq
combinations for the Intel card and recreate the installation floppy.
Then you would determine which address/irq pair works. Of course, you
need to have a single NIC in the system to begin with. For use as a
firewall, you will be installing the second card, and that one must not
conflict either. Your DOS setup utility should detect conflicts when
both cards are plugged in and that might help a bit.
One final thought: boot from the floppy with "boot -c", and enter UKC
mode. Then disable a whole bunch of ports with "disable port 0x300",
"disable port 0x280" and so on. Even do "disable port 0x320" (your card
in question), and also say "disable isapnp". Now do "enable ex0" to
turn your card back on. Then quit. With any luck, the system will boot
and see your card ??
GENERIC file from 2.6 release
<snip>
ec0 at isa? port 0x250 iomem 0xd8000 irq 9 # 3C503 ethernet
ne0 at isa? port 0x240 irq 9 # NE[12]000 ethernet
ne1 at isa? port 0x300 irq 10 # NE[12]000 ethernet
ne2 at isa? port 0x280 irq 9 # NE[12]000 ethernet
ne* at isapnp? # NE[12]000 PnP ethernet
eg0 at isa? port 0x310 irq 5 # 3C505/Etherlink+
ethernet
el0 at isa? port 0x300 irq 9 # 3C501 ethernet
ep0 at isa? port ? irq ? # 3C509 ethernet
ep* at isapnp? # 3C509 PnP ethernet
ep* at isa? port ? irq ? # 3C509 ethernet
ef* at isapnp? # 3C515 PnP ethernet
ie0 at isa? port 0x360 iomem 0xd0000 irq 7 # StarLAN and 3C507
ie1 at isa? port 0x300 irq 10 # EtherExpress
le0 at isa? port 0x360 irq 15 drq 6 # IsoLan, NE2100, and
DEPCA
ex0 at isa? port 0x320 irq 5 # Intel EtherExpress
PRO/10
ep0 at eisa? slot
?
<snip>
Regards / John
-
Contrex Consulting 1117 Clarke Road
Tel: +1(250)544-0857 Brentwood Bay, BC
Fax: +1(250)544-0896 V8M 1E2, CANADA
Message prepared: 10:53, 26/10/2000
by