Molecular0079 Now • 75%
I've always hated it and thought it was a stupid untuitive mechanic that didn't map to anything in real life. It also looks equally stupid in multiplayer when you see player character models spasm their way up a ledge during a crouch jump. It's an old school mechanic that I am glad is going out of fashion due to better vault controls.
like a simulation of pulling your legs up in real life.
You don't pull your legs up in real life though, you use your hands to vault onto something. You can't just swap stances in mid air without holding onto anything. Even if you were talking about box jumps, like the kinds you normally do at a gym, it still isn't anything remotely like a crouch jump. Also anyone doing a box jump in an actual combat situation just looks goofy.
Any time a game explicitly has a tutorial for crouch jump, my immersion is completely broken. I am instantly reminded that it is a game.
Molecular0079 Now • 100%
Performance parity? Heck no, not until this bug with the GSP firmware is solved: https://github.com/NVIDIA/open-gpu-kernel-modules/issues/538
Molecular0079 Now • 62%
Yeah, it's amazing how upvoted the previous comment is. Just a bunch of idiots jumping on the web-hate bandwagon when even basic media players like Kodi have a tough time playing back video on the Pi.
It just isn't a very optimized device for video playback. The Pi 5 is actually a step backwards as well, providing only H265 hardware video decode which the web doesn't even use.
Molecular0079 Now • 100%
Some people have reported that installing the 32-bit version of mesa libva drivers makes it work for them? Might be worth a shot.
Molecular0079 Now • 100%
Thanks! So VRR works out of the box for you or did you have to do tweaks to get it to work? The answers on the Amazon page are conflicting, with the manufacturer saying VRR is not supported but some users saying it does. Don't know who to believe.
Molecular0079 Now • 100%
It is not necessary to add the nvidia stuff to initramfs. The important part is nvidia_drm.modeset=1.
Molecular0079 Now • 100%
I have the Arctis 7 as well and the default EQ sounds just fine, although I do prefer the Bass Boost. You can run the software inside a Windows VM, passthrough the USB dongle and configure all your settings as well. They get saved into the headset and work just fine in Linux without Linux native software.
Molecular0079 Now • 100%
Usually yes, but it doesn't apply to BG3. The vulkan renderer is terribly broken ever since Patch 3.
Molecular0079 Now • 100%
They borked the Vulkan Renderer somewhere around Patch...3 I think? It used to be so performant, but now it runs only at 40-60fps on my Nvidia 3090 compared to the DX11 renderer which can render at 80-120 T_T
Molecular0079 Now • 100%
Here's the adapter I use: https://www.youtube.com/watch?v=-b6w814wXvc
Did you copy the wrong link? This was a random youtube video.
Good to hear that some adapters do work though. The lack of HDMI 2.1 basically prevented me from ever considering AMD, but if there are converters that work that certainly opens up my options.
Molecular0079 Now • 100%
Yeah, in a Reddit comment, Hector Martin himself said that the memory bandwidth on the Apple SIlicon GPU is so big that any potential performance problems due to TBDR vs IMR are basically insignificant.
...which is a funny fact because I had another Reddit user swear up and down that TBDR was a big problem and that's why Apple decided not to support Vulkan and instead is forcing everyone to go Metal.
Molecular0079 Now • 100%
Do they support VRR though? Last I heard that was still an issue with these converters.
Molecular0079 Now • 100%
Nowadays, I mostly don't even care about compatibility issues anymore and just expect a game to work in Linux, which is just freaking cool. Obviously, some competitive MP games are off the table due to anti-cheat, but that isn't my main gaming category nowadays so it works out.
Molecular0079 Now • 100%
I have a 3090 and just swapped over to the beta 555 drivers and Kwin with explicit sync patches applied (the patches will be available out of the box with Kwin 6.1). Honestly, the Wayland experience is basically flawless now for most cases. The only bug I am experiencing is Steam shows some corruption in the web views on start up until I resize the window, but it's a minor quibble in exchange for getting Wayland. I expect most of the minor remaining issues to be hammered out quickly.
Honestly, I've had genuinely bad experiences with AMD. I hated my unstable Vega 64 that would crash almost every day and was much happier when I finally ditched that card for my 3090. My laptop has a Radeon 680M and that would regularly have hard system hangs, broken video acceleration, etc.
Besides that, I also think being part of the AMD ecosystem is difficult at times. FSR sucks compared to DLSS, raytracing is sub-par, there's no path reconstruction equivalent. From a compute perspective, ROCm is unstable. Even running something as simple as Darktable with ROCm would cause half of each of my photos to not render out properly. Blender with Optix is much faster than Blender with AMD HIP. If you want to do AI, forget AMD as the ecosystem has basically gone with CUDA.
And yeah, the lack of HDMI 2.1 means no 4k 120Hz VRR on a wide variety of displays. Everyone says "why not display port", but it is tough finding a DP capable monitor with the right specs and size sometimes. For example, try finding an equivalent of an LG C2 that has DP. There's only one, its by Asus, and it costs $600 bucks more.
Molecular0079 Now • 100%
A lot of displays don't support DP unfortunately. I have an LG C2 which is perfect for desktop use and one of the more affordable OLED screens out there, and it does not support DP. The PC monitor equivalent that uses the same panel is made by Asus, but that one has a $600 dollar mark up.
Molecular0079 Now • 100%
Yeah but none of that means they're giving up the consumer space. This is all just conjecture.
Molecular0079 Now • 100%
I've heard something about Apple Silicon GPUs being tile-based and not immediate mode, which means the Vulkan API is different compared to regular PCs. How has this been addressed in the Vulkan driver?
Molecular0079 Now • 100%
Huge fucking deal, especially for Nvidia users, but it is great for the entire ecosystem. Other OSes have had explicit sync for ages, so it is great for Linux to finally catch up in this regard.
Molecular0079 Now • 100%
You're correct. While the stable version of KDE Wayland is usable right now with the new driver with no flickering issues, etc., it technically does not have the necessary patches needed for explicit sync. Nvidia has put some workarounds in the 555 driver code to prevent flickering without explicit sync, but they're slower code paths.
The AUR has a package called kwin-explicit-sync, which is just the latest stable kwin with the explicit sync patches applied. This combined with the 555 drivers makes explicit sync work, finally solving the flickering issues in a fast performant way.
I've tested with both kwin and kwin-explicit-sync and the latter has dramatically improved input latency. I am basically daily driving Wayland now and it is awesome.
Molecular0079 Now • 100%
LOL, same. I did a docker-compose pull and restarted, came here to look at the release notes, and almost started panicking whether I omitted some important upgrade steps. Turns out everything upgraded smoothly automatically though.
I've been trying to migrate my services over to rootless Podman containers for a while now and I keep running into weird issues that always make me go back to rootful. This past weekend I almost had it all working until I realized that my reverse proxy (Nginx Proxy Manager) wasn't passing the real source IP of client requests down to my other containers. This meant that all my containers were seeing requests coming solely from the IP address of the reverse proxy container, which breaks things like Nextcloud brute force protection, etc. It's apparently due to this Podman bug: https://github.com/containers/podman/issues/8193 This is the last step before I can finally switch to rootless, so it makes me wonder what all you self-hosters out there are doing with your rootless setups. I can't be the only one running into this issue right? If anyone's curious, my setup consists of several docker-compose files, each handling a different service. Each service has its own dedicated Podman network, but only the proxy container connects to all of them to serve outside requests. This way each service is separated from each other and the only ingress from the outside is via the proxy container. I can also easily have duplicate instances of the same service without having to worry about port collisions, etc. Not being able to see real client IP really sucks in this situation.
On one of my machines, I am completely unable to log out. The behavior is slightly different depending on whether I am in Wayland or X11. Wayland 1. Clicking log out and then OK in the log out window brings me back to the desktop. 2. Doing this again does the same thing 3. Clicking log out for a third time does nothing X11 1. Clicking log out will lead me to a black screen with just my mouse cursor. In my journalctl logs, I see: Apr 03 21:52:46 arch-nas systemd[1]: Stopping User Runtime Directory /run/user/972... Apr 03 21:52:46 arch-nas systemd[1]: run-user-972.mount: Deactivated successfully. Apr 03 21:52:46 arch-nas systemd[1]: user-runtime-dir@972.service: Deactivated successfully. Apr 03 21:52:46 arch-nas systemd[1]: Stopped User Runtime Directory /run/user/972. Apr 03 21:52:46 arch-nas systemd[1]: Removed slice User Slice of UID 972. Apr 03 21:52:46 arch-nas systemd[1]: user-972.slice: Consumed 1.564s CPU time. Apr 03 21:52:47 arch-nas systemd[1]: dbus-:1.2-org.kde.kded.smart@0.service: Deactivated successfully. Apr 03 21:52:47 arch-nas systemd[1]: dbus-:1.2-org.kde.powerdevil.discretegpuhelper@0.service: Deactivated successfully. Apr 03 21:52:47 arch-nas systemd[1]: dbus-:1.2-org.kde.powerdevil.backlighthelper@0.service: Deactivated successfully. Apr 03 21:52:48 arch-nas systemd[1]: dbus-:1.2-org.kde.powerdevil.chargethresholdhelper@0.service: Deactivated successfully. Apr 03 21:52:54 arch-nas systemd[4500]: Created slice Slice /app/dbus-:1.2-org.kde.LogoutPrompt. Apr 03 21:52:54 arch-nas systemd[4500]: Started dbus-:1.2-org.kde.LogoutPrompt@0.service. Apr 03 21:52:54 arch-nas ksmserver-logout-greeter[5553]: qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile Apr 03 21:52:54 arch-nas ksmserver-logout-greeter[5553]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11 Apr 03 21:52:54 arch-nas plasmashell[5079]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0 Apr 03 21:52:55 arch-nas systemd[4500]: Created slice Slice /app/dbus-:1.2-org.kde.Shutdown. Apr 03 21:52:55 arch-nas systemd[4500]: Started dbus-:1.2-org.kde.Shutdown@0.service. Apr 03 21:52:55 arch-nas systemd[4500]: Stopped target plasma-workspace-wayland.target. Apr 03 21:52:55 arch-nas systemd[4500]: Stopped target KDE Plasma Workspace. Apr 03 21:52:55 arch-nas systemd[4500]: Requested transaction contradicts existing jobs: Transaction for is destructive (drkonqi-coredump-pickup.service has 'start' job queued, but 'stop' is included in transaction). Apr 03 21:52:55 arch-nas systemd[4500]: graphical-session.target: Failed to enqueue stop job, ignoring: Transaction for graphical-session.target/stop is destructive (drkonqi-coredump-pickup.service has 'start' job queued, but 'stop' is included in transaction). Apr 03 21:52:55 arch-nas systemd[4500]: Stopped target KDE Plasma Workspace Core. Apr 03 21:52:55 arch-nas systemd[4500]: Stopped target Startup of XDG autostart applications. Apr 03 21:52:55 arch-nas systemd[4500]: Stopped target Session services which should run early before the graphical session is brought up. Apr 03 21:52:55 arch-nas systemd[4500]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Main process exited, code=exited, status=1/FAILURE Apr 03 21:52:55 arch-nas systemd[4500]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Failed with result 'exit-code'.graphical-session.target/stop I've filed an [upstream bug](https://bugs.kde.org/show_bug.cgi?id=485011) for this but I was wondering if anyone else here was also experiencing the same issue.
Currently, I have SSH, VNC, and Cockpit setup on my home NAS, but I have run into situations where I lose remote access because I did something stupid to the network connection or some update broke the boot process, causing it to get stuck in the BIOS or bootloader. I am looking for a separate device that will allow me to not only access the NAS as if I had another keyboard, mouse, and monitor present, but also let's me power cycle in the case of extreme situations (hard freeze, etc.). Some googling has turned up the term KVM-over-IP, but I was wondering if any of you guys have any trustworthy recommendations.
I mean, come on, this has to be a joke right XD
www.phoronix.com
cross-posted from: https://lemmy.world/post/4930979 > Bcachefs making progress towards getting included in the kernel. My dream of having a Linux native RAID5 capable filesystem is getting closer to reality.
www.phoronix.com
Bcachefs making progress towards getting included in the kernel. My dream of having a Linux native RAID5 capable filesystem is getting closer to reality.
Patch 2 seems to have drastically slowed down the Vulkan Renderer. Before I was able to get 80-110FPS in the Druid Grove, but now I am only getting 50fps. DX11 seems fine though, but I prefer using Vulkan since I am on Linux. Arch Linux, Kernel 6.4.12 Ryzen 3900x Nvidia 3090 w/ 535.104.05 drivers Latest Proton Experimental
I am using [one of the official Nextcloud docker-compose files](https://github.com/nextcloud/docker/tree/master/.examples/docker-compose/insecure/mariadb/apache) to setup an instance behind a SWAG reverse proxy. SWAG is handling SSL and forwarding requests to Nextcloud on port 80 over a Docker network. Whenever I go to the Overview tab in the Admin settings, I see this security warning: ``` The "X-Robots-Tag" HTTP header is not set to "noindex, nofollow". This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly. ``` I have X-Robots-Tag set in SWAG. Is it safe to ignore this warning? I am assuming that Nextcloud is complaining about this because it still thinks its communicating over an insecured port 80 and not aware of the fact that its only talking via SWAG. Maybe I am wrong though. I wanted to double check and see if there was anything else I needed to do to secure my instance. **SOLVED:** Turns out Nextcloud is just picky with what's in X-Robots-Tag. I had set it to SWAG's recommended setting of `noindex, nofollow, nosnippet, noarchive`, but Nextcloud expects `noindex, nofollow`.
cross-posted from: https://lemmy.world/post/3989163 > I've been messing around with podman in Arch and porting my self-hosted services over to it. However, it's been finicky and I am wondering if anybody here could help me out with a few things. > > 1. Some of my containers aren't getting properly started up by `podman-restart.service` on system reboot. I realized they were the ones that depended on my slow external BTRFS drive. Currently its mounted with `x-systemd.automount,x-systemd.device-timeout=5` so that it doesn't hang up the boot if I disconnect it, but it seems like Podman doesn't like this. If I remove the systemd options the containers properly boot up automatically, but I risk boot hangs if the drive ever gets disconnected from my system. I have already tried `x-systemd.before=podman-restart.service` and `x-systemd.required-by=podman-restart.service`, and even tried increasing the device-timeout to no avail. > > When it attempts to start the container, I see this in journalctl: > ``` > Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Got automount request for /external, triggered by 3130 (3) > Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Automount point already active? > Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Got automount request for /external, triggered by 3130 (3) > Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Automount point already active? > Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Got automount request for /external, triggered by 3130 (3) > Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Automount point already active? > Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Got automount request for /external, triggered by 3130 (3) > Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Automount point already active? > Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Got automount request for /external, triggered by 3130 (3) > Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Automount point already active? > Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Got automount request for /external, triggered by 3130 (3) > Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Automount point already active? > Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Got automount request for /external, triggered by 3130 (3) > Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Automount point already active? > Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Got automount request for /external, triggered by 3130 (3) > Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Automount point already active? > Aug 27 21:15:46 arch-nas systemd[1]: libpod-742b4595dbb1ce604440d8c867e72864d5d4ce1f2517ed111fa849e59a608869.scope: Deactivated successfully. > Aug 27 21:15:46 arch-nas conmon[3124]: conmon 742b4595dbb1ce604440 : runtime stderr: error stat'ing file `/external/share`: Too many levels of symbolic links > Aug 27 21:15:46 arch-nas conmon[3124]: conmon 742b4595dbb1ce604440 : Failed to create container: exit status 1 > ``` > > 2. When I shutdown my system, it has to wait for 90 seconds for `libcrun` and `libpod-conmon-.scope` to timeout. Any idea what's causing this? This delay gets pretty annoying especially on an Arch system since I am constantly restarting due to updates. > > All the containers are started using `docker-compose` with `podman-docker` if that's relevant. > > Any help appreciated! > > **EDIT:** So it seems like podman really doesn't like systemd automount. Switching to `nofail, x-systemd.before=podman-restart.service` seems like a decent workaround if anyone's interested.
I've been messing around with podman in Arch and porting my self-hosted services over to it. However, it's been finicky and I am wondering if anybody here could help me out with a few things. 1. Some of my containers aren't getting properly started up by `podman-restart.service` on system reboot. I realized they were the ones that depended on my slow external BTRFS drive. Currently its mounted with `x-systemd.automount,x-systemd.device-timeout=5` so that it doesn't hang up the boot if I disconnect it, but it seems like Podman doesn't like this. If I remove the systemd options the containers properly boot up automatically, but I risk boot hangs if the drive ever gets disconnected from my system. I have already tried `x-systemd.before=podman-restart.service` and `x-systemd.required-by=podman-restart.service`, and even tried increasing the device-timeout to no avail. When it attempts to start the container, I see this in journalctl: ``` Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Got automount request for /external, triggered by 3130 (3) Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Automount point already active? Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Got automount request for /external, triggered by 3130 (3) Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Automount point already active? Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Got automount request for /external, triggered by 3130 (3) Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Automount point already active? Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Got automount request for /external, triggered by 3130 (3) Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Automount point already active? Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Got automount request for /external, triggered by 3130 (3) Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Automount point already active? Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Got automount request for /external, triggered by 3130 (3) Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Automount point already active? Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Got automount request for /external, triggered by 3130 (3) Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Automount point already active? Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Got automount request for /external, triggered by 3130 (3) Aug 27 21:15:46 arch-nas systemd[1]: external.automount: Automount point already active? Aug 27 21:15:46 arch-nas systemd[1]: libpod-742b4595dbb1ce604440d8c867e72864d5d4ce1f2517ed111fa849e59a608869.scope: Deactivated successfully. Aug 27 21:15:46 arch-nas conmon[3124]: conmon 742b4595dbb1ce604440 : runtime stderr: error stat'ing file `/external/share`: Too many levels of symbolic links Aug 27 21:15:46 arch-nas conmon[3124]: conmon 742b4595dbb1ce604440 : Failed to create container: exit status 1 ``` 2. When I shutdown my system, it has to wait for 90 seconds for `libcrun` and `libpod-conmon-.scope` to timeout. Any idea what's causing this? This delay gets pretty annoying especially on an Arch system since I am constantly restarting due to updates. All the containers are started using `docker-compose` with `podman-docker` if that's relevant. Any help appreciated! **EDIT:** So it seems like podman really doesn't like systemd automount. Switching to `nofail, x-systemd.before=podman-restart.service` seems like a decent workaround if anyone's interested.
cross-posted from: https://lemmy.world/post/3754933 > While experimenting with ProtonVPN's Wireguard configs, I realized that my real IPv6 address was leaking while IPv4 was correctly going through the tunnel. How do I prevent this from happening? > > I've already tried adding `::/0` to the `AllowedIPs` option and IPv6 is listed as disabled in the NetworkManager profile.
While experimenting with ProtonVPN's Wireguard configs, I realized that my real IPv6 address was leaking while IPv4 was correctly going through the tunnel. How do I prevent this from happening? I've already tried adding `::/0` to the `AllowedIPs` option and IPv6 is listed as disabled in the NetworkManager profile.
So I have been running into a weird issue lately where if I disconnect a Bluetooth audio device, it will remain visible in the KDE audio mixer. Reconnecting the audio device then adds a duplicate entry and the keyboard volume control for it is completely broken. It stays at the same volume. This was working just fine about a week ago and I've already downgraded pipewire, kpipewire, bluedevil, and plasma-pa to no avail. Nothing shows up in the logs, so I don't know exactly what's causing this bug. Anyone else experiencing the same thing? Arch Linux Kernel 6.4.8-arch1-1 Pipewire 0.3.77-1 KDE Plasma: 5.27.7 KDE Frameworks Version: 5.108.0 Qt 5.15.10 **EDIT:** Seems like simply changing the Bluetooth A2DP audio profile causes this issue as well. I have Bluetooth earbuds that have both AAC and SBC modes and toggling between them just creates more and more duplicate devices with the same name. **THE FIX:** Seems like `pipewire-pulse` 0.3.77 was the culprit after all. Downgrade it to pipewire-pulse 0.3.76 and then do a `systemctl --user restart pipewire-pulse` to workaround this issue. **EDIT 2:** pipewire-pulse 0.3.77-2 has the patch backported. Feel free to update to latest version in Arch repos. Relevant bug report: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3414
I tried both Mullvad and Mozilla VPN and when I do a dns test, both are still using my ISP's DNS instead of the VPN's. This only happens on my Arch systems, works fine on my phone. **EDIT:** Turns out these VPN clients depend on systemd-resolved in order to change your DNS. Enabling the service makes it work properly. A bit scary that they don't give you a warning that you're leaking DNS if you don't have systemd-resolved enabled.
I am in the process of making a DIY NAS box and I am debating between mdadm + BTRFS and ZFS. What are your experiences with using ZFS on Arch? Have you run into any major issues? Does ZFS being an external kernel module cause any annoyances with the frequent Arch kernel updates? Give me the dirty details! Any recommendations or pitfalls I should avoid? Thanks!
cross-posted from: https://lemmy.world/post/1313651 > Every time I plug in my Quadcast S USB mic into my Arch Linux box, I can't properly go into deep sleep. Unplugging it before attempting to sleep makes it work again, but its annoying to have to do that every time. How do I debug this and where do I even submit a bug report for this? > > Here's the relevant journalctl: > ``` > Jul 10 11:59:39 systemd[1]: Starting System Suspend... > Jul 10 11:59:39 systemd-sleep[70254]: Entering sleep state 'suspend'... > Jul 10 11:59:39 kernel: PM: suspend entry (deep) > Jul 10 11:59:39 kernel: Filesystems sync: 0.066 seconds > Jul 10 11:59:42 kernel: Freezing user space processes > Jul 10 11:59:42 kernel: Freezing user space processes completed (elapsed 0.001 seconds) > Jul 10 11:59:42 kernel: OOM killer disabled. > Jul 10 11:59:42 kernel: Freezing remaining freezable tasks > Jul 10 11:59:42 kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds) > Jul 10 11:59:42 kernel: printk: Suspending console(s) (use no_console_suspend to debug) > Jul 10 11:59:42 kernel: serial 00:04: disabled > Jul 10 11:59:42 kernel: sd 2:0:0:0: [sdb] Synchronizing SCSI cache > Jul 10 11:59:42 kernel: sd 1:0:0:0: [sda] Synchronizing SCSI cache > Jul 10 11:59:42 kernel: sd 5:0:0:0: [sdc] Synchronizing SCSI cache > Jul 10 11:59:42 kernel: sd 1:0:0:0: [sda] Stopping disk > Jul 10 11:59:42 kernel: sd 2:0:0:0: [sdb] Stopping disk > Jul 10 11:59:42 kernel: sd 5:0:0:0: [sdc] Stopping disk > Jul 10 11:59:42 kernel: ACPI: PM: Preparing to enter system sleep state S3 > Jul 10 11:59:42 kernel: ACPI: PM: Saving platform NVS memory > Jul 10 11:59:42 kernel: Disabling non-boot CPUs ... > Jul 10 11:59:42 kernel: Wakeup pending. Abort CPU freeze > Jul 10 11:59:42 kernel: Non-boot CPUs are not disabled > Jul 10 11:59:42 kernel: ACPI: PM: Waking up from system sleep state S3 > Jul 10 11:59:42 kernel: sd 5:0:0:0: [sdc] Starting disk > Jul 10 11:59:42 kernel: sd 2:0:0:0: [sdb] Starting disk > Jul 10 11:59:42 kernel: sd 1:0:0:0: [sda] Starting disk > Jul 10 11:59:42 kernel: serial 00:04: activated > ``` > > Thanks in advance!
Every time I plug in my Quadcast S USB mic into my Arch Linux box, I can't properly go into deep sleep. Unplugging it before attempting to sleep makes it work again, but its annoying to have to do that every time. How do I debug this and where do I even submit a bug report for this? Here's the relevant journalctl: ``` Jul 10 11:59:39 systemd[1]: Starting System Suspend... Jul 10 11:59:39 systemd-sleep[70254]: Entering sleep state 'suspend'... Jul 10 11:59:39 kernel: PM: suspend entry (deep) Jul 10 11:59:39 kernel: Filesystems sync: 0.066 seconds Jul 10 11:59:42 kernel: Freezing user space processes Jul 10 11:59:42 kernel: Freezing user space processes completed (elapsed 0.001 seconds) Jul 10 11:59:42 kernel: OOM killer disabled. Jul 10 11:59:42 kernel: Freezing remaining freezable tasks Jul 10 11:59:42 kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds) Jul 10 11:59:42 kernel: printk: Suspending console(s) (use no_console_suspend to debug) Jul 10 11:59:42 kernel: serial 00:04: disabled Jul 10 11:59:42 kernel: sd 2:0:0:0: [sdb] Synchronizing SCSI cache Jul 10 11:59:42 kernel: sd 1:0:0:0: [sda] Synchronizing SCSI cache Jul 10 11:59:42 kernel: sd 5:0:0:0: [sdc] Synchronizing SCSI cache Jul 10 11:59:42 kernel: sd 1:0:0:0: [sda] Stopping disk Jul 10 11:59:42 kernel: sd 2:0:0:0: [sdb] Stopping disk Jul 10 11:59:42 kernel: sd 5:0:0:0: [sdc] Stopping disk Jul 10 11:59:42 kernel: ACPI: PM: Preparing to enter system sleep state S3 Jul 10 11:59:42 kernel: ACPI: PM: Saving platform NVS memory Jul 10 11:59:42 kernel: Disabling non-boot CPUs ... Jul 10 11:59:42 kernel: Wakeup pending. Abort CPU freeze Jul 10 11:59:42 kernel: Non-boot CPUs are not disabled Jul 10 11:59:42 kernel: ACPI: PM: Waking up from system sleep state S3 Jul 10 11:59:42 kernel: sd 5:0:0:0: [sdc] Starting disk Jul 10 11:59:42 kernel: sd 2:0:0:0: [sdb] Starting disk Jul 10 11:59:42 kernel: sd 1:0:0:0: [sda] Starting disk Jul 10 11:59:42 kernel: serial 00:04: activated ``` Thanks in advance!
cross-posted from: https://lemmy.world/post/1108366 > I commented on a post a while back and thought I'd check it out again to see if there was any additional discussion. When I clicked into my comment to get to the original post, I realized the post itself had been removed. I'd like to go into the modlog and see why it was deleted but I can only filter by user. Is there a way I could download a text version of the modlog and search for the post id there?