Hi,
Can anyone tell me if this (see image below) button works? If it does, does it do what I am assuming that it does?
That is, it blinks the led’s on the respective network card, so that I can mach the physical connector with the currently selected ethernet port.
Regards, Martin
PS - This is currently 13.1. But I have not seen any evidence of working in any of the previous releases or alternative hardware configurations.
http://www.mpr75.talktalk.net/blink.png
On 2013-12-16 14:46, martinprowe wrote:
>
> Hi,
>
> Can anyone tell me if this (see image below) button works?
Dunno.
> If it does,
> does it do what I am assuming that it does?
> That is, it blinks the led’s on the respective network card, so that I
> can mach the physical connector with the currently selected ethernet
> port.
That’s what I assume.
> PS - This is currently 13.1. But I have not seen any evidence of working
> in any of the previous releases or alternative hardware configurations.
Well, you made me test it (12.3). I tried it on my second socket, and it
did not blink.
If you create a bugzilla on it, I’ll add a “me too”.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
On Mon 16 Dec 2013 01:46:02 PM CST, martinprowe wrote:
Hi,
Can anyone tell me if this (see image below) button works? If it does,
does it do what I am assuming that it does?
That is, it blinks the led’s on the respective network card, so that I
can mach the physical connector with the currently selected ethernet
port.
Regards, Martin
PS - This is currently 13.1. But I have not seen any evidence of working
in any of the previous releases or alternative hardware configurations.
[image: http://www.mpr75.talktalk.net/blink.png]
Hi
Does it work with;
ethtool -p <interface> 5
Does the interface and module have to support this feature?
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLED 11 SP3 (x86_64) GNOME 2.28.0 Kernel 3.0.101-0.8-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
On 2013-12-16 16:10, malcolmlewis wrote:
> Does the interface and module have to support this feature?
Maybe.
In which case, YaST should say so, so that we don’t squeeze into tight
and difficult places looking for the blinking led.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Thank you both,
Yes - That’s to “gotcha” Malcolm!
Checking each of my interfaces, I find that my Intel Server cards do flash with the ethtool commands AND Yast2 GUI.
However, with my cheepie PCIe cards, I get “Operation not supported” on the ethtool command line, that you don’t see in the Yast2 GUI.
Regards, Martin.
PS - What’s with the new (13.1) ethernet port naming scheme?
On 12/16/2013 10:46 AM, martinprowe wrote:
> PS - What’s with the new (13.1) ethernet port naming scheme?
The new version of udev is what changed the naming. On machines with more than
one identical interfaces, the choice of name could be different from boot to
boot. On headless servers, this was a real PITA. To correct that, udev was
changed to make the name be dependent on the bus, which will remain constant
unless the card is moved. Thus on one of my systems, lspci shows the following
for the network card:
00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
and udev names it enp0s7 for EtherNet Pci bus 7 Subdevice 0.
If you want the old name, you should write one of the old-style rules for
/etc/udev/rules.d/70-persistent-net.rules. The necessary line is
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="XX:XX:XX:XX:XX:XX", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth0"
/code/
That should all be on one line, and the XX's replace with the MAC address of
your device.Thank you for the explanation.
And, no, I’ve no need to change back to the old naming system. Bit of a fan of udev…
Regards, Martin
On 2013-12-16 18:51, Larry Finger wrote:
> If you want the old name, you should write one of the old-style rules
> for /etc/udev/rules.d/70-persistent-net.rules. The necessary line is
You can do it also in YaST. Netowrk config, edit entry, Hardware tab,
press “change” button. Actually, it writes that file:
> Eleanor4:~ # cat /etc/udev/rules.d/70-persistent-net.rules
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0c:29:5f:45:90", ATTR{type}=="1", NAME="eth0"
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)