Installing drivers for Realtek RTL8169 Cardbus (PCMCIA)



  • I have bought a cardbus STLab Cardbus LAN card with a Realtek RTL8169 chip, but it isn't discovered by pfSense when installing. I have the drivers on CD, have put them on an USB pen drive, mounted this drive, and trying "make clean modules". The make command is not available.

    I need some advice for installing this driver.

    Here is the readme file coming with the linux driver:

     <linux device="" driver="" for="" realtek="" ethernet="" controllers="">This is the Linux device driver released for RealTek Ethernet controllers, which are listed as following.
    	1\. RTL8169S/SB/SC (Gigabit Ethernet with PCI interface)
    	2\. RTL8168B (Gigabit Ethernet with PCI-Express interface)
    	3\. RTL8101E (Fast Ethernet with PCI-Express interface)
    
     <requirements>- kernel source tree (supported versions 2.4.x or 2.6.x)
      - compiler/binutils for kernel compilation
    
     <quick install="" with="" proper="" kernel="" settings="">Unpack the tarball :
    	tar vzxf r1000_vX.YZ.tgz
    
      Change to the directory:
    	cd r1000_vX.YZ
    
      If you are running the target kernel, then you should be
      able to do :
    
    	make clean modules	(as root or with sudo)
    	make install
    	depmod -a
    
     <force link="" status="">1\. Force the link status when insert the driver.
    	If the user is in the path ~/r1000, the link status can be forced to one of the 5 modes as following command.
    
    	#insmod ./src/r1000.ko speed=SPEED_MODE duplex=DUPLEX_MODE autoneg=NWAY_OPTION
    
    	,where
    		SPEED_MODE	= 1000	for 1000Mbps
    				= 100	for 100Mbps
    				= 10	for 10Mbps
    		DUPLEX_MODE	= 0	for half-duplex
    				= 1	for full-duplex
    		NWAY_OPTION	= 0	for auto-negotiation off
    				= 1	for auto-negotiation on
    	For example:
    	#insmod ./src/r1000.ko speed=100 duplex=0 autoneg=0
    	will force PHY to operate in 100Mpbs Half-duplex.
    
    2\. Force the link status by using ethtool.
    	a. Insert the driver first.
    	b. Make sure that ethtool exists in /sbin.
    	c. Force the link status as the following command.
    
    	#ethtool -s eth? speed SPEED_MODE duplex DUPLEX_MODE autoneg NWAY_OPTION
    
    	,where
    		SPEED_MODE	= 1000	for 1000Mbps
    				= 100	for 100Mbps
    				= 10	for 10Mbps
    		DUPLEX_MODE	= half	for half-duplex
    				= full	for full-duplex
    		NWAY_OPTION	= off	for auto-negotiation off
    				= on	for auto-negotiation on
    
     <advanced feature="">- Supports Jumbo Frame
      - Hardware Tx/Rx flow control</advanced></force></quick></requirements></linux> 
    


  • The pfSense image doesn't come with the tool-chain needed to build applications/modules/drivers.

    Maybe you could download a matching version of FreeBSD, build the module there, and then move it over to the pfSense image.

    I'm not sure if the image has all the pieces needed to support PCMIA cards though, so even with the driver, you still may be out of luck.

    Cheers.



  • @EddieA:

    Maybe you could download a matching version of FreeBSD, build the module there, and then move it over to the pfSense image.
    I'm not sure if the image has all the pieces needed to support PCMIA cards though, so even with the driver, you still may be out of luck.

    In case anyone can guide me, or even help me, I have put the drivers available (from the driver CD) here:
    Linux driver for Gigabit Realtek RTL8169 Cardbus/PCMCIA (18k)

    I will let the driver be available for some time from that link.



  • @paalgg:

    Linux driver for Gigabit Realtek RTL8169 Cardbus/PCMCIA

    pfSense is based on FreeBSD, not Linux.  From what I can see, the emulation that allows Linux drivers to run on FreeBsd only works for USB devices.  But, I could be wrong about that.

    But, the RTL8169 chip is supported by the re driver, which is included in pfSense, because that's what my box is using for it's WAN interface.

    If it isn't recognised, then maybe my other thought is correct, that the PCMCIA support isn't present.  Or, you need a PCMCIA aware driver, not the PCI one you referenced.

    Cheers.



  • Please post the output of the dmesg shell command so we can see if the cardbus bridge is correctly initialised.

    It seems that some systems don't have a BIOS that correctly initialises the cardbus bridge for use with FreeBSD.


  • Rebel Alliance Developer Netgate

    The output of "usbdevs" and "pciconf -lv" may also help.

    The re(4) driver is for PCI and PCIe cards, not USB, so it's possible that support for that chip via USB doesn't exist in FreeBSD, at least FreeBSD 7/8.

    Here is the list I see for RealTek on FreeBSD 8:

    re(4)                    - RealTek 8139C+/8169/816xS/811xS/8101E PCI/PCIe Ethernet adapter driver
    rl(4)                    - RealTek 8129/8139 Fast Ethernet device driver
    rue(4)                  - RealTek RTL8150 USB to Fast Ethernet controller driver
    urtw(4)                  - Realtek RTL8187B/L USB IEEE 802.11b/g wireless network device



  • @wallabybob:

    Please post the output of the dmesg shell command so we can see if the cardbus bridge is correctly initialised.

    Here is the output of dmesg (the bus must be cbb0?):

    Copyright (c) 1992-2010 The FreeBSD Project.
    Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
    	The Regents of the University of California. All rights reserved.
    FreeBSD is a registered trademark of The FreeBSD Foundation.
    FreeBSD 8.0-STABLE #0: Thu Feb 11 22:50:50 EST 2010
        sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense.8 i386
    Timecounter "i8254" frequency 1193182 Hz quality 0
    CPU: Intel(R) Pentium(R) M processor 1.73GHz (1729.18-MHz 686-class CPU)
      Origin = "GenuineIntel"  Id = 0x6d8  Stepping = 8
      Features=0xafe9fbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,tm,pbe>Features2=0x180 <est,tm2>AMD Features=0x100000 <nx>real memory  = 1073741824 (1024 MB)
    avail memory = 1022488576 (975 MB)
    ACPI APIC Table: <intel  alviso ="">ioapic0: Changing APIC ID to 1
    ioapic0 <version 2.0="">irqs 0-23 on motherboard
    wlan: mac acl policy registered
    kbd1 at kbdmux0
    cryptosoft0: <software crypto="">on motherboard
    padlock0: No ACE support.
    acpi0: <ptltd  rsdt="">on motherboard
    acpi0: [ITHREAD]
    acpi0: Power Button (fixed)
    Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
    acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
    acpi_ec0: <embedded controller:="" gpe="" 0x17="">port 0x62,0x66 on acpi0
    acpi_lid0: <control method="" lid="" switch="">on acpi0
    acpi_button0: <sleep button="">on acpi0
    pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
    pci0: <acpi pci="" bus="">on pcib0
    vgapci0: <vga-compatible display="">port 0x1800-0x1807 mem 0xb0080000-0xb00fffff,0xc0000000-0xcfffffff,0xb0000000-0xb003ffff irq 16 at device 2.0 on pci0
    agp0: <intel 82915gm="" (915gm="" gmch)="" svga="" controller="">on vgapci0
    agp0: detected 7932k stolen memory
    agp0: aperture size is 256M
    vgapci1: <vga-compatible display="">at device 2.1 on pci0
    uhci0: <intel 82801fb="" fr="" fw="" frw="" (ich6)="" usb="" controller="" usb-a="">port 0x1820-0x183f irq 23 at device 29.0 on pci0
    uhci0: [ITHREAD]
    usbus0: <intel 82801fb="" fr="" fw="" frw="" (ich6)="" usb="" controller="" usb-a="">on uhci0
    uhci1: <intel 82801fb="" fr="" fw="" frw="" (ich6)="" usb="" controller="" usb-b="">port 0x1840-0x185f irq 17 at device 29.1 on pci0
    uhci1: [ITHREAD]
    usbus1: <intel 82801fb="" fr="" fw="" frw="" (ich6)="" usb="" controller="" usb-b="">on uhci1
    uhci2: <intel 82801fb="" fr="" fw="" frw="" (ich6)="" usb="" controller="" usb-c="">port 0x1860-0x187f irq 18 at device 29.2 on pci0
    uhci2: [ITHREAD]
    usbus2: <intel 82801fb="" fr="" fw="" frw="" (ich6)="" usb="" controller="" usb-c="">on uhci2
    uhci3: <intel 82801fb="" fr="" fw="" frw="" (ich6)="" usb="" controller="" usb-d="">port 0x1880-0x189f irq 19 at device 29.3 on pci0
    uhci3: [ITHREAD]
    usbus3: <intel 82801fb="" fr="" fw="" frw="" (ich6)="" usb="" controller="" usb-d="">on uhci3
    ehci0: <intel 82801fb="" (ich6)="" usb="" 2.0="" controller="">mem 0xb0040000-0xb00403ff irq 23 at device 29.7 on pci0
    ehci0: [ITHREAD]
    usbus4: EHCI version 1.0
    usbus4: <intel 82801fb="" (ich6)="" usb="" 2.0="" controller="">on ehci0
    pcib1: <acpi pci-pci="" bridge="">at device 30.0 on pci0
    pci6: <acpi pci="" bus="">on pcib1
    iwi0: <intel(r) pro="" wireless="" 2200bg="">mem 0xb0100000-0xb0100fff irq 21 at device 5.0 on pci6
    iwi0: [ITHREAD]
    rl0: <realtek 10="" 8139="" 100basetx="">port 0x3000-0x30ff mem 0xb0101000-0xb01010ff irq 20 at device 7.0 on pci6
    miibus0: <mii bus="">on rl0
    rlphy0: <realtek internal="" media="" interface="">PHY 0 on miibus0
    rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    rl0: [ITHREAD]
    cbb0: <ene cb1410="" pci-cardbus="" bridge="">at device 9.0 on pci6
    cardbus0: <cardbus bus="">on cbb0
    pccard0: <16-bit PCCard bus> on cbb0
    cbb0: [FILTER]
    pci0: <multimedia, audio="">at device 30.2 (no driver attached)
    pci0: <simple comms,="" generic="" modem="">at device 30.3 (no driver attached)
    isab0: <pci-isa bridge="">at device 31.0 on pci0
    isa0: <isa bus="">on isab0
    atapci0: <intel ich6="" udma100="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1810-0x181f irq 16 at device 31.1 on pci0
    ata0: <ata 0="" channel="">on atapci0
    ata0: [ITHREAD]
    ata1: <ata 1="" channel="">on atapci0
    ata1: [ITHREAD]
    pci0: <serial bus,="" smbus="">at device 31.3 (no driver attached)
    acpi_tz0: <thermal zone="">on acpi0
    acpi_tz1: <thermal zone="">on acpi0
    atrtc0: <at realtime="" clock="">port 0x70-0x77 irq 8 on acpi0
    atkbdc0: <keyboard controller="" (i8042)="">port 0x60,0x64 irq 1 on acpi0
    atkbd0: <at keyboard="">irq 1 on atkbdc0
    kbd0 at atkbd0
    atkbd0: [GIANT-LOCKED]
    atkbd0: [ITHREAD]
    psm0: <ps 2="" mouse="">irq 12 on atkbdc0
    psm0: [GIANT-LOCKED]
    psm0: [ITHREAD]
    psm0: model Generic PS/2 mouse, device ID 0
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    battery0: <acpi control="" method="" battery="">on acpi0
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    acpi_ec0: EcRead: failed waiting to get data
    ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531
    ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    ACPI Error (uteval-0329): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc46b79e0), AE_NO_HARDWARE_RESPONSE
    acpi_acad0: <ac adapter="">on acpi0
    cpu0: <acpi cpu="">on acpi0
    est0: <enhanced speedstep="" frequency="" control="">on cpu0
    p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
    pmtimer0 on isa0
    orm0: <isa option="" roms="">at iomem 0xcf800-0xd07ff,0xdc000-0xdffff,0xe0000-0xe3fff pnpid ORM0000 on isa0
    sc0: <system console="">at flags 0x100 on isa0
    sc0: VGA <16 virtual consoles, flags=0x300>
    vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
    ppc0: parallel port not found.
    Timecounter "TSC" frequency 1729184935 Hz quality 800
    Timecounters tick every 1.000 msec
    IPsec: Initialized Security Association Processing.
    usbus0: 12Mbps Full Speed USB v1.0
    usbus1: 12Mbps Full Speed USB v1.0
    usbus2: 12Mbps Full Speed USB v1.0
    usbus3: 12Mbps Full Speed USB v1.0
    usbus4: 480Mbps High Speed USB v2.0
    ad0: 19077MB <ic25n020atcs04 0="" ca2oa71a="">at ata0-master UDMA100 
    ugen0.1: <intel>at usbus0
    uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
    ugen1.1: <intel>at usbus1
    uhub1: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus1
    ugen2.1: <intel>at usbus2
    uhub2: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus2
    ugen3.1: <intel>at usbus3
    uhub3: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus3
    ugen4.1: <intel>at usbus4
    uhub4: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus4
    acd0: DVDR <hl-dt-st dvd-rw="" gwa-4082n="" cp03="">at ata0-slave UDMA33 
    Root mount waiting for: cbb0 usbus4 usbus3 usbus2 usbus1 usbus0
    uhub0: 2 ports with 2 removable, self powered
    uhub1: 2 ports with 2 removable, self powered
    uhub2: 2 ports with 2 removable, self powered
    uhub3: 2 ports with 2 removable, self powered
    cbb0: Warning: Bus reset timeout
    Root mount waiting for: usbus4
    Root mount waiting for: usbus4
    uhub4: 8 ports with 8 removable, self powered
    Trying to mount root from ufs:/dev/ad0s1a
    pflog0: promiscuous mode enabled
    rl0: link state changed to UP
    ugen4.2: <kingston>at usbus4
    umass0: <kingston 0="" 2="" datatraveler2.0,="" class="" 0,="" rev="" 2.00="" 2.00,="" addr="">on usbus4
    umass0:  SCSI over Bulk-Only; quirks = 0x0000
    umass0:0:0:-1: Attached to scbus0
    (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 
    (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
    (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
    (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
    (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed
    (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
    da0 at umass-sim0 bus 0 scbus0 target 0 lun 0
    da0: <kingston datatraveler2.0="" 4.70="">Removable Direct Access SCSI-0 device 
    da0: 40.000MB/s transfers
    da0: 243MB (499200 512 byte sectors: 64H 32S/T 243C)
    ugen4.2: <kingston>at usbus4 (disconnected)
    umass0: at uhub4, port 8, addr 2 (disconnected)
    (da0:umass-sim0:0:0:0): lost device
    (da0:umass-sim0:0:0:0): removing device entry
    ugen4.2: <kingston>at usbus4
    umass0: <kingston 0="" 2="" datatraveler2.0,="" class="" 0,="" rev="" 2.00="" 2.00,="" addr="">on usbus4
    umass0:  SCSI over Bulk-Only; quirks = 0x0000
    umass0:0:0:-1: Attached to scbus0
    (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 
    (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
    (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
    (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
    (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed
    (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
    da0 at umass-sim0 bus 0 scbus0 target 0 lun 0
    da0: <kingston datatraveler2.0="" 4.70="">Removable Direct Access SCSI-0 device 
    da0: 40.000MB/s transfers
    da0: 243MB (499200 512 byte sectors: 64H 32S/T 243C)
    ugen4.2: <kingston>at usbus4 (disconnected)
    umass0: at uhub4, port 7, addr 2 (disconnected)
    (da0:umass-sim0:0:0:0): lost device
    (da0:umass-sim0:0:0:0): removing device entry
    ugen4.2: <kingston>at usbus4
    umass0: <kingston 0="" 2="" datatraveler2.0,="" class="" 0,="" rev="" 2.00="" 2.00,="" addr="">on usbus4
    umass0:  SCSI over Bulk-Only; quirks = 0x0000
    umass0:0:0:-1: Attached to scbus0
    (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 
    (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
    (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
    (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
    (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed
    (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
    da0 at umass-sim0 bus 0 scbus0 target 0 lun 0
    da0: <kingston datatraveler2.0="" 4.70="">Removable Direct Access SCSI-0 device 
    da0: 40.000MB/s transfers
    da0: 243MB (499200 512 byte sectors: 64H 32S/T 243C)</kingston></kingston></kingston></kingston></kingston></kingston></kingston></kingston></kingston></kingston></kingston></hl-dt-st></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></ic25n020atcs04></generic></system></isa></cpu></enhanced></acpi></ac></acpi></ps></at></keyboard></at></thermal></thermal></serial></ata></ata></intel></isa></pci-isa></simple></multimedia,></cardbus></ene></realtek></mii></realtek></intel(r)></acpi></acpi></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></vga-compatible></intel></vga-compatible></acpi></acpi></sleep></control></embedded></ptltd ></software></version></intel ></nx></est,tm2></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,tm,pbe> 
    

    The output of "usbdevs" and "pciconf -lv" may also help.
    The re(4) driver is for PCI and PCIe cards, not USB, so it's possible that support for that chip via USB doesn't exist in FreeBSD, at least FreeBSD 7/8.

    Please note that the card I am using is PCMCIA/Cardbus. The command usbdevs did not exists, here is the output of pciconf -lv:

    hostb0@pci0:0:0:0:	class=0x060000 card=0x006a1025 chip=0x25908086 rev=0x03 hdr=0x00
        class      = bridge
        subclass   = HOST-PCI
    vgapci0@pci0:0:2:0:	class=0x030000 card=0x006a1025 chip=0x25928086 rev=0x03 hdr=0x00
        class      = display
        subclass   = VGA
    vgapci1@pci0:0:2:1:	class=0x038000 card=0x006a1025 chip=0x27928086 rev=0x03 hdr=0x00
        class      = display
    uhci0@pci0:0:29:0:	class=0x0c0300 card=0x006a1025 chip=0x26588086 rev=0x03 hdr=0x00
        class      = serial bus
        subclass   = USB
    uhci1@pci0:0:29:1:	class=0x0c0300 card=0x006a1025 chip=0x26598086 rev=0x03 hdr=0x00
        class      = serial bus
        subclass   = USB
    uhci2@pci0:0:29:2:	class=0x0c0300 card=0x006a1025 chip=0x265a8086 rev=0x03 hdr=0x00
        class      = serial bus
        subclass   = USB
    uhci3@pci0:0:29:3:	class=0x0c0300 card=0x006a1025 chip=0x265b8086 rev=0x03 hdr=0x00
        class      = serial bus
        subclass   = USB
    ehci0@pci0:0:29:7:	class=0x0c0320 card=0x006a1025 chip=0x265c8086 rev=0x03 hdr=0x00
        class      = serial bus
        subclass   = USB
    pcib1@pci0:0:30:0:	class=0x060401 card=0x006a1025 chip=0x24488086 rev=0xd3 hdr=0x01
        class      = bridge
        subclass   = PCI-PCI
    none0@pci0:0:30:2:	class=0x040100 card=0x006a1025 chip=0x266e8086 rev=0x03 hdr=0x00
        class      = multimedia
        subclass   = audio
    none1@pci0:0:30:3:	class=0x070300 card=0x006a1025 chip=0x266d8086 rev=0x03 hdr=0x00
        class      = simple comms
        subclass   = generic modem
    isab0@pci0:0:31:0:	class=0x060100 card=0x006a1025 chip=0x26418086 rev=0x03 hdr=0x00
        class      = bridge
        subclass   = PCI-ISA
    atapci0@pci0:0:31:1:	class=0x01018a card=0x006a1025 chip=0x266f8086 rev=0x03 hdr=0x00
        class      = mass storage
        subclass   = ATA
    none2@pci0:0:31:3:	class=0x0c0500 card=0x006a1025 chip=0x266a8086 rev=0x03 hdr=0x00
        class      = serial bus
        subclass   = SMBus
    iwi0@pci0:6:5:0:	class=0x028000 card=0x27018086 chip=0x42208086 rev=0x05 hdr=0x00
        class      = network
    rl0@pci0:6:7:0:	class=0x020000 card=0x006a1025 chip=0x813910ec rev=0x10 hdr=0x00
        class      = network
        subclass   = ethernet
    cbb0@pci0:6:9:0:	class=0x060700 card=0x006a1025 chip=0x14101524 rev=0x01 hdr=0x02
        class      = bridge
        subclass   = PCI-CardBus
    
    


  • Neither the dbus output nor the pciconf output show any devices downstream of the cardbus bridge. Either your device is not fully engaged in the socket (and therefore its not visible to the hardware) or the cardbus bridge is not correctly initialised by the BIOS for FreeBSD or the bridge is broken or your card is broken. You should do some experiments to eliminate some of these possibilities.

    I have come across some systems where the cardbus bridge is not correctly initialised by the BIOS for operation with FreeBSD and FreeBSD has not seen cardbus devices but other operating systems have seen cardbus devices on the same hardware. FreeBSD seems to be more commonly used on servers (which typically don't have cardbus devices) than on laptops (which do commonly have cardbus slots) and hence the cardbus support in FreeBSD probably doesn't get as much of a workout as it needs.

    An alternative to the cardbus NIC might be a USB NIC. I don't know of any USB gigabit NICs but there are 10/100 USB ethernet NICs that have 480Mbps USB speed and are supported in FreeBSD. Warning: Many of the cheap 10/100 USB ethernet NICs have only 12Mbps USB speed (which is more than enough for some circumstances).


Log in to reply