Posts by chewitt

I would avoid doing this split set-up because Windows\saves\files\paths\like\this and Linux/uses/paths/like/this .. so while most config will work, there is always a percentage off stuff that will not. Unpicking the stuff that does not work usually takes longer than doing it the 'hard' way.

dmesg | paste
blkid | paste
parted -s /dev/sdb unit s print | paste <= where /dev/sdb is the 2TB drive

share the URLs here

"SMB" encompasses multiple not-quite-compatible versions of a shitty designed networking protocol that is implemented via a third-part integration library (smbclient) that is wrapped in Kodi code that hasn't seen much love in aeons. Somewhere in that list resides a mess of problems. The current resurgence in reported issues (which may or may not be your issue) is largely due to Microsoft changing things in their SMB server stack. I forget what changed and thus what might be required to coerce things to work again; but it probably involves registry hacking to downgrade features on the Windows end. Best solution is to get a NAS because this will run "Samba" with an older SMB protocol version which is more widely supported (and powered on permanently which solves other silliness) or use NFS on the server side to sidestep SMB completely. Sorry if that sounds a bit shitty-worded, but Windows networking has been a complete turd since Windows '95 and I'm struggling to work up the enthusiasm for it today..

RPi3 and RPi2 are essentially the same device but RPi3 uses a newer generation of the core SoC that runs at higher clock speeds. As the hardware is so similar we can use a common kernel/OS image that supports both devices. One quirk of the Pi firmware in this configuration is that 64-bit RPi3 hardware reports itself as a 32-bit RPi2. It is possible to make RPi3 run a 64-bit image and report CPU etc. correctly but this requires you to run a different kernel configuration, and then Kodi doesn't run as nobody 64-bit ported the mountain of very highly optimised 32-bit video code that Kodi depends upon. TL;DR - it's a cosmetic issue and there's nothing to see, move along please

Auto-update is supported by custom channels, but this is not a simple URL/page scrape and requires something server side, and most community builders do not provide/support the server side bit needed to use a custom channel.

Kodi sometimes fails to retrieve addons.xml from Kodi server(s) which leads to 'get more' etc. not showing anything. If you context click on the repo and "check for updates" manually that forces it to be retrieved and Kodi now has a valid list of whats available.

The hard reset process is triggered by /storage/.cache/reset_oe being present in the filesystem. There is no logging on that process so you're not missing anything useful from the logs being nuked as part of the reset.

The only scenario that I can come up with for this happening is that you've hit "hard reset" and then said "no" when it prompts to reboot (assuming it does prompt, it probably does) and then you've taken a backup of the system. This would lead to reset_oe being present in the backup.

Adding them into the core distro by default is not going to happen because our average OS image size is ~130MB and the complete Noto font collection is ~970MB according to the Google download page

It's a valid request though. I'll ask the team to think about another method to make system-fonts user-installable.

add "dtoverlay=pi3-disable-wifi" to config.txt

If you are using the onboard wireless, it's not brilliant. The easy solution is to use an external USB dongle.

No idea what the issue is, but the backup is just a .tar archive containing some folders. Copy this to /storage and uncompress the archive, then stop Kodi (systemctl stop kodi.service) and move the directories you care about (.cache, .config and .kodi) back to the right places, then restart kodi.service.

MacOS + Safari user? The default behaviour of Safari is to uncompress archive formats after downloading so the .img.gz file becomes .img

This behaviour can be disabled in Safari preferences.

MacOS uses Apple's own implementation interpretation of Samba which historically (back in MacOS 10.7 days) was quite broken and smbup was the proven solution. I'm not sure that advice is still valid for current MacOS versions; a little Google search doesn't turn up anyone singing it's praises on a current release and I can see statements that it's not tested on 10.12 etc. - I'd avoid that route for now.

Can we please have a copy of the previous DB file from the same folder; for Jarvis this will be Addons20.db. Share the file via dropbox or similar or if not possible email to my forum username @libreelec.tv. The file will be passed to Kodi developers to investigate why the migration process is failing. Fixes were added into Krypton 17.1 to solve a previous (more common) migration issue but there are clearly other scenarios that cause issues.

[    2.999500] scsi 5:0:0:0: Direct-Access     ATA      SAMSUNG HD753LJ  1107 PQ: 0 ANSI: 5
[    3.033457] sd 5:0:0:0: [sdb] 1465149168 512-byte logical blocks: (750 GB/699 GiB)
[    3.033489] sd 5:0:0:0: Attached scsi generic sg1 type 0
[    3.033509] sd 5:0:0:0: [sdb] Write Protect is off
[    3.033512] sd 5:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    3.033543] sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.039490]  sdb: sdb1
[    3.039731] sd 5:0:0:0: [sdb] Attached SCSI disk

Kernel can see the disk. There's no errors, which is good, but no apparent attempt to mount it, which is odd. Hmm..

Search for builds from "demetris"

LE defaults to using pool.ntp.org servers unless NTP details are provided via DHCP (some routers do this) or the ISP blocks NTP requests (dumb, but it happens) and on Pi there is often an issue with slow loading network (wireless) drivers that mean the initial NTP request fails. Looking at the system log via "journalctl -b 0 --no-pager" will reveal what is happening.

mount -o remount,rw /flash
nano /flash/config.txt
[make changes, save]
mount -o remount,ro /flash

once you're in LE

Quote from bicky

The Kodi website says that we have to upgrade to Kodi Krypton, because the support for HTTPS is being withdrawn.

No the Kodi website does not say this. A third-party website run by ignorant fcukwits that promotes piracy add-ons said that.

If you are using add-ons from that repo/website there is no further support available to you in this forum.

The Piracy Box Sellers and Youtube Promoters Are Killing Kodi | Kodi | Open Source Home Theater Software
Official:Forum rules/Banned add-ons - Official Kodi Wiki