Turris Build issueshttps://gitlab.nic.cz/turris/os/build/-/issues2019-05-07T13:53:14+02:00https://gitlab.nic.cz/turris/os/build/-/issues/13Device tree patching fails if SFP module is connected as first module2019-05-07T13:53:14+02:00Karel KociDevice tree patching fails if SFP module is connected as first moduleI connected SFP module as only module to Mox and it fails to start with following error in U-boot.
```
U-Boot 2018.11 (Dec 03 2018 - 09:33:41 +0000)
DRAM: 512 MiB
Enabling Armada 3720 wComphy-0: SGMII1 1.25 Gbps
Comphy-1: PEX0 ...I connected SFP module as only module to Mox and it fails to start with following error in U-boot.
```
U-Boot 2018.11 (Dec 03 2018 - 09:33:41 +0000)
DRAM: 512 MiB
Enabling Armada 3720 wComphy-0: SGMII1 1.25 Gbps
Comphy-1: PEX0 5 Gbps
Comphy-2: USB3_HOST0 5 Gbps
MMC: sdhci@d8000: 0
Loading Environment from SPI Flash... SF: Detected w25q64dw with page size 256 Bytes, erase size 4 KiB, total 8 MiB
OK
Model: CZ.NIC Turris Mox Board
Net: eth0: neta@30000
Turris Mox:
Board version: 22
RAM size: 512 MiB
Serial Number: 0000000D3000001B
ECDSA Public Key: 030149fd703bed9cbd664723986eaf76a2e4c1ef45ccb845dda2dab5b21ed0605b5a75abd9577d9bb29f0a88fc9d9c4d034dbb20332152075ede0c7199e0e8d9d2bc70
SD/eMMC version: SD
Module Topology:
1: SFP Module
Hit any key to stop autoboot: 0
gpio: pin GPIO221 (gpio 57) value is 0
gpio: pin GPIO220 (gpio 56) value is 1
SF: Detected w25q64dw with page size 256 Bytes, erase size 4 KiB, total 8 MiB
device 0 offset 0x7f0000, size 0x10000
SF: 65536 bytes @ 0x7f0000 Read: OK
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
403 bytes read in 72 ms (4.9 KiB/s)
## Executing script at 04d00000
9959432 bytes read in 482 ms (19.7 MiB/s)
19292 bytes read in 66 ms (285.2 KiB/s)
## Flattened Device Tree blob at 04f00000
Booting using the fdt blob at 0x4f00000
Loading Device Tree to 000000001bf14000, end 000000001bf1bb5b ... OK
ERROR: board-specific fdt fixup failed: FDT_ERR_NOTFOUND
- must RESET the board to recover.
FDT creation failed! hanging...### ERROR ### Please RESET the board ###
```Turris OS 4.0Marek BehunMarek Behunhttps://gitlab.nic.cz/turris/os/build/-/issues/12SFP port on Turris Omnia does not work2019-05-07T13:53:14+02:00Karel KociSFP port on Turris Omnia does not workThere seems to be some problem with SFP on Omnia. It is not detected correctly and reports errors.
This was initially reported on forum: https://forum.turris.cz/t/turris-os-4-0-alpha4-is-out/9836/22
I reproduced it successfully with di...There seems to be some problem with SFP on Omnia. It is not detected correctly and reports errors.
This was initially reported on forum: https://forum.turris.cz/t/turris-os-4-0-alpha4-is-out/9836/22
I reproduced it successfully with different SFP module.
```
[ 4.716114] mdio_bus f1072004.mdio-mii: /soc/internal-regs/mdio@72004/sfp has invalid PHY address
[ 4.725015] mdio_bus f1072004.mdio-mii: scan phy sfp at address 0
[ 4.731127] mdio_bus f1072004.mdio-mii: scan phy sfp at address 1
[ 4.737241] mdio_bus f1072004.mdio-mii: scan phy sfp at address 2
[ 4.743354] mdio_bus f1072004.mdio-mii: scan phy sfp at address 3
```
Scan goes up to address 31 and then stops.Turris OS 4.0https://gitlab.nic.cz/turris/os/build/-/issues/30block-mount fstab service causes unmount of all FSs2019-06-05T13:29:45+02:00Karel Kociblock-mount fstab service causes unmount of all FSsRunning `/etc/init.d/fstab restart` causes all FSs to be unmounted and not mounted back. This is because it does not have reboot section so default one is provided. That one just calls `stop` and `start` in sequence. Problem is that `sto...Running `/etc/init.d/fstab restart` causes all FSs to be unmounted and not mounted back. This is because it does not have reboot section so default one is provided. That one just calls `stop` and `start` in sequence. Problem is that `stop` unmounts all FSs but `start` just prints message that `fstab` init script is obsoleted.
This is problematic because as part of update process we restart services. Restart of this service then causes just unmount of all additional FSs.Turris OS 4.0https://gitlab.nic.cz/turris/os/build/-/issues/34[lxc] Failed to download http://repo.turris.cz/lxc//meta/1.0/index-user2019-06-06T16:01:54+02:00Ghost User[lxc] Failed to download http://repo.turris.cz/lxc//meta/1.0/index-user{"kernel":"4.14.123","hostname":"to","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"armada-385-turris-omnia","release":{"distribution":"TurrisOS","version":"4.0-beta2","revision":"758d612","target":"mvebu\/co...{"kernel":"4.14.123","hostname":"to","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"armada-385-turris-omnia","release":{"distribution":"TurrisOS","version":"4.0-beta2","revision":"758d612","target":"mvebu\/cortexa9","description":"TurrisOS 4.0-beta2 758d612"}}
___
container creation from http://repo.turris.cz/lxc fails with
> Setting up the GPG keyring
> Downloading the image index
> ERROR: Failed to download http://repo.turris.cz/lxc//meta/1.0/index-user
There seems to be a mismatch (index-**user** vs index-**system**), least when browsing the directory
![directory](/uploads/2c71401a8675d13e70c494ec0c2bfe31/directory.png)https://gitlab.nic.cz/turris/os/build/-/issues/19Syslog spammed with promiscuous mode messages2019-06-07T14:38:39+02:00Vojtech MyslivecSyslog spammed with promiscuous mode messages## Affected devices:
* MOX
## Affected HW combinations:
* MOX A + MOX B + MOX C
* MOX A + MOX E
## TurrisOS branch + date:
* HBS - 2019-03-10 (alfa 2)
* HBD - 2019-03-14
## Affected SW component (best guess)
* kernel / network config...## Affected devices:
* MOX
## Affected HW combinations:
* MOX A + MOX B + MOX C
* MOX A + MOX E
## TurrisOS branch + date:
* HBS - 2019-03-10 (alfa 2)
* HBD - 2019-03-14
## Affected SW component (best guess)
* kernel / network configuration
## Detailed description
Kernel spam syslog with *promiscuous mode* messages off `br-guest_turris` interface. There is always "on" and "off" consecutive messages circa ten times a second.
### Setup (+stacktraces/screenshots)
*syslog* fragment:
```
Mar 10 13:07:12 turris kernel: [ 2860.424244] device br-guest_turris entered promiscuous mode
Mar 10 13:07:12 turris kernel: [ 2860.494298] device br-guest_turris left promiscuous mode
Mar 10 13:07:12 turris kernel: [ 2861.014159] device br-guest_turris entered promiscuous mode
Mar 10 13:07:13 turris kernel: [ 2861.084074] device br-guest_turris left promiscuous mode
Mar 10 13:07:13 turris kernel: [ 2861.604066] device br-guest_turris entered promiscuous mode
Mar 10 13:07:13 turris kernel: [ 2861.663915] device br-guest_turris left promiscuous mode
```
### Unexpected behaviour
Log is full of useless messages. Changing this states probably slow down CPU/kernel from useful work (such as routing :slight\_smile: )
### Expected behaviour
Promiscuous mode is not changed so often or not at all.Turris OS 4.0https://gitlab.nic.cz/turris/os/build/-/issues/37Cannot save LAN settings if the last octet exceeds 222019-06-19T17:00:47+02:00Ghost UserCannot save LAN settings if the last octet exceeds 22Tested in v3.11.4 and does not work in 4b2 either. More info in https://forum.turris.cz/t/cannot-save-any-lan-settings/10341.Tested in v3.11.4 and does not work in 4b2 either. More info in https://forum.turris.cz/t/cannot-save-any-lan-settings/10341.Štěpán HenekŠtěpán Henekhttps://gitlab.nic.cz/turris/os/build/-/issues/24mv88e6xxx SMI leak warning2019-07-10T06:00:11+02:00Ghost Usermv88e6xxx SMI leak warning> {"kernel":"4.14.121","hostname":"to","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"armada-385-turris-omnia","release":{"distribution":"TurrisOS","version":"4.0-beta2","revision":"07918c2","target":"mvebu\/...> {"kernel":"4.14.121","hostname":"to","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"armada-385-turris-omnia","release":{"distribution":"TurrisOS","version":"4.0-beta2","revision":"07918c2","target":"mvebu\/cortexa9","description":"TurrisOS 4.0-beta2 07918c2"}}
___
> [ 4.432488] libphy: mv88e6xxx SMI: probed
> [ 4.437412] ------------[ cut here ]------------
> [ 4.442061] WARNING: CPU: 0 PID: 1 at fs/proc/generic.c:572 remove_proc_entry+0x140/0x154
> [ 4.450257] remove_proc_entry: removing non-empty directory 'irq/58', leaking at least 'mv88e6xxx-g2'
> [ 4.459501] Modules linked in:
> [ 4.462569] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.14.121 #0
> [ 4.468674] Hardware name: Marvell Armada 380/385 (Device Tree)
> [ 4.474623] [ <c010ed2c> ] (unwind_backtrace) from [<c010a9fc>] (show_stack+0x10/0x14)
> [ 4.482391] [ <c010a9fc> ] (show_stack) from [<c0793488>] (dump_stack+0x88/0x9c)
> [ 4.489634] [ <c0793488> ] (dump_stack) from [<c0121c94>] (__warn+0xe4/0x100)
> [ 4.496613] [ <c0121c94> ] (__warn) from [<c0121ce8>] (warn_slowpath_fmt+0x38/0x48)
> [ 4.504116] [ <c0121ce8> ] (warn_slowpath_fmt) from [<c0269d5c>] (remove_proc_entry+0x140/0x154)
> [ 4.512752] [ <c0269d5c> ] (remove_proc_entry) from [<c016bfd0>] (unregister_irq_proc+0xcc/0xe8)
> [ 4.521385] [ <c016bfd0> ] (unregister_irq_proc) from [<c01632f4>] (free_desc+0x2c/0x54)
> [ 4.529320] [ <c01632f4> ] (free_desc) from [<c016335c>] (irq_free_descs+0x40/0x74)
> [ 4.536821] [ <c016335c> ] (irq_free_descs) from [<c05b0590>] (mv88e6xxx_g1_irq_free_common+0x4c/0x74)
> [ 4.545975] [ <c05b0590> ] (mv88e6xxx_g1_irq_free_common) from [<c05b0618>] (mv88e6xxx_irq_poll_free+0x2c/0x38)
> [ 4.555914] [ <c05b0618> ] (mv88e6xxx_irq_poll_free) from [<c05b1fac>] (mv88e6xxx_probe+0x318/0x344)
> [ 4.564894] [ <c05b1fac> ] (mv88e6xxx_probe) from [<c051c6ac>] (really_probe+0x114/0x274)
> [ 4.572921] [ <c051c6ac> ] (really_probe) from [<c051aee4>] (bus_for_each_drv+0x44/0x98)
> [ 4.580857] [ <c051aee4> ] (bus_for_each_drv) from [<c051c528>] (__device_attach+0x78/0xe0)
> [ 4.589055] [ <c051c528> ] (__device_attach) from [<c051bb80>] (bus_probe_device+0x28/0x88)
> [ 4.597253] [ <c051bb80> ] (bus_probe_device) from [<c051a040>] (device_add+0x3d0/0x5b4)
> [ 4.605191] [ <c051a040> ] (device_add) from [<c05a8df4>] (mdio_device_register+0x1c/0x44)
> [ 4.613303] [ <c05a8df4> ] (mdio_device_register) from [<c064a140>] (of_mdiobus_register+0x168/0x2b4)
> [ 4.622377] [ <c064a140> ] (of_mdiobus_register) from [<c05b8108>] (orion_mdio_probe+0x204/0x2e8)
> [ 4.631099] [ <c05b8108> ] (orion_mdio_probe) from [<c051dc6c>] (platform_drv_probe+0x34/0x70)
> [ 4.639556] [ <c051dc6c> ] (platform_drv_probe) from [<c051c6ac>] (really_probe+0x114/0x274)
> [ 4.647840] [ <c051c6ac> ] (really_probe) from [<c051c898>] (__driver_attach+0x8c/0xb0)
> [ 4.655689] [ <c051c898> ] (__driver_attach) from [<c051ae38>] (bus_for_each_dev+0x4c/0xa0)
> [ 4.663888] [ <c051ae38> ] (bus_for_each_dev) from [<c051bdbc>] (bus_add_driver+0xe8/0x200)
> [ 4.672084] [ <c051bdbc> ] (bus_add_driver) from [<c051cfdc>] (driver_register+0xa8/0xe4)
> [ 4.680106] [ <c051cfdc> ] (driver_register) from [<c0101b10>] (do_one_initcall+0xc0/0x184)
> [ 4.688306] [ <c0101b10> ] (do_one_initcall) from [<c0a00f30>] (kernel_init_freeable+0x1c0/0x254)
> [ 4.697030] [ <c0a00f30> ] (kernel_init_freeable) from [<c07a6554>] (kernel_init+0x8/0x114)
> [ 4.705228] [ <c07a6554> ] (kernel_init) from [<c0107808>] (ret_from_fork+0x14/0x2c)
> [ 4.712827] ---[ end trace 622458f73aa20313 ]---Marek BehunMarek Behunhttps://gitlab.nic.cz/turris/os/build/-/issues/57Turris Omnia kernel 4.19 support2019-07-31T16:32:53+02:00Karel KociTurris Omnia kernel 4.19 supportUpdate patches for Turris Omnia for kernel 4.19
Upstream set kernel version in master to 4.19 for mvebu architecture. We should follow with that.
Currently we do not have correct device tree because we split it to two device trees. Thi...Update patches for Turris Omnia for kernel 4.19
Upstream set kernel version in master to 4.19 for mvebu architecture. We should follow with that.
Currently we do not have correct device tree because we split it to two device trees. This means that package `omnia-support` fails with following error in master build:
```
install: cannot stat '/home/beast/beast/workspace/turris-os-packages-master-omnia/build/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/linux-mvebu_cortexa9/linux-4.19.56/arch/arm/boot/dts/armada-385-turris-omnia-*.dtb': No such file or directory
```
Porting patches to 4.19 should fix this.https://gitlab.nic.cz/turris/os/build/-/issues/72Updater won't remove packages with webapp2019-09-02T11:53:53+02:00Karel KociUpdater won't remove packages with webappThis is same issue and reason as in https://gitlab.labs.nic.cz/turris/turris-build/issues/70 but for webapp packages.This is same issue and reason as in https://gitlab.labs.nic.cz/turris/turris-build/issues/70 but for webapp packages.Turris OS 4.0https://gitlab.nic.cz/turris/os/build/-/issues/70Updater won't remove Foris or Luci plugins because of language packages2019-09-02T11:54:15+02:00Karel KociUpdater won't remove Foris or Luci plugins because of language packagesThere is a bug with new code introduced in 1e07e9d4c89bfa004dbc9f6e44ba4ccf0e867e2a and 9656c3d85417e9221c87a98dcc4e36708c3fea22. The problem is that it installs translation packages if package is installed but if request to install that...There is a bug with new code introduced in 1e07e9d4c89bfa004dbc9f6e44ba4ccf0e867e2a and 9656c3d85417e9221c87a98dcc4e36708c3fea22. The problem is that it installs translation packages if package is installed but if request to install that package is no longer present it won't remove it nor translation package. That is because it is already installed. Mentioned code results to languages and in proxy installed package is required. That means it is never removed.
The correct behavior should be that if request to that package is dropped then it is removed and languages are removed as well.
This leads to some weak dependencies but we do not have anything like that in updater so we should think about how to do it with what we have in updater.Turris OS 4.0https://gitlab.nic.cz/turris/os/build/-/issues/80fails to build 4.x2019-10-14T13:51:47+02:00Ghost Userfails to build 4.xTried building 4.x which however fails - run in debug mode (-x) and that is the tail end of the log
>make[4]: *** [Makefile:579: scripts] Error 2
>Removing child 0x56223d073370 PID 16016 from chain.
>make[4]: Leaving directory '/s...Tried building 4.x which however fails - run in debug mode (-x) and that is the tail end of the log
>make[4]: *** [Makefile:579: scripts] Error 2
>Removing child 0x56223d073370 PID 16016 from chain.
>make[4]: Leaving directory '/srv/compiled/tos/4/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/linux-mvebu_cortexa9/linux-4.14.137'
>Reaping losing child 0x562cd368f3e0 PID 14715
>make[3]: *** [Makefile:22: /srv/compiled/tos/4/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/linux-mvebu_cortexa9/linux-4.14.137/.modules] Error 2
>Removing child 0x562cd368f3e0 PID 14715 from chain.
>make[3]: Leaving directory '/srv/compiled/tos/4/target/linux/mvebu'
>Reaping losing child 0x5585a94e6920 PID 9658
>make[2]: *** [Makefile:13: compile] Error 2
>Removing child 0x5585a94e6920 PID 9658 from chain.
>make[2]: Leaving directory '/srv/compiled/tos/4/target/linux'
>time: target/linux/compile#35.01#25.67#45.99
>Reaping losing child 0x55cd40eb8650 PID 9650
>make[1]: *** [target/Makefile:25: target/linux/compile] Error 2
>Removing child 0x55cd40eb8650 PID 9650 from chain.
>make[1]: Leaving directory '/srv/compiled/tos/4'
>Reaping losing child 0x55f5ad74e7d0 PID 9624
>make: *** [/srv/compiled/tos/4/include/toplevel.mk:218: target/compile] Error 2
>Removing child 0x55f5ad74e7d0 PID 9624 from chain.
____
Since the verbosity is not very specific of what goes wrong I could only speculate whether one of the reported issues #79 | #78 | #77 could be the cause.
____
the make log [compile.txt](/uploads/6c88f14f856388c53efd00a026dde7fb/compile.txt)https://gitlab.nic.cz/turris/os/build/-/issues/90Kernel for Turris1x fails to mount BTRFS root2019-11-20T10:50:22+01:00Ondřej CaletkaKernel for Turris1x fails to mount BTRFS rootJust tried current `hbk` and `hbl` medkits for Turris 1.0 (using Btrfs on SD card) and the router keeps restarting with kernel panic, because it cannot mount root fs, caused probably by this:
BTRFS error (device mmcblk0p2): superblo...Just tried current `hbk` and `hbl` medkits for Turris 1.0 (using Btrfs on SD card) and the router keeps restarting with kernel panic, because it cannot mount root fs, caused probably by this:
BTRFS error (device mmcblk0p2): superblock checksum mismatch
When rolled back manually to working Turris OS by taking the SD card out and changing `@` snapshot and `zImage`/`fdt` on FAT32 partition, the recovered TurrisOS remounted the root fs to read only due to broken FS. I had to backup all the data and recreate btrfs from scratch.
`hbt` and `hbs` branches are not affected.Turris OS 4.0.2https://gitlab.nic.cz/turris/os/build/-/issues/96HBK: wget is removed by updater2019-11-26T18:40:17+01:00Karel KociHBK: wget is removed by updaterThere seems to be a problem with updater not wanting to install `wget` package.
The combination of these two commits probably caused it: 6425621c66c7aff60a47a95bc0d6cee1e8a4fe73 80f46e2b75fbe2baa4b5ca76dbc42b8e556d5e04There seems to be a problem with updater not wanting to install `wget` package.
The combination of these two commits probably caused it: 6425621c66c7aff60a47a95bc0d6cee1e8a4fe73 80f46e2b75fbe2baa4b5ca76dbc42b8e556d5e04Turris OS 4.0.2https://gitlab.nic.cz/turris/os/build/-/issues/97Omnia reboots when wifi is accessed2019-12-09T16:00:13+01:00Karel KociOmnia reboots when wifi is accessedThere is problem in latest HBK and HBT. Omnia reboots (provably because of kernel panic) when wifi is acessed.
It was reported by users and I (@kkoci) was able to reproduce it as well on my home router.There is problem in latest HBK and HBT. Omnia reboots (provably because of kernel panic) when wifi is acessed.
It was reported by users and I (@kkoci) was able to reproduce it as well on my home router.Turris OS 4.0.2https://gitlab.nic.cz/turris/os/build/-/issues/99A CTI router can't update to TOS 4.0.22019-12-11T15:57:10+01:00Vojtech MyslivecA CTI router can't update to TOS 4.0.2A CTI Omnia router in HBS:
```
root@skolka:~# pkgupdate
INFO:Target Turris OS: 4.0.2
WARN:Package wpad is in cyclic dependency. It might fail its post-install script.
WARN:Package hostapd is in cyclic dependency. It might fail its post...A CTI Omnia router in HBS:
```
root@skolka:~# pkgupdate
INFO:Target Turris OS: 4.0.2
WARN:Package wpad is in cyclic dependency. It might fail its post-install script.
WARN:Package hostapd is in cyclic dependency. It might fail its post-install script.
WARN:Requested package pkglists-l10n-cs that is missing, ignoring as requested.
WARN:Requested package luci-i18n-adblock-en that is missing, ignoring as requested.
WARN:Requested package luci-i18n-adblock-cs that is missing, ignoring as requested.
WARN:Requested package luci-i18n-bcp38-en that is missing, ignoring as requested.
WARN:Requested package luci-i18n-bcp38-cs that is missing, ignoring as requested.
WARN:Requested package luci-i18n-mjpg-streamer-en that is missing, ignoring as requested.
WARN:Requested package luci-i18n-mjpg-streamer-cs that is missing, ignoring as requested.
WARN:Requested package luci-i18n-sqm-en that is missing, ignoring as requested.
WARN:Requested package luci-i18n-sqm-cs that is missing, ignoring as requested.
WARN:Requested package luci-i18n-rainbow-en that is missing, ignoring as requested.
WARN:Requested package luci-i18n-rainbow-cs that is missing, ignoring as requested.
line not found
line not found
line not found
line not found
line not found
ERROR:
inconsistent: Requested package turris-survey that is not available.
```
As the output says, updater tries to install `turris-survey` package, which is not available.Turris OS 4.0.2https://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/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/117Pakon Signature verification failure2020-02-24T16:54:58+01:00Jan HoracekPakon Signature verification failureIt is not possible to update due to broken signature on one HBL user list
runtime: [string "requests"]:417: [string "utils"]:429: Unable to finish URI (https://repo.turris.cz/hbl/omnia/lists/pkglists/pakon.lua): Signature verification f...It is not possible to update due to broken signature on one HBL user list
runtime: [string "requests"]:417: [string "utils"]:429: Unable to finish URI (https://repo.turris.cz/hbl/omnia/lists/pkglists/pakon.lua): Signature verification failureTurris OS 5.0https://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/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.