Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #63749 > unrolled thread

Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen 積丹尼 Dan Jacobson <jidanni@jidanni.org> - 2019-04-02 16:50 +0200
    Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen Ben Hutchings <ben@decadent.org.uk> - 2019-04-03 01:00 +0200
      Processed: Re: Bug#926149: AMD: Add nomodeset kernel parameter to  avoid black screen "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-04-03 01:00 +0200
      Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen 積丹尼 Dan Jacobson <jidanni@jidanni.org> - 2019-04-03 04:20 +0200
        Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen Ben Hutchings <ben@decadent.org.uk> - 2019-04-03 15:40 +0200
          Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen 積丹尼 Dan Jacobson <jidanni@jidanni.org> - 2019-04-04 03:40 +0200
            Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen Ben Hutchings <ben@decadent.org.uk> - 2019-04-04 17:20 +0200
              Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen 積丹尼 Dan Jacobson <jidanni@jidanni.org> - 2019-04-05 14:20 +0200
              Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen 積丹尼 Dan Jacobson <jidanni@jidanni.org> - 2019-04-07 05:00 +0200
                Processed (with 2 errors): Re: Bug#926149: AMD: Add nomodeset  kernel parameter to avoid black screen "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-04-07 05:10 +0200
              Bug#925891: AMD/ATI Carrizo driver incorrectly detected 積丹尼 Dan Jacobson <jidanni@jidanni.org> - 2019-04-07 05:20 +0200
                Processed: AMD/ATI Carrizo driver incorrectly detected "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-04-07 05:20 +0200
          Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen 積丹尼 Dan Jacobson <jidanni@jidanni.org> - 2019-04-04 06:20 +0200

#63749 — Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen

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

[toc] | [next] | [standalone]

#63752

[Multipart message — attachments visible in raw view] — view raw

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=logs.gz;msg=50

I wish you would just provide the information inline, but anyway that
does answer the question:

00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev e6)
	Subsystem: ASUSTeK Computer Inc. Device [1043:8719]

Ben.

-- 
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
                               A fail-safe circuit will destroy others.

[toc] | [prev] | [next] | [standalone]

#63753 — Processed: Re: Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen

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://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925891
926149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926149
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#63754

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 snappy graphical install interface, crisp
non-graphical rescue shells etc. ... but then the system that it
installs oddly cannot deal with that hardware anymore? (Black screen.)

Note the whole experiment was done offline as to reduce outside
interference in isolating the problem.

[toc] | [prev] | [next] | [standalone]

#63758

[Multipart message — attachments visible in raw view] — view raw

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 Computer Inc. Device [1043:8719]
> 
> giving nice splash screens, a snappy graphical install interface, crisp
> non-graphical rescue shells etc. ... but then the system that it
> installs oddly cannot deal with that hardware anymore? (Black screen.)

The installer normally uses a dumb framebuffer driver (probably efifb
on this system) that is built into the kernel.  This is too low-
performance for a proper desktop.

Ben.

> Note the whole experiment was done offline as to reduce outside
> interference in isolating the problem.
-- 
Ben Hutchings
Q.  Which is the greater problem in the world today,
    ignorance or apathy?
A.  I don't know and I couldn't care less.

[toc] | [prev] | [next] | [standalone]

#63768

>>>>> "BH" == Ben Hutchings <ben@decadent.org.uk> 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 intends to write to the installation really will work, by telling the
user:

"5 seconds please, while we test your framebuffer ability."

During which it could launch its proposed framebuffer,
see if /proc/sys/.../{voltage or number of lit pixels, etc.} has
suddenly dropped to zero, indicating a black screen, and then back out
of that choice. Or simply ask the user "in a moment you will be asked if
you saw a black screen".

Anyway, if the installer thinks a certain video mode is so cool that it
sets it up as what will be used when the new system boots, then why
doesn't the installer try a "taste of its own medicine," and use it
right away when running the graphical and non-graphical interactive
installs. I mean if it is so confident that it will work...

Or the kernel itself certainly should have a way to do "OK, for the next
operation, check if it has made the screen (which was not black) now
become suddenly black? If so, back out."

