Posts: 148
Joined: Aug 2011
Reputation:
3
Regarding EDID, which is the recommended option... edit xorg or edit grub?
Posts: 23,308
Joined: Aug 2011
Reputation:
1,077
fritsch
Team-Kodi Developer
Posts: 23,308
2016-08-04, 19:43
(This post was last modified: 2016-08-04, 19:49 by fritsch.)
As xorg does absolutely nothing for intel, guess :-)
For the other poster: check the manual x11-common and especially the x11 legacy permissions.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 23,308
Joined: Aug 2011
Reputation:
1,077
fritsch
Team-Kodi Developer
Posts: 23,308
That howto is not complete. I posted another one including changing the initramfs somewhere else.
Remember: display off means no handshake. This is by design. It's like unplugging cable and complaining to see no image. The edid overwriting is no bugfix but a workaround.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 168
Joined: Sep 2013
I'm a little confused.
With sudo systemctl start kodi it starts by default with a reboot already.
So what is the advantage of using sudo systemctl enable kodi.service?
Posts: 23,308
Joined: Aug 2011
Reputation:
1,077
fritsch
Team-Kodi Developer
Posts: 23,308
Nothing ... it's the most laziest workaround I have ever seen proposed :-) you save to reboot if you switch on your TV late, but other workarounds (drm_kms_helper and so on are better suited). See the LibreELEC / OpenELEC wiki for a beginner's howto on cpio contained workaround.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 168
Joined: Sep 2013
Thank you.
I will read up on the guide.
Posts: 11
Joined: Aug 2016
Reputation:
0
maurer
Junior Member
Posts: 11
2016-08-06, 06:43
(This post was last modified: 2016-08-06, 06:44 by maurer.)
thanks for the info
I've managed to fix my first (and worst) issue - system starts X with display off following second post tutorial link.
I've enabled kodi service but it still doesn't start correctly - it enters failed state and can't seem to find the log why
Do you have yours auto starting ?
Posts: 23,308
Joined: Aug 2011
Reputation:
1,077
fritsch
Team-Kodi Developer
Posts: 23,308
How about posting the logfiles (all of them) including dmesg | pastebinit the first post wants?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 309
Joined: Jan 2010
Reputation:
1
Fritsch, what I do not understand (honestly, please explain if you would). is that in your previous link for edid you post Ubuntu needs a workaround for initramfs.
However I read somewhere else that you have during boot late and early binding of edid.
With just the grub line added you will have late KMS binding. With ramfs you have an early binding. Why would you want early binding?
I am certainly no expert and all I know is just by googling... Realy appreciated if you could clarify.
Posts: 23,308
Joined: Aug 2011
Reputation:
1,077
fritsch
Team-Kodi Developer
Posts: 23,308
Quite easy:
- Try it and check with dmesg | pastebinit to spot the difference
You will realize that the first time drm_kms_helper searches for the edid file it can't access it. At the time of writing the Braswells did not (!) enable the video output at all if there was no faked edid connected at this early stage, that's why it is there. This is btw. what I am using here in my living room.
So, just check what happens if you boot without TV attached and compare with and without "early binding".
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.