arm June 2020

arm@lists.fedoraproject.org

12 participants
14 discussions

Status of armhfp grubs2-efi on top of Uboot
by Mark Verlinde 02 Nov '20

02 Nov '20

Hi, A while ago (around the freeze of FC29) grub2-efi on top of Uboot was proposed as the (potentially) default setup for armhfp too. Unfortunately (IMHO) it did not materialize and I'm searching for the game-breaker. On buggzilla found a few hints, " we have at least a grub2 <-> kernel bug" (1) among them, they did not make the holdup clear to me. My investigation so-far: * It works pretty good with a close to upstream build grub, not with the default gub2 packages. Which makes me believe loading an arm32 kernel as an Portable Executable instead of grub's LoadImage() and StartImage() services may be a game-stopper. NOTE : I understand this is necessary for chain loading efi stubs for secure-boot. IMO this is not the pursued goal here. * Since kernel patch "efi: libstub/arm: account for firmware reserved memory at the base of RAM" (2) it works on RPI's too (given a "custom" build grub2) All feedback is appreciated, grtz Mark 1) https://bugzilla.redhat.com/show_bug.cgi?id=1602948 2) https://patchwork.kernel.org/patch/11189097/

3 4

The server images are not working with Fedora 31
by Peter Hjalmarsson 04 Aug '20

04 Aug '20

Hi, Just wanted to point out that due to U-Boot not supporting XFS, and Fedora Server has moved to a XFS /boot, the current images as https://dl.fedoraproject.org/pub/fedora/linux/releases/31/Server/aarch64/im… does not boot on any system using U-Boot, like for example the raspberry pi. Best Regards, Peter Hjalmarsson

3 5

CMA on raspberry pi 4
by Thomas H.P. Andersen 04 Aug '20

04 Aug '20

Hi, I have looked into the CMA setting issue a bit. This is what I have found so far. The rpi4 needs CMA to be in ZONE_DMA (lower 1GB of memory) as this is the only area that the peripherals on the rpi4 can address. The DT sets the allowed range to allocate the CMA from ( arch/arm/boot/dts/bcm2711.dtsi#L869 <https://github.com/torvalds/linux/blob/master/arch/arm/boot/dts/bcm2711.dts…>), but it seems to not work here. What does work is instead to set the offset manually. I replaced "cma=256MB" with "cma=256M@704M" and then it boots. Note that it has to be 256M instead of 256MB. Removing the cma option on the command line was known as a workaround. Without that we would fall back to the build config of 64MB cma which was located at offset 0x38000000. This left 64MB at the end of ZONE_DMA, and I chose offset 704M so that those 64MB would still be free. Not sure if that is needed or not. The crashkernel needs to be in ZONE_DMA as well but it seems to be set to 0 size. I have tested on 5.7 rc2 from rawhide. This probably belongs in a bug report. What would be the correct place to file that? From what I can tell upstream has been tested with cma settings without problems (as long as the requested CMA size can fit in ZONE_DMA). From that it seems like fedora-specific issue. Not sure though. Cheers, Thomas

4 17

Workstation on Pinebook Pro
by Ben Cotton 09 Jul '20

09 Jul '20

Hi ARM friends, I've been trying without success to get the F32 Workstation RC1.6 (tomorrow's release) installed on my Pinebook Pro. If anyone here has done it, do you have instructions written up somewhere? One layer of trouble I've had is that the image apparently doesn't have the uboot files. The arm-image-installer script looks for them, AFAICT, in the image, so I called the installer with the PREFIX set to '', which was enough to get the install script to work, but the PBP doesn't boot from the SD card. I also used the 'rock64' target, which seems like it should be the right answer and not 'pinebook' (since the Pinebook uses a different board from the Pinebook Pro). But maybe that's part of my problem, too? -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis

5 9

Fedora 32 aarch64 virt-install MMC kernel drivers missing from initramfs
by Felix Geschwindner 27 Jun '20

27 Jun '20