Anyway certainly
https://lists.opensuse.org/opensuse-factory/2011-09/msg00732.html
has it right at least about the *2nd (recovery mode) grub entries*.
They should certainly have nomodeset added!

[toc] | [prev] | [next] | [standalone]

#63772

[Multipart message — attachments visible in raw view] — view raw

On Thu, 2019-04-04 at 09:22 +0800, 積丹尼 Dan Jacobson wrote:
> > > > > > "BH" == Ben Hutchings <ben@decadent.org.uk> 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 intends to write to the installation really will work, by telling the
> user:
> 
> "5 seconds please, while we test your framebuffer ability."
> 
> During which it could launch its proposed framebuffer,
> see if /proc/sys/.../{voltage or number of lit pixels, etc.} has
> suddenly dropped to zero, indicating a black screen, and then back out
> of that choice. Or simply ask the user "in a moment you will be asked if
> you saw a black screen".
[...]

There is generally no way to back out of changing the framebuffer
driver, other than to reboot.  So we would have to implement some
ability for the installer to checkpoint its progress and then continue
after a reboot.  I suspect that that would require a pretty major
architectural change and is unlikely to happen any time soon.

However it might be reasonable to add "nomodeset" to the command line
in GRUB's "recovery" boot menu items.

Ben.

-- 
Ben Hutchings
Any smoothly functioning technology is indistinguishable
from a rigged demo.

[toc] | [prev] | [next] | [standalone]

#63774

> 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 to help you finish testing before I
finish installing my system and thus will not be able to help anymore.

[toc] | [prev] | [next] | [standalone]

#63788

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 <ben@decadent.org.uk> writes:

BH> However it might be reasonable to add "nomodeset" to the command line
BH> in GRUB's "recovery" boot menu items.

[toc] | [prev] | [next] | [standalone]

#63789 — Processed (with 2 errors): Re: Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen

Processing commands for control@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 merged with others. Use an existing clone.

> retitle -1 [AMD/ATI] Carrizo driver incorrectly detected
Failed to set the title of -1: The 'bug' parameter ("-1") to Debbugs::Control::set_title did not pass regex check
.

> retitle 926149 Add nomodeset kernel parameter for recovery boot grub entry
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
Changed Bug title to 'Add nomodeset kernel parameter for recovery boot grub entry' from 'AMD: Add nomodeset kernel parameter to avoid black screen'.
Changed Bug title to 'Add nomodeset kernel parameter for recovery boot grub entry' from 'Debian Black Screen of Death worse than Microsoft's Blue Screen of Death'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
925891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925891
926149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926149
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#63790 — Bug#925891: AMD/ATI Carrizo driver incorrectly detected

unmerge 925891
retitle 925891 AMD/ATI Carrizo driver incorrectly detected?
thanks

Now making the incorrect driver detection a separate issue.

All I know is with that minimal install, it somehow assumes the correct
driver is present, or it is, but it uses it wrong. See also
https://wiki.debian.org/AtiHowTo . Anyway the result is a successful
install, but a black screen upon boot.

I'm delaying completing my installation so I can help somebody fix this.
I can work around it myself.
Just tell me when you don't need my help anymore for testing the
installer on this, so I can proceed with my installation. Thanks.

[toc] | [prev] | [next] | [standalone]

#63791 — Processed: AMD/ATI Carrizo driver incorrectly detected

Processing commands for control@bugs.debian.org:

> unmerge 925891
Bug #925891 [src:linux] Add nomodeset kernel parameter for recovery boot grub entry
Bug #926149 [src:linux] Add nomodeset kernel parameter for recovery boot grub entry
Disconnected #925891 from all other report(s).
> retitle 925891 AMD/ATI Carrizo driver incorrectly detected?
Bug #925891 [src:linux] Add nomodeset kernel parameter for recovery boot grub entry
Changed Bug title to 'AMD/ATI Carrizo driver incorrectly detected?' from 'Add nomodeset kernel parameter for recovery boot grub entry'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
925891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925891
926149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926149
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#63769

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web