Wifi fails to connect

[OS1]

Deleted

[OS1]

http://forum.mandriva.com/en/viewtopic.php?t=59630
http://linuxgazette.net/137/misc/lg/man ... twork.html

[OS1]

Already tried making network wide open, i.e. broadcast SSID, no encryption, no passphrase and no access controls, makes no difference

[OS1]

Code: Select all

grep NM /etc/sysconfig/network-scripts/ifcfg*
/etc/sysconfig/network-scripts/ifcfg-wlan0:NM_CONTROLLED=no

[doktor5000]

Well, looking at that forum thread, seems the problem is more with the dhcp client daemon. Maybe you can just try out another one, there are several selectable in drakconnect?

[marja]

The discussion in this thread about WLAN support being poor or not surprises me.

Before Mageia 2 was released, our wireless issues tracker https://bugs.mageia.org/show_bug.cgi?id=5015 has been discussed in several meetings. It had the Release Blocker priority until most of the bugs were solved, it still has the High priority for the remaining bugs.

Some will think this means we have good WLAN support, others will think the opposite, depending on expectations, experiences, amount of optimism etc. There is no worldwide accepted standard to go by, meaning we can endlessly disagree. I'd rather we'd save our energy.

However, we are a community distribution: Mageia is made by the Mageia community for the Mageia community, by volunteers in their spare time. We don't get paid and, in case you didn't know, none of our developers gets money to buy a piece of hardware someone has an issue with, so he can more easily solve the issue.
If someone doesn't have time to do his share of the work, because of job, study, family and/or other commitments: no problem, he can freely use and enjoy Mageia.
But if he does have time, it would be nice if he would pitch in and help. Besides, even if he can't solve the problems that are most urgent to him himself, he might free up some time of others who can solve them

[OS1]

doktor5000 - what can I do about the DHCP daemon? How do I interact / debug it? Is there anything I can do to try and get it working? Please can you tell me how to setup another one?

However, we are a community distribution: Mageia is made by the Mageia community for the Mageia community, by volunteers in their spare time. We don't get paid and, in case you didn't know, none of our developers gets money to buy a piece of hardware someone has an issue with, so he can more easily solve the issue.
If someone doesn't have time to do his share of the work, because of job, study, family and/or other commitments: no problem, he can freely use and enjoy Mageia.
But if he does have time, it would be nice if he would pitch in and help. Besides, even if he can't solve the problems that are most urgent to him himself, he might free up some time of others who can solve them

I know, which is why I was volunteering to get any debug info I could and try any suggested fixes. I am still willing to do this.

[doktor5000]

Well, you could try to get some informations by looking at the information messages which are put out when the network connection is initiated.
For that, the easiest way IMHO would be to:

Code: Select all

service network stop

open another terminal, and as root launch there tailf /var/log/messages
and in the first terminal, start network services again via

Code: Select all

service network start

or try to initate wireless connection manually via iwconfig maybe you want to have a look at Archlinux wiki page, as this is quite extensive about wireless setup.

For the dhcp client, you can set that f.ex. in drakconnect advanced settings, as shown in the screenshot:

Bildschirmfoto2_2.png (57.87 KiB) Viewed 5689 times

If you really want to debug this issue, best add set -x at the beginning of every network-related scripts (mostly ifup/ifdown/iwconfig scripts) and then analyse the output when you iniate your network connection next time.

[marja]

For the dhcp client, you can set that f.ex. in drakconnect advanced settings, as shown in the screenshot:

Don't forget to look at all of the picture, when you scroll to the right you see the other dhcp client options, which might be hidden now

[zxc232]

The first issue is drakconnect. Whatever you enter for security it always seems to fall back to WEP. Very occasionally it does display the settings you used before but very rarely.

I confirm that. My solution: reboot Mageia. Mandriva don't need.

[linuxero]

Hi there;

The only time I had a problem with Mandriva was in the 2005 or 2006 release if I recall correctly and due to a strange broadcom or alike card..anyways; I find Mageia quite steady and stable connectionwise..better even than Mandriva 2011! I noticed though that you need to reboot after installing the correct rpms for your card, and please make sure to switch it on if it has a soft on/off button because this trivial issue made me waste a couple of minutes time ago

Good luck

[zxr250cc]

