Are PC hardware companies driving technology into restricted closed ecosystems?
scottrlarson.com
scottrlarson.com
And back when PCs were far more open, good old IDE was always an option too.
Ever since BIOS became EFI, and flash ROMs started getting much bigger, it seems they've not been adding functionality but removing it slowly. The excuse is often "security" (against the user), and "legacy" (the oldest interfaces are also the most widely understood and stable).
That said, I'd stay away from the "prebuilt" manufacturers like Dell, Lenovo, HP, etc. if you want configurability. They've always had far less options in their BIOS than equivalent offerings from "enthusiast" or "gamer" oriented companies, although in the laptop space it's more difficult to do that.
In Silicon Valley you can go to Central Computer, though they aren't a tiny neighborhood shop by any means.
For laptops you might buy a Linux laptop.
I’m planning on using Central for a PC build in a month or so - definitely going to try to stretch my dollars.
Closest thing to that dream now is the framework laptop, which does have replaceable parts.
From other comments you can still sort of configure your own laptop.
What I was referring to was laptops already configured with Linux. So all the drivers are working, for example.
IDE is extremely slow, the connectors occupy a lot of precious space, and it hasn’t been used for modern drives for a very, very long time.
If anyone really needs IDE then they should get a USB IDE adapter for their use case.
Faulting motherboard manufacturers for removing ancient connectors is just grasping at straws.
But 2,5 kg versus 1,8 kg for a Lenovo with way better specs (I'm a traveller, weight is everything)... tough...
That's pretty much why phones never had a chance for this idea until very recently (and AFAIK, those recent examples are still not commercially available).
LG Gram laptop series. My LG Gram is the best laptop I ever had. It's lighter than Mac laptops.
Broadcom... that same hardware mfgr that makes your Debian install so much extra fun... (well, if you care about networking and integrated controllers...)
Across multiple laptops the Win 11 iso doesn't have Wifi drivers. And since we're in hell, you can't finish the setup process and actually use your computer without an Internet connection. Since then you'd be able to run an installer for the WiFi drivers.
Luckily you can use an Android phone to create an Internet bridge which will allow you to proceed.
However, The OEMs will automatically install CrapWare( we should start calling it this) even on vanilla Windows installs.
Compared to my last few CachyOS installs where everything just works out of the box. I don't need to provide my email address to use my computer.
Honestly as long as I can disable secureboot and install Linux it's ok. The moment I can't do this I'll be using legacy hardware ( or import a laptop from the EU where this is banned).
Edit: Hopefully the EU will make secure boot an option we can disable...
To be fair normal people don't care. My friend needed a new laptop, and since she's not too worried about the latest specs I just picked up what I could find at target for 300$. She is never going to reinstall. When Windows messes itself up in a year or two she'll probably just buy another 300$ laptop.
MS itself started doing that in Win10.
Anyone who is this passionate about computers should be buying a Professional license anyway, namely to get proper access to Group Policy and other things peasants won't care for.
Windows Professional has a lot of bullshit.Yesterday I lost 3 hours because, after a crash, Windows will run an "online checkdisk" and die before completion. Pulling the ethernet cable solved the issue. (this machine does not and will not have a wifi connection).
Because they closed the one where you use a fake email and get the password wrong.
Because they closed the one where you could fake not having an internet connection.
Because they removed the workflow to set up a local account. After they used dark patterns and misleading language to convince people to set up MS accounts instead.
It's a steaming load of shit.
Where Microsoft keeps your bit locker keys in your forced Microsoft account instead of letting you save them to USB drive.
Why not at least give the user choice? Maybe I want a simple password to decypt ? Maybe I don't care about encryption.
Then again, it's not my computer anymore. I'm sharing it with Microsoft.
They are even trying to push out local user accounts on their embedded / IoT version of their OS. The company I work for is evening having me port their product's hosted OS from Windows to Linux so they don't have to deal with their hostel user experience.
For servers purchased in bulk by hyperscalers, OpenCompute has done a great job of coordinating owner requirements for hardware and firmware delivered by ODMs and silicon vendors in the server supply chain. Founded by Facebook, OCP built on the pioneering ethos of whitebox servers at early Google Search.
To create a similar organization for clients, one would need to pool enough buying power to influence the supply chain for "PC" (x86/Arm) client devices. OCP bypassed Tier 1 OEMs and worked directly with Taiwan ODMs. This worked because hyperscalers could implement custom firmware and do their own support. The closest existing client vendor might be Framework, which has not yet managed open-source firmware. Plus Clevo (coreboot) OEMs. DMTF [2] might have some interest.
A possible baby step towards open clients would be an OCP reference design for a "privileged access workstation" to access security-sensitive administrator web consoles for hyperscaler clouds. Include both a discrete TPM and an open silicon root of trust (OCP MS Caliptra or Google OpenTitan are both open firmware). AMD OpenSIL has promised OSS client firmware by 2026 and AMD mini-PC boards are everywhere. The building blocks are present for a high-integrity reference client with open firmware, under control of the client-owning cloud customer.
With suitable licensing, anyone from Tier1 PC OEMs or small vendors could create custom derivatives of the OCP reference client IF they retain mandatory core properties like open firmware and open silicon RoT. We could intentionally reboot the accidentally-open IBM PC ecosystem, at least for the small niche of secure cloud administration. If the OCP reference client is successful, it could motivate a new client-focused org for open client hardware.
If AMD EPYC CPU policy is enforced by PSP firmware, then it can be negotiated by customers in a large enough, non-OEM, buying pool.
Plus, shipping a motherboard is much more difficult and expensive than a CPU.
Generally, the used market values standard form factor stuff more, so you'll frequently see people running a supermicro/etc server with a low end CPU wanting to upgrade to a better CPU from the same gen. So, pulling CPUs to sell to the enthusiasts in the used market from proprietary servers (HP, Dell, etc) when they go EOL has been pretty standard practice for at least a decade. There then ends up being a big pile of undesirable proprietary motherboards/chassis, and low-end CPUs for them. Both eventually get e-wasted, sometimes with the motherboards/chassis getting parted out.
The reasoning for this is pretty simple. Shipping an entire server is expensive - at least $100 CAD, sometimes more. Shipping a motherboard is cheap (sub-$30), and a CPU basically free (~$10). A proprietary server cannot be upgraded down the line (whereas a standard SSI-EEB chassis can have its motherboard swapped for a newer one), which decreases its value further. If someone has a standard chassis, they can buy any standard motherboard; to sell your proprietary one, you have to find someone with a proprietary chassis and a dead/missing motherboard, a very small market (supply vastly outpacing demand). For someone to want to buy your proprietary whole server, they'll have to be willing to accept that the chassis is junk whenever they want to upgrade past its generation of hardware, which is a relatively small market. Resale value in a few will also be terrible, because no one wants old hardware they can't upgrade. The market has a pretty hard cap on value for old hardware. All of this put together means that proprietary whole servers are worth (maximum_price_for_used_server * proprietary_undesirability_multiplier) - (shipping_cost), while a standard motherboard is worth (maximum_price_for_used_server) - (shipping_cost) and an unlocked CPU is worth (maximum_price_for_used_cpu) - (shipping_cost). It can sometimes be the case that selling an unlocked CPU from a proprietary server nets more money to the seller than selling the entire server, depending on era/brand/specific CPU.
The locking is handled on-chip, it's permanent, and it leaves the CPU working only on the OEMs motherboard/BIOS. This poisons the used parts market. But worse, these systems are always just one BIOS update away from not booting the fused CPUs anymore (e.g. signing the firmware update with new keys).
AMD included this in their CPUs because large OEMs like Lenovo and Dell asked for it. There's no extra security being offered by this feature, despite the OEMs throwing the word around every time to cover up it's only securing profit.
This sounds like more of the same, a kind of uncaring that shades into hostility.
I think it's more than "uncaring" - since they just shifted the pinout 3 pins over from standard ATX, got rid of the 3.3V and added another 2 5V lines: https://www.vogons.org/viewtopic.php?t=59959
More than just a valid choice, in the long run even 5V is going to be dropped. Intel's ATX12VO standard has only 12V coming from the power supply, all other voltages are generated on the motherboard when necessary.
For what it's worth, I'm not sure the consumer is hurt too bad either: Because of their sheer scale, aftermarket Dell parts and clone parts are extremely cheap. Any Dell part number turns ip tons off off-brand replacements on Amazon and eBay.
The biggest downside to Dell's approach is e-waste. When they change a design, otherwise serviceable hardware isn't useful when working with newer models. Speaking of those wonderful old E-series docks, we had to replace them all simply because they don't sell laptops with the connector anymore.
I got very lucky because it was possible to desolder the flash RAM from that HDD board to another one and get the drive working again.
The AHCI / RAID switch the author is describing is only relevant to drive controllers which support SATA disks - AHCI is the protocol that's used to interact with a SATA controller. This switch has no effect on NVMe drives, and never has; the fact that the BIOS control for it even mentioned NVMe is odd.
The "RST storage driver" (i.e. Intel Rapid Storage Technology) is only required for systems which support SATA RAID using an Intel integrated RAID controller. It is not required to use NVMe devices. I wouldn't expect Dell to provide this driver for systems which don't use SATA disks, since it wouldn't do anything.
It certainly wouldn't surprise me if there were some weird trick required to perform a clean install of Windows on these machines. But I don't think the author has identified it correctly, and I find their theory that this is a deliberate effort to "control the user experience" unconvincing.
Please tell me where this is misguided..
First, doesn't Windows knows how to use NVME drives as NVME drives, without going through some weird SATA compatibility layer? Second, if I'm reading you right, Windows also has bundled drivers for RST. It's just that the installer doesn't.
Is that right? Are you saying that the Windows installer doesn't know how to use storage interfaces that the final installed Windows system would know how to use, and furthermore that those include storage interfaces that might be used for the boot drive? So in order to install, you have to get an RST driver and somehow load it into the installer, but after that the system will work?
Because that sounds like a Windows problem more than a BIOS problem. You're installing your OS on reasonably vanilla storage[^1]. Why would you expect to have to download a driver from Dell at all?
[^1]: Sort of vanilla. I don't know about this "RST" nonsense and am suspicious of anything that might make it hard to move a drive, or indeed an entire RAID array, to another computer or controller intact.
After reading the Dell documentation... yeah, that's exactly the situation. A laptop only has one drive BTW.
I am not disputing your experience at all, but it is weird to me that we'd need an RST driver to install Windows with an NVMe device; RST is a SATA/AHCI RAID tech, and while it does also do something with the 'optane memory' accelerators that Intel used to sell, I wouldn't have expected it to also make NVMe drives visible to the installer. My own experience is not current at this point, though.
[0] https://www.dell.com/support/home/en-us/drivers/driversdetai...
One workaround is to install in AHCI mode and then use the safe mode method to switch the storage mode out from under Windows, install missing drivers for the desired boot mode under safe mode if they aren't installed automatically by Windows, then reboot to exit safe mode.
https://www.tenforums.com/tutorials/22631-enable-ahci-window...
https://www.tenforums.com/drivers-hardware/15006-attn-ssd-ow...
However, OP doesn't seem to have the option to switch to anything other than RST, which could be due to BIOS settings and/or Windows settings, as well as flags on your partitions that cause Windows to boot in read only mode. You might need to toggle some settings for legacy/uefi compatibility mode, reset BIOS/EFI to (un optimized for Windows 8/10/11) default settings, disable secure boot temporarily, etc to let the EFI allow you to toggle the boot mode on some Dell BIOSes, however, especially in OP's case where they appear to not have any alternate drive modes besides RST in BIOS/EFI. In especially bad cases, you might even need to update the BIOS to enable these modes and/or wipe the EFI partitions and possibly the entire boot drive, as sometimes the BIOS/EFI is inserting itself in the boot process via "dirty bits" and/or Fast Startup mode.
https://superuser.com/questions/1554458/how-does-windows-loc...
I'd be pretty disappointed if I put in an actual service tag and nothing showed up. I wonder if it's showing you stuff that's been released since your specific laptop left the factory? This RST driver is dated November 29.
Your criticism may be reasonable; but does it really cut at the heart of the issue? Also; some of these options are occasionally oddly named, so let's not ignore the possibility that the article's author is right on this.
The article hardly provides any support for its "closed ecosystems" thesis beyond this anecdote. Whatever the situation is on this hardware (and wmf's sibling comment points out that there might indeed be something odd going on), it seems far more likely that it's the result of sloppy engineering by Dell and/or Microsoft, rather than a deliberate plan to restrict user choice (or something).
[0]: https://www.scottrlarson.com/categories/deceptivetechnology/
I'm not sure what to make of OP's issues tbh, as I was able to find the RST driver for their model here:
https://www.dell.com/support/home/en-us/drivers/driversdetai...
via
https://www.dell.com/support/home/en-us/product-support/prod...
Also, you can reboot into safe mode on Windows 10/11 and even 8/8.1, and before it reaches Windows initialization, enter the BIOS/EFI, toggle the AHCI/RAID/RST mode flag, save and exit BIOS/EFI, continue booting Windows to safe mode, install drivers if they aren't automatically installed by Windows, then reboot to exit safe mode. Apparently safe mode re-initializes the HAL similarly to the first install reboot OOBE mode, but normally HAL doesn't like you doing this in normal boot mode.
https://www.tenforums.com/tutorials/22631-enable-ahci-window...
https://www.tenforums.com/drivers-hardware/15006-attn-ssd-ow...
He said (with screenshots) that flag doesn't exist. Maybe he didn't look hard enough for the flag and didn't look hard enough for the driver though. I got a "I don't want to fix my laptop; I want to complain" vibe from the blog post.
They became the exception among 16 bit systems in regards to openness, and while it contributed to PC taking over everything else, OEMS want their margins back.
https://archive.org/details/IBMPCIBM5150TechnicalReference63...
"By June 1983 PC Magazine defined "PC 'clone'" as "a computer [that can] accommodate the user who takes a disk home from an IBM PC, walks across the room, and plugs it into the 'foreign' machine".[7] Demand for the PC by then was so strong that dealers received 60% or less of the inventory they wanted,[8] and many customers purchased clones instead.[9][10][11] Columbia Data Products produced the first computer more or less compatible with the IBM PC standard during June 1982, soon followed by Eagle Computer. Compaq announced its first product, an IBM PC compatible in November 1982, the Compaq Portable. The Compaq was the first sewing machine-sized portable computer that was essentially 100% PC-compatible. The court decision in Apple v. Franklin, was that BIOS code was protected by copyright law, but it could reverse-engineer the IBM BIOS and then write its own BIOS using clean room design. Note this was over a year after Compaq released the Portable. The money and research put into reverse-engineering the BIOS was a calculated risk. "
Copyright law and clean room design being the magic words.
Followed a couple of years later with,
"Compaq, IBM Reach Broad Patent-Sharing Agreement"
https://www.latimes.com/archives/la-xpm-1989-07-15-fi-3046-s...
If you want open, buy open. Options exist.
In the AHCI era (and earlier), drives connected to a SATA controller, and there were three ways this could work:
a) The controller was just a controller. Perhaps it appeared as an AHCI device over PCI. No funny business, and the OS could talk to the drive more or less directly via the controller.
b) Hardware, at at least hardware-ish, RAID. A RAID controller speaks SATA to the drives, and the OS speaks some protocol to the controller. It’s possible for the protocol to be obnoxious and to require obnoxious drivers and/or management software, but at least it makes sense.
c) Software “RAID” that pretends to be hardware. The CPU really does speak AHCI to the drive, but the vendor has decided to make it pretend to be a high end vendor thing and to integrate it with BIOS. But this is a mess, since the controller really is AHCI. So some hack is done to prevent the OS’s native driver from noticing the AHCI devices and instead let a (generally very bad) vendor “driver” that is actually a full RAID stack claim the devices. This could be as simple as firmware asking the AHCI controller not to report AHCI compatibility. Intel has also enabled this through multiple generations of disgusting kludges.
Enter NVMe. Unlike SATA, there is no controller. NVMe drives are PCIe devices. So the choices are different:
a) Vendor does nothing except boot support. NVMe drives show up on PCIe just like anything else would.
b) Vendor has an actual RAID controller. It’s a device that speaks PCIe to the NVMe devices and, itself, acts as an NVMe (or AHCI) device as seen by the OS. This could work fine, but it’s unlikely to be as fast as the drives themselves (NVMe is fast).
c) A truly atrocious hack, again enabled by Intel, in which firmware can ask the Intel PCIe hardware to straight up lie to the OS about what devices are connected. The hardware will try to identify NVMe drives that it’s supposed to hide (which is itself a mess — these drives are all actually just PCIe devices, and there is no reliable way in general to figure out which devices are supposed to be hidden). Then some magic “RAID” driver will do some other kludge to talk to the NVMe devices behind the OS’s back and pretend to be a disk itself. Of course it works poorly.
In any case, I wonder if the OP’s machine is actually an example of (b), where the NVMe drives, presumably connected to a fancy backplane, are genuinely connected via PCIe to an actual RAID controller, not the CPU or chipset. If so, a firmware option for “native NVMe” would make no sense, and the actual correct solution is for the OP to arrange for the Windows installer to use the right driver. This has been officially supported, usually in some annoying way, since at least Windows NT 4.0 and probably for quite a bit longer.
The only time I have come across scenario B was with a VAIO laptop from around 2011. The machine was advertised to come with “fastest SSD on the market” which turned out to be four (!) off the shelf eMMC modules in RAID 0 through a hardware controller. As janky as it sounds, OS compatibility was never an issue because the controller was a fairly common model with well established driver support rather than some bespoke mystery.
[0] - https://learn.microsoft.com/en-us/powershell/module/dism/exp...
Yes, it’s unfortunate that Dell didn’t put this specific driver on their website for this specific model. However, I think the simplest explanation is that Dell is getting lazy with their driver coverage on their website, not some conspiracy to slowly boil the industry alive.
Use the common tools for exporting a driver from the OEM media if you can’t find it online.
That being said, I recently did a dual boot install (on an MSI motherboard) with Windows and Pop!_OS and the Linux install went much smoother than Windows. For Windows I had to get the RST drivers and run the setup exe in extract mode in order to get drivers that worked during initial install. And Windows also didn't even include an Ethernet driver by default.
Here is just one example of computing that has no limits on problem solving. The only limits are scale and what good is scale anyway. Problems solved at scale are too general and over complex for most individuals problems.
https://hackaday.com/2019/09/09/everything-you-wanted-to-kno...
Like a bog-standard Dell??
Do you have any recommendations for an alternative machine? I’m looking for a solid, reliable workhorse that could serve for years. My current DELL setup has never failed or let me down, and I’d like to find something within a similar budget that I can rely on for constant use for years.
OTOH it's of course new and modern vs used and aging.
Yeah, that's the part that doesn't work. You have to eat losses on (at least) the first generation to succeed.
I think Raptor’s plan was/is the right one but the market of consumers who will pay extra to get that openness is quite small.
Framework is close. They’ve had a LOT of VC money.
https://old.reddit.com/r/sysadmin/comments/1hp3sst/pc_hardwa...
I mean, it's not like Linux didn't spend 30 frikkin' years specifically aping hardware that carried the WIntel brand from the IBM PC with MS-DOS up to WindozeWhatever13 or whatever they are up to now...
I cannot fathom the strange incentivization schema that would cause the entirety of the existing mass-retail OEM computer production to be "Windows ONLY" and actively contributing to literally selling LESS of their own units via efforts to lock their own hardware against running your own damned OS upon it!
I buy hardware I can run Linux on. I have no use for Microsoft Windows in any capacity for any purpose, period. end of story.
Hardware Manufacturers please take note! (I remain puzzled... Dell even sells some preloaded Linux laptops, IIRC... what gives, Dell?)
What gives is that the Developer Edition gives them permission to make the other models 110% Windows-only because "if you want Linux just buy the Developer Edition". In their minds there is no reason to make the normal edition support Linux.
I think its just a battery life issue, and as far as I know its not much worse than windows.
If you are going to carry the power brick around with you anyway, might as well just plug in it a little earlier.
For example, with web browsers, most Linux ones (including Chrome and Firefox) disable much of hardware accelerated graphics on Linux by default because of "unstable graphics drivers". If I remember correctly, Chrome just disables it across the board, while Firefox has a whitelist of drivers considered stable which is basically just Intel.
In my testing, unless you muck around with these settings, you're can easily lose something like an hour of battery life compared to Windows if all you do is just browse websites (and I'm not even talking about anything fancy here; my automated test was literally just scrolling the main Reddit feed).
https://www.dell.com/en-us/shop/laptops/intel-core-ultra-ser...
I had one of the early Project Sputnik laptops (XPS 13 with Ubuntu preloaded) and loved it. Now I use a Framework which is fine, but not anything amazing.
I'm writing to you from a $250 laptop running Mint (with 11 hours of charge remaining) that this is is pure, unadulterated FUD from 20 years ago.
Lenovo certifies their systems for use with both RHEL and Ubuntu [1] which means that most mainstream distros will work contemporary, high-end business ultrabooks that are widely regarded as some of the best in their class. Arch has a lush, green compatibility matrix [2] for these laptops too. Once a year on average I buy a four-year-old T series and throw Mint on it for a friend or relative and everything works out of the box. This has been the case for at least a decade. If you don't want to buy a Thinkpad then the acclaimed XPS 13 is one of many [3] Dell laptops that comes pre-loaded with Ubuntu. Others in this thread have also pointed out the numerous vendors that ship Linux on rebadged barebones hardware.
We need to cut it out with the "desktop Linux is hard" meme. It's a counterproductive mind virus. It hasn't been true since the Bush administration and almost always amounts to some hand-wavey comment like the above. The hoops you have to jump through with modern Windows a la Group Policy hacks, TPM requirement bypass, selecting the exactly-correct LTSC version, etc. are consistently greater than anything you have to deal with on modern desktop Linux in my experience.
[1] https://support.lenovo.com/us/en/solutions/pd031426-linux-fo...
[2] https://wiki.archlinux.org/title/Laptop/Lenovo
[3] https://www.dell.com/en-us/shop/dell-laptops/scr/laptops/app...
Writing this from a Framework 13. I've been using Linux laptops for the past 15 years, and this is the first time a Linux-friendly machine has checked all my boxes (including excellent battery life).
https://minifree.org/product/libreboot-t480/
https://puri.sm/products/librem-14/
https://www.raptorcs.com/TALOSII/
https://frame.work/ie/en/products/laptop16-diy-amd-7040
The only way to fight enshitification is government regulation.
Otherwise, for the 0.1% of market population able to make an informed choice, there remains a 99.9% of consumers ready to buy the cheapest thing and then shrug up or whine.
A good friend of me decided to stop (as far as possible) having any further contact to people who use "spying devices" in his presence.
A good idea.
I think LG's webOS is nice - its consumer friendly, but as a developer, you can whip something up and install it on your TV easily in an afternoon. OTOH, I believe not all the APIs are documented, as some of the interfaces provided to/from Netflix/Prime Video/Dinsey+ don't appear to be possible with documented APIs, and ofc, from a hardware perspective, they are completely locked in.
We should call it out loud and clear where ever we see it.
Don't buy from for-profit entities, or soon there will be no non-for-profit entities.
But really, capitalism properly managed shouldn’t be about figuring how to profit by making things worse, it should be about profiting by solving problems.
When a business profits by creating problems rather than solving them, it is a parasite on society. Such businesses are effectively criminal enterprises, and should not be allowed to exist.
"Capitalism properly managed" isn't capitalism anymore, so if that's what we want (and I agree with you) then let's use proper terminology. Workers-owned coops, democratically-chosen regulations, communities governed by and building for themselves,federating between each other, the stuff
Its a security feature to limit the amount of rootkits that are installed.
They couldn't even get their touch-pads consistent (https://news.ycombinator.com/item?id=41992784).
I have very few generic vendor sourcing advice when it comes to computing hardware, but "Nobody ever got fired for NOT buying Dell." is one of them.
Just don't.
Maybe I got lucky?
Similarly, my last three laptops have all been Dell Precision -- only issue until I switched to Intel integrated gpu was Nvidia on Linux (black screens, laptop attempting liftoff due to gpu heating issues) causing periodic grief.
Also, for the author, Dell Precision provides advanced BIOS options out of the box, something that their consumer line of laptops probably doesn't offer.
Their R815s after eliminating the early failures (leading edge of the bathtub curve) just trucked on. I used to run an OpenStack cluster on top of them till last April or so. At the end, either the CPU power regulators died, or their RAID cards just called quits. No other errors after 10+ years of service.
We also have their newer CPU and GPU servers. They just work. Scream occasionally due to high load, but not overheating or dying.
They're built like a tank, from our experience.
I would definitely avoid their laptops and get Thinkpads instead.