fluidsynth is problematic. It blocked my sound device on every second
boot until I disabled it. And I'm not the only one with that problem see
#1053245
Regards
Axel
I had the same problem and it took me quite some time to find that
fluidsynth was the root cause of this. Fluidsynth was installed as new
dependency from lutris 0.5.14 and blocked my sound device each ~second
boot.
@Patrick I could check the status with "systemctl --user status
fluidsynth" an
Further investigation shows mclk is stuck at lowest frequency so it is
most likely the same bug as reported here:
https://gitlab.freedesktop.org/drm/amd/-/issues/2657
Should be fixed with firmware-nonfree 20200421-1
Should be fixed with firmware-nonfree 20200421-1.
Since we have mesa, libdrm and kernel with Navi 10 support in Debian
now, it would be nice to also have the firmware files available direct.
They were added to the kernel archive at october 23rd
(https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=417a9c6e197a8
gamemode-simulate-game works fine and gamemode -s reports that gamemode
is active. ps aux | grep gamemode returns:
at46 1525 0.0 0.0 13528 3500 ? Ssl 07:55 0:00
/usr/bin/gamemoded -l
at46 18549 0.0 0.0 6548 892 pts/3 S+ 14:28 0:00 grep
gamemode
My system
I updated from unstable via apt to 1.4+git20190722.4ecac89-2 and saw in
the changelog that you re-enabled the daemon. To be sure I rebooted
before I tested again. Unfortunately that didn't fix the automatic
activation of gamemode which made me curious what you've actually
changed. Then I saw th
Just saw that I forgot to update libgamemode0 and libgamemodeauto0. I
did that now rebooted and tried again. Same result. I need to set
gamemoderun %command% as launchoption or gamemode isn't active in RotTR.
Axel
close 911511
thanks
Seems the warnings are gone. Neither with update-initramfs nor with
setupcon I get the "WARNING: Unknown X keysym "dead_belowmacron""
messages anymore.
Axel
I cannot confirm this bug with an AMD Radeon RX 570 4gb. There are no
problems with firmware-nonfree/20190114-1 and launching opengl games.
The problem seems to be more hardware specific or is caused by something
else.
Axel
Hi Jean-Dominique,
are you mixing stable and testing? As far as I can see
Firmware-nonfree/20190114-1 isn't available for stable/stretch. Maybe
you also need to use a newer kernel. The Debian changelog
(https://tracker.debian.org/media/packages/f/firmware-nonfree/changelog-20190114-1)
mention
Bug is fixed with 4.18.13
You are right. Seems to be the same bug. I thought that since everything
works fine without plymouth that it should be fixed there but now I am
not sure anymore. Also I'm not so familiar with debian bug tracker. Can
or should I mark it as duplicate somehow or merge it with your bug report?
Am
15 matches
Mail list logo
