Announcement

Collapse
No announcement yet.

Ubuntu 12.04 LTS Tries For A Wayland Preview

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

  • phoronix
    started a topic Ubuntu 12.04 LTS Tries For A Wayland Preview

    Ubuntu 12.04 LTS Tries For A Wayland Preview

    Phoronix: Ubuntu 12.04 LTS Tries For A Wayland Preview

    While we're at least a year away from seeing the Wayland Display Server play any semi-serious role in the Ubuntu stack, for Ubuntu 12.04 LTS there may actually be an experimental Wayland preview session available...

    http://www.phoronix.com/vr.php?view=MTAxMTE

  • Azpegath
    replied
    I went to a Richard Stallman presentation yesterday in Stockholm, so now I'm really psyched to get this working on GNU/Hurd!

    Leave a comment:


  • ChrisXY
    replied
    Originally posted by ChrisXY View Post
    Seriously: It's so beyond broken now that I can hardly imagine that preview doing anything useful.
    I'd like to test it too. I like testing. I use mesa git and kernel 3.1 and firefox nightly.
    But for considering to actually test it I think it should be even remotely usable.

    In a tty it still only displays distorted graphics when I start any wayland client, crashes my X that is running in another tty and spews this sort of thing in my log:
    Code:
    [50456.471266] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x9a
    [50456.471272] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    [50458.659764] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x9a
    [50458.659771] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    [50458.660009] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x9a
    [50458.660015] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    [50458.660262] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x9a
    [50458.660269] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    [50458.660473] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x9a
    [50458.660479] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    [50458.661053] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x9a
    [50458.661058] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    [50458.661257] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x9a
    [50458.661262] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    [50458.661515] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x9a
    [50458.661520] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    [50458.661714] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x9a
    [50458.661720] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    [50458.662194] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x9a
    [50458.662199] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    [50458.662400] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x9a
    [50458.662405] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    [50458.662802] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x9a
    [50458.662807] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    [50458.663003] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x9a
    [50458.663008] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    [50458.663486] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x9a
    [50458.663491] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    [50458.663707] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x9a
    [50458.663712] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    [50458.664224] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x9a
    [50458.664231] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    [50458.664453] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x9a
    [50458.664459] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    [50458.664734] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x9a
    [50458.664739] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    [50458.664914] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x9a
    [50458.664919] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    [50458.675789] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0xa0
    [50458.675798] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    [50459.416350] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0xa0
    [50459.416354] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
    So either the radeon driver in the kernel is broken, mesa is broken or wayland is broken. Somehow I suspect wayland.

    Leave a comment:


  • 89c51
    replied
    Originally posted by Azpegath View Post
    Are there any ways to help Wayland along? There are mentions of early testing in the article, but is that needed at this stage?

    1. Can I help with testing?
    2. Can I give money to someone (not intel/amd/nvidia)?
    3. Can I help with development?
    there is a big TODO list so if you ask the WL people on the mailing list or IRC i am sure they will find a way for you to help

    Leave a comment:


  • ChrisXY
    replied
    Well, that release will certainly be "interesting".

    At the moment my typical wayland session in X looks like this:

    http://pastebin.com/Ht9EMeuT

    At least it doesn't crash the graphics drivers completely as it does when running natively without X.
    And in X it even partly succeeds in rendering the clients correctly. At the beginning. For example, in the dnd demo the icons just go black when being clicked. Without X it just displays some stripes and after some time begins to consume 100% CPU and won't allow chaning to another tty.

    HD 6550, mesa git (with gallium egl, but without gallium egl it doesn't look much better), kernel 3.1, wayland git, cairo with gl git.

    Seriously: It's so beyond broken now that I can hardly imagine that preview doing anything useful.
    Last edited by ChrisXY; 11-04-2011, 07:22 AM.

    Leave a comment:


  • kraftman
    replied
    Originally posted by sunweb View Post
    So they partically banned gnome 3.4 saying about stability rather than "that shit will ruin some of our unity eco system" but allow wayland that hasn't been properly tested and put it in stable release ?
    Like stated in the article Wayland will be shipped as an experimental preview for those who want to test it.

    Leave a comment:


  • Azpegath
    replied
    Are there any ways to help Wayland along? There are mentions of early testing in the article, but is that needed at this stage?

    1. Can I help with testing?
    2. Can I give money to someone (not intel/amd/nvidia)?
    3. Can I help with development?

    Leave a comment:


  • sunweb
    replied
    So they partically banned gnome 3.4 saying about stability rather than "that shit will ruin some of our unity eco system" but allow wayland that hasn't been properly tested and put it in stable release ?

    Leave a comment:


  • fabioamd87
    replied
    Launching X application is like what apple does?

    Leave a comment:


  • natewiebe13
    replied
    I think this is a great step in the right direction if they can manage to find time for this. But there's still one major problem (for me at least). Using the nvidia binary driver with wayland. AFAIK nvidia has said they don't plan to support this graphics server. I'm sure though as time progresses and more and more distros migrate to wayland, this will change. Hopefully sooner than later.

    Leave a comment:

Working...
X