logo

Could not compile stylesheet for simplistic. Using last compiled stylesheet.

Libertas taking a long time to launch

posted in Uncategorized
Thursday, November 03 2011, 05:14 PM
davigier
davigier
Offline
0
Hello I have an issue with the libertas module and firmware: it\\\'s taking a very long time to load at start-up. I have the following in dmesg: [ 20.109039] libertas_sdio: Libertas SDIO driver [ 20.114044] libertas_sdio: Copyright Pierre Ossman and then: [ 143.142211] libertas: 00:0b:6c:90:d1:32, fw 9.70.3p24, cap 0x00000303 [ 143.149200] libertas: unidentified region code; using the default (USA) [ 143.164642] cfg80211: Calling CRDA for country: US [ 143.171325] libertas: wlan0: Marvell WLAN 802.11 adapter Any idea why it is taking so long ? The consequence is that the connection script in /etc/network/interfaces is not picking wlan0 at startup. I tried several things: - Doing a rmmod libertas_sdio between the 20s and the 143s timestamps gave me the following: rmmod: cannot unload \\\'libertas_sdio\\\': Device or resource busy So it\\\'s definitely trying to do something. - Once loaded, rmmod libertas_sdio and modprobe libertas_sdio work fine (no time lag): [ 205.916412] libertas_sdio: Libertas SDIO driver [ 205.921173] libertas_sdio: Copyright Pierre Ossman [ 205.948364] libertas: 00:0b:6c:90:d1:32, fw 9.70.3p24, cap 0x00000303 [ 205.955383] libertas: unidentified region code; using the default (USA) [ 205.974517] cfg80211: Calling CRDA for country: US [ 205.994384] libertas: wlan0: Marvell WLAN 802.11 adapter - I noticed that the file /etc/dev.tar contained the following lines: ./dev.tar:dev/.udev/firmware-missing/libertas\\\\x2fsd8686_v8_helper.bin ./dev.tar:dev/.udev/firmware-missing/libertas\\\\x2fsd8686_v9_helper.bin I don\\\'t know if it has anything to do with my issue... - Is there a configuration file somewhere that tells the kernel what modules to load ? Thanks for any help.
Responses (9)
  • Accepted Answer

    davigier
    davigier
    Offline
    Friday, November 04 2011, 04:26 PM - #permalink
    0
    Has anyone hit into a similar issue ?
    The reply is currently minimized Show
  • Accepted Answer

    davigier
    davigier
    Offline
    Friday, November 04 2011, 04:32 PM - #permalink
    0
    I may be doing something wrong because actually I am unable to unload definitely my modules: when I unload them using rmmod, they load themselves again at the next reboot... What am I doing wrong ? Both issues could be linked I guess.
    The reply is currently minimized Show
  • Accepted Answer

    davigier
    davigier
    Offline
    Saturday, November 05 2011, 07:19 PM - #permalink
    0
    I think I\\\'m narrowing down on my issue. I noticed in the kernel sources that the file drivers/net/wireless/libertas/if_sdio.c contains the following: static const struct lbs_fw_table fw_table[] = { { MODEL_8385, \\\"libertas/sd8385_helper.bin\\\", \\\"libertas/sd8385.bin\\\" }, { MODEL_8385, \\\"sd8385_helper.bin\\\", \\\"sd8385.bin\\\" }, { MODEL_8686, \\\"libertas/sd8686_v9_helper.bin\\\", \\\"libertas/sd8686_v9.bin\\\" }, { MODEL_8686, \\\"libertas/sd8686_v8_helper.bin\\\", \\\"libertas/sd8686_v8.bin\\\" }, { MODEL_8686, \\\"sd8686_helper.bin\\\", \\\"sd8686.bin\\\" }, { MODEL_8688, \\\"libertas/sd8688_helper.bin\\\", \\\"libertas/sd8688.bin\\\" }, { MODEL_8688, \\\"sd8688_helper.bin\\\", \\\"sd8688.bin\\\" }, { 0, NULL, NULL } }; MODULE_FIRMWARE(\\\"libertas/sd8385_helper.bin\\\"); MODULE_FIRMWARE(\\\"libertas/sd8385.bin\\\"); MODULE_FIRMWARE(\\\"sd8385_helper.bin\\\"); MODULE_FIRMWARE(\\\"sd8385.bin\\\"); MODULE_FIRMWARE(\\\"libertas/sd8686_v9_helper.bin\\\"); MODULE_FIRMWARE(\\\"libertas/sd8686_v9.bin\\\"); MODULE_FIRMWARE(\\\"libertas/sd8686_v8_helper.bin\\\"); MODULE_FIRMWARE(\\\"libertas/sd8686_v8.bin\\\"); MODULE_FIRMWARE(\\\"sd8686_helper.bin\\\"); MODULE_FIRMWARE(\\\"sd8686.bin\\\"); MODULE_FIRMWARE(\\\"libertas/sd8688_helper.bin\\\"); MODULE_FIRMWARE(\\\"libertas/sd8688.bin\\\"); MODULE_FIRMWARE(\\\"sd8688_helper.bin\\\"); MODULE_FIRMWARE(\\\"sd8688.bin\\\"); Could it be that the driver is trying to find those v8 and v9 firmware files ? and so it could explain why the module is taking so long to load ???
    The reply is currently minimized Show
  • Accepted Answer

    hedwin
    hedwin
    Offline
    Sunday, November 06 2011, 12:35 AM - #permalink
    0
    When I switched to android gingerbread using 2.6.37 I added v9 to firmware file names to get the wireless and bluetooth working. What I am not sure of is whether the \\\"hugh\\\" delay made it not working.
    The reply is currently minimized Show
  • Accepted Answer

    davigier
    davigier
    Offline
    Monday, November 07 2011, 02:06 PM - #permalink
    0
    I tried adding v9 to the firmware file names, but it\\\'s not working any better... Actually, it\\\'s even worse: [ 204.898590] libertas: failed to find firmware (-2) [ 204.906646] libertas_sdio: probe of mmc1:0001:1 failed with error -2 Anyway, thanks for helping out Hedwin.
    The reply is currently minimized Show
  • Accepted Answer

    hedwin
    hedwin
    Offline
    Monday, November 07 2011, 02:58 PM - #permalink
    0
    In what directory did you put the firmware files? What distro do you use? (linaro, poky ...)
    The reply is currently minimized Show
  • Accepted Answer

    davigier
    davigier
    Offline
    Monday, November 07 2011, 03:01 PM - #permalink
    0
    I just managed to get it working !!! I had the firmware files in /lib/firmware. I moved them to /lib/firmware/libertas and it worked. However, renaming them to v9 did not work. Thanks Hedwin !! The wiki should be changed: it used to work to have the firmware files in /lib/firmware. It no longer works with 2.6.37
    The reply is currently minimized Show
  • Accepted Answer

    Monday, November 07 2011, 04:06 PM - #permalink
    0
    We have a IGEPv2 DM3730 with kernel version 3.1.0-rc10 and the solution here was not only to move the files to /lib/firmware/libertas but also to rename them from sd8686.bin to sd8686_v9.bin and sd8686_helper.bin to sd8686_v9_helper.bin
    The reply is currently minimized Show
  • Accepted Answer

    davigier
    davigier
    Offline
    Monday, November 07 2011, 04:26 PM - #permalink
    0
    Actually, Alexander, the same for me... I got a little mixed up. Here is what I have found out: - When putting the firmware files in /lib/firmware, it works only with the \\\"old\\\" naming, but there is a huge delay to bring the interface up - When putting the firmware files in /lib/firmware/libertas, it works well but only with the v9 naming, not the \\\"old\\\" naming Seems a bit strange, but I\\\'m finished exploring this issue, I\\\'m not going any further :-)
    The reply is currently minimized Show
Your Reply

SUPPORT


This email address is being protected from spambots. You need JavaScript enabled to view it.
This email address is being protected from spambots. You need JavaScript enabled to view it.
IGEP Community Wiki
IGEP Community Forum
IGEP Community Online Chat