[XFree86] value of dot clock, probeonly

2004-11-05 Thread Roger
00 to 400.00 MHz the line "clock range" it is my value of dot clock? Excused for my English. Thanks. Roger [EMAIL PROTECTED] ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86

[XFree86] Radeon 9200/DVI with latest XFree86

2003-11-10 Thread Roger Sunshine
e. Thanks for any information. -Roger _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/tempest:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 This is a pre-release version of XFree86, and is not supported in

[XFree86] Quitting X never returns me to console.

2003-09-22 Thread Roger Fischer
Hi, I finally got XFree86 up and running on my NetBSD box. Problem is, that when I quit X (Log out of the last xterm) the Screen disappears, but the monitor never syncs back up. It appears to be the video card, because turning the monitor off and back on has no effect. The only way I have been ab

Re: [XFree86] Problems with external connection

2003-03-27 Thread Grosswiler Roger
> On Thu, 27 Mar 2003, Grosswiler Roger wrote: > >> I am beginner, trying already since days to get connected to my linux >> with a gui. Until now, all my tries did not bring the expected result. >> >> 1) i just said putty, that it should support X11-forwarding on &

[XFree86] Problems with external connection

2003-03-27 Thread Grosswiler Roger
I am beginner, trying already since days to get connected to my linux with a gui. Until now, all my tries did not bring the expected result. 1) i just said putty, that it should support X11-forwarding on localhost 11.0. This was the answer: "X connection to localhost:11.0 broken (explicit kill or

[XFree86] Problems with external connection

2003-03-27 Thread Grosswiler Roger
I am beginner, trying already since days to get connected to my linux with a gui. Until now, all my tries did not bring the expected result. 1) i just said putty, that it should support X11-forwarding on localhost 11.0. This was the answer: "X connection to localhost:11.0 broken (explicit kill or

[XFree86] XFree86 4.2.99.901 Bug Report

2003-02-14 Thread Roger Hill-Cottingham
local display. However, running the same commandline on the same machine but over a LAN, gives a nice-looking clock on the remote display running XFree86-4.2.1 Regards, Roger Hill-Cottingham. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree8

[XFree86] Savage 3D Problem on Red Hat 7.0

2003-02-13 Thread Roger Daniel F Ferreira
faqs.org/faqs/x-faq/xfree86/) without success. Hope you can help me. Regards, Roger _ Advertência: Esta mensagem não implica a assunção de obrigações em nome da Itaipu Binacional, cujo Estatuto dispõe, em seu Arti

Re: [XFree86] X windows crash

2003-01-31 Thread Roger Harden
John Tapsell wrote: First, reboot. Then boot by: when you boot, pass the following option to the kernel: 'init=/bin/bash" So if you normally type "linux", do "linux init=/bin/bash" There's probably a better way. Perhaps "linux single" works, or "linux safe". I am using GRUB as the boot

Re: [XFree86] X windows crash

2003-01-30 Thread Roger Harden
the error message and switched to the text login screen where I could log into linux. Now I can't seem to break into the loop! Previous Log file attached. Any suggestions how I break into the loop? It's merrily looping as I write this note! Roger Harden Yikes. Is it doing exactly

Re: [XFree86] X windows crash

2003-01-30 Thread Roger Harden
John Tapsell - thanks for your reply. I've added the line, FontPath "unix/:-1" to the XF86Vonfig file. On rebooting the system it loops continuously between showing me the text login screen and a blank screen. Have you any further suggestions please? Roger Harden - O

[XFree86] X windows crash

2003-01-30 Thread Roger Harden
ttach the relevant log file.   Regards Roger Harden XFree86.0.log Description: Binary data

Re: [XFree86] X System Crash

2003-01-22 Thread Roger Harden
l IO error 104 (connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining." I feel that an essential file was corrupted when the X system crashed. Any further thoughts? Regards Roger Harden - Original Message - From: "Henr

[XFree86] X System Crash

2003-01-22 Thread Roger Harden
.   Regards Roger Harden XFree86.0.log Description: Binary data

[XFree86] X System Crash

2003-01-20 Thread Roger Harden
.   Regards Roger Harden   XFree86.0.log Description: Binary data