Age | Commit message (Collapse) | Author |
|
It was a welcome band-aid for Debian 11 (even if it required some heavy
lifting to work correctly), but becomes unnecessary with Debian 12: we
do have modalias information (as we did for Debian 11) and official
installation images include non-free-firmware packages, so graphics
drivers shouldn't be an issue anymore.
|
|
This is a little more subtle than that: hw-detect only enables the
relevant components, but in practice almost all firmware packages are
from non-free-firmware, so let's keep things simple.
|
|
It would be a shame if users would delete those files and make
hw-detect's job harder.
|
|
Given the way debian-cd's make-firmware-image works, it seems quite
unlikely (even if always possible, lots of changes there lately!) that we
would be missing actual firmware packages, i.e. packages which have a
good-looking name *and* actual firmware files in the expected location.
Sending users on a wild goose chase seems like a waste of everyone's time.
|
|
|
|
Since hw-detect uses modalias information (Debian 11), video drivers will
get noticed by the install-firmware hook even if check-missing-firmware
doesn't see any missing firmware files mentioned in dmesg.
Debian 12 makes it much more likely to find required firmware packages.
|
|
|
|
Start by mentioning a few workarounds that might help log in into the
installed system: nomodeset & Ctrl-Alt-F2.
Document how to use isenkram-cli to automate firmware installation (and
mention what happens so that users are taken by surprise).
Finally, set an `id` for this new subsection so that it can be linked to
directly.
v2: Apply suggestions by Holger Wansing, thanks!
|
|
cover-term, where applicable
|
|
|
|
M en/using-d-i/loading-firmware.xml
|
|
including how to look for “firmware” in dmesg's output. Closes: #695403.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|