Announcement

Collapse
No announcement yet.

Catalyst 8.12 in debian lenny

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

  • #16
    Originally posted by nbi1 View Post
    Nope, it simply will not work. Same problems as my post dated 01-09-2009, 12:03 AM. The fglrx from Catalyst 8.12 is not usable in 64 bit Lenny.
    It will work. As I noted again and again just wait until 8-12 is in _LENNY_, not experimental stable etc...

    http://qa.debian.org/excuses.php?package=fglrx-driver there you will see when it will enter it, now just wait before you break your system.

    Comment


    • #17
      Originally posted by the-me View Post
      It will work. As I noted again and again just wait until 8-12 is in _LENNY_, not experimental stable etc...

      http://qa.debian.org/excuses.php?package=fglrx-driver there you will see when it will enter it, now just wait before you break your system.
      What do you mean by "it will work"? Please spare us the speculation. If you know firsthand that it does work then clearly say so, otherwise you simply don't know (in which case your earlier posts were wasting my time along with everyone else's).

      People - regardless of how close you might be to the development and/or distro packaging process please don't offer speculation as a solution. There are a lot of details to get right in resolving these driver issues. What may seem obvious to you isn't necessarily obvious to the rest of us.

      I certainly welcome insights, but when I'm willing to roll up my sleeves and dig in I don't want to be sent on a wild goose chase.

      Comment


      • #18
        Originally posted by nbi1 View Post
        What do you mean by "it will work"? Please spare us the speculation. If you know firsthand that it does work then clearly say so, otherwise you simply don't know (in which case your earlier posts were wasting my time along with everyone else's).

        People - regardless of how close you might be to the development and/or distro packaging process please don't offer speculation as a solution. There are a lot of details to get right in resolving these driver issues. What may seem obvious to you isn't necessarily obvious to the rest of us.

        I certainly welcome insights, but when I'm willing to roll up my sleeves and dig in I don't want to be sent on a wild goose chase.
        Do not think that I am aggressive against you in any case. In this case I noted that fglrx 8-12 will be in the Lenny release and that you might backport it for your PC until it enters it (which takes some days).
        Then I saw that you do not know how Debian packaging works (no problem, you do not have to ), so it is better in my opinion, that you live a few more days with those issues, instead of breaking maybe your whole system - I do not think that you or I want this, or not?

        Comment


        • #19
          Originally posted by the-me View Post
          Do not think that I am aggressive against you in any case. In this case I noted that fglrx 8-12 will be in the Lenny release and that you might backport it for your PC until it enters it (which takes some days).
          Then I saw that you do not know how Debian packaging works (no problem, you do not have to ), so it is better in my opinion, that you live a few more days with those issues, instead of breaking maybe your whole system - I do not think that you or I want this, or not?
          The system in question is a new install and not my production system. So it can be broken (within reason, I don't want to completely reinstall on every problem) due to experimentation. The ultimate goal is to have a working (as in meeting basic video requirements) Debian or Ubuntu platform. Then I can begin migrating away from etch towards this platform.

          Don't know what you mean by "how Debian packaging works". I'm fluent with dpkg and apt-get. I can also build .debs. If you're referring to the decision making utilized by Debian packagers (the folks chartered with creating packages) you are correct, I don't know how it works. I neither want to nor should I need to. What matters is whether or not available packages lend themselves towards solving a problem.

          Your advice to wait is certainly safe, but it doesn't solve any problems. And in the case of Debian it might not for another 6 months or so and that would be unacceptable. Again, I have no problem with building my own version, but the recipe(s) I'm given need to be sound.

          Comment


          • #20
            [QUOTE=Kano;58419]@nbi1

            For standard cards (not new chips with extra AGP connector) 2.6.28 works with fglrx not better or worse than other kernels.

            Are you saying that the current lenny (or even selfmade) packages will NOT work for 2.6.28 and AGP cards (radeon HD-3650 in my case)?

            Which kernel would you recommend?

            M

            Comment


            • #21
              My script is tested with Debian lenny 64 bit. It uses dkms and standard 2.6.26 and 2.6.28 works - now updated to 9-1. Of course when the card has problems the script can not fix driver issues. But the driver install is 100% correct. Tested with

              rm /etc/X11/xorg.conf*
              dpkg-reconfigure -phigh xserver-xorg

              And this script:

              http://kanotix.com/files/install-fglrx-debian.sh

              To check dkms:

              dkms status

              module-assistant is completely outdated, dkms is what you really want - boot any kernel (with installed headers) and the driver will work.

              Comment


              • #22
                Ok;

                I hope that if "locate fglrx" remains empty my plain ati installation is fully removed..

                Will try;

                Comment


                • #23
                  OK;

                  I'm not sure if my other reply came through;

                  I ran your script, which apparently worked (it built the fglrx-packages, removed the old ones and installed the built ones).

                  The fglrx module was built but not installed.

                  When I do
                  modprobe fglrx
                  I get only the agpgart installed

                  Xorg.0.log has copmlaints which follow in excerpts.
                  Finally my machine locks up and reboots when I press ctrl-alt-f1

                  (II) fglrx(0): ATI Video BIOS revision 9 or later detected
                  drmOpenDevice: node name is /dev/dri/card0
                  drmOpenDevice: open result is -1, (No such device or address)
                  drmOpenDevice: open result is -1, (No such device or address)
                  drmOpenDevice: Open failed
                  [..]
                  drmOpenByBusid: drmOpenMinor returns -6
                  (WW) fglrx(0): Failed to open DRM connection
                  (EE) fglrx(0): [FB] Can not get FB MC address range.
                  [..]
                  (EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
                  [..]
                  (EE) fglrx(0): XMM failed to open CMMQS connection.


                  Any hint?

                  Comment


                  • #24
                    Best would be: buy Nvidia card

                    Comment


                    • #25
                      How to install fglrx on Debian:

                      mkdir fglrx
                      cd fglrx
                      wget https://a248.e.akamai.net/f/674/9206...x86.x86_64.run
                      $ sh ./ati-driver-installer-9-1-x86.x86_64.run --buildpkg Debian/lenny

                      dpkg -i *.deb
                      cd /usr/src

                      m-a prepare
                      unp fglrx.tar.bz // or so... look into the directory

                      cd /usr/src/linux
                      make-kpkg --append-to-version=-1-686 modules-image

                      cd /usr/src
                      dpkg -i *.deb // look into the directory


                      you are done

                      Comment


                      • #26
                        Originally posted by Kano View Post
                        Best would be: buy Nvidia card
                        Sure, which one would you suggest, if I have the following requirements:
                        o suspend/resume works reliably
                        o minimum power consumption
                        o play lo-res vid
                        o minimal 3d (googleearth / zatttoo)

                        Sorry for being offtopic, but I'm desperately frustrated with this new laptop and the shitty ati card.

                        Comment


                        • #27
                          Originally posted by Gregor A. View Post
                          How to install fglrx on Debian:

                          mkdir fglrx
                          cd fglrx
                          wget https://a248.e.akamai.net/f/674/9206...x86.x86_64.run
                          $ sh ./ati-driver-installer-9-1-x86.x86_64.run --buildpkg Debian/lenny

                          dpkg -i *.deb
                          cd /usr/src

                          m-a prepare
                          unp fglrx.tar.bz // or so... look into the directory

                          cd /usr/src/linux
                          make-kpkg --append-to-version=-1-686 modules-image

                          cd /usr/src
                          dpkg -i *.deb // look into the directory


                          you are done
                          Two questions:
                          1: 32 or 64 bit version of debian?
                          2: Which ATI model: Radeon HD 3650?

                          I suspect this model is not yet supported...

                          Comment


                          • #28
                            I recently solved the fglrx driver problem in Ubuntu Intrepid. I now have the 8.561 driver working in Intrepid with the 2.6.28 kernel. The root cause of the problem was that an essential module was not being loaded. I have yet to figure out which one it is, but it isn't one of the obvious ones.

                            Since I'm seeing the exact same failure mode under lenny I'm guessing the solution might be the same. That solution was to get the list of loaded modules via `lsmod` for the stock Intrepid kernel for which fglrx works. I put that list in /etc/modules and voila the dkms rebuild of the fglrx module resulted in a working system.

                            A potential wrinkle with lenny is that the X server is much older. It isn't clear to me if the X server needs to be upgraded first. Kano, what do you think? Upgrade server or not? Or don't bother because fglrx won't work on lenny for other reasons?

                            Comment


                            • #29
                              Please do not use /etc/modules. That's a very bad hack and leads to problems. Let the driver load fglrx module and the rest of the modules let udev load. You can use it for lm-sensors, but that's not critical.

                              Comment


                              • #30
                                Originally posted by Kano View Post
                                Please do not use /etc/modules. That's a very bad hack and leads to problems. Let the driver load fglrx module and the rest of the modules let udev load. You can use it for lm-sensors, but that's not critical.
                                Sorry, but specifying all the modules in /etc/modules solved the mangled X display problem in Intrepid. Something that should have been getting loaded but wasn't now is. Yes, /etc/modules may be a hack but the bottom line is that I now have working fglrx.

                                And you didn't answer my question. Upgrade X server in lenny or not?

                                Comment

                                Working...
                                X