SEARCH

Enter your search query in the box above ^, or use the forum search tool.

You are not logged in.

#1 2015-09-10 22:21:30

plemil
Member
From: Värnamo, SWEDEN
Registered: 2015-09-09
Posts: 17

[Solved] Backport kernel 3.16, no WebGL in Chrome

edit: I mark this as solved. Works OK in BunsenLabs Hdrogen RC1, but I have not been able to get to work in Crunchbang Waldorf with a bxkported 3.16 kernel. /edit.

After a kernel update through the wheezy-backports I have run in to some issues.
No sound, Virtualbox won't start the virtual machines etc. After some readings here on the forum I will probably sort that stuff out, seems to be fairly common issues.
Or maybe I skip that and go straight to BunsenLabs instead. smile

My major issue is the inability to enable WebGL in Google Chrome (running rev 45) and I have the same issue in Google Chrome Unstable (rev 47). In my main browser, Opera I had to re-enable the WebGL support, but that was it. With the 3.2 kernel I had to enable the "Override software rendering list" to get it to work but to no avail with the 3.16 kernel.

Some background...
In Sweden we have a "electronic ID-card" to be used on computers and smart phones to be able to securely identify on-line with to your bank, hospital etc. Originally there where support for Win, Mac and Linux on computers and for Android and iOS on phones. The company developing the application ditched the Linux version last year, blaming the lacking need due to low Linux usage in Sweden. Linux users are now directed to the smart-phone versions and have no longer the ability to use it natively under Linux.

In Sweden the Ubuntu users have been trying to solve this issue both politically and technically and the current solution is to run the Android version in Google Chrome using "App Runtime for Chrome" extension. They where happy with the performance, then enter Plemil (me that is...). I could not get it to work on my box. I could install the app, after I enabled the "Override software rendering..." flag. I could start the app but it would terminate after a while before it opened properly.
I installed a recent Ubuntu in VB with same result. BunsenLabs alpha, same issue and a Win7 with the same issue.
On a different machine running Win7 I installed a BunsenLabs alpha and Lubuntu in VB and voila I could connect.

After some Ubuntu forum discussions some one pointed out that the Google Chrome "App Runtime for Chrome" extension needed a kernel >3.5 to be able to run. That made some sense as BunsenLabs used the 3.16 kernel and Lubunt also used a more current kernel.

I found a nice backport post on this forum and went along on a fresh CB install on a third machine. Prior to the kernel update I verified that I had the same issue on a fresh install. It performed the same as on my main box, it would open but terminate. Performed the kernel update and that made me able to use the Android app within Google Chrome. Finally!

Held back a couple of days before I added the backports to my main box and performed the kernel update, but finally made the move. As I mentioned earlier that led to sound issues, VB won't start the virtual OSes etc. But my main issue is the lack of WebGL in Chrome.

Main issue:
When using the 3.16 kernel running the Android app in Chrome presented an new window instead of the termination, displaying some thing in the line of "This application is not supported on your hardware." Hmm... Progress or not?
Then I made a huge mistake as I decided to reinstall Google Chrome, which led to an upgrade to rev 45 from the currently used rev 44. Since then I am not able to even install the app, due to the lacking WebGL support. Enable the "Override..." flag does not help any more.
Using the 3.2 kernel have the same issues.

Anyone here that have any suggestions for my next step?
Do I have to ditch my beloved Sony Vaio VGN-A397XP (not going to happen!)?
I know she is quite old these days but she runs real smooth with CB Waldorf and hopefully with BL also.

Sorry for this mega monster post, but I have not found anything useful searching, and have run out of ideas.
If there are information lacking or if it is totally impossible to comprehend please let me know.

Best regards / Plemil (aka Per)

Last edited by plemil (2015-09-17 11:07:47)

Offline

Be excellent to each other!

#2 2015-09-10 22:58:48

tknomanzr
#! Die Hard
From: Heavener, OK
Registered: 2014-12-09
Posts: 777

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

Are you saying you are having trouble getting it to run in Virtualbox? If so, then I would recommend setting up a Linux partition on some real hardware and giving that a go.

Offline

#3 2015-09-10 23:09:32

plemil
Member
From: Värnamo, SWEDEN
Registered: 2015-09-09
Posts: 17

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

The issues I have are on my main box running Waldorf, as of now backported to the 3.16 kernel.
Maybe it's a HW thing after all.
I have had it up and running with the 3.16 kernel on two other machines. Both in VB and as a real install.

Q: Would it be possible to use a BunsenLabs live and install the needed Chrome stuff?

/p

Offline

#4 2015-09-10 23:25:22

tknomanzr
#! Die Hard
From: Heavener, OK
Registered: 2014-12-09
Posts: 777

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

