Microsoft Azure Adds Ampere Altra Arm CPUs
servethehome.com
servethehome.com
It's not consistently available over all Internet-facing Azure services, even including such high-profile services as Azure App Service (f.k.a. Azure Websites), which is a very surprising omission today.
It's been a highly-upvoted ask on UserVoice for over 7 years: https://docs.microsoft.com/en-us/answers/questions/676236/ip...
That arguably makes it just as good as not having it :-)
I just think it's a shame IBM doesn't offer POWER10 and Oracle doesn't offer SPARC boxes (even though I don't think SPARC would be competitive these days).
I have been developing on Windows and deploying on whatever since two decades now.
The problem are the devices on people's desk running software bought several years ago with no reason for them to upgrade.
Those are also going away sooner rather than later, as more and more software is offered as web-based experiences with ties to remote-running servers.
Which is exactly the domain I was busy with when I took some time off out of Web development.
You won't find much love for Web UIs in automation or laboratory devices, or stuff like DAWs.
As for the rest, we already have X Windows, VNC, RDP, Citrix, WebRTC streaming,....
Kind of, if you can handle the abysmal price.
Just got a Mac Studio (M1 Max), and it’s a pretty smooth beast.
If I'm being completely honest: unless your opposition to Apple machines is purely political or whatever (which is whatever, do your thing), your best bet is probably just to buy an M1 Mac Mini, install Asahi Linux on it, and run it headless. You can get some aftermarket rackmount kits that can bundle 1-2 Minis, even, if you actually have racks. The performance/watt/$-spent is simply much better all around due to the massive economies of scale and consumer focus and it's a very modern ARMv8.something machine. All of the competitors are simply much slower in raw performance, have buggier hardware/firmware (often both), and run much more expensive when that isn't the case. Hell, even if you bought the Mac Studio and just ran Linux on it, it would probably still be reasonably price competitive, all things considered, even with like half the chip currently non-functional (GPU, NPU, etc). The hardware really is pretty good.
At this point I'm waiting for their ARMv9 chips to start rolling out before jumping on the Linux train. Maybe they'll do a Mac Studio refresh in a year or two from now...
I agree. Especially on residential power it may be worth looking at the power consumption.
The base M1 mini starts to become really cheap used too.
Having fast chips is nice, but I really want to have an ARM platform that I can just throw any Linux, BSD, Windows, etc image at.
On the plus side, they're pretty cheap.
[0] https://developer.nvidia.com/buy-jetson
[1] https://www.reddit.com/r/linux/comments/b2po26/nvidia_jetson...
When I was looking around, there was some stuff in the $500 to $2000 range:
Nvidia's usual Jetson/Tegra lineup
- sometimes has decent CPUs
- Good luck running anything other than Nvidia's slowly updated Kernel with blobs all over. Support drops real fast for older boards, leaving one stuck on old kernels (Jetson Nano and its upstream family was "EOL'd" in terms of kernel upgrades a while ago, even though Nvidia will still gladly take your money for a new Jetson Nano). - Has a lot of Nvidia stuff attached, so you do get a GPU and a PCIe slot.
NXP LayerScape
- lots of CPU cores, but not great ones
- Claims 2nd highest level of ARM Systemready, so it may work with mainline kernels?
- Has a lot of networking stuff attached, since this seems to be the successor to generations of PPC networking chips.
Apple
- IMO, you already know the pros and cons, and will have already decided to purchase a Mac M1 or not by now.
- Popular vendor with a tendency to not make too many different variants, so some are trying to mainline device support in the Linux kernel (Asahi linux).
Qualcomm's developer platform for WoA
- Somewhat limited in specs and afaik, no mainline kernel support of note.
There are others in this range, such as Amazon's Annapurna Labs, Marvell's various SoCs, Broadcomm, Ampere, etc. IMO, none of them really target consumers or workstations. Some (Marvell, Broadcomm) treat simple public datasheets and documentation as a sin - Marvell's takedowns of fmr XScale documentation in particular. Even Nvidia isn't quite this prudish with their documentation, though they do hold back a bit vs the big x86 giants. Annapurna is found all over the place (Qnap NAS & Mikrotik routers are two places I've been surprised to find them), so there may be reclaimed consumer hardware, but Amazon is similarly stingy with documentation.
Ultimately, I don't feel it is really the year of the ARM workstation quite yet.
Note that the Jetson Nano is supported pretty well by Fedora with a fully upstream kernel. This includes GPU acceleration through Nouveau, without reclocking catches.
And just before deprecating support for it entirely (won't get BSP releases beyond JetPack 4.x), they gave it u-boot on SPI with the UEFI module, which wasn't used at all before.
https://nullr0ute.com/2020/11/installing-fedora-on-the-nvidi...
The new BSP release that is released tomorrow in public preview is Xavier onwards only, and sets the baseline to Linux 5.10, with UEFI across the board.
The older BSP release that supports Tegra X1 onwards, including the Jetson Nano, will continue getting security updates for years to come. Just don't expect new features anymore on the NVIDIA binary UM driver stack.
> slowly updated Kernel with blobs all over
It's a heavily diverged kernel tree, but it's all GPLv2, including the full GPU kernel-mode driver (https://nv-tegra.nvidia.com/r/gitweb?p=linux-nvgpu.git;a=sum...) for those. (there's no binary kernel modules present at all on the platform)
Firmware, like everyone else, and userspace is where you have the proprietary bits.
> Firmware, like everyone else, and userspace is where you have the proprietary bits.
My experience with this, is moving away from the Nvidia kernel isn't practically feasible. Userspace may be a refuge, but even trying to upgrade away from the Nvidia/Ubuntu 18.04 userspace was always going to bring up general incompatibilities and small problems. The long awaited 5.10 update targets Ubuntu 20.04, just as 22.04 is progressing through beta. Backporting PCIe device drivers and modules was painful enough that I eventually gave up on my jetson adventures.
The nullr0ute URL even notes: > it’s not perfect yet and we’re actively working to fix and improve the support for the Jetson Nano [] https://nullr0ute.com/2020/11/installing-fedora-on-the-nvidi...
In my experience, perfect was too lofty of a goal for running a mainline kernel on a Jetson/Tegra. Similar to these users as well. [] https://lists.fedorahosted.org/archives/list/arm@lists.fedor...
[] https://forums.developer.nvidia.com/t/installing-centos-on-j...
In the end, I spent enough time trying to get the platform to work normally, that I realized I was wasting time when I could just get an x86 board for similar cost or get a Raspberry Pi CM4, and quit trying to grow the Jetson Nano out of its embedded system roots.
Nvidia needs to step it up, big time. Jetson Xavier users are finally going to get a beta for Cuda 11, when x86 and SBSA arm users had Nvidia's official Cuda 11 for almost 2 years now.
Oh yup... for just 4.14 (from the NV 4.9 kernel), took so much work to keep up...
I eventually had a project to decouple nvgpu so that it could be used with a regular mainline kernel as a DKMS module... but I didn't get around to it. The situation on that front will become better in the future, but it's taking way too long.
> Userspace may be a refuge, but even trying to upgrade away from the Nvidia/Ubuntu 18.04 userspace was always going to bring up general incompatibilities and small problems.
CUDA 10.2 doesn't support Ubuntu 20.04 so hello problems on that front. Enough said...
> Nvidia needs to step it up, big time. Jetson Xavier users are finally going to get a beta for Cuda 11, when x86 and SBSA arm users had Nvidia's official Cuda 11 for almost 2 years now.
Yes... the thing is that Jetson has been put exclusively on an LTS lifecycle and that posed a bunch of problems. We have promises that it won't happen again in the future, with CUDA being decoupled from L4T shipping sometime towards the end of the year.
And the beta shipping tomorrow is for CUDA 11.4, not the latest 11.6.
Also as a side note if you're on Xavier and trying to OTA update to the BSP released tomorrow, just don't, that flow is just not supported. Full reinstall required between major BSP releases.
The we'd have a 7-A alliteration.