Page 14 of 14 FirstFirst ... 4121314
Results 131 to 137 of 137

Thread: R600/r700 kms + 3d dri1/dri2

  1. #131
    Join Date
    Nov 2009
    Location
    Italy
    Posts
    944

    Default

    Do not use 2.6.33, use 2.6.32+drm-next instead.
    http://xorg.freedesktop.org/wiki/rad...198d772a55fad3

  2. #132
    Join Date
    Nov 2009
    Posts
    15

    Default

    Quote Originally Posted by darkbasic View Post
    Do not use 2.6.33, use 2.6.32+drm-next instead.
    http://xorg.freedesktop.org/wiki/rad...198d772a55fad3
    Aren't all DRM related patches supposed to be pulled into 2.6.33? Since the merge window is already closed, shouldn't it provide stable KMS by itself?

  3. #133
    Join Date
    Aug 2009
    Posts
    122

    Default

    Quote Originally Posted by darkbasic View Post
    Do not use 2.6.33, use 2.6.32+drm-next instead.
    http://xorg.freedesktop.org/wiki/rad...198d772a55fad3
    nah, it's easier and faster to apply this patch http://files.netkas.org/drm_33_rc1.tar.bz2 to 2.6.32 , (fw for irq is in tarball too), just disable intel drm to compile all fine.

  4. #134
    Join Date
    May 2009
    Location
    Exodus hair
    Posts
    76

    Default

    Quote Originally Posted by darkbasic View Post
    Do not use 2.6.33, use 2.6.32+drm-next instead.
    http://xorg.freedesktop.org/wiki/rad...198d772a55fad3
    I use (on ATI HD3650)(due to lack of experience, knowledge and time) pre-compiled stuff such as daily kernels, ppa:xorg-edgers and my (short) experience with 2.6.33-999-generic is better that the one with either 2.6.32-8.12 or 2.6.32-999 with ppa:xorg-edgers. The only "problem" is, when forcing KMS I get gdm screen totally garbled with vertical lines in alll colors and I (found that way, mybe there is better solution) skip to tty, run service gdm restart and viola ... everything works as prescribed. In 2.6.32-8.12, and earlier, KMS works out of the box and I do not have to use R600_rlc.bin, which is needed in case of 2.6.33-999.
    2.6.33-999 seems to have brought imporvement in overall speed, networking and feeling of smoothness. Networking involves many non-kernel stuff such as situation on ADSL and network globally so do not hold me responsible if that is not entirely true ... but, after some hours with 2.6.33-999 in "rush-hour" on network, I'm sort of convinced.

  5. #135
    Join Date
    Aug 2009
    Posts
    122

    Default

    Quote Originally Posted by zika View Post
    I use (on ATI HD3650)(due to lack of experience, knowledge and time) pre-compiled stuff such as daily kernels, ppa:xorg-edgers and my (short) experience with 2.6.33-999-generic is better that the one with either 2.6.32-8.12 or 2.6.32-999 with ppa:xorg-edgers. The only "problem" is, when forcing KMS I get gdm screen totally garbled with vertical lines in alll colors and I (found that way, mybe there is better solution) skip to tty, run service gdm restart and viola ... everything works as prescribed. In 2.6.32-8.12, and earlier, KMS works out of the box and I do not have to use R600_rlc.bin, which is needed in case of 2.6.33-999.
    2.6.33-999 seems to have brought imporvement in overall speed, networking and feeling of smoothness. Networking involves many non-kernel stuff such as situation on ADSL and network globally so do not hold me responsible if that is not entirely true ... but, after some hours with 2.6.33-999 in "rush-hour" on network, I'm sort of convinced.
    try this commands

    sudo -s
    echo radeon modeset 1 >> /etc/modules
    Last edited by netkas; 12-18-2009 at 04:31 PM.

  6. #136
    Join Date
    May 2009
    Location
    Exodus hair
    Posts
    76

    Default

    Quote Originally Posted by darkbasic View Post
    Do not use 2.6.33, use 2.6.32+drm-next instead.
    http://xorg.freedesktop.org/wiki/rad...198d772a55fad3
    Thank You for pointing me to drm-next (2.6.32-996) kernel. I've installed it and it works (I think well) with Lucid(vanilla)+ppa:xorg-edgers. Even though I have garbled (unreadable, like TV-test-signal (sort-of) screen at start of gdm and I have to visit tty and restart gdm to get it going. It is as fas as 2.6.33-999 is. I do get segmentation fault in libc.so message in all the kernels except in official 2.6.32-9.13 ... But, that is, probably, another story ...

  7. #137
    Join Date
    May 2009
    Location
    Exodus hair
    Posts
    76

    Default

    Last night I hooked up Samsung 2343BW on DVI>DVI connection instead of 2343NW DVI>VGA>VGA connection on my PhenomX3 ATI HD 3650 512M. If I use 2.6.32-10 it is great! This 2.6.32-10 is one of the best kernels I've seen in some time. If I try 2.6.33-999(7-Jan-2010) it looses connection while entering GDM and I can restore it by turning it off on a rocker switch (on the back) (not on a touch switch on the front panel). It is the same with KMS and without it. Once that obstacle is solved everything is OK. It works nicely, also, with 2.6.32-9 but not nearly as good as with 2.6.32-10. The same problem is on either one of two DVI outputs. What could be the difference between .32 and .33 kernels that make this "problem"? I did not have this problem with analog connection. Nevertheless change from analog to digital was worth it.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •