gumstix

Here is my script to manually load the wifi module without udev and hotplug.
This is only useful if you don't need plug and play and only need to load up
the modules once at startup.


#!/bin/sh

# start libertas wifi driver
modprobe libertas_sdio &

# wait for driver to load and create system files for wifi
x=0
while [ "$x" -lt 100 -a ! -e /sys/class/firmware/mmc1* ]; do
        x=$((x+1))
	sleep .01
done

cd /sys/class/firmware/mmc1*

echo 1 > loading
cat /lib/firmware/sd8686_helper.bin > data
echo 0 > loading

sleep .1

cd /sys/class/firmware/mmc1*

echo 1 > loading
cat /lib/firmware/sd8686.bin > data
echo 0 > loading


--
View this message in context: http://gumstix.8.n6.nabble.com/Did-they-ever-solve-the-slow-bring-up-of-wifi-problem-tp4944197p4964318.html
Sent from the Gumstix mailing list archive at Nabble.com.

All,

I did some work/searching last night and I believe that I have a solution
for the slow WiFi bring-up problem that so many have been facing.  As I had
mentioned earlier, the latest udev being used in the any variant of the
OpenEmbedded console/desktop image requires that all modules/firmware be
loaded asynchronously.  But, the libertas SDIO driver is synchronous, so it
bogged down the boot process.  I found some patches create by Daniel Drake
at laptop.org that addressed this slow bringup issue, but his patches were
for an older version of the libertas firmware.  So, last night I went
through and read the patches and generated new patches to match the libertas
driver in 
http://www.sakoman.com/cgi-bin/gitweb.cgi?p=linux-omap-2.6.git;a=commit;h=513770d80c0cfb26cc406c9ca3916df2e7afe46d
this  Sakoman 3.2 kernel commit (which is the commit dtran11 posted).  I
have attached the patch files, in addition to my modified virtual/kernel
bitbake recipe, which are here: 
http://gumstix.8.n6.nabble.com/file/n4964350/decl_h.patch decl_h.patch , 
http://gumstix.8.n6.nabble.com/file/n4964350/dev_h.patch dev_h.patch , 
http://gumstix.8.n6.nabble.com/file/n4964350/if_sdio_c.patch if_sdio_c.patch
,  http://gumstix.8.n6.nabble.com/file/n4964350/main_c.patch main_c.patch , 
http://gumstix.8.n6.nabble.com/file/n4964350/linux-omap3_git.bb
linux-omap3_git.bb .

This patch should probably work wit the Sakoman 3.0 kernel as well, but I
haven't tested it.  Currently, the asynchronous change has only been applied
to the SDIO driver, which I fine for Overo use.  But, I will apply the
changes to the USB, GSPA and SPI interfaces later.  I tested the patches
this morning on my Overo FireSTORM w/ Tobi expansion board the bring-up time
was within 2-3 seconds.  So, hopefully others will have the same kind of
results and will eliminate the need for any handcrafted workaround boot
scripts to get our Linux COMs booting the way they should.

-Donald


Donny3000 wrote
> 
> I'm having the same slow bring up of wifi as well.  I tried using the 3.2
> kernel commit that you posted with the omap3-console-image, but to no
> avail.  Do you (or anyone else) know what could be causing this?  I've
> been fighting this for awhile, but have been unsuccessful in my attempts
> to resolve it.  I feel like it's a kernel/driver issue, but I'm not sure. 
> Although, I read 
> http://comments.gmane.org/gmane.linux.kernel.wireless.general/86066 this
> gmane post  that udev-175+ requires asynchronous firmware loading and the
> libertas hasn't been converted to that.  I also stumbled across this 
> http://www.spinics.net/lists/netdev/msg185742.html link  in my googling
> that looks like it might apply to this slow wifi bring up.  Don't know if
> these changes apply to our Gumstix platform, but I'm looking into them.
> 
> 
> dtran11 wrote
>> 
>> Just tried the latest version of 3.2 (commit
>> 513770d80c0cfb26cc406c9ca3916df2e7afe46d) and the wireless seems to be a
>> lot better now. I am getting around 600KB/s consistently. I don't know if
>> the fix for the mmc had anything to do with it:
>> http://www.sakoman.com/cgi-bin/gitweb.cgi?p=linux-omap-2.6.git;a=commit;h=513770d80c0cfb26cc406c9ca3916df2e7afe46d
>> 
>> Please give it a try and tell me what you guys get. Thanks.
>> 
> 

--
View this message in context: http://gumstix.8.n6.nabble.com/Did-they-ever-solve-the-slow-bring-up-of-wifi-problem-tp4944197p4964350.html
Sent from the Gumstix mailing list archive at Nabble.com.

Hi Donald,

I have the same issue with the libertas_sdio driver, when using the Sakoman
3.2 kernel. I tried the patches from your email, but it does not work.

Here is the output I got on dmesg:

cfg80211: Calling CRDA to update world regulatory domain
libertas enter: lbs_init_module()
libertas leave: lbs_init_module()
libertas enter: if_sdio_init_module()
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
libertas enter: if_sdio_probe()
libertas sdio: class = 0x7, vendor = 0x2DF, device = 0x9103, model = 0xB,
ioport = 0x0
libertas enter: lbs_add_card()
libertas enter: lbs_cfg_alloc()
libertas leave: lbs_cfg_alloc()
libertas enter: lbs_init_adapter()
libertas enter: lbs_allocate_cmd_buffer()
libertas enter: __lbs_cleanup_and_insert_cmd()
libertas leave: __lbs_cleanup_and_insert_cmd()
libertas enter: __lbs_cleanup_and_insert_cmd()
libertas leave: __lbs_cleanup_and_insert_cmd()
libertas enter: __lbs_cleanup_and_insert_cmd()
libertas leave: __lbs_cleanup_and_insert_cmd()
libertas enter: __lbs_cleanup_and_insert_cmd()
libertas leave: __lbs_cleanup_and_insert_cmd()
libertas enter: __lbs_cleanup_and_insert_cmd()
libertas leave: __lbs_cleanup_and_insert_cmd()
libertas enter: __lbs_cleanup_and_insert_cmd()
libertas leave: __lbs_cleanup_and_insert_cmd()
libertas enter: __lbs_cleanup_and_insert_cmd()
libertas leave: __lbs_cleanup_and_insert_cmd()
libertas enter: __lbs_cleanup_and_insert_cmd()
libertas leave: __lbs_cleanup_and_insert_cmd()
libertas enter: __lbs_cleanup_and_insert_cmd()
libertas leave: __lbs_cleanup_and_insert_cmd()
libertas enter: __lbs_cleanup_and_insert_cmd()
libertas leave: __lbs_cleanup_and_insert_cmd()
libertas leave: lbs_allocate_cmd_buffer(), ret 0
libertas leave: lbs_init_adapter(), ret 0
libertas thread: Starting main thread...
libertas leave: lbs_add_card(), priv dbfd8320
libertas enter: if_sdio_prog_firmware()
libertas sdio: firmware status = 0x0
libertas sdio: scratch ret = 0
libertas fw: Starting async firmware load
libertas fw: Requesting libertas/sd8686_v9_helper.bin
libertas enter: lbs_thread()
libertas thread: 1: currenttxskb  (null), dnld_sent 0
libertas thread: sleeping, connect_status 1, psmode 0, psstate 0
libertas leave: if_sdio_prog_firmware(), ret 0
libertas leave: if_sdio_probe(), ret 0
libertas leave: if_sdio_init_module(), ret 0
libertas fw: Requesting libertas/sd8686_v8_helper.bin
libertas fw: Requesting sd8686_helper.bin
libertas fw: firmware load complete, code -2
libertas_sdio: failed to find firmware (-2)


Any idea what is wrong?

The firmware is in /lib/firmware

Thanks
Uli 

--
View this message in context: http://gumstix.8.n6.nabble.com/Did-they-ever-solve-the-slow-bring-up-of-wifi-problem-tp4944197p4964535.html
Sent from the Gumstix mailing list archive at Nabble.com.

Hi Ulih,

I actually made some changes to the patches for the libertas_sdio driver for
the 3.2 kernel.  Try these and let me know if they work for you. 
Previously, I was trying to minimize the number of files, but this time I
just re-patched the entire driver so I wouldn't miss anything.  I applied
these patches and they seemed to work for me with a considerable decrease in
the wait time (about 2-3 seconds).

Patch Files:
http://gumstix.8.n6.nabble.com/file/n4964541/asynchronous_add_decl_h.patch
asynchronous_add_decl_h.patch 
http://gumstix.8.n6.nabble.com/file/n4964541/asynchronous_add_dev_h.patch
asynchronous_add_dev_h.patch 
http://gumstix.8.n6.nabble.com/file/n4964541/asynchronous_add_firmware_c.patch
asynchronous_add_firmware_c.patch 
http://gumstix.8.n6.nabble.com/file/n4964541/asynchronous_add_if_cs_c.patch
asynchronous_add_if_cs_c.patch 
http://gumstix.8.n6.nabble.com/file/n4964541/asynchronous_add_if_sdio_c.patch
asynchronous_add_if_sdio_c.patch 
http://gumstix.8.n6.nabble.com/file/n4964541/asynchronous_add_if_spi_c.patch
asynchronous_add_if_spi_c.patch 
http://gumstix.8.n6.nabble.com/file/n4964541/asynchronous_add_if_usb_c.patch
asynchronous_add_if_usb_c.patch 
http://gumstix.8.n6.nabble.com/file/n4964541/asynchronous_add_main_c.patch
asynchronous_add_main_c.patch 
http://gumstix.8.n6.nabble.com/file/n4964541/asynchronous_add_Makefile.patch
asynchronous_add_Makefile.patch 

I didn't do anything special other than making sure my
/etc/network/interfaces and /etc/wpa_supplicant.conf were configured
correctly.  To do that I followed this 
http://wiki.gumstix.org/index.php?title=Overo_Wifi Overo WiFi  wiki.

--
View this message in context: http://gumstix.8.n6.nabble.com/Did-they-ever-solve-the-slow-bring-up-of-wifi-problem-tp4944197p4964541.html
Sent from the Gumstix mailing list archive at Nabble.com.

Hi,

thank you very much for your reply (and sorry for my delayed response). I tried your patches. When I load the module ("modprobe libertas_sdio"), the wait time is indeed very short, but the firmware is not found. After maybe 30 seconds, I get the error message:
libertas_sdio: failed to find firmware (-2)

The content of /lib/firmware is:

