Cant find network folder

Tnx novsan… There are troubles yea. Cause the hardware is found in Yast. But there is no interface configured for this device…

In the hardware manager I can c the driver is not active.
How can I reload the drivers -> rt2800sta and rt2x00sta? I cant find the directories.

How can I reload the drivers -> rt2800sta and rt2x00sta? I cant find the directories.

Hi!
You need remove lines:

blacklist rt2800sta
blacklist rt2x00sta

at the end of the file /etc/modprobe.d/50-blacklist.conf
After that you can load these drivers:

modprobe rt2800sta
modprobe rt2x00sta

And another question. There is already compiled rt2870sta.ko module in the /lib/modules/2.6.*/kernel/drivers/staging/ directory. Did you tried use it before than you’ve got compiled your own driver? It needs some additional firmware.
Did you install it?

Sorry, it’s my fault - there isn’t rt2800sta and rt2x00sta modules. There are rt2800usb and rt2x00usb modules :wink:

Hi novsan, I only used my own rt2870sta.ko build.

But now I c too it was already there in the kernel. I check for the firmware. :wink:
But why it need firmware. Isnt the firmware running on the USB stick?

No, firmware is loaded by driver, i think.
You can download firmware ralink-firmware-1.1-1.1.noarch.rpm package here : Index of /repositories/driver:/wireless/11.2-update/noarch
Or from ralinktech site: Ralink corp.
If you will download from ralinktech site - unpuck archive and copy rt2870.bin file in /lib/firmware directory.
After that, try to reload rt2870sta driver.

Tnx novsan… IOU !

novsan… I did all the instructions but still no wlan interface.
I run collectNWData and this is the result->



collectNWData.sh V0.6.3.4 (Rev: 1.220, Build: 2010/04/05 13:36:33 UTC)
— Which type of your network connection should be tested?
— (2) Wireless connection (WLAN)
— What’s the type of networktopology?
— (1) WLAN access point <—> LinuxClient
— On which host is the script executed?
— (1) LinuxClient

— NWEliza is analyzing the system for common network configuration errors …

!!! CND0110E: For the selected connection type there was no active network interface found on your system
!!! CND0310W: Classic network configuration with ifup was detected. Configuration with knetworkmanager is much easier

— Go to http://www.linux-tips-and-tricks.de/CND#English to get more detailed instructions
— about the error/warning messages and how to fix the problems on your own.

— If you are unsuccessful then place the contents of file collectNWData.txt in the net
— (see http://www.linux-tips-and-tricks.de/CND_UPL#English for links)
— and then paste the nopaste link on your favorite Linux forum.

==================================================================================================================

*** uname -a
Linux linux-y4n6 2.6.31.5-0.1-desktop #1 SMP PREEMPT 2009-10-26 15:49:03 +0100 i686 athlon i386 GNU/Linux

*** cat /etc/-_]release || cat /etc/-_]version
/etc/SuSE-release
openSUSE 11.2 (i586)
VERSION = 11.2

*** cat /etc/resolv | grep -i “nameserver”

*** cat /etc/hosts
127.0.0.1 localhost
127.0.0.2 linux-y4n6.site linux-y4n6

*** route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo

*** ifconfig
eth0 Link encap:Ethernet HWaddr ##:##:##:##:##:#1
UP BROADCAST MULTICAST MTU:1500 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:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:26 Base address:0x2000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:130 errors:0 dropped:0 overruns:0 frame:0
TX packets:130 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8476 (8.2 Kb) TX bytes:8476 (8.2 Kb)

*** ping tests
connect: Network is unreachable
Ping of 195.135.220.3 failed
ping: unknown host www.suse.de
Ping of www.suse.de failed

*** dhcpcd-test

*** lspci
00:06.0 Ethernet controller [0200]: nVidia Corporation MCP65 Ethernet [10de:0450] (rev a3)

*** lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 07d1:3c0a D-Link System
Bus 001 Device 007: ID 1307:0165 Transcend Information, Inc. 2GB/4GB Flash Drive
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c01d Logitech, Inc. MX510 Optical Mouse

*** hwinfo (filtered)
16: PCI 06.0: 0200 Ethernet controller
Model: “nVidia MCP65 Ethernet”
Vendor: pci 0x10de “nVidia Corporation”
Device: pci 0x0450 “MCP65 Ethernet”
SubVendor: pci 0x1458 “Giga-byte Technology”
SubDevice: pci 0xe000
Driver: “forcedeth”
Driver Modules: “forcedeth”
Device File: eth0
Link detected: no
Driver Status: forcedeth is active
Driver Activation Cmd: “modprobe forcedeth”

