Sabayon Community

by **freeallbadgers** » Wed Aug 08, 2007 2:35

Ok, the rt2500 is recognised as wlan0 at login. Knetwork manager see's no AP's, even tho there are 3 near me including my own.

Ive tried connecting via knetworkmanager = no joy
Ive tried connecting via net-setup = no joy
Set it up manually i.e. ifconfig etc, route etc, iwconfig and adding the essid details manually still no joy.

Code: Select all: iwconfig lo no wireless extensions. eth0 no wireless extensions. wmaster0 no wireless extensions. wlan0 IEEE 802.11g ESSID:"FuckOffNoseyCunts" Mode:Ad-Hoc Frequency:2.422 GHz Cell: Not-Associated Retry min limit:7 RTS thr:off Fragment thr=2346 B Encryption key:6E69-7665-6B77-6869-7465-3132-33 Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0

I manually associated the cell of my ap's mac by using iwconfig wlan0 ap <A3:00 etc etc>, it didnt help.

dmesg

Code: Select all: [ 29.104795] ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 18 (level, low) -> IRQ 20 [ 29.104812] ohci_hcd 0000:00:1c.1: OHCI Host Controller [ 29.104848] ohci_hcd 0000:00:1c.1: new USB bus registered, assigned bus number 3 [ 29.104871] ohci_hcd 0000:00:1c.1: irq 20, io mem 0xf8003000 [ 29.157994] Device driver usbdev3.1_ep00 lacks bus and class support for being resumed. [ 29.158011] usb usb3: configuration #1 chosen from 1 choice [ 29.158448] hub 3-0:1.0: USB hub found [ 29.158465] hub 3-0:1.0: 3 ports detected [ 29.259146] Device driver usbdev3.1_ep81 lacks bus and class support for being resumed. [ 29.259357] ACPI: PCI Interrupt 0000:00:15.0[A] -> GSI 18 (level, low) -> IRQ 20 [ 29.280759] Device driver phy0 lacks bus and class support for being resumed. [ 29.281004] Device driver wmaster0 lacks bus and class support for being resumed. [ 29.362124] wmaster0: Selected rate control algorithm 'simple' [ 29.379580] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel. [ 29.384709] [fglrx] Maximum main memory to use for locked dma buffers: 795 MBytes. [ 29.384729] [fglrx] module loaded - fglrx 8.38.6 [Jun 22 2007] on minor 0 [ 29.398806] Device driver wlan0 lacks bus and class support for being resumed. [ 29.398860] ali1535_smbus 0000:00:1e.1: ALI1535_smb region uninitialized - upgrade BIOS? [ 29.398863] ali1535_smbus 0000:00:1e.1: ALI1535 not detected, module not inserted. [ 29.398879] PCI driver ali1535_smbus lacks driver specific resume support. [ 29.438239] ali15x3_smbus 0000:00:1e.1: ALI15X3_smb region uninitialized - upgrade BIOS or use force_addr=0xaddr [ 29.438244] ali15x3_smbus 0000:00:1e.1: ALI15X3 not detected, module not inserted. [ 29.438264] PCI driver ali15x3_smbus lacks driver specific resume support. [ 29.454285] alim7101_wdt: Steve Hill <steve@navaho.co.uk>. [ 29.454296] alim7101_wdt: ALi 1543 South-Bridge not present - WDT not set [ 29.519505] usb 3-1: new full speed USB device using ohci_hcd and address 2 [ 29.710379] Device driver usbdev3.2_ep00 lacks bus and class support for being resumed. [ 29.710389] usb 3-1: configuration #1 chosen from 1 choice [ 29.713371] Device driver usbdev3.2_ep81 lacks bus and class support for being resumed. [ 29.713446] Device driver usbdev3.2_ep05 lacks bus and class support for being resumed. [ 29.713475] Device driver usbdev3.2_ep85 lacks bus and class support for being resumed. [ 30.030212] NET: Registered protocol family 8 [ 30.030216] NET: Registered protocol family 20 [ 30.043071] Device driver usbdev3.2_ep06 lacks bus and class support for being resumed. [ 30.043210] Device driver usbdev3.2_ep07 lacks bus and class support for being resumed. [ 30.043345] Device driver usbdev3.2_ep87 lacks bus and class support for being resumed. [ 30.698652] usb 3-1: reset full speed USB device using ohci_hcd and address 2 [ 30.881050] Device driver usbdev3.2_ep81 lacks bus and class support for being resumed. [ 30.884341] Device driver usbdev3.2_ep06 lacks bus and class support for being resumed. [ 30.884501] Device driver usbdev3.2_ep07 lacks bus and class support for being resumed. [ 30.884646] Device driver usbdev3.2_ep87 lacks bus and class support for being resumed. [ 30.887202] Device driver usbdev3.2_ep05 lacks bus and class support for being resumed. [ 30.887366] Device driver usbdev3.2_ep85 lacks bus and class support for being resumed. [ 30.887448] usbcore: registered new interface driver speedtch [ 30.887452] USB driver speedtch lacks resume support. [ 30.888331] Device driver 3-1:1.0 lacks bus and class support for being resumed. [ 30.943591] Device driver 3-1:1.0 lacks bus and class support for being resumed. [ 30.968878] Device driver 3-1:1.0 lacks bus and class support for being resumed. [ 30.985687] speedtch 3-1:1.0: speedtch_find_firmware: no stage 1 firmware found! [ 31.752715] EXT3 FS on sda3, internal journal [ 32.062637] vboxdrv: Trying to deactivate NMI watchdog permanently... [ 32.062642] vboxdrv: Successfully done. [ 32.821902] Adding 923728k swap on /dev/disk/by-uuid/60e5d5df-fd16-45c0-b172-c4f9b3d58ee6. Priority:-1 extents:1 across:923728k [ 54.284797] fbsplash: console 1 using theme 'sabayon' [ 54.291421] fbsplash: switched splash state to 'on' on console 1 [ 54.323188] fbsplash: console 2 using theme 'sabayon' [ 54.330008] fbsplash: switched splash state to 'on' on console 2 [ 54.352293] fbsplash: console 3 using theme 'sabayon' [ 54.363206] fbsplash: switched splash state to 'on' on console 3 [ 54.385077] fbsplash: console 4 using theme 'sabayon' [ 54.396145] fbsplash: switched splash state to 'on' on console 4 [ 54.418053] fbsplash: console 5 using theme 'sabayon' [ 54.429040] fbsplash: switched splash state to 'on' on console 5 [ 54.441093] fbsplash: console 11 using theme 'sabayon' [ 54.447785] fbsplash: switched splash state to 'on' on console 11 [ 56.721424] ACPI: PCI Interrupt 0000:01:05.0[A] -> GSI 17 (level, low) -> IRQ 19 [ 59.130013] [fglrx] total GART = 130023424 [ 59.130023] [fglrx] free GART = 114032640 [ 59.130026] [fglrx] max single GART = 114032640 [ 59.130029] [fglrx] total LFB = 134217728 [ 59.130031] [fglrx] free LFB = 99340288 [ 59.130034] [fglrx] max single LFB = 99340288 [ 59.130036] [fglrx] total Inv = 0 [ 59.130038] [fglrx] free Inv = 0 [ 59.130041] [fglrx] max single Inv = 0 [ 59.130043] [fglrx] total TIM = 0 [ 67.278421] uli526x: eth0 NIC Link is Down [ 69.354138] atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly. [ 70.354389] atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly. [ 70.355857] psmouse.c: TouchPad at isa0060/serio3/input0 lost synchronization, throwing 2 bytes away. [ 264.608320] Clocksource tsc unstable (delta = -182103654 ns) [ 448.546733] usb 3-1: USB disconnect, address 2 [ 480.401849] usb 1-3: new high speed USB device using ehci_hcd and address 3 [ 480.519805] Device driver usbdev1.3_ep00 lacks bus and class support for being resumed. [ 480.519828] usb 1-3: configuration #1 chosen from 1 choice [ 480.531773] scsi2 : SCSI emulation for USB Mass Storage devices [ 480.531821] Device driver host2 lacks bus and class support for being resumed. [ 480.532646] Device driver usbdev1.3_ep81 lacks bus and class support for being resumed. [ 480.532704] Device driver usbdev1.3_ep02 lacks bus and class support for being resumed. [ 480.534083] usb-storage: device found at 3 [ 480.534092] usb-storage: waiting for device to settle before scanning [ 485.531755] usb-storage: device scan complete [ 485.532096] Device driver target2:0:0 lacks bus and class support for being resumed. [ 485.532747] scsi 2:0:0:0: Direct-Access USB Flash Memory 6.50 PQ: 0 ANSI: 0 CCS [ 485.532995] Device driver target2:0:1 lacks bus and class support for being resumed. [ 485.533224] Device driver target2:0:2 lacks bus and class support for being resumed. [ 485.533440] Device driver target2:0:3 lacks bus and class support for being resumed. [ 485.533654] Device driver target2:0:4 lacks bus and class support for being resumed. [ 485.533885] Device driver target2:0:5 lacks bus and class support for being resumed. [ 485.534168] Device driver target2:0:6 lacks bus and class support for being resumed. [ 485.534384] Device driver target2:0:7 lacks bus and class support for being resumed. [ 485.537087] sd 2:0:0:0: [sdb] 1952767 512-byte hardware sectors (1000 MB) [ 485.537964] sd 2:0:0:0: [sdb] Write Protect is off [ 485.537973] sd 2:0:0:0: [sdb] Mode Sense: 45 00 00 08 [ 485.537979] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 485.539846] sd 2:0:0:0: [sdb] 1952767 512-byte hardware sectors (1000 MB) [ 485.540580] sd 2:0:0:0: [sdb] Write Protect is off [ 485.540588] sd 2:0:0:0: [sdb] Mode Sense: 45 00 00 08 [ 485.540594] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 485.540808] sdb: unknown partition table [ 485.544887] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 485.545650] sd 2:0:0:0: Attached scsi generic sg2 type 0 [ 222.828943] usb 1-3: reset high speed USB device using ehci_hcd and address 3 [ 222.946369] Device driver usbdev1.3_ep81 lacks bus and class support for being resumed. [ 222.946398] Device driver usbdev1.3_ep02 lacks bus and class support for being resumed. [ 681.437476] wlan0: Trigger new scan to find an IBSS to join [ 409.081932] wlan0: Creating new IBSS network, BSSID 5a:0b:0c:d9:7d:d3 [ 409.081959] wlan0: Configured IBSS beacon template based on scan results [ 851.703970] wlan0: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge) [ 884.947956] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate

