[gentoo-user] udev upgrade and non-working eth0

[gentoo-user] udev upgrade and non-working eth0

[Mrugesh Karnik]

Hi,

I upgraded to udev-103 yesterday. Since then, my internet hasn't been working.

I connect through eth0, which is a VIA Rhine adapter on my
motherboard. ifconfig shows the link to be up. But, I can't even ping
the gateway through eth0. I get destination unreachable replies.

This is what syslog tells me after bootup:

Nov 27 19:11:14 mrugeshkarnik kernel: eth0: link down

And this is the ifconfig output:

eth0      Link encap:Ethernet  HWaddr 00:0D:88:45:C1:C9
            inet addr:10.40.37.47  Bcast:10.40.37.255  Mask:255.255.255.0
	    UP BROADCAST MULTICAST  MTU:1500  Metric:1
            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
	    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
	    collisions:0 txqueuelen:1000
	    RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
	    Interrupt:18 Base address:0xe000

I don't see a RUNNING flag in there..

What do I do? I'm completely stuck without the internet on Gentoo.. :(

Thanks in advance.

Mrugesh.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] udev upgrade and non-working eth0

[Uwe Thiem]

On 27 November 2006 15:58, Mrugesh Karnik wrote:

> And this is the ifconfig output:
>
> eth0      Link encap:Ethernet  HWaddr 00:0D:88:45:C1:C9
>             inet addr:10.40.37.47  Bcast:10.40.37.255  Mask:255.255.255.0
> 	    UP BROADCAST MULTICAST  MTU:1500  Metric:1
>             RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> 	    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> 	    collisions:0 txqueuelen:1000
> 	    RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
> 	    Interrupt:18 Base address:0xe000
>
> I don't see a RUNNING flag in there..

There's "UP"  at the begin of the thrid line.

What does "route -n" say?

Uwe

-- 
Mark Twain: I rather decline two drinks than a German adjective.
http://www.SysEx.com.na
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] udev upgrade and non-working eth0

[blackhawk]

> Hi,
>
> I upgraded to udev-103 yesterday. Since then, my internet hasn't been
> working.
>
> I connect through eth0, which is a VIA Rhine adapter on my
> motherboard. ifconfig shows the link to be up. But, I can't even ping
> the gateway through eth0. I get destination unreachable replies.
>
> This is what syslog tells me after bootup:
>
> Nov 27 19:11:14 mrugeshkarnik kernel: eth0: link down
>
> And this is the ifconfig output:
>
> eth0      Link encap:Ethernet  HWaddr 00:0D:88:45:C1:C9
>             inet addr:10.40.37.47  Bcast:10.40.37.255  Mask:255.255.255.0
> 	    UP BROADCAST MULTICAST  MTU:1500  Metric:1
>             RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> 	    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> 	    collisions:0 txqueuelen:1000
> 	    RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
> 	    Interrupt:18 Base address:0xe000
>
> I don't see a RUNNING flag in there..
>
> What do I do? I'm completely stuck without the internet on Gentoo.. :(
>
> Thanks in advance.
>
> Mrugesh.
> --
> gentoo-user@gentoo.org mailing list
>
>
Hello,

    Do you have coldplug installed ?
    What's the content of /etc/conf.d/net ?

    Could you post more debugging information please because it's
difficult t osolve your problem with your information... It seems that
your interface is configured with a private adress, which isn't
normal...

    What's the output of route -n too please ?

Regards.

Blackhawk

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: udev upgrade and non-working eth0

[7v5w7go9ub0o]

FWIW, I also upgraded and find that my laptop, which previously had eth0  
and eth1 for its two cards (one wired and one wireless) now has eth0 and  
eth2.

After editing my scripts and configurations (e.g. wpa_supplicant startup  
and kismet conf), things seem to work fine.

HTH, newbie
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: udev upgrade and non-working eth0

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 529 bytes --]

On Mon, 27 Nov 2006 09:36:38 -0500, 7v5w7go9ub0o wrote:

> FWIW, I also upgraded and find that my laptop, which previously had
> eth0 and eth1 for its two cards (one wired and one wireless) now has
> eth0 and eth2.

Do you have IEEE1394_ETH1394 set in your kernel? If so, it's possible
that eth1 is being set to your Firewire interface. You can use udev
rules to ensure that the interfaces are named as you wish. 


-- 
Neil Bothwick

Newsflash! Explosion at M$ beta testsite - Infinite number of monkeys
killed.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Re: udev upgrade and non-working eth0

[Mrugesh Karnik]

On 27/11/06, 7v5w7go9ub0o <7v5w7go9ub0o@gmail.com> wrote:
> FWIW, I also upgraded and find that my laptop, which previously had eth0
> and eth1 for its two cards (one wired and one wireless) now has eth0 and
> eth2.
>
> After editing my scripts and configurations (e.g. wpa_supplicant startup
> and kismet conf), things seem to work fine.

