[XFree86] xkb frustration

2003-07-08 Thread Noah L. Meyerhans
I don't think I've ever managed to make xkb work right...

Right now, I'm trying to configure X to recognize my Microsoft Natural
Pro keyboard.  So:
Option XkbRules xfree86
Option XkbModel microsoftpro
Option XkbLayout us

But, XFree86.0.log contains:
Couldn't load XKB keymap, falling back to pre-XKB keymap

So, try setxkbmap on the commandline:
locutus:~$ setxkbmap -v 10 -rules xfree86 -model microsoftpro -layout us -option 
Setting verbose level to 10
locale is C
Warning! Multiple definitions of rules file
 Using command line, ignoring X server
Warning! Multiple definitions of keyboard model
 Using command line, ignoring X server
Warning! Multiple definitions of keyboard layout
 Using command line, ignoring X server
Applied rules from xfree86:
model:  microsoftpro
layout: us
Trying to build keymap using the following components:
keycodes:   xfree86
types:  complete
compat: complete
symbols:pc/pc(pc105)+pc/us
geometry:   microsoft(natural)
Error loading new keyboard description

So that's the most verbose description of the problem I can come up
with.  That's really not a lot of help.  Can anybody point me in the
right direction?  More descriptive error messages really would be
helpful here.  What's causing the setxkbmap warnings?  Is it because the
relevant files are being found multiple times?  Is there a path that is
searched for these files, or what?  And what is the actual error that's
preventing the keyboard description from being loaded?

Thanks.
noah



pgp0.pgp
Description: PGP signature


[Xpert]3d accelleration support

2002-12-02 Thread Noah L. Meyerhans
I'll admit that I don't pay super close attention, but it seems to me
that there's a growing trend among the top 3d chipset makers to provide
their own proprietary accellerated drivers for XFree86.  ATI and NVidia
are the two examples I can think of, and it seems like they're the best
3d chipset makers.

I'm still using an older 3dfx Voodoo3 because I know that the full
programming specs are available and I can get open source accellerated
drivers for it.  If I were to replace this card with another 3d card,
what would be a safe chipset to select if I want to stick with
open source drivers?

Thanks.
noah

-- 
 ___
| Web: http://web.morgul.net/~frodo/
| PGP Public Key: http://web.morgul.net/~frodo/mail.html 



msg11301/pgp0.pgp
Description: PGP signature


[Xpert]CVS nv driver + PowerPC Linux

2002-12-01 Thread Noah L. Meyerhans
Hi folks.  I'm using X built from the CVS HEAD branch on a Mac cube with
an Nvidia GeForce 2.  I had been using the same build of the X server
and modules for a couple of months, but replaced it last week after
hearing that the initialization bug that made it impossible to start X
twice had been fixed.  Now, however, I am not able to start X at all.
Here is all the output I get when starting the server:

XFree86 Version 4.2.99.2 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 25 November 2002
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems.  (See http://www.XFree86.Org/)
Build Operating System: Linux 2.4.19 ppc [ELF] 
Module Loader present
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: Sun Dec  1 14:53:27 2002
(==) Using config file: /etc/X11/XF86Config-4

After this, the monitor seems to no longer be receiving a video signal,
or perhaps the signal is way out of range or something.  When I attach
to the running XFree86 process in gdb, I see the same symptoms I saw
when the server had the video card initialization problem.  The
execution pointer seem to have flown out way beyond the stack
boundaries, and stack itself just seems gone:
(gdb) bt
#0  0x1074b6bc in ?? ()

So this looks an awful lot like the misfeature that was corrected in
early november, except now it's happening the first time the X server
tries to initialize the video hardware, rather than the second.  Any
help would be much appreciated at this point.  I can provide more
information if you need it.

Thanks!
noah

-- 
 ___
| Web: http://web.morgul.net/~frodo/
| PGP Public Key: http://web.morgul.net/~frodo/mail.html 



msg11276/pgp0.pgp
Description: PGP signature


Re: [Xpert]Geforce2 on PowerPC

2002-07-28 Thread Noah L. Meyerhans

On Sat, Jul 27, 2002 at 09:37:45PM -0700, Mark Vojkovich wrote:
 
Option XaaNoScanlineCPUToScreenColorExpandFill
 
It's most likely happening when text rendering gets clipped
 in a certain way.

Hey, that seems to work!  Excellent!  Thanks!

noah

-- 
 ___
| Web: http://web.morgul.net/~frodo/
| PGP Public Key: http://web.morgul.net/~frodo/mail.html 
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]Geforce2 on PowerPC

2002-07-28 Thread Noah L. Meyerhans

OK, I seem to have another problem with this system.  X now starts and
runs just fine.  I've seen no problems with it.  However, if I exit the
X server, any subsequent attempts to run startx result in a dead
display.  The monitor loses signal.  The system is still running, and
I've been able to log in and reboot the system, but nothing seems to be
able to recover the display.  This happens regardless of the color depth
or resolution.

