Search:

Well, I'm using wifi networks for years and this is the first time I see this kind of problem. I believe we can discard that option.


I've been looking at /var/log/syslog just after one freeze...

Hi. I'm experiencing lags and freezes with my wireless mouse and keyboard. I haven't detected a pattern yet, but when it starts to happen is very annoying. Even toggling on and off the devices...

Hi.

I have a .desktop file for a Wine application. It works as expected but unity shows the default icon instead the correct one. Of course I have several of them in their respective...

I don't know if it was compile again the driver after upgrading the kernel, or remove strange characters from the passphrase, but the wifi is not disconnecting any more.

I've reduced the complexity of the passphrase and checked that router is only working in WPA2 mode.

I'll let you know how it's going.

I'm going to update kernel, so I have to compile again.

If I notice strange behaviours I'll go back.

rt3562sta 778214 1

Apparently there's only one driver to rule them all hehe.

Hi again. Sorry, I don't want to be annoying, but I'm experiencing random disconnections.


Nov 25 22:57:24 altair wpa_supplicant[1161]: CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=0...

Maybe with sudo? I had to put it in front of iwpriv to stop debugging.

Wild Man, your solution would be perfect if it hadn't to be done on every boot.

By luck, I found a similar thread in this forum and the solution proposed was compile again without a debug flag. In...

Ok, I'll try, thanks. But, does it really solves the problem? I mean, is there any chances that I have two drivers (old & new) claiming the same device?

Done!


sudo apt-get purge conky-all


Unfortunately, nothing has changed. As I said, we could try to double check lsmod and stuff like that.

Hi!

I'm posting again because I've started noticing some inestability in the connection. Maybe because there are more wifi clients today...

Moreover, using a P2P application I couldn't get the...

Yeah, but I deleted other persistent rules which I didn't copied ](*,)




Sadly, nothing seems to change, although this version seems more accurate.

I've found an older thread with a similar problem after installing the propietary drivers.

Hope it helps.

http://ubuntuforums.org/showthread.php?t=1612271&page=6


EDIT 1

I've tried...

I've recovered previous rules from a Clonezilla backup :cool: soooo, this is not a problem anymore.

Apart from this, my syslog it's about 15 MB right now hahaha.

Finally I've managed to restore previous rules from a Clonezilla image. I don't know if there will be differences, but I prefer keep things as they are ;)

For me this is solved. Thanks!

Even after reboot files are empty. Can I simply forget it? Although it doesn't make any sense to have files populated with info if they are not going to be used.

I've had to reinstall udev and libudev because I've accidentally deleted the persistent-rules (is my fault).

New created rules are empty. System is running fine but the syslog pollution is there.

Ok, fine. But new created files are empty and previously weren't.

Any problem with this?

Hi folks!

I've accidentally deleted the 70-persistent-cd.rules and 70-persistent-net.rules files. For what are these files? How can I recover them since they're not automatically recreated at boot...

Main problem is solved I guess. Thanks!


I've followed your instructions but persistent rules were not automatically created at boot and syslog messages are still appearing...

ifconfig


eth0 Link encap:Ethernet direcciónHW xx:xx:xx:xx:xx:xx
ACTIVO DIFUSIÓN MULTICAST MTU:1500 Métrica:1
Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:0...

I've disabled the conky script at boot up, but messages are still appearing. So... this might not be the guilty.

Ok. I'm on it!


lsmod


Module Size Used by
pci_stub 12622 1
vboxpci 23200 0
vboxnetadp 13382 0