• Re: Bug#1100105: linux-image-amd64: Issues with Framework audio module

    From Uwe =?utf-8?Q?Kleine-K=C3=B6nig?=@21:1/5 to Richard on Tue Apr 8 19:10:02 2025
    XPost: linux.debian.kernel

    Hello Richard,

    On Sun, Mar 30, 2025 at 06:50:26PM +0200, Richard wrote:
    Only rebooting helps. I'm currently trying not use the headphone jack expansion module, but the normal USB C module and a USB C to jack
    adapter I had lying around, that way I can test out if this may be an
    issue with the expansion card. I also had the battery run empty,
    remove SSD, RAM, battery and all modules a few days ago after that was recommended by Framework support, but the results are still not in.

    Maybe it's worth to try to reload the usb bus driver in the broken
    state. Something like:

    # cd -P /sys/bus/usb/devices/usb5/../driver/
    # echo 0000:02:00.0 > unbind
    # echo 0000:02:00.0 > bind

    (where 0000:02:00.0 is a link in the directory that the first command
    cd'd into). Note that

    a) there might be several device links in that directory, try

    ls -ld /sys/bus/usb/devices/usb5

    to determine the right one.

    b) While I expect that the format of the device string matches mine, it
    might also be something completely different.

    c) When unbinding the usb bus driver your USB keyboard might stop
    working. So either do bind and unbind in a single line (and hope that
    binding works again :-), or do that via network (or with a PS/2
    keyboard).

    Does the bookworm kernel work on this machine? You could try that then.
    Or the Ubuntu kernel might be worth a try.

    I would prefer to use a newer Kernel since on one hand features like
    VRR are missing from 6.1 (also I don't even know how far that would
    boot, I did install bookworm originally because at that time the
    Calamares installer was missing from testing ISO, but I think I at
    least updated Kernel and Firmware to backports/upstream) and bookworm-backports is probably still missing quite a lot of fixes for
    various amdgpu issues. And since I'm currently on Kernel 6.14,
    compiled from source based on the config from 6.12.15, I don't know if another Debian Kernel would be enough.


    But yes, trying the Kernel from one of the officially supported Ubuntu
    or Fedora distros was also recommended by the support, so that would
    be Ubuntu 22.04, 24.04 or Fedora 41. With Ubuntu, can I just install
    their .deb package? I would still have to ask Framework support which
    Kernel they recommend, generic seems to be only v6.8 in 24.04, linux-image-generic-hwe-24.04 is v6.11.0, linux-oem-24.04b is another
    version of 6.11.0. Though, because of newer Kernel version, I had
    asked them if they happened to know where I could get sources and
    config for the latest Kernel in Fedora 41, so I could just put that
    through "make bindeb-get" and install that one. But they haven't come
    back to me yet with that one. But if you think that could also be
    worth a try and happen to know where I can get the parts (or can tell
    me where I can get their rpm and install the Kernel with that
    manually), I would try that, at least after verifying the current
    tests.

    I tried installing an Ubuntu (noble) kernel in a Debian 12 VM. While
    this worked and produced a booting system, it pulled in quite some dependencies, so it might get hard to restore an all-Debian system
    afterwards.

    Best regards
    Uwe

    -----BEGIN PGP SIGNATURE-----

    iQEzBAABCgAdFiEEP4GsaTp6HlmJrf7Tj4D7WH0S/k4FAmf1VUgACgkQj4D7WH0S /k6D6AgAmTpWpuI39PYfPgS0vNNXPKz5dAbgTAe75NxSPsBKpgq86EUFxl+5bO1s l0YWwcxhhnamBMz+uFFxQUkutf8y0ER2KKC7Ni8jynhFYby9E2N/GmFzp+9spJxv PpDaEHd7gPyop+ya7PbYN8HdQk289B/6uAC7kMWWfWcewwqZdgLs3vzBa2JhaijH fR2geXbYnbCFelVguX1p6/tJFv6EFog5/eNj1qKhdgfP23Sn9XbYbPvxwUtz2BhI RNFAk5SgDZ7ahOiAyZe3py6X0LgbOflZ89UoT2hJybwbzLZWA1nzl4ElX3TmRKft K9SWxvWKvVwUZDBl7XGpMzXPVvk1Qw==
    =5UwY
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Uwe =?utf-8?Q?Kleine-K=C3=B6nig?=@21:1/5 to Richard on Thu May 29 18:40:02 2025
    XPost: linux.debian.kernel

    On Sun, May 25, 2025 at 04:07:19PM +0200, Richard wrote:
    So, it has been a while, here a little update. As I couldn't figure
    out - and didn't have the time to do so - how to compile Fedora's
    kernel sources with their config through make bindeb-pkg, I didn't
    even bother trying with Ubuntu's kernel. I have now used the Fedora 41
    live USB for the past two weekends and the most part of the past week,
    yet the issue didn't show up once. And since I very much doubt that to
    be a coincidence and the issue just fixed itself, the issue must be
    located in some place inside what Trixie has been shipping for roughly
    the last 6 months (I first reported this in early January to the
    Framework community, but that's just when it became frequent enough
    and had been around already for at least a month if not more, I'd say.

    Which version of the Fedora kernel are you using? Can you test the base version, too? (So if Fedora uses a modified 6.13.7, test on a vanilla
    6.13.7. That allows to determine if there is something in the Fedora
    patch stack that helps or if it's just a different base version that is improved compared to the 6.12.17 kernel that you reported this issue
    against.)

    Best regards
    Uwe

    -----BEGIN PGP SIGNATURE-----

    iQEzBAABCgAdFiEEP4GsaTp6HlmJrf7Tj4D7WH0S/k4FAmg4jDYACgkQj4D7WH0S /k6m2wf/cK7FckWl8glqsqiNrHR/8PIVN92bhev2ejb/9cXzmRs5QEKPvYzj7nWr 3lE1UWtiFUOoS+sw/3TB6oqka+iQXDX726e/xdFeKejFjFQ1UkWTqcbskkaWBhwM +vEKQCb57Dq3lCa3j4luCs8VjEu3QwtvsYI2XoEShJ5x+CLnjJRwHtEXbHN6nPYO C6Nb04hMuRI0vX4MBw99Oh3y0V3LPtIRMZ+gojXKV8Omx+W25mTZJaANDaChSH2t hW0EI+ZbnoEpMrvTAF/9yjxtmFFW4LL/98I00KEJ9OG85x6LFRkGjutJX1ezgu1J 0SrAg1RCKAvSTw/5TvJc7C4Vwxx5Bg==
    =NoF5
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)