root@...# ls -la
total 152
drwxrwxr-x 9 root root  4096 Jun  6  2012 .
drwxrwxr-x 6 root root  4096 Jun  6  2012 ..
drwxrwxr-x 2 root root  4096 Jun  6  2012 edgeport
drwxrwxr-x 2 root root  4096 Jun  6  2012 emi26
drwxrwxr-x 2 root root  4096 Jun  6  2012 emi62
drwxrwxr-x 2 root root  4096 Jun  6  2012 kaweth
drwxrwxr-x 2 root root  4096 Jun  6  2012 keyspan_pda
drwxr-xr-x 2 root root  4096 Jun  6  2012 libertas
-rw-r--r-- 1 root root 13847 Jun  6  2012 mts_cdma.fw
-rw-r--r-- 1 root root 14067 Jun  6  2012 mts_edge.fw
-rw-r--r-- 1 root root 13847 Jun  6  2012 mts_gsm.fw
-rw-r--r-- 1 root root  2048 May 29 22:19 rt73.bin
lrwxrwxrwx 1 root root    36 May 31 15:13 sd8686.bin -> /lib/firmware/libertas/sd8686_v9.bin
lrwxrwxrwx 1 root root    43 May 31 15:13 sd8686_helper.bin -> /lib/firmware/libertas/sd8686_
v9_helper.bin
-rw-r--r-- 1 root root 13765 Jun  6  2012 ti_3410.fw
-rw-r--r-- 1 root root 13764 Jun  6  2012 ti_5052.fw
-rw-r--r-- 1 root root 23554 Jun  6  2012 whiteheat.fw
-rw-r--r-- 1 root root  5626 Jun  6  2012 whiteheat_loader.fw
drwxrwxr-x 2 root root  4096 May 31  2012 zd1211



root@...# ls -la
total 2224
drwxr-xr-x 2 root root   4096 Jun  6  2012 .
drwxrwxr-x 9 root root   4096 Jun  6  2012 ..
-rw-r--r-- 1 root root  95132 Jun  6  2012 cf8381.bin
-rw-r--r-- 1 root root   2132 Jun  6  2012 cf8381_helper.bin
-rw-r--r-- 1 root root  97128 Jun  6  2012 cf8385.bin
-rw-r--r-- 1 root root   2140 Jun  6  2012 cf8385_helper.bin
-rw-r--r-- 1 root root 154608 Jun  6  2012 gspi8682.bin
-rw-r--r-- 1 root root   2140 Jun  6  2012 gspi8682_helper.bin
-rw-r--r-- 1 root root 126652 Jun  6  2012 gspi8686_v9.bin
-rw-r--r-- 1 root root   2140 Jun  6  2012 gspi8686_v9_helper.bin
-rw-r--r-- 1 root root 261596 Jun  6  2012 gspi8688.bin
-rw-r--r-- 1 root root   2140 Jun  6  2012 gspi8688_helper.bin
-rw-r--r-- 1 root root 120924 Jun  6  2012 lbtf_sdio.bin
-rw-r--r-- 1 root root  96716 Jun  6  2012 sd8385.bin
-rw-r--r-- 1 root root   2140 Jun  6  2012 sd8385_helper.bin
-rw-r--r-- 1 root root 155648 Jun  6  2012 sd8682.bin
-rw-r--r-- 1 root root   2616 Jun  6  2012 sd8682_helper.bin
-rw-r--r-- 1 root root 122800 Jun  6  2012 sd8686_v8.bin
-rw-r--r-- 1 root root   2464 Jun  6  2012 sd8686_v8_helper.bin
-rw-r--r-- 1 root root 124188 Jun  6  2012 sd8686_v9.bin
-rw-r--r-- 1 root root   2516 Jun  6  2012 sd8686_v9_helper.bin
-rw-r--r-- 1 root root 259172 Jun  6  2012 sd8688.bin
-rw-r--r-- 1 root root   2616 Jun  6  2012 sd8688_helper.bin
-rw-r--r-- 1 root root 127824 Jun  6  2012 usb8388_olpc.bin
-rw-r--r-- 1 root root 100292 Jun  6  2012 usb8388_v5.bin
-rw-r--r-- 1 root root 126644 Jun  6  2012 usb8388_v9.bin
-rw-r--r-- 1 root root 174332 Jun  6  2012 usb8682.bin

Is there a way to get more debugging output?


Thanks for any other ideas
Best
Uli




________________________________
 From: Donny3000 [via Gumstix] <ml-node+s8n4964541h53@...>
To: ulih <uh_de@...> 
Sent: Wednesday, June 6, 2012 7:22 AM
Subject: Re: Did they ever solve the slow bring up of wifiproblem?
 

Hi Ulih, 

I actually made some changes to the patches for the libertas_sdio driver for the 3.2 kernel.  Try these and let me know if they work for you.  Previously, I was trying to minimize the number of files, but this time I just re-patched the entire driver so I wouldn't miss anything.  I applied these patches and they seemed to work for me with a considerable decrease in the wait time (about 2-3 seconds). 

Patch Files: 
asynchronous_add_decl_h.patch
asynchronous_add_dev_h.patch
asynchronous_add_firmware_c.patch
asynchronous_add_if_cs_c.patch
asynchronous_add_if_sdio_c.patch
asynchronous_add_if_spi_c.patch
asynchronous_add_if_usb_c.patch
asynchronous_add_main_c.patch
asynchronous_add_Makefile.patch

I didn't do anything special other than making sure my /etc/network/interfaces and /etc/wpa_supplicant.conf were configured correctly.  To do that I followed this Overo WiFi wiki. 

________________________________
 
If you reply to this email, your message will be added to the discussion below:http://gumstix.8.n6.nabble.com/Did-they-ever-solve-the-slow-bring-up-of-wifi-problem-tp4944197p4964541.html 
To unsubscribe from Did they ever solve the slow bring up of wifi problem?, click here.
NAML

--
View this message in context: http://gumstix.8.n6.nabble.com/Did-they-ever-solve-the-slow-bring-up-of-wifi-problem-tp4944197p4964715.html
Sent from the Gumstix mailing list archive at Nabble.com.

Okay, with enabled debugging, I get this:

