[TESTING] Linux 4.9 kernel and improved video stack for Vero 4K / 4K +

Testing
522

I spoke too soon - the 3d has been hurt badly by the update today. Yesterday I watched the meg in 3d and it was perfect. I just did the update and now it has flashing screen with pixelations. i checked a few other movies (avatar 3d and avengers 3d) and it has the same issue. while i didn’t watch avatar 3d or avengers 3d recently, the meg 3d was perfect yesterday (with the previous update) and it now unwatchable (after today’s update).

the hobbit 3d issue as shown in my post earlier and with the logs is unfortunately still there.

523

Issues with the latest update for me:

  1. All white listed resolutions were removed. I had to manually add them.

  2. After rebooting the first three times, the refresh rate defaulted to the first one on my list (1080p @ 23.98) and not what I manually set it at (1080p @ 60.00). This now seems to have resolved itself.

  3. The contrast bug is still present.

  4. Lip sync issue is now difficult to determine for some reason.

Fixed:

  1. Menu text, clearlogo, icons now rendered cleanly like in kernel 3.14.
524

Hi Sam,

I’m still not able to connect the Vero4K to my 5GHz network (channel 112).

Fyi: "iw list"shows

  • 3.14 kernel: channels 1-11, 36-64, 100-165
  • 4.9 kernel: channels 1-11, 36-64, 149-165

Regulatory domain: DE

Could it be a firmware or nvram issue?

525

Try installing CRDA and setting the regulatory domain.

526

crda is already installed (REGDOMAIN=DE). Any other idea?

527

Not without logs, no.
I will try set up a test network

528

I posted a log on 8 April (above). Pls let my know if you need anything else. Thank you!

529

Thanks. I will check it soon.

530

Checked that log, didn’t see a region being set. Could be a driver issue or something else.
Have you verified with sudo iw reg get

531

I’ve also did update recently, but still not able to see USB serial connection :neutral_face:

533

I don’t know what CONFIG_ options are needed, and no one has provided a log of it working from 3.14, so I’m not able to solve this at this time.

534

to add to my previous post, i just went back to the previous version (april 16 - 4.9.113-16) and the avengers 3d and avatar 3d do play fine with that version.

535

That’s fine.
just a quick question regarding this: is it possible to downgrade to 3.14?
Thanks

536

Yes - you can reinstall from the Downloads page.

537

That’s weird, the movie doesn’t have the stereoscopic flag set, so the 3d MVC detection fails. But the file has also the MVC tag in its name, so it should be detected as MVC as fallback. But it isn’t. I assume (because there’s also the ‘3D’ in its name) that this “3D” overrides the “MVC” and then Kodi defaults to left_right. I’ll try to reproduce it here. Stay tuned …

538

thanks for getting back to me! just a thought - could it be b/c of the part 1 in the name?

539

I have also the pixalation in some 3D movies - and - a lot of x64 content, mostly with lower resolution will play only without hardware acceleration. On 1080p, some will play some not.

540

Hi fzinken,

setting the regulatory domain with crda seems to work:

osmc@Vero4K:~$ uname -r
4.9.113-17-osmc

osmc@Vero4K:~$ sudo iw reg get
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)

osmc@Vero4K:~$ iw list | grep dBm
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm)
* 2472 MHz [13] (20.0 dBm)
* 5180 MHz [36] (20.0 dBm)
* 5200 MHz [40] (20.0 dBm)
* 5220 MHz [44] (20.0 dBm)
* 5240 MHz [48] (20.0 dBm)
* 5260 MHz [52] (20.0 dBm) (no IR, radar detection)
* 5280 MHz [56] (20.0 dBm) (no IR, radar detection)
* 5300 MHz [60] (20.0 dBm) (no IR, radar detection)
* 5320 MHz [64] (20.0 dBm) (no IR, radar detection)
* 5745 MHz [149] (20.0 dBm)
* 5765 MHz [153] (20.0 dBm)
* 5785 MHz [157] (20.0 dBm)
* 5805 MHz [161] (20.0 dBm)
* 5825 MHz [165] (20.0 dBm)

541

@aliebe - after setting this, can you run dmesg | paste-log and send me the URL

Cheers

Sam

542

Just as an update: I know what’s causing the recent playback issues.

A simple (temporary) fix could be to revert a couple of things, but this won’t be solution we want going forward. If we can’t make enough progress in the next few days, then we’ll push this as a stop-gap to keep testers happy during this lockdown.

I would like to stress clearly though that this is still a testing build and is expected to be somewhat rough around the edges.

Cheers

Sam

4 Likes