• Intel HD Graphics is slower than it should be

    Recordings were made under clear linux, i had this problem so long that i though my intel core i3-380M cpu does not capable to achive 60fps, then when i switched clear linux from ubuntu 17.04, i amazed with the results but after updates clear linux performance dropped to 40~ fps , now i am having the same issue with antregos , i had with ubuntu too. there is not so much documentary about ironlake processors. Both videos recorded with simple screen recorder with ffvhuff codec under clear linux

    Before slowdown:
    Youtube: https://youtu.be/oA6yGPHFGrI , Google Drive: https://drive.google.com/open?id=1jkQCTjTWcI6q8jb4X5UO_qqO1VT-N_BJ
    After slowdown:
    Youtube: https://youtu.be/9QIlXvdvlIc , Google Drive: https://drive.google.com/open?id=1tCWHQysW8tBzqfu5DIDpksWLHJ7dDgry

    [[email protected] ~]$ dmesg > dmesg.txt
    [[email protected] ~]$ glxinfo > glxinfo.txt
    [[email protected] ~]$ sudo systool -m i915 -av > systool.txt
    [sudo] password for utku: 
    [[email protected] ~]$ xrandr --verbose > xrandr.txt
    [[email protected] ~]$ uname -a
    Linux utku 4.14.14-1-ARCH #1 SMP PREEMPT Fri Jan 19 18:42:04 UTC 2018 x86_64 GNU/Linux


  • @tuxutku

    The Clear Linux* Project for Intel® Architecture is a distribution built for cloud and IoT use cases

    This can be used on desktops too? I have no idea how this project works, check their documentation, maybe there’s something in there: https://clearlinux.org/documentation/clear-linux

    now i am having the same issue with antregos

    The best guess is usually drivers, maybe update them to a new version or go back to an older version, it usually fix things.

    Official Intel Graphics for Linux website: https://01.org/ , maybe the answer is there.

  • @ssspacez i don’t know when the slow down happened or what realy causes this, i don’t know which driver i should revert to, drivers were loading and 3d applications does work but gnome desktop environment for example jiggers (unity does not had a problem like that), 3d real time rendering %25 slower than how its should be, Arch linux page does not give information about ironlake cpu issues, (ironlake is the first generation of mobile intel core processors and skylake is realy different from ironlake) my main question is what triggers this and are people noticing it? (i didn’t knew that it was slower than how its should be even when i was using unity and desktop environment was fluid) intel didn’t respond when i opened issue on clear linux github page https://github.com/clearlinux/distribution/issues/9, and there is no results of someone else had this issue and get response.

    sorry if i made grammar mistakes because my english is not well

  • from your dmesg: [ 12.571075] intel ips 0000:00:1f.6: failed to get i915 symbols, graphics turbo disabled until i915 loads

    @tuxutku you should take a look here: https://wiki.archlinux.org/index.php/Intel_graphics#Enable_early_KMS
    may do you not using early load with KMS? or missing Enable GuC / HuC firmware loading e.t.c.

  • Did you try switching the Desktop Environment? Maybe Gnome/Unity is too heavy for your hardware and they are slowing everything and causing the FPS drop, try a lighter Desktop Environment like Xfce or MATE. I have a Intel HD Graphics 3000 and it works fine with Xfce, it uses on average just 400 MB RAM, Cinnamon or Gnome are too heavy for my laptop, I’ve noticed that the FPS dropped in a few games when I was using them.

  • Check this Intel benchmark I’ve found:


    Some games with Gnome Wayland have worse FPS than Gnome Xorg, maybe this is the cause of the FPS drop. This is a Ubuntu benchmark, but maybe it applies to Arch based distro too, I don’t know. I recommend switching the Desktop Environment to get higher FPS.

  • @joekamprad https://01.org/linuxgraphics/downloads/firmware does not contain ironlake firmware, ironlake is the first generation and oldest generation that supports guc and huc firmware is kabylake (9th generation) as i understand

    [[email protected] BombSquad_Linux_64bit_1.4.128]$ sudo cat /sys/kernel/debug/dri/0/i915_guc_info
    [sudo] password for utku: 
    GuC submission not supported

    And i have used early load with KMS but nothing is changed :

  • @ssspacez i have used xfce while recording both of the videos and i am still using xfce

  • do you have two MODULES lines inside mkinitcpio as you show in the shot?

    only one will be valid … only to make sure you try it right.

    Türkiye’ye selamlar!

  • @joekamprad Thanks for correcting, it seems to load earlier but performance didn’t changed
    new dmesg output: dmesg2.txt

    [[email protected] ~]$ cat /etc/mkinitcpio.conf
    # vim:set ft=sh
    # The following modules are loaded before any boot hooks are
    # run.  Advanced users may wish to specify all system modules
    # in this array.  For instance:
    #     MODULES=(piix ide_disk reiserfs)
    MODULES=(... i915 ...)
    # This setting includes any additional binaries a given user may
    # wish into the CPIO image.  This is run last, so it may be used to
    # override the actual binaries included by a given hook
    # BINARIES are dependency parsed, so you may safely ignore libraries
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in any way.  This is useful for config files.
    # HOOKS
    # This is the most important setting in this file.  The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    ##   This setup specifies all modules in the MODULES setting above.
    ##   No raid, lvm2, or encrypted root is needed.
    #    HOOKS=(base)
    ##   This setup will autodetect all modules for your system and should
    ##   work as a sane default
    #    HOOKS=(base udev autodetect block filesystems)
    ##   This setup will generate a 'full' image which supports most systems.
    ##   No autodetection is done.
    #    HOOKS=(base udev block filesystems)
    ##   This setup assembles a pata mdadm array with an encrypted root FS.
    ##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
    #    HOOKS=(base udev block mdadm encrypt filesystems)
    ##   This setup loads an lvm2 volume group on a usb device.
    #    HOOKS=(base udev block lvm2 filesystems)
    ##   NOTE: If you have /usr on a separate partition, you MUST include the
    #    usr, fsck and shutdown hooks.
    HOOKS="base udev autodetect modconf block keyboard keymap resume filesystems fsck"
    # Use this to compress the initramfs image. By default, gzip compression
    # is used. Use 'cat' to create an uncompressed image.
    # Additional options for the compressor

    Türkiye’ye selamlar!

    Teşekkürler , sizlerede selam

  • @joekamprad said in Intel HD Graphics is slower than it should be:

    symbols, graphics turbo disabled until i915 loads

    is not showing up anymore …

  • I have runned glmark2 for extra information, closed all other applications before running glmark2

    [[email protected] ~]$ glmark2 > glmark2.txt
    [[email protected] ~]$ cat glmark2.txt
        glmark2 2017.07
        OpenGL Information
        GL_VENDOR:     Intel Open Source Technology Center
        GL_RENDERER:   Mesa DRI Intel(R) Ironlake Mobile 
        GL_VERSION:    2.1 Mesa 17.3.3
    [build] use-vbo=false: FPS: 386 FrameTime: 2.591 ms
    [build] use-vbo=true: FPS: 390 FrameTime: 2.564 ms
    [texture] texture-filter=nearest: FPS: 406 FrameTime: 2.463 ms
    [texture] texture-filter=linear: FPS: 398 FrameTime: 2.513 ms
    [texture] texture-filter=mipmap: FPS: 400 FrameTime: 2.500 ms
    [shading] shading=gouraud: FPS: 305 FrameTime: 3.279 ms
    [shading] shading=blinn-phong-inf: FPS: 295 FrameTime: 3.390 ms
    [shading] shading=phong: FPS: 250 FrameTime: 4.000 ms
    [shading] shading=cel: FPS: 242 FrameTime: 4.132 ms
    [bump] bump-render=high-poly: FPS: 169 FrameTime: 5.917 ms
    [bump] bump-render=normals: FPS: 433 FrameTime: 2.309 ms
    [bump] bump-render=height: FPS: 393 FrameTime: 2.545 ms
    [effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 237 FrameTime: 4.219 ms
    [effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 99 FrameTime: 10.101 ms
    [pulsar] light=false:quads=5:texture=false: FPS: 356 FrameTime: 2.809 ms
    [desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 94 FrameTime: 10.638 ms
    [desktop] effect=shadow:windows=4: FPS: 236 FrameTime: 4.237 ms
    [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 182 FrameTime: 5.495 ms
    [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 183 FrameTime: 5.464 ms
    [buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 193 FrameTime: 5.181 ms
    [ideas] speed=duration: FPS: 304 FrameTime: 3.289 ms
    [jellyfish] <default>: FPS: 195 FrameTime: 5.128 ms
    [terrain] <default>: FPS: 15 FrameTime: 66.667 ms
    [shadow] <default>: FPS: 192 FrameTime: 5.208 ms
    [refract] <default>: FPS: 34 FrameTime: 29.412 ms
    [conditionals] fragment-steps=0:vertex-steps=0: FPS: 411 FrameTime: 2.433 ms
    [conditionals] fragment-steps=5:vertex-steps=0: FPS: 348 FrameTime: 2.874 ms
    [conditionals] fragment-steps=0:vertex-steps=5: FPS: 409 FrameTime: 2.445 ms
    [function] fragment-complexity=low:fragment-steps=5: FPS: 407 FrameTime: 2.457 ms
    [function] fragment-complexity=medium:fragment-steps=5: FPS: 332 FrameTime: 3.012 ms
    [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 385 FrameTime: 2.597 ms
    [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 385 FrameTime: 2.597 ms
    [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 330 FrameTime: 3.030 ms
                                      glmark2 Score: 284 

    I have also runned :

    [[email protected] ~]$ LIBGL_DEBUG=verbose MESA_LOG_FILE=/home/utku/mesaglmark2log.txt GALLIUM_LOG_FILE=/home/utku/galliumglmark2log.txt VC4_DEBUG=perf INTEL_DEBUG=perf SOFTPIPE_DUMP_FS=1 SOFTPIPE_DUMP_GS=1 glmark2 -d > glmark2_2.txt 2>&1

    /home/utku/galliumglmark2log.txt and /home/utku/mesaglmark2log.txt files were not created but glmark2_2.txt file is quite verbose (10,7 MB)

    Also compressed version: glmark2_2.txt.xz

    There are buffer warnings:

    WC mapping a busy “bufferobj” BO stalled and took 3.421 ms

    Using a blit copy to avoid stalling on glBufferSubData(200172, 216000) (15kb) to a busy (0-288000) / valid (0-288000) buffer object.

  • i have forked this issue to intel: https://communities.intel.com/message/522012#522012 i hope they will response

  • @tuxutku can you find one question on https://communities.intel.com with an answear?
    It looks like there is no response.

  • @joekamprad No i couldn’t find any results

  • oh here:


    But Question is made by a dev and responds are all from “users”

  • @joekamprad my VGA monitor is 60 hz and i can use at 60 hz, glxgears works at 60fps and if application is simple enough it will run at 60fps, problem is 3d rendering is lot slower compared to how its been

  • @joekamprad intel respond me with giving this link: https://communities.intel.com/external-link.jspa?url=https%3A%2F%2Fdownloadcenter.intel.com%2Fproduct%2F50178%2FIntel-Core-i3-380M-Processor-3M-Cache-2-53-GHz- and i am downloaded: https://downloadcenter.intel.com/download/27337/Linux-Processor-Microcode-Data-File?product=50178 i will try to install it
    for now dmesg | grep microcode gives:

    [[email protected] ~]$ dmesg | grep microcode
    [    0.000000] microcode: microcode updated early to revision 0x4, date = 2013-06-28
    [    0.702698] microcode: sig=0x20655, pf=0x10, revision=0x4
    [    0.702894] microcode: Microcode Update Driver: v2.2.


  • hm ? thats nice from them :)
    I was thinking that microcode gets updated automatic if you configure it?

    While microcode can be updated through the BIOS, the Linux kernel is also able to apply these updates during boot
    For Intel processors, install the intel-ucode package, and continue reading.

  • @joekamprad i am not sure that i am correctly updated my frimware:

    [[email protected] microcode-20171117]$ ls
    intel-ucode  microcode.dat  releasenote
    [[email protected] microcode-20171117]$ sudo cp -v intel-ucode/* /lib/firmware/intel-ucode/
    [sudo] password for utku: 
    'intel-ucode/06-03-02' -> '/lib/firmware/intel-ucode/06-03-02'
    'intel-ucode/06-05-00' -> '/lib/firmware/intel-ucode/06-05-00'
    'intel-ucode/06-05-01' -> '/lib/firmware/intel-ucode/06-05-01'
    'intel-ucode/06-05-02' -> '/lib/firmware/intel-ucode/06-05-02'
    'intel-ucode/06-05-03' -> '/lib/firmware/intel-ucode/06-05-03'
    'intel-ucode/06-06-00' -> '/lib/firmware/intel-ucode/06-06-00'
    'intel-ucode/06-06-05' -> '/lib/firmware/intel-ucode/06-06-05'
    'intel-ucode/06-06-0a' -> '/lib/firmware/intel-ucode/06-06-0a'
    'intel-ucode/06-06-0d' -> '/lib/firmware/intel-ucode/06-06-0d'
    'intel-ucode/06-07-01' -> '/lib/firmware/intel-ucode/06-07-01'
    'intel-ucode/06-07-02' -> '/lib/firmware/intel-ucode/06-07-02'
    'intel-ucode/06-07-03' -> '/lib/firmware/intel-ucode/06-07-03'
    'intel-ucode/06-08-01' -> '/lib/firmware/intel-ucode/06-08-01'
    'intel-ucode/06-08-03' -> '/lib/firmware/intel-ucode/06-08-03'
    'intel-ucode/06-08-06' -> '/lib/firmware/intel-ucode/06-08-06'
    'intel-ucode/06-08-0a' -> '/lib/firmware/intel-ucode/06-08-0a'
    'intel-ucode/06-09-05' -> '/lib/firmware/intel-ucode/06-09-05'
    'intel-ucode/06-0a-00' -> '/lib/firmware/intel-ucode/06-0a-00'
    'intel-ucode/06-0a-01' -> '/lib/firmware/intel-ucode/06-0a-01'
    'intel-ucode/06-0b-01' -> '/lib/firmware/intel-ucode/06-0b-01'
    'intel-ucode/06-0b-04' -> '/lib/firmware/intel-ucode/06-0b-04'
    'intel-ucode/06-0d-06' -> '/lib/firmware/intel-ucode/06-0d-06'
    'intel-ucode/06-0e-08' -> '/lib/firmware/intel-ucode/06-0e-08'
    'intel-ucode/06-0e-0c' -> '/lib/firmware/intel-ucode/06-0e-0c'
    'intel-ucode/06-0f-02' -> '/lib/firmware/intel-ucode/06-0f-02'
    'intel-ucode/06-0f-06' -> '/lib/firmware/intel-ucode/06-0f-06'
    'intel-ucode/06-0f-07' -> '/lib/firmware/intel-ucode/06-0f-07'
    'intel-ucode/06-0f-0a' -> '/lib/firmware/intel-ucode/06-0f-0a'
    'intel-ucode/06-0f-0b' -> '/lib/firmware/intel-ucode/06-0f-0b'
    'intel-ucode/06-0f-0d' -> '/lib/firmware/intel-ucode/06-0f-0d'
    'intel-ucode/06-16-01' -> '/lib/firmware/intel-ucode/06-16-01'
    'intel-ucode/06-17-06' -> '/lib/firmware/intel-ucode/06-17-06'
    'intel-ucode/06-17-07' -> '/lib/firmware/intel-ucode/06-17-07'
    'intel-ucode/06-17-0a' -> '/lib/firmware/intel-ucode/06-17-0a'
    'intel-ucode/06-1a-04' -> '/lib/firmware/intel-ucode/06-1a-04'
    'intel-ucode/06-1a-05' -> '/lib/firmware/intel-ucode/06-1a-05'
    'intel-ucode/06-1c-02' -> '/lib/firmware/intel-ucode/06-1c-02'
    'intel-ucode/06-1c-0a' -> '/lib/firmware/intel-ucode/06-1c-0a'
    'intel-ucode/06-1d-01' -> '/lib/firmware/intel-ucode/06-1d-01'
    'intel-ucode/06-1e-05' -> '/lib/firmware/intel-ucode/06-1e-05'
    'intel-ucode/06-25-02' -> '/lib/firmware/intel-ucode/06-25-02'
    'intel-ucode/06-25-05' -> '/lib/firmware/intel-ucode/06-25-05'
    'intel-ucode/06-26-01' -> '/lib/firmware/intel-ucode/06-26-01'
    'intel-ucode/06-2a-07' -> '/lib/firmware/intel-ucode/06-2a-07'
    'intel-ucode/06-2d-06' -> '/lib/firmware/intel-ucode/06-2d-06'
    'intel-ucode/06-2d-07' -> '/lib/firmware/intel-ucode/06-2d-07'
    'intel-ucode/06-2f-02' -> '/lib/firmware/intel-ucode/06-2f-02'
    'intel-ucode/06-3a-09' -> '/lib/firmware/intel-ucode/06-3a-09'
    'intel-ucode/06-3c-03' -> '/lib/firmware/intel-ucode/06-3c-03'
    'intel-ucode/06-3d-04' -> '/lib/firmware/intel-ucode/06-3d-04'
    'intel-ucode/06-3e-04' -> '/lib/firmware/intel-ucode/06-3e-04'
    'intel-ucode/06-3e-06' -> '/lib/firmware/intel-ucode/06-3e-06'
    'intel-ucode/06-3e-07' -> '/lib/firmware/intel-ucode/06-3e-07'
    'intel-ucode/06-3f-02' -> '/lib/firmware/intel-ucode/06-3f-02'
    'intel-ucode/06-3f-04' -> '/lib/firmware/intel-ucode/06-3f-04'
    'intel-ucode/06-45-01' -> '/lib/firmware/intel-ucode/06-45-01'
    'intel-ucode/06-46-01' -> '/lib/firmware/intel-ucode/06-46-01'
    'intel-ucode/06-47-01' -> '/lib/firmware/intel-ucode/06-47-01'
    'intel-ucode/06-4e-03' -> '/lib/firmware/intel-ucode/06-4e-03'
    'intel-ucode/06-4f-01' -> '/lib/firmware/intel-ucode/06-4f-01'
    'intel-ucode/06-55-04' -> '/lib/firmware/intel-ucode/06-55-04'
    'intel-ucode/06-56-02' -> '/lib/firmware/intel-ucode/06-56-02'
    'intel-ucode/06-56-03' -> '/lib/firmware/intel-ucode/06-56-03'
    'intel-ucode/06-56-04' -> '/lib/firmware/intel-ucode/06-56-04'
    'intel-ucode/06-5c-09' -> '/lib/firmware/intel-ucode/06-5c-09'
    'intel-ucode/06-5e-03' -> '/lib/firmware/intel-ucode/06-5e-03'
    'intel-ucode/06-7a-01' -> '/lib/firmware/intel-ucode/06-7a-01'
    'intel-ucode/06-8e-09' -> '/lib/firmware/intel-ucode/06-8e-09'
    'intel-ucode/06-8e-0a' -> '/lib/firmware/intel-ucode/06-8e-0a'
    'intel-ucode/06-9e-09' -> '/lib/firmware/intel-ucode/06-9e-09'
    'intel-ucode/06-9e-0a' -> '/lib/firmware/intel-ucode/06-9e-0a'
    'intel-ucode/06-9e-0b' -> '/lib/firmware/intel-ucode/06-9e-0b'
    'intel-ucode/0f-00-07' -> '/lib/firmware/intel-ucode/0f-00-07'
    'intel-ucode/0f-00-0a' -> '/lib/firmware/intel-ucode/0f-00-0a'
    'intel-ucode/0f-01-02' -> '/lib/firmware/intel-ucode/0f-01-02'
    'intel-ucode/0f-02-04' -> '/lib/firmware/intel-ucode/0f-02-04'
    'intel-ucode/0f-02-05' -> '/lib/firmware/intel-ucode/0f-02-05'
    'intel-ucode/0f-02-06' -> '/lib/firmware/intel-ucode/0f-02-06'
    'intel-ucode/0f-02-07' -> '/lib/firmware/intel-ucode/0f-02-07'
    'intel-ucode/0f-02-09' -> '/lib/firmware/intel-ucode/0f-02-09'
    'intel-ucode/0f-03-02' -> '/lib/firmware/intel-ucode/0f-03-02'
    'intel-ucode/0f-03-03' -> '/lib/firmware/intel-ucode/0f-03-03'
    'intel-ucode/0f-03-04' -> '/lib/firmware/intel-ucode/0f-03-04'
    'intel-ucode/0f-04-01' -> '/lib/firmware/intel-ucode/0f-04-01'
    'intel-ucode/0f-04-03' -> '/lib/firmware/intel-ucode/0f-04-03'
    'intel-ucode/0f-04-04' -> '/lib/firmware/intel-ucode/0f-04-04'
    'intel-ucode/0f-04-07' -> '/lib/firmware/intel-ucode/0f-04-07'
    'intel-ucode/0f-04-08' -> '/lib/firmware/intel-ucode/0f-04-08'
    'intel-ucode/0f-04-09' -> '/lib/firmware/intel-ucode/0f-04-09'
    'intel-ucode/0f-04-0a' -> '/lib/firmware/intel-ucode/0f-04-0a'
    'intel-ucode/0f-06-02' -> '/lib/firmware/intel-ucode/0f-06-02'
    'intel-ucode/0f-06-04' -> '/lib/firmware/intel-ucode/0f-06-04'
    'intel-ucode/0f-06-05' -> '/lib/firmware/intel-ucode/0f-06-05'
    'intel-ucode/0f-06-08' -> '/lib/firmware/intel-ucode/0f-06-08'
    [[email protected] microcode-20171117]$ sudo su -c 'echo 1 > /sys/devices/system/cpu/microcode/reload'
    [[email protected] microcode-20171117]$ sudo mkinitcpio -p linux
    [sudo] password for utku: 
    ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
      -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    ==> Starting build: 4.14.15-1-ARCH
      -> Running build hook: [base]
      -> Running build hook: [udev]
      -> Running build hook: [autodetect]
      -> Running build hook: [modconf]
      -> Running build hook: [block]
      -> Running build hook: [keyboard]
      -> Running build hook: [keymap]
      -> Running build hook: [resume]
      -> Running build hook: [filesystems]
      -> Running build hook: [fsck]
    ==> ERROR: module not found: `...'
    ==> ERROR: module not found: `...'
    ==> Generating module dependencies
    ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
    ==> WARNING: errors were encountered during the build. The image may not be complete.
    ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
      -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    ==> Starting build: 4.14.15-1-ARCH
      -> Running build hook: [base]
      -> Running build hook: [udev]
      -> Running build hook: [modconf]
      -> Running build hook: [block]
    ==> WARNING: Possibly missing firmware for module: wd719x
    ==> WARNING: Possibly missing firmware for module: aic94xx
      -> Running build hook: [keyboard]
      -> Running build hook: [keymap]
      -> Running build hook: [resume]
      -> Running build hook: [filesystems]
      -> Running build hook: [fsck]
    ==> ERROR: module not found: `...'
    ==> ERROR: module not found: `...'
    ==> Generating module dependencies
    ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
    ==> WARNING: errors were encountered during the build. The image may not be complete.

    i will reboot and see if i updated the firmware

intel39 graphics27 slower2 Posts 25Views 2238
Bloom Email Optin Plugin

Looks like your connection to Antergos Community Forum was lost, please wait while we try to reconnect.