First Run Dialog for next Lucid Puppy

[shinobar]

Your(bigpup case) xrandr says 50 or 51Hz is the only available rate for 1280X1024.
Is the xranr wrong?

Yes!!

Thanks, bigpup.
Then our story becomes quite different.
Using the xrandr to change the resolution can be our mistake.

I have not truly been unaware with the xrandr limitation.
It strongly depends on the driver.

... The dialog of the Personalize Setting says:

If your desired resolution is not shown on the list, you have a chance with running the XorgWizard, and may need to choose the video driver.

That is all i can do at this point of time...
Any of good idea? > to all

[shinobar]

bigpup,
Your suggestion is welcome.
My thought is it can be another project and may take a long term.

I like to confirm, bigpup.
In your case, xorgwizard has no problem, and the problem is of the Video Resolution Changer(xrandrshell)/the Personalize Stting?

You can see my trial to change the resolution by GUI in Puppy-431JPqs3, a half year ago released. Same can be seen in the Browserlinux i remember.
At that time, i didn't use the xrandr.



In the LupQ i aborted it because touching the xorgwizard is hard.
But i like to try again in near future.

As for the Mobeus case, it is different.
i will upload the improved version in a couple of days.

Thanks to all.

[bigpup]

I like to confirm, bigpup.
In your case, xorgwizard has no problem, and the problem is of the Video Resolution Changer(xrandrshell)/the Personalize Stting?

Yes Xorgwizard works fine. However, to get a choice of refresh rate, you have to run Test after selecting a resolution.
Resolution Changer and Personalize Setting. No good, because of no adjustment for refresh rate.
This really got me in trouble in my early days of using Puppy Linux. Like I really know what I am doing now!
Thanks for putting up with my rant!

[bigpup]

shinobar,
About the resolution and refresh rate issue.
Using the First Run Dialog on different video hardware and with different video drivers made a big difference.
Example;
Nvidia NV 37GL Quadro pci-e in a dell.
ATI Radeon 2600 Pro in a home built.

Vesa driver
Nvidia Quadro -no settings looked good.
Ati Radeon -got settings I could use.

Video driver specific to video card
Nvidia Quadro -settings better but still not good.
Ati Radeon -got settings I could use.

Thanks for this, good feature on initial startup.

[shinobar]

shinobar,
About the resolution and refresh rate issue.
Using the First Run Dialog on different video hardware and with different video drivers made a big difference.

Thanks bigpup for the report.
Yes i know that is the limitation of xrandr.

[shinobar]

Hope to be this is the final for the stage 1.
See the top of this topic.

Ensure taking the lowest frequency for the refresh rate of the screen
to avoid the Mobeus case.
Support Xvesa and may run on any Puppy-4.x/5.x.

Thanks, Mobeus and to all.

[Mobeus]

Shinobar,

Good news: The firstrun dialog did offer and set a usable 1024x768 / 60 screen setting in Luci-233.

Bad news: Upon reboot the screen was black.

I am attaching the xorg.conf files and the xrandrindex file in case that will help.

This may not be relevant but, could the problem be in ~/.xinitrc?

[gcmartin]

Hmmm. Shinobar can either a display of the Hostname OR a hostname selection be added to your First Run Dialog before 5.2 goes "live". I think you see the advantage to this.

[shinobar]

Bad news: Upon reboot the screen was black.

I see. We need to rewrite /usr/sbin/xranrshel, and xorgwizard hopefully.
Thanks, Mobeus for this important report.

[bigpup]

Luci-233
First Run Dialog V1.0
Resolution issues still. Just letting you know that naming it Version 1.0 did not work. Good try!

X Server buttons.
Are they info of what you are using or selections to make?
Here is what I get;

[bigpup]

shinobar,
Resolution issue.
Could all the resolutions that come up on the list be set to have a refresh rate of 60HZ, Like locked setting? I think any monitor could handle that refresh rate, with no problems, for any resolution setting.
Just an idea for you to think about.

[shinobar]

