[XFree86] Want to lose up to 19% weight. Try Adipren!

2004-09-21 Thread Alec G. Ramirez
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


Re: [XFree86] x server

2004-09-21 Thread Lemmit Kaplinski
Have you tried CTRL-ALT-F1?

L.

On Tue, 2004-09-21 at 18:25 -0700, desert whomper wrote:
> can u please tell me how to kill or exit x server on mandrake 10 so i
> can install my nvidia drivers? i really need help and have tried alot
> and have found no help
> ___
> XFree86 mailing list
> [EMAIL PROTECTED]
> http://XFree86.Org/mailman/listinfo/xfree86

___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] My testimonial about skuper viakgra

2004-09-21 Thread Cecil N. Charles
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] Pharma

2004-09-21 Thread Jimmie Posey
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] Screen Noise

2004-09-21 Thread davidjpenton
Is it normal for X to generate a lot of visual noise on the screen when, 
e.g., you drag a vertical scroll bar?  My system shows tons of "sparks" 
to the right of a window if you drag a scroll bar, and in some other cases.

- Dave -
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


Re: [XFree86] "AllowMouseOpenFail" does not work?

2004-09-21 Thread David Sun
Hi, Vivek
One more question:
is it ordinary that the whole system hangs when XFree86 waiting for a
configure mouse to be present?
thanks so much
David
å 2004-09-21 ä ç 18:32ï Vivek Dasmohapatra åéï
> On Tue, Sep 21, 2004 at 06:19:57PM +0800, David Sun wrote:
> 
> > Could any body tell me what's possibly the reason of the
> > "AllowMouseOpenFail" failure?
> 
> What is happening here (I am informed) is that X is waiting to see
> some mouse input before noticing the keyboard. It's really annoying,
> but recent X seems to suffer from this.
> 
> When I last checked (which was admittedly a long time ago) 
> allowmouseopenfail was necessary top allow X to start _at all_ 
> if it couldn't open the configured mouse device.
> ___
> XFree86 mailing list
> [EMAIL PROTECTED]
> http://XFree86.Org/mailman/listinfo/xfree86
> 

___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


Re: [XFree86] Report of XFree86 4.4.99.7 on NEC PC98

2004-09-21 Thread David Dawes
On Wed, Sep 22, 2004 at 04:12:04AM +0900, Satoshi Kimura wrote:
>XFree86 Bug/Test Report Form
>
>Please fill in as many of the fields a possible, and return this form to
>[EMAIL PROTECTED]  Replace the comments in [] with your own text.
>
>VERSION:
>
>XF86_VERSION 4.4.99.7
>
>VIDEO DRIVER:
>
>all drivers for NEC PC-98x1
>
>OPERATING SYSTEM:
>
>FreeBSD(98) 4.9
>
>VIDEO CARD:
>
>MODEL:
>
>all cards for NEC PC-98x1
>
>GRAPHICS CHIPSET:
>
>Matrox MGA 2064W etc.
>
>RAMDAC:
>
>
>CLOCKCHIP:
>
>
>VIDEO MEMORY:
>
>
>BUS TYPE:
>
>PCI
>
>REPORT:
>
>1. BUG
> I already sent patch for XFree86 4.4.0 and it was commited.
>In "changelog-4.4.99.7"
> 124. Don't do various keycode conversions on NEC PC-98 platforms
>  (Satoshi Kimura).
>
>But I find that modified source on 4.4.99.7 do not accord with
>patch which I sent. The difference is as folllows.
>These translation of scanCode are to be skipped on PC-98.

I've corrected this now.  Thanks for the followup.

David
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] x server

2004-09-21 Thread desert whomper
can u please tell me how to kill or exit x server on mandrake 10 so i
can install my nvidia drivers? i really need help and have tried alot
and have found no help
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


Re: [XFree86] Monitor/Driver Problem

2004-09-21 Thread Thomas Winischhofer
[EMAIL PROTECTED] wrote:
I’ve seen Windows pretty recently so I strongly believe there isn’t
such a way (actually the main reason for starting this thread).
While new to this forum, I have to assume that beside the expected
hard-core Linux aficionados who wouldn’t touch Windows with a
ten-foot pole, one might encounter many disaffected Windows users and, with any luck, 
even recent, disgusted Windows defectors for whom the notion of not being able to fix 
the refresh rate of the Windows video driver was too much to bear and the last straw.
Any comments pro/con are warmly invited and details dismissing my above claim will be 
happily appreciated and followed.
And here he fires up vmware...
In 2000, you need to open the display properties, select the right-most 
tab ("Settings"), click on "advanced", select "monitor" and select a 
different monitor than "generic" or "pnp", such as "legacy" or 
"standard". (I only have a swedish version of Windows 2000 running under 
vmware here, so the actual wording of the buttons/tabs may not be exact.)

