Hello.
I’m wondering why the boot image of OSMC is a lower resolution on Vero 2 than on Vero?
Looks like its 480p or lower.
Can you explain a little more, perhaps with a photo?
U-Boot will pass the suggeste video mode to the kernel which will then be used. Usually this is 720p or 1080p.
Sam
You don’t see it clearly on a photo, but if you take a look at the “R”, you can see it.
It was at least 720p on Vero, as I didn’t see pixels as I do now on Vero 2.
Do you only see this issue on the splash screen?
What does cat /proc/cmdline show?
Sam
Yes.
osmc@osmc:~$ cat /proc/cmdline
init=/init console=ttyS0,115200n8 no_console_suspend storage=1 vdaccfg=0xa000 logo=osd1,loaded,0x7900000,720p50hz,full hdmimode=720p50hz cvbsmode=576cvbs androidboot.firstboot=0 hdmitx= mac=08:61:60:11:26:64 console=tty0 consoleblank=0 osmcdev=vero2 root=/dev/vero-nand/root hdmitx=cecf quiet
-Andreas
You have a 720p TV?
It may be a scaling issue with ply-lite. I will check it out. If it’s only affecting splash, then I wouldn’t worry about it for now.
Sam
No, I have a 1080p TV.
Ok, so a reinstall of the system won’t fix the issue?
No, I don’t believe so.
It seems that U-Boot believes the preferred video mode of your device is 720p50. It would be good if you could run the following commands to confirm whether the kernel also believes this:
cat /sys/class/amhdmitx/amhdmitx0/edid
cat /sys/class/amhdmitx/amhdmitx0/disp_cap
If you have an AVR, you may wish to connect directly to the TV temporarily. It’s possible it’s giving the device the incorrect EDID.
Sam
Vero 2 is, and has always been, connected directly do my TV (Sony KDL-50W805B), the first Vero was too.
osmc@osmc:~$ cat /sys/class/amhdmitx/amhdmitx0/edid
Receiver Brand Name: SNY
Receiver Product Name: SONY
EDID block number: 0x1
blk0 chksum: 0x8a
Source Physical Address[a.b.c.d]: 2.0.0.0
native Mode f0, VIC (native 255):
ColorDeepSupport b8, MaxTMDSClock 45
31 16 20 5 19 4 32 34 60 62 18 22 3 7 17 21 2 6 1
Audio {format, channel, freq, cce}
{1, 5, 7, 7}
{2, 5, 7, 0}
Speaker Allocation: f
Vendor: c03
Rx 3D Format Support List:
{VIC FramePacking TopBottom SidebySide}
{ 31 0 1 1 }
{ 16 0 1 1 }
{ 20 1 1 1 }
{ 5 1 1 1 }
{ 19 0 1 1 }
{ 4 0 1 1 }
{ 32 0 1 1 }
{ 34 1 1 1 }
{ 60 1 1 1 }
{ 62 1 1 1 }
{ 18 0 1 1 }
{ 22 0 1 1 }
{ 3 0 1 1 }
{ 7 0 1 1 }
{ 17 0 1 1 }
{ 21 0 1 1 }
{ 2 0 0 0 }
{ 6 0 0 0 }
{ 1 0 0 0 }
osmc@osmc:~$ cat /sys/class/amhdmitx/amhdmitx0/disp_cap
480i
480p
576i
576p
720p
1080i
1080p
720p50hz
1080i50hz
1080p50hz
1080p24hz
-Andreas
There should be an asterisk beside one of the modes on the output of the second command next to the TV’s preferred mode.
Your TV is not reporting a native/preferred mode. Because of this we default to 720p.
This doesn’t stop you selecting 1080p in Kodi however, so it only affects the resolution of the boot screen.
The program that displays the boot screen does not do high quality scaling so any boot resolution besides 1080p will cause the word OSMC to look a bit jaggy.
There is no asterisk beside any of the info I get when I run the command “cat /sys/class/amhdmitx/amhdmitx0/disp_cap”.
Not sure if I really understood if I was supposed to do something or check something with what you said in the first sentence.
Ok, thanks for the explanation. Kodi set this info automatically:
Settings - System info - Video - “Screen resolution: 1920x1080@60.00Hz - Full screen”.
Settings - System - Video output - “Resolution 1920x1080p”, “Refresh rate 60.00”.
If I understood everything correctly - All is working as intended, and nothing is wrong, beside the splash screen of course, but that wont affect the viewing experience of movies and tv-shows?
The problem is my TV, but it’s nothing to do about it?
The lack of asterisk means your TV lists what modes it supports, but doesn’t say what one is optimal. As such we just boot in 720p. When Kodi starts, the resolution gets changed to 1080p
Nothing to worry about as @DBMandrake says
Sam
