Now I'm confused: do you have always seen the syslinux boot screen?
4. Question: Can I type anything at the debug shell to troubleshoot ?
In this case:
Now I'm confused: do you have always seen the syslinux boot screen?
4. Question: Can I type anything at the debug shell to troubleshoot ?
In this case:
Which thread? My web search foo seem not to be good enough to find it.
To shorten this thread I've created an empty legacy boot only image with DOS partitioning scheme. After creating the stick you have to copy the LINUX and SYSTEM files of the desired LE release.
I've no knowledge about the structure of an Ubuntu UUI stick therefore I can't answer this question.
When the Dell heuristic is not accepting the disk layout in legacy boot mode no configuration change can help.
If you succeed in creating an disk image that boot on the Dell into any linux boot loader (e.g syslinux or grub) LibreELEC can be manually added to it.
Now I got it, it is a race between devices. Create
[Unit]
Description=Wait for server
After=time-sync.target
[Service]
Type=oneshot
ExecStart=/bin/sh -c "until ping -c 1 -W 3 192.168.50.12;do sleep 1;done"
ExecStart=/bin/sh -c "until ping -c 1 -W 3 192.168.50.13;do sleep 1;done"
StandardOutput=null
#StandardError=null
RemainAfterExit=yes
and add
to your mount units.
Untested, expect some rough edges.
Development notice: we should use the CIFS debug default. It is a PIA without:
This is executed when opening the Chrome Addon.
Network is up but "No route to host" for 192.168.50.12 and 192.168.50.13.
What is the result of arp -a?
shedrock Chome addon's default.py is accumulating the needed parameters.
A pastekodi is always a good start.
On 9.2.6+ add After=time-sync.target
The easiest work around is to install an empty, not functional addon after having configured anything: Testing LibreELEC-settings addon · Issue #4547 · LibreELEC/LibreELEC.tv · GitHub
Subtitle font selection is at Settings -> player settings -> language. You have to use Expert Level.
Guess: .TTF is not .ttf
It's a question of coltage, not current.
According to the USB 2.0 Standard chapter 7.2.2 the minimal allowed device input voltage is 4.5V if even connected to a high powered host. No HDD/SSD is designed to operate with this.
Always take the time you need. A detailed response is better tan a fast one.
If you still have a copy of the crashing NFO file please post both in the kodi forum. Maybe the crash can be fixed.