Author: admin

MacBook Pro GPU AMD Failure Method 2

MacBook Pro GPU AMD Failure Method 2

As detailed in the post over there, a friend had an issue with MacBook pro with the GPU AMD failing. A few months later it  wouldn’t even boot. Couldn’t even get it into single user mode.

So, how did I get it working again. Well first of all I had a USB stick with a non-GUI version of Linux, I used ArchLinux. I won’t go into the details here, but I did have issues copying the ISO of ArchLinux onto a USB stick using my own Mac. You can see how I did this here.

WARNING – these worked for me, they may not work for you, ensure you take a full back up before performing any of these tasks, the read only disk image will be faster, but the read-write is better, it still took me two days to perform a backup for a 500GB disk. If your Time Machine is available, use that. The author of CheekyFactor.com will not be held liable for loss of data or broken machines. Do not perform these tasks if you are a novice.

OK, now to get this MacBook pro working again. Stick the USB disk in with ArchLinux on into the MacBook pro.

Power on the machine, ideally it needs to have the power cable attached to the machine. As soon as you hit power, press down the alt key at the same time.

You will get an option to either boot from the Macs hard drive, or UEFI. Select UEFI, you will see something like this:

Ensure you have the top item selected for ArchLinux and press e. As you can see at the bottom of this image you will see a line, at the end of that line add nomodeset and hit enter.

You will be booted into ArchLinux:

Change the directory by running the command:

cd /sys/firmware/efi/efivars

You will see something like this:

Run the command:

ls

That is an L not an I. Hit enter and you will something like:

What we are interest in is those GPU lines in the bottom left hand corner, they may not necessarily be there, you just need to look for something like this. But don’t worry if you can’t see them.

Now we have to unmount the efivars folder

Run:

cd /

umount /sys/firmware/efi/efivars/

mount -t efivarfs rw /sys/firmware/efi/efivars/

cd /sys/firmware/efi/efivars/

Then run:

run

chattr -i “gpu-power-prefs- then press tab and close it with a “
chmod ugo+w gpu-power-prefs- then press tab
rm gpu-power-prefs- and press tab to get the file

This will look something like this.

We now need to create a new gpu file that we can mute, run:

printf “\x07\x00\x00\x00\x01\x00\x00\x00” > /sys/firmware/efi/efivars/gpu-power-prefs-fa4ce28d-b62f-4c99-9cc3-6815686e30f9

Now to mute it, the chattr command makes it accessible only to the superuser, so in theory when you boot it won’t mess up, run:

chattr +i “/sys/firmware/efi/efivars/gpu-power-prefs-fa4ce28d-b62f-4c99-9cc3-6815686e30f9”

Now to flush the efivars cache by running:

cd /
umount /sys/firmware/efi/efivars/

In theory, we can now reboot, type in reboot. Initially I had issues booting, it got stuck and kept restarting. So I booted into recover mode by holding down command and R down on boot.

Once in recovery mode I opened the terminal:

If you have more than one partition run the following lines, if you only have one partition you can skip this bit:

diskutil cs list (find UUID for drive)

diskutil coreStorage unlockVolume UUID

Now, we all need to do the following, run the command:

cd /Volumes/Macintosh\ HD

Now, we need to remove the AMD Kexts, first create a directory where we can stick them on the off chance you need them in the future using the line:

mkdir AMD_Kexts

Now, lets move those AMD Kexts:

mv System/Library/Extensions/AMD*.* AMD_Kexts/

then type in reboot:

reboot

In theory, if you have done everything correctly, you should now have a working MacBook Pro.

BUT, please have in mind, this is not a permanent fix. When you upgrade or if you need to reset the SMC or NVRAM you will get the same error and you will need to perform the tasks above again.

I just hope this is a better solution than what was shown in method 1 which kept failing without the SMC or NVRAM being reset.

There is a permanent solution I have found on YouTube, but due to knowing how bad I am at soldering, I think I will pass on that one. But if you want to look at the permanent solution check this out.

But if you do that, you are on your own.

Using addon domains with WAMPserver

Using addon domains with WAMPserver

Don’t judge here, it is not my choice here, for one of my servers I am forced to use Windows 2012 R2, I have WAMPserver installed on this server.

So, it came to a point where I needed to have different domain names pointing to different directories on the server. So I have a main domain, say for example domainname.com, but I need to have domaintwo.com on the same server. With what I am about to show you, you can have as many domains as you want, if you are working locally you can also have say local1.domain and local2.domain.

Right so how can this be done? 

Read More Read More

MediaWiki composer extensions

MediaWiki composer extensions

With certain extensions using MediaWiki you may need to use composer. Two examples are Semantic Compound Queries and Maps. This example is using Windows Server 2012 R2 running WAMPserver. Obviously you will need to have composer installed in the PHP version you are using.

To install this using composer open the compose.json in the root of the Wiki:

You will see a lot of code like this:

Find the line:

“mediawiki/semantic-media-wiki”: “~2.5”

In the example for Semantic Compound Queries the extension page tells you to add the code:

{
    "require": {
        "mediawiki/semantic-compound-queries": "~1.1"
    }
}

But in reality, we are only interested adding

“mediawiki/semantic-compound-queries”: “~1.1”

Add this line above the Semantic MediaWiki line:

“mediawiki/semantic-compound-queries”: “~1.1”,

Note, we now have a comma on the end of the line, this is key:

Save and close the composer.json file.

If you have already been running commands in the command prompt, and crucially if you have set the path anywhere, close the command prompt and reopen it.

Change the directory to the root of your Wiki and run:

composer update

Then run:

composer require mediawiki/semantic-compound-queries:~1.1