In the area below, you can choose a fixed vertical refresh rate.

By a really strange coincidence, ever since I converted to 4.4 I’ve been fascinated by 
what I perceived to be the impossibility of fixing the video driver parameters in _Linux_.  
(that was before I discovered the subject problem with Windows).
Thomas, I sent you an E-mail to this effect at the time, probably lost in the cyber fog.  I 
never expected to be so fortunate to meet you here in this forum, so I’m now taking 
the liberty of reproducing in full, unedited, the letter (and the questions included therein, 
at the end) below, so you can comment.
The E-mail is dated Aug 25, 2004.

My appologies, but please understand that I am a developer, no call 
center. My impression was that you had either config problems or 
theoretical questions, both not specifically related to my driver. In 
such cases I take the liberty of not responding to each and every mail I 
get. That is exactly what the mailing lists are for.


Subject:  XF86Config Mode Questions
Dear Dr. Winischhofer,
First and foremost, many thanks for your excellent Linux SiS drivers.
I have an ASUS machine (P4S533-MX) with SiS651 as North Bridge. 
I worked with your 4.2 driver (on 2.6.7) and now I'm happily stable on 4.4 and 
2.6.8.1.
Also, your Linux/SiS/vga page is absolutely impressive!  Good to know there are 
still professionals around!
Everything is AOK; however, I'm a little confused about how XFree86 and your 
SiS driver handle the "modes" feature.
I'd very much appreciate if you can clear me up on a few questions below (at 
your leisure, of course - as I said, everything is just fine, SiS driver-wise).
--
In my '/etc/X11/XF86Config' file there are only two "modes" lines,
one a comment:
# Default "1024x768": 94.5 MHz (Dot Clock), 68.7 kHz (Horiz.), 85 Hz (refresh)
and the other one the "main" line:
ModeLine "1024x768" 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync

Then, in the Section "Screen", this I got this Subsection:
Subsection "Display"
Depth 24
Modes "1024x768"
ViewPort 0 0
EndSubsection
The '/var/log/XFree86.0.log' file has these related lines (excerpt):
XFree86 Version 4.4.0
Release Date: 29 February 2004
X Protocol Version 11, Revision 0, Release 6.6
...
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
...
(II) SIS(0): SiS driver (2004/08/20-1)
(II) SIS(0): Copyright (C) 2001-2004 Thomas Winischhofer> and others
(II) SIS(0): Compiled for XFree86 version 4.4.0.0
...
(II) SIS(0): Not using default mode "1024x768" (vrefresh out of range)
(II) SIS(0): Not using default mode "1024x768" (hsync out of range)
...
(--) SIS(0): Virtual size is 1024x768 (pitch 1024)
(**) SIS(0): *Mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz
(II) SIS(0): Modeline "1024x768" 94.50 1024 1072 1168 1376 768 769 772 808 
+hsync +vsync
(**) SIS(0): Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz
(II) SIS(0): Modeline "1024x768" 94.50 1024 1072 1168 1376 768 769 772 808 
+hsync +vsync
(**) SIS(0): Default mode "1024x768": 78.7 MHz, 60.0 kHz, 75.0 Hz
(II) SIS(0): Modeline "1024x768" 78.75 1024 1040 1136 1312 768 769 772 800 
+hsync +vsync
(**) SIS(0): Default mode "1024x768": 75.2 MHz, 56.6 kHz, 70.2 Hz
(II) SIS(0): Modeline "1024x768" 75.17 1024 1048 1184 1328 768 771 777 806 -
hsync -vsync
...
(**) SIS(0): Default mode "320x200": 12.5 MHz, 31.3 kHz, 70.9 Hz (D)
(II) SIS(0): Modeline "320x200" 12.53 320 328 376 400 200 206 207 221 
doublescan -hsync +vsync
(--) SIS(0): Display dimensions: (370, 280) mm
...
(II) SIS(0): Restoring by setting old mode 0x03

--
Questions:
1. My monitor (Hitachi CM715) display is perfect at 1024x768 @ 85 Hz, i.e. as 
"suggested" by my (only) Modeline. 'XF86Config' does 

[XFree86] Monitor/Driver Problem

2004-09-21 Thread alupu
Thomas,

Again, many thanks for your prompt help and invaluable insights.

