Page 1 of 2

Wifi fails to connect

PostPosted: Jun 9th, '12, 00:28
by OS1
Mageia inherited the poor WiFi support from Mandriva and it hasn't improved. In fact with Mg2 the situation has got worse. I first raised this on the bug list for MDV 2007 and it STILL hasn't been fixed. Actually the problem largely went away, not entirely, in MDV 2010.1 but was back for 2010.2!

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.

Then there's drakroam. There doesn't seem to be anyway of adding a hidden network. Sometimes you'll see a hex address but this may or may not be the hidden network you're after. Hex addresses don't really mean very much. So you resort to drakconnect and thereby overwrite your main network.

If you do manage to setup your hidden network it then appears in drakroam but in Mg2 you still can't connect. With Mg2 all my usual strategies have stopped working which is going to be a issue for me as I don't always want to be tied to 2 metres from my router!

Makes no difference using Network Centre or Setup A New Network Interface in DrakConf. Network Center creates two files in /etc/sysconfig/network-scripts/wireless.d, 00:0f:b5:15:5d:aa and abcdefg, they both have identical contents.

I am happy to collect any diagnostics and try anything that won't damage my machine! in order to resolve this. After all, it's now 2012 and just because Vista couldn't handle hidden networks is no reason for Mageia not to as well!!

As I said in 2007, this problem does not exist in Ubuntu, Fedora, SUSE nor OS-X. It is not my router, we have several computers with flavours of Linux and OS-X and only the MDV and Mg ones have this issue.

My router configuration is hidden SSID, G only, channel 5 and WPA-PSK

Pleeeaasse someone help. I don't want to use another distribution, I love MDK / MDV / Mg and don't want to switch. I've lived with this issue for five years now and I'm reaching the end of the tether.

Code: Select all
iwconfig

lo        no wireless extensions.

wlan0     IEEE 802.11abg  ESSID:off/any 
          Mode:Managed  Frequency:2.432 GHz  Access Point: Not-Associated   
          Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
         
irda0     no wireless extensions.

eth0      no wireless extensions.


Code: Select all
ps -ef | grep -v grep | grep -i net

root        10     2  0 23:04 ?        00:00:00 [netns]
root      1201     1  0 23:05 ?        00:00:00 /usr/sbin/NetworkManager --no-daemon
owen      4443  3873  0 23:08 ?        00:00:05 /usr/bin/perl /usr/bin/net_applet


Code: Select all
ifconfig

