Errors when starting NAS

  • Good morning. At the start of my NAS, I've noticed that it shows 3 errors that I believe are related to the GPU pro as even I am somewhat a newbie with OMV/Linux I prefer to refer to as people who know much more than me. I've looking on the internet and say this:



    You do not have installed the package firmware-linux-nonfree.


    If you don't have non-free firmware or free sources of Debian, add them, then install the non-free firmware and restart.


    Loading...




    Not sure if it is what I need to correct the errors. On the Nas boots up as normal apparently


    Any sugestion?


    Best regards


    This 3 messages.................


    [drm] *ERROR* GT0: GuC firmware i915/tgl_guc7obin: fetch failed - ENDENT


    [drm] *ERROR* GT0: GuC initializacion failerd - ENDENT


    [drm] *ERROR* GT0: Enabling uc failed (-5)


    [drm} *ERROR* GT0: Enabling uc failed to initialize GPU, declaring it wedged!

  • Hello, I first ran "sudo apt update" and then "sudo apt install firmware-misc-nonfree" via SSH, and the system says I already have the latest version installed. Now I've run "dmesg | grep i915" and the log output is:


    root@xxxxxx:~# dmesg | grep i915

    [ 10.606168] i915 0000:00:02.0: [drm] Found ALDERLAKE_P/ADL-N (device ID 46d1) display version 13.00 stepping D0

    [10.606770] i915 0000:00:02.0: [drm] VT-d active for gfx access

    [10.607102] i915 0000:00:02.0: vgaarb: deactivate vga console

    [10.607158] i915 0000:00:02.0: [drm] Using Transparent Hugepages

    [10.608223] i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=io+mem

    [10.611533] i915 0000:00:02.0: firmware: failed to load i915/adlp_dmc.bin (-2)

    [10.611541] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_70.bin (-2)

    [10.611543] i915 0000:00:02.0: firmware: failed to load i915/adlp_dmc.bin (-2)

    [10.611547] i915 0000:00:02.0: firmware: failed to load i915/adlp_dmc.bin (-2)

    [ 10.611549] i915 0000:00:02.0: Direct firmware load for i915/adlp_dmc.bin failed with error -2

    [10.611551] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_70.bin (-2)

    [10.611557] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_70.bin (-2)

    [10.611558] i915 0000:00:02.0: firmware: failed to load i915/adlp_dmc_ver2_16.bin (-2)

    [10.611563] i915 0000:00:02.0: firmware: failed to load i915/adlp_dmc_ver2_16.bin (-2)

    [10.611568] i915 0000:00:02.0: firmware: failed to load i915/adlp_dmc_ver2_16.bin (-2)

    [10.611568] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_70.1.1.bin (-2)

    [ 10.611570] i915 0000:00:02.0: Direct firmware load for i915/adlp_dmc_ver2_16.bin failed with error -2

    [10.611571] i915 0000:00:02.0: [drm] Failed to load DMC firmware i915/adlp_dmc.bin (-ENOENT). Disabling runtime power management.

    [10.611573] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_70.1.1.bin (-2)

    [10.611573] i915 0000:00:02.0: [drm] DMC firmware homepage: https://git.kernel.org/pub/scm…rmware/linux-firmware.git

    [10.611578] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_70.1.1.bin (-2)

    [10.611584] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_69.0.3.bin (-2)

    [10.611595] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_69.0.3.bin (-2)

    [10.611600] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_69.0.3.bin (-2)

    [ 10.611601] i915 0000:00:02.0: [drm] *ERROR* GT0: GuC firmware i915/tgl_guc_70.bin: fetch failed -ENOENT

    [10.611607] i915 0000:00:02.0: [drm] GT0: GuC firmware(s) can be downloaded from https://git.kernel.org/pub/scm…ux-firmware.git/tree/i915

    [ 10.612318] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/tgl_guc_70.bin version 0.0.0

    [ 10.612393] i915 0000:00:02.0: [drm] *ERROR* GT0: GuC initialization failed -ENOENT

    [ 10.612397] i915 0000:00:02.0: [drm] *ERROR* GT0: Enabling uc failed (-5)

    [10.612400] i915 0000:00:02.0: [drm] *ERROR* GT0: Failed to initialize GPU, declaring it wedged!

    [ 10.612762] i915 0000:00:02.0: [drm] CI tainted: 0x9 by intel_gt_init+0xb2/0x2f0 [i915]

    [ 10.712751] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])

    [ 10.748272] [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 0

    [12.732328] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])

    [12.734110] fbcon: i915drmfb (fb0) is primary device

    [12.821256] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device


    I have searched for the files mentioned in the log and the system has not found them.



    Any help are wellcome.

    All the best

    OMV 8.0.9-1 (Synchrony); CPU: Intel N100 x64; 16 Gb RAM; OMV in Pendrive 64 Gb, Dockers in Nvme 1 Tb; Personanl data Raid 5 11 Tb

  • I can't help with the specifics of an N100 and the potential GPU BIOS settings, but the i915 stuff is all intel GPU driver related.


    Depending on the motherboard, the GPU core may not be completely "alive" if there is no monitor connected to the system, to which I ask, are you running headless?


    If that is the issue and you want to continue running headless, if there are no BIOS settings that can help, you could potentially us a little HDMI dummy plug to get the GPU to come "alive" completely.


    If you don't know what I am referring to, you can readily find them on amazon for $10 or less

    Amazon.ca: Hdmi Dummy Plug

    Asrock B450M, AMD 5600G, 64GB RAM, 6 x 4TB RAID 5 array, 2 x 10TB RAID 1 array, 100GB SSD for OS, 1TB SSD for docker and VMs, 1TB external SSD for fsarchiver OS and docker data daily backups

  • Hi. NAS is connected to Hdmi monitor (2040P) alzó is connected keyboard.


    Regards

    OMV 8.0.9-1 (Synchrony); CPU: Intel N100 x64; 16 Gb RAM; OMV in Pendrive 64 Gb, Dockers in Nvme 1 Tb; Personanl data Raid 5 11 Tb

  • In that case, did you install the driver as your searching suggested?


    I will have to defer to others that have experience with the oddities of an n100.

    Asrock B450M, AMD 5600G, 64GB RAM, 6 x 4TB RAID 5 array, 2 x 10TB RAID 1 array, 100GB SSD for OS, 1TB SSD for docker and VMs, 1TB external SSD for fsarchiver OS and docker data daily backups

  • Good morning. I have contacted the support of my Intel motherboard N100 and after sending the log I have commented the following:


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


    Thank you for providing the detailed logs — they are very helpful.


    Based on the dmesg output, the issue is almost certainly caused by missing Intel GPU firmware files, rather than a hardware problem with the motherboard.


    The key indicator is the repeated error:



    “[ 10.611601] i915 0000:00:02.0: [drm] *ERROR* GT0: GuC firmware i915/tgl_guc_70.bin: fetch failed -ENOENT”


    In Linux, -ENOENT literally means “file not found.”

    This tells us the system is trying to load firmware such as:


    - i915/adlp_dmc.bin

    - i915/adlp_dmc_ver2_16.bin

    - i915/tgl_guc_70.bin


    but those files are not present in /lib/firmware/i915/.


    Why this happens


    Although firmware-misc-nonfree is installed, newer Intel CPUs like Alder Lake-N (N100) often require very recent linux-firmware packages. Some Debian / OMV builds ship with firmware that is slightly outdated, so the GPU driver looks for files that are not included yet.


    This is a common Linux firmware version mismatch, not a motherboard defect.


    Also importantly — your log shows:


    [drm] Initialized i915

    fb0: i915drmfb frame buffer device


    This means the GPU is still working in a basic mode. The missing firmware mainly affects:


    - Power management

    - Hardware video acceleration

    - Some performance optimizations


    For a NAS system, this usually does not impact normal operation unless you rely on hardware transcoding.


    Recommended Fix (Most Effective)


    Please manually update the Intel firmware from the official Linux repository:


    1. Download the latest firmware package:


    kernel/git/firmware/linux-firmware.git - Repository of firmware blobs for use with the Linux kernel


    You can download it directly on the system:


    2. Rebuild initramfs and reboot:


    After reboot, run:


    The firmware errors should disappear.


    Alternative (Often Easier)


    If available for your OMV version, upgrading to a newer kernel can also resolve this automatically because newer kernels expect the matching firmware.


    Important Note


    This behavior is related to the Linux firmware ecosystem and is not caused by faulty hardware. Your motherboard is functioning normally.


    If the system is stable, you may even choose to ignore these warnings — many headless NAS users do.


    If you need any further assistance, please feel free to contact us anytime — we are happy to help.


    Best regards,

    CWWK Official


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

    I went to the url that tells me the manufacturer but I do not see anything related to GPU Intel Alder Lake (N100):



    I have gone to the url indicated by the manufacturer but I do not see anything related to Intel alder Lake GPU (N100). On the other hand, the motherboard support comments that the most effective thing is to run 'Rebuild initramfs' but searching on the internet it is not clear to me how to do it.


    All the best

    OMV 8.0.9-1 (Synchrony); CPU: Intel N100 x64; 16 Gb RAM; OMV in Pendrive 64 Gb, Dockers in Nvme 1 Tb; Personanl data Raid 5 11 Tb

    • New
    • Official Post

    If available for your OMV version, upgrading to a newer kernel can also resolve this automatically because newer kernels expect the matching firmware.

    This is the same suggestion I made in my previous post.

    • New
    • Official Post

    This is the same suggestion I made in my previous post.

    Perhaps I should have provided more explanation in my first post about how that solution would solve the problem.


    I'm sorry, but I think I've become a bit lazy over time. :)

  • Hello I tried to install OMV kernel pluggin in and out a red error.


    ...in the task get this:

    Code
    Instalar plugin
    Reading package lists...
    Building dependency tree...
    Reading state information...
    
    ** CONNECTION LOST **


    System is un Pendrive class 10 64 Gb with 44 Gb free espace


    Regards

    OMV 8.0.9-1 (Synchrony); CPU: Intel N100 x64; 16 Gb RAM; OMV in Pendrive 64 Gb, Dockers in Nvme 1 Tb; Personanl data Raid 5 11 Tb

    Edited 4 times, last by tipitao ().

    • New
    • Official Post

    I tried to install OMV kernel pluggin in and out a red error

    Copy the error from the bell icon to the clipboard and paste it into a code box.


    (That's why I get lazy; it's boring to repeat the same things all the time...)

    • New
    • Official Post

    You need to copy the error message and post it here in full. Without the error message, we can't figure out what's wrong with your system. Please read the link I gave you.

  • Hello I have copied the contents of the bell to the clipboard (failed to download/run the pluggin OMV

    openmediavault-kernel 8.0.6 kernel package).



    Regards

    OMV 8.0.9-1 (Synchrony); CPU: Intel N100 x64; 16 Gb RAM; OMV in Pendrive 64 Gb, Dockers in Nvme 1 Tb; Personanl data Raid 5 11 Tb

  • Hi. I've upgrade now from OMV 8.0.8-1. New version is


    Información del sistema
    Nombre de equipo
    xxxxxxx.local

    Versión
    8.0.9-1 (Synchrony)

    Procesador
    Intel(R) N100

    Kernel
    Linux 6.12.63+deb13-amd64

    Hora del sistema
    sáb 31 ene 2026 17:49:15

    Tiempo en funcionamiento
    una hora


    Hi rebbot NAS and thi OMV upgrade don´t fix3 error


    Code
    drm] *ERROR* GT0: GuC firmware i915/tgl_guc7obin: fetch failed - ENDENT
    [drm] *ERROR* GT0: GuC initializacion failerd - ENDENT
    [drm] *ERROR* GT0: Enabling uc failed (-5)
    [drm} *ERROR* GT0: Enabling uc failed to initialize GPU, declaring it wedged!

    Regards

    OMV 8.0.9-1 (Synchrony); CPU: Intel N100 x64; 16 Gb RAM; OMV in Pendrive 64 Gb, Dockers in Nvme 1 Tb; Personanl data Raid 5 11 Tb

    Edited once, last by tipitao ().

    • New
    • Official Post

    Hi rebbot NAS and thi OMV upgrade don´t fix3 error

    Have you already installed omv-kernel? Have you already installed kernel 6.14?

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!