Alex wrote (among other things):
>> I do not know a way to “switch off the monitor detection in
>> Windows and use a fixed rate there”.   I’d appreciate a pointer
>> from you here …

Thomas replies:
> Haven't been using Windows for ages, but I guess you'll find this
> in the Display properties somewhere.

I’ve seen Windows pretty recently so I strongly believe there isn’t
such a way (actually the main reason for starting this thread).
While new to this forum, I have to assume that beside the expected
hard-core Linux aficionados who wouldn’t touch Windows with a
ten-foot pole, one might encounter many disaffected Windows users and, with any luck, 
even recent, disgusted Windows defectors for whom the notion of not being able to fix 
the refresh rate of the Windows video driver was too much to bear and the last straw.
Any comments pro/con are warmly invited and details dismissing my above claim will be 
happily appreciated and followed.

By a really strange coincidence, ever since I converted to 4.4 I’ve been fascinated by 
what I perceived to be the impossibility of fixing the video driver parameters in 
_Linux_.  (that was before I discovered the subject problem with Windows).
Thomas, I sent you an E-mail to this effect at the time, probably lost in the cyber 
fog.  I never expected to be so fortunate to meet you here in this forum, so I’m now 
taking the liberty of reproducing in full, unedited, the letter (and the questions 
included therein, at the end) below, so you can comment.
The E-mail is dated Aug 25, 2004.

Subject:  XF86Config Mode Questions
Dear Dr. Winischhofer,

First and foremost, many thanks for your excellent Linux SiS drivers.
I have an ASUS machine (P4S533-MX) with SiS651 as North Bridge. 
I worked with your 4.2 driver (on 2.6.7) and now I'm happily stable on 4.4 and 
2.6.8.1.
Also, your Linux/SiS/vga page is absolutely impressive!  Good to know there are 
still professionals around!
Everything is AOK; however, I'm a little confused about how XFree86 and your 
SiS driver handle the "modes" feature.
I'd very much appreciate if you can clear me up on a few questions below (at 
your leisure, of course - as I said, everything is just fine, SiS driver-wise).
--
In my '/etc/X11/XF86Config' file there are only two "modes" lines,
one a comment:
# Default "1024x768": 94.5 MHz (Dot Clock), 68.7 kHz (Horiz.), 85 Hz (refresh)
and the other one the "main" line:
ModeLine "1024x768" 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync

Then, in the Section "Screen", this I got this Subsection:
Subsection "Display"
Depth 24
Modes "1024x768"
ViewPort 0 0
EndSubsection

The '/var/log/XFree86.0.log' file has these related lines (excerpt):

XFree86 Version 4.4.0
Release Date: 29 February 2004
X Protocol Version 11, Revision 0, Release 6.6
...
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
...
(II) SIS(0): SiS driver (2004/08/20-1)
(II) SIS(0): Copyright (C) 2001-2004 Thomas Winischhofer> and others
(II) SIS(0): Compiled for XFree86 version 4.4.0.0
...
(II) SIS(0): Not using default mode "1024x768" (vrefresh out of range)
(II) SIS(0): Not using default mode "1024x768" (hsync out of range)
...
(--) SIS(0): Virtual size is 1024x768 (pitch 1024)
(**) SIS(0): *Mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz
(II) SIS(0): Modeline "1024x768" 94.50 1024 1072 1168 1376 768 769 772 808 
+hsync +vsync
(**) SIS(0): Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz
(II) SIS(0): Modeline "1024x768" 94.50 1024 1072 1168 1376 768 769 772 808 
+hsync +vsync
(**) SIS(0): Default mode "1024x768": 78.7 MHz, 60.0 kHz, 75.0 Hz
(II) SIS(0): Modeline "1024x768" 78.75 1024 1040 1136 1312 768 769 772 800 
+hsync +vsync
(**) SIS(0): Default mode "1024x768": 75.2 MHz, 56.6 kHz, 70.2 Hz
(II) SIS(0): Modeline "1024x768" 75.17 1024 1048 1184 1328 768 771 777 806 -
hsync -vsync
...
(**) SIS(0): Default mode "320x200": 12.5 MHz, 31.3 kHz, 70.9 Hz (D)
(II) SIS(0): Modeline "320x200" 12.53 320 328 376 400 200 206 207 221 
doublescan -hsync +vsync
(--) SIS(0): Display dimensions: (370, 280) mm
...
(II) SIS(0): Restoring by setting old mode 0x03

