From: Nicholas Kirchner <kirc0...@umn.edu>

> Try using PCINIC [0] from David Dunfield [1] to figure out where the
> second NIC is on the bus.
Tried this, and it gave me the I/O address like I needed (thanks!). Now
I have the following conundrum:

Running
`pcnpkt int=0x60` works with the first network card, and outputs a line
"Interrupt number 0xa (10)".  DHCP works.
Rebooting, then running
`pcnpkt int=0x60 ioaddr=0xd020` seems to work in that pcnpkt doesn't
error, but I get the output "Interrupt number 0x (0)", and then DHCP
fails to communicate.
Rebooting again, then running
`pcnpkt int=0x60 ioaddr=0xd020 irq=(irq #)` fails for all values of irq
# from 1 to 15 and 0x1 to 0xf with the error "PCI device IRQ number
mismatch."  (The irq value reported by pcinic for this card is 10)

Is there something easy I'm missing (other than picking out another
network card in VirtualBox  :-D )?  Right now I'm suspecting a bug, and
looking at the pcntpk source to figure out why it doesn't capture the
right irq when given an ioaddr.

--Nick

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99)

---
 * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to