On Friday 20 September 2019 17:03:06 Gene Heskett wrote: > I have the mesa stuff running, as in full screen glxgears is >50 fps, > I think I am ready to tackle the next step in making linuxcnc run on a > rpi4, which is building it a realtime kernel. > > So, Following along with the kernel-building page from the raspian > site: > > #>sudo apt install bc bison flex libssl-dev > No errors. > modify the git command to git the latest kernel that uname says it is: > #>sudo git clone --depth=1 https://github.com/raspberrypi/linux -b > rpi-4.19.y-rt > #>sudo chown -R pi:pi linux > #>cd linux > #>make bcm2711_defconfig > no errors > skip to rpi-4 instructions; but do a make menuconfig first to check > stuff Trouble, needs ncurses-devel or libncurses-dev: > * Unable to find the ncurses package. > * Install ncurses (ncurses-devel or libncurses-dev > * depending on your distribution). > > I suspect wayland is the culprit.. > > sudo apt can't find any ncurses packages > use less to verify the rt stuff is set, is: > # Timers subsystem > # > CONFIG_TICK_ONESHOT=y > CONFIG_NO_HZ_COMMON=y > # CONFIG_HZ_PERIODIC is not set > CONFIG_NO_HZ_IDLE=y > # CONFIG_NO_HZ_FULL is not set > CONFIG_NO_HZ=y > CONFIG_HIGH_RES_TIMERS=y > CONFIG_PREEMPT=y > CONFIG_PREEMPT_RT_BASE=y > CONFIG_HAVE_PREEMPT_LAZY=y > CONFIG_PREEMPT_LAZY=y > # CONFIG_PREEMPT_NONE is not set > # CONFIG_PREEMPT_VOLUNTARY is not set > # CONFIG_PREEMPT__LL is not set > # CONFIG_PREEMPT_RTB is not set > CONFIG_PREEMPT_RT_FULL=y > CONFIG_PREEMPT_COUNT=y > > So, not being able to intelligently modify it, I fire off a "make -j2 > zImage modules dtbs" to see what falls out. I'd try the j4, but w/o a > fan on that big one piece heat sink, and its hot already, a j4 might > be pushing my luck. Half an hour later its still munching along at > about 3x a pi3's speed. > > Now, I see something in the raspberry kernel building docs that I > think will be handier than sliced bread, I can name the zImage I copy > to the /boot partition differently, as long as I also use that name as > the kernel to boot in the /boot/config.txt file. So a quick edit of > that file, either on a live machine, or in a reader, can put me back > to booting the default kernel. I don't know as I can do that on a > pi3. But it for sure is worth trying! The limit of course is the size > of the /boot, and how full it is. On the pi4, 260 megs, df say its 16% > used, so there is room to play. But the pi3 /boot is only 60 megs, and > 55% used, so maybe not. > > Done but me somewhat confused. It built bcm2711-rpi-4-b.dtb > which is in the /boot directory, but built it > in > /media/pi/workspace/kernel/linux/arch/arm/boot/dts/bcm2711-rpi-4-b.dtb >, which is nearly the same location it built zImage in. > > There is an install.sh in that /arch/arm/boot directory, but it needs > at least 3 arguments. Anyboy got an idea what to pass to it? > So then I thought I'd see how far I could get with a 2 or 3 week old pull of linuxcnc-master, but ./configure bails out:
checking for libusb-1.0... yes checking for module installation directory... configuring for run-in-place /media/pi/slash/linuxcnc-master/rtlib checking for glib... configure: error: no -- required until somebody makes glib optional Another wayland casualty? Thanks for any guidance everybody. 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) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene> _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
