> From: acsmith [mailto:acsmith@...]
> I just built a 3.5.7 kernel (Dylan 1.4.2) version of the
> gumstix-console-image and mine didn't have the networkmanager
> in it. I
> built the image, modified the wpa_supplicant.conf file to
> suit my wireless
> that has worked on OE - 3.2 kernel. It would connect to the wireless
> ("wlan0: link becomes ready"), udhcpc (v1.20.2) starts,
> sending discover ...
> , no lease, failing and then the wifi light drops out and
> never lights up
> solid again.
> ifup / ifdown both work out of the box, didn't need to modify
I haven't seen quite that combination of failures, but I've seen something
screwy where wpa_supplicant appears to successfully connect, and then
something instantly kills it. This is pretty brittle stuff, I guess.
I have another non-Gumstix project built with Dylan, using ifupdown, and
it does bring up my ethernet on bootup automatically. Even though it's
systemd-based, it still has a lot of old sysvinit scripts, including
"networking", which runs "ifup -a" on startup.
The gumstix-console-image.bb recipe in Danny includes some ad hoc code to
blacklist a bunch of these files, including the "networking" one. I just
checked the Dylan version, and it doesn't have any blacklisting. So I
un-blacklisted it in the Gumstix/Danny recipe, and the script now appears
in /etc/init.d, but it still doesn't appear to run.
I haven't yet figured out why my networking is starting up on that other
project but not in my Gumstix project. In both cases, there are links to
the "networking" script in runlevels 0, 1, 6 and S. It's possible that I'm
on a wild goose chase, and it's something else entirely that's starting
the network on that other system.
Ciao, Paul D. DeRocco