Right. The idiosyncrasies!

I checked dmesg (Should have done that earlier.. duh!). Here's the output:

eth0: RealTek RTL8139 at 0xe000, 00:0d:88:45:c1:c9, IRQ 18
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
eth0: link down

eth1: VIA Rhine II at 0xfa002000, 00:13:d3:60:4a:a5, IRQ 19.
eth1: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1.

Now, how do I swap the two cards? I don't know how to write udev rules
yet. I was planning on learning that next week.. I guess I should
learn it as soon as the internet works..

Anyway, I'd very much appreciate the exact solution from the list right now :)

Thanks to everyone who replied.

And well, the ip addresses are correct. My ISP gives me a NAT'ed
connection (duh! :/).

Thanks again,
Mrugesh
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: udev upgrade and non-working eth0

[Richard Fish]

On 11/27/06, Mrugesh Karnik <mrugeshkarnik@gmail.com> wrote:
> Now, how do I swap the two cards? I don't know how to write udev rules
> yet. I was planning on learning that next week.. I guess I should
> learn it as soon as the internet works..

Add the following to /etc/udev/rules.d/10-local.rules:

# ethernet devices
ACTION=="add", SUBSYSTEM=="net", SYSFS{address}=="00:13:d3:60:4a:a5",
NAME="eth0"
ACTION=="add", SUBSYSTEM=="net", SYSFS{address}=="00:0d:88:45:c1:c9",
NAME="eth1"

-Richard
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: udev upgrade and non-working eth0

[Mrugesh Karnik]

On 27/11/06, Richard Fish wrote:
> On 11/27/06, Mrugesh Karnik <mrugeshkarnik@gmail.com> wrote:
> > Now, how do I swap the two cards? I don't know how to write udev rules
> > yet. I was planning on learning that next week.. I guess I should
> > learn it as soon as the internet works..
>
> Add the following to /etc/udev/rules.d/10-local.rules:
>
> # ethernet devices
> ACTION=="add", SUBSYSTEM=="net", SYSFS{address}=="00:13:d3:60:4a:a5",
> NAME="eth0"
> ACTION=="add", SUBSYSTEM=="net", SYSFS{address}=="00:0d:88:45:c1:c9",
> NAME="eth1"

No go. They didn't swap.

Mrugesh
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: udev upgrade and non-working eth0

[Richard Fish]

On 11/27/06, Mrugesh Karnik <mrugeshkarnik@gmail.com> wrote:
> > # ethernet devices
> > ACTION=="add", SUBSYSTEM=="net", SYSFS{address}=="00:13:d3:60:4a:a5",
> > NAME="eth0"
> > ACTION=="add", SUBSYSTEM=="net", SYSFS{address}=="00:0d:88:45:c1:c9",
> > NAME="eth1"
>
> No go. They didn't swap.

Just in case, you did make those 2, not 4, lines right?  Silly gmail
word-wrapping... :-(

What do "udevtest /class/net/eth0" and "udevtest /class/net/eth1"
report?  Also "udevinfo -a -p /class/net/eth0" and "udevinfo -a -p
/class/net/eth1".

-Richard
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: udev upgrade and non-working eth0

[Mrugesh Karnik]

On Tuesday 28 November 2006 04:16, Richard Fish wrote:
> On 11/27/06, Mrugesh Karnik <mrugeshkarnik@gmail.com> wrote:
> > > # ethernet devices
> > > ACTION=="add", SUBSYSTEM=="net", SYSFS{address}=="00:13:d3:60:4a:a5",
> > > NAME="eth0"
> > > ACTION=="add", SUBSYSTEM=="net", SYSFS{address}=="00:0d:88:45:c1:c9",
> > > NAME="eth1"
> >
> > No go. They didn't swap.
>
> Just in case, you did make those 2, not 4, lines right?  Silly gmail
> word-wrapping... :-(
>
> What do "udevtest /class/net/eth0" and "udevtest /class/net/eth1"
> report?  Also "udevinfo -a -p /class/net/eth0" and "udevinfo -a -p
> /class/net/eth1".

Aaah! Feels so good to be writing this email in kmail again!! So, as you might 
guess, its working now.

The problem apparently was that I used upper case letters in the hex numbers. 
I didn't know those hex numbers are lower case only :s

Oh and I HAD put them on two lines.

Anyway, now I get this message during bootup:

udevd-event[3110]: rename_netif: error changing net interface name eth0_rename 
to eth1: No such device.

It works fine though. But, how do I get rid of that message? Its just annoying 
to look at :/

/me thinks about setting RC_DEVICE_TARBALL="yes"

Anyway, all you people, thanks for your help. Very much appreciated!

-- 
----------------------------------------
Mrugesh Karnik
GPG Key 0xBA6F1DA8
Public key on http://wwwkeys.pgp.net
----------------------------------------
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: udev upgrade and non-working eth0

[Richard Fish]

On 11/27/06, Mrugesh Karnik <mrugeshkarnik@gmail.com> wrote:
> udevd-event[3110]: rename_netif: error changing net interface name eth0_rename
> to eth1: No such device.

Hmm, haven't seen this error, but these rules (based on
70-persistent-net.rules) might work better:

SUBSYSTEM=="net", ATTRS{address}=="00:13:d3:60:4a:a5", NAME="eth0"
SUBSYSTEM=="net", ATTRS{address}=="00:0d:88:45:c1:c9", NAME="eth1"

> /me thinks about setting RC_DEVICE_TARBALL="yes"

This won't help for ethernet naming.  There is no /dev/eth* device
node, after all.

-Richard
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: udev upgrade and non-working eth0

[Mrugesh Karnik]

On Tuesday 28 November 2006 06:38, Richard Fish wrote:
> On 11/27/06, Mrugesh Karnik <mrugeshkarnik@gmail.com> wrote:
> > udevd-event[3110]: rename_netif: error changing net interface name
> > eth0_rename to eth1: No such device.
>
> Hmm, haven't seen this error, but these rules (based on
> 70-persistent-net.rules) might work better:
>
> SUBSYSTEM=="net", ATTRS{address}=="00:13:d3:60:4a:a5", NAME="eth0"
> SUBSYSTEM=="net", ATTRS{address}=="00:0d:88:45:c1:c9", NAME="eth1"

