Discussion about linux-rpi rebrand

This forum is for discussion about general software issues.

Re: Gripes about linux-rpi rebrand

Postby principia » Tue Nov 30, 2021 1:59 pm

Thanks for pointing me to the announcement - sorry I missed the last few lines. Good advice on pacman for the future, thanks ;)
principia
 
Posts: 3
Joined: Tue Nov 30, 2021 1:25 pm

Re: Gripes about linux-rpi rebrand

Postby quark » Tue Nov 30, 2021 3:53 pm

I've recompiled the newest kernel earlier, and installed it but anyway:

$this->bbcode_second_pass_code('', '[quark@archpi ~]$ pacman -Qs linux-
local/linux-api-headers 5.12.3-1
Kernel headers sanitized for use in userspace
local/linux-firmware 20211027.1d00989-1
Firmware files for Linux
local/linux-rpi-legacy 5.10.82-1
RPi Foundation patched Linux kernel and modules - RPi 1/2/Zero/Zero W
local/linux-rpi-legacy-headers 5.10.82-1
RPi Foundation header and scripts for building modules for Linux kernel
- RPi 1/2/Zero/Zero W
local/python-linux-procfs 0.6.3-1
Linux /proc abstraction classes for python
local/util-linux-libs 2.37.2-1
util-linux runtime libraries')
quark
 
Posts: 59
Joined: Thu Nov 25, 2021 8:26 am

Re: Gripes about linux-rpi rebrand

Postby donatom » Tue Nov 30, 2021 5:01 pm

I am running Archlinux-ARM and Raspberry pi 4 off of a usb drive. A couple of days ago I upgraded my system with pacman -Syu and was greeted with the question of whether to upgrade the kernel to linux-rpi which I answered affirmatively. Upon reboot my system went into an emergency shell stating that device /dev/mmcblk0p2 could not be found.

Somehow the update changed my /boot/cmdline.txt to one made for devices created for a SD card.

After a few hours of research I determined that I needed to change the /boot/cmdline.txt to reflect the UUID number for my root partition (you can of course find the UUID number by running the command "# blkid /dev/sdx - x being the letter of the device running archlinux-arm). I also checked my /etc/fstab file to make sure the UUID #'s for the boot and the root partition were correct.

This is what my /boot/cmdline.txt file looks like with change (UUID): $this->bbcode_second_pass_code('', 'root=UUID=058b46df-7058-467b-86c4-8d570e480a66 rw rootwait console=serial0,115200 console=tty1 selinux=0 plymouth.enable=0 smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 kgdboc=serial0,1152
00
')

After doing the above, my system booted up without a hiccup.

This is just a heads-up for those who run archlinux-arm on a usb drive and who have a similar experience when updating to linux-rpi.
donatom
 
Posts: 1
Joined: Tue Nov 30, 2021 4:18 pm

Re: Gripes about linux-rpi rebrand

Postby graysky » Tue Nov 30, 2021 6:58 pm

$this->bbcode_second_pass_quote('quark', '
')$this->bbcode_second_pass_code('', '[quark@archpi ~]$ pacman -Qs linux-
...
local/linux-rpi-legacy 5.10.82-1
RPi Foundation patched Linux kernel and modules - RPi 1/2/Zero/Zero W
local/linux-rpi-legacy-headers 5.10.82-1
RPi Foundation header and scripts for building modules for Linux kernel
- RPi 1/2/Zero/Zero W
')


If that is your custom compiled kernel, you did not change $pkgbase to your own which is why pacman wants to pull down the repo version.
graysky
Developer
 
Posts: 1728
Joined: Sun Jun 26, 2011 6:56 am
Location: /run/user/1000

Re: Gripes about linux-rpi rebrand

Postby quark » Tue Nov 30, 2021 7:14 pm

Indeed I completely forgot about it. Thanks!
I'll do it next time I compile it.
quark
 
Posts: 59
Joined: Thu Nov 25, 2021 8:26 am

Re: Gripes about linux-rpi rebrand

Postby pudge » Wed Dec 01, 2021 1:38 am

A quick question.

Right now if one uses the the Raspberry Pi installation tab, at the bottom of the instructions it says

AArch64 Installation
Follow the above instructions, substituting with the following tarball:
http://os.archlinuxarm.org/os/ArchLinux ... est.tar.gz

Which installs the linux-aarch64 kernel 5.15.1-1
Is there any plans in the future to offer a aarch64 tarball that will install the linux-rpi kernel 5.10.82-2?

Thank you.

Pudge
pudge
 
Posts: 24
Joined: Thu Mar 29, 2018 5:38 pm

Re: Gripes about linux-rpi rebrand

Postby quark » Thu Dec 02, 2021 8:40 pm

Isn't the linux-rpi kernel a 32bit one?
quark
 
Posts: 59
Joined: Thu Nov 25, 2021 8:26 am

Re: Gripes about linux-rpi rebrand

Postby graysky » Thu Dec 02, 2021 8:45 pm

$this->bbcode_second_pass_quote('quark', 'I')sn't the linux-rpi kernel a 32bit one?


Available in both armv7h and aarch64.
graysky
Developer
 
Posts: 1728
Joined: Sun Jun 26, 2011 6:56 am
Location: /run/user/1000

Re: Gripes about linux-rpi rebrand

Postby skunark » Sun Dec 05, 2021 1:44 am

$this->bbcode_second_pass_quote('', 'T')hanks 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?


One option missing for both armv7h and aarch64 is support for wireless.

I still haven't tried to install aarch64 on a CM4, but i did manage to change to aarch64 based on wiki.archlinux.org details. Seems to be working fine other than no wireless still.
$this->bbcode_second_pass_code('', 'Model : Raspberry Pi Compute Module 4 Rev 1.0
Linux 5.10.82-4-rpi-ARCH #1 SMP PREEMPT Fri Dec 3 15:11:24 UTC 2021 aarch64 unknown unknown GNU/Linux')

I do have one CM4 that i need to install an OS, hopefully I can do that soon and report back.
skunark
 
Posts: 16
Joined: Fri Apr 30, 2021 12:36 am
Top

Re: Gripes about linux-rpi rebrand

Postby keithspg » Sat Dec 11, 2021 11:23 pm

My gripes are:
1) gpu_mem=16 causes the armv6 kernel to not boot
2) For some reason the armv7 kernel on the PiZero2W and the armv6 kernel on a PiZeroW will not reboot. It will power cycle and boot but when reboot is issued from the CLI, it never reboots.
3) The onboard audio is not functional any more for the PiB1. When ‘dtparam=audio=on’ is set in the config.txt, nothing happens.

This is with kernel 5.10.83-1-rpi-legacy-ARCH on the v6 ZeroW and 5.10.83-1-rpi-ARCH on the v7 Zero2W

Keith
keithspg
 
Posts: 221
Joined: Mon Feb 23, 2015 4:14 pm

PreviousNext

Return to General

Who is online

Users browsing this forum: No registered users and 6 guests