just by dropping it in ~/.update/ ?
Posts by GDPR-7
-
-
wenn du den letzten scheiß haben willst musst du aber auch damit rechnen das es nicht so easy peasy geht
wenn du zu viele Alpha-/Beta-Tester hast, musst du das nur sagen !
- *ich* hatte mich nicht über dein addon beschwert -
Okay ?
-
- scratched -
-
if you want to play with the unfinished toys you need to be a bit more patient
btw it is already there for LE10Beta1 (not yet released) so everything is fine
you surely intended to write "won't" instead of "want", won't you ?
- okay, english isn't my native language too. You'll surely find enough "JoeAverage" statements that bullet proof that -
anyway, I was only kidding, see the smiley:
WACKO | meaning in the Cambridge English Dictionary
wacko is me !
anyway 2, I completely switch to nightly.
well, all (seems) fine here, - with some ${expected hiccup's}, though -
-
Today I flashed the HDMI successful, but some hints:
VC runtime
you need one or two additional files, otherwise the HDMI-Update-Tool will run in an error (see attached Photo)
both files from here:
Aktuelle unterstützte Downloads für Visual C++
for x86 and maybe for x64
I first installed x64 (on the 64 bit Win10), but the HDMI-Tool wasn't happy, so I installed x86 too.
I guess the HDMI-Tool depends on x86, so it should be sufficing to install only x86, but if not: also x64
HDMI-Update-Tool
if you read the "NUC8ixBE-HDMI-FW-Update-Guide-Version 1.78.4.0.3.pdf" (in the tool directory) you will find that the version numbers in the graphic aren't current, esp.: the new HDMI-FW check after the update !
so here is what I get (after the update):
======================================================
Current on-board F/W Version: Bobcat App: MC2800 v1.78.4 (cut2.2)
CMDB: Ver:0.3 (Custom Ver: 0.3)
=======================================================
Gerätemanager
if you have trouble to find the known Gerätemanager in Win10:
in the (File-)Explorer right-click on "Dieser PC" => "Eigenschaften": top right (in fullscreen mode) => "Gerätemanager"
-
currently not (anymore)
THX.
-
uncurrent for Generic since moon's, Hrmph...
-
Well it seams that option TWO is the best choice. Also setting up LE again is not a big deal.
So I think I go with that. Installing WIN10 on a NUC shouldn't be a big problem. Well we never know.
Let's see where I can download a Intel-driver-featured Win10 64 bit.
Any tips regarding Win + NUC?
Thomas
P. S. Native German, plus English and Spanish. Living in the moment in Buenos Aires.
Bios Keys (if unknown):
F2 bios config./settings
F7 bios update (with *.bio on an usb stick, OS independent Bios updates)
F10 boot menu
Tips regarding Win install:
- you could use the link from comment #13 "c't Notfall..." => the first 64 bit, german
- don't let you trick by MS's insist (insistance ?) to need an online account during install (use Domäne beitreten ...)
- the rest of setting during install: as you wish and no need to spent a lot of time
- if it comes to that point somehow: don't use the driver offered by windows update (they are downsized), use only (!) the Intel one's from their site
Tips regarding driver (in that sequence):
copy-pasted from the readme in the "Bundle Drivers":
1. Intel® Chipset Device
2. Intel® Management Engine Consumer Driver
3. Intel® Graphics DCH Driver
?. Intel® Serial IO Driver (don't know which function is has, but it won't hurt)
?. Intel® Ethernet (isn't necessary for the HDMI update)
?. Realtek* High Definition Audio Driver (last time I didn't install it for an HDMI update)
that's all driver we/you need.
- reboot Windows after driver install so that all driver are sharp
- you'll find in the device manager some unsatisfied entries - cause we didn't install all driver -
- chipset and most important graphic should be satified !
- HDMI is an extra download (not in the bundle) !
- HDMI update works without LAN/WIFI
additions:
a) BIOS ?
last is 87.
is yours current ? (NUC booted with F2-Key pressed/tapped)
no:
either it's in the bundle too or later (anytime and any OS) via an '.bio on an usb stick
b) Secure Erase SSD (if needed)
- software comes from your manufacturer
usually (I got a Samsung SSD) they build an usb stick to boot with. (suprise: they boot an linux )
P.S.
I thought that you're an german
P.P.S
I hope the whole effort works out regarding your initial sound problem.
-
sh*t.
in comment #13 I provided a link to an german Win10 ISO.
what is your native language or more accurate: are you able to read/understand german ?
Background:
the link to heise site also provides an environment to build an WinPE.
moons ago I fetched that and build an WinPE (~1.5 GB), but in 32 bit and german only.
I guess the 64 bit driver from Intel might not install there, so I need to build an 64 bit WinPE.
so I tried an PE laying around (hbcd_pe), but after an test with an hbcd_pe_x64, I must realize that that didn't work.
Intel driver install run into error, cause - I guess - .net seem not included in hbcd or maybe something else ...
"surprises sponsored by MS" ?!
AAArrrggghhh...
there are few options I currently see:
1. (work expensive to me, but ...)
- I get an english Win 10 64 bit
- I build an WinPE from that with .net included
- I test if Intel driver install in that WinPE (result might NOT be satisfying)
- I upload that WinPE, where you could fetch it
- you need an Windows PC (friend ?, ...) to bring the WinPE.iso on an usb stick (~8 GB size) or - unusual these days - an DVD
2. you make an backup of your current LE and save it offline OR you get an spare 2.5" Disk/SSD
- to install an Intel-driver-featured Win10 64 bit
- update HDMI in an safe way
- re-install LE and restore the backup
3. (risky)
- HDMI flash under the hbcd_pe (as is, means few/no (?) Intel drivers)
~1.5 GB
*I* tend to option 2.:
- cause less work for me -
- cause it's the safest way !
- cause an running usb on *my* box doesn't necessarily mean it will run on *your* box too (see above "surprises" and is this case: "... by Intel and MS")
- and cause I guess you got an SSD in your NUC.
Right ?
If so, you are able to secure erase your SSD too (to bring it to nearly maiden speed again, if it was running some moons).
And most secure erase tools run on windows only, too.
secure erase also means an - hopefully [*] - empty/clean disk ...
to me, that task is triggered, when an fresh/clean install with an shiny new LE 10 is released and the SSD was in use for 6 or 12 month.
currently I'm thinking to do option 2 in the next days here too and switch - after HDMI update, secure erase - to LE nightly...
[*]
AFAIK, it's not clear if secure erase cleans really all data blocks on an/every SSD.
-
yes, but wait some hours, I'll check that.
what I know for sure:
You're able to install drivers under an from a USB running windows 10 ( Win 7 wasn't able to do that !)
Q.:
do you got a 2cd box with windows around or an linux to install VBox on it ?
Hints:
- get the 64 bit Windows from the heise site
- get the driver bundle from the intel site (only 64 bit driver)
- get the HDMI flash tool from the intel site (it's not in the bundle)
-
Need Windows installed on my NUC to update HDMI? What... 😂
Oh my god.
Thomas
it seems wise to install the intel driver's for the NUC under windows (at least chipset, graphic), too.
a somehow damaged flash could lead to an damage LSPCON (see photo).
I wouldn't risk it !
a link for windows 10 iso:
c't-Notfall-Windows 2021 | c't Magazin
I mean I did an full featured window 10 install on an USB-Stick.
- I'll check that the next hours after an doc date this afternoon, stay tuned ... -
-
... and check the Bios Version too.
dito, there was an HDMI update, too
Bios:
Download BIOS Update [BECFL357]
HDMI:
Download HDMI Firmware Update Tool for NUC8i3BE, NUC8i5BE, NUC8i7BE
Read the User Guide !!!
-
pen is an USB Stick ?
- long (not quick !) format it under µ-soft window
- check the downloaded 9.2.6
slowness and an truncation sounds like one (or maybe both: "your luck is doubled then") is sh*t: the pen or the download.
2 program's the check what it could be:
both zip files containing english readme's, if german isn't your laguage
-
ever and ever "~tomorrow"
-
Q.: should "Nuc Bi5BEH" read "Nuc 8i5BEH" ?
if so:
i'm running an 8i3BEH (also a "Bean Canyon" with lower CPU) and my sound is routed through an Philips Monitor (not an TV Monitor, Typ: see photo)) via HDMI and further to an 2.1 speaker system via headphone out (Monitor)
I haven't had any problems you described nor with LE 9.2.6 neither nightly.
attaching photo (sound setting in LE, Bios sound settings)
- edit -
I guess Da Flex means with "EFI settings" the Bios Settings (?!)
hit F2-Key during start of the NUC
-
yup, that was the point !
thanks
-
ping CvH
tried an fresh/clean install with:
- LibreELEC-Generic.x86_64-10.0-nightly-20210307-7932f3f.img.gz
- 9.80.11-Generic-x86_64-service.tvheadend43-9.80.11.100.zip
turns out:
- addon not visible in the addon repo's (only 4.2)
- manual install fails also (unsupported addon install or the like was set)
ideas ?
-
for the record:
Tvheadend 4.3 arrived today - thanks CvH - and seems to fixes the above crashes