Posts by arcasys

The TVHadmin-JS addon for Tvheadend cannot be installed in LibreElec the way it's described in the project wiki, see github project.

I've opened an issue for the project, where you can find some research on the root cause of the problem: in LibreElec the tvheadend web server along with the root path

/usr/share/tvheadend/src/webui/static

is built into the tvheadend binary and not accessible to the user.

That's where my capabilities end and I'm asking to support dave-p when he's willing to create a TVHadmin-JS addon for LibreElec. This would be really cool.

A recording (1) started or scheduled from the tvheadend client works and is listed in TV/Recordings.
A recording (2) started or scheduled from the tvheadend web interface also works but is not listed in recordings, although the files from both recording (1) and (2) are present in the folder /storage/recordings.

Why is this and what can I do about it?

Background: I simply want to be able to schedule recordings from a web intrface...

I've filed a bug on this topic but was told to address the forum and the bug ((Issue #8566) was closed immediately.

I really need help to solve this problem

After a certain period of time. e.g. over night. both mouse and keyboard stop working.
Mouse Logitech M310 and keyboard K330 are paired with a Logitech Unifying receiver.
Detaching and reattaching the receiver does not help.
After a reboot everything is back to normal.

How to reproduce

Steps to reproduce the behavior:

1. dmesg (after reboot)
`# dmesg | grep logitech
[ 4.445891] logitech-djreceiver 0003:046D:C52B.0003: hiddev96,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-3f980000.usb-1.2/input2

[ 4.578527] logitech-hidpp-device 0003:046D:4055.0004: input,hidraw1: USB HID v1.11 Mouse [Logitech Wireless Device PID:4055] on usb-3f980000.usb-1.2/input2:1

[ 4.587362] logitech-hidpp-device 0003:046D:1024.0005: input,hidraw2: USB HID v1.11 Mouse [Logitech M310] on usb-3f980000.usb-1.2/input2:2

[ 4.596918] logitech-hidpp-device 0003:046D:4016.0006: input,hidraw3: USB HID v1.11 Keyboard [Logitech K330] on usb-3f980000.usb-1.2/input2:3

[ 126.925966] logitech-hidpp-device 0003:046D:4016.0006: HID++ 2.0 device connected.

[ 7456.477316] logitech-djreceiver 0003:046D:C52B.0009: hiddev96,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-3f980000.usb-1.2/input2

[ 7456.612825] logitech-hidpp-device 0003:046D:4055.000A: input,hidraw1: USB HID v1.11 Mouse [Logitech Wireless Device PID:4055] on usb-3f980000.usb-1.2/input2:1

[ 7456.627803] logitech-hidpp-device 0003:046D:1024.000B: input,hidraw2: USB HID v1.11 Mouse [Logitech M310] on usb-3f980000.usb-1.2/input2:2

[ 7456.639775] logitech-hidpp-device 0003:046D:4016.000C: input,hidraw3: USB HID v1.11 Keyboard [Logitech K330] on usb-3f980000.usb-1.2/input2:3
[ 7472.470051] logitech-hidpp-device 0003:046D:4016.000C: HID++ 2.0 device connected.
'

2. Wait overnight
Mouse and keyboard have stopped working.
dmesg will produce the same result.

3. Check with udevadm monitor
No evenr will be reported when the receiver is detached and reattached.

3. Reboot
Mouse and keyboard are working without any problem until they again stop working after some time.

System Information

• LibreELEC Version: 11.0.5
• Hardware Platform: RPi3+

The solution is as simple as that:

Instead of stopping the vdr-addon or even kodi and copying the presorted channels.conf.mine to channels.conf simply do

# cd /storage/.kodi/userdata/addon_data/service.multimedia.vdr-addon/config
# cat channels.conf.mine > channels.conf

Then reboot.

Why does this work?
I think owerwriting the channels.conf using '>' does neither change the original file date date nor the file dscriptor while a copy command does.

Actually it's sometimes not that simple:

While the channels within the groups are ordered like in the channels.conf, the groups are always ordered alphabetically. I solved this for me with preceding the group names with 1_, 2_, etc.

Take care of the correct configuration:

In Setting / PVR & Live TV -> Channels set

• Synchronize channel groups ..
• Use channel order from backed

In ~/.kodi/userdata/addon_data/service.multimedia.vdr-addon/config/setup.conf setting UpdateChannels = 2 is a good choice.

If you want to start with a clean database ~/.kodi/username/Database/TV40.db, you can delete this file- In that case you better stop kodi and service.multimedia.vdr-addon before deleting. If you don' do this existing channel groups remain in the database but you can safely delete these groups in the channel manager.

I'm glad all this is not an everyday's task...

In LE11.05, the Disk menu appears and the title of the inserted disk iis shown, That's perfect so far.

There is now some different behavior:

• When viewing a disk had been interrupted, choosing Disk->Play immediately jumps tothe point of interruption without asking if the disk should be played from the beginnning. Has this choice been removed intentionally?
• The parts before the disk menu are not skipped although this has been configured in the Player setup (bug?)

Nice ideas. Most of it I've already tried, see my previous post.

Neither replacing the channels.conf nor removing TV*.db while kodi is stopped works. TV40.db is rebuilt. channelgroups are created from the bouqet names in the channel.conf. The channel,conf is then overridden.

I can't find anything that would leave my channel.conf intact.

Still frustrating. I'll try to find and contact the VNSI client developer.

I've already tried this to no avail:

kodi:~/.kodi/userdata/addon_data/service.multimedia.vdr-addon/config # ls -l
total 67
-rw-r--r--    1 root     root         20016 Jan 24 18:37 channels.conf
-rw-r--r--    1 root     root         26841 Jan 22 15:53 channels.conf.sort
kodi:~/.kodi/userdata/addon_data/service.multimedia.vdr-addon/config # systemctl stop service.multimedia.vdr-addon
kodi:~/.kodi/userdata/addon_data/service.multimedia.vdr-addon/config # cp channels.conf.sort channels.conf
kodi:~/.kodi/userdata/addon_data/service.multimedia.vdr-addon/config # ls -l
-rw-r--r--    1 root     root         26841 Jan 24 18:36 channels.conf
-rw-r--r--    1 root     root         26841 Jan 22 15:53 channels.conf.sort
kodi:~/.kodi/userdata/addon_data/service.multimedia.vdr-addon/config # systemctl start service.multimedia.vdr-addon
kodi:~/.kodi/userdata/addon_data/service.multimedia.vdr-addon/config # ls -l
-rw-r--r--    1 root     root         26841 Jan 24 18:36 channels.conf
-rw-r--r--    1 root     root         26841 Jan 22 15:53 channels.conf.sort
kodi:~/.kodi/userdata/addon_data/service.multimedia.vdr-addon/config # ls -l
-rw-r--r--    1 root     root         20016 Jan 24 18:37 channels.conf
-rw-r--r--    1 root     root         26841 Jan 22 15:53 channels.conf.sort

This is really frustrating. I think it has to do with the channel manager and group manager.???

7 years later this problem appears again with LE11. Maintainng an own presorted and nicely grouped channels.conf for VDR seems to be impossible. Wherever I place the channels,conf, it won't work. The channels.conf in

~/.kodi/userdata/addon_data/service.multimedia.vdr-addon/config

gets updated by kodi automatically while the channels.conf in

~/.kodi/addons/service.multimedia.vdr-addon/

is ignored.

Unfortunately the channel manager and the group manager in Settings/PVR and TV are not really useful when you have a list of +350 channels. As I said I already have a working channels.conf but cannot use it!

Any help to solve this is very much appreciated!

Quote from petediscrete

Check your logs for a definitive answer. It’s all there to be seen.

Yes, I know. But I wanted to avoid this kind of hacking like using 'udevadm monitor' to see whats going on and trial and error with udev rules ...

I hoped for someone knowing the details of the LibreElec implementation to answer.

My question was: what do I have to change to make the Disc menu appear when my drive is connected to a USB hub.

UPDATE

Navigating to Videos->Files lists the title. Choosing the title lists AUDIO_TS and VIDEO_TS. Choosing VIDEO_TS plays the Video. After the trailer the DVD menu is showing and works perfectly. From there everything works like I was coming from the Disc menu.

So there's some inconvenience to get to the DVD title but it works and it proves that DVDs can also be played by a DVD drive connected to a hub.

I'm having the same problem as the OP.

When I directly connect to the RPi's USB port the Disc menu show up only for a short period of time and the drive won't settle when I insert a DVD. I think it's a power problem. Changing the 2A PSU for a 3A PSU didn't solve the problem.

When I connect the drive through a powered hub, LE mounts an inserted DVD without any problem but mount shows that /dev/sr0 is mounted as /var/media/<20 chars of the title> and no Disc option appears in the menu. I've read somewhere that DVD drives shouldn't be attached through a hub, so I'm not surprised.

I'm quite sure this can be solved by creating/changing a udev rule specific to my drive. Maybe someone knows more about this and spares me the hacking ...

Quote from chewitt

And the errors are

First thing: if no disk is inserted in the target drive the nbd-client command fails (short read) and mount caanot find a valid file system on /dev/nbd

If a disk is inserted 'nbd-cleint -p -N share-name target-host /nbd0' command returns with no error

dmesg:

[12607.336769] nbd0: detected capacity change from 0 to 15922560
[12607.755782] block nbd0: Other side returned error (5)
[12607.755823] blk_print_req_error: 2 callbacks suppressed
[12607.755849] I/O error, dev nbd0, sector 15922432 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[12607.871430] block nbd0: Other side returned error (5)
[12607.871471] I/O error, dev nbd0, sector 15922432 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[12607.871526] buffer_io_error: 22 callbacks suppressed
[12607.871538] Buffer I/O error on dev nbd0, logical block 1990304, async page read
[12607.991723] block nbd0: Other side returned error (5)
[12607.991783] I/O error, dev nbd0, sector 15922432 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[12607.991807] Buffer I/O error on dev nbd0, logical block 1990304, async page read

mount returns:

mount: mounting /dev/nbd0 on media failed: Invalid argument

dmesg:

[14005.279332] /dev/nbd0: Can't open blockdev
[14005.281426] /dev/nbd0: Can't open blockdev
[14005.289287] /dev/nbd0: Can't open blockdev
[14005.294137] /dev/nbd0: Can't open blockdev
[14005.309858] ISOFS: unsupported/invalid hardware sector size 4096
[14007.968217] block nbd0: Other side returned error (5)
[14007.968277] I/O error, dev nbd0, sector 15921352 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[14007.968330] UDF-fs: error (device nbd0): udf_read_tagged: read failed, block=1990169, location=1990169
[14008.324575] block nbd0: Other side returned error (5)
[14008.324636] I/O error, dev nbd0, sector 15921336 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[14008.324686] UDF-fs: error (device nbd0): udf_read_tagged: read failed, block=1990167, location=1990167
[14008.745285] block nbd0: Other side returned error (5)
[14008.745352] I/O error, dev nbd0, sector 4096 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[14008.745400] UDF-fs: error (device nbd0): udf_read_tagged: read failed, block=512, location=512
[14009.192698] block nbd0: Other side returned error (5)
[14009.192779] I/O error, dev nbd0, sector 15920112 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[14009.192832] UDF-fs: error (device nbd0): udf_read_tagged: read failed, block=1632832, location=1632832
[14009.538532] block nbd0: Other side returned error (5)
[14009.538622] I/O error, dev nbd0, sector 15920120 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[14009.538682] UDF-fs: error (device nbd0): udf_read_tagged: read failed, block=1632833, location=1632833
[14010.382490] block nbd0: Other side returned error (5)
[14010.382531] I/O error, dev nbd0, sector 4992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[14010.382599] UDF-fs: error (device nbd0): udf_read_tagged: read failed, block=512, location=512
[14010.461530] block nbd0: Other side returned error (5)
[14010.461577] I/O error, dev nbd0, sector 4992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[14010.461647] UDF-fs: error (device nbd0): udf_read_tagged: read failed, block=512, location=512
[14010.461666] UDF-fs: warning (device nbd0): udf_fill_super: No partition found (1)
[14010.463071] F2FS-fs (nbd0): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[14010.463095] F2FS-fs (nbd0): Can't find valid F2FS filesystem in 1th superblock
[14010.467440] F2FS-fs (nbd0): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[14010.467461] F2FS-fs (nbd0): Can't find valid F2FS filesystem in 2th superblock
[14010.468197] /dev/nbd0: Can't open blockdev

The errors show clearly that nbd-client cannot even handle a share for a dvd. let alone changing disks.

End of story ...

I checked open-scsi and followed the instructions given by chewitt in the thread open-iscsi support for raspberry Pi 3. Creating an image with Iscsi-client worked but I don't have a scsi drive. Maybe it would work, maybe not.

Then I checked nbd-client, which is built into LibreElec:

• export the dvd drive on my Ubuntu server unsing nbd-server
• the nbd-client command on LibreElec to connect the drive returns with no error
• mounting /dev/nbd0 fails with various error messages (dmesg)

Now I made another test and installed ndb-client on my Xubuntu laptop

• connecting the remote drive works
• mounting /dev/nbd0 works (type seems to be udf, which looks ok)
• the disk can be played flawlessly with VLC as if it was in a local drive

Looks good so far, but changing the disk is not recognized and has weird effects on the mount.

Conclusion: Even if nbd-client and mounting the remote drive would work on LibreElec, this will never work like a local drive. In my opinion, it's not worth following up beacuse there are even more problems to be expected...

Maybe someone has more and better ideas.

I mistook SCSI for SATA! No need for iscsi-client. Sorry for this.
I'll close this thread and open a new one for nbd.

The good thing: compiling libreelec succeeded and iscsi-client was there. Thanks for the instructions.

While building the new image is in progress I wonder if the open-iscsi package could be built for itself and then included somehow or, even better, built as a plugin? This would possibly be faster and leverage system updates without rebuilding the entire image. Just an idea...

I guess the makefile in the open-scsi package is used by the image build and cannot be be used standalone. Right?

Thanks for the fast reply. I'll try this and report back eventually.

I'd like to try open-scsi to access a DVD drive in a media server near by. Unfortunately the open-scsi package in packages/sysutils/ in the source tree seems not to be included in the image LibreELEC-RPi2.arm-11.0.4.img.gz.

Can this package be compiled separately and then installed on the Pi, and if so, how could this be schieved? Any hints are welcome.

Background:

There is not much to be found on the web about this topic. I found some thread by users with the same problem but advice was not very helpful, like

• open-iscsi is located only in the initramfs - I don't believe this because it doesn't make sense and there is nothing to be seen in sysetemctl
• rip your DVDs and store them as mp4 - no comment
• get a usb player or buy a dvd or blue ray player from walmart for 50 bucks - thank you. this is not an anwer to the question. I don't have the space for yet another device

I had kodi installed on my media server (running ubuntu server) for some time, but out of reasons unknown, after a system upgrade, hdmi stopped working as it should . I liked the kodi DVD support which worked very nice. Running kodi on a Pi is a very good solution for me but I'm missing the DVD.