- Posts: 136
- Thank you received: 0
LMDE2 internet conn fail with 3.18.13-rt10mah+
I'm using a mesa 7i76E on a pc with LMDE2. with the preempt kernel 3.18.13-rt10mah+ kernel if I connect to the internet by an wifi usb adapter, after a few minutes, the internet freezes. I cant even do a ping, But using another kernel (3.16.0-4-586) everything related to the internet or wifi connection seems to be ok.
I did a lsmod on both kernels, that is he outputs:
this are the modles on 3.18.13-rt10mah+
on the default kernel:
If I do a lsmod when the internet connection fails, the output is the same, so at the moment I had no clue what can do this. any help will be welcome.
Please Log in to join the conversation.
I'm using a mesa 7i76E on a pc with LMDE2. with the preempt kernel 3.18.13-rt10mah+
Michael will have probably built that kernel on Debian Jessie, but rt-preempt kernels are generally quite forgiving and transferable
..... I connect to the internet by an wifi usb adapter ......
Unless you say what the wifi adapter is and which chipset it contains, the list of modules does not help.
Run tail -f /var/log/messages when you plug the usb adaptor in to see what is reported
I got this plugging in a crappy old usb wifi stick( they are all crappy
You also need to check you have the firmware for that NIC installed, (eg, firmware-realtek firmware-linux-nonfree )
which may entail fetching from sid or whatever to get the up to date ones.
Then remake initrd.img-3.18.13-rt10 to ensure it is up to date.
This is ancient, but the process remains the same
ww.fdsd.co.uk/wiki/Tech/HowToRebuildInitrdImage.twiki.html
Please Log in to join the conversation.
If i try to install with sudo apt-get install firmware-realtek or firmware-linux-nonfree it says that is already installed and up to date.
on the log i says: rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin and searching for this in google look liker its associated with firmware-realtek ( packages.debian.org/wheezy-backports/firmware-realtek )
Please Log in to join the conversation.
You seem have all the modules and firmware required.
I would be interested to see what gets posted in /var/log/messages and /var/log/dmesg when you have a problem with it.
Once you have the problem, go to a terminal and do
cat /var/log/messages > messages.txt
and
dmesg > dmesg.txt
and attach those txt files.
I am a little puzzled as to why the stick is coming up as wlan3.
That would suggest there are 3 previously assigned wireless lan connections in existence.
Please do in a terminal
cat /etc/network/interfaces > interfaces.txt
and attach that too.
Need to check which network manager you are using, if you have network-manager package and wicd installed, they conflict and can cause all sorts of problems.
Run
whereis wicd
whereis nmcli
If it finds both, you have potential problems right there.
Please Log in to join the conversation.
Attachment not found
the last thing that i did are update initramfs and install initramfs-tools. but after half an hour or so it freezes again...
I will post the log messages when the problem happens.
Please Log in to join the conversation.
Your interfaces file just refers back to interfaces.d, which is certainly different to how Debian normally sets things up.
I'll wait to see what the logs contain, when you get a drop out on wireless.
There is nothing wrong per se with the modules and firmware, the dongle is being recognised and brought up.
These USB dongles are pretty flaky a lot of the time in my experience.
I tend to always use wicd for a much more reliable wireless connection.
Would be worth trying removing the package network-manager and installing wicd.
Just make sure you keep the dongle plugged in, so that hopefully it will be picked up automatically.
If it doesn't, you can normally use this procedure.
If Wireless LAN is shown blocked (soft or hard)
Then
which should give something like
Note wlan1 is shown as DOWN
Now check appears in listing
Which it does
Now check it is receiving and what stations are in range
and you get something like this
Now you can open up wicd and click on the right hand drop menu [V]
Attachment not found
Select 'Preferences', get this menu and add your WLAN desigination, in this case wlan1.
Attachment not found
Then click OK and return to main dialog and click [Refresh], after which those stations you detected should come up and you are up and running once you select one of them and sort out password etc.
Attachment not found
Note the strength of first station is 72%
That was 3ft from the router! Just shows how flaky these dongles are, my laptop gets 100% anywhere in visible range and 85% 15 metres away, behind 3 brick walls.
regards
Please Log in to join the conversation.
there is the messages:
Attachment not found
and dmesg:
Attachment not found
Im already working on an alternative with Debian wheezy, and today when I tryed to optimize the latency times with "grub" options I already have a similar problem on wheezy
this is the "stock" wheezy configuration:
this is the LMDE2 configuration that had problems:
the modified wheezy configuration where I lost wifi connection to:
after this I remove :
from this configuration and the wifi connection seems to be stable (needs more test).
can it be related in somehow with the wifi problems??
tnks
Please Log in to join the conversation.
this is the LMDE2 configuration that had problems:
linux /boot/vmlinuz-3.18.13-rt10mah+ root=UUID=34501974-505a-490f-873f-4937e569da86 ro quiet splash isolcpus=2,3 intel_idle.max_cstate=0 processor.max_cstate=0
If you google intel_idle.max_cstate=0 you will find lots of references to problems with networking, especially wifi.
There is some suggestion that using state 1 is a better option, but I have never bothered with these options and turn off all power management, turn fan speed to full etc in BIOS
I always disable suspend, hibernate etc at kernel level for the same reason (when I build the kernel - not through params)
I wish you had said exactly what you were doing in the beginning, these kernel parameters look like the problem, not the kernel itself.
You don't need brilliant latency to run with mesa cards, 50K is quite good enough.
You can quite often improve latency considerably on a multicore newer computer with larger processor caches, by running a dummy base thread at about 25 - 50us with nothing attached to it. Keeps the cores busy so the rt code remains in one cache.
Try it with latency-test 25us 1ms to test it out and look at the servo figures
The USB stick seems to be erroring and repeatedly connecting and disconnecting in the dmesg, but not looked at it very much in light of the preceding.
Get rid of the kernel params and it should be fine
Please Log in to join the conversation.
I uninstalled network-manager but have errors installing wicd. so I believe that I'm stuck with no way to connect to the internet. Tomorrow I will decide if worth keeping try to fix that or just simply migrate to wheezy (this work is already done).
Please Log in to join the conversation.
I uninstalled network-manager but have errors installing wicd. so I believe that I'm stuck with no way to connect to the internet
Without knowing what the errors are, can't assist. To revert just un-install wicd and re-install network-manager.
If the packages are still in /var/cache/apt/archives you don't need a network connection to do that.
Tomorrow I will decide if worth keeping try to fix that or just simply migrate to wheezy (this work is already done).
If wheezy is an option, just use the stock debian rt-preempt kernel, it works perfectly well
Please Log in to join the conversation.
