| Summary: | KMS, Dualhead: Strange bigger console | ||
|---|---|---|---|
| Product: | xorg | Reporter: | Achim Schaefer <achim_schaefer> |
| Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> |
| Status: | CLOSED NOTABUG | QA Contact: | Xorg Project Team <xorg-team> |
| Severity: | normal | ||
| Priority: | medium | CC: | achim_schaefer |
| Version: | unspecified | ||
| Hardware: | x86 (IA32) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Achim Schaefer
2009-12-29 14:39:24 UTC
This is the expected behaviour. fbcon was never designed for multiple displays, so this is the best that can be done at this time. I know handling of this situation is not very easy. But the current situation is Would it be possible to use in both screens the lower resolution, so in my case in both 1024x768? (In general the highest res all active screens support) At least this would avoid some trouble. Switching to X would than cause a mode change on the bigger screen, but I think that is less problematic compared to the usage of a small part of a bigger screen. Achim, this is more of a user preference to choose one over the other: 1. use the best mode on each output 2. use the largest common mode on all outputs Case 1 is what X does, and one goal of KMS is flickerless boot, so it fits and is the default policy in general. Case 2 you should be able to achieve with the "video" kernel command line parameter, forcing the small mode on the big monitor. I hope it is documented in the kernel Documentation, since I do not recall the correct syntax. (In reply to comment #3) > Case 2 you should be able to achieve with the "video" kernel command line > parameter, forcing the small mode on the big monitor. I hope it is documented > in the kernel Documentation, since I do not recall the correct syntax. That depends if nouveau driver uses modedb or not. from Documentation/fb/modedb.txt Drivers that support modedb boot options 123 Boot Name Cards Supported 124 125 amifb - Amiga chipset frame buffer 126 aty128fb - ATI Rage128 / Pro frame buffer 127 atyfb - ATI Mach64 frame buffer 128 pm2fb - Permedia 2/2V frame buffer 129 pm3fb - Permedia 3 frame buffer 130 sstfb - Voodoo 1/2 (SST1) chipset frame buffer 131 tdfxfb - 3D Fx frame buffer 132 tridentfb - Trident (Cyber)blade chipset frame buffer 133 vt8623fb - VIA 8623 frame buffer But here you can not find nouveau. So either a new doc gets created with the options to handle this, or this doc gets updated including nouveau. I hope with staging drivers you are allowed to change the existing docs-) => I assume I'll close this bug, and open a documentation bug? (In reply to comment #4) > (In reply to comment #3) > > Case 2 you should be able to achieve with the "video" kernel command line > > parameter, forcing the small mode on the big monitor. I hope it is documented > > in the kernel Documentation, since I do not recall the correct syntax. > That depends if nouveau driver uses modedb or not. > > from Documentation/fb/modedb.txt That is the legacy fb option "video". I was talking about the drmfb "video" variant, but I cannot find the documentation. The only doc I know of is: http://cgit.freedesktop.org/nouveau/linux-2.6/tree/drivers/gpu/drm/drm_fb_helper.c#n68 The syntax is something like: video=<output>:<mode> Where output is as reported by the kernel DRM/KMS. A made-up example: video=DVI-I-1:1024x768 This option is for all DRM/KMS fb drivers AFAIK: intel, radeon and nouveau. It's a bit odd that it isn't properly documented yet. the specified parameters work as expected. Thanks |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.