Two identical network cards in a laptop - followup

Hi,

I still haven't been able to make these two network cards work together.
I tried pccardd with debuglevel 9.
Here's what gets reported when I insert the first network card:
-------------
Nov 14 22:42:12 kg-omni2 /kernel: pccard: card inserted, slot 1
Nov 14 22:42:14 kg-omni2 pccardd[48]: Card "Billionton"("LNA-100B") [V] [1.0] matched 
"Billionton" ("LNA-100B") [(null)] [(null)] 
Nov 14 22:42:14 kg-omni2 pccardd[48]: Using I/O addr 0x300, size 32 
Nov 14 22:42:14 kg-omni2 pccardd[48]: Setting config reg at offs 0x3c0 to 0x47, Reset 
time = 50 ms 
Nov 14 22:42:19 kg-omni2 pccardd[48]: Assigning I/O window 0, start 0x300, size 0x20 
flags 0x5 
Nov 14 22:42:19 kg-omni2 pccardd[48]: Assign ed1, io 0x300-0x31f, mem 0x0, 0 bytes, 
irq 3, flags 0 
Nov 14 22:42:19 kg-omni2 /kernel: ed1 at port 0x300-0x31f irq 3 slot 1 on pccard1
Nov 14 22:42:19 kg-omni2 /kernel: ed1: address 00:10:60:f3:13:b0, type NE2000 (16 bit) 
Nov 14 22:42:19 kg-omni2 pccardd[48]: ed1: Billionton (LNA-100B) inserted.
Nov 14 22:42:25 kg-omni2 pccardd[48]: pccardd started
-----------------
So far, so good. Now, lets insert the second card:
----------------
Nov 14 22:43:01 kg-omni2 pccardd[48]: Card "Billionton"("LNA-100B") [V] [1.0] matched 
"Billionton" ("LNA-100B") [(null)] [(null)] 
Nov 14 22:43:01 kg-omni2 pccardd[48]: Using I/O addr 0x240, size 32 
Nov 14 22:43:01 kg-omni2 pccardd[48]: Setting config reg at offs 0x3c0 to 0x47, Reset 
time = 50 ms 
Nov 14 22:43:06 kg-omni2 pccardd[48]: Assigning I/O window 0, start 0x240, size 0x20 
flags 0x7 
Nov 14 22:43:06 kg-omni2 pccardd[48]: Assign ed2, io 0x240-0x25f, mem 0x0, 0 bytes, 
irq 5, flags 0 
Nov 14 22:43:06 kg-omni2 pccardd[48]: driver allocation failed for Billionton(LNA-100B): 
Device not configured
-------------------
Everything looks alright to me (except for "driver allocation failed"). How do I get pccardd
to tell me more about why the driver allocation failed?
-- 
Torfinn Ingolfsen,
Norway



To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-mobile" in the body of the message