Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 23

Thread: Linux 2.6.36-rc1 Kernel Released

  1. #11
    Join Date
    Dec 2008
    Posts
    988

    Default

    For instance someone posts a patch to fix some problem in the drm for r600/r700, that patch could possibly also apply to Evergreen drm code, but the Evergreen drm code for some reason is not updated. Result: Bug fixed in r600/r700, bug still present in Evergreen.

  2. #12
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,458

    Default

    Sure, I guess that could happen in theory, but nearly all of the 6xx/7xx drm patches came from agd5f, who is actively testing/fixing the Evergreen code as well.

  3. #13

    Default

    Quote Originally Posted by korpenkraxar View Post
    How badly does an rc1 kernel usually hurt when it misbehaves? I crave those drm and responsiveness improvements...
    worst case was the corrupting of firmware for a specific network card, leaving the computer with no network.
    http://lwn.net/Articles/300202/
    there was a workaround fairly quickly, and the true cause was eventually found
    http://lwn.net/Articles/303390/
    and it was possible to re-upload the firmware in most cases. i think only a very small number of people were effected, you won't find more than a couple of angry rants (compared to hundreds when ubuntu moved the window buttons).

    the odds of this kind of thing are very small. a more likely, but still rare possibility is filesystem corruption bug. as long as you have a backup you should be fine.

  4. #14
    Join Date
    Aug 2007
    Location
    Poland
    Posts
    215

    Default

    Anyone know if Ubuntu is going to switch from 2.6.35 to 2.6.36 with Maverick (10.10) or not?

  5. #15
    Join Date
    May 2007
    Posts
    319

    Default

    Quote Originally Posted by monraaf View Post
    For instance someone posts a patch to fix some problem in the drm for r600/r700, that patch could possibly also apply to Evergreen drm code, but the Evergreen drm code for some reason is not updated. Result: Bug fixed in r600/r700, bug still present in Evergreen.
    For instance someone on a forum has no clue what they are talking about?

    Dave.

  6. #16
    Join Date
    Aug 2008
    Location
    California, USA
    Posts
    196

    Default

    Do ATI HDMI audio chips handle multichannel LPCM yet?

  7. #17
    Join Date
    Jul 2009
    Location
    Torrington, Ct. USA
    Posts
    166

    Default

    Quote Originally Posted by xeros View Post
    Anyone know if Ubuntu is going to switch from 2.6.35 to 2.6.36 with Maverick (10.10) or not?
    Extremely doubtful. Better chance that Fedora 14 will ship with 2.6.36 but even Fedora 14 will more likely stick with 2.6.35. Still I'm sure Ubuntu will backport some stuff from 2.6.36 to their 2.6.35 kernels like they usually do.

  8. #18
    Join Date
    Jul 2009
    Posts
    416

    Default

    Quote Originally Posted by xeros View Post
    Anyone know if Ubuntu is going to switch from 2.6.35 to 2.6.36 with Maverick (10.10) or not?
    No. .36 will be out in November or December, which is after 10.10 would be out.

  9. #19
    Join Date
    Dec 2008
    Posts
    988

    Default

    Quote Originally Posted by airlied View Post
    For instance someone on a forum has no clue what they are talking about?

    Dave.
    Whatever. It's not like this -- where a bug was present in multiple drivers but was only fixed in a few -- has never happened before.

  10. #20
    Join Date
    Jan 2009
    Location
    Vienna, Austria; Germany; hello world :)
    Posts
    637

    Default

    Quote Originally Posted by ssam View Post
    worst case was the corrupting of firmware for a specific network card, leaving the computer with no network.
    http://lwn.net/Articles/300202/
    there was a workaround fairly quickly, and the true cause was eventually found
    http://lwn.net/Articles/303390/
    and it was possible to re-upload the firmware in most cases. i think only a very small number of people were effected, you won't find more than a couple of angry rants (compared to hundreds when ubuntu moved the window buttons).

    the odds of this kind of thing are very small. a more likely, but still rare possibility is filesystem corruption bug. as long as you have a backup you should be fine.
    bingo !

    Filesystem corruption with 2.6.36-rc1-wl+ and ecryptfs

    so hands off 2.6.36-rc1 if you're using ubuntu & ecryptfs (encrypted /home folder) !

    another (small) bug is a segfault with reiserfs partitions

    catalyst / fglrx 10.7 also doesn't work with it yet

    anyone cares to provide a patch for it - so that we can start testing 2.6.36 with >=rc2 or rc3 ?

Posting Permissions

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