The wiki says:
Before centos-userland-release-7-5.1804, in order to activate the new kernel and edit /boot/extlinux/extlinux.conf, you had to run /usr/bin/update-boot. This is no longer valid and it is done automatically by grubby.
But I just happened to look at /boot/grub/grub.conf
default=0 timeout=5 splashimage=(hd0,1)/grub/splash.xpm.gz hiddenmenu title CentOS-Userland-7-armv7hl-generic-GNOME-1804 (4.14.28-201.el7.centos.armv7hl) root (hd0,1) kernel /vmlinuz-4.14.28-201.el7.centos.armv7hl ro root=UUID=be2c9311-e289-4cab-b878-89b522144d70 initrd /initramfs-4.14.28-201.el7.centos.armv7hl.img
And I did the yum update that installed the 4.14.52 kernel.
Should I run update-boot?
/boot/klist.txt has: 4.14.28-201.el7.centos.armv7hl 4.14.52-201.el7.armv7hl
Robert, grub.conf is not used for boot in armhfp. Can you take a look at the contents of /boot/extlinux/extlinux.conf ?
Thanks. Pablo
El 2/8/18 a las 16:53, Robert Moskowitz escribió:
The wiki says:
Before centos-userland-release-7-5.1804, in order to activate the new kernel and edit /boot/extlinux/extlinux.conf, you had to run /usr/bin/update-boot. This is no longer valid and it is done automatically by grubby.
But I just happened to look at /boot/grub/grub.conf
default=0 timeout=5 splashimage=(hd0,1)/grub/splash.xpm.gz hiddenmenu title CentOS-Userland-7-armv7hl-generic-GNOME-1804 (4.14.28-201.el7.centos.armv7hl) root (hd0,1) kernel /vmlinuz-4.14.28-201.el7.centos.armv7hl ro root=UUID=be2c9311-e289-4cab-b878-89b522144d70 initrd /initramfs-4.14.28-201.el7.centos.armv7hl.img
And I did the yum update that installed the 4.14.52 kernel.
Should I run update-boot?
/boot/klist.txt has: 4.14.28-201.el7.centos.armv7hl 4.14.52-201.el7.armv7hl
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Ah, well:
# extlinux.conf generated by appliance-creator ui menu.c32 menu autoboot Welcome to CentOS-Userland-7-armv7hl-generic-GNOME-1804. Automatic boot in # second{,s}. Press a key for options. menu title CentOS-Userland-7-armv7hl-generic-GNOME-1804 Boot Options. menu hidden timeout 20 totaltimeout 600
default=CentOS-Userland-7-armv7hl-generic-GNOME-1804 (4.14.28-201.el7.centos.armv7hl) label CentOS Linux (4.14.52-201.el7.armv7hl) 7 (Core) kernel /vmlinuz-4.14.52-201.el7.armv7hl append ro root=UUID=be2c9311-e289-4cab-b878-89b522144d70 LANG=en_US.UTF-8 fdtdir /dtb-4.14.52-201.el7.armv7hl initrd /initramfs-4.14.52-201.el7.armv7hl.img
label CentOS-Userland-7-armv7hl-generic-GNOME-1804 (4.14.28-201.el7.centos.armv7hl) kernel /vmlinuz-4.14.28-201.el7.centos.armv7hl append ro root=UUID=be2c9311-e289-4cab-b878-89b522144d70 fdtdir /dtb-4.14.28-201.el7.centos.armv7hl initrd /initramfs-4.14.28-201.el7.centos.armv7hl.img
So which one gets selected? Is there a command to run or a file to check to see which kernel is loaded?
I went looking here because I was wondering if there was any kernel option specified to use that strange ifcfg-link file...
On 08/02/2018 04:08 PM, Pablo Sebastián Greco wrote:
Robert, grub.conf is not used for boot in armhfp. Can you take a look at the contents of /boot/extlinux/extlinux.conf ?
Thanks. Pablo
El 2/8/18 a las 16:53, Robert Moskowitz escribió:
The wiki says:
Before centos-userland-release-7-5.1804, in order to activate the new kernel and edit /boot/extlinux/extlinux.conf, you had to run /usr/bin/update-boot. This is no longer valid and it is done automatically by grubby.
But I just happened to look at /boot/grub/grub.conf
default=0 timeout=5 splashimage=(hd0,1)/grub/splash.xpm.gz hiddenmenu title CentOS-Userland-7-armv7hl-generic-GNOME-1804 (4.14.28-201.el7.centos.armv7hl) root (hd0,1) kernel /vmlinuz-4.14.28-201.el7.centos.armv7hl ro root=UUID=be2c9311-e289-4cab-b878-89b522144d70 initrd /initramfs-4.14.28-201.el7.centos.armv7hl.img
And I did the yum update that installed the 4.14.52 kernel.
Should I run update-boot?
/boot/klist.txt has: 4.14.28-201.el7.centos.armv7hl 4.14.52-201.el7.armv7hl
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
El 2/8/18 a las 17:22, Robert Moskowitz escribió:
Ah, well:
# extlinux.conf generated by appliance-creator ui menu.c32 menu autoboot Welcome to CentOS-Userland-7-armv7hl-generic-GNOME-1804. Automatic boot in # second{,s}. Press a key for options. menu title CentOS-Userland-7-armv7hl-generic-GNOME-1804 Boot Options. menu hidden timeout 20 totaltimeout 600
default=CentOS-Userland-7-armv7hl-generic-GNOME-1804 (4.14.28-201.el7.centos.armv7hl) label CentOS Linux (4.14.52-201.el7.armv7hl) 7 (Core) kernel /vmlinuz-4.14.52-201.el7.armv7hl append ro root=UUID=be2c9311-e289-4cab-b878-89b522144d70 LANG=en_US.UTF-8 fdtdir /dtb-4.14.52-201.el7.armv7hl initrd /initramfs-4.14.52-201.el7.armv7hl.img
label CentOS-Userland-7-armv7hl-generic-GNOME-1804 (4.14.28-201.el7.centos.armv7hl) kernel /vmlinuz-4.14.28-201.el7.centos.armv7hl append ro root=UUID=be2c9311-e289-4cab-b878-89b522144d70 fdtdir /dtb-4.14.28-201.el7.centos.armv7hl initrd /initramfs-4.14.28-201.el7.centos.armv7hl.img
So which one gets selected? Is there a command to run or a file to check to see which kernel is loaded?
Always the first one (the default= line is completely ignored) uname -a should tell you the current kernel.
I went looking here because I was wondering if there was any kernel option specified to use that strange ifcfg-link file...
I really have no idea about that ifcfg-link, sorry....
On 08/02/2018 04:08 PM, Pablo Sebastián Greco wrote:
Robert, grub.conf is not used for boot in armhfp. Can you take a look at the contents of /boot/extlinux/extlinux.conf ?
Thanks. Pablo
El 2/8/18 a las 16:53, Robert Moskowitz escribió:
The wiki says:
Before centos-userland-release-7-5.1804, in order to activate the new kernel and edit /boot/extlinux/extlinux.conf, you had to run /usr/bin/update-boot. This is no longer valid and it is done automatically by grubby.
But I just happened to look at /boot/grub/grub.conf
default=0 timeout=5 splashimage=(hd0,1)/grub/splash.xpm.gz hiddenmenu title CentOS-Userland-7-armv7hl-generic-GNOME-1804 (4.14.28-201.el7.centos.armv7hl) root (hd0,1) kernel /vmlinuz-4.14.28-201.el7.centos.armv7hl ro root=UUID=be2c9311-e289-4cab-b878-89b522144d70 initrd /initramfs-4.14.28-201.el7.centos.armv7hl.img
And I did the yum update that installed the 4.14.52 kernel.
Should I run update-boot?
/boot/klist.txt has: 4.14.28-201.el7.centos.armv7hl 4.14.52-201.el7.armv7hl
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Thanks.
Is everyone here using the generic ethernet setup with dhcp? Hasn't anyone configured a static address?
Sigh.
On 08/02/2018 05:10 PM, Pablo Sebastián Greco wrote:
El 2/8/18 a las 17:22, Robert Moskowitz escribió:
Ah, well:
# extlinux.conf generated by appliance-creator ui menu.c32 menu autoboot Welcome to CentOS-Userland-7-armv7hl-generic-GNOME-1804. Automatic boot in # second{,s}. Press a key for options. menu title CentOS-Userland-7-armv7hl-generic-GNOME-1804 Boot Options. menu hidden timeout 20 totaltimeout 600
default=CentOS-Userland-7-armv7hl-generic-GNOME-1804 (4.14.28-201.el7.centos.armv7hl) label CentOS Linux (4.14.52-201.el7.armv7hl) 7 (Core) kernel /vmlinuz-4.14.52-201.el7.armv7hl append ro root=UUID=be2c9311-e289-4cab-b878-89b522144d70 LANG=en_US.UTF-8 fdtdir /dtb-4.14.52-201.el7.armv7hl initrd /initramfs-4.14.52-201.el7.armv7hl.img
label CentOS-Userland-7-armv7hl-generic-GNOME-1804 (4.14.28-201.el7.centos.armv7hl) kernel /vmlinuz-4.14.28-201.el7.centos.armv7hl append ro root=UUID=be2c9311-e289-4cab-b878-89b522144d70 fdtdir /dtb-4.14.28-201.el7.centos.armv7hl initrd /initramfs-4.14.28-201.el7.centos.armv7hl.img
So which one gets selected? Is there a command to run or a file to check to see which kernel is loaded?
Always the first one (the default= line is completely ignored) uname -a should tell you the current kernel.
I went looking here because I was wondering if there was any kernel option specified to use that strange ifcfg-link file...
I really have no idea about that ifcfg-link, sorry....
On 08/02/2018 04:08 PM, Pablo Sebastián Greco wrote:
Robert, grub.conf is not used for boot in armhfp. Can you take a look at the contents of /boot/extlinux/extlinux.conf ?
Thanks. Pablo
El 2/8/18 a las 16:53, Robert Moskowitz escribió:
The wiki says:
Before centos-userland-release-7-5.1804, in order to activate the new kernel and edit /boot/extlinux/extlinux.conf, you had to run /usr/bin/update-boot. This is no longer valid and it is done automatically by grubby.
But I just happened to look at /boot/grub/grub.conf
default=0 timeout=5 splashimage=(hd0,1)/grub/splash.xpm.gz hiddenmenu title CentOS-Userland-7-armv7hl-generic-GNOME-1804 (4.14.28-201.el7.centos.armv7hl) root (hd0,1) kernel /vmlinuz-4.14.28-201.el7.centos.armv7hl ro root=UUID=be2c9311-e289-4cab-b878-89b522144d70 initrd /initramfs-4.14.28-201.el7.centos.armv7hl.img
And I did the yum update that installed the 4.14.52 kernel.
Should I run update-boot?
/boot/klist.txt has: 4.14.28-201.el7.centos.armv7hl 4.14.52-201.el7.armv7hl
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
-
Pablo Sebastián Greco -
Robert Moskowitz