#linuxcnc-devel Logs

Aug 29 2022

#linuxcnc-devel Calendar

12:19 AM linuxcnc-build: build #2076 of 4041.deb-buster-rtpreempt-amd64 is complete: Failure [4failed shell_3 shell_4] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4041.deb-buster-rtpreempt-amd64/builds/2076 blamelist: CMorley <chrisinnanaimo@hotmail.com>
03:26 AM pere: build master on debian/buster is no longer supported, right?
03:45 AM pere: Are the supported platforms listed somewhere? <URL: https://github.com/LinuxCNC/linuxcnc/issues/1941 > could use such link.
04:40 AM Tom_L: pere, on the HDD_IMAGE_BUILD_OPTIONS i think i'm using them all but maybe the --initramfs live-boot
04:41 AM Tom_L: supported: http://buildbot.linuxcnc.org/
04:44 AM Tom_L: line 21 --distribution wheezy :)
04:45 AM Tom_L: there may be a a couple things there i can try
04:52 AM Tom_L: http://archive.raspbian.org/raspbian/dists/
04:52 AM Tom_L: that's going to be all 32 bit
04:53 AM Tom_L: not 64
04:54 AM Tom_L: might work with buster but i still need a valid bootloader in the bootloader directory i think
05:20 AM pere: Tom_L: I updated my proposal in <URL: https://github.com/LinuxCNC/linuxcnc-live-build/pull/10 >.
05:48 AM Tom_L: you sure you don't want arm64?
05:49 AM pere: andypugh: what do you think about publishing a tech preview iso for bookworm/x86?
05:49 AM Tom_L: isn't bullseye + 64bit?
05:50 AM Tom_L: lemme know where the dust settles...
05:50 AM pere: I build locally for bullseye, nothing in the debian archives.
05:51 AM Tom_L: i thought buster was the last one that would rely on buildbot
05:51 AM pere: and no-one has worked on bullseye live images. I looked at bookworm, the next stable, as I expect it will take a while to get it ready and did not start on something that might be obsolete before we are done.
05:52 AM Tom_L: there is no checkout for bullseye in your repo afik. just buster and bookworm
05:52 AM pere: probably fairly easy, but need bullseye apt repos for linuxcnc, which I could not be bothered with when bookworm have the package already in debian.
05:54 AM Tom_L: afik buster builds with armhf and bookworm builds with arm64
05:55 AM pere: there is an arm iso for buster?
05:55 AM pere: Note, my question for andypugh is not about arm, but x86 architectures.
05:55 AM Tom_L: 2.8.1
05:55 AM Tom_L: http://linuxcnc.org/downloads/
05:57 AM pere: ok. unable to reach that site. :(
05:57 AM Tom_L: https://www.linuxcnc.org/iso/linuxcnc-2.8.1-pi4.zip
05:58 AM Tom_L: the only 'official' arm release i know of
06:00 AM pere: perhaps those build rules could use an update too?
06:05 AM pere: rene-dev5: do you agree that #479 is a subset of #581?
06:28 AM pere: hansu: hi. :)
06:30 AM hansu: Hi!
06:38 AM -!- #linuxcnc-devel mode set to +v by ChanServ
06:38 AM -!- #linuxcnc-devel mode set to +v by ChanServ
06:44 AM pere: hansu: great to see us touching the 25 mark yesterday with the pull requests. :)
06:44 AM -!- #linuxcnc-devel mode set to +v by ChanServ
06:45 AM hansu: yes!
06:46 AM Tom_L: pere, i've also been building mine with the mate gui
06:46 AM hansu: What's your opinion about https://github.com/LinuxCNC/linuxcnc/pull/1972 ?
06:47 AM pere: my opinion is that the html and pdf documentation should have the same order and content. do not really have an opinion on what order is a good one.
06:48 AM hansu: I also wonder why integrator and developer have separate PDF files
07:07 AM pere: I wonder why the pdfs are split the way they are. :)
07:08 AM pere: one 1300 page PDF, and several very small one, and one 600 page pdf with a section also in the 1200 page pdf (the man pages).
07:08 AM pere: s/1200/1300/
07:18 AM Tom_L: pere, would you like the config line i've been using?
07:18 AM pere: Tom_L: sure
07:18 AM -!- #linuxcnc-devel mode set to +v by ChanServ
07:19 AM -!- #linuxcnc-devel mode set to +v by ChanServ
07:19 AM Tom_dev: sudo lb config \
07:19 AM Tom_dev: --architecture arm64 \
07:19 AM Tom_dev: --bootstrap-qemu-arch arm64 \
07:19 AM Tom_dev: --bootstrap-qemu-static /usr/bin/qemu-arm-static \
07:19 AM Tom_dev: --bootloaders syslinux \
07:19 AM Tom_dev: --system live \
07:19 AM Tom_dev: --binary-filesystem fat32 \
07:19 AM Tom_dev: --binary-images hdd \
07:19 AM Tom_dev: --chroot-filesystem squashfs \
07:19 AM Tom_dev: --hdd-size 512 \
07:19 AM Tom_dev: --bootappend-live "boot=live config hostname=pi username=pi" \
07:19 AM Tom_dev: --distribution bookworm \
07:19 AM Tom_dev: --compression gzip \
07:19 AM Tom_dev: --gzip-options '-9 --rsyncable' \
07:19 AM Tom_dev: --mode debian \
07:19 AM Tom_dev: --linux-flavours arm64
07:20 AM Tom_dev: also edit auto/config
07:23 AM Tom_dev: http://paste.debian.net/1252038/
07:23 AM Tom_dev: i edit 4 files as such and include the above config line
07:24 AM Tom_dev: those have to be done last or they get overwritten each timee
07:24 AM pere: I do not believe sudo is needed for lb config, only lb build.
07:25 AM Tom_L: correct
07:25 AM Tom_L: not sure why it's there :)
07:26 AM Tom_L: there were 2 entries in the firmware.list to remove is all
07:26 AM Tom_L: they are not supported
07:26 AM Tom_L: the rest seem to be ok
07:27 AM pere: did your line work? did you try without --bootloaders syslinux?
07:28 AM silopolis[m]: <hansu> "I also wonder why integrator and..." <- Like I explained in my mail, in my view, integrator doesn't code but only configures lcnc for a special setup
07:28 AM Tom_L: i get an error building still
07:28 AM Tom_L: not a valid bootloader iirc
07:28 AM pere: I also suspect 512 MiB is too small for the linuxcnc installation.
07:29 AM Tom_L: remove it and it reverts to auto
07:29 AM pere: I notice my proposal have --initramfs live-boot and lack your --bootappend line.
07:29 AM Tom_L: i likely forgot to add that :)
07:30 AM Tom_L: i did have to install syslinux
07:31 AM Tom_L: later..
08:00 AM hansu: silopolis[m]: I would just move Integrator in the Configuration section...
08:20 AM pere: I tried the new pot= feature in po4a to split documentation.pot into several topic related files. it failed, not sure why.
08:25 AM hansu: :-(
08:27 AM pere: ah, it can not be used with po4a_alias, have to be used on each individual file. :(
08:37 AM pere: but the process of generating the POT files is horribly slow. it run msggrep and msgmerge once per file and once more per language per file...
09:00 AM pere: the automated test of linuxcnc in debian I added did fail as expected, but not quite how I expected it to fail... <URL: https://ci.debian.net/data/autopkgtest/unstable/amd64/l/linuxcnc/25460185/log.gz > :)
09:39 AM skunkwor1s is now known as skunkworks
10:20 AM silopolis[m]: <hansu> "silopolis: I would just move..." <- Yes same, I just tend to like the user profile oriented naming :)
11:14 AM linuxcnc-build: build #2079 of 4041.deb-buster-rtpreempt-amd64 is complete: Failure [4failed shell_3 shell_4] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4041.deb-buster-rtpreempt-amd64/builds/2079 blamelist: Hans Unzner <hansunzner@gmail.com>
12:14 PM Tom_L: pere, i think i looked at --initramfs but it defaults to live-boot anyway
12:14 PM pere: ah, good.
12:14 PM Tom_L: so that would have been included here anyway
12:15 PM Tom_L: biggest problem is finding an arm64 bootloader in the correct format for live build
12:15 PM Tom_L: did you look at the last log?
12:15 PM pere: perhaps fat32 with grub(-efi) on hdd is the best option?
12:16 PM Tom_L: it error'd on no candidate for syslinux
12:16 PM Tom_L: maybe for 32bit
12:16 PM pere: <URL: http://paste.debian.net/1252038/ >, you mean?
12:16 PM Tom_L: i'd like to get a 64bit version working
12:16 PM Tom_L: no
12:16 PM pere: it did not look like a log
12:16 PM pere: I would also like to get the 64 bit version working.
12:16 PM Tom_L: http://tom-itx.no-ip.biz:81/~webpage/cnc/live-build/build.log
12:16 PM Tom_L: bottom
12:17 PM Tom_L: that was the last build
12:18 PM pere: I see the syslinux complaint again. I have vague memories of syslinux being most useful for CD boot.
12:18 PM Tom_L: i've no clue.. i'm a noob at this :)
12:18 PM Tom_L: just trying things and finding out what works or doesn't
12:18 PM pere: which is why I suggest grub, as it is for booting from hd.
12:19 PM Tom_L: there is no grub-efi bootloader
12:19 PM pere: I expected the default for hdd to be good, but apparently not.
12:19 PM Tom_L: not on the git anyway
12:19 PM pere: I based it on --bootloaders grub-legacy|grub-pc|syslinux|grub-efi|"BOOTLOADERS" from the lb config --help output.
12:20 PM Tom_L: you may have to separate amd64 and arm64 on git
12:20 PM pere: I believe grub-pc is for x86, unsure about grub-legacy and grub-efi might have a chance of working on rpi.
12:20 PM Tom_L: i looked at some working sd cards and saw arm64 on one
12:21 PM Tom_L: armhf on buster
12:22 PM -!- #linuxcnc-devel mode set to +v by ChanServ
12:23 PM Tom_dev: https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#raspberry-pi-boot-modes
12:23 PM Tom_dev: there is that
12:23 PM linuxcnc-build: build #1972 of 4042.deb-buster-rtpreempt-rpi4 is complete: Failure [4failed shell_3 shell_4] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4042.deb-buster-rtpreempt-rpi4/builds/1972 blamelist: Hans Unzner <hansunzner@gmail.com>
12:26 PM Tom_dev: maybe we somehow need to point to these: http://raspbian.raspberrypi.org/raspbian/dists/
12:26 PM Tom_dev: and include what extras we want built in
12:44 PM pere: Tom_L: given that freedombox build rpi images directly from debian without anything from raspian, I believe it should be doable.
12:45 PM pere: Tom_L: perhaps the rpi firmware package is needed?
12:50 PM Tom_L: where is that found?
12:50 PM Tom_L: pretty sure it's still waiting for a valid bootloader though...
12:50 PM Tom_L: in the firmware.list the top and bottom entries were all that caused failure
12:51 PM Tom_L: (not on a linux box atm)
12:51 PM pere: <URL: https://tracker.debian.org/pkg/raspi-firmware >
12:51 PM Tom_L: how can that be included in the git repo?
12:52 PM pere: I would guess you only need to add the package to the package list to be installed.
12:52 PM pere: <URL: https://packages.debian.org/unstable/raspi-firmware >
12:53 PM Tom_L: or the firmware list?
12:54 PM Tom_L: that is likely going to be 32bit
12:55 PM pere: it claim rpi 1-4 support. worth a try?
12:55 PM Tom_L: i'm in :)
01:01 PM pere: probably need to also get rid of the syslinux error, for example by requesting the grub-efi boot loader. I got the impression that it did not error out (but did not work either. :)
01:01 PM Tom_L: pretty sure i got an error on grub-efi
01:01 PM Tom_L: no bootloader found
01:01 PM Tom_L: i have an errand to run. back later on
01:01 PM pere: :(
01:02 PM Tom_L: if you come up with a fix or something to try, i'll run it when i get back
01:03 PM Tom_L: i'm not sure how to link that firmware to the repo...
01:16 PM pere: Tom_L: I discovered I know the raspi-firmware maintainer, and is asking him how to get this working.
01:16 PM pere: you do not need to link anything to the repo, you just need to get it installed in the chroot.
01:17 PM pere: "Getting it to boot is very simple... you just need to drop the needed firmware plus a Linux kernel in a FAT partition
01:17 PM pere: mount the FAT partition as /boot/firmware/ and install raspi-firmware
01:17 PM pere: the last three are what he told me. :)
01:18 PM pere: so I guess /boot/firmware should be a fat partition, while the rest should be a linux file system (btrfs, ext4, whatnot).
03:12 PM Tom_L: so how do you get it into chroot?
03:13 PM Tom_L: i was gonna ask you if you know of an preempt-rt kernel to use for it?
03:18 PM -!- #linuxcnc-devel mode set to +v by ChanServ
03:21 PM Tom_dev: pere, i see some flags here that aren't described in the man pages: http://paste.debian.net/1251987/
03:22 PM Tom_dev: is that for lb or some other build system?
03:22 PM Tom_dev: should we add --package linuxcnc-xxx ?
03:35 PM Tom_L: pere, yes the boot is a small partition
03:36 PM Tom_dev: Device Boot Start End Sectors Size Id Type
03:36 PM Tom_dev: /dev/sdd1 8192 532479 524288 256M c W95 FAT32 (LBA)
03:36 PM Tom_dev: /dev/sdd2 532480 124735487 124203008 59.2G 83 Linux
03:36 PM Tom_dev: as such
03:37 PM Tom_dev: i compared that to a working sd
03:38 PM Tom_dev: you can create that with fdisk /dev/sdX but need to have the build do it
04:16 PM -!- #linuxcnc-devel mode set to +v by ChanServ
05:47 PM -!- #linuxcnc-devel mode set to +v by ChanServ
05:50 PM Tom_itx is now known as Tom_L
06:09 PM -!- #linuxcnc-devel mode set to +v by ChanServ
06:10 PM Tom_dev: tried installing the raspi-firmware
06:10 PM Tom_dev: E: raspi-firmware: installed raspi-firmware package post-installation script subprocess returned error exit status 1
06:10 PM Tom_dev: E: initramfs-tools: installed initramfs-tools package post-installation script subprocess returned error exit status 1
06:13 PM Tom_dev: pere, http://tom-itx.no-ip.biz:81/~webpage/cnc/live-build/raspi-firmware-error.txt
07:26 PM -!- #linuxcnc-devel mode set to +v by ChanServ
07:26 PM -!- #linuxcnc-devel mode set to +v by ChanServ
07:54 PM -!- #linuxcnc-devel mode set to +v by ChanServ
07:54 PM -!- #linuxcnc-devel mode set to +v by ChanServ
09:13 PM -!- #linuxcnc-devel mode set to +v by ChanServ
10:04 PM pere: Tom_L: "Error: missing /boot/firmware, did you forget to mount it?" tell me we need to do something about the disk structure up front.