See below. Interestingly "sudo grub2-mkconfig" resulted in permission denied but "su" worked. Nevertheless, I am stilled faced w/
[pi@raspi ~]$ lsb_release -d;uname -r Description: Fedora release 29 (Twenty Nine) 5.0.10-200.fc29.aarch64
Thanks, Thomas
[pi@raspi ~]$ lsb_release -d;uname -r Description: Fedora release 29 (Twenty Nine) 5.0.10-200.fc29.aarch64 [pi@raspi ~]$ rpm -qa| grep kernel| sort kernel-5.0.10-200.fc29.aarch64 kernel-5.0.6-200.fc29.aarch64 kernel-5.0.9-200.fc29.aarch64 kernel-core-5.0.10-200.fc29.aarch64 kernel-core-5.0.6-200.fc29.aarch64 kernel-core-5.0.9-200.fc29.aarch64 kernel-headers-5.0.9-200.fc29.aarch64 kernel-modules-5.0.10-200.fc29.aarch64 kernel-modules-5.0.6-200.fc29.aarch64 kernel-modules-5.0.9-200.fc29.aarch64 kernel-tools-5.0.9-200.fc29.aarch64 kernel-tools-libs-5.0.9-200.fc29.aarch64 [[pi@raspi ~]$ sudo grub2-mkconfig > /boot/efi/EFI/fedora/grub.cfg -bash: /boot/efi/EFI/fedora/grub.cfg: Permission denied [pi@raspi ~]$ su Password: [root@raspi pi]# grub2-mkconfig > /boot/efi/EFI/fedora/grub.cfg Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.0.10-200.fc29.aarch64 Found initrd image: /boot/initramfs-5.0.10-200.fc29.aarch64.img Found linux image: /boot/vmlinuz-5.0.9-200.fc29.aarch64 Found initrd image: /boot/initramfs-5.0.9-200.fc29.aarch64.img Found linux image: /boot/vmlinuz-5.0.6-200.fc29.aarch64 Found initrd image: /boot/initramfs-5.0.6-200.fc29.aarch64.img done
On Fri, May 3, 2019 at 9:45 PM Peter Robinson pbrobinson@gmail.com wrote:
https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#aarch64_suppor... only quotes Fedora 29.
Description: Fedora release 30 (Thirty) in combination w/ 5.0.10-200.fc29.aarch64
is the concern. Thanks.
Ah, missed the f29 bit. What does the following return?
"rpm -qa| grep kernel| sort"
I suspect you might just need to regenerate the grub config for the new BLS feature which you can do with:
"grub2-mkconfig > /boot/efi/EFI/fedora/grub.cfg"
See below. Interestingly "sudo grub2-mkconfig" resulted in permission denied but "su" worked. Nevertheless, I am stilled faced w/
Well there's no F-30 kernels installed so it's booted as expected, even if it's not what's desired!
I would: "rm -rf /var/cache/dnf/*" "dnf upgrade --refresh"
Peter
[pi@raspi ~]$ lsb_release -d;uname -r Description: Fedora release 29 (Twenty Nine) 5.0.10-200.fc29.aarch64
Thanks, Thomas
[pi@raspi ~]$ lsb_release -d;uname -r Description: Fedora release 29 (Twenty Nine) 5.0.10-200.fc29.aarch64 [pi@raspi ~]$ rpm -qa| grep kernel| sort kernel-5.0.10-200.fc29.aarch64 kernel-5.0.6-200.fc29.aarch64 kernel-5.0.9-200.fc29.aarch64 kernel-core-5.0.10-200.fc29.aarch64 kernel-core-5.0.6-200.fc29.aarch64 kernel-core-5.0.9-200.fc29.aarch64 kernel-headers-5.0.9-200.fc29.aarch64 kernel-modules-5.0.10-200.fc29.aarch64 kernel-modules-5.0.6-200.fc29.aarch64 kernel-modules-5.0.9-200.fc29.aarch64 kernel-tools-5.0.9-200.fc29.aarch64 kernel-tools-libs-5.0.9-200.fc29.aarch64 [[pi@raspi ~]$ sudo grub2-mkconfig > /boot/efi/EFI/fedora/grub.cfg -bash: /boot/efi/EFI/fedora/grub.cfg: Permission denied [pi@raspi ~]$ su Password: [root@raspi pi]# grub2-mkconfig > /boot/efi/EFI/fedora/grub.cfg Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.0.10-200.fc29.aarch64 Found initrd image: /boot/initramfs-5.0.10-200.fc29.aarch64.img Found linux image: /boot/vmlinuz-5.0.9-200.fc29.aarch64 Found initrd image: /boot/initramfs-5.0.9-200.fc29.aarch64.img Found linux image: /boot/vmlinuz-5.0.6-200.fc29.aarch64 Found initrd image: /boot/initramfs-5.0.6-200.fc29.aarch64.img done
On Fri, May 3, 2019 at 9:45 PM Peter Robinson pbrobinson@gmail.com wrote:
https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#aarch64_suppor... only quotes Fedora 29.
Description: Fedora release 30 (Thirty) in combination w/ 5.0.10-200.fc29.aarch64
is the concern. Thanks.
Ah, missed the f29 bit. What does the following return?
"rpm -qa| grep kernel| sort"
I suspect you might just need to regenerate the grub config for the new BLS feature which you can do with:
"grub2-mkconfig > /boot/efi/EFI/fedora/grub.cfg"
On Fri, May 3, 2019 at 9:28 PM Peter Robinson pbrobinson@gmail.com wrote:
See below. Interestingly "sudo grub2-mkconfig" resulted in permission denied but "su" worked. Nevertheless, I am stilled faced w/
Well there's no F-30 kernels installed so it's booted as expected, even if it's not what's desired!
I would: "rm -rf /var/cache/dnf/*" "dnf upgrade --refresh"
And if that doesn't give you a new kernel update try:
"dnf --releasever=30 --setopt=deltarpm=false distro-sync"
"dnf --releasever=30 --setopt=deltarpm=false distro-sync" does the trick. I wonder, if it could replace "sudo dnf -y system-upgrade download --releasever=30" or just complete it.
[pi@raspi ~]$ lsb_release -d;uname -r Description: Fedora release 30 (Thirty) 5.0.10-300.fc30.aarch64
On Fri, May 3, 2019 at 10:30 PM Peter Robinson pbrobinson@gmail.com wrote:
On Fri, May 3, 2019 at 9:28 PM Peter Robinson pbrobinson@gmail.com wrote:
See below. Interestingly "sudo grub2-mkconfig" resulted in permission
denied but "su" worked. Nevertheless, I am stilled faced w/
Well there's no F-30 kernels installed so it's booted as expected, even if it's not what's desired!
I would: "rm -rf /var/cache/dnf/*" "dnf upgrade --refresh"
And if that doesn't give you a new kernel update try:
"dnf --releasever=30 --setopt=deltarpm=false distro-sync"
On Sat, May 4, 2019 at 1:37 PM ng0177@gmail.com wrote:
"dnf --releasever=30 --setopt=deltarpm=false distro-sync" does the trick. I wonder, if it could replace "sudo dnf -y system-upgrade download --releasever=30" or just complete it.
distro-sync is an alternative to system-upgrade, there's pros and cons to it though so the later tends to be more suitable for most users. The former is useful to ensure you have the latest packages plus and changes like new package additions that may not get pulled in, or just as a cleanup mechanism like this.
Peter
[pi@raspi ~]$ lsb_release -d;uname -r Description: Fedora release 30 (Thirty) 5.0.10-300.fc30.aarch64
On Fri, May 3, 2019 at 10:30 PM Peter Robinson pbrobinson@gmail.com wrote:
On Fri, May 3, 2019 at 9:28 PM Peter Robinson pbrobinson@gmail.com wrote:
See below. Interestingly "sudo grub2-mkconfig" resulted in permission denied but "su" worked. Nevertheless, I am stilled faced w/
Well there's no F-30 kernels installed so it's booted as expected, even if it's not what's desired!
I would: "rm -rf /var/cache/dnf/*" "dnf upgrade --refresh"
And if that doesn't give you a new kernel update try:
"dnf --releasever=30 --setopt=deltarpm=false distro-sync"
That makes sense. I noticed with distro-sync that the "getdns-stubby" package had vanished and needed to be reinstalled. But I prefer distro-sync for it seems a cleaner installation. Thanks for all the help!
On Sat, May 4, 2019 at 4:22 PM Peter Robinson pbrobinson@gmail.com wrote:
On Sat, May 4, 2019 at 1:37 PM ng0177@gmail.com wrote:
"dnf --releasever=30 --setopt=deltarpm=false distro-sync" does the
trick. I wonder, if it could replace "sudo dnf -y system-upgrade download --releasever=30" or just complete it.
distro-sync is an alternative to system-upgrade, there's pros and cons to it though so the later tends to be more suitable for most users. The former is useful to ensure you have the latest packages plus and changes like new package additions that may not get pulled in, or just as a cleanup mechanism like this.
Peter
[pi@raspi ~]$ lsb_release -d;uname -r Description: Fedora release 30 (Thirty) 5.0.10-300.fc30.aarch64
On Fri, May 3, 2019 at 10:30 PM Peter Robinson pbrobinson@gmail.com
wrote:
On Fri, May 3, 2019 at 9:28 PM Peter Robinson pbrobinson@gmail.com
wrote:
See below. Interestingly "sudo grub2-mkconfig" resulted in
permission denied but "su" worked. Nevertheless, I am stilled faced w/
Well there's no F-30 kernels installed so it's booted as expected, even if it's not what's desired!
I would: "rm -rf /var/cache/dnf/*" "dnf upgrade --refresh"
And if that doesn't give you a new kernel update try:
"dnf --releasever=30 --setopt=deltarpm=false distro-sync"
-
ng0177＠gmail.com -
Peter Robinson