--
Questions:
1. My monitor (Hitachi CM715) display is perfect at 1024x768 @ 85 Hz, i.e. as 
"suggested" by my (only) Modeline. 'XF86Config' does not contain the other 
"Default mode" lines, contrary to what the log seems to indicate (by the ** 
marker)

2. I noticed in your 'XF86Config' examples that you no longer seem to favor the 
usage of Modelines. 
If the many "Not using default mode ... " log entries represent some sort of 
"probing" - with its expected delay of X's startup - shouldn't a Modeline like 
mine still be useful to force a direct, immediate setting 

Re: [XFree86] (no subject)

2004-09-21 Thread Lemmit Kaplinski
Hi,

> (II) I740: Driver for Intel i740 chipset: i740 (agp), i740 (pci)
[snip]
> (EE) No devices detected.


What graphics chipset are you using. X tries to use the i740 driver, but
it fails to detect any devices - this most probably means you are using
the wrong driver or an unsupported chipset.

L.

On Tue, 2004-09-21 at 14:44 -0500, Ambica P Padhy wrote:
> hi ,
> I am having trouble in the startx for linux i am sending the XFree86.0.log .
> Can you check hwat is wrong so that I can correct the same or i need some
> patch to install.
> thanks,
> apadhy

___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


Re: [XFree86] could not open default font 'fixed'

2004-09-21 Thread Lemmit Kaplinski
Hi,

trying to get two flies here

On Tue, 2004-09-21 at 11:38 -0700, Mattias Thorslund wrote:
> FontPath "/usr/local/share/fonts"
> FontPath "/usr/share/fonts"
> FontPath "/usr/X11R6/lib/X11/fonts"

and Anup Shah wrote:
>FontPath   "unix/:7100"

in the first case: most likely the fixed font is in a subdirectory
of /usr/X11R6/lib/fonts. Maybe 75dpi or 100dpi. Look at all the subdirs
(and if this fails, all other places where you have fonts installed) and
scan the contents of fonts.dir file. This file contains the font names,
sizes and other such information for the files in the relevant
directory. Somewhere you should find information about the font "fixed".
Just add that directory to the list (FontPath "/some/directory")

In the other case, X gets all of its fonts from a font server, which is
entirely different piece of software. It is most probably called xfs and
its config file should be somewhere in /etc/X11 -
maybe /etc/X11/xfs/xfs.conf or similar. The file syntax is a little bit
different, but the idea is the same - find the place on your hard disk,
where the fixed font actually is (/usr/lib/X11/fonts/misc/ in teh case
of Debian) and add that directory to the list.

Hope this helps,

L.



___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] Losing resources on Geode processor.

2004-09-21 Thread Benstead, Kevin
We are using XFree 4.4.0 on a system with a 300MHz Geode GX1 processor and
the CS5530A companion chip.

We have written a small application using Borland's Kylix which draws five
bar charts which are updated every second.  The program runs fine BUT its
using 70% of CPU time to keep the display updated.  (The numbers fed to the
charts are generated by the program,  there is no external factor
influencing the generation of these numbers).

If we run the same program (re-compiled) on the same hardware running
Micro$oft Windoze 98 the program uses about 10% CPU time.

The LINUX version of the program running on a 400MHz EDEN processor with a
Savage graphics chip takes less than 1% of CPU time.

Is it just that the geode driver is not very good or is there some other
problem.  If windoze drivers can draw the charts quick enough why cant the
xfree drivers do the same thing.


Kevin
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] (no subject)

2004-09-21 Thread Ambica P Padhy
hi ,
I am having trouble in the startx for linux i am sending the XFree86.0.log .
Can you check hwat is wrong so that I can correct the same or i need some
patch to install.
thanks,
apadhy


XFree86.0.log
Description: Binary data


[XFree86] Report of XFree86 4.4.99.7 on NEC PC98

