

You don’t need to format the drive if you’re writing from an image.
Install Balena Etcher (also available in Gnome Software), select the ISO you want to write from, and the target USB drive, write it, then it’s usable.


You don’t need to format the drive if you’re writing from an image.
Install Balena Etcher (also available in Gnome Software), select the ISO you want to write from, and the target USB drive, write it, then it’s usable.


All of those explanations, but you’re not even saying WHY it’s an alternative, or to WHAT


God damn. That’s a 2m video stretched WAY the fuck out. He’s constantly repeating the same couple points over and over and over. Not even phrasing it differently even.


Yeah, see my edit. This is a Pipewire session thing. Each user needs a unique Pipewire session to do audio. Video has nothing to do with Pipewire.


Check the groups the working user is included in, and make sure the non-working user is in those same groups. See if anything there.
Edit: Oh, you know what. I think this is probably Pipewire not starting for multiple users when multiple are logged in. On the non-working user, you need to start a unique Pipewire session for that user, because the other working user’s session can’t be shared by default.
Alpine is very specific in its use-case. Unless you know the exact package set you need to work with, it’s not suitable for general purpose use. It doesn’t even include glibc, for example 🤣 It’s meant to BARE as possible with a small footprint.
I’m not sure your rationale for picking Alipine for this use-case, but you might want to consider a more fleshed out distro for a NAS. Alpine is the BARE MINIMUM of an OS, meaning a lot of helpers that exist on other distros are not there for things like setting your power settings and link negotiations in certain cases. Sure the NIC driver is there, but all the nice tweaks for that specific module that exist in, say, Fedora Server aren’t going to be there, leading to this issue.
I’d honestly just throw FreeNAS, TrueNAS, or Unraid on this box and be done with it. They’ll have all the power settings and tweaks meant for a NAS in place, and then you won’t need to spend time hunting stuff like this down.
It could be related to power saving settings and/or your power profile.
Some Q’s:
I saw you tried to set power for the interface itself, but if this is a power issue, you probably want to disable power savings on your PCIe interfaces. Easiest way to do this is probably installing powertop, and navigating over to the ‘tunables’ menu, and disabling power management for those interfaces, just to test and see if it fixes it.


Resolution alone isn’t the only factor. It’s a larger display, requiring more power, which is either a PC/PD issue, or a battery issue. The point is that the power draw has to come from somewhere, and nothing this is the same platform as an iPhone (essentially), there’s going to be a trade-off somewhere.
As you noted they’ve reduced the refresh rate, which makes a big impact, but I don’t think it stops there.
The original platform has apps that are optimized for that platform, and now you’re throwing a different OS at it which has more expansive use of resources: CPU, memory, GPU, and power.
We’ll have to see how they have made paths through MacOS to account the platform specifically, but I’m betting there are several drawbacks. This was the main complaint of how they dealt with those insanely expensive Mac Pro with M-class chips when they first came out, but in the inverse. High power draw, heat issues…etc.


Mobile chip power is insane AT THAT SCALE though. That’s the key differentiation here. So if you’re running a larger format display with a higher resolution, cut that by quite a bit. Also cut it if you’re running desktop apps that aren’t optimized for mobile, and if this is intended to run MacOS instead of iOS, the mobile optimistic memory scheduling is out the window. I’ll have to see it to say for sure, but I’m guessing the performance for average desktop apps is going to be pretty, but that’s kind of the price point.
This is Apple’s scoop up of the ChromeOS segment.


Repair friendly means CHEAP components repair, which Apple just does not do.
As an example, in a machine like this if your WiFi module tanks…that’s a full logic board replacement. Might as well buy a new one.
According to this, Apple is basically making an insurance vertical as part of their business, and they are pricing repairs to be exactly 1/3 the retail cost of the machine for pretty much everything except screens.
This is pretty scam my when you consider their past of quoting customers for repairs that are above and beyond the scope of the actual hardware failures, and what maximizes profits for their AppleCare and RMA process. There are dozens of breakdowns in this, so I won’t write a novel, but it’s very obvious they’ve baked in the costs to make it more cost-effective to just keep buying new units as a replacement in the face of simple hardware failures.


The failure rates of these will be the determining factor. The components inside are cheap, all soldered on, and will not be repairable at all (waiting on the iFixIt score).
Its pretty much just their phone platform with a big screen and keyboard, so maybe it’ll be okay. It’s not built like a phone though, so I’m expecting some interesting testing outcomes. It’s either going to be cheap enough that they have a new planned obsolescence hit on their hands, or people are going to be pissed at it sucking so hard.
Fedora or Debian, but it depends on what you’re going to be using it for.
Maybe you want a NAS OS instead? Maybe a media system like Open Filevault? If just runnings VMs and Containers, maybe something geared towards that.
Fedora does have some nice preconfigured stuff like Cockpit and several helper automations by default. Yes, they can be installed on Debian, but it’s extra steps.
Your hardware is really the defining factor at the lower levels, but then whether you have encrypted partitions is the barrier at the OS level.
Understanding where your problem lies needs to be known, so more symptoms or logs would be helpful.


Detected means the system sees them. Mounted means the partitions in those drives have been mapped to a local area on your filesystem where you can access them.
Depending on your desktop and settings, this is usually an automatic thing for well known filesystems like NTFS or FAT, but not so with encrypted volumes because there are extra steps to mounting them during boot (like a passphrase).
If they you had Bitlocker enabled in Windows, then they will not automount. So if in Gnome open up the ‘Disks’ app, or ‘Partition Manager’ in KDE, see if your dicks show up there, then click on the partition you want to mount and it should ask for your disk password to mount it.
Not that I’ve heard of this. This isn’t a compressed package in the same way a zip is, it’s an application package.


I assume you mean they aren’t mounted and readily showing up for access. Are they encrypted?
Open whatever disk manager you like and see if there drives are detected, but just not mounted. Usually the case if they are encrypted.


Good soundtrack, at least in the first one.
That zip file contains an rpm package that has the PPD files. You’ll need to be on an RPM-based distro to install it as-is, or use a tool to unpack it.
What distro are you running?
Ubuntu 25+ has specific optimizations for these chips, but last I heard performance was pretty weak due to Qualcomm refusing to open their drivers and optimizations.
Fedora 44 also has some specific optimizations for these chips.