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.
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.
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.
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)
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.
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?
If you can get it running on a non-backported 3.16 kernel, then yeah it would . 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.
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.
Yes I know it became a monster post. Had to let of some steam
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.
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).
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.
plj@crunchbang:~$ lspci | grep VGA 03:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI M24 1P [Radeon Mobility X600]
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.
sudo aticonfig --initial
Last edited by tknomanzr (2015-09-13 01:16:22)
^ I will check it out and report back.
Probably late to night or possibly tomorrow.
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:
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.