Comment 21 for bug 47775

Revision history for this message
In , agd5f (agd5f) wrote :

(In reply to comment #11)
> (In reply to comment #10)
> > > Strange I found, that
> > > a.) X always started in 1280x1024 clone mode, however only showing 1024x768 on
> > > both monitors (with a virtual screen of 1280x1024)
> >
> > This is because your first metamode is 1024x768. and the largest metamode is
> > 1280x1024.
> >
> Ähh, o.k. How can I start X then in 1024x768 clone mode without any virtual
> screen. This would be my default setup. Only when I connect to the docking
> station with the external monitor, I would like to switch to 1280x1024 clone
> mode (with the virtual screen on the laptop LCD) or the dual-head-setup.

Unforunately that is a limitation of mergedfb, which is a big hack to begin
with. you'd either need to hack the driver to pre-reserve the additional
desktop space at the beginning or and xrandr -s 0 to your .xinitrc to resize the
desktop when you login. I think keithp is working on an improved version of
mergedfb that may address this.

>
> > > c.) switching with CTRL-ALT-Keypad+/- switched through all three modes but in
> > > the clone modes there was always a 1280x1024 virtual screen area. No windows
> > > were repositioned (and the the KDE kicker did not adapt either)
> >
> > only xrandr resizes the desktop. CTRL-ALT-Keypad+/- just changes the mode; the
> > desktop remains the same size.
> >
>
> O.K. so one needs a combination of xrandr and the CTRL-ALT-Keypad in order to
> switch between these three modes?
>

depending on what you want to do xrandr should be fine. CTRL-ALT-Keypad uses
the vidmode extension to change the mode. It came along before xrandr could
resize the desktop to match the mode.

> > >
> > > 2.) What I always hate with such freezes is that data is lost on the harddisk.
> > > I'm using ext3 and in the boot process you first see the journal
recovering with
> > > lots of inodes deleted, then the fsck yielding lots of errors, trying to
correct
> > > them and then finally a reboot. Awful :(
> >
> > save your data and type 'sync' to flush to the HD before you try test
> something likely to crash.
> >
>
> I thought ALT-SYSRQ-S + ALT-SYSRQ-U should do (sync and remount ro). But that
> did not work. Next time I try to issue "sync" and see what happens...

that won't work if your system is already locked solid ;) sync is a preemptive
method.

>
> > What version of the radeon driver are you using?
> >
>
> 6.5.8.0-1 from Debian unstable.
>
> Xorg.0.log says:
>
> (II) LoadModule: "radeon"
> (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
> (II) Module radeon: vendor="X.Org Foundation"
> compiled for 7.0.0, module version = 4.0.3
> Module class: X.Org Video Driver
> ABI class: X.Org Video Driver, version 0.8
> (II) LoadModule: "ati"
> (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
> (II) Module ati: vendor="X.Org Foundation"
> compiled for 7.0.0, module version = 6.5.8
> Module class: X.Org Video Driver
> ABI class: X.Org Video Driver, version 0.8
>
> (II) ATI: ATI driver (version 6.5.8) for chipsets: ati, ativga
>

That should be the most recent stable 7.0 release, IIRC.