Posts by JoeAverage

    no way to trace what's going on ?


    - make --trace (from man make)

    - for kernel compile there is make V=1 (=> make help [being in the kernel tree])

    - searching via google with search string "collect2: error: ld returned 1 exit status" or the string where the first error occured

    ... ?

    dito no audio with todays nightly.

    the box runs with the same bios, audio setting on LE 9.2.4, though.


    attaching some photo's and output of dmesg from nightly running.


    you'll see audio is switched off, somehow and mp2, aac are "unknown".

    Anyone, to teach me "Maori" ?;)


    grep -iE 'alsa|pulse|hda' dmesg.txt

    [ 2.883483] ALSA device list:

    [ 5.860302] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops 0xffffffffb6a0ae00)

    [ 5.893548] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC233: line_outs=1 (0x21/0x0/0x0/0x0/0x0) type:hp

    [ 5.893550] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)

    [ 5.893552] snd_hda_codec_realtek hdaudioC0D0: hp_outs=0 (0x0/0x0/0x0/0x0/0x0)

    [ 5.893553] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0

    [ 5.893553] snd_hda_codec_realtek hdaudioC0D0: inputs:

    [ 5.893555] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19

    [ 5.973936] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1f.3/sound/card0/input14

    [ 5.973974] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input15

    [ 5.974003] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input16

    [ 5.974034] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input17

    [ 5.974072] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input18

    [ 5.974096] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input19

    [ 5.974124] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input20

    [ 5.974148] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input21

    yup, 3. did it.


    thanks for your patience.


    P.S.

    I guess I had done so ever with my milhouse nightly installations and forgot about it or was now mislead with the offered bootprompts "Install" versus "run".

    It's not that obvious (to me) that "run" also ~installs~ on a stick ...


    P.P.S

    it seems that the intel graphic is compiled in ?!

    on my homebrewed kernels on an other box I compile it as module so that the i915-firmware gets loaded.

    maybe there is a module option nowadays, although I played with it months/years ago without luck.

    to 2.:

    i have done so several times since ~march 2020 to get milhouse nightly running.

    With the same stick and an initial LE Release, btw.

    At that time the stick I booted from was visible as install target.

    Today it's not, so I need to replug.


    I was under the impression that the whole installer stuff was copied to RAM, so the stick was free.


    okay, will try with two sticks...

    the stick seems to be okay

    see attached file "smart_2020-09.txt" from today after a run of smartctl -t long /dev/sdb


    anyway, tried another stick (Corsair VoyagerGT on /dev/sdb with LE Release):

    after the creator created the install stick:

    cat SYSTEM.md5 => 52b0c54371949fe8785bd3d9eebf1b06 target/SYSTEM

    md5sum SYSTEM => 52b0c54371949fe8785bd3d9eebf1b06 SYSTEM


    and after the installer installed on the stick:

    cat SYSTEM.md5 => 52b0c54371949fe8785bd3d9eebf1b06 target/SYSTEM

    md5sum SYSTEM => f152a99128d2166c518680ed4738c235 SYSTEM


    mismatch !


    attached some photo's from the installer log file.

    it seems the installer is running wild somehow and I guess the bug is here (esp. when installing on USB Sticks)


    on an Sandisk: box boots into an debug shell.

    on an corsair: box doesn't boot/see the stick (=> no boot flag set)


    I wonder what the installer is doing with /dev/sdc

    But I have to admit that I need to replug the stick that the installer gets aware of it.


    the box is an NUC with only an Sata-SSD as /dev/sda


    more confused.

    Friedhofsblond a "like" is nice and good, but it would be better if we all (!) see/hear if and how your problem was solved, if it is solved.


    I personal need no "likes" and such.

    the community needs "shareable" solutions for their problems.

    and today also no luck with 20200925-4722b9e.

    all the same as before.


    I reformated the stick: no luck.

    I then tried with Release LE: huh, also no luck. stick boots, but only to debug mode.

    I tried 2 diff. boxes


    investigating: turns out that the LibreELEC USB-SD Creator from here:

    LibreELEC Downloads – LibreELEC throws some I/O-errors during installing on the stick.

    - alas "save log" saved it somewhere, but not on the stick... -


    compared the md5sums of the Creator on my box and from the website: checksum are equal.


    moons ago I created with an (/this ?) Creator the same stick with Release LE 9.2.2 or .3 and updated to Milhouse nightly without errors...


    confused !


    hint:

    the checksum of one of the Kernel or the System after the Creator action and after install on the stick do NOT match !

    is this normal ?


    Questions:

    - how to save the installer log's that they survive ?

    - where to get an elder LibreELEC USB-SD Creator from ?

    I took some photos from an Intel_NUC_8i3BEH, cause I guess the Bios's are the same.


    - not that sharp, but might help -

    btw.:

    - 1st pic, right side: all enabled apart charging port.

    - last pic: Secure boot is OFF


    ============

    To get a Windows USB Install stick (other tools/techniques may work, but might not 8))


    on an 2cd windows box (or an Windows in an VM):


    diskpart (run as admin)

    then:


    - list disk

    - select disk N (be aware: N is the number of your usb stick)

    - detail disk (to verify the correct device was picked before)

    - clean (!!! all data are lost on the above selected device !!!)

    - create partition primary

    - format fs=ntfs quick (fat32 for Windows 7)

    - assign

    - active


    now copy over the contents of the Windows DVD to the USB stick


    done !


    be aware:

    - nvme driver is NOT included

    so if you need it:

    "MSI Smart Tool" from here:

    Support For B250 PC MATE | Motherboard - The world leader in motherboard design | MSI Global


    - USB3 is NOT include on Windows 7 DVD's (Win10 it is !)

    use the same tool from above !

    Hi JoeAverage,


    thanks, ive worked with Hiren’s BootCD PE x64 (v1.0.1)

    I tried to download these drivers Download Intel® Graphics - BETA Windows® 10 DCH Drivers
    but when trying to install there is an error says "newdev.dll is missing from your computer"

    maybe do you have another link?

    No !


    try the driver without "DCH" in it's name [1].

    DCH is the microsoft fit-them-all sh*t.

    Frequently Asked Questions about Windows* DCH Drivers for Intel®...

    ===


    What do you actual want to do:

    a) Beta-Driver testing ?

    b) HDMI-FW update ?


    I would recomment to do FW-Updates in an *save* environment.

    *NO* experiments.

    Never ever.

    if you ever have flashed a chip badly (in my case a BIOS update, moons ago) you know where I'm talking about...


    [1]

    if this doesn't work, somehow:

    - LE backup

    - backup saved !

    - windows install on the LE-disk

    - chipset-/Graphic-driver install with reboots

    - HDMI flash

    - LE re-install

    - LE backup restore

    may I add my thoughts ?


    Hiren's BootCD PE

    Download | Hiren's BootCD PE


    cit from the 1st link:

    "Hiren’s BootCD PE (Preinstallation Environment) is a restored edition of Hiren’s BootCD based on Windows 10 PE x64 ..."


    The elder boot cd (without "PE") has only a windows XP on it and may make some trouble regarding buildin .net-Version/-Env. (don't know if it's the case for the HDMI-Update-Tool, but I guess it might if you try to install drivers expecting a higher .net-version/-Env. .

    The chipset-/graphic drivers comes to mind [1] )


    => Hiren's BootCD 15.2 | Hiren's BootCD PE

    cit.:

    ...

    Mini Windows Xp

    ...


    [1]

    I'm not an programmer, but at least I would install the chipset- and graphic-drivers in the HirenPE (without reboot at a time) before I would run the HDMI-Update-Tool !


    it might work without, but what's when not ?