Skip Navigation

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:

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 (flatpak) Shell: bash 5.2.26 Resolution: 1920x1080 DE: GNOME 46.2 WM: Mutter WM Theme: Adwaita Theme: Adwaita [GTK2/3] Icons: Adwaita [GTK2/3] Terminal: gnome-terminal CPU: Intel i7-3540M (4) @ 3.700GHz GPU: AMD ATI Radeon HD 7550M/7570M/765 Memory: 1998MiB / 7879MiB Dmesg -H

``` [Jun20 22:26] Linux version 6.8.11-300.fc40.x86_64 (mockbuild@f09cc32e12c24ed6a1a66c2a2e9f1728) (gcc (GCC) 14.1.1 20240522 (Red Hat 14.1.1-4), GNU ld version 2.41-37.fc40) #1 SMP PREEMPT_DYNAMIC Mon May 27 14:53:33 UTC 2024 [ +0.000000] Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.8.11-300.fc40.x86_64 root=UUID=XXXXX ro rootflags=subvol=root rhgb quiet drm.edid_firmware=DP-2:edid/sony.bin

```

Any help is appreciated

16

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

```

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 tmpfs defaults,nosuid,nodev 0 0

``` I am not using swap for sake of simplicity.

8- I install grub-arm64-efi and then issue the command grub-install --target=arm64-efi --efi-directory=/boot/efi --bootloader-id="Void" --no-nvram. Note the --no-nvram because for some reason EFI variables are not available to me in UTM.

9- After the xbps-reconfigure -fa command, I exit and them attempt to unmount using umount -R /mnt only to be told that the device is busy. Using lsof returns nothing so I shutdown, remove the live Arch Linux image, and boot the system again only to be greeted with the UEFI shell.

I am not sure where my issue is and I would appreciate any help, advice, and/or guidance anyone can provide.

Thank you

2

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 wrote this guide with a lot of help from two other people, including /u/neo@lemmy.comfysnug.space. It’s available on our community wiki, https://wiki.comfysnug.space. As with all pages on our wiki, it’s licensed under Creative Commons Attribution-ShareAlike 4.0, meaning you’re free to share, remix, and build on the content as long as you credit us. > > We also have some other pages you may find useful: > > * If you're looking for something to play, check out our Recommendations page. > * If you want to know where and how to buy a visual novel you want to play, our comprehensive Buying page will help you out. > * And if you want to read a visual novel in Japanese, our Reading in Japanese page offers a lot of advice and points you to some useful software to make the process easier. >

2