user:-macos-11-“big-sur”-can-make-older-macs-unusable

User: macOS 11 “Big Sur” can make older Macs unusable

Users on various forums report problems with their Macs when trying to install Big Sur. The setup then stops and makes the computer unusable, a restart is no longer possible.

The new operating system, including macOS 11 has been available since last week. A large number of MacBook Pro machines of the years 2013 and 2014 be – and here in particular the 13 – inch model, according to a five-page thread in the Apple Support Communities. Common debugging methods seem to fail According to users, the big sur remains -In the meantime the installation shows a black screen – nothing seems to happen after that. Attempts to revive affected computers – for example by resetting, starting safe mode or restoring the Internet – seem to fail, the MacBook Pro remains “bricked”. If Apple is asked what to do, the service is said to have suggested a visit to the Genius Bar in the local Apple Store, reports a user.

Apple itself seems to be informed about the problem in the meantime. One affected person reported that the support team had told him that the bricking had been “escalated” to Apple’s engineering team. What exactly leads to bricking is currently completely unclear – including why older machines of all things are affected. In addition, it cannot yet be said whether only the 13 inch MacBook Pro of these years is subject to a risk of bricking and whether it is possibly a Hardware problem that is revealed by the Big Sur installation.

Make a backup Until Apple has addressed the bug, users of older Macs can only wait with the Big Sur installation; However, not all machines are affected by any means, so that bricking becomes a gamble. You should urgently create a backup before starting the installation of macOS 11.

The update brings In addition to a new surface, various changes under the hood. There are numerous programs that have not yet been or only partially adapted to Big Sur, so there is no rush to install them. However, Apple has apparently only fixed a number of security problems with macOS 11. 0.1, older macOS versions are still waiting for fixes. (bsc)

microsoft-announces-details-of-the-end-of-support-for-surface-devices

Microsoft announces details of the end of support for Surface devices

In a support document, Microsoft has announced information about the end of support for the devices of the in-house Surface series. It’s not about the end of support for the installed Windows version, but about when Microsoft will not provide firmware updates or new drivers for these devices. For this, Microsoft promises four years of support from the first release of the device; in most cases the date of the market launch in the USA should apply here.

There was already a date for individual devices known, new additions are now Surface Laptop 3 (22. October 2023), Surface Pro 7 (22 October 2023), Surface Pro X (November 5th 2023), Surface Pro X SQ2 (13. October 2024), Surface Go 2 (May 6th 2024) and Surface-Laptop Go (13. October 2024).

Support consists of two parts: Support for the respective operating system version and that for drivers and firmware updates. Incidentally, the end of support for the hardware does not mean that the device then has to be disposed of: the operating system continues to receive updates. (ll)

some-raspberry-pi-4s-can-now-overlock-to-23-ghz-here’s-how.

Some Raspberry Pi 4s Can Now Overlock to 2.3 GHz. Here’s How.

Leave no MHz behind. Where the previous Raspberry Pi overclocking high for the Pi 4 was 2.147 GHz, newer units, including the Raspberry Pi 4 8GB and some variations of the Compute Module 4 can now hit a full 2.3 GHz. All Raspberry Pi 4 units, except the Raspberry Pi 400, operate a stock clock speed of 1.5 GHz so this is a 35 percent speed jump you get by tweaking a few settings and, hopefully, providing active cooling.

Overclocking a Raspberry Pi is deceptively simple. We edit the config.txt file found in the boot partition and, after a reboot, we see a performance boost, for free. We spent the time testing the limits of the Raspberry Pi 4 and the Compute Module 4, deploying multiple overclocks from 2.2 GHz to 2.3 GHz to give you the data that you need to overclock your Raspberry Pi 4 / Compute Module 4. 

Our tests involved the Raspberry Pi 4 4GB and 8GB, Compute Module 4 1GB and an 8GB Compute Module Lite connected to the official Compute Module 4 IO Board. For the Compute Module 4, we used its onboard eMMC flash storage as a boot device, and for the Raspberry Pi 4s and the Compute Module Lite we used a microSD card (see best Raspberry Pi microSD cards) as our boot medium. All test machines ran the latest version of Raspberry Pi OS, updated with the latest software. Our stress tests were conducted using Stressberry which runs the CPU at 100% to generate temperature data and to ensure that the CPU can cope with heavy tasks at those speeds.

Before we conducted the test we needed to prepare our devices for use.

Flashing an Image: Raspberry Pi 4 and the Compute Module 4 Lite 

The Compute Module 4 Lite has no eMMC storage so we will need to write a micro SD card using the Raspberry Pi Imager. This is exactly the same process as if we were to write a card for other models of Raspberry Pi. See how to set up a Raspberry Pi for the first time or how to set up a headless Raspberry Pi for details. If you already have a microSD card set up, make sure you update your operating system by entering: 

sudo apt update 
sudo apt upgrade

You may also want to update your firmware to the latest version by entering

Sudo rpi-update

