Posts by JoeAverage

    @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

    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

    - 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

    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 -

    Thomas_AR

    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"