eth0      Link encap:Ethernet  HWaddr 00:09:6B:50:1A:B9 
          inet6 addr: fe80::209:6bff:fe50:1ab9/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:3180 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2495 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3314537 (3.1 MiB)  TX bytes:383242 (374.2 KiB)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:80 errors:0 dropped:0 overruns:0 frame:0
          TX packets:80 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:23831 (23.2 KiB)  TX bytes:23831 (23.2 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:05:5D:9F:C2:06 
          inet6 addr: fe80::205:5dff:fe9f:c206/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:726 (726.0 b)  TX bytes:835 (835.0 b)


Code: Select all
iwevent

Waiting for Wireless Events from interfaces...
23:17:38.774972   wlan0    Scan request completed
23:17:46.806765   wlan0    Scan request completed
23:17:54.474850   wlan0    Set Mode:Managed
23:17:54.529110   wlan0    Set Encryption key:off
23:17:54.544976   wlan0    Set Encryption key:****-****-****-****-****-****-**
23:17:54.555314   wlan0    Set ESSID:"abcdefg"
23:17:54.716551   wlan0    Set Mode:Managed
23:17:54.717495   wlan0    Set ESSID:off/any
23:17:57.581804   wlan0    Scan request completed
23:17:57.582275   wlan0    Set ESSID:off/any
23:17:57.582941   wlan0    Set Mode:Managed
23:17:57.602778   wlan0    Set Frequency:2.432 GHz (Channel 5)
23:17:57.603302   wlan0    Set ESSID:"abcdefg"
23:17:57.608880   wlan0    Association Response IEs:010882848B968C1298243204B048606C
23:17:57.608965   wlan0    New Access Point/Cell address:00:0F:B5:15:5D:AA
23:17:57.626879   wlan0    New Access Point/Cell address:Not-Associated
23:18:00.756655   wlan0    Scan request completed
23:18:00.761192   wlan0    Set ESSID:off/any
23:18:00.762302   wlan0    Set Mode:Managed
23:18:00.763266   wlan0    Set Frequency:2.432 GHz (Channel 5)
23:18:00.768101   wlan0    Set ESSID:"abcdefg"
23:18:00.773800   wlan0    Association Response IEs:010882848B968C1298243204B048606C
23:18:00.773874   wlan0    New Access Point/Cell address:00:0F:B5:15:5D:AA
23:18:00.777637   wlan0    New Access Point/Cell address:Not-Associated
23:18:03.906775   wlan0    Scan request completed
23:18:03.908076   wlan0    Set ESSID:off/any
23:18:03.908646   wlan0    Set Mode:Managed
23:18:03.908899   wlan0    Set Frequency:2.432 GHz (Channel 5)
23:18:03.913526   wlan0    Set ESSID:"abcdefg"
23:18:03.919191   wlan0    Association Response IEs:010882848B968C1298243204B048606C
23:18:03.919264   wlan0    New Access Point/Cell address:00:0F:B5:15:5D:AA
23:18:03.948017   wlan0    New Access Point/Cell address:Not-Associated
23:18:07.078646   wlan0    Scan request completed
23:18:07.080101   wlan0    Set ESSID:off/any
23:18:07.080770   wlan0    Set Mode:Managed
23:18:07.081628   wlan0    Set Frequency:2.432 GHz (Channel 5)
23:18:07.084099   wlan0    Set ESSID:"abcdefg"
23:18:07.089606   wlan0    Association Response IEs:010882848B968C1298243204B048606C
23:18:07.089678   wlan0    New Access Point/Cell address:00:0F:B5:15:5D:AA
23:18:07.109611   wlan0    New Access Point/Cell address:Not-Associated
23:18:10.250755   wlan0    Scan request completed
23:18:18.282755   wlan0    Scan request completed
23:18:22.121765   wlan0    Scan request completed
23:18:30.151781   wlan0    Scan request completed
23:18:38.180637   wlan0    Scan request completed


Code: Select all
lsmod | grep ath

ath5k                 170218  0
ath                    19390  1 ath5k
mac80211              384735  1 ath5k
cfg80211              169030  3 mac80211,ath,ath5k


Code: Select all
lspci -vv -nn -q -Q

09:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212/AR5213 Wireless Network Adapter [168c:0013] (rev 01)
        Subsystem: D-Link System Inc Device [1186:3a07]
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 168 (2500ns min, 7000ns max), Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at d8000000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [44] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=2 PME-
        Kernel driver in use: ath5k


Driver ath5k
Chipset Atheros

Code: Select all
tail daemons/errors.log

Jun  8 00:09:27 localhost /etc/sysconfig/network-scripts/ifup-eth: ath5k device wlan0 does not seem to be present, delaying initialization.


Code: Select all
tail daemons/info.log

Jun  8 00:14:38 localhost ifplugd(wlan0)[4729]: ifplugd 0.28 initializing.
Jun  8 00:14:38 localhost ifplugd(wlan0)[4729]: Using interface wlan0/00:05:5D:9F:C2:06 with driver <ath5k> (version: 3.3.6-desktop-2.mga2)
Jun  8 00:14:38 localhost ifplugd(wlan0)[4729]: Using detection mode: SIOCETHTOOL
Jun  8 00:14:38 localhost ifplugd(wlan0)[4729]: Initialization complete, link beat not detected.
Jun  8 00:14:42 localhost avahi-daemon[1183]: Registering new address record for fe80::205:5dff:fe9f:c206 on wlan0.*.
Jun  8 00:20:36 localhost avahi-daemon[1183]: Withdrawing address record for fe80::205:5dff:fe9f:c206 on wlan0.
Jun  8 00:20:36 localhost avahi-daemon[1183]: Withdrawing workstation service for wlan0.
Jun  8 00:20:37 localhost ifplugd(wlan0)[4729]: Failed to detect plug status of wlan0
Jun  8 00:20:37 localhost ifplugd(wlan0)[4729]: Exiting.


Code: Select all
tail kernel/errors.log

Jun  8 00:20:37 localhost kernel: [  727.347664] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated).  Use CAP_NET_ADMIN and alias netdev-wlan0 instead
Jun  8 00:20:37 localhost kernel: [  727.441477] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated).  Use CAP_NET_ADMIN and alias netdev-wlan0 instead
Jun  8 00:20:37 localhost kernel: [  727.458486] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated).  Use CAP_NET_ADMIN and alias netdev-wlan0 instead
Jun  8 00:20:37 localhost kernel: [  727.475456] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated).  Use CAP_NET_ADMIN and alias netdev-wlan0 instead
Jun  8 00:20:37 localhost kernel: [  727.490721] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated).  Use CAP_NET_ADMIN and alias netdev-wlan0 instead
Jun  8 00:20:37 localhost kernel: [  727.507676] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated).  Use CAP_NET_ADMIN and alias netdev-wlan0 instead
Jun  8 00:20:37 localhost kernel: [  727.622505] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated).  Use CAP_NET_ADMIN and alias netdev-wlan0 instead
Jun  8 00:20:37 localhost kernel: [  727.627885] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated).  Use CAP_NET_ADMIN and alias netdev-wlan0 instead
Jun  8 00:20:37 localhost kernel: [  727.635638] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated).  Use CAP_NET_ADMIN and alias netdev-wlan0 instead


