I have just removed the write permission for my guisettings.xml. Unfortunately it has no effect, and the system still overwrites it when I change the resolution by GUI.
Maybe deactivating "hdmi_force_hotplug=1" again avoids overwriting, but I'm not sure.
Do you mean that I should insert manually this line :
Code<setting id="videoscreen.whitelist">0192001080060.00000pstd,0192001080050.00000pstd,0128000720060.00000pstd,0128000720050.00000pstd</setting>
To be precise, insert / edit the content of this XML tag into your existing empty XML tag.
The content is:
0192001080060.00000pstd,0192001080050.00000pstd,0128000720060.00000pstd,0128000720050.00000pstdYou can see four comma-divided values. The relevant numbers are before the point. For value one "0192001080060" is relevant. It means a resolution of 1920x1080 and a vertical frequency of 60Hz. Now you can insert all data, which your screen supports (see your manual).
The selected (in-use) value of the described whitelist is stored here:
<setting id="videoscreen.screenmode" default="true">DESKTOP</setting>The value "DESKTOP" means 720p / 50Hz (last value of my whitelist). You can replace that value by any value of your whitelist.
Hopefully Kodi will not overwrite your edited guisettings.xml (store a backup). If it does, maybe removing the write permission for that file could help.
I have been tried a Raspberry Pi with LE on my DVI monitor, and it worked fine with a DVI <---> HDMI adapter. But maybe your screen simply doesn't send any data from it's DE-15 output to Kodi.
So, what could you do in that case? You could insert the data by yourself. You need to know the resolution and the vertical frequency of your screen. Here is my guisettings.xml. Try to adapt it for your needs.
/storage/.kodi/userdata/guisettings.xml
Thanx. The ".kodi" folder exists, which is good. But the whitelist is empty, which is bad. Usually Kodi automatically insert content into the whitelist (<setting id="videoscreen.whitelist" default="true"></setting>) by receiving data from the connected screen. I think that doesn't work in your setup.
Da Flex .. good luck in running sudo commands in LE (hint: sudo doesn't exist). Please stop offering untested advice.
OK, "blkid" will do it.
Is that normal/part of the setup as it is wanted?
And how do i find out what kind of connection is failing with this message all the time?
No, it's no normal setup. Your screenshots are saying that two partitions can't be mounted (two different UUID's). Plug off / in connected devices to find problematic partitions. Use the "sudo blkid" command on SSH to see which partitions have been mounted successfully.
Analyzing the kodi.log can help a lot when it's about booting problems.
@chewitt:
Yes, I just want to help, that's no bad thing. We are still in theory mode. A ".kodi" folder has to be created at the first run of LE, right? If the permissions don't allow to create the folder, it's a possible cause. Feel free to post your theory about it.
PS: Use Etcher to install LE on MicroSD. It's possible that your current installation has been set wrong read/write permissions, and ".kodi" can't be created when LE runs.
What should I change to fit my screen size (1920x1080) ?
That looks like the untouched version, because "videoscreen.whitelist" is empty. If it's not stored in the ".kodi" folder, than it's just the template, not the version that LE actually uses. That's why I think changing the file doesn't makes sense. Where does it come from, what's the path in LE? If you don't have the ".kodi" folder, updating "guisettings.xml" can't work.
PS: Because Kodi was working with your former setup, it's possible that LE uses more wattage than Win and reduces the output signal of the laptop. Just a theory...
Could be a weak electrical connection between laptop and TV. Maybe a weak output signal of the laptop, bad / too long cable... something like that. On such a weak connection LE can't receive all possible screen resolutions / vertical frequencies.
I'm using the terminal, and "ls -la" doesn't list any hidden files.
That's weird. You can use this on your PC or at SSH login:
find / -name "guisettings.xml" -printI'm not familiar with Mac, but maybe there is an option to see hidden files at the file manager.
@maxagaz:
It's in STORAGE -> .kodi -> userdata.
After the LE installation you'll start with an untouched "guisettings.xml", which seems to work fine. After the first boot the "guisettings.xml" will be updated with a "videoscreen.whitelist" (see XML tag inside the file) fitting to your screen. I think that process fails.
To test my theory, do this:
- make a fresh LE installation on MicroSD
- copy the untouched "guisettings.xml" from MicroSD to your PC
- boot the RPi with LE
- power off RPi by shutdown menu
- remove the MicroSD card and plug it into your PC
- copy the potentially corrupted "guisettings.xml" to your PC (verify it, and maybe post it here)
- replace it by the untouched original
- try to boot the RPi again
It could end up having a DE-15 <---> HDMI issue.
Does the touchscreen work with the other two OS's?
Pooling gpio pin every second is probably very bad idea.
Yes, I think the Python version is more efficient.