Hey ARM guys, I'm trying to build a custom Fedora32 aarch64 image for the RPI 3/4. I'm using the livemedia-creator (part of lorax) in QEMU mode on an RPI 4 which is running the minimal image from here: https://kojipkgs.fedoraproject.org/compose/32/latest-Fedora-32/compose/Spin… The install is going great and successfully completes but when DDing the image onto an SDCARD and booting a PI 3/4 with it, it hangs while it is discovering the root drive. After a bit of investigating DMESG, it turns out that initramfs never loads any drivers neccessary for the SDCARD to be discovered (mmc_block.ko, sdhci-iproc.ko, sdhci-pltfm.ko, sdhci.ko) and thus can't boot the final root filesystem. I can easily fix the problem manually by copying an initramfs from the working minimal image but I'd like to understand why dracut is generating the initramfs during kickstart without the SDHCI modules. After that fix I can boot the new image and when I run dracut from that system it generates the correct initramfs. My guess right now is that QEMU abstracts the storage system and dracut (or even depmod) doesn't see a need to include those kernel driver modules. Once the system is actually booted with the SDCARD hardware present it correctly includes those modules. This can be verified by manually running dracut -vvv in the %post section during kickstart and the output shows that it doesn't include any of the mentioned modules. I'm looking for a method to apply within the %post section of kickstart that lets me go around that issue. Looking at the anaconda logs, I can see that depmod is already running wit the -a flag which instructs it to include ALL modules so go figure. Thanks!

1 0

How Will Apple Custom-Silicon Impact Fedora on Mac?
by Geoffrey Marr 27 Jun '20

27 Jun '20

Perhaps it's too early to speculate, but with the recent release of information that Apple will be transitioning from Intel-based CPUs to their own, custom ARM chips, I wonder if anyone deeper in the know (pbrobinson, pwhalen, others?) could speak to the continuing of Fedora on the Mac platform? Geoff Marr IRC: coremodule

3 2

Jetson-tk1 regulator and initramfs
by Nicolas Chauvet 26 Jun '20

26 Jun '20

HI, FYI, I've found an issue with the current kernel 5.6.x (maybe earlier) the as3722_regulator module isn't added by dracut in hostonly mode (it is added as all others regulators) I need to add this: cat >/etc/dracut.conf.d/jetson-tk1.conf<<EOF add_drivers+=" as3722-regulator " EOF This prevents the board to mount the rootfs in mmc or sda when the initramfs is in host-only mode. I've reported the issue to dracut upstream at https://github.com/dracutdevs/dracut/issues/847 Now I wonder if other boards are affected by such regulators tweak and if a common solution can be found ? Thanks for your advice. -- - Nicolas (kwizart)

2 1

Re: Banana Pi-R1 - kernel 5.6.0 and later broken - b43 DSA
by Peter Robinson 26 Jun '20

26 Jun '20

