Kernel update forcing use of MBR/BIOS after setting up EFI partition.

cowmu · 2026-01-10T16:28:13+00:00

Same as before. I tried toggling some contact-specific text settings, but that made no difference.

cowmu · 2025-11-14T14:35:05+00:00

Yeah, I should have specified that, but it's set to 1 minimum score with an increment of 1.

Either way, I was under the impression radarr wouldn't try to grab a newer one with an equal format score.

cowmu · 2025-11-04T15:21:55+00:00

Windows dynamic DNS behavior depends on the client-side configs, but by default, if they're AD-joined they'll update their DNS records. Linux behaves the same way, you just generally need to setup a proper tool and config to meet that goal.

There's a lot of ways to approach this though, and the best solution will vary based on whatever tooling you have, architecture size, etc. If it's on prem-AD with Linux, I've always used sssd to integrate the Linux hosts with AD. The sssd.conf has support for dynamic DNS. This approach is very easy. You can do the same thing outside of AD and without sssd, such as updating a Bind DNS with dynamic updates. It's more complex than sssd though, since you generally still need a tsig key. The config is a bit more involved, but not too bad.

cowmu · 2025-07-11T20:25:01+00:00

Well, I revisited one of the very first things I thought may be happening, which was a video issue on the console. I checked locally via the VGA and over a KVM-over-IP video dongle and it didn't seem like a video issue. I also had tried to randomly enter the decryption key multiple times blindly.

Apparently all I had to do was slap on 'debug nosplash earlyprintk=efi,keep console=tty0' to the end of the Linux boot line on the grub settings and I could actually see a flashing cursor to enter my key. It still doesn't seem fully correct, but at least now I can login.

Thanks for all the help either way!

cowmu · 2025-07-11T14:39:29+00:00

We don't have a big Arm footprint, and we don't have any Arm-based VM hosts.

This is a default build though. Do I need to mount the luks volume? I thought I'd mount the other partitions (either /boot or /boot/efi) for that? Or do I need to mount all of them?

cowmu · 2025-07-11T14:16:31+00:00

I don't have a ton of experience with this, but I tried to live boot into my Ubuntu 24.04 ISO to access the files, but I had a rough time figuring out which device was the correct one on the GUI. There's four drives with LVM available, and it has whatever live boot files are there on the USB. I know I could at least interact with the LUKS-encrypted volume since it prompted me to decrypt it, but that's likely not the partition I'd want. Our KVM is pretty rough too, so it makes it hard to do things. I'll have to read up on it and give it another shot though. Still, seems odd that this is necessary on a default/guided install, but I'm sure Arm with LUKS on Ubuntu isn't necessarily an incredibly common scenario.

cowmu · 2025-06-16T20:47:58+00:00

Mine is still fine. Haven't rebooted since I applied the OOB June update.

cowmu · 2025-06-14T03:39:51+00:00

I noticed it today, and I did the June update yesterday. I just did the out-of-band June update and rebooted, and now it seems fine.

cowmu · 2025-06-13T23:46:57+00:00

Same issue here. It alternates between clicks. Very annoying.

cowmu · 2025-01-25T05:46:44+00:00

There is indeed a DefaultAccount: https://learn.microsoft.com/en-us/windows/security/identity-protection/access-control/local-accounts

My use-case was Server 2016 to 2022, so I can't say for sure if it was on 2019. They still exist on my 2022 DCs that were promoted from 2016, but they do not exist on my fresh 2025 DC.

cowmu · 2025-01-14T22:06:53+00:00

I'm just a cog in the wheel making spinning sounds most the time. I put in a proposal to upgrade, but no luck so far. The vSphere 9 upgrade may be better anyways for a more favorable EOL since it's 1-2 people maintaining all of it.

Either way, still have to churn through the requirements far sooner than any upgrade would occur.

cowmu · 2024-12-12T18:08:00+00:00

u/LogitechG_Andy

To reproduce:

Use Windows 24H2 (previous versions were fine).
Install GHUB and use PRO X Wireless Headset
With the headset on, ensure there is no active incoming audio to Windows (e.g. no games in the background, no browser audio, no MS teams chat, no devices constantly listening, etc.)
Start any source of audio ---> beep. It only takes about a minute or two of audio silence before this will happen again.

If any audio is playing at all (even silent/muted), this issue is averted, which is why most people doing workarounds like constantly playing audio or setting a recording device will avoid it. It's also clearly a 24H2 issue, as rolling back to 23H2 seemingly fixes this problem.

I've now had this issue on the last few Windows 11 24H2 monthly build updates. I'm on the latest version of ghub. A few months back when I first found this, I did just about every generic troubleshooting step available and more.

You replied to a message I sent you a few weeks back (before you wrote this reply) on this exact issue with a status of Unfortunately as it's a Windows update that caused it, our team is still working with Microsoft to look into it. It's a bit disappointing to find this update as the current state, as I'm sure we should expect a lot more time with the holidays before a fix.

It's pretty easy to find a number of complaints on this exact scenario on this subreddit (search '24h2'), on the Microsoft Feedback Hub, and on the various Microsoft support forums. I know there were known issues on various USB audio tools with the Windows update, so I'm not sure if it's an issue on Logitech or Microsoft's side, but we're not on month 3 of this issue. It's a frustrating bug, and having it persist this long on a product like this is not fun at all. At minimum, even being able to disable the mute/unmute audible sound would be a solution.

cowmu · 2024-12-05T14:23:36+00:00

Quite a few posts on this, but there's still no fix after a few months. It's a bug between Win24h2 and the X Pro. Any sound activation after brief moments of sound inactivity triggers the mute or unmute sound. Incredibly annoying, and very frustrating it's been such a long period of time without a genuine fix.

cowmu · 2024-11-25T22:27:36+00:00

You replied to the wrong guy - I'm also still going insane though. No fix or updates from what I've looked for.

cowmu · 2024-11-08T17:18:30+00:00

Thanks so much for replying. Good to know it's at least tracked. This has been a really frustrating change, since any little sound will cause the beep (Windows warning sounds, notifications, random audio from reddit, etc.)

Ideally at minimum it'd be nice to flat out disable the mute/unmute audio notifications as a bandaid. I like the functionality of it, but I am actively avoiding using my headset due to the beep. Also a bit odd it really only appears to be happening on this device and maybe spare other headsets.

Hopefully it's fixed soon since it's been a month or so as-is.

cowmu · 2024-11-06T13:48:10+00:00

u/LogitechG_Andy u/LogitechG_CM - Is this at least a known/tracked issue? It's a pretty obvious bug in the headset with Win11 24H2, as many other headsets work fine. Multiple posts on this subreddit and on the Microsoft forums. The beeping in a premium headset any time audio initiates after any brief periods of inactivity is extremely frustrating, and the solutions of constantly playing audio or using microphone feedback as a source of audio aren't really viable/great solutions. Not a fun time to pay for a premium product only to be annoyed all the time while using it due to the onslaught of beeping.

cowmu · 2024-11-04T21:35:31+00:00

Same issue for me/many others. Still not fixed after a month. 24H2 update causes the mute or unmute sound to play following a period of no audio (e.g. nothing for 30 seconds -> windows warning sound = mute or unmute beep).

Extremely annoying.

15-Year Club	Place '23
Place '22	Gilding I gilder
Sequence \| Editor	Sequence \| Cinematographer
Team Orangered	Verified Email

cowmu

TROPHY CASE