Belkin wireless card F5D7010 RT2500 chipset on Solaris10 IBMthinpad R40

I have a Belkin F5D7010 wireless card with RT2500 chipset .I have been trying to set up this wireless card on Solaris10 (IBM thinkpad R40 box) for the past week, without success. If i use ndis wrapper I am getting $chicago$ Segementation Fault core dumped error while running ./ndiscvt -i ndis.inf - s ndis.sys -o ndis.h command. I tried with Ral driver too, I was able to plumb and the ifconfig-a shows ral0 interface up, but no connection. Is there no light at the end of the tunnel? Any help is appreciated . I am a novice in solaris.
Thanks.

Thanks, what about RAL driver , is it hopeless for
this card too. At this point I am pretty much ready
to get myself one of these cardsdon't know. All I do know is that their NDIS driver only has the code base for Broadcom cards only. I was hoping to use a Linksys card with their NDIS port but slammed into the wall and then posted a message. Support for any card other then Broadcom is simply not in the code base so there is nothing that you can do.
Netgear WG511T Cardbus Works, forgot to mention that I needed cardbus-0.3 as well.
So Netgear WG511T
with
ath-01 for Solaris 10 support
wificonfig -01 for Solaris 10 support
cardbus-0.3 to get cardbus support added to Solaris 10.
The Netgear card is cardbus and Solaris 10 only has PCMCIA support without cardbus.
alan

Similar Messages

PowerMac G4 With Belkin Wireless Card

I recently moved my G4 (MDD) to the basement where I do not have wiring for the network. I have a belkin wireless pci card that I was not using so I thought I'd try to install it in the G4. How should I go about doing this. Thanks
Jon

If the Belkin card uses the Broadcomm chipset it will just work, otherwise confirm with Belkin that they supply Mac drivers.
iFelix

Belkin Wireless Card+Powerbook G4

Firstly, I apologise for the question, but despite my best efforts I havent been able to find a quick answer.
I'm currently travelling in italy and have just picked up a Belkin F5D7011 Wireless card so I can get on the net in the hotel I am staying at (yeah, should have sorted this before i left, I know, I'm a fool!).
There are no drivers, and while belkins online help say its not compatible I have seen posts saying that if its based on the broadcom (if thats right) chipset, then it should work. I've plugged it into the machine, and tried the airport helper, but nothing appeared to happen.
I am currently posting from an internet cafe, hence the desperation and foolish question. I will go back to my hotel to try it again, but is there something I should be doing, or more accuratly, is there something I'm doing wrong, ie, a certain procedure?
If anyone has any links to other discussions or help articles, I'd really really love you for it.

Hi, sf. The 7011, which does use the same Broadcom chipset as Apple's Airport hardware, is reported to work fine on Macs running Airport 3.4.1 software. If your Tiger installation includes a newer Airport software version than that, perhaps that's where the problem lies.
Does Apple System Profiler detect the card?

Belkin pre n to belkin wireless card bridged to nic to router to emac

Ok, so I have a wireless router (Belkin Pre N) getting it's signal from a comcast modem. One other port is hardwired into my upstairs neighbors computer (PC running windows xp pro SP 2). That computer is generally off.
My set up is an old PC (running win xp pro SP2, 500mhz, 184MB Ram, AMD-K6) which has a belkin wireless G desktop network card with a compaq nic card. I use the network connections window to bridge these two together on the PC. The nic on the PC goes to a "network everywhere" 4 port cable/dsl router (with the firmware updated). The ethernet cable goes from the PC's nic into the 3rd port of the router and the other ethernet cable on port 2 goes into my emacs ethernet port.
Now, I can maintain some connectivity in this manner for my emac. The problem is that I have to leave the network prefs window open to click the "renew DHCP lease" button every 5-10 minutes because I am just suddenly not connected to the network. The odd thing is when I refresh the ip nothing changes. I just get my connectivity back...
Worse, ultimately, I'd say every 4 or so hours, suddenly my PC loses it's wireless connection and stops seeing any neighboring wireless connections (there is many, I live in Chicago) and the bridge suddenly starts getting it's ip from the router between my pc and mac instead of from the wireless card that was connecting to the upstairs belkin pre N. Essentially the network starts working in reverse!. I've tried using the network everywhere router as just a router or even setting it with a static ip with the dns and router configurations from the belkin pre N. I get awesome throughput but in 5-10 minutes it always degrades to nothing on the mac. It is to the point that I keep the network prefs window open on the mac and just periodically click "renew DHCP lease" basically the whole time I am using the internet or downloading something.
Now once the PC loses it's wireless connection I've found the only way to get it back to the way it was is to disable the nic, the bridge, then the wireless and then enable them in reverse order (wireless, bridge, and nic) and it goes back to working correctly... usually once going back to the mac and clicking "renew DHCP lease" I then have 1 more addition to the last number of my ip. Like 192.168.2.3 would then be 192.168.2.4 and so on this continues. The highest I got before reseting all including the router was .2.30
Does anyone know why this is or have a similar set up?
G3 Mac OS X (10.3.9) 400 Mhz 576MB SDRAM