If you can get it running on a non-backported 3.16 kernel, then yeah it would big_smile. I asked the question because I don't think I have ever gotten 100% open-gl hardware acceleration running in VB. Even when it says it's hardware supported there always seems to be bits missing.

Offline

#5 2015-09-11 06:28:45

Head_on_a_Stick
CatMod
From: A world of pure imagination
Registered: 2014-01-21
Posts: 4,797

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

Is there a specific reason why you changed your kernel version?

The stock wheezy/Waldorf kernel still has support from the Security team (this will continue until February 2016) so you only have to change it if there is a lack of support for your hardware.

Even then, I would recommend trying the live version of the BunsenLabs RC1 to see if it works with your hardware.
http://www.bunsenlabs.org/installation.html

I don't use Google Chrome but perhaps it no longer works with the wheezy/Waldorf libraries.

Offline

#6 2015-09-11 09:13:12

tknomanzr
#! Die Hard
From: Heavener, OK
Registered: 2014-12-09
Posts: 777

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

Chrome not supported in Wheezy
Remember this? If you need Chrome then your only real choice is to upgrade to Jessie. The BunsenLabs RC1 would fit nicely for that. This is completely unrelated to the OpenGL issue but it is worth noting that Chrome is no longer receiving support under Wheezy.

Offline

#7 2015-09-11 09:59:45

plemil
Member
From: Värnamo, SWEDEN
Registered: 2015-09-09
Posts: 17

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

Head_on_a_Stick wrote:

Is there a specific reason why you changed your kernel version?

Due to some issues with Seccomp-BPF in NaCl I had to update my kernel. And please don't ask me what this actually do, I don´t have a clue... But Seccomp-BPF are apparently only supported on kernels >3.5 and hence my need to upgrade. This module are needed to be able to run the Android stuff in Chrome.

BL RC1 seeds from home right now smile I hope I will be able to play with that tonight.

tknomanzr wrote:

Chrome not supported in Wheezy

Thanks for pointing that out, I had no idea. One more reason to try the RC1 from BL smile As of now the only solution is to run the app in Chrome. My main browser is still Opera.
I have been playing with Android in Virtualbox (a different proposed solution from the Swedish Ubuntu people), but that did not work due to some lacking hardware acceleration stuff.

I'm currently a bit low on HDD space and a bit reluctant to ditch Waldorf right away.
Q1: Is it possible to install Chrome within the live session?
Q2: Or do you need to set up a persistent live-USB for that?

Thanks for you input.
/p

Offline

#8 2015-09-11 10:03:14

damo
#! gimpbanger
From: N51.5 W002.8 (mostly)
Registered: 2011-11-24
Posts: 5,434

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

plemil wrote:

....
Q1: Is it possible to install Chrome within the live session?
...

You can use apt-get as normal, although you need persistence for it to..er..persist wink


BunsenLabs Group on deviantArt
damo's gallery on deviantArt
Openbox themes
Forum Moderator smile

Offline

#9 2015-09-11 10:23:00

plemil
Member
From: Värnamo, SWEDEN
Registered: 2015-09-09
Posts: 17

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

^ Hahaha.
I think I will try to make a persistence liveUSB with the RC1. I just read a recent tread [SOLVED] Debian jessie persistent live USB that looks promising.

Will probably not be a hero back home, but what the heck smile Thinks I spend way to much time in front of the screen already. Some how She don´t understand that this is fun  big_smile

Offline

#10 2015-09-11 14:40:09

hhh
Cityspeak
Registered: 2010-08-04
Posts: 3,253

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

plemil wrote:

I just read a recent tread [SOLVED] Debian jessie persistent live USB that looks promising.

Although those steps worked for me when running them from a jessie setup, johnraff's attempt from a wheezy/waldorf one failed. If you have 2 USB drives, you could run Hydrogen RC1 live on one and use that to run those instructions on the other drive.

Anyway, please report back if you do try that tutorial, thanks!


bunsenlabs     8)     forum mod squad

Offline

#11 2015-09-11 18:21:38

Head_on_a_Stick
CatMod
From: A world of pure imagination
Registered: 2014-01-21
Posts: 4,797

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

That link refers to Chromium, from the official Debian repositories.

I do believe the OP is talking about Google Chrome which was never supported by Debian anyway wink

I may be wrong but I think the independently-installed Google Chrome will have all the necessary security patches. My point was that it is installed via a repository and the repository line lists "stable" which is of course jessie now.
https://wiki.debian.org/UnofficialRepositories

Offline

#12 2015-09-11 21:31:34

plemil
Member
From: Värnamo, SWEDEN
Registered: 2015-09-09
Posts: 17

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

