Turris Build issueshttps://gitlab.nic.cz/turris/os/build/-/issues2023-08-16T10:56:03+02:00https://gitlab.nic.cz/turris/os/build/-/issues/321Update libblkid to 2.372023-08-16T10:56:03+02:00Michal NazarewiczUpdate libblkid to 2.37Would it be possible to get libblkid to 2.37?
Specifically, I care about [a commit which makes Atari partition detection more robust](https://github.com/util-linux/util-linux/commit/282ceadc3a72fc07dd0388b8880fd751490bb87f).
My Omnia w...Would it be possible to get libblkid to 2.37?
Specifically, I care about [a commit which makes Atari partition detection more robust](https://github.com/util-linux/util-linux/commit/282ceadc3a72fc07dd0388b8880fd751490bb87f).
My Omnia with TurrisOS 5.3.3 started recognising one of my partitions as Atari partition:
[omnia]# blkid /dev/md0
/dev/md0: PTTYPE="atari"
This wouldn’t be a huge issue except that it’s a plain encrypted partition and cryptsetup refuses to open it without human confirmation:
WARNING: Device /dev/md0 already contains a 'atari' partition signature.
WARNING!
========
Detected device signature(s) on /dev/md0. Proceeding further may damage existing data.
Are you sure? (Type uppercase yes): YES
This still wouldn’t be a huge issue except my [router started rebooting randomly every couple of days](https://forum.turris.cz/t/turrisos-5-3-3-randomly-reboots/16498) so now every day or so I need to log into the router to mount the partition.https://gitlab.nic.cz/turris/os/build/-/issues/311Wrong order of ethernet ports on Turris 1.x on TOS 5.3.22021-12-09T17:54:07+01:00Stepan RechnerWrong order of ethernet ports on Turris 1.x on TOS 5.3.2On a freshly installed TOS 5.3.2 from medkit on Turris 1.1 the order of ports is inverse in the `Interfaces` tab in reForis to the labels on the physical box.
cc: @mhruseckyOn a freshly installed TOS 5.3.2 from medkit on Turris 1.1 the order of ports is inverse in the `Interfaces` tab in reForis to the labels on the physical box.
cc: @mhruseckyhttps://gitlab.nic.cz/turris/os/build/-/issues/176luci fails with JSON cyclic structure error after initial wizard setup2023-08-16T10:58:54+02:00Michael Richardsonluci fails with JSON cyclic structure error after initial wizard setup# Summary
This is probably the wrong repo to report this, but gitlab.nic.cz doesn't have a luci repo, and this is certainly something wrong in some interaction between reForis and luci.
When I go into: https://n6416fd.r.dasblinkenled.o...# Summary
This is probably the wrong repo to report this, but gitlab.nic.cz doesn't have a luci repo, and this is certainly something wrong in some interaction between reForis and luci.
When I go into: https://n6416fd.r.dasblinkenled.org/cgi-bin/luci/admin/network/network
and select "Edit" on any of the network interfaces, I get an error:
TypeError
JSON.stringify cannot serialize cyclic structures.
This only thing that has been doing anything to the configuration is reForis (Turris 5.1.0).
I therefore suspect something inside uci has gotten confused.
This is a JS error
# Steps To Reproduce
1. flash MEDKIT
2. go through configuration wizard, setup LAN/WAN, setup Wifi and guest_wifi
3. go into Luci (was wondering why guest_wifi did not get IPv6 ULA)
# Expected Result
Luci should open Interface editor
# Actual Result
JSON.stringify cannon serialize cyclic structures.
I will see what other builds exhibit this problem.https://gitlab.nic.cz/turris/os/build/-/issues/145foris & luci unreachable on 5.02020-05-14T17:22:28+02:00Claude Nobsforis & luci unreachable on 5.0some recent update broke foris & luci (but not reforis) on my turris omnia.
current version:
TurrisOS 5.0.0 a8c92e9eda1f9f801345255eac80bf16f65f6f4c
# symptoms
foris would just not show up
luci, after a long time shows :
`/usr/lib/lu...some recent update broke foris & luci (but not reforis) on my turris omnia.
current version:
TurrisOS 5.0.0 a8c92e9eda1f9f801345255eac80bf16f65f6f4c
# symptoms
foris would just not show up
luci, after a long time shows :
`/usr/lib/lua/luci/dispatcher.lua:426: /etc/config/luci seems to be corrupt, unable to find section 'main'`
# solution
`ln -sfn /usr/bin/python3 /usr/bin/python`
don't know whether that fix solves the issue or is just a workaround. but hey it works.Turris OS 5.0Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/build/-/issues/138Cannot install less2023-08-16T11:04:09+02:00Leonardo Brondani SchenkelCannot install lessTurrisOS 5.0.0 (but happened on earlier versions as well)
```
# opkg install less
Installing less (530-1.0) to root...
Downloading https://repo.turris.cz/hbt/omnia/packages/packages/less_530-1_arm_cortex-a9_vfpv3.ipk
Collected errors:
...TurrisOS 5.0.0 (but happened on earlier versions as well)
```
# opkg install less
Installing less (530-1.0) to root...
Downloading https://repo.turris.cz/hbt/omnia/packages/packages/less_530-1_arm_cortex-a9_vfpv3.ipk
Collected errors:
* check_data_file_clashes: Package less wants to install file /bin/less
But that file is already provided by package * busybox
* opkg_install_cmd: Cannot install package less.
```
Shouldn't be this be using the alternative system as mentioned in https://gitlab.labs.nic.cz/turris/turris-os-packages/issues/579?https://gitlab.nic.cz/turris/os/build/-/issues/136busybox collision with binutils2023-08-16T11:04:11+02:00Ghost Userbusybox collision with binutilsexhibits on
> {"kernel":"4.19.93","hostname":"to","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"cznic,turris-omnia","release":{"distribution":"TurrisOS","version":"6.0-future","revision":"a52af5d","target":...exhibits on
> {"kernel":"4.19.93","hostname":"to","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"cznic,turris-omnia","release":{"distribution":"TurrisOS","version":"6.0-future","revision":"a52af5d","target":"mvebu/cortexa9","description":"TurrisOS 6.0-future 7936cb94a930dcff0d30d294efb693648e1768ff"}}
and
>{"kernel":"4.14.172","hostname":"to","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"cznic,turris-omnia","release":{"distribution":"TurrisOS","version":"5.1.0","revision":"5b9b833","target":"mvebu/cortexa9","description":"TurrisOS 5.1.0 5b9b833f8c4dc973f557e90f1038d7d3f1d2042b"}}
___
trying to install *gcc* package terminates with
>Checking for file collisions between packages
>line not found
>line not found
>line not found
>line not found
>line not found
>line not found
>DIE:
>[string "transaction"]:328: [string "transaction"]:153: Collisions:
>• /bin/strings: busybox (existing-file), binutils (new-file)Turris OS 5.0https://gitlab.nic.cz/turris/os/build/-/issues/133Remove sysupgrade2023-08-16T11:03:45+02:00Josef SchlehoferRemove sysupgradeSysupgrade is present in Turris OS 5.0+. We should remove it. It is a dangerous to have it in system.
Reported here and confirmed: https://forum.turris.cz/t/bricked-turris-omnia-after-turris-os-5-0-sysupgrade-openwrt-19-07-2/12558?u=pepeSysupgrade is present in Turris OS 5.0+. We should remove it. It is a dangerous to have it in system.
Reported here and confirmed: https://forum.turris.cz/t/bricked-turris-omnia-after-turris-os-5-0-sysupgrade-openwrt-19-07-2/12558?u=pepeTurris OS 5.0Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/build/-/issues/132Several packages are not compiled as ld cannot find -lintl2020-07-23T15:25:10+02:00Josef SchlehoferSeveral packages are not compiled as ld cannot find -lintlA few packages, which currently fails: modemmanager, gkrellmd, quasselc for all of our builds for Turris 1.x, Turris Omnia and Turris MOX.
Log:
```
/path-omnia/build/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-7.5.0_musl_eabi/lib/gc...A few packages, which currently fails: modemmanager, gkrellmd, quasselc for all of our builds for Turris 1.x, Turris Omnia and Turris MOX.
Log:
```
/path-omnia/build/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-7.5.0_musl_eabi/lib/gcc/arm-openwrt-linux-muslgnueabi/7.5.0/../../../../arm-openwrt-linux-muslgnueabi/bin/ld: cannot find -lintl
collect2: error: ld returned 1 exit status
Makefile:505: recipe for target 'test-qcdm' failed
make[6]: *** [test-qcdm] Error 1
make[6]: Leaving directory '/path-omnia/build/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/ModemManager-1.12.4/libqcdm/tests'
Makefile:426: recipe for target 'all-recursive' failed
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory '/path-omnia/build/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/ModemManager-1.12.4/libqcdm'
Makefile:503: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory '/path-omnia/build/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/ModemManager-1.12.4'
Makefile:435: recipe for target 'all' failed
```Turris OS 5.0.4https://gitlab.nic.cz/turris/os/build/-/issues/125Turris 1.x: no interfaces for DSA switch chip2020-03-04T12:32:37+01:00Karel KociTurris 1.x: no interfaces for DSA switch chipOn HBL there are no LAN interfaces from DSA managed switch chip.On HBL there are no LAN interfaces from DSA managed switch chip.Turris OS 5.0https://gitlab.nic.cz/turris/os/build/-/issues/124Turris 1.x: fails to boot2021-07-28T14:03:28+02:00Karel KociTurris 1.x: fails to bootBooting Turris 1.x in HBL fails to continue. Last message is warning.
```
Hit any key to stop autoboot: 0
BOOT NAND
reading zImage
4310887 bytes read in 197 ms (20.9 MiB/s)
wdt status 00000003
reading fdt
13241 bytes read in 14 ms (92...Booting Turris 1.x in HBL fails to continue. Last message is warning.
```
Hit any key to stop autoboot: 0
BOOT NAND
reading zImage
4310887 bytes read in 197 ms (20.9 MiB/s)
wdt status 00000003
reading fdt
13241 bytes read in 14 ms (922.9 KiB/s)
WARNING: adjusting available memory to 30000000
## Booting kernel from Legacy Image at 02100000 ...
Image Name: Linux-4.14.171
Created: 2020-03-03 0:13:45 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 4310823 Bytes = 4.1 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 02000000
Booting using the fdt blob at 0x2000000
Uncompressing Kernel Image ... OK
Loading Device Tree to 03ff9000, end 03fff3b8 ... OK
WARNING: could not find compatible node fsl-usb2-dr
```
The question is why it fails to boot. It seems to correctly load everything but kernel just prints only this warning and that is it.Turris OS 5.0https://gitlab.nic.cz/turris/os/build/-/issues/123HBL: Package perf is not compiled2020-03-04T22:17:39+01:00Michael RichardsonHBL: Package perf is not compiledOn an Ubuntu 18.04 LTS host (EC2), with hbl checked out, after running `compile_pkgs prepare_tools -t omnia `
successfully, a build fails with:
```
Makefile.config:304: *** No gnu/libc-version.h found, please install glibc-dev[el]. St...On an Ubuntu 18.04 LTS host (EC2), with hbl checked out, after running `compile_pkgs prepare_tools -t omnia `
successfully, a build fails with:
```
Makefile.config:304: *** No gnu/libc-version.h found, please install glibc-dev[el]. Stop.
Makefile.perf:203: recipe for target 'sub-make' failed
make[4]: *** [sub-make] Error 2
Makefile:76: recipe for target '/home/ubuntu/turris-build/build/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/linux-mvebu_cortexa9/linux-4.14.171/tools/perf-target-arm_cortex-a9+vfpv3_musl_eabi/.built' failed
make[3]: *** [/home/ubuntu/turris-build/build/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/linux-mvebu_cortexa9/linux-4.14.171/tools/perf-target-arm_cortex-a9+vfpv3_musl_eabi/.built] Error 2
```
I will attempt again after cleaning the build directory again.
I tried hbl, after failing repeatedly with hbk, and 4.0.5.https://gitlab.nic.cz/turris/os/build/-/issues/121Package mariadb-server requires package libaio that is not available2023-08-16T11:05:28+02:00Karel KociPackage mariadb-server requires package libaio that is not availableTurris OS 5.0https://gitlab.nic.cz/turris/os/build/-/issues/120Requested package lvm2 that is not available2023-08-16T11:05:31+02:00Karel KociRequested package lvm2 that is not availableTurris OS 5.0https://gitlab.nic.cz/turris/os/build/-/issues/119Package tvheadend requires package libx264 that is not available2020-03-09T19:06:22+01:00Karel KociPackage tvheadend requires package libx264 that is not availableTurris OS 5.0https://gitlab.nic.cz/turris/os/build/-/issues/116Installation of pkglist hardening results in router softblock2023-08-16T11:07:21+02:00Karel KociInstallation of pkglist hardening results in router softblockInstalling hardening I managed to get system to state where most of the processes were failing to run correctly. Router was clearly running but processes such as lighttpd or dnsmasq were taking together full system load and router was ac...Installing hardening I managed to get system to state where most of the processes were failing to run correctly. Router was clearly running but processes such as lighttpd or dnsmasq were taking together full system load and router was accessible only trough console. It is possible that processes as SSH were affected by that as well and something prevented them to run correctly. I had to do forced reboot (`/proc/sysrq-trigger`). After that reboot issue was gone.
I suspect that problem is with initial installation of hardening components to running system and application of them on first boot.Turris OS 5.0.1Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/build/-/issues/111Borked update of libubox causes procd crash but fixes security issue2023-08-16T11:03:51+02:00Karel KociBorked update of libubox causes procd crash but fixes security issueOpenWrt updated in 19.07 libubox and introduced bug that can be invoked by using `procd_add_param pidfile` in init file. This causes in some cases crash of procd.
Initially we fixed it by reverting it but it is required for security fix...OpenWrt updated in 19.07 libubox and introduced bug that can be invoked by using `procd_add_param pidfile` in init file. This causes in some cases crash of procd.
Initially we fixed it by reverting it but it is required for security fix in ucert. We do not want to revert ucert as well but it fails to build otherwise.Turris OS 5.0https://gitlab.nic.cz/turris/os/build/-/issues/110Package LXC fails to build2020-01-16T14:28:16+01:00Karel KociPackage LXC fails to buildFailed to build with:
```
OpenWrt-libtool: compile: ccache_cc -DHAVE_CONFIG_H -I. -I../../src -I/home/beast/beast/workspace/turris-os-packages-kittens-omnia/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/usr/include -I/home/bea...Failed to build with:
```
OpenWrt-libtool: compile: ccache_cc -DHAVE_CONFIG_H -I. -I../../src -I/home/beast/beast/workspace/turris-os-packages-kittens-omnia/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/usr/include -I/home/beast/beast/workspace/turris-os-packages-kittens-omnia/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/include -I/home/beast/beast/workspace/turris-os-packages-kittens-omnia/build/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-7.3.0_musl_eabi/usr/include -I/home/beast/beast/workspace/turris-os-packages-kittens-omnia/build/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-7.3.0_musl_eabi/include/fortify -I/home/beast/beast/workspace/turris-os-packages-kittens-omnia/build/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-7.3.0_musl_eabi/include -fPIC -DPIC -DLXCROOTFSMOUNT=\"/usr/lib/lxc/rootfs\" -DLXCPATH=\"/srv/lxc\" -DLXC_GLOBAL_CONF=\"/etc/lxc/lxc.conf\" -DLXCINITDIR=\"/usr/lib\" -DLIBEXECDIR=\"/usr/lib\" -DLXCTEMPLATEDIR=\"/usr/share/lxc/templates\" -DLXCTEMPLATECONFIG=\"/usr/share/lxc/config\" -DLOGPATH=\"/var/log/lxc\" -DLXC_DEFAULT_CONFIG=\"/etc/lxc/default.conf\" -DLXC_USERNIC_DB=\"/var/run/lxc/nics\" -DLXC_USERNIC_CONF=\"/etc/lxc/lxc-usernet\" -DDEFAULT_CGROUP_PATTERN=\"lxc/%n\" -DRUNTIME_PATH=\"/var/run\" -DSBINDIR=\"/usr/sbin\" -I ../../src -I ../../src/lxc -I ../../src/lxc/storage -I ../../src/lxc/cgroups -DHAVE_SECCOMP -I/home/beast/beast/workspace/turris-os-packages-kittens-omnia/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/usr/include -pthread -Os -pipe -mcpu=cortex-a9 -mfpu=vfpv3-d16 -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable -Wno-error=unused-result -mfloat-abi=hard -iremap/home/beast/beast/workspace/turris-os-packages-kittens-omnia/build/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/lxc-3.0.3:lxc-3.0.3 -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro -fdiagnostics-color -Wimplicit-fallthrough -Wcast-align -fno-strict-aliasing -fstack-protector-strong -g -Werror=implicit-function-declaration -Wvla -std=gnu11 -Werror -MT liblxc_la-seccomp.lo -MD -MP -MF .deps/liblxc_la-seccomp.Tpo -c seccomp.c -fPIC -DPIC -o .libs/liblxc_la-seccomp.o
In file included from �[01m�[Kseccomp.c:28:0�[m�[K:
�[01m�[K/home/beast/beast/workspace/turris-os-packages-kittens-omnia/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/usr/include/seccomp.h:705:10:�[m�[K �[01;31m�[Kfatal error: �[m�[Kseccomp-syscalls.h: No such file or directory
#include �[01;31m�[K<seccomp-syscalls.h>�[m�[K
�[01;31m�[K^~~~~~~~~~~~~~~~~~~~�[m�[K
compilation terminated.
```Turris OS 4.0.5https://gitlab.nic.cz/turris/os/build/-/issues/104Turris 1.x - flooding syslog with mmcblk0: error -84 transferring data and mm...2020-01-15T10:46:50+01:00Josef SchlehoferTurris 1.x - flooding syslog with mmcblk0: error -84 transferring data and mmc0: Internal clock never stabilised.I have been running HBK branch on Turris 1.1 for some time, but with the recent builds, my syslog is flooded with those messages:
```
Jan 7 20:59:48 turris kernel: [93318.602435] mmcblk0: error -84 transferring data, sector 903456, nr...I have been running HBK branch on Turris 1.1 for some time, but with the recent builds, my syslog is flooded with those messages:
```
Jan 7 20:59:48 turris kernel: [93318.602435] mmcblk0: error -84 transferring data, sector 903456, nr 64, cmd response 0x900, card status 0xc00
Jan 7 20:59:48 turris kernel: [93318.632515] mmc0: Internal clock never stabilised.
```
So, I thought this is microSD card issue as it happened on one our routers at work, which was running HBD. I removed the microSD card, insert there a new one, flashed it with HBS branch and it was running for an hour flawlessly. I used `switch-branch` to `hbk` and my router almost does not want to boot up, because those messages were back.Turris OS 4.0.5https://gitlab.nic.cz/turris/os/build/-/issues/101kresd on 5.0-dev does not forward requests to the selected server2023-08-16T11:05:36+02:00Giuseppe Piscitellikresd on 5.0-dev does not forward requests to the selected serverI'm using Turris OS 5.0-dev on Omnia. Although it chooses a server from the list of those in Foris / DNS to forward my DNS queries, they continue to be resolved by my ISP's servers. I enclose two screenshots: in the first one we see that...I'm using Turris OS 5.0-dev on Omnia. Although it chooses a server from the list of those in Foris / DNS to forward my DNS queries, they continue to be resolved by my ISP's servers. I enclose two screenshots: in the first one we see that the configuration (in the example with Cloudflare) is correctly loaded in kresd; in the other, we see that by performing a test on dnsleaktest.com the server used is that of Telecom Italia (my ISP).
In addition, using reForis and opening the DNS tab, I see an error, which could be related to the bug above.![Schermata_del_2019-12-13_17-19-33](/uploads/3ce8d8c015b057f921d4dbda4a332bf2/Schermata_del_2019-12-13_17-19-33.png)![Schermata_del_2019-12-13_17-20-15](/uploads/4a50adf486266a26f9349b8e10bb0423/Schermata_del_2019-12-13_17-20-15.png)![Schermata_del_2019-12-13_15-47-50](/uploads/026f1bd7943d9d502e89ebd14cd79098/Schermata_del_2019-12-13_15-47-50.png)Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/build/-/issues/98OpenWrt 19.07 does not provide Mozilla-iot-gateway2023-08-16T11:04:17+02:00Karel KociOpenWrt 19.07 does not provide Mozilla-iot-gatewayOpenWrt 19.07 no longer contains mozzila-iot-gateway but we have patches to make it work.
Should we maintain it in upstream or should we drop it?
For now the patches were removed from tree for `v5.0`+.OpenWrt 19.07 no longer contains mozzila-iot-gateway but we have patches to make it work.
Should we maintain it in upstream or should we drop it?
For now the patches were removed from tree for `v5.0`+.