public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: lee <lee@yagibdah.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] black screen on boot when udevevents are processed
Date: Wed, 30 Sep 2015 01:47:58 +0200	[thread overview]
Message-ID: <87h9mczt1t.fsf@heimdali.yagibdah.de> (raw)
In-Reply-To: <20150929211333.45b01180@hal9000.localdomain> (wabenbau@gmail.com's message of "Tue, 29 Sep 2015 21:13:33 +0200")

<wabenbau@gmail.com> writes:

> lee <lee@yagibdah.de> wrote:
>
> [...]
>> I finally got a cable that works.  It's from Delock and says 82771 on
>> the back of the package where the EAN code is.  I like it, it seems to
>> be good quality, and most importantly, it works.
>
> Then you really had luck. I had two faulty cables from Delock and I
> decided not to buy a cable from Delock again.

Perhaps you got another model/type?  This one has some sort of fabric
around and the plugs look really good.

>> However, I can see the BIOS and the boot manager menu, then during
>> booting, the screen goes black and the monitor says "no signal"
>> (probably when the nvidia module is loaded).  So I logged in blindly
>> and started X11 and got a picture again.
>> 
>> The monitor info says 4k@60Hz in the BIOS and when X11 is running.  So
>> there must be some setting which causes the graphics card to blank out
>> on the console.
>> 
>> Any idea what that could be?
>
> That's strange. I would understand a message like "Frequencies out of 
> range" or something like that. But "No signal" indicates, that the 
> monitor gets no signal at all. 
>
> What happens when you switch from X to text console (Alt + Strg + F1)?

Oh I hadn't thought of that and just tried:  I'm getting a picture, so I
could use the console now.

Perhaps there's some option for the nvidia module I should use.  I'll
have to look into that ...

Hm, and strange is that I'm pretty sure that I used 'nomodeswitch', yet
that isn't there.  I don't know if that's still required, though.  It
might already fix it.

So I need to read some documentation tomorrow ...


-- 
Again we must be afraid of speaking of daemons for fear that daemons
might swallow us.  Finally, this fear has become reasonable.


  reply	other threads:[~2015-09-29 23:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 18:23 [gentoo-user] black screen on boot when udevevents are processed lee
2015-09-01 21:46 ` wabenbau
2015-09-01 22:29   ` lee
2015-09-02  1:15     ` wabenbau
2015-09-29 17:58       ` lee
2015-09-29 19:13         ` wabenbau
2015-09-29 23:47           ` lee [this message]
2015-10-03 18:17             ` lee
2015-09-02  1:29     ` Fernando Rodriguez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h9mczt1t.fsf@heimdali.yagibdah.de \
    --to=lee@yagibdah.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox