It’s called secure boot and it’s been around for over 10 years now.

Ah kay, definitely not a RAM size problem then.

iostat -x 5 Will print out per drive stats every 5 seconds. The first output is an average since boot. Check all of the drives have similar values while performing a write. Might be one drive is having problems and slows everything down, hopefully unlikely if they are brand new drives.

zpool iostat -w Will print out a latency histogram. Check if any have a lot above 1s and if it’s in the disk or sync queues. Here’s mine with 4 HDDs in z1 working fairly happily for comparison:

The init_on_alloc=0 kernel flag I mentioned below might still be worth trying.

deleted by creator

After some googling:

Some Linux distributions (at least Debian, Ubuntu) enable init_on_alloc option as security precaution by default. This option can help to prevent possible information leaks and make control-flow bugs that depend on uninitialized values more deterministic.

Unfortunately, it can lower ARC throughput considerably (see bug).

If you’re ready to cope with these security risks 6, you may disable it by setting init_on_alloc=0 in the GRUB kernel boot parameters.

I think it’s set to 1 on Raspberry Pi OS, you set it in /boot/cmdline.txtI think.

Exhaustive ZFS performance tuning guide

sync=disabled will make ZFS write to disk every 5 seconds instead of when software demands it, which maybe explains your LED behavior.

Jeff Geerling found that writes with Z1 was 74 MB/sec using the Radxa Penta SATA HAT with SSDs. Any HDD should be that fast, the SATA hat is likely the bottleneck.

Are you performing writes locally, or over smb?

Can try iostat or zpool iostat to monitor drive writes and latencies, might give a clue.

How much RAM does the Pi 5 have?

OpenAI noticed that Generative Pre-trained Transformers get better when you make them bigger. GPT-1 had 120 million parameters. GPT-2 bumped it up to 1.5 billion. GPT-3 grew to 175 billion. Now we have models with over 300 billion.

To run, every generated word requires doing math with every parameter, which nowadays is a massive amount of work, running on the most power hungry top of the line chips.

There are efforts to make smaller models that are still effective, but we are still in the range of 7-30 billion to get anything useful out of them.

Personally I think it’s fallen out of fashion. For my blog I’d either use a meme or other dump picture for each post. When generated images first came out I used a few for blog posts, it was new and interesting and said “I’m interested in technology and like playing around with new things”.

Nowadays I’m back on the meme pics. I feel now it’s so much easier to generate images, it more says “I want to look professional but also spend no money and have no standards”.

I always assumed that Poettering is an arse to people because of the hate he got for systemd. I imagine it’s hard to see the best in people when there’s a crowd of haters everywhere you go. Though I have no idea what he was like beforehand.

You can read IAEA’s press releases for each attack. They go through the precise function and nature of each building and access the potential danger. Though they haven’t updated for the US’s latest bombing.

Like Hawke said it seems like the graphics card or driver crashing. Very hard to troubleshoot, especially when it’s random. Bazzite probably already has very recent drivers, there’s this post on the bad website listing some things to try. This stuff can lead to superstitious thinking, with people changing something, rebooting to have it work fine for a while then they post that change as if it fixed it.

God speed.

Your motherboard wouldn’t happen to be an AsRock? There’s been reports of ASRock mobos in particular causing problems with 9000 series AMD chips, especially the X3D. Mate of mine running windows has been having it crash especially when idle at desktop.

I’m not familiar with a green Linux equivalent to the BSOD. Is it completely green? In that case it may be a graphics problem…

Maybe you should

It runs basically the same PebbleOS, so they’ll work with any app that works with the original Pebbles. They plan to keep using the community app hosting at https://apps.rebble.io/. There’s also GadgetBridge that’s compatible. Eric mentioned on HN the intention for an official open source library that can be used to make other companion apps too.

Yeah the mobile app is open source too https://github.com/pebble-dev/mobile-app

I was so bewildered reading the novel. I had heard he wrote it as a pro military propaganda piece, but I couldn’t help but see it as satire.

They are kitted out in mech suits, making them seem more machine than man, put into drop pods that are fired onto the planet like bullets out a gun. In the pod they are isolated from their comrades, isolated from their humanity, literally turned into pieces of a weapon.

Then they land on the alien planet to perform a terrorist attack on a civilian city. And this book is meant to be pro war?

I had a 5 II too, used lineageOS for years, worked great. Doesn’t totally solve the battery or fingerprint reader. My screen got the dreaded green lightsaber too. Nail in the coffin was Australia turning off 3G so it can’t make calls anymore. (Wasn’t officially sold here so they didn’t bother loading it with VoLTE profiles)

Some googling suggests this is what Dropbox does when it doesn’t like the owner or permissions of any files in the Dropbox folder. It is very weird though. I assume you have dropbox installed? It is syncing correctly? Running find /home/dullbananas/Dropbox/ ! -user 'dullbananas' will list any files in that folder that aren’t owned by you.

Assuming your userid is 1000 (likely but not guaranteed), running the script should be harmless and stop the password prompt from appearing until there is another file permission issue. Check your user id with id -u 'dullbananas'.

I don’t have a Fedora box to check for sure, but have a look in /var/log/secure, it might have details of the request and what program called it.

Surely the space is part of the command. It’s running sh with the file in /tmp as the parameter (run this file).

Seems weird to have a separate app read sent and received messages? Is it poking holes in the Messages app sandbox?