I've been having troubles with Xv output on my Radeon cards (a 7500 at
home and an M6 in my laptop). The color key wasn't working, so I cribbed
some code from Gatos to fix it. The Gatos code was a bit broken, working
for only depth 16 and depth 24 TrueColor visuals, but that was easy enough
On Fri, 29 Mar 2002, Keith Packard wrote:
I've been having troubles with Xv output on my Radeon cards (a 7500 at
home and an M6 in my laptop). The color key wasn't working, so I cribbed
some code from Gatos to fix it. The Gatos code was a bit broken, working
for only depth 16 and depth
On Fri, Mar 29, 2002 at 12:39:14AM -0800, Keith Packard wrote:
I've been having troubles with Xv output on my Radeon cards (a 7500 at
home and an M6 in my laptop). The color key wasn't working, so I cribbed
some code from Gatos to fix it. The Gatos code was a bit broken, working
for
On Fri, 29 Mar 2002, Kevin E Martin wrote:
Keith, I'm still working on merging in some of my Radeon changes, so I
handle checking it in. Also, I'd like to hear from others if this works
for their cards (i.e., Keith's second question above). I just saw Andrew
Aitchison's post (ATI Radeon VE
I am not the greatest typist and I keep inadvertently touching the thing
and moving the point. Then I find myself typing in unexpected places on
the screen.
I looked at some code, and tried commenting out the 4th button stuff in
the config file, but no joy.
TIA,
dlg
P.S. The new
DLG == David L Gehrt [EMAIL PROTECTED] writes:
DLG I looked at some code, and tried commenting out the 4th button
DLG stuff in the config file, but no joy.
You don't mention what OS you're running, but for Linux there's a
tpconfig utility. See URL:http://www.compass.com/synaptics/.
- J
On Fri, 29 Mar 2002, Auke Kok wrote:
Try to adjust the keyboard repeat rate settings with xset,
man xset shows you the syntax and xset -q will show the current
settings.
Problem now solved with
Option XkbDisabletrue
Thanks,
Jeff.
On Fri, 29 Mar 2002, Keith Packard wrote:
I've been having troubles with Xv output on my Radeon cards (a 7500 at
home and an M6 in my laptop). The color key wasn't working, so I cribbed
some code from Gatos to fix it. The Gatos code was a bit broken, working
for only depth 16 and depth
Most like some of kdm configuration files got overwritten. Try
reinstalling kdm.
Vladimir Dergachev
On Tue, 26 Mar 2002, Robert [ISO-8859-1] Wörle wrote:
Hi
my KDM is not starting anymore after i installed Xfree86 4.2.0
this happened on 3 machines !! now i use GDM as
Around 14 o'clock on Mar 29, Vladimir Dergachev wrote:
The Gatos code was a bit broken, working
for only depth 16 and depth 24 TrueColor visuals, but that was easy enough
to fix.
Keith, could you tell me what was broken in GATOS code ?
RADEONSetColorKey needs to convert a pixel value
Here is a description of and workaround for the system hangs triggered
by the Blaster and Starfish modules of xscreensaver (version 4.01)
under XFree86 acceleration for a Savage4-based AGP video card.
My system hangs instantly with Blaster. Otherwise, it hangs within
minutes if I run
I'm currently running an application whose developers stubbornly support
only 8-bit pseudocolor visuals. I have success to run the application
in 8 bpp mode, but am not happy with the color-flashing side effects. I
understand there's a way to run an Xserver in 24bpp depth with an 8bpp
overlay
Hello,
I had a problem a few months ago with a 4 screen machine and xinerama. A
few people on this list came through with the answer and I'm very
appreciative. The less is more approach worked well. Now I have a new
problem with a three screen machine.
The 4 screen machine that works is
On Fri, 29 Mar 2002, Auke Kok wrote:
Try to adjust the keyboard repeat rate settings with xset,
man xset shows you the syntax and xset -q will show the current
settings.
Some BIOSes also allow you to adjust kbd rates.
Tried that, but still not working well.
The keys were fine with X, but
I have this strange problem. If I run X in framebuffer mode my SBLive
works fine (driver compiled in). It's when I switch to my graphics
cards's native driver (have had the same problem with savage and sis)
that I no longer have sound.
As can be seen in the log file X detects sblive as a
Hello.
I'm sending this E-mail here because I seem to have increasing difficulty
with my graphic chip for each new realese of Xfree. I have a Toshiba
Satellite with a Trident Cyber 9525/DVD chipset. Back to Red Hat 7.0, which
still used XF86 3.3.6, I could use the Accel option with 24 bpp
[please cc me on replies, i am not subscribed]
hi all,
i have this shiny dell latitude c610 laptop sitting here, and it's
giving me a headache...
i am running X on it (debian woody, version 4.1.0-14,
xserver-xfree86). it has an unsupported radeon mobility card (drivers
only in 4.2.0), but it's
Hi,
I've managed to get a ps/2 keyboard (actually, sun, with adapter) and
a USB numeric keypad working under XF4.1.0 without too much difficulty.
But the numlock key on the keypad is always on. Pressing numlock on
either keyboard/pad just toggles the light on the ps/2 keyboard.
Any tips on
Hi.
I never got Xinerama working completely. First failure is mouse cursor on second
monitor:
-Executing simply 'X', cursor appears on first monitor but not on second.
-On KDE, cursor doesn't appear either on second monitor. Guessing its position, if I
drag it (left button) a big black square
Quoting David L. Gehrt [EMAIL PROTECTED]:
I am not the greatest typist and I keep inadvertently touching the thing
and moving the point. Then I find myself typing in unexpected places on
the screen.
I looked at some code, and tried commenting out the 4th button stuff in
the config
Hi all,
is it possible to write an xfree86 graphics driver that has similar functionality as
Xvfb? (i.e. doesn't care/require graphics hw on the machine). I'm playing with writing
a thin client (like vnc) that's transparent to X apps, and even though i could hack
Xvfb to do what i want, it
On Fri, 29 Mar 2002, Keith Packard wrote:
Around 14 o'clock on Mar 29, Vladimir Dergachev wrote:
The Gatos code was a bit broken, working
for only depth 16 and depth 24 TrueColor visuals, but that was easy enough
to fix.
Keith, could you tell me what was broken in GATOS code ?
On Fri, 29 Mar 2002, Keith Packard wrote:
Around 15 o'clock on Mar 29, Vladimir Dergachev wrote:
I was under impression that Radeon driver only uses 565 and 32bpp ARGB
framebuffer formats. I do not think it makes sense to support Xv with 8bpp
modes so I thought the code to be correct.
Around 10 o'clock on Mar 29, Kevin E Martin wrote:
Keith, I'm still working on merging in some of my Radeon changes, so I
handle checking it in.
Ok. I've also added code to set the default color key value and I need to
fix how it computes color key values so that non-TrueColor visuals work
On Fri, 29 Mar 2002, Keith Packard wrote:
Around 15 o'clock on Mar 29, Vladimir Dergachev wrote:
I was under impression that Radeon driver only uses 565 and 32bpp ARGB
framebuffer formats. I do not think it makes sense to support Xv with 8bpp
modes so I thought the code to be correct.
On Fri, 29 Mar 2002, Mark Vojkovich wrote:
On Fri, 29 Mar 2002, Keith Packard wrote:
Around 15 o'clock on Mar 29, Vladimir Dergachev wrote:
I was under impression that Radeon driver only uses 565 and 32bpp ARGB
framebuffer formats. I do not think it makes sense to support Xv with
Around 12 o'clock on Mar 29, Mark Vojkovich wrote:
The Rage 128 didn't work that way. It keyed off index values, not
the color they correspond to. If it keys off the post colormap lookup
value, this isn't very useful for video since there can be many identical
colors in the colormap
Around 12 o'clock on Mar 29, Mark Vojkovich wrote:
The Rage 128 didn't work that way. It keyed off index values, not
the color they correspond to. If it keys off the post colormap lookup
value, this isn't very useful for video since there can be many identical
colors in the colormap
Around 15 o'clock on Mar 29, Vladimir Dergachev wrote:
The reason is that we use colorkeying for clipping. 8bbp display has a
very large chance that this will break down and part of video will show
thru. Additionally, 8bpp is just plain bad for color intensive apps - you
will be ok if your
Around 15 o'clock on Mar 29, Dr Andrew C Aitchison wrote:
While you are at it, you might wish to change the default colo[u]rkey
from 0. Black is a common enough text colour; with Keith's patch
highlighted text shows the video layer beneath :-)
I stole a few lines from the R128 driver and
On Fri, 29 Mar 2002, Keith Packard wrote:
Around 15 o'clock on Mar 29, Dr Andrew C Aitchison wrote:
While you are at it, you might wish to change the default colo[u]rkey
from 0. Black is a common enough text colour; with Keith's patch
highlighted text shows the video layer beneath :-)
hi all,
i have this shiny dell latitude c610 laptop sitting here, and it's
giving me a headache...
i am running X on it (woody, version 4.1.0-14, xserver-xfree86). it
has an unsupported radeon mobility card (drivers only in 4.2.0), but
it's said to work with the vesa module for XFree86-4.1.0,
also sprach martin f krafft [EMAIL PROTECTED] [2002.03.29.1943 +0100]:
it seems that this will only happen when the machine is left idling,
because it has not yet happened to me whilst working locally on the
X desktop. then again, i haven't really spent a lot of time on that
machine other
On Fri, 29 Mar 2002, Vladimir Dergachev wrote:
While you are at it, you might wish to change the default colo[u]rkey
from 0. Black is a common enough text colour; with Keith's patch
highlighted text shows the video layer beneath :-)
I stole a few lines from the R128 driver and stuck
Sig 4 usually happens in one of two cases. 1) Trying to execute
non-executable code (like a bad function pointer might do). 2) A
broken compiler or building with incompatible options (like building
for a 686 architecture on a 586).
My guess is that this is a code generation issue. I
On Fri, 29 Mar 2002, Marc Aurele La France wrote:
While you are at it, you might wish to change the default colo[u]rkey
from 0. Black is a common enough text colour; with Keith's patch
highlighted text shows the video layer beneath :-)
I stole a few lines from the R128 driver and
On Fri, 29 Mar 2002, Keith Packard wrote:
Around 18 o'clock on Mar 29, Vladimir Dergachev wrote:
The video key is now configurable (option videokey 42) and
has a non-zero default value (30).
I just want to point out that GATOS code already supports this.
As for 8bbp - I will
On Fri, 29 Mar 2002, Marc Aurele La France wrote:
On Fri, 29 Mar 2002, Marc Aurele La France wrote:
While you are at it, you might wish to change the default colo[u]rkey
from 0. Black is a common enough text colour; with Keith's patch
highlighted text shows the video layer
could someone point me to a document or HOWTO, or maybe explain it
quickly, what i need to do to have an X session happen across two
physical screens -- you know, go off one screen with the mouse and
appear on the other screen (of another network-connected machine, this
is not dual-headed...)
The program x2x does just what you're looking for.
http://freshmeat.net/projects/x2x/?topic_id=861
This is available as a debian package in the debian distribution. Don't
know about other systems.
-Rob
On Fri, 2002-03-29 at 17:51, martin f krafft wrote:
could someone point me to a document
also sprach Rob Adams [EMAIL PROTECTED] [2002.03.30.0301 +0100]:
The program x2x does just what you're looking for.
http://freshmeat.net/projects/x2x/?topic_id=861
This is available as a debian package in the debian distribution. Don't
know about other systems.
wow, thanks for the rapid
Around 18 o'clock on Mar 29, Vladimir Dergachev wrote:
As for Radeon colorkeying the reason we use RGB values is because Radeon
no longer supports keying on the value of graphics pixel,
Well, I just experimentally determined that (at least on my M6 LY), this
is not true. For the component
Hey,
This is an error I get when
installing the fonts collection for X. I will also attach below the
information from the XFree86 log file and my basic system info. Thanx for
any help!
**(basic system
info)
Pentium III 600
portstree updated to
This will be the condensed version in HTML as it got held up :)
- Original Message -
From: Mike Richards
To: [EMAIL PROTECTED] ; [EMAIL PROTECTED]
Sent: Thursday, March 28, 2002 10:44 AM
Subject: XFree86 problem with fonts.
Hey,
This is an error I get when installing the fonts
On Friday 29 March 2002 09:22 pm, martin f krafft wrote:
also sprach Rob Adams [EMAIL PROTECTED] [2002.03.30.0301 +0100]:
The program x2x does just what you're looking for.
http://freshmeat.net/projects/x2x/?topic_id=861
This is available as a debian package in the debian distribution.
On Fri, 29 Mar 2002, Keith Packard wrote:
Around 18 o'clock on Mar 29, Vladimir Dergachev wrote:
As for Radeon colorkeying the reason we use RGB values is because Radeon
no longer supports keying on the value of graphics pixel,
Well, I just experimentally determined that (at least on
46 matches
Mail list logo
