LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (http://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Trouble with Wireless PCI card - (not the driver) (http://www.linuxquestions.org/questions/linux-hardware-18/trouble-with-wireless-pci-card-not-the-driver-697030/)

pwd_pwd_omg_pwd 01-13-2009 12:51 PM

Trouble with Wireless PCI card - (not the driver)
 
Hey guys

I've just become the proud new owner of a 54Mbps 802.11g wireless PCI, but it doesnt seem to want to work. ive done the whole driver thing via ndiswrapper and that seems to have worked:
Code:

ndiswrapper -l
net8185 : driver installed

net8185 being the driver off the CD.

From the looks of it, the card isnt being recognised seen as iwconfig gives:

lo no wireless extensions
eth0 no wireless extensions
eth1 no wireless extensions

although there is only one ethernet slot on my machine so maybe the wireless is being mis-read? just a thought.

Im thinking i need to put something in the kernel via insmod but am running a blank at what to do. any help would be much appreciated.

farslayer 01-13-2009 02:13 PM

You know there is a Linux driver for that card on the Realtek website right ?

http://www.realtek.com.tw/downloads/...Downloads=true

pwd_pwd_omg_pwd 01-13-2009 07:52 PM

ah, well i was told to do it via ndiswrapper. many ways to skin a cat. But all the same, the driver is fine, but the card isnt being recognised or coming up as being there at all. ideas?

farslayer 01-13-2009 11:16 PM

how can the driver be fine if the card isn't coming up ?

I prefer not to use a shim (ndiswrapper) if a native Linux driver is available. to each his own.

Best of luck.

pwd_pwd_omg_pwd 01-14-2009 07:04 AM

Thats what was confusing me. But regardless of any driver issues, is there something i need to do to have the hardware recognised in the first place?

farslayer 01-14-2009 10:29 AM

if you type lspci at the command prompt it should display a list of hardware in your machine. One of the items in the list should be your wireless card. If it's there in the list it has been recognized. You then need to install a driver and configure the card.

No matter hat method you use ndiswrapper or the Linux Driver you still need to ad the interface to your configuration file. So you are running Ubuntu, Fedora, Suse, Other ? (update your profile to show your Distro, or mention it in your posts.)

Most distros will allow you to configure a working Wireless card with Network-manager kwifi-manager, wicd, etc..

Code:

RTL8185 Linux Driver v1027.0823.2007 for linux kernel 2.6

  - Support Client mode for either infrastructure or adhoc mode
  - Support WEP and WPAPSK/WPA2PSK connection

===============================================================================================
< Component >
The driver is composed of several parts:
    (1)source code
        rtl8185.tar.gz
        stack.tar.gz

    (2)Script ot build the modules
        makedrv

    (3)Script to load/unload modules
        wlan0up
        wlan0down

    (4)Script and configuration for DHCP
        wlan0dhcp
        ifcfg-wlan0

    (5)Supplicant source code
        wpa_supplicant-0.4.9.tar.gz
           
    (6)Example of supplicant configuration file
        wpa1.conf


< Installation >
Running the scripts can finish all operations of building up modules from source code and start the nic:

        (1)Build up the driver from the source code
                ./makedrv

            (2)Load the driver module to kernel and start up nic
                    ./wlan0up

          (if "insmod: error inserting 'r8180.ko': -File exists." met,
                ./wlan0rmv
                ./wlan0down
                ./wlan0up
            should be OK.
          )
        (3)Refer to < Set wireless lan MIBs > to set Wireless LAN specific parameters.





< Set wireless lan MIBs >
This driver uses Wireless Extension as an interface allowing you to set
Wireless LAN specific parameters.

Current driver supports "iwlist" to show the device status of nic

        iwlist wlan0 [parameters]
where

        parameter explaination              [parameters]   
        -----------------------            ------------- 
        Show available chan and freq        freq / channel 
        Show and Scan BSS and IBSS        scan[ning]         
        Show supported bit-rate        rate / bit[rate]       
        Show Power Management mode      power           

For example:

        iwlist wlan0 channel
        iwlist wlan0 scan
        iwlist wlan0 rate
        iwlist wlan0 power


Driver also supports "iwconfig", manipulate driver private ioctls, to set MIBs.

        iwconfig wlan0 [parameters] [val]
where

        parameter explaination      [parameters]                [val] constraints
        -----------------------    -------------              ------------------
        Connect to AP by address    ap                              [essid]
        Set the essid, join (I)BSS  essid                            [mac_addr]
        Set operation mode          mode                          {Managed|Ad-hoc}
        Set keys and security mode  key / enc[ryption]          {N|open|restricted|off}


For example:

        iwconfig wlan0 ap XX:XX:XX:XX:XX:XX
        iwconfig wlan0 essid "ap_name"
        iwconfig wlan0 mode Ad-hoc
        iwconfig wlan0 mode essid "name" mode Ad-hoc
        iwconfig wlan0 key 0123456789 [2] open
        iwconfig wlan0 key off
        iwconfig wlan0 key restricted [3] 0123456789


< Getting IP address >
After start up the nic, the network needs to obtain an IP address before transmit/receive data.
This can be done by setting the static IP via "ifconfig wlan0 IP_ADDRESS" command, or using DHCP.

If using DHCP, setting steps is as below:
       
        (1)connect to an AP via "iwconfig" settings
                iwconfig wlan0 essid [name]        or
                iwconfig wlan0 ap XX:XX:XX:XX:XX:XX

        (2)run the script which run the dhclient
                ./wlan0dhcp
          or
                dhcpcd wlan0
                      (Some network admins require that you use the
                      hostname and domainname provided by the DHCP server.
                      In that case, use
                dhcpcd -HD wlan0)



< WPAPSK >
WPA_SUPPLICANT help the network to communicate under the protection of WPAPSK mechanism
       
        (1)Unpack source code of WPA supplicant:
                tar -zxvf wpa_supplicant-0.4.9.tar.gz
                cd wpa_supplicant-0.4.9
       
        (2)Create .config file:
                cp defconfig .config
               
        (3)Edit .config file, uncomment the following line:
                #CONFIG_DRIVER_IPW=y.
               
        (4)Build WPA supplicant:
                make
       
        If make error for lack of <include/md5.h>, install the openssl lib:
        1. Install the openssl lib from corresponding installation disc:
            Fedora Core 2/3/4/5/6/7(openssl-0.9.71x-xx),
            Mandrake10.2/Mandriva10.2(openssl-0.9.7x-xmdk),
            Debian 3.1(libssl-dev), Suse 9.3/10.0/10.1(openssl_devl),
            Gentoo(dev-libs/openssl), etc.
        2. Download the openssl open source package from www.openssl.org, build and install it.
       
        (5)Edit wpa_supplicant.conf to set up SSID and its passphrase.
        For example, the following setting in "wpa1.conf" means SSID to join is "BufAG54_Ch6"
        and its passphrase is "87654321".

                network={
                        ssid="BufAG54_Ch6"
                        proto=WPA
                        key_mgmt=WPA-PSK
                        pairwise=CCMP TKIP
                        group=CCMP TKIP WEP104 WEP40
                        psk="87654321"
                        priority=2
                }
        Note: 1. proto=WPA for WPA, proto=RSN for WPA2.
              2. If you want to connect an AP which works under WPA2 mixed mode, you'd better
                use Realtek customed wpa_supplicant package.
       

        (6)Execute WPA supplicant (Assume 8185 and related modules had been loaded):
                ./wpa_supplicant -D ipw -c wpa1.conf -i wlan0 &


pwd_pwd_omg_pwd 01-15-2009 09:16 AM

I decided to take your advice and download a driver from realtek, which seems to be getting me closer seen as lspci gives:
00:09.0 Ethernet controller: Realtek Semiconducter Co., Ltd. RTH-8185 IEEE 802.11a/b/g Wireless LAN Controller (rev 20)
but still nothing. iwconfig still says nothing other that "no wireless extension" for everything as above.

Didier Spaier 01-15-2009 10:02 AM

Please send, in output of "lspci -v", the block of information about your card, so we can see info about kernel driver in use and module(s) for it.

farslayer 01-15-2009 11:09 AM

when you issue the command ./wlan0up as directed in the how-to does it give you any feedback or errors, show anything on the screen at all ?

pwd_pwd_omg_pwd 01-19-2009 09:54 AM

Cheers for all the help guys.
my lspci -v gives:
00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge
Subsystem: ASUSTeK Computer Inc. Unknown device 8118
Flags: bus master, 66MHz, medium devsel, latency 8
Memory at e0000000 (32-bit, prefetchable) [size=64M]
Capabilities: [80] AGP version 3.5
Capabilities: [c0] Power Management version 2

00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: e8000000-e9ffffff
Prefetchable memory behind bridge: e4000000-e7ffffff
Capabilities: [80] Power Management version 2

00:08.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) (prog-if 10 [OHCI])
Subsystem: AFAVLAB Technology Inc Unknown device 3044
Flags: bus master, medium devsel, latency 32, IRQ 17
Memory at eb101000 (32-bit, non-prefetchable) [size=2K]
I/O ports at c000 [size=128]
Capabilities: [50] Power Management version 2

