gmane.linux.redhat.fedora.general

Re: wifi bit rate

Ed Greshko — 2012-05-23T11:21:13

I looked back through the posts in this thread and, while I may have missed it due to
the number of posts, I did not see a mention of what make/model of wireless AP you
have. 

My sample size is small...but the AP's that I've worked with all had a "Status" page
in their Web Admin interface showing the current active wireless connections as well
as the mode they are connected in and the current data rate.  Does yours have this?

Re: Problem with Emacs

Steven Ulrick — 2012-05-23T10:20:11

Almost forgot, when I start emacs, "ps aux | grep -i emacs" looks like this:

steve< at >localhost ~$ ps aux | grep -i emacs
steve     6607  101  0.1 260220 13468 pts/2    R+   05:16   0:39 emacs .bashrc

the first core of my quad core processor is maxed out, and if I "kill
6607" that core immediately goes back to normal...

Problem with Emacs

Steven P. Ulrick — 2012-05-23T10:10:57

Hello, Everyone
For quite a while now, Emacs has ceased being useable on our system. 
For example, if I run "emacs .bashrc" in a terminal, Emacs starts up as 
expected, but the file cannot be edited.  I can use the mouse to select 
text in the portion of the file that is actually displayed in the 
terminal, but I cannot move the cursor(?) or delete/add/change any text.
I have the following alias in ~/.bashrc that has worked perfectly for me 
for quite a while:
alias emacs="unset DISPLAY && emacs"

If I just run "/usr/bin/emacs" from a terminal the graphical version of 
Emacs opens the file file, and I can edit it as I wish.  I do NOT have 
xemacs installed on this system.

So, the way this is working for me now, if I want to use Emacs in a 
non-graphical console session, I am out of luck.  It does not make any 
difference what user I am logged in as, the problem is the same.  Also, 
here is the permissions on the file that I used earlier as my example:
-rw-r--r-- 1 steve steve 6.9K May 23 04:50 .bashrc

So,

Re: wifi bit rate

JD — 2012-05-23T09:58:08

Sorry, no effect:
# iwconfig wlan1 rate 54M
# iwconfig wlan1
wlan1     IEEE 802.11bg  ESSID:"Private"
           Mode:Managed  Frequency:2.452 GHz  Access Point: 
00:AA:BB:CC:DD:EE
           Bit Rate=18 Mb/s   Tx-Power=20 dBm
           Retry  long limit:7   RTS thr:off   Fragment thr:off
           Power Management:off
           Link Quality=70/70  Signal level=-30 dBm
           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:52   Missed beacon:0

Re: wifi bit rate

JD — 2012-05-23T09:55:30

Hi John,
The link quality (signal strength) came back up
after a few  minutes, but bit rate remains fixed.

           Bit Rate=18 Mb/s   Tx-Power=20 dBm
           Retry  long limit:7   RTS thr:off   Fragment thr:off
           Power Management:off
           Link Quality=70/70  Signal level=-30 dBm
           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:50   Missed beacon

Re: wifi bit rate

John Horne — 2012-05-23T09:50:11

                        ^^^
'54M' not 'G'.




John.

Re: wifi bit rate

JD — 2012-05-23T09:43:20

One of them is a Brother brand wireless printer and it has a 54G card,
the other is a windows vista laptop and has 801.11N (300) card, and
the third is an Apple MacBookPro with an 802.11N (300) card).

I had a lot of work backlog jam, so I did not have the
time to switch back to the Atheros.
But I just tried it on the rtl card. Speed rate remains at 18 mb/s

# iwconfig wlan1 rate 54G
# iwconfig wlan1
wlan1     IEEE 802.11bg  ESSID:"Private"
           Mode:Managed  Frequency:2.452 GHz  Access Point: 
00:AA:BB:CC:DD:EE
           Bit Rate=18 Mb/s   Tx-Power=20 dBm
           Retry  long limit:7   RTS thr=2346 B   Fragment thr=2346 B
           Power Management:off
           Link Quality=70/70  Signal level=-32 dBm
           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:34   Missed beacon:0

# iwconfig wlan1 rts off frag off
# iwconfig wlan1
wlan1     IEEE 802.11bg  ESSID:"Private"
           Mode:Managed  Frequency:2.452 GHz  Access Point: 
00:AA:BB

Re: wifi bit rate

John Horne — 2012-05-23T09:25:27

Hi,

Ah. I don't think you mentioned that other clients were working fine.
Are these 802.11b/g cards or are they 802.11n but for some reason
running at 54Mb/s?

As said, you can change these on the fly for the card: 'iwconfig wlan0
rate 54M'




John.

Re: wifi bit rate

John Horne — 2012-05-23T09:22:08

Hi,

No need to use modprobe.d. Just run from the command line:

modprobe -r ath9k
modprobe ath9k debug=0xFFFF




John.

Re: wifi bit rate

John Horne — 2012-05-23T09:15:15

Hi,

But you can change them on the fly :-)
Just run (as root) 'iwconfig wlan0 rts off frag off' from the command
line. If things don't improve then you can set them back ('iwconfig
wlan0 rts 2346 frag 2346').




John.

Re: Bugzilla: after upgrade, no longer ML tag?

Reindl Harald — 2012-05-23T08:37:27


Am 23.05.2012 10:30, schrieb Pedro Francisco:

