tech-x11 archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: mga(4) dual-head setup broken after update



Tobias Nygren --> tech-x11 (2009-11-23 16:00:16 +0100):
> On Wed, 18 Nov 2009 00:10:34 +0100
> Jukka Salmi <j+nbsd%2009.salmi.ch@localhost> wrote:
> 
> > updating a NetBSD/i386 5.0_STABLE system with native Xorg (X server
> > 1.4.2 -> 1.6.3, mga driver 1.4.8 -> 1.4.11) broke the dual-head setup
> > I'm using with my Matrox G450 video card:
> > 
> > $ startx
> > [...]
> > (WW) MGA(0): Direct rendering disabled
> > (==) RandR enabled
> > (EE) MGA(1): Unable to map BAR 0.  Invalid argument (22)
> > 
> > Fatal server error:
> > AddScreen/ScreenInit failed for driver 1
> > [...]
> > 
> > (The full [1]log is available, as is the [2]log from before the update.)
> > 
> > Any hints about how to fix this?  Single-head works fine, BTW.
> 
> Probably delete your configuration, start over with a clean one and use
> xrandr(1) to configure the dual-head setup from your ~/.xsession.
> 
> This means you lose the ability to use your monitors as separate
> screens. For some reason they broke this with 1.5 server, it's
> not just an MGA issue.

Thanks for the hint.

However, with a clean (i.e., `Xorg -configure'-generated) xorg.conf,
xrandr(1) sees only a single output:

$ xrandr -q
Screen 0: minimum 400 x 300, current 1600 x 1200, maximum 1600 x 1200
default connected 1600x1200+0+0 0mm x 0mm
   1600x1200      60.0* 
   1400x1050      60.0     75.0  
   1280x1024      75.0     60.0  
   1280x960       60.0  
   1152x864       75.0  
   1024x768       75.0     70.0     60.0  
   832x624        75.0  
   800x600        75.0     72.0     60.0     56.0     65.0  
   700x525        75.0     60.0  
   640x512        75.0     60.0  
   640x480        75.0     73.0     67.0     60.0  
   720x400        70.0  
   576x432        75.0  
   512x384        75.0     70.0     60.0  
   416x312        75.0  
   400x300        75.0     72.0     60.0     56.0  

I tried adding a second "Monitor" section to xorg.conf, but this seems
not to help.  Any hints?


TIA, Jukka

-- 
This email fills a much-needed gap in the archives.


Home | Main Index | Thread Index | Old Index