tail -n 50 /var/log/messages

Code: Select all: Aug 8 02:34:11 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Aug 8 02:34:11 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Aug 8 02:34:11 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Aug 8 02:34:11 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Aug 8 02:34:11 localhost NetworkManager: <info> Activation (wlan0/wireless): access point 'FuckOffNoseyCunts' is encrypted, and a key exists. No new key needed. Aug 8 02:34:13 localhost NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0 wext /var/run/wpa_supplicant ' Aug 8 02:34:13 localhost NetworkManager: <info> SUP: response was 'OK' Aug 8 02:34:13 localhost NetworkManager: <info> SUP: sending command 'AP_SCAN 1' Aug 8 02:34:13 localhost NetworkManager: <info> SUP: response was 'OK' Aug 8 02:34:13 localhost NetworkManager: <info> SUP: sending command 'ADD_NETWORK' Aug 8 02:34:13 localhost NetworkManager: <info> SUP: response was '0' Aug 8 02:34:13 localhost NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 4675636b4f66664e6f73657943756e7473' Aug 8 02:34:13 localhost NetworkManager: <info> SUP: response was 'OK' Aug 8 02:34:13 localhost NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 scan_ssid 1' Aug 8 02:34:13 localhost NetworkManager: <info> SUP: response was 'OK' Aug 8 02:34:13 localhost NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE' Aug 8 02:34:13 localhost NetworkManager: <info> SUP: response was 'OK' Aug 8 02:34:13 localhost NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 wep_key0 <key>' Aug 8 02:34:13 localhost NetworkManager: <info> SUP: response was 'OK' Aug 8 02:34:13 localhost NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 wep_tx_keyidx 0' Aug 8 02:34:13 localhost NetworkManager: <info> SUP: response was 'OK' Aug 8 02:34:13 localhost NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0' Aug 8 02:34:13 localhost NetworkManager: <info> SUP: response was 'OK' Aug 8 02:34:13 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Aug 8 02:34:16 localhost NetworkManager: <info> Old device 'wlan0' activating, won't change. Aug 8 02:34:24 localhost NetworkManager: <info> Old device 'wlan0' activating, won't change. Aug 8 02:34:31 localhost NetworkManager: <info> Old device 'wlan0' activating, won't change. Aug 8 02:34:36 localhost NetworkManager: <info> Old device 'wlan0' activating, won't change. Aug 8 02:34:42 localhost NetworkManager: <info> Old device 'wlan0' activating, won't change. Aug 8 02:34:48 localhost NetworkManager: <info> Old device 'wlan0' activating, won't change. Aug 8 02:34:53 localhost NetworkManager: <info> Old device 'wlan0' activating, won't change. Aug 8 02:34:59 localhost NetworkManager: <info> Old device 'wlan0' activating, won't change. Aug 8 02:35:05 localhost NetworkManager: <info> Old device 'wlan0' activating, won't change. Aug 8 02:35:11 localhost NetworkManager: <info> Old device 'wlan0' activating, won't change. Aug 8 02:35:13 localhost NetworkManager: <info> Activation (wlan0/wireless): association took too long (>60s), asking for new key. Aug 8 02:35:13 localhost NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'FuckOffNoseyCunts'. Aug 8 02:35:23 localhost NetworkManager: <info> Activation (wlan0) New wireless user key for network 'FuckOffNoseyCunts' received. Aug 8 02:35:23 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Aug 8 02:35:23 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Aug 8 02:35:23 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Aug 8 02:35:23 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Aug 8 02:35:23 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Aug 8 02:35:23 localhost NetworkManager: <info> Activation (wlan0/wireless): access point 'FuckOffNoseyCunts' is encrypted, and a key exists. No new key needed. Aug 8 02:35:26 localhost NetworkManager: <info> Error opening supplicant global control interface. Aug 8 02:35:26 localhost NetworkManager: <WARN> real_act_stage2_config(): Activation (wlan0/wireless): couldn't connect to the supplicant. Aug 8 02:35:26 localhost NetworkManager: <info> Activation (wlan0) failure scheduled... Aug 8 02:35:26 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Aug 8 02:35:26 localhost NetworkManager: <info> Activation (wlan0) failed for access point (FuckOffNoseyCunts) Aug 8 02:35:26 localhost NetworkManager: <info> Activation (wlan0) failed. Aug 8 02:35:26 localhost NetworkManager: <info> Deactivating device wlan0.

