Re: xlibmesa-gl1-dri-trunk conflicting with X from experimental ?
- To: Soeren Sonnenburg <firstname.lastname@example.org>
- Cc: Benjamin Herrenschmidt <email@example.com>, "firstname.lastname@example.org" <email@example.com>
- Subject: Re: xlibmesa-gl1-dri-trunk conflicting with X from experimental ?
- From: Michel Dänzer <firstname.lastname@example.org>
- Date: Fri, 09 Jan 2004 12:57:59 +0100
- Message-id: <email@example.com>
- In-reply-to: <1073574189.10977.28.camel@localhost>
- References: <1073462045.5138.5.camel@localhost> <firstname.lastname@example.org> <1073553012.2827.26.camel@localhost> <email@example.com> <1073574189.10977.28.camel@localhost>
On Thu, 2004-01-08 at 16:03, Soeren Sonnenburg wrote:
> On Thu, 2004-01-08 at 15:26, Michel Dänzer wrote:
> > On Thu, 2004-01-08 at 10:18, Soeren Sonnenburg wrote:
> > > On Wed, 2004-01-07 at 17:01, Michel Dänzer wrote:
> > > > On Wed, 2004-01-07 at 08:54, Soeren Sonnenburg wrote:
> > >
> > > > > And while we are at it, I now get a blank screen when switching back to
> > > > > console... it even does not go on again when switching back to X... all
> > > > > that helps is putting the machine to sleep and back or reboot.
> > > >
> > > > Can you try and determine what change caused this?
> > >
> > > uuhh, it works now... not 100% sure whether this is because I switched
> > > back from 2.6.1-rc1-ben1 to 2.6.0-ben1 or happened in the recent apt-get
> > > upgrades...
> > Actually, reading your description again, it matches a known
> > intermittent problem when running without Option "UseFBDev".
> but why does it seem to work now in 2.6.0-ben1 ... hmm.
'Intermittent' is the keyword. It seemed to happen about every second
time on average for me but may be rarer for you.
> [scroll speed issue]
> I really tried to find out what happens in xterm but did not succeed
> (time constraints)... however I really noticed the fast scroll speed in
> Eterm which seems to deaccellerated when it reaches the last lines...
> Maybe some X guru could resolve that issue.
My understanding is that it's all related to (lack of) buffering. Piping
output to cat seems a usable workaround in most cases, but of course it
doesn't help with vim...
Earthling Michel Dänzer | Debian (powerpc), X and DRI developer
Software libre enthusiast | http://svcs.affero.net/rm.php?r=daenzer