Page 1 of 2 12 LastLast
Results 1 to 10 of 78

Thread: Binary Driver Blobs Aren't Yet Ready For Wayland

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    15,388

    Default Binary Driver Blobs Aren't Yet Ready For Wayland

    Phoronix: Binary Driver Blobs Aren't Yet Ready For Wayland

    Aside from the Wayland/Weston 0.95 announcement, also being discussed in recent days on the Wayland development list has been support supporting the AMD Catalyst and NVIDIA Linux binary graphics drivers under Wayland...

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

  2. #2
    Join Date
    Dec 2009
    Posts
    492

    Default

    Considering Wayland is pretty much a one-man show that hasn't seen its first release yet, all those remarks are hardly surprising.
    I'm sure drivers will come quickly, especially if Wayland makes it easy to port the existing ones over. And at least a few major distros adopt Wayland, of course, but that's almost a given.

  3. #3
    Join Date
    Mar 2008
    Posts
    578

    Default

    It's clear to me that the OSS world is lacking of middleman.

  4. #4
    Join Date
    Jun 2012
    Posts
    21

    Default

    From the article:
    "Please don't make it easy for "the blob to work with Wayland/Weston", and don't change anything in our stacks for that to happen. Please don't sacrifice anything in our side.
    Let Nvidia adapt to Wayland/Weston and not the other way around. And if they won't, I think people will be more than happy to be on Nouveau."

    Couldn't agree more with this. The problem with the blobs is that they replace a lot of the X functionality. We can wait. The Open AMD driver is usable for working with all but the latest generation; obviously same applies to the Intel driver. I never tried Nouveau, but I heard great things about it.

  5. #5
    Join Date
    May 2012
    Posts
    908

    Default

    Quote Originally Posted by tstrunk View Post
    From the article:
    I never tried Nouveau, but I heard great things about it.
    Nouveau is the weakest link actually. It's slower and less feature rich than the Intel or AMD's open source driver. And for (not so) new nvidia cards (GTX 400+) you still need FUC for the card to even start working.

    So nouveau is far from being "more than enough", it's "less than enough", unless you're using an older card like GT 9600 where Nouveau works reasonably good (yet obviously without a pile of important features).


    But I don't want Wayland to bend over backwards to please Nvidia's binary blob cause Nvidia will have to adapt to Wayland anyway imo, so bending over backwards will only allow Nvidia to keep their blob inconsistent with Wayland for (way) longer.
    Last edited by mark45; 07-25-2012 at 10:03 AM.

  6. #6

    Default

    But, of course, some Wayland developers think that the binary drivers can just burn in hell and everything will be fine. "Wayland is already successful in a large way. It is most certainly not contingent upon proprietary drivers supporting wayland. Nvidia will likely fix their driver, but only *AFTER* wayland is being used."
    Well I hope she/he was kidding. If you have a non-intel card you don't really have a full alternative. You have an half one (radeon and nouveau), and I really hope this message can last: you must be able to use your hardware, and to use it as it is supposed to be. No things like "sorry the power management.... you know... it is an hard life". I totaly agree if you say "buy intel, don't even look at something else". Intel graphics is just a smooth expirience (I have 2, one old GMA3xxx at work and HD 4000 at home, wonderfull). This is also a strategy to support open source development. So ok binary drivers are a bug and it must be fixed, but burning them all will not make "everything fine", this is true only for people not using them. Ok maybe she/he was just kidding and I'm worrying for nothing.

    Please don't make it easy for "the blob to work with Wayland/Weston", and don't change anything in our stacks for that to happen. Please don't sacrifice anything in our side.

    Let Nvidia adapt to Wayland/Weston and not the other way around.
    I totaly agree with this, I mean with "don't sacrifice anything in our side" and NVIDIA/AMD/others must adapt. Wayland born for Linux, not for NVIDIA/AMD. Of course I don't agree to the line "let's keep them out in any case", and I will soon explain a bit what I mean.

    And if they won't, I think people will be more than happy to be on Nouveau.
    Stop non-sense please, really. Try to think why someone is actually using the binary nvidia driver instead of nouveau. I was a big fan of the open source radeon driver some time ago. I tried so many time to use it. Fglrx was working better, nothing to do with that. Composite more smooth, GPU (and CPU, the fan is shared) more cool, games with better quality, battery life longer. Tell me why the hell I should use radeon if not because it is open source (which is definetly a merit, but doesn't make my hardware to work better), and fglrx has a crappy development model and slow support for new xorg (you can live with that, but it is annoying I agree). If you make a software like GNU/Linux OS display server / kernel you do that because people can use it. If you prevent people to use it.... why creating it?

    Ok you can say just buy intel and you will be able to use it. But please understand intel is not good for everyone being a low end IGP in the end. There is more then just gamers that need a powerfull GPU in the chassis.

    Anyway I wish my best luck to Wayland and we will see if/when it will replace Xorg.
    Cheers

  7. #7
    Join Date
    Nov 2008
    Location
    Madison, WI, USA
    Posts
    881

    Default

    Quote Originally Posted by enrico.tagliavini View Post
    Tell me why the hell I should use radeon if not because it is open source (which is definetly a merit, but doesn't make my hardware to work better), and fglrx has a crappy development model and slow support for new xorg (you can live with that, but it is annoying I agree)
    I've got two reasons:

    1) My work machine has dual 1080p monitors attached to a Radeon 5450 in Ubuntu x64 (currently 12.04, previously 11.10). Using Catalyst/fglrx, I could never get X to recognize the second monitor correctly. I switched to the OSS radeon driver and immediately the second monitor became usable.

    2) I hate Unity, but my work machine had Ubuntu installed by the IT people at my request (I was using it at home at the time I was hired... I've since switched to Mint at home). I knew that Gnome Shell worked for me, and so I figured I'd switch to that as my window manager. Catalyst always gave me corruption/stability issues in GS (maybe they've fixed that by now, but they sure are/were taking their time). The Radeon driver works without corruption, and is rock solid for stability.

  8. #8

    Default

    Quote Originally Posted by Veerappan View Post
    I've got two reasons:

    1) My work machine has dual 1080p monitors attached to a Radeon 5450 in Ubuntu x64 (currently 12.04, previously 11.10). Using Catalyst/fglrx, I could never get X to recognize the second monitor correctly. I switched to the OSS radeon driver and immediately the second monitor became usable.

    2) I hate Unity, but my work machine had Ubuntu installed by the IT people at my request (I was using it at home at the time I was hired... I've since switched to Mint at home). I knew that Gnome Shell worked for me, and so I figured I'd switch to that as my window manager. Catalyst always gave me corruption/stability issues in GS (maybe they've fixed that by now, but they sure are/were taking their time). The Radeon driver works without corruption, and is rock solid for stability.
    1) True fglrx is quite a mess there, but for me it worked after 2 reboots playing with amdcccle. My HDMI full HD second monitor just works with it.

    2) I use KDE and fglrx just works with it

    And be aware you are talking about bad issue, but not as critical as missing powersave from the radeon driver in my opinion. I have literally burned a laptop (not a fault of radeon that time to be clear), so I'm very critical about powersave.

    I agree fglrx is not the best solution, of course it is not! Damn the intel driver is a paradise compared to it. I sold every AMD/NVIDIA machine I had to switch to intel. But still fglrx, even it is an half pile of bugged crap, is usefull to someone. Burning it is not a good solution.

  9. #9
    Join Date
    Jun 2012
    Posts
    21

    Default

    Quote Originally Posted by enrico.tagliavini View Post
    Fglrx was working better, nothing to do with that. Composite more smooth, GPU (and CPU, the fan is shared) more cool, games with better quality, battery life longer. Tell me why the hell I should use radeon if not because it is open source (which is definetly a merit, but doesn't make my hardware to work better), and fglrx has a crappy development model and slow support for new xorg (you can live with that, but it is annoying I agree). If you make a software like GNU/Linux OS display server / kernel you do that because people can use it. If you prevent people to use it.... why creating it?
    My experiences were different; that was also why I was happy the developers shared my view. I followed the development of the 'first' new ATI driver with my 4850. There I always experienced Video tearing and subpar compiz performance with the fglrx. The open-source driver fixed all that instantly. I then switched to a 6850. Again on fglrx I am currently experiencing tearing and have problems with Gnome 3 and dual monitor support. I am still on fglrx because HDMI audio doesn't work on the open source driver. This will be fixed in Kernel 3.5. Then I will switch again.

    I suppose it's just different experience. I'd really just like Wayland to be as optimal as possible without bending to the closed source drivers.
    Last edited by tstrunk; 07-25-2012 at 11:37 AM. Reason: Typo

  10. #10
    Join Date
    Mar 2011
    Posts
    223

    Default

    I like the idea of being able to use Wayland with my current Nvidia binary drivers. That way more people would be able to move to Wayland before Nvidia optimizes their driver for it (giving them a reason to do so in the first place).

Posting Permissions

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