2012 Mac Mini Linux
Melia Hazinski
But I would like to use the AKAI APCmini MK2 to assign the pads to specific MIDI instruments on the Black Pearl drum set. So I could use the pads to play a drum, which would then be recorded in the Ardor. I now have the AKAI APCmini MK2 running, but the pads are mixed up with the Black Pearl instruments. The pads on which I have the instruments do not light up either. Here I would also have the pads light up in colors that I chose so that I can quickly see which pads have certain instruments on them.
given that Mark has installed GQRX with no problems from the default repositories, the problem may be with the package that you downloaded and installed. For Mint 20, and Ubuntu 20.04, the repository version of GQRX is 2.12. The packaged version of libairspyhf.so. offers its library at /usr/lib/x86_64-linux-gnu/libairspyhf.so.1 (see ). The location given for the missing library is where, by usual default, locally compiled libraries would be placed. The irony is that libairspyhf is not necessary to run the Airspy mini.
On upgrading to Lubuntu 20.04LTS , kernel version 5 was in use from the start. I installed gqrx and gnuradio, using the repository versions supplied with 20.04, but my Airspys still weren't recognised. It was then that I found the advice to install the missing libraries, libairspy and libairspyhf. The gqrx version I'm using is 2.12.1-1build2 and I don't remember it being updated since I upgraded to Lubuntu 20.04 from 19.10.
Update: I now have RL running on a mini server 2010 model and the 2011 desktop model that I mentioned, right on the metal, no underlying OS or virtualization needed. Just like I wanted. Next will be the 2011 server box.
Sounds promising, I might even be able to the external Thunderbolt HDD enclosure working, that would be neat. Of course actual driver support to mount the drives, as RAID even, is an unknown at this point
I just got done installing RL 8.5 on a new 2012 mini that I got hold of, a 2.6 GHz i7 model with 16 gigs of memory and 1 TB hard disk. I noticed that Thunderbolt shows up in the Devices under Gnome as shown:
This thread was helpful to get a Mac mini (2012) running Rocky. When creating your installation media on a USB stick using a Macintosh running MacOS, do not forget to convert the downloaded ISO image to IMG using hdiutil.
Then write the resulting .dmg file with dd to your USB stick. Note that the first file path is the OUTPUT file, the second is the path to the downloaded installation image. This extra step saved me from needing to find a DVD drive and media.
My approach consisted of writing a minimal install ISO to a DVD, then booting from a USB optical drive. With 2012 and earlier models, there is no supported version of macOS so you might as well just install Linux on the entire disk and not bother with dual boot. I have done that successfully on a number of 2010 to 2012 mac minis as well as a 2012 MacBook Pro.
As mentioned above, this works for converting a Mac to Linux only, not for dual-boot.On the positive side, my old 2012 Mac mini that had gotten pretty much unsupportable with MacOS is now a perfectly modern, fast, well-behaved Linux machine with this method!
I have done this procedure on a good number of 2012 model quad core i7 minis now. The price of these boxes on ebay is such that you can get a pair of them for what a Raspberry Pi 4 costs nowadays. I have a stack of them now that I have running RL for a Plex server, a Wordpress web server, a Guacamole server, and file servers, along with one running as a Security Onion manager node. I have plans for another one or two of them sitting around such as an email server.
Following these instructions. I have identified my card as BCM4321, which from the tables I read I can use the b43 driver/module (is a driver really just a module?) which is already in the kernel. I ran lsmod and sure enough can see that b43 is loaded. Checked iwconfig and can see wlan0 IEE 802 ect.
If I run ip link set wlan0 up (which i'm guessing turns on the card/wifi?) I'm notified about the need for some firmware. Ok so reading the instructions from the above website I need to get this firmware which I am pretty sure would solve the aforementioned issue, but my main problem is how do I get the firmware without physically connecting the mac to router via ethernet.
I have a laptop that I'm currently using with W7 and F16 on and a pendrive which currently has the arch installation media on it, I am hoping i can stick the firmware on a pendrive and load from there if so how?
Whilst writing this I have thought that I should just be able to wget the tarballs from here, put those on the pendrive and then try loading transferring them into arch, will still ask this question in case of failure :-)
That is exactly what to do. Unfortunately, Broadcom does not provide distribution licensing for the firmware, so you have to download their full proprietary driver from their website, then extract the firmware from it. This can be done on any system. There are directions on the site you linked about how to do this. At one point, it has you download a different driver version depending on what kernel version you have. Archlinux systems usually have the latest kernel, but if you just installed from an installation medium, it may be older; do uname -a on the Arch system to find out what kernel version you have. Once you have it, place it in the /lib/firmware/ directory of your Arch system.
If you haven't heard of Asahi, it's a Linux distribution based on Arch Linux that aims to bring a polished Linux experience on Apple Silicon Macs (all the current M1 Macs, and any new Apple Silicon Macs that come in the future).
Full support of all M1 features (most notably, the GPU) isn't complete, and it's nowhere near a final release, but I thought it would be fun to try it out, and see how well Linux (at least one distro) runs on Apple's ARM64 architecture.
The instructions in the blog post give a curl sudo bash style instruction to run curl sh. Since I'm okay with completely nuking this Mac back to factory defaults if things go wrong, I'll take them up on the offer.
At some point the Asahi community might also offer an App download or USB-stick-based installer too, but right now the easiest way to get all the partitions in order is to run a script from their site. The alx.sh URL just loads in an installer from and some data files to kick off the installation process.
The prompts are fairly straightforward, though you should probably not attempt installing Asahi (it's alpha after all!) unless you're familiar with at least the basics of the command line and Linux. Some of the options, if chosen without understanding, could lead to a bit of a degraded experience if you choose poorly, so don't just dive in on your main or only Mac if you rely on it day to day! If you want to get more comfortable with the process, I highly recommend reading Asahi's Introduction to Apple Silicon.
It's important to wait for the Mac to shut down completely. Then you need to hold down the power button continuously until it boots into recoveryOS, a special lightweight system that comes on M1 Macs that allows you to choose boot OSes other than the primary macOS installation:
After selecting Asahi Linux, you're prompted for your macOS administrator password, then the Asahi installer completes its installation process from recoveryOS. As part of this process, you have to enter your administrator password again to set the computer's boot policy to 'permissive' mode, to allow non-macOS operating systems to run.
I added my user to the docker group, logged out and logged back in, then I could run any Docker images just like I would on my Mac. I installed Docker Compose with pip3 install docker-compose, and added export PATH="$HOME/.local/bin:$PATH" to my .zshrc file so docker-compose would work.
And I also ran two processes involved in setting up my jeffgeerling-com website codebase locally, composer installing all my site's dependencies over a shared volume, and installing Drupal, and both are markedly faster under Docker in Asahi:
So you can't draw the conclusion that 'Asahi Linux is faster than macOS' just based on Docker results. Michael Larabel over on Phoronix did a lot more benchmarking, and found that there are a number of natively-compiled apps that do run faster on Asahi, on the exact same hardware.
But because Asahi doesn't have some optimizations, like boosting the efficiency CPU core clocks, nor does it have drivers for the GPU (so no Vulkan, Metal, or OpenGL support), there's still a ways to go before it can reach full parity for benchmarks. But progress is being made, and rapidly!
As it turns out, a PCIe flag was setting the link speed for the network adapter to x1 instead of x4, which severely crippled the NIC, limiting it to about 1.5 Gbps over a 2.5, 5, or 10Gbase-T connection.
For the former, it can be impossible to get the software to compile on an ARM64 system like the M1. In the past, the excuse for not supporting the ARM64 platform has been a lack of server-grade hardware.
More and more, that's a bad take: above the hobbyist-tier Raspberry Pi, Ampere and AWS have already paved a path towards data-center-scale ARM, Solid-Run has shown some (pricey, but adequate) mid-range servers and workstation boards, and now Apple has put out not just the base-level M1, but the midrange-workstation-grade M1 Max and Ultra chips, which can battle with higher-end Intel and AMD chips (though not yet on the highest performance servers).
In the next 5 years, as used prices for the original M1 Mac mini go sub-$500... this machine would be perfect to run as a silent, efficient homelab server. Heck, it could run a lot of SMB applications via Asahi or any other compatible Linux distribution.
Hi Jeff.
Is this your @Jeff_Geerling account in Telegram?
I think the scammers are pretending to be you.
=rU06vpstBg0
below this video i got a message from "Text me on Telegram @Jeff_Geerling".
Sincerely.