Announcement

Collapse
No announcement yet.

no boot on latest kernel drm-radeon-testing/add NI pci ids

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • no boot on latest kernel drm-radeon-testing/add NI pci ids

    The latest drm-radeon-testing kernel does not boot but hangs at a black screen. I'm at commit "add NI pci ids". There has been no change in my kernel .config since drm-radeon-testing rc3.

  • #2
    What hardware are you using? If you are using 6xx, 7xx, or evergreen hw you may need this patch:
    http://git.kernel.org/?p=linux/kerne...fa3eee4520f5e5

    Comment


    • #3
      Same here but using 2.6.38-rc1...
      I thought that patch already included to rc1.
      I also tried to run my 6850 with KMS drm-testing before
      at this topic with same result.

      Anyway I tried again with changed bios compliance modes set to DISABLED or GEN1 but it doesn't helps.

      I am not using KMS booting but fglrx. I get into shell via "3" as boot parameter at grub.
      When I try to load radeon kernel with KMS computer became BSOD... CTRL+ALT+DEL doesn't working yet. But modprobing okey if I made modeset=0.

      Does it any way to debug this easy? I couldn't print dmesg lines here due lockup

      Comment


      • #4
        The best bet would be to bisect and see what commit is causing the problem for you. It would also be easier to track this if you opened a bug report:
        https://bugs.freedesktop.org
        Select "DRI", then, "DRM/Radeon"

        Comment


        • #5
          I open a bug report.

          Also don't know if it work (try each git commit one by one) since NI doesn't supported before. Might be understand which commit triggers that behavior but I am not experienced on git well. Might be try later, if it's not fixed on other release candidates.

          Comment


          • #6
            To revert 1 commit at a time:
            Code:
            git reset --hard HEAD~1
            It may take a while to find the commit. I'll try the patch. I'm using an HD3850/RV670 card.

            Comment


            • #7
              Originally posted by charlie View Post
              To revert 1 commit at a time:
              Code:
              git reset --hard HEAD~1
              It may take a while to find the commit. I'll try the patch. I'm using an HD3850/RV670 card.
              Use git bisect. It's much easier.

              Comment


              • #8
                This is the commit that causes boot to fail: http://git.kernel.org/?p=linux/kerne...45f2fbb4faacf9 (drm/radeon: use system_wq instead of dev_priv->wq)

                Commit "vga_switcheroo: fix build with non switcheroo enabled path" builds fine.

                Comment


                • #9
                  The patch at http://git.kernel.org/?p=linux/kerne...fa3eee4520f5e5 does not work.

                  Comment


                  • #10
                    Originally posted by charlie View Post
                    This is the commit that causes boot to fail: http://git.kernel.org/?p=linux/kerne...45f2fbb4faacf9 (drm/radeon: use system_wq instead of dev_priv->wq)
                    I don't really see how that would cause an issue, but Tejun may have some ideas. Please file a bug:
                    https://bugzilla.kernel.org/

                    Comment


                    • #11
                      Fixed via reverting:
                      http://git.kernel.org/?p=linux/kerne...a929005ba72aad

                      Little offtopic but,
                      But I can't enable 3D with r600g. Using mesa trunk & xf86-video-ati trunk...
                      Doesn't it support 3D yet?

                      glxinfo gives segmentation fault and gmesg has this lines:

                      Code:
                      glxinfo[16659]: segfault at 1e0bbca48 ip 00007f6fddfa2b15 sp 00007fff806e7f60 error 6 in r600_dri.so[7f6fddcda000+dc2000]
                      glxgears[16672]: segfault at 1e0bbda48 ip 0007f0f3a1d6b15 sp 00007fff6401f120 error 6 in r600_dri.so[7f0f39f0e000+dc2000]
                      Am I doing something wrong?

                      Comment


                      • #12
                        You said the following earlier :

                        I am not using KMS booting but fglrx. I get into shell via "3" as boot parameter at grub. When I try to load radeon kernel with KMS computer became BSOD... CTRL+ALT+DEL doesn't working yet. But modprobing okey if I made modeset=0.
                        Does that mean you have fglrx installed as well ?

                        Comment


                        • #13
                          Originally posted by bridgman View Post
                          You said the following earlier :
                          Does that mean you have fglrx installed as well ?
                          Yes, with patched kernel module code to make it work with 2.6.38.
                          But when I trying that, fglrx module doesn't loaded in memory. I also tried without fglrx but that not related with BSOD error...

                          Now I am using my pc with fglrx uninstalled to run Mesa Gallium3D stack but it doesn't working. I have just 2D. /var/log/Xorg.0.log looks OK. No problem appears... But getting segmentation faults when I try to run any 3D app.

                          Comment


                          • #14
                            Originally posted by Death Knight View Post
                            Yes, with patched kernel module code to make it work with 2.6.38.
                            But when I trying that, fglrx module doesn't loaded in memory. I also tried without fglrx but that not related with BSOD error...

                            Now I am using my pc with fglrx uninstalled to run Mesa Gallium3D stack but it doesn't working. I have just 2D. /var/log/Xorg.0.log looks OK. No problem appears... But getting segmentation faults when I try to run any 3D app.
                            Installing fglrx over-writes some 3d-related files and I'm not sure if just building and installing mesa is enough to get them all back. Anyone ?

                            Comment


                            • #15
                              Fixed.
                              my older config for mesa is :
                              ./autogen.sh TALLOC_LIBS=-ltalloc TALLOC_CFLAGS=-I/usr/include/ --with-dri-drivers=r600,swrast --enable-gallium-{r600,llvm} --prefix=/usr --libdir=/usr/lib64 --enable-xcb --enable-gl-osmesa --enable-egl --enable-openvg --with-state-trackers=egl,glx,dri,xorg,vega --enable-gles1 --enable-gles2

                              after make make distclean just used this config for mesa.
                              ./autogen.sh TALLOC_LIBS=-ltalloc TALLOC_CFLAGS=-I/usr/include/ --with-dri-drivers=swrast --enable-gallium-r600 --prefix=/usr --libdir=/usr/lib64

                              Don't know exactly but I am suspecting about dri (not gallium-dri) driver might generate problem since it's not compatible with NI.

                              Comment

                              Working...
                              X