Skip to content

Why is my GPU freezing

I bought a new gpu, AMD’s r9 290x. I was a bit surprised after first day since it seemed to be freezing some times. It could run just perfectly for few hours and then *boom*, it freezes. I googled the issue a bit and the most common explanations were Power issues and driver problems. I borrowed a new PSU from a friend, and it was still freezing. Reinstalled the drivers couple of times etc.

After couple of days I was certain that I had a broken GPU. I was also thinking that I have return it and get a new one from the warranty. However leaving an odd error description like “freezes after few hours” might just do nothing, since the maintenance clerk can always say “it works fine in here”.

I decided that I have to know what’s wrong with the GPU, so I can easily prove that the GPU is broken. I would need something like memtest86 for GPUs. MemtestCL does just that. I just download MemtestCL, and I got memory errors from my GPU. This could have saved so many hours of meaningless debugging! I also left a warranty claim that the memory is broken and you can easily see it by yourself with memtestCL. I got a new GPU the following day!

Note to self; If I ever have freezing problems with GPU, see if the memory is working with MemtestCL.

Oh, And remember to use the most current version of MemtestCL found from github: https://github.com/ihaque/memtestCL

Viskisieppo Chrome plugin to bypass glenmorangie.com site restriction to Finland

Finnish alcohol politics are like DRM. It has no effective on the abusive users, but it pisses off everyone else. Currently it seems that Whisky site glenmorangie.com is blocking Finnish users due to Finland’s alcohol laws.

Information want’s to be free, so I made a simple plugin for Chrome to bypass the country block at glenmoorangie.com.

Download

You can download the plugin from Chrome marketplace: https://chrome.google.com/webstore/detail/viskisieppo/dgmcbnhfgeejfapefklhjpilfiholhcc?hl=fi

How it works

You can download the whole project from my github page: https://github.com/Summeli/Viskisieppo

The plugin basically add, or edits the “X-Forwarded-for” HTTP-headers to make the requests look like they are not coming from Finland. This is basically implemented with Chrome webrequest-API

var requestFilter = {
	urls: [
		"*://*/*"
	]
};

chrome.webRequest.onBeforeSendHeaders.addListener(function(details) {
	var headers = details.requestHeaders;
	var header_set = false;
	for(var i = 0, l = headers.length; i < l; ++i) {
		if( headers[i].name == "X-Forwarded-for" ) {
			headers[i].value = "12.13.14.15";
			header_set = true;
			break;
		}
	}
	if(!header_set){
		headers.push({name:"X-Forwarded-for",value:"12.13.14.15"});
	}
	return {requestHeaders: headers};
}, requestFilter, ['requestHeaders','blocking']);

JamendoFM is now featured at Firefox Marketplace

JamendoFM is now on the list of featured music apps at Firefox Marketplace. It’s really nice to see that at least I had some success with this app, after porting it to Tizen, FirefoxOS and Android.

You can download the JamendoFM for

..maybe I could do one more client for Samsung smart tvs.

FirefoxFeatured

Updating JamendoFM for Android

I just got new phone Samsung Galaxy S4 and I noticed that the JamendoFM can not play music on it. I’m sure that it worked with some older Android phones, but it turns out that it doesn’t work with the new ones.

The problem is somehow related to the radiocontrols. Settings the audiosource, and programatically pressing play doesn’t seem to work with Android anynmore so I changed that stuff into Audio object, which seem to be working pretty well with new Androids.

Here’s my changes with the audio:

   /*the old code that doesn't work*/ 
   /*
    var audio = $("#radiocontrols");
    $("#radiosource").attr("src", sourceUrl);
    audio[0].pause();
    audio[0].load();
    audio[0].play();*/
    
    //lets do it with Audio object
    try {
    g_myaudio = new Audio(sourceUrl);
    g_myaudio.id = 'playerMyAdio';
    g_myaudio.play();
   } catch (e) {
    alert('no audio support!');
  } 

I also added the permissions for the lockscreen so the music will continue to play even when the lockscreen is on. The lockscreen permissions can be added though config.xml (phonegap) like this:

   <gap:config-file platform="android" parent="/manifest">
      <uses-permission android:name="android.permission.WAKE_LOCK" />
   </gap:config-file>

Samsung SmartTV and 802.11n

I just bough a new Samsung SmartTV (model UE46F6400). I just spent few hours just to configure the Wlan connection on it correctly. The TV can connect into the WLAN, but it disconnects after about 30 seconds, and then you’ll have to re-enter the password etc. to get it connected again for about 30 seconds, before it disconnects again.

I used the Ethernet connection to update the device firmware, but it did not help. I got multiple hits just by Googling the issue about Samsung SmartTVs that are disconnecting from the network. One blogger seemed to have similar problem as did I: http://blog.alexanderwinkler.se/post/53743100177/samsung-smart-tv-and-cisco-linksys-router However setting the WPA2 down to the WPA also downgrades the wifi n spec into lower bandwidth.  I even tested this with my Cisco Liksys E4500 with both 5Ghz antenna, and 2.4Ghz antenna. The Samsung TV actually can use the WPA2, if the network connection has been set into lower speed.

Here’s what I got working;

  • 5Ghz, Wifi A-connection, not mixed, or N
  • 2.4Ghz, B/G Connection, not mixed, or N

After that I had debugged the working Wifi settings I took a quick look at the manual. It says that Samsung recommends 802.11n, and soon after that it says that it doesn’t work correctly with GreenField mode. Yes, I can verify! it does not work. WTF Samsung!

The thing that troubles me is that the crappy Samsung TV software can not filter the Wlan hotspots that it can not support properly. It’s really frustrating to connect into these networks just to get disconnected after about 30 seconds. I would also like to know why does Samsung recommend using 802.11n in the user manual, while it does not support the specification properly. I bet that the average TV user does not know the difference between 802.11n legacy mode, and the GreenField mode.