Could all the resolutions that come up on the list be set to have a refresh rate of 60HZ, Like locked setting?

We know the xrandr reports wrog in many case.
So, the bigpup's proposal is very attractive.
I am not sure all or most of the hardwares can manage it.

The problem is how to organize the testers.

[bigpup]

Could all the resolutions that come up on the list be set to have a refresh rate of 60HZ, Like locked setting?

We know the xrandr reports wrog in many case.
So, the bigpup's proposal is very attractive.
I am not sure all or most of the hardwares can manage it.

The problem is how to organize the testers.

I have never seen specs, on a monitor, that did not list 60HZ as a refresh rate for any resolution. I think it is a standard supported by all.
From Wikipedia;

Windows XP, Windows Vista and Windows 7, set the default refresh rate to a "conservative" rate, usually 60 Hz.

(Why did my screen go black when I wrote that quote)?
My LCD monitor support suggests I use 60HZ refresh rate all resolutions.
All the resolution settings listed in my monitor manual have 60HZ as a setting.

The most common refresh rate for LCD monitors is 60 Hz. This normally cannot be changed for flat panel displays using Plug and Play settings.

Suggested refresh rate for CRT monitor at HP support how to in that other operating system.

[shinobar]

Bad news: Upon reboot the screen was black.

Fixed.
But note that the xranrshell nor xorgwizard are not yet fixed.
They still have a problem with selectiong the refresh rate with some hardware as Mobeus reported.

The proposal from bigpup (not rely xrandr refresh rate) is pending for this update, v1.1.

[Mobeus]

Success! No problems here with v1.1in Luci-234. Set to 1024x768/60, and retained it after reboot. Installed Xorg-High and still had the desired settings after rebooting.

FYI the v1.0 built in to Luci-234 gave a black screen after rebooting.

Congratulations!

[L18L]

firstrun-1.1
revised german translation attached

[01micko]

shino

On some thinking about fullstart..

This is all that is needed

Code: Select all

#!/bin/sh

. /etc/rc.d/PUPSTATE #get pupmode

if [[ $PUPMODE != 2 && $PUPMODE != 3 ]];then exit
	else 
	first-run.sh &
	#rm -f /$HOME/Startup/fullstart  #this file self destructs after first run
	chmod -x /root/Startup/fullstart ##change permission instead
fi

That way the code will only execute once in pupmode 2 and 3 only (full installs to fast and slow media respectively).

There is no need of the permission change in /usr/bin/first-run.sh... (unless of course this one is removed maybe more correct syntax that way )

Cheers

[shinobar]

On some thinking about fullstart..

Maybe playdayz mistook in packaging Luci-235.
My code in firstrun-1.1.pet, /root/Startup/fullstart:

Code: Select all

#!/bin/sh
[ -s /tmp/firstrun ] && chmod -x $0 && exit
firstrun
[ -s /tmp/firstrun ] && chmod -x $0

Seems tricky but may work.

EDIT: I forgot the detail of these scripts...
It is quite complex.
One thing i remember is the firstrun(countrywizard.qs) can be canceled with CTL-ALT-BS when trying new resolution.
Another, the delayedrun may change its sequence in the future... etc.
My thought, the delayedrun need not call the first-run.sh, but should launch the Startup scripts soon. It must be more simple with the variety of install style.

By the way, i see you use '[[ ]]'.
what is the difference from '[ ]'?
I am not familiar with '[[ ]].

[01micko]

Hi shino

Yes I use the [[ ]] to avoid "[; unary operator expected" error which occurs when using "not" operator... it's not fatal but it does produce an error. Also is necessary when testing 2 conditions with "&&" or "||".. (or even -a or -o).

Perhaps you are right that playdayz did misplace a file as we did discuss the full install earlier.

Also I agree with the delayedrun call not being a good idea. /root/Startup/* is executed just after and is very versatile. If you put "0_<scriptname>" in /root/Startup it gets priority.

Cheers

[shinobar]

Yes I use the [[ ]] to avoid "[; unary operator expected" error

Thanks mike for the lecture. Lastly I got it