Turris Build issueshttps://gitlab.nic.cz/turris/os/build/-/issues2019-09-02T11:53:53+02:00https://gitlab.nic.cz/turris/os/build/-/issues/72Updater won't remove packages with webapp2019-09-02T11:53:53+02:00Karel KociUpdater won't remove packages with webappThis is same issue and reason as in https://gitlab.labs.nic.cz/turris/turris-build/issues/70 but for webapp packages.This is same issue and reason as in https://gitlab.labs.nic.cz/turris/turris-build/issues/70 but for webapp packages.Turris OS 4.0https://gitlab.nic.cz/turris/os/build/-/issues/70Updater won't remove Foris or Luci plugins because of language packages2019-09-02T11:54:15+02:00Karel KociUpdater won't remove Foris or Luci plugins because of language packagesThere is a bug with new code introduced in 1e07e9d4c89bfa004dbc9f6e44ba4ccf0e867e2a and 9656c3d85417e9221c87a98dcc4e36708c3fea22. The problem is that it installs translation packages if package is installed but if request to install that...There is a bug with new code introduced in 1e07e9d4c89bfa004dbc9f6e44ba4ccf0e867e2a and 9656c3d85417e9221c87a98dcc4e36708c3fea22. The problem is that it installs translation packages if package is installed but if request to install that package is no longer present it won't remove it nor translation package. That is because it is already installed. Mentioned code results to languages and in proxy installed package is required. That means it is never removed.
The correct behavior should be that if request to that package is dropped then it is removed and languages are removed as well.
This leads to some weak dependencies but we do not have anything like that in updater so we should think about how to do it with what we have in updater.Turris OS 4.0https://gitlab.nic.cz/turris/os/build/-/issues/30block-mount fstab service causes unmount of all FSs2019-06-05T13:29:45+02:00Karel Kociblock-mount fstab service causes unmount of all FSsRunning `/etc/init.d/fstab restart` causes all FSs to be unmounted and not mounted back. This is because it does not have reboot section so default one is provided. That one just calls `stop` and `start` in sequence. Problem is that `sto...Running `/etc/init.d/fstab restart` causes all FSs to be unmounted and not mounted back. This is because it does not have reboot section so default one is provided. That one just calls `stop` and `start` in sequence. Problem is that `stop` unmounts all FSs but `start` just prints message that `fstab` init script is obsoleted.
This is problematic because as part of update process we restart services. Restart of this service then causes just unmount of all additional FSs.Turris OS 4.0https://gitlab.nic.cz/turris/os/build/-/issues/19Syslog spammed with promiscuous mode messages2019-06-07T14:38:39+02:00Vojtech MyslivecSyslog spammed with promiscuous mode messages## Affected devices:
* MOX
## Affected HW combinations:
* MOX A + MOX B + MOX C
* MOX A + MOX E
## TurrisOS branch + date:
* HBS - 2019-03-10 (alfa 2)
* HBD - 2019-03-14
## Affected SW component (best guess)
* kernel / network config...## Affected devices:
* MOX
## Affected HW combinations:
* MOX A + MOX B + MOX C
* MOX A + MOX E
## TurrisOS branch + date:
* HBS - 2019-03-10 (alfa 2)
* HBD - 2019-03-14
## Affected SW component (best guess)
* kernel / network configuration
## Detailed description
Kernel spam syslog with *promiscuous mode* messages off `br-guest_turris` interface. There is always "on" and "off" consecutive messages circa ten times a second.
### Setup (+stacktraces/screenshots)
*syslog* fragment:
```
Mar 10 13:07:12 turris kernel: [ 2860.424244] device br-guest_turris entered promiscuous mode
Mar 10 13:07:12 turris kernel: [ 2860.494298] device br-guest_turris left promiscuous mode
Mar 10 13:07:12 turris kernel: [ 2861.014159] device br-guest_turris entered promiscuous mode
Mar 10 13:07:13 turris kernel: [ 2861.084074] device br-guest_turris left promiscuous mode
Mar 10 13:07:13 turris kernel: [ 2861.604066] device br-guest_turris entered promiscuous mode
Mar 10 13:07:13 turris kernel: [ 2861.663915] device br-guest_turris left promiscuous mode
```
### Unexpected behaviour
Log is full of useless messages. Changing this states probably slow down CPU/kernel from useful work (such as routing :slight\_smile: )
### Expected behaviour
Promiscuous mode is not changed so often or not at all.Turris OS 4.0https://gitlab.nic.cz/turris/os/build/-/issues/13Device tree patching fails if SFP module is connected as first module2019-05-07T13:53:14+02:00Karel KociDevice tree patching fails if SFP module is connected as first moduleI connected SFP module as only module to Mox and it fails to start with following error in U-boot.
```
U-Boot 2018.11 (Dec 03 2018 - 09:33:41 +0000)
DRAM: 512 MiB
Enabling Armada 3720 wComphy-0: SGMII1 1.25 Gbps
Comphy-1: PEX0 ...I connected SFP module as only module to Mox and it fails to start with following error in U-boot.
```
U-Boot 2018.11 (Dec 03 2018 - 09:33:41 +0000)
DRAM: 512 MiB
Enabling Armada 3720 wComphy-0: SGMII1 1.25 Gbps
Comphy-1: PEX0 5 Gbps
Comphy-2: USB3_HOST0 5 Gbps
MMC: sdhci@d8000: 0
Loading Environment from SPI Flash... SF: Detected w25q64dw with page size 256 Bytes, erase size 4 KiB, total 8 MiB
OK
Model: CZ.NIC Turris Mox Board
Net: eth0: neta@30000
Turris Mox:
Board version: 22
RAM size: 512 MiB
Serial Number: 0000000D3000001B
ECDSA Public Key: 030149fd703bed9cbd664723986eaf76a2e4c1ef45ccb845dda2dab5b21ed0605b5a75abd9577d9bb29f0a88fc9d9c4d034dbb20332152075ede0c7199e0e8d9d2bc70
SD/eMMC version: SD
Module Topology:
1: SFP Module
Hit any key to stop autoboot: 0
gpio: pin GPIO221 (gpio 57) value is 0
gpio: pin GPIO220 (gpio 56) value is 1
SF: Detected w25q64dw with page size 256 Bytes, erase size 4 KiB, total 8 MiB
device 0 offset 0x7f0000, size 0x10000
SF: 65536 bytes @ 0x7f0000 Read: OK
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
403 bytes read in 72 ms (4.9 KiB/s)
## Executing script at 04d00000
9959432 bytes read in 482 ms (19.7 MiB/s)
19292 bytes read in 66 ms (285.2 KiB/s)
## Flattened Device Tree blob at 04f00000
Booting using the fdt blob at 0x4f00000
Loading Device Tree to 000000001bf14000, end 000000001bf1bb5b ... OK
ERROR: board-specific fdt fixup failed: FDT_ERR_NOTFOUND
- must RESET the board to recover.
FDT creation failed! hanging...### ERROR ### Please RESET the board ###
```Turris OS 4.0Marek BehunMarek Behunhttps://gitlab.nic.cz/turris/os/build/-/issues/12SFP port on Turris Omnia does not work2019-05-07T13:53:14+02:00Karel KociSFP port on Turris Omnia does not workThere seems to be some problem with SFP on Omnia. It is not detected correctly and reports errors.
This was initially reported on forum: https://forum.turris.cz/t/turris-os-4-0-alpha4-is-out/9836/22
I reproduced it successfully with di...There seems to be some problem with SFP on Omnia. It is not detected correctly and reports errors.
This was initially reported on forum: https://forum.turris.cz/t/turris-os-4-0-alpha4-is-out/9836/22
I reproduced it successfully with different SFP module.
```
[ 4.716114] mdio_bus f1072004.mdio-mii: /soc/internal-regs/mdio@72004/sfp has invalid PHY address
[ 4.725015] mdio_bus f1072004.mdio-mii: scan phy sfp at address 0
[ 4.731127] mdio_bus f1072004.mdio-mii: scan phy sfp at address 1
[ 4.737241] mdio_bus f1072004.mdio-mii: scan phy sfp at address 2
[ 4.743354] mdio_bus f1072004.mdio-mii: scan phy sfp at address 3
```
Scan goes up to address 31 and then stops.Turris OS 4.0https://gitlab.nic.cz/turris/os/build/-/issues/99A CTI router can't update to TOS 4.0.22019-12-11T15:57:10+01:00Vojtech MyslivecA CTI router can't update to TOS 4.0.2A CTI Omnia router in HBS:
```
root@skolka:~# pkgupdate
INFO:Target Turris OS: 4.0.2
WARN:Package wpad is in cyclic dependency. It might fail its post-install script.
WARN:Package hostapd is in cyclic dependency. It might fail its post...A CTI Omnia router in HBS:
```
root@skolka:~# pkgupdate
INFO:Target Turris OS: 4.0.2
WARN:Package wpad is in cyclic dependency. It might fail its post-install script.
WARN:Package hostapd is in cyclic dependency. It might fail its post-install script.
WARN:Requested package pkglists-l10n-cs that is missing, ignoring as requested.
WARN:Requested package luci-i18n-adblock-en that is missing, ignoring as requested.
WARN:Requested package luci-i18n-adblock-cs that is missing, ignoring as requested.
WARN:Requested package luci-i18n-bcp38-en that is missing, ignoring as requested.
WARN:Requested package luci-i18n-bcp38-cs that is missing, ignoring as requested.
WARN:Requested package luci-i18n-mjpg-streamer-en that is missing, ignoring as requested.
WARN:Requested package luci-i18n-mjpg-streamer-cs that is missing, ignoring as requested.
WARN:Requested package luci-i18n-sqm-en that is missing, ignoring as requested.
WARN:Requested package luci-i18n-sqm-cs that is missing, ignoring as requested.
WARN:Requested package luci-i18n-rainbow-en that is missing, ignoring as requested.
WARN:Requested package luci-i18n-rainbow-cs that is missing, ignoring as requested.
line not found
line not found
line not found
line not found
line not found
ERROR:
inconsistent: Requested package turris-survey that is not available.
```
As the output says, updater tries to install `turris-survey` package, which is not available.Turris OS 4.0.2https://gitlab.nic.cz/turris/os/build/-/issues/97Omnia reboots when wifi is accessed2019-12-09T16:00:13+01:00Karel KociOmnia reboots when wifi is accessedThere is problem in latest HBK and HBT. Omnia reboots (provably because of kernel panic) when wifi is acessed.
It was reported by users and I (@kkoci) was able to reproduce it as well on my home router.There is problem in latest HBK and HBT. Omnia reboots (provably because of kernel panic) when wifi is acessed.
It was reported by users and I (@kkoci) was able to reproduce it as well on my home router.Turris OS 4.0.2https://gitlab.nic.cz/turris/os/build/-/issues/96HBK: wget is removed by updater2019-11-26T18:40:17+01:00Karel KociHBK: wget is removed by updaterThere seems to be a problem with updater not wanting to install `wget` package.
The combination of these two commits probably caused it: 6425621c66c7aff60a47a95bc0d6cee1e8a4fe73 80f46e2b75fbe2baa4b5ca76dbc42b8e556d5e04There seems to be a problem with updater not wanting to install `wget` package.
The combination of these two commits probably caused it: 6425621c66c7aff60a47a95bc0d6cee1e8a4fe73 80f46e2b75fbe2baa4b5ca76dbc42b8e556d5e04Turris OS 4.0.2https://gitlab.nic.cz/turris/os/build/-/issues/90Kernel for Turris1x fails to mount BTRFS root2019-11-20T10:50:22+01:00Ondřej CaletkaKernel for Turris1x fails to mount BTRFS rootJust tried current `hbk` and `hbl` medkits for Turris 1.0 (using Btrfs on SD card) and the router keeps restarting with kernel panic, because it cannot mount root fs, caused probably by this:
BTRFS error (device mmcblk0p2): superblo...Just tried current `hbk` and `hbl` medkits for Turris 1.0 (using Btrfs on SD card) and the router keeps restarting with kernel panic, because it cannot mount root fs, caused probably by this:
BTRFS error (device mmcblk0p2): superblock checksum mismatch
When rolled back manually to working Turris OS by taking the SD card out and changing `@` snapshot and `zImage`/`fdt` on FAT32 partition, the recovered TurrisOS remounted the root fs to read only due to broken FS. I had to backup all the data and recreate btrfs from scratch.
`hbt` and `hbs` branches are not affected.Turris OS 4.0.2https://gitlab.nic.cz/turris/os/build/-/issues/110Package LXC fails to build2020-01-16T14:28:16+01:00Karel KociPackage LXC fails to buildFailed to build with:
```
OpenWrt-libtool: compile: ccache_cc -DHAVE_CONFIG_H -I. -I../../src -I/home/beast/beast/workspace/turris-os-packages-kittens-omnia/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/usr/include -I/home/bea...Failed to build with:
```
OpenWrt-libtool: compile: ccache_cc -DHAVE_CONFIG_H -I. -I../../src -I/home/beast/beast/workspace/turris-os-packages-kittens-omnia/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/usr/include -I/home/beast/beast/workspace/turris-os-packages-kittens-omnia/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/include -I/home/beast/beast/workspace/turris-os-packages-kittens-omnia/build/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-7.3.0_musl_eabi/usr/include -I/home/beast/beast/workspace/turris-os-packages-kittens-omnia/build/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-7.3.0_musl_eabi/include/fortify -I/home/beast/beast/workspace/turris-os-packages-kittens-omnia/build/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-7.3.0_musl_eabi/include -fPIC -DPIC -DLXCROOTFSMOUNT=\"/usr/lib/lxc/rootfs\" -DLXCPATH=\"/srv/lxc\" -DLXC_GLOBAL_CONF=\"/etc/lxc/lxc.conf\" -DLXCINITDIR=\"/usr/lib\" -DLIBEXECDIR=\"/usr/lib\" -DLXCTEMPLATEDIR=\"/usr/share/lxc/templates\" -DLXCTEMPLATECONFIG=\"/usr/share/lxc/config\" -DLOGPATH=\"/var/log/lxc\" -DLXC_DEFAULT_CONFIG=\"/etc/lxc/default.conf\" -DLXC_USERNIC_DB=\"/var/run/lxc/nics\" -DLXC_USERNIC_CONF=\"/etc/lxc/lxc-usernet\" -DDEFAULT_CGROUP_PATTERN=\"lxc/%n\" -DRUNTIME_PATH=\"/var/run\" -DSBINDIR=\"/usr/sbin\" -I ../../src -I ../../src/lxc -I ../../src/lxc/storage -I ../../src/lxc/cgroups -DHAVE_SECCOMP -I/home/beast/beast/workspace/turris-os-packages-kittens-omnia/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/usr/include -pthread -Os -pipe -mcpu=cortex-a9 -mfpu=vfpv3-d16 -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable -Wno-error=unused-result -mfloat-abi=hard -iremap/home/beast/beast/workspace/turris-os-packages-kittens-omnia/build/build_dir/target-arm_cortex-a9+vfpv3_musl_eabi/lxc-3.0.3:lxc-3.0.3 -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro -fdiagnostics-color -Wimplicit-fallthrough -Wcast-align -fno-strict-aliasing -fstack-protector-strong -g -Werror=implicit-function-declaration -Wvla -std=gnu11 -Werror -MT liblxc_la-seccomp.lo -MD -MP -MF .deps/liblxc_la-seccomp.Tpo -c seccomp.c -fPIC -DPIC -o .libs/liblxc_la-seccomp.o
In file included from �[01m�[Kseccomp.c:28:0�[m�[K:
�[01m�[K/home/beast/beast/workspace/turris-os-packages-kittens-omnia/build/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/usr/include/seccomp.h:705:10:�[m�[K �[01;31m�[Kfatal error: �[m�[Kseccomp-syscalls.h: No such file or directory
#include �[01;31m�[K<seccomp-syscalls.h>�[m�[K
�[01;31m�[K^~~~~~~~~~~~~~~~~~~~�[m�[K
compilation terminated.
```Turris OS 4.0.5https://gitlab.nic.cz/turris/os/build/-/issues/104Turris 1.x - flooding syslog with mmcblk0: error -84 transferring data and mm...2020-01-15T10:46:50+01:00Josef SchlehoferTurris 1.x - flooding syslog with mmcblk0: error -84 transferring data and mmc0: Internal clock never stabilised.I have been running HBK branch on Turris 1.1 for some time, but with the recent builds, my syslog is flooded with those messages:
```
Jan 7 20:59:48 turris kernel: [93318.602435] mmcblk0: error -84 transferring data, sector 903456, nr...I have been running HBK branch on Turris 1.1 for some time, but with the recent builds, my syslog is flooded with those messages:
```
Jan 7 20:59:48 turris kernel: [93318.602435] mmcblk0: error -84 transferring data, sector 903456, nr 64, cmd response 0x900, card status 0xc00
Jan 7 20:59:48 turris kernel: [93318.632515] mmc0: Internal clock never stabilised.
```
So, I thought this is microSD card issue as it happened on one our routers at work, which was running HBD. I removed the microSD card, insert there a new one, flashed it with HBS branch and it was running for an hour flawlessly. I used `switch-branch` to `hbk` and my router almost does not want to boot up, because those messages were back.Turris OS 4.0.5https://gitlab.nic.cz/turris/os/build/-/issues/103crashes in Foris (controller | client)2023-08-16T11:05:33+02:00Ghost Usercrashes in Foris (controller | client)>* {"kernel":"4.14.162","hostname":"to","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"cznic,turris-omnia","release":{"distribution":TurrisOS","version":"5.0-dev","revision":"e7908af","target":"mvebu/cortexa9...>* {"kernel":"4.14.162","hostname":"to","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"cznic,turris-omnia","release":{"distribution":TurrisOS","version":"5.0-dev","revision":"e7908af","target":"mvebu/cortexa9","description":"TurrisOS 5.0-dev eb156345419953a382cda233bffa4291f5cb78d8"}}
* also happens with a TOS Master instance
___
`/etc/init.d/foris-controller start` produces
>foris-controller: Traceback (most recent call last):
>foris-controller: File "/usr/bin/foris-controller", line 11, in <module>
>foris-controller: load_entry_point('foris-controller==1.0.8', 'console_scripts', 'foris-controller')()
>foris-controller: File "/__main__.py", line 184, in main
>foris-controller: File "/mqtt.py", line 417, in __init__
>foris-controller: File "/usr/lib/python3.7/site-packages/paho/mqtt/client.py", line 937, in connect
>foris-controller: return self.reconnect()
>foris-controller: File "/usr/lib/python3.7/site-packages/paho/mqtt/client.py", line 1071, in reconnect
>foris-controller: sock = self._create_socket_connection()
>foris-controller: File "/usr/lib/python3.7/site-packages/paho/mqtt/client.py", line 3522, in _create_socket_connection
>foris-controller: return socket.create_connection(addr, source_address=source, timeout=self._keepalive)
>foris-controller: File "/socket.py", line 728, in create_connection
>foris-controller: File "/socket.py", line 716, in create_connection
>foris-controller: ConnectionRefusedError: [Errno 111] Connection refused
finally terminating with
>procd: Instance foris-controller::instance1 s in a crash loop 6 crashes, 1 seconds since last crash
___
potential domino effect (or separate issue)
`ps | lighttpd -D -f /etc/lighttpd/lighttpd.conf`
>Traceback (most recent call last):
> File "/usr/bin/foris", line 11, in <module>
> load_entry_point('Foris==100.6', 'console_scripts', 'foris')()
> File "/__main__.py", line 124, in main
> File "/backend.py", line 62, in __init__
> File "/mqtt.py", line 184, in __init__
> File "/base.py", line 56, in __init__
>Exception in thread foris-client-reply-listener:
>Traceback (most recent call last):
> File "/threading.py", line 926, in _bootstrap_inner
> File "/mqtt.py", line 161, in run
> File "/usr/lib/python3.7/site-packages/paho/mqtt/client.py", line 937, in connect
> return self.reconnect()
> File "/usr/lib/python3.7/site-packages/paho/mqtt/client.py", line 1071, in reconnect
> sock = self._create_socket_connection()
> File "/usr/lib/python3.7/site-packages/paho/mqtt/client.py", line 3522, in _create_socket_connection
> return socket.create_connection(addr, source_address=source, timeout=self._keepalive)
> File "/socket.py", line 728, in create_connection
> File "/socket.py", line 716, in create_connection
>ConnectionRefusedError: [Errno 111] Connection refusedTurris OS 4.0.6https://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/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/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.0