Announcement

Collapse
No announcement yet.

What Is AtomBIOS & These Different Drivers?

Collapse
This is a sticky topic.
X
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    I tried one more time with FGLRX :

    1/ Removed radeon driver (sudo apt-get remove --purge (...)-ati (...)-radeon)
    2/ Installed Catalyst 10.5 with ati installer script
    3/ Deleted xorg.conf (after backup)
    4/ Ran : sudo aticonfig -f --initial=dual-head --adapter=all
    5/ Modified my kdmrc file disabling multiseat mode back to single "normal" mode (launching a single Xorg without any "exotic" parameter)
    6/ Restart
    ...
    7/ Same system crash :-(

    Empty Xorg.log file !

    I've found this in the kern.log file :

    May 30 14:41:37 belgarion kernel: [ 9.389229] fb1: radeondrmfb frame buffer device
    May 30 14:41:37 belgarion kernel: [ 9.389232] [drm] Initialized radeon 2.0.0 20080528 for 0000:03:00.0 on minor 1
    May 30 14:41:37 belgarion kernel: [ 9.390411] vga16fb: initializing
    May 30 14:41:37 belgarion kernel: [ 9.390413] vga16fb: mapped to 0xffff8800000a0000
    May 30 14:41:37 belgarion kernel: [ 9.390415] vga16fb: not registering due to another framebuffer present
    May 30 14:41:37 belgarion kernel: [ 9.411898] Console: switching to colour frame buffer device 210x65
    May 30 14:41:37 belgarion kernel: [ 9.476605] [drm] 2: conflicting encoders switching off 9-pin DIN-1
    May 30 14:41:37 belgarion kernel: [ 9.476607] [drm] in favor of DVI-I-1
    May 30 14:41:37 belgarion kernel: [ 9.486597] [drm] 2: conflicting encoders switching off 9-pin DIN-1
    May 30 14:41:37 belgarion kernel: [ 9.486599] [drm] in favor of DVI-I-1
    May 30 14:41:37 belgarion kernel: [ 9.877968] type=1505 audit(1275223297.234:5): operation="profile_replace" pid=1147 name="/sbin/dhclient3"
    May 30 14:41:37 belgarion kernel: [ 9.878342] type=1505 audit(1275223297.234:6): operation="profile_replace" pid=1147 name="/usr/lib/NetworkManager/nm-dhcp-client.action"
    May 30 14:41:37 belgarion kernel: [ 9.878546] type=1505 audit(1275223297.234:7): operation="profile_replace" pid=1147 name="/usr/lib/connman/scripts/dhclient-script"
    May 30 14:41:37 belgarion kernel: [ 9.880119] type=1505 audit(1275223297.234:8): operation="profile_load" pid=1151 name="/usr/lib/cups/backend/cups-pdf"
    May 30 14:41:37 belgarion kernel: [ 9.880568] type=1505 audit(1275223297.234:9): operation="profile_load" pid=1151 name="/usr/sbin/cupsd"
    May 30 14:41:37 belgarion kernel: [ 9.881836] type=1505 audit(1275223297.234:10): operation="profile_load" pid=1152 name="/usr/sbin/mysqld-akonadi"
    May 30 14:41:37 belgarion kernel: [ 9.882824] type=1505 audit(1275223297.234:11): operation="profile_load" pid=1153 name="/usr/sbin/tcpdump"
    May 30 14:41:37 belgarion kernel: [ 10.014079] vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=nonewns=none
    May 30 14:41:37 belgarion kernel: [ 10.014083] vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=nonewns=io+mem
    May 30 14:41:37 belgarion kernel: [ 10.118624] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id



    I think i need help...

    Comment


    • #32
      Maybe something about a kms / fbcon conflict ?

      Comment


      • #33
        Yep. Not sure why, but you've still got the open source drm running.

        You don't need to remove the open source driver btw; the fglrx install and subsequent aticonfig will update xorg.conf to use the fglrx x driver.

        Normally the install operation blacklists the open source radeon drm driver to avoid the conflict you are seeing.

        Comment


        • #34
          When you say "restart" are you just talking about X or did you actually reboot the entire machine?

          Adam

          Comment


          • #35
            @Sebsan

            Better use:
            Code:
            sudo rm -f /etc/X11/xorg.conf*
            wget -N http://kanotix.com/files/install-fglrx-debian.sh
            DISPLAY= sudo sh install-fglrx-debian.sh -z
            sudo reboot

            Comment


            • #36
              Originally posted by adamk View Post
              When you say "restart" are you just talking about X or did you actually reboot the entire machine?

              Adam
              I mean reboot the entire machine (with a kick in the a... :-) )

              Comment


              • #37
                I've just red this on : http://wiki.debian.org/fr/ATIProprietary

                # modprobe -r radeon drm

                # modprobe fglrx

                # echo fglrx >> /etc/modules

                Comment


                • #38
                  Originally posted by Kano View Post
                  @Sebsan

                  Better use:
                  Code:
                  sudo rm -f /etc/X11/xorg.conf*
                  wget -N http://kanotix.com/files/install-fglrx-debian.sh
                  DISPLAY= sudo sh install-fglrx-debian.sh -z
                  sudo reboot
                  I think i will stay on the "standard" way but Thank you anyway Kano. ;-)

                  Comment


                  • #39
                    Is "radeondrmfb" the ati proprietary framebuffer to use instead of open source "drm" ?

                    Comment


                    • #40
                      My script is the correct way. You NEVER load fglrx in the modules file as this module is loaded on X start. The one who wrote this must be on drugs.

                      Comment


                      • #41
                        Originally posted by Sebsan View Post
                        Is "radeondrmfb" the ati proprietary framebuffer to use instead of open source "drm" ?
                        No, radeondrmfb is part of the open source radeon kernel DRM. The 'radeon' kernel module should have been blacklisted when you installed the proprietary driver.

                        Adam

                        Comment


                        • #42
                          Originally posted by adamk View Post
                          The 'radeon' kernel module should have been blacklisted when you installed the proprietary driver.
                          So, in my case, dri and radeon kernel modules haven't been blacklisted for an unknown reason...

                          How can i do this manually ?

                          By the "modprobe -r radeon drm" command ?

                          Or by editing "/etc/modprobe.d/blacklist" file ?

                          Comment


                          • #43
                            You don't blacklist drm, just radeon. You can create any .conf filein /etc/modprobe.d. That's usally done automatically when you use my script (part of the packageing).

                            Comment


                            • #44
                              Originally posted by Sebsan View Post
                              So, in my case, dri and radeon kernel modules haven't been blacklisted for an unknown reason...

                              How can i do this manually ?

                              By the "modprobe -r radeon drm" command ?

                              Or by editing "/etc/modprobe.d/blacklist" file ?
                              Okay, sorry, i ask too much noobs questions... I've found this with google on Ubuntu doc.

                              I will verify the blacklist myself tonight.

                              Thank you all guys, i'll keep you aware.

                              Seb

                              Comment


                              • #45
                                I'm so disappointed... :-(

                                I indeed resolved the framebuffer conflict by manually blacklisting radeon module.

                                But nothing really changed.

                                During linux boot, the kernel simply stops... just at the beginning.

                                Logs are not written, there's absolutly nothing in Xorg.log, in kern.log there is just ten lines and the last line was just half-writtened. I red *everything*.log in /var/log directory and there is nothing like an error nor a bug. Not even a little warning...

                                With radeon driver, it works pretty fine. It does the minimum but it works.

                                Did someone really test with success the fglrx driver with 2.6.32 kernel and Xorg 7.5 in multi gpu mode ??? (two gpu would be enough)

                                I'm running out of ideas.

                                PS: If you want Catalyst installer to blacklist radeon driver correctly, you must not remove it before or Catalyst seems to "forget" it.

                                Comment

                                Working...
                                X