i can not confirm that it ever had

if it had and now missing than it is more a bugfix
than a bug - bugzilla is NOT a mailing-list

Re: Bugzilla: after upgrade, no longer ML tag?

Pedro Francisco — 2012-05-23T08:30:43

Snippet of Gmail's info of a subscribed bug's mail:
Latest email:
from: bugzilla< at >redhat.com
to: <me>
date: Mon, May 21, 2012 at 3:51 PM
subject: [Bug 814451] samba4 makes a mess preventing updates
mailed-by: redhat.com

Previous mail:
from: bugzilla< at >redhat.com
to: <me>
date: Mon, May 7, 2012 at 5:27 PM
subject: [Bug 814451] samba4 makes a mess preventing updates
mailing list: bugzilla.redhat.com
<------------------------------------------------------
mailed-by: redhat.com


Apparently bugzilla in the past added "mailing list:
bugzilla.redhat.com" and now it does not. Is this a "feature" or a
bug?

Re: [UPDATED:] Re: confusion on /sbin/ifconfig on F16

Reindl Harald — 2012-05-23T08:07:57


Am 23.05.2012 08:17, schrieb Paul Allen Newell:

edit "/etc/udev/rules.d/70-persistent-net.rules" (ONE LINE, replace MAC with yours)

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:50:56:bd:00:27", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
__________________________

this has NOTHING to do with i686 / x86_64
http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming

remove the package, edit config as statet above and that was it

Re: [UPDATED:] Re: confusion on /sbin/ifconfig on F16

Ed Greshko — 2012-05-23T07:26:09

No.  Not something that I've needed or wanted to do.

Re: [UPDATED:] Re: confusion on /sbin/ifconfig on F16

Paul Allen Newell — 2012-05-23T06:46:38

Ed:

Okay, that's a good question that I hadn't considered. So do you happen 
to know how to change the names?

Paul

Re: [UPDATED:] Re: confusion on /sbin/ifconfig on F16

Ed Greshko — 2012-05-23T06:33:29

It will continue to work....  Just not support some new features.


????  The "ip" command has nothing to do with the device/interface name.

It simply lists information on all the interfaces available on the
system...regardless of if they are up/down....   There is no "right" or "wrong".

[egreshko< at >meimei ~]$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: p128p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 40:61:86:7c:2b:db brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.18/24 brd 192.168.0.255 scope global p128p1
    inet6 fe80::4261:86ff:fe7c:2bdb/64 scope link
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 70:1a:04:f4:df:69 brd ff:ff:ff:ff:ff:ff
5: vboxnet0: <BROADCAST,MUL

Re: [UPDATED:] Re: confusion on /sbin/ifconfig on F16

Paul Allen Newell — 2012-05-23T06:17:49

Ed:

With all due respect, its become clear to me that ifconfig is obsolete 
and a solution which uses it doesn't have a future. Can you try to get 
the ip address with command "ip" on a i686 and x86_64 system without 
having to run a different command for each?

As for the "issue", I am still hoping someone can tell me that "ip addr 
show" giving a different device for the static IP on x86_64 and i686 is 
"not right" so I can bug it with confidence that I am not making a 
mistake (or let me know that I am making a mistake ... with enough info 
that I can confirm it is a pilot error)

Thanks,
Paul

Re: [UPDATED:] Re: confusion on /sbin/ifconfig on F16

Ed Greshko — 2012-05-23T05:49:04

Well, as you said, things are in transition....  And, if you did some google searches
you'd find that there were/are differences between how interface names appear(ed) at
various points depending on system architecture.  That seems to be your main "issue".

All that aside....  If you have a system with a single interface you can always do....

[egreshko< at >meimei test]$ /sbin/ifconfig | grep 'inet ' | grep -v '127.0.0.1' | cut -d
: -f 2 | awk '{ print $1}'
192.168.0.18

Re: [UPDATED:] Re: confusion on /sbin/ifconfig on F16

Paul Allen Newell — 2012-05-23T05:31:57

Ed:

Thanks for reply.

First problem is I think there is something wrong if "ip addr show" 
lists eth0 on x86_64 and em1 on i686. I know things are in transition, 
but I would expect that to be on a release by release, not sub-set of 
platform by platform as it makes scripts that work on one break on the 
other. I am trying to get some validation that I am not doing something 
wrong so I can submit as bug

Second problem is, given that, I can't figure out how to get "ip addr 
show" to work on both platforms. My fault for not including example as I 
was more focused on the possible bug and thinking I just needed to kick 
the ip command a few more times.

On x86_64, "ip addr show" gives:
+++

1: lo:<LOOPBACK,UP,LOWER_UP>  mtu 16436 qdisc noqueue state UNKNOWN
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
     inet 127.0.0.1/8 scope host lo
     inet6 ::1/128 scope host
        valid_lft forever preferred_lft forever
2: eth0:<BROADCAST,MULTICAST,UP,LOWER_UP>  mtu 1500 qdisc pfifo_fast state UP ql

Re: ZFS on linux for fedora

Edward M — 2012-05-23T05:11:35


   thanks for the link, I sometimes forget fedora also has forums, since 
iḿ used to only using mailing lists. :-)

Re: ZFS on linux for fedora

Edward M — 2012-05-23T05:08:01

    I appreciate  it, will give them a spin soon.

   Thank you for your time:-)