Stupid question perhaps.. but does it matter in which files the rules go? I 
can see a 75-persistent-net-generator.rules file in there..

> > /me thinks about setting RC_DEVICE_TARBALL="yes"
>
> This won't help for ethernet naming.  There is no /dev/eth* device
> node, after all.

True. Hmm.
-- 
----------------------------------------
Mrugesh Karnik
GPG Key 0xBA6F1DA8
Public key on http://wwwkeys.pgp.net
----------------------------------------
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: udev upgrade and non-working eth0

[Richard Fish]

On 11/27/06, Mrugesh Karnik <mrugeshkarnik@gmail.com> wrote:
> On Tuesday 28 November 2006 06:38, Richard Fish wrote:
> > On 11/27/06, Mrugesh Karnik <mrugeshkarnik@gmail.com> wrote:
> > > udevd-event[3110]: rename_netif: error changing net interface name
> > > eth0_rename to eth1: No such device.
> >
> > Hmm, haven't seen this error, but these rules (based on
> > 70-persistent-net.rules) might work better:
> >
> > SUBSYSTEM=="net", ATTRS{address}=="00:13:d3:60:4a:a5", NAME="eth0"
> > SUBSYSTEM=="net", ATTRS{address}=="00:0d:88:45:c1:c9", NAME="eth1"
>
> Stupid question perhaps.. but does it matter in which files the rules go? I

Not really.  The files are parsed in alphabetical order, so if you
have a NAME= setting in 10-file, it will override anything in a
"later" file. 10-local.rules is the normal place for your own rules to
go.

> can see a 75-persistent-net-generator.rules file in there..

Hmm, not sure how I got a 70-persistent-net.rules.  There is some
interaction between that and 75-persistent-net-generator.rules (and
the /lib/udev/write_net_rules script), but I'm a bit too tired to
figure it out ATM.  It looks like 70-... should be created by the
write_net_rules script...

-Richard
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: udev upgrade and non-working eth0

[Mrugesh Karnik]

On Tuesday 28 November 2006 07:31, Richard Fish wrote:
> > can see a 75-persistent-net-generator.rules file in there..
>
> Hmm, not sure how I got a 70-persistent-net.rules.  There is some
> interaction between that and 75-persistent-net-generator.rules (and
> the /lib/udev/write_net_rules script), but I'm a bit too tired to
> figure it out ATM.  It looks like 70-... should be created by the
> write_net_rules script...


RULES_FILE='/etc/udev/rules.d/70-persistent-net.rules'

That's the first line of write_net_rules.

-- 
----------------------------------------
Mrugesh Karnik
GPG Key 0xBA6F1DA8
Public key on http://wwwkeys.pgp.net
----------------------------------------
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: udev upgrade and non-working eth0

[Richard Fish]

On 11/27/06, Mrugesh Karnik <mrugeshkarnik@gmail.com> wrote:
> On Tuesday 28 November 2006 07:31, Richard Fish wrote:
> > > can see a 75-persistent-net-generator.rules file in there..
> >
> > Hmm, not sure how I got a 70-persistent-net.rules.  There is some
> > interaction between that and 75-persistent-net-generator.rules (and
> > the /lib/udev/write_net_rules script), but I'm a bit too tired to
> > figure it out ATM.  It looks like 70-... should be created by the
> > write_net_rules script...
>
>
> RULES_FILE='/etc/udev/rules.d/70-persistent-net.rules'
>
> That's the first line of write_net_rules.

