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.
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.


My TV has a HDMI port marked DVI:

Maybe your “COMPUTER” input is negotiating DVI and the others don’t support it or something?


Sure, Soda then. As that’s the fork of Wine that Bottles develops, and the fork of Wine that this article is about.


Ignore the other guy on this, I have an A770 in my gaming ring and a B60 in my server. The drivers are amazing on Linux, and much better than NVIDIA.
If all you need is encoding, then VAAPI just works. There are some other caveats with the Alchemist series, which is mostly it was made during the transition to xe, which means you either pick better encoding with i915 (default) or better gaming performance with xe. For your use case I’d leave it with the default i915, though there are encoding patches for xe if you must use the newer driver. Both drivers are mainlined and officially supported by Intel.


For context, CodeWeavers sells a paid Wine product, CrossOver, and its database still lists Microsoft Office 365 on Linux as “Installs, Will Not Run,” last tested against CrossOver 26.3.0.
Office 365 does run in CrossOver, just poorly. They’ve also recently dropped support for it in CrossOver 26, and AFAIK CrossOver 27 won’t be able to run it at all.
So it’s good to know that Bottles has effectively replaced it.


Regarding Google Coral, from the docs: https://docs.frigate.video/frigate/hardware
The Coral is no longer recommended for new Frigate installations, except in deployments with particularly low power requirements or hardware incapable of utilizing alternative AI accelerators for object detection. Instead, we suggest using one of the numerous other supported object detectors. Frigate will continue to provide support for the Coral TPU for as long as practicably possible given its still one of the most power-efficient devices for executing object detection models.
Personally, I’d recommend OpenVINO. It works on iGPUs, and if that’s not possible it’s quite performant on CPUs. I currently run a Google Coral and the Linux driver is no longer officially maintained meaning it breaks every now and then after a kernel update, next time it breaks I’m going with OpenVINO.
Also, I’d install Docker in an LXC for Frigate, it makes passing the iGPU through to it a lot easier.


Ignoring all the scary censorship things, I thought they’d be some sensible exceptions for this:
Require all website owners to write a risk of harm assessment to the Australian government (the list of required things to say in this assessment is really long)
But there seems to not be:
26A Risk assessments
(1) A person who provides an online service must conduct a written assessment of the risk of harm posed by the service in Australia.
…
Then an ‘online service’ is defined as:
25A Online services
(1) Each of the following is an online service:
(a) an internet carriage service;
(b) a social media service;
(c) a relevant electronic service;
(d) a designated internet service;
(e) a hosting service;
(f) an internet search engine service;
(g) an app distribution service;
…
Then a ‘designated internet service’ is defined in the Online Safety Act 2021:
14 Designated internet service
(1) For the purposes of this Act, designated internet service means:
(a) a service that allows end-users to access material using an internet carriage service; or
(b) a service that delivers material to persons having equipment appropriate for receiving that material, where the delivery of the service is by means of an internet carriage service;
but does not include:
(c) a social media service; or
(d) a relevant electronic service; or
(e) an on-demand program service; or
(f) a service specified under subsection (2); or
(g) an exempt service (as defined by subsection (3)).
(2) The Minister may, by legislative instrument, specify one or more services for the purposes of paragraph (1)(f).
Exempt services
(3) For the purposes of this section, a service is an exempt service if none of the material on the service is accessible to, or delivered to, one or more end-users in Australia.
So yeah, all website owners would need to do annual risk assessments, and keep them for at least 6 years, unless your website is not accessible to Australia.
Please lmk if I’m wrong.


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.


Can confirm it does:
OrgAbuseHandle: ABUSE9107-ARIN
OrgAbuseName: ABUSE
OrgAbusePhone: +1-313-516-8908
OrgAbuseEmail: abuse@hostodo.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/ABUSE9107-ARIN
Depends on how low level you need. If you’re just looking at the data being sent, then Wireshark will work fine; I’ve even used it to help reverse engineer a UPS. If you’re investigating interference/timing/collisions/whatever then you’d need a scope or logic analyser.
Deleted - Replied to wrong comment.
Probably, and that font looks remarkably like Calibri which seems suspicious too.


At least not since 1951.


Oh cool. Like ReactOS is to Wine, I hope this will be useful to Darling.


I believe OP would require an authoritative DNS server, which AFAIK Quad9 is not. desec.io would be my recommendation though.


The data included a transcript of all messenger messages.
Not to defend Facebook, but it would be weird if they didn’t, since you can use messenger on any device, and it’s obviously saved on their servers. A transcript of WhatsApp messages would’ve been different though, as they say they can’t read them.
No doubt it’s worse now.
Yeah definitely, and they’re probably hiding some the data too.
It also stands for Immigration and Customs Enforcement in the US.
Also like the other guy, when you spam all your blog posts within the same hour, it’s annoying and most people will ignore them. At least limit yourself to once a day.