0 Followers
0 Following
2 Posts
This worked, Thanks!

How can I unmod myself?

https://lemmy.world/post/5229546

How can I unmod myself? - Lemmy.world

I’d like to unmod myself from [email protected] [/c/[email protected]], but I don’t see any button to do it, and by quick research the actions suggested do not appear for me. I don’t see an option via a comment of mine: [https://lemmy.world/pictrs/image/65808e5d-0178-4b7c-8ec6-9a236cf6c4b4.png] And neither over the sidebar: [https://lemmy.world/pictrs/image/d4307910-0d9d-43bf-b980-83a2a0980e57.png]

Only difference in info I can see is that display name ends with :0 instead of :0.0. Depending on your DE, you might fiddle with display settings there. Are you running X natively and not XWayland?
Already used these drivers on previous installation, was 525 iirc (Linux Mint), but also went from 530 to 535 on Arch and it persisted. Thing is problem started the exact day I also flashed BIOS firmware so it’s likely that it could come from there, but trying lts kernel now

Randomly stuck at "Reboot: Power Down"

https://lemmy.world/post/2749481

Randomly stuck at "Reboot: Power Down" - Lemmy.world

## Symptoms * Complete Freeze after: preparing to enter ACPI S5 state Reboot: Power Down * seemlingly random (can successfully shutdown maybe 10 times in a row, then suddenly freezes again) * seems to happen more often as uptime grows * Case Fans still spin, LEDs and Lights stay on * Monitors stay on, still react to HDMI/DP Hotplugging (unplug/plug) * REISUB/REISUO doesn’t work * Disks are already powered off and disconnected * USB devices (eg. keyboard unresponsive) ## Since When * After switching to Arch and flashing BIOS Firmware 7C88v18 to MSI B460M-A Pro Board * Arch Linux is ruled out by me since it’s very unlikely Userland plays a role, and already used Linux before without the problem * Gone from linux ~6.2.10 to 6.4.8, Kernel bug unlikely ## Attempted: * Reflash 7C88v18 from a FAT32 formatted partition (USB) * Add reboot=pci or reboot=acpi acpi=force to kernel cmdline * run fwupd * Stop X and wait a bit for processes to clear up (???) * intel-ucode is installed: ~> pacman -Qi intel-ucode | head -2 Name : intel-ucode Version : 20230613-1 * Other threads on the Internet seem to have easier reproducibility (always happening), solutions were about either kernel cmdline or outdated kernel (If I didn’t see a thread with my exact problem, apologies) ## Hardware Info ~> pacman -Qi nvidia | head -2 Name : nvidia Version : 535.86.05-8 ~> cat /sys/class/dmi/id/board_* 2>/dev/null Default string B460M-A PRO (MS-7C88) Micro-Star International Co., Ltd. 1.0 ~> LC_ALL=C lscpu | grep -i 'model name' Model name: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz ~> sudo journalctl -k --grep=microcode [...] kernel: microcode: updated early: 0xf0 -> 0xf6, date = 2022-12-26 [...] kernel: SRBDS: Mitigation: Microcode [...] kernel: microcode: Microcode Update Driver: v2.2. ## Misc * Did I just miss something obvious? * I don’t want to go back to an outdated BIOS firmware * lscpu, nvidia-smi and other info added if needed * I have another device (ASUS Board, similar CPU) with similar arch linux setup (nouveau instead of propietary nvidia there), no problems on that device

How to make high refresh rates work in Xorg

https://lemmy.world/post/2338208

How to make high refresh rates work in Xorg - Lemmy.world

This concerns a multi monitor setup with different refresh rates (e. g. 1 with 60hz and 1 with 144hz). The text below is part of the linked article. If you have both nvidia and picom installed, check both sections. ## NVIDIA (propietary) * Open nvidia-settings * Go to ‘X Server Display Configuration’ * In the bottom right, Click on ‘Advanced…’ if it says ‘Advanced…’ * Make sure anything regarding ‘force composition pipeline’ is checked off * Make sure you selected the highest refresh rates possible. You can either select it through the settings, configure it with xrandr or with your DEs Display Settings, is applicable ## picom * Make sure to start picom with --no-vsync ## Misc If it still doesn’t work, try settings these environment variables: CLUTTER_DEFAULT_FPS=<your highest refresh rate> __GL_SYNC_DISPLAY_DEVICE=<your highest refresh rate display> __GL_SYNC_TO_VBLANK=0 Find the DISPLAY_DEVICE name with xrandr | grep connected Add the text block above to /etc/environment (Tip: Use EDITOR=<your editor, if EDITOR is not set anywhere else> sudoedit instead of sudo nano or sudo vim) -> sudoedit /etc/environment

It was from a GitHub Gist but idk which exactly it was, there are multiple. Keep in mind some files need to have copy-on-write deactivated (swapfile, VirtualBox disk images). The Arch Wiki mentions when copy-on-write should be turned off for a file
What do you mean with “birds part”? Learned from YouTube Videos, Arch Wiki, and experimenting on bare metal and in Virtualbox. Hardest part for me when installing Arch 1st time was partitioning and bootloaders

You might install an older kernel version from /var/cache/pacman/pkg and then regenerate the initramfs. If not using NVIDIA, it’s very easy to have multiple kernels installed (e. g. linux, linux-lts) to have another option if one kernel causes trouble.

I’d generally recommend having the lts or mainline kernel additionally if you use custom kernels, like zen or self compiled

In the Gentoo wiki it is also mentioned that “While it is true that Btrfs is still considered experimental and is growing in stability, the time when Btrfs will become the default filesystem for Linux systems is getting closer.”. I don’t know how many distros out there use Btrfs by default (never distrohopped), but it seems to become much more widely adopted than zfs.

wiki.gentoo.org/wiki/Btrfs#Features

Btrfs - Gentoo wiki