[opensuse-arm] bcm43xx-firmware not symlinked in RPi3 32 bits
Hi, WiFi does not work out of the box on JeOS-raspberrypi3 armv7l image (downstream 32 bits) because: cat /sys/firmware/devicetree/base/compatible returns: brcm,bcm2710brcm,bcm2709 and not: *raspberrypi,3-model-b* But: cat /sys/firmware/devicetree/base/model returns: Raspberry Pi 3 Model B Could we add this case in bcm43xx-firmware script? Note that JeOS raspberry pi 3 (AArch64 contrib) has no WiFi, probably because of the following error: brcmfmac_sdio: probe of mmc1:0001:1 failed with error -110 brcmfmac_sdio: probe of mmc1:0001:2 failed with error -110 whereas mmc1 seems to be ok: [ 3.109301] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) [ 3.111430] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 3.113282] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 3.120140] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) [ 3.339697] random: nonblocking pool is initialized [ 3.357090] mmc1: new SDIO card at address 0001 Any idea why it happens? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Guillaume, Am 26.10.2016 um 12:02 schrieb Guillaume Gardet:
WiFi does not work out of the box on JeOS-raspberrypi3 armv7l image (downstream 32 bits) because: cat /sys/firmware/devicetree/base/compatible returns: brcm,bcm2710brcm,bcm2709 and not: *raspberrypi,3-model-b*
I know, which is why I chose not to install that package for armv7l: https://build.opensuse.org/request/show/433902 Dirk made the change to install it for armv7l, too: https://build.opensuse.org/package/rdiff/openSUSE:Factory:ARM/JeOS?linkrev=base&rev=469 I already "shouted" at him for doing so without asking me and for doing it silently as a commit rather than SR so that I didn't get notified. ;) If we know it doesn't work, there's no point in installing it.
But: cat /sys/firmware/devicetree/base/model returns: Raspberry Pi 3 Model B
Could we add this case in bcm43xx-firmware script?
First of all, does it even work if you create the symlink manually? :) Next, why do we need downstream quirks here? It's an official Factory package and we will soon have a Tumbleweed based aarch64 image, the only issue still to be worked around is the broadcom/ subdir for the .dtb (i.e., a U-Boot patch). I am already running 4.8.4 on mine using first a symlink, now a custom boot.scr script calling bootefi. * I would not want to do it based on a "brcm,bcm2710" compatible string because it's not part of the SoC. * The model seems possible although quite ugly as it's supposed to be human-readable only. * What about simply patching the downstream .dts to prepend the official board compatible instead? * An alternative would be config.sh for an install-time symlink.
Note that JeOS raspberry pi 3 (AArch64 contrib) has no WiFi, probably because of the following error: brcmfmac_sdio: probe of mmc1:0001:1 failed with error -110 brcmfmac_sdio: probe of mmc1:0001:2 failed with error -110
whereas mmc1 seems to be ok: [ 3.109301] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) [ 3.111430] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 3.113282] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 3.120140] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) [ 3.339697] random: nonblocking pool is initialized [ 3.357090] mmc1: new SDIO card at address 0001
Any idea why it happens?
See https://build.opensuse.org/request/show/435498 On aarch64 /etc/dracut.conf.d/raspberrypi_modules.conf gained an entry to blacklist one of the two SDHCI drivers that interfered with Wifi. Courtesy of our trainee Fabian, who did awesome work for the rpi3! We decided we couldn't enable it though because 4.8 (now in Factory) does not have the second SDHCI driver, and blacklisting the only available driver breaks booting from SD card. Therefore you need to manually comment out that line *if* using only downstream kernels and wanting to use Wifi, then run mkinitrd or equivalent dracut command. Essentially we are waiting how things will evolve upstream - v4.9-rc2 still only has the sdhci-iproc driver AFAICS, so this is specific to the 42.2 kernel at this time and more of a quick workaround than a permanent solution. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Le 26/10/2016 à 14:14, Andreas Färber a écrit :
Hi Guillaume,
Am 26.10.2016 um 12:02 schrieb Guillaume Gardet:
WiFi does not work out of the box on JeOS-raspberrypi3 armv7l image (downstream 32 bits) because: cat /sys/firmware/devicetree/base/compatible returns: brcm,bcm2710brcm,bcm2709 and not: *raspberrypi,3-model-b* I know, which is why I chose not to install that package for armv7l: https://build.opensuse.org/request/show/433902
Dirk made the change to install it for armv7l, too: https://build.opensuse.org/package/rdiff/openSUSE:Factory:ARM/JeOS?linkrev=base&rev=469
I already "shouted" at him for doing so without asking me and for doing it silently as a commit rather than SR so that I didn't get notified. ;) If we know it doesn't work, there's no point in installing it.
But: cat /sys/firmware/devicetree/base/model returns: Raspberry Pi 3 Model B
Could we add this case in bcm43xx-firmware script? First of all, does it even work if you create the symlink manually? :)
Yes, it does. :)
Next, why do we need downstream quirks here? It's an official Factory package and we will soon have a Tumbleweed based aarch64 image, the only issue still to be worked around is the broadcom/ subdir for the .dtb (i.e., a U-Boot patch). I am already running 4.8.4 on mine using first a symlink, now a custom boot.scr script calling bootefi.
* I would not want to do it based on a "brcm,bcm2710" compatible string because it's not part of the SoC. * The model seems possible although quite ugly as it's supposed to be human-readable only. * What about simply patching the downstream .dts to prepend the official board compatible instead? * An alternative would be config.sh for an install-time symlink.
I think this last solution should be the best.
Note that JeOS raspberry pi 3 (AArch64 contrib) has no WiFi, probably because of the following error: brcmfmac_sdio: probe of mmc1:0001:1 failed with error -110 brcmfmac_sdio: probe of mmc1:0001:2 failed with error -110
whereas mmc1 seems to be ok: [ 3.109301] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) [ 3.111430] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 3.113282] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 3.120140] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) [ 3.339697] random: nonblocking pool is initialized [ 3.357090] mmc1: new SDIO card at address 0001
Any idea why it happens? See https://build.opensuse.org/request/show/435498
On aarch64 /etc/dracut.conf.d/raspberrypi_modules.conf gained an entry to blacklist one of the two SDHCI drivers that interfered with Wifi. Courtesy of our trainee Fabian, who did awesome work for the rpi3!
We decided we couldn't enable it though because 4.8 (now in Factory) does not have the second SDHCI driver, and blacklisting the only available driver breaks booting from SD card. Therefore you need to manually comment out that line *if* using only downstream kernels and wanting to use Wifi, then run mkinitrd or equivalent dracut command.
Essentially we are waiting how things will evolve upstream - v4.9-rc2 still only has the sdhci-iproc driver AFAICS, so this is specific to the 42.2 kernel at this time and more of a quick workaround than a permanent solution.
Thanks for information. Guillaume
Regards, Andreas
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (2)
-
Andreas Färber -
Guillaume Gardet