Posts by Da Flex

PS: Plan: Check the ext4 partition (GParted), reformat the ext4 partition (GParted), then try to reinstall LE on that partition.

GParted can check your fat32 and ext4 partitions. You can run it from CD or USB stick.

It would be helpful to have a complete list of your UUID's. I mean all partitions of all your storage devices, including the installation USB stick.

Quote from Darkyputz

What do you say?

That could be the two partitions from your screenshots. If you don't see them mounted when running LE, you can probably delete them.

PS: But that's all partitions you have on your SSD, right? So, I would completely reformat the SSD.

PPS: Be sure to unplug all other storage devices.

Quote from alexamend

Now i search for solution to get one GPIO set to high during power on.

That's pretty easy, if you call a Python script from the autostart script. I did that to activate a status LED when LE starts - look here.

You did the right hardware tests. Because it works with your other TV, I think the cause is bad HDMI communication of your Sony TV. You don't have a whitelist in your guisettings.xml, because the Sony TV doesn't transmit the possible screen modes, I guess.

If you would try VGA, there will be no whitelist transmission. If you would try DVI <---> HDMI, it would basically work like HDMI, with no whitelist, too.

I had a conversation with another user without whitelist. At the end I gave him a weird idea, but it's still untested.

Quote from Darkyputz

It is a OCZ Vertex 2 SSD with 64 Gig space

I had it running for years with Kodibuntu...so i assumed it would just work fine with Librelec

It looks like you still have some partitions from your older installation, and LE tries to mount them. Remove those unneeded partitions. If you are not familiar with partition operations, reformat the whole SSD and reinstall LE.

Can you try to play MP3 over USB stick instead of network access?

Which screen resolution do you use when playing MP3?

If you use 4K, your system maybe actually is on it's limit, because the screen grabs all the resources.

Quote from antcj

I know this may be a bit off topic, but a few questions.

is there a reason one cant do the LE upgrade on a USB stick rather than sd?

Regards USB stick, how do they stand up to having an os installed.? I have need to install linux to a new drive yearly (read tax dates) and would like to just swap out old for new, each new fin. year, so keeping that year intact.

To my limited knowledge, USB sticks and SD cards have no big difference in lifetime. They both last long, if they are just read.

If you run Linux on a USB / SD medium, the interesting point is what data Linux writes back to that medium. A Linux system can be configured to write temporary data to the RAM instead of USB / SD. That's good for the lifetime of the medium. I think the Linux of LE does as much as it can to avoid writing data back to the storage medium. That's why I would keep a MicroSD for that special Linux.

Other Linux systems write a lot of temporary data to the permanent storage medium. No problem for SSD, but bad for USB sticks or SD cards.

I have seen a HDMI dummy plug at Amazon. It fakes a connected monitor with a fixed 1920x1080 / 60Hz resolution. If you combine a HDMI splitter with a dummy plug, it would be some kind of a hack.

One output of the HDMI splitter goes to the dummy plug, and the second output goes to the DE-15 <---> HDMI monitor.

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.

Quote from maxagaz

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.00000pstd

You 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.

Quote from maxagaz

/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.

Quote from chewitt

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.

Quote from Darkyputz

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.