00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller (rev 20)
Subsystem: Realtek Semiconductor Co., Ltd. RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at c400 [size=256]
Memory at eb102000 (32-bit, non-prefetchable) [size=512]
Capabilities: [50] Power Management version 2

00:0a.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 08)
Subsystem: Intel Corporation EtherExpress PRO/100+ Management Adapter
Flags: bus master, medium devsel, latency 32, IRQ 16
Memory at eb100000 (32-bit, non-prefetchable) [size=4K]
I/O ports at c800 [size=64]
Memory at eb000000 (32-bit, non-prefetchable) [size=1M]
[virtual] Expansion ROM at 20000000 [disabled] [size=1M]
Capabilities: [dc] Power Management version 2

00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. A7V8X-X motherboard
Flags: bus master, medium devsel, latency 32, IRQ 18
I/O ports at cc00 [size=32]
Capabilities: [80] Power Management version 2

00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. A7V8X-X motherboard
Flags: bus master, medium devsel, latency 32, IRQ 18
I/O ports at d000 [size=32]
Capabilities: [80] Power Management version 2

00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. A7V8X-X motherboard
Flags: bus master, medium devsel, latency 32, IRQ 18
I/O ports at d400 [size=32]
Capabilities: [80] Power Management version 2

00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. A7V8X-X motherboard rev 1.01
Flags: bus master, medium devsel, latency 32, IRQ 18
Memory at eb103000 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2

