how do i do that?
Probably by editing your GRUB config or whatever bootloader you’re using.
Here is the EDID
Thanks, that should be enough I’ll have a look when I’m free. Also something like get-edid > monitor.bin would probably be easier for me though.
Edit: I’ve had a look, I can’t see any issues. Both checksums validate correctly and it advertises audio support. As you’ve probably seen in edid-decode, I’d expect it to show as ‘SONY TV’ (or at least for KDE ‘Sony SONY TV’ I believe).
I wrote a guide here: stevetech.me/posts/force-enable-vrr-edid
But it was mostly just changing random things and hoping for the best, so YMMV. I hope it helps!
None of my monitors (which are all DisplayPort) have audio, but one appears in the audio settings, so I’d say DisplayPort itself does support audio.
Is edid/sony.bin your new EDID? Does it revert back if you remove drm.edid_firmware all together?
Also, do you mind sharing your EDID? I had to edit mine to get VRR to work, so maybe there’s something invalid in yours. It does contain serial numbers though if that’s a problem.
I believe the main contributor for drm_panic wants to add one eventually. Here’s what it might look like:
https://gitlab.com/kdj0c/panic_report/-/issues/1
Also it looks like the colours are configurable at compile time (with white on black default).
Also a solution: Use Wayland, it’ll probably break other things, and Nvidia support is only just getting there; but it’s multi monitor support is amazing, so it should fix that issue. So maybe it’s worth a try?
For electron, if ELECTRON_OZONE_PLATFORM_HINT and electron-flags.conf don’t work, you can also add --ozone-platform-hint=wayland to the end of Exec in each .desktop file (also works on Chromium, but not CEF AFAIK).
There’s also --ozone-platform-hint=auto if you find yourself switching between X11 and Wayland.
I have also added all Cloudflare IPs in Jellyfin’s known proxies
You should only need to add the IP of the last proxy before reaching Jellyfin, which would be Caddy.
The CAD files for the Framework 13 have also been out for a few years too.
ADCs, DACs, IO extenders
These should all work without kernel drivers. For example, here’s a user space python library for ADS1*15 ADCs, or Nuvoton MS51 IO Expanders. Unless you need very specific timing or require the kernel to know about it, you shouldn’t need a kernel driver.
Idk, with I2C if it’s not something that needs a kernel level driver, there usually isn’t a problem with interacting with it from user space, for example basically all RAM RGB controllers are I2C and OpenRGB has no problem with them. I’m pretty sure I’ve only ever used an I2C device tree overlay for an RTC.
Also I2C/SMBus is present everywhere on x86, like some graphics cards expose it through their HDMI ports, even some server motherboards have a header for it; but for GPIO I’m unaware of any motherboards that expose it, so good luck researching the chipset and tracing out the pins.
but I can’t figure out which of the “0000:00:whatever’s” correlate to my Bluetooth card
lspci will list your PCI devices and their ID, but if it’s a combo WiFi & Bluetooth card, they usually use PCIe for WiFi and USB for Bluetooth.
Because how can linux ARM run on a device that used to run windows x86?
Have you misread AMD64 as ARM64?
AMD64 is the 64bit extension of x86, often also called x86_64.
As others has said, ARM is a completely different architecture which is not compatible with x86 without translation layers. ARM also has a 64bit version called ARM64 (or AArch64).
Just curious, what parts aren’t open source? At a glance it seems like they’re working on supporting self hosting and I couldn’t find any binaries.
I’m probably jumping to conclusions, but Nvidia?
I can’t say it isn’t a fork bomb, but it does happen to match IPv6 address with regex.
Firstly, there actually isn’t much difference between server grade and gaming motherboards, like sure one might support ECC + IPMI and the other RGB + overclocking, but as far as compute goes, they are both effective motherboards.
Secondly, I don’t think OP was going for a ‘server’ but more of just a workstation type build, so why one or the other?
Thirdly, why does it even matter? OP should be proud of their system whether you like it or not. Even if they are using it as a server, my first server was just some reasonably priced consumer grade parts and I never had any sort of stability issues with it.
To me that does sound like your initramfs just needed recreating, since un/installing a module will do that usually.