Re: no screens found
pues ya lo solucione y ya mire la paginita esa que me habeis sugerido /\/\/\/ On Sat, 4 Dec 2004 17:01:34 +0100, David Schmitt [EMAIL PROTECTED] wrote: On Tue, Nov 30, 2004 at 06:28:27PM -0500, David Arenas wrote: (==) Using config file: /etc/X11/XF86Config-4 Parse error on line 124 of section DRI in file /etc/X11/XF86Config-4 :p! is not a valid keyword in this section. (EE) Problem parsing the config file (EE) Error from xf86HandleConfigFile() Reading the above, I'd guess another case of vi. Try deleting line 124 in /etc/X11/XF86Config-4 Regards, David -- * Customer: My palmtop won't turn on. * Tech Support: Did the battery run out, maybe? * Customer: No, it doesn't use batteries. It's Windows powered. -- http://www.rinkworks.com/stupid/cs_power.shtml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: no screens found
Em Qua, 2004-12-15 às 13:56, David Arenas escreveu: pues ya lo solucione y ya mire la paginita esa que me habeis sugerido /\/\/\/ On Sat, 4 Dec 2004 17:01:34 +0100, David Schmitt [EMAIL PROTECTED] wrote: On Tue, Nov 30, 2004 at 06:28:27PM -0500, David Arenas wrote: (==) Using config file: /etc/X11/XF86Config-4 Parse error on line 124 of section DRI in file /etc/X11/XF86Config-4 :p! is not a valid keyword in this section. See the log -- Parse error on line 124 of section DRI in file /etc/X11/XF86Config-4 :p! is not a valid keyword in this section. (EE) Problem parsing the config file (EE) Error from xf86HandleConfigFile() Reading the above, I'd guess another case of vi. Try deleting line 124 in /etc/X11/XF86Config-4 Regards, David -- * Customer: My palmtop won't turn on. * Tech Support: Did the battery run out, maybe? * Customer: No, it doesn't use batteries. It's Windows powered. -- http://www.rinkworks.com/stupid/cs_power.shtml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: no screens found
Hi David, here some ideas to it: On Tue, Nov 30, 2004 at 06:28:27PM -0500, David Arenas wrote: hi, in file /var/log/XFree86.0.log This is a pre-release version of XFree86, and is not supported in any ^^ this might tell a bit already ... [...] (==) Using config file: /etc/X11/XF86Config-4 Parse error on line 124 of section DRI in file /etc/X11/XF86Config-4 :p! is not a valid keyword in this section. (EE) Problem parsing the config file (EE) Error from xf86HandleConfigFile() did you fix this error already? no screens could be caused by that. (EE) Problem parsing the config file (EE) Error from xf86HandleConfigFile() Fatal server error: no screens found 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/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] After fixing the error above (and all others which might follow), report the problem as described above; you could also ask here, but it might be useful to let the xf86-programmers know it as well. Regards -- hgb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: no screens found
On Wed, Dec 01, 2004 at 01:06:00AM +0100, Hans-Georg Bork wrote: Fatal server error: no screens found 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/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] After fixing the error above (and all others which might follow), report the problem as described above; you could also ask here, but it might be useful to let the xf86-programmers know it as well. no, don't - you have a configuration problem, not a buggy server, the xf86 team will NOT want to know about it!! Sam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
