Oh no! Where's the JavaScript?
Your Web browser does not have JavaScript enabled or does not support JavaScript. Please enable JavaScript on your Web browser to properly view this Web site, or upgrade to a Web browser that does support JavaScript.

nvidia - 64-bit

Last updated on 1 hour ago
D
deadwoodAROS Dev
Posted 1 hour ago
@Korban

Please for now remove from your test set any cards that have DisplayPort connector.
D
deadwoodAROS Dev
Posted 4 hours ago
Making progress ^^ (note video cards used in this test)

axrt.org/media/nouveau_05.jpeg
Edited by deadwood on 30-06-2026 11:46, 4 hours ago
Amiwell79, miker1264, Farox, sonountaleban, Deremon, aha, retrofaza, ami-elvis
J
Jeff1138Member
Posted 23 hours ago
Thanks
F
FaroxMember
Posted 1 day ago
I don't know if this the exact version but...
Mesa 20.0.0 release note
https://docs.mesa3d.org/relnotes/20.0.0.html#mesa-20-0-0-release-notes-2020-02-19
D
deadwoodAROS Dev
Posted 1 day ago
I don't know the exact level - you'd have to check the documentation for Mesa version 20.x on which APIs are supported.
J
Jeff1138Member
Posted 1 day ago
Hi,

Well done, I take it this could take us to OpenGL3 or even OpenGL4?
D
deadwoodAROS Dev
Posted 1 day ago
First signs of life from 3D driver!

axrt.org/media/nouveau_04.jpeg
Amiwell79, miker1264, ntromans, x-vision, Farox, sonountaleban, retrofaza, ncafferkey, aha, ami-elvis, Argo
pixiepixieMember
Posted 2 days ago

deadwood wrote:

@deadwood - @Amiwell79

Does it happen right after boot or after screen resolution change?

@pixie

The non-accelerated driver is a temporary stage - it's not going to be used for anything else then initial tests. If all goes well we should get 2D acceleration on all supported cards in a couple of days, so get a supported card (up to GTX 750) and test how it works for you.


Sadly i do not own such a card, only a 2070 ti.
A
Amiwell79Distro Maintainer
Posted 2 days ago
it happens after startup
D
deadwoodAROS Dev
Posted 3 days ago
@Amiwell79

Does it happen right after boot or after screen resolution change?

@pixie

The non-accelerated driver is a temporary stage - it's not going to be used for anything else then initial tests. If all goes well we should get 2D acceleration on all supported cards in a couple of days, so get a supported card (up to GTX 750) and test how it works for you.
pixiepixieMember
Posted 3 days ago
Would it be possible to post a quick demo comparing the hardware-accelerated version with the non-accelerated version? Seeing both versions in the same scenarios would be a great way to showcase the real benefits of the advancements that await us in the future.
A
Amiwell79Distro Maintainer
Posted 4 days ago
I replaced the driver, but when I start Wanderer, everything freezes, even the cursor, and I have to turn off the computer. Thanks anyway, I'll wait for a new release. I have an NVIDIA GT 210 1 GB
D
deadwoodAROS Dev
Posted 5 days ago
To clarify: By Tesla and Fermi I mean all cards starting from GF8**** and ending with GTX 5xx series. I'm starting to work right now to get 2D acceleration for GTX 6xx - 7xx series.
Amiwell79, sonountaleban, Farox, Argo, Deremon
A
Amiwell79Distro Maintainer
Posted 5 days ago
The Tesla is an add-on board, it doesn't have connectors, it needs to be used with another board
D
deadwoodAROS Dev
Posted 6 days ago
We are moving ahead with functionality, here is Beta-1:

https://axrt.org/development/nouveau.hidd-20260624-47.5.zip

https://axrt.org/development/gfxbench.zip

Fixes:
- enabled 2D acceleration on Tesla and Fermi cards - you can use gfxbench to test it, be sure to have your screen in 1024x768x24 for comparable results
- tested on GTX 550Ti, FTX 750 (no 2D acceleration) and 8500GT

Known issues:
- doesn't work on GTX 950 - firmware loading missing
- after selecting resolution in Prefs/ScreenMode everything will freeze for ~10 seconds, just wait

Below are results on my GTX 550Ti (up to 10x better then with VESA driver):

