1.0.7a: update for XorgWizard, 15Dec2005
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
1.0.7a: update for XorgWizard, 15Dec2005
From here:
http://www.pupweb.org/test/
Lots more features, bugfixes.
It should be much easier for people who are unfamiliar with X
and who would be intimidated having to edit xorg.conf directly.
It should cater very nicely for both cases, a plug-and-play
monitor and a non-plug-and-play monitor.
Kindly test on your hardware, let me know what happens.
Requires Pup 1.0.7alpha.
http://www.pupweb.org/test/
Lots more features, bugfixes.
It should be much easier for people who are unfamiliar with X
and who would be intimidated having to edit xorg.conf directly.
It should cater very nicely for both cases, a plug-and-play
monitor and a non-plug-and-play monitor.
Kindly test on your hardware, let me know what happens.
Requires Pup 1.0.7alpha.
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
Incorporated the new xorgwizard (which on downloading just auto-opened as a text file? which I copied over the old file in usr/sbin)
I ran xorgwizard. Selecting 1280x1024. (Edit: What a fool - I did not press space to select - when I did it was OK - am in the higher res now - the settings below are the default - will run the test again . . .)
It then ran the test box (with the artic whale fin pic) with the following settings displayed:
which would seem correct from what happened next
get-edid (see below) is reporting the wrong settings
I also tried the wacom tablet and running the mouse wizard from the xorg wizard - but no luck there so I suppose some manual settings? (no tablet device is available in mtpaint)
I have not done any manual config (as yet)
Hope this is useful. Anything further you would recommend?
I ran xorgwizard. Selecting 1280x1024. (Edit: What a fool - I did not press space to select - when I did it was OK - am in the higher res now - the settings below are the default - will run the test again . . .)
It then ran the test box (with the artic whale fin pic) with the following settings displayed:
Code: Select all
- 800x600
hz 46.875
Refresh 75
get-edid (see below) is reporting the wrong settings
I also tried the wacom tablet and running the mouse wizard from the xorg wizard - but no luck there so I suppose some manual settings? (no tablet device is available in mtpaint)
Code: Select all
# get-edid | parse-edid
get-edid: get-edid version 1.4.1
Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
Function supported
Call successful
VBE version 300
VBE string at 0xc0df0 "S3 Incorporated. Savage4"
VBE/DDC service about to be called
Report DDC capabilities
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
Function supported
Call successful
Monitor and video card combination does not support DDC1 transfers
Monitor and video card combination supports DDC2 transfers
0 seconds per 128 byte EDID block transfer
Screen is not blanked during DDC transfer
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
parse-edid: parse-edid version 1.4.1
parse-edid: EDID checksum passed.
# EDID version 1 revision 3
Section "Monitor"
# Block type: 2:0 3:ff
# Block type: 2:0 3:fd
# Block type: 2:0 3:fc
Identifier "LM-700"
VendorName "AOC"
ModelName "LM-700"
# Block type: 2:0 3:ff
# Block type: 2:0 3:fd
HorizSync 30-80
VertRefresh 55-75
# Max dot clock (video bandwidth) 130 MHz
# Block type: 2:0 3:fc
# DPMS capabilities: Active off:yes Suspend:no Standby:no
Mode "1280x1024" # vfreq 75.025Hz, hfreq 79.976kHz
DotClock 135.000000
HTimings 1280 1296 1440 1688
VTimings 1024 1025 1028 1066
Flags "-HSync" "-VSync"
EndMode
# Block type: 2:0 3:ff
# Block type: 2:0 3:fd
# Block type: 2:0 3:fc
EndSection
Hope this is useful. Anything further you would recommend?
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
these are the settings after I used space to select 1280 x 1024 (previous post I did not press space just moved to that position and clicked OK)
Display seems OK
when running the xorg from the menu the system reboots and you go through the setup of mouse etc sequence again . . .
Display seems OK
when running the xorg from the menu the system reboots and you go through the setup of mouse etc sequence again . . .
Code: Select all
# get-edid | parse-edid
get-edid: get-edid version 1.4.1
Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
Function supported
Call successful
VBE version 300
VBE string at 0xc0df0 "S3 Incorporated. Savage4"
VBE/DDC service about to be called
Report DDC capabilities
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
Function supported
Call successful
Monitor and video card combination does not support DDC1 transfers
Monitor and video card combination supports DDC2 transfers
0 seconds per 128 byte EDID block transfer
Screen is not blanked during DDC transfer
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
parse-edid: parse-edid version 1.4.1
parse-edid: EDID checksum passed.
# EDID version 1 revision 3
Section "Monitor"
# Block type: 2:0 3:ff
# Block type: 2:0 3:fd
# Block type: 2:0 3:fc
Identifier "LM-700"
VendorName "AOC"
ModelName "LM-700"
# Block type: 2:0 3:ff
# Block type: 2:0 3:fd
HorizSync 30-80
VertRefresh 55-75
# Max dot clock (video bandwidth) 130 MHz
# Block type: 2:0 3:fc
# DPMS capabilities: Active off:yes Suspend:no Standby:no
Mode "1280x1024" # vfreq 75.025Hz, hfreq 79.976kHz
DotClock 135.000000
HTimings 1280 1296 1440 1688
VTimings 1024 1025 1028 1066
Flags "-HSync" "-VSync"
EndMode
# Block type: 2:0 3:ff
# Block type: 2:0 3:fd
# Block type: 2:0 3:fc
EndSection
#
it seems to work ok on my machine ... no duplicated HorizSync line
it puts
BusID "PCI:1:0:0"
in the "Device" section ... i comment that out, because it doesn't seem to be necessary ... it doesn't seem to hurt anything, of course ... maybe it's needed for machines with more than one video card
everything else seems to be perfect ... mouse, video driver, video modes, monitor ... actually, many distros are a lot worse ... for example, when i boot the pclinuxos live cd, i have to boot to console mode, edit xorg.conf with vi, to change the video driver (always set to vesa), resolution (always set to 1600x1400 or something), refresh rate (always set to 60 hz), then start X ... otherwise, if you try to restart X, it reboots, and changes to xorg.conf are lost ... i think i also have to edit xorg.conf to get the mouse wheel to work
it puts
BusID "PCI:1:0:0"
in the "Device" section ... i comment that out, because it doesn't seem to be necessary ... it doesn't seem to hurt anything, of course ... maybe it's needed for machines with more than one video card
everything else seems to be perfect ... mouse, video driver, video modes, monitor ... actually, many distros are a lot worse ... for example, when i boot the pclinuxos live cd, i have to boot to console mode, edit xorg.conf with vi, to change the video driver (always set to vesa), resolution (always set to 1600x1400 or something), refresh rate (always set to 60 hz), then start X ... otherwise, if you try to restart X, it reboots, and changes to xorg.conf are lost ... i think i also have to edit xorg.conf to get the mouse wheel to work
Re: 1.0.7a: update for XorgWizard, 15Dec2005
Booted the 1.0.7(a) live CD with boot option 4 (no hard drive), Xvesa. Got online, went to the forum and clicked on the above link. It appeared to my rheumy old eyes that the .gz file automatically gunzipped when it gdownloaded. I right-clicked in it and chose Select All, then Copy to put it on the clipboard. Then I clicked on the Edit icon on the desktop to open Beaver, clicked File -> Open in Beaver, found /usr/sbin/xorgwizard and opened it in Beaver, right-clicked in the file, chose Select All, then Paste. The text changed slightly, which I took to indicate that the file from the clipboard had replaced the original. Again I clicked File in Beaver but this time chose Save. Beaver said it saved the file so I exited Beaver, did ctrl-alt-backspace then typed xorgwizard at the prompt.BarryK wrote:From here:
http://www.pupweb.org/test/
Lots more features, bugfixes.
It should be much easier for people who are unfamiliar with X
and who would be intimidated having to edit xorg.conf directly.
It should cater very nicely for both cases, a plug-and-play
monitor and a non-plug-and-play monitor.
Kindly test on your hardware, let me know what happens.
Requires Pup 1.0.7alpha.
Sorry I can't remember what the various wizard dialog windows said, but I made what seemed to be the appropriate choices as I went through them. I do remember that although my LCD monitor is capable of 1280 x 760 the maximum resolution the wizard said was supported was only 800 x 600. So I get to the last xorgwizard window and take the plunge. The screen goes black. I wait a full minute then try ctrl-alt-backspace: nothing. I try ctrl-alt-delete: nothing. Then I tried every key on the keyboard: still nothing but black. I had to push the power-off button on the computer to reboot.
The wizard itself seems to be working fine now; there seems to be some incompatibility with my hardware. This happens when I run the unmodified xorgwizard too. I have the i815T chipset with onboard video.
My results with new xorgwizard:
-Chose 1280x1024x16 from list
-execute "xwin", X starts up fine.
-check xorg.conf, values are as before except:
-Chose 1280x1024x16 from list
- Report on X test: success
Resolution: 1280x1024 pixels
Horz freq: unknown kHz
Refresh freq: unknown Hz
The "unknown" means...wizard cannot continue"
-execute "xwin", X starts up fine.
-check xorg.conf, values are as before except:
- Section "Monitor"
#DisplaySize 340 270 # mm
Identifier "Monitor0"
VendorName "BNQ"
ModelName "BenQ FP731"
HorizSync 31.0 - 81.0
VertRefresh 56.0 - 75.0
Option "DPMS" <== missing this time
EndSection
- Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 16
Subsection "Display"
Depth 16
Modes "1280x1024"
EndSubsection
EndSection
- Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
# Option "Protocol" "auto"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/mouse"
#Option "Emulate3Buttons"
#Option "Emulate3Timeout" "50"
Option "ZAxisMapping" "4 5" #scrollwheel
EndSection
New Xorgwizard results
Tested on two older systems so far.
1: IBM i1400 thinkpad, neomagic video, older LCD (1024x768 60 Hz not auto detected so manual choices displayed)
Works correctly, no extra lines, refresh rate needed to be tweaked down to 60. I edited xorg.conf on this one.
2: Pine AGP card based on SIS 6326 chip, CTX 5700 15 inch CRT.
Worked correctly, Same refresh rates as previously, no extra lines, "DPMS" option chosen correctly, maximum monitor refresh rate of 85 Hz chosen, Tweak refresh worked well to lower it to 75Hz.
One comment. The hardware probing and parsing is quite slow so a caution to that effect at the beginning
of the wizard might head off a few operator errors.
1: IBM i1400 thinkpad, neomagic video, older LCD (1024x768 60 Hz not auto detected so manual choices displayed)
Works correctly, no extra lines, refresh rate needed to be tweaked down to 60. I edited xorg.conf on this one.
2: Pine AGP card based on SIS 6326 chip, CTX 5700 15 inch CRT.
Worked correctly, Same refresh rates as previously, no extra lines, "DPMS" option chosen correctly, maximum monitor refresh rate of 85 Hz chosen, Tweak refresh worked well to lower it to 75Hz.
One comment. The hardware probing and parsing is quite slow so a caution to that effect at the beginning
of the wizard might head off a few operator errors.
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Paul,pakt wrote:My results with new xorgwizard:
-Chose 1280x1024x16 from list
- Report on X test: success
Resolution: 1280x1024 pixels
Horz freq: unknown kHz
Refresh freq: unknown Hz
Your problem is occurring in this code in xorgwizard:
Code: Select all
TESTMODELINE="`xvidtune -display :0 -show | tr -s " "`"
CLOCKMHZ=`echo -n "$TESTMODELINE" | cut -f 2 -d " "`
CLOCKHZ=`dc $CLOCKMHZ 1000000 \* p`
XTOTAL=`echo -n "$TESTMODELINE" | cut -f 6 -d " "`
YTOTAL=`echo -n "$TESTMODELINE" | cut -f 10 -d " "`
XTEST=`echo -n "$TESTMODELINE" | cut -f 3 -d " "`
YTEST=`echo -n "$TESTMODELINE" | cut -f 7 -d " "`
VRTEST=`dc $CLOCKHZ $XTOTAL \/ $YTOTAL \/ p`
HSTEST=`dc $CLOCKHZ $XTOTAL \/ 1000 \/ p`
[ "$VRTEST" = "nan" ] && VRTEST='unknown'
[ "$HSTEST" = "nan" ] && HSTEST='unknown'
Code: Select all
xvidtune -show | tr -s " " | cut -f 2 -d " "
Let's call that CLOCKMHZ.
Then try this:
Code: Select all
dc $CLOCKMHZ 1000000 \* p
Code: Select all
xvidtune -show | tr -s " " | cut -f 6 -d " "
Then try this:
Code: Select all
dc $CLOCKHZ $XTOTAL \/ 1000 \/ p
...hopefully you will then be able to find out why "dc" is
returning "nan" (not a number).
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: New Xorgwizard results
Marv,Marv wrote:One comment. The hardware probing and parsing is quite slow so a caution to that effect at the beginning
of the wizard might head off a few operator errors.
The Wizard does have this:
Press TAB then ENTER for Xorg (probing will take a few secs)...
Maybe that is an understatement, and should be
" (probing may take several seconds)..."
or
" (PLEASE WAIT, probing will take several seconds)..."
worked on my hardware
Barry, your xorg wizard worked well for me. The original selected a conservative frequency because my monitor is not PnP (so assumed basic 15"). The new wizard gave me the opportunity to indicate that it's a 17" and resulted in higher frequency. XTest reported correctly for me. Thanks!
That gives: 0.00BarryK wrote: Could you open a terminal window and try some experiments:Code: Select all
xvidtune -show | tr -s " " | cut -f 2 -d " "
I then tried:
# xvidtune -show
"1280x1024" 0.00 1280 0 0 0 1024 0 0 0
There's the problem - the code is manipulating zeros...
Paul
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Hmmm, I wonder if there is any other way to get the current actual horiz and vert frequencies.pakt wrote:That gives: 0.00BarryK wrote: Could you open a terminal window and try some experiments:Code: Select all
xvidtune -show | tr -s " " | cut -f 2 -d " "
I then tried:
# xvidtune -show
"1280x1024" 0.00 1280 0 0 0 1024 0 0 0
There's the problem - the code is manipulating zeros...
Paul
I wonder what it is about your hardware that is upsetting xvidtune...
If I run xvidtune w/o switches I get:BarryK wrote:Hmmm, I wonder if there is any other way to get the current actual horiz and vert frequencies.pakt wrote:That gives: 0.00BarryK wrote: Could you open a terminal window and try some experiments:Code: Select all
xvidtune -show | tr -s " " | cut -f 2 -d " "
I then tried:
# xvidtune -show
"1280x1024" 0.00 1280 0 0 0 1024 0 0 0
There's the problem - the code is manipulating zeros...
Paul
I wonder what it is about your hardware that is upsetting xvidtune...
- # xvidtune
Vendor: BNQ, Model: BenQ FP731
Num hsync: 1, Num vsync: 1
hsync range 0: 31.00 - 81.00
vsync range 0: 56.00 - 75.00
Video are not settable on this chip
Obviously, xvidtune can determine the frequencies. Too bad it is just in interactive mode...
BTW, it has nothing to do with my external 17" TFT screen. When I disconnect it and delete xorg.conf, I get:
- # xvidtune -show
"1024x768" 0.00 1024 0 0 0 768 0 0 0
# xvidtune
Vendor: CMO, Model: 1502
Num hsync: 1, Num vsync: 1
hsync range 0: 31.50 - 48.50
vsync range 0: 40.00 - 70.00
Video are not settable on this chip
#
Well, I updated xorgwizard the same way as Flash mentioned. I still have the same results as before with some new discoveries. I have not been able to do anything with the test mode at the end of the xorgwizard (frozen with either blank screen or vertical lines). The only way I can get into X.Org is with a reboot and loading the previous pup004 file. The xorgwizard lists 640x480 (16 & 24), 800x600 (16 & 24) as supported (xvesa the same up to 16-bit mode), 1024x768 and higher as unsupported, and a few as dangerous. 800x600@24 freezes on boot and so makes pup004 unusable. 800x600@16 & 1024x768@24 works but a lot of portions are scrambled, I'm barely able to navigate (see my my screen capture below). The 640x480 modes work but its too low of a resolution for practical/normal use. Although, like Barry mentioned on his news page (8 Dec, 2005), I'm using the virtual screen feature to expand it to 800x600 which makes it OK but kinda annoying without a scroll wheel mouse.
While I was in low-res mode I viewed the xorg.conf file and it correctly identified my video card as shown in the (uncommented) Device sections:
Identifier "Card0"
Driver "i810"
VendorName "Intel Corp."
BoardName "82810 DC-100 CGC [Chipset Graphics Controller]"
BusID "PCI:0:1:0"
So, like Flash, I suspect it is from poor driver support/incompatiblity with my graphics chipset. So, I would suggest we have:
EDIT: added a little about the virtual screen thing
EDIT2: moved image offsite
While I was in low-res mode I viewed the xorg.conf file and it correctly identified my video card as shown in the (uncommented) Device sections:
Identifier "Card0"
Driver "i810"
VendorName "Intel Corp."
BoardName "82810 DC-100 CGC [Chipset Graphics Controller]"
BusID "PCI:0:1:0"
So, like Flash, I suspect it is from poor driver support/incompatiblity with my graphics chipset. So, I would suggest we have:
- a kernel parameter/boot option to not start X at boot
- a message in the initial xorgwizard better clarifying that xvesa w/ XFree86 will work on most any video card and X.Org may not work properly but supports many more display options
EDIT: added a little about the virtual screen thing
EDIT2: moved image offsite
Last edited by J_Rey on Sat 07 Jan 2006, 18:19, edited 1 time in total.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
pakt,
Can you test the program "xrandr", attached.
Just type "xrandr" on the commandline, and see if it gives you
the vertical refresh frequency.
If it does, then I will use that as a fallback for when xvidtune
doesn't work.
Knowing the vert freq, I should be able to calculate the horiz
freq.
Can you test the program "xrandr", attached.
Just type "xrandr" on the commandline, and see if it gives you
the vertical refresh frequency.
If it does, then I will use that as a fallback for when xvidtune
doesn't work.
Knowing the vert freq, I should be able to calculate the horiz
freq.
- Attachments
-
- xrandr.gz
- (5.13 KiB) Downloaded 500 times
With 17" external TFT panel connected:BarryK wrote:pakt,
Can you test the program "xrandr", attached.
Just type "xrandr" on the commandline, and see if it gives you the vertical refresh frequency.
The TFT screen display information shows: 1280x1024 75Hz
SZ: Pixels Physical Refresh
*0 1280 x 1024 ( 342mm x 271mm ) *76
1 1024 x 768 ( 342mm x 271mm ) 76
2 800 x 600 ( 342mm x 271mm ) 73
3 640 x 480 ( 342mm x 271mm ) 73
Changed xorg.conf section "Screen" from "1280x1024" to "800x600" then re-ran X
The TFT screen display information shows: 800x600 75Hz
SZ: Pixels Physical Refresh
*0 800 x 600 ( 344mm x 272mm ) *73
1 640 x 480 ( 344mm x 272mm ) 73
Deleted xorg.conf, shutdown, disconnected 17", rebooted, chose h31.5-48.5v40-70 LCD Panel 1024x768 and 1024x768x16 video mode:
SZ: Pixels Physical Refresh
*0 1024 x 768 ( 347mm x 260mm ) *0
1 800 x 600 ( 347mm x 260mm ) 0
2 640 x 480 ( 347mm x 260mm ) 0
Shutdown, re-connected 17", rebooted using previous xorg.conf:
SZ: Pixels Physical Refresh
*0 1024 x 768 ( 342mm x 271mm ) *61
1 800 x 600 ( 342mm x 271mm ) 61
2 640 x 480 ( 342mm x 271mm ) 61
Still using 17" panel and previous xorg.conf, changed xorg.conf section "Screen" from "1024x768" to "1280x1024" then re-ran X. The resolution defaulted back to 1024x768. I assume this is because Section "Monitor" specified VertRefresh 40-70 and 1280x1024 would require 75Hz (from above info).
SZ: Pixels Physical Refresh
*0 1024 x 768 ( 342mm x 271mm ) *61
1 800 x 600 ( 342mm x 271mm ) 61
2 640 x 480 ( 342mm x 271mm ) 61
Barry, this brings up something else to consider. When I run the xorgwizard with my external 17" TFT panel connected (and xorg.conf deleted), the wizard goes directly to "video mode menu". I don't get the chance to select LCD panel or CRT monitor. That's of course why the 17" ends up at 75Hz instead of 60Hz. The wizard assumes it is a CRT monitor and correctly chooses the highest refresh frequency. Not good in this case as a TFT panel should work at 60Hz...
Paul
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Hmmm, that's an awkward one, but I don't see it as critical.Barry, this brings up something else to consider. When I run the xorgwizard with my external 17" TFT panel connected (and xorg.conf deleted), the wizard goes directly to "video mode menu". I don't get the chance to select LCD panel or CRT monitor. That's of course why the 17" ends up at 75Hz instead of 60Hz. The wizard assumes it is a CRT monitor and correctly chooses the highest refresh frequency. Not good in this case as a TFT panel should work at 60Hz...
Xorg auto-detects the plug-and-play LCD monitor, which is why
the wizard goes straight to resolution selection dialog.
Xorg will only drive the panel at a frequency that it reports it is
capable of.
If you consider 75Hz too high, after the first test, you do get an opportunity to "tweak" the settings, and you can drop the frequency down.
Actually, I have a better idea than having a boot option/kernel parameter to allow users to get Puppy back to normal if X.org freezes on boot.
There could be a script that checks to see if X exited properly and if it didn't then skip loading X at boot and go to console with a message that says what happened and tells the user to type "loadx" to start X again or type "xorgwizard" to change the display settings. I was thinking of something like have a line in a file (e.g. xload) that says X-Loaded=true and have it set to true just before X is started (including the test following xorgwizard) and set to false immediately after X is exited. Then at boot, check to make sure that it doesn't say true. Maybe have a script "loadx" that sets X-Loaded to true and then loads X via xwin and passes on whatever parameters were given then sets X-Loaded to false and exits. I probably repeated myself a bit but oh well.
There could be a script that checks to see if X exited properly and if it didn't then skip loading X at boot and go to console with a message that says what happened and tells the user to type "loadx" to start X again or type "xorgwizard" to change the display settings. I was thinking of something like have a line in a file (e.g. xload) that says X-Loaded=true and have it set to true just before X is started (including the test following xorgwizard) and set to false immediately after X is exited. Then at boot, check to make sure that it doesn't say true. Maybe have a script "loadx" that sets X-Loaded to true and then loads X via xwin and passes on whatever parameters were given then sets X-Loaded to false and exits. I probably repeated myself a bit but oh well.
I'm sad to hear there are problems with the new Xorg wizard with some of you. I tested it with my old non plug and play 17" CRT monitor at the weekend and it worked great.
I ran it to start afresh creating the xorg.conf file and tried to act like a non-technical user. I did not consult my monitor manual and tried to follow the screens. It started X OK but the screen was misplaced so I went into the tweak options. With the old Wizard I had to consult my manual to get frequencies. This time I just increased the frequency to that suggested and it worked although the frequency was not as high as that found when I put the frequency range from the monitor manual in. I've just realised that I knew I had to increase the frequency because of previous experience. How would a newbie know whether to increase or decrease the frequency? This revised wizard is a big step forward. I like X-Org!
ICPUG
I ran it to start afresh creating the xorg.conf file and tried to act like a non-technical user. I did not consult my monitor manual and tried to follow the screens. It started X OK but the screen was misplaced so I went into the tweak options. With the old Wizard I had to consult my manual to get frequencies. This time I just increased the frequency to that suggested and it worked although the frequency was not as high as that found when I put the frequency range from the monitor manual in. I've just realised that I knew I had to increase the frequency because of previous experience. How would a newbie know whether to increase or decrease the frequency? This revised wizard is a big step forward. I like X-Org!
ICPUG