Posts by milhouse

Crashlogs, that what we need. /storage/.kodi/temp/kodi_crash.log
[hr]

Quote from russellz

I'm having the same problem. I have SSH'd into the frozen and trie TOP to see what is running. Kodi just pops up occasionally on the list so it is starting and then stopping.

Journal: LFNJ
kodi.log: JWLO

Any suggestions appreciated.

Russell

Although in this case, it's pretty clear you have a database issue:

15:52:33.483 T:1962264704   ERROR: SQL: [Addons27.db] SQL error or missing database
                                            Query: SELECT idVersion FROM version

Try:

rm /storage/.kodi/userdata/Database/Addons27.db

and reboot.

For some reason your addon database has failed to migrate. If it continues, try uploading your AddonsXX.db version prior to Addons27.db and paste a link.

Quote from carnivoire

Is there any solution to activate this at startup, or when the network starts?

Try:

echo "net.ipv4.ip_forward = 1" >/storage/.config/sysctl.d/ip_forward.conf

and reboot.

Confirm it is enabled with:

sysctl net.ipv4.ip_forward

and you should see:

net.ipv4.ip_forward = 1

Needs a better solution though, as this is only a band aid.

Yes it's hidden (all files/directories starting with a dot are hidden in Linux). However you can access it with ssh.

No idea about the Mac, sorry.

Quote from phant0mw0rm

Hello!

I'm running LibreELEC on a Raspberry Pi 3.
During the first time setup, in the Internet connection setting, I have chosen my SSID but LibreELEC froze and restarted before asking for the password.

Did the whole device restart (this is very rare) or did only Kodi restart? If the latter you should have a crashlog, so please upload the latest log*.zip in the "Logfiles" share (to dropbox, google drive etc.), and then post the download link.

Quote from phant0mw0rm

Then, the setup continued with the next section (SSH & Samba).
After that, I have tried to go in Settings in order to try to configure the Internet connection again, but the whole WiFi connection part is missing.

Just to be sure it wasn't an hardware issue, I have flashed OpenELEC on the microSD and run the the first time setup: all went good.

Anyway, I'd love to move on LibreELEC, so any help would be appreciated.

Is this using the built-in RPi3 WiFi, or a USB WiFi dongle?

I believe the change/fix is to the smb lock directory. If you're using a clean install of 8.0.1 this probably won't affect you, however just in case please post the contents of /storage/.smb/smb.conf

OpenVPN is included as standard in LibreELEC. There are several guides on the internet that discuss configuring OpenVPN.

Kodi is crashing and won't start, we need to see your crashlog to understand what the issue is. Connect to the "Logfiles" smb share on your "frozen" LibreELEC device and upload the latest log*.zip file somewhere (dropbox, google drive etc.) then paste a download link.

This is a Kodi issue so should be reported there, try creating a ticket on trac.kodi.tv (if there isn't one already).

Quote from DarrenHill

# cat /proc/cpuinfo | pastebinit
cUfN

# vcgencmd otp_dump | pastebinit
FURT

It's a rev1.1 pi zero if that helps (the one without the camera connector or built in WiFi).

Thanks for the help on this by the way

Thanks, that all looks OK (possibly a rev1.2 based on the revision code).

What's odd is that your device is loading "bcm2708-rpi-b-plus.dtb" when it should (I think) be loading "bcm2835-rpi-zero.dtb"

DarrenHill can you paste the output from when booting 8.0.1:

cat /proc/cpuinfo | pastebinit
vcgencmd otp_dump | pastebinit

sprungle.us -> sprunge.us
[hr]
There's a kernel oops during the initial boot, which is presumably related to the USB WiFi hardware (Ralink RT2800USB_RT53XX).

This may require popcornmix to diagnose this further.

Can you try my latest test build based on kernel 4.10.5 and Kodi 18a1: RPi - let's see if this is any better (may give a clue).

Can you run:

journalctl -a | pastebinit
vcdbg log msg 2>&1 | pastebinit
cat /flash/config.txt | pastebinit

then post the links.

scripts: revert changes that led to accumulation of old packages by MilhouseVH · Pull Request #1474 · LibreELEC/LibreELEC.tv · GitHub should fix this. Thanks for the report.

Once it hangs can you connect with ssh, or ping the device?

Can you connect to the device with ssh and run these commands, the paste the output in your reply:

dmesg | pastebinit
systemctl status brcmfmac_sdio-firmware | pastebinit
vcdbg log msg 2>&1 | pastebinit
ls -la /dev | pastebinit
cat /flash/config.txt | pastebinit
cat /flash/cmdline.txt | pastebinit

Quote from djhifi

Can you please advise the correct input prompt? Im lost as to which one it is.

Afraid I don't understand the question - what input prompt are you referring to? The workaround involves creating the udev file as per post #3.

Quote from djhifi

PS: Haven't your already fixed this on your latest fork in the GIT ?

No, the only fix at the moment is the workaround, which is only required by a subset of Nvidia users (typically users of older hardware, but sufficiently recent that it can use both non-legacy and legacy drivers). Unless Nvidia fix the bug in the non-legacy driver the only solution LE could implement is one that forces older Nvidia hardware to use only the legacy driver.

If you forgot to enable ssh and no longer have access to the Kodi GUI, simply add "ssh" (without quotes) to the end of the line in cmdline.txt (you'll find it in the root of the SD card).

Right, then the answer is in the 4th post of that thread:

Quote from fritsch

There is no VDPAU 10 bit decoding support on linux as of now. Nowhere.

Your vdpauinfo will most likely also tell that there is no support. Until ffmpeg gets 10 bit vdpau decoding support -> kodi also won't have it.

There is experimental Kodi 4K/10-bit HEVC for VAAPI (Intel/AMD) support in some community LibreELEC builds (eg from piotrasd, fritsch) but Nvidia 10-bit support (ie. VDPAU) is not on the horizon.