Hi all Running Fedora release 22 (Rawhide) 3.19.0-0.rc7.git3.1.fc22.armv7hl I find I have a problem with wlan0 becoming de-activated. Running headless, attempt to ssh to device. No response. Turn on monitor at device. ifconfig shows an ip address ok. cannot ping router try |sudo systemctl restart network.service| no change decide to ifdown/ifup wlan0 system returns to normal, can then ping router and ssh to device from my laptop. journalctl for wlan0 gives results as per attached. Can anyone explain what is happening to the wlan0 device and why I have to re-activate it?
Thanks Rob
On Fri, Feb 27, 2015 at 11:47 AM, Robert Brown rebrown@exemail.com.au wrote:
Hi all Running Fedora release 22 (Rawhide) 3.19.0-0.rc7.git3.1.fc22.armv7hl I find I have a problem with wlan0 becoming de-activated. Running headless, attempt to ssh to device. No response. Turn on monitor at device. ifconfig shows an ip address ok. cannot ping router try sudo systemctl restart network.service no change decide to ifdown/ifup wlan0 system returns to normal, can then ping router and ssh to device from my laptop. journalctl for wlan0 gives results as per attached. Can anyone explain what is happening to the wlan0 device and why I have to re-activate it?
What device? Anything in dmesg about crashes? It's not the firewall getting in the way?
Hi On 27/02/15 22:56, Peter Robinson wrote:
On Fri, Feb 27, 2015 at 11:47 AM, Robert Brown rebrown@exemail.com.au wrote:
Hi all Running Fedora release 22 (Rawhide) 3.19.0-0.rc7.git3.1.fc22.armv7hl I find I have a problem with wlan0 becoming de-activated. Running headless, attempt to ssh to device. No response. Turn on monitor at device. ifconfig shows an ip address ok. cannot ping router try sudo systemctl restart network.service no change decide to ifdown/ifup wlan0 system returns to normal, can then ping router and ssh to device from my laptop. journalctl for wlan0 gives results as per attached. Can anyone explain what is happening to the wlan0 device and why I have to re-activate it?
What device?
Rikomagic MK802II
Anything in dmesg about crashes?
Nothing there. No errors reported.
It's not the firewall getting in the way?
This is just internal network comms. I don't think the firewall is involved. Would cycling the wlan0 device clear anything with the firewall?
Thanks
Running Fedora release 22 (Rawhide) 3.19.0-0.rc7.git3.1.fc22.armv7hl I find I have a problem with wlan0 becoming de-activated. Running headless, attempt to ssh to device. No response. Turn on monitor at device. ifconfig shows an ip address ok. cannot ping router try sudo systemctl restart network.service no change decide to ifdown/ifup wlan0 system returns to normal, can then ping router and ssh to device from my laptop. journalctl for wlan0 gives results as per attached. Can anyone explain what is happening to the wlan0 device and why I have to re-activate it?
What device?
Rikomagic MK802II
Anything in dmesg about crashes?
Nothing there. No errors reported.
It's not the firewall getting in the way?
This is just internal network comms. I don't think the firewall is involved. Would cycling the wlan0 device clear anything with the firewall?
Looking at google it looks like a Ralink8188 device, is it attached via usb or some other manner? How is the mk802ii powered? If it's via usb make sure it's got a 2A PSU as we had a similar issue (usb dying after a period of time) reported here with a CubieTruck recently which was fixed by powering the device with a more powerful power supply.
Peter
Hi On 27/02/15 23:18, Peter Robinson wrote:
Running Fedora release 22 (Rawhide) 3.19.0-0.rc7.git3.1.fc22.armv7hl I find I have a problem with wlan0 becoming de-activated. Running headless, attempt to ssh to device. No response. Turn on monitor at device. ifconfig shows an ip address ok. cannot ping router try sudo systemctl restart network.service no change decide to ifdown/ifup wlan0 system returns to normal, can then ping router and ssh to device from my laptop. journalctl for wlan0 gives results as per attached. Can anyone explain what is happening to the wlan0 device and why I have to re-activate it?
What device?
Rikomagic MK802II
Anything in dmesg about crashes?
Nothing there. No errors reported.
It's not the firewall getting in the way?
This is just internal network comms. I don't think the firewall is involved. Would cycling the wlan0 device clear anything with the firewall?
Looking at google it looks like a Ralink8188 device, is it attached via usb or some other manner?
The on-board wireless adapter requires a rtl8188eu module which I have not got around to compiling yet so am using a USB device also a Realtek but requires a RTL8191SU module.
How is the mk802ii powered? If it's via usb make sure it's got a 2A PSU as we had a similar issue (usb dying after a period of time) reported here with a CubieTruck recently which was fixed by powering the device with a more powerful power supply.
The PS is a 3A through a powered USB hub but I may need to try the wireless device in another port for more available power. Thanks for the tip. Will check it out.
Rob
On Fri, 2015-02-27 at 23:38 +1100, Robert Brown wrote:
The on-board wireless adapter requires a rtl8188eu module which I have not got around to compiling yet so am using a USB device also a Realtek but requires a RTL8191SU module.
Robert,
Realtek based devices on the 8188/8192 family of chipsets tend to work very reliably with the VENDOR (Realtek provided) drivers, but one of the many issues with using the mainline drivers, (provided with the Fedora kernel), is that they "fall off" the network after a period of time, and you'll need to reboot to get them going again. Down/up network or remove/insmod the module isn't enough.
As regards current wi-fi hardware, there is good mainline support for Atheros and Intel, but at the bottom end of the market, (ie. cheap), Ralink (Mediatek or whatever they are calling themselves now), and Realtek.... you need to be using out-of-tree drivers. Just MHO.
Regards
Clive
Hi Clive
On 01/03/15 22:43, Clive Messer wrote:
On Fri, 2015-02-27 at 23:38 +1100, Robert Brown wrote:
The on-board wireless adapter requires a rtl8188eu module which I have not got around to compiling yet so am using a USB device also a Realtek but requires a RTL8191SU module.
Robert,
Realtek based devices on the 8188/8192 family of chipsets tend to work very reliably with the VENDOR (Realtek provided) drivers, but one of the many issues with using the mainline drivers, (provided with the Fedora kernel), is that they "fall off" the network after a period of time, and you'll need to reboot to get them going again. Down/up network or remove/insmod the module isn't enough.
Yes I have found this to be the case. What is also interesting is that there is also a power issue as Peter pointed out. I find that if I leave the hdmi monitor powered on there must be some extra voltage support to the bus because the USB wirless device stays up. When I power down the monitor I lose the wireless device within a few minutes.
As regards current wi-fi hardware, there is good mainline support for Atheros and Intel, but at the bottom end of the market, (ie. cheap), Ralink (Mediatek or whatever they are calling themselves now), and Realtek.... you need to be using out-of-tree drivers. Just MHO.
Thanks for the suggestion. My solution is going to be to get the on-board device sorted using the rtl8188eu module to avoid the USB device power issue. So I have grabbed the source files from git and am engrossed in the joys of compiling.
Regards
Rob
On Mon, 2015-03-02 at 17:50 +1100, Robert Brown wrote:
Yes I have found this to be the case. What is also interesting is that there is also a power issue as Peter pointed out. I find that if I leave the hdmi monitor powered on there must be some extra voltage support to the bus because the USB wirless device stays up. When I power down the monitor I lose the wireless device within a few minutes.
I have a whole list of "cranky" when it comes to wi-fi dongles. I have spent too many hours with a scope and one specific piece of hardware trying to "debug" the over/undershoot with the way they have implemented cascading "buck" regs.... Which I suspect may also be the case with your hardware, resulting in what happens when you power down the monitor and that affecting wi-fi stability.
Thanks for the suggestion. My solution is going to be to get the on-board device sorted using the rtl8188eu module to avoid the USB device power issue. So I have grabbed the source files from git and am engrossed in the joys of compiling.
I'm have zero experience with the EU variant part. Think this uses a separate driver, rather than the "stock" 8188/8192 drivers. I'm more than familiar with the 8188CUS and 8192CU having purchased several hundred for commercial projects. One of the first things I do after every Fedora release kernel push, is rebuild with the mainline rtl8192cu driver patched-out and the Realtek VENDOR 8188/8192 driver, patched-in.
http://www.squeezecommunity.org/repo/21/SRPMS/kernel-3.18.7-200.1.fc21.src.r...
I had a little chuckle when the Pi guys pushed their 3.18 device tree kernel to stable, having forgotten to patch-in the VENDOR 8188 driver, which they had been using by default with older kernels for quite some time, and the squealing from users with wi-fi issues started. The 8188 being their "officially unofficial" dongle of choice for Pi hardware. (The Pi people see to prefer the Edimax EW-7811UN part which uses the Realtek 8188CUS chipset.)
I'm getting my fingers burned right now, having made an akmod package to support the people using the Pi2B images and Ralink MT7601U dongles. There appears to be a whole load of crankiness with this Ralink (Mediatek) supplied driver and there isn't an upstream driver. LOL.
I hate wi-fi!
Regards
Clive
-
Clive Messer -
Peter Robinson -
Robert Brown