Processing commands for [EMAIL PROTECTED]:
> tag 161072 + upstream
Bug#161072: xlibs: XScreenSaverQueryInfo broken on Alpha
Tags added: upstream
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian
Michel Dänzer wrote:
>> > - TuxRacer: Tux looks white!
>>
>>Hah! Tux looks normal now!
>>However, still problems with Tuxracer: with the new drivers, the game
>>slows down incredibly about every second. It seems to go smoooth,
almost
>>stops then, continues smoothly then, almost stops
On Sam, 2002-11-09 at 13:29, Manuel Bilderbeek wrote:
> Setting up xserver-xfree86-dri-trunk (2002.11.06-1) ...
> Argument "180=" isn't numeric in numeric lt (<) at
> /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 25.
Hmm, might be caused by some cruft left over in the postinst. Cleaning
that u
package: xserver-xfree86
version: 4.2.1-3
packages from testing, latest driver from nvidia(1.0-3123) compiled
against 2.4.19 and/or 2.4.20-rc1.
kernel reports "no more MTRRs available", the messages in XFree86.0.log
are the same, except the driver reporting the warning is NV(0).
the message co
Michel Dänzer wrote:
Hmm, might be caused by some cruft left over in the postinst. Cleaning
that up for the next version.
OK, I'm doing a dist-upgrade everyday, so I guess I'll see it coming then.
I downgraded the xserver-xfree86-dri-trunk package, which solved the
problem.
Ah, this might be
#include
* H. Ziegler [Sat, Nov 09 2002, 03:41:56PM]:
> package: xserver-xfree86
> version: 4.2.1-3
>
> packages from testing, latest driver from nvidia(1.0-3123) compiled
> against 2.4.19 and/or 2.4.20-rc1.
>
> kernel reports "no more MTRRs available", the messages in XFree86.0.log
> are the
Hi,
the previous patch didn't apply cleanly against 4.2.1; this one
does. I've also tested it, and it works.
As libXss is only built statically, programs using it will have to be
rebuilt on Alpha. I will try to do that for programs I can identify,
after a fixed X has been uploaded.
--
F
Package: xserver-xfree86
Version: 4.2.1-3
Severity: normal
Hello,
as very good described on
http://www.cse.unsw.edu.au/~chak/linux/c400.html
its not possible to use the dell latitude c600 with a "normal"
(1024x768 16 or more Bit) resolution.
The patch
(http://www.cse.unsw.edu.au/~chak/linux/i830
Processing commands for [EMAIL PROTECTED]:
> tag 168178 - moreinfo
Bug#168178: xserver-xfree86: [savage] runs out of MTRRs
Tags removed: moreinfo
> tag 168178 + upstream
Bug#168178: xserver-xfree86: [savage] runs out of MTRRs
Tags added: upstream
>
End of message, stopping processing here.
Plea
Processing commands for [EMAIL PROTECTED]:
> retitle 168178 xserver-xfree86: [savage] runs out of MTRRs on unknown chipset
>(0x8c2e) rev 5
Bug#168178: xserver-xfree86: [savage] runs out of MTRRs
Changed Bug title.
>
End of message, stopping processing here.
Please contact me if you need assista
On Fri, Nov 08, 2002 at 09:24:49PM -0800, Chad Carr wrote:
> Attached inline. Also, I have been in communication with Tim Roberts
> (the upstream author?) and he has given me version 1.1.26t which seems
> to fix the problem, but has additional issues with gradient drawing.
[...]
> (--) PCI:*(1:0:0
On Sat, Nov 09, 2002 at 10:07:44PM +0100, Falk Hueffner wrote:
> the previous patch didn't apply cleanly against 4.2.1; this one
> does. I've also tested it, and it works.
>
> As libXss is only built statically, programs using it will have to be
> rebuilt on Alpha. I will try to do that for progra
On Sat, Nov 09, 2002 at 03:41:56PM +0100, H. Ziegler wrote:
> finally the server doesn't start because:
> "caught signal 11. server aborting"
>
> let me know if you need more info.
I always need the info described in the XF86Config(7) manual page.
$ man 7 XF86Config
--
G. Branden Robinson
On Sam, 2002-11-09 at 18:23, Manuel Bilderbeek wrote:
>
> >>Most debug messages are gone now (e.g. when dragging the
> >>glxgears window), but the problems with Tuxracer remain.
> >
> > What problems exactly? Note that it is slow in depth 24, and it shows
> > some incorrect rendering unless RADEO
Michel Dänzer wrote:
On Sam, 2002-11-09 at 18:23, Manuel Bilderbeek wrote:
What problems exactly? Note that it is slow in depth 24, and it shows
some incorrect rendering unless RADEON_TCL_FORCE_DISABLE=1 is set.
This doesn't really make a difference. The problems are:
- Every about 0.4 seconds
On Sat, 9 Nov 2002 17:08:22 -0500
"Branden Robinson" <[EMAIL PROTECTED]> wrote:
> On Fri, Nov 08, 2002 at 09:24:49PM -0800, Chad Carr wrote:
> > Attached inline. Also, I have been in communication with Tim Roberts
> > (the upstream author?) and he has given me version 1.1.26t which seems
> > to f
On Sat, Nov 09, 2002 at 03:13:10PM -0800, Chad Carr wrote:
> "Branden Robinson" <[EMAIL PROTECTED]> wrote:
> > > (--) PCI:*(1:0:0) S3 unknown chipset (0x8c2e) rev 5, Mem @ 0xffe8/19,
>0xec00/26, 0xe800/26, 0xe600/25, BIOS @ 0x000c/16
> >
> > I'd say the above is a good sign th
On Fri, Nov 08, 2002 at 04:00:10PM -0500, Branden Robinson wrote:
> merge 80404 168147
> thanks
>
> Just FYI, it's considered polite to check existing bug reports against a
> package before filing duplicates.
Oops, sorry :-/
Julian
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Processing commands for [EMAIL PROTECTED]:
> tag 161072 + upstream
Bug#161072: xlibs: XScreenSaverQueryInfo broken on Alpha
Tags added: upstream
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian
Michel Dänzer wrote:
>> > - TuxRacer: Tux looks white!
>>
>>Hah! Tux looks normal now!
>>However, still problems with Tuxracer: with the new drivers, the game
>>slows down incredibly about every second. It seems to go smoooth,
almost
>>stops then, continues smoothly then, almost stop
On Sam, 2002-11-09 at 13:29, Manuel Bilderbeek wrote:
> Setting up xserver-xfree86-dri-trunk (2002.11.06-1) ...
> Argument "180=" isn't numeric in numeric lt (<) at
> /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 25.
Hmm, might be caused by some cruft left over in the postinst. Cleaning
that u
package: xserver-xfree86
version: 4.2.1-3
packages from testing, latest driver from nvidia(1.0-3123) compiled
against 2.4.19 and/or 2.4.20-rc1.
kernel reports "no more MTRRs available", the messages in XFree86.0.log
are the same, except the driver reporting the warning is NV(0).
the message
Michel Dänzer wrote:
Hmm, might be caused by some cruft left over in the postinst. Cleaning
that up for the next version.
OK, I'm doing a dist-upgrade everyday, so I guess I'll see it coming then.
I downgraded the xserver-xfree86-dri-trunk package, which solved the
problem.
Ah, this might b
#include
* H. Ziegler [Sat, Nov 09 2002, 03:41:56PM]:
> package: xserver-xfree86
> version: 4.2.1-3
>
> packages from testing, latest driver from nvidia(1.0-3123) compiled
> against 2.4.19 and/or 2.4.20-rc1.
>
> kernel reports "no more MTRRs available", the messages in XFree86.0.log
> are the
Hi,
the previous patch didn't apply cleanly against 4.2.1; this one
does. I've also tested it, and it works.
As libXss is only built statically, programs using it will have to be
rebuilt on Alpha. I will try to do that for programs I can identify,
after a fixed X has been uploaded.
--
F
Package: xserver-xfree86
Version: 4.2.1-3
Severity: normal
Hello,
as very good described on
http://www.cse.unsw.edu.au/~chak/linux/c400.html
its not possible to use the dell latitude c600 with a "normal"
(1024x768 16 or more Bit) resolution.
The patch
(http://www.cse.unsw.edu.au/~chak/linux/i830
Processing commands for [EMAIL PROTECTED]:
> tag 168178 - moreinfo
Bug#168178: xserver-xfree86: [savage] runs out of MTRRs
Tags removed: moreinfo
> tag 168178 + upstream
Bug#168178: xserver-xfree86: [savage] runs out of MTRRs
Tags added: upstream
>
End of message, stopping processing here.
Plea
Processing commands for [EMAIL PROTECTED]:
> retitle 168178 xserver-xfree86: [savage] runs out of MTRRs on unknown chipset
> (0x8c2e) rev 5
Bug#168178: xserver-xfree86: [savage] runs out of MTRRs
Changed Bug title.
>
End of message, stopping processing here.
Please contact me if you need assist
On Fri, Nov 08, 2002 at 09:24:49PM -0800, Chad Carr wrote:
> Attached inline. Also, I have been in communication with Tim Roberts
> (the upstream author?) and he has given me version 1.1.26t which seems
> to fix the problem, but has additional issues with gradient drawing.
[...]
> (--) PCI:*(1:0:0
On Sat, Nov 09, 2002 at 10:07:44PM +0100, Falk Hueffner wrote:
> the previous patch didn't apply cleanly against 4.2.1; this one
> does. I've also tested it, and it works.
>
> As libXss is only built statically, programs using it will have to be
> rebuilt on Alpha. I will try to do that for progra
On Sat, Nov 09, 2002 at 03:41:56PM +0100, H. Ziegler wrote:
> finally the server doesn't start because:
> "caught signal 11. server aborting"
>
> let me know if you need more info.
I always need the info described in the XF86Config(7) manual page.
$ man 7 XF86Config
--
G. Branden Robinson
On Sam, 2002-11-09 at 18:23, Manuel Bilderbeek wrote:
>
> >>Most debug messages are gone now (e.g. when dragging the
> >>glxgears window), but the problems with Tuxracer remain.
> >
> > What problems exactly? Note that it is slow in depth 24, and it shows
> > some incorrect rendering unless RADEO
Michel Dänzer wrote:
On Sam, 2002-11-09 at 18:23, Manuel Bilderbeek wrote:
What problems exactly? Note that it is slow in depth 24, and it shows
some incorrect rendering unless RADEON_TCL_FORCE_DISABLE=1 is set.
This doesn't really make a difference. The problems are:
- Every about 0.4 second
On Sat, 9 Nov 2002 17:08:22 -0500
"Branden Robinson" <[EMAIL PROTECTED]> wrote:
> On Fri, Nov 08, 2002 at 09:24:49PM -0800, Chad Carr wrote:
> > Attached inline. Also, I have been in communication with Tim Roberts
> > (the upstream author?) and he has given me version 1.1.26t which seems
> > to f
On Sat, Nov 09, 2002 at 03:13:10PM -0800, Chad Carr wrote:
> "Branden Robinson" <[EMAIL PROTECTED]> wrote:
> > > (--) PCI:*(1:0:0) S3 unknown chipset (0x8c2e) rev 5, Mem @ 0xffe8/19,
> > > 0xec00/26, 0xe800/26, 0xe600/25, BIOS @ 0x000c/16
> >
> > I'd say the above is a good si
On Fri, Nov 08, 2002 at 04:00:10PM -0500, Branden Robinson wrote:
> merge 80404 168147
> thanks
>
> Just FYI, it's considered polite to check existing bug reports against a
> package before filing duplicates.
Oops, sorry :-/
Julian
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
36 matches
Mail list logo