I've attached the contents of /var/log/XFree86.log for both the first
try, in which everything works OK, and the second try, in which things
fail.  Aside from the fact that the logs might give some idea of where
the problem occurs, the actual contents aren't that different.  The case
where the display dies has a lot less info logged, as maybe the X server
has gone in to some strange state where it's not able to drive the
display or log anything.

Any help here would again be much appreciated!  Thanks

noah

-- 
 ___
| Web: http://web.morgul.net/~frodo/
| PGP Public Key: http://web.morgul.net/~frodo/mail.html 



This is a pre-release version of XFree86, and is not supported in any
way.  Bugs may be reported to [EMAIL PROTECTED] and patches submitted
to [EMAIL PROTECTED]  Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
(http://www.XFree86.Org/cvs)

XFree86 Version 4.2.99.1 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 7 June 2002
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems.  (See http://www.XFree86.Org/)
Build Operating System: Linux 2.4.18-newpmac ppc [ELF] 
Module Loader present
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: Sun Jul 28 18:43:10 2002
(==) Using config file: /etc/X11/XF86Config-4
(==) ServerLayout Default Layout
(**) |--Screen Default Screen (0)
(**) |   |--Monitor sony
(**) |   |--Device cube display
(**) |--Input Device Generic Keyboard
(**) Option XkbRules xfree86
(**) XKB: rules: xfree86
(**) Option XkbModel macintosh
(**) XKB: model: macintosh
(**) Option XkbLayout us
(**) XKB: layout: us
(==) Keyboard: CustomKeycode disabled
(**) |--Input Device Configured Mouse
(**) FontPath set to 
unix/:7100,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/cyrillic,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi
(==) RgbPath set to /usr/X11R6/lib/X11/rgb
(==) ModulePath set to /usr/X11R6/lib/modules
(--) using VT number 7

(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) Module ABI versions:
XFree86 ANSI C Emulation: 0.1
XFree86 Video Driver: 0.6
XFree86 XInput driver : 0.3
XFree86 Server Extension : 0.1
XFree86 Font Renderer : 0.3
(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.2.99.1, module version = 1.0.0
Module class: XFree86 Font Renderer
ABI class: XFree86 Font Renderer, version 0.3
(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.2.99.1, module version = 1.0.0
ABI class: XFree86 Video Driver, version 0.6
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:0b:0: chip 106b,0020 card , rev 00 class 06,00,00 hdr 00
(II) PCI: 00:10:0: chip 10de,0110 card 0208,a5b8 rev a1 class 03,00,00 hdr 00
(II) PCI: 01:0b:0: chip 106b,001f card , rev 00 class 06,00,00 hdr 00
(II) PCI: 01:17:0: chip 106b,0022 card , rev 03 class ff,00,00 hdr 00
(II) PCI: 01:18:0: chip 106b,0019 card , rev 00 class 0c,03,10 hdr 00
(II) PCI: 01:19:0: chip 106b,0019 card , rev 00 class 0c,03,10 hdr 00
(II) PCI: 01:1a:0: chip 104c,8020 card , rev 00 class 0c,00,10 hdr 00
(II) PCI: 02:0b:0: chip 106b,001e card , rev 00 class 06,00,00 hdr 00
(II) PCI: 02:0f:0: chip 106b,0021 card , rev 01 class 02,00,00 hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:11:0), (-1,0,0), BCTRL: 0x08 (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) Host-to-PCI bridge:
(II) Bus 1: bridge is at (1:11:0), (-1,1,0), BCTRL: 0x08 (VGA_EN is set)
(II) Bus 1 I/O 

[Xpert]Geforce2 on PowerPC

2002-07-27 Thread Noah L. Meyerhans

I've got a Linux powerpc system (Mac G4 cube running Debian 3.0) with a
GeForce2 card in it, which is mostly working with X but is having
problems.

It's running a locally built version of X from CVS, and it starts and
runs just fine.  It is fast and very solid feeling.  However, after a
bit of use the display becomes unresponsive.  The mouse pointer is still
perfectly responsive, but no windows update and none are able to receive
input.  Exactly how long it takes for this to happen seems like it may
be related to the display resolution and/or color depth, but it is
usually less than 30 minutes.  There are no warning signs before it
happens.  Once the display is locked like this, it is impossible to
regain control of it without rebooting.  I can't switch to another
virtual console, nor can I kill the X server with Ctrl+Alt+BS.  Nothing
at all abnormal is output on stdout or stderr by the X server.

I have tried different sets of clients, but this behavior doesn't seem
tied to a particular one.  Does anybody have any suggestions about what
to do?  Any help would be much appreciated.

Thanks.
noah

-- 
 ___
| Web: http://web.morgul.net/~frodo/
| PGP Public Key: http://web.morgul.net/~frodo/mail.html 



msg08047/pgp0.pgp
Description: PGP signature