Main Page Archives

Backgrounds Vectors Photoshop

Avatar View my profile All stats

Stickies

No stickies found.

Random Comment

Comment #7973

rent a car, couldn\'t be very expensive

- Alex on Porter Airlines nonstop flight from Montreal to Halifax

	1600 X 1200 1920 X 1440	Mini Port Made by: Alex 2009-02-07 Desktop Picture
	1600 X 1200 1920 X 1440	Mini Bison Made by: Alex 2009-02-07 Desktop Picture

Particular problems with dual booting M1 Macs

Posted at 14:05 - 23rd, July 2021 by Alex

Tags: Apple, MacOS, Big Sur, dual boot, macbook, imac, macmini

Here's an interesting and somewhat unique issue that no one foresaw. Apparently if you have any M1 mac (Macbook, MacMini, iMac) and install the newest version of MacOS on it, which upgrades the firmware of the machine, the process has a special admin user that is created that impedes dual booting other OS' on the machine, even other versions of MacOS.
The real question is: is this intentional? Is Apple planning on blocking dual booting on Macs? Is this a developer preview bug?

With my macbook pro nearing actual end of life - not what Apple calls end of life, I was looking into getting another laptop and the idea of possibly getting an new Macbook did occur to me for a travel companion. But the issues just keep increasing with Apple.

Last Week on My Mac: The perils of M1 Ownership

According to the small print in Apple’s Platform Security Guide, when you set up a new M1 Mac, or set one up after restoring it in DFU mode, the primary admin account created is special: it’s the Owner account of that Mac. During that inital setup, the Mac sends a request to Apple for that Mac’s signed Owner Identity Certificate (OIC). This is based on a private key generated in the Secure Enclave known as the Owner Identity Key (OIK).

Each M1 Mac has just a single OIK, and access to that is confined to that primary admin user of the internal SSD, who is thus its Owner. If your M1 is configured with a single macOS boot volume group on its internal SSD, never boots from an external disk, and has no other admin users – a vanilla system – then that’s all transparent.

If you install a second operating system, on internal or external storage, the Owner needs to agree to hand over Ownership to users of that second system. And that’s where problems can occur, with a combination of puzzlement and frustration. Last week, when trying to perform a macOS update on a second operating system on my M1 Mac mini, I only succeeded at the third attempt, after a total of five hours.

It's an interesting little find but only the full release of Big Sur will tell us for certain what direction Apple is actually taking.

Be the first to comment on this.

Trance Fridays #363 - Ferry Corsten - Indigo

Posted at 19:55 - 22nd, July 2021 by Alex

Tags: Trance Fridays, ferry corsten, indigo, armin van buuren, bbc essentials

I almost get a video game vibe from this.

Be the first to comment on this.

Trance Fridays #362 - Simon Doty Feat Forest - This time

Posted at 23:23 - 10th, July 2021 by Alex

Tags: Trance Fridays, Simon Doty, Forest, This time

Be the first to comment on this.

Macbook pro Late 2011 GPU fix

Posted at 22:58 - 6th, July 2021 by Alex

Tags: macbook pro, late 2011, AMD, Radeon, discrete graphics, tech support

My late 2011 Macbook Pro finally bit the bullet. The graphic card problems that eventually affect all of that line finally got mine. Apparently, the GPU, an AMD Radeon 3000 HD, is the main problem, or at least a chip on the GPU. It's entirely possible to replace the whole GPU through removing and replacing it with a good one - a process that needs a technician like Louis Rossmann and a working GPU.

It's time consuming

Parts are difficult to find at this point

Even if you find replacement parts, the defect in the cards in ubiquitous and will happen again given time due to bad design

There is a way to salvage the macbook though!
Apparently, someone found a way to disable the discrete gpu and switch it back to the onboard intel card. God, who'd of thought switching to the on board card would be a good thing...
The process was relatively well known that DosDude01 even made a program to simplify the process, as long as you could get into the OS.

Personally, I found this guy's instructions on YouTube

But for those who don't want to watch the video, here are the instructions:

Turn off the machine

When the machine is completely off, turn it back on and hold Left Shift + Control + Option. The screen is supposed to flash, mine did, his didn't. This resets the SMC.

Now hit turn on the macbook and hold Command + Option + P + R for 2 chimes. This resets the PRAM.

Shut down the computer again, you may need hold the power button depending on your GPU and the what comes on the screen.

If you have a recovery mode turn on the macbook while holding Command + Option + R. This will bring up some kind of prompt for reinstalling the OS, potentially through a network download. I could never get the download to work for me, maybe because I'm Still on 10.10 and Apple is Apple, but not sure. I finally worked around it by holding the Option key on boot and choosing a recovery partition. But only bothered with getting into recovery mode later on, so I skipped to the next step without too much trouble. The dude has the same issue.

Turn on the macbook and hold Command + S to get into Single user Mode. This is basically the Bash prompt before MacOS loads up.

at the prompt enter the following code which will disable the discrete gpu

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

Now enable verbose mode to be able to see what's going on

nvram bott-args="-v"

Before you reboot you'll need to get into the Recovery mode I mentioned above, so on reboot hold Command + Option + R. When ready to reboot just type "reboot" (without the quotes) and hit enter. The graphics are fixed but only temporarily.

We need to disable Crucibal in recovery mode, it will take time depending on your internet connection. The newer OS's have a recovery partition that might be able to boot faster but for some reason mine didn't. Once it's finished loading click next on the language or welcome screen and then in the menu choose utilities and terminal.

In the terminal window, type "csrutil disable" (again without the quotes) and hit enter, this disables the security check for the os.
This is where it got messy for me. I got command csrutil not found. It took me a while to figure out, but apparently MacOs 10.10 does not have the command. I even tried running it like this: /usr/bin/csrutil. No luck. So for the most part as far as I can tell, it doesn't exist on 10.10. If you hit this problem on another os, you can always run an installer off a usb to get to this same point and run the command and everything should work.

Reboot the Macbook again, if you have the same graphics problems then run the above mentioned steps in single user mode one more time to change the nvram....gpu-power-prefs and then reboot. Now reboot and get back into single user mode.

When you can, type sbin/mount -uw / basically you're mounting and givign writable permission to the root of your hard drive.

Fair warning, you can mess up your macbook from here out so be very careful.

Now we're going to move some .kext files that reference the AMD card that's died, so we're going to type mkdir -p /System/Library/Extensions-off This creates a backupfolder the files we're going to move.

Now we're going to move the files by typing mv /System/Library/Extenstions/AMDRadeonX3000.kext /System/Library/Extensions-off/

Now we have to touch the folder to make the OS aware of the changes. touch /System/Library/Extensions/

Reboot the machine two or three times to make sure everything is working properly.

It's working, great, let's brings things back to how they were. Reboot into single user mode and undo the verbose command to show all the text on boot up sudo nvram boot-args=""

And if your OS has it, let's reactivate Crucibal. Get back into recovery mode (Command + option + r) open terminal and type this csrutil enable