Turris OS 3.10.3 in RC

release

#1

Dear Turris users,

we just released Turris OS 3.10.3 into RC. Most of the stuff is really minor, the main reason for release is updated Unbound that includes workaround for some broken Microsoft DNS servers. So it mainly affects Turris 1.X users but there are few minor fixes for everybody. Full release notes are as follows:

  • nextcloud: update
  • pakon, storage: minor fixes
  • kernel, unbound: update and minor fixes

Let us know if you encounter any issues.

EDIT: Updated RC fixing cosmetic issue in unbound and some other issue in storage plugin


Turris OS 3.10.3 v RC
#2

#3

New version unbound don’t create /var/run/unbound.pid file.


#4

Thanks for reporting. We’ve fixed it. :slight_smile:


#5

I tests the NUT packet with the 5SC 500i ups eaton. It is connected to the turris omnii via the usb connector.
After the connection, create /dev/hidXXXX.
[ 1946.294322] hid-generic 0003:0463:FFFF.0003: hiddev0,hidraw1: USB HID v1.10 Device [EATON Eaton 5SC] on usb-f10f8000.usb3-1.3/input0
This device does not exist for about a one second. Just be gone!
This proves me because the command ups to shutdown the end with a message:

upsdrvctl shutdown
Network UPS Tools - UPS driver controller 3.10-76-gd2caa7d
Network UPS Tools - Generic HID driver 0.41 (3.10-76-gd2caa7d)
USB communication driver 0.33
Can not claim USB device [0463:ffff]: No such file or directory
Driver failed to start (exit status = 1)

Mouse work corectly!? Permanently create /dev/hidraw0.
[ 17.064464] input: Microsoft Comfort Mouse 3000 as /devices/platform/soc/soc:internal-regs/f10f8000.usb3/usb4/4-1/4-1.2/4-1.2:1.0/0003:045E:077B.0001/input/input0

The nut-server package can not create two LISTEN ip1 and LISTEN ip2 commands.

When creating ups.conf, I can not to create commands without the second parameter so “param1 = xxx”!
Such orders are for example:
/lib/nut /usbhid-ups -h

Do not use polling, just use interrupt pipe: -x interruptonly NOK
Number of bytes to read from interrupt pipe : -x interruptsize=value OK


#6

Info from:

udevadm monitor

KERNEL[6308.310358] add      /devices/platform/soc/soc:internal-regs/f10f8000.usb3/usb4/4-1/4-1.2 (usb)
KERNEL[6308.311296] add      /devices/platform/soc/soc:internal-regs/f10f8000.usb3/usb4/4-1/4-1.2/4-1.2:1.0 (usb)
KERNEL[6311.039259] add      /devices/platform/soc/soc:internal-regs/f10f8000.usb3/usb4/4-1/4-1.2/4-1.2:1.0/0003:0463:FFFF.0007 (hid)
KERNEL[6311.042698] add      /class/usbmisc (class)
KERNEL[6311.042741] add      /devices/platform/soc/soc:internal-regs/f10f8000.usb3/usb4/4-1/4-1.2/4-1.2:1.0/usbmisc/hiddev0 (usbmisc)
KERNEL[6311.042777] add      /devices/platform/soc/soc:internal-regs/f10f8000.usb3/usb4/4-1/4-1.2/4-1.2:1.0/0003:0463:FFFF.0007/hidraw/hidraw0 (hidraw)
KERNEL[6311.315724] remove   /devices/platform/soc/soc:internal-regs/f10f8000.usb3/usb4/4-1/4-1.2/4-1.2:1.0/usbmisc/hiddev0 (usbmisc)
KERNEL[6311.315777] remove   /usbmisc (class)
KERNEL[6311.315811] remove   /devices/platform/soc/soc:internal-regs/f10f8000.usb3/usb4/4-1/4-1.2/4-1.2:1.0/0003:0463:FFFF.0007/hidraw/hidraw0 (hidraw)
KERNEL[6311.315853] remove   /devices/platform/soc/soc:internal-regs/f10f8000.usb3/usb4/4-1/4-1.2/4-1.2:1.0/0003:0463:FFFF.0007 (hid)

#7

Do you need it for anything? Added it back as we were fixing some other issue.


#8

Yes. Mam NAS perk with 2 HDDs with btrfs raid1. If an electric energy falls out of the way, it will badly carry the field raid. And you can fall …
With Pepe I talked about NAS issues. One of his time is also NUT.
It would help me to continue. I hope to write the NUT setting. This is a prerequisite for continuing testing. UPS that does not shut down is two things …
Thx.


#9

It was question to @ajb007 regarding unbound pid, sorry for the confusion.


#10

#12