00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
Subsystem: ASUSTeK Computer Inc. A7V8X-X motherboard
Flags: bus master, stepping, medium devsel, latency 0
Capabilities: [c0] Power Management version 2

00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: ASUSTeK Computer Inc. A7V8X-X motherboard rev. 1.01
Flags: bus master, medium devsel, latency 32, IRQ 20
[virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
[virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
[virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
[virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
I/O ports at d800 [size=16]
Capabilities: [c0] Power Management version 2

00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/K8V Deluxe motherboard (ADI AD1980 codec [SoundMAX])
Flags: medium devsel, IRQ 21
I/O ports at dc00 [size=256]
Capabilities: [c0] Power Management version 2

00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
Subsystem: ASUSTeK Computer Inc. Unknown device 80ff
Flags: bus master, medium devsel, latency 32, IRQ 19
I/O ports at e400 [size=256]
Memory at eb104000 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 2

01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video (rev 01) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Unknown device 8118
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 17
Memory at e4000000 (32-bit, prefetchable) [size=64M]
Memory at e8000000 (32-bit, non-prefetchable) [size=16M]
[virtual] Expansion ROM at e9000000 [disabled] [size=64K]
Capabilities: [60] Power Management version 2
Capabilities: [70] AGP version 2.0



I hope that clears something up. Ive tried the howto, but cant get past the wlan0up command- "command not found"
I really appreciate the help guys

Didier Spaier 01-19-2009 10:14 AM

Quote:

Originally Posted by pwd_pwd_omg_pwd (Post 3413786)
I hope that clears something up.

Yes it does. Your wireless PCI card show on "lspci -v" output:
Code:

00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller (rev 20)
Subsystem: Realtek Semiconductor Co., Ltd. RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at c400 [size=256]
Memory at eb102000 (32-bit, non-prefetchable) [size=512]
Capabilities: [50] Power Management version 2

But we should see information about kernel drivers in use and kernel modules ?? Please try 'lspci -k'.

EDIT may be you don't have a 2.6 kernel; this could explain why we don't get info about drivers and modules. So please send output of 'uname -a' too.

pwd_pwd_omg_pwd 01-19-2009 11:17 AM

So it knows the wireless card is there but not being recognised yeah?

uname -a gives:

Quote:

Linux daniel-desktop 2.6.24-22-generic #1 SMP Mon Nov 24 18:32:42 UTC 2008 i686 GNU/Linux
but when i try lspci -k it says that -k is an invalid option.
thanks

farslayer 01-19-2009 11:39 AM

Quote:

cant get past the wlan0up command- "command not found"
well the command is ./wlan0up not wlan0up and you must be in the directory that contains the script in order to run it with that command..

find / -name wlan0up

I do believe the script you are supposed to run, is what loads the driver modules for the card. At least that's how the Directions read to me..

pwd_pwd_omg_pwd 01-19-2009 12:00 PM

still no luck on the wlan0up front (or the ./wlan0up front). Find doesnt bring up anything. do you know where abouts to look as i'll trail all the files on the machine if it gets this fixed!

Didier Spaier 01-19-2009 02:06 PM

On my distro, the 'lspci' command is included in pciutils-2.2.10 package and I do have access to 'lspci -k', provided I type it as root.

May be you could look in lspci's manual (man lspci) to know which options are available on yours system in order to know drivers in use and kernel modules available for your card.


All times are GMT -5. The time now is 07:20 AM.