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

Bug#989863: marked as done (debian-installer: Firmware problems in bullseye)

Your message dated Sun, 1 Aug 2021 16:16:56 +0200
with message-id <20210801141656.q6wjzmu4bc24dcbx@mraw.org>
and subject line Re: Bug#989863: debian-installer: Firmware problems in bullseye
has caused the Debian Bug report #989863,
regarding debian-installer: Firmware problems in bullseye
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.)


-- 
989863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989863
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: debian-installer
Severity: important

Hi,

This is an umbrella bug report that I intend to use to track at least
two separate issues (that are really the two sides of the same coin):

 - Official installation images (main-only) might lead to a successful
   installation but result in a black screen upon rebooting the
   installed system. Some of these issues are due to free drivers
   wanting or even requiring some firmware to work properly, on a
   per-device basis.

 - Unofficial installation images (shipping firmware from non-free)
   might also lead to a successful installation but result in the same
   kind of issue due to the way firmware detection is happening.


Please don't turn this bug report into a “firmware packages should have
their own section”, or “firmware packages should be in the installation
images”, etc. If you'd like to change the project's consensus on this,
please follow the appropriate process (see previous firmware GRs). I'm
not speaking for the installer team as a whole, but I would personally
be happy if we could make the life or our users easier in the current
times where escaping non-free is *very* hard. But again, I don't think
we're entitled to making this kind of decision, and that kind of thing
should be discussed with the Debian project as a whole, not here.


This bug report and follow-ups (one bug report for each of those two
issues, which will block this one) are about trying to implement
practical (even if imperfect) solutions for Debian 11.

People wanting to learn about this can refer to Lucas's tentative
summary of earlier threads on mailing lists, and to my reply:
 - https://lists.debian.org/debian-release/2021/04/msg00646.html
 - https://lists.debian.org/debian-release/2021/04/msg00711.html


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

--- End Message ---
--- Begin Message --- 
Cyril Brulebois <kibi@debian.org> (2021-07-28):
> Cyril Brulebois <kibi@debian.org> (2021-07-26):
> > Given Paul's ACK, I'll turn this into a bug report against the
> > installation guide, with a slightly better draft.
> 
> This is my next action.

That was tracked (even if shortly) in #991627, installation-guide was
uploaded to unstable, migrated to testing, and sync'd (automatically
apparently) to the website, as can be seen on those pages:
  https://www.debian.org/releases/bullseye/amd64/ch02s02
  https://www.debian.org/releases/bullseye/amd64/ch06s04

> I'll retest “for real” once packages are in the archive, once I've
> triggered a new d-i daily build, and once debian-cd has spinned another
> firmware-enabled netinst daily build, but besides a possible typo here
> or there, I think I'm out of obvious issues that need fixing!

All that looked good, so we went ahead and started official builds
after:
 1. linux & util-linux migration;
 2. d-i upload + migration + dak copy-installer.

A few hours ago, I described both installations using the tentative
firmware-enabled amd64 image for D-I Bullseye RC 3 as “uneventful”.

Which is what we aim for!

> Besides some builds (hw-detect, cdrom-detect, linux) and some final
> tests (then migration to testing), I think we have all the pieces for
> D-I Bullseye RC 3.

I'm waiting a little so that others on #debian-cd can report back as
well, but it looks like we're almost ready to publish RC 3.

On the firmware front still: I've opened #991771 to keep track of a
slightly different use case (main-only image + manually providing
firmware on extra storage), which doesn't look like it's overly
user-friendly (not much guidance in the installation guide at first
glance) or well-maintained. Definitely not a blocker for Bullseye, it'll
be a bonus if we can improve support for this use case later.


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

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: