Old (out of date ciphers) PuTTY version?
Posts by chewitt
-
-
I've submitted a backport, so if we spin another 10.x release is should be included.
-
-
It's hard to comment without seeing a UART boot log from the board (if you have one, please share it) but if the older image works, use it and then update via the .tar file in /storage/.update as normal. I've clean installed both N2 and N2+ recently without any issues, so I'm fairly sure there are no issues with the image. You do need the boot switch to the right? If petitboot is active (switch to the left) it will not boot, as HK are not interested to support modern u-boot with it.
-
Interesting - where is the best place to offer feedback on this, and help ?
I've pinged you some options in PM. It would be good to have your eyeballs on the text!
-
elonesna As long as the MAC address doesn't change flipping between Android and LE should work. The other option which I sometimes use in hotels is Ethernet tethering. LE exposes a wifi hotspot/tether in the GUI, but if you create /storage/.config/connman_main.conf from /etc/connman/main.conf and allow ethernet tethering you can connect a laptop to the Ethernet port on the box, which allows the laptop to share the boxes WiFi connection and complete any kind of registration process needed to get the LE box online. The only fiddly part is, you probably need to SSH into the box over WiFi to set the tether, and this is not always allowed, or (easier, if the device is an SBC) have a UART cable to get a local serial console. These days I'm travelling with a Radxa Zero in a flirc Pi Zero case which is both tiny, fast, and has GPIO pins exposed so I can run the board from the +5V on the UART cable and access the UART console easily.
-
Current nightlies are GBM images with no Xorg which means no nVidia support. At the moment there is still a "Generic_Legacy" device that can be built in our codebase, but we are deliberately not building nightlies for it and hope to drop it before formal LE11 releases start. There are signs that nVidia is starting to get its sh1t together with respect to upstream standards, but there's still too many bits of jigsaw puzzle missing for nVidia support under GBM.
-
frakkin64 I had a crack at some 4K/HDR documentation earlier https://wiki.libreelec.tv/configuration/4k-hdr
-
how can i install libreelec test 11 on emmc odroid N2
If you have a USB => eMMC module reader/writer board, connect the module and write the "odroid-n2.img.gz" directly to eMMC, then put the SPI switch to the right (so petitboot is not used) and power on the board. If you don't have the USB/eMMC converter, you will need to boot the N2 from an SD card first, then SSH into the console and download the image to the SD card, and use "emmctool" to write the LE image to the module (overwriting anything on eMMC).
-
See https://github.com/LibreELEC/LibreELEC.tv/pull/5991 .. once it's merged the next nightly will support the card.
-
noobs for RPi4 is currently shipping 10.0.0 and we should update that to 10.0.1, but as we have not formally released LE10 for RPi2 yet (and RPi0 is deprecated) both of those currently point to LE 9.2.8 noobs .tar files.
-
Those are two of the best known mirror sites in Europe. No scam.
-
Code
[ 2.579005] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002) [ 2.579188] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops 0xffffffff8bc18620)^ hard to say.. have you tried a currently Nightly image? (newer kernel and drivers)
-
I think there are two separate issues:
a) Logs show the box has an RTC chip that keeps time between boots, and connman reports NTP sync with under 1 sec clock drift and shows 1.nz.pool.ntp.org as the active server, and there are no certificate errors in the Kodi log - so it's not the "NTP fails to set clock causing invalid TLS cert" problem. You need to enable debug mode in Kodi and reboot/reshare the logs so we can see more about the failure to connect to LE servers. Also, have you tried doing a force refresh? (navigate left in the add-on browsing views, force refresh).
b) Kodi sets the timezone in /storage/.cache/timezone when it changes, so from what I'm seeing in code/patches and the tz-data.service it would have to be Kodi writing the wrong value. Again, debug mode might show more (maybe).
-
I gave up on "browsing" aeons ago. It just takes a little effort to configure shares; personally I edit /storage/.kodi/usersdata/sources.xml as the format it simple and typing smb://user:pass@SERVER/SHARE is easier on a keyboad via SSH than using a remote in the GUI. SMB2/3 file sharing works fine in Kodi so there's really no need to downgrade things to SMB1.
-
SSH into the box and run "dmesg | paste" after a clean boot, then share the URL
-
You can look at the package.mk in https://github.com/LibreELEC/Libr…rmed/package.mk in our master branch this will tell you the current status of the package. We make periodic updates to add-ons and build them when upstream things are bumped (and we notice, there is no automation) but they are not built "nightly" like core images.
-
Add "video=HDMI-A-1:1920x1080M@60D" to boot params in cmdline.txt and see if that helps?
