Testing for Marvell Dreamplug U-Boot-2017.07-tld-1

I used kwboot with the latest kernel and rootfs.

Linux debian 4.13.5-kirkwood-tld-1
Debian-4.12.1-kirkwood-tld-1-rootfs
uboot.2017.07-tld-1.dreamplug

Which produces the already known.

[   22.738932] Bluetooth: Core ver 2.22
[   22.765495] NET: Registered protocol family 31
[   22.773351] mwifiex_sdio mmc0:0001:1: Direct firmware load for mrvl/sd8787_uapsta.bin failed with error -2
[   22.773365] mwifiex_sdio mmc0:0001:1: Failed to get firmware mrvl/sd8787_uapsta.bin
[   22.773372] mwifiex_sdio mmc0:0001:1: info: _mwifiex_fw_dpc: unregister device
[   22.905521] Bluetooth: HCI device and connection manager initialized
[   22.911919] Bluetooth: HCI socket layer initialized
[   22.951340] Bluetooth: L2CAP socket layer initialized
[   22.974357] Bluetooth: SCO socket layer initialized
[   23.016767] Bluetooth: vendor=0x2df, device=0x911a, class=255, fn=2
[   23.155334] btmrvl_sdio mmc0:0001:2: Direct firmware load for mrvl/sd8787_uapsta.bin failed with error -2
[   23.164959] Bluetooth: request_firmware(firmware) failed, error code = -2
[   23.171831] Bluetooth: Failed to download firmware!
[   23.176778] Bluetooth: Downloading firmware failed!
[   23.181941] Bluetooth: vendor=0x2df, device=0x911b, class=255, fn=3
[   23.305320] btmrvl_sdio mmc0:0001:3: Direct firmware load for mrvl/sd8787_uapsta.bin failed with error -2
[   23.314932] Bluetooth: request_firmware(firmware) failed, error code = -2
[   23.321791] Bluetooth: Failed to download firmware!
[   23.326739] Bluetooth: Downloading firmware failed!
done.

From https://forum.doozan.com/read.php?2,29065

bodhi Wrote:
-------------------------------------------------------
>
> After booted into Debian, to get Wifi, Bluetooth,
> and the SD card working, install libertas firmware
> (this is available in jessie non-free apt
> sources):
>

> apt-get install firmware-libertas
>

>
Will need to add non-free to the sources.list though.

deb http://ftp.us.debian.org/debian stretch main contrib non-free

deb http://security.debian.org/ stretch/updates main contrib non-free

deb     http://http.debian.net/debian stretch-updates main contrib non-free

Which results in:

[   28.028657] Bluetooth: Core ver 2.22
[   28.056967] NET: Registered protocol family 31
[   28.082389] Bluetooth: HCI device and connection manager initialized
[   28.116436] Bluetooth: HCI socket layer initialized
[   28.143463] Bluetooth: L2CAP socket layer initialized
[   28.180334] Bluetooth: SCO socket layer initialized
[   28.713951] mwifiex_sdio mmc0:0001:1: info: FW download over, size 463240 bytes
[   28.845309] mwifiex_sdio mmc0:0001:1: WLAN FW is active
[   28.850835] Bluetooth: vendor=0x2df, device=0x911a, class=255, fn=2
[   29.455683] sdio platform data not available
[   29.457487] mwifiex_sdio mmc0:0001:1: CMD_RESP: cmd 0x242 error, result=0x2
[   29.468813] mwifiex_sdio mmc0:0001:1: mwifiex_process_cmdresp: cmd 0x242 failed during	initialization
[   29.501354] Bluetooth: vendor=0x2df, device=0x911b, class=255, fn=3
[   29.509416] mwifiex_sdio mmc0:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (14.66.35.p52) 
[   29.509424] mwifiex_sdio mmc0:0001:1: driver_version = mwifiex 1.0 (14.66.35.p52) 
done (timeout).
[ ok ] Activating swap:.
[  148.591864] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[ ok ] Will now activate lvm and md swap:done.
[info] Will now check all file systems.
fsck from util-linux 2.29.2
Checking all file systems.
LABEL=rootfs is mounted
[....] Done checking file systems. A log is being saved in /var/log/fsck/checkfs if that location i[ ok table..
[  149.645249] Bluetooth: FW failed to be active in time!
[  149.650480] Bluetooth: Downloading firmware failed!

update & upgrade did not change outcome nor did adding proposed-updates and backports.

Do I need to blacklist drivers?

Should I drop back to just 4.12 kernel & rootfs and retry?

What would you want me to do to try and chase this down?

Thanks feas!

I'll take a look in my Dreamplug. IIRC, I thought this mwifiex_sdio error was gone the last time I look.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> Thanks feas!
>
> I'll take a look in my Dreamplug. IIRC, I thought
> this mwifiex_sdio error was gone the last time I
> look.

I did too, why I asked if you think I should try older kernels to see or if you might have been aware of a change and was working it in the new write up. Full disclosure, been a rough couple days so might just be me. (I know shocking ;))

