Linux kernel 6.x not vailable for Rocky on ARM (RPi4)?

Rocky Linux General
41

@toracat works like a charm on my generic aarch64 image :slight_smile:

[root@vcr ~]# cat /sys/firmware/devicetree/base/model
Raspberry Pi 4 Model B


[root@vcr ~]# uname -a
Linux vcr 6.1.0-1.bcat2.el9.elrepo.aarch64 #1 SMP PREEMPT_DYNAMIC Sat Dec 17 17:24:07 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux
1 Like
42

@Sherif

That’s great news !!

1 Like
43

I was about to go ahead and test this, but when I access the RPi via SSH I login with the user rocky, but this user doesn’t have sudo privileges, how are you able to do anything that requires root access on the host?

44

Using the ELRepo Project’s time-machine, the kernel-ml-6.1.1-1.el9.elrepo.aarch64 package set (to be released on Wednesday) is currently being built.

The configuration options (as tested by Sherif, above, using the .bcat2 kernel) are now incorporated by default.

2 Likes
45

I hope @Sherif can help you.

1 Like
46

it is all written in the readme :slight_smile: https://rockyrepos.gnulab.org/images/README.txt ,

no sudo, just su and password is rocky

1 Like
47

Testing more boards and might open a feature / bug request in mantis early next year :slight_smile:

1 Like
48

I think I managed to install kernel 6 successfully according to the instructions given above:

[rocky@camilladsp ~]$ uname -r
6.1.0-1.bcat2.el9.elrepo.aarch64

I also saw the grub menu at boot, so things are looking quite as promised :slight_smile:

@Sherif I think the readme is incorrect, I was trying to SSH into the host with root using the password rocky as the readme suggests, but that doesn’t work. Using su works though.

Since @burakkucat mentioned that these changes will be rolled out to elrepo tomorrow, I’m thinking I should just wait for that, then clean install the generic image from rockyrepos.gnulab.org along with the kernel release from elrepo? Is this still the recommended method after the elrepo release? I think I installed some needless stuff while tinkering with this since I’m not used to dnf and importing external repos, so I think a clean install would be nice.

2 Likes
49

RFEs are always welcome. :cat:

1 Like
50

@alt, you are right, there is no root access allowed over SSH in RHEL / Rocky 9. the read me should say no SSH access “fixed” :slight_smile:

I don’t add any “extra” repos to the genericaarch64 images, so recommended way would be:

  • install the generic image as you did " this will be baked with kernel-5.15 that is based on @pgcrog works
  • Then you have one of two options:
    ** install Gnulabrepos and stay with kernel-5.15 or whever kernels we will maintain after that " usually will be LTS, and pkgs already started being pushed into rocky official SIG/Kernel repos , so soon you won’t need to use gnulab at all :slight_smile:
    ** install elrepo repos and use the kernel-ml

P.S

  • The official rockyRPI images uses RPI foundation kernel which is patched to have support for RPI hardware, those patches are not in kernel mainline sources yet as far as I know
  • The rockyRPI official image doesn’t have grub, I don’t think any official RPI images of any distro does as long as they are using RPI kernel, the kernel is being booted via config.txt as far as I recall
  • The genericaarch64 image is kinda of beta stage :slight_smile: so please keep that in mind, however it uses the very same repos for aarch64 + the LTS kernel which is based on RHEL/Fedora kernel with configurations enabled for extra hardware

if there is any bugs, please feel free to open them via https://bugs.rockylinux.org

51

The el9 installer offers two (interactive) options about root:

  1. Is root “disabled” – whatever that means
  2. Can root ssh with password

The default, if root password is supplied, is that root is enabled but ssh as root requires keypair (and interactive install does not install authorized_keys).

If one selects “allow password auth” for the second option, then root “has SSH access”.

1 Like
52

I meant in the default installation and my kickstart only allow root SSH via keys as you mentioned :slight_smile: thanks for the clarification :slight_smile:

53

I have kickstart mainly to drop in the keys. (Ansible does most afterwards.)

The el9 sshd default is: PermitRootLogin prohibit-password
(Up to el8 the default was “yes”.)

If you do tick the “allow password” in installer, then installer creates file:
/etc/ssh/sshd_config.d/01-permitrootlogin.conf
that has PermitRootLogin yes

A follofup task, just in case I had to initially allow pw-login:

  - name: Limit root ssh to keys
    file:
      path:  /etc/ssh/sshd_config.d/01-permitrootlogin.conf
      state: absent
    notify: Restart sshd
54

I’ve reinstalled the image, but when trying to add ELRepo I’m getting the below errors. Do I need to do something specific for this to work on RPi?

