Processing commands for cont...@bugs.debian.org:
> clone 926149 -1
Bug #926149 [src:linux] AMD: Add nomodeset kernel parameter to avoid black
screen
Bug #925891 [src:linux] Debian Black Screen of Death worse than Microsoft's
Blue Screen of Death
Failed to clone 926149: Bug is marked as being mer
clone 926149 -1
retitle -1 [AMD/ATI] Carrizo driver incorrectly detected
retitle 926149 Add nomodeset kernel parameter for recovery boot grub entry
thanks
> "BH" == Ben Hutchings writes:
BH> However it might be reasonable to add "nomodeset" to the command line
BH> in GRUB's "recovery" boot m
> However it might be reasonable to add "nomodeset" to the command line
> in GRUB's "recovery" boot menu items.
OK, great. Now all that is left is for me to help you figure out why
the installer incorrectly detects that the drivers are available, etc.
I am able to workaround all this, I just want
B> However it might be reasonable to add "nomodeset" to the command line
B> in GRUB's "recovery" boot menu items.
OK, great. Now all that is left is for me to help you figure out why
the installer incorrectly detects that the drivers are available, etc.
I am able to workaround all this, I just wa
On Thu, 2019-04-04 at 09:22 +0800, 積丹尼 Dan Jacobson wrote:
> > > > > > "BH" == Ben Hutchings writes:
>
> BH> The installer normally uses a dumb framebuffer driver (probably efifb
> BH> on this system) that is built into the kernel. This is too low-
> BH> performance for a proper desktop.
>
> OK
And lo and behold, in /etc/grub.d/10_linux :
if [ "$ubuntu_recovery" = 1 ]; then
GRUB_CMDLINE_LINUX_RECOVERY="$GRUB_CMDLINE_LINUX_RECOVERY nomodeset"
fi
> "BH" == Ben Hutchings writes:
BH> The installer normally uses a dumb framebuffer driver (probably efifb
BH> on this system) that is built into the kernel. This is too low-
BH> performance for a proper desktop.
OK, the installer could first double check that the framebuffer driver
it inten
On Wed, 2019-04-03 at 10:14 +0800, 積丹尼 Dan Jacobson wrote:
> So the question becomes why does that installer ISO know how to properly deal
> with the
>
> BH> 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
> [AMD/ATI] Carrizo [1002:9874] (rev e6)
> BH> Subsystem: ASUSTeK
So the question becomes why does that installer ISO know how to properly deal
with the
BH> 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Carrizo [1002:9874] (rev e6)
BH> Subsystem: ASUSTeK Computer Inc. Device [1043:8719]
giving nice splash screens, a sna
Control: tag -1 - moreinfo
On Tue, 2019-04-02 at 22:41 +0800, 積丹尼 Dan Jacobson wrote:
> BH> Please send the output of "lspci -vnn" for the system that shows this
> BH> problem.
>
> Would lspci -knn be good enough for now?:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=0;bug=925556;filename=
Processing control commands:
> tag -1 - moreinfo
Bug #926149 [src:linux] AMD: Add nomodeset kernel parameter to avoid black
screen
Bug #925891 [src:linux] Debian Black Screen of Death worse than Microsoft's
Blue Screen of Death
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
--
925891: https
BH> Please send the output of "lspci -vnn" for the system that shows this
BH> problem.
Would lspci -knn be good enough for now?:
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=0;bug=925556;filename=logs.gz;msg=50
Processing control commands:
> reopen -1
Bug #926149 {Done: Ben Hutchings } [installation-reports]
AMD: Add nomodeset kernel parameter to avoid black screen
Bug #925891 {Done: Ben Hutchings } [installation-reports]
Debian Black Screen of Death worse than Microsoft's Blue Screen of Death
Bug reop
13 matches
Mail list logo