Have not get to my Dreamplug yet, but I do vaguely recall there was some change in the way FW bin files managed in new kernel version.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/22/2017 08:00PM by bodhi.

i am testing backwards from 4.12 to 4.4 to see were it works. Will let you know if I find one working. I vaguely remember messing with ap mode on but will find out.

edit:

None of them worked for me. I believe I had to follow these instructions to get it working before. Will test it tomorrow with the latest rootfs and kernel.

https://www.spinifex.com.au/plugs/dphowtowificl.html



Edited 1 time(s). Last edit at 11/22/2017 09:41PM by feas.

Here is my log

Linux Dreamplug 4.13.5-kirkwood-tld-1 #1 PREEMPT Fri Oct 6 23:54:39 PDT 2017 armv5tel GNU/Linux

[   30.029297] mwifiex_sdio mmc0:0001:1: info: FW download over, size 447384 bytes
[   30.158004] mwifiex_sdio mmc0:0001:1: WLAN FW is active
[   30.168540] Bluetooth: vendor=0x2df, device=0x911a, class=255, fn=2
[   30.240396] EXT4-fs (sda2): mounting ext3 file system using the ext4 subsystem
[   30.283661] EXT4-fs (sda2): warning: maximal mount count reached, running e2fsck is recommended
[   30.302744] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: errors=remount-ro
[   30.668360] sdio platform data not available
[   30.669791] mwifiex_sdio mmc0:0001:1: CMD_RESP: cmd 0x242 error, result=0x2
[   30.681192] mwifiex_sdio mmc0:0001:1: mwifiex_process_cmdresp: cmd 0x242 failed during	initialization
[   30.693810] Bluetooth: vendor=0x2df, device=0x911b, class=255, fn=3
[   30.702109] sdio platform data not available
[   30.728712] mwifiex_sdio mmc0:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (14.66.9.p96) 
[   30.755207] mwifiex_sdio mmc0:0001:1: driver_version = mwifiex 1.0 (14.66.9.p96) 
[   32.817884] Bluetooth: hci0 command 0x1005 tx timeout
[   34.897884] Bluetooth: hci0 command 0x0c23 tx timeout
[   35.857892] Bluetooth: PSMODE command failed
[   36.977881] Bluetooth: hci0 command 0x0c14 tx timeout
[   39.057887] Bluetooth: hci0 command 0x0c25 tx timeout
[   40.897895] Bluetooth: HSCFG command failed
[   41.137901] Bluetooth: hci0 command tx timeout
[   45.857898] Bluetooth: module_cfg_cmd(f1) failed
[   51.935931] EXT4-fs (sdc1): re-mounted. Opts: (null)

It might not be a FW problem.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Was it from a clean 4.13.5 stretch rootfs and just upgrade and add libertas cause your file is an older version.

I added some other programs after my post and had varying results. But the consistent theme seemed to be timing out.

ap-utils uapevent uaputl iw firmware-misc-nonfree firmware-linux-nonfree firmware-linux-free firmware-linux

feas Wrote:
-------------------------------------------------------
> Was it from a clean 4.13.5 stretch rootfs and just
> upgrade and add libertas cause your file is an
> older version.
>
> I added some other programs after my post and had
> varying results. But the consistent theme seemed
> to be timing out.
>
>

> ap-utils uapevent uaputl iw firmware-misc-nonfree
> firmware-linux-nonfree firmware-linux-free
> firmware-linux
>

Yup. I have not upgraded this rootfs for a while so FW is old.

I'll upgrade and see if I get the same error as you have.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/22/2017 10:26PM by bodhi.

feas,

Looks like my FW load was OK. The error was BT initialization.

