(old)Puppy Linux Discussion Forum

shinobar wrote:Your(bigpup case) xrandr says 50 or 51Hz is the only available rate for 1280X1024.

bigpup wrote:I am Using 60HZ now.
Yes I can edit xorg.conf and make it 60HZ refresh rate at 1280X1024.
I can change it to 60HZ in xorgwizard.
I can change it to 60HZ by using the Nvidia X server settings program.

There lies fundamental problem as for the nvidia driver.
The xrandr reports wrong, and cannnot set 1280X1024@60Hz in this case.
Should use the Nvidia X server settings.

Attached ones are out of date.
Get the most recent version, firstrun-1.2.pet from here.
CHANGES (v1.1 to 1.2)
* Add support locales with '@', like 'fr_BE@euro'.
* Add hostname
* Improve resolution change. The fresh rate taken near 60Hz. Support nvidia driver.
* Work as a clone of the 'Resolution Changer', xrandrshell.
* Dialog layout

@playdayz
The /usr/sbin/countrywizard and /usr/sbin/xrandrshell to be replaced with a link to the same /usr/sbin/countrywizard.qs. (done with pinstall.sh)
They act as the clone of the each functions.

Investigating the refresh rate issue, i found the xrandr cannot manage it.
In the firstrun-1.2, i take the nearest to 60Hz from the list the xrandr gives.
Because it may be the safest. But note that the xrandr do not always work properly.

If you want precise refresh rate, you need to try the xorgwizard, or manually edit the xorg.conf.

As for the 'nvidia' driver, xrandr is wrong at all.
So the firstrun-1.2 detects the nvidia driver and offers 'NVIDIA X Server Settings' instead using xrandr.

That is what i did in the firstrun-1.2 as for the refresh rate.

Sorry if this was already answered.. and if this is a hijack..

I have installed firstun 1.2 in a puppy 4.2 system (turbopup/puppy arcade)..
I want to remaster it.
The firstrun GUI works well, it changes the settings correctly.

But the 4.2 system needs to be tweaked for more user friendly experience.
By default, the boot to X settings of 4.2 do not work perfectly with firstrun...

So... Here's my questions..

1. How do I skip the old (classic) ncurses mouse wizard, keyboard, xorgwizard, etc?
I want to boot straight to the desktop, then use firstrun...
Can this even be done in puppy 4.2?

Also, I want to stop the Xvesa resolution changer from starting, when users boot into an Xvesa desktop..
How do I stop the Xvesa resolution changer from starting up when Xvesa loads up?

sc0ttman wrote:Sorry if this was already answered.. and if this is a hijack..

I have installed firstun 1.2 in a puppy 4.2 system (turbopup/puppy arcade)..
I want to remaster it.
The firstrun GUI works well, it changes the settings correctly.

But the 4.2 system needs to be tweaked for more user friendly experience.
By default, the boot to X settings of 4.2 do not work perfectly with firstrun...

So... Here's my questions..

1. How do I skip the old (classic) ncurses mouse wizard, keyboard, xorgwizard, etc?
I want to boot straight to the desktop, then use firstrun...
Can this even be done in puppy 4.2?

Also, I want to stop the Xvesa resolution changer from starting, when users boot into an Xvesa desktop..
How do I stop the Xvesa resolution changer from starting up when Xvesa loads up?

Thanks sc0ttman and gaylesmith.
There is another topic, but maybe outdated.
The direct desktop in Lucid 5.1.x uses recent Xorg server.
But also we can manage with old Puppy as well thanks to Xvesa.
http://www.murga-linux.com/puppy/viewtopic.php?t=51630

shinobar wrote:

sc0ttman wrote:1. How do I skip the old (classic) ncurses mouse wizard, keyboard, xorgwizard, etc in 4.2?
I want to boot straight to the desktop, then use firstrun...

Thanks sc0ttman and gaylesmith.
There is another topic, but maybe outdated.
The direct desktop in Lucid 5.1.x uses recent Xorg server.
But also we can manage with old Puppy as well thanks to Xvesa.
http://www.murga-linux.com/puppy/viewtopic.php?t=51630