libertas enter: if_sdio_init_module()
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
libertas enter: if_sdio_probe()
libertas sdio: class = 0x7, vendor = 0x2DF, device = 0x9103, model = 0xB,
ioport = 0x0
libertas enter: lbs_add_card()
libertas enter: lbs_cfg_alloc()
libertas leave: lbs_cfg_alloc()
libertas enter: lbs_init_adapter()
libertas enter: lbs_allocate_cmd_buffer()
libertas enter: __lbs_cleanup_and_insert_cmd()
libertas leave: __lbs_cleanup_and_insert_cmd()
libertas enter: __lbs_cleanup_and_insert_cmd()
libertas leave: __lbs_cleanup_and_insert_cmd()
libertas enter: __lbs_cleanup_and_insert_cmd()
libertas leave: __lbs_cleanup_and_insert_cmd()
libertas enter: __lbs_cleanup_and_insert_cmd()
libertas leave: __lbs_cleanup_and_insert_cmd()
libertas enter: __lbs_cleanup_and_insert_cmd()
libertas leave: __lbs_cleanup_and_insert_cmd()
libertas enter: __lbs_cleanup_and_insert_cmd()
libertas leave: __lbs_cleanup_and_insert_cmd()
libertas enter: __lbs_cleanup_and_insert_cmd()
libertas leave: __lbs_cleanup_and_insert_cmd()
libertas enter: __lbs_cleanup_and_insert_cmd()
libertas leave: __lbs_cleanup_and_insert_cmd()
libertas enter: __lbs_cleanup_and_insert_cmd()
libertas leave: __lbs_cleanup_and_insert_cmd()
libertas enter: __lbs_cleanup_and_insert_cmd()
libertas leave: __lbs_cleanup_and_insert_cmd()
libertas leave: lbs_allocate_cmd_buffer(), ret 0
libertas leave: lbs_init_adapter(), ret 0
libertas thread: Starting main thread...
libertas enter: lbs_thread()
libertas thread: 1: currenttxskb   (null), dnld_sent 0
libertas thread: sleeping, connect_status 1, psmode 0, psstate 0
libertas leave: lbs_add_card(), priv de458320
libertas enter: if_sdio_prog_firmware()
libertas sdio: firmware status = 0x0
libertas sdio: scratch ret = 0
libertas fw: Starting async firmware load
libertas fw: Requesting libertas/sd8686_v9_helper.bin
libertas leave: if_sdio_prog_firmware(), ret 0
libertas leave: if_sdio_probe(), ret 0
libertas leave: if_sdio_init_module(), ret 0
libertas fw: Requesting libertas/sd8686_v8_helper.bin
libertas fw: Requesting sd8686_helper.bin
libertas fw: firmware load complete, code -2
libertas_sdio: failed to find firmware (-2)

--
View this message in context: http://gumstix.8.n6.nabble.com/Did-they-ever-solve-the-slow-bring-up-of-wifi-problem-tp4944197p4964735.html
Sent from the Gumstix mailing list archive at Nabble.com.

Ulih,

What command are you using to load the module?  I'm trying to figure out why
it's trying to load all of the firmware versions.  It should only be loading
either the sd8686_v9_helper.bin, sd8686_v8_helper.bin or the
sd8686_helper.bin.  Can you post your contents of /lib/firmware or
/lib/firmware/libertas again?

Donald

--
View this message in context: http://gumstix.8.n6.nabble.com/Did-they-ever-solve-the-slow-bring-up-of-wifi-problem-tp4944197p4964762.html
Sent from the Gumstix mailing list archive at Nabble.com.

Donald,

I am loading it with:

modprobe libertas
echo "0x02FFFFFF" > /sys/module/libertas/parameters/libertas_debug
modprobe libertas_sdio

The content of the folders are:
total 276
drwxrwxr-x 2 root root   4096 2012-06-27 10:26 edgeport
drwxrwxr-x 2 root root   4096 2012-06-27 10:26 emi26
drwxrwxr-x 2 root root   4096 2012-06-27 10:26 emi62
drwxrwxr-x 2 root root   4096 2012-06-27 10:26 kaweth
drwxrwxr-x 2 root root   4096 2012-06-27 10:26 keyspan_pda
drwxr-xr-x 2 root root   4096 2012-06-27 11:47 libertas
-rw-r--r-- 1 root root  13847 2012-06-26 17:28 mts_cdma.fw
-rw-r--r-- 1 root root  14067 2012-06-26 17:28 mts_edge.fw
-rw-r--r-- 1 root root  13847 2012-06-26 17:28 mts_gsm.fw
-rw-r--r-- 1 root root   2048 2012-05-29 14:19 rt73.bin
-rw-r--r-- 1 root root 124188 2012-06-28 12:15 sd8686.bin
-rw-r--r-- 1 root root   2516 2012-06-28 12:15 sd8686_helper.bin
-rw-r--r-- 1 root root  13765 2012-06-26 17:28 ti_3410.fw
-rw-r--r-- 1 root root  13764 2012-06-26 17:28 ti_5052.fw
-rw-r--r-- 1 root root  23554 2012-06-26 17:28 whiteheat.fw
-rw-r--r-- 1 root root   5626 2012-06-26 17:28 whiteheat_loader.fw
drwxrwxr-x 2 root root   4096 2012-06-27 10:27 zd1211




