That doesn’t fix the problem of needing specific device tree files for every computer.

So you still won’t be able to say, swap your WiFi chip in your laptop and still have it work.

This just enables a small subset of (specifically Windows ARM laptops) to boot from an image.

This is very different from x86, where ACPI allows you to have a single image that knows very little about the hardware.

If ARM started using SystemReady, you could see a truly generic image, rather than having a specific list of laptops the “generic” image works with

That’s also what we say when continuing our own task

And understand when you can use them…

I’ve seen too much code following this advice blindly that just does something like

strncpy(dst, src, strlen(src))

There aren’t any ARM manufacturers that upstream their drivers, and no SystemReady support from any manufacturers

Basically every package works on ARM, but the lack of manufacturer support for hardware means ARM effectively requires a special kernel build for every PC

RaspberryPi has worked on upstreaming their Broadcom SoC, Collabora had worked on upstreaming the RK3588 SoC…

None of Qualcomm’s recent chips are very usable (always missing something like audio, or other basic functionality)

Asahi Linux worked on Apple M1/M2 support

Unless a new ARM manufacturer comes along, general use ARM PCs are a long way away

I would assume its in reference to the section of the video quoting YouTube’s policies that channels can be removed after 3 copyright strikes. Bloomberg has 10 days to appeal to YouTube and keep the strike active

That’s why all of the major players have been frothing at the mouth to get rid of discs

Alpine already doesn’t use systemd

How are you defining “Obsolete” vs “Nu”?

e.g. Brainfuck from 1993 is all the way to Nu, while D (2001) and Rust (2012) are less “Nu”?

My take: There was one user that kept making post after post after post as they tried to upgrade, which made it seem like there were more issues than there were

Scrolling through it right now, every support question from the last week appears to be from the same person

What? They haven’t changed anything since they were supposed to be banned.

Trump just keeps pushing back the deadline. Right now it’d be banned Sept 17th, but presumably he’ll push it back again.

It’s just too popular for the administration to take the flak for it disappearing while they’re in office

The TreeStyleTab add-on lets you deal with a lot more open tabs before it becomes untenable

You have to at least modify your sources.list.d manually first. For most people, updating sources.list.d and running full-upgrade will probably work fine…

The full instructions are

1. run dist-upgrade
2. remove back ports
3. remove obsolete packages
4. remove non-debian packages
5. clean up old configuration files
6. add non-free-firmware (this is a 12 -> 13 specific)
7. remove proposed updates
8. disable pinning
9. update sources.list.d to point to the next release
10. apt upgrade --without-new-packages
11. apt full-upgrade

It takes like an hour? but it’s still not “just press okay.”

Ubuntu’s has broken on some upgrades for friends and they had to do the whole Debian process manually, but it does try to automate the removals, disablements, and updating sources

Edit: instructions taken from Trixie release. I skipped some that aren’t really unique, like make a backup

https://www.debian.org/releases/trixie/release-notes/upgrading.en.html

AMD has been proving that x86_64 can be at least as power efficient as ARM over the last few years (given a floor of performance for like a phone/laptop… I doubt it can get as low power as a little ARM microcontroller)

It seems like x86 was getting so power hungry because of Intel’s laser focus on single core performance

They’re talking about a Debian 12 -> Debian 13 upgrade

On Debian, you get release notes on what commands to run.

Ubuntu has their own software update utility, separate from Software Center or Discover, that runs the commands for you

Just a heads up, if you’re on the 7040 mainboard, I needed to add this to the kernel command line on Debian 13 for reliable suspend/resume. Without it, the screen would just be grey sometimes and not resume

amdgpu.dcdebugmask=0x10

Edit: may also only affect the 2.8k display