Hi Peter, > Peter Robinson <pbrobinson@xxxxxxxxx> hat am 22. Dezember 2018 um 03:47 geschrieben: > > > > > Tested against Fedora 28 aarch64 on RPi3. Unfortunately I have negative > > > feedback. > > > > > > I was happily running kernel-4.19.4-200.fc28.aarch64 with wifi before > > > the update. But after the update and reboot, wifi disappeared. Moreover, > > > reboot back to kernel-4.19.4-200.fc28.aarch64 also did not help. > > > > i assume you have a 3 B not a B+. > > > > Can you provide a complete dmesg? > > > > > > > > > > > [root@rpi3 ~]# ip a > > > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN > > > group default qlen 1000 > > > 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 fq_codel state > > > UP group default qlen 1000 > > > link/ether b8:27:eb:a2:a9:f1 brd ff:ff:ff:ff:ff:ff > > > inet 192.168.129.8/25 brd 192.168.129.127 scope global dynamic > > > noprefixroute eth0 > > > valid_lft 3563sec preferred_lft 3563sec > > > inet6 fe80::f6b0:a847:88c7:1fe7/64 scope link noprefixroute > > > valid_lft forever preferred_lft forever > > > [root@rpi3 ~]# nmcli device wifi list > > > [root@rpi3 ~]# dmesg | egrep -i "brcm|firmware" > > > [ 4.408297] raspberrypi-firmware soc:firmware: Attached to firmware > > > from 2018-09-21 15:44 > > > [ 21.876808] platform regulatory.0: Direct firmware load for > > > regulatory.db failed with error -2 > > > [ 22.058065] brcmfmac: probe of mmc1:0001:1 failed with error -110 > > > [ 22.100755] brcmfmac: probe of mmc1:0001:2 failed with error -110 > > > [ 22.101025] usbcore: registered new interface driver brcmfmac > > > [ 32.708983] bluetooth hci0: Direct firmware load for > > > brcm/BCM43430A1.hcd failed with error -2 > > > [ 32.726479] Bluetooth: hci0: BCM: Patch brcm/BCM43430A1.hcd not found > > > > Interesting the wifi chip is found, so the devicetree bugfix is working. > > So this seems to be a different a issue. > > I've found on a lot of devices if you just reboot with the fix it > doesn't always work, a full unplug reset of the power generally makes > it work again. the mentioned fix is correct, but it is only half of the work. There is an issue in the sdhci driver which leads to an unwanted reset of the wifi chip. Please try this little x-mas present: https://marc.info/?l=linux-arm-kernel&m=154559884601004 Regards Stefan _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