total 2216
-rw-r--r-- 1 root root  95132 2012-06-27 11:47 cf8381.bin
-rw-r--r-- 1 root root   2132 2012-06-27 11:47 cf8381_helper.bin
-rw-r--r-- 1 root root  97128 2012-06-27 11:47 cf8385.bin
-rw-r--r-- 1 root root   2140 2012-06-27 11:47 cf8385_helper.bin
-rw-r--r-- 1 root root 154608 2012-06-27 11:47 gspi8682.bin
-rw-r--r-- 1 root root   2140 2012-06-27 11:47 gspi8682_helper.bin
-rw-r--r-- 1 root root 126652 2012-06-27 11:47 gspi8686_v9.bin
-rw-r--r-- 1 root root   2140 2012-06-27 11:47 gspi8686_v9_helper.bin
-rw-r--r-- 1 root root 261596 2012-06-27 11:47 gspi8688.bin
-rw-r--r-- 1 root root   2140 2012-06-27 11:47 gspi8688_helper.bin
-rw-r--r-- 1 root root 120924 2012-06-27 11:47 lbtf_sdio.bin
-rw-r--r-- 1 root root  96716 2012-06-27 11:47 sd8385.bin
-rw-r--r-- 1 root root   2140 2012-06-27 11:47 sd8385_helper.bin
-rw-r--r-- 1 root root 155648 2012-06-27 11:47 sd8682.bin
-rw-r--r-- 1 root root   2616 2012-06-27 11:47 sd8682_helper.bin
-rw-r--r-- 1 root root 122800 2012-06-27 11:47 sd8686_v8.bin
-rw-r--r-- 1 root root   2464 2012-06-27 11:47 sd8686_v8_helper.bin
-rw-r--r-- 1 root root 124188 2012-06-27 11:47 sd8686_v9.bin
-rw-r--r-- 1 root root   2516 2012-06-27 11:47 sd8686_v9_helper.bin
-rw-r--r-- 1 root root 259172 2012-06-27 11:47 sd8688.bin
-rw-r--r-- 1 root root   2616 2012-06-27 11:47 sd8688_helper.bin
-rw-r--r-- 1 root root 127824 2012-06-27 11:47 usb8388_olpc.bin
-rw-r--r-- 1 root root 100292 2012-06-27 11:47 usb8388_v5.bin
-rw-r--r-- 1 root root 126644 2012-06-27 11:47 usb8388_v9.bin
-rw-r--r-- 1 root root 174332 2012-06-27 11:47 usb8682.bin


Thanks for your help!
Uli



________________________________
 From: Donny3000 <donald.poole@...>
To: gumstix-users@... 
Sent: Thursday, June 28, 2012 8:29 AM
Subject: Re: [Gumstix-users] Did they ever solve the slow bring up of wifiproblem?
 
Ulih,

What command are you using to load the module?  I'm trying to figure out why
it's trying to load all of the firmware versions.  It should only be loading
either the sd8686_v9_helper.bin, sd8686_v8_helper.bin or the
sd8686_helper.bin.  Can you post your contents of /lib/firmware or
/lib/firmware/libertas again?

Donald

--
View this message in context: http://gumstix.8.n6.nabble.com/Did-they-ever-solve-the-slow-bring-up-of-wifi-problem-tp4944197p4964762.html
Sent from the Gumstix mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
gumstix-users mailing list
gumstix-users@...
https://lists.sourceforge.net/lists/listinfo/gumstix-users

Hmm, try only executing /modprobe libertas_sdio/.  I don't think you need to
execute /modprobe libertas/ to load the /libertas/ module.  It should get
loaded automatically at the appropriate time after /modprobe libertas_sdio/
is executed.

--
View this message in context: http://gumstix.8.n6.nabble.com/Did-they-ever-solve-the-slow-bring-up-of-wifi-problem-tp4944197p4964765.html
Sent from the Gumstix mailing list archive at Nabble.com.

Yes, I did that before. I only load libertas first to enable debugging, before loading libertas_sdio.



________________________________
 From: Donny3000 <donald.poole@...>
To: gumstix-users@... 
Sent: Thursday, June 28, 2012 2:56 PM
Subject: Re: [Gumstix-users] Did they ever solve the slow bring up of wifiproblem?
 
Hmm, try only executing /modprobe libertas_sdio/.  I don't think you need to
execute /modprobe libertas/ to load the /libertas/ module.  It should get
loaded automatically at the appropriate time after /modprobe libertas_sdio/
is executed.

--
View this message in context: http://gumstix.8.n6.nabble.com/Did-they-ever-solve-the-slow-bring-up-of-wifi-problem-tp4944197p4964765.html
Sent from the Gumstix mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
gumstix-users mailing list
gumstix-users@...
https://lists.sourceforge.net/lists/listinfo/gumstix-users

Ulih,

Try removing all of the extra firmware pairs and just leaving the sd8686.bin
and sd8686_helper.bin in the /lib/firmware directory by renaming either the
v9 or v8 firmware to the appropriate file name like you did.  I can't
remember which firmware version works with the the driver/chipset so try
both.

 Also, I'm not sure where you got those firmware files, but the file size of
your sd8686.bin does not match that found in the sysroot of my OpenEmbedded
build (filesize of 124244 bytes).  Are you using Bitbake/OpenEmbedded to
build your rootfs?

--
View this message in context: http://gumstix.8.n6.nabble.com/Did-they-ever-solve-the-slow-bring-up-of-wifi-problem-tp4944197p4964772.html
Sent from the Gumstix mailing list archive at Nabble.com.

Hi,

I finally got it running! I downgraded from kernel 3.2 to 3.0-pm, and then it worked out of the box. The driver is buggy though (only about 100KB/s, which I one of my colleagues has confirmed). But better than nothing :-)

Uli



________________________________
 From: Donny3000 <donald.poole@...>
To: gumstix-users@... 
Sent: Friday, June 29, 2012 8:02 AM
Subject: Re: [Gumstix-users] Did they ever solve the slow bring up of wifiproblem?
 
Ulih,