[root@localhost rocky]# rpm --import https://www.elrepo.org/RPM-GPG-KEY-elrepo.org
[root@localhost rocky]# dnf install https://www.elrepo.org/elrepo-release-9.el9.elrepo.noarch.rpm
ELRepo.org Community Enterprise Linux Repository - el9                                                                                                                                                2.2  B/s | 196  B     01:28
Errors during downloading metadata for repository 'elrepo':
  - Status code: 404 for http://mirrors.colocall.net/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 62.149.2.66)
  - Status code: 404 for http://mirrors.xservers.ro/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 89.38.249.150)
  - Status code: 404 for http://ftp.cc.uoc.gr/mirrors/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 147.52.159.12)
  - Status code: 404 for http://lon.mirror.rackspace.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 94.236.26.35)
  - Status code: 404 for http://mirrors.thzhost.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 103.246.18.122)
  - Status code: 404 for http://mirrors.coreix.net/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 85.13.241.50)
  - Status code: 404 for http://repos.mia.lax-noc.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 173.44.32.10)
  - Status code: 404 for http://ftp.osuosl.org/pub/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 64.50.233.100)
  - Status code: 404 for http://ord.mirror.rackspace.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 166.78.229.131)
  - Status code: 404 for http://dfw.mirror.rackspace.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 74.205.112.120)
  - Status code: 404 for http://repos.ord.lax-noc.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 104.129.31.245)
  - Status code: 404 for http://ftp-srv2.kddi-research.jp/Linux/RPMS/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 202.255.47.226)
  - Status code: 404 for http://ftp.yz.yamagata-u.ac.jp/pub/linux/RPMS/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 133.24.248.19)
  - Status code: 404 for http://ftp.nluug.nl/os/Linux/distr/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 145.220.21.40)
  - Status code: 404 for http://mirror.uta.edu.ec/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 192.188.46.165)
  - Status code: 404 for http://elrepo.mirror.angkasa.id/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 103.29.148.124)
  - Status code: 404 for http://mirror.cedia.org.ec/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 201.159.221.67)
  - Status code: 404 for http://mirrors.mivocloud.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 185.163.44.44)
  - Status code: 404 for http://ftp.ines.lug.ro/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 89.149.59.178)
  - Curl error (6): Couldn't resolve host name for http://ftp.utexas.edu/elrepo/elrepo/el9/aarch64/repodata/repomd.xml [Could not resolve host: ftp.utexas.edu]
  - Status code: 404 for http://repos.dfw.lax-noc.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 96.44.142.5)
  - Status code: 404 for http://mirror.pit.teraswitch.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 204.16.246.250)
  - Status code: 404 for http://muug.ca/mirror/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 208.81.1.244)
  - Curl error (28): Timeout was reached for http://mirrors.leadhosts.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml [Connection timed out after 30000 milliseconds]
  - Status code: 404 for http://syd.mirror.rackspace.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 119.9.32.73)
  - Status code: 404 for http://linux-mirrors.fnal.gov/linux/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 131.225.105.75)
  - Status code: 404 for http://mirror-hk.koddos.net/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 103.109.101.20)
  - Status code: 404 for http://iad.mirror.rackspace.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 72.4.120.219)
  - Status code: 404 for https://elrepo.org/linux/elrepo/el9/aarch64/repodata/repomd.xml (IP: 69.195.83.87)
  - Curl error (47): Number of redirects hit maximum amount for http://elrepo.0m3n.net/elrepo/el9/aarch64/repodata/1 [Maximum (6) redirects followed]
  - Status code: 404 for http://fedora.is/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 176.57.227.242)
  - Status code: 404 for http://ftp.icm.edu.pl/pub/Linux/distributions/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 193.219.28.2)
  - Status code: 404 for https://mirrors.tuna.tsinghua.edu.cn/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 101.6.15.130)
  - Status code: 404 for https://reflector.westga.edu/repos/ELRepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 160.10.5.37)
  - Status code: 404 for http://hkg.mirror.rackspace.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 180.150.156.88)
  - Status code: 404 for http://elrepo.mirrors.arminco.com/elrepo/el9/aarch64/repodata/repomd.xml (IP: 109.68.120.144)
  - Status code: 404 for http://mirrors.nav.ro/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 5.154.224.26)
  - Status code: 404 for http://mirror.rackspace.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 72.4.120.219)
  - Status code: 404 for http://mirrors.neusoft.edu.cn/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 219.216.128.25)
  - Status code: 404 for http://mirror.koddos.net/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 31.220.0.151)
  - Status code: 404 for http://www.jules.fm/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 46.22.137.105)
55

Just a quick note to say that the kernel-ml-6.1.1-1.el9.elrepo package set has now been released.

https://lists.elrepo.org/pipermail/elrepo/2022-December/006309.html

1 Like
57

I’ve reinstalled the image, but when trying to add ELRepo I’m getting this:

[root@localhost rocky]# rpm --import https://www.elrepo.org/RPM-GPG-KEY-elrepo.org
[root@localhost rocky]# dnf install https://www.elrepo.org/elrepo-release-9.el9.elrepo.noarch.rpm     
[root@localhost rocky]# dnf install –-enablerepo=elrepo-kernel kernel-ml
ELRepo.org Community Enterprise Linux Repository - el9                                                                                                                                                4.1  B/s | 196  B     00:47
Errors during downloading metadata for repository 'elrepo':
  - Status code: 404 for http://mirror.cedia.org.ec/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 201.159.221.67)
  - Status code: 404 for http://repos.dfw.lax-noc.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 96.44.142.5)
  - Status code: 404 for http://dfw.mirror.rackspace.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 74.205.112.120)
  - Status code: 404 for http://lon.mirror.rackspace.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 94.236.26.35)
  - Status code: 404 for https://mirrors.tuna.tsinghua.edu.cn/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 101.6.15.130)
  - Curl error (28): Timeout was reached for http://mirrors.leadhosts.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml [Connection timed out after 30000 milliseconds]
  - Status code: 404 for http://muug.ca/mirror/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 208.81.1.244)
  - Curl error (6): Couldn't resolve host name for http://elrepo.0m3n.net/elrepo/el9/aarch64/repodata/repomd.xml [Could not resolve host: elrepo.0m3n.net]
  - Status code: 404 for http://mirror-hk.koddos.net/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 103.109.101.20)
  - Status code: 404 for http://ftp.icm.edu.pl/pub/Linux/distributions/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 193.219.28.2)
  - Status code: 404 for http://mirrors.neusoft.edu.cn/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 219.216.128.25)
  - Status code: 404 for http://ftp.ines.lug.ro/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 89.149.59.178)
  - Status code: 404 for http://repos.ord.lax-noc.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 104.129.31.245)
  - Status code: 404 for http://linux-mirrors.fnal.gov/linux/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 131.225.105.75)
  - Status code: 404 for http://mirror.rackspace.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 72.4.120.219)
  - Status code: 404 for http://elrepo.mirror.angkasa.id/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 103.29.148.124)
  - Status code: 404 for https://elrepo.org/linux/elrepo/el9/aarch64/repodata/repomd.xml (IP: 69.195.83.87)
  - Status code: 404 for http://mirrors.thzhost.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 103.246.18.122)
  - Status code: 404 for http://iad.mirror.rackspace.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 72.4.120.219)
  - Status code: 404 for http://mirrors.colocall.net/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 62.149.2.66)
  - Status code: 404 for http://mirror.pit.teraswitch.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 204.16.246.250)
  - Status code: 404 for http://ftp.cc.uoc.gr/mirrors/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 147.52.159.12)
  - Status code: 404 for http://mirror.uta.edu.ec/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 192.188.46.165)
  - Status code: 404 for http://mirror.koddos.net/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 31.220.0.151)
  - Status code: 404 for http://ftp-srv2.kddi-research.jp/Linux/RPMS/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 202.255.47.226)
  - Status code: 404 for http://elrepo.mirrors.arminco.com/elrepo/el9/aarch64/repodata/repomd.xml (IP: 109.68.120.144)
  - Status code: 404 for http://hkg.mirror.rackspace.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 180.150.156.88)
  - Status code: 404 for http://ftp.yz.yamagata-u.ac.jp/pub/linux/RPMS/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 133.24.248.18)
  - Status code: 404 for http://fedora.is/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 176.57.227.242)
  - Status code: 404 for http://www.jules.fm/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 46.22.137.105)
  - Status code: 404 for http://syd.mirror.rackspace.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 119.9.32.73)
  - Status code: 404 for http://mirrors.mivocloud.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 185.163.44.44)
  - Status code: 404 for http://mirrors.coreix.net/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 85.13.241.50)
  - Status code: 404 for http://ftp.nluug.nl/os/Linux/distr/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 145.220.21.40)
  - Status code: 404 for http://repos.mia.lax-noc.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 173.44.32.10)
  - Status code: 404 for http://mirrors.nav.ro/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 5.154.224.26)
  - Status code: 404 for http://ord.mirror.rackspace.com/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 166.78.229.131)
  - Curl error (6): Couldn't resolve host name for http://ftp.utexas.edu/elrepo/elrepo/el9/aarch64/repodata/repomd.xml [Could not resolve host: ftp.utexas.edu]
  - Status code: 404 for http://mirrors.xservers.ro/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 89.38.249.150)
  - Status code: 404 for http://ftp.osuosl.org/pub/elrepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 64.50.236.52)
  - Status code: 404 for https://reflector.westga.edu/repos/ELRepo/elrepo/el9/aarch64/repodata/repomd.xml (IP: 160.10.5.37)
Error: Failed to download metadata for repo 'elrepo': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

Is this an incorrect way to add elrepo on RPi?

58

Does anyone have any help for me regarding the above? I’m still stuck on this one.

59

It took me a while to notice the error. Look closely at the “–-enablerepo=” above. The first dash is a “–” instead of a “-” (dash). Change it to “–enablerepo=” (double dash) and it will work. :slight_smile:

60

That’s not the actual problem I’m afraid. I tried typing it out by hand with double dashes and it fails just the same with 404 for all mirrors. The different dashes in my quoted output is probably just an artifact from how the forum parses text.

61

Yeah, looks like a Forum display issue.

What is odd is that I cannot reproduce what you are seeing. Can you try the following:

# dnf clean expire-cache

Also, disable all repos except elrepo-kernel:

# dnf --disablerepo=\* --enablerepo=elrepo-kernel list kernel-ml