Flashing an Image on Compute Module 4 with eMMC Storage 

There are 32 variants of the Compute Module 4, but at the most basic level there are two key models. The Compute Module 4 and the Lite version. The Compute Module 4 has onboard eMMC flash storage, while the lite version omits any form of flash storage.

For the Compute Module 4, to flash the onboard storage we need to download the contents of a Git repository to a machine running Linux, or another Raspberry Pi.

1.  Open a terminal and clone the repository.

$ git clone --depth=1 https://github.com/raspberrypi/usbboot

2.  Change directory to enter the download repository.

$ cd usbboot

3.  Install libusb, a developer tool to enable USB access in scripts. 

$ sudo apt install libusb-1.0-0-dev

4.  We then need to make the rpiboot application from the downloaded files. 

$ make

5.  Connect the Compute Module 4 to the Compute Module 4 io Board. Connect a micro USB cable to micro USB port and then connect the other end to a USB port on your Linux computer.

6. Locate pins J2 and fit a jumper to disable eMMC boot. If you do not have a jumper, then a female to female connector can be used. This will prevent the Compute Module 4 from booting and will instead enable us to mount the Compute module 4 as if it were a USB flash drive. 

(Image credit: Tom’s Hardware)

In the Terminal, run the rpiboot command to mount the Compute Module. 

$ sudo ./rpiboot

After a few moments the drive will appear and be accessible.

7.  On your Linux computer, navigate to https://www.raspberrypi.org/downloads/ to download Raspberry Pi Imager. Install the application.

8. Open Raspberry Pi Imager and select Raspberry Pi OS (32-bit).

(Image credit: Tom’s Hardware)

9.  Click on CHOOSE SD CARD and select your Compute Module 4.

10. Click on Write, to flash the OS to the eMMC storage.

With the OS written to the Compute Module 4, we can now close Raspberry Pi Imager. 

Before we can use the Compute Module 4, we need to make a change to a config file in order to use the USB ports of the IO Board which are disabled by default.

1. Open the File Manager, locate the Boot partition of the Compute Module 4, or the micro SD card and open the config.txt file with a text editor.

2. At the bottom of the file add the following lines to enable the USB ports. The first line is a comment to remind ourselves as to the function of the command underneath it. 

#Enable USB ports on IO Board
dtoverlay=dwc2,dr_mode=host

An optional step is to enable the use of an external antenna. The Compute Module 4 has a built in Wi-Fi antenna and a ufl connector for an official external antenna. To use this we need to add a further line to the config file, config.txt.

At the bottom of config.txt add these lines to enable the external antenna.

#Enable external antenna
dtparam=ant2

Eject the boot and root partitions from your Linux machine before removing the USB cable / micro SD card.

Booting the Compute Module 4 

If you are using the Compute Module 4, remove the micro USB cable and the jumper from J2 of the IO Board. If you are using the Compute Module 4 Lite, insert the micro SD card.

For both versions, connect your keyboard, mouse, HDMI and external antenna (if you have chosen to use an external antenna). Then plug into power, which will trigger the Compute Module 4 to boot to the Raspberry Pi OS desktop.

Overclocking the Raspberry Pi 4 and the Compute Module 4 

(Image credit: Tom’s Hardware)

The stock speed of the Raspberry Pi 4 and the Compute Module 4 is 1.5 GHz. As with any model of Raspberry Pi, they can be overclocked to provide a free performance boost.  

(Image credit: Tom’s Hardware)

Before we even start the overclock process we will need to ensure that there is adequate cooling. For passive cooling you will need much more than some simple stick-on heatsinks. We chose to cool the Compute Module 4 with a Pimoroni Fan Shim, hacked to sit above the module and controlled from the GPIO. We also wrote a simple Python script to run on boot which started the fan at full speed. If you have access to, or a wish to use PC fans then the Compute Module 4 IO Board has a fan header at J17 which can be used with 12V PC fans. 

(Image credit: Tom’s Hardware)

To cool our Raspberry Pi 4, we used a 52Pi IceTower, an extreme cooling solution which looks and acts as heatsink and fan found inside a PC case. This cooling solution runs directly from the 5V pins of the GPIO. 

(Image credit: Tom’s Hardware)

To overclock a Raspberry Pi we need to edit the config.txt file, the same file that we earlier edited to add USB and external antenna support.

1. Open the config.txt file for editing in a terminal window on your Pi. 

sudo nano /boot/config.txt

2. Using the keyboard, move to the bottom of the file and add a comment line to identify the overclock instructions.

#Overclock Instructions

3. Set the CPU speed by adding the arm_freq option and entering the desired speed in MHz. In this example we set the overclock to 2275MHz. Changing the value will set the maximum CPU speed, so use 2200, 2250 and 2275 etc. 

arm_freq=2275

4. Overclock the GPU to 750MHz by adding this line. 

gpu_freq=750

5. Overclocking requires extra voltage for the CPU. Add the over_voltage value of 8 to provide 1.4V of extra voltage.

