2. SSH and TigerVNC work fine when the connection is on DHCP (wifi connection), but both throw a "connection refused" when i set the connection to static.
doesn't your router have a sorta "always give a device the same IP adress" ?
gateway, DNS is still DHCP then
AVM Fritzboxes do
As long you are not able to boot from USB you should not delete the LE system on the HDD.
just out of interest and to learn.
Why ?
following your link you provided and dive into it, esp. this one:
Archive:Chromebox - Official Kodi Wiki
it seems to me that I ever could get the device running LE as long as I get a network connection (some more work involved, though)
- install the Kodi E-Z Setup Script
- install with it "ChromeOS + LibreELEC" (dual boot, though)
no need for USB boot
No ?
... i like to update LibreELEC now, or just reset all data and settings, but cant find the way.
yup, then as mglae mentioned: the first page of his link in comment #3:
read the header of the page
and then:
=> "For a standalone setup, you will need to perform the following steps:"
No ?!
esp.: "Open the ChromeBox and remove the write-protect screw"
Urrgghh ...
write-protection could cause the error you see, I guess ...
It would be cool if I could not buy a dozen before I got a compatible one.
one part to prevent buying a dozen is to read the spec's of that device *before* buying them.
regarding your currently bought device *I* can't find the keywords: "compatible avec Linux" to begin with ... [1]
so why do you wonder it's not detected by LE ?
[1]
and I wouldn't be satisfied if I would find one, but only with self-compiled driver support (- apart from the workload every time the kernel changes - it might work today, but tomorrow ?)
googled was "linux RTL8821CU"
P.S:
*I* provided a link in comment #5 leading to further links "Theme: WLAN, in-tree (!!!) linux-driver, mailing lists, etc."
all you need is to search the ML's and/or the internet for the chip (in this case:) "RTL8821CU"
I do not use the Chrome OS so i dont think HP will be mush help, only run LibreELEC.
my intention was to esp. check the storage and when HP has buildin routines, why not use them. [1]
I've read some of this devices have emmc storage and that this typ of storage might elder/wear out quicker, don't know...
You told nothing about the state of the device.
you bought it used and I guess from someone foreign ?!
my first check with hardware (regardless if new, but even when used) is to see what's up with it !
afterwards I know what I can do with it and what not, e.g. install another OS on it, etc.
see your usb boot problem:
- does the devices usually do it ?
- if yes: why now not ?
- why was the device sold ??? (old, too slow, damaged with the same problem *you* have now ?)
[1]
if the device were usb bootable you could use SysRescueCD to do some checks eg.g smartctl
already known by him (englisch ?), see page 552, comment #8286
Questions:
1. Chromebox CB1-020no translates to "HP Chromebox CB1-020no PC" ?
HP Chromebox CB1-020no PC Product Specifications | HP® Customer Support
2. you need a generic LE image, then ?
I can't tell much to the specific error, but what happens when you type "mount" or a "df -h" in that debugging shell ?
regarding 2.:
IIRC, the direct jump from LE 8.2.5 to LE 10 wasn't suggested, e.g. somewhere between the releases a "fresh install" was indicated.
regarding 1.:
- surfing the HP website -
HP Chromebox CB1-020no PC (ENERGY STAR) Troubleshooting | HP® Customer Support
=> https://support.hp.com/sg-en/product/…ument/c04355990
- I would first check what's up with the device (bought from someone foreign ?)
- maybe a HW reset to maybe get USB booting [1]
[1]
i couldn't figure it out, cause the links to the manuals are pointing to nothing/nowhere (at least here)
If you spend $$ on faster SD cards you may be able to empirically measure a minor speed bump and it might boot marginally quicker, but in practical terms you will not notice any real-world difference in performance.
I currently don't know about SDCards, but some higher priced USB Stick (Sandisk Extreme Pro, the elder one's) do have TRIM, too.
USB Sticks and I guess sdcards too getting slow over time.
to reset to initial speed one need to full format (not "quick" under windows) them from time to time.
I guess a good measurement (not the card only, but Kernel, equipment, USB/SDCard) would be:
write speed:
dd if=/dev/zero of=tempfile bs=1MB count=10240
read speed:
dd if=tempfile of=/dev/zero bs=1MB count=10240
both with cd'ed to a folder on the USB/sdcard first !
anyway for an 256 GB Samsung EVO Plus (SAMSUNG MB-MC256HA-EU) under Windows/Linux with an sdcard reader (Transend TS-RDF5) I get this:
also, confirmation from here (for nightly (generic), Tvh 4.3)
thanks CvH
thanks CvH for lightning fast response.
sad !
currently don't know if this is a regression.
it's moons ago that I opened a console (addon System Tool) in LE and that time it was LE Release.
anyway I tried under yesterday's nightly (Generic) and nothing happened.
- Is it just me ? (ever and ever "me again" ? 
)
- if not: bug is known ?
comments/rotten fruits ?
deepee, you should read what I wrote under "for the record (the fix)"
- don't overlook the bold number -
in LE's git I see there some work/help/solution in the pipe..., next days ..., tomorrow ?
and
I wonder how do you do this:
do you do the download on the LE box only (no 2cd box involved) ?
how do you get the correct download link for the new nightly ?
does a web-browser sorta Lynx as an addon or so exists (currently can't find one) ?
with system tools installed:
it would be sufficing if an
wget https://test.libreelec.tv/LibreELEC-Gene…4-11.0-nightly-*.tar
would work ... (as long as only one nightly is in that directory)
alas not
+++ EDIT +++
wrote a small script (maybe needs some improvements...?!)
I guess it's mostly self declaring
- "&&" := short hand "if-then"
- fetch the new nightly *name* from the server
- check if the server's nightly is already running on the box
if not:
- download the last nightly from the server into ~/.update/
- backup a copy to ~/backup/
be aware: no warranty by me !!!
be aware: the script fills up ~/backup
#!/bin/bash
NIGHTLY="LibreELEC-Generic.x86_64-11.0-nightly-";
SERVER_URL="https://test.libreelec.tv";
# clean in any case ~/.update/
rm -rf ~/.update/*;
# operate in /tmp and clean up before
cd /tmp/ && rm -rf releases.json*;
wget ${SERVER_URL}/releases.json;
[ -e releases.json ] && NEW_NIGHTLY=$(grep -i ${NIGHTLY} releases.json | grep tar | cut -d: -f2| sed -e 's/"//g' -e 's/ //g' -e 's/,//g');
if [ ! -z "${NEW_NIGHTLY}" ]; then
# get currently running nightly version
CURRENT_NIGHTLY=$(cat /etc/issue |grep nightly|cut -d: -f2|cut -d "(" -f1|sed -e 's/ //g');
# and compare with the one on the server
RC=$(echo ${NEW_NIGHTLY} | grep ${CURRENT_NIGHTLY});
[ ! -z "${RC}" ] && echo -e "\n lastest nightly already running \n" && exit 13;
echo -e "\n fetching ${NEW_NIGHTLY} \n\t wait ...\n";
# clean ~/.update, download new nightly to ~/.update/ and save a copy to ~/backup/
cd ~/.update/ && rm -rf *;
wget -nc ${SERVER_URL}/${NEW_NIGHTLY};
cp *.tar ~/backup/;
echo -e "\n\n reboot to install the new nightly, e.g. \n\n\t "sync && sync && systemctl reboot" \n";
else
echo -e "\n No new nightly \n";
fi;
exit 0;(to my taste)
problem is Resolved
please keep a least one elder nightly around for download when a newer nightly is build.
I'm running nightly "in production" on a daily base with daily updates.
it has some risks [1] - I know -
but doing so, has - for my view - the advantage to get the bugs they're (maybe) still in getting reported and fixed.
YMMV
but there should be a easy backup/fallback solution if the last nightly doesn't play well.
I know I could
- run a additional LE e.g. LE Release on a usb stick
- download nightly twice and keep the elder one
- ...
[1]
until today I was the opinion that a LE backup saves me against all risks.
I've learned: no, not all !
thanks jernej
it {sh,w}ould be a good idea to have a elder nightly available if - as in this case - something bursts.
- will write a RFC, soon -
for the record (the fix)
===================
copying libhdhomerun.so into ~/.kodi/addons/service.tvheadend43/lib/ fixed it for me
with today nightly (nightly-20211225-9841784 (Generic.x86_64)) TvHeadend (v10.80.2.102) stopped working
in it's service.log:
/storage/.kodi/addons/service.tvheadend43/bin/tvheadend: error while loading shared libraries: libhdhomerun.so: cannot open shared object file: No such file or directory
backup restore doesn't work/fixed it here
anywhere to get the yesterday nightly ?