Date: Fri, 08 Dec 2000 20:42:55 -0600 From: David Syphers <dbsypher@uchicago.edu> To: current@freebsd.org Subject: problems configuring cardbus card Message-ID: <4.3.2.7.2.20001208140130.00c5e1a0@nsit-popmail.uchicago.edu>
next in thread | raw e-mail | index | archive | help
I'm running a FreeBSD 5-CURRENT snapshot from Dec. 5, and trying to
configure an AmbiCom Cardbus ethernet card (a DEC Tulip base). I've
included cardbus, pccbb, miibus, and dc in my kernel, and enabled use of
DHCP. Since I haven't tracked -current since 4.x split off from it, I had
a great deal of FM to R before I realized things like there's a file called
/boot/device.hints that's very important. Putting
hint.dc.0.at="isa"
hint.dc.0.port="0x300"
hint.dc.0.irq="10"
into /boot/device.hints made the "watchdog timeout" errors I had been
getting on boot go away, but the card still didn't work. Do I need to
specify drq or maddr, and how would I determine if 0x300 is the right
port? This may be due to the fact that it looks like my graphics card and
my ethernet card are both assigned IRQ 11 (see clip from dmesg below). But
I really have no idea how to use device.hints or even how to set up an
ethernet card under FreeBSD (I know, I should have picked something other
than cardbus on -current for my first experience), so any help would be
appreciated. Thanks!
[part of dmesg output]
pci0: <NeoMagic MagicGraph 128XD SVGA controller> at 2.0 irq 11
...
pccbb0: <TI1131 PCI-CardBus Bridge> at device 10.0 on pci0
pccbb0: PCI Memory allocated: 18020000
pci_cfgintr_unique: hard-routed to irq 11
pci_cfgintr: 0:10 INTA routed to irq 11
cardbus0: <Cardbus bus (newcard)> on pccbb0
pccbb0: WARNING: cannot attach pccard bus.
pccbb1: <TI1131 PCI-CardBus Bridge> at device 10.1 on pci0
pccbb1: PCI Memory allocated: 18021000
pci_cfgintr_unique: hard-routed to irq 11
pci_cfgintr: 0:10 INTB routed to irq 11
cardbus1: <Cardbus bus (newcard)> on pccbb1
pccbb1: WARNING: cannot attach pccard bus.
...
pccbb0: card inserted: event=0x00000009, state=30000b20
pccbb0: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44]
pccbb0: bad Vcc request. ctrl=0x0, status=0x30000b20
pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44]
pccbb0: pccbb_power: CARD_VCC_3V and CARD_VPP_VCC [11]
pccbb0: bad Vcc request. ctrl=0x33, status=0x30000b20
pccbb_power: CARD_VCC_3V and CARD_VPP_VCC [11]
TUPLE: LINKTARGET [3]: 43 49 53
Product version: 5.0
Product name: AmbiCom, Inc. | AMB8100 | Fast Ethernet CardBus PC Card | 1.00 |
Manufacturer ID: 13958100
Functions: Network Adaptor, Multi-Functioned
Function Extension: 0102
Function Extension: 0280969800
Function Extension: 0200e1f505
Function Extension: 0301
cardbus0: Opening BAR: type=IO, bar=10, len=0080
TUPLE: CONFIG_CB [7]: 03 01 00 00 00 00 ff
TUPLE: CFTABLE_ENTRY_CB [5]: 41 80 fb 00 ff
dc1: <Intel 21143 10/100BaseTX> port 0x3000-0x307f mem
0x18040000-0x1807ffff,0x18022000-0x180223ff irq 11 at device 0.0 on cardbus0
dc1: Ethernet address: 00:80:00:80:00:80
miibus0: <MII bus> on dc1
dcphy0: <Intel 21143 NWAY media interface> on miibus0
dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pccbb1: removal of nonexistant card!
Note: "dc1" used to be "dc0" before I put the lines in device.hints, but
then I got "watchdog timeout" errors.
-David Syphers
Charon@freethought.org
http://www.seektruth.org/
Cannibalism is a small price to pay for popularity.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.3.2.7.2.20001208140130.00c5e1a0>