Bugzilla – Bug 352867
sax2: cannot configure NVIDIA dual GPU cards
Last modified: 2008-06-24 20:07:01 UTC
Created attachment 190047 [details] Error no screen found for sax2 ..... All attempts to configure a NVIDIA Quadro NVS 440 card (dualhead) with sax2 failed. Configuration with nvidia-xconfig -a work, but more testing should be done. Single head configuration works, but wrong BusID is selected.
Created attachment 190048 [details] Error for configure (Ups lost card( with sax2 -r -m ...
Created attachment 190049 [details] Configuration hangs
Created attachment 190050 [details] Working configuration, but only one screen created The configuration is basically okay, but ... xorg.conf needs manual editing, because wrong card was selected. BusID 8:0:0 was used, but it should be BusID 7:0:0
as I said you have two cards one is at 7 the other at 8 sax2 -c 0 one screen sax2 -c 1 the other screen I'm sorry if both screens together doesn't work this is a driver problem. I can't help you I'm sorry
Hello Marcus, Please pay attention it is one card with 2 gpus. nvidia-xconfig works and have also a look at 352647, under SLED10 SP1 Novell generates with the same driver a xorg.conf for dualhead ( which unfortunately does not work ).
there are two devices with separate device ID's no matter if they are on one card or not. SLED for sure doesn't use the same driver because the kernel is different. Anyway if you don't mind call: init 3 sax2 --> send the log file /var/log/SaX.log thanks
Created attachment 190079 [details] includes SaX.log Beside the requested /var/log/SaX.log also Xorg.0.log and Xorg.90.log are included.
and what is the problem: you should see two displays one at 800x600 the other at 1024x768 (II) NVIDIA(0): Setting mode "800x600" (--) NVIDIA(0): Connected display device(s) on Quadro NVS 440 at PCI:8:0:0: (--) NVIDIA(0): CRT-0 ==> maybe no monitor connected or not detectable via DDC (--) NVIDIA(1): Connected display device(s) on Quadro NVS 440 at PCI:7:0:0: (--) NVIDIA(1): FUS B17-2 (DFP-0) (II) NVIDIA(1): Setting mode "1280x1024" ==> DDC ID FUSB172 (looks like a Fujitsu Siemens monitor) looks good to me ???
Sorry, the send log is not okay - what I should have sent is an output for sax2 -r Unfortunately I am running now a test. On Monday I will generate a new log. Winfrid
*** Bug 352647 has been marked as a duplicate of this bug. ***
Created attachment 190413 [details] Requested Data I have now rerun the command. Only sax2 -r -a works, in case of omitting the option -a the display goes black and my only chance was to reboot the system. With sax2 -r -a the order of screens is changed. The behaviour is similar to 352647 but not always identical.
Now I understand this is a card with two cpu's but they don't appear as single cards on the bus. Well I think we never took care that this was configured correctly. I also don't have such a card. * Stefan you already mentioned that we can't configure dual cpu cards Do we have such a card ? * Winfrid you said nvidia-xconfig can configure the card correctly. So can you send the xorg.conf created by the tool ? * Winfrid you said the wrong busID was selected but the only class 0x300 device in the PCI stack is 08-00-0. The binary nvidia driver see two devices yes but the linux kernel doesn't or I overlooked it in the logs Stefan could you comment here ? I don't think this is a bug but more a missing feature
Marcus, unfortunately we don't have such a card. In the Xserver log I can see two devices with class 300. (II) PCI: 07:00:0: chip 10de,014a card 10de,0358 rev a2 class 03,00,00 hdr 00 (II) PCI: 08:00:0: chip 10de,014a card 10de,0358 rev a2 class 03,00,00 hdr 00 SaX2 detects and configures two devices as well. 10-Jan 15:09:28 <I> [ Sysp: Server detection data Card0 => DomainId : 0x0 Card0 => BusId : 0x7 Card0 => SlotId : 0x00 Card0 => FuncId : 0x0 Card0 => Vendor : NVidia Card0 => Device : Quadro NVS 440 Card0 => VID : 0x10de Card0 => DID : 0x014a Card0 => Module : nv Card0 => BusType : AGP Card0 => Detected : 2 Card0 => Flag : DEFAULT Card0 => SUB-VID : 0x10de Card0 => SUB-DID : 0x0358 Card0 => DrvProfile : Depth24,NVidia Card1 => DomainId : 0x0 Card1 => BusId : 0x8 Card1 => SlotId : 0x00 Card1 => FuncId : 0x0 Card1 => Vendor : NVidia Card1 => Device : Quadro NVS 440 Card1 => VID : 0x10de Card1 => DID : 0x014a Card1 => Module : nv Card1 => BusType : AGP Card1 => Detected : 2 Card1 => Flag : DEFAULT Card1 => SUB-VID : 0x10de Card1 => SUB-DID : 0x0358 Card1 => DrvProfile : Depth24,NVidia Section "Device" BoardName "Quadro NVS 440" BusID "7:0:0" Driver "nvidia" Identifier "Device[0]" VendorName "NVidia" EndSection Section "Device" BoardName "Quadro NVS 440" BusID "8:0:0" Driver "nvidia" Identifier "Device[1]" VendorName "NVidia" EndSection --> comment #7.
but not comment #11 I'm maximal confused
Right. In comment #11 SaX2 only detects one device. The Xserver PCI scan detects two devices though. Don't know why.
Would it be possible that FSC sends us such a card short-term? This would make things much more easier to investigate. Location is Nürnberg, Germany.
Created attachment 190808 [details] requested xorg.conf ( #12 ) Hello Stefan, Don't be confused the xorg.conf was generated on a Celsius V840 running SLED10 SP1 64bit. If NVidia does not contact you until Jan. 23 - you should give me a note. Winfrid
I can't see something special in the file. As I said in my last comment I'm confused why one sax log find two devices while another sax log on the same machine doesn't. I guess this one here can only be solved if we have such a card. Stefan could you drop me a note if you got the card ? thanks
I agree. I'll let you know when/if the card arrives in the next two weeks.
==> set to later
The card just arrived.
Finally I got the promised 2 NVS 440 (PCIE + PCIX16) from NVIDIA.
Since I finally have the hardware for testing now I plan to look at this issue in the next week. For this it would be good to know what the requirements/expectations are from your side for SaX2 for creating the configuration for NVS 440 cards. This should include monitor setup - how many monitors connected to the graphics card - connected to which GPU/DMS-59 connector - connected via VGA or DVI-D Possibly we need a special profile for this card.
Hello Stefan, I informed Rainer to provide you the requested information. Winfrid
Hello Stefan, Maybe it was not really clear from the inital issue - my minimum expectation was, that a graphical installation with one display works - the situation at the time when I opened the incident, was - all steps of the graphical installation worked until the display is configured, after this the display is "black". All other requirements should be discussed with Rainer König. Winfrid
Thanks for clarification. But even for this minimal singlehead configuration I need to know how the hardware setup looks like.
I might be wrong here, but the minimal requirement is to have a working single-head display on the first connector. Getting dual-head right comes on top of that. Don't you agree?
Yes, but SaX2/driver behaviour might be completely different when connecting more than one monitor to the graphics card. Therefore I still would prefer to know the detailed hardware setup.
I'll give it a try using openSUSE 11.0 Beta1 with a single-head configuration - monitor connected to the first connected via DVI-D.
# sax2 -p Chip: 0 is -> VESA Framebuffer Graphics 04:00:0 0x10de 0x014a AGP fbdev Chip: 1 is -> VESA Framebuffer Graphics 05:00:0 0x10de 0x014a AGP fbdev # sax2 -r SaX: initializing please wait... SaX: your current configuration will not be read in SaX: no X-Server is running SaX: will start own server if needed SaX: ups lost card during probing... abort SaX: something went wrong while X was called with -probeonly SaX: try to call 'sax2 -p' and select a single device ? abort /var/log/SaX.log [...] 18-Apr 16:51:14 <I> [ Sysp: XStuff detection data SaX: ups lost card during probing... abort ] Using sax2 -r -c 0 m 0=nv works fine, but I'm not sure how to achieve this by a profile. Marcus, any hints? Machine is f29.
xorg-x11-driver-video.changes ------------------------------------------------------------------- Fri Apr 18 17:05:41 CEST 2008 - sndirsch@suse.de - added NVIDIA Quadro NVS 440 Device ID to sax2/hwinfo data [...]
It looks very similar when using the nvidia driver: # sax2 -p Chip: 0 is -> NVIDIA Quadro NVS 440 04:00:0 0x10de 0x014a AGP nvidia Chip: 1 is -> NVIDIA Quadro NVS 440 05:00:0 0x10de 0x014a AGP nvidia # sax2 -r SaX: initializing please wait... SaX: your current configuration will not be read in SaX: no X-Server is running SaX: will start own server if needed SaX: ups lost card during probing... abort SaX: something went wrong while X was called with -probeonly SaX: try to call 'sax2 -p' and select a single device ? abort /var/log/SaX.log 18-Apr 19:19:41 <I> [ Sysp: XStuff detection data SaX: ups lost card during probing... abort ] The workaround would be the same: sax2 -r -c 0 So here we would need a special profile as well.
I'm sorry I don't have time to take care for multi card support. Especially in all of these cases I end up with X-Server problems which are really annoying and all I found is what I wrote in the past what has worked before doesn't work anymore. It would be really really really the best thing if Xorg would support and maintain their own configuration tool as soon as possible
There has been a misunderstanding. I'll do some more investigation on this issue.
Implementing enhancement Bug #381644 would resolve this issue.
*** Bug 396543 has been marked as a duplicate of this bug. ***
Same problem with a GeForce 9800 GX2.
*** Bug 402164 has been marked as a duplicate of this bug. ***
*** Bug 403366 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 381644 ***