Code: Select all
tail -n 60 kernel/info.log

Jun  8 00:14:47 localhost kernel: [  378.257374] wlan0: authenticate with 00:0f:b5:15:5d:aa (try 1)
Jun  8 00:14:47 localhost kernel: [  378.258643] wlan0: authenticated
Jun  8 00:14:47 localhost kernel: [  378.258775] wlan0: associate with 00:0f:b5:15:5d:aa (try 1)
Jun  8 00:14:47 localhost kernel: [  378.261195] wlan0: RX AssocResp from 00:0f:b5:15:5d:aa (capab=0x431 status=0 aid=1)
Jun  8 00:14:47 localhost kernel: [  378.261205] wlan0: associated
Jun  8 00:14:47 localhost kernel: [  378.261215] wlan0: moving STA 00:0f:b5:15:5d:aa to state 1
Jun  8 00:14:47 localhost kernel: [  378.261221] wlan0: moving STA 00:0f:b5:15:5d:aa to state 2
Jun  8 00:14:47 localhost kernel: [  378.261228] wlan0: moving STA 00:0f:b5:15:5d:aa to state 3
Jun  8 00:14:47 localhost kernel: [  378.277345] wlan0: disassociating from 00:0f:b5:15:5d:aa by local choice (reason=3)
Jun  8 00:14:47 localhost kernel: [  378.277476] wlan0: deauthenticating from 00:0f:b5:15:5d:aa by local choice (reason=3)
Jun  8 00:14:47 localhost kernel: [  378.284430] wlan0: moving STA 00:0f:b5:15:5d:aa to state 2
Jun  8 00:14:47 localhost kernel: [  378.284440] wlan0: moving STA 00:0f:b5:15:5d:aa to state 1
Jun  8 00:14:47 localhost kernel: [  378.284447] wlan0: moving STA 00:0f:b5:15:5d:aa to state 0
Jun  8 00:14:47 localhost kernel: [  378.284492] cfg80211: Calling CRDA to update world regulatory domain
Jun  8 00:14:47 localhost kernel: [  378.304704] cfg80211: World regulatory domain updated:
Jun  8 00:14:47 localhost kernel: [  378.304715] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jun  8 00:14:47 localhost kernel: [  378.304725] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jun  8 00:14:47 localhost kernel: [  378.304734] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jun  8 00:14:47 localhost kernel: [  378.304742] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jun  8 00:14:47 localhost kernel: [  378.304751] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jun  8 00:14:47 localhost kernel: [  378.304759] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)


I'm beginning to think that WiFi under Linux only works by luck! Googling for "disassociating from by local choice (reason=3)" reveals yet another swathe of issues around WiFi and they've been happening for years. It seems to affect loads of distributions with just as many solutions proposed; add aliases to modprobe.conf, set the radio kill switch to off - how?!, use a different kernel, Network Manager is rubbish and always has been! change encryption, change channel, unhide SSID, use ndiswrapper, don't use ndiswrapper! It doesn't seem to matter which WiFi chipset either. The only thing missing seems to be a solution! Sad it's gone on for so long.

Should I try the kernel from MDV 2010.1?

Re: Wifi fails to connect

PostPosted: Jun 9th, '12, 01:34
by wintpe
it only falls back to wep if it failed to complete the whole connection including dhcp.

its kind of a fall back to default position (highly annoying I agree).

as soon as it succeeds the connection is saved , and works perfectly from then on.

