Search

Help with Custom EDID
Edit: Solved, while changing EDID make sure to remove the old module first and reinstall it with the new EDID
I have a faulty DP to HDMI adapter, that unfortunately never seems to parse the EDID data, so while connecting to a TV I used this guide and a 1920x1080.bin file from the internet and it worked, but unfortunately I was unable to use the TV speakers(I guessed the EDID file didn't specify that the device had audio out)
Using a separate pc I extracted my TVs EDID.bin file and repeated the steps but unfortunately, it just doesn't work, its stuck on the old 1920x1080.bin(I can tell because it shows up as 'Linux Foundation 23'') The issue persists even after I delete the old .bin file from /usr/lib/firmware/edid
I am using wayland
System info:
undefined
OS: Fedora Linux 40 (Workstation Editi Host: TECRA R940 PT439V-03U02WAR Kernel: 6.8.11-300.fc40.x86_64 Uptime: 29 mins Packages: 2209 (rpm), 32 (

Void Linux aarch64 chroot installation in VM on M1 MacBook
I am in the process of installing Void Linux inside a virtual machine on my M1 MacBook. I have followed the guide for chroot installation and I am having trouble getting it to work.
This is what I have done, and please correct me if I am wrong:
1- Created an empty virtual hard drive
2- Booted a live image of Arch Linux aarch64 due to the lack of Void Linux live image.
3- Using cfdisk, I create a gpt partition label and write 2 partitions (500MB /dev/vda1
) and (Remaining free space /dev/vda2
) with mount points (/boot/efi/
) and (/
), respectively.
4- Format as vfat and ext4, respectively.
5- Mount them as per the guide and then manually enter chroot.
6- Again, do pretty much everything as listed in the guide.
7- For (/etc/fstab
), I do the following
undefined
# Corresponds to /dev/vda1 UUID=1a2b.....uvw /boot/efi vfat defaults 0 2 # Corresponds to /dev/vda2 UUID=3c4d.....xyz / ext4 defaults 0 1 tmpfs /tmp

Playing Visual Novels on GNU/Linux
cross-posted from: https://lemmy.comfysnug.space/post/138679
We've been working on a guide to help players on all major GNU/Linux distributions play visual novels for the past few weeks. This guide is designed to be used by both beginners and experts, with minimal need to touch the command line.
openSUSE wins the award for "never had to touch the terminal" and "simplest setup instructions", but Fedora is a close second.
While there are a few existing visual novel guides for GNU/Linux around, we've tried to fill in the gaps we noticed. We've put a lot of research into this guide and ensured it is accurate while remaining simple and approachable.
If you're interested, start here!
We have an extensive Troubleshooting section on our Problems page if you're having trouble getting visual novels to work, too.
I wr