[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#991627: marked as done (installation-guide: expand firmware-related documentation)



Your message dated Fri, 30 Jul 2021 19:33:29 +0000
with message-id <E1m9YG9-000Cu2-8c@fasolo.debian.org>
and subject line Bug#991627: fixed in installation-guide 20210730
has caused the Debian Bug report #991627,
regarding installation-guide: expand firmware-related documentation
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
991627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991627
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: installation-guide
Severity: important
X-Debbugs-Cc: debian-release@lists.debian.org, isenkram@packages.debian.org

[ RT and isenkram maintainers in the loop for information ]

Hi,

This bug report is about the first part of the proposal outlined in this
other bug report:
  https://bugs.debian.org/989863

which is trying to be a bit more helpful regarding firmware problems.


Looking at the amd64 documentation, there are several places where
firmware is mentioned:
 - 2.1.5, which basically points at 2.2.
   → https://www.debian.org/releases/bullseye/amd64/ch02s01#gfx
 - 2.2, which pretends graphics cards should work at least minimally
   (which tends not to be true), and which also points at 6.4.
   → https://www.debian.org/releases/bullseye/amd64/ch02s02 
 - 6.4, which documents a number of things.
   → https://www.debian.org/releases/bullseye/amd64/ch06s04


At first glance, I'm proposing:
 - not to change 2.1.5;
 - to amend 2.2, mentioning graphics cards might be problematic, and
   mentioning nomodeset as a possible workaround (plus another pointer
   at 6.4 right after that);
   → https://salsa.debian.org/installer-team/installation-guide/-/commit/09375ab4dfd366560d86bda554cd8d89c8920294
 - to extend 6.4, mentioning nomodeset again (for people who haven't
   seen 2.2 first), as well as an automated way to detect and install
   missing firmware.
   → https://salsa.debian.org/installer-team/installation-guide/-/commit/ed2ec80f30e4a024ed5d061e03251af5f7a28e00

For now, both commits are in a pu/firmware-v0 branch in the installation
guide repository.

I'm not very used to best practices when it comes to end-user doc in
general and to the installation-guide package in general, so I'd be
happy for other to build on those suggested changes, and amend/reword as
required!


Some remarks:
 - There's a copy-paste for the “nomodeset” option, which I suppose
   could be avoided with some include logic. This might avoid duplicate
   works on the l10n front (which might be important due to the next
   point).
 - This is a *possible* workaround, as I have not been able to test it
   (I couldn't reproduce the black screen issue with test hardware). I
   plan to have some kind of survey organized to see if people affected
   by this issue can confirm.
 - 6.4.1 points at `unofficial/non-free/firmware/` which have been made
   to work out of the box (as much as possible) as detailed in #989863,
   but “the archive (tar or zip) on a separate support” use case wasn't
   tackled yet (in particular detecting graphics firmware might be
   required, even if the installer didn't spot that on its own due to
   using generic drivers). I don't think it makes sense to document that
   separately, as we might improve this in a point release, and the
   “nomodeset workaround” + “isenkram procedure” combination should be
   enough to fix things up from the installed system.
 - I documented in a note what happens with that “isenkram procedure”
   since mentioning non-free seemed to be the bare minimum. We might
   skip mentioning contrib though (see earlier note in 6.4.2; the logic
   is exactly the same though — same code!).
 - Documenting what isenkram-autoinstall-firmware does means we should
   check what happens for each major release, to keep up with the
   current implementation. Doing that once every two years doesn't seem
   unreasonable though.


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager989863 -- Release team member -- Freelance Consultant

--- End Message ---
--- Begin Message ---
Source: installation-guide
Source-Version: 20210730
Done: Cyril Brulebois <kibi@debian.org>

We believe that the bug you reported is fixed in the latest version of
installation-guide, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 991627@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cyril Brulebois <kibi@debian.org> (supplier of updated installation-guide package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 30 Jul 2021 20:25:02 +0200
Source: installation-guide
Architecture: source
Version: 20210730
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team <debian-boot@lists.debian.org>
Changed-By: Cyril Brulebois <kibi@debian.org>
Closes: 991627
Changes:
 installation-guide (20210730) unstable; urgency=medium
 .
   [ Holger Wansing ]
   * Remove outdated-translation mark for Japanese.
 .
   [ Cyril Brulebois ]
   * Expand firmware-related documentation (Closes: #991627):
      - Mention rebooting into the installed system can result in a black
        screen or garbled display.
      - Mention possible workarounds (nomodeset, VT switching).
      - Mention an isenkram-based procedure to automatically install
        firmware packages from within the installed system.
   * Refresh README.
 .
   [ Updated translations ]
   * Catalan by d
   * Japanese by YOSHINO Yoshihito
   * Chinese (simplified) by Boyuan Yang <073plan@gmail.com>
Checksums-Sha1:
 ca89ff2102bcc367926e27ba2ba18a4af755919a 2868 installation-guide_20210730.dsc
 7e6486c4f2e241339da315bda6c22958ddcec8da 3750476 installation-guide_20210730.tar.xz
 3ab81f02ed7e78aec149c29c3b878c5acf561a10 6017 installation-guide_20210730_source.buildinfo
Checksums-Sha256:
 31e3dcd1f178c1f9474b37aa6257edc4df2782e05f16618572ca963a84f004af 2868 installation-guide_20210730.dsc
 18f663efc760cbe71e775a8a151428bec8bafaa5947c071f81a33c03c9fdda71 3750476 installation-guide_20210730.tar.xz
 1cbf248e044cb66a2ada489817b72ac5149a603fe2b71d525d10e4a56a3e36e4 6017 installation-guide_20210730_source.buildinfo
Files:
 187480ee15009fbb80e085bd18e86360 2868 doc optional installation-guide_20210730.dsc
 c5bf7802aca7059cda61910b8015131f 3750476 doc optional installation-guide_20210730.tar.xz
 ee8c2f1268115337b872292017e20868 6017 doc optional installation-guide_20210730_source.buildinfo

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

iQJEBAEBCgAuFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmEEUP0QHGtpYmlAZGVi
aWFuLm9yZwAKCRD/kUrwwrNVIATSEAC2RPDoWSsA3UOyhn8k+zSk7MqrrmAuZ+SI
aQor2pyj1rCv7GsIxXYVlFXTLgRO8rXmaFwZQgLVC+Nq6diFUtfEGgvdKN5KUj5G
iIRY23hYG2rhe3S6HMlXr5GopaFkcpDVnSjc4lNZJey+An/sjjaeHsnrpnEP2y9z
v1LpUv0PWWo+2kkiYDUGrZC1B3BE9AVDmBQ2ZSQqeOh1ciaDAwmYIMRW81j0AZuP
7ouMoUPo9YH1MKlowPHehUlB15/17YdLtoBm/7K2MYz01KzMAm94TpquBaBRwyLV
s9OyjkhltSdsOQvuK0wcZiNrlJ6g/T+13DtUXh0u8FAw7hsypMGhi84C2R+5InSk
ZKKMKVWoEpY7AF1hm2r/1dx5Uass2IlgnQeVJKf6Ex51/XetHyFgBacU+cqhYIfU
qtIR0Z7vuUdO2AYAEFxb0kL2bD5TiuB+toctCXG/CAkXNU5z4ijS5mu7upLFdEdG
IyU9F+N33Q8vDuPk4WSm1bHp2Ca6vC+Sj8sZZNZXPH0EULyoOLTJWldPvof6k0AJ
2CL9mTkRo7cIDzmoQpvyw0kTmZb5H0xHlk7WqjJe/H6DNRnfLco9J1+3SvBMH7rG
SGgIywQgTO1UjY8m8FcRirQD7N1wS2iosmlVuqdI4zkTlKGafO6uvvkn+7GHiP2q
z8djJuOOmQ==
=vTWL
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: