Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #63768
| From | 積丹尼 Dan Jacobson <jidanni@jidanni.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen |
| Date | 2019-04-04 03:40 +0200 |
| Message-ID | <xIZwd-3mD-3@gated-at.bofh.it> (permalink) |
| References | (4 earlier) <xIsTD-jq-3@gated-at.bofh.it> <xIAxP-4YN-1@gated-at.bofh.it> <xIDFn-75f-5@gated-at.bofh.it> <xIOhr-4XZ-1@gated-at.bofh.it> <xI0aZ-81g-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
>>>>> "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!
Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
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
csiph-web