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, 02 Sep 2015 00:29:36 +0200 [thread overview]
Message-ID: <871tehojsf.fsf@heimdali.yagibdah.de> (raw)
In-Reply-To: <20150901234602.3263a3c1@hal9000.localdomain> (wabenbau@gmail.com's message of "Tue, 1 Sep 2015 23:46:02 +0200")
<wabenbau@gmail.com> writes:
> lee <lee@yagibdah.de> wrote:
>
>> Hi,
>>
>> I'm getting a black screen during booting, with the last message I can
>> see being that udevevents are being processed.
>>
>> This happens with an NVIDIA GTX770 connected to a 4k display via a
>> display port cable, and only when the monitor is configured to use
>> display port 1.2 rather than 1.1. With 1.1, I can get only 30Hz
>> refresh rate, so I want to use 1.2, which should allow 60.
>>
>> Installed are nvidia-drivers 343.36.
>>
>> Do I need a very special display port cable for this, or what might
>> the issue? Both the graphics card and the monitor should be able to
>> do the full resolution at 60Hz just fine.
>
> You need a DP cable that is able to handle a resolution of 4k@60Hz. Not
> all DP cables can do this.
Hm, I bought this cable today, so I'd think it should be ok --- but I
didn't explicitly specify that it must be one that does 4k@60. I didn't
know I might have to.
Is there any way to tell? The sticker on the package only says DP/DP
2.0m.
> But if you use the cable that is delivered with your monitor, it
> should work for all resolutions/refresh rates as long as it is not
> broken.
Unfortunately, the cable that came with it has a normal size connector
on one end and a small size connector on the other. Both the monitor
and the graphics card require the normal size connector, so I cannot use
that cable. That's why I bought one ...
> Sorry, but I can't say anything about the rest of your questions.
Np; when I don't have the right cable, it'll never work anyway. Now I
know what I need to look into first :)
--
Again we must be afraid of speaking of daemons for fear that daemons
might swallow us. Finally, this fear has become reasonable.
next prev parent reply other threads:[~2015-09-01 22:29 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 [this message]
2015-09-02 1:15 ` wabenbau
2015-09-29 17:58 ` lee
2015-09-29 19:13 ` wabenbau
2015-09-29 23:47 ` lee
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=871tehojsf.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