I dont have an issue with wireless on mandriva or mga1, although i cant say for mga2 yet, that may have issues that make it look like its become unreliable.

Ill reserve judgement till i see for myself.

I use Atheros 802.n modems

regards peter

Re: Wifi fails to connect

PostPosted: Jun 15th, '12, 14:04
by timosch
hi OS1
i agree to you that "M" has very very poor WLAN Support and often it hangs and crashes, no connect, lost connect, needs several times before a connect works, but the reason is not the Kernel.....
"M"´s net-scripts are the reasons for all this trouble.
I still wonder why no one tryed to get the Ubuntu, Debian or Fedora sripts ported and working on "M"

Re: Wifi fails to connect

PostPosted: Jun 15th, '12, 22:04
by OS1
Thanks for the replies, does anyone have a solution for this, it's driving me nuts, or am I going the have to move to a new distribution? :-(

Re: Wifi fails to connect

PostPosted: Jun 15th, '12, 23:24
by timosch
Hi OS1,
no -i- dont have a 100% working solution right now, in general the ath5k works pretty fine in case u use the right driver, i have it working on several Mandriva 2010.x Boxes, time to time it hangs a bit, giving the box a few time to sync with the Ap and it works then as if nothng was before.
I cant say any abt Mageia 2 WLAN at time bec i am still stuck at one problem (vdr, vdr-sc, atom-kernel drivers and v4l) i still dont have any gui running and no WLAN, just a simple eth, horrible, but true.
I take the/my time to get it working step by step, i still dont know if i´m wasting time , i will see, when i am lucky i will surely have a look at the buggy "WLAN" if not, i switch back to Gentoo ^^

What i cant get, Mageia is already talking abt MAG3 and Mag2 is not nearly working stable......

My opinion at time, be sorry that i am so honest, WLAN on Mageia SUCKS

A hint for you, mixing PLF, MIB AND ! Mag1 rpms works often, (carefull with EDU rpms !) i tried it allready on Mandriva 2010.x , its not a perfect nor actual system, but works stable, but be warned with MIB rpms, allways do a backup (image) befor eu try them ;)

Re: Wifi fails to connect

PostPosted: Jun 16th, '12, 00:51
by OS1
Many thanks timosch, I'll take a look at PLF, what is MIB?

Re: Wifi fails to connect

PostPosted: Jun 16th, '12, 21:51
by timosch
OS1 wrote:Many thanks timosch, I'll take a look at PLF, what is MIB?

MIB is also a Fork MIB = Mandriva International Backports (formerly those who wear black :lol: )
But be carefull, never update ur sys when u have their tree active, u better DL the needed rpm´s by ur own and install them then....

Re: Wifi fails to connect

PostPosted: Jun 16th, '12, 22:03
by alf
timosch wrote:MIB is also a Fork
MIB is a distro? Since when?

Re: Wifi fails to connect

PostPosted: Jun 16th, '12, 22:19
by timosch
no, not a distro, they fork of the forked fork rpm´s thats all, sometimes good, sometimes not (das weißt du doch alf ;) )
a while ago i heard they had build a own image, but i never saw it somewhere.

They are just not so smart like Mageia or akDengie´s Team (EDU)

@Lebarhon
exactly ;)

Re: Wifi fails to connect

PostPosted: Jun 16th, '12, 22:24
by Lebarhon
MIB isn't a distro, it was at the beginning an Italian group of hackers and MIB stood for Mandriva Italian Backports. They build backports for Mandriva. Now, peoples from other countries joined the group and MIB means Mandriva International Backports.

Re: Wifi fails to connect

PostPosted: Jun 16th, '12, 23:16
by OS1
At the end of the day wouldn't it be easier for the developers at Mageia just to fix something that should have been fixed years ago

Re: Wifi fails to connect

PostPosted: Jun 16th, '12, 23:17
by alf
Lebarhon wrote:MIB isn't a distro, it was at the beginning an Italian group of hackers and MIB stood for Mandriva Italian Backports
Yes, i know that. But a third party repo is not comparable to a fork and we shouldn't mess up things.

Re: Wifi fails to connect

PostPosted: Jun 16th, '12, 23:31
by timosch
OS1 wrote:At the end of the day wouldn't it be easier for the developers at Mageia just to fix something that should have been fixed years ago