Obviously replace the semantic compound queries as detailed on the extensions page on MediaWiki.

Install Semantic MediaWiki on a Windows Machine

Install Semantic MediaWiki on a Windows Machine

You can find instructions on Semantic MediaWiki site on how to install on Windows, but it is advised that Semantic MediaWiki is not supported for Windows environments. It also misses a few areas that need to be included to ensure it installs. This is how I did it:

Ensure you have composer installed and it is in the PHP version you are using.

Remove or comment out any Semantic MediaWiki lines in the LocalSettings.php

Add the line:

enableSemantics(‘localhost/wiki’); /**adjust to yours*/

Open the command prompt, change the directory to the root of your wiki and run:

composer update:

Next run:

composer require mediawiki/semantic-media-wiki “~2.5”

Verify it has installed by going to the Version page:

Job done, on the off chance things don’t go to plan, change the directory to the maintenance folder. With Windows you will need to set the path to the PHP version by running:

set path=path/to/PHP/install

Then run:

php update.php –skip-external-dependencies

Job done.

To make Semantic MediaWiki more useful you may want to install other extensions to work with it, the five I use are:

  • Page Forms
  • Semantic Compound Queries
  • Semantic Drilldown
  • Semantic Internal Objects
  • Maps

Page Forms, Semantic Drilldown and Semantic Internal objects are fairly straight forward to install, just follow the guidance on the extension page. But Semantic Compound Queries and Maps are a little more complex. They both require the use of composer.

See the MediaWiki composer extensions for more details.

MacBook Pro GPU AMD Failure Method 1

MacBook Pro GPU AMD Failure Method 1

So a friend has an issue with an issue where his MacBook Pro late 2011 was not booting. Looking at the issue and finding information online, it turns out the AMD card seems to fail on MacBook Pros. But thankfully it can be programatically bypassed.

A lot of information I was finding insisted on using ArchLinux. I did get ArchLinux booting on a Surface Pro Virtual Box, but just couldn’t get it working on the Mac, it just kept either not recognising that boot media was inserted into the USB or CD drive. I also tried using Gentoo, but I couldn’t get passed the Grub.

But eventually I sussed it out.

This is a short video of what it was like, sped up, to what it looked like once it was up and running. When I first attempted to boot up before it failed it took six minutes to reboot, once the changes had been made it booted in less than a minute.

WARNING – these worked for me, they may not work for you, ensure you take a full back up before performing any of these tasks, the read only disk image will be faster, but the read-write is better, it still took me two days to perform a backup for a 500GB disk. If your Time Machine is available, use that. The author of CheekyFactor.com will not be held liable for loss of data or broken machines. Do not perform these tasks if you are a novice.

Boot up in single user mode by holding down Cmd S when you turn on your Mac, enter the following:

nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00

Turn on Verbose mode as default:

nvram boot-args=”-v”

and type in:

reboot

The machine should now boot normally.

A few months later the same machine had the same issue, even having issues booting. So, after looking on Google, I found a new way of fixing the issue, hopefully it will be a more permanent fix, you can see how I did this over here.

SharePoint Calendar does not show when in a page as a webpart

SharePoint Calendar does not show when in a page as a webpart

So I was asked to add an events calendar to a SharePoint site that is being used as a portal. This would display the calendar as a WebPart on a SharePoint Wiki page.

But, obviously, as with anything SharePointy, this wasn’t as straight forward as just sticking the WebPart in. The issue I encountered was the events were not showing when it was inserted as a WebPart.

After much use of Google and asking specialists in SharePoint I was coming up blank. I did find that it was due to a JavaScript issue. To fix the issue, I had to open the page which the calendar was displayed on in SharePoint designer and add the following code:

<script type=”text/javascript”>
SP.SOD.executeOrDelayUntilScriptLoaded(function () {
SP.UI.ApplicationPages.ElementUtility.$3f = function ($p0) {
return ($p0.substring(0, 3).toUpperCase() == “WPQ”)
? $get(‘WebPart’ + $p0)
: $get($p0);
}
}, “SP.UI.ApplicationPages.Calendar.js”);
</script>

This over-rides the default JavaScript in the Wiki page, job done.

Install MediaWiki

Install MediaWiki

So, I was asked to install MediaWiki on a Windows Server 2012 R2. This example shows you to install when using the server with a GUI.

You can transfer the files using your control panel if you don’t have a GUI, and in theory it should also work the same with a Linux

Read More Read More

Orange or Red on WAMP installation

Orange or Red on WAMP installation

So, for work I was provided with a Windows Server. To run the scripts I wanted I had to install WAMP. I did this on my own personal server initially for testing purposes.

But I had a small issue, it came with the error where the WAMP sign refused to change from Red or Orange to Green as it should, I was stuck with:

So what did I do to fix this? I hear you cry (sorry, couldn’t resist).

Read More Read More

Installing WordPress

Installing WordPress

I used to be a Joomla! type of person. That was until 2014 when things kept breaking and simply not working. I started using WordPress instead when a company I worked for decided to switch from Joomla! to WordPress. This was really the first experience I had with WordPress, since I have primarily used WordPress with the occasions of using other systems such as MediaWiki, depends what work at the time I have on and what system is required.

To install WordPress, there are two ways of doing this, the easy way, and the hard way (but not that hard). I will go into more detail on the hard way soon, but first I will touch on the easy way.

Easy Install of WordPress

Read More Read More

Notice for AdBlock users

Please support this website by adding us to your whitelist in your ad blocker.

Ad-revenue is vital for the upkeep of this site, expenses incurred include time to manage the site, hosting and domain name. You can also support this site by donating and/or registering for goPro.

With goPro you will not see any ads.

Your assistance is appreciated.

Gary