*** lsmod # (filtered)
| af_packet | amd74xx | cfg80211 | cpufreq_conservative| cpufreq_powersave |
| cpufreq_userspace| crc16 | crc_ccitt | edd | fat |
| floppy | forcedeth | fuse | i2c_nforce2 | ide_cd_mod |
| ide_gd_mod | ieee1394 | input_polldev | jbd2 | k8temp |
| mac80211 | nls_cp437 | nls_iso8859_1 | ohci1394 | pata_amd |
| powernow_k8 | ppdev | rfkill | rt2800usb | rt2x00lib |
| rt2x00usb | sg | snd_hda_codec | snd_hda_codec_realtek| snd_hda_intel |
| snd_hwdep | snd_seq_device | sr_mod | st | thermal |
| thermal_sys | vfat |

*** cat /etc/sysconfig/network/ifcfg-[earwd]*
— /etc/sysconfig/network/ifcfg-eth0
BOOTPROTO=‘dhcp’
BROADCAST=’’
ETHTOOL_OPTIONS=’’
IPADDR=’’
MTU=’’
NAME=‘MCP65 Ethernet’
NETMASK=’’
NETWORK=’’
REMOTE_IPADDR=’’
STARTMODE=‘auto’
USERCONTROL=‘no’

*** iwconfig
lo no wireless extensions.
eth0 no wireless extensions.

*** Actual date for bias of following greps
20:42:30 2010-03-27

*** grep -i radio /var/log/messages* | tail -n 5

*** dmesg | grep -i radio | tail -n 5

*** tail -n 300 /var/log/messages* | /bin/grep -i firmware | tail -n 5