root@Dreamplug:~# uname -a
Linux Dreamplug 4.13.5-kirkwood-tld-1 #1 PREEMPT Fri Oct 6 23:54:39 PDT 2017 armv5tel GNU/Linux
root@Dreamplug:~# cat /etc/debian_version 
9.2

[   29.282586] Bluetooth: HCI device and connection manager initialized
[   29.382192] Bluetooth: HCI socket layer initialized
[   29.418124] Bluetooth: L2CAP socket layer initialized
[   29.454823] Bluetooth: SCO socket layer initialized

[   30.059383] mwifiex_sdio mmc0:0001:1: info: FW download over, size 447384 bytes
[   30.187999] mwifiex_sdio mmc0:0001:1: WLAN FW is active

[   30.211338] Bluetooth: vendor=0x2df, device=0x911a, class=255, fn=2
[   30.219483] EXT4-fs (sda2): mounting ext3 file system using the ext4 subsystem
[   30.241993] EXT4-fs (sda2): warning: maximal mount count reached, running e2fsck is recommended
[   30.275550] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: errors=remount-ro
[   30.698315] sdio platform data not available
[   30.700219] mwifiex_sdio mmc0:0001:1: CMD_RESP: cmd 0x242 error, result=0x2
[   30.711603] mwifiex_sdio mmc0:0001:1: mwifiex_process_cmdresp: cmd 0x242 failed during	initialization
[   30.726263] Bluetooth: vendor=0x2df, device=0x911b, class=255, fn=3
[   30.736500] sdio platform data not available
[   30.759331] mwifiex_sdio mmc0:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (14.66.9.p96) 
[   30.786770] mwifiex_sdio mmc0:0001:1: driver_version = mwifiex 1.0 (14.66.9.p96) 
[   32.897843] Bluetooth: hci0 command 0x0c23 tx timeout
[   34.977843] Bluetooth: hci0 command 0x0c14 tx timeout
[   37.057844] Bluetooth: hci0 command 0x0c25 tx timeout
[   39.137872] Bluetooth: hci0 command 0x0c38 tx timeout
[   41.217840] Bluetooth: hci0 command 0x0c39 tx timeout
[   43.297854] Bluetooth: hci0 command tx timeout
[   46.497853] Bluetooth: module_cfg_cmd(f1) failed

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/23/2017 03:29AM by bodhi.

So I have blacklisted in /lib/modprobe.d/fbdev-blacklist.conf:

blacklist mwifiex_sdio
blacklist mwifiex
blacklist libertas
blacklist libertas_sdio

and have added sd8787_uapsta.bin in /lib/firmware/mrvl/

Which seems to be getting closer but still returns:

[   22.843966] Bluetooth: Core ver 2.22
[   22.878751] NET: Registered protocol family 31
[   22.884598] usb 1-1.3: reset high-speed USB device number 4 using orion-ehci
[   22.945465] Bluetooth: HCI device and connection manager initialized
[   22.984678] Bluetooth: HCI socket layer initialized
[   23.007853] Bluetooth: L2CAP socket layer initialized
[   23.012963] Bluetooth: SCO socket layer initialized
[   23.186613] Bluetooth: vendor=0x2df, device=0x911a, class=255, fn=2
[   23.368608] random: crng init done
[   23.741106] Bluetooth: FW download over, size 429336 bytes
[   24.344652] sdio platform data not available
[   24.349345] Bluetooth: vendor=0x2df, device=0x911b, class=255, fn=3
done (timeout).
[ ok ] Activating swap:.
[  142.980053] EXT4-fs (sda1): re-mounted. Opts: (null)
[....] Will now check root file system:fsck from util-linux 2.29.2
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -y -C0 /dev/sda1 
e2fsck 1.43.4 (31-Jan-2017)
rootfs: clean, 14535/244800 files, 208756/978432 blocks
. ok 
[  143.230590] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[ ok ] Will now activate lvm and md swap:done.
[info] Will now check all file systems.
fsck from util-linux 2.29.2
Checking all file systems.
LABEL=rootfs is mounted
[....] Done checking file systems. A log is being saved in /var/log/fsck/checkfs[ ok hat location is writable..
[  144.474619] Bluetooth: FW failed to be active in time!
[  144.484828] Bluetooth: Downloading firmware failed!

The [ 24.344652] sdio platform data not available is consistent every time.

Reading the below seems to indicate a problem with if a pin pull low might be the culprit.

https://community.nxp.com/thread/311138

unfortunately I do not quite follow if this may be the cause.