Hi all,

I have had trouble at times over the last five years with M version wi fi but usually figured out how to use it with the exception of Mandriva 2011.

When I have been unable to use dhcp and have it set up automatically I have done manual set up successfully. Your router probably allows you to choose a range of addresses to use for access. (Don't they all?) For a TP-LINK router, for example I set the IP address to 192.168.1.77, Netmask as 255.255.255.0, Gateway as 192.168.1.1, then for DNS 1 used 192.168.1.254 and 192.168.1.1 for DNS 2. This manual set up has been good for me usually. I could use other IP address from 192.168.1.2 through 192.168.1.254 for the router in the example, obviously.

I have two routers in my system and one is connected through the other one to a DSL modem. Why two routers? I have an old DELL AXIM x51v PDA set up as an instant weather map with Mobile Opera browser and it cannot use WPA 2. I set the USR G router up so the Dell works with it and use the TP-LINK N router for other laptop connections and all are secure. If you try to use DHCP for the one router through the other it will not work or work so slow it is like it does not work. I set the TP-LINK manually to connect to the USR router with a fixed address and all is right with the world and SURFS UP!

I have had easy automatic set up with many LIVE CD disks for Linux but usually with some other distribution than M. I wonder if Ubuntu is the best at this? Others are also good at this including SUSE and Mepis. I have even had easy auto set up in a desktop with wireless NIC and in a T-23 ThinkPad with PUPPY LINUX which is a very small total size program. Maybe 300 MB total install. They get it right.

I have used Ralink and Atheros chipset based PCMCIA cards with Linux and wifi NIC with Atheros cards with good results. I had USR PCMCIA cards but trying to use them was a total pain. I totally avoid BROADCOM chipset parts. PCMCIA cards are very cheap in many places and it is easier to use a card that Linux works with than to fight with NDISWRAPPER crap to get a card to work. I have done it the past; I don't need the trouble. One Ralink G PCMCIA card I bought was $10. It works great with every Linux flavor I have tried to use it with so far.

Nothing is perfect. I wish wireless was automatic but it seems that is not here yet.

Cheers,

gcd

[linuxero]

Try use Channel 3 and below or 9 and above..Sorry guys, but if the router allows you ignore the regulations of your country!!

I have this problem sometimes and with certain cards channels 3 and 2 work fine, with other cards channels 9 and 11 work the best. Then as you say you have different flavours of OS running and connecting to the same network, I would not assume it to be a problem of a plasterboard or the painting used in your facility..but I happened to run through this once.

Anyway; I agree there are some bugs, but still it works fine with some tweaking..

Maybe the logic in the WIFI connection in Mandriva, consequently Mageia, needs a stronger signal or other factor..maybe they should be a bit more lenient with that..

Good luck

[zxr250cc]

A program that will show you ALL the wi fi for signal strength and which channels are in use near you and allow you to choose one that is not busy is called INSSIDER and is free from METAGEEKS. It runs on Windows, sorry, but it will let you see what is around you. It is best, if possible, to be 3 channels away from other near location channels in set up. If this is not possible you can at least see all the channels represented in levels of strength and choose the weakest one to share for your system.

There is also a Linux version of this but I have not been able to get it to work so I use the windows version. With this as a tool, I have run my USR G router on channel 4 and my TP-Link N router on channel 10 and have great results. I am on alternate channels (1 channel different from others)to ones in use and at least 15-18 db higher in level than any other router in my area in the channels I have chosen. It works great. INFORMATION is the answer to the problem. This is free.

http://www.metageek.net/

UPDATE: This morning I see 20 wi fi hotspots in the inssider screen and eight of them are on channel 1, four are on 11 and three of them are on 8. I am sure they wonder why they have interference in their systems since I doubt any of them are using this software. Just an example for your information.


cheers,

gcd

[lfields]

I am having this problem with Mageia2 on an HPlaptop with RALink RT5390 wireless???

I have never had any of these issues with Atheros chipsets. I think chipset really has a big infuence on performance of wireless scripts and connection setup. This is actually the first RALink wireless I've ran. Not sure what to think yet. Funny I have an old hp with Atheros, and the new one with RaLink. When my router goes down, the Old Atheros sees it come back up and connects almost instantly. But the New one with ralink dogs it for 15 minutes of hell before it finally, randomly, connects.... Both running Magiea2....

In this case, it will connect right away sometimes. Then, when we close the lid, or some other disconnect, it will not connect for anything. Keep trying, keep reconfiguring the connection, disable network and re-enable from command line, reboot, try some more. Then suddenly it connects for no reason. Sometimes it even disconnects for no reason. And I also get the switching to WEP after failures.

I think every linux distro out there has poor wireless setup and control. Mageia/Mandy seem to work good, but some chipsets just suck. Wireless not working is a huge show stopper for Mageia. A Mageia laptop with wireless issues is hard to push to new linux users.

I would help but I am not a network tools programmer, I have contributed for many years in many other ways. My point is, there is alot of crap on here about mageia's is good, it's bad, others suck, others are better. But in the end, can we make it better? This would be an important thing to advance on. I will try to get some debug info the next time this thing goes sideways on me and post it here.

And great job to the Mageia team. Absolutly impressed with every release. I have ran Madriva since (Mandrake Linux 6.0) and these Mageia releases are the best ever. The same great distro that I fell in love with, but with a renewed dedication and polish I havn't seen in years. Excellent....

[doktor5000]

@OS1: Did you make some progress with troubleshooting your issue?

@lfields: Well, your right, but sometimes it's also rather hard to tell what the problem actually is, as many parts come into play.
Often there are only problems with DHCP exchanges, so your wireless connections is up, but you won't get any ip adress assigned, which is effectively the same as not working.

[OS1]

Hello Dok,

Very sorry, haven't had a chance to try your previous ideas. Hopefully will get some time tonight or tomorrow night.

[OS1]

I've attached the contents of /var/log/messages from doing "service network stop" to "service network start".

I've tried all the DHCP options but they all behave exactly the same. All except pump as "there is no package pump".

I am beginning to think that the ATH5K driver is basically shafted.

Well, you could try to get some informations by looking at the information messages which are put out when the network connection is initiated.
For that, the easiest way IMHO would be to:

Code: Select all

service network stop

open another terminal, and as root launch there tailf /var/log/messages
and in the first terminal, start network services again via

Code: Select all

service network start

or try to initate wireless connection manually via iwconfig maybe you want to have a look at Archlinux wiki page, as this is quite extensive about wireless setup.

For the dhcp client, you can set that f.ex. in drakconnect advanced settings, as shown in the screenshot:

The attachment Bildschirmfoto2_2.png is no longer available

If you really want to debug this issue, best add set -x at the beginning of every network-related scripts (mostly ifup/ifdown/iwconfig scripts) and then analyse the output when you iniate your network connection next time.

[OS1]

Ok, so a bit of searching and it appears that the ath5k module got broken in 2.6.31!! and has never really been fixed since! So is it time to lodge a bug in the kernel bug tracking system? I could attempt a build and run of 2.6.30 againts MG2 but goodness only knows if it'll even boot. Can anyone recomend a PCMCIA WiFi card that actually works with MG2?

[tom_]

here it is declared working on kernel 3.4

and there are still development on that module.

so you could try the caulderon kernel, if you know how to do and what you risk.
Or you could look better the fix, maybe you can rebuild the newer module on your kernel

[OS1]

Thanks for the reply tom_. I have tried the 3.4 kernel but still not working. There seeme to be some confusion as to the fix being in 3.5 or 3.4! My next course of action is to get the latest kernel source and do a build and also to try and get hold of a 2.6.30 to see if the ath5k module really did work back then. If all else fails then I will consider buying a WiFi card that works or switch to Mac

[OS1]

Well, after a fruitless couple of days trying or building practically every kernel from 2.6.27 to 3.5.0 it still doesn't work and I am now sitting here typing this using 3.2 on Ubuntu 12.04. With Ubuntu there was absolutely no issues and it also seems to be better on battery usage as well! I'll keep my Mg partition as I still think overall Mdk / Mdv / Mg is better but I need to actually use my laptop so it looks like it's Ubuntu for me now, so sorry.

[doktor5000]

Well, use what works best for you

[doktor5000]

FWIW, my parents box also uses ath5k module, and their wireless works out of the box, even within the installer as it doesn't require any firmware or anything fancy.