*PixelArray benchmark 1024x576*
||Test||Blits/s||MB/s||
| WritePixelArray RECTFMT_RGB FW|973.90|2191|
| WritePixelArray RECTFMT_RGB HW|2114.46|4757|
| WritePixelArray RECTFMT_ARGB FW|955.60|2150|
| WritePixelArray RECTFMT_ARGB HW|2043.78|4598|
| WritePixelArray RECTFMT_RGBA FW|817.86|1840|
| WritePixelArray RECTFMT_RGBA HW|1545.13|3476|
| WritePixelArray RECTFMT_RGB16PC FW|788.97|1775|
| WritePixelArray RECTFMT_RGB16PC HW|1503.32|3382|
| WritePixelArray RECTFMT_LUT8 FW|55.70|125|
| WritePixelArray RECTFMT_LUT8 HW|65.13|146|
| ReadPixelArray RECTFMT_RGB FW|796.63|1792|
| ReadPixelArray RECTFMT_RGB HW|1496.11|3366|
| ReadPixelArray RECTFMT_ARGB FW|1096.34|2466|
| ReadPixelArray RECTFMT_ARGB HW|2193.99|4936|
| ReadPixelArray RECTFMT_RGBA FW|832.99|1874|
| ReadPixelArray RECTFMT_RGBA HW|1580.03|3555|
| ReadPixelArray RECTFMT_RGB16PC FW|814.77|1833|
| ReadPixelArray RECTFMT_RGB16PC HW|1552.69|3493|
| WritePixelArrayAlpha RECTFMT_ARGB FW|276.96|623|
| WritePixelArrayAlpha RECTFMT_ARGB HW|608.86|1369|


*Text benchmark 1024x576*
||Test||Blits/s||MB/s||
|JAM1, NON-ANTIALIASED, LEN 100|192.63|433|
|JAM2, NON-ANTIALIASED, LEN 100|271.62|611|
|COMPLEMENT, NON-ANTIALIASED, LEN 100|176.75|397|
|JAM1, ANTIALIASED, LEN 100|153.56|345|
|JAM2, ANTIALIASED, LEN 100|203.20|457|
|COMPLEMENT, ANTIALIASED, LEN 100|196.06|441|
|JAM1, NON-ANTIALIASED, LEN 5|181.67|408|
|JAM2, NON-ANTIALIASED, LEN 5|32.12|72|
|COMPLEMENT, NON-ANTIALIASED, LEN 5|8.65|19|
|JAM1, ANTIALIASED, LEN 5|4.98|11|
|JAM2, ANTIALIASED, LEN 5|30.35|68|
|COMPLEMENT, ANTIALIASED, LEN 5|6.72|15|
Edited by deadwood on 24-06-2026 09:50, 6 days ago
aha, Argo, ntromans, sonountaleban, x-vision, Farox, miker1264, pixie, retrofaza, Amiwell79, Deremon
K
KorbanNewbie
Posted 16 days ago

deadwood wrote:

@deadwood - Hmm, that's quite weird for the 4xx, 5xx and 6xx series. Which output are you using? VGA or DVI?


Generally DVI, but cards that have had both Ive sometimes tested with both. Same with if there's multiple DVI outputs (ie. tested both).
D
deadwoodAROS Dev
Posted 16 days ago
Hmm, that's quite weird for the 4xx, 5xx and 6xx series. Which output are you using? VGA or DVI?
K
KorbanNewbie
Posted 16 days ago
Tested unsuccessfully on the following and results/symptoms were identical to original driver:

275 gtx
460 gts
570 gtx
660 gtx
660 ti
780 gtx
960 gtx
970 gtx

Tested and working:

8600gts (didnt with last driver)
440gt (did with last driver)
650 gtx (didnt with last driver)

The other differences I noticed were that with some non working cards fans now turn off at the time Wanderer would normally show and that there seems to be more resolution options for working cards. Take this with a grain of salt as its possible I just hadnt noticed last time, but Im reasonably sure its accurate.

Will do more testing shortly.
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 17 days ago
@ deadwood

Test nouveau.hidd-20260613-47.4

Laptop HP ENVY 15-k112nl, NVIDIA GeForce GTX 850M, is not yet supported

Laptop ACER ASpire 5920, NVIDIA GeForce 8600M, a black screen with a white line at the top of the screen.
A
Amiwell79Distro Maintainer
Posted 17 days ago
works on my GT 210 1Gb
You can view all discussion threads in this forum.
You cannot start a new discussion thread in this forum.
You cannot reply in this discussion thread.
You cannot start on a poll in this forum.
You cannot upload attachments in this forum.
You cannot download attachments in this forum.