Easiest solution, get a wireless adapter for the eMac.
Sounds like you don't have ICS configured correctly, and it can do this when using a wireless to wired connection.
iFelix

Wifi card with rt2500 chipset not detected

Hi all,
I got a new pci wifi card with chipset rt2500, but I can't make it work. I installed without problems rt2500 driver from beta 3, and when I run ifconfig, the wifi card doesn't show up. If I run iwconfig, ra0 shows up but with no wireless extension. I tried to do iwconfig ra0 mode monitor or managed, and it says "Invalid argument". The card works with a live cd distro (rt2500 driver) and with windows so it's not an hardware problem, and when I do a lspci, card is appearing.
I tried the rt2500-cvs driver, but I have the same problem too.
So I think help is needed

Zanton - maybe this is wrong place to ask this question but please can you tell me how did you compile your own kernel. I'm newbie with Arch and using pci wifi card with chipset rt2500 (not just now ).
I've used Slacware over an year without problems and I think it's little bit tricky to compile Arch-linux kernel with ABS-way because it was so easy in Slack.
So did you compile with ABS http://wiki.archlinux.org/index.php/Cus … n_with_ABS or some other way?
I'm using latest rt2500-driver (nightly-cvs) and SMP as well PREEMPT is on!

Belkin Wireless Notebook Network Card F5D7010 and Tiger

Hi
I'm currently running OSX 3.9 Panther on my G3 500mhz Powerbook and I have a Belkin Wireless Card F5D7010 vers.1314uk which has a Broadcom chipset and works perfectly with Airport. (vers. 1.x 2.x and 4.x are Broadcom, vers. 3.x are Prism)
I'm thinking of upgrading to Tiger but I'm worried that the change of operating system will render my wireless card inoperable or cause problems. Has anybody on these forums had any experience with this Belkin card version and Tiger and can they confirm that it will work after the upgrade?
Any advice would be appreciated
Barry
PowerBook G3500mhz Mac OS X (10.3.9)

Hi Barry,
Here's what I found...
http://www.xlr8yourmac.com/archives/may05/050405.html#S19180
And about 2/3rds down this page...
Tiger user report on Belkin F5D7011 Wireless PCcard...
http://www.xlr8yourmac.com/archives/jun05/060805.html

[SOLVED] WPA_SUPPLICANT and rt2500 chipset cards [SOLVED]

