user-docs issueshttps://gitlab.nic.cz/turris/user-docs/-/issues2021-06-28T09:25:46+02:00https://gitlab.nic.cz/turris/user-docs/-/issues/156Document ethernet cage leds behaviour for all our boards2021-06-28T09:25:46+02:00Karel KociDocument ethernet cage leds behaviour for all our boardsThis should add a table with status indication LEDs explanation.
* On 1.x we have non-standard behavior so we should describe it for sure
* Omnia has no ethernet cage LEDs and it should be noted that front leds are used instead (blinkin...This should add a table with status indication LEDs explanation.
* On 1.x we have non-standard behavior so we should describe it for sure
* Omnia has no ethernet cage LEDs and it should be noted that front leds are used instead (blinking on activity and light on link up, there is no standard way to indicate speed)
* Mox behavior is being discussed in turris/os/build#272https://gitlab.nic.cz/turris/user-docs/-/issues/161Link(s) to versions in changelog recognized as incorrect2022-03-17T17:34:16+01:00Lukas JelinekLink(s) to versions in changelog recognized as incorrectThe remote link checker recognizes links to Turris OS versions in the changelog as incorrect. This is because these links are build in JavaScript and the file itself contains only a template for these links.
We should modify the checker...The remote link checker recognizes links to Turris OS versions in the changelog as incorrect. This is because these links are build in JavaScript and the file itself contains only a template for these links.
We should modify the checker and/or the changelog to drop this false positive warning.https://gitlab.nic.cz/turris/user-docs/-/issues/162There is no mention in our documentation, that we use Knot2021-10-26T17:31:11+02:00Stepan RechnerThere is no mention in our documentation, that we use KnotWe use Knot resolver in Turris OS instead of the OpenWrt default dnsmasq. This way, a set-up made in LuCI may not be actually applied and conflicts may occur.
What should be documented:
* this fact,
* which configuration files and optio...We use Knot resolver in Turris OS instead of the OpenWrt default dnsmasq. This way, a set-up made in LuCI may not be actually applied and conflicts may occur.
What should be documented:
* this fact,
* which configuration files and options were added in addition to the OpenWrt ones,
* how to set Knot resolver up.
~~For some users may be helpful:~~
* ~~How to switch back to the OpenWrt default configuration.~~Lukas JelinekLukas Jelinekhttps://gitlab.nic.cz/turris/user-docs/-/issues/165Rainbow and LEDs signaling2022-11-07T14:17:08+01:00Karel KociRainbow and LEDs signaling* [ ] documentation for `rainbow` command line tool and its configuration (in the future hopefully about reForis plugin as well)
* [ ] documentation about LEDs signaling for every board
Note that boards use LEDS to signal boot process a...* [ ] documentation for `rainbow` command line tool and its configuration (in the future hopefully about reForis plugin as well)
* [ ] documentation about LEDs signaling for every board
Note that boards use LEDS to signal boot process as well as hardware failures. With turris/os/packages!846 we also plan to signal running update and notifications.https://gitlab.nic.cz/turris/user-docs/-/issues/168Article omnia/ssd-boot: Configuring Schnapps section still necessary?2022-01-17T11:59:35+01:00Jan BetikArticle omnia/ssd-boot: Configuring Schnapps section still necessary?> Schnapps expects that your root device is on eMMC.
Is it hardcoded somewhere?
The author of the original post on forum supplemented the post with following statement
> According to the original instructions, it is still necessary t...> Schnapps expects that your root device is on eMMC.
Is it hardcoded somewhere?
The author of the original post on forum supplemented the post with following statement
> According to the original instructions, it is still necessary to configure schnapps for the new root partition. But this should not be true for the current version. Therefore I’ve removed this step.:
Log into the router via ssh or serial console.
Back up the current system with:
schnapps create "Initial version on SSD"
Read the “Problems ahead” section in the original Document 6.
> Note: In my original posting - and original setup - I wrote the line ROOT_DEV="/dev/sda1" to the file /etc/schnapps/config. Now this is not only superfluous, but also bad. With this option the command schnaps -d /mnt create always creates a backup of the Root partition and ignores the option -d.
I tried it on Omnia with SSD installed and `schnapps` works out of the box without any other configuration changes.Lukas JelinekLukas Jelinekhttps://gitlab.nic.cz/turris/user-docs/-/issues/171Update VLAN documentation for OpenWrt 21.022022-02-21T16:59:40+01:00Karel KociUpdate VLAN documentation for OpenWrt 21.02In reference of changes handled in turris/os/build#273 we should update VLAN configuration.In reference of changes handled in turris/os/build#273 we should update VLAN configuration.https://gitlab.nic.cz/turris/user-docs/-/issues/178Feature request: provide steps to boot from SSD without working system2022-05-10T13:23:10+02:00Josef SchlehoferFeature request: provide steps to boot from SSD without working systemHey there,
I noticed that I am not able to use steps given in **Preparation of SSD**, they assume that I have working system (with functional eMMC). That's wrong in my case. Most people will be looking into it when they worn-out their i...Hey there,
I noticed that I am not able to use steps given in **Preparation of SSD**, they assume that I have working system (with functional eMMC). That's wrong in my case. Most people will be looking into it when they worn-out their internal storage.
My u-boot version: ``U-Boot 2019.07 (Oct 05 2020 - 23:50:39 +0000), Build: jenkins-turris-os-packages-dragons-omnia-1753``.
When I selected 7 (``run rescueboot`` does not work], I am able to use steps given in our old documentation, these days, community one: https://wiki.turris.cz/doc/en/howto/omnia_booting_from_external_storagehttps://gitlab.nic.cz/turris/user-docs/-/issues/182MOX A USB port does not support hub - should be mentioned2022-10-24T12:28:19+02:00Stepan RechnerMOX A USB port does not support hub - should be mentionedAt the [Turris MOX A site](https://docs.turris.cz/hw/mox/modules/a/) in the documentation, it is mentioned among other specifications:
> - USB 3.0 port
But it is not mentioned, that a USB hub inserted in it would not work. Nevertheless...At the [Turris MOX A site](https://docs.turris.cz/hw/mox/modules/a/) in the documentation, it is mentioned among other specifications:
> - USB 3.0 port
But it is not mentioned, that a USB hub inserted in it would not work. Nevertheless, users may expect that. It should be probably mentioned there.
A side note: another description of Turris MOX A is at the website <https://www.turris.cz/cs/mox/moduly/>.
cc: @prohar @dmelinhttps://gitlab.nic.cz/turris/user-docs/-/issues/183Info about the need of a restart when SFP is plugged in is missing2022-10-24T12:28:17+02:00Stepan RechnerInfo about the need of a restart when SFP is plugged in is missingIn a Turris Omnia router, since Turris OS 4, the SFP port is not plug-and-play. It should be mentioned [in the documentation](https://docs.turris.cz/hw/omnia/omnia/#network-interfaces) that a restart of the router is required.In a Turris Omnia router, since Turris OS 4, the SFP port is not plug-and-play. It should be mentioned [in the documentation](https://docs.turris.cz/hw/omnia/omnia/#network-interfaces) that a restart of the router is required.https://gitlab.nic.cz/turris/user-docs/-/issues/186Support: mention Minimal Snapshot Manager and Diagnostics page2023-01-11T13:41:16+01:00Josef SchlehoferSupport: mention Minimal Snapshot Manager and Diagnostics pagehttps://gitlab.nic.cz/turris/user-docs/-/issues/190Mention backup keyword on Schnapps docs2024-03-27T16:34:25+01:00Vinzenz SinapiusMention backup keyword on Schnapps docsSo I was looking for a way to backup our Turris Omnia, searched for "Backup" on the docs page and didn't find anything. It took me a while until I finally found the Schnapps utility. Maybe mention it somewhere on the page?So I was looking for a way to backup our Turris Omnia, searched for "Backup" on the docs page and didn't find anything. It took me a while until I finally found the Schnapps utility. Maybe mention it somewhere on the page?Lukas JelinekLukas Jelinekhttps://gitlab.nic.cz/turris/user-docs/-/issues/191Explicitly discourage users from sharing diagnostics output publicly2023-01-17T18:10:12+01:00Simon BorekExplicitly discourage users from sharing diagnostics output publiclyIn [Formulating your problem section of Getting Help documentation page](https://docs.turris.cz/basics/support/#formulating-your-problem) there is stated: "If you have logs, include them. But be aware that those __might contain sensitiv...In [Formulating your problem section of Getting Help documentation page](https://docs.turris.cz/basics/support/#formulating-your-problem) there is stated: "If you have logs, include them. But be aware that those __might contain sensitive data__."
As logs are listed as one of the diagnostics modules, it is technically clear the warning applies to them as well, but in practice users shouldn't be required to come to that conclusion themselves.
It might be highly beneficial to add a similar warning addressing diagnostics directly while being placed in an actual warning frame instead of being included as a part of text.
Related: https://gitlab.nic.cz/turris/reforis/reforis-diagnostics/-/issues/9https://gitlab.nic.cz/turris/user-docs/-/issues/193Updated MOX product brochure2023-03-02T09:03:33+01:00Filip HronUpdated MOX product brochurefollows #192
Upload updated MOX Brochure to reflect new Wi-Fi 6 card and deprecated SDIO.follows #192
Upload updated MOX Brochure to reflect new Wi-Fi 6 card and deprecated SDIO.Filip HronFilip Hronhttps://gitlab.nic.cz/turris/user-docs/-/issues/195Turris Mox USB (from module A) not working any more (for mass storage) after ...2023-05-18T13:38:03+02:00Lukas JelinekTurris Mox USB (from module A) not working any more (for mass storage) after TOS 6.0 upgrade - add to FAQAdd an item to the FAQ according this: https://forum.turris.cz/t/turris-mox-usb-from-module-a-not-working-any-more-for-mass-storage-after-tos-6-0-upgrade/17918/95Add an item to the FAQ according this: https://forum.turris.cz/t/turris-mox-usb-from-module-a-not-working-any-more-for-mass-storage-after-tos-6-0-upgrade/17918/95https://gitlab.nic.cz/turris/user-docs/-/issues/200SFP module unstable after TOS4 - VDSL Modem2024-01-09T13:20:39+01:00johnappletreeSFP module unstable after TOS4 - VDSL Modem[Copy paste from the forum:](https://forum.turris.cz/t/user-experience-allnet-all4781-vdsl2-sfp-switch-modul-mini-gbic-vdsl2/7062/105?u=johnappletree)
Whist the module performs on my IPS’s subscriber line generally stable after the swit...[Copy paste from the forum:](https://forum.turris.cz/t/user-experience-allnet-all4781-vdsl2-sfp-switch-modul-mini-gbic-vdsl2/7062/105?u=johnappletree)
Whist the module performs on my IPS’s subscriber line generally stable after the switch from TOS3.x to TOS4.x I noticed intermittent hiccups manifested in the logs
` sfp: module transmit fault indicated`
` sfp: module transmit fault recovered`
and sometimes also
` sfp: module persistently indicates fault, disabling`
Those messages are generated by SFP.C [1] (not available in TOS3.x with kernel 4.9.x) and are pertinent to the check routines implemented for state machine:
- checks signal status (asserted / dessarted) for RX_LOS and TX_FAULT
with
` sfp: module transmit fault indicated`
relating to the signal status of TX_FAULT (`tx-fault in hi IRQ`)
SFP.C tries to clear (recover) the fault fives times in total, pausing one second between each attempt and if successful (`tx-fault in lo IRQ`) prints
` sfp: module transmit fault recovered`
If the five attempts are however exhausted it prints
` sfp: module persistently indicates fault, disabling`
and as a result there is no WAN connectivity. Signal status detection is only attempted again if the interface is being restarted, else the link will remain a down state.
It is not clear why the module most of the times passes the check but other times intermittently fails. Potential reasons could be:
- Module hardware defect that was not exposed in TOS3.x (lacking the presence of SFP.C and related checks)
- Something chocking the I2C bus communication with the module and preventing a timely response (within 300 ms) on the TX_FAULT signal status from the module
- Some bug in the SFP.C code, though its developer is adamant that it is not the case but trusts that the module misbehaves instead
[1] https://github.com/torvalds/linux/blob/master/drivers/net/phy/sfp.chttps://gitlab.nic.cz/turris/user-docs/-/issues/203/hw/omnia/revisions.md Add info about newer revisions2024-03-04T13:13:27+01:00Marek Novotny/hw/omnia/revisions.md Add info about newer revisionsThe documentation page about Turris Omnia board revisions is incomplete.The documentation page about Turris Omnia board revisions is incomplete.Marek NovotnyMarek Novotnyhttps://gitlab.nic.cz/turris/user-docs/-/issues/204Add CZ11NIC33 to revisions2024-03-04T13:13:26+01:00Lukas JelinekAdd CZ11NIC33 to revisionsAdd information about CZ11NIC33 to revisions in the documentation.Add information about CZ11NIC33 to revisions in the documentation.https://gitlab.nic.cz/turris/user-docs/-/issues/206hw/omnia/ssd-boot: Add guide for new revisions with press-on stand-offs2024-03-12T10:19:10+01:00Marek Novotnyhw/omnia/ssd-boot: Add guide for new revisions with press-on stand-offsA lot of users are confused by having press-on stand-offs in their Omnias. Would be great to mention it in the guide.A lot of users are confused by having press-on stand-offs in their Omnias. Would be great to mention it in the guide.Marek NovotnyMarek Novotnyhttps://gitlab.nic.cz/turris/user-docs/-/issues/207Add information that SD cards shouldn't be moved between devices2024-03-27T10:49:41+01:00Lukas JelinekAdd information that SD cards shouldn't be moved between devicesSome users reported various problems occurred when an SD card was moved from one device to another one (of the same type). This operation should be mentioned as strongly discouraged because it may break some relations between devices and...Some users reported various problems occurred when an SD card was moved from one device to another one (of the same type). This operation should be mentioned as strongly discouraged because it may break some relations between devices and files. An SD card may be used in another device but it should be formatted and a new medkit should be installed.Lukas JelinekLukas Jelinekhttps://gitlab.nic.cz/turris/user-docs/-/issues/208Rework LTE setup2024-03-26T10:34:16+01:00Filip HronRework LTE setup- Get specific on particular `LTE` hardware
- "we use this and this card"
- drop current OpenWRT setup help
- specific lUCI setup no longer needed
- describe limitation of each HW (geek)
- example: `mmcli` is not able to sim-lock o...- Get specific on particular `LTE` hardware
- "we use this and this card"
- drop current OpenWRT setup help
- specific lUCI setup no longer needed
- describe limitation of each HW (geek)
- example: `mmcli` is not able to sim-lock on `EC20` hardware