Announcement

Collapse
No announcement yet.

Two X-Servers?

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

  • #16
    Originally posted by Zhick View Post
    maybe a ps ax | grep /usr/bin/X would be more useful?
    I don't have two X servers running... I'm using Ubuntu 8.04 and Catalyst 8.5.

    Odd, maybe it's a distribution-specific thing?

    Results from mine:
    Code:
     5779 tty7     Ss+    8:02 /usr/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7
    28336 pts/0    R+     0:00 grep /usr/bin/X



    [edit] I'M COMPLETELY WRONG. DISREGARD THE ABOVE. I DO HAVE TWO INSTANCES OF X RUNNING. ID-10-T ERROR ON THE ABOVE POST.
    Last edited by Porter; 06-23-2008, 08:53 AM.

    Comment


    • #17
      Just wanted to confirm that I have the same problem using Gentoo and Fedora 8.
      Very nasty indeed, especially when I see the memory consumption of both servers (70 MB!).

      Comment


      • #18
        Archlinux here, also 2 identical X processes running.

        Comment


        • #19
          what surprises me, is that this issue surprises!

          it's much that this is a known issue... and what surprises me even more, is that at ATi, they didn't know it!!!

          but look, what top says using 'M':
          Code:
          top - 18:48:32 up  2:33,  0 users,  load average: 0.19, 0.12, 0.07
          Tasks:  98 total,   2 running,  96 sleeping,   0 stopped,   0 zombie
          Cpu(s):  8.3%us,  1.9%sy,  0.0%ni, 89.2%id,  0.0%wa,  0.3%hi,  0.2%si,  0.0%st
          Mem:   2058348k total,   770484k used,  1287864k free,    70444k buffers
          Swap:  4192924k total,        0k used,  4192924k free,   318472k cached
          
            PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND        
           3150 ben       20   0  139m  51m 5604 R    1  2.6   1:51.83 wish               
           2098 root      20   0  201m  48m  16m S   11  2.4   3:50.39 X                  
           2269 root      20   0  201m  48m  16m S    0  2.4   0:00.00 X                  
          16145 ben       20   0  138m  44m  15m S    0  2.2   0:07.78 firefox-bin        
           2282 ben       20   0  355m  37m  16m S    9  1.8   7:14.88 enlightenment      
          12980 ben       20   0  110m  36m 5288 S    1  1.8   0:45.42 wish
          nice, ain't it? :-)
          Last edited by Vighy; 06-14-2008, 01:03 PM.

          Comment


          • #20
            Interesting. I think there is a bugzilla ticket open on this already bug didn't realize how many people are seeing it.

            OK, looks like #702 - would you folks be able to add your system specifics to the ticket ?

            http://ati.cchtml.com/show_bug.cgi?id=702

            Comment


            • #21
              Originally posted by Vighy View Post
              what surprises me, is that this issue surprises!

              it's much that this is a known issue... and what surprises me even more, is that at ATi, they didn't know it!!!

              (...)

              nice, ain't it? :-)
              That's how we love it - Eating up memory and doing nothing
              However, how do you know that ATI doesn't know about it?

              EDIT: #22 says it all ;-)
              Last edited by NeoBrain; 06-14-2008, 01:11 PM.

              Comment


              • #22
                Hold on Vighy, there's a big difference between "ATI didn't know" and "bridgman didn't know". The second one happens all the time

                This seems like one of those things which happens on some systems and doesn't happen on others. If we can get more info about the systems where it *does* happen then we can start to see patterns and have a better chance of reproducing it on one of *our* systems so we can do something about it.
                Last edited by bridgman; 06-14-2008, 01:15 PM.

                Comment


                • #23
                  I had this issue ever since I ran fglrx, for 2 years...

                  AMD Radeon X1900XT 512

                  I don't think more information is required as I had plenty of different configuration since those two years and it happened with all of them.

                  Comment


                  • #24
                    Originally posted by bridgman View Post
                    This seems like one of those things which happens on some systems and doesn't happen on others. If we can get more info about the systems where it *does* happen then we can start to see patterns and have a better chance of reproducing it on one of *our* systems so we can do something about it.
                    Okay, let's see then...
                    Using
                    an AMD Athlon XP 2400+
                    512 MB RAM
                    an Sapphire ATI Radeon X1600 Pro 512 MB (AGP)
                    an ASRock Motherboard (don't know model number)
                    256 MB AGPGART size
                    Fedora 8: kernel 2.6.24, Xorg 7.2/XServer 1.3, KDE 4.0.4
                    AIGLX & Composite enabled
                    Catalyst 8.4 (8.5 has too much troubles recognizing my monitor and can't start a 3D enabled X server on another VT)

                    Comment


                    • #25
                      For the guys thinking that it's distribution specific, I'm the guy who reported that bug 1 year ago. I'm currently using the same installation (debian testing) with a "green company" card and the second X has gone away.

                      Also, suse guys like to patch their things, so they can be ironed this bug by patching X. Suse was one of the rare distros that cannot be run with a stock kernel...

                      Comment


                      • #26
                        Originally posted by bridgman View Post
                        Interesting. I think there is a bugzilla ticket open on this already bug didn't realize how many people are seeing it.

                        OK, looks like #702 - would you folks be able to add your system specifics to the ticket ?

                        http://ati.cchtml.com/show_bug.cgi?id=702
                        It may be interesting to mention also how you did install fglrx. With ATI installer, packages produced by ATI installer or your distribution's packages ?

                        HTH

                        Comment


                        • #27
                          Same here ...

                          Hey,

                          I wondered the hell why I was "topping" two X servers ... I tought that may be usefull for ATI drivers to work like this, something related to crossfire to come ...

                          Anyway, if it's useless, I'll kill the idling X server to get memory back

                          Here's my config :
                          ------------------

                          Slackware 10.2 (32 bit ARCH)
                          Kernel 2.6.24.7
                          Ati drivers 8.4 (using ATI INSTALLER)
                          X org 7.3

                          I hope ATI will improve their linux support quickly ...

                          Comment


                          • #28
                            Well I installed the Drivers via Portage / a Gentoo-Ebuild, which is probably almost the same as using the ATi Installer (not sure about that though).

                            Comment


                            • #29
                              Same here

                              Tried the ubuntu stock driver and also the catalyst 8.6 installer, both have the same effect. Never had any problems with the ubuntu feisty install, the two processes only showed up after an update to Hardy.

                              Ubuntu Hardy 8.04
                              Kernel 2.6.24
                              Xorg 7.3
                              ATI mobility Radeon X600
                              BIOS version: BK-ATI VER008.017M.192.052
                              Memory Type: DDR SGRAM/SDRAM
                              Memory Size: 128 Mb
                              Memory Clock: 263 MHz
                              Core Clock: 398 MHz
                              Bus type: PCI Express
                              Bus setting: x16
                              Driver version: 8.50.3
                              OpenGL version: 2.1.7659

                              Comment


                              • #30
                                Originally posted by hvbakel View Post
                                Tried the ubuntu stock driver and also the catalyst 8.6 installer, both have the same effect. Never had any problems with the ubuntu feisty install, the two processes only showed up after an update to Hardy.
                                They were already there, maybe you didn't notice.

                                By the way it's impossible to hope ati will solve a bug just discovered in the subsequent driver for it's model of delivering drivers.
                                We may expect the fix in the next release or in the one after the next.

                                Comment

                                Working...
                                X