Hi all.
Another newbie question.
I read the sticky thread quoted in the title, tried the suggested command (sudo /usr/sbin/iwconfig wlan0 rate XXM) and it worked.
Now: how to make this permanent?
Thanks a lot for your help
campamax wrote:
> Hi all.
>
> Another newbie question.
> I read the ‘sticky thread’ (http://tinyurl.com/bxx28v) quoted in the
> title, tried the suggested command (sudo /usr/sbin/iwconfig wlan0 rate
> XXM) and it worked.
> Now: how to make this permanent?
What part do you need to be permanent. That command is merely to test
if your device is receiving.
Larry
No. That command sets the rate to XX Mbps.
Sorry - I was too quick on the keyboard.
With a modern driver that uses mac80211, the rate setting should be
automatic. What driver are you using, what is the output of the
command ‘dmesg | grep rate’, and what rate does your device get after
you have run a ping for about 20 seconds?
Larry
With my driver, the automatic rate is set to 1 - 2 Mbps, but if I force it with iwconfig to say 11 or 24 Mbps everything works and my download speed is deliciously high. So my guess is that my driver (compat_wireless) is nat capable of correctly handling the automatic rate.
So, back to my question: how to fix permanently the ger?rate? Through a script command written somewhere I do not know using iwconfig, or writing some script to force NetworkManager? This is my question.
Thanks
campamax wrote:
> With my driver, the automatic rate is set to 1 - 2 Mbps, but if I force
> it with iwconfig to say 11 or 24 Mbps everything works and my download
> speed is deliciously high. So my guess is that my driver
> (compat_wireless) is nat capable of correctly handling the automatic
> rate.
>
> So, back to my question: how to fix permanently the ger?rate? Through a
> script command written somewhere I do not know using iwconfig, or
> writing some script to force NetworkManager? This is my question.
When I asked for the data in my previous message, I was wearing my
developer hat. If there is a driver that is not honoring the automatic
rates, I would like to know the details.
What you want is a PITA. As far as I know, NM relies on the automatic
rate mechanism, therefore it needs to be done with a script run at
boot time, but it must wait until the wireless connection has been
established. In addition, the data will be lost whenever the
connection is remade.
For control with ifup, you can add a line “WIRELESS_RATE=XXM” to
/etc/sysconfig/network/ifcfg-wlan0. It is possible that NM will also
honor this info, but I have not tested.
Larry
Thanks Larry, I will try.
Anyway, the command you suggested says automatic rate:
phy0: Selected rate control algorithm ‘pid’
campamax wrote:
> Thanks Larry, I will try.
> Anyway, the command you suggested says automatic rate:
> phy0: Selected rate control algorithm ‘pid’
OK, I now know that you are using a mac80211-based driver. Which one?
Why is getting information from you so difficult? Do you want your
problem fixed in future releases, or are you happy this way?
No, sorry! 
When I answered you I had already manually forced the rate, so I could not give you further info.
Now I am in XP since I spent almost one hour to understand why the wireless stopped working at all both in Suse and XP, then I removed the battery and all went ok: why the hell my chipset remained in a similar weird condition?!? May I have generated this mess with iwconfig commands?? I do hope not!!!
Let’s go on. As soon as I get back in Suse I’ll give you all the info you asked for. Thanks a lot for your help!! I dod not want to appear unpleasant: I have at the moment very limited time to spend on my pc, and having this annoying issue on the wifi made me upset! Sorry again.
Back soon with further info then!
Regards
driver: ath5k
I compiled the devel package “compat-wireless-2009-02-03” downloaded form the developers’ site @kernel.org, hoping the issue had been corrected…
phy0: Selected rate control algorithm ‘pid’
While idle:
wlan0 IEEE 802.11bg ESSID:“XXXXXXXXXXXXXXX”
Mode:Managed Frequency:2.462 GHz Access Point: XXXXXXXXXXXXXX
Bit Rate=1 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr: off Fragment thr=2352 B
Power Management: off
Link Quality=100/100 Signal level:-36 dBm Noise level=-99 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
While pinging:
wlan0 IEEE 802.11bg ESSID:“XXXXXXXXXXXXXX”
Mode:Managed Frequency:2.462 GHz Access Point: XXXXXXXXXXXXXXX
Bit Rate=54 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr: off Fragment thr=2352 B
Power Management: off
Link Quality=100/100 Signal level:-40 dBm Noise level=-99 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
So, maybe you showed my the right thing: is the issue really an issue??
Well, all this was originated by something that happened some days ago: I tried to download a torrent, and the download rate was veeeeery low (< 0.1 Kbps) with two different clients (Monsoon and uTorrent via wine). So I booted XP and the torrent went in few seconds at 50 Kbps. This generated a doubt in me: there’s something wrong in my Suse networking!!
So I started googling, I learned about the devel drivers and the “rate issue” (if we want to call it this way)".
Now I am with the devel drivers in auto rate mode and I am downloading an OOo torrent: the dl speed went up to >300 Kbps in a few mins, but looks very unstable: high for some time, then 0 for same time again, then high again. At this point I could think that there was some kind of issue in the original driver that has been improved with the devel one, but the “rate issue” seems unreal.
Comments?
Thanks a lot for yor effort. And for your patience: this upset newbie has to learn how to listen! :shame:
Regards
P.S.
If you have further questions please ask.
campamax wrote:
> No, sorry!
>
> When I answered you I had already manually forced the rate, so I could
> not give you further info.
> Now I am in XP since I spent almost one hour to understand why the
> wireless stopped working at all both in Suse and XP, then I removed the
> battery and all went ok: why the hell my chipset remained in a similar
> weird condition?!? May I have generated this mess with iwconfig
> commands?? I do hope not!!!
On some systems, Windows will mess with the wireless when it
hibernates. If you have one with this problem, check for a BIOS
setting that forces Windoze to leave the the card alone. Iwconfig
commands do not persist between boots.
> Let’s go on. As soon as I get back in Suse I’ll give you all the info
> you asked for. Thanks a lot for your help!! I dod not want to appear
> unpleasant: I have at the moment very limited time to spend on my pc,
> and having this annoying issue on the wifi made me upset! Sorry again.
OK. It is just frustrating for me that the information that I need is
not supplied. I do have other demands on my time.
Larry
You now should have everything you need in my former message.
I am very pleased that you wrote the article it put me on the right path to better understanding of how and what to ask when I get a problem! So here goes: -
I have an Atheros 5418 - 5008 pci express card and I am using openSUSE 11.0 and compat-wireless with the 2.6.25.20-0.1-default kernel.
iwconfig shows: Bit Rate=1 Mb/s Tx-Power=23 dBm with: Security mode:open.The system log shows two unusual lines as follows:
Feb 8 17:13:57 linux-m3ih kernel: padlock: VIA PadLock not detected.
I also am puzzled because the iwconfig wlan0 rate xxM command does NOT change the 1 Mb/s rate. Can you give me some advice on this?
Feb 8 17:13:57 linux-m3ih modprobe: WARNING: Error inserting padlock_aes (/lib/modules/2.6.25.20-0.1-default/kernel/drivers/crypto/padlock-aes.ko): No such device
wiilow wrote:
> I am very pleased that you wrote the article it put me on the right path
> to better understanding of how and what to ask when I get a problem! So
> here goes: -
> I have an Atheros 5418 - 5008 pci express card and I am using openSUSE
> 11.0 and compat-wireless with the 2.6.25.20-0.1-default kernel.
> iwconfig shows: Bit Rate=1 Mb/s Tx-Power=23 dBm with: Security
> mode:open.The system log shows two unusual lines as follows:
> Feb 8 17:13:57 linux-m3ih kernel: padlock: VIA PadLock not detected.
> I also am puzzled because the iwconfig wlan0 rate xxM command does NOT
> change the 1 Mb/s rate. Can you give me some advice on this?
> Feb 8 17:13:57 linux-m3ih modprobe: WARNING: Error inserting
> padlock_aes
> (/lib/modules/2.6.25.20-0.1-default/kernel/drivers/crypto/padlock-aes.ko):
> No such device
The padlock-aes module is vir VIA C3 processors. You don’t appear to
have the hardware to run it. If your wireless works, you don’t need it.
Have you run the ‘iwconfig wlan0 rate xxM’ as root? It does require
privilege.
Thanks for the advice on the security ‘VIA’ note. I worried about it because I have set up the AP with WPA2-PSK and password the iwconfig output shows security - open!
I have tried a few things to change the - 1Mb/s rate:-
I have run the ‘iwconfig wlan0 rate xxM’ as root with ‘su’ privilege.
I have also tried to change the rate in /etc/sysconfig editor from ‘auto’ to 54 and 18. None of these attempts changed the iwconfig rate from the 1Mb/s.
dmesg | grep wlan0 also gives a ‘normal’ response!
I am not a complete ‘noobie’, but I am unsure what to try next?
Coul somone tell me how to extablish connection with wireless using pppoe?
In Mint6 and Ubuntu10 this was easy just by using command :sudo pppoeconfig
please I have searched quite a lot but no result?:’(
I have a problem with the firmware package.
I have a Linksys WPC54G Notebook adapter and I can’t get it work. I downloaded firmware from the homepage, but when I entered the command “dmesg|grep firmware” it shows:
“firmware: requesting b43/ucode5.fw
b43-phy0 ERROR: You must go to b43 - Linux Wireless and download the latest firmware (version 4).
firmware: requesting b43/ucode5.fw
b43-phy0 ERROR: You must go to b43 - Linux Wireless and download the latest firmware (version 4).firmware: requesting b43/ucode5.fw
b43-phy0 ERROR: You must go to b43 - Linux Wireless and download the latest firmware (version 4).firmware: requesting b43/ucode5.fw
b43-phy0 ERROR: You must go to b43 - Linux Wireless and download the latest firmware (version 4).firmware: requesting b43/ucode5.fw
b43-phy0 ERROR: You must go to b43 - Linux Wireless and download the latest firmware (version 4).firmware: requesting b43/ucode5.fw
b43-phy0 ERROR: You must go to b43 - Linux Wireless and download the latest firmware (version 4).firmware: requesting b43/ucode5.fw
b43-phy0 ERROR: You must go to b43 - Linux Wireless and download the latest firmware (version 4).
firmware: requesting b43/ucode5.fw
firmware: requesting b43/pcm5.fw
firmware: requesting b43/b0g0initvals5.fw
firmware: requesting b43/b0g0bsinitvals5.fw
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)”
using opensuse 11.1 GNOME
now firmware works, but I can’t connect to the router.
STS301 wrote:
> I have a problem with the firmware package.
>
> I have a Linksys WPC54G Notebook adapter and I can’t get it work. I
> downloaded firmware from the homepage, but when I entered the command
> “dmesg|grep firmware” it shows:
> “firmware: requesting b43/ucode5.fw
> b43-phy0 ERROR: You must go to ‘b43 - Linux Wireless’
> (http://linuxwireless.org/en/users/Drivers/b43#firmware) and download
> the latest firmware (version 4).
> firmware: requesting b43/ucode5.fw
> b43-phy0 ERROR: You must go to ‘b43 - Linux Wireless’
> (http://linuxwireless.org/en/users/Drivers/b43#firmware) and download
> the latest firmware (version 4).firmware: requesting b43/ucode5.fw
> b43-phy0 ERROR: You must go to ‘b43 - Linux Wireless’
> (http://linuxwireless.org/en/users/Drivers/b43#firmware) and download
> the latest firmware (version 4).firmware: requesting b43/ucode5.fw
> b43-phy0 ERROR: You must go to ‘b43 - Linux Wireless’
> (http://linuxwireless.org/en/users/Drivers/b43#firmware) and download
> the latest firmware (version 4).firmware: requesting b43/ucode5.fw
> b43-phy0 ERROR: You must go to ‘b43 - Linux Wireless’
> (http://linuxwireless.org/en/users/Drivers/b43#firmware) and download
> the latest firmware (version 4).firmware: requesting b43/ucode5.fw
> b43-phy0 ERROR: You must go to ‘b43 - Linux Wireless’
> (http://linuxwireless.org/en/users/Drivers/b43#firmware) and download
> the latest firmware (version 4).firmware: requesting b43/ucode5.fw
> b43-phy0 ERROR: You must go to ‘b43 - Linux Wireless’
> (http://linuxwireless.org/en/users/Drivers/b43#firmware) and download
> the latest firmware (version 4).
> firmware: requesting b43/ucode5.fw
> firmware: requesting b43/pcm5.fw
> firmware: requesting b43/b0g0initvals5.fw
> firmware: requesting b43/b0g0bsinitvals5.fw
> b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)”
You are showing mixed results. The last 5 lines show that the firmware loaded -
the first part shows that it was not available.
What is the story?
Larry
STS301 wrote:
> now firmware works, but I can’t connect to the router.
Is your device receiving? Does ‘sudo /usr/sbin/iwlist scan’ show your AP? If it
does, then all you need to do is run the NetworkManager applet found in the
right-hand corner of the screen (upper for Gnome, lower for KDE) and click on
“New Connection”.
Larry