You can mount the second partition on the SD card from another Linux box (as it's ext4 and cannot be natively read from macOS or Windows) and remove /storage/.cache/shadow* .. then unmount, put the SD card back in the RPi and power on and the password should be back to the defaults again. At some point we need to add a reset function to the LE settings addon GUI..
Posts by chewitt
-
-
340.xx is already in the default (official) Generic image.
-
Team Kodi had plans for ADSP addons which did all that stuff .. but development stalled and code was finally pulled from Kodi v18 since it was getting progressively more broken over time. Hopefully the original developer resurrects it or someone else takes over, but I wouldn't hold breath.
-
That worked for me on 8.2 LE, but it's not working on CoreELEC.
Not our problem to solve then
-
Install the ls.io docker repo (from the LE addon repo) and install their new pi-hole container; which resulted/evolved from @Iridium's work
-
I've tested change of username and password on 8.2.5 and current alpa (master branch) builds from High Sierra and it works fine.
Did you cache the original (default) credentials in the macOS keychain?
-
Hit eBay and find a cheap USB dongle with an Atheros ath9k chipset. It'll work reliably (ath9k is well written) and you won't have to attempt custom builds with random drivers from github. Third party (out of tree) drivers are a pain in the rear to work with so it's not something we'd think about adding to the distro.
-
The three folders that normally contain things are:
/storage/.cache
/storage/.kodi
/storage/.config
-
-
-
I'm looking for some help with this problem and appreciate any comments/corrective actions. Thanks
S802.arm updating to S802.arm is allowed as the project.arch matches. If you update to something else (S8X2.arm) the project.arch does not match so the update aborts. If you want to force the change; read the on-screen text for instructions.
-
No kodi debug log = No problem
-
The lspci output only proves the hardware powered on, it has no bearing on driver support for the hardware. The (broadcom) wl module contains a mixed GPL/proprietary license which taints the license status of the kernel (no longer pure GPL). It's irrelevant.
What driver is that card supposed to use?
-
Updates are performed by placing the .tar file in the .update folder. The img.gz files are for burning fresh SD/USB installs.
Shoog
Unless wrxtasy broke something in his releases we have supported .img.gz file updates since LE 7.0
-
Windows and Linux have fundamentally different approaches to drive mounting. Windows wants to ensure you can access your data so as long as there is 'a' valid disk scheme somewhere on the disk it will mount. Linux values integrity and will refuse to mount when issues are found.
If you have other storage devices; move the data off (via Win) and reformat the drive, copy the data back. Test for a while. If all is good it was nothing to worry about. If you see further issues it may be a physical issue with the drive and it's time for a replacement.
-
Please provide a Kodi debug log showing the install failures.
-
It's probably a shutdown problem. We wait patiently for Kodi to stop gracefully, but there's a timer running and if we time-out Kodi is killed and the system stopped. Kodi saves guisettings.xml on shutdown so if we have to kill the Kodi process you can get partially written xml, and on startup the malformed/incomplete xml is detected and replaced with default settings; hence the appearance of settings reverting or being lost. Add-ons are the main cause of delays to shutdown. Another possible reason is you're looking a media via an add-on, in which case it's the add-on authors responsibility to support persistent view states. I have a couple of legitimate add-ons that don't.
-
I've never spoken to anyone from Minix and I have zero knowledge of their roadmap. I have visibility of others' roadmaps though..