Try removing all of the extra firmware pairs and just leaving the sd8686.bin
and sd8686_helper.bin in the /lib/firmware directory by renaming either the
v9 or v8 firmware to the appropriate file name like you did.  I can't
remember which firmware version works with the the driver/chipset so try
both.

Also, I'm not sure where you got those firmware files, but the file size of
your sd8686.bin does not match that found in the sysroot of my OpenEmbedded
build (filesize of 124244 bytes).  Are you using Bitbake/OpenEmbedded to
build your rootfs?

--
View this message in context: http://gumstix.8.n6.nabble.com/Did-they-ever-solve-the-slow-bring-up-of-wifi-problem-tp4944197p4964772.html
Sent from the Gumstix mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
gumstix-users mailing list
gumstix-users@...
https://lists.sourceforge.net/lists/listinfo/gumstix-users

Is there any other process to bring up the wifi interface in the Overo? I
have been using the /etc/modprobe.d folder with previous linux kernel
version to 3.2. But with recents kernel versions (kernel 3.5, 3.6) this
method not work for me. 
The modules libertas_sdio.ko doesn't accept param for helper_name and
fw_name.

Actually, I have build an image using the Sakoman repository
(linux-omap-2.6.git) with kernel 3.5. The Overo boot correctly but I have to
wait 40 seg after it has booted until the system detect the wireless
interface wlan0.

[  137.646179] libertas_sdio mmc1:0001:1: (unregistered net_device):
00:19:88:23:e9:4c, fw 9.70.7p0, cap 0x00000303
[  137.677307] libertas_sdio mmc1:0001:1: wlan0: Marvell WLAN 802.11 adapter


By the way, can anyone use the wireless with power management mode? I'm
trying:
root@...:/# iwconfig wlan0 power on
Error for wireless request "Set Power Management" (8B2C) :
    SET failed on device wlan0 ; Operation not supported.

I used it a long time ago, but I remember it was not work correctly.



--
View this message in context: http://gumstix.8.n6.nabble.com/Did-they-ever-solve-the-slow-bring-up-of-wifi-problem-tp4944197p4965521.html
Sent from the Gumstix mailing list archive at Nabble.com.

Donny3000's patches eariler in this thread fixed the slow bring up problem
for me. 

Same issue you report, 40 seconds until the libertas firmware loads.

Thanks Donald!

I'm using it with Sakoman's 3.2 kernel.

I consolidated the patches into one file here

https://github.com/scottellis/meta-jumpnow/blob/master/recipes-kernel/linux/linux-sakoman-3.2/libertas-async-fwload.patch

and an example on how to include it in the kernel recipe here

https://github.com/scottellis/meta-jumpnow/blob/master/recipes-kernel/linux/linux-sakoman_3.2.bb

I have nothing related to the wifi drivers in /etc/modprobe.d



--
View this message in context: http://gumstix.8.n6.nabble.com/Did-they-ever-solve-the-slow-bring-up-of-wifi-problem-tp4944197p4965522.html
Sent from the Gumstix mailing list archive at Nabble.com.

No problem! I glad to see the patches are working out for the community!

-Donald



--
View this message in context: http://gumstix.8.n6.nabble.com/Did-they-ever-solve-the-slow-bring-up-of-wifi-problem-tp4944197p4965523.html
Sent from the Gumstix mailing list archive at Nabble.com.

Thanks for your reply.
With this patch I can solve the problem that the system is waiting for the
starter to mount the wlan0 interface, but still have to wait when the system
boots (since I can see on the shell the "# Overo loguin") for 1 min and 30
sec until I have wifi available.

libertas_sdio MMC1: 0001:1: (unregistered net_device): 00:19:88:15: af: 95,
fw 9.70.7p0, cap 0x00000303
libertas_sdio MMC1: 0001:1: wlan0: Marvell WLAN 802.11 adapter

Right now I've tried it with kernel 3.2 Sakoman repository.
There must be something different in our images, but I don't know what could
be the problem do to delay loading the interface. ¿?

My interfaz file:
auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp

Thanks. 



--
View this message in context: http://gumstix.8.n6.nabble.com/Did-they-ever-solve-the-slow-bring-up-of-wifi-problem-tp4944197p4965527.html
Sent from the Gumstix mailing list archive at Nabble.com.

On Fri, Sep 28, 2012 at 8:00 AM, jumpnowdev <scott@...> wrote:

> Donny3000's patches eariler in this thread fixed the slow bring up problem
> for me.
>
> Same issue you report, 40 seconds until the libertas firmware loads.
>
> Thanks Donald!
>
> I'm using it with Sakoman's 3.2 kernel.
>
> I consolidated the patches into one file here
>
>
> https://github.com/scottellis/meta-jumpnow/blob/master/recipes-kernel/linux/linux-sakoman-3.2/libertas-async-fwload.patch
>
> and an example on how to include it in the kernel recipe here
>
>
> https://github.com/scottellis/meta-jumpnow/blob/master/recipes-kernel/linux/linux-sakoman_3.2.bb
>
> I have nothing related to the wifi drivers in /etc/modprobe.d
>

I've started looking around for info on running the 3.2 kernel with the
sakoman r13 system and I don't see much (or maybe nothing) on the sakoman
site about this.  I can't find any packages in opkg list that relate to the
3.2 kernel.  Are there any instructions posted somewhere that I'm missing?

I see bits and blurbs about compiling a 3.2 kernel in the mailing list
archives when I google, but it's been longer than 6 months since I've tried
to build the linux kernel so I've forgotten most of what I knew about that.
 Most of what I've found is references to people getting 3.2 running or
trying to, but nothing about how to do it?

Are there any instructions posted anywhere for getting the 3.2 kernel going
on a sakoman r13 system?

