[IwasLegend]

I had Kodi working fine on my RPi 2b in Canada, moved to England and never got it to start again, so I'm guessing it's my Benq monitor, which didn't come wiith nearly enough setup information.

Kernel: Linux 3.18.0-trunk-rpi2 #1 SMP PREEMPT Debian 3.18.5-1~exp1+rpi19 (2015-08-08)
Release: Raspbian GNU/Linux 8 (jessie)
Kodi: 15.2

Debug log


Specifically, I think this part of the debug log:
18:13:23 T:1946181632 DEBUG: EGL initial desktop resolution 1920x1080 (1920x1080) @ 60.00 - Full Screen (1.00)
18:13:23 T:1946181632 DEBUG: EGL get supported modes (1) = 15, prefer_group=1, prefer_mode=10
...
18:13:23 T:1946181632 DEBUG: EGL mode 7: 1920x1080 (1920x1080) @ 60.00 - Full Screen (1.00) N:10
...
18:13:23 T:1946181632 DEBUG: EGL get supported modes (2) = 13, prefer_group=1, prefer_mode=10
...
18:13:23 T:1946181632 DEBUG: EGL mode 10: 1920x1080 (1920x1080) @ 60.00 - Full Screen (1.00) :52
18:13:23 T:1946181632 DEBUG: EGL mode 11: 1600x900 (1600x900) @ 60.00 - Full Screen (1.00) :53
18:13:23 T:1946181632 DEBUG: EGL mode 12: 0x33064 (0x1080) @ 0.00 - Full Screen (inf) :37
18:13:23 T:1946181632 DEBUG: EGL set resolution 0x0 -> 0x0 @ 0.00 fps (2,0) flags:20004 aspect:nan
18:13:23 T:1946181632 ERROR: EGL error in CreateSurface: 300b

The value for mode 12 looks impossible and that "set resolution 0x0" looks onimous!

[dandnsmith]

I think that to get sensible comment you need to say which monitor you have, how it is connected, whether you have anything set in config.txt. Also, did you change monitor from what worked?
I assume that you've been able to SSH in, to get that log.
What else is connected, and perhaps you need a new PSU?

[nickr]

SSH in and stop kodi, then backup guisettings.xml and restart kodi ie

Code:

systemctl stop kodi
mv .kodi/userdata/guisettings.xml .kodi/userdata/guisettings.xml.bkup
systemctl start kodi

Your settings may be stuck on something your monitor doesn't support.

[IwasLegend]

SSH in and stop kodi, then backup guisettings.xml and restart kodi ie

Ah. I was confused for a couple of minutes, because I couldn't see how 'backing up' guisettings could possibly help (and it doesn't need a 'restart' because it never even starts), but you meant 'move out of the way'. I'll give that a shot as soon as I get home.

[popcornmix]

This is suspicious:

Code:

18:13:23 T:1946181632  NOTICE: Found resolution 0 x 0 for display 0 with 0 x 0 @ 0.000000 Hz
18:13:23 T:1946181632  NOTICE: Found resolution 0 x 1080 for display 0 with 0 x 42720 @ 0.000000 Hz
18:13:23 T:1946181632  NOTICE: Found resolution 0 x 600 for display 0 with 0 x 600 @ 0.000000 Hz

Can you grab the edid for me? ssh in and run:

Code:

tvservice -d edid.dat

and get that file to me (e.g. using dropbox or google drive).

[IwasLegend]

Your settings may be stuck on something your monitor doesn't support.

Good idea, but no luck.

[IwasLegend]

Can you grab the edid for me? ssh in and run:

Code:

tvservice -d edid.dat

and get that file to me (e.g. using dropbox or google drive).

Oh, dear. No "tvservice" command here, but I know I've got the edid before, so I'll figure it out.

[IwasLegend]

Oh, look. rpi-update, to get kernel 4.4 and firmware, and now I have an /opt/vc/bin... It's a testament to the Pi that I haven't bothered to update the kernel and firmware in well over a year!

I'll get you that edid as soon as I get back from walking the dog, who has been very patient with me as I swore at my computer...

ETA: I guess I won't. I'm not getting past the rainbow screen booting that firmware. Bedtime, I'll try again tomorrow.

[IwasLegend]

ETA: I guess I won't. I'm not getting past the rainbow screen booting that firmware. Bedtime, I'll try again tomorrow.

Damn, I'm not getting anywhere fixing the boot issue. I'm going to put a clean OS on it ... and trust that my backups of the additions I've made are as complete as they need to be ;-)