Right.  I just wasn't able to figure out why you didn't already have
this file created, nor why my laptop had it but not my desktop.

So the story is that 75-persistent-net-generator.rules will call the
script when ethernet devices are added, and it is up to the
write_net_rules script to generate 70-persistent-net.rules.  The
problem is that when udev starts very early in the boot process, your
root filesystem may still be mounted read-only, preventing this file
from being created.

This worked on my laptop, because I added module aliases to prevent
udev from coldplugging the ipw3945 driver, since it requires a daemon
to be running in order to work and that required /var to be mounted.
The module is loaded later in the boot process, after all of the
filesystems are mounted read-write, and that allowed udev to create
the rules file for me, but only for that adapter.

The upshot of this is this: by far the easiest way to solve the
net-naming problem is to run

/lib/udev/write_net_rules all_interfaces

This will generate the rules for all interfaces, and then you can just
edit the file to change the names as you like.  So I guess I'll know
that for the next person that asks. :-P

-Richard
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: udev upgrade and non-working eth0

[Mick]

[-- Attachment #1: Type: text/plain, Size: 2699 bytes --]

On Wednesday 29 November 2006 17:33, Richard Fish wrote:
> On 11/27/06, Mrugesh Karnik <mrugeshkarnik@gmail.com> wrote:
> > On Tuesday 28 November 2006 07:31, Richard Fish wrote:
> > > > can see a 75-persistent-net-generator.rules file in there..
> > >
> > > Hmm, not sure how I got a 70-persistent-net.rules.  There is some
> > > interaction between that and 75-persistent-net-generator.rules (and
> > > the /lib/udev/write_net_rules script), but I'm a bit too tired to
> > > figure it out ATM.  It looks like 70-... should be created by the
> > > write_net_rules script...
> >
> > RULES_FILE='/etc/udev/rules.d/70-persistent-net.rules'
> >
> > That's the first line of write_net_rules.
>
> Right.  I just wasn't able to figure out why you didn't already have
> this file created, nor why my laptop had it but not my desktop.
>
> So the story is that 75-persistent-net-generator.rules will call the
> script when ethernet devices are added, and it is up to the
> write_net_rules script to generate 70-persistent-net.rules.  The
> problem is that when udev starts very early in the boot process, your
> root filesystem may still be mounted read-only, preventing this file
> from being created.
>
> This worked on my laptop, because I added module aliases to prevent
> udev from coldplugging the ipw3945 driver, since it requires a daemon
> to be running in order to work and that required /var to be mounted.
> The module is loaded later in the boot process, after all of the
> filesystems are mounted read-write, and that allowed udev to create
> the rules file for me, but only for that adapter.
>
> The upshot of this is this: by far the easiest way to solve the
> net-naming problem is to run
>
> /lib/udev/write_net_rules all_interfaces
>
> This will generate the rules for all interfaces, and then you can just
> edit the file to change the names as you like.  So I guess I'll know
> that for the next person that asks. :-P

Not sure if/how it is related to the OP, but this is what was created in 
my /etc/udev/rules.d/70-persistent-net.rules:
=====================================
# USB device 0x050d:0x7050 (rt2500usb)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:11:50:18:55:3f", 
ATTRS{type}=="1", NAME="wlan0"
=====================================

However, if I boot with the USB WiFi adaptor plugged in it, the device is not 
being detected.  If I plug it in after the system has booted then there is no 
problem.  The USB devices are 'udev-plugged' relatively late in the boot 
process, well after udevd has started.  Therefore I cannot understand why 
this adaptor is not being detected.  Any ideas?
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Re: udev upgrade and non-working eth0

[Mrugesh Karnik]

On Wednesday 29 November 2006 23:03, Richard Fish wrote:
> The upshot of this is this: by far the easiest way to solve the
> net-naming problem is to run
>
> /lib/udev/write_net_rules all_interfaces
>
> This will generate the rules for all interfaces, and then you can just
> edit the file to change the names as you like.  So I guess I'll know
> that for the next person that asks. :-P

Cool, that worked perfectly! I remember seeing an error about write_net_rules 
not being able to create a file during bootup, twice..

Btw, I really would like to master udev. Good documentation? I can see a 
couple of links at the bottom of the Gentoo udev guide. Anything else I 
should be referring to?

Thanks a lot btw. :)

-- 
----------------------------------------
Mrugesh Karnik
GPG Key 0xBA6F1DA8
Public key on http://wwwkeys.pgp.net
----------------------------------------
-- 
gentoo-user@gentoo.org mailing list