From: Gavin S. <gav...@gm...> - 2011-10-04 23:57:26
|
I found an article that mentioned creating an empty generator rule in /etc/udev/rules.d. That will prevent the one in /lib from running. This leaves me with the preferred outcome of the only eth device becoming eth0. I have added a touch command to my udev recipe. Hopefully this will fix the problem. I'm wondering if this is something that should not be the default for the gumstix platform? Having your devices move from board to board with the same SD card does not seem like the behavior anyone would want. Gavin S On Tue, Oct 4, 2011 at 3:29 PM, Austin, Alex <Ale...@sp...> wrote: > >From my understanding, /lib/udev/rules.d/ are global rules that come > With udev, and are run alongside those in /etc/udev/rules.d/. /etc > rules are machine-specific, while /lib/udev rules are global and > apply to any computer. > > -----Original Message----- > From: Gavin Swanson [mailto:gav...@gm...] > Sent: Tuesday, October 04, 2011 5:08 PM > To: General mailing list for gumstix users. > Subject: Re: [Gumstix-users] Changed SMSC chip? > > I have discovered this problem is nothing to do with a new chip but > rather the obscure 70-persistent-net.rules file forcing the eth > interfaces to seemingly arbitrary numbers (eth4 etc). The file is not > installed by udev-151 but appears to get created sometime during the > first run. It is not listed in the files-in-image.txt as being under > /etc/udev/rules.d > > Does anyone know where the file gets created so I can prevent it from > being created? It may be easier to add a command to the end of the > first boot that deletes the file, but I'd rather stop it from being > created in the first place. > > I grepped the recipe directory for something that references the > generator or the write_net_rules script. It only gets copied in by the > nokia900 stuff. > > The work directory for udev shows the > 75-persistent-net-generator.rules and write-net-rules files being > copied to /lib/udev/[rules.d]. but nothing ever seems to run the files > or link the /lib/udev stuff to /etc/udev/rules.d where it would > actually get run. > > Gavin S > > On Mon, Oct 3, 2011 at 5:46 PM, Gavin Swanson <gav...@gm...> wrote: >> It would appear that Gumstix changed the SMSC ethernet chip within the >> run of Tobi boards that use the newer USB A port. I have a couple >> units with the A1015-AB24 Chip that work. and a few others with >> A1046-AB24 that don't. The latter of which will work with an older >> kernel. I am running 2.6.39. Is there something I need to add to my >> image or a command I need to run to get the ethernet working on the >> "newer" chips? >> >> Thanks >> >> Gavin S >> > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |