Originally posted by theriddick
View Post
Announcement
Collapse
No announcement yet.
Nouveau Developers Remain Blocked By NVIDIA From Advancing Open-Source Driver
Collapse
X
-
Originally posted by karolherbst View PostYeah, there are already plans to have better coverage on older hardware as well, just a matter of time when we are able to actually start working on this, because it would be quite an investment. There were some talks about CI and driver testing on XDC this year as well.
We really loved to reduce introducing regressions and have a broader way of testing to detect that important features are getting taken care of, as display stuff is for sure.
By the way, is it possible to perform web-browser accelerated rendering stability tests too? Seems like right now accelerated rendering at least with Blink-based web-browsers is lead to bunch of stability issues, like for first hour or two it could be Ok, but then everything is slowdown, rendering artefacts start to appear on the screen, to the point that machine became barely unusable (due to slowness) or to GPU lockup.
If not, what is best way to report such issues? There is no exact steps-to-reproduce, it's simply something that happen every time if one sit and browse web with enabled hardware rendering in Blink-based web-browser on affected GPU (like one mentioned in my bugreport).Last edited by RussianNeuroMancer; 24 September 2017, 02:14 PM.
Comment
-
Originally posted by RussianNeuroMancer View PostGood to know! Finally nouveau developers is looking into older hardware stability
By the way, is it possible to perform web-browser accelerated rendering stability tests too? Seems like right now accelerated rendering at least with Blink-based web-browsers is lead to bunch of stability issues, like for first hour or two it could be Ok, but then everything is slowdown, rendering artefacts start to appear on the screen, to the point that machine became barely unusable (due to slowness) or to GPU lockup.
If not, what is best way to report such issues? There is no exact steps-to-reproduce, it's simply something that happen every time if one sit and browse web with enabled hardware rendering in Blink-based web-browser on affected GPU (like one mentioned in my bugreport).
It is more likely that things like that might be fixed randomly.
Comment
-
Originally posted by imirkin View Postit'd be no use contributing to something like the AMD RadeonSI driver - it's backed by full-time developers who are already familiar with the hardware, driver stack, etc., and have the hardware on hand. Not a lot of low-hanging fruit left there for a volunteer part-time contributor. (Not to mention that it uses LLVM for its compiler backend, which is an instant turn-off.)
When I look at Nvidia or Intel I don't feel like I should spend life time to improve their market share and revenue more in any way. That's just what I personally think is healthy for us.
Yeah perhaps I don't have the most fun in things I do but together with the results I feel more satisfied than when I just life for the fun moment itself.
I don't really care for brands, I look at balances and efficiency of an ecosystem. And I'm definitely ready to give up on statistics of my hardware or bank account to make the real world more the way I like it to be.
So it seems to me like there are always different points of view how people look at their lives.
- Likes 1
Comment
-
Originally posted by imirkin View Post
Strictly speaking, nothing. There are some technical hurdles, but nothing strictly impossible. We do exactly this for some of the video decoding engine firmware. The technical hurdles have, however, yet to be surmounted. I just don't think there's a lot of interest in it, and the pool of people who can pull it off is dwindling.
Comment
-
Originally posted by bridgman View Post
Stopping rumors is really hard, except for those rare cases where the reality is more interesting than the rumor
Agree that there does seem to be some potential for lowering voltages while maintaining reliable operation, but I'm not sure if all boards shipped that way would work in all expected conditions. I think the direction chosen was making it easier for user to undervolt instead (the whole WattMan thing) but not sure.
So it may be a legend, but it's rooted in truth
I'd really like to know the syntax to reduce voltage for my Polaris, it reaching 89°C really does worry me - 0.02V less does reduce temperature by several degrees under Windows (using Wattman), I'd love to be able to do the same in Linux.
Comment
-
On the article, this was mentioned:
"Signed firmwares accessible publicly but not redistributable"
Comment
-
Originally posted by aht0 View Post
This thread makes funny reading.. All the indignant outcries, wide-eyed radicality.. like watching teenage kids bashing the 'hated authorities'..
Give it a decade or two and you might suddenly notice being the target yourself.. undeservedly in your own eyes.
I'd be curious to see how many of you would really care about open-source from the second it would threaten IP your economic well-being depends from. Then you would perhaps see the open-source die-hards as a pack of vultures trying to get for free what you worked your ass off to achieve.. All things are relative, like Einstein proved..
uhhh, well that might be true, but we simply ask to at least help us out with their signed firmware situation. It doesn't change a thing for the IP situation. Also they even published stuff with their NVGPU driver, which we asked for, but never got an answer. So "IP" doesn't really seems to be the problem here, does it?Originally posted by karolherbst View Post
uhhh, well that might be true, but we simply ask to at least help us out with their signed firmware situation. It doesn't change a thing for the IP situation. Also they even published stuff with their NVGPU driver, which we asked for, but never got an answer. So "IP" doesn't really seems to be the problem here, does it?
The main problem is the attitude. We could have a nice project with their having the stuff their need and we do our stuff all inside the same project.
Check out this for example http://www.ebay.com/itm/New-NVIDIA-G...g/201727165907
Want to take a stab at guessing what this card really is? It sure as fuck ain't 1050. It's probably GTX550 Ti with hacked BIOS.
With a problem like this, it's foregone conclusion that manufacturer does whatever it takes to protect itself and it's reputation. If it means complaints and whine of a 1% of PC users, then so be it. It sure as fuck does not want class-action lawsuit because it did not do everything in it's power to protect buyers of it's cards.Last edited by aht0; 25 September 2017, 07:23 AM.
Comment
-
Originally posted by aht0 View Post
Then instead of relentlessly bashing Nvidia tell hearty "Thank You" to Chinese scammers who started selling cheap(er) reflashed Nvidia FAKE cards in eBay/AliExpress. You could have bought "770Ti" from Chinese and received fucking "250 GTS" which would still claim itself to be a "770Ti" but support none of the extra features (like hardware encoding H.264) and perform like.. well "250 GTS".
Check out this for example http://www.ebay.com/itm/New-NVIDIA-G...g/201727165907
Want to take a stab at guessing what this card really is? It sure as fuck ain't 1050. It's probably GTX550 Ti with hacked BIOS.
With a problem like this, it's foregone conclusion that manufacturer does whatever it takes to protect itself and it's reputation. If it means complaints and whine of a 1% of PC users, then so be it. It sure as fuck does not want class-action lawsuit because it did not do everything in it's power to protect buyers of it's cards.
Comment
Comment