> "Colin" == Colin Watson <[EMAIL PROTECTED]> writes:
Colin> Depends how you did the upgrade - did you use 'apt-get
Colin> upgrade' (which probably won't be suitable), 'apt-get
Colin> dist-upgrade' (which should work), or something else like
Colin> dselect or aptitude?
Colin> All of
> "Cameron" == Cameron Matheson <[EMAIL PROTECTED]> writes:
Cameron> On Thursday 23 January 2003 04:45 am, Nicos Gollan wrote:
>> On Wednesday 22 January 2003 23:32, [EMAIL PROTECTED] wrote: > *
>> kernel 2.4.19 has got tdfx compiled in
>>
>> This might actually be the problem. Remo
On Thursday 23 January 2003 04:45 am, Nicos Gollan wrote:
> On Wednesday 22 January 2003 23:32, [EMAIL PROTECTED] wrote:
> > * kernel 2.4.19 has got tdfx compiled in
>
> This might actually be the problem. Remove the kernel builtin tdfx support
> and use the module from drm-trunk-module-src. The DR
> "Colin" == Colin Watson <[EMAIL PROTECTED]> writes:
Colin> X 4.2 changed the direct rendering architecture somewhat, and
Colin> requires an upgrade to kernel 2.4.20.
Well I found one minor glitch.
The upgrade to testing left xserver-xfree86 at 4.1.0 instead of
upgrading it to 4.2.1 al
On Thu, Jan 23, 2003 at 09:50:09AM -0800, [EMAIL PROTECTED] wrote:
> > "Colin" == Colin Watson <[EMAIL PROTECTED]> writes:
> Colin> X 4.2 changed the direct rendering architecture somewhat, and
> Colin> requires an upgrade to kernel 2.4.20.
[Please just reply to the list, not to me as well
> "Cameron" == Cameron Matheson <[EMAIL PROTECTED]> writes:
Cameron> Hi, try removing libglide2 (i think that it actually was
Cameron> detrimental to me in the past--i'm not using a voodoo right
Cameron> now tho, so i can't check my settings). also, have you
Cameron> checked your XF86
On Wednesday 22 January 2003 23:32, [EMAIL PROTECTED] wrote:
> I've got a voodoo3 using X DRI which _was_ working just fine
> until I "upgraded" to testing.
>
> Now it's broke.
>
> Things I _know _ are OK (after all - it _was_ working):
>
> * kernel 2.4.19 has got tdfx compiled in
This might actua
On Wed, Jan 22, 2003 at 07:38:00PM -0800, [EMAIL PROTECTED] wrote:
> Ok - I'll give it a try.
>
> Thanks for the info.
>
> Incidentally how are the mere mortals supposed to know this ?
>
> I spent a lot of time at the dri site and didn't see this mentioned
> anywhere.
No idea. I don't remember
Hi,
try removing libglide2 (i think that it actually was detrimental to me in the
past--i'm not using a voodoo right now tho, so i can't check my settings).
also, have you checked your XF86Config-4 to make sure that it hasn't been
overriden?
Cam
On Wednesday 22 January 2003 03:32 pm, [EMAIL
name of display: :0.0
display: :0 screen: 0
direct rendering: No
*sigh*
Linux soggy 2.4.20 #1 Wed Jan 22 20:04:49 PST 2003 i686 unknown
Any other ideas ?
Brian
> "Colin" == Colin Watson <[EMAIL PROTECTED]> writes:
Colin> On Wed, Jan 22, 2003 at 02:32:57PM -0800, [EMAIL PROTECTED]
Col
Ok - I'll give it a try.
Thanks for the info.
Incidentally how are the mere mortals supposed to know this ?
I spent a lot of time at the dri site and didn't see this mentioned anywhere.
Brian
> "Colin" == Colin Watson <[EMAIL PROTECTED]> writes:
Colin> On Wed, Jan 22, 2003 at 02:32:57P
On Wed, Jan 22, 2003 at 02:32:57PM -0800, [EMAIL PROTECTED] wrote:
> I've got a voodoo3 using X DRI which _was_ working just fine
> until I "upgraded" to testing.
>
> Now it's broke.
>
> Everything I know to check is OK, but when I do glxinfo, dri is NOT
> active.
>
> ~ $ glxinfo
> name
I've got a voodoo3 using X DRI which _was_ working just fine
until I "upgraded" to testing.
Now it's broke.
Everything I know to check is OK, but when I do glxinfo, dri is NOT
active.
~ $ glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: No
13 matches
Mail list logo