Review of Linux on Minisforum V3 AMD Ryzen Tablet
mudkip.me
mudkip.me
Though it's not mentioned in the review, good standby time is also important. Not only is it irritating to find one's tablet/laptop dead when pulled out for use, the sleeping battery drain typical of x86 laptops since the advent of "modern" standby runs through your battery's cycles much more quickly than necessary.
... I won't hold my breath for Qualcomm to be bringer of SystemReady. I might end up too blue.
2024 Microsoft Surface?
So Linux-on-ARM-Surface had a lot of magical thinking involving using device tree etc. caused by people hitting the wall with broken UEFI implementation.
> ACPI can be used for Armv8 and Armv9 systems designed to follow the BSA (Arm Base System Architecture) [0] and BBR (Arm Base Boot Requirements) [1] specifications. Both BSA and BBR are publicly accessible documents. Arm Servers, in addition to being BSA compliant, comply with a set of rules defined in SBSA (Server Base System Architecture).
https://docs.kernel.org/arch/arm64/arm-acpi.html
There's people in the ecosystem doing good things, but wow been a decade now of ARM ecosystem forever being ever-so-close to doing the right thing & learning from the ways x86 is such an open interoperable healthy ecosystem (Intel wifi chips aside; even the "PCIe" ones no longer work in any other systems/aren't spec complaint).
So here we are a decade later & still ARM is good only in flagship (and 25% of mid-ranged) cell phones running vendor sdks and now some hyperscaler's servers, but literally no one else can use decent modern arm stuff without a bunch of fuss. What's the quote? Chips without drivers are just expensive sand?
It really blows my mind that this is the case. If Intel or AMD doesn't want their architecture to be discarded they need to fix this. They should be on full alert working on this problem, yet it seems like nobody even cares. Maybe they deserve the defeat that is coming, though I'd much prefer they learn.
Apple owns the stack and iterates slowly.
Most laptops change to some of their chips (wifi, graphics, etc) every year. But it can easily take a couple of years of experience working with a shop and writing drivers for it to fix every power usage bug.
For many years (!!) Microsoft actually kept the same wireless chipset in their Surface machines. Was it the latest and greatest? No, but it worked!
Then or course you have software. For years Firefox had a bug where if any open tab has GPU accelerated content, it would prevent the entire machine from going to sleep.
If Microsoft clamps down on that sort of behavior it'll break someone's software (complaints about laptops going to sleep fall into 1 of 2 camps, it happens too often or it doesn't happen enough !)
Integrators here are really on the hook for validating their configuration and chasing down the appropriate vendor to fix it (be it Intel/AMD or, I dunno, Qualcomm).
The main impact is mild inconvenience: lugging and managing an external battery, babysitting battery when needed or plugging it more than less.
That sucks, but you can deal with it. There's little way to deal with the iPad having a restricted OS with no JIT/compiling/virtualization support, or the MacBook having no touch or pen support.
Another thing is when combined with good standby time, long battery life means the device will be more predictable and ready to use at any given point without leaving it plugged in all the time or having to remember to plug it in regularly. This isn't as important for a "daily driver" laptop that gets regular/constant use, but for tablets and 2-in-1's that serve more auxiliary purposes it's huge.
it's better now that everything does reasonable fast-charging, but this sets up a pretty simple inequality: T(using)/T(charging) <= rate(charging)/rate(using). In other words if I am inside for 15 minutes out of every 2 hours, I have 7 parts using to 1 part charging, so with ideal usage my charge rate needs to be 8x the use rate. if you have an 85W charge rate, that means your average power consumption needs to be under 85/8 = ~10.625W average system power. with the screen and everything included. And in practice an 85W charger does not charge at 85W into the battery - not just system power, but the delivery isn't 100% efficient to begin with (look at your charge rate in system report or with aldente/coconutbattery!), you might get 70W out of that 85W connection to begin with, and 60W goes into the battery after running the laptop.
of course in practice you can accept a little attrition over time, you just need enough excess capacity to last you the day even if it's depleted at the end, but x86 laptops aren't idling at sub-10W with max screen brightness (probably no 1000 nits screen either). that number might be 25W average system power (not just processor!) or more for x86. when you're running an IDE and the screen is all the way up you probably are pulling closer to 17-18 watts even on apple silicon (the "stats" utility is great for showing this, use combined modules on the menu bar). you pretty clearly are going to burn through a large chunk of that battery even with frequent top-ups.
the better argument is "why don't you just pull over an extension cord" but that's the point, it's a quality-of-life change in the amount of charging you need to do and the degree to which you are tethered to the cord. Being able to go outside and run max screen brightness in mid-day while the dogs play in the yard, while running moderate workloads, and basically get like 6-8 hours of actual working usage plus any additional charge I can cram in while I'm inside for a break.
Then the corporate world has a solution for that for as long as computer existed: there's charging cables in basically every meeting room, every guest desk etc. In the olden days people would also keep around secundary, tertiary batteries to make the day. This would translate to a mobile battery in this days and age.
It's always nicer to not have to rely too heavily on these, but if your job is to be on the go all day long, you can't solely rely on your device battery either way.
Yeah, it's an engineering triumph and nice to have, but how important is it really?
That's why people moved to macs even as they didn't have the faster processors or better hardware. Specs were only numbers, and macs had attractive user features.
Now we're on the other side, where keynotes heavily rely on performance and technical prowess, and yes I'd totally see them come up with a mid-air floating iPad with absolutely no story behind it, the same way we have an m4 iPad Pro with no software to match it.
i would have to measure it but it probably is at least 15-20% a month which is moderately crazy compared to apple silicon. i've picked up a MBA and it instantly woke up and it had lost like 2% in the month or two since I replaced it.
None of these super cheap Chinese devices come with bios or firmware support or updates.
Minisforum, topton, qotom, beelink etc all have like maybe 1 or 2 bios updates AND EVEN THAT MANY IS RARE!
In the post spectre age, just look at amd security bulletins! Every few months there’s major bios/firmware/cpu vulnerabilities
And all the tech bloggers happily continue to showcase these devices (ltt, level1techs, sth) without any mention of the bios.
People recommend them as firewalls!
Edit: the best solution of course would be to have Coreboot.
Os level microcode updates only address a portion of these vulns, same for disabling smt. One unpatched vulnerability is too many let alone numerous. Not all require physical access either
Sadly there are too many low quality firmwares and even more below and below the floor, but that should be the theory.
Running with mitigations=off on a single user workstation ain't the end of the world, assuming you actually trust the code you're running (and if you don't trust it... why are you running it to begin with?).
Desktop OS design still assumes that programs can access user data on disk anyway, after all.
(This isn't an excuse to throw buggy / broken firmware into the world and not support it, which is also something these no-name vendors are happy to do)
I'd love to see what folks can do with power tuning on it. For good or for bad there's quite the rabbit hole of options. It'd be excellent to see a write-up from a pro on undervolting & tuning the performance profiles. Seeing what kind fo gains are possible.
There's efforts like Tuned (which is replacing the abysmally limited power-profiles-daemon in Fedora https://www.phoronix.com/news/Fedora-41-Goes-Tuned-PPD) which can get far. But there's so many different options! And it just doesn't feel like we have good shared working knowledge on what people do and especially on what the net results are.
- The screen panel QC seems very inconsistent. My unit got at least 2 dead pixels and over 6 bright pixels and a horizontal faint line across the screen, possibly caused by coating. I don't notice the dead pixels that much during the normal use due to the screen PPI being quite high (215 PPI), but it has way too many. (I'm trying to arrange a replacement with Minisforum, and JP store seems to have better support than the rest, so I'm keeping my fingers crossed.)
- The overall pen experience is quite good for writing. There's no perceivable lag in Krita as far as I can tell. I would still prefer Wacom Cintiq or iPad Pro for any serious drawing/painting session (the V3 pen pressure detection doesn't feel accurate enough to me).
- Everything mostly working out of the box as of kernel 6.6 (LTS). Sleep works great. The only thing that seems broken so far is the audio, which lacks any volume control. A lot of people suggest setting pipewire to use soft-mixer, but this caused the device to be muted during the machine startup. My workaround to this is to have a soft mixer Virtual Sink in pipewire and leave the audio device as-is.
- Tablet experience is suboptional. As mentioned in the article, if you happen to use more than one language, and have to use Fcitx5 for text input, then you're likely going to manually have to switch between Maliit and Fcitx5 every time you detach a keyboard (because Plasma only allow one Virtual Keyboard to be used).
- Also, Maliit lacks Ctrl/Alt/Cursor Keys, making this very unsuitable for an emergency console during travel/transit unless you also pack a keyboard, which adds thickness/weight. At this point, ThinkPad may have been a better choice. (I'm looking into possibly adding at least arrow keys to Maliit). (Also, Maliit Japanese keyboard uses a flick layout, which is broken because Maliit also uses a downward-drag gesture to dismiss itself... so you can't type any letters that require a downward flick)
- Battery life is, as mentioned in the article, 6 hours if I use powersave with power EPP, and around 4 hours if I use powersave with balance_performance EPP. Under Linux, battery drain during sleep is only around 1-2% over 8 hours (tested by charging to full before bed and leaving it unplug).
- The touchpad experience is fine. They're not amazing, but good enough to get the job done (there are certain angles that the touchpad sensor will stop registering touch events).
I have tried Waydroid, but the lack of full USB passthrough means I cannot login to my Google Account (due to Advanced Protection; and U2F doesn't work over HID forwarding) so I didn't test it further.
Ah it's a shame the Android-X86 project seems to have entered the abandon-ware territory. But you can look into another OSS project, BlissOS (their latest release bases on A13, still kernel 6.1.x), should be fine but not everything would work seemlessly I assume.
Edit: I just did a quick test, it seems to work pretty well. The volume control works, the camera works. So far, what doesn't seem to work is the fingerprint sensor and automatic orientation. The pen also seems to work.
I would be interested in hearing more - I was given to believe that most open source software was fine on any of the major architectures[0], and I've not heard of the 16k thing at all (is Asahi doing something nonstandard with memory pages?)
[0] Albeit with POWER somewhat weaker and SPARC mostly lost. But I thought ARM was in good shape, and MIPS has been weirdly resilient.
It's not really non-standard so much as it is new-standard or different-standard. Aarch64 officially supports 4K, 16K, and 64K pages. This flexibility in the aarch64 ABI means that most compilers already produce 64K aligned load segments for aarch64, so it's not a huge deal except for software that works at a low level and makes assumptions about mmap (for example).
The main software that's truly affected beyond just needing recompilation or tweaks is x86/x86-64 emulation software, since x86 is pretty tightly coupled to 4k pages.
As far as I can tell on mobile, the eu store has choice between German and English (UK?) keyboards. I don't see us as an option there however - which I would prefer if Norwegian isn't an option.
It works mostly fine, the nuphy keyboard has been a bit glitchy in humid environments and the battery doesn't hold a charge well but it manages. Having a keyboard+trackpad that does both wired and wireless is helpful when batteries run low and in dual boot scenarios.
Overall it feels like the author is not much aware of the higher range in the non Apple laptop class beside Surface.
Not a big problem per se, but article like that are always following a journey / story so it sort of should be mentioned.
Lenovo is, for some reason, a friggin joke when it comes to screen resolution and quality. Their consumer laptops tend to have better resolutions on-paper than their pro lines. Good luck finding anything better than 1080p on 12 inches...
I am perfectly aware of the non-Apple tablet market and I also think Surface is literally the best there is, as crappy MS is. Because no one else is even trying. The screen, aspect ratio, writing feel, builtin kickstand, ...
I am currently looking at a old 3rd gen lenovo x13 yoga or the Minisforum
While I personally would love the new Qualcomm Surface Pro, It's just not worth the price.
The Surface has always been in my eyes but from what I've seen the linux support is not as trivial with newer models.
Un-crippling of Apple Silicon iPads with Magic Keyboards, which have a superset of MacBook Air features, can happen via:
- Competition from Linux on Qualcomm Oryon tablets and 2-in-1
- New Apple leadership
- EU regulation to unlock dual-boot of other operating systems, like Linux/BSD
- Future jailbreakhttps://x.com/utmapp/status/1708907045314035986
Apple removed Hypervisor support from XNU in iOS 16.4. Here is a diff of iOS 16.3.1 and iOS 16.4. What this means is that even if a jailbreak/TrollStore comes out for iOS 16.6.1/17.0, there will not be UTM virtualization support, even on M1/M2 iPads.
MacOS app to save blobs: https://github.com/airsquared/blobsaverSadly it doesn’t seem that Apple are really interested in offering that.
I have used various Surface devices as well - and whilst they are fine with the keyboard attached, I’ve never loved the touch experience on Windows.