Based on Turris OS 6.2.2 is out! - #6 by jada4p, it seems to be fixed with Turris OS 6.2.2?
Yes, at least for me 
it is really working
(df:)
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda 15138816 6408 14594488 0% /srv
(fdisk -l /dev/sda:)
Disk /dev/sda: 14.44 GiB, 15502147584 bytes, 30277632 sectors
Disk model: DataTraveler 3.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
(ls /srv:)
log spool
No problem.
(lsusb -vt:)
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
ID 1d6b:0003
|__ Port 1: Dev 2, If 0, Class=, Driver=usb-storage, 5000M
ID 0951:1666
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
ID 1d6b:0002
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=orion-ehci/1p, 480M
ID 1d6b:0002
Edit:
One thing more: trying to check whether there are another variants of fdisk (i.e. cfdisk, sfdisk, parted) I issued find command with result bellow
find / -name \\*disk
/sys/class/scsi_disk
/sys/devices/platform/soc/soc:internal-regs@d0000000/d0058000.usb/usb3/3-1/3-1:1.0/host0/target0:0:0/0:0:0:0/scsi_disk
/usr/sbin/fdisk
showing first that there is only fdisk command present (which should be included manually, as shown by AreYouLoco
(Fdisk is missing on newly installed Turris OS?) using opkg update and
opkg install fdisk), and, second, that - if I understand it well - there is USB3 driver used.
Edit2:
Parted could be installed in simillar way.
2 Likes
I just upgraded my Mox to Turris OS 6.2.2, but it still does not see my USB3 mass-storage devices (that work well with Turris OS 5.4.4).
root@turris:~# uname -a
Linux turris 5.15.88 #0 SMP Wed Jan 18 07:04:32 2023 aarch64 GNU/Linux
root@turris:~# cat /etc/os-release
NAME="TurrisOS"
VERSION="6.2.2"
ID="turrisos"
ID_LIKE="lede openwrt"
PRETTY_NAME="TurrisOS 6.2.2"
VERSION_ID="6.2.2"
HOME_URL="https://www.turris.cz/"
BUG_URL="https://gitlab.nic.cz/groups/turris/-/issues/"
SUPPORT_URL="https://www.turris.cz/support/"
BUILD_ID="r16820+125-8b46a263ab"
OPENWRT_BOARD="mvebu/cortexa53"
OPENWRT_ARCH="aarch64_cortex-a53"
OPENWRT_TAINTS="busybox"
OPENWRT_DEVICE_MANUFACTURER="CZ.NIC"
OPENWRT_DEVICE_MANUFACTURER_URL="https://www.turris.cz/"
OPENWRT_DEVICE_PRODUCT="Turris Mox"
OPENWRT_DEVICE_REVISION="v0"
OPENWRT_RELEASE="TurrisOS 6.2.2 8b46a263ab4afaf9857f0d29d369c2eefbf8a4f4"
root@turris:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mmcblk0p1 15558140 9826476 4544516 68% /
devtmpfs 512 0 512 0% /dev
tmpfs 506320 23596 482724 5% /tmp
tmpfs 512 0 512 0% /dev
none 51200 52 51148 0% /srv
root@turris:~# lsusb -vt
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
ID 1d6b:0003
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
ID 1d6b:0002
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=orion-ehci/1p, 480M
ID 1d6b:0002
root@turris:~# opkg list-installed kmod-usb*
kmod-usb-core - 5.15.88-2-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-ehci - 5.15.88-2-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-storage - 5.15.88-2-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-storage-extras - 5.15.88-2-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-storage-uas - 5.15.88-2-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-xhci-hcd - 5.15.88-2-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb2 - 5.15.88-2-64722ee4b91fa2779e55bbf4f1bbe4a6
I’ve tried to install package kmod-usb3 (and restart), but it was not better.
I’ve tried with different USB3 devices with not more luck. When I plug or unplug any USB3 mass-storage device, nothing happens in dmesg. If I plug or unplug an USB2 mass-storage device, it’s properly detected and shows up in dmesg.
I’ve generated a diagnostic report (with dmesg etc), if it can help.
But I have to revert to 5.4.4 again (the USB3 device is the storage of my k3s cluster so it’s a blocker).
1 Like
According to listing of installed modules, you had version 5.15.88 of them, while I have installed version 5.15.89, ie. newer
root@MOXjp:~# opkg list-installed kmod-usb*
kmod-usb-core - 5.15.89-1-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-ehci - 5.15.89-1-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-storage - 5.15.89-1-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-storage-extras - 5.15.89-1-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-storage-uas - 5.15.89-1-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb2 - 5.15.89-1-64722ee4b91fa2779e55bbf4f1bbe4a6
I suppose that you didn’t made update properly 
Edit:
As mentioned in another thread:
“Search the forum, probably you have to do fresh (clean) installation of last version. Suggest to follow documentation”
Another mention regarding manual update using SSH was to issue command opkg update first, only than opkg install *module-name* .
1 Like
Interesting, many thanks for this feedback!
I had simply accepted the upgrade that the Mox suggested to me on January 19th (with, indeed, kernel 5.15.88).
I just did the upgrade again, and it also gave me a kernel 5.15.88.
I ran an “opkg update”, then asked again to check for updates in the UI: no update (except the removal of fix-* packages, version 1-59, that I applied)
Can’t imagine what the problem could be… As suggested elsewhere, possible solution may be to create fresh snapshot (schnapps), export it (to USB or SSD) for later extracting of your configurations, do fresh installation of last medkit, import snapshot created in previous step and extract your configurations and implement them…
Have a good luck!
I also tried to run pkgupdate from the command-line, but it does not help either:
root@turris:~# pkgupdate
INFO:Target Turris OS: 6.2.2
WARN:Requested package reforis-snapshots-plugin-l10n-fr that is missing, ignoring as requested.
WARN:Requested package reforis-openvpn-plugin-l10n-fr that is missing, ignoring as requested.
WARN:Requested package reforis-data-collection-plugin-l10n-fr that is missing, ignoring as requested.
WARN:Requested package reforis-diagnostics-plugin-l10n-fr that is missing, ignoring as requested.
WARN:Requested package reforis-haas-plugin-l10n-fr that is missing, ignoring as requested.
As the upgrade to kernel 5.15.88 has been suggested to me on January 19th, I’ll try to revert to a snapshot before this date: I have one on January 15th. Hopefully it might let it find the kernel 5.15.89?
What branch are you on? hbs? or hbs-sdio?
I’m probably on hbs (did not try to manually switch to another one). How can I check?
edit: found a way to check: I’m indeed on hbs:
root@turris:~# cat /etc/config/updater
config turris 'turris'
option mode 'branch'
option branch 'hbs'
config l10n 'l10n'
list langs 'fr'
config autorun 'autorun'
option enable '1'
option approvals '1'
I switched back to my snapshot of January 15th, asked the UI to look for updates again, and it still finds kernel 5.15.88.
Then you could try switching to hbt. There is no release currently in testing, but it might still be worth trying…
switch-branch hbtIn fact, if I open file https://repo.turris.cz/hbs/mox/packages/core/Packages.gz (which is the URL grabbed if I run opkg update, on hbs branch), it only contains kernel 5.15.88, no 5.15.89.
and the hbs-sdio branch (https://repo.turris.cz/hbs-sdio/mox/packages/core/Packages.gz) contains an older kernel: 4.14.294-1
@peci1 : hbt is also with 5.15.88. I would need to switch to hbk to have 5.15.89. @jada4p on which branch are you?
When I read Turris OS 6.2.2 is out!, I thought it meant it was released on hbs?
Correct.
I think we’re just randomly trying to find stuff that might help you. Trying to switch to hbk might be a good test to see whether your issue is still there.
I tried hbs, hbt (6.2.2 with kernel 5.15.88) and hbk (6.2.3 with kernel 5.15.89).
My USB3 HDD doesn’t work with any of those versions.
6.2.2:
# uname -a
Linux turris 5.15.88 #0 SMP Wed Jan 18 07:04:32 2023 aarch64 GNU/Linux
# cat /etc/os-release
NAME="TurrisOS"
VERSION="6.2.2"
ID="turrisos"
ID_LIKE="lede openwrt"
PRETTY_NAME="TurrisOS 6.2.2"
VERSION_ID="6.2.2"
HOME_URL="https://www.turris.cz/"
BUG_URL="https://gitlab.nic.cz/groups/turris/-/issues/"
SUPPORT_URL="https://www.turris.cz/support/"
BUILD_ID="r16820+125-8b46a263ab"
OPENWRT_BOARD="mvebu/cortexa53"
OPENWRT_ARCH="aarch64_cortex-a53"
OPENWRT_TAINTS="busybox"
OPENWRT_DEVICE_MANUFACTURER="CZ.NIC"
OPENWRT_DEVICE_MANUFACTURER_URL="https://www.turris.cz/"
OPENWRT_DEVICE_PRODUCT="Turris Mox"
OPENWRT_DEVICE_REVISION="v0"
OPENWRT_RELEASE="TurrisOS 6.2.2 8b46a263ab4afaf9857f0d29d369c2eefbf8a4f4"
# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mmcblk0p1 15554048 1719212 12216148 12% /
devtmpfs 512 0 512 0% /dev
tmpfs 249172 20716 228456 8% /tmp
tmpfs 512 0 512 0% /dev
# lsusb -vt
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
ID 1d6b:0003
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
ID 1d6b:0002
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=orion-ehci/1p, 480M
ID 1d6b:0002
# opkg list-installed kmod-usb*
kmod-usb-core - 5.15.88-2-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-ehci - 5.15.88-2-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-storage - 5.15.88-2-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-storage-extras - 5.15.88-2-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-storage-uas - 5.15.88-2-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb2 - 5.15.88-2-64722ee4b91fa2779e55bbf4f1bbe4a6
6.2.3:
# uname -a
Linux turris 5.15.89 #0 SMP Fri Jan 27 00:08:56 2023 aarch64 GNU/Linux
# cat /etc/os-release
NAME="TurrisOS"
VERSION="6.2.3"
ID="turrisos"
ID_LIKE="lede openwrt"
PRETTY_NAME="TurrisOS 6.2.3"
VERSION_ID="6.2.3"
HOME_URL="https://www.turris.cz/"
BUG_URL="https://gitlab.nic.cz/groups/turris/-/issues/"
SUPPORT_URL="https://www.turris.cz/support/"
BUILD_ID="r16821+124-944265347a"
OPENWRT_BOARD="mvebu/cortexa53"
OPENWRT_ARCH="aarch64_cortex-a53"
OPENWRT_TAINTS="busybox"
OPENWRT_DEVICE_MANUFACTURER="CZ.NIC"
OPENWRT_DEVICE_MANUFACTURER_URL="https://www.turris.cz/"
OPENWRT_DEVICE_PRODUCT="Turris Mox"
OPENWRT_DEVICE_REVISION="v0"
OPENWRT_RELEASE="TurrisOS 6.2.3 944265347a81eadc3354731d5f739a6a4fdf6e7b"
# lsusb -vt
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
ID 1d6b:0003
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
ID 1d6b:0002
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=orion-ehci/1p, 480M
ID 1d6b:0002
# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mmcblk0p1 15554048 2224732 11755092 16% /
devtmpfs 512 0 512 0% /dev
tmpfs 249172 20704 228468 8% /tmp
tmpfs 512 0 512 0% /dev
# opkg list-installed kmod-usb*
kmod-usb-core - 5.15.89-1-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-ehci - 5.15.89-1-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-storage - 5.15.89-1-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-storage-extras - 5.15.89-1-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-storage-uas - 5.15.89-1-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb2 - 5.15.89-1-64722ee4b91fa2779e55bbf4f1bbe4a6
I’ve rolled back to 5.4.4 where USB3 drive works just fine.
Just to add, re-connecting USB cable to MOX doesn’t make any effect, nothing in dmesg output.
1 Like
That’s it! On MOX I’m on HBK branch, on Omnia it’s HBS
I think you can safely switch to HBK branch as well, at least to be able to use USB3 for time being, and later switch back to HBS, to be on safe side
Well, not so sure that switching to hbk is enough, based on the feedback from @padam above.
I’ve reverted to 5.4.4 too, because I can’t block all my hosted services for too long.
USB3 still doesn’t work for me on MOX hbs 6.2.2 either. I tried a flash drive and a USB3 SATA adapter.
As a workaround I got myself a USB2 SATA adapter.
It doesn’t work on 6.2.3. I did a factory reset to 6.2.2 and then switched to HBK branch, and my USB3.0 devices are still ignored.