
KitKat managed to turn a stolen truck into a marketing campaign. I wouldn’t be surprised if NVIDIA was trying to do the same thing.

KitKat managed to turn a stolen truck into a marketing campaign. I wouldn’t be surprised if NVIDIA was trying to do the same thing.

What’s the IPv4? I believe Cloudflare has different prefixes for WAF, warp, and workers.
2a06:98c0:3600::103 is definitely a Cloudflare WAF IP, so my guess is someone using either warp or workers is sending requests and added that IP to X-Forwarded-For as a red herring.
Switching ttys wouldn’t have done anything. The kernel logs are usually saved to efi_pstore (or sometimes erst) by default though.
Edit: you can also set drm.panic_screen=kmsg as a kernel parameter to print the logs instead of the QR.
Nah, when a kernel panic hits then everything’s screwed.
Pressing ESC does work for systemd-bsod (which is different) and as you mentioned Plymouth; but not drm_panic.
Edit: yes, it was Systemd who implemented it.
Nah, systemd-bsod is different and designed to show info about boot failures:

It’s rather quite useless.
drm_panic on the other hand has nothing to do with systemd, and is what’s shown in OPs post. The link can be quite useful for users to post their issues on bug reports or whatever. But if you know what you’re doing, then it’s pretty easy to configure it to print text instead.
Also remember, the reason drm_panic exists is because graphical outputs would otherwise freeze during a kernel panic, and not show anything useful.
This probably isn’t too useful for you as they only have 24v and 54v models, but Ubiquiti used to make EdgePower UPSes. They have a http management interface that lets you monitor the power usage or power cycle the router if a ping stops responding, and etc. I installed one recently for a POE switch of mine.

the smallest model made by Deepseek is about a 300B param model.
This is not correct. DeepSeek has plenty of smaller models. I just had a scroll through their huggingface, and picked out a few: DeepSeek-V2-Lite (16B), deepseek-moe-16b-chat, deepseek-llm-7b-chat, but there’s quite a few more too.
Though DeepSeek R1 is their flagship model, which is the one people usually think of, and that’s a 684B param model.
So it seems I was wrong about Cloudflare having seperate prefixes for WAF and workers. And these are all WAF/workers IPs (but not warp). My guess is that someone’s made themselves a http proxy worker, and are using that to proxy their bot’s requests.