On Friday 26 April 2019 00:02:33 Alan Condit wrote: > I downloaded the Arabian Stretch nightly image > Armbian_5.83.190424_Rockpro64_Debian_stretch_dev_5.0.0.7z > <https://dl.armbian.com/rockpro64/nightly/Armbian_5.83.190424_Rockpro6 >4_Debian_stretch_dev_5.0.0.7z>. It is running the 5.0.0 kernel (as > patched by Armbian. When I ran menuconfig, I had to figure out how to > select the full RT preempt. Then I built the > linux-stable-rt-4.19.31-rt18 kernel and installed it. At the end of > the install the Image link was still pointing to the 5.0.0 kernel but > the Initrd link was pointing to the > initrd-linux-stable-rt-4.19.31-rt18. So I tried booting it up and it > booted the 5.0.0 image, then I went into /boot, deleted the Image link > and created a new symbolic link to 4.19.31-rt kernel. Then I tried > booting again and it worked. I typed uname -a and it reported the > 4.19.31 kernel with full SMP Preempt RT. > > So, Gene, you could do the same thing for your Rock64 but you need to > download the Armbian image for the Rock64 rather than the RockPro64. > Don’t ask how I know!!! > > I compiled the kernel on the RockPro64. I started about 8:00p.m. and > it finished sometime after 2:00a.m. and before 7:00a.m. > That is slow, I've built, but not installed several of the 4.8 etc kernels in rt-preempt on the rock64, takes about an hour working against a 60GB SSD. The rock64 has an odd, 3 stage boot sequence I'm told, and the Makefile doesn't know what to do with it. I've not tried to have it make a deb which might work. Somebody has the tools to make a deb that does work because I've seen apt update the kernel, so it can be done, but questions about the how have gone unanswered on their forums for a year now. The biggest problem is the rpspi.ko source code that makes the spi driver on the pi, has so many tests to make sure its running on a pi, so it exits when tried on anything else. Thats good code, but it needs stripped of that, and made to use the gpio defines of the rock64. And I looked at it, not even close to compatible includes. Since that is a complete show stopper for running linuxcnc, I wasted a hundred buying 2 of them. Which is sad, because compared to the pi, its many times faster because its i/o doesn't have to fight traffic in the pi's internal usb2 hub that everything but the wifi radio and spi has to get thru to get in or out. I also bought the extra 16GB memory gizmo's, but haven't found any docs on how to make them use that as opposed to the sd card to boot from. Thats apparently an insider secret I don't qualify for. Overall, I'm disappointed because the info to actually put them to work as anything but a media server isn't being shared with us hobbiests. Sour grapes maybe, but thats how I see it.
And now the buildbot has stopped building for armhf, so I haven't had a linuxcnc update for the pi in quite a spell. Several months it seems. Still running 2.8.0-pre1-3855-g02ba5a1, installed Sept 16 2018. The intel machines are up to 2.8.0-pre1-4701-g5d6f7e9. That bypassing by spi is the saving grace that allows the pi to work. Thanks Alan. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