On Fri, Jun 26, 2020 at 5:42 AM Florian Fainelli <f.fainelli(a)gmail.com> wrote: > > > > On 6/25/2020 4:23 PM, Peter Robinson wrote: > >> I'm having troubles with the Banana Pi-R1 router with newer kernels. No > >> config changes, config works well since a lot of lernel updates ... > >> Banana Pi-R1 is configured via systemd-networkd and uses the DSA > >> (Distributed Switch Architecture) with b53 switch. No visible difference > >> in interfaces, vlan config, bridge config, etc. Looks like actual > >> configuration in the switch in the hardware is broken. > >> > >> # OK: Last good known version (booting that version is also ok) > >> Linux bpi 5.5.18-200.fc31.armv7hl #1 SMP Fri Apr 17 17:25:00 UTC 2020 > >> armv7l armv7l armv7l GNU/Linux > >> > >> # NOK: no network > >> Linux bpi 5.6.8-200.fc31.armv7hl #1 SMP Wed Apr 29 19:05:06 UTC 2020 > >> armv7l armv7l armv7l GNU/Linux > >> > >> # NOK: no network > >> Linux bpi 5.6.0-300.fc32.armv7hl #1 SMP Mon Mar 30 16:37:50 UTC 2020 > >> armv7l armv7l armv7l GNU/Linux > >> > >> # NOK: no network > >> Linux bpi 5.6.19-200.fc31.armv7hl #1 SMP Wed Jun 17 17:10:22 UTC 2020 > >> armv7l armv7l armv7l GNU/Linux > >> > >> # NOK: no network > >> Linux bpi 5.7.4-200.fc32.armv7hl #1 SMP Fri Jun 19 00:52:22 UTC 2020 > >> armv7l armv7l armv7l GNU/Linux > >> > >> > >> Saw that there were a lot of changes in the near past in the b53 driver: > >> > >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/driv… > > > > So from your notes above it looks like something regressed between the > > 5.5.x series and the 5.6.0 release? If so I'm not sure what the > > context of the changed in 5.8 are here. If there's more changes to the > > driver in 5.8 dev cycle have you tried one of the Fedora rawhide 5.8 > > rc1 or rc2 kernel builds to see if that resolves it? > > See my response to Gerhard, there are changes expected to how the > network configuration should be done after: It appears your response was off list, and he had follow up questions and I don't see a response from you. > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… > > > > > Failing that looking for the change in the 5.6 cycle would likely be > > the better bet so we can work out what broke it and report it to the > > upstream driver maintainer. Have you searched to see if others are > > seeing a similar issue or have reported a similar issue upstream? > > > > Gerhard is doing exactly this with his email. No, I asked if he'd searched elsewhere to see if others are having problems, like other distros etc.

1 0

Banana Pi-R1 - kernel 5.6.0 and later broken - b43 DSA
by Gerhard Wiesinger 25 Jun '20

25 Jun '20

Hello, I'm having troubles with the Banana Pi-R1 router with newer kernels. No config changes, config works well since a lot of lernel updates ... Banana Pi-R1 is configured via systemd-networkd and uses the DSA (Distributed Switch Architecture) with b53 switch. No visible difference in interfaces, vlan config, bridge config, etc. Looks like actual configuration in the switch in the hardware is broken. # OK: Last good known version (booting that version is also ok) Linux bpi 5.5.18-200.fc31.armv7hl #1 SMP Fri Apr 17 17:25:00 UTC 2020 armv7l armv7l armv7l GNU/Linux # NOK: no network Linux bpi 5.6.8-200.fc31.armv7hl #1 SMP Wed Apr 29 19:05:06 UTC 2020 armv7l armv7l armv7l GNU/Linux # NOK: no network Linux bpi 5.6.0-300.fc32.armv7hl #1 SMP Mon Mar 30 16:37:50 UTC 2020 armv7l armv7l armv7l GNU/Linux # NOK: no network Linux bpi 5.6.19-200.fc31.armv7hl #1 SMP Wed Jun 17 17:10:22 UTC 2020 armv7l armv7l armv7l GNU/Linux # NOK: no network Linux bpi 5.7.4-200.fc32.armv7hl #1 SMP Fri Jun 19 00:52:22 UTC 2020 armv7l armv7l armv7l GNU/Linux Saw that there were a lot of changes in the near past in the b53 driver: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/driv… Any ideas? Thnx. Ciao, Gerhard

2 1

Re: Banana Pi-R1 - kernel 5.6.0 and later broken - b43 DSA
by Gerhard Wiesinger 22 Jun '20

22 Jun '20

