Posts by mglae

  • Usb Hard drive not recongize since 11.0.4

    I did a web search regarding ntfs-3g and ntfs3 mounts.

    Result is that ntfs3 does ever refuse to mount a FS with dirty bit set whereas ntfs-3g only refuse to mount FS with "real" errors.

    So for the user experience it is a regression because much more mounts fail after switching from ntfs-3g to ntfs3 mount.

    A said in the Arch wiki an equivalent mount behavior require a combination of ntfsfix -d and mount -t ntfs3. But this require further tests to get the boundary conditions.

    As a first step I will create a "NTFS-3g for udevil" addon (Coming Soon! :-)) that can be backported to LE12.

  • Intel ec1000s nic support for LE

    The driver will be included in LE12 nightly first and therefore be automatic be part ff next LE12 release (and of course of LE13).

    A LE12 stable nightly is always a good choice because being latest release plus fixes.

    The question is if you find a stable (boot-)configuration for the AX200 with LE12.

  • Support of Intel AX200 WiFi card

    dipswitch Sorry regarding AX200 I only looked for firmware errors and there are none.

    The good news: in LE 13 the AX200 is working fine:

    Code
    Oct 15 16:48:26.567299 DigitalEngine kernel: Intel(R) Wireless WiFi driver for Linux
Oct 15 16:48:26.567357 DigitalEngine kernel: iwlwifi 0000:01:00.0: enabling device (0000 -> 0002)
Oct 15 16:48:26.567546 DigitalEngine kernel: iwlwifi 0000:01:00.0: Detected crf-id 0x3617, cnv-id 0x100530 wfpm id 0x80000000
Oct 15 16:48:26.567707 DigitalEngine kernel: iwlwifi 0000:01:00.0: PCI dev 2723/0084, rev=0x340, rfid=0x10a100
Oct 15 16:48:26.567843 DigitalEngine kernel: iwlwifi 0000:01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz

    But in LE12:

    Error -110 can be caused by power on issue, you can try this fix. The file name is /storage/.config/modprobe.d/iwlwifi.conf in LE.

  • [RPi4, LE12.0.1] Autostart.sh with python script for fan control won't work

    Code
    2024-10-06 15:32:15.351 T:1041    debug <general>: CPythonInvoker(1, /storage/.kodi/addons/service.joy-it.fancontrol/fan.py): trigger Monitor abort request
2024-10-06 15:32:15.352 T:939      info <general>: [Joy-IT Fan Controller 1.0.9] Joy-IT fan control service finished
2024-10-06 15:32:15.352 T:939     debug <general>: CPythonInvoker(1, /storage/.kodi/addons/service.joy-it.fancontrol/fan.py): script successfully run
2024-10-06 15:32:15.352 T:939      info <general>: CPythonInvoker(1, /storage/.kodi/addons/service.joy-it.fancontrol/fan.py): waiting on thread 1496097344
2024-10-06 15:32:20.359 T:1041    error <general>: CPythonInvoker(1, /storage/.kodi/addons/service.joy-it.fancontrol/fan.py): script didn't stop in 5 seconds - let's kill it

    _PvD Guess without any knowledge about gpiozero: GPIO "resource" is not freed because thread is killed instead of terminated gracefully.

  • Autostart bei Aufnahme / Autostart on recording

    Usually this is caused by Kodi hanging or crashing at shutdown and not writing wakeup information.

    Unfortunately on your old LE 11 system pasting logs does not work any more because http://ix.io service was suspended. To upload it manually do (e.g.):

    Code
    cat /storage/.kodi/temp/kodi.old.log | nc termbin.com 9999

    You may consider updating to LE12.

    Looking at the HW side the RTC battery may be dead. Having an older PC it is always worth just to replace the CR2032 on the motherboard. Remember to reset the BIOS/firmware settings to default after that.