Dan Christensen <[EMAIL PROTECTED]> writes:
> I see that this is a Debian specific patch:
>
> 044_chips_default_to_noaccel_on_69k.diff
Does anyone know why and when this patch was included in Debian? The
only reference to it I could find in the changelog (or old changelog)
Dan Christensen <[EMAIL PROTECTED]> writes:
> Dan Christensen <[EMAIL PROTECTED]> writes:
>
>> Package: xserver-xfree86
>> Version: 4.3.0.dfsg.1-14
>>
>> (WW) CHIPS(0): Acceleration is disabled by default on C&T 69000 as it has
>> been r
Dan Christensen <[EMAIL PROTECTED]> writes:
> Package: xserver-xfree86
> Version: 4.3.0.dfsg.1-14
>
> I upgraded from an old (4.1) version of XFree86 to 4.3.0.dfsg.1-14
> today, and now acceleration is disabled for my chipset by the driver:
>
> (WW) CHIPS(0): Accelera
Dan Christensen <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] (Aaron M. Ucko) writes:
>
>> Dan Christensen <[EMAIL PROTECTED]> writes:
>>
>>> Option "Accel"
>>
>> You may need to use a double negative here; does
>>
>
[EMAIL PROTECTED] (Aaron M. Ucko) writes:
> The chips(4) manpage
I didn't know about that manpage. It says that the 69000 should
support acceleration. Also, the README.chips.gz distributed
with xserver-xfree86 says that X 4.3 has "heaps more acceleration".
Dan
--
To UNSUBSCRIBE, email to [E
[EMAIL PROTECTED] (Aaron M. Ucko) writes:
> Dan Christensen <[EMAIL PROTECTED]> writes:
>
>> Option "Accel"
>
> You may need to use a double negative here; does
>
> Option "NoAccel" "off"
>
> work any better?
I won't h
Package: xserver-xfree86
Version: 4.3.0.dfsg.1-14
Severity: normal
I upgraded from an old (4.1) version of XFree86 to 4.3.0.dfsg.1-14
today, and now acceleration is disabled for my chipset by the driver:
(WW) CHIPS(0): Acceleration is disabled by default on C&T 69000 as it has been
reported
to
Tomas Nykung <[EMAIL PROTECTED]> writes:
> So, here is what I want:
> - 3 X servers running at the same time, started from kdm
> (for graphical login)
>
> - the first server running at 1024x768, with 16 bits colours, DRI enabled
> (for the kids, they mostly play games...)
>
> - the two others runn
Dan Christensen <[EMAIL PROTECTED]> writes:
> Michel Dänzer <[EMAIL PROTECTED]> writes:
>
>> On Thu, 2002-01-10 at 23:19, Dan Christensen wrote:
>>> Lars Steinke <[EMAIL PROTECTED]> writes:
>>>
>>> > use the X11 Framebuffer driver (
Dan Christensen <[EMAIL PROTECTED]> writes:
> Michel Dänzer <[EMAIL PROTECTED]> writes:
>
>> On Thu, 2002-01-10 at 23:19, Dan Christensen wrote:
>>> Lars Steinke <[EMAIL PROTECTED]> writes:
>>>
>>> > use the X11 Framebuffer driver (
Michel Dänzer <[EMAIL PROTECTED]> writes:
> On Thu, 2002-01-10 at 23:19, Dan Christensen wrote:
>> Lars Steinke <[EMAIL PROTECTED]> writes:
>>
>> >> Alternatively, is there any work-around I could use in the meantime?
>> >
>> > use the
Michel Dänzer <[EMAIL PROTECTED]> writes:
> On Thu, 2002-01-10 at 23:19, Dan Christensen wrote:
>> Lars Steinke <[EMAIL PROTECTED]> writes:
>>
>> >> Alternatively, is there any work-around I could use in the meantime?
>> >
>> > use the
Lars Steinke <[EMAIL PROTECTED]> writes:
>> Alternatively, is there any work-around I could use in the meantime?
>
> Sure use the X11 Framebuffer driver (with the radeonfb driver in Linux 2.4),
Thanks, I just compiled 2.4.17 with radeonfb as a module. When I
ran startx, it complained about no
Lars Steinke <[EMAIL PROTECTED]> writes:
>> Alternatively, is there any work-around I could use in the meantime?
>
> Sure use the X11 Framebuffer driver (with the radeonfb driver in Linux 2.4),
Thanks, I just compiled 2.4.17 with radeonfb as a module. When I
ran startx, it complained about no
Lars Steinke <[EMAIL PROTECTED]> writes:
> I wonder if you had time to provide that patch set you mentioned on
> http://lists.debian.org/debian-x/2001/debian-x-200111/msg00033.html
> to Branden yet ? I downloaded a 4.1.99.1 binary package elsewhere and
> found the Mobility Radeon M6 2D support to
Lars Steinke <[EMAIL PROTECTED]> writes:
> I wonder if you had time to provide that patch set you mentioned on
> http://lists.debian.org/debian-x/2001/debian-x-200111/msg00033.html
> to Branden yet ? I downloaded a 4.1.99.1 binary package elsewhere and
> found the Mobility Radeon M6 2D support to
ave
Option "DPMS"
in both the Device section and the Monitor section.
The extmod module is loaded fine (I think this handles dpms, but might
be wrong).
Any suggestions for what else to try? Any other information I
should provide?
Thanks,
Dan
--
Dan Christensen
[EMAIL PROTECTED]
ave
Option "DPMS"
in both the Device section and the Monitor section.
The extmod module is loaded fine (I think this handles dpms, but might
be wrong).
Any suggestions for what else to try? Any other information I
should provide?
Thanks,
Dan
--
Dan Christensen
[EMAIL PROTECT
Is there documentation available which describes the various modules
that can be loaded into XFree 86, what they do, and what size they
are? The version of dexter in the 4.0.1-3 debian package produces an
XF86Config file that loads all sorts of modules by default, and as a
result my X server consu
Is there documentation available which describes the various modules
that can be loaded into XFree 86, what they do, and what size they
are? The version of dexter in the 4.0.1-3 debian package produces an
XF86Config file that loads all sorts of modules by default, and as a
result my X server cons
Taketoshi Sano <[EMAIL PROTECTED]> writes:
> 4.0.1e has some updates on C&T driver, it does not use cfb now but uses fb.
>
> But I'm not sure if this new version can solve this problem, the change
> from 4.0.1d to 4.0.1e may be just irrelevant.
4.0.1e, as packaged in 4.0.1-2, works for me! It's
Taketoshi Sano <[EMAIL PROTECTED]> writes:
> 4.0.1e has some updates on C&T driver, it does not use cfb now but uses fb.
>
> But I'm not sure if this new version can solve this problem, the change
> from 4.0.1d to 4.0.1e may be just irrelevant.
4.0.1e, as packaged in 4.0.1-2, works for me! It'
Taketoshi Sano <[EMAIL PROTECTED]> writes:
> Maybe another C&T driver problem. Trying 4.0.1e, or rebuild with DEBUG
> defined of chips_drv.o and libvgahw.a from the source would be recommended
> in order to track the cause of this problem.
What is 4.0.1e? Does it have relevant fixes for C&T chip
Taketoshi Sano <[EMAIL PROTECTED]> writes:
> Maybe another C&T driver problem. Trying 4.0.1e, or rebuild with DEBUG
> defined of chips_drv.o and libvgahw.a from the source would be recommended
> in order to track the cause of this problem.
What is 4.0.1e? Does it have relevant fixes for C&T chi
Seth Arnold <[EMAIL PROTECTED]> writes:
> * Dan Christensen <[EMAIL PROTECTED]> [001107 09:39]:
> > My machine also freezes completely when I try the new X. I have the
> > same card, the CT6, in my Transmonde laptop, and the machine dies
> > when I run
Seth Arnold <[EMAIL PROTECTED]> writes:
> * Dan Christensen <[EMAIL PROTECTED]> [001107 09:39]:
> > My machine also freezes completely when I try the new X. I have the
> > same card, the CT6, in my Transmonde laptop, and the machine dies
> > when I run
> Just now, i am in large struggle with my notebook. I did an ordinary update
> within woody and discovered X4 in it . Wow! But:
>
> I have a chips&technologies 6 , that usually was covered by the
> XF_SVGA-Driver. Now, since 3.3.6-12 support has been vanished. oops.
>
> OK, i wanted to test
> Just now, i am in large struggle with my notebook. I did an ordinary update
> within woody and discovered X4 in it . Wow! But:
>
> I have a chips&technologies 6 , that usually was covered by the
> XF_SVGA-Driver. Now, since 3.3.6-12 support has been vanished. oops.
>
> OK, i wanted to test
28 matches
Mail list logo
