nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   Twinview virtual screen size (http://www.nvnews.net/vbulletin/showthread.php?t=86888)

encmonkey 02-22-07 01:29 PM

Twinview virtual screen size
 
1 Attachment(s)
Howdy!

I am trying to configure two metamodes: first one with the CRT off, the DFP on at 1440x900. The second metamode is CRT at 800x600, and the DFP at 1440x900. The CRT is a projector, and 90% of the time it will be off, but it's nice to kick on and show a movie or something.

The issue I'm running into is the driver seems to find the largest virtual screen size on the metamode line and use that for all the metamodes - in this case, 2240x900. This is fine if the CRT is on, but when the CRT is off, I get the big panning 2240x900 desktop on my 1440x900 DFP.

Am I doing something wrong, or is this the normal behavior? I've seen lots of examples with modelines like "1280x1024,1280x1024; 1024x768,1024x768" and can't believe that folks running in the second, smaller resolution are panning around like mad, so I assume I'm farking something up.

Any help would be greatly appreciated, as I've killed a ton of time on this one.

encmonkey 02-26-07 01:17 AM

Re: Twinview virtual screen size
 
Any ideas on this? Does Twinview resize the desktop size based on the metamode selected, or just create a window based on the largest?

Also, I've noticed that if a metamode with a NULL monitor is listed first, it will crash X (cold stop, no additional logging).

Any ideas would be appreciated -

AaronP 03-02-07 06:31 PM

Re: Twinview virtual screen size
 
Hi encmonkey,

Yes, the screen will start up with a desktop large enough to fit all of the requested modes. You can use the xrandr command to resize your desktop after the server has started. As for NULL modes crashing, I'm not able to reproduce that problem.

encmonkey 03-04-07 09:04 PM

Re: Twinview virtual screen size
 
Hrm.. I tried that - when I put the "NULL, 1440x900" listing in (after the 800x600, 1440x900 metamode) I can do xrandr -q to get the modes (and they will both be listed) but only once in a blue moon will changing over to xrandr -s 1 (1440x900) not result in a hard wedged machine. I've checked the Xlog file, and it doesn't look to be catching any crash dump info.

I'm running the kernel from 64studio with the debian etch repositories. The nvidia kernel seemed to compile just fine and install. Are there any known issues with a config like this?

AaronP 03-04-07 11:59 PM

Re: Twinview virtual screen size
 
Looking at your bug report, I'm seeing IRQ problems that could be related to the fact that your kernel is using MMCONFIG. See http://us.download.nvidia.com/XFree8...ppendix-l.html and try using the "pci=nommconf" kernel option.

encmonkey 03-07-07 04:08 AM

Re: Twinview virtual screen size
 
Thanks for the help, AaronP. I've added pci=nommconf per your instructions (and attached docs) but that had no change. I also tried (fer giggles) upgrading the bios on the motherboard to see if that would fix any IRQ issues lingering, also no change.

Could you give an example of the IRQ issues you saw in the debug? This machine should be pretty simple hardware-wise, with the only additional component being an RME Digi9652. Everything else is the motherboard..

AaronP 03-07-07 10:51 AM

Re: Twinview virtual screen size
 
Code:

PCI: Using MMCONFIG at e0000000
...
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
...
nvidia: module license 'NVIDIA' taints kernel.
ACPI: PCI Interrupt Link [APC7] enabled at IRQ 16
ACPI: PCI Interrupt 0000:00:05.0[A] -> Link [APC7] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:05.0 to 64
NVRM: loading NVIDIA UNIX x86_64 Kernel Module  1.0-9746  Fri Dec 15 10:19:35 PST 2006
...
irq 16: nobody cared (try booting with the "irqpoll" option)

Call Trace:
 [<ffffffff802ac2c6>] __report_bad_irq+0x30/0x7d
 [<ffffffff802ac4df>] note_interrupt+0x1cc/0x202
 [<ffffffff802ab8e5>] thread_simple_irq+0x6c/0x7b
 [<ffffffff802ac088>] do_irqd+0xe6/0x2f4
 [<ffffffff802abfa2>] do_irqd+0x0/0x2f4
 [<ffffffff80294451>] keventd_create_kthread+0x0/0x66
 [<ffffffff802304f3>] kthread+0xd1/0x101
 [<ffffffff8025af08>] child_rip+0xa/0x12
 [<ffffffff80294451>] keventd_create_kthread+0x0/0x66
 [<ffffffff80230422>] kthread+0x0/0x101
 [<ffffffff8025aefe>] child_rip+0x0/0x12

handlers:
[<ffffffff882d4aec>] (snd_rme9652_interrupt+0x0/0x5f [snd_rme9652])
[<ffffffff88656ef6>] (nv_kern_isr+0x0/0x5e [nvidia])
turning off IO-APIC fast mode.
irq 16: nobody cared (try booting with the "irqpoll" option)

Call Trace:
 [<ffffffff802ac2c6>] __report_bad_irq+0x30/0x7d
 [<ffffffff802ac4df>] note_interrupt+0x1cc/0x202
 [<ffffffff802ab8e5>] thread_simple_irq+0x6c/0x7b
 [<ffffffff802ac088>] do_irqd+0xe6/0x2f4
 [<ffffffff802abfa2>] do_irqd+0x0/0x2f4
 [<ffffffff80294451>] keventd_create_kthread+0x0/0x66
 [<ffffffff802304f3>] kthread+0xd1/0x101
 [<ffffffff8025af08>] child_rip+0xa/0x12
 [<ffffffff80294451>] keventd_create_kthread+0x0/0x66
 [<ffffffff80230422>] kthread+0x0/0x101
 [<ffffffff8025aefe>] child_rip+0x0/0x12

handlers:
[<ffffffff882d4aec>] (snd_rme9652_interrupt+0x0/0x5f [snd_rme9652])
[<ffffffff88656ef6>] (nv_kern_isr+0x0/0x5e [nvidia])



All times are GMT -5. The time now is 12:23 PM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.