intel i915 video driver

  • This topic has 14 replies, 5 voices, and was last updated Apr 6-4:45 pm by zpimp.
Viewing 15 posts - 1 through 15 (of 15 total)
  • Author
    Posts
  • #8648
    Member
    zpimp

      i have a lenovo notebook with cpu i3-5010u with intel graphics hd5500
      posted about this before, antix17 hangs at blackscreen, and it seems to be the video driver
      like instructed before , i used boot parameter “3” to avoid loading x and cli-installer to install

      then i changed the kernel to latest, 4.15 iirc, thinking will also update the video driver, but the problem persists

      then i added testing repos and updated the xserver-xorg-video-intel
      i had 2.99.917+git20161206-1
      updated to 2.99.917+git20171229-1

      still same problem
      does anyone have an idea how to tackle this problem?

      offtopic: i wanted to post a thread yesterday in tips’n’tricks, it showed me as latest poster in main forum, but i cant see the thread, it was about multiboot usb grub iso loop, didnt think the problem deserved its own thread

      #8657
      Forum Admin
      rokytnji
        Helpful
        Up
        0
        ::

        hmm. Let me see what video chip is on my AntiX 17 full 64bit Dell I5 computer.

        harry@biker:~
        $ uname -a
        Linux biker 4.15.9-antix.1-amd64-smp #2 SMP PREEMPT Tue Mar 13 17:58:48 EET 2018 x86_64 GNU/Linux

        harry@biker:~
        $ pinxi -G
        Graphics: Card-1: Intel Core Processor Integrated Graphics driver: i915 v: kernel
        Display Server: X.Org 1.19.2 driver: intel resolution: 1366×768~60Hz
        OpenGL: renderer: Mesa DRI Intel Ironlake Mobile v: 2.1 Mesa 13.0.6
        harry@biker:~
        `
        I had to nothing special with the F key cheat codes to arrive to this point. Updating my kernel was done through cli-aptiX. After my install.
        No black screen for me. Did you md5sum check your iso before install?

        Tips and tricks are for users that have already found a solution on how to overcome a problem or run a application. It is not for questions. I have moved questions in tips and tricks to New User because of that. If I misunderstood you grub sentence. Sorry. Maybe you got hit by the spam filters here on that thread.

        Also. What version of AntiX are you running? Post the output of

        inxi -Fxzr

        Edit: starting to wonder if your laptop has one of dual video graphics chips. One on the processor. The other on the board. Like Intel and Nvidia.
        That is why I am asing for the inxi readout. Easy way out is to disable ncvidia chip in bios. And just roll with the intel chip.

        2nd edit: I saw your grub thread on how to section. Your thread is AOKAY there. I am just having trouble trying to trash the double post there.

        • This reply was modified 5 years, 1 month ago by rokytnji.
        • This reply was modified 5 years, 1 month ago by rokytnji.

        Sometimes I drive a crooked road to get my mind straight.
        Not all who Wander are Lost.
        I'm not outa place. I'm from outer space.

        Linux Registered User # 475019
        How to Search for AntiX solutions to your problems

        #8667
        Member
        zpimp
          Helpful
          Up
          0
          ::

          i only have one gpu
          inxi -F says intel hd graphics 5500
          display server x,org 1.19.2 drivers: modesetting (unloaded: fbdev,vesa)
          i used boot parameter “3” to prevent loading x

          im running antix 17.1 386,i tried x64 as well
          i checked md5 of both, also tried antix17 before, same result

          antix15.1 boots
          antix16.2 boots
          antix17 boots only with safe video mode “quiet splash=v disable=lx nomodeset xorg=safe” wich apparently loads the vesa driver

          #8669
          Forum Admin
          anticapitalista
            Helpful
            Up
            0
            ::

            You probably need the older version of xserver-xorg-video-intel.
            Not sure you’ll be able to get it though.

            You could try coping the following from your working antix16.2 to installed antiX-17 (note link is to 64 bit deb)

            xserver-xorg-video-intel/filelist

            You will probably have to either remove any /etc/X11/xorg.conf file (if there is one) or copy over the one on antiX-16.2 (again, if there is one).

            • This reply was modified 5 years, 1 month ago by anticapitalista.

            Philosophers have interpreted the world in many ways; the point is to change it.

            antiX with runit - leaner and meaner.

            #8672
            Member
            zpimp
              Helpful
              Up
              0
              ::

              tried installing older version of xserver-xorg-video-intel from debian v2.21, wich said it needed xorg-videoabi-18 wich when i wanted to install it said it needed xorg-core something, for wich there is no install candidate

              i updated the kernel to 4.15.14 still no go

              got back on xserver-xorg-video-intel 2.99 and deleted /etc/X11/xorg.conf.in the only xorg file i could find there

              still no go
              will try to copy files from antix 16.2

              any idea what is happening, i really have no idea what is going on 🙂
              is this driver part of the kernel, so if i update kernel i update the driver?
              does xserver-xorg-video-intel has something to do with systemd

              debian live boots fine with same package version 2.99.917+git20161206-1
              on debian inxi -F says – “drivers: modesetting (unloaded:fbdev,vesa)”
              does this mean the i915 driver os loaded? on antix16 it says “drivers: intel (unloaded:modesetting,fbdev,vesa)”

              #8677
              Forum Admin
              anticapitalista
                Helpful
                Up
                0
                ::

                It seems like you need older not newer intel drivers. They don’t appear anymore in stretch and later.

                Philosophers have interpreted the world in many ways; the point is to change it.

                antiX with runit - leaner and meaner.

                #8688
                Member
                zpimp
                  Helpful
                  Up
                  0
                  ::

                  copied the files manually from live antix16.2 to installed antix17.1
                  https://packages.debian.org/jessie/amd64/xserver-xorg-video-intel/filelist
                  still no go

                  so
                  antix16.2/xserver-xorg-video-intel_2.21.15-2+b2 – works
                  antix17.1/xserver-xorg-video-intel_2.99.917+git20161206-1 – doesent work
                  debian9.4.0/xserver-xorg-video-intel_2.99.917+git20161206-1 – works

                  and if this wasnt enough, i wanted to test some performance with glxgears
                  antix16.2 vblank_mode=0 glxgears ~ 240fps (intel 2.21 driver)
                  antix17.1 vblank_mode=0 glxgears ~ 900fps (nomodeset – vesa)
                  debian9.4.0 vblank_mode=0 glxgears ~ 6700fps (intel 2.99 driver)
                  i asumed intel driver would get more fps than vesa

                  #8692
                  Moderator
                  caprea
                    Helpful
                    Up
                    0
                    ::

                    You could try to force the intel-driver on antiX17 like shown here in the first example
                    https://mxlinux.org/wiki/hardware/intel-video-driver

                    #8715
                    Member
                    zpimp
                      Helpful
                      Up
                      0
                      ::

                      i dont have that file there only
                      upon creation it said
                      waited 2020ms for i915.ko driver to load
                      no devices detected
                      no screens found
                      edit:
                      after removing nomodeset from grub, it booted to desktop
                      i had the time to check inxi -F and showed the driver as being intel
                      and vblank_mode=0 showed +6k fps
                      in about a minute or less, the system froze
                      even alt+sysrq+e didnt unfroze it. i can change to other terminals but cant type/login
                      caps lock is lit, and doesent change

                      • This reply was modified 5 years, 1 month ago by zpimp.
                      #8717
                      Member
                      ohh
                        Helpful
                        Up
                        0
                        ::

                        Don’t know if this will help but take a look here: 3rd post from the end on pg 1

                        https://forums.linuxmint.com/viewtopic.php?t=250485

                        cheers,
                        ohh

                        Every matter requires prior knowledge.

                        - Du Mu
                        The Art of War

                        #8731
                        Member
                        zpimp
                          Helpful
                          Up
                          0
                          ::

                          it seems this has kinda work
                          https://mxlinux.org/wiki/hardware/intel-video-driver

                          if i keep it busy it seems to work

                          if i dont do nothing it freezes, seems to have something to do woth powersaving, powerstates
                          if i close all programs, in about a minute it freezes

                          1st edit:
                          after searching a bit i found https://askubuntu.com/questions/761706/ubuntu-15-10-and-16-04-keep-freezing-randomly
                          so i added kernel parameter “intel_idle.max_cstate=1”

                          its been 3 mins no freeze, will test some more,
                          is it normal to have constant disk activity 1-2MB ?

                          2nd edit: after searching some more and setting “intel_idle.max_cstate=0”
                          still getting errors in syslog i tried to change driver to modesetting, with no success
                          i tried to make /etc/X11/xorg.conf.d/20-modesetting.conf
                          Section “Device”
                          Identifier “Intel Graphics”
                          Driver “modesetting”
                          Option “AccelMethod” “glamor”
                          Option “DRI” “3”
                          EndSection

                          it goes blackscreen
                          can you give me some hints on this modesetting driver , i read that its a fallback if you uninstall the intel driver, but cant seem to get it working

                          • This reply was modified 5 years, 1 month ago by zpimp.
                          • This reply was modified 5 years, 1 month ago by zpimp.
                          • This reply was modified 5 years, 1 month ago by zpimp.
                          #8752
                          Moderator
                          caprea
                            Helpful
                            Up
                            0
                            ::

                            Normally, if you uninstall the intel-driver
                            sudo apt-get remove xserver-xorg-video-intel

                            and delete the /etc/X11/xorg.conf.d/20-modesetting.conf or intel.conf you created
                            and delete any xorg.conf in /etc/X11

                            the system should boot automatically the modesetting driver.

                            Are you still using any boot-parameters? Because I think the video=safe and the nomodesetting are working against the modesetting driver and the vesa-driver is used.
                            Also if you can make it to a console during boot you can look with inxi -G which driver is used.

                            #8874
                            Member
                            zpimp
                              Helpful
                              Up
                              0
                              ::

                              mx-linux-17.1-386 boots fine with the same driver, like debian
                              inxi -G from mxlinux:

                              Graphics:  Card: Intel HD Graphics 5500
                                         Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
                                         Resolution: 1366x768@60.02hz
                                         OpenGL: renderer: Mesa DRI Intel HD Graphics 5500 (Broadwell GT2) x86/MMX/SSE2
                                         version: 4.5 Mesa 13.0.6
                              
                              #8876
                              Forum Admin
                              anticapitalista
                                Helpful
                                Up
                                0
                                ::

                                Is the anything in /etc/X11/xorg.conf on MX or in /etc/X11/xorg.conf.d?

                                • This reply was modified 5 years, 1 month ago by anticapitalista.

                                Philosophers have interpreted the world in many ways; the point is to change it.

                                antiX with runit - leaner and meaner.

                                #8892
                                Member
                                zpimp
                                  Helpful
                                  Up
                                  0
                                  ::

                                  in /etc/X11/ there is only xorg.conf.in
                                  in /etc/X11/xorg.conf.d/ i only have 10-evdev.conf and synaptics.conf

                                Viewing 15 posts - 1 through 15 (of 15 total)
                                • You must be logged in to reply to this topic.