OK thanks, I saw that, but I want 4.2 to boot straight to Xvesa desktop and show the Firstrun1.2 dialog.. Not firsetsetup 1.9en..

How do you recommend that I make my new 4.2 boot straight to Xvesa, then show only firstrun1.2?

I will follow this quide as usual, however..

I have questions about what I can do after step 4 (install firstsetup)...
(Before I restart X and run firstsetup...)

1. Can I remove '/root/Startup/firstsetup', and '/usr/bin/firstsetup'?
Then symlink usr/sbin/firstsetup to '/usr/bin/firsrun'? (to be safe)

2. Do I need to run firstsetup before I remaster?
If not, do I need to restart X before I remaster?

Thanks...

Just a question, does it take command line arguments? Like "pkeys=us"?

sc0ttman wrote: I want 4.2 to boot straight to Xvesa desktop and show the Firstrun1.2 dialog.

Uploaded quicksetup-1.0-p4-xvesa.pet for Puppy-4.x.
http://www.murga-linux.com/puppy/viewtopic.php?t=51630

@Shinobar this is a very crafty tool for configuring a PUP at desktop startup. Its name does not it justice for what it contributes...."System Configuration".

One item that seems to be a constant question is "what WM is running?"

Understanding that your plate is full, I do have one question that might eliminate that question. Could your system configuration tool display the running WM name in its Header bar or somewhere on the screen?

Just an idea.

gcmartin wrote:One item that seems to be a constant question is "what WM is running?".

Good point, gcmartin.

Your request is reasonable on Puppy's having multiple window managers.
It is the matter of the developers who provide multiple window managers in their distribution.
As for Luci, it offers the 'WM Switcher' by mick, i am not sure it is enough or not.
There are many configuration tools found in the menu, but some works and some doesn't because they are not for the current window manager.

I hope more discussions in each distributions on that issue.

The version bundled with the current Luci works nicely, although en_GB isn't listed in the Main Language dropdown list. Typing it into the box using the keyboard does work, however. Speaking of keyboards, that keyboard test box that comes up is a nice touch.

I too would like to see a refresh rate option as I'm using a ViewSonic E70fSB (17" CRT) but 60Hz is a sensible compromise and as you say I can change it myself later with the Xorg Video Wizard.

Jades wrote:en_GB isn't listed in the Main Language dropdown list. Typing it into the box using the keyboard does work, however.

Yes you can. But also you can select 'English' from the dropdown list.

As for the refresh rate, i would not support further because the xrandr is not reliable. I suppose you are better to edit the xorg.conf manually.

I suppose you are better to edit the xorg.conf manually.

Is there any way of a bash script editing it for users? It could be a simple script that if it has any problems it tells the user what to do.

shinobar wrote:

Jades wrote:en_GB isn't listed in the Main Language dropdown list. Typing it into the box using the keyboard does work, however.

Yes you can. But also you can select 'English' from the dropdown list.

I know, but IIRC that (en) uses US English spelling. Interestingly, when my machine is set to en_GB the option for en_US isn't listed in Personalize Settings.

shinobar wrote:As for the refresh rate, i would not support further because the xrandr is not reliable.

That's possibly a side-effect of some hardware (either the monitor or the graphics card) not supporting DDC or EDID properly. According to the Wikipedia article on DDC some KVM switches can interfere with the signal,

shinobar wrote:I suppose you are better to edit the xorg.conf manually.

I set it manually to 1024x768@85Hz using the Resolution Changer from the Xorg Video Wizard, but I know what settings my ViewSonic E70fSB is capable of. I've just tried xrandr on Merlin and all of the values shown are correct for my system.

Both of these issues are really just minor niggles, I'm very impressed with the First Run dialog.

Thanks, Jades.
As for the refresh rate, i am now pending because it strongly depends on the graphic drivers and the xrandr is not reliable. If another measure exists, please manage it with them.

Jades wrote:

shinobar wrote:

Jades wrote:en_GB isn't listed in the Main Language dropdown list. Typing it into the box using the keyboard does work, however.