2004-09-21 Thread Satoshi Kimura
XFree86 Bug/Test Report Form
(B
(BPlease fill in as many of the fields a possible, and return this form to
(B[EMAIL PROTECTED]  Replace the comments in [] with your own text.
(B
(BVERSION:
(B
(BXF86_VERSION 4.4.99.7
(B
(BVIDEO DRIVER:
(B
(Ball drivers for NEC PC-98x1
(B
(BOPERATING SYSTEM:
(B
(BFreeBSD(98) 4.9
(B
(BVIDEO CARD:
(B
(BMODEL:
(B
(Ball cards for NEC PC-98x1
(B
(BGRAPHICS CHIPSET:
(B
(BMatrox MGA 2064W etc.
(B
(BRAMDAC:
(B
(B
(BCLOCKCHIP:
(B
(B
(BVIDEO MEMORY:
(B
(B
(BBUS TYPE:
(B
(BPCI
(B
(BREPORT:
(B
(B1. BUG
(B I already sent patch for XFree86 4.4.0 and it was commited.
(BIn "changelog-4.4.99.7"
(B 124. Don't do various keycode conversions on NEC PC-98 platforms
(B  (Satoshi Kimura).
(B
(BBut I find that modified source on 4.4.99.7 do not accord with
(Bpatch which I sent. The difference is as folllows.
(BThese translation of scanCode are to be skipped on PC-98.
(B
(B--- xc/programs/Xserver/hw/xfree86/common/xf86Events.c.orig Wed Sep 22 03:
(B25:33 2004
(B+++ xc/programs/Xserver/hw/xfree86/common/xf86Events.c  Wed Sep 22 03:25:59 20
(B04
(B@@ -655,7 +655,7 @@
(B* they need to get the same key code as the base key on the same
(B* physical keyboard key.
(B*/
(B-  if (xf86IsPc98()) {
(B+  if (!xf86IsPc98()) {
(B if (scanCode == KEY_SysReqest)
(B   scanCode = KEY_Print;
(B else if (scanCode == KEY_Break)
(B
(B2. patch
(B  Following patch is available to modify the error.
(BIt is the same as above lines.
(B
(Bbegin 644 patch.kbd
(BM+2TM('AC+W!R;V=R86US+UAS97)V97(O:'&9R964X-B]C;VUM;VXO>&8X
(BM-D5V96YT2!C;V1E
(BM(&%S('1H92!B87-E(&ME>2!O;B!T:&4@&8X-DES4&,Y."@I*2!["BL@
(BM(&EF("@A>&8X-DES4&,Y."@I*2!["B`@("`@:[EMAIL PROTECTED]'-C86Y#;V1E(#T]($M%
(BM65]3>7-297%Ehttp://XFree86.Org/mailman/listinfo/xfree86

Re: [XFree86] could not open default font 'fixed'

2004-09-21 Thread Mattias Thorslund
Lemmit Kaplinski wrote:
What is in the "Files" Section of your XF86Config (should
be /etc/X11/XF86Config-4)
L.
 

It says:
Section "Files"
   # Multiple FontPath entries are allowed (they are concatenated 
together)
   # By default, Mandrake 6.0 and later now use a font server 
independent of
   # the X server to render fonts.
   FontPath "/usr/local/share/fonts"
   FontPath "/usr/share/fonts"
   FontPath "/usr/X11R6/lib/X11/fonts"
EndSection

/Mattias
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


Re: [XFree86] could not open default font 'fixed'

2004-09-21 Thread Anup Shah
Hi,
Sorry to jump in but I have exactly the same problem
I have posted it earlier with a complete log and subject "xserver problem"
but did not get any answer so would appreciate your help.

I have in my "Files" section:

Section "Files"
RgbPath"/usr/X11R6/lib/X11/rgb"
FontPath   "unix/:7100"
EndSection

Please help!

Thanks, Anup
- Original Message - 
From: "Lemmit Kaplinski" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, September 21, 2004 11:23 AM
Subject: Re: [XFree86] could not open default font 'fixed'


> What is in the "Files" Section of your XF86Config (should
> be /etc/X11/XF86Config-4)
>
> L.
>
> On Tue, 2004-09-21 at 09:33 -0700, Mattias Thorslund wrote:
> > Hi good people,
> >
> > I messed up something in my fonts directories, and now I can't run KDE
> > anymore, not even the graphical login prompt works.  I'm on Mandrake
10.0.
> >
> > This is what I get:
> >
> > Fatal Server Error:
> > Could not open default font 'fixed'
> >
> > I have googled a bit but without finding something useful.
> >
> > What do I need to do to reinstall my fonts (if that's what I need to
do)??
> >
> >
> > /Mattias
> >
> > ___
> > XFree86 mailing list
> > [EMAIL PROTECTED]
> > http://XFree86.Org/mailman/listinfo/xfree86
>
> ___
> XFree86 mailing list
> [EMAIL PROTECTED]
> http://XFree86.Org/mailman/listinfo/xfree86
>

___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


Re: [XFree86] could not open default font 'fixed'

2004-09-21 Thread Lemmit Kaplinski
What is in the "Files" Section of your XF86Config (should
be /etc/X11/XF86Config-4)

L.

On Tue, 2004-09-21 at 09:33 -0700, Mattias Thorslund wrote:
> Hi good people,
> 
> I messed up something in my fonts directories, and now I can't run KDE 
> anymore, not even the graphical login prompt works.  I'm on Mandrake 10.0.
> 
> This is what I get:
> 
> Fatal Server Error:
> Could not open default font 'fixed'
> 
> I have googled a bit but without finding something useful.
> 
> What do I need to do to reinstall my fonts (if that's what I need to do)??
> 
> 
> /Mattias
> 
> ___
> XFree86 mailing list
> [EMAIL PROTECTED]
> http://XFree86.Org/mailman/listinfo/xfree86

___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] X terminal keyboard problem

2004-09-21 Thread Lemmit Kaplinski
Hi,

I helped a local school set up a Linux computer lab with X terminals.
Everything is working fine but for one thing: changing keyboard layouts
(I need ee and ru) does not work. In fact, even the keyboard layout
specified in the XF86Config file does not work (falls back to pre XKB
keymap).

The terminals mount / and /usr from a server. I have checked an double
checked, and /usr/X11R6/lib/xkb and related directories (in Debian they
are symlinked to /etc/X11) are visible in the terminal filesystem.

X is version 4.3 and the system is Debian unstable.

Here are some symptoms:

* (run from X client side) setxkbmap ee fails to load the new keymap
with an error along the lines of "Failed to load new keymap"
* (run from X client side) setxkbmap ee -print | xkbcomp -
192.168.0.222:0 however works
* (run from X client side) running setxkbmap -print produces this:
xkb_keymap {
xkb_keycodes  { include "xfree86+aliases(qwerty)"   };
xkb_types { include "complete"  };
xkb_compat{ include "complete"  };
xkb_symbols   { include "pc/pc(pc105)+pc/ee"};
xkb_geometry  { include "pc(pc105)" };
};
which is strange because it claims using an Estonian layout while in
fact it is not (fell back to US)
* running xkbcomp from the terminal (X server side) also works
* XKB extension is loaded (at least the log file says so)

I am very much out of ideas and would be very happy if someone could
offer something to try.

Thank you,

L.

___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] could not open default font 'fixed'

2004-09-21 Thread Mattias Thorslund
Hi good people,
I messed up something in my fonts directories, and now I can't run KDE 
anymore, not even the graphical login prompt works.  I'm on Mandrake 10.0.

This is what I get:
Fatal Server Error:
Could not open default font 'fixed'
I have googled a bit but without finding something useful.
What do I need to do to reinstall my fonts (if that's what I need to do)??
/Mattias
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] redhat 9.0 xserver crashed

2004-09-21 Thread vikram agrawal
Red hat 9 is installed on my computer .2 days agolinux crashed which is
led to some fatal error in starting xserver ..i m attaching the log file
along with this mail ..plz help
XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2)
Release Date: 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] 
Build Date: 27 February 2003
Build Host: porky.devel.redhat.com
 
	Before reporting problems, check http://www.XFree86.Org/
	to make sure that you have the latest version.
Module Loader present
OS Kernel: Linux version 2.4.20-8 ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:54:28 EST 2003 
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Tue Sep 21 17:46:10 2004
(==) Using config file: "/etc/X11/XF86Config"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "Videocard0"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "pc105"
(**) XKB: model: "pc105"
(**) Option "XkbLayout" "us"
(**) XKB: layout: "us"
(==) Keyboard: CustomKeycode disabled
(**) |-->Input Device "DevInputMice"
(**) FontPath set to "unix/:7100"
(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(==) ModulePath set to "/usr/X11R6/lib/modules"
(--) using VT number 7

(II) Open APM successful
(II) Module ABI versions:
	XFree86 ANSI C Emulation: 0.2
	XFree86 Video Driver: 0.6
	XFree86 XInput driver : 0.4
	XFree86 Server Extension : 0.2
	XFree86 Font Renderer : 0.4
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor="The XFree86 Project"
	compiled for 4.3.0, module version = 1.0.0
	Module class: XFree86 Font Renderer
	ABI class: XFree86 Font Renderer, version 0.4
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor="The XFree86 Project"
	compiled for 4.3.0, module version = 1.0.0
	ABI class: XFree86 Video Driver, version 0.6
(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x8058, mode1Res1 = 0x8000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,1130 card 1019,0a51 rev 04 class 06,00,00 hdr 00
(II) PCI: 00:02:0: chip 8086,1132 card 8086,1132 rev 04 class 03,00,00 hdr 00
(II) PCI: 00:1e:0: chip 8086,244e card , rev 11 class 06,04,00 hdr 01
(II) PCI: 00:1f:0: chip 8086,2440 card , rev 11 class 06,01,00 hdr 80
(II) PCI: 00:1f:1: chip 8086,244b card 1019,0a51 rev 11 class 01,01,80 hdr 00
(II) PCI: 00:1f:2: chip 8086,2442 card 1019,0a51 rev 11 class 0c,03,00 hdr 00
(II) PCI: 00:1f:3: chip 8086,2443 card 1019,0a51 rev 11 class 0c,05,00 hdr 00
(II) PCI: 00:1f:4: chip 8086,2444 card 1019,0a51 rev 11 class 0c,03,00 hdr 00
(II) PCI: 00:1f:5: chip 8086,2445 card 1019,0a51 rev 11 class 04,01,00 hdr 00
(II) PCI: 01:00:0: chip 10ec,8139 card 11f6,8139 rev 10 class 02,00,00 hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
	[0] -1	0	0x - 0x (0x1) IX[B]
(II) Bus 0 non-prefetchable memory range:
	[0] -1	0	0x - 0x (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
	[0] -1	0	0x - 0x (0x0) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x0006 (VGA_EN is cleared)
(II) Bus 1 I/O range:
	[0] -1	0	0xc000 - 0xc0ff (0x100) IX[B]
	[1] -1	0	0xc400 - 0xc4ff (0x100) IX[B]
	[2] -1	0	0xc800 - 0xc8ff (0x100) IX[B]
	[3] -1	0	0xcc00 - 0xccff (0x100) IX[B]
(II) Bus 1 non-prefetchable memory range:
	[0] -1	0	0xd400 - 0xd5ff (0x200) MX[B]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(--) PCI:*(0:2:0) Intel Corp. 82815 CGC [Chipset Graphics Controller] rev 4, Mem @ 0xd000/26, 0xd600/19
(II) Addressable bus resource ranges are
	[0] -1	0	0x - 0x (0x0) MX[B]
	[1] -1	0	0x - 0x (0x1) IX[B]
(II) OS-reported resource ranges:
	[0] -1	0	0xffe0 - 0x (0x20) MX[B](B)
	[1] -1	0	0x0010 - 0x3fff (0x3ff0) MX[B]E(B)
	[2] -1	0	0x000f - 0x000f (0x1) MX[B]
	[3] -1	0	0x000c - 0x000e (0x3) MX[B]
	[4] -1	0	0x - 0x0009 (0xa) MX[B]
	[5] -1	0	0x - 0x (0x1) IX[B]
	[6] -1	0	0x - 0x00ff (0x100) IX[B]
(II) Active PCI resource ranges:
	[0] -1	0	0xd500 - 0xd5ff (0x100) MX[B]
	[1] -1	0	0xd600 - 0xd607 (0x8) MX[B](B)
	[2] -1	0	0xd000 - 0xd3ff (0x400)

Re: [XFree86] "AllowMouseOpenFail" does not work?

2004-09-21 Thread david sun
Hi, Vivek
thanks for reply.
I am not sure if I understood your idea correctly. Do you mean having a mouse is a 
prerequisite to having a keyboard in starting X window? This can't be the situation of 
mine because the "AllowMouseOpenFail" option didnot work wether with or without a 
keyboard.

I guess I'd better provide more information of the system:
*XFree86 4.3.0 compiled from source code from official xfree86.org ftp
*glibc 2.2.5
*kernel 2.4.22

thanks
David
-- Original Message --
From: Vivek Dasmohapatra <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date:  Tue, 21 Sep 2004 11:32:18 +0100

>On Tue, Sep 21, 2004 at 06:19:57PM +0800, David Sun wrote:
>
>> Could any body tell me what's possibly the reason of the
>> "AllowMouseOpenFail" failure?
>
>What is happening here (I am informed) is that X is waiting to see
>some mouse input before noticing the keyboard. It's really annoying,
>but recent X seems to suffer from this.
>
>When I last checked (which was admittedly a long time ago) 
>allowmouseopenfail was necessary top allow X to start _at all_ 
>if it couldn't open the configured mouse device.
>___
>XFree86 mailing list
>[EMAIL PROTECTED]
>http://XFree86.Org/mailman/listinfo/xfree86
>
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] X crash on Presario 2539EA

2004-09-21 Thread Hesham Sokkar
Dear All

I have installed RedHat 9.0 into my Compaq Presario 2539EA, But X crashes. Appreciate 
if someone can help.


Regards
Hesham Sokkar
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] We sell regalis for an affordable price

2004-09-21 Thread Ramona Sims
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


Re: [XFree86] "AllowMouseOpenFail" does not work?

2004-09-21 Thread Vivek Dasmohapatra
On Tue, Sep 21, 2004 at 06:19:57PM +0800, David Sun wrote:

> Could any body tell me what's possibly the reason of the
> "AllowMouseOpenFail" failure?

What is happening here (I am informed) is that X is waiting to see
some mouse input before noticing the keyboard. It's really annoying,
but recent X seems to suffer from this.

When I last checked (which was admittedly a long time ago) 
allowmouseopenfail was necessary top allow X to start _at all_ 
if it couldn't open the configured mouse device.
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] "AllowMouseOpenFail" does not work?

2004-09-21 Thread David Sun
Hi, all
sorry to put a weird question (at least i think so) here:
question in a word: even with the "AllowMouseOpenFail" option, XFree86
can not successfully startup without keyboard/mouse

detailed question:
I'm working on a Linux-on-256M-CF-card with touch screen, X window works
fine. then I would like to use only the touch screen as input device, so
I add the "AllowMouseOpenFail" option in XF86Config file, then unplugged
my mouse, reboot the system,(without keyboard operation has been
successfully tried) but every time I try to startx, the system will
hang, keyboard hit unresponded, ping&telnet from other host unanswered.

Could any body tell me what's possibly the reason of the
"AllowMouseOpenFail" failure?

I have walked through XFree86.0.log, finding no explicit warning or
error complaining about absence of a mouse, so this log file isn't
attached. If anyone think it valuable, I can post it.

thanks in advance
David

___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


Re: [XFree86] Monitor/Driver Problem

2004-09-21 Thread Thomas Winischhofer
[EMAIL PROTECTED] wrote:
Thank you very much for your prompt comments and help.
For the record – The monitor is always fully shut off, whether
between a switch from Linux to Windows or just before a boot up on
Windows. This eliminates the possibility that the monitor (if OK)
might not present the proper DDC1 info to Windows.
As I mentioned, the only time the problem doesn’t show up is when I 
leave the monitor off until after Windows has been fully up (thus 
“simulating” the “switching off of monitor detection in Windows” the
hard way.) This raises a few new questions: 1.  Is it possible that
the Linux driver, once it gets (and maybe stores) the correct info
from the monitor on first install, it no longer cares what happens
afterwards, while Windows keeps inquiring the now wrong DDC1 data on
any boot up? 

The DDC spec says that as soon as a device is switched to DDC2, it has 
to stay in this mode until it is switched off. Since your monitor is 
off, I don't see a connection. (And no driver can switch it back to 
DDC1, nor "program" or "restore" anything.)

Besides, I have no clue about the Windows driver's internals, ie when 
and how often it queries the monitor for DDC data.

> In other words, is it possible that the monitor is now
defective (DDC1-wise) with Linux not noticing anything? 

No.

2.  I do not
know a way to “switch off the monitor detection in Windows and use a
fixed rate there”.  I’d appreciate a pointer from you here (even if
it might include messing up with system registry). 

Haven't been using Windows for ages, but I guess you'll find this in the 
Display properties somewhere.


3.  When you say
“But then again, this is SiS... you never know...”, I detect a
certain unhappiness with SiS651 on your part. Do you think my
spending some money on a video card (with a different chip, of
course) would fix this annoying problem for sure?

Sorry, no idea. (But it is certainly not the "chip's" problem, more a 
driver problem on the Windows side here.)

Thomas
Again, many thanks, -- Alex
___ XFree86 mailing list 
[EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86


--
Thomas Winischhofer
Vienna/Austria
thomas AT winischhofer DOT net *** http://www.winischhofer.net
twini AT xfree86 DOT org
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


Re: [XFree86] X problem with presario 2539EZ

2004-09-21 Thread Julien Boibessot
Hi !

if you want help, then you should provide your XF86Config file too !! ;-)

Julien

On Tuesday 21 September 2004 10:13, Hesham Sokkar wrote:
> Dear Support
>
> I have installed Linux ( Redhat 9.0 ) into my Compaq presario 2539EA
> Notebook. But there is a problem with X.
>
>
>
> Hope you can help.
>
> Regards
> Hesham SOkkar

___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] X problem with presario 2539EZ

2004-09-21 Thread Hesham Sokkar
Dear Support

I have installed Linux ( Redhat 9.0 ) into my Compaq presario 2539EA Notebook. But 
there is a problem with X.



Hope you can help.

Regards
Hesham SOkkar


XFree86.0.log
Description: Binary data