Thanks,

Curt.
-- 
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org

YMMV, but this is what I'm using

--- /etc/udev/scripts/wlan.rules ---
KERNEL=="wlan0", ACTION=="add" RUN+="/etc/udev/scripts/wlan.sh"
KERNEL=="wlan0", ACTION=="remove" RUN+="/etc/udev/scripts/wlan.sh"

--- /etc/udev/scripts/wlan.sh ---
#!/bin/sh

if [ "$INTERFACE" = "wlan0" ]; then
  case $ACTION in
    add)
	/usr/sbin/wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B
        sleep 1 
	/sbin/udhcpc -iwlan0
    	;;
    remove)
	/usr/bin/killall wpa_supplicant
    	;;
  esac
fi

--- /etc/wpa_supplicant.conf ---
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1

network={
     ssid="my-ssid"
     proto=WPA2
     key_mgmt=WPA-PSK
     pairwise=CCMP TKIP
     group=CCMP TKIP
     scan_ssid=1
     psk="my-passphrase"
     priority=10
}


I have no references to wlan0 in /etc/network/interfaces.

I also do not have network manager installed. It's a custom image.

I have wlan0 up with an IP address by the time I get a login prompt, 
~20 seconds after power-on.

I have only used this at my office. WPA2 access point (Netgear N600).

If you have to modify it to work in other scenarios I'd like to hear about
it.
I don't have much wireless testing equipment.





--
View this message in context: http://gumstix.8.n6.nabble.com/Did-they-ever-solve-the-slow-bring-up-of-wifi-problem-tp4944197p4965531.html
Sent from the Gumstix mailing list archive at Nabble.com.

Since there hasn't been any replies to my specific question, maybe I can
re-ask a slightly different way?  I have a usb wifi device I'd like to run
from my overo.  It works on my fedora desktop system.  However, the drivers
are not built by default in the sakoman r13 v3.0.0 kernel.  I need the
ath9k_htc drivers.  I think I see a reference to those in the 3.0.0 kernel
config.  I think (I hope!) the drivers are included in the 3.0.0 kernel or
the 3.2 kernel so at this point I don't care either way which one I use,
but I'd like to rebuild the kernel with the needed drivers included, or
build just the driver modules I need (?)

In the old default gumstix OpenEmbedded system with bitbake, I was able to
rebuild the kernel 2.6 and had that figured out, but that was quite a while
ago now.

What do I need to do to rebuild the kernel (or just the modules I need) in
the sakoman system?  Are there any short cuts or docs?

Do I need to start from scratch and recompile the entire sakoman r13 +
gnome distribution from source?

Is there a way to streamline that and just build the kernel and not the
whole rootfs from source?

Can I do this with the native development system onboard the overo or do I
need to cross compile from my linux pc host?

I run Fedora here.  Most of the "from scratch" instructions presume Ubuntu
-- is that a requirement for doing any or all of this?

I can probably figure out quite a bit on my own, but I'm hoping someone can
just nudge me in the right starting direction here and tell me that the
shortest path to building a new kernel for sakoman r13 is to do XYZ, and
hopefully I can take it from there with minimal hand holding.  I'd like to
avoid having to compile the entire shooting match from scratch if I can,
but if I must, then maybe someone can at least tell me that so I don't
waste time looking for shortcuts that don't exist?

Thanks!  (And I apologize in advance if these are dumb questions and I've
just missed all the documentation -- but in that case please could someone
point me to the appropriate documentation?)


Curt.



On Mon, Oct 1, 2012 at 9:44 AM, Curtis Olson <curtolson@...:

> I've started looking around for info on running the 3.2 kernel with the
> sakoman r13 system and I don't see much (or maybe nothing) on the sakoman
> site about this.  I can't find any packages in opkg list that relate to the
> 3.2 kernel.  Are there any instructions posted somewhere that I'm missing?
>
> I see bits and blurbs about compiling a 3.2 kernel in the mailing list
> archives when I google, but it's been longer than 6 months since I've tried
> to build the linux kernel so I've forgotten most of what I knew about that.
>  Most of what I've found is references to people getting 3.2 running or
> trying to, but nothing about how to do it?
>
> Are there any instructions posted anywhere for getting the 3.2 kernel
> going on a sakoman r13 system?
>
> Thanks,
>
> Curt.
> --
> Curtis Olson:
> http://www.atiak.com - http://aem.umn.edu/~uav/
> http://www.flightgear.org - http://gallinazo.flightgear.org
>
>


-- 
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org

Hello Curtis,

Sorry for the delay, but I have been tied up with another project for the
past few months.  I will try to answer you questions the best I can.


*
> In the old default gumstix OpenEmbedded system with bitbake, I was able to
> rebuild the kernel 2.6 and had that figured out, but that was quite a
> while ago now.
> 
> What do I need to do to rebuild the kernel (or just the modules I need) in
> the sakoman system?  Are there any short cuts or docs?
*

