Description of problem: Since 06/12 kernel updates, I'm unable to start usb wireless device (rt2870) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
Modules loaded: [root@ts040 ~]# lsmod | grep rt2 rt2800usb 22543 0 rt2800lib 51743 1 rt2800usb crc_ccitt 12573 1 rt2800lib rt2x00usb 19779 1 rt2800usb rt2x00lib 47494 3 rt2800usb,rt2800lib,rt2x00usb mac80211 202034 3 rt2800lib,rt2x00usb,rt2x00lib cfg80211 179003 2 rt2x00lib,mac80211 usbcore 159868 10 rt2800usb,rt2x00usb,usbhid,uas,usb_storage,ehci_hcd,uhci_hcd lsusb: Bus 007 Device 002: ID 07d1:3c09 D-Link System DWA-140 RangeBooster N Adapter(rev.B1) [Ralink RT2870] /var/log/messages: Dec 7 09:18:01 ts040 ifplugd(wlan0)[1466]: Link beat lost. Dec 7 09:18:02 ts040 ifplugd(wlan0)[2684]: Link beat lost. Dec 7 09:18:02 ts040 ifplugd(wlan0)[1466]: Link beat detected. Dec 7 09:18:03 ts040 ifplugd(wlan0)[2684]: Link beat detected. Dec 7 09:18:05 ts040 kernel: cfg80211: Calling CRDA to update world regulatory domain Dec 7 09:18:05 ts040 kernel: cfg80211: World regulatory domain updated: Dec 7 09:18:05 ts040 kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Dec 7 09:18:05 ts040 kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 7 09:18:05 ts040 kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Dec 7 09:18:05 ts040 kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Dec 7 09:18:05 ts040 kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 7 09:18:05 ts040 kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 7 09:18:05 ts040 kernel: cfg80211: Calling CRDA for country: BR Dec 7 09:18:05 ts040 kernel: cfg80211: Regulatory domain changed to country: BR Dec 7 09:18:05 ts040 kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Dec 7 09:18:05 ts040 kernel: cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) Dec 7 09:18:05 ts040 kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) Dec 7 09:18:05 ts040 kernel: cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 7 09:18:05 ts040 kernel: cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 7 09:18:05 ts040 kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm) Dec 7 09:18:05 ts040 ifplugd(wlan0)[1466]: Link beat lost. Dec 7 09:18:06 ts040 ifplugd(wlan0)[2684]: Link beat lost. Dec 7 09:18:06 ts040 ifplugd(wlan0)[1466]: Link beat detected. repeats this block endlessly ifup: [root@ts040 ~]# ifup wlan0 Determining IP information for wlan0...PING 192.168.86.1 (192.168.86.1) 56(84) bytes of data. --- 192.168.86.1 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms failed.
Please ensure you have services mandi and avahi running, that you don't have package networkmanager (if needed remove with --nodeps), that /etc/sysconfig/network-scripts/ifcfg-wlan0 does not contain a line NM_CONTROLLED=yes # change to 'no' if 'yes' and provide please the output of the command rfkill list If needed unblock the device, see 'man rfkill'.
CC: (none) => dvgevers
Dec 7 09:45:36 ts040 rpm: [RPM] networkmanager-0.9.2.0-1.mga2.x86_64 removed Dec 7 09:45:57 ts040 kernel: usb 7-1: new high speed USB device number 4 using ehci_hcd Dec 7 09:45:58 ts040 kernel: usb 7-1: New USB device found, idVendor=07d1, idProduct=3c09 Dec 7 09:45:58 ts040 kernel: usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Dec 7 09:45:58 ts040 kernel: usb 7-1: Product: 802.11 n WLAN Dec 7 09:45:58 ts040 kernel: usb 7-1: Manufacturer: Ralink Dec 7 09:45:58 ts040 kernel: usb 7-1: SerialNumber: 1.0 Dec 7 09:45:58 ts040 kernel: usb 7-1: reset high speed USB device number 4 using ehci_hcd Dec 7 09:45:58 ts040 mtp-probe: checking bus 7, device 4: "/sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1" Dec 7 09:45:58 ts040 mtp-probe: bus: 7, device: 4 was not an MTP device Dec 7 09:45:58 ts040 kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready Dec 7 09:45:58 ts040 kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready Dec 7 09:45:58 ts040 ifplugd(wlan0)[17193]: ifplugd 0.28 initializing. Dec 7 09:45:58 ts040 ifplugd(wlan0)[17193]: Using interface wlan0/00:1C:F0:DB:6A:E0 with driver <rt2800usb> (version: 3.1.4-tmb-desktop-3.mga2) Dec 7 09:45:58 ts040 ifplugd(wlan0)[17193]: Using detection mode: SIOCETHTOOL Dec 7 09:45:58 ts040 ifplugd(wlan0)[17193]: Initialization complete, link beat not detected. Dec 7 09:46:00 ts040 kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Dec 7 09:46:01 ts040 ifplugd(wlan0)[17193]: Link beat detected. Dec 7 09:46:02 ts040 ifplugd(wlan0)[17193]: Executing '/etc/ifplugd/ifplugd.action wlan0 up'. Dec 7 09:46:03 ts040 dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67 Dec 7 09:46:06 ts040 dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67 Dec 7 09:46:06 ts040 dhclient: DHCPACK from 192.168.86.1 Dec 7 09:46:06 ts040 kernel: martian source 255.255.255.255 from 192.168.86.1, on dev wlan0 Dec 7 09:46:06 ts040 kernel: ll header: ff:ff:ff:ff:ff:ff:00:18:e7:fb:15:5d:08:00 Dec 7 09:46:06 ts040 NET[17376]: /sbin/dhclient-script : updated /etc/resolv.conf Dec 7 09:46:06 ts040 dhclient: bound to 192.168.86.99 -- renewal in 2147483648 seconds. Dec 7 09:46:06 ts040 ifplugd(wlan0)[17193]: client: Determining IP information for wlan0... done. Dec 7 09:46:06 ts040 vnstatd[1812]: SIGHUP received, flushing data to disk and reloading config. Dec 7 09:46:06 ts040 vnstat[17454]: Recarregando configuração vnstatd [ OK ] Dec 7 09:46:06 ts040 ifplugd(wlan0)[17193]: client: [ OK ]#015 Dec 7 09:46:06 ts040 ifplugd(wlan0)[17193]: Program executed successfully. [root@ts040 network-scripts]# rfkill list 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Now it's working fine. But... 1. networkmanager is automatically installed with task-gnome & task-gnome minimal 2. ifcfg-wlan0 had NO in NM_CONTROLLED Why this problem occurred if the interface was NOT in being controlled by networkmanager?
Dear Luiz: 1. You can put networkmanager in /etc/urpmi/skip.list 2. Please see Cauldron-dev ML. I dunno the why.
Too fast... I've rebooted the machine (with the device inserted) and the problem is still here. messages still shows the same as comment #1. rfkill now shows: [root@ts040 ~]# rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Maybe something with one of the various errors with systemctl during the initialization?
Hmmm. But you don't say if you use systemd or not.
No idea. How can I know if I am using or not? What I can say, for sure, is that systemctl is giving a lot of error messages during boot.
If you installed the kernel via rpm, urpmi or rpmdrake w/o changes to /boot/grub/menu.lst it should show up in: $ cat /proc/cmdline and you should have at least the packages: $ rpm -qa |grep systemd lib64systemd-daemon0-37-13.mga2 systemd-units-37-13.mga2 systemd-tools-37-13.mga2 systemd-37-13.mga2 systemd-sysvinit-37-13.mga2 lib64systemd-login0-37-13.mga2 Please compare (as root): # systemctl list-units and # systemctl list-units --all |grep wlan
[root@ts040 ~]# cat /proc/cmdline BOOT_IMAGE=linux root=UUID=34bfb3be-6b47-4390-9e47-80c6187dd699 resume=UUID=d7bd968e-e8d6-4e01-a107-8592af18a230 splash=silent init=/bin/systemd init=/bin/systemd vga=788 So... Yes. I'm using systemd. [root@ts040 ~]# rpm -qa |grep systemd systemd-sysvinit-37-13.mga2 systemd-tools-37-13.mga2 systemd-37-13.mga2 lib64systemd-login0-37-13.mga2 systemd-gtk-37-13.mga2 systemd-units-37-13.mga2 lib64systemd-daemon0-37-13.mga2 [root@ts040 ~]# systemctl list-units --all |grep wlan sys-devi...t-wlan0.device loaded active plugged DWA-140 RangeBooster N Adapter(rev.B1) [Ralink RT2870] The same problem with start wlan0 and tons of messages in /var/log/messages. But... If I unplug the device and then plug it again, all works fine.
I'm now at a point where I'm guessing, because I'm not an expert, but I would expect that if you boot and you have no wireless active, that lsmod will not show all modules you list in Comment #1: only after un- and replugging. In my experience there should be an alias for your device in /etc/modprobe.conf and/or /etc/modprobe.d/modprobe.conf (If the content of /etc/modprobe.conf is repeated in /etc/modprobe.d/*.conf, you can safely delete /etc/modprobe.conf, but it will soon be recreated - usually as a zero byte file - in Cauldron because it is till owned by module-init-tools). For example my laptop has quote ... alias wlan0 rtl8192se alias pci:v0000............................... rtl8192se unquote and systemctl list-units shows a device in systemctl list-units like: sys-devi...t-wlan0.device loaded active plugged /sys/devices/pci0000:.........../net/wlan0 I dunno precisely how this was 'auto-magically' done by drakx / udev etcetera, pf someone else can help, but I guess it should be similar in your machine. @ bugsquad: can you add appropriate dev in cc ? thanks.
s/pf/ph
>I dunno precisely how this was 'auto-magically' done by drakx / udev etcetera, >pf someone else can help, but I guess it should be similar in your machine. >@ bugsquad: can you add appropriate dev in cc ? thanks. As you read bugs@, you are also in the bugsquad :D Thierry, idea ?
CC: (none) => thierry.vignaud
New systemd, old problem... The same messages of comment #1 on /var/log/messages, after reboot with the device plugged.
@Luiz: Did you look at /etc/modprobe.conf as per #c10 ?
My /etc/modprobe.conf has: alias wlan0 rt2800usb But.. Take a look at Bug 3719. The problem is systemd related. Anyway, thanks for your interest.
Depends on: (none) => 2120Source RPM: kernel-3.1.4-2.mga2.src.rpm => systemd
CC: (none) => marianne
@ Luiz Do you still have this bug in current cauldron / Mga2a3 ?
Keywords: (none) => NEEDINFOCC: (none) => marja11
what about this bug with systemd 40 ?
CC: (none) => dmorganec
@ Luiz, could you please reply to the previous questions? (please answer for systemd 43, too) If you won't reply within two weeks from now, I will have to close this bug as OLD. Thank you.
Blocks: (none) => 5015
closing as told in comment #18 Please reopen if you have more infos to provide.
Status: NEW => RESOLVEDResolution: (none) => OLD