Posts by Meganiekje

Hi pajtaz : There are some issues with hardware acceleration in the Chrome browser.

You need to force the video driver to enable 'TearFree', to enable hardware acceleration in Chrome, and fix the tearing.

Read this post, it might help to solve your problem : Screen tearing issue with Nvidia GPU

In some versions of Mesa and Chrome, the hardware acceleration was broken for older Intel IGPU's (HD3000 and older), but this is fixed in the latest version.

Quote from pajtaz

Now the hardware acceleration is not there any more (or at least it cannot be used for site Ziggogo.tv for which I need Chrome). Video playback if full of tearing and is really not enjoyable.

I know exactly what you mean, as I'm a Ziggo customer as well.....

if we can make LE start into the chrome browser by default, we have our own 'chromebook' that runs on all hardware.

Quote from HaLeXz

Fujitsu ESPRIMO Q900 - Intel Core i5 vPro (i think it has an Intel HD 3000 igpu). I don't mind about the tearing issue in chrome, because I use it only to browse the web, not to watch videos. Can you tell me how to run it without hw acceleration? Is there a flag to accomplish it?

Thank you

Hi HaLeXz , The easy way is : install the chrome add-on from the LE-repo (do not use the one in the LE-RR version) , right-click with your mouse on de crome add-on, select 'settings' , switch hardware acceleration 'off', click 'Ok'.

The HD3000 has this HW-acceleration problem.

Hi dschlic1, can you go in the chrome addon settings, and switch OFF the hardware acceleration ?

If chrome does start now, you most likely have an intel iGPU.

It looks like HW-acceleration for older intel graphics is broken in the newest mesa driver.

Quote from HaLeXz

About te Chrome issue, I stopped kodi and run chrome without flags, but the error is about the need to run it with "no sandbox" flag, so started it with the flag.

Hi HaLeXz and 5schatten :

Halexz seems to have the same issue as I have: If you have an older intel CPU (before Hd4500 iGPU) and you try to start the Chrome browser with 'HW-acceleration' enabled, you get a 'FATAL:memory_linux.cc(42)] Out of memory' error.

