Re: Thoshiba Tecra 8000 with 3com 3CXFE575CT

From: Psadi <freebsd_at_psam.se>
Date: Mon, 17 Oct 2005 20:56:21 +0200
Yes I had the card in while I was booting. When I start it outside and 
then connect the card it will detect and configure it correctly. This is 
what I get in the consol message while booting with boot -v

cardbus1: Resource not specified in CIS: id=14, size=80
cardbus1: Resource not specified in CIS: id=18, size=80
found-> vendor=0x10b7, dev=0x5257, revid=0x10
        bus=21, slot=0, func=0
        class=02-00-00, hdrtype=0x00, mfdev=0
        cmdreg=0x0000, statreg=0x0210, cachelnsz=8 (dwords)
        lattimer=0xa8 (5040 ns), mingnt=0x0a (2500 ns), maxlat=0x05 
(1250 ns)
        intpin=a, irq=11
        powerspec 1  supports D0 D1 D2 D3  current D0
xl0: <3Com 3c575C Fast Etherlink XL> port 0x1080-0x10ff mem 
0x88000000-0x8800007
f,0x88000080-0x880000ff irq 11 at device 0.0 on cardbus1
xl0: using port I/O
xl0: media options word: 40
xl0: found MII/AUTO
miibus0: <MII bus> on xl0
tdkphy0: <TDK 78Q2120 media interface> on miibus0
tdkphy0: OUI 0x00c039, model 0x0014, rev. 11
tdkphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
xl0: bpf attached
xl0: Ethernet address: 00:00:86:51:81:f8
xl0: [MPSAFE]
xl0: watchdog timeout
(around here I get a IP from my dhcp server)
xl0: watchdog timeout

When I disconnect the card this is shown in the consol
login: xl0: reset didn't complete
xl0: command never completed!
xl0: command never completed!
xl0: command never completed!
tdkphy0: detached
miibus0: detached
xl0: detached
Oct 17 20:53:01 laptop dhclient[540]: connection closed
Oct 17 20:53:01 laptop dhclient[540]: exiting.


/peter

M. Warner Losh skrev:

>OK.  Next step is a question.  I can't tell from your dmesg for sure,
>but it looks like you have the xl0 card inserted on boot.  Is that
>correct?  If so, I'd like to suggest an experiment.  Insert the card
>after the login: prompt has appeared.  Does it detect and configure?
>If not, then we have a global routing problem.  If so, then we have an
>interrupt issue with the TOPIC 95B chip that you have of some sort
>that we need to address.  It looks like my Topic 97 part works great,
>but I'll double check again with -current and 6.0.
>
>Warner
>
>
>  
>
Received on Mon Oct 17 2005 - 16:56:45 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:45 UTC