From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1GpUjV-00025a-Vm for garchives@archives.gentoo.org; Wed, 29 Nov 2006 19:04:38 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id kATJ13qF024892; Wed, 29 Nov 2006 19:01:03 GMT Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by robin.gentoo.org (8.13.8/8.13.8) with ESMTP id kATIul1l024096 for ; Wed, 29 Nov 2006 18:56:48 GMT Received: by nf-out-0910.google.com with SMTP id c31so4621573nfb for ; Wed, 29 Nov 2006 10:56:47 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:reply-to:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; b=dXsJRyUtch5WqoMmg1WWyTurEl1YRepA84VdYB82A4L+m59hp4jpvGnnbBJW45TwAx5d5bwau4Xf4NdPJ6upxltRNFGExqRkoP0+teD6+ic4lYq9O8GhICtSagXOkocA2REUXD/jA1SA/+gSmeeKBgCKnMXhvRwwk2L2/ai3djA= Received: by 10.49.90.18 with SMTP id s18mr6722842nfl.1164826607157; Wed, 29 Nov 2006 10:56:47 -0800 (PST) Received: from m281-mp1.cvx1-c.bre.dial.ntli.net ( [62.255.117.25]) by mx.google.com with ESMTP id o9sm30135796nfa.2006.11.29.10.56.34; Wed, 29 Nov 2006 10:56:46 -0800 (PST) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: udev upgrade and non-working eth0 Date: Wed, 29 Nov 2006 18:45:10 +0000 User-Agent: KMail/1.9.5 References: <2b49f0c80611270558n792864dbtc209ed27423d5d6c@mail.gmail.com> <200611280749.49142.mrugeshkarnik@gmail.com> <7573e9640611290933o16ea01e8sd7b53db30e14d7b6@mail.gmail.com> In-Reply-To: <7573e9640611290933o16ea01e8sd7b53db30e14d7b6@mail.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart14753132.gzLANzDrdu"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200611291845.21401.michaelkintzios@gmail.com> X-Archives-Salt: bac576f7-5fa6-4e96-8a34-7bb163370caa X-Archives-Hash: 1eb7967ddd0456aa0bd0db8d38cea87d --nextPart14753132.gzLANzDrdu Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 29 November 2006 17:33, Richard Fish wrote: > On 11/27/06, Mrugesh Karnik 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=3D'/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=20 my /etc/udev/rules.d/70-persistent-net.rules: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D # USB device 0x050d:0x7050 (rt2500usb) SUBSYSTEM=3D=3D"net", DRIVERS=3D=3D"?*", ATTRS{address}=3D=3D"00:11:50:18:5= 5:3f",=20 ATTRS{type}=3D=3D"1", NAME=3D"wlan0" =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D However, if I boot with the USB WiFi adaptor plugged in it, the device is n= ot=20 being detected. If I plug it in after the system has booted then there is = no=20 problem. The USB devices are 'udev-plugged' relatively late in the boot=20 process, well after udevd has started. Therefore I cannot understand why=20 this adaptor is not being detected. Any ideas? =2D-=20 Regards, Mick --nextPart14753132.gzLANzDrdu Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQBFbdVB5Fp0QerLYPcRAltSAKCo5SD0sF0X5mrW+o3o9nOfTOHGHgCfStXP 3OQEpqdBJVMkvZgev8/Xwvc= =+Ntg -----END PGP SIGNATURE----- --nextPart14753132.gzLANzDrdu-- -- gentoo-user@gentoo.org mailing list