Black Screen after update

Help and Support Raspberry Pi
21

tvservice -s
state 0x12001a [HDMI CEA (16) RGB lim 16:9], 1920x1080 @ 60.00Hz, progressive

tvservice -m CEA
Group CEA has 14 modes:
mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive
mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive
mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive
mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive
mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced
(prefer) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive
mode 17: 720x576 @ 50Hz 4:3, clock:27MHz progressive
mode 18: 720x576 @ 50Hz 16:9, clock:27MHz progressive
(native) mode 19: 1280x720 @ 50Hz 16:9, clock:74MHz progressive
mode 20: 1920x1080 @ 50Hz 16:9, clock:74MHz interlaced
mode 31: 1920x1080 @ 50Hz 16:9, clock:148MHz progressive
mode 32: 1920x1080 @ 24Hz 16:9, clock:74MHz progressive
mode 33: 1920x1080 @ 25Hz 16:9, clock:74MHz progressive
mode 34: 1920x1080 @ 30Hz 16:9, clock:74MHz progressive

tvservice -m DMT
mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive
mode 5: 640x480 @ 72Hz 4:3, clock:31MHz progressive
mode 6: 640x480 @ 75Hz 4:3, clock:31MHz progressive
mode 8: 800x600 @ 56Hz 4:3, clock:36MHz progressive
mode 9: 800x600 @ 60Hz 4:3, clock:40MHz progressive
mode 10: 800x600 @ 72Hz 4:3, clock:50MHz progressive
mode 11: 800x600 @ 75Hz 4:3, clock:49MHz progressive
mode 16: 1024x768 @ 60Hz 4:3, clock:65MHz progressive
mode 17: 1024x768 @ 70Hz 4:3, clock:75MHz progressive
mode 18: 1024x768 @ 75Hz 4:3, clock:78MHz progressive
mode 21: 1152x864 @ 75Hz 4:3, clock:108MHz progressive
mode 28: 1280x800 @ 60Hz 16:10, clock:83MHz progressive
mode 32: 1280x960 @ 60Hz 4:3, clock:108MHz progressive
mode 35: 1280x1024 @ 60Hz 5:4, clock:108MHz progressive
mode 36: 1280x1024 @ 75Hz 5:4, clock:135MHz progressive
mode 47: 1440x900 @ 60Hz 16:10, clock:106MHz progressive
mode 48: 1440x900 @ 75Hz 16:10, clock:136MHz progressive
mode 51: 1600x1200 @ 60Hz 4:3, clock:162MHz progressive
mode 58: 1680x1050 @ 60Hz 16:10, clock:146MHz progressive

The TV does detect signal but it is blank.
Ok so retropie can mess things up, but I have not had any trouble Before this last update.

22

19:05:39 382.825653 T:1956388864 NOTICE: ARM mem: 496MB GPU mem: 512MB MPG2:0 WVC1:1

This is part of your issue. Are you on a Pi2? Should be no reason to set higher than 256mb on a Pi2. If you are on a Pi B, 144mb should be the spec.

23

I have tried 256 also, no difference…

24

Please give us

paste-log /boot/config.txt
25

Here are my TV results (screen is just black, as if there was a completely black background.)

state 0x12001a [HDMI CEA (16) RGB lim 16:9], 1920x1080 @ 60.00Hz, progressive

Group CEA has 14 modes:
mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive
mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive
mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive
mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive
mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced
(prefer) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive
mode 17: 720x576 @ 50Hz 4:3, clock:27MHz progressive
mode 18: 720x576 @ 50Hz 16:9, clock:27MHz progressive
mode 19: 1280x720 @ 50Hz 16:9, clock:74MHz progressive
mode 20: 1920x1080 @ 50Hz 16:9, clock:74MHz interlaced
mode 31: 1920x1080 @ 50Hz 16:9, clock:148MHz progressive
mode 32: 1920x1080 @ 24Hz 16:9, clock:74MHz progressive
mode 33: 1920x1080 @ 25Hz 16:9, clock:74MHz progressive
mode 34: 1920x1080 @ 30Hz 16:9, clock:74MHz progressive

Group DMT has 19 modes:
mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive
mode 5: 640x480 @ 72Hz 4:3, clock:31MHz progressive
mode 6: 640x480 @ 75Hz 4:3, clock:31MHz progressive
mode 9: 800x600 @ 60Hz 4:3, clock:40MHz progressive
mode 10: 800x600 @ 72Hz 4:3, clock:50MHz progressive
mode 11: 800x600 @ 75Hz 4:3, clock:49MHz progressive
mode 16: 1024x768 @ 60Hz 4:3, clock:65MHz progressive
mode 17: 1024x768 @ 70Hz 4:3, clock:75MHz progressive
mode 18: 1024x768 @ 75Hz 4:3, clock:78MHz progressive
mode 21: 1152x864 @ 75Hz 4:3, clock:108MHz progressive
mode 28: 1280x800 @ 60Hz 16:10, clock:83MHz progressive
mode 32: 1280x960 @ 60Hz 4:3, clock:108MHz progressive
mode 35: 1280x1024 @ 60Hz 5:4, clock:108MHz progressive
mode 36: 1280x1024 @ 75Hz 5:4, clock:135MHz progressive
mode 39: 1360x768 @ 60Hz 16:9, clock:85MHz progressive
mode 47: 1440x900 @ 60Hz 16:10, clock:106MHz progressive
mode 48: 1440x900 @ 75Hz 16:10, clock:136MHz progressive
mode 51: 1600x1200 @ 60Hz 4:3, clock:162MHz progressive
mode 58: 1680x1050 @ 60Hz 16:10, clock:146MHz progressive

26

is this correct?

http://paste.osmc.io/apepuvafef

27

Guys please can I get some help here. I really don’t want to have to rebuild again

28

Hi… are you using NOOBS? If so I think I’ve found the error.

29

nope vanilla OSMC build. What do you think it maybe? I will try anything

30

Sorry I have no clue for you then. My problem was that NOOBS boot partition for OSMC did not get updated and had old files left. I mounted boot partition and copied over Everything from a working vanilla OSMC version and now Everything works again.
Check your boot partition and see so you have version 3.18.13-1 and not 3.18.10-1.

31

The newest version is 4.X.X.X so of course check for that too.

32

I wonder why NOOBS is not working with update function in OSMC. It only writes to NOOBS recovery partition because that is what is mounted, not the one belonging to OSMC partition…

33

I still have version 3.18.13-1 how do I update it?

34

No clues in the logs that you’ve provided so far.

Can you provide the following logs:

paste-log /var/log/apt/term.log
paste-log /var/log/apt/history.log
dpkg -l | grep osmc | paste-log
sudo journalctl | paste-log
df -h | paste-log

If you are still on a 3.18 kernel it means your update failed part way through so hopefully the above will give us enough info to find out what went wrong.

35

Here I have a link to my recovery partition with newest files and kernel for you update. I am pretty sure it will work after you replaced them. Remember to keep your config.txt and cmdline.txt.enter link description here

36

No offence but I’d rather try to troubleshoot and fix this properly than have chewiesw download and overwrite system files from a random source…

If the problem is a partially failed update, with the correct log files it should be possible to fix with the correct apt commands.

37

http://paste.osmc.io/wojekilere
http://paste.osmc.io/ijomokawux
http://paste.osmc.io/puciniloye
http://paste.osmc.io/iralopicen
http://paste.osmc.io/igiziqafoj

Anyway to restart the update again

38

The problem appears to be that your
/boot partition is not mounted thus the boot loader update fails.

Have you made any changes to /etc/fstab ? Please post a copy of that here:

paste-log /etc/fstab

Thanks.

39

http://paste.osmc.io/nuwiwupiru

40

You’re missing the line for the /boot partition. You didn’t say whether you have made any changes to fstab ?

If not, some software you have installed or run has tampered with your fstab file. Here is an original one:

/dev/mmcblk0p1  /boot    vfat     defaults,noatime    0   0
/dev/mmcblk0p2  /    ext4      defaults,noatime    0   0

Edit the file with the following command:

sudo nano /etc/fstab

Then paste in the missing line, save and reboot. Check with the ‘df -h’ command that you now have a line listing how much free space there is on /boot, then try running updates again by doing the following:

sudo apt-get update && sudo apt-get -f dist-upgrade