Hi Tom,
No, I have this same card running on a Toshiba Tecra 8100,
and it does indeed use the dc driver, and the ethernet part
of it does indeed work (I'm running Current, last updated yesterday).
The dc driver needs the miibus device configured in the kernel in order
to work correctly, and it appears as if you haven't configured
your kernel with this device- your dmesg is showing:
dc0: port 0x1000-0x107f mem
0x8400-0x84ff,0x84000100-0x8400017f irq 11 at device 0.0 on cardbus0
dc0: Ethernet address: 00:00:00:00:00:00
dc0: MII without any PHY!
while you should in fact be seeing something like:
dc0: port 0x1000-0x107f mem
0x84002000-0x840020ff,0x84002100-0x8400217f irq 11 at device 0.0 on cardbus0
dc0: Ethernet address: 2e:29:21:02:06:00
miibus0: on dc0
tdkphy0: on miibus0
tdkphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
I haven't been able to get the modem part of this to work since
October. Warner had given us some hints on how to get this working
early last year, and it actually did work up until the 'sio' code
was broken out from isa and put under sys/dev/sio/. This hadn't
really been a problem until yesterday, as I had been using an
Alcatel usb ADSL modem with the pppoa port to connect to the internet,
but yesterday's cvsup (or most likely earlier- before yesterday, I last
upgraded on 11/20/01) broke that as well- now I have no way of
connecting :-(
Warner, do you have any clues on how to get the modem half of this
card working again?
best regards,
tom
[EMAIL PROTECTED]
Tom Skoglund wrote:
> I'll try contacting him as well if I cannot find a solution "soon".
> Thanks, anyway!
>
> -Tom
>
>
> "Greg Smith" <[EMAIL PROTECTED]> wrote:
>
>
>>Tom,
>>
>>OK, but I am doubtful.
>>
>>My feeling was that dc is for some old Dec cards and related, not even
>>available in pcmcia/cardbus; and that xe was for various Xircom cards
>>and related. I think the same driver often supports 16 and 32 bit
>>cards. You might want to ask [EMAIL PROTECTED] who seems to try
>>single-handedly to keep the xe driver up to date.
>>
>>Best of luck.
>>
>>Greg
>>
>>-Original Message-
>>
>>
>>>This encoded message has been converted to an attachment.
>>>
>>>Remember that this is a cardbus card, and AFAIK it should use the dc
>>>driver. Think I actually tried the xe driver by mistake also, but I
>>>
>>have
>>
>>>not really played around with it.
>>>
>>>-Tom
>>>
>>>- Original Message -
>>>From: "Greg Smith" <[EMAIL PROTECTED]>
>>>To: "Tom Skoglund" <[EMAIL PROTECTED]>
>>>
>>>
Tom,
I'm a little surprised that card is using the dc driver instead of
>>the
>>
xe driver. I thought all the Xircom ..em56 cards used xe. Is that
>>how
>>
it was set up in pccard.conf?
Greg
-Original Message-
>Hi,
>I have been eager to get my Xircom pcmcia nic to work under
>
>>FreeBSD,
>>
and
>have been reading up on the mailing list an so on. My system is a
>
Compaq
>Armada E500 running 20020119-CURRENT. This weekend I gave it a try,
>
with
>not
>so good results I might add. I made a new kernel (I have tried many
>
this
>weekend) built on NEWCARD. I have been fooling around with all the
>different
>config files and kernel parameters I can imagine.
>
>Basically I'm trying to get the dc driver working. I have attached
>
some
>logs
>(dmesg, kldstat, sysctl, pciconf) for you to look at. When the
>
>>driver
>>
>module
>fails it also screws up my screen by dividing it in 3 and adding
>
>>som
>>
random
>"graphics", so I have to reboot to see anything again. This
>
>>behaviour
>>
is
>the
>same if I boot with the card or try to insert it runtime.
>
>What I see in the logs makes me belive it doesn't read the
>
>>registers
>>
right.
>So before I start hacking the cardbus/if_dc files can anyone see if
>
there
>is
>something else I might try?
>
>
>-Tom
>
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-mobile" in the body of the message
>
>
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