Right now Im running Bunsen RC1 Live, but unfortunally not in persistence. I will give it one more try and report back about that in the proper thread. Sorry for some missing signs as I have not been able to configure my keyboard to a Swedish layout... Slightly anoying to not find the correct keys at the moment.

I did manage to install Google Chrome but can not get WebGL to work. Enable the "Software override..." did not help either. In Iceweasel it worked from start and in Opera I had to enable it, but after that it is displaying correctly.

Head_on_a_Stick wrote:

Google Chrome which was never supported by Debian anyway

Maybe this is a dead end for me, but it is disturbing that it only fails in Chrome... And right now I need the Android stuff working in Chrome. Leaving Debian... Nah.

Wherent Ubuntu supposed to have some relation to Debian or have they abandoned that? The Ubuntu based distros seems to work without any issues.

Do you think it would be possible to run a non-Debian based distro in VB and get it to work with BunsenLabs as a host?
Or will BunsenLabs (Debian) be the limiting factor anyway?

/p

Offline

#13 2015-09-11 21:41:10

Head_on_a_Stick
CatMod
From: A world of pure imagination
Registered: 2014-01-21
Posts: 4,797

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

How did you install Google Chrome?

Other forums members (notably @ew/spacex) have reported many times that Google Chrome works very well in Debian.

Apologies if you covered this in your OP but I'm too tired to make my way through it.
hmm

Offline

#14 2015-09-11 22:01:09

plemil
Member
From: Värnamo, SWEDEN
Registered: 2015-09-09
Posts: 17

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

Yes I know it became a monster post. Had to let of some steam smile

My first atempt to install in the BunsenLabs RC1 Live environment where with apt-get in terminal, but that did not work for some reason so I reverted to the Install Google Chrome Stable in the WWW Browsers menu. That pulled in the latest stable rev 45.
As I did not get the persistence to work I am curently running Iseweasel.

In my CB Waldorf I have used both the menu installer and apt-get. No difference in performance, but Chrome versions prior to 45 seems to at least get WebGL up and running. But letting people install older versions dont seem to be the Google way. But on the other hand I never got the Android to perform properly anyway.

Offline

#15 2015-09-11 22:55:23

Head_on_a_Stick
CatMod
From: A world of pure imagination
Registered: 2014-01-21
Posts: 4,797

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

So does Google Chrome work in BunsenLabs?

I understand that it doesn't "stick" but does it at least run?

BTW, which `apt-get` command did you attempt to use?

I didn't think the Google Chrome repository was added to CrunchBang Waldorf (maybe the menu entry did that; I never tried it).

Offline

#16 2015-09-12 00:17:42

tknomanzr
#! Die Hard
From: Heavener, OK
Registered: 2014-12-09
Posts: 777

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

I am wondering if it might not be a video driver issue, the more I think about this. The limiting factor should not be the browser, as I can say that WebGL rendering is enabled on my Chrome browser running in the most recent BL. The laptop has ATI graphics. As I was having some issues with the card locking up with the open-source driver provided in Debian repos, I upgraded it to Debian fglrx drivers. I have no idea whether WebGL was enabled prior to the upgrade, however. At any rate, giving us an idea what video card you are running may be a more productive approach.
Post the output of:

lspci | grep VGA

and enclose it in code tags please.

Offline

#17 2015-09-12 04:55:37

hhh
Cityspeak
Registered: 2010-08-04
Posts: 3,253

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

The RC1 ISO has fbxkb installed. Fire that up and see if it makes keyboard configuration easier.
https://packages.debian.org/jessie/fbxkb


bunsenlabs     8)     forum mod squad

Offline

#18 2015-09-12 06:49:30

plemil
Member
From: Värnamo, SWEDEN
Registered: 2015-09-09
Posts: 17

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

A big thanks to everyone for helping out. I'v been running out of ideas...
Thank you all!

tknomanzr wrote:

video driver issue

plj@crunchbang:~$ lspci | grep VGA
03:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI M24 1P [Radeon Mobility X600]
hhh wrote:

fbxkb

Will try that onece I'm back in Bunsen. CB at the moment smile

Head_on_a_Stick wrote:

BTW, which `apt-get` command did you attempt to use?

sudo apt-get install google-chrome-stable
You might have a point as I did not verify that the repo where added. Silly me.

Offline

#19 2015-09-12 09:03:07

damo
#! gimpbanger
From: N51.5 W002.8 (mostly)
Registered: 2011-11-24
Posts: 5,434

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

plemil wrote:

....

Head_on_a_Stick wrote:

BTW, which `apt-get` command did you attempt to use?

sudo apt-get install google-chrome-stable
You might have a point as I did not verify that the repo where added. Silly me.

