Bug 14221 - Ralink rt2800pci WLAN connection is not starting on boot
Summary: Ralink rt2800pci WLAN connection is not starting on boot
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2014-10-02 18:48 CEST by diego w
Modified: 2015-12-19 07:16 CET (History)
4 users (show)

See Also:
Source RPM: systemd?, drakx-net
CVE:
Status comment:


Attachments
dmesg of bootup incl. rmmod and modprobe of rt2800pci after bluetooth msgs at around 53 (54.36 KB, text/plain)
2014-10-02 19:10 CEST, diego w
Details

Description diego w 2014-10-02 18:48:16 CEST
for a couple of days my ralink rt2790 mini pci express card won't automatically start up the connection at boot anymore. until yesterday I could just open the network center and connect, but now it is impossible to scan networks (no error in GUI displayed, both iw and iwlist produce an error code (I will add this after the next reboot together with a fresh dmesg).

the workaround is:

rmmod rt2800pci
modprobe rt2800pci

this enables scanning and bringing up the connection.

lspci -v is:

01:00.0 Network controller: Ralink corp. RT2790 Wireless 802.11n 1T/2R PCIe
        Subsystem: Ralink corp. RT2790 Wireless 802.11n 1T/2R PCIe
        Physical Slot: eeepc-wifi
        Flags: bus master, fast devsel, latency 0, IRQ 19
        Memory at f8000000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+
        Capabilities: [70] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Kernel driver in use: rt2800pci
        Kernel modules: rt2800pci
Comment 1 diego w 2014-10-02 19:10:07 CEST
Created attachment 5468 [details]
dmesg of bootup incl. rmmod and modprobe of rt2800pci after bluetooth msgs at around 53
Comment 2 diego w 2014-10-02 19:10:40 CEST
[root@localhost diego]# iwlist s
lo        Interface doesn't support scanning.

enp3s0    Interface doesn't support scanning.

wlp1s0    Interface doesn't support scanning : Operation not supported

[root@localhost diego]# iw dev wlp1s0 scan
command failed: Operation not supported (-95)
diego w 2014-10-02 19:16:04 CEST

CC: (none) => smiling.diego
Target Milestone: --- => Mageia 5
Source RPM: (none) => kernel, drakx-net

Comment 3 diego w 2014-10-04 03:14:40 CEST
oh that's embarassing...

I was playing with hostapd, it seems it gets started at boot, no wonder the wlan is not usable as a client at the same time.

Still the problem with the connection not coming up despite start on boot is ticked.

changed bug title accordingly.

Summary: Ralink rt2800pci stopped working in cauldron around mass rebuild => Ralink rt2800pci WLAN connection is not starting on boot

Comment 4 diego w 2014-10-07 00:48:02 CEST
I tried enabling wpa_supplicant.service:

#dmesg |grep wpa
[   13.753646] systemd[1]: Configuration file /usr/lib/systemd/system/wpa_supplicant.service is marked executable. Please remove executable permission bits. Proceeding anyway.


$ ps ax|grep wpa
  645 ?        Ss     0:00 /usr/sbin/wpa_supplicant -u -P /run/wpa_supplicant.pid -f /var/log/wpa_supplicant.log -c /etc/wpa_supplicant.conf

still no connection at bootup...

is there anything im missing?
diego w 2014-10-07 00:48:38 CEST

Source RPM: kernel, drakx-net => systemd?, drakx-net

Comment 5 Samuel Verschelde 2015-05-19 20:58:54 CEST
Hi, sorry that this bug was overlooked. Does it work in Mageia 5 RC or latest cauldron?

Keywords: (none) => NEEDINFO
CC: (none) => mageia, tmb
Target Milestone: Mageia 5 => ---

Comment 6 Marja Van Waes 2015-12-19 07:16:55 CET
7 months later, no reply, so closing as OLD

Please reopen if you see this happen again in a supported version of Mageia

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.