Dougal, the 28th April version does not work for me -- I lost the automatic monitor detection. My laptop only "properly" supports 1280x800, and the monitor probe detects that and only offers 1280x800x16 and 1280x800x24. The 28th version came up with a list of all modes, seemingly having failed the auto-probe.

I have made a small mod to the 24th April version, mentioned it in today's blog. Um, should post it here too...

Dougal, the 28th April version does not work for me -- I lost the automatic monitor detection.

It's not lost -- that the solution to Leon's problem of not getting high resolutions: if you have less than 4 resolutions detected, then I force it to give you the full list.
I also thought of maybe modifying the way that "if" works, so it always gives the ones that were detected + the ones from the list (with the appropriate warnings about being detected or not).

Note that the April 28th version was not attached to the first post, as it's just a "testing" version -- I want people to test changing to the vesa driver before testing X._________________What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind

perhaps instead of displaying all the options, you could only give one option of "showing all resolutions" incase the resolution they need isn't listed? And only make it more prominent if they have under 4 listed._________________

perhaps instead of displaying all the options, you could only give one option of "showing all resolutions" incase the resolution they need isn't listed? And only make it more prominent if they have under 4 listed.

That might be complicated, as you are given the options further down the script._________________What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind

Barry: you asked a while ago that I add the 915 code to the video-wizard.
I am not completely clear about this, so will need some help.
Here's what I figured this far:

1) Check ddcprobe output for Intel card. If we are using one, then:
2) Find card resolutions from ddcprobe utput.
3) Check each of those: if it isn't listed in the Xvesa modes, add it to list offered to user.
4) If user has selected one of these modes, use 915resolution to set mode 38 to requested resolution.

What now? What do I put into /etc/videomode?
You mention "38" as being 1024x768, which would mean 0x0117 or 0x0118 (I assume the second). So do I put '0x0118 1024x768x24' into /etc/videomode?
(BTW, I also get 0x011A and 0x011B (1280x1024))

And what about the colour-depth? Is that constant?

Or does the code in /etc/resolutionfix do all the work for me, so it doesn't matter what's in /etc/videomode?_________________What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind

Dougal, I'm not sure if I'm answering your question properly, and I have to try and remember what I did back then.... yes, I think if you execute what is in /etc/resolutionfix, then the 1280x800 or whatever becomes a standard VESA mode, number 38, and running 'Xvesa -listmodes' will show it. 915resolution replaces whatever was the previous VESA mode for 38 with the new one.

But, you would have to go through ddcprobe first to probe the monitor. In the case of my laptop, only 1280x800 is returned as a valid mode by the monitor probe. Though, other VESA modes do work.
Basically, LCD displays have jst the one mode that is native and is what they should run at, particularly laptops. Color depth can be changed though.

Just to make sure, though: should I only offer the user only the native resolutions of his screen? If your lcd is wide-screen, it doesn't really make any sense giving the "normal" resolutions..._________________What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind

Dougal, yes, native resolutions only -- that's why I got confused with the 28th April version. But you would still have to cater for failed probing that doesn't return enough modes -- maybe, as was suggested, another button "Show more modes" -- but too many buttons can become confusing, also 'dialog' is limited to three buttons.

Note, in the version I attached earlier, I removed 'root=/dev/ram0' -- perhaps you could make this a variable, read /etc/puppyversion, if you want the script to work with 2.16 and earlier pups.
Although, it seems root=/dev/ram0 just gets ignored anyway in 2.16.

Note, in the version I attached earlier, I removed 'root=/dev/ram0' -- perhaps you could make this a variable, read /etc/puppyversion, if you want the script to work with 2.16 and earlier pups.
Although, it seems root=/dev/ram0 just gets ignored anyway in 2.16.

I assume you are referrign to the installer... Yes I've been meaning to do it, but haven't got around to it yet. Maybe today.

I've updated my Xvesawizard and the video-wizard to work with 915, see the first post.

Here's also a modified xorgwizard (based on the last "stable" one) that uses the Xvesawizard (note that the video-wizard is still used, when changing resolution from within X (when you're already using xvesa).

Dougal, yes, native resolutions only -- that's why I got confused with the 28th April version. But you would still have to cater for failed probing that doesn't return enough modes -- maybe, as was suggested, another button "Show more modes" -- but too many buttons can become confusing, also 'dialog' is limited to three buttons.

What about adding the option "Show more modes ..." to the end of the list of native resolutions? When choosing this option then a warning message will be displayed:

I noticed that the xorg.conf.new file (generated by Xorg when it probed my HW) contained more modules to load than are included in the final xorg.conf.
The reason for that is that those modules are ignored and what you get in xorg.conf are just a few constant modules which come in xorg.conf0.

So I modified the wizard to add any modules listed in xorg.conf.new which aren't in the list of defaults.

I don't know how exactly we benefit from this... I don't have any info on these modules, but I tend to assume that if Xorg listed them, thay might be useful...
(in my case only two additional modules were listed, "dri" and "record", both of which were not loaded before hand -- never appeared in /var/log/Xorg.0.log)

Note that this tarball also includes a modified xorg.conf0, which should go in /etc/X11/. (if you want to go back to the old version of the wizard, you will have to restore both files, from /initrd/pup_ro2)

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