Hi Petter, [Ouch, this mail became rather long, with several attachments, so it will probably not reach debian-boot]
Am 6. März 2021 15:24:31 MEZ schrieb Petter Reinholdtsen <p...@hungry.com>: >You are looking at the wrong tool, I suspect. The firmware installer >script (aka isenkram-autoinstall-firmware) will report packages with >firmware requested by kernel modules, that is true. > >But the isenkram-lookup script (and its friends isenkram-pkginstall, >isenkramd and its tasksel 'isenkram-packages' task) will use PCI, USB >and other modalias matches to locate packages, which seem more in line >with what you want. OK, so there might still be some hope :-) >The mappings come both from a list provided by the isenkram package, >and >from appstream data provided by each individual package in the Debian >archive. In other words, one do not need to update isenkram to >recognize a new package, and isenkram do not need to wait for all [..] So, calling isenkram-lookup inside of the installer gives me a list of packages, suitable to my hardware as it seems :-) However, it does NOT list 'firmware-amd-graphics', which is needed by my Radeon graphics card :-(( But see below. >> Since the usb.ids database is included into isenkram, I wonder if >> doing similar for pci.ids could help us here? > >Is the usb.ids file really included in isenkram? I thought isenkram >dependend on an external package for both USB and PCI vendor and model >names? Where did you find it? Hmm, maybe I was somewhat unclear. I should have better wrote something like "There seems to be some functionality integrated in isenkram to use IDs from USB devices." There is the /usr/lib/python3/dist-packages/isenkram/usb.py script in isenkram-cli package, and isenkram-cli depends on usb.ids package (and NOT on pci.ids package). This is what made me think "There is some function specific for USB, which works via hardware device IDs, but not for PCI." Doing some further tests on my Thinkpad T60, this time NOT inside of the installer environment, but after rebooting in the newly installed Debian system! This machine has an AMD/ATI RV515/M52 [Mobility Radeon X1300] graphics card built in. [[[[[ Please find some lspci output from that machine attached in "lspci.output". ]]]]] Calling isenkram-lookup, shows the same output as stated above (no entry for the graphics card). [[[[[ Please find the output of isenkram-lookup from that machine attached in ]]]]] [[[[[ "isenkram-lookup.output". ]]]]] Then I called 'cat $(find /sys -name modalias) | sort -u' (I found that command in the manpage of isenkram-lookup). [[[[[ Please find the output of above find from that machine attached in ]]]]] [[[[[ "find-modalias.output". ]]]]] Next, I executed 'isenkram-pkginstall'. A long list of binary/firmware files came up, with the informal line "info: locating packages with the requested firmware files" Then, the machine seemed to hang for about 25 minutes! top showed, that there were many appstreamcli processes running (like 'appstreamcli what-provides firmware:runtime radeon/CAYMAN_me.bin'). Then I called tasksel and selected the new entries generated by isenkram (Hardware specific packages (autodetected by isenkram and Hardware specific firmware packages (autodetected by isenkram). That lead to the same hanging machine again, as above, again for ~25 minutes. After that, the informal line was ’info: No new firmware package with requested firmware detected.’ [[[[[ Please find the output of above tasksel command attached in ]]]]] [[[[[ "tasksel.output". ]]]]] So, in summary, burned the CPU for nearly an hour without result! 'firmware-amd-graphics' was still not installed!!! I assume there is still something wrong, at least with this firmware-amd-graphics package? (I have no nvidia-containing machine here, so I'm unable to test the status there.) Hopefully, you don't get angry with me for this big piece of mail :-| Regards Holger -- Holger Wansing <hwans...@mailbox.org> PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
lspci.output
Description: Binary data
isenkram-lookup.output
Description: Binary data
find-modalias.output
Description: Binary data
tasksel.output
Description: Binary data
