Hello You have the error "dracut-initqueue[230]: Warning: /dev/disk/by-uuid/675d1330-cb5f-4562-98e0-b5b5b1bb4f2c does not exist ". Is it the same UUID you add on 4.0.0 kernel on extlinux.conf file? Le 19/08/2015 18:06, Robert Moskowitz a écrit : > Well I did something wrong.... > > On 08/19/2015 08:03 AM, Mandar Joshi wrote: >>> Fortunately, I was logging the serial console (I use screen and turn on >>> logging), and see: >>> >>> /usr/lib/kernel/install.d/51-dracut-rescue.install: line 59: >>> /boot/loader/entrie >>> s/82bd824c4a564768ba015297f0bec908-0-rescue.conf: No such file or >>> directory >>> warning: %posttrans(kernel-core-4.2.0-0.rc2.git0.1.centos.el7.armv7hl) >>> scriptlet >>> failed, exit status 1 >>> Non-fatal POSTTRANS scriptlet failure in rpm package >>> kernel-core-4.2.0-0.rc2.git >>> 0.1.centos.el7.armv7hl >>> >> You will have to generate the initrd manually using dracut. > > I booted with the 4.0.0 kernel then: > > cd /boot > dracut "initramfs-4.2.0-0.rc2.git0.1.centos.el7.armv7hl.img" > vmlinuz-4.2.0-0.rc2.git0.1.centos.el7.armv7hl > > And there was the message: > > Kernel version vmlinuz-4.2.0-0.rc2.git0.1.centos.el7.armv7hl has no > module directory > /lib/modules/vmlinuz-4.2.0-0.rc2.git0.1.centos.el7.armv7hl > > But I pushed on. See below: > >> >>> What I see in the log from the reboot is: >>> >>> Scanning mmc 0:1... >>> Found /extlinux/extlinux.conf >>> Retrieving file: /extlinux/extlinux.conf >>> Starting kernel ... >>> >>> ==================== >>> >>> So please tell me how to get my Cubietruck to boot into the newer >>> kernel. >>> >> Edit /boot/extlinux/extlinux.conf and add a entry for the new kernel. > > I added: > > label centos 4.2.0-0 > kernel /vmlinuz-4.2.0-0.rc2.git0.1.centos.el7.armv7hl > append enforcing=0 root=UUID=675d1330-cb5f-4562-98e0-b5b5b1bb4f2c > fdtdir /dtb-4.2.0-0.rc2.git0.1.centos.el7.armv7hl > initrd /initramfs-4.2.0-0.rc2.git0.1.centos.el7.armv7hl.img > > Rebooted and selected centos 4.2.0-0. > > Boot seemed to be going along, then stopped and gave me the following: > > Mounting Configuration File System... > [ OK ] Mounted Configuration File System. > dracut-initqueue[230]: /bin/dracut-initqueue: line 77: 823 > Segmentation fault udevadm settle --timeout=0 > /dev/null 2>&1 > dracut-initqueue[230]: Warning: Could not boot. > dracut-initqueue[230]: Warning: > /dev/disk/by-uuid/675d1330-cb5f-4562-98e0-b5b5b1bb4f2c does not exist > Starting Dracut Emergency Shell... > Warning: /dev/disk/by-uuid/675d1330-cb5f-4562-98e0-b5b5b1bb4f2c does > not exist > > Generating "/run/initramfs/rdsosreport.txt" > > > Entering emergency mode. Exit the shell to continue. > Type "journalctl" to view system logs. > You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick > or /boot > after mounting them and attach it to a bug report. > > > dracut:/# > > ======= > > So I did something wrong. > >> The rbfkernelup.py yum plugin in RBF is meant for this purpose. For >> the Cubietruck, it will add an entry to /boot/extlinux/extlinux.conf. >> >> You can read more about it in the section "Usage of >> yumplugins/rbfkernelup.py" in the README >> https://github.com/mndar/rbf/blob/master/README.md and in >> https://github.com/mndar/rbf/blob/master/doc/KERNELUP_README.md > > I looked there and did not see what to install to get this yum plugin. > > thanks > > Oh, and I can still boot into the 4.0.0 kernel. > > > _______________________________________________ > Arm-dev mailing list > Arm-dev at centos.org > http://lists.centos.org/mailman/listinfo/arm-dev