11-13-2024, 04:11 AM
(This post was last modified: 10 hours ago by grindstone.)
Sitting on a month-end data-limit right now, personally, so 23.1 core (to be apples-to-apples for RC7) can't happen here today.
Took a (manual) look at package lists for 23.0 core (what I had here already) vs. RC7
- RADEON bits of kernel configs identical
- relevant X libs in core are all in RC7
- core contains 5 more firmware packages than RC7
firmware-amd-graphics
firmware-ast
firmware-linux
firmware-linux-nonfree
firmware-samsung
firmware-linux is the top-level meta package dep on both -free (present already) and firmware-linux-nonfree (not included in RC7). Top-level descriptions are no help and I haven't dug online for details.
At the individual file level (/usr/lib/firmware):
- Something like 3200+ lines in firmware under core, ~2600 RC7 (forgot/bleery)
If memory serves, John has "hand-adjusted" certain firmware for other users but perhaps not installed the entire packages, so conclusions at the package level, on one hand, are an "easy" install+snapshot/remaster away. OTOH, if that works, we still wouldn't know why.
Arguably more sane way to look at packages is to swipe bitjam's "spin" investigation method; for each version, run (redirect to different filenames):
dpkg-query -l | sed -n 's/^ii\s\+//p' > installed-packages.txt
then use the following commands to get lists of added and removed packages:
comm -23 <(sort f.old) <(sort f.new)
comm -13 <(sort f.old) <(sort f.new)
man comm
-> The beauty of you using -core is that it can only be a kernel module and firmware (and radeon.ko and radeonfb.ko are present in core).
-> You already custom-made an image with the firmware-amd-graphics contents, right, and that didn't work. apt-cache show on that package might be the answer:
replaces: firmware-linux-nonfree
which is what was in core but not in RC7. Certainly it's large and that's likely among the reasons why it has been pruned.
Here's some raw (unsorted) stuff for now.
--------------
Edit: I missed the obvious again. What happens if you just swipe all of /usr/lib/firmware from -core runit 23.2 and chuck it in your DSL re-brew?
Took a (manual) look at package lists for 23.0 core (what I had here already) vs. RC7
- RADEON bits of kernel configs identical
- relevant X libs in core are all in RC7
- core contains 5 more firmware packages than RC7
firmware-amd-graphics
firmware-ast
firmware-linux
firmware-linux-nonfree
firmware-samsung
firmware-linux is the top-level meta package dep on both -free (present already) and firmware-linux-nonfree (not included in RC7). Top-level descriptions are no help and I haven't dug online for details.
At the individual file level (/usr/lib/firmware):
- Something like 3200+ lines in firmware under core, ~2600 RC7 (forgot/bleery)
If memory serves, John has "hand-adjusted" certain firmware for other users but perhaps not installed the entire packages, so conclusions at the package level, on one hand, are an "easy" install+snapshot/remaster away. OTOH, if that works, we still wouldn't know why.
Arguably more sane way to look at packages is to swipe bitjam's "spin" investigation method; for each version, run (redirect to different filenames):
dpkg-query -l | sed -n 's/^ii\s\+//p' > installed-packages.txt
then use the following commands to get lists of added and removed packages:
comm -23 <(sort f.old) <(sort f.new)
comm -13 <(sort f.old) <(sort f.new)
man comm
-> The beauty of you using -core is that it can only be a kernel module and firmware (and radeon.ko and radeonfb.ko are present in core).
-> You already custom-made an image with the firmware-amd-graphics contents, right, and that didn't work. apt-cache show on that package might be the answer:
replaces: firmware-linux-nonfree
which is what was in core but not in RC7. Certainly it's large and that's likely among the reasons why it has been pruned.
Here's some raw (unsorted) stuff for now.
--------------
Edit: I missed the obvious again. What happens if you just swipe all of /usr/lib/firmware from -core runit 23.2 and chuck it in your DSL re-brew?