Help on CardBus Bridge...

From: todd nguyen
Date: Tue Sep 21 2004 - 23:54:33 EST


Hello,
I have a little problem with the CardBus Bridge that
we bought recently. When Linux bootup, the OS see all
the devices after the CardBus twice. For example, we
have only 1 device called "VIS16" after the CardBus
but the the "lspci" display twice. Does anyone have
any idea why? Also, dmesg showed some conflict in the
bus segment which has the "VIS16" device. Please let
me know if you need more information.

Thanks in advance,
Todd Nguyen

===============Kernel version==========

Linux winter-lnx 2.4.21-4.0.1.EL #1 Thu Oct 23
01:36:33 EDT 2003 i686 unknown unknown GNU/Linux

================lspci=================
00:00.0 Host bridge: Intel Corp.: Unknown device 3340
(rev 03)
00:01.0 PCI bridge: Intel Corp.: Unknown device 3341
(rev 03)
00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub
#1) (rev 01)
00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub
#2) (rev 01)
00:1d.2 USB Controller: Intel Corp. 82801DB USB (Hub
#3) (rev 01)
00:1d.7 USB Controller: Intel Corp. 82801DB USB EHCI
Controller (rev 01)
00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI
Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corp.: Unknown device 24cc
(rev 01)
00:1f.1 IDE interface: Intel Corp.: Unknown device
24ca (rev 01)
00:1f.5 Multimedia audio controller: Intel Corp.
82801DB AC'97 Audio (rev 01)
01:00.0 VGA compatible controller: ATI Technologies
Inc: Unknown device 4c66 (rev 02)
02:00.0 Ethernet controller: BROADCOM Corporation:
Unknown device 165d (rev 01)
02:01.0 CardBus bridge: O2 Micro, Inc.: Unknown device
7113 (rev 20)
02:01.1 CardBus bridge: O2 Micro, Inc.: Unknown device
7113 (rev 20)
02:03.0 Network controller: BROADCOM Corporation:
Unknown device 4320 (rev 02)
03:00.0 PCI bridge: Unknown device 9902:0001 (rev 02)
03:00.1 Bridge: Unknown device 9902:0002 (rev 02)
04:00.0 PCI bridge: Unknown device 9902:0003 (rev 01)
04:00.0 PCI bridge: Unknown device 9902:0003 (rev 01)
05:01.0 PCI bridge: Unknown device 9902:0001 (rev 02)
05:01.0 PCI bridge: Unknown device 9902:0001 (rev 02)
05:02.0 PCI bridge: Unknown device 9902:0001 (rev 02)
05:02.0 PCI bridge: Unknown device 9902:0001 (rev 02)
06:0d.0 Diamond Instrument: Todd System, Corp. VIS16
(rev ad)
06:0d.0 Diamond Instrument: Todd System, Corp. VIS16
(rev ad)
06:1f.0 Bridge: Unknown device 9902:0002 (rev 02)
06:1f.0 Bridge: Unknown device 9902:0002 (rev 02)
====================================================

=================dmesg==============================
cs: cb_alloc(bus 3): vendor 0x9902, device 0x0001
Cardbus: Bridge found - we suck.
Allocating for type 101, in bus resource.
Allocating for type 200, in bus resource.
Allocating for type 1200, in bus resource.
PCI: Cannot allocate resource region 9 of bridge
03:00.0
Scanning behind PCI bridge 03:00.0, config 000000
Scanning bus 04
Fixups for bus 04
Scanning behind PCI bridge 04:00.0, config 000000
Scanning bus 05
Fixups for bus 05
Scanning behind PCI bridge 05:01.0, config 000000
Scanning bus 06
Fixups for bus 06
PCI: Failed to allocate resource 0(0-1ff) for 06:0f.0
PCI: Failed to allocate resource 1(1000-fff) for
06:0f.0
PCI: Failed to allocate resource 2(0-1fffff) for
06:0f.0
PCI: Device 06:0f.0 not available because of resource
collisions
PCI: Failed to allocate resource 0(0-7fff) for 06:1f.0
PCI: Failed to allocate resource 1(1000-fff) for
06:1f.0
PCI: Device 06:1f.0 not available because of resource
collisions
Bus scan for 06 returning with max=06
Scanning behind PCI bridge 05:02.0, config 000000
================================================




__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/