Hello Florian, On 20.06.2020 21:13, Florian Fainelli wrote: > Hi, > > On 6/20/2020 10:39 AM, Gerhard Wiesinger wrote: > Can you share your network configuration again with me? Find the network config below. >> # OK: Last good known version (booting that version is also ok) >> Linux bpi 5.5.18-200.fc31.armv7hl #1 SMP Fri Apr 17 17:25:00 UTC 2020 >> armv7l armv7l armv7l GNU/Linux > OK, I suspect what has changed is this commit: > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… > > which, if I remember your configuration correctly means that you now > have proper DSA interfaces and so all of the wan, lan1-lan4 interfaces > can now run a proper networking stack unlike before where you had to do > this via the DSA master network device (eth0). This also means that you > should run your DHCP server/client on the bridge master network device now. Yes, config should be a proper DSA config, see also below. IP config is only on brlan and brwan. Do the changes need a config change? e.g. net: dsa: b53: Ensure the default VID is untagged https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/d… Thnx. Ciao, Gerhard Config: brctl show bridge name bridge id STP enabled interfaces brlan 8000.AAAAAAAAAAAA no lan.101 brlansw 8000.BBBBBBBBBBBB no lan1 lan2 lan3 lan4 brwan 8000.CCCCCCCCCCCC no wan.102 brwansw 8000.DDDDDDDDDDDD no wan ================================================================================ = /etc/systemd/network/30-autogen-eth0.network ================================================================================ [Match] Name=eth0 [Network] VLAN=lan.101 VLAN=wan.102 ================================================================================ = /etc/systemd/network/40-autogen-lan.101.netdev ================================================================================ [NetDev] Name=lan.101 Kind=vlan [VLAN] Id=101 ================================================================================ = /etc/systemd/network/40-autogen-wan.102.netdev ================================================================================ [NetDev] Name=wan.102 Kind=vlan [VLAN] Id=102 ================================================================================ = /etc/systemd/network/50-autogen-brlan.netdev ================================================================================ [NetDev] Name=brlan Kind=bridge [Bridge] DefaultPVID=none VLANFiltering=false STP=false ================================================================================ = /etc/systemd/network/50-autogen-brlansw.netdev ================================================================================ [NetDev] Name=brlansw Kind=bridge [Bridge] DefaultPVID=none VLANFiltering=true STP=false ================================================================================ = /etc/systemd/network/50-autogen-brwan.netdev ================================================================================ [NetDev] Name=brwan Kind=bridge [Bridge] DefaultPVID=none VLANFiltering=false STP=false ================================================================================ = /etc/systemd/network/50-autogen-brwansw.netdev ================================================================================ [NetDev] Name=brwansw Kind=bridge [Bridge] DefaultPVID=none VLANFiltering=true STP=false ================================================================================ = /etc/systemd/network/60-autogen-brlan-lan.101.network ================================================================================ [Match] Name=lan.101 [Network] Bridge=brlan ================================================================================ = /etc/systemd/network/60-autogen-brlansw-lan1.network ================================================================================ [Match] Name=lan1 [Network] Bridge=brlansw [BridgeVLAN] VLAN=101 EgressUntagged=101 PVID=101 ================================================================================ = /etc/systemd/network/60-autogen-brlansw-lan2.network ================================================================================ [Match] Name=lan2 [Network] Bridge=brlansw [BridgeVLAN] VLAN=101 EgressUntagged=101 PVID=101 ================================================================================ = /etc/systemd/network/60-autogen-brlansw-lan3.network ================================================================================ [Match] Name=lan3 [Network] Bridge=brlansw [BridgeVLAN] VLAN=101 EgressUntagged=101 PVID=101 ================================================================================ = /etc/systemd/network/60-autogen-brlansw-lan4.network ================================================================================ [Match] Name=lan4 [Network] Bridge=brlansw [BridgeVLAN] VLAN=101 EgressUntagged=101 PVID=101 ================================================================================ = /etc/systemd/network/60-autogen-brwansw-wan.102.network ================================================================================ [Match] Name=wan.102 [Network] Bridge=brwansw ================================================================================ = /etc/systemd/network/60-autogen-brwansw-wan.network ================================================================================ [Match] Name=wan [Network] Bridge=brwansw [BridgeVLAN] VLAN=102 EgressUntagged=102 PVID=102 ================================================================================ = /etc/systemd/network/60-autogen-brwan-wan.102.network ================================================================================ [Match] Name=wan.102 [Network] Bridge=brwan ================================================================================ = /etc/systemd/network/61-autogen-brlan.network ================================================================================ [Match] Name=brlan [Network] Address=192.168.39.2/24 Gateway=192.168.39.1 DNS=192.168.39.1 Domains=mydomain ================================================================================ = /etc/systemd/network/61-autogen-brwan.network ================================================================================ [Match] Name=brwan [Network] Address=192.168.1.1/24

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm June 2020