gmane.linux.suse.general

wireless interface not achieving full bit rate

Per Jessen — 2013-05-19T13:07:58

In roughly the same position, i.e. with 2 meters of each other, I have
two systems both connected over wifi.  One is my livingroom mythtv box,
the other is a laptop.  
Occasionally the mythtv machine will start having pauses in video+audio
delivery and I've narrowed this down to being due to a lower wifi
bitrate - today I saw 18Mbit/s and 9Mbit/s whilst the laptop would be
doing fine at 54Mbit/s.  I stoppped and started the tvbox interface,
didn't help. I reboot the access point, didn't help.  Then I rebooted
the mythtv box, and voila! bitrate was re-established at 54Mbit/s.  It
is as if the bitrate slowly deteriorates.  Occasionally the tvbox will
also get completely stuck, which I'm beginning to suspect is the wifi
connection failing renegotiation.  
The WLAN card is Ralink corp. RT2561/RT61 - I think it's a D-Link. Has
anyone experienced something similar?

Re: Clone SSD via rsync?

Markus Egg — 2013-05-19T12:10:42

Am 04/04/13 23:11, schrieb MarkusGMX:

Any ideas?

Thanks in advance
ME

Re: new network interface naming scheme

Andrey Borzenkov — 2013-05-19T09:33:42

В Sun, 19 May 2013 09:59:39 +0200
Per Jessen <per< at >computer.org> пишет:


If it will be found that it has problems that are too hard to solve -
yes.

I think it is too early to make any statement at this point.

Re: Re: new network interface naming scheme (result of systemd & initrd)

Per Jessen — 2013-05-19T08:03:00


You mean without an initrd?  Not me, I'm afraid.  Using an initrd works
very well for me, without exception.

Re: new network interface naming scheme

Per Jessen — 2013-05-19T07:59:39

[snip]

Well, the new naming scheme also does not always work reliably (nor
consistently). What do you propose we do - drop it too? :-)


I am discussing it here where it is important, in an openSUSE user
forum.  If we don't want to alienate our user base, we should provide a
way of reverting to the previous behaviour.

Re: new network interface naming scheme

Andrey Borzenkov — 2013-05-19T07:52:05

В Sun, 19 May 2013 09:19:22 +0200
Per Jessen <per< at >computer.org> пишет:


The problem is, renaming of interfaces did not always work reliably.
Which was the exact reason why it was dropped upstream.

If you believe this decision is wrong and renaming can be done reliably
you should really discuss it upstream and convince them to revert to
old behavior.

Re: new network interface naming scheme

Per Jessen — 2013-05-19T07:19:22


Disabling the new naming scheme is easy, but what we need is an option
to revert to the previous openSUSE behaviour of having persistent net
names:

https://bugzilla.novell.com/show_bug.cgi?id=820589

Re: new network interfaqce naming scheme (brought to you by systemd&initrd)

Linda Walsh — 2013-05-18T23:21:35

---
liar liar pants on fire.

www/ Software/ systemd/ PredictableNetworkInterfaceNames
Back to systemd
Predictable Network Interface Names
---
Why is the required?  Because no booting from
Harddisk with writable storage.

Another reason why booting from initrd is bad.

Re: new network interfaqce naming scheme

Linda Walsh — 2013-05-18T23:19:05

---
I have never had that... and never had a problem.

Keeping uniform naming allows firewalls and traffic shaping to work.

So all that will now break?

Great -- based on whatever slot you happen to put your card
in?   how lovely.

Re: new network interfaqce naming scheme (result of systemd & initrd)

Linda Walsh — 2013-05-18T23:17:54

       [... by driver name?]
----
It's worse than this.. it's going to the windows
style of naming things by its hardware address...
bustype-busnumber,slot,unit#... ... all that stuff that's in
the windows registry and windows realized users didn't want to see..
so they give users stable name in the UI....but not w/systemd
HW-addresses only!

Which is a horrible choice for portability and maintenance... they try to claim
it's good if you slip in a new card into the same slot.

But more often, I add new cards and they are in different slots!...
I repurpose the old .. but I don't want to have to change over all my scripts
(fW, traffic flow/ management...etc)...That's just being evil to system admins
(not to mention users)...


