klorinczi

I got plug-in errors after updating from OpenPLI 8.3 to 9.0.

Using VU+ DUO 4K SE PVR.

I got the following errors:
Some plugins are not available:
System Plugins/QuadPiP ('asci' codec can't decode byte 0xc3 in position 1: ordinal not in range(128)) SystemPlugins/Firmware Upgrade (No module named 'thread')


Could be possible to fix it?

Hangs device VU+ DUO 4K SE PVR with OpenPLI v8.3.


I was able to find a possible crash fingerprint in /var/log/messages:

May 15 16:37:08 vuduo4kse user.alert kernel: [767177.356191] Unable to handle kernel paging request at virtual address dac10c40
May 15 16:37:08 vuduo4kse user.alert kernel: [767177.363522] pgd = d585b340
May 15 16:37:09 vuduo4kse user.alert kernel: [767177.366331] [dac10c40] *pgd=80000000007003, *pmd=14fad003, *pte=00000000
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.373376] Internal error: Oops: 207 [#1] SMP ARM
May 15 16:37:09 vuduo4kse user.warn kernel: [767177.378260] Modules linked in: bthid(O) btusb(O) bluetooth ipv6 brcmfb(O) dvb_bcm7444(PO) dvb_base(PO) bcm_event(PO) procmk(O) dhd(O) fuse [last unloaded: bthid]
May 15 16:37:09 vuduo4kse user.warn kernel: [767177.392960] CPU: 0 PID: 1279 Comm: nx_sched_high_s Tainted: P O 4.1.45-1.17 #1
May 15 16:37:09 vuduo4kse user.warn kernel: [767177.401406] Hardware name: Broadcom STB (Flattened Device Tree)
May 15 16:37:09 vuduo4kse user.warn kernel: [767177.407418] task: d668ba80 ti: d4f1e000 task.ti: d4f1e000
May 15 16:37:09 vuduo4kse user.warn kernel: [767177.412973] PC is at bcm7335_recpump_dataready+0x24/0x1a0 [dvb_bcm7444]
May 15 16:37:09 vuduo4kse user.warn kernel: [767177.420207] LR is at NEXUS_P_Scheduler_Step+0x1e8/0x6d0 [dvb_base]
May 15 16:37:09 vuduo4kse user.warn kernel: [767177.426483] pc : [<bf705e8c>] lr : [<bf074774>] psr: a00e0013
May 15 16:37:09 vuduo4kse user.warn kernel: [767177.426483] sp : d4f1fcf8 ip : d9f11888 fp : bf705e68
May 15 16:37:09 vuduo4kse user.warn kernel: [767177.438146] r10: 00000001 r9 : d9f11888 r8 : d4f1fd98
May 15 16:37:09 vuduo4kse user.warn kernel: [767177.443464] r7 : bf491824 r6 : d3fd8840 r5 : db789768 r4 : d4f945c0
May 15 16:37:09 vuduo4kse user.warn kernel: [767177.450084] r3 : 1b48c000 r2 : bf784c40 r1 : 00000000 r0 : d9f11888
May 15 16:37:09 vuduo4kse user.warn kernel: [767177.456707] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
May 15 16:37:09 vuduo4kse user.warn kernel: [767177.463936] Control: 30c5387d Table: 1585b340 DAC: fffffffd
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.469777] Process nx_sched_high_s (pid: 1279, stack limit = 0xd4f1e210)
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.476658] Stack: (0xd4f1fcf8 to 0xd4f20000)
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.481107] fce0: d9f11888 00000000
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.489382] fd00: 00000000 00000000 d4f945c0 00000005 d3fd8840 bf491824 d4f1fd98 bf491824
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.497657] fd20: 00000001 bf074774 d4f1fd60 09a931a5 00000064 bf0687fc 00000000 d9f11888
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.505930] fd40: 2db433fd 2db43433 2db43416 d0192280 d4f94580 00000000 00000400 00000000
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.514203] fd60: 00000001 00000000 a786c60b bf478a10 00000000 d4f1fde0 0000001e d6589940
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.522476] fd80: d5800dc0 b6698e0c b6698f7c bf068b78 bf478a10 00000064 d4f1fde0 0000001e
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.530750] fda0: b6698e0c d5800dc0 00000000 bf067358 a786c60b 09a931a5 a78fe985 09a931a5
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.539022] fdc0: 09a4ae22 09a4ae22 09a931a5 00042274 d4f1fe44 d4f1fe80 00000064 00000007
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.547295] fde0: 00000000 00000000 ffffe000 c00802f4 d6594000 c0080ddc a786c60b 00000000
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.555568] fe00: a78fe985 00000002 00000000 00000000 00000002 00042274 d4f1e000 00042274
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.563840] fe20: d4f1fe44 c0080f20 d4f1fe44 00000000 00000400 00000000 d4fba200 00010000
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.572113] fe40: d4fba200 d6594000 00020000 d4fb5040 d5c72c00 bf1cb318 d4fbb280 bf1cb3c0
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.580386] fe60: d5c72c00 00180008 00030000 d50364a4 00000020 d5c72c00 00000000 00000001
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.588659] fe80: 00000000 00000000 00000000 00000001 00000081 ffffffff 00000001 00000000
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.596932] fea0: d4f1e000 00042274 00000000 c0080bec 00000000 00042000 d5e9d740 00000274
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.605204] fec0: 00000080 00000001 00000081 00000000 00042274 00000000 d4f1e000 c0082a58
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.613477] fee0: ffffffff 00000000 00656412 00000000 0000001e bf067df0 00000000 00000000
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.621750] ff00: 00656412 d668ba80 d6589940 b6698e0c d6589940 d4f1e000 00000000 bf0726b8
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.630022] ff20: 00000000 00656412 b6698e0c d5f878d8 00656412 c00f2be8 00000081 00000000
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.638295] ff40: 00042274 c0010104 d4f1e000 00000001 00000000 c00834b8 00000001 00000000
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.646568] ff60: ffffffff d640f800 c085acbc 00000000 d6589941 00000004 00656412 b6698e0c
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.654841] ff80: d6589940 d4f1e000 00000000 c00f3040 b6f9bfa8 b6698e0c b6698dfc 00000036
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.663115] ffa0: c0010104 c000ff80 b6f9bfa8 b6698e0c 00000004 00656412 b6698e0c b6f9bfa8
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.671388] ffc0: b6f9bfa8 b6698e0c b6698dfc 00000036 b6698e04 00000004 00011000 b6698f7c
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.679661] ffe0: b6f99df4 b6698dbc b6a22918 b68e29dc 000b0010 00000004 00393239 55465f5f
May 15 16:37:09 vuduo4kse user.warn kernel: [767177.688681] [<bf705e8c>] (bcm7335_recpump_dataready [dvb_bcm7444]) from [<bf074774>] (NEXUS_P_Scheduler_Step+0x1e8/0x6d0 [dvb_base])May 15 16:37:09 vuduo4kse user.warn kernel: [767177.701932] [<bf074774>] (NEXUS_P_Scheduler_Step [dvb_base]) from [<bf068b78>] (nexus_driver_run_scheduler+0x44/0xd0 [dvb_base])
May 15 16:37:09 vuduo4kse user.warn kernel: [767177.714486] [<bf068b78>] (nexus_driver_run_scheduler [dvb_base]) from [<bf067358>] (nexus_driver_proxy_ioctl+0x1c4/0x53c [dvb_base])May 15 16:37:09 vuduo4kse user.warn kernel: [767177.727331] [<bf067358>] (nexus_driver_proxy_ioctl [dvb_base]) from [<bf067df0>] (nexus_generic_driver_ioctl+0x194/0x204 [dvb_base])May 15 16:37:09 vuduo4kse user.warn kernel: [767177.740170] [<bf067df0>] (nexus_generic_driver_ioctl [dvb_base]) from [<bf0726b8>] (nexus_driver_ioctl_native+0x54/0x94 [dvb_base])
May 15 16:37:09 vuduo4kse user.warn kernel: [767177.752523] [<bf0726b8>] (nexus_driver_ioctl_native [dvb_base]) from [<c00f2be8>] (do_vfs_ioctl+0x21c/0x640)
May 15 16:37:09 vuduo4kse user.warn kernel: [767177.762452] [<c00f2be8>] (do_vfs_ioctl) from [<c00f3040>] (SyS_ioctl+0x34/0x60)
May 15 16:37:09 vuduo4kse user.warn kernel: [767177.769862] [<c00f3040>] (SyS_ioctl) from [<c000ff80>] (ret_fast_syscall+0x0/0x3c)
May 15 16:37:09 vuduo4kse user.emerg kernel: [767177.777529] Code: e593200c e3a03f6d e0030293 e59f2160 (e7928003)
May 15 16:37:09 vuduo4kse user.warn kernel: [767177.783942] ---[ end trace 4d5076aa18eb9a66 ]---

 

Is this helpful for fix the hanging bug?


Thanks!

Using VU+ DUO 4K SE pvr, OpenPLi 8.3-release (2024-01-18-release-8.3).

 

Unfortunately the transcoded stream of a recorded video does not have the correct timecode included.

Usually it is unstable, not related to valid video time positions.

 

Transcoded stream link is the following:

http://192.168.1.100...=2&interlaced=0

 

 

Could be possible to add this feature?

 

I have VU+DUO 4K SE PVR with Openpli v8.3.

I used a 2TB HDD, but I got it filled.

I copied the 2TB EXT4 partition to 3TB HDD, then resized partition to 3TB size.

If I check the resized EXT4 partition with fsck.ext4, it shows a clean filesystem.

But when I put the drive to the external hdd enclosure of VU+DUO 4K SE PVR, it doesn't mount, does not recognize it.

The disk is recognized, the sda1 partition and EXT4 filesystem is not.

ls /dev/sda*
shows only /dev/sda, but not /dev/sda1.

Are 3TB GPT disks supported in OpenPLI v8.3?


What can cause not to mount this 3TB HDD with GPT partition and EXT4 filesystem?