[SOLVED] eth0 missing after upgrading sarpi-firmware/hack of 17 feb 2021

mralk3 · 03-14-2021, 05:42 PM

Well, second thought, reinstall your raspberry pi 4 with sarpi using the Pi 4 installer or rootfs. While the file system would be fine transfering between the pi3 and pi4, the drivers and kernel would not be so much. Theres a reason Exaga makes separate packages.

Pigi_102 · 03-14-2021, 05:53 PM

That's rather strange: the bcmgenet is not compiled as module so I can't modprobe it.
The dtb seems to be there:

Code:

root@casa:~# fdtdump /boot/bcm2711-rpi-4-b.dtb | grep eth

**** fdtdump is a low-level debugging tool, not meant for general use.
**** If you want to decompile a dtb, you probably want
****     dtc -I dtb -O dts <filename>

        ethernet0 = "/scb/ethernet@7d580000";
        enable-method = "brcm,bcm2836-smp";
            enable-method = "spin-table";
            enable-method = "spin-table";
            enable-method = "spin-table";
            enable-method = "spin-table";
        ethernet@7d580000 {
                ethernet-phy@1 {
        eth_led0 = <0x0000002e 0x6c65642d 0x6d6f6465 0x733a3000>;
        eth_led1 = <0x0000002e 0x6c65642d 0x6d6f6465 0x733a3400>;
        genet = "/scb/ethernet@7d580000";
        genet_mdio = "/scb/ethernet@7d580000/mdio@e14";
        phy1 = "/scb/ethernet@7d580000/mdio@e14/ethernet-phy@1";

and also in /sys it seems to be seen:
root@casa:~# find /sys/ -name \*ethe\*
/sys/devices/platform/scb/fd580000.ethernet
/sys/firmware/devicetree/base/scb/ethernet@7d580000
/sys/firmware/devicetree/base/scb/ethernet@7d580000/mdio@e14/ethernet-phy@1
/sys/firmware/devicetree/base/aliases/ethernet0
/sys/bus/platform/devices/fd580000.ethernet

but nothing seems to make her appears.

In the thread you mentioned, @mralk3 , It seems that it was a driver problem.
Eventually I need to recompile the kernel with the bcmgenet as module, to see if I can get some more info.

Thanks for every bit of info.

alekow · 03-14-2021, 06:22 PM

Quote:

Originally Posted by Pigi_102

Hello all,
trying to fix a problem with wifi not working on my RPi4, as access point, on 21 February this year I've upgraded the two packages:

Code:

sarpi4-hacks-4.0-armv7l-1_slackcurrent_17Feb21_sp1
sarpi4-boot-firmware-armv7l-1_slackcurrent_17Feb21_sp1

I haven't rebooted as it was only firmware (...)
Pigi

The sarpi4-boot-firmware package is the boot firmware, not the kernel firmware. This contains the .dtb files which I think are kernel specific. You didn't upgrade the kernel and kernel-modules, maybe that is causing the issue?

mralk3 · 03-14-2021, 07:12 PM

Quote:

Originally Posted by alekow

The sarpi4-boot-firmware package is the boot firmware, not the kernel firmware. This contains the .dtb files which I think are kernel specific. You didn't upgrade the kernel and kernel-modules, maybe that is causing the issue?

DTB stands for device tree blob. You need the dtb and the firmware; the dtb just passes hardware information to the kernel so it knows how to use the firmware. At least that is how I understand it. So the slackware kernel-firmware AND sarpi-boot-firmware packages are both indeed necessary. Still, you need to update the kernel and modules to match the firmware packages. Exaga dates the sarpi packages as a way to match them up and so that we know when there is something to upgrade.

I won't repeat what Exaga has already stated on his project site:

Quote:

SARPi file descriptions
• sarpi4-installer_slackcurrent - Slackware ARM current installer disk image archive (.xz) for the Raspberry Pi 4 and Raspberry Pi 400. The installer was constructed using the official Slackware ARM current initial RAM disk and Raspberry Pi GitHub repository source. See the SARPi Slackware ARM Installation Guide [or the included README] for details on how to use this image for installing Slackware ARM on a Raspberry Pi 4 or Raspberry Pi 400.

• sarpi4-installer-boot_slackcurrent - Raspberry Pi 4 and Raspberry Pi 400 boot-firmware, Linux kernel, and initrd [RAM disk minirootfs containing the Slackware ARM installer] compressed file (.zip) archive. They are exactly the same files as those within the sarpi4-installer_slackcurrent disk image (.xz) archive. The difference being that these files can be extracted and easily managed individually, without having to write the entire image to a SD card.

• kernel_sarpi4-5.10.20 - Linux kernel package for the Raspberry Pi 4 and Raspberry Pi 400. This Linux kernel has been built specifically for the Raspberry Pi 4 (but also works on the Raspberry Pi 400) using the official source from the Raspberry Pi Foundation GitHub repository.

• kernel-headers-sarpi4-5.10.20 - kernel headers package for the Raspberry Pi 4 and Raspberry Pi 400. Kernel headers are the include files from kernel_sarpi-5.10.20 which are used by userspace programs and required when compiling most system software for Linux.

• kernel-modules-sarpi4-5.10.20 - kernel modules package for the Raspberry Pi 4 and Raspberry Pi 400. Kernel modules are pieces of object code that can be dynamically loaded into the Linux kernel to provide new functions. A lot of these modules provide support for devices such Wi-Fi adapters, sound devices, and other hardware. You can select which modules you want to load by editing /etc/rc.d/rc.modules.

• sarpi4-boot-firmware - Closed source boot-firmware blobs package for the Raspberry Pi 4 and Raspberry Pi 400. These blobs are essential for booting the Raspberry Pi device successfully. This boot-firmware was prepared specifically for the Raspberry Pi 4 and Raspberry Pi 400 devices using the official source from the Raspberry Pi Foundation GitHub repository.

• sarpi4-hacks-4.0 - Fixes/modifications for Slackware ARM on a Raspberry Pi 4 and Raspberry Pi 400. See the sarpi-hacks.README for further details.

• sarpi4-kernel-source-5.10.20 - Linux kernel source used for building the kernel for the SARPi4 installer and packages. This source includes the appurtenant kernel .config file used during the build process.

Exaga · 03-14-2021, 08:04 PM

Quote:

Originally Posted by Pigi_102

Hello all,
trying to fix a problem with wifi not working on my RPi4, as access point, on 21 February this year I've upgraded the two packages:

Code:

sarpi4-hacks-4.0-armv7l-1_slackcurrent_17Feb21_sp1
sarpi4-boot-firmware-armv7l-1_slackcurrent_17Feb21_sp1

Can you help shine some light on this ?
What should I check ?

Thanks in advance

Hi Pigi.

First of all you're dealing with SARPi batch 17Feb21 pkgs that were built during the "NVRAM-gate" fiasco where the brcmfmac43455 NVRAM files were updated due to new firmware being released. The issue was touched on in this post: https://www.linuxquestions.org/quest...ml#post6222303

I suspect you may have suffered the same predicament. You could try to fix it - i.e. changing whatever the "boardflags3=" value is in '/lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt' to 'boardflags3=0x48200100'... BUT it would benefit you greatly if you installed the latest SARPi batch pkgs instead - because these latest SARPi pkgs contain the new firmware and fixed NVRAM files - https://sarpi.fatdog.eu/index.php?p=rpi4getcurrent

ARM architectures are specific and you cannot take the sd card from a RPi3 which has a BCM2709 SoC and expect it to work perfectly on a RPi4 BCM2711 SoC. Something, somewhere, sometime, will break or give you trouble. I build the installers and pkgs natively, on the devices on which they are intended to run, to avoid any risk of incompatibility.

Pigi_102 · 03-15-2021, 04:40 AM

Hello Exaga.
Thanks for your advice.
At the moment ( and in the 17Feb21 ) there is no brcmfmac43455-sdio.raspberrypi,4-model-b.txt file.
I will upgrade with the latest hacks and firmware and let you know.

Is it enough to upgrade hacks and firmware or I need also kernel stuffs ( as per sarpi page ) ?

Thanks

Exaga · 03-15-2021, 04:46 AM

Quote:

Originally Posted by Pigi_102

Hello Exaga.
Thanks for your advice.
At the moment ( and in the 17Feb21 ) there is no brcmfmac43455-sdio.raspberrypi,4-model-b.txt file.
I will upgrade with the latest hacks and firmware and let you know.

Is it enough to upgrade hacks and firmware or I need also kernel stuffs ( as per sarpi page ) ?

Thanks for any feedback you can offer Pigi. All feedback is very welcome.

It's up to you how you proceed. You can just install sarpi-hacks and see if that works for you but it's prudent to upgrade the kernel/modules/boot-firmware as well, all at the same time. Then everything is from the same batch and it's much easier and less confusing to deal with, given recent events with firmware, etc.

hazel · 03-15-2021, 05:16 AM

I'm glad this thread got taken over by someone who understands raspberry pi's! I've never used one so I was floundering somewhat.

alekow · 03-15-2021, 05:30 AM

Quote:

Originally Posted by Pigi_102

Hello Exaga.
Thanks for your advice.
At the moment ( and in the 17Feb21 ) there is no brcmfmac43455-sdio.raspberrypi,4-model-b.txt file.
I will upgrade with the latest hacks and firmware and let you know.

Is it enough to upgrade hacks and firmware or I need also kernel stuffs ( as per sarpi page ) ?

Thanks

This file is part of kernel-firmware-20210211_f7915a0-noarch-1.txz which is part of slackwarearm not sarpi and can be found here.

Regards,
Alex

Exaga · 03-15-2021, 06:05 AM

Quote:

Originally Posted by alekow

This file is part of kernel-firmware-20210211_f7915a0-noarch-1.txz which is part of slackwarearm not sarpi and can be found here.

Regards,
Alex

Not sure why you think this file is not 'part of SARPi'. Or why you quote an official package from the Slackware ARM current-tree. Or where your information comes from.

NB: The SARPi installer supports the 'brcmfmac43455-sdio.raspberrypi,4-model-b.txt' file, as does sarpi-hacks pkgs.

Whatever MoZes includes within Slackware ARM is his prerogative. SARPi's only purpose is to follow and support the work of MoZes and promote the OS on the RPi devices.

[EDIT] the point being... the file in question is not a problem. I just checked it to completely waste my time and the settings it contains are correct.

alekow · 03-15-2021, 06:29 AM

Quote:

Originally Posted by Exaga

Not sure why you think this file is not 'part of SARPi'. Or why you quote an official package from the Slackware ARM current-tree. Or where your information comes from.

NB: The SARPi installer supports the 'brcmfmac43455-sdio.raspberrypi,4-model-b.txt' file, as does sarpi-hacks pkgs.

Whatever MoZes includes within Slackware ARM is his prerogative. SARPi's only purpose is to follow and support the work of MoZes and promote the OS on the RPi devices.

[EDIT] the point being... the file in question is not a problem. I just checked it to completely waste my time and the settings it contains are correct.

Hi Exaga,

As i understand SARPI is just the installer and it uses slackwarearm packages. Therefore if the file is not in place it would probably mean the above mentioned package is not installed?
What I meant is the file wouldn't be installed by any sarpi packages, that is all. No offence.

All the best,
Alex

Exaga · 03-15-2021, 08:02 AM

Quote:

Originally Posted by alekow

Hi Exaga,

As i understand SARPI is just the installer and it uses slackwarearm packages. Therefore if the file is not in place it would probably mean the above mentioned package is not installed?
What I meant is the file wouldn't be installed by any sarpi packages, that is all. No offence.

All the best,

No offence taken, but we don't need to complicate or hamper any progress by getting into the nitty-gritty about where certain file(s) comes from. Especially when this is a 2K blob settings file in a 140MiB Slackware ARM kernel-firmware*.txz pkg. If it's old (and from 17 Feb 2021) it definitely needs to be replaced. The current 'brcmfmac43455-sdio.raspberrypi,4-model-b.txt' file works as intended. Your advice when you wrote, "You didn't upgrade the kernel and kernel-modules, maybe that is causing the issue?" would be my assumption of what's missing. i.e. system pkgs are out of date, or firmware pkgs are not up-to-date, or the correct pkgs are not installed.

All I'm interested in is moving on from this latest brcmfmac/BCM debacle. It has annoyed and frustrated me personally in recent weeks because; there's a reason why MoZes doesn't have to support it by choice, and there's a reason why I must. NB: MoZes gets the much better end of the deal here! (i.e. it's closed-source, proprietary, bespoke, corporate license agreement, non-negotiable, might as well sell your worthless soul for a few pennies, etc. ...you get the point.)

Going by what Pigi has reported, his 'brcmfmac43455-sdio.raspberrypi,4-model-b.txt' file could come from the period [late-January to mid/late-February 2021] where the 'boardflags3=0x48200100' setting in the upstream version stopped the RPI4 onboard wireless card from operating within established parameters. This was rectified with a patch until the issue was fixed upstream in the main-tree, which happened around 24 Feb 2021. I started including these updates in SARPi installers and pkgs from 05 March 2021, once the dust had settled and I found the motivation to do it.

So, updating Slackware ARM current with all the latest official pkgs - if it hasn't already been done [WHY NOT?!?!

] - and installing the latest SARPi shizzle pgks, should fix this problem.

Exaga · 03-15-2021, 08:09 AM

Quote:

Originally Posted by hazel

I'm glad this thread got taken over by someone who understands raspberry pi's! I've never used one so I was floundering somewhat.

So am I and that's why I'm so relieved to see you here! I really haven't got a clue otherwise.

Pigi_102 · 03-15-2021, 01:06 PM

I have a ( at least one ) question, before proceeding : inside the two sarpi packages for hack and boot-firmware there is no such brcmfmac43455-sdio.raspberrypi,4-model-b.txt, nor I can find any reference of in in the install script of the two.

Code:

root@casa:~/sarpi# tar tf sarpi4-boot-firmware-armv7l-1_slackcurrent_06Mar21_sp1.txz | grep txt
boot/config.txt.new
boot/version-sarpi4-boot.txt
root@casa:~/sarpi# tar tf sarpi4-hacks-4.0-armv7l-1_slackcurrent_06Mar21_sp1.txz | grep txt
boot/version-sarpi4-hacks.txt
lib/firmware/brcm/brcmfmac43430-sdio.txt
lib/firmware/brcm/brcmfmac43436-sdio.txt
lib/firmware/brcm/brcmfmac43455-sdio.txt
lib/firmware/brcm/brcmfmac43456-sdio.txt
usr/share/doc/bluez-firmware/BCM-LEGAL.txt

If the cause of my problem is somehow tied to this ( missing ) file, how it comes that I don't find it ?

Unfortunally, until tomorrow evening I cannot stop my Pi as I need internet for a certification exam and cannot spend all the night recovering

but I will do this tomorrow, when the exam is gone.

In the meantime I'm searching through packages but without change.

Why I didn't upgraded to current ? That's a subject for a new thread, but if you are in line with -current x86, there are too many changes I cannot fight with ( ATM )

Pigi

EDIT: in the dmesg from raspbian there is the similar error messages:

Code:

brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt failed with error -2

Exaga · 03-15-2021, 01:44 PM

Quote:

Originally Posted by Pigi_102

I have a ( at least one ) question, before proceeding : inside the two sarpi packages for hack and boot-firmware there is no such brcmfmac43455-sdio.raspberrypi,4-model-b.txt, nor I can find any reference of in in the install script of the two.

If the cause of my problem is somehow tied to this ( missing ) file, how it comes that I don't find it ?

[EDIT] you don't find it (I'm guessing) because your Slackware ARM pkgs are from before the fixed file was included in the mainline kernel. Therefore this file didn't exist at that time. I have the file you need...

I've attached the latest 'brcmfmac43455-sdio.raspberrypi,4-model-b.txt' file to this post Pigi. This may be easier and quicker to test with than asking you to 'slackpkg upgrade-all '.

[EDIT #2] There's two settings in this new file that may be different or missing from your existing file...

Code:

boardflags3=0x44200100
btc_params50=0x972c

Before you replace the existing file could you tell me what the value of boardflags3="" is within it please?