*** ls /lib/firmware/*
| 2.6.31.5-0.1-desktop | 3com | acenic | adaptec |
| advansys | agere_ap_fw.bin | agere_sta_fw.bin | ar9170-1.fw |
| ar9170-2.fw | atmsar11.fw | av7110 | bnx2 |
| bnx2x-e1-4.8.53.0.fw | bnx2x-e1h-4.8.53.0.fw | cis | cpia2 |
| cxgb3 | dabusb | dsp56k | dvb-fe-xc5000-1.6.114.fw |
| e100 | edgeport | emi26 | emi62 |
| ess | i2400m-fw-usb-1.3.sbcf | i2400m-fw-usb-1.4.sbcf | intelliport2.bin |
| iwlwifi-1000-3.ucode | iwlwifi-3945-2.ucode | iwlwifi-4965-2.ucode | iwlwifi-5000-1.ucode |
| iwlwifi-5000-2.ucode | iwlwifi-5150-2.ucode | kaweth | keyspan |
| keyspan_pda | korg | libertas | LICENCE.agere |
| LICENCE.atheros_firmware| LICENCE.i2400m | LICENCE.iwlwifi_firmware| LICENCE.libertas |
| LICENCE.mwl8k | LICENCE.qla2xxx | LICENCE.ralink-firmware.txt| LICENCE.xc5000 |
| LICENSE.ralink-firmware.txt| mts_cdma.fw | mts_edge.fw | mts_gsm.fw |
| mwl8k | myricom | ositech | ql2100_fw.bin |
| ql2200_fw.bin | ql2300_fw.bin | ql2322_fw.bin | ql2400_fw.bin |
| ql2500_fw.bin | qlogic | rt2561.bin | rt2561s.bin |
| rt2661.bin | rt2860.bin | rt2870.bin | rt73.bin |
| sb16 | slicoss | sun | sxg |
| tehuti | ti_3410.fw | ti_5052.fw | tigon |
| tr_smctr.bin | ttusb-budget | usbdux | usbduxfast_firmware.bin |
| usbdux_firmware.bin | v4l-cx231xx-avcore-01.fw| v4l-cx23418-apu.fw | v4l-cx23418-cpu.fw |
| v4l-cx23418-dig.fw | v4l-cx23885-avcore-01.fw| v4l-cx23885-enc.fw | v4l-cx25840.fw |
| vicam | whiteheat.fw | whiteheat_loader.fw | yam |
| yamaha |

*** ndiswrapper -l
No ndiswrapper module loaded

*** Active processes
wpa_supplicant:NO knetworkmanager:NO nm-applet:NO

*** egrep -i “persistent|networkmanager” /etc/sysconfig/network/config | grep -v “^#|^$”
NETWORKMANAGER=“no”

*** grep ‘eth|ath|wlan|ra’ /etc/udev/rules.d/net_persistent /etc/udev/rules.d/persistent-net
/etc/udev/rules.d/70-persistent-net.rules:SUBSYSTEM==“net”, ACTION==“add”, DRIVERS=="?", ATTR{address}=="##:##:##:##:##:#1", ATTR{type}==“1”, KERNEL=="eth", NAME=“eth0”

*** grep -r ‘eth[0-10]|ath[0-10]|wlan[0-10]|ra[0-10]’ /etc/modprobe.*

*** iwlist scanning
No WLANs found

*** NWElizaStates
DI:0 AP:0 NI:1 cNI:1 NDIS:0 NIWL:0 IP6:0 KM:0 WLW:0 RTDT:SuSE



The firmware is an image. So it must reside in the Flash first time I boot the usb device. No? I cant belive it must be loaded everytime I boot my system.

On 04/19/2010 02:56 PM, In Control01 wrote:
>
> novsan… I did all the instructions but still no wlan interface.
> I run collectNWData and this is the result->

The script shows no hardware device.

You have done a lot of fooling around, yet I see no instance of you
looking at the ID codes for the device. If it is PCI, post the output of
‘/sbin/lspci -nnk’. If it is a USB deevice, then post the output of the
command ‘lsusb’. NOTE: We do not need the entire output - only the
section that describes your wireless device.

Hi Iwfinger,

This is my WLAN device->


Bus 001 Device 003: ID 07d1:3c0a D-Link System 

What interface it need?

On 04/19/2010 04:06 PM, In Control01 wrote:
>
> Hi Iwfinger,
>
> This is my WLAN device->
>
> Code:
> --------------------
>
> Bus 001 Device 003: ID 07d1:3c0a D-Link System
>
> --------------------

The driver for that device is rt2800usb, which is built into the kernel.
If you have blacklisted any rt2800 drivers, please revert those changes.
After you do that, issuing the command


sudo /sbin/modprobe -v  rt2800usb

should allow you to see the device with


/usr/sbin/iwconfig

You then need to check if firmware is available with


dmesg  |  egrep "firmware|rt2"

I am assuming you have openSUSE 11.2.

After firmware detection -> He write on command line:

phy0-> rt2800usb_init_eeprom: Error - Invalid RT chipset detected.
phy0-> rt2x00lib_probe_dev: Error - Failed to allocate device.

The phy, Its the physical adapter layer?

On 04/19/2010 05:16 PM, In Control01 wrote:
>
> After firmware detection -> He write on command line:
>
> phy0-> rt2800usb_init_eeprom: Error - Invalid RT chipset detected.
> phy0-> rt2x00lib_probe_dev: Error - Failed to allocate device.
>
> The phy, Its the physical adapter layer?

It is the hardware that implements the Physical Device Layer.

Was the firmware loaded correctly? I expect it may have been. With a
little more research, I see that although that ID is assigned to the
rt2800usb driver and the rt2870sta driver from the staging directory.
Please try the following:


sudo  /sbin/modprobe  -rv  rt2800usb
sudo  /sbin/modprobe  -v   rt2870sta

RA Link has really screwed up with their devices.

In_Control01. Did you removed your own rt2870sta compiled driver?

Thats true…

What is the difference between the usb and the sta?

And what is the correct device?

rt2800usb is open source implementaion, rt2870sta -third party from ralinktech.
And some question to you:
i assume that you have dlink dwa-140 usb dongle. Which hw version adapter is (A1,B1,B2)?

rt2800usb driver will not work with your device yet.

On 04/19/2010 05:16 PM, lwfinger wrote:
>Was the firmware loaded correctly? I expect it may have been. With a
>little more research, I see that although that ID is assigned to the
>rt2800usb driver and the rt2870sta driver from the staging directory.

How do u c the firmware is loaded correctly? Where is the staging directory?

directory is /lib/modules/$(uname -r)/kernel/drivers/staging/

novsan wrote
>i assume that you have dlink dwa-140 usb dongle. Which hw version adapter is (A1,B1,B2)?

Yes, DWA-140 usb device.
HW version B2.

Does Ralink make custom firmware for each vendor?

Seems, that dlink has line of adapters, which have same id, but some adapters needs rt2870sta driver, other rt3070sta driver.
I think you should use rt3070sta driver over rt2870sta module. Firmware is the same.