Hello,
I'm trying to edit the xorg.conf but am confused by puppy's auto-generated construction of xorg.conf. Does puppy construct a real, complete xorg.conf through the xorgwizard process? Yesterday I had to fall back into vesa mode since xorg couldn't produce a viewable screen for my cle266 video chip/monitor combination. I edited xorg.conf with values from the http://xtiming.sourceforge.net modeline generator. After saving my changes, I ctrl-alt-bksp'd out of the vesa mode of xwin, and entered xorgwizard hoping that it would use the new values. No success. In fact when I fell back again into vesa xwin I checked the xorg.conf file and my changes where no longer there.

I also noticed at the bottom of the xorg.conf file a line that was something like #puppycle266... but this had nothing underneath it. it sort of looked like a reference to an external file with the cle266 modes. Is xorg.conf and the way that puppy uses it documented anywhere?
thanks in advance,
Martin

Will,
Thanks for your help. I tried the commands you suggested but ran into a problem with:
ln -s /usr/X11R7/bin/Xorg /usr/X11R7/bin/Xorg
I'm not familiar with the ln command but recognize that the two file references are the same (which the OS balked at). Should one of the two files references be different?
thanks again,
Martin

The ln means link, and the -s makes it a symlink. The first parameter, /usr/X11R7/bin/Xorg is the source file, and the second, /usr/X11R7/bin/X is the name of the link to make._________________Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

Thanks Pizza and Will for the pointers. I apologize again for my basic questions... but here's a couple more: I found from other forum threads that my Modeline needs to be added to the "Monitor" and "Screen" sections of xorg.conf.
(1) What about the "Modes" section of the the xorg.conf file? It appears right below the "Monitor" section. There is a comment line in the "Monitor" section that refers to "Modes0" (which appears in the "Modes" section. Do I need to duplicate the whole or part of the Modeline statement to this section?
(2) Do I need to include the -HSync and +Vsync terms at the end of the Modeline statement? The XFree86 Modeline Generator doesn't include these but the Linux gtf command does.
Martin

I presume you have actually run the xorgwizard to completion and then run xwin to start X, what happens.
For anyone else that hasn't noticed the cle266 is a via graphics card. Martin what motherboard is it on, there is a fair chance someone else here has one._________________Will
contribute: community website, screenshots, puplets, wiki, rss

Will,
After the rm and ln commands I restart X via xwin but just get a blank screen (the monitor appears to not be able to sync with what the video chip is sending it). I then ctrl-alt-bksp to rerun the xorgwizard and slip back into xvesa before xorg.conf gets re-written. I can then edit xorg.conf while in xvesa mode and return to the command prompt to perform another set of rm/ln/xwin tests.

My motherboard is a Via Epia ME6000. I have the standard video BIOS settings on the board. My monitor is a Soyo DYLM24D6.
Thanks again,
Martin

Martin
you might find life easier if you learnt to edit the file in the console.
mp /etc/X11/xorg.conf
will start the mp text editor
cursor keys to move about
when you have finished your editing
CTRL-S to save
CTRL-Q to quit
then xwin

Well, I've spent quite a bit of time on this and have come to the conclusion that 2.17/Xorg must have a bug when it comes to support for the CLE266 chip. I tried a number of different modeline settings (via both xtiming.sourceforge.net and gtf probe) that conform to supported CLE266 dotclock values but everyone was rejected. Then, I booted Ubuntu 7.04 on the same CLE266 system and found it was able to drive my monitor at higher resolutions. I don't know enough about the relative versions of xorg compiled within Puppy 2.17 and Ubuntu 7.04 or how to go forward from here. But, if someone else does, I'd be happy to work with them to do some testing. Thanks again for your help.

You might want to check the Xorg log file after the failed attempt. It's at /var/log/Xorg.0.log. You can read it with less or mp on the commandline, or start Xvesa and read it with your preferred editor, then manually set Xorg as the default again.

A quick way to find most error messages is this:
grep "(EE)" /var/log/Xorg.0.log
and for warnings, this:
grep "(WW)" /var/log/Xorg.0.log

Those won't show any lines around those errors though, so you might still need to view the file in it's entirety to see what's going on.

You also might want to compare the xorg.conf file from Ubuntu to see if there's anything different_________________Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

What is the glx module? Is it possible its in a directory that can't be found by the system?

Also, I don't understand why the Via driver appears coded to drive the mode clock to 157.5 MHz for 1280x1024. Here's the modeline that I added to my xorg.conf file (which was generated by gtf) in support of the 1280x1024 resolution (and which shows a clock of 108.88 MHz):

I'm just curious. What would happen if you simply rebooted your computer and booted from your puppy 2.17.1 disc? I encountered this problem back with 1.0.7. I ended up backing up my files to cd and then reinstalling my system with the new xorg configuration that was created when I booted from cd. Of course I am the idiot that used puppy 0.7 for about three and half months without a hard drive in his computer, so I am probably clueless anyway.

KF6SNJ,
Thanks for your suggestion. I'm essentially doing just this, that is, booting from a CF/IDE with the LiveCD image of 2.17.1. The problem appears to be a miscalculation (or miscoding?) of the dotclock frequency required by the cle266 driver to drive an external display above 1024x768. My next task is to boot on Ubuntu, where its cle266 driver can successfully drive xorg to 1280x1024, and compare the xorg.0.log with puppy's.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum