Navigation

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

    X-6000 watchguard and USB Tenda 311U Wireless Adapter

    Hardware
    3
    10
    4341
    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.
    • F
      fastcon68 last edited by

      I have connected a USB Tenda 311U wireless adapter to my x-6000.  I don't see it under interfaces.  Now while doing some research I thought that I have bought one that would be supported by PFsense.

      I have down loaded and review the start up log file from the x-6000.  Here it is, and does any see that it might be tring to load the driver but it is not fully starting?

      Copyright © 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.1-RELEASE-p4 #0: Wed Jun  1 19:17:08 EDT 2011
          sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386 i386
      Timecounter "i8254" frequency 1193182 Hz quality 0
      CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2800.11-MHz 686-class CPU)
        Origin = "GenuineIntel"  Id = 0xf29  Family = f  Model = 2  Stepping = 9
        Features=0xbfebfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>Features2=0x4400 <cnxt-id,xtpr>real memory  = 536870912 (512 MB)
      avail memory = 506286080 (482 MB)
      ACPI Error: A valid RSDP was not found (20100331/tbxfroot-309)
      MPTable: <oem00000 prod00000000="">ioapic0: Assuming intbase of 0
      ioapic1: Assuming intbase of 24
      ioapic0 <version 2.0="">irqs 0-23 on motherboard
      ioapic1 <version 2.0="">irqs 24-47 on motherboard
      wlan: mac acl policy registered
      ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
      ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
      module_register_init: MOD_LOAD (ipw_bss_fw, 0xc0708980, 0) error 1
      ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
      ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
      module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc0708a20, 0) error 1
      wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.
      wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/loader.conf.
      module_register_init: MOD_LOAD (wpi_fw, 0xc087b840, 0) error 1
      ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
      ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
      module_register_init: MOD_LOAD (ipw_monitor_fw, 0xc0708ac0, 0) error 1
      ACPI Error: A valid RSDP was not found (20100331/tbxfroot-309)
      ACPI: Table initialisation failed: AE_NOT_FOUND
      ACPI: Try disabling either ACPI or apic support.
      cryptosoft0: <software crypto="">on motherboard
      padlock0: No ACE support.
      pcib0: <mptable host-pci="" bridge="">pcibus 0 on motherboard
      pci0: <pci bus="">on pcib0
      pcib1: <pci-pci bridge="">at device 1.0 on pci0
      pci1: <pci bus="">on pcib1
      pcib2: <mptable pci-pci="" bridge="">at device 3.0 on pci0
      pci2: <pci bus="">on pcib2
      em0: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.3="">port 0xb000-0xb01f mem 0xfd800000-0xfd81ffff,0xfd820000-0xfd83ffff irq 18 at device 1.0 on pci2
      em0: [FILTER]
      pcib3: <mptable pci-pci="" bridge="">at device 28.0 on pci0
      pci3: <pci bus="">on pcib3
      pci3: <encrypt decrypt,="" network="" computer="" crypto="">at device 13.0 (no driver attached)
      em1: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.3="">port 0xc000-0xc03f mem 0xfd9e0000-0xfd9fffff,0xfd900000-0xfd93ffff irq 26 at device 14.0 on pci3
      em1: [FILTER]
      em2: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.3="">port 0xc100-0xc13f mem 0xfd9c0000-0xfd9dffff,0xfd940000-0xfd97ffff irq 27 at device 14.1 on pci3
      em2: [FILTER]
      uhci0: <uhci (generic)="" usb="" controller="">port 0xe100-0xe11f irq 16 at device 29.0 on pci0
      uhci0: [ITHREAD]
      usbus0: <uhci (generic)="" usb="" controller="">on uhci0
      uhci1: <uhci (generic)="" usb="" controller="">port 0xe000-0xe01f irq 19 at device 29.1 on pci0
      uhci1: [ITHREAD]
      usbus1: <uhci (generic)="" usb="" controller="">on uhci1
      pci0: <base peripheral=""> at device 29.4 (no driver attached)
      ehci0: <intel 6300esb="" usb="" 2.0="" controller="">mem 0xfdc00000-0xfdc003ff irq 23 at device 29.7 on pci0
      ehci0: [ITHREAD]
      usbus2: EHCI version 1.0
      usbus2: <intel 6300esb="" usb="" 2.0="" controller="">on ehci0
      pcib4: <mptable pci-pci="" bridge="">at device 30.0 on pci0
      pci4: <pci bus="">on pcib4
      fxp0: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0xd000-0xd03f mem 0xfdbe0000-0xfdbe0fff,0xfdb00000-0xfdb1ffff irq 19 at device 9.0 on pci4
      miibus0: <mii bus="">on fxp0
      inphy0: <i82555 10="" 100="" media="" interface="">PHY 1 on miibus0
      inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
      fxp0: [ITHREAD]
      fxp1: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0xd100-0xd13f mem 0xfdbe4000-0xfdbe4fff,0xfdb20000-0xfdb3ffff irq 18 at device 10.0 on pci4
      miibus1: <mii bus="">on fxp1
      inphy1: <i82555 10="" 100="" media="" interface="">PHY 1 on miibus1
      inphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
      fxp1: [ITHREAD]
      fxp2: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0xd200-0xd23f mem 0xfdbe2000-0xfdbe2fff,0xfdb40000-0xfdb5ffff irq 17 at device 11.0 on pci4
      miibus2: <mii bus="">on fxp2
      inphy2: <i82555 10="" 100="" media="" interface="">PHY 1 on miibus2
      inphy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
      fxp2: [ITHREAD]
      fxp3: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0xd300-0xd33f mem 0xfdbe6000-0xfdbe6fff,0xfdb60000-0xfdb7ffff irq 16 at device 12.0 on pci4
      miibus3: <mii bus="">on fxp3
      inphy3: <i82555 10="" 100="" media="" interface="">PHY 1 on miibus3
      inphy3:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
      fxp3: [ITHREAD]
      fxp4: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0xd400-0xd43f mem 0xfdbe1000-0xfdbe1fff,0xfdb80000-0xfdb9ffff irq 19 at device 13.0 on pci4
      miibus4: <mii bus="">on fxp4
      inphy4: <i82555 10="" 100="" media="" interface="">PHY 1 on miibus4
      inphy4:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
      fxp4: [ITHREAD]
      fxp5: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0xd500-0xd53f mem 0xfdbe3000-0xfdbe3fff,0xfdba0000-0xfdbbffff irq 18 at device 14.0 on pci4
      miibus5: <mii bus="">on fxp5
      inphy5: <i82555 10="" 100="" media="" interface="">PHY 1 on miibus5
      inphy5:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
      fxp5: [ITHREAD]
      fxp6: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0xd600-0xd63f mem 0xfdbe5000-0xfdbe5fff,0xfdbc0000-0xfdbdffff irq 17 at device 15.0 on pci4
      miibus6: <mii bus="">on fxp6
      inphy6: <i82555 10="" 100="" media="" interface="">PHY 1 on miibus6
      inphy6:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
      fxp6: [ITHREAD]
      isab0: <pci-isa bridge="">at device 31.0 on pci0
      isa0: <isa bus="">on isab0
      atapci0: <intel 6300esb="" udma100="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f 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)
      cpu0 on motherboard
      atrtc0: <at realtime="" clock="">at port 0x70-0x71 irq 8 pnpid PNP0b00 on isa0
      unknown: <pnp0c01>can't assign resources (memory)
      ppc0: <ecp parallel="" printer="" port="">at port 0x378-0x37f,0x778-0x77f irq 7 drq 3 pnpid PNP0401 on isa0
      ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
      ppc0: FIFO with 16/16/9 bytes threshold
      ppc0: [ITHREAD]
      ppbus0: <parallel port="" bus="">on ppc0
      ppi0: <parallel i="" o="">on ppbus0
      uart0: <non-standard ns8250="" class="" uart="" with="" fifos="">at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
      uart0: [FILTER]
      uart0: console (9600,n,8,1)
      uart1: <non-standard ns8250="" class="" uart="" with="" fifos="">at port 0x2f8-0x2ff irq 3 on isa0
      uart1: [FILTER]
      unknown: <pnp0c01>can't assign resources (memory)
      Timecounter "TSC" frequency 2800111124 Hz quality 800
      Timecounters tick every 10.000 msec
      IPsec: Initialized Security Association Processing.
      usbus0: 12Mbps Full Speed USB v1.0
      usbus1: 12Mbps Full Speed USB v1.0
      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
      usbus2: 480Mbps High Speed USB v2.0
      ad0: 3825MB <sandisk sdcfh-004g="" hdx="" 5.09="">at ata0-master PIO4
      ugen2.1: <intel>at usbus2
      uhub2: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus2
      Root mount waiting for: usbus2 usbus1 usbus0
      uhub0: 2 ports with 2 removable, self powered
      uhub1: 2 ports with 2 removable, self powered
      Root mount waiting for: usbus2
      uhub2: 4 ports with 4 removable, self powered
      Root mount waiting for: usbus2
      ugen2.2: <ralink>at usbus2
      run0: <1.0> on usbus2
      run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address c8:3a:35:c6:bc:e9
      runfw: root not mounted yet, no way to load image
      run0: failed loadfirmware of file runfw
      run0: could not load 8051 microcode
      device_attach: run0 attach returned 6
      run0: <1.0> on usbus2
      run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address c8:3a:35:c6:bc:e9
      Root mount waiting for: usbus2
      runfw: root not mounted yet, no way to load image
      run0: failed loadfirmware of file runfw
      run0: could not load 8051 microcode
      device_attach: run0 attach returned 6
      Trying to mount root from ufs:/dev/ufs/pfsense1
      WARNING: / was not properly dismounted
      WARNING: R/W mount of / denied.  Filesystem is not clean - run fsck

      This was my last boot, Any thoughts?
      RC</ralink></intel></intel></sandisk></intel></intel></intel></intel></pnp0c01></non-standard></non-standard></parallel></parallel></ecp></pnp0c01></at></serial></ata></ata></intel></isa></pci-isa></i82555></mii></intel></i82555></mii></intel></i82555></mii></intel></i82555></mii></intel></i82555></mii></intel></i82555></mii></intel></i82555></mii></intel></pci></mptable></intel></intel></uhci></uhci></uhci></uhci></intel(r)></intel(r)></encrypt></pci></mptable></intel(r)></pci></mptable></pci></pci-pci></pci></mptable></software></version></version></oem00000></cnxt-id,xtpr></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>

      1 Reply Last reply Reply Quote 0
      • stephenw10
        stephenw10 Netgate Administrator last edited by

        Just like it says:

        run0: failed loadfirmware of file runfw
        run0: could not load 8051 microcode

        It can't upload the firmware to the adapter which it needs to run.

        Steve

        Edit:

        @Wallabybob:

        Add the line:

        runfw_load="YES"

        to /boot/loader.conf.local to get the firmware loaded at boot time.

        1 Reply Last reply Reply Quote 0
        • F
          fastcon68 last edited by

          I modified the boot.conf now my device will not start at all.  I trying to figure out how I can recover it without rebuilding it.  Can anyone base on the conversations list give me a idea what the boot.conf should look like.

          My plan is to ghost the flash drive then using ghost explorer mount the disk and put the right boot file in place.

          Help!!

          1 Reply Last reply Reply Quote 0
          • stephenw10
            stephenw10 Netgate Administrator last edited by

            boot.conf or /boot/loader.conf?

            Are you running a nanobsd install? In which case you could just switch to the other slice.

            You could try booting a live bsd cd and then mounting the drive.

            Steve

            1 Reply Last reply Reply Quote 0
            • F
              fastcon68 last edited by

              TO All:
              Here is where I have recovered to:

              FreeBSD/i386 boot
              Default: 0:ad(0,a)runfw_load="YES"
              boot: No runfw_load="YES"

              FreeBSD/i386 boot
              Default: 0:ad(0,a)runfw_load="YES"
              boot: 1No 1

              FreeBSD/i386 boot
              Default: 0:ad(0,a)1
              boot: rebootNo reboot

              FreeBSD/i386 boot
              Default: 0:ad(0,a)reboot
              boot: ?. .. .snap COPYRIGHT bin boot boot.config cf conf conf.default dev etc home kernels lib libexec media mnt proc rescue root sbin scripts test_php.php tmp usr var nanobuild nano

              FreeBSD/i386 boot

              What to I do to get it back up and running?
              RC

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

                @fastcon68:

                I modified the boot.conf now my device will not start at all.  I trying to figure out how I can recover it without rebuilding it.  Can anyone base on the conversations list give me a idea what the boot.conf should look like.

                I have no boot.conf anywhere in the file system of my pfSense 2.0 so I have no idea of what you have done to your system.

                I suspect you will have to rebuild your system. If you do this on a new flash card you may be able to recover the configuration file from your existing flash card.

                1 Reply Last reply Reply Quote 0
                • F
                  fastcon68 last edited by

                  I modified the wrong file.  the boot.conf is located in root of the boot volume.  it contains a -h in it and that is all.  I flashed my card and started over completely.  It is working fantastic and the wireless is even working.

                  I have gotten all of the following complete:
                  1.  LCD driver - installed
                  2.  Boot.loader - modified to support usb wireless adapter
                  3.  Wireless Access Point set up and configured.

                  Remaining task:
                  1.  ARM light to green
                  2.  Work on Bridging of ports and DHCP support

                  I have a question about DHCP setting, do I set the IP address on the bridge or the one of the ports in the bridge?

                  I am planning to stay on the version from today.  I not going to upgrade until I get my hard drive in.  It took 4 + hours to get working but I am back up and running.  PFSense is the only way to go.  I have look at a lot of different products and tested a bunch but this is the only way to go.
                  RC

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

                    Glad you have it working.

                    @fastcon68:

                    I have a question about DHCP setting, do I set the IP address on the bridge or the one of the ports in the bridge?

                    Bridge.

                    1 Reply Last reply Reply Quote 0
                    • F
                      fastcon68 last edited by

                      I got a question, I planning to order new fans, to quite the x6000 down.  i been debating painting my x6000.  How is that going change the thermal properties.  I want to do a nice crinkle black finish, and leave text in red & white.  Then put a nice pfsense logo on top and front.  I worried that the paint could change the thermal properties.

                      I am adding a HD and may add a wireless internally.  i am worried about heat.
                      RC

                      1 Reply Last reply Reply Quote 0
                      • stephenw10
                        stephenw10 Netgate Administrator last edited by

                        Changing the colour will have virtually no effect on the thermal properties of the case. However if you paint it black it will radiate heat better so, in theory, it might run slightly cooler. I'd be very surprised if you could measure a difference though. It will also absorb radiated heat better so don't put it in direct sunlight!  ;)

                        You're worried about the HD producing heat or being damaged by heat?

                        You may want to consider swapping the CPU for something less power hungry if you are going to swap out the fans. In my own testing I found the original fans move so much air that the cpu heatsink was barely getting warm. You may also consider running the existing fans slower rather than replacing them.

                        Steve

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post

                        Products

                        • Platform Overview
                        • TNSR
                        • pfSense
                        • Appliances

                        Services

                        • Training
                        • Professional Services

                        Support

                        • Subscription Plans
                        • Contact Support
                        • Product Lifecycle
                        • Documentation

                        News

                        • Media Coverage
                        • Press
                        • Events

                        Resources

                        • Blog
                        • FAQ
                        • Find a Partner
                        • Resource Library
                        • Security Information

                        Company

                        • About Us
                        • Careers
                        • Partners
                        • Contact Us
                        • Legal
                        Our Mission

                        We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

                        Subscribe to our Newsletter

                        Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

                        © 2021 Rubicon Communications, LLC | Privacy Policy