date:20030716

Hi Mark,

OK, I build XFree86 from CVS (pulled this morning).  The build itself 
went cleanly, but I had several problems.

Also, I stopped using xfs, based on a recommendation from Andy Goth, 
just to take one more potential problem out of the situation.  I now 
explicitely use font paths, and I verified they work ok before I started 
installing the new version of XF86.

(The whole time I was using the config file that's attached to this email.)

So...

Problem 1:  When I first ran make install, there was some hp keyboard 
config thing that was a file, where the installer wanted it to be a 
directory.  I renamed that file from hp to hp.original, and then I 
could install cleanly.



Problem 2:  When I then rebooted, X came up, but not in a good way.  My 
background was a small black/white cross-hatch, and I had a very plain 
console in the top-left corner.  The mouse worked, but they keyboard 
didn't.  I couldn't even alt-shift-f1.

The log file produced from this is the email attachment named, 
XFree86.0.log-good-login-scree-but-no-login.



Problem 3: I thought that maybe I should now restore the contents of my 
/usr/X11R6 directory to what Mandrake 9.1 had given me (I'd backed it up 
before installing the new xf86 build.)  So I renamed /usr/X11R6, and put 
hte Mandrake-supplied version there instead.

Now I get further:  The nice Mandrake login screen comes up.  However, 
then I log in, the screen goes black briefly, and I get bounced right 
back to the login screen.

The log file associated with Problem 3 is the email attachment named, 
XFree86.0.log-good-login-scree-but-no-login

Question:  Are we participating in the process by which my kind of 
notebook screen and graphics chip become supported by the XFree86 
project, or is there usually some other mechanism?

Thanks for any help you care to give,
Christian
Mark Vojkovich wrote:
   I'm not sure what is the correct way to enable debug.
I usually copy xc/config/xf86site.def over to xc/config/host.def
and uncomment the DefaultGcc2i386Opt line and add -g to it:
#define DefaultGcc2i386Opt  -O2 -g -fno-strength-reduce

			Mark.

On Mon, 14 Jul 2003, Christian Convey wrote:


Hi Mark,

Yeah, I'm guessing the segfault had something to do with my general 
cluelessness about installing new builds of XFree86.

I did throw the coredump into gdb, but since the thing wasn't built in 
debug mode, there were no symbols for the backtrace.  I didn't think 
you'd have any use for it in that case.

If you'd like to tell me how to build it with debug symbols, I'm happy 
to repeat the experiment.

- Christian

Mark Vojkovich wrote:

  I'm not sure what's up with that.  I don't know any reason
why it would segfault.   I'm thinking that segfault probably
doesn't have anything to do with the driver.  Do you have a
core dump?  Do you know how to use gdb to get a backtrace
out of it?
  I'll see if I can get access to one of these.

			Mark.

On Mon, 14 Jul 2003, Christian Convey wrote:



Hi Mark.

I build from thee head of the CVS tree, and installed it over my 
Mandrake 9.1 stuff using make install after blowing away /usr/X11R6/*

The building and installation went OK, but when I rebooted (the only way 
I know of to restart X, cuz I'm a newbie), the server crashed.  (See 
attached log file.)

That makes me think I didn't really test your hypothesis, because I 
didn't actually get X to run.

Any suggestions?

I'm happy to continue working on this, but perhaps I should just suck up 
the problem until people have more experience with P25's?

Also, I'm willing to undergo some measure of pain with my laptop if you 
want, since you've been so helpful.  If you want, I can be your (or your 
delegate's) guinea pig for hammering out Toshiba P25 issues for a few weeks.

Thanks,
Christian
Mark Vojkovich wrote:


 I think the vesa driver is limited to the modes that are
in the bios.  Sounds like that mode is not in there, but I don't  
know much about the vesa driver.

 As for the nv driver not restoring the console correctly,
perhaps CVS works better.  I don't have access to one of those
laptops at the moment so I can't check it out.
			Mark.

On Sun, 13 Jul 2003, Christian Convey wrote:




Hey Mark,

As you suggested, I switched to using the vesa driver rather than the nv driver (simply by changing the Device--Driver entry).

The results: I no longer have that problem where the last line of my terminals runs off the end of the screen. The terminals look great.

However, X won't start.

I've attached the config and log files, in case you're willing to take a look.

I didn't quite understand why I got the error I got:

(II) VESA(0): Not using mode 1440x900 (no mode of this name)

because in my config file I do seem to have a Monitor--ModeLine defined with that name.

Thanks for any ideas you have.  I really appreciate it.

- Christian




Subject: Re: [XFree86] Odd problem with terminals
Date: Sun, 13 Jul 2003 11:55:15 -0700 (PDT)
From: Mark Vojkovich [EMAIL PROTECTED]
Reply-To:

Re: [XFree86] Overwriting Mandrake 9.1's XFree software

On Wednesday, July 16, 2003 5:51 am, Christian Convey wrote:
 Mark Vojkovich is working with me (on a thread in this list) to get
 through the issues, and he asked me to grab the newest code from CVS to
 see if that helps.

Guess I haven't been paying attention.

 No, I mean stack trace.  As in, I build XFree86 in debug mode, and when
 it crashes (actually producing a core dump), I use gdb to get a symbolic
 stack dump.

That's not good...  Now that you're on the latest CVS, it would probably be 
helpful if you shared the stack trace.  Include line numbers if you can, and 
be sure to give the date on which you downloaded the latest and/or greatest.

-- 
Andy Goth  |  [EMAIL PROTECTED]  |  http://ioioio.net/
Engineers love to change things.

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

Re: [XFree86] ati all inwonder please help

On Wednesday, July 16, 2003 2:37 am, rijovm wrote:
 Andy Goth [EMAIL PROTECTED] wrote:
   cannot find the display is the error when configure xconfig with my
   original settings.
  
  Your configuration and log file(s) look fine.  It sounds like you have a
  problem with your DISPLAY variable and/or your X authentication.
  
  Do you get error messages like xterm Xt error: Can't open display:?
  
  What do you type or do to get the error?

 When I install xconfig at the prompt(dos) textmodus

That's not DOS. :^)  MS-DOS is a different operating system altogether, and 
it's not really worth anyone's time except as a curiosity.

What's xconfig?  Is it a package that comes with your distribution?  What 
distribution would that be?  Red Hat, Slackware, Debian, etc. are GNU/Linux 
distributions.

By install do you mean start?

 and fill in everything
 correctly from my books that go with my monitor and my videocard.

Frequency ranges and such?

 then I get errors like that .

When exactly does the error come up?

 How can i make a screen dump in linux in the text mode do you no the
 right commands.

You can use script to track everything you type and everything that is 
displayed (in text).  When you're done making the script, type exit.  The 
result will be in a file called typescript.  Upload it somewhere or post it 
to the list if it is not too large.

 By the way what do they mean by virtual sreens.

A virtual screen, to X, is where you have a larger display area than your 
monitor can show at one time.  You use the mouse to scroll around by moving 
the pointer to the edges of the displayed area.  It's pretty annoying, so 
don't use it if you can avoid it.

You reminded me of something else that's probably worth mentioning: The Linux 
console lets you have multiple virtual consoles that you can flip through 
using Alt+F1, Alt+F2, Alt+F3, and so on.  When you start XFree86, it creates 
a new virtual console for its display (Alt+F7 with most distributions).  To 
temporarily switch back to text, use Ctrl+Alt+F1, F2, or whatever, and then 
use Alt+F7 or similar to get back to X.  Why Alt sometimes and Ctrl+Alt 
others?  When you're on a normal text screen, Linux is handling your 
keyboard, and Linux likes Alt+F__ to change virtual consoles (also Alt+Left 
and Alt+Right).  When you're in X, XFree86 handles your keyboard, and since 
Alt+F__ is commonly needed by applications and window managers, it uses 
Ctrl+Alt+F__ instead.  Ctrl+Alt+Backspace is another important key combo---it 
kills the X server.

 I tryed Xrandr but get error like cannot open display (null)

If your server isn't running (see startx or xdm), then there's nothing for X 
clients such as xrandr to connect to.  If your server is running, normally 
you're executing commands like xrandr from inside a menu or xterm already 
connected to X, and the DISPLAY variable is automatically inherited.

DISPLAY says what server to connect to.  X is actually a network server, but 
it's also suitable for single-computer use.

-- 
Andy Goth  |  [EMAIL PROTECTED]  |  http://ioioio.net/
Engineers love to change things.

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

Re: [XFree86] Odd problem with terminals

On Wednesday, July 16, 2003 10:05 am, Christian Convey wrote:
 Also, I stopped using xfs, based on a recommendation from Andy Goth,
 just to take one more potential problem out of the situation.  I now
 explicitely use font paths, and I verified they work ok before I started
 installing the new version of XF86.

We might want to come back and debug the xfs problem.

 Problem 2:  When I then rebooted, X came up, but not in a good way.  My
 background was a small black/white cross-hatch, and I had a very plain
 console in the top-left corner.  The mouse worked, but they keyboard
 didn't.  I couldn't even alt-shift-f1.

Alt+Shift+F1 probably did exactly what it was supposed to do, that is, 
nothing.  Try Alt+CTRL+F1. :^)

Run more programs, including a window manager, from the xterm (twm is great if 
you like ugly displays, heh).  Use xsetroot -solid steelblue for a prettier 
background.  Don't forget to start long-running programs backgrounded by 
putting a  at the end of the command line.  You can also put this stuff into 
an .xinitrc in your home directory or into /etc/X11/xinit/xinitrc (or even 
/usr/X11R6/bin/startx if you really want to).  It's been so long since I used 
xdm that I can't really help with it.

I'd read the logs and the rest of the email, but it's time for mass.  See you 
all later.

-- 
Andy Goth  |  [EMAIL PROTECTED]  |  http://ioioio.net/
Engineers love to change things.

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

Re: [XFree86] Matrox G550 Drivers And The Latest Version Of XFree86

2003-07-16 Thread John Lowell

Hi Andy,

Many thanks for your quick response.

You say:

Where are you downloading your XFree86 source code?  Your distribution may
be
 splitting up the XFree86 tar into many smaller chunks in an attempt to
 mitigate its size, and it could be that they forgot about mga.  I guess.

Its beginnng to look as though the problem here has a lot more to do with
something along these lines than anything else. With the distro I'm using,
downloading sources, compiling and installing XFree86 - and everything else
for that matter - is achieved with one command. You simply configure XFree86
the way you want it via menu, drivers most notably, enter the appropriate
command and voila! But here I'm selecting the mga driver and its not being
included for some reason. When I tried to use the drivers from Matrox and
found that they would not compile because they were incompatible with the
current version of XFree86, I mistakenly concluded that mga no longer came
as part of XFree86 source code. You've straightened me out on that one,
thank you. I've made inquiries with the distro's principal as to why my menu
selection of mga is being ignored. I'll let you know what I learn.

Very best regards.

John Lowell







- Original Message -
From: Andy Goth [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, July 16, 2003 3:25 AM
Subject: Re: [XFree86] Matrox G550 Drivers And The Latest Version Of XFree86


 On Wednesday, July 16, 2003 2:06 am, John Lowell wrote:
  When I did the installations, I configured XFree86 to include the
  mga display driver.

 How did you do *this* configuration?  I usually do it by editing
 xc/config/cf/xf86site.def .  Look for XF86CardDrivers.

  I configured via xf86config and everything seemed fine
  but exiting out of my window manager I get messages indicating that the
mga
  module can't be located.

 Please send us your /var/log/XFree86.0.log and your /etc/X11/XF86Config
files.
 I'm not sure how XFree86 would start if it couldn't find the driver it was
 configured to use, or how XFree86 would complain about being unable to
load a
 driver it isn't configured to use.

  A little checking revealed both that the driver
  wasn't included with the source code downloaded for XFree86 after all
and
  that further attempts to get it through the distro's resources would
come
  to naught.

 Where are you downloading your XFree86 source code?  Your distribution may
be
 splitting up the XFree86 tar into many smaller chunks in an attempt to
 mitigate its size, and it could be that they forgot about mga.  I guess.

 I recommend getting your source straight from the, uh, source. :^)  Bad
 Andy... heh.

  Drivers available from Matrox for this card won't compile since
  none were designed for the current version of XFree86. I would dearly
love
  to have a card specific driver for these boxes and am at sea regard the
  proper course to follow. Is source code for an mga driver that will work
  with the current version of XFree86 available? If so, where do I go to
get
  it?

 XFree86 comes with an mga driver.  It has been there for at least four
years.
 And yet CVS reports the latest change as being only four hours old.  I
guess
 that means it's actively developed. :^)

 Look in xc/programs/Xserver/hw/xfree86/drivers/mga/ .  Everything should
be
 there.

 By the way, the standard XFree86 distribution tarball unpacks into the
xc
 directory.  This is what I refer to above.

 --
 Andy Goth  |  [EMAIL PROTECTED]  |  http://ioioio.net/
 Engineers love to change things.

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


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

[XFree86] VESA modes for Toshiba P25 laptop (GeForce 5200 GO, 1440x900 lcd)

Andy Goth requested these, so here's a log file spewn out when using the 
 vesa driver on my P25.

- Christian

Andy Goth wrote:
On Tuesday, July 15, 2003 4:30 am, Christian Convey wrote:

What's the best way - just send you XFree86.0.log file resulting from a
vesa run of XF86?


That'll do.  I don't care if it's a crash or not.  I just want to see the mode 
list (plus the rest of the file, if it's convenient).


XFree86 Version 4.3.0
Release Date: 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.21-0.13mdksmp i686 [ELF] 
Build Date: 12 March 2003
Before reporting problems, check http://www.XFree86.Org/
to make sure that you have the latest version.
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: Wed Jul 16 11:22:06 2003
(==) Using config file: /etc/X11/XF86Config-4
(==) ServerLayout layout1
(**) |--Screen screen1 (0)
(**) |   |--Monitor monitor1
(**) |   |--Device device1
(**) |--Input Device Keyboard1
(WW) Option XkbCompat requires an string value
(**) Option XkbModel pc105
(**) XKB: model: pc105
(**) Option XkbLayout us
(**) XKB: layout: us
(WW) Option XkbOptions requires an string value
(==) Keyboard: CustomKeycode disabled
(**) |--Input Device Mouse1
(**) FontPath set to 
/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/mdk/,/usr/X11R6/lib/X11/fonts/100dpi/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/encodings/,/usr/X11R6/lib/X11/fonts/misc/
(==) RgbPath set to /usr/X11R6/lib/X11/rgb
(==) ModulePath set to /usr/X11R6/lib/modules
(**) Option AllowMouseOpenFail
Using vt 7
(--) 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 = 0x, mode1Res1 = 0x8000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,2570 card 1179,ff00 rev 02 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 8086,2571 card , rev 02 class 06,04,00 hdr 01
(II) PCI: 00:1d:0: chip 8086,24d2 card 1179,ff00 rev 02 class 0c,03,00 hdr 80
(II) PCI: 00:1d:1: chip 8086,24d4 card 1179,ff00 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1d:2: chip 8086,24d7 card 1179,ff00 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1d:3: chip 8086,24de card 1179,ff00 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1d:7: chip 8086,24dd card 1179,ff00 rev 02 class 0c,03,20 hdr 00
(II) PCI: 00:1e:0: chip 8086,244e card , rev c2 class 06,04,00 hdr 01
(II) PCI: 00:1f:0: chip 8086,24d0 card , rev 02 class 06,01,00 hdr 80
(II) PCI: 00:1f:1: chip 8086,24db card 1179,ff00 rev 02 class 01,01,8a hdr 00
(II) PCI: 00:1f:3: chip 8086,24d3 card 1179,ff00 rev 02 class 0c,05,00 hdr 00
(II) PCI: 00:1f:5: chip 8086,24d5 card 1179,ff00 rev 02 class 04,01,00 hdr 00
(II) PCI: 00:1f:6: chip 8086,24d6 card 1179,0001 rev 02 class 07,03,00 hdr 00
(II) PCI: 01:00:0: chip 10de,0324 card 1179,ff00 rev a1 class 03,00,00 hdr 00
(II) PCI: 02:00:0: chip 104c,8026 card 1179,ff00 rev 00 class 0c,00,10 hdr 00
(II) PCI: 02:01:0: chip 10ec,8139 card 1179,ff00 rev 10 class 02,00,00 hdr 00
(II) PCI: 02:02:0: chip 168c,0012 card 144f,7005 rev 01 class 02,00,00 hdr 00
(II) PCI: 02:04:0: chip 1179,0617 card 4000, rev 32 class 06,07,00 hdr 82
(II) PCI: 02:04:1: chip 1179,0617 card 4800, rev 32 class 06,07,00 hdr 82
(II) PCI: 02:06:0: chip 1179,0805 card 1179,ff00 rev 03 class 08,80,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,5), 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:1:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set)
(II) Bus 1 non-prefetchable memory range:
[0] -1  0   0xc100 - 0xc1ff

Re: [XFree86] Overwriting Mandrake 9.1's XFree software

Andy Goth wrote:
On Wednesday, July 16, 2003 5:51 am, Christian Convey wrote:

Mark Vojkovich is working with me (on a thread in this list) to get
through the issues, and he asked me to grab the newest code from CVS to
see if that helps.


Guess I haven't been paying attention.

OK, I'm cuting your pay for this help in half ;)


No, I mean stack trace.  As in, I build XFree86 in debug mode, and when
it crashes (actually producing a core dump), I use gdb to get a symbolic
stack dump.


That's not good...  Now that you're on the latest CVS, it would probably be 
helpful if you shared the stack trace.  Include line numbers if you can, and 
be sure to give the date on which you downloaded the latest and/or greatest.

Now that I downloaded it again this morning and am not using xfs, I 
don't crash (I followed your advice for going from xfs to simple 
directory lists.)

I guess the morals of the story are...

1. I'll try to give stack traces when this happens, and

2. Maybe what's in CVS right now can't handle unfound font servers?  (I 
also noticed that it was saying the socket # to look for the font server 
on is -1.  Could that be the cause of the problem?)

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

Re: [XFree86] Odd problem with terminals

Andy Goth wrote:
On Wednesday, July 16, 2003 10:05 am, Christian Convey wrote:

Also, I stopped using xfs, based on a recommendation from Andy Goth,
just to take one more potential problem out of the situation.  I now
explicitely use font paths, and I verified they work ok before I started
installing the new version of XF86.


We might want to come back and debug the xfs problem.
If you want to, I'm willing.



Problem 2:  When I then rebooted, X came up, but not in a good way.  My
background was a small black/white cross-hatch, and I had a very plain
console in the top-left corner.  The mouse worked, but they keyboard
didn't.  I couldn't even alt-shift-f1.


Alt+Shift+F1 probably did exactly what it was supposed to do, that is, 
nothing.  Try Alt+CTRL+F1. :^)
Sorry - pretend I said Alt+CTRL+F1, cuz that's what I actually tried. 
My bad.

Run more programs, including a window manager, from the xterm (twm is great if 
you like ugly displays, heh).  Use xsetroot -solid steelblue for a prettier 
background.  Don't forget to start long-running programs backgrounded by 
putting a  at the end of the command line.  You can also put this stuff into 
an .xinitrc in your home directory or into /etc/X11/xinit/xinitrc (or even 
/usr/X11R6/bin/startx if you really want to).  It's been so long since I used 
xdm that I can't really help with it.

I'd read the logs and the rest of the email, but it's time for mass.  See you 
all later.

Thanks for the tip, but how can I run something from the xterm when my 
keystrokes are totally ignored?

Thanks again for working through this with me.

- Christian

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

[XFree86] Help with Intel 845 video

2003-07-16 Thread Sal Valente

I'm using an IBM NetVista with a video controller that Windows claims is
Intel 82845G/GL/GE/PE/GV Graphics Controller.

I installed RedHat 9 with XFree86 4.3.0-2.  The RedHat installer claims
the video is Intel 845.

When I run X, the only mode it will use is 640x480.  How can I fix
this?  I'll attach my XF86Config and XFree86.0.log.

Thanks,
Sal


# XFree86 4 configuration created by redhat-config-xfree86

Section ServerLayout
Identifier Default Layout
Screen  0  Screen0 0 0
InputDeviceMouse0 CorePointer
InputDeviceKeyboard0 CoreKeyboard
InputDeviceDevInputMice AlwaysCore
EndSection

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

Section Module
Load  dbe
Load  extmod
Load  fbdevhw
Load  glx
Load  record
Load  freetype
Load  type1
EndSection

Section InputDevice
Identifier  Keyboard0
Driver  keyboard
Option  XkbRules xfree86
Option  XkbModel pc105
Option  XkbLayout us
EndSection

Section InputDevice
Identifier  Mouse0
Driver  mouse
Option  Protocol PS/2
Option  Device /dev/psaux
Option  ZAxisMapping 4 5
Option  Emulate3Buttons no
EndSection

Section InputDevice
Identifier  DevInputMice
Driver  mouse
Option  Protocol IMPS/2
Option  Device /dev/input/mice
Option  ZAxisMapping 4 5
Option  Emulate3Buttons no
EndSection

Section Monitor
Identifier   Monitor0
VendorName   Monitor Vendor
ModelNameE90fb
DisplaySize  360270
HorizSync30.0 - 86.0
VertRefresh  50.0 - 150.0
Option  dpms
EndSection

Section Device
Identifier  Videocard0
Driver  i810
VendorName  Videocard vendor
BoardName   Intel 845
EndSection

Section Screen
Identifier Screen0
Device Videocard0
MonitorMonitor0
DefaultDepth 16
SubSection Display
Depth 16
Modes1024x768 800x600 640x480
EndSubSection
EndSection

Section DRI
Group0
Mode 0666
EndSection


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: Wed Jul 16 11:29:26 2003
(==) 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 = 0x8000f800, mode1Res1 = 0x8000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,2560 card , rev 01 class 06,00,00 hdr 00
(II) PCI: 00:02:0: chip 8086,2562 card 1014,0267 rev 01 class 03,00,00 hdr 00
(II) PCI: 00:1d:0: chip 8086,24c2 card 1014,0267 rev 01 class 0c,03,00 hdr 80
(II) PCI: 00:1d:1: chip 8086,24c4 card 1014,0267

[XFree86] Completely OT: Reply-to munging on the list

2003-07-16 Thread Jay R. Ashworth

I'll reply to this, but I know David and others aren't interested, so, guys,
feel free to ignore it, 'k?

On Tue, Jul 15, 2003 at 11:36:29PM -0500, Andy Goth wrote:
 Since everybody has a different opinion, I think it would make sense to set up 
 the mail server so that people can choose whether or not they want Reply-To 
 fields tacked onto emails they receive.  This should make everybody (except 
 the admin, heh) happy.
 
 Then only remaining debate would be what should be the default.  Existing 
 users should be set to Reply-To mode until they tell the server otherwise.
 
 As for new users, the subscribe page should have a checkbox (by default 
 checked) enabling Reply-To fields.  If there is also an email-only way to 
 subscribe (I don't know), it should by default enable Reply-To, and the 
 subscription confirmation message should explain the issues and how to change 
 the Reply-To setting.
 
 Rationale: My observations indicate that it's mostly people with longtime 
 experience who complain about Reply-To, so these people should be capable of 
 follow simple instructions to change their account settings.

I'm not sure this will help, Andy: it's precisely those people who will
complain because of their knowledge who *don't* need it.  It's the *newbies*,
who've never been on a list before, and don't realize that they need to look,
who are the problem.

This is, I think, one of the very rare circumstances where it doesn't really
much matter if you supply the knob -- there is no good default.  The reason
for which, of course, is that one setting of the knob solves one problem, and
the other a related, but quite different problem.

argument category=inflammatory
It is, alas, much akin to the argument between the anti-abortion camp and the
pro-abortion camp.  Oh, I mean the pro-life camp and the anti-life camp.

You see the problem: one side is pro-abortion-*rights*, and the other side
is pro-life.  Two almost completely different topics, tied together by a
common base subject.  Same thing here.

Hitler!

Godwin!
/argument

 It doesn't matter much to me if someone actually implements this suggestion.  
 If it happens, I'll turn off Reply-To's for mails sent to me.  If it doesn't 
 happen, I won't complain.  It may be a little ugly, but I know how to use my 
 mua to send to the original poster despite Reply-To's setting, so long as 
 he/she didn't have to set Reply-To in the first place.

And your MUA likely has enough *control* to let you deal appropriately, which
ties into the won't help the pros argument above.

 Yeah, I know I said I wouldn't reply, but I think that maybe, just maybe, the 
 above might lead to a resolution nearly everybody can (grudgingly?) live 
 with.

Hmmm...


Cheers,
-- jra
-- 
Jay R. Ashworth[EMAIL PROTECTED]
Member of the Technical Staff Baylink RFC 2100
The Suncoast Freenet The Things I Think
Tampa Bay, Floridahttp://baylink.pitas.com +1 727 647 1274

   OS X: Because making Unix user-friendly was easier than debugging Windows
-- Simon Slavin, on a.f.c
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86

[XFree86] Excessive CPU Usage with 4.3.0

2003-07-16 Thread Wes Janzen

I upgraded to 4.3.0 using the SuSE package for SuSE 8.0...

I upgraded my video card to a radeon at the same time so I don't know if 
this problem is due to the DRI driver (which is working fine) or if it 
is a problem with X.

On my K6-2 400 system, CPU usage for X runs at 15-30% all the time.  If 
I switch to one of my virtual terminals, the CPU usage drops down again. 

Does anyone have any ideas how to tame the CPU usage of X?

Thanks,

Wes Janzen

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

[XFree86] Replacing Xsco with XFree86

2003-07-16 Thread Frank Tarczynski

I've finally been able to built the XFree86 server under unixware 7.1.3.

Does anyone have any experience with replacing the stock Xsco server under
unixware?

I've tried disabling Xsco (scologin disable) and then starting XFree86 but
scologin appears to delete the named pipes and other stuff in /dev/X and
/tmp/.X*.

I get these errors:


_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running

Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't
already running

When reporting a problem related to a server crash, please send
the full server output, not just the last messages.
This can be found in the log file /var/adm/XFree86.0.log.
Please report problems to [EMAIL PROTECTED]

Can anyone who replaced Xsco share any pointers?

Frank



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

[XFree86] Opteron, GinGin and PCIGart

2003-07-16 Thread Mark Lane

I am getting a weird error when attempting to run ForcePCIMode on an 
opteron with a Radeon 7500 PCI. I have also used a 7000 with the same results.

(EE) RADEON(0): GetBuffer timed out, resetting engine...
(EE) RADEON(0): RADEONCPGetBuffer: CP reset -1020
(EE) RADEON(0): RADEONCPGetBuffer: CP start -1020
(EE) RADEON(0): RADEONCPGetBuffer: CP GetBuffer -1020
(EE) RADEON(0): GetBuffer timed out, resetting engine...
(EE) RADEON(0): RADEONCPGetBuffer: CP reset -1020
(EE) RADEON(0): RADEONCPGetBuffer: CP start -1020
(EE) RADEON(0): RADEONCPGetBuffer: CP GetBuffer -1020
(EE) RADEON(0): GetBuffer timed out, resetting engine...
I am running the stock XFree86 which comes with GinGin.
--
Mark Lane, CET  mailto:[EMAIL PROTECTED]
Hard Data Ltd.  http://www.harddata.com
T: 01-780-456-9771  F: 01-780-456-9772
11060 - 166 Avenue Edmonton, AB, Canada, T5X 1Y3
-- Ask me about our Excellent 1U Systems! --
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86

Re: [XFree86] Odd problem with terminals

On Wed, 16 Jul 2003, Christian Convey wrote:

 Hi Mark,
 
 OK, I build XFree86 from CVS (pulled this morning).  The build itself 
 went cleanly, but I had several problems.
 
 Also, I stopped using xfs, based on a recommendation from Andy Goth, 
 just to take one more potential problem out of the situation.  I now 
 explicitely use font paths, and I verified they work ok before I started 
 installing the new version of XF86.
 
 (The whole time I was using the config file that's attached to this email.)
 
 So...
 
 Problem 1:  When I first ran make install, there was some hp keyboard 
 config thing that was a file, where the installer wanted it to be a 
 directory.  I renamed that file from hp to hp.original, and then I 
 could install cleanly.

   Yes, I've seen this to.  It tries replace a file with a directory
and it fails.  make install of any recent XFree86 will break unless
you remove the old file first.


 
 Problem 2:  When I then rebooted, X came up, but not in a good way.  My 
 background was a small black/white cross-hatch, and I had a very plain 
 console in the top-left corner.  The mouse worked, but they keyboard 
 didn't.  I couldn't even alt-shift-f1.
 
 The log file produced from this is the email attachment named, 
 XFree86.0.log-good-login-scree-but-no-login.
 
 
 
 Problem 3: I thought that maybe I should now restore the contents of my 
 /usr/X11R6 directory to what Mandrake 9.1 had given me (I'd backed it up 
 before installing the new xf86 build.)  So I renamed /usr/X11R6, and put 
 hte Mandrake-supplied version there instead.
 
 Now I get further:  The nice Mandrake login screen comes up.  However, 
 then I log in, the screen goes black briefly, and I get bounced right 
 back to the login screen.
 
 The log file associated with Problem 3 is the email attachment named, 
 XFree86.0.log-good-login-scree-but-no-login

   Are you running kdm or something like that?  Can you run
startx instead. 


 
 
 Question:  Are we participating in the process by which my kind of 
 notebook screen and graphics chip become supported by the XFree86 
 project, or is there usually some other mechanism?

   So far, what you are describing doesn't sound like anything
more than a configuration problem.  The server is not generating
any errors.   In the first case:

Couldn't load XKB keymap, falling back to pre-XKB keymap
(II) Server_Terminate keybinding not found

  The keymap is missing.  In the second case it sounds like
the server is running fine, you just can't login for some
reason.  Perhaps an authentication problem.  Not running a
graphic login will help narrow down the problem.


Mark.

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

[XFree86] Errors

2003-07-16 Thread Rob Deschaine

Hi
When I try to compile any software I get a error.
ERROR: /etc/x11 exists, but is not a symlink to /usr/x11r6/etc.
Then the install fails and cant install, any ideas
Rob 
[EMAIL PROTECTED]



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

[XFree86] New XFree86 binary vs. Compaq ABNT2 Keyboard

2003-07-16 Thread Pedro M. Rabinovitch

Hi,

  I was having problems with my Trident video card (the let's pretend the 
cursor is a couple of centimeters to the left and see what happens problem) 
and was directed to download the new trident_drv.o driver from ~alanh's. 
According to directions there, I also got the new XFree86 binary and the two 
pci libs.

The thing is I'm using a Compaq ABNT2 Keyboard (model br-abnt2, basic layout) 
and the new setup doesn't recognize the slash / question mark key. That seems 
pretty much the only key it doesn't react to. Of course, at vterms everything 
works as usual, and when I replace the old binaries things still work as 
expected. My XF86Config* files are ok and unscathed from the experiment as a 
whole.

Any thoughts?

Thanks in advance,

Pedro.
-- very anxious to have his hand-cursor coordination back

-- 
Pedro Miller Rabinovitch
[EMAIL PROTECTED]

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

Re: [XFree86] 4.3.0 binary installation probs

2003-07-16 Thread SAK

The first error  most of those following it look something like this:

Xinstall.sh: line 1050:  142 segmentation fault $TAR xvf $VERSTARBALL
$VERSIONFILE
Warning: can't detect the bindist version


Which makes me think it doesn't like my tar version (which is GNU tar
1.13).  However, I don't have any problems with tar elsewhere.  Hope
this is useful.

--- Christian Convey [EMAIL PROTECTED] wrote:
 Best bet is to tell us what the first error you see is.
 
 And is the first error during installation, or when you try to
 actually 
 run X?
 
 SAK wrote:
  Have been unable to install xf86-4.3.0 from binaries.  Have no
 history
  of same with 4.2 (this easily installs from binaries).  Must be
  something different or a new requirement.  All attempts yield a
  partially installed system with numerous errors.  Ideas???
  
  __
  Do you Yahoo!?
  SBC Yahoo! DSL - Now only $29.95 per month!
  http://sbc.yahoo.com
  ___
  XFree86 mailing list
  [EMAIL PROTECTED]
  http://XFree86.Org/mailman/listinfo/xfree86
  
 
 
 ___
 XFree86 mailing list
 [EMAIL PROTECTED]
 http://XFree86.Org/mailman/listinfo/xfree86


__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86

[XFree86] RE: Re: Application

2003-07-16 Thread MAILsweeper . cvis158

The Marconi Communications Mail Gateway has detected a mail message
with subject Re: Application
containing a virus. The original message has been quarantined for a week.
It has NOT been delivered to any recipients.

The message was sent from  [EMAIL PROTECTED]  to the following:
[EMAIL PROTECTED]


Please ensure that your system has been cleaned of viruses before sending again.

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

[XFree86] Campos do Jordão

2003-07-16 Thread Fabio

Campos do Jordão está lotada. Mas nós ainda temos lugares.
Recém construida, privacidade, conforto  e estilo de vida.
A melhor opção para famílias de bom gosto. Alugue para temporada.

Visite: http://www.casaemcampos.com  

Fabio
Dúvidas pelo email: [EMAIL PROTECTED]







Para ser removido de futuros correios, por favor, envie email para
[EMAIL PROTECTED], com o assunto REMOVER. Obrigado.


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

Re: [XFree86] Compliation problem under unixware

2003-07-16 Thread Frank Tarczynski

Marc Aurele La France wrote:

On Wed, 16 Jul 2003, Frank Tarczynski wrote:

 

Perhaps the problem occurs because 430HX_BRIDGE starts with a numeric?
Try changing it to BRIDGE_430HX.
 

 

No need to change it now.  I've already built the server by just deleting
the _ for those 2 #define's.
   

I'm afraid that's not good enough.  I need to know why your pre-processor
seems to be treating _ in tokens specially.  So far, it seems that it's
because the token starts with a numeric.  For portability reasons, I'd
really prefer to nail down if that's that's the case.
OK, I've checked what the unixware 7.1.3 cc does.  If the numeric 
portion is first: no good.  If the BRIDGE is first, as in BRIDGE_430HX: 
it works.

cc reports itself as Optimizing C Compilation System (CCS) 4.1 10/31/02 
(OU7.1.3bl11.1)

Frank

 

Do you have any experience with replacing Xsco?
   

Unfortunately I don't.  But it sounds to me that Xsco uses non-standard
means of determining whether or not another server is running.
Marc.

+--+---+
|  Marc Aurele La France   |  work:   1-780-492-9310   |
|  Computing and Network Services  |  fax:1-780-492-1729   |
|  352 General Services Building   |  email:  [EMAIL PROTECTED]  |
|  University of Alberta   +---+
|  Edmonton, Alberta   |   |
|  T6G 2H1 | Standard disclaimers apply|
|  CANADA  |   |
+--+---+
XFree86 Core Team member.  ATI driver and X server internals.
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
 



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

Re: [XFree86] Scroll Wheel doesn't work

2003-07-16 Thread JoeHill

On Wed, 16 Jul 2003 14:45:08 -0700
Peter Nehem [EMAIL PROTECTED] uttered:

 Hi all,
 I'm hoping this is the right place to post this message.
 I have a Logitech MX 700 wireless usb mouse. I have to move the mouse
 around a few seconds before it starts to respond (but I can live with
 this). Afterwords most of the buttons seem to work. It has 8 button.
 But I can't get the wheel to scroll up or down. Here is how the mouse
 looks in the XF86Config file:
 
 Section Input Device
   Identifier Mouse0
   Driver mouse
   Option Protocol auto
   Option Device /dev/usbmouse
   Option Buttons 10
   Option ZAxisMapping 9 10
   Option Resolution 800
 EndSection

Looks like the ZAxisMapping is wrong...should have all of the buttons
enumerated I believe.

There may be useful info for you about how that works here:

http://www.deadman.org/

 One other quick question: How do you change the Windows Manager root
 can use? Right now it is KDE, but I'd like to work with Gnome, but I
 can't find out where you change this at. Thanks!

You shouldn't be logging in to a graphical environment as root...but...

How do you boot, to a graphical login or text mode (ie. runlevel 3)?

If it's text mode, open a console, su root, and type cd to get to your
home dir. Now create a file called .xinitrc and add a line executing the
WM or desktop you want, ie. exec fluxbox, etc.

This is NOT recommended. You should really always log in as a user, then
perform only specific tasks as root when required.

-- 
 Joehill
 Registered Linux user #282046
 Homepage: http://nodex.sytes.net
 **
 Filtering out noise is one way to get a clearer signal.
 **
 20:22:46 up 27 min,  1 user,  load average: 0.00, 0.02, 0.00
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86

Re: [XFree86] Odd problem with terminals

Mark Vojkovich wrote:
On Wed, 16 Jul 2003, Christian Convey wrote:

IIRC, however, the main reason you had me pull a new version of XF86 from CVS was to see if it fixed the problem where on my virtual consoles, the last half of the last line is below the bottom of the screen. Unfortunately, I do still have that problem.

One detail I forgot to mention: Always (regardless of any playing around I've done), I have another problem: Mandrake 9.1 gives me what I think is a boot-loader menu during startup. The text inside that menu is absolutely garbled, but the rest of the graphics on that screen look normal. \

When I hit Enter and go to the screen that shows the startup log messages scrolling by, the text there, and from then on, looks perfectly normal. Could this be related to my virtual console problem?

It could be. I noticed that there didn't appear to be a 1440x900
mode supported by the bios. It's possible that the kernel framebuffer
stuff relies on that. I assume you are using a kernel framebuffer?
That would be rivafb either built as a kernel module or staticly
compiled into the kernel. If you wanted to you could try building
a kernel without kernel framebuffer support. That might help.
If you get the penguin image while the kernel boot messages are flowing
by, that means you've definitely got kernel framebuffer support.
Thanks. So does it work like the following?

During early boot up, the boot-loader software is responsible for
rendering text, such as in my boot-loader menu. It requires bios
support for those fonts, and I apparently don't have it.
Then, the kernel is responsible for rendering text. That controls the
rendering of the messages that flow by as the initiation scripts run.
This also relies on the BIOS support for rendering that text.
Finally, xf86 is responsible for rendering text, even on the virtual
consoles. At this point a deficiency in the BIOS won't necessary
matter, because xf86 can use font / resolution definitions from sources
other than the BIOS to handle virtual console text rendering.
I would normally suggest trying NVIDIA's binary Linux drivers, but
it is my understanding that the last NVIDIA binary Linux driver release
(4363) didn't support GeForceFX laptops but the next release will,
though it has not yet been released.
Thanks. Is there any way of knowing getting word when they're expected
to be released?
Also, is there any remedy whatsoever for the bad text rendition shown
during the boot loader? For instance, a BIOS update?
Thanks for all your help,
Christian

Mark.

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

Re: [XFree86] no screen after exiting X from startx

2003-07-16 Thread gabe f

oh yeah, got the source for svgatextmode, but haven't tried it yet, 
though
sounds promising.

On Tuesday, July 15, 2003, at 05:24 PM, Rich Johnson wrote:

gabe--

It's a shot it the dark, but...check to see if your kernel has Radeon 
display support enabled.
I encountered the same symptoms  running a distribution kernel (Debian 
Woody) with a FireGL 1000 Pro Card.
In my case all the virtual consoles went away when _entering_ X with 
startx.  But that wasn't apparent until you exited X.
I built a new kernel with the correct options and, _voila_, the 
problem went away.

Also, a good reference is:
   http://www.linux.org/docs/ldp/howto/Framebuffer-HOWTO-5.html


On Thursday, July 10, 2003, at 01:04 PM, gabebf  wrote:

I saw this posted in the groups, but no response there. I start X 
4.3.0 from startx, and works fine, but on exit,
I don't have a screen, but i can type shutdown -r now, blindly, and 
it works. What is it?

I have an ati radeon 7500, and have the problem on both an lcd and a 
crt monitor. I'm running fvwm 2.4.15.

gabe

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

__
Ode On A Sugar Sweet LAN
   I love my 'pooters, and my 'pooters love me.
   We're just a big digital family.
   Me and my 'pooters, we get along fine.
   I'm super tickled, my 'pooters are mine.
__
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86

Re: [XFree86] How to install XFree 4.3.0 on OpenBSD 3.3?

2003-07-16 Thread gabe f

are you having problems with the documentation supplied with xfree86 
4.3?

On Wednesday, July 16, 2003, at 10:35 AM, [EMAIL PROTECTED] wrote:

Pls. read the Subject. Thanks :o)

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

__
Ode On A Sugar Sweet LAN
   I love my 'pooters, and my 'pooters love me.
   We're just a big digital family.
   Me and my 'pooters, we get along fine.
   I'm super tickled, my 'pooters are mine.
__
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86

Re: [XFree86] Odd problem with terminals

On Wed, 16 Jul 2003, Christian Convey wrote:

 Mark Vojkovich wrote:
  
  On Wed, 16 Jul 2003, Christian Convey wrote:
  
  
 IIRC, however, the main reason you had me pull a new version of XF86 from CVS was 
 to see if it fixed the problem where on my virtual consoles, the last half of the 
 last line is below the bottom of the screen.  Unfortunately, I do still have that 
 problem.
 
 One detail I forgot to mention:  Always (regardless of any playing around I've 
 done), I have another problem: Mandrake 9.1 gives me what I think is a boot-loader 
 menu during startup.  The text inside that menu is absolutely garbled, but the 
 rest of the graphics on that screen look normal.  \
 
 When I hit Enter and go to the screen that shows the startup log messages 
 scrolling by, the text there, and from then on, looks perfectly normal.  Could 
 this be related to my virtual console problem?
 
  
  
 It could be.  I noticed that there didn't appear to be a 1440x900
  mode supported by the bios.  It's possible that the kernel framebuffer
  stuff relies on that.  I assume you are using a kernel framebuffer?
  That would be rivafb either built as a kernel module or staticly
  compiled into the kernel.  If you wanted to you could try building
  a kernel without kernel framebuffer support.  That might help.
  If you get the penguin image while the kernel boot messages are flowing
  by, that means you've definitely got kernel framebuffer support.
 
 Thanks.  So does it work like the following?
 
 During early boot up, the boot-loader software is responsible for
 rendering text, such as in my boot-loader menu.  It requires bios
 support for those fonts, and I apparently don't have it.
 
 Then, the kernel is responsible for rendering text.  That controls the
 rendering of the messages that flow by as the initiation scripts run.
 This also relies on the BIOS support for rendering that text.
 
 Finally, xf86 is responsible for rendering text, even on the virtual
 consoles.  At this point a deficiency in the BIOS won't necessary
 matter, because xf86 can use font / resolution definitions from sources
 other than the BIOS to handle virtual console text rendering.

   I don't know the details of how the OS deals with graphics
during bootup.  I assume it uses the BIOS.

   XFree86 isn't responsible for doing anything more than
restoring the hardware to the state it found it in.  To my
knowledge, there aren't any problems in the nv driver related
to that, but there have been in the past, and it's reasonable
that there could be a problem there that I don't know about 
yet.  I asked about a framebuffer device because I think
it may be involved in the text mode setup.  With my limited
knowledge of how the framebuffer devices work, it occurs to
me that the misrestoration of the text mode may be due to
the framebuffer device, which might possibly rely on the
BIOS.

 
  
 I would normally suggest trying NVIDIA's binary Linux drivers, but
  it is my understanding that the last NVIDIA binary Linux driver release
  (4363) didn't support GeForceFX laptops but the next release will,
  though it has not yet been released.
 
 Thanks.  Is there any way of knowing getting word when they're expected
 to be released?

   I suppose they'll be released when they're ready, not that it
will specifically address this problem.  If there's a mode missing
in the BIOS and the framebuffer device is relying on that, it would
probably occur with the NVIDIA binary drivers as well.

 
 Also, is there any remedy whatsoever for the bad text rendition shown
 during the boot loader?  For instance, a BIOS update?

   A BIOS update would probably fix that.  It might fix everything,
actually.  BIOSes on these systems are usually combination
System/Video BIOSes and are the responsibility of the vendor
(Toshiba in this case).

   I don't suppose you know your bios version do you?  I'm not
sure how to find it out on laptops these days.


Mark.

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

Re: [XFree86] Odd problem with terminals

Thanks for the info.  Comments below...

Mark Vojkovich wrote:

[snip]

  I would normally suggest trying NVIDIA's binary Linux drivers, but
it is my understanding that the last NVIDIA binary Linux driver release
(4363) didn't support GeForceFX laptops but the next release will,
though it has not yet been released.
Thanks.  Is there any way of knowing getting word when they're expected
to be released?


   I suppose they'll be released when they're ready, not that it
will specifically address this problem.  If there's a mode missing
in the BIOS and the framebuffer device is relying on that, it would
probably occur with the NVIDIA binary drivers as well.
So for the garbled-boot-menu issue, I wonder if the boot loader has any 
control over this.

I mean, if it's intelligent enough to slap some Mandrake-specific 
graphcs around the menu, perhaps it's selecting a video mode for which 
my BIOS can't render text.  That would make it a (Grub or Lilo) + 
Mandrake issue...



And for the framebuffer-restoration issue, do you think it's telling 
that I get this problem with the nv driver but not with the vesa 
driver?  I.e., does that point to a possible problem in the nv driver's 
code that we should look at?



Also, is there any remedy whatsoever for the bad text rendition shown
during the boot loader?  For instance, a BIOS update?


   A BIOS update would probably fix that.  It might fix everything,
actually.  BIOSes on these systems are usually combination
System/Video BIOSes and are the responsibility of the vendor
(Toshiba in this case).
   I don't suppose you know your bios version do you?  I'm not
sure how to find it out on laptops these days.
This particular laptop has a nice, desktop-like boot sequence, so it's 
pretty easy...

During POST, it says PhoenixBIOS 4.0 Release 6.0.  Insite the BIOS 
setup utility, however, it says BIOS version 1.10.



			Mark.

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


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

Re: [XFree86] Odd problem with terminals

On Wed, 16 Jul 2003, Christian Convey wrote:

 
 And for the framebuffer-restoration issue, do you think it's telling 
 that I get this problem with the nv driver but not with the vesa 
 driver?  I.e., does that point to a possible problem in the nv driver's 
 code that we should look at?

   I missed that part.  If the vesa driver doesn't have the problem
but the nv driver does that would point to a problem with the nv
driver.  Does it look like the text mode looks correct at some
point during the server shutdown, but then gets messed up?  If not,
then I'll just have to wait until I get my hands on one of these
so I can poke around.  

 Also, is there any remedy whatsoever for the bad text rendition shown
 during the boot loader?  For instance, a BIOS update?
  
  
 A BIOS update would probably fix that.  It might fix everything,
  actually.  BIOSes on these systems are usually combination
  System/Video BIOSes and are the responsibility of the vendor
  (Toshiba in this case).
  
 I don't suppose you know your bios version do you?  I'm not
  sure how to find it out on laptops these days.
 
 This particular laptop has a nice, desktop-like boot sequence, so it's 
 pretty easy...
 
 During POST, it says PhoenixBIOS 4.0 Release 6.0.  Insite the BIOS 
 setup utility, however, it says BIOS version 1.10.

   Usually the bios has a big long number with lots of decimal places
in it.  Like 4.17.00.61.31.


Mark.

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

Re: [XFree86] Scroll Wheel doesn't work

2003-07-16 Thread Wes Janzen

JoeHill wrote:

On Wed, 16 Jul 2003 14:45:08 -0700
Peter Nehem [EMAIL PROTECTED] uttered:
 

Hi all,
I'm hoping this is the right place to post this message.
I have a Logitech MX 700 wireless usb mouse. I have to move the mouse
around a few seconds before it starts to respond (but I can live with
this). Afterwords most of the buttons seem to work. It has 8 button.
But I can't get the wheel to scroll up or down. Here is how the mouse
looks in the XF86Config file:
Section Input Device
 Identifier Mouse0
 Driver mouse
 Option Protocol auto
 Option Device /dev/usbmouse
 Option Buttons 10
 Option ZAxisMapping 9 10
 Option Resolution 800
EndSection
   

Looks like the ZAxisMapping is wrong...should have all of the buttons
enumerated I believe.
There may be useful info for you about how that works here:

http://www.deadman.org/
 

I have an MX700 with 4.3.0 and use:

Section InputDevice
 Driver   mouse
 Identifier   Mouse[3]
 Option   ButtonNumber 10
 Option   Device /dev/pointer0
 Option   InputFashion Mouse
 Option   Name Autodetection
 Option   Protocol imps/2
 Option   Vendor Sysp
 Option   ZAxisMapping 4 5
EndSection
I don't use any of the other buttons beside the wheel though, but I 
don't think any other setting of ZAxisMapping will allow the wheel to work.

Hope that helps.

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

Re: [XFree86] Excessive CPU Usage with 4.3.0

2003-07-16 Thread Wes Janzen

Nevermind, found the problem.  I was using kernel 2.5.75-mm3 had a 
rather old drm source.  I'm now running 2.6.0-test1-mm1 and X is back 
down to normal usage.

Wes Janzen wrote:

I upgraded to 4.3.0 using the SuSE package for SuSE 8.0...

I upgraded my video card to a radeon at the same time so I don't know 
if this problem is due to the DRI driver (which is working fine) or if 
it is a problem with X.

On my K6-2 400 system, CPU usage for X runs at 15-30% all the time.  
If I switch to one of my virtual terminals, the CPU usage drops down 
again.
Does anyone have any ideas how to tame the CPU usage of X?

Thanks,

Wes Janzen

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

Re: [XFree86] No valid mode found for this DFP/LCD on ATI Radeon QL

On Wednesday, July 16, 2003 3:38 pm, jpavelek wrote:
 (II) RADEON(0): Total number of valid DDC mode(s) found: 0
 (WW) RADEON(0): Mode 1280x1024 is out of range.
 [...]
 (II) RADEON(0): Total number of valid FP mode(s) found: 0
 (EE) RADEON(0): No valid mode found for this DFP/LCD
 
 Is there, by chance, anything plugged in your composite or S-Video port? 
  If so, remove it, reboot, and try again.

 Thanks - this worked. Would there be any explanation why this doesn't
 work anymore? I just hate unplugging the S-Video (connected to my TV)
 every time I boot Linux:-(

Plus I would like to get this working for my own system.  Recall that someone 
else had this same problem.  Just search the list archive for psychic :^)

For those just tuning in, we're having trouble with composite and S-Video 
output on Radeons.

jpavelek, did this work correctly with the previous version of XFree86?

Are we supposed to set up special modelines for special resolutions or 
something?

-- 
Andy Goth  |  [EMAIL PROTECTED]  |  http://ioioio.net/
Engineers love to change things.

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

Re: [XFree86] Overwriting Mandrake 9.1's XFree software

On Wednesday, July 16, 2003 10:42 am, Christian Convey wrote:
 Andy Goth wrote:
  Guess I haven't been paying attention.

 OK, I'm cuting your pay for this help in half ;)

Crap!  I needed that extra $0!

  That's not good...  Now that you're on the latest CVS, it would probably
  be helpful if you shared the stack trace.  Include line numbers if you
  can, and be sure to give the date on which you downloaded the latest
  and/or greatest.

 Now that I downloaded it again this morning and am not using xfs, I
 don't crash (I followed your advice for going from xfs to simple
 directory lists.)

What happens if you re-add unix/:7100 to your font path list?  Put it at the 
bottom, then the top, and then comment out all other entries, until you see a 
crash.  Do this with and without xfs actually running.

That is, if you really want to pursue this.

 I guess the morals of the story are...

 1. I'll try to give stack traces when this happens, and

Cool.

 2. Maybe what's in CVS right now can't handle unfound font servers?  (I
 also noticed that it was saying the socket # to look for the font server
 on is -1.  Could that be the cause of the problem?)

xfs is supposed to listen on port 7100.

-- 
Andy Goth  |  [EMAIL PROTECTED]  |  http://ioioio.net/
Engineers love to change things.

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

Re: [XFree86] VESA modes for Toshiba P25 laptop (GeForce 5200 GO, 1440x900 lcd)

On Wednesday, July 16, 2003 10:36 am, Christian Convey wrote:
 XFree86 Version 4.3.0

CVS?  Mine says 4.3.0.1.  Release date: 9 May 2003; Build date: 07 June 2003

(By the way, why is there a leading zero on the build date and not the release 
date?)

 (WW) Option XkbCompat requires an string value
 (WW) Option XkbOptions requires an string value

From your XF86Config-4:

Option XkbCompat 
Option XkbOptions 

Why do you have these lines?

 (WW) VESA(0): Bad V_BIOS checksum

I wonder if this is causing us problems.

 *Mode: 112 (640x480)
 *Mode: 115 (800x600)
 *Mode: 118 (1024x768)

These three modes (all 32bpp) will fit on your screen.  Alas, VESA doesn't 
define a 1440x900 mode... unless I'm mistaken, it doesn't do hardware 
acceleration, either.

From XF86Config-4:

 Modeline 1440x900 106.47 1440 1520 1672 1904 900 901 904 932 -HSync +Vsync

VESA doesn't use modelines.

 (II) VESA(0): Not using mode 1440x900 (no mode of this name)

See? :^)

 (II) VESA(0): Not using built-in mode 1280x1024 (width too large for \
 virtual size)
 (II) VESA(0): Not using built-in mode 1024x768 (width too large for \
 virtual size)
 (II) VESA(0): Not using built-in mode 800x600 (width too large for \
 virtual size)
 (II) VESA(0): Not using built-in mode 640x480 (width too large for \
 virtual size)

640?  Too wide!?

From XF86Config-4:

 Subsection Display
 Depth 24
 Modes 1440x900  #1280x960 1152x864 1024x768 800x600 640x480
 EndSubsection

1440x900 fails since there's no matching VESA mode.  Then XFree86 appears to 
fall back on its no-Modes-list heuristic, that is, find the biggest usable 
mode.  At least, that's what I think it does---I don't rely on it.  Could 
someone confirm/correct?  But why doesn't it try the 320x VESA modes?  Mode 
10f would have worked, I think...

 (EE) VESA(0): No valid modes
 (EE) Screen(s) found, but none have a usable configuration.

The end.

Does nVidia's proprietary driver work?  You said that XFree86's nv driver 
looks good but futzes up the bottom row of text on your screen.  Is it an 
80x25 screen?  What's the character size in pixels?  9x16?  What happens if 
you set a smaller font?  Have you tried SVGATextMode?  fbcon?

If these questions have been asked before, forgive me.  I'm tired.

-- 
Andy Goth  |  [EMAIL PROTECTED]  |  http://ioioio.net/
Engineers love to change things.


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

CVS Update: xc (branch: trunk)

2003-07-16 Thread Matthieu Herrb

CVSROOT:/home/x-cvs
Module name:xc
Changes by: [EMAIL PROTECTED]   03/07/16 12:20:26

Log message:
  IPV6_JOIN_GROUP/IPV6_LEAVE_GROUP have replaced
  IPV6_ADD_MEMBERSHIP/IPV6_DROP_MEMBERSHIP

Modified files:
  xc/programs/xdm/:
socket.c 
  
  Revision  ChangesPath
  3.12  +9 -3  xc/programs/xdm/socket.c

___
Cvs-commit mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/cvs-commit

CVS Update: xc (branch: trunk)

2003-07-16 Thread Matthieu Herrb

CVSROOT:/home/x-cvs
Module name:xc
Changes by: [EMAIL PROTECTED]   03/07/16 12:35:40

Log message:
  - include sys/socket.h to get AF_INET6 definition
  - fix for a double free() recent code, in the case where a machine has
multiple addresses.

Modified files:
  xc/programs/xauth/:
process.c 
  
  Revision  ChangesPath
  3.21  +15 -3 xc/programs/xauth/process.c

___
Cvs-commit mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/cvs-commit

CVS Update: xc (branch: trunk)