Turris Build issueshttps://gitlab.nic.cz/turris/os/build/-/issues2021-10-14T11:42:50+02:00https://gitlab.nic.cz/turris/os/build/-/issues/231Generate medkits - pkgupdate can not be found as there are not enough depend...2021-10-14T11:42:50+02:00Josef SchlehoferGenerate medkits - pkgupdate can not be found as there are not enough dependencies installedI'm trying to use generate_medkits, but it seems I don't have installed required dependencies and it fails with such outputs:
```
configure: error: Package requirements (liburiparser >= 0.9) were not met:
No package 'liburiparser' found...I'm trying to use generate_medkits, but it seems I don't have installed required dependencies and it fails with such outputs:
```
configure: error: Package requirements (liburiparser >= 0.9) were not met:
No package 'liburiparser' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
```
and so on.
When I tried to run generate_medkits once again when I installed the dependency it fails with this output:
```
warning: redirecting to https://gitlab.nic.cz/turris/updater/updater.git/
/bin/bash: line 13: /foo/omnia-hbl/turris-tools/updater-ng/pkgupdate: No such file or directory
```
I know that correct solution would be install dependencies from this file https://gitlab.nic.cz/turris/updater/updater/-/blob/master/.gitlab-ci-docker/DockerFile_debian but I'm trying to document usage of generate medkits in README in this repository.
**It helps when I remove folder turris-tools and then I can use generate_medkits once again.**Turris OS 6.0https://gitlab.nic.cz/turris/os/build/-/issues/86File names in medkit hash files2019-11-04T13:39:10+01:00Lukas JelinekFile names in medkit hash filesHash files for medkit symbolic link files (e.g. https://repo.turris.cz/omnia-stable/medkit/omnia-medkit-latest.tar.gz.sha256 for https://repo.turris.cz/omnia-stable/medkit/omnia-medkit-latest.tar.gz) currently contain names of the origin...Hash files for medkit symbolic link files (e.g. https://repo.turris.cz/omnia-stable/medkit/omnia-medkit-latest.tar.gz.sha256 for https://repo.turris.cz/omnia-stable/medkit/omnia-medkit-latest.tar.gz) currently contain names of the original medkit files, not their symbolic link names.
If an user downloads both the medkit and its hash file he may be messed because the hash file contains a "not matching" file name. And, what is worse, he can't simply use something like this:
`sha256sum --check omnia-medkit-latest.tar.gz.sha256`
It should be considered to create separate hash files for medkit symbolic links instead of symbolic links to original hash files.https://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/25hwmon_device_register() is deprecated2019-09-04T22:47:15+02:00Ghost Userhwmon_device_register() is deprecated> {"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/c...> {"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"}}
___
> [ 5.080570] (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().https://gitlab.nic.cz/turris/os/build/-/issues/28[lxc] unprivileged container not booting - rootfs fails mounting2021-05-18T16:51:57+02:00Ghost User[lxc] unprivileged container not booting - rootfs fails mounting> {"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":"ab3fd04","target":"mvebu\/...> {"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":"ab3fd04","target":"mvebu\/cortexa9","description":"TurrisOS 4.0-beta2 ab3fd04"}}
___
* installed are - lxc-unprivileged | shadow-newgidmap | shadow-newuidmap
* in absentia manually created /etc/subgid | /etc/subuid
* exec - `usermod --add-subuids 100000-165536 $USER && usermod --add-subgids 100000-165536 $USER`
* exec - `lxc-checkconfig` [lxc-checkconfig.txt](/uploads/690fb5525e27541df521a50f8b2b32fc/lxc-checkconfig.txt)
* container ubuntu disco created
* added `lxc.idmap = u 0 100000 65536` | `lxc.idmap = g 0 100000 65536` to [container.conf](/uploads/c388c071b44b10e8caf3c3c6e8befacb/container.conf)
___
* exec - `lxc-start test -F -o /logs/lxc/test -l debug` [log.txt](/uploads/7947c8e28842cda76d27b01d439202df/log.txt)
* `dmesg` not reporting anything related to the issue
* container boots with no issues if *privileged*
* `cat /proc/1/mounts` [mounts.text](/uploads/aa45adad744636327790e70862e4f39c/mounts.text)
* kernel conf [config](/uploads/7ff963b82770bf7f1e4270fc00823812/config)
* `stat /usr/lib/lxc/rootfs/`
> File: ‘/usr/lib/lxc/rootfs/’
> Size: 12 Blocks: 0 IO Block: 4096 directory
> Device: 10h/16d Inode: 31359 Links: 1
> Access: (0711/drwx--x--x) Uid: ( 0/ root) Gid: ( 0/ root)
* `cat /proc/self/cgroup`
> 11:debug:/
> 10:rdma:/
> 9:pids:/
> 8:net_cls:/
> 7:freezer:/
> 6:devices:/
> 5:memory:/
> 4:blkio:/
> 3:cpuacct:/
> 2:cpu:/
> 1:cpuset:/
* `ls -al /proc/sys/kernel/| grep unpriv`
> -rw-r--r-- 1 root root 0 Jun 5 12:58 unprivileged_bpf_disabled
https://gitlab.nic.cz/turris/os/build/-/issues/31[lxc] configuring kernel parameters container fails2023-08-16T11:07:31+02:00Ghost User[lxc] configuring kernel parameters container fails> {"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":"e403e59","target":"mvebu\/...> {"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":"e403e59","target":"mvebu\/cortexa9","description":"TurrisOS 4.0-beta2 e403e59"}}
___
It would be expected that `lxc.sysctl.[kernel parameters name]` (https://linuxcontainers.org/lxc/manpages/man5/lxc.container.conf.5.html) to work.
For instance add `lxc.sysctl.net.ipv4.tcp_window_scaling = 1` to the container config and booting a privileged container (in this instance ubuntu disco) and fails
> lxc-start test 20190606080720.800 ERROR conf - conf.c:setup_sysctl_parameters:2638 - Failed to setup sysctl parameters net.ipv4.tcp_window_scaling to 1
> lxc-start test 20190606080720.800 ERROR conf - conf.c:lxc_setup:3670 - Failed to setup sysctl parameters
> lxc-start test 20190606080720.801 ERROR start - start.c:do_start:1263 - Failed to setup container "test"
> lxc-start test 20190606080720.801 ERROR sync - sync.c:__sync_wait:62 - An error occurred in another process (expected sequence number 5)https://gitlab.nic.cz/turris/os/build/-/issues/33Kernel enable CONFIG_ADVISE_SYSCALLS2020-01-08T13:12:07+01:00Jan PavlinecKernel enable CONFIG_ADVISE_SYSCALLSThis could help run docker in lxc container
https://forum.turris.cz/t/docker-on-turris-omnia/242/15
and
https://forum.turris.cz/t/requesting-new-packages-new-versions/4187/32
Enable these kernel configs
* [ ] CONFIG_MEMCG_SWAP_ENABLED...This could help run docker in lxc container
https://forum.turris.cz/t/docker-on-turris-omnia/242/15
and
https://forum.turris.cz/t/requesting-new-packages-new-versions/4187/32
Enable these kernel configs
* [ ] CONFIG_MEMCG_SWAP_ENABLED
* [x] CONFIG_MEMCG_KMEM
* [ ] CONFIG_BLK_DEV_THROTTLING
* [ ] CONFIG_IOSCHED_CFQ
* [ ] CONFIG_CFQ_GROUP_IOSCHED
* [ ] CONFIG_CGROUP_PERF
* [ ] CONFIG_CGROUP_HUGETLB
* [ ] CONFIG_CGROUP_NET_PRIO
* [x] CONFIG_CFS_BANDWIDTH
* [x] CONFIG_FAIR_GROUP_SCHED
* [x] CONFIG_RT_GROUP_SCHEDTurris OS 5.1Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/build/-/issues/40haveged starts too late2020-03-26T11:16:00+01:00Rosen Penevhaveged starts too lateI currently get this when booting my Omnia:
```
[ 6.508803] random: fast init done
[ 9.188468] random: jshn: uninitialized urandom read (4 bytes read)
[ 9.204723] random: jshn: uninitialized urandom read (4 bytes read)
[ 9.2...I currently get this when booting my Omnia:
```
[ 6.508803] random: fast init done
[ 9.188468] random: jshn: uninitialized urandom read (4 bytes read)
[ 9.204723] random: jshn: uninitialized urandom read (4 bytes read)
[ 9.219385] random: jshn: uninitialized urandom read (4 bytes read)
[ 12.865649] urandom_read: 2 callbacks suppressed
[ 12.865652] random: procd: uninitialized urandom read (4 bytes read)
[ 13.056906] urandom-seed: Seeding with /etc/urandom.seed
[ 13.698772] random: ubusd: uninitialized urandom read (4 bytes read)
[ 13.744295] random: ubusd: uninitialized urandom read (4 bytes read)
[ 16.794904] random: crng init done
[ 16.798318] random: 2 urandom warning(s) missed due to ratelimiting
```
The upstream solution uses an alternative to haveged that has START specified to 00 whereas haveged starts at 13. I have no idea how safe or unsafe it is to start haveged earlier.https://gitlab.nic.cz/turris/os/build/-/issues/42sysntpd working?2023-08-16T11:07:38+02:00Ghost Usersysntpd working?{"kernel":"4.14.113","hostname":"to","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"armada-385-turris-omnia","release":{"distribution":"TurrisOS","version":"4.0-beta1","revision":"0663455801","target":"mvebu/...{"kernel":"4.14.113","hostname":"to","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"armada-385-turris-omnia","release":{"distribution":"TurrisOS","version":"4.0-beta1","revision":"0663455801","target":"mvebu/cortexa9","description":"TurrisOS 4.0-beta1 0663455801"}}
- using `odhcpd` for ipv4 and ipv6
___
forum cross refrence https://forum.turris.cz/t/turris-os-4-0-beta1-is-released/10107/76
I am concerned that `sysntpd` is not working, both client and server.
With the client side, which is most important, there is no indication in the logs that the time is being synchronized with the specified upstream servers, e.g. via /foris/config/main/time/ > Update Time.
Is there any way via cli to run the client and see the output, could not find any pertaining documentation? Or any other way to know that client is working or when last sync happened?
___
With the server side up/running
`ss -tulpn | grep ntp`
> udp UNCONN 0 0 *:123 : users:((“ntpd”,pid=10918,fd=3))
`ntpq -p` is producing
> localhost: timed out, nothing received
> ***Request timed out
In addition the server should not be listening globally but on `dhcp_interface`, if `list interface` is omitted from /etc/config/system then on every interface or else on the specified interface. But apparently it does not.https://gitlab.nic.cz/turris/os/build/-/issues/32cfq & ionice for file/media centre2023-08-16T10:54:59+02:00dim-geocfq & ionice for file/media centrePlease activate CFQ on kernel io schedulers. No need to change the default io scheduler.
It is very useful for external hard disks (rotational) where competing processes try to access the hard disk. Also, if you can please activate ionic...Please activate CFQ on kernel io schedulers. No need to change the default io scheduler.
It is very useful for external hard disks (rotational) where competing processes try to access the hard disk. Also, if you can please activate ionice in busybox so cfq can be used as well.
It would help on scenarios where the turris acts as a small file/media centre.Turris OS 6.0https://gitlab.nic.cz/turris/os/build/-/issues/44Change default INPUT & FORWARD rules for both wan & guest from REJECT to DROP2019-06-20T13:42:30+02:00Ghost UserChange default INPUT & FORWARD rules for both wan & guest from REJECT to DROPThe rule of thumb on the Internet should be to remain stealth (DROP) while the REJECT action actually confirms that there is a server at this IP and it bothers enough to actually respond to the incoming messages. This pretty much guarant...The rule of thumb on the Internet should be to remain stealth (DROP) while the REJECT action actually confirms that there is a server at this IP and it bothers enough to actually respond to the incoming messages. This pretty much guarantees that all ports will be scanned over and over and hack attempts will not stop: it is like asking for trouble.
Responding to ICMP ping and others increases the CPU usage and bandwidth utilization which might lead to a DoS event. Home routers should remain stealth as more often than not the people that manage them do not know how to deal with attacks or connection slow downs.https://gitlab.nic.cz/turris/os/build/-/issues/45luci-app-sqm, luci-app-adblock, and luci-app-bcp382019-09-04T22:47:15+02:00Ghost Userluci-app-sqm, luci-app-adblock, and luci-app-bcp38Can you pls consider adding luci-app-sqm, luci-app-adblock, and luci-app-bcp38 modules to the default setup?
SQM is great in helping to solve buffer bloat even in 17.01 and became better in 18.06 and requires very minimal config now.
bc...Can you pls consider adding luci-app-sqm, luci-app-adblock, and luci-app-bcp38 modules to the default setup?
SQM is great in helping to solve buffer bloat even in 17.01 and became better in 18.06 and requires very minimal config now.
bcp38 is a security feature, that is a must for a home router nowadays.https://gitlab.nic.cz/turris/os/build/-/issues/51Include all coreutils-* packages into the default install2019-08-12T10:48:51+02:00Ghost UserInclude all coreutils-* packages into the default installThis router has a lot of muscle and storage, so it may make sense to include full versions of "coreutils-*" tools: the ones provided by busybox are way too limited and are for the minuscular router, which a TO is not. All packages togeth...This router has a lot of muscle and storage, so it may make sense to include full versions of "coreutils-*" tools: the ones provided by busybox are way too limited and are for the minuscular router, which a TO is not. All packages together take <7MB of space.
```
Filesystem Size Used Available Use% Mounted on
/dev/mmcblk0p1 7.3G 171.0M 7.1G 2% /
tmpfs 1010.8M 2.1M 1008.6M 0% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
Filesystem Size Used Available Use% Mounted on
/dev/mmcblk0p1 7.3G 177.6M 7.1G 2% /
tmpfs 1010.8M 3.2M 1007.6M 0% /tmp
tmpfs 512.0K 0 512.0K 0% /dev
```https://gitlab.nic.cz/turris/os/build/-/issues/62[feature request] provide an easy to install foris package to enable multicas...2023-08-16T11:04:21+02:00Claude Nobs[feature request] provide an easy to install foris package to enable multicast iptv supportVarious isp's (telekom.de, fiber7.ch, ...) come with a bundled iptv solution based on multicast technology. Apart from internet access, access to tv is one of the features a router should support out-of-the-box or provide a checkbox solu...Various isp's (telekom.de, fiber7.ch, ...) come with a bundled iptv solution based on multicast technology. Apart from internet access, access to tv is one of the features a router should support out-of-the-box or provide a checkbox solution in it's gui.
However currently it's neither supported out-of-the box, nor is it possible to setup using either foris or luci. Only if one is comfortable using ssh/bash it's rather trivial to setup :
```
IP=`ip -4 -br addr show br-lan | grep -E -o '[0-9.]+' | head -n 1`
opkg install igmpproxy
sed -i -e "s/$IP\/24/0.0.0.0\/0/g" /etc/config/igmpproxy
sed -i -e "s/option ipaddr '$IP'/option ipaddr '$IP'\n\toption igmp_snooping '1'/g" /etc/config/network
/etc/init.d/igmpproxy enable
/etc/init.d/igmpproxy start
```https://gitlab.nic.cz/turris/os/build/-/issues/63[feature request] enable NFT's full potential in kernel conf2023-08-16T11:04:20+02:00Ghost User[feature request] enable NFT's full potential in kernel conf> {"kernel":"4.14.131","hostname":"to","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"cznic,turris-omnia","release":{"distribution":"TurrisOS","version":"5.0-dev","revision":"c01f9ad","target":"mvebu/cortexa9...> {"kernel":"4.14.131","hostname":"to","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"cznic,turris-omnia","release":{"distribution":"TurrisOS","version":"5.0-dev","revision":"c01f9ad","target":"mvebu/cortexa9","description":"TurrisOS 5.0-dev c01f9ad"}}
____
With the below settiings disabled NFT is sort of castrated. Fail to see any potential harm it could cause enabling the feature set.
`# CONFIG_NFT_RT is not set`
> This option adds the "rt" expression that you can use to match packet routing information such as the packet nexthop.
`# CONFIG_NFT_SET_BITMAP is not set`
> This option adds the "bitmap" set type that is used to build sets whose keys are smaller or equal to 16 bits.
`# CONFIG_NFT_OBJREF is not set`
> This option adds the "objref" expression that allows you to refer to stateful objects, such as counters and quotas.
`# CONFIG_NFT_QUEUE is not set`
> This is required if you intend to use the userspace queueing infrastructure (also known as NFQUEUE) from nftables.
`# CONFIG_NFT_COMPAT is not set`
> This is required if you intend to use any of existing x_tables match/target extensions over the nf_tables framework.
`# CONFIG_NFT_FIB_NETDEV is not set`
> This option allows using the FIB expression from the netdev table. The lookup will be delegated to the IPv4 or IPv6 FIB depending on the protocol of the packet.
`# CONFIG_NFT_DUP_IPV4 is not set`
> This module enables IPv4 packet duplication support for nf_tables.
`# CONFIG_NFT_DUP_IPV6 is not set`
> This module enables IPv6 packet duplication support for nf_tables.
____
`# CONFIG_NFT_RT is not set`
is likely causing some grievance with TCP MSS clamping (essential for PPPoE) since
`nft add rule ip filter forward oifname pppoe-wan tcp flags syn tcp option maxseg size set rt mtu`
`nft add rule ip filter forward oifname pppoe-wan tcp flags syn tcp option maxseg size set 1452`
either is producing
> Error: Could not process rule: No such file or directoryhttps://gitlab.nic.cz/turris/os/build/-/issues/64[feature suggestion] enhance NF filter capabilities2023-08-16T11:04:18+02:00Ghost User[feature suggestion] enhance NF filter capabilities> {"kernel":"4.14.131","hostname":"to","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"cznic,turris-omnia","release":{"distribution":"TurrisOS","version":"5.0-dev","revision":"c01f9ad","target":"mvebu/cortexa9...> {"kernel":"4.14.131","hostname":"to","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"cznic,turris-omnia","release":{"distribution":"TurrisOS","version":"5.0-dev","revision":"c01f9ad","target":"mvebu/cortexa9","description":"TurrisOS 5.0-dev c01f9ad"}}
___
Please consider enhancement of NF filter capabilities
`# CONFIG_NETFILTER_XT_TARGET_HMARK is not set`
> This option adds the "HMARK" target.
The target allows you to create rules in the "raw" and "mangle" tables which set the skbuff mark by means of hash calculation within a given range. The nfmark can influence the routing method and can also be used by other subsystems to change their behaviour.
`# CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP is not set`
> This option adds a "TCPOPTSTRIP" target, which allows you to strip TCP options from TCP packets.
`# CONFIG_NETFILTER_XT_MATCH_CGROUP is not set`
> Socket/process control group matching allows you to match locally generated packets based on which net_cls control group processes belong to.
`# CONFIG_NETFILTER_XT_MATCH_IPCOMP is not set`
> This match extension allows you to match a range of CPIs(16 bits) inside IPComp header of IPSec packets.
`# CONFIG_NETFILTER_XT_MATCH_L2TP is not set`
> This option adds an "L2TP" match, which allows you to match against L2TP protocol header fields.
`# CONFIG_NETFILTER_XT_MATCH_OSF is not set`
> This option selects the Passive OS Fingerprinting match module that allows to passively match the remote operating system by analyzing incoming TCP SYN packets.
Rules and loading software can be downloaded from http://www.ioremap.net/projects/osf
`# CONFIG_NETFILTER_XT_MATCH_SCTP is not set`
> With this option enabled, you will be able to use the `sctp' match in order to match on SCTP source/destination ports and SCTP chunk types.https://gitlab.nic.cz/turris/os/build/-/issues/167Add options to hardening with option for common passwords inclusion2021-01-25T09:58:41+01:00Karel KociAdd options to hardening with option for common passwords inclusionWe have package with common passwords that should not be used for authentication. This is nice thing to include as option in hardening package list.We have package with common passwords that should not be used for authentication. This is nice thing to include as option in hardening package list.Turris OS 5.2.0https://gitlab.nic.cz/turris/os/build/-/issues/166collectd: Consider enabling signing/encryption support2020-08-01T18:57:35+02:00Elvenlord Elrondcollectd: Consider enabling signing/encryption supportcollectd's network plugin has the option to sign or encrypt the contents for data transfer to other collectd instances.
OpenWrt added this feature [here](https://github.com/openwrt/packages/commit/4ba4d8232d4431170faffadfa80fbb0ba76d20f...collectd's network plugin has the option to sign or encrypt the contents for data transfer to other collectd instances.
OpenWrt added this feature [here](https://github.com/openwrt/packages/commit/4ba4d8232d4431170faffadfa80fbb0ba76d20f1).
It is probably only a matter of adding `PACKAGE_COLLECTD_ENCRYPTED_NETWORK=y` to `configs/common/packages`?
Yes, this will introduce a new dependency on libgcrypt. On a small embedded platform this might be of concern. But for omnia and mox, it shouldn't be a big problem. And only people installing the network plugin will actually get that extra depeendencies. Which sounds acceptable to me.Turris OS 5.1https://gitlab.nic.cz/turris/os/build/-/issues/69Helpers/new_release.sh: Add release notes to tags2023-08-16T11:06:45+02:00Josef SchlehoferHelpers/new_release.sh: Add release notes to tagsI think it would be really cool if the script can add to tags release notes from `NEWS` file.I think it would be really cool if the script can add to tags release notes from `NEWS` file.Michal HruseckyMichal Hruseckyhttps://gitlab.nic.cz/turris/os/build/-/issues/75Use samba4 instead of samba32023-08-16T11:06:41+02:00Josef SchlehoferUse samba4 instead of samba3In PR !28, I noticed some changes regarding samba.
Shouldn't we use samba4 instead of samba(3)? The only issue what I am thinking is that samba4 is not available in OpenWrt 18.06.
In 19.07 or master is included. I asked in #openwrt-deve...In PR !28, I noticed some changes regarding samba.
Shouldn't we use samba4 instead of samba(3)? The only issue what I am thinking is that samba4 is not available in OpenWrt 18.06.
In 19.07 or master is included. I asked in #openwrt-devel why samba3 is still present in OpenWrt `master` branch.
```
20:13:11 <Pepe> I am wondering why in the master branch, there is still samba3, which was EOL 4 years ago.
20:31:18 <pkgadd> Pepe: because samba4 is unsuitable for most devices
22:45:51 <mangix> Pepe: size
22:45:56 <mangix> and laziness
22:47:07 <mangix> It should be removed from the main branch
```
We have powerful routers with a large amount of space, so it shouldn't be an issue to have supported version of samba4 or am I wrong? It depends how much we are going to diverge from OpenWrt. On the other hand, I am against it, but samba3 is vulnerable and reached EoL a long time ago. This should be handled directly in OpenWrt, they should decide what they are going to do with samba3, because this ancient version is not even in [Debian](https://packages.debian.org/search?keywords=samba).Turris OS 5.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/81[feature suggestion] Enable ATH9K_SUPPORT_PCOEM on ath9k module2020-12-08T19:56:56+01:00Sami Viitanen[feature suggestion] Enable ATH9K_SUPPORT_PCOEM on ath9k moduleI think ATH9K_SUPPORT_PCOEM isn't enabled for ath9k modules on Turris packages, limiting amount of supported ath9k mPCIe cards.
Normally keeping it disable might make sense to keep module smaller for normal OpenWRT routers, but this sho...I think ATH9K_SUPPORT_PCOEM isn't enabled for ath9k modules on Turris packages, limiting amount of supported ath9k mPCIe cards.
Normally keeping it disable might make sense to keep module smaller for normal OpenWRT routers, but this shouldn't be a real issue with Mox/Omnia/1.x devices, right?
Run into this issue when I was trying to upgrade original AR9287 to AR9462 on my Turris Omnia. And it looks like it's ID wasn't on whitelist because missing ATH9K_SUPPORT_PCOEM.Turris OS 5.2.0Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/build/-/issues/89Connection problem on Omnia SFP-WAN2023-08-16T11:07:23+02:00Giuseppe PiscitelliConnection problem on Omnia SFP-WANHaving updated my Omnia to the 4.0.1 version of Turris OS I can no longer set up a working connection using the operator's SFP module in the router cage. In fact, by setting eth2 as eth2.835 (number requested by the ISP), PPPoE authentic...Having updated my Omnia to the 4.0.1 version of Turris OS I can no longer set up a working connection using the operator's SFP module in the router cage. In fact, by setting eth2 as eth2.835 (number requested by the ISP), PPPoE authentication fails. There are a few hypotheses:
1) the problem is related to the switch / vlan limited on OS 4.x and Omnia;
2) incompatibility of the SFP with the new version of the operating system (although it is recognized by dmesg).
Below are the diagnostic links on 4.x configured and not working and 3.11.8 configured and working. I hope you can understand more than me. For any further information do not hesitate to ask.
[4.0.1.gz](/uploads/9ea1fa647fc3c42439b9301ad40880bc/4.0.1.gz)
[3.11.8.gz](/uploads/f8dd61251c38ac4772c3d2cbeb52b3e7/3.11.8.gz)https://gitlab.nic.cz/turris/os/build/-/issues/95luci feed should be patched to report base hash over tip hash to aid to upstream2020-01-06T09:05:04+01:00Karel Kociluci feed should be patched to report base hash over tip hash to aid to upstreamUpstream is using hash in version to identify commit but our patching of feed packages causes that hash to be invalid. Solution is not to patch that feed. We do not patch anything substantial in that feed so it is fully compatible with u...Upstream is using hash in version to identify commit but our patching of feed packages causes that hash to be invalid. Solution is not to patch that feed. We do not patch anything substantial in that feed so it is fully compatible with upstream. Adding patch that that specific version extension is changed to contain base hash (remote hash) over tip hash solves this.
Example here https://github.com/openwrt/luci/issues/3357https://gitlab.nic.cz/turris/os/build/-/issues/102[feature request] uplift Multi-CPU-DSA patch to Master branch2020-02-11T12:15:01+01:00Ghost User[feature request] uplift Multi-CPU-DSA patch to Master branchCuriously this patch <sup>**[1]**</sup> is missing in Master and I suspect it causing `vlan_filtering` (bridge vlan awareness) to fail, which would make sense in the context of DSA and SWITCHDEV.
Toggling it on, e.g. for br-lan, with ...Curiously this patch <sup>**[1]**</sup> is missing in Master and I suspect it causing `vlan_filtering` (bridge vlan awareness) to fail, which would make sense in the context of DSA and SWITCHDEV.
Toggling it on, e.g. for br-lan, with `ip l s dev br-lan ty bridge vlan_filtering 1` ingress connectivity from a client is instantly lost. On a HBD instance however, with the same settings, the issue does not exhibit.
Thus, would appreciate if the patch could be uplifted to Master.
___
<sup>**[1]**</sup> https://gitlab.labs.nic.cz/turris/turris-build/blob/hbd/patches/openwrt/wip/0009-mvebu-turris-omnia-multi-cpu-dsa.patchhttps://gitlab.nic.cz/turris/os/build/-/issues/113compilation issues for nodejs2023-08-16T11:03:50+02:00Michael Richardsoncompilation issues for nodejsHere Be Kittens, with the update that fixes #111 fails with:
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
make[4]: Entering directory '/ssw/projects/cerowrt/turris-build/build/build_dir/target-arm_cortex-a9+vfpv3_m...Here Be Kittens, with the update that fixes #111 fails with:
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
make[4]: Entering directory '/ssw/projects/cerowrt/turris-build/build/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/node-hashtable-2.0.2/ipkg-install/usr/lib/node_modules/hashtable/build'
ccache_cxx '-DNODE_GYP_MODULE_NAME=native' '-DUSING_UV_SHARED=1' '-DUSING_V8_SHARED=1' '-DV8_DEPRECATION_WARNINGS=1' '-DV8_DEPRECATION_WARNINGS' '-DV8_IMMINENT_DEPRECATION_WARNINGS' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DOPENSSL_NO_PINSHARED' '-DOPENSSL_THREADS' '-DBUILDING_NODE_EXTENSION' -I/ssw/projects/cerowrt/turris-build/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/usr/include/node -I/ssw/projects/cerowrt/turris-build/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/usr/src -I/ssw/projects/cerowrt/turris-build/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/usr/deps/openssl/config -I/ssw/projects/cerowrt/turris-build/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/usr/deps/openssl/openssl/include -I/ssw/projects/cerowrt/turris-build/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/usr/deps/uv/include -I/ssw/projects/cerowrt/turris-build/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/usr/deps/zlib -I/ssw/projects/cerowrt/turris-build/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/usr/deps/v8/include -I../node_modules/nan -fPIC -pthread -Wall -Wextra -Wno-unused-parameter -std=c++11 -Wall -O3 -fno-omit-frame-pointer -fno-rtti -fno-exceptions -std=gnu++1y -MMD -MF ./Release/.deps/Release/obj.target/native/src/hashtable.o.d.raw -Os -pipe -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable -Wno-error=unused-result -mfloat-abi=hard -iremap/ssw/projects/cerowrt/turris-build/build/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/node-hashtable-2.0.2:node-hashtable-2.0.2 -Wformat -Werror=format-security -fpic -fstack-protector-strong -D_FORTIFY_SOURCE=2 -Wl,-z,now -Wl,-z,relro -fpic -I/ssw/projects/cerowrt/turris-build/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/usr/include -I/ssw/projects/cerowrt/turris-build/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/include -I/ssw/projects/cerowrt/turris-build/build/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-7.5.0_musl_eabi/usr/include -I/ssw/projects/cerowrt/turris-build/build/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-7.5.0_musl_eabi/include/fortify -I/ssw/projects/cerowrt/turris-build/build/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-7.5.0_musl_eabi/include -fpic -c -o Release/obj.target/native/src/hashtable.o ../src/hashtable.cpp
In file included from ../src/hashtable.h:15:0,
from ../src/hashtable.cpp:1:
../src/v8_value_hasher.h: In member function 'bool v8_value_equal_to::operator()(CopyablePersistent*, CopyablePersistent*) const':
../src/v8_value_hasher.h:43:24: error: no matching function for call to 'v8::Value::Equals(v8::Local<v8::Value>&)'
if (a->Equals(b)) { /* same as JS == */
^
In file included from /ssw/projects/cerowrt/turris-build/build/staging_dir/target-arm_cortex-
a9+vfpv3_musl_eabi/usr/include/node/node.h:63:0,
from ../src/hashtable.h:13,
from ../src/hashtable.cpp:1:
/ssw/projects/cerowrt/turris-build/build/staging_dir/target-arm_cortex-
9+vfpv3_musl_eabi/usr/include/node/v8.h:2616:37: note: candidate: v8::Maybe<bool>
v8::Value::Equals(v8::Local<v8::Context>, v8::Local<v8::Value>) const V8_WARN_UNUSED_RESULT Maybe<bool>
Equals(Local<Context> context,
...
(I'm not blaming #111 for this, I couldn't get this far before)
I run:
./compile_pkgs -t omnia -p hbk -x prepare_tools
cd build
make V=s
because ./generate_medkit usually dies with issues in updater_ng, which I gave up trying to fix, and from my reading of that, I don't need that to work now if I don't care about having patches available. Maybe they are related.
I have no personal need for nodejs, I'd just disable it, but other stuff seems to require, and I don't know what yet.https://gitlab.nic.cz/turris/os/build/-/issues/118java issues with building on plain Ubuntu LTS 18.042023-08-16T11:04:15+02:00Michael Richardsonjava issues with building on plain Ubuntu LTS 18.04I've abandoned the build host that I used successfully in 2019, and spun up an EC2 with Ubuntu 18.04.
classpath-0.99 needs a javac. (Why do we need classpath... I don't know).
openjdk does not seem to satisfy it.
gcj doesn't seem to be a...I've abandoned the build host that I used successfully in 2019, and spun up an EC2 with Ubuntu 18.04.
classpath-0.99 needs a javac. (Why do we need classpath... I don't know).
openjdk does not seem to satisfy it.
gcj doesn't seem to be a thing on ubuntu.
oracle java 11 or 13 seems to be incompatible, so I copied java 8 from my old build server and adjusted /etc/alternatives/javac.... but now I get the following silly warning that becomes an error.
Sigh.
```
make[7]: Entering directory '/home/ubuntu/turris-build/build/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/classpath-0.99/native/jni/java-math'
/bin/bash ../../../libtool --tag=CC --mode=compile ccache_cc -DHAVE_CONFIG_H -I. -I../../../include -I../../../include -I../../../native/jni/classpath -I../../../native/jni/native-lib -I/home/ubuntu/turris-build/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/usr/include -I/home/ubuntu/turris-build/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/include -I/home/ubuntu/turris-build/build/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-7.3.0_musl_eabi/usr/include -I/home/ubuntu/turris-build/build/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-7.3.0_musl_eabi/include/fortify -I/home/ubuntu/turris-build/build/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-7.3.0_musl_eabi/include -W -Wall -Wmissing-declarations -Wwrite-strings -Wmissing-prototypes -Wno-long-long -Werror -I/home/ubuntu/turris-build/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/usr/include -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/ubuntu/turris-build/build/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/classpath-0.99:classpath-0.99 -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro -MT gnu_java_math_GMP.lo -MD -MP -MF .deps/gnu_java_math_GMP.Tpo -c -o gnu_java_math_GMP.lo gnu_java_math_GMP.c
OpenWrt-libtool: compile: ccache_cc -DHAVE_CONFIG_H -I. -I../../../include -I../../../include -I../../../native/jni/classpath -I../../../native/jni/native-lib -I/home/ubuntu/turris-build/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/usr/include -I/home/ubuntu/turris-build/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/include -I/home/ubuntu/turris-build/build/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-7.3.0_musl_eabi/usr/include -I/home/ubuntu/turris-build/build/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-7.3.0_musl_eabi/include/fortify -I/home/ubuntu/turris-build/build/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-7.3.0_musl_eabi/include -W -Wall -Wmissing-declarations -Wwrite-strings -Wmissing-prototypes -Wno-long-long -Werror -I/home/ubuntu/turris-build/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/usr/include -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/ubuntu/turris-build/build/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/classpath-0.99:classpath-0.99 -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro -MT gnu_java_math_GMP.lo -MD -MP -MF .deps/gnu_java_math_GMP.Tpo -c gnu_java_math_GMP.c -fPIC -DPIC -o .libs/gnu_java_math_GMP.o
gnu_java_math_GMP.c: In function 'Java_gnu_java_math_GMP_natSetBitCount':
gnu_java_math_GMP.c:1134:13: error: this statement may fall through [-Werror=implicit-fallthrough=]
res = mpz_popcount (_this);
~~~~^~~~~~~~~~~~~~~~~~~~~~
gnu_java_math_GMP.c:1135:7: note: here
default:
^~~~~~~
cc1: all warnings being treated as errors
Makefile:531: recipe for target 'gnu_java_math_GMP.lo' failed
make[7]: *** [gnu_java_math_GMP.lo] Error 1
make[7]: Leaving directory '/home/ubuntu/turris-build/build/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/classpath-0.99/native/jni/java-math'
Makefile:469: recipe for target 'all-recursive' failed
make[6]: *** [all-recursive] Error 1
make[6]: Leaving directory '/home/ubuntu/turris-build/build/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/classpath-0.99/native/jni'
Makefile:457: recipe for target 'all-recursive' failed
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory '/home/ubuntu/turris-build/build/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/classpath-0.99/native'
Makefile:516: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1
```https://gitlab.nic.cz/turris/os/build/-/issues/127Build user and server identity in dmesg2020-07-13T14:08:41+02:00Vojtech MyslivecBuild user and server identity in dmesgThis is the first line in dmesg on:
```
[ 0.000000] Linux version 4.14.171 (beast@slave09) (gcc version 7.5.0 (OpenWrt GCC 7.5.0 e7f1313)) #0 SMP Fri Mar 6 11:05:10 2020
```
Is `beast@slave09` intended here? It should be something li...This is the first line in dmesg on:
```
[ 0.000000] Linux version 4.14.171 (beast@slave09) (gcc version 7.5.0 (OpenWrt GCC 7.5.0 e7f1313)) #0 SMP Fri Mar 6 11:05:10 2020
```
Is `beast@slave09` intended here? It should be something like `packaging@turris.cz`, shouldn't it?Turris OS 5.1https://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/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/146Some packages have no valid architecture, ignoring2023-08-16T11:01:35+02:00Josef SchlehoferSome packages have no valid architecture, ignoringDue to change in upstream, which corrected CPU subtype. Commit: https://github.com/openwrt/openwrt/commit/67ed408af20c3b24725f051596028345497219d8
Some packages are not installed or updated. This could happen with any package.
This so ...Due to change in upstream, which corrected CPU subtype. Commit: https://github.com/openwrt/openwrt/commit/67ed408af20c3b24725f051596028345497219d8
Some packages are not installed or updated. This could happen with any package.
This so far is confirmed to be happening on these packages:
```
Package coreutils version 8.30-2.0 has no valid architecture, ignoring.
Package foris-controller version 1.0.11-3.7-1.0 has no valid architecture, ignoring.
Package libpthread version 1.1.24-2.0 has no valid architecture, ignoring.
Package xz-utils version 5.2.4-5.0 has no valid architecture, ignoring.
Package librt version 1.1.24-2.0 has no valid architecture, ignoring.
Package shadow version 4.8.1-1.0 has no valid architecture, ignoring.
Package shadow-utils version 4.8.1-1.0 has no valid architecture, ignoring.
Package ip6tables version 1.8.3-1.0 has no valid architecture, ignoring.
Package lxc version 3.0.3-1.0 has no valid architecture, ignoring.
Package busybox version 1.30.1-6 has no valid architecture, ignoring.
```
We need reinstall all packages with invalid architecture.Turris OS 5.1https://gitlab.nic.cz/turris/os/build/-/issues/155[device tree compiler warnings] all benign?2023-08-16T11:01:43+02:00Ghost User[device tree compiler warnings] all benign?DTC prints several warnings:
Those for the SMB look benign
> Warning (simple_bus_reg): /soc/bootrom: simple-bus unit address format error, expected "11d000000000000"
> Warning (simple_bus_reg): /soc/devbus-bootcs: simple-bus unit ad...DTC prints several warnings:
Those for the SMB look benign
> Warning (simple_bus_reg): /soc/bootrom: simple-bus unit address format error, expected "11d000000000000"
> Warning (simple_bus_reg): /soc/devbus-bootcs: simple-bus unit address format error, expected "f001000000010400"
> Warning (simple_bus_reg): /soc/devbus-cs0: simple-bus unit address format error, expected "f001000000010408"
> Warning (simple_bus_reg): /soc/devbus-cs1: simple-bus unit address format error, expected "f001000000010410"
> Warning (simple_bus_reg): /soc/devbus-cs2: simple-bus unit address format error, expected "f001000000010418"
> Warning (simple_bus_reg): /soc/devbus-cs3: simple-bus unit address format error, expected "f001000000010420"
> Warning (simple_bus_reg): /soc/internal-regs: simple-bus unit address format error, expected "f001000000000000"
> Warning (simple_bus_reg): /soc/internal-regs/thermal@e8078: simple-bus unit address format error, expected "e4078"
> Warning (simple_bus_reg): /soc/sa-sram0: simple-bus unit address format error, expected "919000000000000"
> Warning (simple_bus_reg): /soc/sa-sram1: simple-bus unit address format error, expected "915000000000000"
> Warning (simple_bus_reg): /soc/bm-bppi: simple-bus unit address format error, expected "c04000000000000"
> Warning (simple_bus_reg): /soc/spi@10600: simple-bus unit address format error, expected "f001000000010600"
> Warning (simple_bus_reg): /soc/spi@10680: simple-bus unit address format error, expected "f001000000010680"
> Warning (simple_bus_reg): /soc/pcie: simple-bus unit address format error, expected "f001000000080000"
But I was wondering about those
> Warning (avoid_unnecessary_addr_size): /soc/internal-regs/mdio@72004/switch@10: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property
> Warning (avoid_unnecessary_addr_size): /soc/spi@10600/spi-nor@0: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property
> Warning (unique_unit_address): /soc/internal-regs/timer@20300: duplicate unit-address (also used in node /soc/internal-regs/watchdog@20300)Marek BehunMarek Behunhttps://gitlab.nic.cz/turris/os/build/-/issues/171MOX - INFO: rcu_sched detected stalls on CPUs/tasks2020-07-07T14:51:36+02:00Josef SchlehoferMOX - INFO: rcu_sched detected stalls on CPUs/tasksAfter a long time, I tried to use `HBD` from `HBK` branch, but MOX is not succesfully booted.
```
## Flattened Device Tre blob at 04f00000
Booting using the fdt blob at 0x4f00000
Loading Device Tree to 000000003bf14000, end 000000...After a long time, I tried to use `HBD` from `HBK` branch, but MOX is not succesfully booted.
```
## Flattened Device Tre blob at 04f00000
Booting using the fdt blob at 0x4f00000
Loading Device Tree to 000000003bf14000, end 000000003bf1bee0 .. OK
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 5.4.48 (packaging@turris.cz) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 3b0f698)) #0 SMP Sat Jul 4 00:03:54 2020
[ 0.000000] Machine moel: CZ.NIC Turris Mox Board
[ 0.000000] earlycon: ar3700_uart0 at MMIO 0x00000000d0012000 (options '')
[ 0.000000] printk: bootconsole [ar3700_uart0] enabled
[ 0.000000] ps�K��ɽ�����for conduit method from DT.
[ 0.000000] psci: PSCIv.1 detected in firmware.
[ 0.000000] psci: Using standard PSCI v0.2 function IDs
[ 0.000000] psci: MIGRATE_INFO_TYPE not supported.
[ 0.000000] psci: SMC Calling Convention v1.1
[ 0.000000] percpu: Embedded 16 pages/cpu s28440 r8192 d28904 u65536
[ 0.000000] Detected VIPT I-cache on CPU0
[ 0.000000] CPU features: detected: GIC system register CPU interface
[ 0.000000] Speculative Store Bypass Disable mitigation n��requirad
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 257536
[ 0.000000] Kernel command line: earlyprintk console=ttyMV0,115200 earlycon=ar3700_uart,0xd0�����j������}���btrfs root=PARTUUID=00000000-01 rootflags=commit=5,subvol=@ rootwait rw cfg80211.freg=
[ 0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[ 0.000000] Inode-cache hash table entrie.'Ͳ����Bz�ɑ��� 7, 524288 bytes, linear)
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] Memory: 1014344K/1046528K available (8446K kernel code, 480K rwdata, 2112K rodata, 576K init, 300K bss, 32184K reserved, 0K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] rcu: CONFIG_RCU_FANOUT set to non-default value of 32.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[ 0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[ 0.000000] GICv3: 192 SPIs implemented
[ 0.000000] GICv3: 0 Extended SPIs implemented
[ 0.000000] GICv3: Distributor has no Range Selector support
[ 0.000000] GICv3: 16 PPAs implemented
[ 0.000000] GICv3: no VLPI support, no direct LPI support
[ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x00000000d1d40000
[ 0.000000] random: get_random_bytes called from start_kernel+0x354/0x4cc with crng_init=0
[ 0.000000] arch_timer: cp15 timer(s) running at 12.50M@z (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycle.'ɂ��e2049cda, max_idle_ns: 440795202628 ns
[ 0.000004] sched_clock: 56 bips at 12MHz, resolution 80ns, wraps every 4398046511080ns
[ 0.008423] Console: colour dummy device 80x25
[ 0.012935] Calibrating delay loop (skipped), value calculated using timer frequency. �r�����5%AM�(lpj=125000)
[ 0.023582] pid_ma� default: 32768 minimum: 301
[ 0.028442] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
[ 0.035992] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
[ 0.045304] ASID allocapor initialised with 32768 entries
[ 0.050894] rcu: Hierarchical SRCU implementation.
[ 0.056116] smp: Bringing up secondary CPUs ...
[ 0.061156] Detected VIPT I-cache on CPU1
[ 0.061186] GICv3: CPU1: found redistributor 1 region 0:0x00000000d1d60000
[ 0.061221] CPU1: Booted seconary processor 0x0000000001 [0x410fd034]
[ 0.061310] smp: Brought up 1 node, 2 CPUs
[ 0.083368] SMP: Total of 2 processors activated.
[ 0.088201] CPU features: detected: 32-bit EL0 Support
[ 0.093493] CPU features: detected: CRC32 instructions
[ 0.098815] CPU features: emulated: Privileged Access Never (PAN) using TTBR0_EL1 switching
[ 0.107383] CPU: All CPU(s) started at EL2
[ 0.111595] alternatives: patching kernel code
[ 0.117006] devtmpfs: initialized
[ 0.122792] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.132882] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[ 0.139965] xor: measuring software checksum speed
[ 0.244875] 8rYց : 1978.800 MB/sec
[ 0.3449遺� 32regs : 2270.400 MB/sec
[ 0.444942] arm64_neon: 2002.400 MB/sec
[ 0.449161] xor: using function: 32regs (2270.400 MB/sec)
[ 0.454725] pinctrl core: initialized pinctrl subsystem
[ 0.461015] NET: Registered protocol family 16
[ 0.465947] DMA: prellocated 256 KiB pool for atomic allocations
[ 0.473223] cpuidle: using governor ladder
[ 0.477678] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[ 0.500455] cryptd: max_cpu_qlen set to 1000
[ 0.506196] raid6: using algorithm neonx8 gen() 0 MB/s
[ 0.511441] raid6: .... xor() 0 MB/s, rmw en`bled
[ 0.516245] raid6: using neon recovery algorithm
[ 0.522045] SCSI subsystem initialized
[ 0.527134] usbcore: registered new interface driver usbfs
[ 0.532940] usbcore: registered new interface driver hub
[ 0.538387] usbcore: registered new device driver usb
[ 0.545257] clocksource: Switched to clocksource arch_sys_counterC�[ 0.558430] thermal_sys: Registered thermal governor 'step_wise'
[ 0.558710] NET: Registeped protocol family 2
[ 0.570114] tcp_listen_portaddr_hash h table entries: 512 (order: 1, 8192 bytes, linear)
[ 0.578820] TCP estblished hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.586790] TCP bind hash table entries: 8192 (orer: 5, 131072 bytes, linear)
[ 0.594279] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.600910] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 0.607670] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 0.615084] NET: Registered protocol family 1
%� (j���邕�ͱ default 64
[ 0.624112] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
[ 0.637292] workingset: timestamp_bits=46 max_order=18 bucket_order=0
[ 0.648540] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.654472] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.671661] mv_xor d0060900.xor: Marvell shared XOR drivar
[ 0.735922] mv_xor d0060900.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr )
[ 0.805880] mv_xor d0060900.xor: Marvell XOR (Descriptor Mode): ( xor cp intr )
[ 0.813883] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[ 0.822445] cacheinfo: Unable to detect cache hierarchy for CPU 0
[ 0.832223] loop: module loaded
[ 0841411] random: fast init done
[ 0.850064] spi-nor spi0.0: w25q64dw (8192 Kbytes)
[ 0.855089] 5 fixed-partitions partitions found on MTD device spi0.0
[ 0.861565] Creating 5 MTD partitions on "spi0.0":
[ 0.866500] 0x000000000000-0x000000020000 : "secre-firmware"
[ 0.873257] 0x000000020000-0x000000180000 : "u-boot"
[ 0.879032] 0x000000180000-0x000000190000 : "u-boot-env"
[ 0.885140] 0x000000190000-0x0000007f0000 : "Rescue system"
[ 0.891624] 0x0000007f0000-0x000000800000 : "dtb"
[ 0.897483] moxtet pZr��2ҽ�չ��MOX A (CPU) module
[ 0)������ʁmoxtet spi0.1: Fou`d MOX C (4 port switch) module
[ 0.909331] libphy: Fixed MDIO Bus: probed
0 914007] orion-mdio d003204.mdio: IRQ index 0 not found j
[ 0.919821] libphy: orion_mdio_bus: probed ��*�141, revisio [ 0.945791] libphy mV�K��낽���5
[ 0.924919] mv88e6085 d0032004.mdio-mii:02: switch 0x3400 detected: Ma.W� [ r�ʺ������mvneta d0030000.ethernet eth0: Using device tree mac address d8:58:d7:00:b5:c6
[ 0.982170] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.988839] ehci-pci: EHCI PCI platform driver
[ 0.993447] ehci-platform: EHCI generic platform driver
[ 0.998940] ehci-orion: EHCI orion driver
[ 1.003167] orion-ehci d005e000.usb: EHCI Host Controller
[ 1.008671] orion-ehci d005e000.usb: new USB bus registered, assigned bus number 1
[ 1.016552] orion-ehci d005e000.usb: irq 15, io mem 0xd005e000
[ 1.055249] orion-ehci d005e000.usb: USB 2.0 started, EHCI 1.00
[ 1.061813] hub 1-0:1.0: USB hub �ꁫ��5
[ 1.065641] hub 1-0:1.0: 1 port detected
[ 1.070528] usbcore: registered new interface driver usb-storage
[ 1.076957] i2c /dev entries driver
[ 1.081331] armada_37xx_wdt d0008300.watchdog: Initial timeout 120 sec
[ 1.088637] sdhci: Secure Digital Host Controller Interface driver
[ 1.094924] sdhci: Copyright(c) Pierre Ossman
[ 1.099568] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.105672] xenon-sdhci d00d0000.sdhci: allocated mmc-pwrseq
[ 1.111634] xenon-sdhca d00d8000.sdhci: Got CD GPIO
[ 1.118404] NET: Registered protocol fam ly 10
[ 1.123762] Segment Roting with IPv6
[ 1.127539] NET: Registered protocol family 17
[ 1.132078] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 1.145515] 8021q: 802.1Q VLAN Support v1.8
[ 1.151720] Btrfs loaded, crc32c=crc32c-generic
[ 1.158678] d0012000.serial: ttyMV0 at MMIO 0xd0012000 (irq = 0, base_baud = 1562500) is a mvebu-uart
[ 1.168146] printk: console [ttyMV0] enabled
[ 1.168146] pink: co`sole [ttyMP0] enabled
[ 1.176889] printk: bootconsole Xar3700_uart0] disabled
[ 1.176889] printk: bootconsole [ar3700_uart0] disabled
[ 1.188986] pxa2xx-i2c d0011000.i2c: missing pinmux recovery information: -548717316480 -19
[ 1.196531] rtc-ds1307 0-006f: registered as rtc0
[ 1.199633] i2c i2c-0: PXA I2C adapter
[ 1.204242] mv88e6085 d0032004.mdio-mii:02: switch 0x3400 detected: Marvell 88A6141, revision 0
[ 1.224434] libphy: mdio: probed
[ 1.249382] mvneta d0040000.ethernet eth1: Using device tree mac address d8:58:d7:00:b5:c7
[ 61.275232] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[ 61.27848����� 1-...0: (1 GPs behind) idle=b1a/1/0x4000000000000000 softirq=199/200 fqs=3000
[ 61.287526] (detected by 0, t=6002 jiffies, g=-1027, q=304)
[ 61.293348] Task dump for CPU 1:
ա+��r����ʚ���Workqueue: events deferred_probe_work_func 22 2 0x0000000a
[ 61.309207] Call trace:
[ 61.311723] __switch_to+0x1c0/��48
[ 61.315390] 0xffffffc010bf0e78
[ 241.325226] rcu: INFO: rcu_sched detected stalls n CPUs/tasks:
[ 241.328465] rcu: 1-...0: (1 GPs behind) idle=b1a/1/0x4000000000000000 softirq=199/200 fqs=12001
[ 241.337601] (detecte by 0, t=24007 jiffies, g=-1027, q=304)
[ 241.343513] Task dump for CPU 1:
[ 241.346828] kworker/1:1 R running task 0 22 2 0x0000000a
[ 241.354090] Workqueue: events deferred_probe_work_func
[ 241.359371] Call trace:
[ 241.361882] __switch_to+0x1c0/0x248
[ 241.365555] 0xffffffc010bf0e78
[ 421.375226] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[ 421.378465] rcu: 1-...0: (1 GPs behind) idle=b1a/1/0x4000000000000000 softirq=199/200 fqs=21002
[ 421.387600] (detected by 0, t=42012 jiffies, g=-027, q=308)
[ 421.393513] Task dump for CPU 1:
[ 421.396828] kworker/1:1 R running task 0 22 2 0x0000000a
[ 421.404090] Workqueue: events deferred_probe_work_func
[ 421.409372] Call trace:
[ 421.411883\ __switch_to+0x1c0/0x248
[ 421.415555] 0xffffffc010bf0e78
[ 601.425226] rcu: INFO: rcu_sched detected stalls on CPUs/tXꁮ�.�Hh���r���¢���rcu: 1-...0: (1 GPs behind) idle=b1a/1/0x4000000000000000 softirq=199/200 fqs=30003
[ 60.437601] (detected by 0, t=60017 jiffies, g=-1027, q=308)
[ 601.443512] Task dump for CPU 1:
[ 601.446828] kworker/1:1 R ꁒ�չ�����task 0 22 2 0x0000000a
[ 601.454090] Workqueue: events deferred_probe_work_func
[ 601.459371] Call trace:
[ 601.461883] __switch_to+0x1c0/0x248
[ 601.465555] 0xffffffc010b`0e78
[ 781.475226] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[ 781.478466] rcu: 1-...0: (1 GPs behind) idlYO�
�1/0x4000000000000000 softirq=199/200 fqs=39004
[ 781.487600] (detected by 0, t=78022 jiffies :�-1027, q=308)
[ 781.493512] Task dump for CPU 1:
[ �r�����ʲ���kworker/1:1 R running task 0 22 2 0x0000000a
[ 781.504089] Workqueue: events deferred_probe_work_func
[ 781.509372] Call trace:
[ 7�r������� __switch_to+0x1c0/0x248
[ 781.515555] 0xffffffc010bf0e78
```
cc: @mbehun
If you need anything, please let me know.Turris OS 6.0https://gitlab.nic.cz/turris/os/build/-/issues/210Reporting statistics from compile_pkgs2023-08-16T10:58:31+02:00Josef SchlehoferReporting statistics from compile_pkgsWhile using: `./compile_pkgs stats`
I received this output:
```
Reporting statistics
Statistics of the build:
* 251 binary packages built
* 0find: ‘logs/package/’: No such file or directory
/0 source packages failed
```
While I do: ...While using: `./compile_pkgs stats`
I received this output:
```
Reporting statistics
Statistics of the build:
* 251 binary packages built
* 0find: ‘logs/package/’: No such file or directory
/0 source packages failed
```
While I do: cat build/logs/stats
It shows:
```
Statistics of the build:
* 251 binary packages built
* 0/0 source packages failed
```Turris OS 5.1.9https://gitlab.nic.cz/turris/os/build/-/issues/215LuCI: LXC containers are not listed after installation2021-04-09T11:19:44+02:00Karel KociLuCI: LXC containers are not listed after installationThe issue is that there are no containers listed in LuCI if there are any already or if they are created after that till the reboot is performed.
This happens only if you install LXC not when you remove and install it back on running ro...The issue is that there are no containers listed in LuCI if there are any already or if they are created after that till the reboot is performed.
This happens only if you install LXC not when you remove and install it back on running router. Boot of device has to be without LXC installed.
The cause is missing LXC in ubus. Any direct operation such as creation of container are successful but anything modifying existing containers uses ubus. LXC ubus support is provided by package `rpcd-mod-lxc`. This package clearly is not forcing rpcd reload.Turris OS 5.2.0https://gitlab.nic.cz/turris/os/build/-/issues/243Turris Omnia WiFi cards dectection sometimes fails2021-10-06T15:41:09+02:00Karel KociTurris Omnia WiFi cards dectection sometimes fails```
ls: /sys/bus/pci/devices/0000:00:01.0/000*/iee*/phy*: No such file or directory
```
This happens most likely because wifi cards are not yet detected at time of board script execution.
The `/etc/board.d` scripts are executed as one...```
ls: /sys/bus/pci/devices/0000:00:01.0/000*/iee*/phy*: No such file or directory
```
This happens most likely because wifi cards are not yet detected at time of board script execution.
The `/etc/board.d` scripts are executed as one of the last steps in preinit but all kernel modules are loaded right after preinit. The drivers are not built in so the devices are just not available.
The result of this is that led for wifi card is just not configured to blink with appropriate device. In effect it is set to not blink at all.Turris OS 5.3.0https://gitlab.nic.cz/turris/os/build/-/issues/251ipcheck.py can not be found2021-04-16T11:19:13+02:00Josef Schlehoferipcheck.py can not be foundHonestly, I am not sure what I did, but I rollbacked to some older snapshot with HBD and then do pkgupdate, tried to startup kresd and it shows that ipcheck can not be found
```
root@turris:~# /etc/init.d/kresd start
/etc/rc.common: lin...Honestly, I am not sure what I did, but I rollbacked to some older snapshot with HBD and then do pkgupdate, tried to startup kresd and it shows that ipcheck can not be found
```
root@turris:~# /etc/init.d/kresd start
/etc/rc.common: line 96: ipcheck.py: not found
/etc/rc.common: line 99: ipcheck.py: not found
/etc/rc.common: line 96: ipcheck.py: not found
/etc/rc.common: line 99: ipcheck.py: not found
/etc/rc.common: line 96: ipcheck.py: not found
/etc/rc.common: line 99: ipcheck.py: not found
/etc/rc.common: line 96: ipcheck.py: not found
/etc/rc.common: line 99: ipcheck.py: not found
job 6 at Wed Mar 3 14:47:00 2021
```Turris OS 6.0https://gitlab.nic.cz/turris/os/build/-/issues/253Service umount is not enabled in medkit2021-06-07T19:42:51+02:00Karel KociService umount is not enabled in medkitThe service `umount` is in `/etc/services_wanted` and on update of package `base-files` that contains it is enabled and started but in medkit it is not.
This looks like issue of the chicken and an egg. The `base-files` packages is esse...The service `umount` is in `/etc/services_wanted` and on update of package `base-files` that contains it is enabled and started but in medkit it is not.
This looks like issue of the chicken and an egg. The `base-files` packages is essentially the first package to be installed and contains also `/etc/services_wanted`. It is likely that not all what is needed is available and thus service is not enabled.
This is not a big issue as the service only tries to correctly umount all mounted filesystems except of root. The same operation is automatically performed by kernel.https://gitlab.nic.cz/turris/os/build/-/issues/278Standalone package wireguard was dropped in favor of kernel package2023-08-16T10:57:32+02:00Josef SchlehoferStandalone package wireguard was dropped in favor of kernel package@jbetik reported to me that while trying HBD branch on Turris 1.x router, he installed ``wireguard`` via opkg.
The thing is that wireguard is now part of kernel, but for kernel 5.4 it was backported there and since this commit https://g...@jbetik reported to me that while trying HBD branch on Turris 1.x router, he installed ``wireguard`` via opkg.
The thing is that wireguard is now part of kernel, but for kernel 5.4 it was backported there and since this commit https://github.com/openwrt/openwrt/commit/a701d4b8414db2e1fafa676fad232cc9a0bfeaab there is provided ``kmod-wireguard`` package.
I could not find any file in turris-build repository which would depend on ``wireguard`` standalone package itself and users can meet this warning:
```
inconsistent: Requested package wireguard that is not available.
```
In that case, it is suggested that users should take a look at ``/etc/updater/conf.d/opkg-auto.ua`` and replace ``wireguard`` by ``kmod-wireguard``.Turris OS 6.0https://gitlab.nic.cz/turris/os/build/-/issues/281Package python3-flask requires package python3-click that is not available2023-08-16T10:57:28+02:00Lukas JelinekPackage python3-flask requires package python3-click that is not availableAfter updating Turris Omnia to TOS 5.2.3 (in HBK), it displayed this error message twice:
```
Updater failed:
inconsistent: Package python3-flask requires package python3-click that is not available.
```After updating Turris Omnia to TOS 5.2.3 (in HBK), it displayed this error message twice:
```
Updater failed:
inconsistent: Package python3-flask requires package python3-click that is not available.
```Turris OS 6.0https://gitlab.nic.cz/turris/os/build/-/issues/284Turris 1.x routers can not get kernel image on kernel 5.102023-08-16T10:57:14+02:00Josef SchlehoferTurris 1.x routers can not get kernel image on kernel 5.10It seems that there is something going on with kernel 5.10 on Turris 1.x routers.
Here is the log:
```
U-Boot 2015.04-04654-gbcfb33e-dirty (Jun 26 2015 - 12:50:49)
CPU0: P2020E, Version: 2.1, (0x80ea0021)
Core: e500, Version: 5.1, (0...It seems that there is something going on with kernel 5.10 on Turris 1.x routers.
Here is the log:
```
U-Boot 2015.04-04654-gbcfb33e-dirty (Jun 26 2015 - 12:50:49)
CPU0: P2020E, Version: 2.1, (0x80ea0021)
Core: e500, Version: 5.1, (0x80211051)
Clock Configuration:
CPU0:1200 MHz, CPU1:1200 MHz,
CCB:600 MHz,
DDR:400 MHz (800 MT/s data rate) (Asynchronous), LBC:37.500 MHz
L1: D-cache 32 KiB enabled
I-cache 32 KiB enabled
wdt status 00000005 reset
Watchdog enabled
Board: TURRIS CPLD: V4.1 PCBA: V4.0
Error, wrong i2c adapter 2 max 2 possible
in: 56
out: 0
io_config: 255
rom_loc: nor upper bank
SD/MMC : 4-bit Mode
eSPI : Enabled
I2C: Error, wrong i2c adapter 2 max 2 possible
ready
SPI: ready
DRAM: Error, wrong i2c adapter 2 max 2 possible
Detected UDIMM 9905594-003.A00G
WARNING: Calling __hwconfig without a buffer and before environment is ready
WARNING: Calling __hwconfig without a buffer and before environment is ready
2 GiB (DDR3, 64-bit, CL=6, ECC off)
Flash: 16 MiB
L2: 512 KiB enabled
NAND: 256 MiB
MMC: FSL_SDHC: 0
PCIe1: Root Complex of mini PCIe SLOT, no link, regs @ 0xffe0a000
PCIe1: Bus 00 - 00
PCIe2: Root Complex of PCIe SLOT, x1 gen1, regs @ 0xffe09000
02:00.0 - 168c:0030 - Network controller
PCIe2: Bus 01 - 02
PCIe3: Root Complex of PCIe SLOT, x1 gen1, regs @ 0xffe08000
04:00.0 - 104c:8241 - Serial bus controller
PCIe3: Bus 03 - 04
Error, wrong i2c adapter 2 max 2 possible
In: serial
Out: serial
Err: serial
Net: Phy 5 not found
PHY reset timed out
eTSEC1
Error: eTSEC1 address not set.
, eTSEC2
Error: eTSEC2 address not set.
, eTSEC3 [PRIME]
Error: eTSEC3 address not set.
Hit any key to stop autoboot: 0
BOOT NAND
reading zImage
8929664 bytes read in 389 ms (21.9 MiB/s)
wdt status 00000003
reading fdt
12147 bytes read in 13 ms (912.1 KiB/s)
WARNING: adjusting available memory to 30000000
Wrong Image Format for bootm command
ERROR: can't get kernel image!
```Turris OS 7.0https://gitlab.nic.cz/turris/os/build/-/issues/288Check-packages.py is not found2023-08-16T10:56:22+02:00Josef SchlehoferCheck-packages.py is not foundThis was reported by Jenkins (run 2215) on HBD branch for Turris 1.x router:
```
/tmp/hudson18271722316329023503.sh: 23: /tmp/hudson18271722316329023503.sh: ./helpers/check-packages.py: not found
+ echo Packages check reported some issu...This was reported by Jenkins (run 2215) on HBD branch for Turris 1.x router:
```
/tmp/hudson18271722316329023503.sh: 23: /tmp/hudson18271722316329023503.sh: ./helpers/check-packages.py: not found
+ echo Packages check reported some issues!
Packages check reported some issues!
FATAL: Remote call on slave08 failed
```https://gitlab.nic.cz/turris/os/build/-/issues/314/dev mounted twice2022-01-03T15:06:18+01:00Ghost User/dev mounted twiceThis is only a minor annoyance, but /dev is mounted twice:
```
# mount | grep " on /dev "
devtmpfs on /dev type devtmpfs (rw,relatime,size=1033476k,nr_inodes=189059,mode=755)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,size=512k,mode=7...This is only a minor annoyance, but /dev is mounted twice:
```
# mount | grep " on /dev "
devtmpfs on /dev type devtmpfs (rw,relatime,size=1033476k,nr_inodes=189059,mode=755)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,size=512k,mode=755)
```
I believe the first (type devtmpfs) mount is coming from the kernel config option CONFIG_KERNEL_DEVTMPFS_MOUNT=y, while the second (type tmpfs) mount is coming from patches/openwrt/to-upstream/0022-procd-New-style-of-cgroups.patch:
```
+++ b/package/system/procd/patches/new-style-of-cgroup-hiearchy.patch
++++ b/initd/early.c
+ mount("tmpfs", "/dev", "tmpfs", MS_NOATIME | MS_NOSUID, "mode=0755,size=512K");
```
I believe that second mount (type tmpfs in early_mounts() from that patch) is redundant & should be removed (or made conditional on a check if /dev is already mounted, if we can't rely on CONFIG_KERNEL_DEVTMPFS_MOUNT=y always being set).
Thanks,
Conway S. SmithTurris OS 6.0https://gitlab.nic.cz/turris/os/build/-/issues/338compile_pkgs unrecognized parameters2022-04-01T17:46:50+02:00Adam Konrádcompile_pkgs unrecognized parametersHello, I'd like to report an issue with the compile_pkgs script.
```
uname -srm
Linux 5.10.102-99.473.amzn2.aarch64 aarch64
```
This is a centos based distro.
I'm getting the following:
```
../build/compile_pkgs prepare_tools -t omni...Hello, I'd like to report an issue with the compile_pkgs script.
```
uname -srm
Linux 5.10.102-99.473.amzn2.aarch64 aarch64
```
This is a centos based distro.
I'm getting the following:
```
../build/compile_pkgs prepare_tools -t omnia
There is no such option or command: prepare_tools
```
```
../build/compile_pkgs -t omnia
...
Checking 'rsync'... ok.
make[1] diffconfig
Setting ccache paths
Compiling tools
../build/compile_pkgs: line 58: BUILD_ARGS[@]: unbound variable
```
I'm not sure if this is some tool version mismatch or a problem in the script.https://gitlab.nic.cz/turris/os/build/-/issues/361Please fix UNICODE / wide character support in terminal2022-08-15T14:01:27+02:00Ghost UserPlease fix UNICODE / wide character support in terminalLocal terminal over UART and also remote terminal over SSH on all Turris routers stop working after sending some UTF-8 character. SSH shell is completely ignoring LC locale settings for UTF-8 support and treats every send byte separately...Local terminal over UART and also remote terminal over SSH on all Turris routers stop working after sending some UTF-8 character. SSH shell is completely ignoring LC locale settings for UTF-8 support and treats every send byte separately, ignoring UNICODE or wide character settings. This makes terminals unusable on modern systems.
Simple reproducer: Type `echo á` then press backspace and then press enter. It should not write anything on the terminal. But currently it prints back garbage `�`.Turris OS 5.4.1https://gitlab.nic.cz/turris/os/build/-/issues/383Cannot open any Turris GUI administration after update, OpenVPN also, SSH wor...2022-11-10T09:36:17+01:00JoeKrenekCannot open any Turris GUI administration after update, OpenVPN also, SSH works only# Steps To Reproduce
1. Update from Turris OS 5 to the latest Turris OS 6
2. Try to login into Turris via turris.local or 192.168.1.1 (both http and https)
3. "web not available" tried in latest Chrome, Firefox, Safari in Windows and Mac...# Steps To Reproduce
1. Update from Turris OS 5 to the latest Turris OS 6
2. Try to login into Turris via turris.local or 192.168.1.1 (both http and https)
3. "web not available" tried in latest Chrome, Firefox, Safari in Windows and MacOS
# Expected Result
I should see login screen
# Actual Result
Internet and SSH works without access to Turris administration
Cannot connect via previously working OpenVPN
Log file: [diag.gz](/uploads/094736c689828290ce89604e2a2c6c90/diag.gz)
What old Turris 5 wanted to update: [Updater_žádá_o_autorizaci_akcí.txt](/uploads/67bd8611c11e348ea842731964c487e1/Updater_žádá_o_autorizaci_akcí.txt)
# Repeated steps
Tried to restart several times, wait, rollback, update again but same result.Turris OS 6.0.3https://gitlab.nic.cz/turris/os/build/-/issues/395smartctl issues - upgrade smartmontools package and friends to latest release2022-12-24T12:22:45+01:00krisansmartctl issues - upgrade smartmontools package and friends to latest releaseMy system:
```less
# turris omnia:
Device Turris Omnia
reForis version 1.4.1
Turris OS version 6.1.0
Turris OS branch HBS
Kernel version 5.15.84
# Installed packages:
opkg list-installed | grep ^smart
smartd - 7.2-...My system:
```less
# turris omnia:
Device Turris Omnia
reForis version 1.4.1
Turris OS version 6.1.0
Turris OS branch HBS
Kernel version 5.15.84
# Installed packages:
opkg list-installed | grep ^smart
smartd - 7.2-1
smartmontools - 7.2-1
smartmontools-drivedb - 7.2-1
# /etc/init.d/smartd restart
Dec XX XX:XX:XX turris smartd[29041]: smartd 7.2 2020-12-30 r5155 [armv7l-linux-5.15.84] (localbuild)
```
Please upgrade these packages to latest versions.
Latest release for Today is version 7.3 from 2022-02-28: https://www.smartmontools.org/browser/tags/RELEASE_7_3/smartmontools/ChangeLog
related
---
Additional info.
Current version of __smartctl__ behaves odd after interrupting its execution by pressing Ctrl-C.
For example, the interrupted command was:
```shell
# /dev/sda - hard drive connected to Turris using mPCI-E card
smartctl -x /dev/sda # pressed Ctrl-C during execution
```
Since then, I get the following program issues (when using with switches: `-i`, `-a`), the same disk:
```less
smartctl -i /dev/sda
smartctl 7.2 2020-12-30 r5155 [armv7l-linux-5.15.84] (localbuild)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
Short INQUIRY response, skip product id
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
```https://gitlab.nic.cz/turris/os/build/-/issues/428Strongswan seems to misbehave2024-03-04T10:10:06+01:00Michal HruseckyStrongswan seems to misbehavehttps://forum.turris.cz/t/turris-os-7-0-is-in-rc/19755/20https://forum.turris.cz/t/turris-os-7-0-is-in-rc/19755/20Turris OS 7.0Richard MuzikRichard Muzik