What I usually do is run the bitbake command /bitbake -c menuconfig
virtual/kernel/ to configure the kernel that way I need it and then run
/bitbake virtual/kernel/ to rebuild the kernel (you might have to clean the
kernel first with bit bake -c clean virtual/kernel and then configure/build
the kernel, but I can't recall).


*
> Do I need to start from scratch and recompile the entire sakoman r13 +
> gnome distribution from source?
*

I'm not familiar with building the sakoman distributions so I can't confirm
or deny this.  But, I presume their should be a way to either install the
newly compiled kernel built with OpenEmbedded or just install the LKM itself
if the kernel configured/built with OpenEmbedded is the same as the kernel
running on the r13+ sakoman distribution you are using.


*
> Is there a way to streamline that and just build the kernel and not the
> whole rootfs from source?
*
My first answer should allow you to just build the kernel and not the whole
rootfs.


*
> Can I do this with the native development system onboard the overo or do I
> need to cross compile from my linux pc host?
*
You could do this on the Overo if you have the build tools necessary, but I
will probably take the whole day (probably more) to recompile the kernel. 
Your best bet is to cross-compile the kernel and either install it manually
or use the opkg package manager on the overo.


*
> I run Fedora here.  Most of the "from scratch" instructions presume Ubuntu
> -- is that a requirement for doing any or all of this?
*
It's highly recommended, but I'm sure you can use Fedora with the right
workarounds/modifications.  I think a few members of the community here use
Fedora as well, so you will have to ask around to see how they configured
there system accordingly.


*
> I can probably figure out quite a bit on my own, but I'm hoping someone
> can just nudge me in the right starting direction here and tell me that
> the shortest path to building a new kernel for sakoman r13 is to do XYZ,
> and hopefully I can take it from there with minimal hand holding.  I'd
> like to avoid having to compile the entire shooting match from scratch if
> I can, but if I must, then maybe someone can at least tell me that so I
> don't waste time looking for shortcuts that don't exist?
*
Again, I'm not the best source for the Sakoman images (may be Steve will
chime in here and give some insight), but I really don't think you need to
rebuild the entire distribution just to update the kernel or add a few LKMs
to your currently running kernel.

I hope $0.02 will help get you started and pointing you in the right
direction.

-Donald



--
View this message in context: http://gumstix.8.n6.nabble.com/Did-they-ever-solve-the-slow-bring-up-of-wifi-problem-tp4944197p4965540.html
Sent from the Gumstix mailing list archive at Nabble.com.

Hello,

I work with overo for some time and would like to switch to duovero.

I have looked in the documentation to see how to get started, which branch to checkout and how to create the image since there is no nand on the COM.

with the overo COM, I used the documentation found here : http://gumstix.org/software-development/open-embedded/61-using-the-open-embedded-build-system.html to create my environment.  I have found nothing for the duovero.

I found that the kernel to use is the 3.6, and found that we now need to use the yocto project ?!  No more open embedded ?

With open embedded it was possible to compile on the gumstix, is it possible with the duovero ?

So, here are my questions : 

1. is there any documentation to get started with the duovero ?
2. is it possible to compile on the duovero COM ?

Thank you :-)

Kris

Hello


For a custom application, I need to have 3mm between boards.  Unfortunately at gumstix the spacers are 1.5mm.  Does somebody knows which company produce these small pieces ?  I have found some replacements but the smaller part needs a 4mm hole, not a #0-80 as for the gumstix.

Thank you

Kris

Hi Kris,

> with the overo COM, I used the documentation found here :
> http://gumstix.org/software-development/open-embedded/61-using-the-open-embedded-build-system.html
> to create my environment.  I have found nothing for the duovero.
There is woefully little about the development environment at this
point but the primary focus has been on getting a kernel that works
well with the duoVero: http://gumstix.org/access-source-code.html
At this point, I'd recommend DuoVero COMs for those who are
comfortable adding their own meta-layer to a oe-core build for DuoVero
or those who specifically want the OMAP4430.
Better software support is underway!
>
> I found that the kernel to use is the 3.6, and found that we now need to use
> the yocto project ?!  No more open embedded ?
The Yocto Project is an umbrella project that includes OE.  A lot of
the technology is the same between oe-classic and the
oe-core+meta-layers version currently in use.
>
> With open embedded it was possible to compile on the gumstix, is it possible
> with the duovero ?
Yes---native compilation works on DuoVero too.
>
> So, here are my questions :
>
> 1. is there any documentation to get started with the duovero ?
For the hardware guys, this is the best source so far:
http://gumstix.org/images/duovero_srm_latest.pdf
> 2. is it possible to compile on the duovero COM ?
It is definitely possible to compile on the duoVero COM.

--Ash

Hello Ash,

Thank you for your reply,

Now I am convinced that I will stay with the overo line :-)

I appreciate !

Kris




________________________________
 From: Ash Charles <ash@...>
To: kris duff <t_dufff@...>; General mailing list for gumstix users. <gumstix-users@...> 
Sent: Friday, October 19, 2012 12:22:27 PM
Subject: Re: [Gumstix-users] duovero getting started ?
 
Hi Kris,

> with the overo COM, I used the documentation found here :
> http://gumstix.org/software-development/open-embedded/61-using-the-open-embedded-build-system.html
> to create my environment.  I have found nothing for the duovero.
There is woefully little about the development environment at this
point but the primary focus has been on getting a kernel that works
well with the duoVero: http://gumstix.org/access-source-code.html
At this point, I'd recommend DuoVero COMs for those who are
comfortable adding their own meta-layer to a oe-core build for DuoVero
or those who specifically want the OMAP4430.
Better software support is underway!
>
> I found that the kernel to use is the 3.6, and found that we now need to use
> the yocto project ?!  No more open embedded ?
The Yocto Project is an umbrella project that includes OE.  A lot of
the technology is the same between oe-classic and the
oe-core+meta-layers version currently in use.
>
> With open embedded it was possible to compile on the gumstix, is it possible
> with the duovero ?
Yes---native compilation works on DuoVero too.
>
> So, here are my questions :
>
> 1. is there any documentation to get started with the duovero ?
For the hardware guys, this is the best source so far:
http://gumstix.org/images/duovero_srm_latest.pdf
> 2. is it possible to compile on the duovero COM ?
It is definitely possible to compile on the duoVero COM.

--Ash