Menu -> Network -> WWW Browsers has options to install various browsers via bl-x-www-browser-pipemenu. I've just tried installing google-chrome-stable using that menu and it went through fine. (google-chrome.list was automatically added to sources.list.d by the pipemenu script, which also deals with apt keys)


BunsenLabs Group on deviantArt
damo's gallery on deviantArt
Openbox themes
Forum Moderator smile

Offline

#20 2015-09-12 14:10:22

plemil
Member
From: Värnamo, SWEDEN
Registered: 2015-09-09
Posts: 17

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

In BunsenLabs RC1 i get

user@debian:~$ lspci | grep VGA
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV380/M24 [Mobility Radeon X600]

Sligthly different output but performance are equal.

Offline

#21 2015-09-13 01:01:17

tknomanzr
#! Die Hard
From: Heavener, OK
Registered: 2014-12-09
Posts: 777

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

You might tryi running ATI's proprietary driver and see if that gets your hardware rendering enabled in Chrome. I have notice several issues with the open-source driver for ATI cards, most notably, the fact that it was causing my display to hardlock periodically while watching Netflix, Youtube, etc. Anyway, here's the Debian how-to:
Debian ATI proprietary
At the end, if only running one monitor, be sure to run:

sudo aticonfig --initial

to enable the driver. If using multiple monitors and you are having trouble getting them running, let me know and I will see if I can remember what I did to get it all working.

Edited to fix the aticonfig command.

Last edited by tknomanzr (2015-09-13 01:16:22)

Offline

#22 2015-09-13 08:56:19

plemil
Member
From: Värnamo, SWEDEN
Registered: 2015-09-09
Posts: 17

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

^ I will check it out and report back.
Probably late to night or possibly tomorrow.

Offline

#23 2015-09-13 22:29:07

plemil
Member
From: Värnamo, SWEDEN
Registered: 2015-09-09
Posts: 17

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

???
As of no reason I am currently able to run the Android Apps in BunsenLabs RC1 LiveUSB persistence.

I have been playing some with Chrome config and cache. Removing, renaming, restart Chrome, close Chrome, put back the original folders again etc. But that made no difference what so ever.

Started to investigate the Debian ATI how-to per tknomanzr :s advice and ended up at Testing performance. Decided to follow these steps before starting to play with a new driver. The tests performed well and showed that I have hardware support for WebGL, as shown in Iceweasel and Opera as well. As the need for a new driver seemed unnecesary I went for a new test with Chrome. Visiting chrome://gpu indicated that I now have hardware support for WebGl. Why? I don't know.
I then tried the Android App I have not been able to use, and hey presto, it runs without a glitch.
I have closed and restarted Chrome, and it runs every time. Rebooted and relaunched Chrome, and it runs.

I created a new persistence LiveUSB and on that one the App launches and runs directly.

I still have the issues in Waldorf, no matter what kernel I use, 3.2 or the 3.16 backport.

Using the glxinfo show some differences, could that be the reason for working in BunsenLabs and not in Crunchbang?
From BL RC1:

user@debian:~$ glxinfo | grep OpenGL
OpenGL vendor string: X.Org R300 Project
OpenGL renderer string: Gallium 0.4 on ATI RV380
OpenGL version string: 2.1 Mesa 10.3.2
OpenGL shading language version string: 1.20
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 10.3.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
OpenGL ES profile extensions:

From CB Waldorf:

plj@crunchbang:~$ glxinfo | grep OpenGL
OpenGL vendor string: X.Org R300 Project
OpenGL renderer string: Gallium 0.4 on ATI RV380
OpenGL version string: 2.1 Mesa 8.0.5
OpenGL shading language version string: 1.20
OpenGL extensions:

What do you clever people think? Can the Mesa 10.3.2 be my "Holy Grail"?
But then again why didn't it work from the beginning in BL?
Perhaps a good time to migrate to Bunsen... As soon I get my sound up and running. smile

Offline

#24 2015-09-17 11:04:24

plemil
Member
From: Värnamo, SWEDEN
Registered: 2015-09-09
Posts: 17

Re: [Solved] Backport kernel 3.16, no WebGL in Chrome

I have been playing my BL persistence LiveUSB for a couple of days now and it have been possible to run the Android apps without any issues. I have not been able to get it to work in my back-ported #! with a 3.16 kernel but as of now I kinda of OK with this setup.

Will probably proceed installing my new memory and  with getting a new HDD/SSD for my laptop and install BL from scratch on that instead of tweaking my current #!. I just have to figure out how to get my sound working...

So as of now I would say that this issue is solved, but unfortunately I do not know why.
Anyway thanks for tips and suggestions all of you, and keep up the good work with BL.

/ Per

Offline

Board footer

Powered by FluxBB

Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.
Server: acrobat

Debian Logo