Description of problem: ======================= fixme:d3d_caps:wined3d_guess_card_vendor Received unrecognized GL_VENDOR "Nouveau". Returning HW_VENDOR_NVIDIA. fixme:d3d_caps:select_card_nvidia_mesa Card selection not handled for Mesa Nouveau driver err:d3d:check_fbo_compat >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from Framebuffer format check @ utils.c / 1083 err:d3d:check_fbo_compat >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from Framebuffer format check @ utils.c / 1083 ide/wine/wine/drive_c/S3Graphics/S3FotoPro/1.0.0.3/S3FotoPro.exe: nv10_state_fb.c:49: get_rt_format: asserzione "0" non riuscita. wine: Assertion failed at address 0x68000852 (thread 004e), starting debugger... Unhandled exception: assertion failed in 32-bit code (0x68000852). Register dump: Version-Release number of selected component (if applicable): wine-1.3.10-1.fc14.i686 How reproducible: Always when D3D is needed Steps to Reproduce: 1. Run a program that requires D3D under wine (you can use the latest beta from http://zx32home.net/ to trigger the error) Additional info: With nvidia proprietary blob it all works well. My card is: 01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev a2)
For 3d to work you will need to have the experimental gallium drivers installed. This might or might not work. Even upstream is not accepting bug reports for 3d features yet. Please also take a look at http://nouveau.freedesktop.org/wiki/FeatureMatrix. 3d is marked was 'work-in-progress' for the NV20 chips. You can test nouveau 3d support by installing mesa-dri-drivers-experimental. However please don't expect any support for it atm.
p.s. I know that nouveau 3D is not production ready. So I don't actually expect this to be fixed nor discussed. I Just wanted to raise a flag, just in case it was an easily fixable issue; eg. by adding a flag in some list of driver/card combinations that wine uses.
Oh I forgot to mention: Of course I have mesa-dri-drivers-experimental installed. :)
*** Bug 668560 has been marked as a duplicate of this bug. ***
(In reply to comment #3) > Oh I forgot to mention: > Of course I have mesa-dri-drivers-experimental installed. :) Of course you are right. I will have a look asap.
I've Got news for you. It is working as of Fedora 16. I like this kind of surprises!!! :))
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping