/This may or may not be related. I posted this bug back in October
regarding the black screen on nvidia using the weekly build. ///https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971871 / Points to
note: I mostly install "ssh" and "system tools" first, then reboot as a
smoke test. Then I
Cyril Brulebois dixit:
>Lucas Nussbaum (2021-04-24):
>> C) Do nothing and document this in the release notes
>
>As said above, I strongly recommend against this.
Right… what about, add another Plan C…
C) When X won’t work, fail gracefully, show a console login
… and dump the above to Plan D?
Le dimanche 25 avril 2021, 13:18:03 CEST Rebecca N. Palmer a écrit :
> Cyril Brulebois wrote:
> > getting my hands on relevant hardware is in progress
>
> Note that https://lists.debian.org/debian-boot/2021/04/msg00247.html
> implies the affected hardware is _not_ simply "all AMD/ATI or NVidia
On 25/04/21 at 11:04 +0200, Cyril Brulebois wrote:
> > B) In the installer, detect that firmware-amd-graphics or
> > firmware-misc-nonfree should be installed, and either install it (?),
> > or redirect the user to the unofficial installer that includes them.
>
> That could be achieved for an
Cyril Brulebois wrote:
getting my hands on relevant hardware is in progress
Note that https://lists.debian.org/debian-boot/2021/04/msg00247.html
implies the affected hardware is _not_ simply "all AMD/ATI or NVidia
hardware". Do we know of hardware that is reproducibly affected?
YunQiang
[ cc+=-x@ ]
Hi Lucas,
Thanks for your summary, I'm not sure about every single detail, but it
seems to be a good basis for discussion. I might point to it from our
errata page (I didn't have a specific bug report when I wrote the most
recent entries):
Hi,
Lucas Nussbaum wrote (Sat, 24 Apr 2021 11:30:03 +0200):
> With Debian 10, the behaviour was that the installation succeeded
> without installing firmware-* packages, and then, and the first boot, X
> would start in a "degraded" mode (using, for example, the vesa driver).
> The user would
On 24/04/21 at 20:07 +0200, Moritz Mühlenhoff wrote:
> Du schriebst in gmane.linux.debian.devel.release:
> > Lucas Nussbaum writes:
> >> It looks like the three open paths for resolution are:
> >>
> >> A) understand and restore the behaviour from Debian 10, that is, get X
> >> to work in a
Du schriebst in gmane.linux.debian.devel.release:
> Lucas Nussbaum writes:
>> It looks like the three open paths for resolution are:
>>
>> A) understand and restore the behaviour from Debian 10, that is, get X
>> to work in a degraded mode after installation. How it worked with Debian
>> 10 (and
Lucas Nussbaum writes:
> It looks like the three open paths for resolution are:
>
> A) understand and restore the behaviour from Debian 10, that is, get X
> to work in a degraded mode after installation. How it worked with Debian
> 10 (and why it doesn't with Debian 11) is unknown.
>
> B) In the
On 24/04/21 at 09:25 +0200, Holger Wansing wrote:
> Hi,
>
> Cyril Brulebois wrote (Fri, 23 Apr 2021 15:13:15 +0200):
> > D-I Bullseye RC 1 was published a few hours ago. And at the risk of
> > sounding like a broken record: I have *absolutely no guarantee* to
> > have a fix or workaround for the
11 matches
Mail list logo
