Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Netgear GA511 (Based on RTL8169)

    Scheduled Pinned Locked Moved Hardware
    6 Posts 2 Posters 3.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K
      KWolf
      last edited by

      I can't for the life of me get it working in pfSense 1.2.3 or 2.0.  It doesn't show up as an available interface.  The GA511 is a cardbus card based on the supported RTL8169 chip that should use the "re" driver.  Anyone have any ideas?

      1 Reply Last reply Reply Quote 0
      • W
        wallabybob
        last edited by

        With the card plugged into the system, issue  the shell command pciconf -l and post the output as a reply. This will show what PCI (and cardbus) devices the system thinks are connected.

        1 Reply Last reply Reply Quote 0
        • K
          KWolf
          last edited by

          Thanks for the reply.  Here is the output of the aforementioned command.  I don't see any mention of the card in here, but I may be missing it.

          $ pciconf -l
hostb0@pci0:0:0:0:	class=0x060000 card=0x006a1025 chip=0x25908086 rev=0x03 hdr=0x00
vgapci0@pci0:0:2:0:	class=0x030000 card=0x006a1025 chip=0x25928086 rev=0x03 hdr=0x00
vgapci1@pci0:0:2:1:	class=0x038000 card=0x006a1025 chip=0x27928086 rev=0x03 hdr=0x00
uhci0@pci0:0:29:0:	class=0x0c0300 card=0x006a1025 chip=0x26588086 rev=0x03 hdr=0x00
uhci1@pci0:0:29:1:	class=0x0c0300 card=0x006a1025 chip=0x26598086 rev=0x03 hdr=0x00
uhci2@pci0:0:29:2:	class=0x0c0300 card=0x006a1025 chip=0x265a8086 rev=0x03 hdr=0x00
uhci3@pci0:0:29:3:	class=0x0c0300 card=0x006a1025 chip=0x265b8086 rev=0x03 hdr=0x00
ehci0@pci0:0:29:7:	class=0x0c0320 card=0x006a1025 chip=0x265c8086 rev=0x03 hdr=0x00
pcib1@pci0:0:30:0:	class=0x060401 card=0x006a1025 chip=0x24488086 rev=0xd3 hdr=0x01
none0@pci0:0:30:2:	class=0x040100 card=0x006a1025 chip=0x266e8086 rev=0x03 hdr=0x00
none1@pci0:0:30:3:	class=0x070300 card=0x006a1025 chip=0x266d8086 rev=0x03 hdr=0x00
isab0@pci0:0:31:0:	class=0x060100 card=0x006a1025 chip=0x26418086 rev=0x03 hdr=0x00
atapci0@pci0:0:31:1:	class=0x01018a card=0x006a1025 chip=0x266f8086 rev=0x03 hdr=0x00
none2@pci0:0:31:3:	class=0x0c0500 card=0x006a1025 chip=0x266a8086 rev=0x03 hdr=0x00
ath0@pci0:6:5:0:	class=0x020000 card=0x04181468 chip=0x001a168c rev=0x01 hdr=0x00
rl0@pci0:6:7:0:	class=0x020000 card=0x006a1025 chip=0x813910ec rev=0x10 hdr=0x00
cbb0@pci0:6:9:0:	class=0x060700 card=0x006a1025 chip=0x14101524 rev=0x01 hdr=0x02

          On boot up this appears in dmesg, also if I remove the card it appears upon re-insertion.  I think this may be part of the issue.

          cbb0: Warning: Bus reset timeout
          1 Reply Last reply Reply Quote 0
          • W
            wallabybob
            last edited by

            The CPU can't see any devices downstream of the cardbus bridge.

            Over the years I've had to do a number of tweaks to FreeBSD the cardbus bridge driver to support particular systems. My impressions is that there isn't any well established convention for the BIOS initialising cardbus bridges and so the FreeBSD driver cardbus bridge driver doesn't always work with "supported" bridges in particular systems because the BIOS on these systems leave the bridges is a different state that that expected by the FreeBSD driver. It doesn't help that FreeBSD seems much more commonly used on servers than laptops and servers generally don't have card cardbus slots.

            You'll probably get further with purchasing a supported USB NIC for that particular system.

            1 Reply Last reply Reply Quote 0
            • K
              KWolf
              last edited by

              My general guess is that it's not waiting long enough for the card to initialize after the reset, which can probably be fixed with the change of a number in the code.  My quick googling tells me the FreeBSD driver waits 1.1 seconds, which is about 1 second shorter than the time it takes for the lights to flash and then turn solid in Windows / Linux.  Alas, I have no idea how to do that and this guy's USB ports are shot (partially why it has been relegated to router duty) so I'll just run IPCop on it for now.

              Thanks for the help!

              Since this appears to be a problem with FreeBSD and I can't get the card to work on the actual FreeBSD release either, I'll see if I can't file some type of bug report or do some further T/S on why this isn't working over at their forum.

              (I did try asking for help on IRC in the freebsdhelp channel, but they banned me.  I guess they really don't like laptops!)

              1 Reply Last reply Reply Quote 0
              • W
                wallabybob
                last edited by

                @KWolf:

                Since this appears to be a problem with FreeBSD and I can't get the card to work on the actual FreeBSD release either, I'll see if I can't file some type of bug report

                You can file FreeBSD bug reports at http://www.freebsd.org/send-pr.html

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.