10-15 secconds black screen during boot

On 2013-06-07 15:26, rbarsoianu wrote:
>
> seeing that log, i suppose it’s something related to the network.
> checking the localmessages log i found this
>
>
> Code:
> --------------------
>
> 2013-06-07T16:14:33.491391+03:00 linux-6xel dhcpcd[1664]: eth0: dhcpcd 3.2.3 starting
> 2013-06-07T16:14:33.491578+03:00 linux-6xel dhcpcd[1664]: eth0: hardware address = 14:da:e9:43:1b:a7
> 2013-06-07T16:14:33.492065+03:00 linux-6xel dhcpcd[1664]: eth0: broadcasting for a lease
> 2013-06-07T16:14:33.678513+03:00 linux-6xel dhcpcd[1664]: eth0: offered 192.168.1.5 from 192.168.1.1
> 2013-06-07T16:14:33.680908+03:00 linux-6xel dhcpcd[1664]: eth0: checking 192.168.1.5 is available on attached networks
> 2013-06-07T16:14:34.684809+03:00 linux-6xel dhcpcd[1664]: eth0: leased 192.168.1.5 for infinity
> 2013-06-07T16:14:34.685134+03:00 linux-6xel dhcpcd[1664]: eth0: adding IP address 192.168.1.5/24
> 2013-06-07T16:14:34.685466+03:00 linux-6xel dhcpcd[1664]: eth0: adding default route via 192.168.1.1 metric 0
> 2013-06-07T16:14:34.921176+03:00 linux-6xel dhcpcd[1664]: eth0: Failed to lookup hostname via DNS: Name or service not known
> 2013-06-07T16:14:35.079563+03:00 linux-6xel dhcpcd[1664]: eth0: exiting
> 2013-06-07T16:14:52.226952+03:00 linux-6xel checkproc: checkproc: can not get session id for process 3593!
>
> --------------------
>
>
> The pause seems to be for exactly 17 secconds between the last 2
> messages

The problem could be that your DHCP server (the router) is giving itself
as the DNS to use - but it fails to answer queries. Thus any network
related service coming up later will fail. If these services are started
while the video is going from one mode to another, screen is black for a
longer period than usual.

The solutions would be to:

  • configure DNS in your router properly. Your router should be using
    the DNS servers provided by your ISP. If these are not working, change
    to other, in the router config.

  • Configure another DNS server in ifup (YaST)

  • Configure another DNS server in network manager.

>
> 2013-06-07T*16:14:35.079563+03:00 linux-6xel dhcpcd[1664]: eth0:
> exiting
> 2013-06-07T
16:14:52.*226952+03:00 linux-6xel checkproc: checkproc: can
> not get session id for process 3593!
>
> Am i on the right track here ? and if so…how can i find what that
> process is ? In top i don’t find any process with PID 3593

Well, that fits with the message.


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

Carlos E. R. wrote:
> set a reasonable period for
> automatic removal (2 months is more than enough)

That is the way to make this thread bitrot

On 2013-06-11 14:56, Dave Howorth wrote:
> Carlos E. R. wrote:
>> set a reasonable period for
>> automatic removal (2 months is more than enough)
>
> That is the way to make this thread bitrot

Maybe, but the thread itself can show if it is relevant or not; and it
is “environment friendly” in not using more resources than needed (at
the paste site). If 2 month is too little, set it to 2 years, by which
time the current releases are all EOL.

The latter the expiry date, the less amount of data you are allowed to
upload there.


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)