Anyhoo, still love the distro, hope you can help to fix this or give me a few pointers.

Thanks in advance.

by **rikd** » Wed Aug 08, 2007 16:44

Seems like the NIC is working, just can't get it to assoc. with the WLAN.

What encryption are you using - WEP, WPA or none?

Does iwlist show any APs?
# iwlist wlan0 scan

You mention you've tried knetworkmanager, net-setup, and by hand - which of these methods do the logs correspond to?

On these:
Am assuming since the ESSID is there, you've tried to associate manually for the ifconfig output, but looks strange as the NIC is "Adhoc" mode not "Managed" which would be typical for an access point. Set this before attempting to associate via
# iwconfig wlan0 mode managed

For dmesg

[ 884.947956] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate

usually indicates a key or authentication method mismatch. Check your keys, etc.

The /var/log/messages output :

Aug 8 02:35:23 localhost NetworkManager: <info> Activation (wlan0/wireless): access point 'FuckOffNoseyCunts' is encrypted, and a key exists. No new key needed.
Aug 8 02:35:26 localhost NetworkManager: <info> Error opening supplicant global control interface.

Looks to me like NetworkManager has a configuration setting for the ESSID which has a WPA key associated with it - but then can't the key from wpa_supplicant. Does /etc/wpa_supplicant/wpa_supplicant.conf contain any valid keys?
[quickedit] Check out Topic http://www.sabayonlinux.org/forum/viewtopic.php?t=9297 and see if running wpa_supplicant helps

When trying the net-setup method did you first disable NetworkManager?
# /etc/init.d/NetworkManager stop
# /etc/init.d/dhcdbd stop

What did net-setup put in /etc/conf.d/net and /etc/conf.d/wireless?

Really need more info to progress further...[/url]

by **freeallbadgers** » Wed Aug 08, 2007 17:02

Seems like the NIC is working, just can't get it to assoc. with the WLAN.

What encryption are you using - WEP, WPA or none?

Does iwlist show any APs?
# iwlist wlan0 scan

Using WEP, even turned encryption off, still = nada

iwlist = nothing picked up

You mention you've tried knetworkmanager, net-setup, and by hand - which of these methods do the logs correspond to?

The ones i posted are for knetworkmanager , but i have had a look at all methods logs and are all similar.

Am assuming since the ESSID is there, you've tried to associate manually for the ifconfig output, but looks strange as the NIC is "Adhoc" mode not "Managed" which would be typical for an access point. Set this before attempting to associate via
# iwconfig wlan0 mode managed

erm thats because its an Ad-Hoc network, i doubt managed mode would be any help!

For dmesg
Quote:
[ 884.947956] wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate

usually indicates a key or authentication method mismatch. Check your keys, etc.

key is fine, as i said before even turned off encryption still no joy.