over_voltage=8

6. Press CTRL + X and then press Y to save and exit the file.

7. Reboot the Raspberry Pi and once the reboot is complete open a Terminal and use the vcgencmd to show the current ARM CPU speed.

(Image credit: Tom’s Hardware)
vcgencmd measure_clock arm

If your Raspberry Pi does not boot, it means that your particular CPU cannot handle the clock speed you configured it for. Stick your microSD card in another computer or mount your Compute Module 4 on another computer so you can change the values in config.txt to a lower MHz.

Overclocking the Raspberry Pi 4 and Compute Module 4 to 2.3 GHz

Before we start, we need to make this very obvious. Overclocking to this level will invalidate your warranty. You break it, you bought it!

We found success with a Raspberry Pi 4 8GB and a Compute Module 4 Lite with 8GB RAM. This overclock did not work with our Compute Module 4 1GB or our Raspberry Pi 4 4GB and the maximum speed we achieved with those boards was 2275 MHz.

To overclock the Raspberry Pi 4 8GB and the Compute Module 4 to 2.3 GHz, we need to edit the config.txt file and most of the configuration is the same as before, except for the CPU speed, 2300 and an extra line which forces turbo mode frequencies even when the ARM cores are not busy. Using “force_turbo” will invalidate your warranty.

Here is our config for 2.3 GHz.

#Overclock
arm_freq=2300
gpu_freq=500
over_voltage=14
force_turbo=1

The Results: 2.3-GHz Raspberry Pi 4 

We ran four overclock tests for each Raspberry Pi 4 and Compute Module 4. Using 2200, 2250, 2275 and 2300 overclocks.

The Compute Module 4 and Raspberry Pi 4 4GB reached 2275 MHz and ran stable. Taking them to 2300 MHz and repeating our tests caused them to lock up and crash during the cooldown period of the Stressberry test. 

The same test on the 8GB Lite module and our 8GB Pi 4 ran perfectly on multiple occasions. Could RAM play a key factor in overclocking performance? Is there something about 8GB Raspberry Pi which makes them better for overclocking? We asked that question to Eben Upton, Chief Executive of Raspberry Pi Trading

“I think this is mostly a silicon lottery effect, possibly influenced by long-term process trends.

There certainly are boards out there that can do crazy speeds, and we’ve been very conservative in how hard we push (Broadcom) 2711: it’s much more important to us that the product runs reliably at 1.5 GHz than that people can get good overclocks,” he said. “We’ve done a bit of attention-to-detail work on the power planes and decoupling on recent boards…but I would expect this to have a relatively marginal effect.”

apple’s-m1-based-macs-do-not-support-external-graphics-cards

Apple’s M1-Based Macs Do Not Support External Graphics Cards



(Image credit: Apple)

We expected Apple’s Macintosh computers running the company’s own system-on-chips (SoCs) to be considerably different compared to systems powered by Intel processors due to all-new hardware and a revamped software stack. It appears that one of the changes for the Apple M1-based Macs unveiled this week is that the company dropped external GPU support (at least for now). 

When Apple announced its latest Apple Silicon-based Macs several months ago, the company officially revealed to software developers that they would only support its own ‘Apple family GPUs.’  More recently, the firm removed the Blackmagic eGPU chassis from the list of accessories compatible with the latest M1-based Mac mini, MacBook Air, and MacBook Pro. AppleInsider now claims that the new systems will rely solely on integrated Apple GPUs and will not support any external graphics cards. 

The website doesn’t reveal whether the information comes directly from Apple or sources close to the company. It also doesn’t disclose whether Apple will drop support for external GPUs or all third-party GPUs in general, which might have some important ramifications.  

On a high level, eGFX technology allows you to connect a graphics card to a PC using a Thunderbolt 3 interface and a special chassis. Still, there are very specific hardware and software requirements to support an external GPU. First up, the system needs a Thunderbolt 3 or a Thunderbolt 4 port with a firmware version that can handle eGFX. Secondly, the system has to support external graphics by its UEFI (i.e., plug-n-play or similar technology and switchable graphics protocols). Thirdly, the GPU drivers have to support eGFX as well as a particular operating system. If one of these components is missing, eGFX simply won’t work. 

It is unclear what exactly Apple’s new PCs are missing and whether this lack of support is temporary, or if there are no plans to support eGFX technologies on the latest 13.3-inch notebooks and the entry-level desktop in general.  

Supporting eGFX on certain systems may be complicated because of SoC limitations and other reasons. Meanwhile, Apple started to support external GPUs in general later than competing PC makers from the Windows camp anyway, meaning that it doesn’t consider this technology a priority. Perhaps Apple’s more advanced desktops and laptops will regain eGFX support. 

It remains to be seen if the company will support third-party GPUs on its Arm-powered Macs at large or will rely solely on its own graphics solutions. Industry-standard GPUs are important to many professionals with iMac, iMac Pro, and Mac Pro desktops, so dropping support might be a bad idea.