Hey! Is there anyone competent enough to help me? This problem is almost blocker for me and I can imagine people who see this bug as blocker. Well, I know that I did not pay for linux or whatever. I want to at least understand what’s the problem before adding it to bug tracker. (Understanding bug what package’s bag it is would be great).
comments like this will not endear you to the community, would be better rephrased. As for help,have you read the stickies at the start of the wireless section ? any problems apart from the above ?You did set things up via YaST - network devices - network settings ? a bit more info on what you have tried would help also
I did read the FAQ post, the word “associated” appears there once but it looks like it is irrelevant to my problem.
Yes, it is configured wireless in Yast. Every time I reboot the PC there is like 50% chance that on next boot internet will be up. If it is not I can still scan for networks (scan actually happens, I see APs in my neighborhood the list refreshes if something changes) but when I try to connect I get “not associated” error (message quoted above).
This bug is extremely annoying as it feels like Stupid Linux(r) is rolling a dice at boot to decide whether to **** me off.
Using ndiswrapper for ath5k. I tried madwifi but it broke whatever little that actually worked.
Tried both ifup and network manager. Same 50% chance of no internet on reboot. The error message is from KInternet, ifup just fails silently (and says it is actually connected somehow to somewhere if I try ifconfig)
Cause when I see bundled Internet Explorer not working on freshly installed WindowsXP I call it “Stupid Windows”.
Any guide to how I configure alternative driver if I already have ndis from repos installed? I mean guide in human readable format that says exactly how to configure it and, if needed, instructions to safely disable the old one.
Another thing that would be very helpful would be to post
which device you actually have. [And, since you haven’t
done that, it makes me think that maybe you also haven’t
read the ‘sticky’ posts at the front of this ‘wireless’ forum.]
Those ‘stickies’ request that you run a cmd like
‘lspci’ (if your device is pci-bus based) and post the result.
Actually, for your situation, the best cmd would be:
Once we know what device you actually have, we can
better lead you to the best solution.
Lastly, reading other posts in this forum, especially ones
of people who have the exact same device that you do,
will bring the quickest results.*
One place I go for a first-indication is the website: Linux wireless LAN support http://linux-wless.passys.nl
where the link above shows your device as ‘green’ for the madwifi-driver.
(i.e. the ‘ath_pci’ driver, whose ‘ath_hal’ component is proprietary)
So, that driver should work for you.
ndiswrapper (i.e. the Windows driver) is proprietary too, so
it looks like you’ll have to ‘taint’ your kernel, no matter
whether you choose madwifi or ndiswrapper. Since you
already have familiarity with ndiswrapper, and since their
website documents 4 separate successes, I’d keep trying ndiswrapper: NDISwrapper
Look specifically at entries 5,44,46,73 in the page above, all of which show your same
For starters, make sure that you have executed:
which creates a file: ‘/etc/modprobe.d/ndiswrapper’
aliasing wlan0 to the ndiswrapper module. (If you ever decide to
switch back to trying to use the madwifi-driver, make sure that you
DELETE this file, as one of the steps in removing ndiswrapper support.)
Yast2->network devices->network settings is where you are supposted to
to ‘configure’ your device, and I assume you’ve been thru this. One
caveat: lots of people are reporting issues here…one approach is
to DELETE the entry pertaining to your device, reboot, and go back
in (it should get re-created and show up as non-configured), then click on
‘edit’ and configure it again. Some (including me) had better luck with
‘ifup’ than with ‘network-manager’ under the global-options section, when
Your output shows that the windows-driver you currently have setup is trying
to run at the (non-standard) bit-rate of 108Mb/s (as the two entries #44 and #46 mention).
I think that only works if your router supports ‘Super G’ rates, so that MIGHT be the problem!
[To test that theory, you could try either of the two Windows-drivers pointed to
by entries #5 and #73 and see if they default to the standard 54Mb/s rate.]
[There is also another way…mucking around in the generated config-file that controls
these lower-level details, but I’d have to do some forum-searching to find
the details for how to do that. Search for ‘bit rate’ in the wireless forum if you
want to learn how to hack on that.]
Hope this helps more than it confuses. [This pretty well reaches the
extend of my knowledge. Good luck.]
The entries you mention are all 108Mbit, not sure that there are 64 bit drivers everyone. At least now I have one hypothesis on the cause of the problem, non-standard speed. However my router is 108Mbit too.
Where should I ask for the meaning of “not associated”? Ndis forums? Kinternet forums? Everywhere?
When your wireless device connects with the access point, it must
complete two steps - establish that the AP is the correct one, and
then perform the authentication process. Only when both steps are
complete is it “associated”.