**** BEGIN LOGGING AT Sat Apr 28 03:00:00 2012 Apr 28 03:00:43 What is the "best" way to configure wifi to auto-connect to a specific ssid (no encryption) upon boot? I've configured interfaces and I see the correct ssid when I 'iwconfig' right after boot, but it seems to ignore my dhcp setting - it doesn't grab a DHCP address. (I can dhclient wlan1 and it grabs an IP right away) Apr 28 03:30:51 Darksmurf: setting the interface to "auto" doesn't do it? Apr 28 03:31:17 unfortunatly, no. During boot I see the /etc/init.d/networking scrupt run, indicate it is configuring all interfaces, and it returns an error that wlan1 isn't ready. The next line shows a message indicating "wlan1: link becomes ready" - I am able to get an address via dhclient wlan1 and I'm able to ping the router, etc Apr 28 03:31:43 I'm also able to pull an address if I "/etc/init.d/networking restart" Apr 28 03:32:55 is the driver loaded as a module or compiled into the kernel? Apr 28 03:33:18 I believe a module Apr 28 03:33:42 lib80211 is loaded as a module, which I think is the Marvell module Apr 28 03:33:51 (although I may be wrong) Apr 28 03:35:27 it's marvell_phy in ther newer kernels... Apr 28 03:36:51 it sounds like it's trying to bring it up too soon Apr 28 03:36:53 I am VERY new to Overo and such, so I assume I'm wrong. Apr 28 03:37:12 agreed Apr 28 03:37:53 a "networking restart" seems to get me connected after I've logged in (via serial), so I may just add that to the end of another script further in the boot process. Not the most elegant fix I know... Apr 28 03:38:16 so the easy workaround would be to dhclient to something like rc.local Apr 28 03:38:27 *add Apr 28 03:39:12 I'm not familar with rc.local, and I don't see it via a find command. Where should it be? Apr 28 03:39:36 I should mention I'm using an Overo, so it may be that it is missing. Apr 28 03:45:51 what's the last thing in /etc/rc5.d ? Apr 28 03:46:27 assuming you're booting runlevel 5... Apr 28 03:46:30 S99rmnologin -I was thinking about adding a new script, say S98 Apr 28 03:46:48 I actually see two S99s, the other starts gpe Apr 28 03:47:20 yes, default runlevel is 5 Apr 28 03:47:21 yeah, you could add a dhclient.sh and make it 99dhclient Apr 28 03:47:39 k, I'll give that a go. Apr 28 03:50:17 i don't have anything embedded with built-in wireless just now... Apr 28 03:50:37 I don't see why this wouldn't work.. rebooting now. Apr 28 03:50:55 * nerdboy wants a pandaboard Apr 28 03:51:37 I've been working with MCUs for years, this is my first embedded linux board. Frankly, this thing is amazing. I'm thinking about a Rasberry Pi for personal use. Apr 28 03:51:47 woot, that did it. Apr 28 03:51:54 thanks for the assistance. Apr 28 03:52:45 now to move this gumstix from the ethernet/HDMI/serial console enabled board to the barebones board that'll be installed in the bot... Apr 28 03:52:53 and see if I can talk to it Apr 28 04:05:49 Now the scary stuff starts :-/ Apr 28 19:06:13 hi, what's the up to date way to create a recent canadian armv4 toolchain for x86(my builder is x86-64) Apr 28 19:06:41 because I've bitbaken meta-toolchain and it created that: Apr 28 19:06:49 oecore-x86_64-armv4t-toolchain-20120428.tar.bz2 Apr 28 19:06:57 first it's x86_64 Apr 28 19:07:10 second some libs are for armv7 Apr 28 19:07:41 (it created the /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/bin/armv7a-vfp-neon-oe-linux-gnueabi directory for instance) Apr 28 19:08:24 hi JaMa Apr 28 19:08:34 hi Apr 28 19:09:15 do you have some pointers for generating a toolchain for armv4 on x86_64 for i686 Apr 28 19:09:50 yes grep SDKMACHINE Apr 28 19:10:09 I should put that in local.conf I guess Apr 28 19:10:13 I'll grep Apr 28 19:10:29 but there was more than one way to make a toolchain Apr 28 19:10:33 the old ways are gone? Apr 28 19:10:52 no idea what you mean by "old ways" Apr 28 19:10:53 also I got some armv7 in the armv4 toolchain Apr 28 19:11:09 there was sdk, nativesdk etc... Apr 28 19:12:01 what's that? you can find some thread about wrong stuff in toolchain, it's on oe-core ML started by me about 2 months ago Apr 28 19:12:23 it was at the oe classic times Apr 28 19:12:28 very long time ago Apr 28 19:12:32 I can't remember well Apr 28 19:12:55 I meant: what's that armv7a-vfp-neon-oe-linux-gnueabi stuff you have there Apr 28 19:13:19 /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/bin/armv7a-vfp-neon-oe-linux-gnueabi Apr 28 19:13:45 you said some libs before.. Apr 28 19:13:50 oecore-x86_64-armv4t-toolchain-20120428.tar.bz2 Apr 28 19:13:59 I guess I've some libs too Apr 28 19:14:00 sorry Apr 28 19:14:29 ah ok Apr 28 19:14:36 no libs should be armv4 Apr 28 19:15:35 Tag_CPU_name: "4T" Apr 28 19:15:35 Tag_CPU_arch: v4T Apr 28 19:15:37 so it's ok Apr 28 19:17:55 thanks a lot, I've read bitbake.conf Apr 28 19:18:05 and I'll add SDKMACHINE = "i686" Apr 28 21:09:07 Anyone know where I can get pyserial for OE? Apr 28 21:19:55 oe-classic has a recipe Apr 28 22:14:00 hi, I compiled an i686 armv4 toolchain with oe (thanks JaMa for the help on SDKMACHINE) but now I've that when using the toolchain to cross compile some microcontroller stuff: Apr 28 22:14:46 http://paste.debian.net/166280/ **** ENDING LOGGING AT Sun Apr 29 02:59:58 2012