Console output after splash screen after switching to 3b+

[pkscout]

I just got a new 3b+. I confirmed OSMC was completely up-to-date on the RPi3 I had, edited the boot config file with my new MPEG2 and VC1 licenses, shutdown the RPi3 from the Kodi menu, unplugged everything, moved the card to the new 3b+ and then booted everything. Now every time I boot I get some Debian status information over the top of the OSMC splash screen. I know this question has been asked, I found it here:

[Solved] Console output on top of splash screen

Hi there, my problem: Since I rebootet osmc/pi while in EmulationStation via SSH, I get the OSMC splash screen with console output on top of it. Dont know, if this is because of the “hard” reboot, or any other changes I made (and forgot). Following screen is just an example, stolen from the inet - not my actual screen/problem. But I think it will help on understanding my “problem”: [image] Is there any way to fix the splash screen, or supress console/boot messages? I was searching for quite…

Unfortunately that solution didn’t help me any. I’ve looked through the journal log and can’t find anything obviously wrong.

-- Logs begin at Wed 2018-03-21 06:56:11 HST, end at Wed 2018-03-21 06:57:52...

Thanks.

[fzinken]

@pkscout

Now every time I boot I get some Debian status information over the top of the OSMC splash screen.

Take a picture/video of what is displayed.

@pkscout

-- Logs begin at Wed 2018-03-21 06:56:11 HST, end at Wed 2018-03-21 06:57:52 HST - Pastebin.com

Provide full logs via grab-logs -A

[pkscout]

OK, here are all the logs from grab-logs:

https://paste.osmc.tv/cegiselaba

And a couple pictures. The first one is the first message that appears. That clears and then I get what’s in the second image.

Thanks.

[dillthedog]

I can’t say what the root cause it but it seems that there is a hang of 9 seconds while waiting for the eth0 interface to become ready.

Mar 22 05:13:55 KodiPi kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Mar 22 05:13:55 KodiPi connmand[254]: Adding interface eth0 [ ethernet ]
Mar 22 05:13:55 KodiPi connmand[254]: wlan0 {create} index 3 type 1 <ETHER>
Mar 22 05:13:55 KodiPi connmand[254]: wlan0 {update} flags 4098 <DOWN>
Mar 22 05:13:55 KodiPi connmand[254]: wlan0 {newlink} index 3 address B8:27:EB:35:18:7C mtu 1500
Mar 22 05:13:55 KodiPi connmand[254]: wlan0 {newlink} index 3 operstate 2 <DOWN>
Mar 22 05:13:55 KodiPi connmand[254]: Adding interface wlan0 [ wifi ]
Mar 22 05:13:55 KodiPi connmand[254]: eth0 {update} flags 36931 <UP,RUNNING>
Mar 22 05:13:55 KodiPi connmand[254]: eth0 {newlink} index 2 address B8:27:EB:60:4D:29 mtu 1500
Mar 22 05:13:55 KodiPi connmand[254]: eth0 {newlink} index 2 operstate 0 <UNKNOWN>
Mar 22 05:13:55 KodiPi connmand[254]: eth0 {update} flags 36867 <UP>
Mar 22 05:13:55 KodiPi connmand[254]: eth0 {newlink} index 2 address B8:27:EB:60:4D:29 mtu 1500
Mar 22 05:13:55 KodiPi connmand[254]: eth0 {newlink} index 2 operstate 2 <DOWN>
Mar 22 05:13:55 KodiPi connmand[254]: Unit connman-vpn.service not found.
Mar 22 05:14:04 KodiPi connmand[254]: eth0 {add} route fe80:: gw :: scope 0 <UNIVERSE>
Mar 22 05:14:04 KodiPi connmand[254]: eth0 {update} flags 102467 <UP,RUNNING,LOWER_UP>
Mar 22 05:14:04 KodiPi connmand[254]: eth0 {newlink} index 2 address B8:27:EB:60:4D:29 mtu 1500
Mar 22 05:14:04 KodiPi connmand[254]: eth0 {newlink} index 2 operstate 6 <UP>
Mar 22 05:14:04 KodiPi kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

You can see the 9 second hang in the middle.

I don’t have a Pi3+ to test myself but my Pi3, although having different log messages, seems to preform this operation in less than a second. Someone with a Pi3+ will need to see what’s happening.

[sam_nazarko]

Might be related to that report from @penfold42 about the PHY connectivity.

1. Login via the command line
2. Edit the file /etc/apt/sources.list
3. Add the following line: deb http://apt.osmc.tv stretch-devel main
4. Run the following commands to update: sudo apt-get update && sudo apt-get dist-upgrade && reboot
5. Your system should have have received the update.

Please see if the issue is resolved.

I also recommend you edit /etc/apt/sources.list again and remove the line that you added after updating. This will return you to the normal update channel.

[penfold42]

If anything this issue looks closer to the failure I had with the updated kernel (.3 was it?).

The original issue gave me a kernel oops

[pkscout]

So, I have some new information, well kind of new. One thing I neglected to mention is that with my old setup I was using a PoE splitter to power the Pi and provide ethernet. The particular adapter I was using was a 10/100. I decided to take it out of the equation with the 3b+ by pulling out my old power adapter and plugging the ethernet cable directly into the switch. With that, the problem went away without any software update.

So I’m wondering if my issue is that the ethernet adapter was struggling to negotiate with the switch about speed with the 10/100 limiter between them. I suppose it could be power related, but I haven’t gotten a single lightning bolt with either the 3b or 3b+ with this config.

Anyway, I’m going to leave this as is and call it solved. I’m planning on getting the PoE HAT when it comes out, so I can run this way until then.