They are whining about not having access to a permanent storage to store
the mappings in (like the:

/etc/udev/rules.d/70-persistent-net.rules,

 >>> hard disk... <<<

THis is all related to booting from a ***ramdisk** -- no permanent storage...
this brought this problem, so their fix i

Re: 5 years later and still whining

Thomas Taylor — 2013-05-18T21:03:05

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, 18 May 2013 08:29:08 -0500
Billie Walsh <bilwalsh< at >swbell.net> wrote:


Some of us still have KDE2 on older systems.

73, KG7CFC
Tom

Re: extinction level events are also examples of change - love to see you adapt to such!

Billie Walsh — 2013-05-18T20:36:14

I came to Linux when KDE# was perfect, or very nearly so. It was 
fantastic. THEN, change happened. Was I happy about it. Not 
particularly. I was more than happy as things were. I decided to install 
a KDE4 system to my spare computer to play with but stay with KDE3 as 
long as possible. They say that life is what happens while your busy 
making other plans. Life happened. My primary computer died, D ... E ... 
D  dead. Took out EVERYTHING. The magic smoke escaped. What to do, what 
to do. I have a perfectly working, brand new install of KDE4 with 
everything I needed already on it. While I acquired a new computer I was 
pushed head first into KDE4 when it was first released, at best a Beta 
version in my opinion. Sink or swim, I was in it. It was a case of adapt 
or die. I chose to adapt and not spend all my time whining about it. 
When I got my new system built up I went with KDE4. Five years later and 
I find that KDE4 is just as good as, better in some ways than, KDE3.

The universe, and everything in

Re: 5 years later and still whining

Billie Walsh — 2013-05-18T20:19:24

He's more than welcome to it.

extinction level events are also examples of change - love to see you adapt to such!

Linda Walsh — 2013-05-18T19:37:10

----
Change is not a constant though.  Gradual change allows adaptation
and evolution.  History and the universe are full of examples where
change happened, and it wiped out entire species and planets.

Change is not what is at issue.  *speed* of change* and how
long people have to adapt is.  In nature, change that allows survival to
happen, takes a LONG time.   Changes that happen in a few weeks or months
usually result in large scale extinctions.

A solar flare, moon hitting the planet, bullet in the head are all
examples of nearly instantaneous change that most humans would not survive.
Are you suggesting it is unreasonable for us to NOT want such changes?

Re: 5 years later KDE4 still doesn't

James Knott — 2013-05-18T18:52:42

This is one I miss too.  I use the KDE3 desktop and classic menu, as I 
hate the new desktop and menu.  It'd be nice to have that search 
function back again.

Re: 5 years later KDE4 still doesn't

James Knott — 2013-05-18T18:47:58

As much as I use the GUI, for some things the command line and config 
files are superior.  For run of the mill, every day stuff, a GUI is 
usually fine.

Re: 5 years later and still whining

Michael S. Dunsavage — 2013-05-18T18:41:06

I think he wants add

  "The only universal constant is change. If a species can not adapt it
goes extinct. That's the law of the universe, adapt or die. "

to his signature

"

Re: 5 years later and still whining

Billie Walsh — 2013-05-18T18:39:27

I have no idea what your talking about, however, you have my permission.

Re: 5 years later and still whining

Anton Aylward — 2013-05-18T18:10:48

Billie Walsh said the following on 05/18/2013 09:29 AM:

I might, if you'll permit, make the automatic and permanent signature 
block for my postings to this list ...

Re: new network interfaqce naming scheme

Per Jessen — 2013-05-18T17:13:45


Yes, I know and I am grateful. If this new scheme had been forcibly
imposed on everyone in a one-size-will-fit-all Microsoft way, you would
have heard a much different reaction.


Today it is done by way of /etc/udev/rules.d/70-persistent-net.rules
using the MAC-address as the key.  In my experience, the initial
automatically generated rules are good for 90-95% of the cases.

Re: new network interfaqce naming scheme

Andrey Borzenkov — 2013-05-18T16:53:01

В Sat, 18 May 2013 17:59:56 +0200
Per Jessen <per< at >computer.org> пишет:


Well, this makes further discussion pointless.

You can continue to use eth0 further, it is easy to disable new naming
scheme.

But one thing I wonder is


How exactly do you *assign* them?