For those folks who, like me, have not upgraded by dumping the upgrade image into /storage/.update before, I can confirm it does not reset your watched show history.
It was really easy. I didn't even unzip the file.
Thank you for this update.
For those folks who, like me, have not upgraded by dumping the upgrade image into /storage/.update before, I can confirm it does not reset your watched show history.
It was really easy. I didn't even unzip the file.
Thank you for this update.
Disabling DHCP alltogether is not an option here, i want it to work for guests.
That's where the server comes in. You may notice I did not describe reverting to manual IP configurations. lol!
Sometimes ISP gateways are not very configurable. Others are quite configurable. If you can change the "ntp-servers" option, your DHCP clients will sync to whatever you specify.
It sounds like you're in good shape. Best wishes to you.
And sure, it "kindof" works now - however, since apparently the router only syncs when it boots, the time *will* drift again in the future, and having to remember to reboot the router when that happens is annoying - i'd prefer some script to issue that ntpd command. Or ideally, libreelec could be fixed to work as expected
I was going to leave this alone in the interest of courtesy but I highly doubt it works as you describe. NTP is a time calibration protocol, not a time sync protocol.
It will figure out the time clock error and periodically add or subtract corrective ticks, as it believes are required. This calibration is stored in a drift file that will survive a reboot. A system that has previously calibrated itself with NTP will have a more accurate clock than a system that has never synced, as long as the NTP daemon is running.
In fact, NTP systems check their clocks against a remote reference less and less frequently over time, as they become increasingly well calibrated.
The factor that will cause the drift calibration to be inaccurate is temperature changes. If the device is in a temperature stable environment, the clock should keep excellent time even if completely disconnected from the Internet.
You probably have a case of your NTP server crashing or stopping, for some reason. I suspect it will be very good until it crashes again.
I disabled the DHCP server in my router for this, and a few other reasons.
My DHCP servers are configured with: "option ntp-servers pool.ntp.org;"
The ISC DHCP server implemented a really neat active/standby feature for high availability, some years ago. It's simple to configure and works great. No need to split address space, like we used to have to do.
Having said that, it sounds like your Internet gateway does a well acceptable job most of the time. Maybe there is no need for you to change anything, now that you have it sorted. I have an audio timer in my home theater stack that is literally flashing "12:00" right now, as I haven't bothered to set the time since the last power outage. You're doing OK. lol!
I have some trouble getting 4K out the HDMI output of Argon One cases. It is the same for four cases. It seems to require a good quality adapter to get 4K to work properly and the Argon adapter isn't quite up to the job at 4K but works great at 1080p.
Has anyone tried the Waveshare dual HDMI adapter at 4K? It looks extremely similar to the Argone One adapter.
I would pick up a few to try them but they are on back order. It must be a popular new product.
Thanks!
Quick note: LE 12.0.0 is the first version in a while for which boot from USB on rPi4 is again working. Anyone who went back to TF card can return to USB/SSD.
Thank you to the LE team for the work you do. Love it!
Brilliant. Thank you.
It appears I can add network mountpoints with the following instructions.
https://wiki.libreelec.tv/how-to/mount_network_share
Still looking for CLI solutions for these settings:
Settings -> LibreELEC -> Network -> NTP Servers -> Timeserver #1
Settings -> Media -> Library -> Pictures -> <menu key> -> Switch media....
Settings -> Services -> General -> Device Name [htpc]
Settings -> Services -> Weather -> Service -> Install Multi-weather
Settings -> Services -> Weather -> Service -> - settings
Settings -> Interface -> Regional
Settings -> Interface -> Startup -> Startup Window -> Videos
Settings -> System -> Audio
OK. Using the Kodi wiki and some minor interpretation, I believe the settings are contained within:
/storage/.kodi/userdata/guisettings.xml
I think I can configure one node, copy guisettings.xml to the server, and then upload guisettings.xml to each node using scp.
I would like to automate LE install across several nodes. Is it possible to use the CLI or similar to automate setting up sources, audio settings, etc.? Perhaps there is another way?
I'm having the identical issue, PackElend. TF card works, SSD does not. Current firmware.
I have three Pi4B with 4GB. All bought at the same time. All in Argon One M.2 cases. Two have WD Blue 512GB SSD, one has WD Blue 256GB SSD.
Other pi OSes boot fine.
10.0.0 -> will not boot from SSD
10.0.1 -> will not boot from SSD
10.0.2 -> will not boot from SSD
10.0.3 -> will not boot from SSD
10.0-nightly-20221212-0731809 -> will not boot from SSD
I've tried a bunch of disk imagers: Startup Disk Creator, UNetBootin, Etcher, etc.
The thing is, libreelec used to boot from SSD just fine on these very same systems. This causes me to suspect something with the latest rPi firmware or perhaps a change to syslinux. I've built SSD images from Windows and a few different Linux systems but no help there, either.
I've been using TF cards for the better part of the last year. They work fine so I just carry on with that. I've been thinking of trying PINN and multi-boot for a media player project. When I test LE booting through PINN from SSD, I will report back.
Just boot from TF and be happy the software works as well as it does.
Yeah. Seriously. lol!
Still working on v10.0.2.
I just pulled another brand new rPi out of a box, installed it in a brand new armour case, brand new micro SD card, used the LE Windows utility... fail.
I tried a different SD card reader, this time.
It came up, showed the LE logo and indicated it was resizing the partition, then rebooted, saw the color spectrum, then blank for 5 minutes.
I found v9.2.6 on my disk so I will try that version.
This is totally whacked but I just got LE 10.0.2 to boot from SD after flashing the SD using the OSMC installer to flash it.
I'm losing my mind over here. lol!
Second image is a USB flash drive. First image is an SSD. Both v10.0.2.
Will not boot from SD card.
I just tried flashing the SSD with OSMC and the GUI comes up but with "install failed: could not mount bootfs". So, something is wrong with USB disk boot on every one of these devices, aparently.
These rPi boot with OctoPi and Moode Audio.
Volumio also working....
I've been running LE for many years and LE on an rPi for a couple. 10.0.2 was working fine until last night when I disconnected the rPi to re-arrange the livingroom. The case is an Argon One M.2 with 120 GB SSD.
On reconnect, it wouldn't boot. Tried a bunch of times, re-installed the boot sector. Still won't work.
Tried 3 other rPi, for a total of 4. None working.
Have tried two different rPi on versions 10.0.1, 10.0.0, 9.2.8 (the oldest one on the DL site)
"chroot: can't execute '/usr/sbin/kernel-overlays-setup'
Flashed from Manjaro Linux using SUSE Studio Imagewriter and USBImager. Your tool for Windows will not image an SSD.
Every one of these systems will boot up fine with a Moode Audio image. No way I had 4 systems that were all working all die at exactly the same time, particularly when they all work with Moode.
I suspect I'm doing something silly but can't figure out what. Any help would be appreciated. Ideas...
Found a USB stick. Installed it using the LE USB-SD Creator.
Won't boot, either. Different error, though.
Fantastic. Thank you, mglae.
Assuming the music you listen to is 2 channel, an audio extraction device would work perfectly for you.
This problem seems to have been caused by a change to the mysql authentication method starting at v8.0 of mysql server. Kodi probably wasn't connecting to mysql since I upgrade the server.
Long story short, I spent a few hours trying to make it work with the old style mysql authentication for kodi and the new style authentication for some scripts. It cannot seem to support both.
I didn't want to convert everything to the old method so I backed out the changes and installed mariadb on a different server for kodi. It's working perfectly now.
Perhaps this thread will help someone in the future.
I'm pretty confident the issue is with my server. It's not listening, for some reason.
I will post back, if/when I figure it out.
I used SPDIF for 15 years but am really happy with HDMI audio out of the Pi. In my case, I use HDMI audio from the Pi directly into the receiver.
I couldn't get an extractor to do DD or DTS. My TV won't pass it through, either. The AVR had zero trouble with DD or DTS, including EX and ES, so now I use the second HDMI port for audio and it works perfectly.
There should probably be an FAQ for HT audio out of a Pi. Perhaps some people have audio extractors that handle multi-channel properly and we can start a list?