Page 1 of 2

[Solved] Blank Screen in many Sites using Chrome in KDE.

Posted: 20 Mar 2014, 01:25
by mparillo
The Chrome browser in my Always Fresh USB seems to work here in the forums, but on some sites, the interior is black. I can tell I am in the right place because the tab title changes, and when I mouse around in the black area, I see the pointer change from a pointer, to a text entry locator, to a selection finger. Any ideas?

Re: Blank Screen in many Sites using Chrome in KDE.

Posted: 20 Mar 2014, 09:36
by fanthom
please provide sample URL of the webpage affected by this issue so we could try to recreate it on our side.
thanks

Re: Blank Screen in many Sites using Chrome in KDE.

Posted: 20 Mar 2014, 14:48
by mparillo
mail.yahoo.com
youtube.com

I wish I could say it was 100% of the time, but maybe 75% of the time.

Re: Blank Screen in many Sites using Chrome in KDE.

Posted: 20 Mar 2014, 16:19
by tome
Pepperflash (flashplayer) + absence nVidia or amdCatalyst? :unknown:

Re: Blank Screen in many Sites using Chrome in KDE.

Posted: 20 Mar 2014, 21:21
by fanthom
@mparillo

please generate xpsinfo report and link here.
thanks

Re: Blank Screen in many Sites using Chrome in KDE.

Posted: 20 Mar 2014, 23:44
by mparillo
fanthom wrote:@mparillo

please generate xpsinfo report and link here.
thanks
Thank you.

My file was uploaded to http://pastebin.ca/2668259

Re: Blank Screen in many Sites using Chrome in KDE.

Posted: 21 Mar 2014, 02:12
by brokenman
Please try using the nVidia drivers.

http://dl.porteus.org/i486/current/driv ... 6-1ftm.xzm

Place this in your modules folder and reboot. At the moment you are usin the opensource nouveau driver which is default.

Re: Blank Screen in many Sites using Chrome in KDE.

Posted: 21 Mar 2014, 09:57
by mparillo
For this to work, I cannot use the 'Always Fresh' mode, right?

Re: Blank Screen in many Sites using Chrome in KDE.

Posted: 21 Mar 2014, 19:57
by francois
All modules, including the nvidia module, will work under always fresh mode. :)

Re: Blank Screen in many Sites using Chrome in KDE.

Posted: 21 Mar 2014, 20:06
by mparillo
But do I have have to re-boot to be using the proprietary drivers? And if so, then how are they saved in the ''always fresh" mode?

Re: Blank Screen in many Sites using Chrome in KDE.

Posted: 21 Mar 2014, 20:15
by francois
If you put a module in the /porteus/modules folder on your usb key you are puttiong the file there really, effectively, even in always fresh mode. In always fresh mode you can change all the file structure of your usb key or your computer. See:
http://www.porteus.org/tutorials/37-ins ... -v-10.html
Porteus allows users to save their changes (i.e., system settings, downloaded files, bookmarks, browser history, etc) to a folder or image file (aka container) that exists outside of Porteus' core files. The 'changes=' cheatcode parameter sets the location for these changes. When you start Porteus with this cheatcode (enabled by default for USB installations), it will boot up the operating system and then apply your changes from this location. By default, Porteus is set to save these changes to /porteus/changes.
However, whatever you will do with you computer in terms of the linux system will not take effect, i.e. modifying your desktop, saving some hyperlinks, ... in always fresh mode. You need the save change mode available with the change= cheatcode, see:
http://www.porteus.org/tutorials/26-gen ... -them.html

changes= cheatcode instruction has to be determined in the instruction of your bootloader, syslinux or grub. If you have a linux filesystem you will not need a save.dat container (for windows filesystem).

I hope this helps. :)

Re: Blank Screen in many Sites using Chrome in KDE.

Posted: 21 Mar 2014, 20:35
by brokenman
But do I have have to re-boot to be using the proprietary drivers? And if so, then how are they saved in the ''always fresh" mode?
To test it, put the module in your modules folder. When you arrive at the boot menu choose the first option but hit the TAB key so you can see the boot options. Remove the 'changes=' code which effectively puts you in 'always fresh' mode but will load all modules in the modules folder.

The real 'always fresh' mode uses the boot option 'base_only' which means nothing in modules folder will be loaded.

If you have too many doubts just stick the module in the base folder and rename it to 009-video-driver.xzm

Re: Blank Screen in many Sites using Chrome in KDE.

Posted: 21 Mar 2014, 21:47
by mparillo
I am pretty sure I copied it to my USB key:
guest@porteus:/mnt/sdb1/porteus/modules$ ls -alc
total 39680
drwxrwxrwx 2 root root 4096 Mar 21 13:34 ./
drwxrwxrwx 6 root root 4096 Mar 20 21:37 ../
-rwxrwxrwx 1 root root 40624128 Mar 21 13:34 nVidia-334.21-porteus-v3.0-i486-1ftm.xzm*
guest@porteus:/mnt/sdb1/porteus/modules$ cd /mnt/sdb1

But my youtube.com window is black still. So I am running xpsinfo again:
My file was uploaded to http://pastebin.ca/2670141

Good thing I have no problems with the Porteus Forum ;-)

Re: Blank Screen in many Sites using Chrome in KDE.

Posted: 21 Mar 2014, 22:24
by brokenman
Nope, you didn't follow the instruction about hitting tab during boot. I see this in your log.

CHEATCODES:
quiet initrd=initrd.xz nomagic base_only norootcopy timezone=America/New_York BOOT_IMAGE=vmlinuz

This means ONLY the base folder will be loaded and the modules folder will be ignored. Place the module in your base folder and call it 07-nvidia.xzm then reboot.

Re: Blank Screen in many Sites using Chrome in KDE.

Posted: 22 Mar 2014, 00:24
by mparillo
Hitting <tab> and removing the changes=/porteus from the default boot option seemed to work.
Thank you.

So, if I want to go back to using the "always fresh" option, I need to mv /mnt/sdb1/porteus/module/nVidia-334.21-porteus-v3.0-i486-1ftm.xzm*
To /mnt/sdb1/porteus/base/
Does it matter what I name it?
07-nvidia.xzm
009-video-driver.xzm

Currently I have:

guest@porteus:/mnt/sdb1/porteus/base$ ls -alc
total 390812
drwxrwxrwx 2 root root 4096 Mar 14 13:34 ./
drwxrwxrwx 6 root root 4096 Mar 20 21:37 ../
-rwxrwxrwx 1 root root 15241216 Mar 14 13:34 000-kernel.xzm*
-rwxrwxrwx 1 root root 46567424 Mar 14 13:34 001-core.xzm*
-rwxrwxrwx 1 root root 47206400 Mar 14 13:34 002-xorg.xzm*
-rwxrwxrwx 1 root root 67751936 Mar 14 13:34 003-kde.xzm*
-rwxrwxrwx 1 root root 49315840 Mar 14 13:35 04-chrome.xzm*
-rwxrwxrwx 1 root root 133033984 Mar 14 13:35 06-libreoffice.xzm*
-rwxrwxrwx 1 root root 41066496 Mar 14 13:35 08-skype.xzm*

BTW, why does the * appear in my konsole, but not in dolphin?