Turris Build issueshttps://gitlab.nic.cz/turris/os/build/-/issues2020-05-24T08:36:00+02:00https://gitlab.nic.cz/turris/os/build/-/issues/1472.4 GHz Wi-Fi card (ath9k) fails to load2020-05-24T08:36:00+02:00Josef Schlehofer2.4 GHz Wi-Fi card (ath9k) fails to loadA few members of our community reported to us that ath9k is not enable to load. Perhaps due to vmalloc error?
Snips from forum thread:
1.
```
2020-05-12 17:20:39 warning kernel[]: [ 17.898428] vmap allocation for size 356352 fail...A few members of our community reported to us that ath9k is not enable to load. Perhaps due to vmalloc error?
Snips from forum thread:
1.
```
2020-05-12 17:20:39 warning kernel[]: [ 17.898428] vmap allocation for size 356352 failed: use vmalloc=<size> to increase size
2020-05-12 17:20:39 warning kernel[]: [ 17.906477] kmodloader: vmalloc: allocation failure: 352256 bytes, mode:0x14000c0(GFP_KERNEL), nodemask=(null)
2020-05-12 17:20:39 info kernel[]: [ 17.916514] kmodloader cpuset=/ mems_allowed=0
2020-05-12 17:20:39 warning kernel[]: [ 17.920973] CPU: 1 PID: 1386 Comm: kmodloader Not tainted 4.14.179 #0
2020-05-12 17:20:39 warning kernel[]: [ 17.927426] Hardware name: Marvell Armada 380/385 (Device Tree)
2020-05-12 17:20:39 warning kernel[]: [ 17.933371] [<c010f8ac>] (unwind_backtrace) from [<c010b378>] (show_stack+0x10/0x14)
2020-05-12 17:20:39 warning kernel[]: [ 17.941136] [<c010b378>] (show_stack) from [<c07c0a60>] (dump_stack+0x94/0xa8)
2020-05-12 17:20:39 warning kernel[]: [ 17.948379] [<c07c0a60>] (dump_stack) from [<c01e6dc0>] (warn_alloc+0xd0/0x190)
2020-05-12 17:20:39 warning kernel[]: [ 17.955710] [<c01e6dc0>] (warn_alloc) from [<c02193f4>] (__vmalloc_node_range+0x22c/0x238)
2020-05-12 17:20:39 warning kernel[]: [ 17.964004] [<c02193f4>] (__vmalloc_node_range) from [<c010c878>] (module_alloc+0x4c/0x54)
2020-05-12 17:20:39 warning kernel[]: [ 17.972304] [<c010c878>] (module_alloc) from [<c019ffd0>] (load_module+0x9e4/0x2134)
2020-05-12 17:20:39 warning kernel[]: [ 17.980070] [<c019ffd0>] (load_module) from [<c01a1868>] (SyS_init_module+0x148/0x198)
2020-05-12 17:20:39 warning kernel[]: [ 17.988009] [<c01a1868>] (SyS_init_module) from [<c0107940>] (ret_fast_syscall+0x0/0x54)
2020-05-12 17:20:39 warning kernel[]: [ 17.996134] Mem-Info:
2020-05-12 17:20:39 warning kernel[]: [ 17.998416] active_anon:406 inactive_anon:0 isolated_anon:0
2020-05-12 17:20:39 warning kernel[]: [ 17.998416] active_file:3472 inactive_file:2011 isolated_file:0
2020-05-12 17:20:39 warning kernel[]: [ 17.998416] unevictable:0 dirty:0 writeback:0 unstable:0
2020-05-12 17:20:39 warning kernel[]: [ 17.998416] slab_reclaimable:558 slab_unreclaimable:1811
2020-05-12 17:20:39 warning kernel[]: [ 17.998416] mapped:311 shmem:4 pagetables:29 bounce:0
2020-05-12 17:20:39 warning kernel[]: [ 17.998416] free:504092 free_pcp:322 free_cma:0
2020-05-12 17:20:39 warning kernel[]: [ 18.030589] Node 0 active_anon:1708kB inactive_anon:0kB active_file:13888kB inactive_file:8044kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:1244kB dirty:0kB writeback:0kB shmem:16kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no
2020-05-12 17:20:39 warning kernel[]: [ 18.052993] Normal free:735192kB min:3476kB low:4344kB high:5212kB active_anon:0kB inactive_anon:0kB active_file:2904kB inactive_file:1860kB unevictable:0kB writepending:0kB present:786432kB managed:757276kB mlocked:0kB kernel_stack:1144kB pagetables:132kB bounce:0kB free_pcp:712kB local_pcp:168kB free_cma:0kB
2020-05-12 17:20:39 warning kernel[]: [ 18.080536] lowmem_reserve[]: 0 10240 10240
2020-05-12 17:20:39 warning kernel[]: [ 18.084768] HighMem free:1280796kB min:512kB low:2016kB high:3520kB active_anon:1584kB inactive_anon:0kB active_file:11004kB inactive_file:6196kB unevictable:0kB writepending:0kB present:1310720kB managed:1310720kB mlocked:0kB kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:684kB local_pcp:192kB free_cma:0kB
2020-05-12 17:20:39 warning kernel[]: [ 18.112480] lowmem_reserve[]: 0 0 0
2020-05-12 17:20:39 warning kernel[]: [ 18.115986] Normal: 38*4kB (U) 3*8kB (M) 5*16kB (UM) 13*32kB (UM) 4*64kB (ME) 4*128kB (ME) 5*256kB (UM) 6*512kB (UME) 6*1024kB (UME) 3*2048kB (UM) 175*4096kB (M) = 734880kB
2020-05-12 17:20:39 warning kernel[]: [ 18.131444] HighMem: 1*4kB (U) 2*8kB (UM) 9*16kB (UM) 5*32kB (M) 2*64kB (M) 1*128kB (M) 1*256kB (U) 2*512kB (UM) 1*1024kB (U) 0*2048kB 312*4096kB (M) = 1280836kB
2020-05-12 17:20:39 warning kernel[]: [ 18.145953] 5496 total pagecache pages
2020-05-12 17:20:39 warning kernel[]: [ 18.149719] 0 pages in swap cache
2020-05-12 17:20:39 warning kernel[]: [ 18.153072] Swap cache stats: add 0, delete 0, find 0/0
2020-05-12 17:20:39 warning kernel[]: [ 18.158315] Free swap = 0kB
2020-05-12 17:20:39 warning kernel[]: [ 18.161204] Total swap = 0kB
2020-05-12 17:20:39 warning kernel[]: [ 18.164107] 524288 pages RAM
2020-05-12 17:20:39 warning kernel[]: [ 18.166995] 327680 pages HighMem/MovableOnly
2020-05-12 17:20:39 warning kernel[]: [ 18.171276] 7289 pages reserved
____
2020-05-12 17:20:39 warning kernel[]: [ 18.191092] vmap allocation for size 356352 failed: use vmalloc=<size> to increase size
2020-05-12 17:20:39 warning kernel[]: [ 18.199171] kmodloader: vmalloc: allocation failure: 352256 bytes, mode:0x14000c0(GFP_KERNEL), nodemask=(null)
2020-05-12 17:20:39 info kernel[]: [ 18.209227] kmodloader cpuset=/ mems_allowed=0
2020-05-12 17:20:39 warning kernel[]: [ 18.213713] CPU: 1 PID: 1386 Comm: kmodloader Not tainted 4.14.179 #0
2020-05-12 17:20:39 warning kernel[]: [ 18.220175] Hardware name: Marvell Armada 380/385 (Device Tree)
2020-05-12 17:20:39 warning kernel[]: [ 18.226133] [<c010f8ac>] (unwind_backtrace) from [<c010b378>] (show_stack+0x10/0x14)
2020-05-12 17:20:39 warning kernel[]: [ 18.233912] [<c010b378>] (show_stack) from [<c07c0a60>] (dump_stack+0x94/0xa8)
2020-05-12 17:20:39 warning kernel[]: [ 18.241172] [<c07c0a60>] (dump_stack) from [<c01e6dc0>] (warn_alloc+0xd0/0x190)
2020-05-12 17:20:39 warning kernel[]: [ 18.248514] [<c01e6dc0>] (warn_alloc) from [<c02193f4>] (__vmalloc_node_range+0x22c/0x238)
2020-05-12 17:20:39 warning kernel[]: [ 18.256816] [<c02193f4>] (__vmalloc_node_range) from [<c010c878>] (module_alloc+0x4c/0x54)
2020-05-12 17:20:39 warning kernel[]: [ 18.265121] [<c010c878>] (module_alloc) from [<c019ffd0>] (load_module+0x9e4/0x2134)
2020-05-12 17:20:39 warning kernel[]: [ 18.272895] [<c019ffd0>] (load_module) from [<c01a1868>] (SyS_init_module+0x148/0x198)
2020-05-12 17:20:39 warning kernel[]: [ 18.280852] [<c01a1868>] (SyS_init_module) from [<c0107940>] (ret_fast_syscall+0x0/0x54)
2020-05-12 17:20:39 err kernel[]: 18.289582] kmodloader: 4 modules could not be probed
2020-05-12 17:20:39 err kernel[]: 18.294710] kmodloader: dependency not loaded ath9k_hw
2020-05-12 17:20:39 err kernel[]: 18.299890] kmodloader: dependency not loaded ath9k_common
2020-05-12 17:20:39 err kernel[]: 18.305485] kmodloader: - ath9k - 2
2020-05-12 17:20:39 err kernel[]: 18.308997] kmodloader: dependency not loaded ath9k_hw
2020-05-12 17:20:39 err kernel[]: 18.314171] kmodloader: - ath9k_common - 1
2020-05-12 17:20:39 err kernel[]: 18.318289] kmodloader: dependency not loaded ath9k_hw
2020-05-12 17:20:39 err kernel[]: 18.323457] kmodloader: dependency not loaded ath9k_common
2020-05-12 17:20:39 err kernel[]: 18.328969] kmodloader: - ath9k_htc - 2
2020-05-12 17:20:39 err kernel[]: 18.332829] kmodloader: - ath9k_hw - 0
```
2.
```
[680735.389653] vmap allocation for size 356352 failed: use vmalloc= to increase size
[680735.397809] modprobe: vmalloc: allocation failure: 352256 bytes, mode:0x14000c0(GFP_KERNEL), nodemask=(null)
[680735.407768] modprobe cpuset=/ mems_allowed=0
[680735.412139] CPU: 0 PID: 12942 Comm: modprobe Not tainted 4.14.172 #0
[680735.418593] Hardware name: Marvell Armada 380/385 (Device Tree)
[680735.424623] [] (unwind_backtrace) from [] (show_stack+0x10/0x14)
[680735.432475] [] (show_stack) from [] (dump_stack+0x94/0xa8)
[680735.439807] [] (dump_stack) from [] (warn_alloc+0xd0/0x190)
[680735.447226] [] (warn_alloc) from [] (__vmalloc_node_range+0x22c/0x238)
[680735.455598] [] (__vmalloc_node_range) from [] (module_alloc+0x4c/0x54)
[680735.463974] [] (module_alloc) from [] (load_module+0x9e4/0x2134)
[680735.471825] [] (load_module) from [] (SyS_init_module+0x148/0x198)
[680735.479851] [] (SyS_init_module) from [] (ret_fast_syscall+0x0/0x54)
[680735.488070] Mem-Info:
[680735.490468] active_anon:27454 inactive_anon:40004 isolated_anon:0
[680735.490468] active_file:100157 inactive_file:91920 isolated_file:0
[680735.490468] unevictable:0 dirty:36 writeback:0 unstable:0
[680735.490468] slab_reclaimable:4080 slab_unreclaimable:4248
[680735.490468] mapped:7240 shmem:27177 pagetables:413 bounce:0
[680735.490468] free:238316 free_pcp:400 free_cma:0
```
More details in huge thread: https://forum.turris.cz/t/turris-os-5-0-0-is-released-in-hbt/12733/55?u=pepeTurris OS 5.0https://gitlab.nic.cz/turris/os/build/-/issues/145foris & luci unreachable on 5.02020-05-14T17:22:28+02:00Claude Nobsforis & luci unreachable on 5.0some recent update broke foris & luci (but not reforis) on my turris omnia.
current version:
TurrisOS 5.0.0 a8c92e9eda1f9f801345255eac80bf16f65f6f4c
# symptoms
foris would just not show up
luci, after a long time shows :
`/usr/lib/lu...some recent update broke foris & luci (but not reforis) on my turris omnia.
current version:
TurrisOS 5.0.0 a8c92e9eda1f9f801345255eac80bf16f65f6f4c
# symptoms
foris would just not show up
luci, after a long time shows :
`/usr/lib/lua/luci/dispatcher.lua:426: /etc/config/luci seems to be corrupt, unable to find section 'main'`
# solution
`ln -sfn /usr/bin/python3 /usr/bin/python`
don't know whether that fix solves the issue or is just a workaround. but hey it works.Turris OS 5.0Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/build/-/issues/141Mox: kernel fails to boot because of sparse blocks2020-04-27T09:54:46+02:00Karel KociMox: kernel fails to boot because of sparse blocksU-boot in Turris Mox fails to correctly reads sparse blocks from BTRFS. Boot fails if kernel is saved to FS with such content.
Common output on serial console:
```
U-Boot 2018.11 (Dec 16 2018 - 12:50:19 +0000), Build: jenkins-turris-os-...U-boot in Turris Mox fails to correctly reads sparse blocks from BTRFS. Boot fails if kernel is saved to FS with such content.
Common output on serial console:
```
U-Boot 2018.11 (Dec 16 2018 - 12:50:19 +0000), Build: jenkins-turris-os-packages-kittens-mox-90
DRAM: 512 MiB
Enabling Armada 3720 wComphy-0: SGMII1 3.125 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: 000000000000000
ECDSA Public Key: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SD/eMMC version: SD
Module Topology:
1: Passthrough Mini-PCIe Module
2: USB 3.0 Module (4 ports)
3: Topaz Switch Module (4-port)
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
963 bytes read in 90 ms (9.8 KiB/s)
## Executing script at 04d00000
19412 bytes read in 61 ms (310.5 KiB/s)
btrfs_map_logical_to_physical: Cannot map logical address 0 to physical
btrfs_file_read: Error reading extent
An error occured while reading file /@/boot/Image
0 bytes read in 384 ms (0 Bytes/s)
## Flattened Device Tree blob at 04f00000
Booting using the fdt blob at 0x4f00000
Loading Device Tree to 000000001bf14000, end 000000001bf1bbd3 ... OK
Starting kernel ...
"Synchronous Abort" handler, esr 0x02000000
elr: ffffffffe5a4d000 lr : 00000000000026c4 (reloc)
elr: 0000000005980000 lr : 000000001ff356c4
x0 : 000000001bf14000 x1 : 0000000000000000
x2 : 0000000000000000 x3 : 0000000000000000
x4 : 0000000005080000 x5 : 0000000000000001
x6 : 0000000000000008 x7 : 0000000000000000
x8 : 000000001c100000 x9 : 0000000000000002
x10: 000000000a200023 x11: 0000000000000002
x12: 0000000000000002 x13: 00000000ffffffff
x14: 0000000000000000 x15: 000000001ff34b34
x16: 0000000000000002 x17: 000000001bf1bbd4
x18: 000000001bf22de8 x19: 000000001ffd39d0
x20: 0000000000000000 x21: 0000000000000000
x22: 0000000000000003 x23: 000000001bfd3238
x24: 000000001ffc1b00 x25: 0000000000000000
x26: 000000001ff356ec x27: 0000000000000400
x28: 000000001bfd3260 x29: 000000001bf1d890
Resetting CPU ...
resetting ...
```Turris OS 5.0Michal HruseckyMichal Hruseckyhttps://gitlab.nic.cz/turris/os/build/-/issues/140Updater put Mox into reboot loop2020-04-23T00:04:53+02:00Martin MatějekUpdater put Mox into reboot loop## Description
After update to latest updater from @kkoci personal repo (https://cynerd.cz/repo/turris/hbk/omnia/personal-pkgs-repo_1.5.0_arm_cortex-a9_vfpv3.ipk) and once you reboot mox, it gets into reboot loop.
```
U-Boot 2018.11 (De...## Description
After update to latest updater from @kkoci personal repo (https://cynerd.cz/repo/turris/hbk/omnia/personal-pkgs-repo_1.5.0_arm_cortex-a9_vfpv3.ipk) and once you reboot mox, it gets into reboot loop.
```
U-Boot 2018.11 (Dec 16 2018 - 12:50:19 +0000), Build: jenkins-turris-os-packages-kittens-mox-90
DRAM: 512 MiB
Enabling Armada 3720 wComphy-0: SGMII1 3.125 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: 0000000D300001C8
ECDSA Public Key: 0200ebe831e338c1e225d6d332d8fdf73418b88619b63e3d100e767c58c7f57eaf2948f90c9dd78fd9fbbb64352a65cb9a95870f06cee2b94a8368ac1c759f6c1ed111
SD/eMMC version: SD
Module Topology:
1: Passthrough Mini-PCIe Module
2: USB 3.0 Module (4 ports)
3: Topaz Switch Module (4-port)
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
963 bytes read in 90 ms (9.8 KiB/s)
## Executing script at 04d00000
19412 bytes read in 61 ms (310.5 KiB/s)
btrfs_map_logical_to_physical: Cannot map logical address 0 to physical
btrfs_file_read: Error reading extent
An error occured while reading file /@/boot/Image
0 bytes read in 384 ms (0 Bytes/s)
## Flattened Device Tree blob at 04f00000
Booting using the fdt blob at 0x4f00000
Loading Device Tree to 000000001bf14000, end 000000001bf1bbd3 ... OK
Starting kernel ...
"Synchronous Abort" handler, esr 0x02000000
elr: ffffffffe5a4d000 lr : 00000000000026c4 (reloc)
elr: 0000000005980000 lr : 000000001ff356c4
x0 : 000000001bf14000 x1 : 0000000000000000
x2 : 0000000000000000 x3 : 0000000000000000
x4 : 0000000005080000 x5 : 0000000000000001
x6 : 0000000000000008 x7 : 0000000000000000
x8 : 000000001c100000 x9 : 0000000000000002
x10: 000000000a200023 x11: 0000000000000002
x12: 0000000000000002 x13: 00000000ffffffff
x14: 0000000000000000 x15: 000000001ff34b34
x16: 0000000000000002 x17: 000000001bf1bbd4
x18: 000000001bf22de8 x19: 000000001ffd39d0
x20: 0000000000000000 x21: 0000000000000000
x22: 0000000000000003 x23: 000000001bfd3238
x24: 000000001ffc1b00 x25: 0000000000000000
x26: 000000001ff356ec x27: 0000000000000400
x28: 000000001bfd3260 x29: 000000001bf1d890
Resetting CPU ...
resetting ...
```
## Affected HW and SW
Mox 512 MB, TOS 5.0.0
## Related
https://gitlab.labs.nic.cz/turris/turris-os-packages/-/merge_requests/248Turris OS 5.0https://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/134python-requests dependency issues2020-04-06T18:40:32+02:00Vojtech Myslivecpython-requests dependency issuesThere is some issue with python(3) requests which causes sentinel-certgen to fail.
Turris MOX in current HBK (%"Turris OS 5.0"):
```
root@mox: ~ # sentinel-certgen certs --hooks-dir /etc/sentinel-certgen_hooks.d
Traceback (most recent c...There is some issue with python(3) requests which causes sentinel-certgen to fail.
Turris MOX in current HBK (%"Turris OS 5.0"):
```
root@mox: ~ # sentinel-certgen certs --hooks-dir /etc/sentinel-certgen_hooks.d
Traceback (most recent call last):
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 583, in _build_master
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 900, in require
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 791, in resolve
pkg_resources.ContextualVersionConflict: (idna 2.9 (/usr/lib/python3.7/site-packages), Requirement.parse('idna<2.9,>=2.5'), {'requests'})
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/sentinel-certgen", line 6, in <module>
from pkg_resources import load_entry_point
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3250, in <module>
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3234, in _call_aside
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3263, in _initialize_master_working_set
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 585, in _build_master
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 598, in _build_from_requirements
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 786, in resolve
pkg_resources.DistributionNotFound: The 'idna<2.9,>=2.5' distribution was not found and is required by requests
```
same problem was confirmed on Omnia as well.Turris OS 5.0https://gitlab.nic.cz/turris/os/build/-/issues/133Remove sysupgrade2023-08-16T11:03:45+02:00Josef SchlehoferRemove sysupgradeSysupgrade is present in Turris OS 5.0+. We should remove it. It is a dangerous to have it in system.
Reported here and confirmed: https://forum.turris.cz/t/bricked-turris-omnia-after-turris-os-5-0-sysupgrade-openwrt-19-07-2/12558?u=pepeSysupgrade is present in Turris OS 5.0+. We should remove it. It is a dangerous to have it in system.
Reported here and confirmed: https://forum.turris.cz/t/bricked-turris-omnia-after-turris-os-5-0-sysupgrade-openwrt-19-07-2/12558?u=pepeTurris OS 5.0Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/build/-/issues/130Turris 1.x has only 752M RAM2023-08-16T11:06:31+02:00Josef SchlehoferTurris 1.x has only 752M RAM![image](/uploads/3571c6c392d7ca160aff97e3d4b75daa/image.png)![image](/uploads/3571c6c392d7ca160aff97e3d4b75daa/image.png)Turris OS 5.0https://gitlab.nic.cz/turris/os/build/-/issues/129extended Active Connections2020-03-17T13:26:19+01:00Jan Horacekextended Active ConnectionsIt would be advisable to increase the number of active connections that the router can serve to a value corresponding to at least the version of TOS 3.x ie 65536 or moreIt would be advisable to increase the number of active connections that the router can serve to a value corresponding to at least the version of TOS 3.x ie 65536 or moreTurris 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/124Turris 1.x: fails to boot2021-07-28T14:03:28+02:00Karel KociTurris 1.x: fails to bootBooting Turris 1.x in HBL fails to continue. Last message is warning.
```
Hit any key to stop autoboot: 0
BOOT NAND
reading zImage
4310887 bytes read in 197 ms (20.9 MiB/s)
wdt status 00000003
reading fdt
13241 bytes read in 14 ms (92...Booting Turris 1.x in HBL fails to continue. Last message is warning.
```
Hit any key to stop autoboot: 0
BOOT NAND
reading zImage
4310887 bytes read in 197 ms (20.9 MiB/s)
wdt status 00000003
reading fdt
13241 bytes read in 14 ms (922.9 KiB/s)
WARNING: adjusting available memory to 30000000
## Booting kernel from Legacy Image at 02100000 ...
Image Name: Linux-4.14.171
Created: 2020-03-03 0:13:45 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 4310823 Bytes = 4.1 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 02000000
Booting using the fdt blob at 0x2000000
Uncompressing Kernel Image ... OK
Loading Device Tree to 03ff9000, end 03fff3b8 ... OK
WARNING: could not find compatible node fsl-usb2-dr
```
The question is why it fails to boot. It seems to correctly load everything but kernel just prints only this warning and that is it.Turris OS 5.0https://gitlab.nic.cz/turris/os/build/-/issues/121Package mariadb-server requires package libaio that is not available2023-08-16T11:05:28+02:00Karel KociPackage mariadb-server requires package libaio that is not availableTurris OS 5.0https://gitlab.nic.cz/turris/os/build/-/issues/120Requested package lvm2 that is not available2023-08-16T11:05:31+02:00Karel KociRequested package lvm2 that is not availableTurris OS 5.0https://gitlab.nic.cz/turris/os/build/-/issues/119Package tvheadend requires package libx264 that is not available2020-03-09T19:06:22+01:00Karel KociPackage tvheadend requires package libx264 that is not availableTurris OS 5.0https://gitlab.nic.cz/turris/os/build/-/issues/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/111Borked update of libubox causes procd crash but fixes security issue2023-08-16T11:03:51+02:00Karel KociBorked update of libubox causes procd crash but fixes security issueOpenWrt updated in 19.07 libubox and introduced bug that can be invoked by using `procd_add_param pidfile` in init file. This causes in some cases crash of procd.
Initially we fixed it by reverting it but it is required for security fix...OpenWrt updated in 19.07 libubox and introduced bug that can be invoked by using `procd_add_param pidfile` in init file. This causes in some cases crash of procd.
Initially we fixed it by reverting it but it is required for security fix in ucert. We do not want to revert ucert as well but it fails to build otherwise.Turris OS 5.0https://gitlab.nic.cz/turris/os/build/-/issues/100Omnia gets stuck during boot in case of broken atsha chip2023-08-16T11:06:37+02:00Jan PavlinecOmnia gets stuck during boot in case of broken atsha chipI'm not sure how valid is this issue. But in case of broken atsha chip, Omnia gets stucks during boot because it waits for entropy for **Lighttpd cert generation**.
Script responsible for this is in /etc/default-uci, so maybe a solutio...I'm not sure how valid is this issue. But in case of broken atsha chip, Omnia gets stucks during boot because it waits for entropy for **Lighttpd cert generation**.
Script responsible for this is in /etc/default-uci, so maybe a solution could be to ensure that haveged is running before running scripts from there...Turris OS 5.0https://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.0