EDIT:
If you want to make an rt2500 chipset wireless card work with wpa_supplicant (and it doesn't already), maybe you have tried to run wpa_supplicant and got a bunch of errors saying nasty things about IOCTRL, this means, most likely, that wpa_supplicant is having trouble communicating with your wireless card. One problem (my problem) was the driver, the old rt2500 driver.
Are you using an old rt2500 driver, or the newer rt2500pci driver? You can probably tell by looking at your rc.conf file, in the section called "MODULES", if you have rt2500 listed, you're
loading the old driver, so you should put an "!" in front to disable it. You also need to make sure you have the rt2500pci drive and (I think) the rt2x00lib and rt2x00pci modules listed. I'm pretty sure these are included with an up to date stock kernel.
I guess another way to look for the driver would be to boot your computer and run "dmesg | more" and parse through the output, or "dmesg | more | grep | rt2500", which should find you any lines that contain text "rt2500".
Now, if you've been using that old rt2500 driver, your wireless card has probably been calling itself "ra0", assuming it's your only card using the rt2500 driver, when you switch to the new driver, it will call itself "wlan?" where ? is some number. It's probably wlan0, unless you have another wireless card, I do (a Broadcom card that has never worked) so mine is actually called wlan1. There are tutorials for making Broadcom cards work, but that's a different kettle of worms and I'm not qualified to talk about it since mine doesn't.
Now it should work with wpa_supplicant using the driver "wext", which should be the default for wpa_supplicant, but just to be safe you can type:
wpa_supplicant -d -iwlan? -Dwext -c/path_to_config_file/your_config_file
| | | |
| | | Config file to use
| | driver to use
| interface to use
|
tell wpa_supplicant to be more verbose, -dd is even more verbose
You probably already read the man pages and wiki for wpa_supplicant, but if you haven't noticed yet the syntax for the options is -oPARAMETER there's no seperation between the option and it's argument.
Now if you did all this, and you're not getting IOCTRL errors, then you're wireless driver and wpa_supplicant are probably communicating just fine. If you're still not able to connect then the problem could be one of:
Unable to associate with access point, possibly because of weak signal or MAC filtering
Errors in your wpa_supplicant config file, maybe a PSK is wrong, maybe you're specifying a protocol wrong? If you have some sort of complex configuration / AP setup, it might be best too try a simpler configuration with an AP you can administer (like a home portal, if you have one), see if you can get that to work, and then figure out why your super complex configuration to work.
If you want too, read tomk's posts below, my other posts are (most likely) not helpful.
_____________________________ORGINAL POST__ORGINAL TOPIC:Can BSD drivers work w/ WPA_SUPPLICANT in Linux?_____________________________________
Hello all,
Recently I installed FreeBSD on a laptap with a rt2500 chipset wireless card and was able, for the first time ever, to use wpa encrypted networking via wpa_supplicant. Then I screwed up my rc.conf file, tried to fix it, and apparently completely broke the system.
So I decided to install arch, because I didn't really want to rebuild the ports I had installed, but then, it appears, I can't get wpa_supplicant to work. Not so, so bad for my home network (I can either use an ethernet connection or switch my router to an open connection), but I'm intrigued enough at the prospect of being able to use the wifi network at my university, that I really want this to work now.
So I messed around with wpa_supplicant, but apparently wpa_supplicant doesn't support the rt2500 driver. But I know the generic BSD driver works (wext does not), so, perhaps naively, I tried to build wpa_supplicant with the BSD driver enabled.
But, when I did this, mkpkg tells me that my config file is bad. Is this because I'm trying to enable the BSD driver?
I realize it might be helpful to look at my config file, but for the moment, I'm too lazy to fiddle with things to get the file of the laptop, but it occurs to me that it might just be downright silly to expect a bsd driver to work with linux. So if I"m being stupid, could someone please tell me?
-thanks!
Last edited by pseudonomous (2008-08-24 21:29:26)

This is the last config file I tried:
# Example wpa_supplicant build time configuration
# This file lists the configuration options that are used when building the
# hostapd binary. All lines starting with # are ignored. Configuration option
# lines must be commented out complete, if they are not to be included, i.e.,
# just setting VARIABLE=n is not disabling that variable.
# This file is included in Makefile, so variables like CFLAGS and LIBS can also
# be modified from here. In most cases, these lines should use += in order not
# to override previous values of the variables.
# Uncomment following two lines and fix the paths if you have installed OpenSSL
# or GnuTLS in non-default location
#CFLAGS += -I/usr/local/openssl/include
#LIBS += -L/usr/local/openssl/lib
# Some Red Hat versions seem to include kerberos header files from OpenSSL, but
# the kerberos files are not in the default include path. Following line can be
# used to fix build issues on such systems (krb5.h not found).
#CFLAGS += -I/usr/include/kerberos
# Example configuration for various cross-compilation platforms
#### sveasoft (e.g., for Linksys WRT54G) ######################################
#CC=mipsel-uclibc-gcc
#CC=/opt/brcm/hndtools-mipsel-uclibc/bin/mipsel-uclibc-gcc
#CFLAGS += -Os
#CPPFLAGS += -I../src/include -I../../src/router/openssl/include
#LIBS += -L/opt/brcm/hndtools-mipsel-uclibc-0.9.19/lib -lssl
#### openwrt (e.g., for Linksys WRT54G) #######################################
#CC=mipsel-uclibc-gcc
#CC=/opt/brcm/hndtools-mipsel-uclibc/bin/mipsel-uclibc-gcc
#CFLAGS += -Os
#CPPFLAGS=-I../src/include -I../openssl-0.9.7d/include \
#-I../WRT54GS/release/src/include
#LIBS = -lssl
# Driver interface for Host AP driver
CONFIG_DRIVER_HOSTAP=y
# Driver interface for Agere driver
#CONFIG_DRIVER_HERMES=y
# Change include directories to match with the local setup
#CFLAGS += -I../../hcf -I../../include -I../../include/hcf
#CFLAGS += -I../../include/wireless
# Driver interface for madwifi driver
CONFIG_DRIVER_MADWIFI=y
# Change include directories to match with the local setup
CFLAGS += -I../madwifi
# Driver interface for Prism54 driver
# (Note: Prism54 is not yet supported, i.e., this will not work as-is and is
# for developers only)
#CONFIG_DRIVER_PRISM54=y
# Driver interface for ndiswrapper
CONFIG_DRIVER_NDISWRAPPER=y
# Driver interface for Atmel driver
CONFIG_DRIVER_ATMEL=y
# Driver interface for Broadcom driver
#CONFIG_DRIVER_BROADCOM=y
# Example path for wlioctl.h; change to match your configuration
#CFLAGS += -I/opt/WRT54GS/release/src/include
# Driver interface for Intel ipw2100/2200 driver
#CONFIG_DRIVER_IPW=y
# Driver interface for generic Linux wireless extensions
CONFIG_DRIVER_WEXT=y
# Driver interface for FreeBSD net80211 layer (e.g., Atheros driver)
CONFIG_DRIVER_BSD=y
CFLAGS += -I/usr/local/include
LIBS += -L/usr/local/lib
# Driver interface for Windows NDIS
#CONFIG_DRIVER_NDIS=y
#CFLAGS += -I/usr/include/w32api/ddk
#LIBS += -L/usr/local/lib
# For native build using mingw
#CONFIG_NATIVE_WINDOWS=y
# Additional directories for cross-compilation on Linux host for mingw target
#CFLAGS += -I/opt/mingw/mingw32/include/ddk
#LIBS += -L/opt/mingw/mingw32/lib
#CC=mingw32-gcc
# By default, driver_ndis uses WinPcap for low-level operations. This can be
# replaced with the following option which replaces WinPcap calls with NDISUIO.
# However, this requires that WZC is disabled (net stop wzcsvc) before starting
# wpa_supplicant.
# CONFIG_USE_NDISUIO=y
# Driver interface for development testing
#CONFIG_DRIVER_TEST=y
# Driver interface for wired Ethernet drivers
CONFIG_DRIVER_WIRED=y
# Enable IEEE 802.1X Supplicant (automatically included if any EAP method is
# included)
CONFIG_IEEE8021X_EAPOL=y
# EAP-MD5
CONFIG_EAP_MD5=y
# EAP-MSCHAPv2
CONFIG_EAP_MSCHAPV2=y
# EAP-TLS
CONFIG_EAP_TLS=y
# EAL-PEAP
CONFIG_EAP_PEAP=y
# EAP-TTLS
CONFIG_EAP_TTLS=y
# EAP-GTC
CONFIG_EAP_GTC=y
# EAP-OTP
CONFIG_EAP_OTP=y
# EAP-SIM (enable CONFIG_PCSC, if EAP-SIM is used)
#CONFIG_EAP_SIM=y
# EAP-PSK (experimental; this is _not_ needed for WPA-PSK)
#CONFIG_EAP_PSK=y
# EAP-PAX
#CONFIG_EAP_PAX=y
# LEAP
CONFIG_EAP_LEAP=y
# EAP-AKA (enable CONFIG_PCSC, if EAP-AKA is used)
#CONFIG_EAP_AKA=y
# EAP-SAKE
#CONFIG_EAP_SAKE=y
# EAP-GPSK
#CONFIG_EAP_GPSK=y
# Include support for optional SHA256 cipher suite in EAP-GPSK
#CONFIG_EAP_GPSK_SHA256=y
# PKCS#12 (PFX) support (used to read private key and certificate file from
# a file that usually has extension .p12 or .pfx)
CONFIG_PKCS12=y
# Smartcard support (i.e., private key on a smartcard), e.g., with openssl
# engine.
CONFIG_SMARTCARD=y
# PC/SC interface for smartcards (USIM, GSM SIM)
# Enable this if EAP-SIM or EAP-AKA is included
#CONFIG_PCSC=y
# Development testing
#CONFIG_EAPOL_TEST=y
# Replace native Linux implementation of packet sockets with libdnet/libpcap.
# This will be automatically set for non-Linux OS.
#CONFIG_DNET_PCAP=y
# Select control interface backend for external programs, e.g, wpa_cli:
# unix = UNIX domain sockets (default for Linux/*BSD)
# udp = UDP sockets (default for Windows)
# y = use default (backwards compatibility)
# If this option is commented out, control interface is not included in the
# build.
CONFIG_CTRL_IFACE=y
# Include support for GNU Readline and History Libraries in wpa_cli.
# When building a wpa_cli binary for distribution, please note that these
# libraries are licensed under GPL and as such, BSD license may not apply for
# the resulting binary.
#CONFIG_READLINE=y
# Remove debugging code that is printing out debug message to stdout.
# This can be used to reduce the size of the wpa_supplicant considerably
# if debugging code is not needed. The size reduction can be around 35%
# (e.g., 90 kB).
#CONFIG_NO_STDOUT_DEBUG=y
# Remove WPA support, e.g., for wired-only IEEE 802.1X supplicant, to save
# 35-50 kB in code size.
#CONFIG_NO_WPA=y
# Remove WPA2 support. This allows WPA to be used, but removes WPA2 code to
# save about 1 kB in code size when building only WPA-Personal (no EAP support)
# or 6 kB if building for WPA-Enterprise.
#CONFIG_NO_WPA2=y
# Remove AES extra functions. This can be used to reduce code size by about
# 1.5 kB by removing extra AES modes that are not needed for commonly used
# client configurations (they are needed for some EAP types).
#CONFIG_NO_AES_EXTRAS=y
# Select configuration backend:
# file = text file (e.g., wpa_supplicant.conf)
# winreg = Windows registry (see win_example.reg for an example)
CONFIG_BACKEND=file
# Select program entry point implementation:
# main = UNIX/POSIX like main() function (default)
# main_winsvc = Windows service (read parameters from registry)
# main_none = Very basic example (development use only)
#CONFIG_MAIN=main
# Select wrapper for operatins system and C library specific functions
# unix = UNIX/POSIX like systems (default)
# win32 = Windows systems
# none = Empty template
#CONFIG_OS=unix
# Select event loop implementation
# eloop = select() loop (default)
# eloop_win = Windows events and WaitForMultipleObject() loop
# eloop_none = Empty template
#CONFIG_ELOOP=eloop
# Select layer 2 packet implementation
# linux = Linux packet socket (default)
# pcap = libpcap/libdnet/WinPcap
# freebsd = FreeBSD libpcap
# winpcap = WinPcap with receive thread
# ndis = Windows NDISUIO (note: requires CONFIG_USE_NDISUIO=y)
# none = Empty template
#CONFIG_L2_PACKET=linux
# IEEE 802.11i/IEEE 802.11e STAKey negotiation for direct link connection
#CONFIG_STAKEY=y
# Proposed replacement for STAKey negotiation: PeerKey handshake for
# Station to Station Link
CONFIG_PEERKEY=y
# Select TLS implementation
# openssl = OpenSSL (default)
# gnutls = GnuTLS (needed for TLS/IA, see also CONFIG_GNUTLS_EXTRA)
# internal = Internal TLSv1 implementation (experimental)
# none = Empty template
#CONFIG_TLS=openssl
# Whether to enable TLS/IA support, which is required for EAP-TTLSv1.
# You need CONFIG_TLS=gnutls for this to have any effect. Please note that
# even though the core GnuTLS library is released under LGPL, this extra
# library uses GPL and as such, the terms of GPL apply to the combination
# of wpa_supplicant and GnuTLS if this option is enabled. BSD license may not
# apply for distribution of the resulting binary.
#CONFIG_GNUTLS_EXTRA=y
# If CONFIG_TLS=internal is used, additional library and include paths are
# needed for LibTomCrypt and TomsFastMath.
#LTC_PATH=/usr/src/libtomcrypt-1.11
#TFM_PATH=/usr/src/tomsfastmath-0.09
#CFLAGS += -I$(LTC_PATH)/src/headers
#LIBS += -L$(LTC_PATH) -L$(TFM_PATH)
#LIBS_p += -L$(LTC_PATH) -L$(TFM_PATH)
# Integrate ndis_events.exe functionality into wpa_supplicant.
# This is only for Windows builds and requires WMI-related header files and
# WbemUuid.Lib from Platform SDK even when building with MinGW.
#CONFIG_NDIS_EVENTS_INTEGRATED=y
#PLATFORMSDKLIB="/opt/Program Files/Microsoft Platform SDK/Lib"
# Add support for DBus control interface
#CONFIG_CTRL_IFACE_DBUS=y
# Add support for loading EAP methods dynamically as shared libraries.
# When this option is enabled, each EAP method can be either included
# statically (CONFIG_EAP_<method>=y) or dynamically (CONFIG_EAP_<method>=dyn).
# Dynamic EAP methods are build as shared objects (eap_*.so) and they need to
# be loaded in the beginning of the wpa_supplicant configuration file
# (see load_dynamic_eap parameter in the example file) before being used in
# the network blocks.
# Note that some shared parts of EAP methods are included in the main program
# and in order to be able to use dynamic EAP methods using these parts, the
# main program must have been build with the EAP method enabled (=y or =dyn).
# This means that EAP-TLS/PEAP/TTLS/FAST cannot be added as dynamic libraries
# unless at least one of them was included in the main build to force inclusion
# of the shared code. Similarly, at least one of EAP-SIM/AKA must be included
# in the main build to be able to load these methods dynamically.
# Please also note that using dynamic libraries will increase the total binary
# size. Thus, it may not be the best option for targets that have limited
# amount of memory/flash.
CONFIG_DYNAMIC_EAP_METHODS=y
# Include client MLME (management frame processing).
# This can be used to move MLME processing of Devicescape IEEE 802.11 stack
# into user space.
#CONFIG_CLIENT_MLME=y
# Currently, driver_devicescape.c build requires some additional parameters
# to be able to include some of the kernel header files. Following lines can
# be used to set these (WIRELESS_DEV must point to the root directory of the
# wireless-dev.git tree).
WIRELESS_DEV=/lib/modules/2.6.24-ARCH/build
CFLAGS += -I$(WIRELESS_DEV)/net/mac80211
Last edited by pseudonomous (2008-08-24 08:23:23)

Linksys WMP11 Wireless Card Setup (Prism 2.5 chipset wlan-ng drivers)

I just finished setting up my first Arch Linux box on an ancient desktop of mine. It is running so suprisingly fast and I am loving it so far. I learned a ton working trough the guides too. Anyway, I am having issues setting up my wireless card. Currently, I am sharing my laptops wifi with my Arch desktop but I would like to use my acutal PCI card.
The card is a Linksys WMP11. I used to lspci to find that it is using the Prism 2.5 chipset. I consulted the Wireless Setup guide
https://wiki.archlinux.org/index.php/Wi … bsolete.29
This informed me that my card is supported by the wlan-ng drivers. My card is supported on the hardware list:
http://www.linux-wlan.org/docs/wlan_adapters.html.gz
I have searched around the official Arch repositories and the AUR and I can not find this package. The Wireless Wiki page states to use tools within the wlan-ng26-utils package. I can't seem to find this package. It does say wlan-ng is obselete. Is it no longer maintained?
I also downloaded the drivers directly from
http://www.linux-wlan.org/
However, I ran into issues when trying to run make configure. The value it generates for the Linux source path is invalid.
So, I am out of luck since the packages don't appear to exist, or is it possible to compile and install the drivers from source? How do I tie this into pacman?
Thanks

Hope this helps. I have the same chipset and have been searching on and off for the past three days for the answer - here's the simple thing that got mine working.
in /etc/rc.conf modify the modules line to include wpa_supplicant
MODULES=(wpa_supplicant)
in /etc/modprobe.d/blacklist.conf add the following line (create this file if it doesn't exist)
blacklist iwconfig
Now you should be able to activate and configure your card via wpa_supplicant. Here is a sample of my wpa_supplicant.conf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
# WEP in Shared Key mode
network={
ssid="MyRouterEssid"
scan_ssid=1
key_mgmt=NONE
wep_key0="MyCustomKey1"
wep_key1="MyCustomKey2"
wep_key2="MyCustomKey3"
wep_key3="MyCustomKey4"
wep_tx_keyidx=2
priority=5
auth_alg=SHARED
And here is the wpa_supplicant command line to start it manually
wpa_supplicant -B -c /etc/wpa_supplicant.conf -i wlan0
BTW, I also have these two lines in the /etc/modprobe.d/blacklist.conf file
blacklist orinono
blacklist orinono_pci
I have not had time yet to verify if this is not needed (was part of previous attempts to get wifi to connect) but wanted to let you know in case it is part of the stuff needed to get these cards working with the newer wpa_supplicant. Of course this configuration is for a WEP Shared Key configuration. I have also not had time yet to test whether or not this will work in WPA mode. I suspect not in my case because the firmware I have on my card is pre-wpa on the Prism 2.5 series. We'll see.
-Brian

Linux compatible chipset wireless card

Okay,
I'm sick to death of my Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card (rev 01)
I'm just curious if there is any company that is looking to cater to the linux market. I'd like my wallet to show my thanks:)
It's not that ndiswrapper is hard to use but even when done I simply can't get it to work and yes I've searched the forum and gone through 4 or 5 different setups........I'm not asking for help on this because plenty has been offered on this board.
My question is: Is there a company that is making pci and pcmcia cards that are linux compatible without having to install some compatibility layer (correct term?) like ndiswrapper? A company that is giving the source code to us so we can have true drivers for our product?
Don't misunderstand this post - I'm not complaining about linux - I just want to support the companies that would like our business.
Thanks,
McRae

arew264 wrote:One thing I have heard is that we shouldn't blame Broadcom for poor driver support because the actual frequencies their cards run on are controlled by the drivers, which means that if they released linux drivers, they could be hacked into letting you access government and police radio frequencies. That would lead to legal problems which is why their are no drivers from Broadcom for linux.
Unfortunately, that's bulldust, we have every reason to blame Broadcom for their lack of support.
The current drivers utilise the firmware files from the windows driver. And it's in those firmware files that the frequencies live. So no, Broadcom COULD have released a driver, just like the one being developed. This is also how intel, Ralink, TI and other vendors work. All of which have licenses that forbid modification, thus if someone does hack them, they're doing so illegally, and the respective manufacturers can't be held at fault. Heck, the firmware in the broadcom windows drivers, already falls under an equivalent license, so they wouldn't need to even change that.
They could even build one like Madwifi, which has a closed source file which is included at compile time that contains the frequencies. Or just not build shit software based wireless cards, and develop proper ones that work more at a hardware level like the rt2500.
That's not a valid excuse from Broadcom part, not even remotely valid.
James

Dell wireless 1350 card with BCM4306 chipset troubles

Hello everyone,
I'm sort of new to setting up wireless in linux and my wireless card is driving me insane. I've tried the bcm43xx, bcm43, and ndiswrapper solutions from here: http://wiki.archlinux.org/index.php/Wireless and none of them seem to work. I am absolutely to determined to get the card working with ndiswrapper now. So I tried a tutorial from someguy who has the exact same chipset as me on the ubuntu forums here: http://www.ubuntuforums.org/showthread.php?t=340689 and followed his exact instructions and it didn't work.
When I try to the command sudo "ifconfig wlan0 up" I recieve the message "SIOCSIFFLAGS: No such file or directory." So first let me go through everything I checked to make sure nothing was wrong. First when I cat out /etc/modprobe.d/ndiswrapper I recieve the message "alias wlan0 ndiswrapper." Next when I run "ndiswrapper -l" I recieve the message
"bcmwl5 : driver installed
device (14E4:4320) present (alternate driver: ssb)"
Next when I run the command "lspci -nn" I recieve the output
"02:00.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03)"
Finally, after I run the command "sudo ifconfig wlan0 up", if I go read the tail end of /var/log/messages.log I see the messages
"Jun 9 13:05:31 theArch kernel: input: b43-phy0 as /devices/virtual/input/input11
Jun 9 13:05:31 theArch kernel: b43 ssb0:0: firmware: requesting b43/ucode5.fw
Jun 9 13:05:31 theArch firmware.sh[2929]: Cannot find firmware file 'b43/ucode5.fw'"
I have come to the startling conclusion that linux cannot find the driver that I installed with ndiswrapper. Is there anyway I can explicitly tell linux where the driver could be found? or should I just go out and buy a new expensive wifi card
If I were to go out and buy a new expensive wifi card, which card would you guys recommend?

Calm down guys - misunderstanding on both sides here.
hilariousity - when you're asking for help, you should be grateful to anyone who takes the time to respond. Telling someone they have no idea about the subject under discussion is likely to make them stop helping you, and to discourage others. I realise you're new here, so you may like to take a few minutes to read this.
wonder - he did say that he had already tried the b43* drivers, and that he was now determined to use ndiswrapper.
To return to the actual topic, wonder is correct. You need to install firmware for the b43* driver, or you need to blacklist the b43* drivers if you intend to use ndiswrapper.
Finally, if you were actually able to load the bcm43xx module, your system is out of date, and you should update it before proceeding.

Problems getting my rt2500 wireless card to see the network

hi there,
I have been struggling for a few days now trying to get my rt2500 wireless network card to see the network. I have got to a point where I am now stuck.
here is what /etc/conf.d/wireless
wlan_ra0="ra0 essid BTHomeHub-F288 key xxxxxxxxxx"
WLAN_INTERFACE=(ra0)
here is the network part of /etc/rc.conf
lo="lo 127.0.0.1"
ra0="dhcp"
INTERFACES=(lo ra0)
this is from /var/log/messages.log
Aug 4 15:28:00 black-hp dhcpcd[5738]: ra0: dhcpcd 3.0.17 starting
Aug 4 15:28:00 black-hp dhcpcd[5738]: ra0: hardware address = 00:90:4b:d6:30:8a
Aug 4 15:28:00 black-hp dhcpcd[5738]: ra0: broadcasting for a lease
Aug 4 15:28:30 black-hp dhcpcd[5738]: ra0: exiting
this is the output of ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
ra0 Link encap:Ethernet HWaddr 00:90:4B:D6:30:8A
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:1707 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:92178 (90.0 Kb)
Interrupt:16 Base address:0x8000
and this is the output of iwconfig
ra0 RT2500 Wireless ESSID:"BTHomeHub-F288"
Mode:Managed Frequency=2.412 GHz Bit Rate=11 Mb/s Tx-Power:-2 dBm
RTS thr:off Fragment thr:off
Encryption key:xxxx-xxxx-xx Security mode:open
Link Quality=0/100 Signal level:-120 dBm Noise level:-80 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Appologies if i have done something really stupid, but this is the first time i have used wireless networking.
Thanks for any help offered
Mike

Hi 2k,
maybe it's a problem with the association between access point and your wireless card.
from the output of iwconfig the security mode is open, try to change it in restricted;
modify /etc/conf.d/wireless in this way:
wlan_ra0="ra0 essid BTHomeHub-F288 key restricted xxxxxxxxxx"

Belkin wireless network card F5D7011

Hi!
I've order a PCMCIA wireless card from apple store for my G4 titanium.
When I plug it in, the card seems to be reconized by the system (I can see it on the right side of my menu bar) but it does not appears in the network configuartion list (only modem or built-in ethernet are in this menu).
What should I do to have it working?
Do I need to install any specific driver?
Do I need to install any Airport software?
I'm still running with Mac OS 10.3.8. Do I have to update to Tiger???
Many thanks in advance for your help.
Ivan
powerbook G4 867MHz Mac OS X (10.3.8)

Thanks for your quick reply!
I can effectively see "broadcom" on the menu.
I said I was running with 10.3.8 but I made a mistake it's 10.2.8 !
I download the 3.1 Airport from the apple site but I can't start it. No network card is found.
I tried to install 10.4.2 (from my sister new G5!) but some message said I can't install this software on my computer (no other explaination). What should I do?
Any other advice???
Thanks anyway for you help!
Ivan

Wireless card not "on" ?

Hello,
So far this forum has been good to me, so I'm hoping that someone might be able to help me out with another problem I've recently encountered.
I am currently trying to set up my Wireless card which is a Belkin F5D7000 card that uses the rt2500 chipset (which there are drivers for through Ralink) and though I have been able to install the drivers alright, I didn't notice until recently that the lights on the back of the card are out and the card doesn't seem to be "active" at all.
Does anyone have any suggestions as to what may be causing this to happen? The card does show up on lspci, but only as "Network controller: unknown device" (although I know that it is the card because of the identification codes).
Thanks!
-Locri

What a co-incidence, I installed Belkin wlan on my Arch/XP dual-boot system a few days ago!....
I'm running the Windows drivers on Arch using ndiswrapper... have you got this bit working yet? You need the rt2500 drivers which you can download or you can find them on your windows installation in program files/belkin.... (you need the .inf and .sys files)
Another issue I've had is I can't get the wlan working on linux with WEP encryption enabled but it works ok on XP. I'm using mac-address locking for security at moment.
If you can be more specific about what your having a problem with I'll try to help (but a bit later when I get back to my home PC!)
- Cheers, Renners

Wireless Card PC54G

I have to wirelless card's pc54g in my two computers, and in windows's one i want to give a try on Windows XP 64 Bits, cause now msi provide almost all drivers for my board (MSI Neo 2 Platinum), but i'm still missing the driver for my wireless card. So the question is: when msi will provide us the driver and the software (WlanUtility) for Windows 64 bits.. thanks in advance

Thank you all. I've got the driver from
http://files.aoaforums.com/index.php?dir=224 - The Topic (You have to login/register first)
http://files.aoaforums.com/code.php?file=2130 - The Driver (You have to login/regiter first)
is a nice forum for the 64 bits world.
Dr Stu, the chipset is Ralink RT2500, i know it cause i use ndiswrapper in Linux to use the card, and with the rt2500.sys driver.
Dream_True thanks, but the site didn't work for me.
Assaf thanks for the faster response.
One more question, if you don't care, there is a WlanUtility version for Windows 64 Bits?
thanks in advance

3rd party PCI Wireless cards

OK, so I've decided to finally install broadband at home.
I've had an Airport Express (AE) for several months to use when traveling, etc.
I have a PowerBook with an Airport Extreme card in it and I use its wireless capability all the time.
My older G4 tower (Digital Audio) does NOT have a wireless card.
I want to install a wireless card in the G4 tower, since I suspect that will be the easiest way to get both of my computers online. I know I could buy a wired router instead, but...
Anyways, my G4 tower would need the old original Airport card, which costs way more than the new Airport Extreme cards. So then, like my title says...
Are there any known issues with using a 3rd party PCI Wireless card?
For instance, Belkin's F5D7001.
I thought I saw somewhere that Belkin supports OS X, but some people had problems in Tiger. Others may have had problems with various wireless encryption methods.
Am I better off just biting the bullet and finding an old Airport card for $100?
Sorry if this topic has been covered, I tried a search but didn't get much info on this particular topic.
I am running Panther on both my machines.
Thanks, folks!

I am using a Belkin F5D7000 in a AGP G4 Tower. The chipset is by Ralink. Free OS X version drivers are available here:
http://www.ralinktech.com/supp-1.htm
While not as elegant as Airport software, of course, the driver and card work excellent.
If you can find a wireless PCI card using the original Broadcom chip sets, just like the Airport card, then it will be recognized as an Airport card and use the Apple software. These are hard to find now however.
Here is an excellent article on what you are trying to do:
http://homepage.mac.com/techedgeezine/2005_0217-54g-inyourmac1.htm

Belkin wireless card F5D7010 RT2500 chipset on Solaris10 IBMthinpad R40

Similar Messages

Maybe you are looking for