Bitcoin donations are welcome:14snQXeLcnJtWUduKZ6rC2MHdPYrYar1Tw

Thursday, April 7, 2016

Chromium in Debian: Flash missing - manual install of Pepperflash

So, here's the situation:
1.) Google Chrome dropped support of 32bit linux
2.) Pepperflash has gone missing from the Debian repositories
3.) Chromium only supports Pepperflash

Here's how you fix it:
1.) Install chromium.
2.) "apt-get purge" (not just remove) everything that has to do with flash.
3.) Download the latest available version of Google Chrome for 32bit so we can extract the plugin we need. Latest available version is google-chrome-stable_48.0.2564.116-1_i386.deb available here: http://bbgentoo.ilb.ru/distfiles/google-chrome-stable_48.0.2564.116-1_i386.deb
4.) Extract the file. Go to opt/google/chrome and find the PepperFlash directory. From this directory copy the libpepflashplayer.so to /usr/lib/chromium/plugins/ or any other available directory.
5.) For some reason I can't chromium to load the plugin by default. So I made a shortcut executable file with the following chromium prefix:
/usr/bin/chromium --ppapi-flash-path=/usr/lib/chromium/plugins/libpepflashplayer.so
6.) Run it. Enter "chrome://plugins/" into your address bar. It should now show up here.

Tuesday, October 27, 2015

IKEA Utrusta LED - remote problems

Installed the IKEA Utrusta LED system for my kitchen. The system have caused me quite a headache as I had a lot of problems with the lights randomly responding to the remote.

After a while I managed to sort out the problems. I did the following:
1.) First I got a new remote from IKEA. I'm not quite sure if this solved any problems or not, but I do think it helped quite a bit.
2.) Then I managed to identify one LED device which seemed to cause problems way more often then the others. I replaced this one. No more specific problem with this light.
3.a) My lights now worked all good until one night when I was downloading some huge files over the wireless network, when the lights went all hammock when using the remote. As I already know the Utrusta remote is using the 2.4ghz frequency - the same as my wifi, I went straight for the router and unplugged it. Suddenly it all worked perfect again.
3.b) To solve this problem I booted up my router again and changed wifi channel. I also have a router which runs on the 5ghz frequency. I was therefore able to change the wifi devices I have which use the most bandwidth to this frequency.

After taking these measures, I haven't had any problems for several weeks. The lights also respond way more synchronous then before. It's rather strange that IKEA doesn't seem to know about the frequency problems themselves. When I called them in the beginning this wasn't even mentioned, but after doing some research online it seems to be a rather normal problem with interference between devices running on the same frequency.

Update: 3 months later. Still no problems. All good! (FYI: The problem lasted me for 1-2 years until I managed to solve it.)

Saturday, May 23, 2015

Torrenting to NAS via CIFS/SMB never completes

Problem: Vuze keeps on redownloading and redownloading the last 10-30% of the torrent file over and over again. MBs downloaded exceeds total torrent size, and it never ends.

Solution:

Edit your /etc/fstab for the cifs mount.
cache=none,user,uid=abcd123,gid=users,rw,suid,credentials=/root/nascredfile

Friday, April 24, 2015

Fix: Shoe air whooshing sound from shoes

I had big problems with this on some Loake Churchill shoes. The sound came from the toebox and was caused by my arch which is a tad large, giving the air in the toe box no easy route to escape when I was walking.

The reason my shoes were so tight around my arch was the lacing which my shoes were delivered with. If you take notice of the Shoe shop lacing pictured below, you will see that when you tighten this lacing, it takes very little pressure before you make the lacing around your arch to tight. The solution is changing the lacing to the zigzag lacing, and leaving enough slack on the lower lacing.

It probably sounds weird that lacing should cause such problems. But give it a try.

I've also read of people leaving strings of leather in a | | formation above your arch, leaving a "channel" for air to escape through, which solved the problem.



Friday, February 13, 2015

Backlight keys not working on t510 linux

This is due to a kernel error from what I understand.

Here's a quick fix.

apt-get install xbacklight

then add the following bindkeys if you are running fluxbox:
nano .fluxbox/keys

add:
None 232 :Exec xbacklight -dec 5
None 233 :Exec xbacklight -inc 5

Reboot fluxbox

Friday, November 14, 2014

CIFS, Wicd and Ubuntu 14.04 slow shutdown/reboot

Got this problem after mounting a CIFS/Samba drive through my wireless network. This appears to be a rather normal problem for lots of users. It was also hard locating a fix for my problem, as many users are using network manager as well.

I found a great fix though, which also is reported to work for network manager.

It's rather uncomplex and logical. The fix is moving the umount procedure to a earlier runlevel in the rc.d folders. The problem appears to be that the system shuts down the wifi before umounting.

Fix:
Go into /etc/rc.0 and /etc/rc.6, and move
user@system:/etc/rc0.d$ mv S31umountnfs.sh S14umountnfs.sh

Hope this helps :-)

More info is available here: http://blog.avirtualhome.com/ubuntu-shutdown-problem-cifs-related/

Saturday, October 11, 2014

Solution: Encrypted system and UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.

If you get this error during startup, it's possible to fix. I did it for debian.

First get a rescue cd from grml.org. When you have booted it up enter the standard command line mode. For some strange reason you only get the option of a few language sets by the system itself when booting, but when you have entered the command line you can easily load other language sets by running loadkeys. There's a bunch of other keysets located on the system.

Next check out this tutorial for more information on how to solve the problems with fsck and the encrypted drive:
http://devouredbylions.blogspot.no/2011/01/fixing-corrupted-encrypted-lvm.html

In short terms you have to run the following cmds:
cryptsetup luksOpen /dev/
vgscan --mknodes
vgchange -ay
fsck /dev//