From: Richman1234 <ric...@na...> - 2010-03-30 15:42:17
|
I am setting up a new Gumstix overo fire with a tobi board. I have added 'eth0' with the network manager, and configured it with static IP. I ran #ifup eth0, and everything worked great. I have asked a question like this before, and was told to add: smsc911x to /etc/modules so that eth0 would load automatically on boot. I did this and rebooted, but eth0 didn't load. I ran #ifup eth0 and everything worked great again. Can someone tell me why eth0 will not load on boot? Please keep it simple, I'm new to this. Thanks -- View this message in context: http://old.nabble.com/eth0-dosn%27t-auto-load-on-boot-tp28084414p28084414.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Trevor W. <two...@gm...> - 2010-03-30 16:23:49
|
There are 2 things that need to happen to allow your system to handle ethernet traffic over a specific interface: 1) the kernel needs to have the specific code available which enables it to communicate with the specific hardware 2) the interface needs to be configured Loading the kernel module (smsc911x) fulfills the first part. This inserts the code of a loadable kernel module into the running kernel. Putting the module's name in the /etc/modules file directs various startup scripts to load that module into the kernel on startup. ifup'ing the interface fulfills the second part, namely configuring the device. The ifup script will consult various configuration files to, for example, set a static IP address, use DHCP, or (in the case of wireless) specify the SSID to use. |
From: Andrew K. (m. l. account) <ak...@mi...> - 2010-03-31 00:27:51
|
On Tuesday 30 March 2010 12:23:42 pm Trevor Woerner wrote: > Loading the kernel module (smsc911x) fulfills the first part. This > inserts the code of a loadable kernel module into the running kernel. > Putting the module's name in the /etc/modules file directs various > startup scripts to load that module into the kernel on startup. I have noticed that on my Overo Earth + Tobi that about 50% of the time the smsc911x driver does not print anything about a MAC address, and when that happens the interface does not come up. It sounds stupid, but I have found that making sure that the console USB is plugged in seems to reduce this to about 30%. Has anyone seen this before on a Tobi? Is there something simple I can do to get ethernet reliably loading on boot? -A. |
From: Miner, J. W (US SSA) <jon...@ba...> - 2010-03-30 16:23:52
|
Have you edited /etc/network/interfaces ? You need a line similar to: iface eth0 inet dhcp ________________________________________ From: Richman1234 [ric...@na...] Sent: Tuesday, March 30, 2010 11:42 To: gum...@li... Subject: [Gumstix-users] eth0 dosn't auto load on boot I am setting up a new Gumstix overo fire with a tobi board. I have added 'eth0' with the network manager, and configured it with static IP. I ran #ifup eth0, and everything worked great. I have asked a question like this before, and was told to add: smsc911x to /etc/modules so that eth0 would load automatically on boot. I did this and rebooted, but eth0 didn't load. I ran #ifup eth0 and everything worked great again. Can someone tell me why eth0 will not load on boot? Please keep it simple, I'm new to this. Thanks -- View this message in context: http://old.nabble.com/eth0-dosn%27t-auto-load-on-boot-tp28084414p28084414.html Sent from the Gumstix mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Richman1234 <ric...@na...> - 2010-03-30 20:28:51
|
Yes, my /etc/network/interfaces file has iface eth0 inet static address 130.129.30.10 netmask 255.255.255.0 broadcast 130.129.30.255 gateway 130.129.30.1 When I boot there is no information under the eth0 when I ifconfig. Then I 'ifup eth0', and then everything works. So everything works after I ifup eht0, but then it stops working when I reboot. Any more suggestions? -- View this message in context: http://old.nabble.com/eth0-dosn%27t-auto-load-on-boot-tp28084414p28088019.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Trevor W. <two...@gm...> - 2010-03-30 20:41:38
|
Sorry I guess I wasn't clear enough in my previous reply. There are 2 things you need to do automatically on each reboot to have this work. By putting the name of the kernel module in the /etc/modules file you've got one of those two things happening automatically on reboot. You still need to have the configuration occur automatically on each reboot. There are several init mechanisms you could be using, and some of those have multiple ways of configuring themselves, so it's not possible for me to give you a specific answer on how you would accomplish this. On Tue, Mar 30, 2010 at 4:28 PM, Richman1234 <ric...@na...> wrote: > > Yes, my /etc/network/interfaces file has > iface eth0 inet static > address 130.129.30.10 > netmask 255.255.255.0 > broadcast 130.129.30.255 > gateway 130.129.30.1 > > When I boot there is no information under the eth0 when I ifconfig. > Then I 'ifup eth0', and then everything works. > > So everything works after I ifup eht0, but then it stops working when I > reboot. > > Any more suggestions? > > -- > View this message in context: http://old.nabble.com/eth0-dosn%27t-auto-load-on-boot-tp28084414p28088019.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Richman1234 <ric...@na...> - 2010-03-30 23:50:11
|
OK, got it. I have modified /etc/modules, so I have one of the two done. After boot, if I run 'ifup eth0' eth0 loads, and everything works great. What is ifup eth0 doing, and how do i get it to do it automaticaly on boot? Thanks Trevor Woerner-6 wrote: > > Sorry I guess I wasn't clear enough in my previous reply. > > There are 2 things you need to do automatically on each reboot to have > this work. > > By putting the name of the kernel module in the /etc/modules file > you've got one of those two things happening automatically on reboot. > > You still need to have the configuration occur automatically on each > reboot. There are several init mechanisms you could be using, and some > of those have multiple ways of configuring themselves, so it's not > possible for me to give you a specific answer on how you would > accomplish this. > > -- View this message in context: http://old.nabble.com/eth0-dosn%27t-auto-load-on-boot-tp28084414p28090004.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Trevor W. <two...@gm...> - 2010-03-31 02:38:59
|
On Tue, Mar 30, 2010 at 7:50 PM, Richman1234 <ric...@na...> wrote: > What is ifup eth0 doing, and how do i get it to do it automaticaly on boot? When the kernel has completed its starting-up procedures it prods userspace to start running by running the "init". Init is a program, usually in /sbin, that is responsible for bringing up the user-space portion of the system. Over the years many people have written many different flavours of init. Although I have a gumstix device, I haven't yet found the time I would like to explore it as I would love to do (paying gigs come first). So I'm not 100% sure exactly which flavour of init you're using, if I knew I could say exactly what you need to do. But the chances are there's a file called /etc/inittab on your gumstix device. This is usually what init uses as its configuration file. On your desktop Linux machine you could try "man 5 inittab" to understand the format of this file. You _could_ modify this file to add your "ifup eth0" line, but that's probably overkill. Your gumstix might have a script located at /etc/init.d/rcS. If so that would be a good place to add your "ifup eth0" line. Alternately you might have directories in /etc/init.d such as "rc0.d", "rc2.d", ... "rc6.d". If you look in /etc/init.d you might find a script called "networking" or "network" or something similar. If you call that script as: "./network start" then you'll probably get your networking going that way. In that case looking in /etc/inittab will tell you the default runlevel the system will enter (look for an "initdefault" entry near the top of the file). If your default runlevel is, say, 2 the you could go into the /etc/init.d/rc2.d directory and add a link to the start script making sure the link name includes a capital 'S' to say you want this functionality [S]tarted at this runlevel ($ ln -s ../network S02network). "ifup" is just a script, probably located in /sbin. If you can understand shell syntax you could look through this script and find out what it's doing. Most likely it is looking through various configuration (such as in /etc/network/interfaces) and getting things configured based on the settings it finds. My experience tends to be with RPM-based Linux systems and small embedded sytems; both of which use entirely different init mechanisms. Debian-based systems, on the other hand, tend to do things differently yet again. Someone with a running gumstix on their hands would need to fill in the specifics for your exact setup. Sorry. |
From: Dustin H. <du...@ho...> - 2010-03-31 04:44:41
|
On Tue, Mar 30, 2010 at 10:38 PM, Trevor Woerner <two...@gm...> wrote: > My experience tends to be with RPM-based Linux systems and small > embedded sytems; both of which use entirely different init mechanisms. > Debian-based systems, on the other hand, tend to do things differently > yet again. Someone with a running gumstix on their hands would need to > fill in the specifics for your exact setup. Sorry. > Angstrom (OE) uses ipkg, which is similar to a stripped dpkg, and sysvinit (thus the rc*.d directories with linked scripts from /etc/init.d) All in all, it's very similar to Debian. That said, that method should work. |
From: Miner, J. W (US SSA) <jon...@ba...> - 2010-03-31 12:06:02
|
One item that nobody (myself included) is the need for an "auto" entry in the /etc/network/interfaces. Here is an example from a working system: auto eth0 iface eth0 inet dhcp The "auto" entry causes the system to automatically run the "ifup" command. A second option is to run the ifplug daemon, which monitors the ethernet link and runs "ifup" when the link comes up, in that case you would not use the "auto" line. |