Announcement

Collapse
No announcement yet.

ATI Radeon HD 5450 On Linux

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

  • #61
    Originally posted by Panix View Post
    Open drivers with HD 5450? Seriously? Nice try. Go tell the owners of this card in the Ubuntu forums.
    ??? i write here on 10.04 ubuntu with the opendriver...

    what is your problem ?

    and ubuntu10.10 mesa7.9 brings full openGL2.1 support...

    Comment


    • #62
      Originally posted by Qaridarium View Post
      ??? i write here on 10.04 ubuntu with the opendriver...

      what is your problem ?

      and ubuntu10.10 mesa7.9 brings full openGL2.1 support...
      They say there's no 3D capability and hardware acceleration doesn't work properly.

      Maybe you could try Google Earth with your card? I have no idea what works or not...just going on hearsay and I was scolded for it already so...

      Comment


      • #63
        Originally posted by Panix View Post
        They say there's no 3D capability and hardware acceleration doesn't work properly.

        Maybe you could try Google Earth with your card? I have no idea what works or not...just going on hearsay and I was scolded for it already so...
        on 10.04 you only have 2d.. shadowFB on 10.10 you have full support...

        i still need to upgrade to 10.10 to test this.

        Comment


        • #64
          Originally posted by Panix View Post
          They say there's no 3D capability and hardware acceleration doesn't work properly.

          Maybe you could try Google Earth with your card? I have no idea what works or not...just going on hearsay and I was scolded for it already so...
          i have now upgrade my system to 10.10 and the 5450 runs!

          Comment


          • #65
            Software rasterizer?

            Comment


            • #66
              Originally posted by curaga View Post
              Software rasterizer?
              uuh??? how to chance that ?

              Comment


              • #67
                I own a laptop with mobility hd 5470 since february. Having evergreen card sucks, royally. Sometimes I think I am dumb sticking to ubuntu on the machine instead going for windows.
                I use my laptop mostly for coding, but I am very often using Blender, where I need hardware acceleration and I like to play Spring engine based games.
                When I bought the machine, there was no driver that would (officially) support the driver, so I had funky "hardware not supported" watermark on my screen, though hardware acceleration was working fine. Then someone came out with a patch removing the watermark.
                In 10.4 drivers, iirc, support for my chipset was finally added, but 2 moths later came the 10.6 version, which made the only game I actually play unplayable (actually both under windows and linux, keep up the good work AMD).
                So to those talking bout progress in fglrx drivers - it is an amazing progress, from drivers not supporting hardware released to not working drivers.
                Of course there was also fun stuff. Like not knowing if system would wake up properly from sleep state. Funky red artifacts on display.
                When I compare my experiences to those of my friend's, who owns a laptop with gt240 card it makes me want to cry.
                Buying a laptop with an ATI card was like shooting myself in a foot, before jumping into a tank full of saltwater... and hungry great white sharks.
                After so joyful experiences I will definitely never again buy an AMD card. I would also advise against it to anyone, who wants to run linux or opengl applications on it.

                Comment


                • #68
                  Originally posted by faceless View Post
                  I own a laptop with mobility hd 5470 since february. Having evergreen card sucks, royally. Sometimes I think I am dumb sticking to ubuntu on the machine instead going for windows.
                  I use my laptop mostly for coding, but I am very often using Blender, where I need hardware acceleration and I like to play Spring engine based games.
                  When I bought the machine, there was no driver that would (officially) support the driver, so I had funky "hardware not supported" watermark on my screen, though hardware acceleration was working fine. Then someone came out with a patch removing the watermark.
                  In 10.4 drivers, iirc, support for my chipset was finally added, but 2 moths later came the 10.6 version, which made the only game I actually play unplayable (actually both under windows and linux, keep up the good work AMD).
                  So to those talking bout progress in fglrx drivers - it is an amazing progress, from drivers not supporting hardware released to not working drivers.
                  Of course there was also fun stuff. Like not knowing if system would wake up properly from sleep state. Funky red artifacts on display.
                  When I compare my experiences to those of my friend's, who owns a laptop with gt240 card it makes me want to cry.
                  Buying a laptop with an ATI card was like shooting myself in a foot, before jumping into a tank full of saltwater... and hungry great white sharks.
                  After so joyful experiences I will definitely never again buy an AMD card. I would also advise against it to anyone, who wants to run linux or opengl applications on it.
                  and what is going on with the catalyst 10-10 ?

                  Comment


                  • #69
                    Originally posted by curaga View Post
                    Software rasterizer?
                    i fix that now by installing the catalyst ;-)

                    maybe i test the os 3d driver with xorg-edgers later

                    Comment


                    • #70
                      Originally posted by faceless View Post
                      Sometimes I think I am dumb sticking to ubuntu on the machine instead going for windows.
                      Have you tried other distros? Most complaints seem to come from ubuntu users. I have openSUSE 11.2 and never had a problem with fglrx. Also it seems that laptops tend to be more problematic than desktop systems.

                      Originally posted by faceless View Post
                      In 10.4 drivers, iirc, support for my chipset was finally added, but 2 moths later came the 10.6 version, which made the only game I actually play unplayable (actually both under windows and linux, keep up the good work AMD).
                      This seems easy enough to solve. Stick with the version that works.

                      Originally posted by faceless View Post
                      When I compare my experiences to those of my friend's, who owns a laptop with gt240 card it makes me want to cry.
                      Only if those don't have Optimus since it will probably never be supported in linux as far as nvidia is concerned.

                      Originally posted by faceless View Post
                      After so joyful experiences I will definitely never again buy an AMD card. I would also advise against it to anyone, who wants to run linux or opengl applications on it.
                      Then your only option is using intel graphics since most, if not all, future nvidia equipped laptops will use optimus. In case you don't know intel linux driver is very bad in terms of performance. There is, however, the chance that all those problems are caused by a bad implementation by the laptop manufacturer.

                      Comment


                      • #71
                        Originally posted by Michael View Post
                        It seems every other day people switch from calling me pro-NVIDIA or pro-ATI
                        Sounds like you've forgotten to be pro-Intel

                        The Intel graphics fanboys are going to livid about this

                        Comment


                        • #72
                          If I can just barge right in here...

                          Hello, all,
                          Just joined phoronix - seems like a lot of knowledgeable people here, and I'm having a problem with my HD5450 that is beginning to drive me crazy, so maybe someone can give me hints on where to look.

                          I'm running Ubuntu Lucid 64-bit for my Desktop system - I have no problem upgrading to 10.10 if it will help, but I kind of like the idea of using the long term release. I mainly use it for web development, and web browsing, no games fancier than minesweeper or Freecell. I do like Compiz, for a couple of features, and I have two 19" LCDs. This all works very well, and the only complaint is the login prompt comes up on the wrong monitor, but I can live with that (and could probably fix it if not).

                          But there is a problem that bugs the hell out of me. Most of the time, right after the grub menu, the text screen gets screwed, so it only displays a single line at the top with colored pixels forming random patterns. The memory-test option causes a reboot, and the virtual terminals all have this same strange mode. I think the VTs are working, as I can see the patterns changing, but can read nothing. I can always get back to the graphics screen with Alt-F7 (or sometimes F8).

                          If I need to choose the recovery mode, that also does not display correctly.

                          I'm not sure what drivers are even active at this point. Any help on where to look, or even where not to look, would be appreciated.

                          Comment


                          • #73
                            Originally posted by linfidel View Post
                            I'm not sure what drivers are even active at this point. Any help on where to look, or even where not to look, would be appreciated.
                            The X log (/var/log/Xorg.0.log) is a good place to start. You may find that your distro loads multiple drivers but as you get further in you should find that all of the messages come from a single graphics driver and that's the one you are running. The X log contains messages from the userspace X driver.

                            Another useful thing is to either run glxinfo and look at the first part of the output or run glxinfo | grep render to pick out the line with "renderer" information.

                            Final thing is to run dmesg, save the output in a file, then you can look at messages from the kernel driver. You get messages from a number of different drivers mixed together but the graphics messages will jump out after a while.

                            Comment


                            • #74
                              Originally posted by bridgman View Post
                              The X log (/var/log/Xorg.0.log) is a good place to start. You may find that your distro loads multiple drivers but as you get further in you should find that all of the messages come from a single graphics driver and that's the one you are running. The X log contains messages from the userspace X driver.
                              Hmm, I would have thought that this problem would be prior to the X system even being loaded, since it first shows up right after the grub menu. In fact, I changed the boot option to delete "quiet", and even added "--verbose", and I can't read any of the output. Also, the failsafe boot doesn't work. Was I mistaken in my guess?

                              Originally posted by bridgman View Post
                              Another useful thing is to either run glxinfo and look at the first part of the output or run glxinfo | grep render to pick out the line with "renderer" information.
                              Only thing I see with "render" is:
                              direct rendering: No (LIBGL_ALWAYS_INDIRECT set),
                              and
                              OpenGL renderer string: ATI Radeon HD 5400 Series
                              Not sure what you mean for me to look for here.
                              Originally posted by bridgman View Post
                              Final thing is to run dmesg, save the output in a file, then you can look at messages from the kernel driver. You get messages from a number of different drivers mixed together but the graphics messages will jump out after a while.
                              I don't see much here, although I do see a message asking me to enable IOMMU (aperture memory hole) in my BIOS for something or other; I don't know that it has anything to do with my problem, but I'll do it; it uses 64 MB of my 4 GB, so I think I can spare it.

                              Thanks for the quick reply. Hopefully, I'll get this problem solved one way or another.

                              Comment


                              • #75
                                Originally posted by linfidel View Post
                                Hmm, I would have thought that this problem would be prior to the X system even being loaded, since it first shows up right after the grub menu. In fact, I changed the boot option to delete "quiet", and even added "--verbose", and I can't read any of the output. Also, the failsafe boot doesn't work. Was I mistaken in my guess?
                                Yeah, sorry, I didn't write enough. X won't be up at the time the artifacts occur, but your choice of X driver will affect which driver *is* running at bootup - I think.

                                If you are running the open drivers then kms will have come up (modesetting code in the open source kernel graphics driver) and I *think* you will be running on "fb" devices created by the kms driver. If you are running the proprietary driver then that stack won't be running yet and you'll be running a different fb driver.

                                I don't know an easy way to tell what driver is running during bootup so I figured it would be easier as a first step to figure out what driver is running after boot and work backwards from there

                                Comment

                                Working...
                                X