So I see how little is there. Well at least selinux is running disabled, so I can move sshd to a different port without semanage.
Since no ntp function, no date time update. Well this is pre-alpha.
Speaking about pre-alpha and the status of the armv7hl development, now that AArch64 is launched, will effort be applied here?
I have NO experience with github and have looked at the rbf information and don't have a cue how I can build any images myself. So I either need a lot of education, or some newer images for me to work with. And a repo of armv7fl rpms to work with!
So any pointers would be appreciated.
On 08/18/2015 11:20 AM, Robert Moskowitz wrote:
So I see how little is there. Well at least selinux is running disabled, so I can move sshd to a different port without semanage.
Since no ntp function, no date time update. Well this is pre-alpha.
Speaking about pre-alpha and the status of the armv7hl development, now that AArch64 is launched, will effort be applied here?
I have NO experience with github and have looked at the rbf information and don't have a cue how I can build any images myself. So I either need a lot of education, or some newer images for me to work with. And a repo of armv7fl rpms to work with!
So any pointers would be appreciated.
The install is a minimal install, but there are a bunch more things available via yum.
Just remove the CentOS-Base.repo file and use the other default repos and install whatever you want.
On 08/18/2015 02:25 PM, Johnny Hughes wrote:
On 08/18/2015 11:20 AM, Robert Moskowitz wrote:
So I see how little is there. Well at least selinux is running disabled, so I can move sshd to a different port without semanage.
Since no ntp function, no date time update. Well this is pre-alpha.
Speaking about pre-alpha and the status of the armv7hl development, now that AArch64 is launched, will effort be applied here?
I have NO experience with github and have looked at the rbf information and don't have a cue how I can build any images myself. So I either need a lot of education, or some newer images for me to work with. And a repo of armv7fl rpms to work with!
So any pointers would be appreciated.
The install is a minimal install, but there are a bunch more things available via yum.
Just remove the CentOS-Base.repo file and use the other default repos and install whatever you want.
Ah, the bit of magic to get updates! Took a long time to cleanup from a new kernel and avahi...
What with going from 4.0.0-1 to 4.2.0-0, I decided to reboot to ensure that it would boot!
But it still booted: Kernel 4.0.0-1.el7.armv7hl on an armv7l
:(
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 Verifying : avahi-libs-0.6.31-14.el7.armv7hl 1/9
Verifying : kernel-4.2.0-0.rc2.git0.1.centos.el7.armv7hl 2/9
Verifying : kernel-modules-4.2.0-0.rc2.git0.1.centos.el7.armv7hl 3/9
Verifying : avahi-autoipd-0.6.31-14.el7.armv7hl 4/9
Verifying : avahi-0.6.31-14.el7.armv7hl 5/9
Verifying : kernel-core-4.2.0-0.rc2.git0.1.centos.el7.armv7hl 6/9
Verifying : avahi-autoipd-0.6.31-13.el7.armv7hl 7/9
Verifying : avahi-0.6.31-13.el7.armv7hl 8/9
Verifying : avahi-libs-0.6.31-13.el7.armv7hl 9/9
Installed: kernel.armv7hl 0:4.2.0-0.rc2.git0.1.centos.el7
kernel-core.armv7hl 0:4.2.0-0.rc2.git0.1.centos.el7
kernel-modules.armv7hl 0:4.2.0-0.rc2.git0.1.centos.el7
Updated: avahi.armv7hl 0:0.6.31-14.el7 avahi-autoipd.armv7hl 0:0.6.31-14.el7
avahi-libs.armv7hl 0:0.6.31-14.el7
Complete!
==========
What I see in the log from the reboot is:
Scanning mmc 0:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 327 bytes read in 126 ms (2 KiB/s) Ignoring unknown command: ui Ignoring malformed menu command: autoboot Ignoring unknown command: totaltimeout centos Options 1: centos Enter choice: 1: centos Retrieving file: /initramfs-4.0.0-1.el7.armv7hl.img 66687488 bytes read in 6427 ms (9.9 MiB/s) Retrieving file: /vmlinuz-4.0.0-1.el7.armv7hl 5692880 bytes read in 681 ms (8 MiB/s) append: enforcing=0 root=UUID=675d1330-cb5f-4562-98e0-b5b5b1bb4f2c Retrieving file: /dtb-4.0.0-1.el7.armv7hl/sun7i-a20-cubietruck.dtb 26288 bytes read in 2581 ms (9.8 KiB/s) Kernel image @ 0x42000000 [ 0x000000 - 0x56ddd0 ] ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 4b066000, end 4efff200 ... OK Loading Device Tree to 4b05c000, end 4b0656af ... OK
Starting kernel ...
====================
So please tell me how to get my Cubietruck to boot into the newer kernel.
Meanwhile, I have to figure out what is in the repo, and what to install to get things like time going...
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.
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.
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
Regards Mandar Joshi
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.
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
The second argument to dracut should be the kernel version, the exact name of the directory as it is in /lib/modules
I looked there and did not see what to install to get this yum plugin.
You will need a new image generated with RBF to use the plugin. You could add files to /etc manually but that could become messy. To use the yum plugin, all you have to do is copy it to the /usr/lib/yum-plugins and the conf file to /etc/yum/pluginconf.d/
Regards Mandar Joshi
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@centos.org http://lists.centos.org/mailman/listinfo/arm-dev
On 08/18/2015 12:20 PM, Robert Moskowitz wrote:
Since no ntp function, no date time update. Well this is pre-alpha.
Simply installing ntp is not enough to get ntp time update shortly after booting. And with no /var/log/messages I can't look for errors.
Any pointers for setting up both ntp (sntp?) and logging until we get a build that provides this, is highly appreciated.
-
Johnny Hughes -
Mandar Joshi -
Nicolas -
Robert Moskowitz