ooooh !!! i am with you OS1 , i think it should be done now !
Megeia is now "free" and could do it whenever they want, whatever they want, they just need to want and do then..... the antiquated cut-off......

Re: Wifi fails to connect

PostPosted: Jun 19th, '12, 22:31
by doktor5000
timosch wrote:Megeia is now "free" and could do it whenever they want, whatever they want, they just need to want and do then..... the antiquated cut-off......

Feel free to volunteer and help doing that ... You know, talk is cheap.

timosch wrote:A hint for you, mixing PLF, MIB AND ! Mag1 rpms works often, (carefull with EDU rpms !)

This is no good advice with Mageia 1, even less to a novice, and not supported at all. Fell free to solve any issues that result from your fine "advices".

timosch wrote:i agree to you that "M" has very very poor WLAN Support and often it hangs and crashes, no connect, lost connect, needs several times before a connect works, but the reason is not the Kernel.....
"M"´s net-scripts are the reasons for all this trouble.

"M" has very poor WLAN support? That's a pretty blanket statement. For me and many others it works just fine, once setup correctly. Also there are many crashes and instable connections on other distributions. Furthermore, the ifcfg-scripts are rather traditional, and actually Fedora uses them too. FWIW also networkmanager is available, which can also be used exclusively, so the same as for Ubuntu or Debian is available. Please get your facts straight before you spread such gossip.

Re: Wifi fails to connect

PostPosted: Jun 20th, '12, 00:28
by OS1
All this heated talk gets us nowhere. I would much rather the issue was addressed and a fix found for a problem that I reported first in 2007, five years ago! While I'd love to help I am a J2EE developer and wouldn't know where to begin. All I can do is collect debug info and try suggestions, so let's stop ranting and start working on the issue. If it's beyond the abilities of this forum then I'll raise another bug report on Mageia.

Re: Wifi fails to connect

PostPosted: Jun 20th, '12, 02:18
by timosch
we should calm down.
its no lie that M has still 2006/ 2007 problems with the net-scripts, i was too one of those who told abt, but at Mandriva no one cared abt, now we have the chance to change it.
My hint that Deb and FC´s scripts work is not just out of the blue. They just need to be ported -cleanly- for Mageia and all will love it
In fact it should be solved asap.

for Doc, we dont need to like each other, but when we have the same goals we can do this whats in need, let it grow and become better, thats my goal and i think with such guys like OS1 in company we do the first step to perfection ^^

Re: Wifi fails to connect

PostPosted: Jun 20th, '12, 08:46
by OS1
how did you use the Deb / FC scripts? Did you simply copy them over?

Re: Wifi fails to connect

PostPosted: Jun 20th, '12, 12:21
by timosch
HI OS1
OH NO !!! dont do that,
absolutely incompatible bec of several different internal structures, in general the FC Scripts had been written by RedHat so there would be a need to figure the one and other already obsolete in M out new.
I noticed already that the one and other scripts of FC are been used by Mageia, not a bad idee bec "mommy RH" is knowing what they do.
Maybe Cent OS is another good way to see the differences (when u do the first install it surely will remember you to the good old Mandrake times ;) )
(another way would be to have a look at Gentoo´s scripts, they are also great, but as i noticed some at Mageia have some twitching in their eye corners when it comes to Gentoo, HEY ! Gentoo and Mandrake had been long ago friends ^^ Its stupid to develop all by ur own when another did it already )
Deb is a bit more different and i am not sure if it would be the best choice to switch into this way, M is an old rpm System what means RedHat, Deb isnt bad..... but we would need to change alot then and get apart from RH, by the way,
just a hint, Gentoo can import rpm´s and export to rpm ... ah?!?!? ^^

Re: Wifi fails to connect

PostPosted: Jun 20th, '12, 13:45
by wobo
Claiming that "M" has poor performance in the wifi section is completely out of proportions. It's rather the opposite. Of course nobody will deny that there are issues for a small minority of users, whatever the reason. Wifi is not a trivial area where you have one solution fits all - f.ex: in one of my systems I have to uninstall networkmanager to get Broadcom wifi to work, in another system networkmanager works ok. In another machine I could not get Atheros wifi to work neither in Fedora nor in Ubuntu, while I had no issues in Mandriva 2010.2 nor Mageia with the same hardware.

Anyhow, whatever is needed to solve these issues for all users, there should be one priority: DO NOT jeopardize something which is working nicely for most people by implementing changes which may (or may not) solve a problem of few but will not work for others. In other words: the current system is working for most people. So implementing additional solutions which may (or may not) solve the issues of a few users can only been done by improving the current system but not breaking it.

