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


Groups > linux.debian.user > #241909

Re: clean Bullseye install, display disappears after "loading initial ramdisk"

From The Wanderer <wanderer@fastmail.fm>
Newsgroups linux.debian.user
Subject Re: clean Bullseye install, display disappears after "loading initial ramdisk"
Date 2021-11-06 00:20 +0100
Message-ID <DggF3-7sN-1@gated-at.bofh.it> (permalink)
References <DgfJ0-6Uh-9@gated-at.bofh.it> <DgfSF-6Xg-13@gated-at.bofh.it> <Dggvo-7pu-25@gated-at.bofh.it>
Organization This space intentionally left blank.

Show all headers | View raw


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

(Is there a reason why the line after the quote and before your new
text, in both cases where that happened, consisted of a string of 11 tab
characters instead of being empty? I had to delete the tabs manually in
order to avoid having it mess up quoting in this reply.)

On 2021-11-05 at 19:03, Felix Miata wrote:

> The Wanderer composed on 2021-11-05 18:25 (UTC-0400):
> 
>> There's a specific kernel-command-line parameter (on top of
>> 'nomodeset') for disabling KMS with certain types of Intel
>> integrated GPU; I don't remember it off the top of my head, but I
>> believe it involves the string 'i915'.
> 
> Nomodeset disables KMS for all graphics hardware.

While I have no reason to doubt this statement, it doesn't seem to
entirely line up with what I've observed in the real world.

I've encountered cases where specifying just 'nomodeset' didn't make the
system stop attempting to switch to a more-advanced display mode (and go
blank, losing the ability to display at all), but specifying both that
and 'i915.whateveritwas' did.

(With exactly the same live-boot image, on different hardware,
specifying just 'nomodeset' worked just fine. So it wasn't something odd
about the boot environment, or at least not exclusively so.)

>> Disabling kernel modesetting isn't the greatest thing for long-term
>> use, but if it can let you boot, you may be able to use that as a
>> basis for figuring out what other solutions may be possible.
> 
> Nomodeset is primarily intended to be a troubleshooting parameter.
> KMS, which nomodeset disables, is an absolute requirement for
> competent graphics performance from al FOSS drivers supporting AMD,
> Intel and NVidia GPUs, among others.

I figured it'd be something like that, but didn't have the
(sufficiently-recent) direct experience to be able to say for sure.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

clean Bullseye install, display disappears after "loading initial ramdisk" Mark Copper <mlcopper@gmail.com> - 2021-11-05 23:20 +0100
  Re: clean Bullseye install, display disappears after "loading initial  ramdisk" The Wanderer <wanderer@fastmail.fm> - 2021-11-05 23:30 +0100
    Re: clean Bullseye install, display disappears after "loading initial  ramdisk" Felix Miata <mrmazda@earthlink.net> - 2021-11-06 00:10 +0100
      Re: clean Bullseye install, display disappears after "loading initial  ramdisk" The Wanderer <wanderer@fastmail.fm> - 2021-11-06 00:20 +0100
        Re: clean Bullseye install, display disappears after "loading initial ramdisk" Mark Copper <mcopper@straitcity.com> - 2021-11-06 04:10 +0100
    Re: clean Bullseye install, display disappears after "loading initial ramdisk" Mark Copper <mcopper@straitcity.com> - 2021-11-06 18:30 +0100

csiph-web