BUG > Bluetooth PAN on Guruplug

[quertyn]

Hello,
I have a guruplug server, i want to use pan in order to use internet connexion by bluetooth thanks a bridge between bluetooth and ethernet on guruplug. First with hcitool dev i can see the chip bluetooth with information (MAC ...) After i compiled the source of bluez and i try to configure the bridge. But now with hcitool dev i have nothing. I unistall all bluez package but i think they overwrite some config file but i dont know which. So i want to return to the default config, at least i want to see bluetooth chip info again. How can i do ? I precise i don't have a jtag.
Thank for helping me.

[quertyn]

In this file /var/log/kern.log :
Jun 24 15:28:09 sheevaplug-debian kernel: Bluetooth: L2CAP ver 2.14
Jun 24 15:28:09 sheevaplug-debian kernel: Bluetooth: L2CAP socket layer initialized
Jun 24 15:28:09 sheevaplug-debian kernel: Bluetooth: RFCOMM TTY layer initialized
Jun 24 15:28:09 sheevaplug-debian kernel: Bluetooth: RFCOMM socket layer initialized
Jun 24 15:28:09 sheevaplug-debian kernel: Bluetooth: RFCOMM ver 1.11
Jun 24 15:28:10 sheevaplug-debian kernel: Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2
Jun 24 15:28:10 sheevaplug-debian kernel: btmrvl_sdio mmc0:0001:2: firmware: requesting sd8688_helper.bin
Jun 24 15:28:10 sheevaplug-debian kernel: btmrvl_sdio_download_helper: request_firmware(helper) failed, error code = -2
Jun 24 15:28:10 sheevaplug-debian kernel: btmrvl_sdio_download_fw: Failed to download helper!
Jun 24 15:28:10 sheevaplug-debian kernel: btmrvl_sdio_probe: Downloading firmware failed!

In the folder /lib/firmware/mrvl : i have helper_sd.bin  sd8688_ap.bin  sd8688.bin  sd8688_helper.bin
What does mean the error code 2 ?
Is possible that the kernel can't do the link with the firmware ?

[sfzhi]

Jun 24 15:28:10 sheevaplug-debian kernel: btmrvl_sdio mmc0:0001:2: firmware: requesting sd8688_helper.bin
Jun 24 15:28:10 sheevaplug-debian kernel: btmrvl_sdio_download_helper: request_firmware(helper) failed, error code = -2
Jun 24 15:28:10 sheevaplug-debian kernel: btmrvl_sdio_download_fw: Failed to download helper!
Jun 24 15:28:10 sheevaplug-debian kernel: btmrvl_sdio_probe: Downloading firmware failed!

In the folder /lib/firmware/mrvl : i have helper_sd.bin  sd8688_ap.bin  sd8688.bin  sd8688_helper.bin
What does mean the error code 2 ?

The error code 2 is ENOENT, which in this context means "file not found".

If you read the error message carefully, especially the part "requesting sd8688_helper.bin", you may notice that it wasn't requesting "mrvl/sd8688_helper.bin". The files "sd8688.bin" and "sd8688_helper.bin" should not be inside "mrvl", they should be directly in "/lib/firmware".

P.S. By the way, don't know if anyone noticed, the files "helper_sd.bin" and "sd8688_helper.bin" are exactly the same, so one of them can be replaced with a link to the other.

[velo_love]

Hi,

in my Guruplug server +, these 2 files sd8688.bin and sd8688_helper.bin are by default in the directory /root/firmware.
I don't use bluetooth but perhaps these files should be moved into the directory /lib/firmware.

[sfzhi]

in my Guruplug server +, these 2 files sd8688.bin and sd8688_helper.bin are by default in the directory /root/firmware.
I don't use bluetooth but perhaps these files should be moved into the directory /lib/firmware.

Yes, someone has decided to put those files in /root/firmware to prevent the kernel from finding them. And then that someone decided to do all those messy things with rmmod/insmod in /root/init_setup.sh in the attempt to deal with the "one chip + two firmware + three drivers" situation. The whole thing is one big kludge. Linux is flexible enough to solve those issues in a more decent way, but that is off-topic here.

My point is that, yes, in general the firmware belongs in /lib/firmware, but if you just move it there you may run into trouble because /root/init_setup.sh is not expecting that.

[velo_love]

My point is that, yes, in general the firmware belongs in /lib/firmware, but if you just move it there you may run into trouble because /root/init_setup.sh is not expecting that.

Yes, I quite agree with you: the init_setup.sh file is... strange. It seems to me there is a topic about how to set bluetooth and wifi according linux rules.

[quertyn]

ok thx it was just that the firmware were in /lib/firmware/mrvl not in the parent folder .