Yes you can. But also you can select 'English' from the dropdown list.

I know, but IIRC that (en) uses US English spelling. Interestingly, when my machine is set to en_GB the option for en_US isn't listed in Personalize Settings.

If you select 'en English' from the pulldown at the 1st dialog, the 2nd dialog appears and you can select en_US,en_GB, en_AU, and etc.
You can also enable UTF-8 encoding with marking on the checkbox.
I know it is somewhat confusing. Do you have any idea? --> @ to all the readers

Regarding the UTF-8 encoding, it is an option for English.
For French is the same, but associated '(Reccomended)'.
If you select Russian, there are no option, but forced UTF-8 encoding.
I am not sure these rules are proper. Give me your advice --> @ to all the readers

shinobar wrote:

Jades wrote:IIRC that (en) uses US English spelling. Interestingly, when my machine is set to en_GB the option for en_US isn't listed in Personalize Settings.

If you select 'en English' from the pulldown at the 1st dialog, the 2nd dialog appears and you can select en_US,en_GB, en_AU, and etc.

So it does - I didn't actually think of checking that option so just typed en_GB to see what happened. I can confirm that selecting 'en' from the first menu and then 'en_GB' from the additional window does have the desired effect.

shinobar wrote:You can also enable UTF-8 encoding with marking on the checkbox.

I leave it switched off myself, and use good old fashioned iso-8859-1 (Western European) on my websites. Main reason why I do it is backwards-compatibility.

shinobar wrote:Regarding the UTF-8 encoding, it is an option for English.
For French is the same, but associated '(Reccomended)'.
If you select Russian, there are no option, but forced UTF-8 encoding.
I am not sure these rules are proper. Give me your advice --> @ to all the readers

The most obvious reason for it not being mandatory for en_GB is that is probably that special characters are rarely used in that language and any that may turn up are covered by iso-8859-1 Western European. Similar reasoning probably goes for most French use. I'm not sure which character set is most common in the USA and Canada but it probably wouldn't cover all of the special characters in other encodings.

Regarding Russian, there is iso-8859-5 for Cyrillic alphabet but presumably UTF-8 is considered to be a better choice.

The Wikipedia article on UTF-8 may be of use. In general, it seems that the key reason why it's recommended is that it has all of the various special characters in it rather than a subset as with the older iso character encodings.

firstrun-1.4.pet is released.
May work on any Puppy-4.2x/5.x. Not tested on Puppy 4.1x and older.
Included the new the script /etc/rc.d/rc.country, supports '*.UTF-8' for the locale name.

I tested 'firstrun' in luci241 over the weekend and it works
perfectly changing languages and keyboard layouts.

I have one small suggestion...

When choosing the English language it can be easy to
overlook the many versions of English that are available.
So I have a small change that might help new users to look
at the list of language variants.


________________________________________________

Hi shinobar

I am in the process of adding firstrun 1.4 to a version of spup051 (that is already loading and running totaly in ram from a usb stick without a save file)

I have added all the firstrun files (in the right directorys) to the sfs except pinstall.sh and puninstall.sh, and it seems to be working great. I just dont know how to stop the kernel from asking for options to be set, so it boots straight to the desktop. Do you have any ideas?

with the current version to boot straight to the desktop I am initially creating a save file and copying the relevant config files from the save file to the sfs, but this is making the program only work on certain hardware.

Thanks
Stripe

Stripe wrote:with the current version to boot straight to the desktop I am initially creating a save file and copying the relevant config files from the save file to the sfs, but this is making the program only work on certain hardware.

It is a topic of Quickset Puppy:
http://www.murga-linux.com/puppy/viewtopic.php?t=51630
There i released a kit for Puppy-4.x with Xvasa. You can apply this method with copying some files from the save file which is set up with Xvesa 800x600.

For the Puppy without Xvesa, you can see an example in LupQ. You can apply the same thing if the Puppy has the X-server version 1.7.x.
Type 'Xorg -version' in a virtual terminal.

The detail shall be discussed at the Quickset Puppy topic above.