[opensuse-arm] Wireless interface on Raspberry Pi 3
My wireless device does not show up on my Raspberry Pi 3, running an up-to-date Leap 42.2 I have seen a number of places suggest editing /etc/dracut.conf.d/raspberrypi_modules.conf and removing sdhci-iproc so that the file becomes: add_drivers+=" bcm2835-sdhost bcm2835_dma mmc_block " # Workaround for Wifi # omit_drivers+=" sdhci-iproc" Then run mkinitrd -f Two questions;: 1. Is this the appropriate edit? 2. Does one run mkinitrd and not dracut on the Raspberry? I really do not want to mess up the initrd file! -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Am 25.08.2017 um 12:57 schrieb Roger Oberholtzer:
2. Does one run mkinitrd and not dracut on the Raspberry? I really do not want to mess up the initrd file!
Recent mkinitrd calls dracut for you. 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
On Fri, Aug 25, 2017 at 6:06 PM, Andreas Färber <afaerber@suse.de> wrote:
Hi,
Am 25.08.2017 um 12:57 schrieb Roger Oberholtzer:
2. Does one run mkinitrd and not dracut on the Raspberry? I really do not want to mess up the initrd file!
Recent mkinitrd calls dracut for you.
I did the suggested edit and built the initrd. After a reboot I still do not see a wireless device I only see this: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether b8:27:eb:cf:55:21 brd ff:ff:ff:ff:ff:ff inet 10.2.10.37/28 brd 10.2.10.47 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::ba27:ebff:fecf:5521/64 scope link valid_lft forever preferred_lft forever Oddly, the modules that was not added in the initrd is still loaded. I am guessing after the root fs was added. I have these modules loaded: Module Size Used by fuse 118784 1 dm_mod 155648 0 af_packet 49152 0 hid_generic 16384 0 usbhid 69632 0 smsc95xx 45056 0 usbnet 57344 1 smsc95xx mii 16384 2 usbnet,smsc95xx nls_iso8859_1 16384 1 nls_cp437 20480 1 vfat 20480 1 brcmfmac 249856 0 fat 86016 1 vfat vc4 122880 0 drm_kms_helper 196608 2 vc4 drm 475136 3 vc4,drm_kms_helper syscopyarea 16384 1 drm_kms_helper brcmutil 20480 1 brcmfmac sysfillrect 16384 1 drm_kms_helper dwc2 167936 0 sysimgblt 16384 1 drm_kms_helper cfg80211 655360 1 brcmfmac fb_sys_fops 16384 1 drm_kms_helper usbcore 327680 4 dwc2,usbhid,usbnet,smsc95xx usb_common 16384 2 dwc2,usbcore rfkill 36864 4 cfg80211 bcm2835_cpufreq 16384 0 i2c_bcm2835 16384 0 bcm2835_thermal 16384 0 pwm_bcm2835 16384 0 bcm2835_rng 16384 0 leds_gpio 16384 0 bcm2835_wdt 16384 0 mmc_block 45056 4 sdhci_iproc 16384 0 sdhci_pltfm 16384 1 sdhci_iproc sdhci 57344 2 sdhci_iproc,sdhci_pltfm bcm2835_sdhost 32768 0 mmc_core 188416 5 mmc_block,sdhci,brcmfmac,sdhci_iproc,bcm2835_sdhost bcm2835_dma 20480 0 virt_dma 16384 1 bcm2835_dma sg 53248 0 efivarfs 16384 1 Am I missing a needed module for the WiFi device? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Montag, 28. August 2017 09:59:22 CEST Roger Oberholtzer wrote:
On Fri, Aug 25, 2017 at 6:06 PM, Andreas Färber <afaerber@suse.de> wrote:
Hi,
Am 25.08.2017 um 12:57 schrieb Roger Oberholtzer:
2. Does one run mkinitrd and not dracut on the Raspberry? I really do not want to mess up the initrd file!
Recent mkinitrd calls dracut for you.
I did the suggested edit and built the initrd. After a reboot I still do not see a wireless device I only see this:
[...]
Am I missing a needed module for the WiFi device?
Do you have the required firmware files installed? There should be some message in the journal when the brcmfmac driver is loaded ... Kind regards, Stefan -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Mon, Aug 28, 2017 at 10:16 AM, Brüns, Stefan <Stefan.Bruens@rwth-aachen.de> wrote:
On Montag, 28. August 2017 09:59:22 CEST Roger Oberholtzer wrote:
On Fri, Aug 25, 2017 at 6:06 PM, Andreas Färber <afaerber@suse.de> wrote:
Hi,
Am 25.08.2017 um 12:57 schrieb Roger Oberholtzer:
2. Does one run mkinitrd and not dracut on the Raspberry? I really do not want to mess up the initrd file!
Recent mkinitrd calls dracut for you.
I did the suggested edit and built the initrd. After a reboot I still do not see a wireless device I only see this:
[...]
Am I missing a needed module for the WiFi device?
Do you have the required firmware files installed? There should be some message in the journal when the brcmfmac driver is loaded ...
I only see this: [ 10.234805] brcmfmac_sdio: probe of mmc1:0001:1 failed with error -110 [ 10.237045] brcmfmac_sdio: probe of mmc1:0001:2 failed with error -110 Not sure what error -110 is. Except that being negative means it is from the kernel. I see these files. -rw-r--r-- 1 root root 269595 May 30 21:23 bcm4329-fullmac-4.bin -rw-r--r-- 1 root root 96224 May 30 21:23 bcm43xx-0.fw -rw-r--r-- 1 root root 180 May 30 21:23 bcm43xx_hdr-0.fw -rw-r--r-- 1 root root 397312 May 30 21:23 brcmfmac43143.bin -rw-r--r-- 1 root root 385067 May 30 21:23 brcmfmac43143-sdio.bin -rw-r--r-- 1 root root 348160 May 30 21:23 brcmfmac43236b.bin -rw-r--r-- 1 root root 455745 May 30 21:23 brcmfmac43241b0-sdio.bin -rw-r--r-- 1 root root 403855 May 30 21:23 brcmfmac43241b4-sdio.bin -rw-r--r-- 1 root root 408682 May 30 21:23 brcmfmac43241b5-sdio.bin -rw-r--r-- 1 root root 479232 May 30 21:23 brcmfmac43242a.bin -rw-r--r-- 1 root root 253748 May 30 21:23 brcmfmac4329-sdio.bin -rw-r--r-- 1 root root 222126 May 30 21:23 brcmfmac4330-sdio.bin -rw-r--r-- 1 root root 402210 May 30 21:23 brcmfmac43340-sdio.bin -rw-r--r-- 1 root root 451566 May 30 21:23 brcmfmac4334-sdio.bin -rw-r--r-- 1 root root 569291 May 30 21:23 brcmfmac4335-sdio.bin -rw-r--r-- 1 root root 1178 Sep 14 2016 brcmfmac43362-sdio-bananapi-m1+.txt -rw-r--r-- 1 root root 1178 Sep 14 2016 brcmfmac43362-sdio-bananapi-m2.txt -rw-r--r-- 1 root root 219557 May 30 21:23 brcmfmac43362-sdio.bin -rw-r--r-- 1 root root 1178 Sep 14 2016 brcmfmac43362-sdio-cubietruck.txt -rw-r--r-- 1 root root 493599 May 30 21:23 brcmfmac4339-sdio.bin -rw-r--r-- 1 root root 369577 May 30 21:23 brcmfmac43430-sdio.bin -rw-r--r-- 1 root root 1108 Sep 14 2016 brcmfmac43430-sdio-raspberrypi3b.txt lrwxrwxrwx 1 root root 36 Jan 1 1970 brcmfmac43430-sdio.txt -> brcmfmac43430-sdio-raspberrypi3b.txt -rw-r--r-- 1 root root 488193 May 30 21:23 brcmfmac43455-sdio.bin -rw-r--r-- 1 root root 623304 May 30 21:23 brcmfmac4350c2-pcie.bin -rw-r--r-- 1 root root 626140 May 30 21:23 brcmfmac4350-pcie.bin -rw-r--r-- 1 root root 591837 May 30 21:23 brcmfmac4354-sdio.bin -rw-r--r-- 1 root root 557056 May 30 21:23 brcmfmac43569.bin -rw-r--r-- 1 root root 623012 May 30 21:23 brcmfmac4356-pcie.bin -rw-r--r-- 1 root root 526383 May 30 21:23 brcmfmac4356-sdio.bin -rw-r--r-- 1 root root 550333 May 30 21:23 brcmfmac43570-pcie.bin -rw-r--r-- 1 root root 629040 May 30 21:23 brcmfmac4358-pcie.bin -rw-r--r-- 1 root root 595472 May 30 21:23 brcmfmac43602-pcie.ap.bin -rw-r--r-- 1 root root 635449 May 30 21:23 brcmfmac43602-pcie.bin -rw-r--r-- 1 root root 989401 May 30 21:23 brcmfmac4366b-pcie.bin -rw-r--r-- 1 root root 623448 May 30 21:23 brcmfmac4371-pcie.bin I just had a similar issue with an iMac where I needed to remove the driver from the initrd because it did not find the firmware files in the initrd. When loaded later it was happy. But then I got an error message that the firmware file was not found. I don't seem to see that here. Maybe I am looking in the wrong place. I found a similar discussion at https://github.com/raspberrypi/linux/issues/1643 where the solution was to run rpi-update, which is a Raspbian thing... -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 28.08.2017 um 09:59 schrieb Roger Oberholtzer:
I did the suggested edit and built the initrd. After a reboot I still do not see a wireless device I only see this:
The edit didn't work for me either, neither did combining it with loading "sdhci_iproc" via modules-load.d. But running "modprobe -r sdhci_iproc" and then "modprobe sdhci_iproc" does at least fix the issue for the current boot. (you have to wait a few seconds for it to re-appear in "ip link" sometimes) I hope someone comes up with a more permanent fix, and of course find the root cause, but for now it might be enough just to write a little script that executes after the System has booted. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Mon, Aug 28, 2017 at 5:39 PM, Friedrich <friedrich.hunstock@t-online.de> wrote:
Am 28.08.2017 um 09:59 schrieb Roger Oberholtzer:
I did the suggested edit and built the initrd. After a reboot I still do not see a wireless device I only see this:
The edit didn't work for me either, neither did combining it with loading "sdhci_iproc" via modules-load.d. But running "modprobe -r sdhci_iproc" and then "modprobe sdhci_iproc" does at least fix the issue for the current boot. (you have to wait a few seconds for it to re-appear in "ip link" sometimes)
That seems to have done it for me, too. When I load the driver it reports: [83140.984355] sdhci: Secure Digital Host Controller Interface driver [83140.984369] sdhci: Copyright(c) Pierre Ossman [83140.987603] sdhci-pltfm: SDHCI platform and OF driver helper [83140.993375] sdhci-iproc 3f300000.sdhci: No vmmc regulator found [83140.993400] sdhci-iproc 3f300000.sdhci: No vqmmc regulator found [83141.039665] mmc1: SDHCI controller on 3f300000.sdhci [3f300000.sdhci] using PIO [83141.054880] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) [83141.056584] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [83141.058284] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [83141.061341] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) [83141.186611] mmc1: new SDIO card at address 0001 [83141.222935] brcmfmac: brcmf_sdio_drivestrengthinit: No SDIO Drive strength init done for chip 43430 rev 1 pmurev 24 [83143.245166] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Aug 29 2016 20:48:16 version 7.45.41.26 (r640327) FWID 01-4527cfab [83143.347340] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code The 'sdhci' and 'mmc1' lines are also present when the system boots. The difference is that 'brcmfmac_sdio:' reports this when the system boots: [ 10.234805] brcmfmac_sdio: probe of mmc1:0001:1 failed with error -110 [ 10.237045] brcmfmac_sdio: probe of mmc1:0001:2 failed with error -110 This really sounds like a problem I had with Leap 42.3 on an iMac where the wireless driver was placed in the initrd, but the firmware was not. So when the driver was loaded the firmware was not found. There seemed to be some recent change to dracut so that it did not know about the required firmware files. The solution was to remove the driver that needed the firmware from initrd. It then gets loaded later after the root file system is mounted, and the firmware is found. Which is what removing and reloading sdhci_iproc seems to accomplish. Maybe it is brcmfmac that should be removed from the initrd? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op dinsdag 29 augustus 2017 08:04:11 CEST schreef Roger Oberholtzer:
On Mon, Aug 28, 2017 at 5:39 PM, Friedrich
<friedrich.hunstock@t-online.de> wrote:
Am 28.08.2017 um 09:59 schrieb Roger Oberholtzer:
I did the suggested edit and built the initrd. After a reboot I still
do not see a wireless device I only see this: The edit didn't work for me either, neither did combining it with loading "sdhci_iproc" via modules-load.d. But running "modprobe -r sdhci_iproc" and then "modprobe sdhci_iproc" does at least fix the issue for the current boot. (you have to wait a few seconds for it to re-appear in "ip link" sometimes)
That seems to have done it for me, too. When I load the driver it reports:
This does not work for Tumbleweed. In fact it makes the system totally unusable. So be warned. -- fr.gr. Freek de Kruijf member openSUSE -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Tue, Aug 29, 2017 at 12:17 PM, Freek de Kruijf <freek@opensuse.org> wrote:
This does not work for Tumbleweed. In fact it makes the system totally unusable. So be warned.
Good to know. I did this on openSUSE Leap 42.2. I have been thinking of moving to Tumbleweed. But I cannot decide. It would be either that or Leap 42.3. Has anyone done a zypper dup from Leap 42.2 to 42.3 on the Pi 3? (New thread, I guess.) -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Mon, Aug 28, 2017 at 5:39 PM, Friedrich <friedrich.hunstock@t-online.de> wrote:
Am 28.08.2017 um 09:59 schrieb Roger Oberholtzer:
I did the suggested edit and built the initrd. After a reboot I still do not see a wireless device I only see this:
The edit didn't work for me either, neither did combining it with loading "sdhci_iproc" via modules-load.d. But running "modprobe -r sdhci_iproc" and then "modprobe sdhci_iproc" does at least fix the issue for the current boot. (you have to wait a few seconds for it to re-appear in "ip link" sometimes)
I hope someone comes up with a more permanent fix, and of course find the root cause, but for now it might be enough just to write a little script that executes after the System has booted.
The solution on the iMac was to blacklist these wireless drivers and then rebuild the initrd: blacklist b43 blacklist ssb blacklist bcma blacklist brcmsmac blacklist brcmfmac So perhaps a similar list for the Raspberry? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (5)
-
Andreas Färber -
Brüns, Stefan -
Freek de Kruijf -
Friedrich -
Roger Oberholtzer