#apertus IRC Channel Logs

se6astian: could you invertigate the github webhook again?

I am happy to

https://lab.apertus.org/T697#12378

{"error":"404 Not Found"}

ah, now i see that a parameter is missing, already wondered

jup

saved

or should I just push a temp file?

worked

nice :)

yeah the trigger was triggered sucessfully

perfect

nice one

*too many

I think gitlab can handle "many" build runs fine

they esentially dont care. Once I ran like 20 build jobs in paralell... its ok

😂

hm... maybe its a bit to early for this. Lets first build a stable and mature image :)

the install script should already contain the important steps

just try calling your install script in the build_tools/inner/install.sh

then build the image with the build instructions and try wether it succeeds

testing is a bit difficult, don't have the hardware here, but maybe se6astian can assist with swapping the firmware on the microzed test board when the daemon is ready

bertl said yesterday, that the image is not yet booting on real hardware

ah, good to know, what about QEMU, any news on that part?

you can build qemu (with build_tools/outer/build_qemu.sh) and then start it using the spawn command from build_tools/outer/run_qemu.expect

jarhab[m]: did you get an error log from the bootprocess from bertl

if it makes sense

se6astian: bertl send me a log, yes

morning folks!

Bertl: do you have a link to a working BOOT.bin?

http://vserver.13thfloor.at/Stuff/AXIOM/BETA/beta_20170109.dd.xz

could you upload a plain BOOT.bin to 13thfloor?

do you mean errors like `File /usr/lib/systemd/system/systemd-journald.service:33 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.

yes

jarhab[m]: can you build u-boot already?

but i could

okay, that would be great

but we should definitely use our configuration for the build

where do i find the configs for u-boot and the kernel?

but it would probably make sense to have them in a dedicated place on github

and uEnv file

and I lied, we are already using xilinx u-boot

ok how do you merge the u-boot elf and the fsbl?

this requires the bootgen utility which combines the elf files into boot.bin

when checking the image yesterday, I saw that scripts and binaries got thrown together in /usr/local/bin, prefixed with axiom- and stripped of any extension, why's that?

you could just type axiom-<tab> and see all the scripts

okay, we should probably break them up into /usr/local/bin and /usr/local/script and keep extensions like .sh and .py

makes sense

pathes need to be adjusted in the scripts, but that's another topic

and all the scripts, that need the funcs change into their real dir (see https://github.com/apertus-open-source-cinema/beta-software/commit/acb0cf2834b031a18a3d494053547df372ff08a7)

hm... ok

probably

ah, bit.func seems to be missing, which is included from i2c.func

I see ...

good night