Looks to me like NetworkManager has a configuration setting for the ESSID which has a WPA key associated with it - but then can't the key from wpa_supplicant. Does /etc/wpa_supplicant/wpa_supplicant.conf contain any valid keys?
[quickedit] Check out Topic http://www.sabayonlinux.org/forum/viewtopic.php?t=9297 and see if running wpa_supplicant helps

It Doesnt

When trying the net-setup method did you first disable NetworkManager?
# /etc/init.d/NetworkManager stop
# /etc/init.d/dhcdbd stop

Yes.

by **Dark_MaGe** » Wed Aug 08, 2007 17:46

if you're going to connect to an "AP" you need to set your connection to managed mode not to "ad-hoc" that is a completely differenct connection, so give a

Code: Select all: ifconfig wlan0 down && iwconfig wlan0 mode managed

then try connect again with knetworkmanager, or assuming you're using wep key try using

Code: Select all: iwconfig wlan0 essid myessid channel numberofthechannel key s:myasciikey

by **rikd** » Wed Aug 08, 2007 17:50

Apologies - some more Qs...

Is it the legacy driver i.e. rt2500 or the new drivers rt2500pci or rt2500usb that you're using?
Legacy used to be ra0 not wlan0 -

If legacy what's in your /etc/Wireless/RT2500STA/RT2500STA.dat file?

might be worth turning on the debug in the driver - you'll get lots of data, but could be useful.
The TESTING file in the tar file from http://rt2x00.serialmonkey.com shows how

4. Ensure there are no compies of the module in memory.
ifconfig ra0 down
rmmod rt2500

5. Load the module with full debug enabled using the commands
modprobe rt2500 debug=1

by **freeallbadgers** » Wed Aug 08, 2007 18:01

Dark Mage, it was set as managed as default, as i said in my original post there is three Ap's around here and the card see's none of them. My network is ad-hoc - doesnt work(in ad-hoc mode) i, used a neighbours (managed AP, with permission - card set in managed mode) and it still doesnt work.

The card does not see any Ap's/networks eg absolutely no signals detected.

I tried your code Dark Mage even tho i knew it was in vain as ive tried every possible connatation imaginable.

Ive been bringing this card up manually since 3.26, i think i know how to do it by now, what im looking for is some new insight.

Thanks in advance.

by **freeallbadgers** » Wed Aug 08, 2007 18:03

Apologies - some more Qs...

Is it the legacy driver i.e. rt2500 or the new drivers rt2500pci or rt2500usb that you're using?
Legacy used to be ra0 not wlan0 -

If legacy what's in your /etc/Wireless/RT2500STA/RT2500STA.dat file?

might be worth turning on the debug in the driver - you'll get lots of data, but could be useful.
The TESTING file in the tar file from http://rt2x00.serialmonkey.com shows how

Yeah i know the legacy drivers denoted the card as ra0, ive been using it since sab 3.26 - they work fine (well with some tweaking)

It seems its the new pci drivers causing the probs.

by **rikd** » Wed Aug 08, 2007 18:47

Which drive & which version are you using?

by **freeallbadgers** » Wed Aug 08, 2007 19:10

hard to say just now, im away from my sabayon box, i guess the driver and version will be in the release notes for 3.4a, I'm sure someone will know.

by **federoco** » Thu Aug 09, 2007 9:38

There is the same problem with rt2500 pci, on sb 4,4 e sb 4,4a versions. Works in the loop 3 version.

The rt2500 usb works perfectly, but the pci doesn

Can i unmerge the new pci rt2500 driver and install the loop3 one?. If that its possible, please tell me how, i 'm an absolute newbie :lol:

Sabayon Community

Ralink rt2500 in 3.4a doesnt seem to work [Solved]

Ralink rt2500 in 3.4a doesnt seem to work [Solved]

Who is online