Discussions in the forum only take us to a certain point but not to a solution. This can only been found by providing a bug report including all necessary information, preferrably including hints at a possible solution, and cooperation with the developer/packager/whatever who will be assigned to the bug. Pointing at old bugreports at Mandriva are only helpful if there were hints or starting points for a possible solution, otherwise they are meaningless.

Additional info: In all the "M"s I had been (and still am) running I experienced only one real bug concerning wifi: The old and well-known issue about getting wifi to work inside the installer, even when the needed firmware is available (as it is for the Atheros chip I am using). This issue has been properly reported and acknowledged in Mageia Bugzilla.

Re: Wifi fails to connect

PostPosted: Jun 20th, '12, 14:35
by timosch
hi wobo, u can ignore it and still say all is fine or open ur mind and understand that some bug reports can easily be understood as critical opinions, whats completely wrong.

how u you do it then, is up to you.
that Mageia 2 has still major problems not only at Wifi is fact, whatever u say. Ignore it or understand we´d like to make u understand and offer some help.
Just up to you

A wise man is one who is open minded and not stuck behind his deprecated "couch"

Re: Wifi fails to connect

PostPosted: Jun 20th, '12, 20:06
by doktor5000
Well, where did you actually offer your help, have you joined packaging team yet? Spreading some gossip and only talking about this or that is not what is called help in my book.

Also, both of you mention issues reported in 2007, which particular issues are those? Any links to some bug reports?

Re: Wifi fails to connect

PostPosted: Jun 20th, '12, 21:25
by timosch
hi again Doc,
no, all this old stuff and "aka nicks " are still deleted bec i stopped long ago the support for mdv as you know.

And if u still cannot see or notice, we had been abt to start helping, must it be always inside this strict rules "u must follow our advise and rules" or u want a solution? ur choice now, we are not forced to help, we could
we also would like when Mageia is more and more bug free, but u must accept that each human has his own way to figure out problems, if you cant, stay behind ur old couch, no one is forced to use Mageia.

Re: Wifi fails to connect

PostPosted: Jun 20th, '12, 21:45
by yankee495
Only half of this makes any sense and less then that is of any help to anyone. Lost me way back I guess.

Anyway, I had problems getting my wifi going as do many. I think my friends Acer Aspire uses the ath5k...I might be wrong, but if not we could offer some first hand advice.

Re: Wifi fails to connect

PostPosted: Jun 20th, '12, 21:54
by doktor5000
Bug reports and forum posts don't get deleted out of the blue ...

And when did i say something like "you must follow our advices and our rules" ?
In fact you've offered helped, or at least you say you want to help, but i see nothing happening in this thread, that's what i mean.
Why don't you start by helping OS1 ?


@OS1: Currently it seems your system is running net_applet and networkmanager at the same time.
Can you please post the output of
Code: Select all
grep NM /etc/sysconfig/network-scripts/ifcfg*
as root?

Also, for testing purposes, could you try to switch to unencrypted mode for some minutes or so, just to see if the encryption is the offending problem?

Re: Wifi fails to connect

PostPosted: Jun 20th, '12, 23:54
by wobo
Well, as has been said:
Nobody denies existing bugs (I'm an active reporter and helper in Bugzilla, just as all the other users) - but I do not accept nebulous rumours and general badmouthing without hard facts. Some wifi issues are facts and they have already been reported, some others are the result of wrong usage (f.ex.: using networkmanager and the draknet tool at the same time), that's what this forum is here for, not for rumours and misleading discussions.

Yes, there are a few rules at Mageia - no such system is able to run without any rules at all. These few rules are based on either technical or logical reasons, none of them are based purely on the doktor's or a few people's opinion. Everybody agrees and uses these rules - except you! So who is the one hiding behind his "couch" of personal opinion? Who is the one with a closed mind?

Short sentence about "past": Yes, past is past - but only as long as wrong things/behavior/whatever of the past are not repeated again and again. Do you really think people here are dumb or in treatment for Alzheimer?

We should leave this now and do what the purpose of thei forum is: help with the issue of this topic. This is not a "shut up!" message (which I'm not entitled to anyway) - if you want to complain about the doktor or me or whatever you think is wrong - please do so in a special thread where other people will also listen and reply.