5 days ago a new version (125) was build for LE10 and LE11
git:
thread:
125 appears in the nightly addons:
alas on both (nightly and LE Release) somehow non gets the update via addon-updater (yet).
it stucks to/on (?) 124 ...
Posts by GDPR-7
-
-
"devel" is the image tag for an ad-hoc built image .. not a scheduled nightly
so it is build only on demand or to proof against a temporary/specific fix or such and is not (every time ?) public available ?
ping kenmills were do you get the devel images from ?
-
The devel Image you are using is not LE10 - it based at a future graphic stack that removes the old x11 and enables HDR and goodnesss. This is not part of "official" LE10.
is "devel Image" apart from nightly ?
cause I'm on yesterdays nightly and see X11 as the "windowing management" (wording ?)
-
This new version is not available in auto update yet (for Generic). When will it be available?
what hold you off from downloading it manually and copy it via scp to ~/.update/
or (if no second box is available)
- install the addon System-tools
- open a terminal with it
- move to ~/.update/
- wget LibreELEC-Generic.x86_64-10.0.0.img.gz
- reboot
-
Horray !
P.S.
Image for auto update seems (on an RC1) not available yet (UTC: 21:00).
-
No, it's fine as it is!
okay, I rechecked it: "failure" is also translated to german "das Fehlen" (engl. "the absence")
-
all fine here.
thanks !
but some hints to improve things regarding the text from here:
LibreELEC (Matrix) 10.0 RC1 – LibreELEC
1.
and there the part regarding topic "DO NOT upgrade"
I and I guess a lot of people already running 19.x stuck here or get somewhat confused, esp. when they don't read the text further.
The confusion is cleared though, but - for my taste - at the wrong place, under the topic "SPARE CARDS AND BACKUPS"
It's the sentence "So unless you are already running an image with Kodi 19 inside, a clean install is preferred. ..."
I guess it would be much clearer and easier to read when it would read (draft):
"DO NOT Upgrade"
unless your are already running an image with Kodi 19 inside ....
and then the rest of the following text why clean install is preferred
2.
another part is the sentence "Your failure to make a backup is not our problem!"
is here a "not" missing => "your failure to *not* make a backup ..."
hint:
my engl/german-dict translates "failure" to german "Ausfall, Betriebsausfall, Erfolglosigkeit, Fehlschlag, Misserfolg, Versagen, Versager"
3.
the tab on the download page/link for generic still carries the word "Beta".
should it be "RC" or just no suffix ?
no suffix would save the work next time (!) and "LibreElec 10" describes/qualifies it enough (YMMV)
comments/rotten fruits ?
-
well, at least you should exclude it's a bug in HDMI. sure, too much encouragement...
good luck, I'm out here (inthis forum)
-
@witetek666
have the disks ever been in an RAID ?
if so:
I remember an simular bug years ago under Fedora.
the fix was to overwrite (not formatting only) the whole disk(s) with pattern/zero's (after an backup) to get rid of an RAID-signatur somewhere on the disk.
P.S.
Houston, why is "shr<put the 5th letter from abc here>d" a censored word ???
-
Tested that usb drive with multiple software include yours and no errors, but replaced with brand new which just arrived and looks that everything is ok now. So usb drive was faulty without errors while testing.
Yes smart toaster. Intel core i3-7167u, 8gb ddr4, 128gb msata
Anyway usb drive landed in the bin. Sorted issue.
curious !
maybe you want give the usb drive another shot ?
here:
Intel NUC 8i5BEH - HDMI Sound problem
comment #28,
where I wrote "in an terminal with admin rights"
try point 1 to 9
-
Can anybody post the link to the latest build based on Kodi matrix? I accedentally deleted the file. The link in this forum is dead.
you means this one ? :
P.S.
please, don't hijack threads with another theme
-
Houston,
all smooth here (in Hollywood, err
, ... on moon )switched from nightly to beta (generic)
THX !
-
no idea what you want to say.
UEFI in front means to me boot via EFI ( no ?)
as I said I don't use EFI, so I have no comparison how it looks normal using it.
attached a photo with add. legacy ON
anyway, the stick boots and installs windows, that's all what's needed here
-
THX for clarification, I didn't know that EFI is unable to boot EXFAT/NTFS - hadn't had M$ its finger on the EFI spec's ?! -
I know that EFI needs a FAT partition, therefore I always didn't use EFI, at least not in my Linux systems.
Why should I ?
the same for ~secure~ (cough) boot.
I also know FAT32 is limited with 4GB.
I'm currently unsure if I have booted my usb stick used in comment #22 with efi or not, anyway both, EFI and normal boot (legacy ?) were enabled in the bios and the NUC booted NTFS fine.
I guess the MS-Creation-Tool builds an stick with EFI on it.
- EDIT -
i checked what you said, and it seems to be invalid.
attached are two photo's:
1. a screenshot of the linux disk manager => NTFS
2. after pressing F10 Key during boot => UEFI (legacy boot was switched OFF before)
hitting enter turns out:
Windows install USB stick, created as described in comment #28, boots from NTFS with UEFI !
-
...
Any special BIOS configuration needed?
Thomas
no.
apart from the above bios key to boot the usb stick.
for the record:
I always do with a second box running windows or - in my case - a VM running windows:
in an terminal with admin rights
1. diskpart
2. list disk
3. select disk N
4. detail disk
5. clean
6. create partition primary
7. format fs=ntfs quick
8. assign
9. active
10 . now, I only need to copy the content (not the iso) from the windows-10-DVD to the usb stick.
hints:
for 3.: "N" is the number for the usb stick.
for 4.: to be sure I selected the correct disk: the stick, because 5. cleans all data ! (wrong disk => all data lost !)
Advantages:
- I'm independent from MS (- tools)
- I could be sure that the stick is bootable, otherwise the stick is bad
- I could use a Windows DVD laying around
-
AFAIK, that exFat isn't bootable from the bios
ntfs is !
-
- I don't know anything about Pi's -
but shouldn't the Web-IF be reachable without any configuration.
I slightly remember a request regarding IP-addresses during Wizard run or do I mix things here ?
Tvheadend might not be started right now after it's installation.
moons ago I saw some hiccup's with TvH 4.3 regarding this point.
a disable/enabled cycle under "Add-ons" => "My add-ons" => "Services" => "Tvheadend..." could help or a simple reboot should do the job
-
there seems to be too much *rums in the linked page:
LibreELEC (Matrix) 10.0 BETA1 – LibreELEC
last paragraph, the link to forums leads to what ?
