Discussion about linux-rpi rebrand

[quark]

Not sure if I did it right but seems the kernel configs are identical, between -1 and the legacy -3 version. So maybe the naming itself is breaking something else in the system then.
edit: seems this issue happened before:
https://github.com/raspberrypi/linux/issues/503
way over what I can understand.
this was a strange mix of me just getting into Arch for ARM and testing it, the second day devs moving to new naming scheme and at the same time upstream kernel having this issue with gpu_mem.

[graysky]

@quark - I am confused. You referenced an issue that is over 7 years old. If you want to run on a Pi Zero, you need linux-rpi-legacy. I believe the Zero is armv6h.

$this->bbcode_second_pass_quote('', '
')$this->bbcode_second_pass_quote('', 'S')hould the compute modules also be listed here?

[graysky]

Thanks for the confirmation. To be clear, you tried linux-rpi (aarch64) and it didn't boot? Any boot logs to share? Perhaps I am missing a config option?

[checkmate]

Alright, did the reboot on my 3B+ with linux-rpi and my old custom cmdline and config. Works, including gpu_mem=16.
root@gw ~ $ uname -r
5.10.82-1-rpi-ARCH

@graysky
I checked linux-rpi and linux-rpi-legacy PKGBUILD: Both provide kernel7.img for arm7h. Is there any difference between the two?

Thanks!

[quark]

@graysky pretty strange of you to frame it like that. I clearly stated that this issue happened before, not that it's the same issue as back then. The issue with "gpu_mem=16" breaking boot happened before, not that it's the same issue now, as back then.
english is not my native language but I'm pretty sure it was clear.
The Zero works with the new kernel, just that if I add "gpu_mem=16" to the config.txt file it doesn't boot anymore, with the new legacy kernel. And the same thing happens now on Pi2 with the legacy kernel, doesn't work with gpu_mem=16 in config.txt.

[quark]

I see now that a new kernel update wants to update my legacy custom kernel built yersterday, on Pi2. I have 5.10.81-3 with a custom string, and the update is 5.10.82-1.
Shouldn't pacman not offer the new kernel update if it sees I have a custom string on mine?

$this->bbcode_second_pass_code('', '[quark@archpi ~]$ uname -r
5.10.81-3-rpi-legacy-ARCH_RT

[quark@archpi ~]$ sudo pacman -Syyu
:: Synchronizing package databases...
core 224.9 KiB 293 KiB/s 00:01 [####################################] 100%
extra 2.3 MiB 6.00 MiB/s 00:00 [####################################] 100%
community 5.5 MiB 8.00 MiB/s 00:01 [####################################] 100%
alarm 102.5 KiB 610 KiB/s 00:00 [####################################] 100%
aur 8.1 KiB 51.0 KiB/s 00:00 [####################################] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (2) linux-rpi-legacy-5.10.82-1 linux-rpi-legacy-headers-5.10.82-1

Total Installed Size: 80.72 MiB
Net Upgrade Size: -0.01 MiB

:: Proceed with installation? [Y/n]')

[principia]

I have now upgraded with the linux-rpi rebrand but I was surprised to find my pi broken because config.txt and cmdline.txt have been replaced by pacman. I had to revert to the saved versions to restore correct operation.

Specifically I had dtparam=i2c_arm=on and dtoverlay=pi3-disable-bt in my config.txt. Without these statements my connected devices do not work. Is this replacement expected pacman behaviour? I would have expected a warning - or did I miss something in the pacman output?

[graysky]

$this->bbcode_second_pass_quote('principia', 'I') have now upgraded with the linux-rpi rebrand but I was surprised to find my pi broken because config.txt and cmdline.txt have been replaced by pacman. I had to revert to the saved versions to restore correct operation.

Specifically I had dtparam=i2c_arm=on and dtoverlay=pi3-disable-bt in my config.txt. Without these statements my connected devices do not work. Is this replacement expected pacman behaviour? I would have expected a warning - or did I miss something in the pacman output?

[graysky]

@quark

Post the output of $this->bbcode_second_pass_code('', 'pacman -Qs linux-')