[gentoo-user] black screen on boot when udevevents are processed

[gentoo-user] black screen on boot when udevevents are processed

[lee]

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.

Is the nvidia module loaded just at the point when the message about
processing udevevents is shown?  I suspect that the display goes black
when the module is loaded.

When the screen goes black, I can still log in, blindly, after booting
and do a shutdown or reboot, so apparently everything is working except
only having a black screen.


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

Re: [gentoo-user] black screen on boot when udevevents are processed

[wabenbau]

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. 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.

Sorry, but I can't say anything about the rest of your questions.

--
Regards
wabe

Re: [gentoo-user] black screen on boot when udevevents are processed

[lee]

<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.

Re: [gentoo-user] black screen on boot when udevevents are processed

[wabenbau]

lee <lee@yagibdah.de> wrote:

> <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.

It should be certified to DP 1.1a at least.

Excerpt from

https://web.archive.org/web/20140327103747/http://www.displayport.org/faq/

----

Q: Where can I buy a DP 1.2 cable? Most of the cables are certified to DP 1.1a.

A: The DisplayPort version 1.2 standard was designed to utilize the Standard Display cable. We did this intentionally to avoid customer confusion. A DisplayPort cable is a DisplayPort cable; EXCEPT if it a “reduced bit rate” (or RBR) cable, which is typically a 15m cable designed for projector applications, and they only support up to 1080P; OR if it is an active cable, which will not support the new HBR2 rate introduced in the DP 1.2 standard.

So a cable that was tested to meet the DP 1.1a requirments also meets the DP 1.2 requirements.

----

But this is theory. I've made the experience that some cables doesn't 
work with 4k@60Hz although they are so-called 1.1a/1.2 certified. I've 
bought four faulty cables before I found the two that I'm using now. 
One of the faulty cables doesn't work at all at full resolution, the 
others are working but the picture had a lot of errors and was sometimes
black for some seconds.

The two cables which I'm using now are a CROMO 41532 (2m length) and a 
CROMO 41533 (3m length).

Do you have the opportunity to test the cable with some other system,
e.g. some live system (knoppix?) or some windows system? I would do this
first before buying a new cable. 

--
Regards
wabe

Re: [gentoo-user] black screen on boot when udevevents are processed

[lee]

<wabenbau@gmail.com> writes:

> lee <lee@yagibdah.de> wrote:
>
>> <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.
>
> It should be certified to DP 1.1a at least.
>
> Excerpt from
>
> https://web.archive.org/web/20140327103747/http://www.displayport.org/faq/
>
> ----
>
> Q: Where can I buy a DP 1.2 cable? Most of the cables are certified to DP 1.1a.
>
> A: The DisplayPort version 1.2 standard was designed to utilize the
> Standard Display cable. We did this intentionally to avoid customer
> confusion. A DisplayPort cable is a DisplayPort cable; EXCEPT if it a
> “reduced bit rate” (or RBR) cable, which is typically a 15m cable
> designed for projector applications, and they only support up to
> 1080P; OR if it is an active cable, which will not support the new
> HBR2 rate introduced in the DP 1.2 standard.
>
> So a cable that was tested to meet the DP 1.1a requirments also meets the DP 1.2 requirements.
>
> ----
>
> But this is theory. I've made the experience that some cables doesn't 
> work with 4k@60Hz although they are so-called 1.1a/1.2 certified. I've 
> bought four faulty cables before I found the two that I'm using now. 
> One of the faulty cables doesn't work at all at full resolution, the 
> others are working but the picture had a lot of errors and was sometimes
> black for some seconds.
>
> The two cables which I'm using now are a CROMO 41532 (2m length) and a 
> CROMO 41533 (3m length).
>
> Do you have the opportunity to test the cable with some other system,
> e.g. some live system (knoppix?) or some windows system? I would do this
> first before buying a new cable. 

Thank you very much for all the info!

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.

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?


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

Re: [gentoo-user] black screen on boot when udevevents are processed

[wabenbau]

lee <lee@yagibdah.de> wrote:

> <wabenbau@gmail.com> writes:
> 
> > lee <lee@yagibdah.de> wrote:
> >
> >> <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.
> >
> > It should be certified to DP 1.1a at least.
> >
> > Excerpt from
> >
> > https://web.archive.org/web/20140327103747/http://www.displayport.org/faq/
> >
> > ----
> >
> > Q: Where can I buy a DP 1.2 cable? Most of the cables are certified
> > to DP 1.1a.
> >
> > A: The DisplayPort version 1.2 standard was designed to utilize the
> > Standard Display cable. We did this intentionally to avoid customer
> > confusion. A DisplayPort cable is a DisplayPort cable; EXCEPT if it
> > a “reduced bit rate” (or RBR) cable, which is typically a 15m cable
> > designed for projector applications, and they only support up to
> > 1080P; OR if it is an active cable, which will not support the new
> > HBR2 rate introduced in the DP 1.2 standard.
> >
> > So a cable that was tested to meet the DP 1.1a requirments also
> > meets the DP 1.2 requirements.
> >
> > ----
> >
> > But this is theory. I've made the experience that some cables
> > doesn't work with 4k@60Hz although they are so-called 1.1a/1.2
> > certified. I've bought four faulty cables before I found the two
> > that I'm using now. One of the faulty cables doesn't work at all at
> > full resolution, the others are working but the picture had a lot
> > of errors and was sometimes black for some seconds.
> >
> > The two cables which I'm using now are a CROMO 41532 (2m length)
> > and a CROMO 41533 (3m length).
> >
> > Do you have the opportunity to test the cable with some other
> > system, e.g. some live system (knoppix?) or some windows system? I
> > would do this first before buying a new cable. 
> 
> Thank you very much for all the info!
> 
> 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.
 
> 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)?

--
Regards
wabe

Re: [gentoo-user] black screen on boot when udevevents are processed

[lee]

<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.

Re: [gentoo-user] black screen on boot when udevevents are processed

[lee]

lee <lee@yagibdah.de> writes:

> <wabenbau@gmail.com> writes:
>

> [...]
>>> 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?
>>
> [...]
>
> So I need to read some documentation tomorrow ...

Does the nvidia module have any options which can specified when it is
loaded?  I haven't found anything about that in the docs.

Using "nomodeswitch" didn't help; blacklisting the module did help.
That proves that loading the module when not starting X11 makes the
screen go blank.


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

Re: [gentoo-user] black screen on boot when udevevents are processed

[Fernando Rodriguez]

On Wednesday, September 02, 2015 12:29:36 AM lee wrote:
> <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 :)

According to [1] a DP cable is a DP cable, so it should work. The exception is 
if the cable is marked as RBR (Reduced Bit Rate). But depending on the brand 
and where you get it's not unlikely that it's RBR but not marked as such. They 
got a list of certified cables on the last paragraph.

1.http://www.displayport.org/cables/how-to-choose-a-displayport-cable-and-not-get-a-bad-one/
-- 
Fernando Rodriguez