Starting chrome with only software acceleration does work, but you get 'tearing' artifacts, mostly visable in a fullscreen video as a triangle in the lower right corner or horizontal stripes. (test with this video:

AMD and Nvidia GPU's are O.K.

The LibreElec official 9.1.501 with Linux 5.1.16 and Mesa 19.1.5 is O.K.

In the previous RR-Nightly-version the HW-acceleration VAAPI was broken within Kodi also, but with version RR-20190920 this is O.K.

HaLeXz: What hardware do you use?

Quote from 5schatten

Meganiekje at least on my systems Chrome works now "tear free" again but this could also be Chrome v77.x related.

Hi 5schatten, on intel sandy bridge mobile ipgu (hd3000) hardware acceleration in Kodi works again with RR-20190920, but in Chrome it still does not. The Chrome://gpu page still shows all is software acceleration. To do te 'tear free' trick, you need (at least) 'canvas' and 'compositing' to be hardware-accelerated.

Quote from 5schatten

What's the output if you just run plain:

Code

kodi-service.sh --stop
strace /opt/google/chrome/chrome

This should boot chrome without any flags... maybe they screw things up.

5schatten : To check if the problem is in the flags, i installed the normal libreelec chome add-on. This addon also does not start on the system with hd3000 igpu.

If i go into settings for this add-on, and set the 'HW acceleration Mode' to 'off', the chrome add-on does start ! . Then i can change the HW acc. Mode to intel, and chrome keeps working, until the next reboot.

It looks like there is a problem with hardware acceleration.....

Also, the xorg.conf with tearfree=on, no longer works.

Quote from 5schatten

What's the output if you just run plain:

Code

kodi-service.sh --stop
strace /opt/google/chrome/chrome

This should boot chrome without any flags... maybe they screw things up.

5schatten : output of terminal session : 192.168.178.50_20190908133225.txt

I see a message about 'root not supported without --no-sandbox',

so i tried the same command on a amd system and chrome does not start here either. : 192.168.178.40_20190908134454.txt.

Quote from 5schatten

you could run this in a terminal step by step and post the output here:

Quote from 5schatten

Code

kodi-service.sh --stop
export CHROME_USER_FLAGS="$(cat ~/.config/google-chrome/chrome-flags.conf)"
strace /opt/google/chrome/chrome $CHROME_USER_FLAGS "$@"

this will stop Kodi then get's the usual chrome flags and run strace & chrome

5schatten : I did a complete fresh install, to get rid of the kernel command-line extension. Stil chrome does not start.

Output of the therminal session: output.txt

Uploaded a better version of the terminal session: 192.168.178.50_20190907141316.txt

I did a test on a i5-4590 with HD4600 IGP, and chrome does run correctly on this system.

Quote from 5schatten

Well it works here flawless http://ix.io/1ur7 and still you run it with your wrong kernel command line options

5schatten : On what intel CPU do you run it ? I can try it on a similar cpu family.

Quote from 5schatten

See if this build runs Chrome.
libreelec-generic.x86_64-9.80-rr-20190905-80e8518.tar

5schatten : No it does not.

Logs: log-2019-09-06-13.56.16.zip

I did test it on another intel system with IGP, Chrome also does not start.

Logfiles: log-2019-09-06-14.33.06.zip

Quote from 5schatten

btw. if the system has no dedicated gpu why is there [radeon.TearFree=on] in your kernel command line?

[Command line: BOOT_IMAGE=/KERNEL boot=UUID=5CCD-5DA5 disk=UUID=53a4726e-944b-4500-95f4-4f2b6e6bba70 quiet radeon.TearFree=on]

5schatten : That is a residu of my quest to get a tear-free chrome browser.

It did not work, and i forgot to remove it 😠

Can i be of any help to tackle the problem of a non starting chome browser on a system with a intel hd3000 IGP ?

I have 2 more desktop pc's with intel IGP's. I'll test them too, and post the results.

niek : I did see this problem too (or something similar) also when switching from LE8 to LE9.

I my case it is about an ir MCE remote, also power button related.

My system switches on from sleep mode, and directly back into sleep mode again, if i press the power button normally.

Only if i press the power button very very short, i get the correct function.

It looks like the linux kernal in LE9 translates a repeating powerkey command as 2 separate actions.

I have not been able to fix this.

Now, when i'm writing this, i think about something: maybe, the bios power-on/off function of the PC and the linux kernal are in some kind of 'overlap' function, and that is why the power command is executed twice !!

Quote from 5schatten

Did you disable the IGP?

5schatten : No, at least not on purpose.... kodi works like normal, without IGP that would not be possible, this system has no external GPU.

I 'downgraded' to version RR-190324-716b9f8, and now the chrome browser starts without any problems.

Here is the log when using RR-190324: log-2019-09-05-13.21.52.zip

Quote from 5schatten

Just get me a copy of the zipped file in your logfiles smb share. The chrome log should be included in the varlog file then.

Hi 5schatten, I did a full hard reset, go to Chrome, I see message about 'first time', and downloading and installing.

But chrome does not start on this latop. logfiles: log-2019-09-04-14.14.00.zip

uploaded the kodi logfile to http://ix.io/1uf8 and kodi crashlog to http://ix.io/1uf9

If i move de hdd to another laptop or desktop, chrome does start.

Move the hdd back to this Dell latitude E6320, chrome does not start.

Let me know if you need more info.

Quote from 5schatten

Just get me a copy of the zipped file in your logfiles smb share. The chrome log should be included in the varlog file then.

Sorry 5schatten, I can not find any other logfiles than the ones i did allready post.

I need some detailed info on how to retrieve the chome log files.

Quote from 5schatten

So if refresh rate switching is mandatory just use these addons which use Kodi for playback.

Let me explain why I'm so fixed on the chrome browser:

The biggest Tv-provider in Holland has a very customer-unfriendly Tv-Replay app on android. You can use chromecast, but not for replay-tv. If you connect a HDMI cable to your android device, the replay app blocks the output of the hdmi.

Their settop-box does only provide replay-tv for 6 channels.

The only way to have it all working on a big screen is to use the chrome browser.

I just need to avoid Nvidia GPU's to get a tear-free experience.

Quote from 5schatten

The Kodi.log does not help in this case because, as the name says, it's a Kodi logfile. Just post the logfile zip as you did before. It contains all logs which could be necessary.

5schatten : Sorry !

here are all the logfiles : kodi_Chrome does not start_log.zip