element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
    About the element14 Community
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      •  Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Raspberry Pi
  • Products
  • More
Raspberry Pi
Raspberry Pi Forum Wireless network conectivity
  • Blog
  • Forum
  • Documents
  • Quiz
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Raspberry Pi to participate - click to join for free!
Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
Raspberry Pi Wishlist
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 75 replies
  • Subscribers 710 subscribers
  • Views 9780 views
  • Users 0 members are here
  • raspberry
  • pi
  • wireless
Related

Wireless network conectivity

wallarug
wallarug over 14 years ago

I bought one of these about 12 mths ago: http://www.jaycar.com.au/productView.asp?ID=YN8306&keywords=high+power+wireless+n&form=KEYWORD

I downloaded the drivers from the link above then installed them on a windows computer.  How do I use these linux drivers/installers on the raspberry pi to get the wireless adaptor to work?

 

Will this work with the Raspberry Pi?

  • Sign in to reply
  • Cancel
Parents
  • e14 Contributor
    e14 Contributor over 14 years ago

    If your adaptor uses Broadcom chipset you may need to install a piece of firmware to make it work. I had a similar problem with my Linux netbook that had Ralink wifi. It booted up but said that there was no WiFi as no firmware was loaded! After much searching the solution is at http://linuxwireless.org/en/users/Drivers/b43.

     

    The B43 package installs the firmware needed to run the Broadcom chipset. As its not GPL it can't be released with any Linux package, but is able to be extracted from the Windows driver. This package is already to go, just install!

     

    I required the firmware-b43-installer package. Not sure if it's in the RasPi repositories as I haven't got mine to play with yet... :-( But the above site it fairly comprehensive!

     

    Hope it works.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • e14 Contributor
    e14 Contributor over 14 years ago in reply to e14 Contributor

    i have had issues with broadcom on various laptops using different distro's of linux, this is the best solution i have found so far. i also cant confirm at the moment if the b43 firmware is in the repositories. i will check tonight and see if it is.

     

    i cant actually try this on the R-Pi as i dont have a USB wifi adapter with the broadcom chipset.

     

    http://ubuntuforums.org/showpost.php?p=10527475&postcount=5

     

    hope this helps.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • wallarug
    wallarug over 14 years ago in reply to e14 Contributor

    Did a bit of research and found out that the RT2770F uses the same drivers as RT2780.  Also, I read the website that was posted by Neill but the RPi did not want to install firmware-b43-installer. image

    But,  From that website I think I discovered how to (attempt to) install the drivers that came with the device.  When I tried:

    image

    The following error messages came-up:

    image

    Can anyone shed-some-light on what is wrong?  Why can't I just use the supplied drivers?  Why won't firmware-b43 install?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • wallarug
    wallarug over 14 years ago in reply to wallarug

    Can someone please see what is wrong with the .tar.bz2 file that came with the device (and gave the above failures).  Can someone play around with these files and see if you can find the problem. I can not post the files here but you can download them from: here or here .

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • wallarug
    wallarug over 14 years ago in reply to wallarug

    Can someone please see what is wrong with the .tar.bz2 file that came with the device (and gave the above failures).  Can someone play around with these files and see if you can find the problem. I can not post the files here but you can download them from: here or here .

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
  • wallarug
    wallarug over 14 years ago in reply to wallarug

    I am reading the Makefile and the readme file that came with the device.  Can someone please explain what I have to do? (based on what the readme file is telling me.)

     

    Extract from readme file:

     

    1> $tar -xvzf RT2870_Linux_STA_x.x.x.x.tgz

        go to "./RT2870_Linux_STA_x.x.x.x" directory.

     

    2> In Makefile

               set the "MODE = STA" in Makefile and chose the TARGET to Linux by set "TARGET = LINUX"

               define the linux kernel source include file path LINUX_SRC

               modify to meet your need.

     

     

    3> In os/linux/config.mk

              define the GCC and LD of the target machine

              define the compiler flags CFLAGS

              modify to meet your need.

              ** Build for being controlled by NetworkManager or wpa_supplicant wext functions

                 Please set 'HAS_WPA_SUPPLICANT=y' and 'HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y'.

                 => #>cd wpa_supplicant-x.x

                 => #>./wpa_supplicant -Dwext -ira0 -c wpa_supplicant.conf -d

              ** Build for being controlled by WpaSupplicant with Ralink Driver

                 Please set 'HAS_WPA_SUPPLICANT=y' and 'HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=n'.

                 => #>cd wpa_supplicant-0.5.7

                 => #>./wpa_supplicant -Dralink -ira0 -c wpa_supplicant.conf -d

     

     

    4> $make

              # compile driver source code

              # To fix "error: too few arguments to function ¡¥iwe_stream_add_event"

                => $patch -i os/linux/sta_ioctl.c.patch os/linux/sta_ioctl.c

     

     

    5> $cp RT2870STA.dat  /etc/Wireless/RT2870STA/RT2870STA.dat

     

    6> load driver, go to "os/linux/" directory.

        #[kernel 2.4]

        #    $/sbin/insmod rt2870sta.o

        #    $/sbin/ifconfig ra0 inet YOUR_IP up

     

        #[kernel 2.6]

        #    $/sbin/insmod rt2870sta.ko

        #    $/sbin/ifconfig ra0 inet YOUR_IP up

     

     

    7> unload driver   

        $/sbin/ifconfig ra0 down

              $/sbin/rmmod rt2870sta

     

     

     

    I don't understand the step that says: " define the linux kernel source include file path LINUX_SRC" .

     

    Can someone help me please?

    Attachments:
    README_STA.zip
    Makefile.zip
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • wallarug
    wallarug over 14 years ago in reply to wallarug

    Found this: http://forums.whirlpool.net.au/archive/1439103 but I don't know where the: "Linux kernel source code header files are installed "

     

    Could someone please fill in the blanks from this post.  Which include: steps 2 and 3.

     

    This would be much appreciated.

     

    Thanks in advanced.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • GreenYamo
    GreenYamo over 14 years ago in reply to wallarug

    Hello Fergus,

     

    Are you sure that it is a 2770 ? Looking at the smaller chip, it is a 2720 which brings up a lot more hits for me in Google regarding wireless cards.

    I'm afraid I am not much of a Linux expert, but what you are posting above looks like you are compiling from source which is well above my head, perhaps someone else could comment on that.

    Have a look at the following link, that may be some help: http://wiki.debian.org/rt2870sta

    I know this may sound a little defeatist, and i'm happy to be told so, but at some point I would say you need to cut your losses and possibly think about buying a USB adaptor that is known to work with the Pi, rather than spending so much time trying to get your current one working ?

     

    Steve

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • wallarug
    wallarug over 14 years ago in reply to GreenYamo

    I think I will take your advice:

    "      but at some point I would say you need to cut your losses and possibly think about buying a USB adaptor that is known to work with the Pi, rather  than spending so much time trying to get your current one working ?"

     

    What do you think of this one: http://www.jaycar.com.au/productView.asp?ID=YN8309

     

    Although it is not branded on the Jaycar website, I think that it is the EW-7811Un which is verified on the wiki [http://elinux.org/RPi_VerifiedPeripherals#USB_WiFi_Adapters ].

     

    Also, I read on the wiki that someone has made a self-installer (so to speak) which should make it easy to impliment.

     

    Any thoughs before I go -out and buy this wireless adapter?

     

    PS: Should some add the other one to the problem adapter section. 

     

    And as a side not, I think the problem may have been the confusion between the two chips (RT2770 + RT2720) somewhere in the software. or that the hub is not providing enough power and therefore this device is pulling power from the RPi.


    Just a though.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • wallarug
    wallarug over 14 years ago in reply to GreenYamo

    The two chips in this device are: Ralink RT2780F chipset with RT2720L as transceiver.  Does this mean anything driver wise?

     

    (I am still going to get a new adapter though)

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube