Pup214R v1.00 - Puppy Linux 2.14 Revisited, is now available

[pdrito]

I try Puppy Linux 2.14 Revisited on a Live CD, multisession.

First boot, all went OK. Nice load, and set-up of network and xorg went Ok , withouth problem.

Then save all the stuf to CD, All process OK.

Second boot.
Start normal till reach this point:

Coping /pup_214R.sfs to tmpfs ....mounting on (/initrd)/pup_ro2....done

Mounting 20017-12-01-16-41 on /pup_rw .... failed

That must be a problem with the multisession code... I modified it but it never got tested. I'll have a look into it.

Hi Dougal,

This is just to remember you to not forget this multisession issue.

Do you have and idea for when will release v2 of 2.14R (or another update name) ? I am a little anxius to use this distro

pdrito.

[SantaClause]

i am curious how well does this version do a "full install" now?

I posted on this thread an updated installer that should get the full install fixed.

also, is there .pet support? .pup? anything that needs to be known by someone used to 3.0* or even 2.16+?

Yes.

also, there needs to be an updated iso for all the fixes that have happened so far.

Pakt has set the date for the first update to the 15th.

one other thing, for future reference, is there a way to "update" each new version of 2.14R from a full install?

We will have "service packs" that can be used instead to apply the changes.

sweet. Around the 15th is about the time i will be able to test out this version so that works out perfect. as for "service packs", excellent idea. i assume these "service packs" will be a .pet with all packages that need updating within it with a script to install each so that the package manager will notice the updates?

cant wait to try it

[rerwin]

dougal, thanks for including the "dubious Toshiba HW" fix. However, one of the models that uses the MagicGraph video adapter has a screen size of 800x600, but does not indicate that in its ddcprobe output. (The larger-screen models appear to also support 800x600 but omit the "timing:" statement.)

In one of my early versions of the fix I added a line to append a "timing: 800x600..." statement to the ddcprobe.txt file, but only if one was not already present. That was because the Trident adapters do include that line, so no need to duplicate it.
Richard

[Dougal]

Before I backstep? to 2.14R. Does it have win-modem support like 2.17 & 3.01 does.

I'm afraid not...

[Dougal]

This is just to remember you to not forget this multisession issue.

I haven't forgotten, I thought you did...

It would help me if you could get me some more information:
- try booting with "pfix=debug" and see what kind of messages you get before it stops.
- maybe try mounting that cd and see what's on it -- maybe the saved foler has a bad name.

[Dougal]

In one of my early versions of the fix I added a line to append a "timing: 800x600..." statement to the ddcprobe.txt file, but only if one was not already present. That was because the Trident adapters do include that line, so no need to duplicate it.

Ok, I'll add that.

[Dougal]

I've got here a couple of little updates people might want to test.

- I've updated jwmconfig so it (hopefully) works ok with adding/removing etc. panel buttons. I've also added to it a dialog for modifying the clock format (but I need feedback on the offered formats -- any more suggestions?).

- I've updated the grubconfig script and the installer, so hopefully it would work ok with a frugal install (when grub isn't previously installed).

[pdrito]

Hi Dougal,

I load Pup214R v1.00 with pfix=debug command.
The following message come:
"Could not find kernel image for pfix=debug"

After that, the normal installations messages comes,
and the installations stop after the message.

mounting 2007-12-10-01-13 on /pup_rw ......... failed

------------------------------
Mounting the CD we can see all the normal files and directorie:
boot.cat
boot.msg
f2
initrd.gz
isolinux.bin
isolinux.config
pup_214.sfs
zdrv_214.sfs
vmlinuz
2007-12-10-01-13 [directory]
inside directory:
sub-directories: dev-etc-lib-root-usr

The only strange thing is on this usr sub-directory:
inside usr I found the file X11R7/bin/X , this X is a red colour filename of a yellow triangle icon with an " ¡ " on it. (meaning missing item ?).

Ok , that was I found till now.

pdrito.

[Dougal]

I load Pup214R v1.00 with pfix=debug command.
The following message come:
"Could not find kernel image for pfix=debug"

That's odd. I wonder what it means...

The only strange thing is on this usr sub-directory:
inside usr I found the file X11R7/bin/X , this X is a red colour filename of a yellow triangle icon with an " ¡ " on it. (meaning missing item ?).

That's fine: it's the link created to Xorg when the xorgwizard was run.

I'll look at the init script and see what I can find.

[Dougal]

In one of my early versions of the fix I added a line to append a "timing: 800x600..." statement to the ddcprobe.txt file, but only if one was not already present. That was because the Trident adapters do include that line, so no need to duplicate it.
Richard

I think that is actually wrong.
The "timing" lines list the modes supported by the screen and in the case of laptops it usually will be only the one, native, mode.
The part of ddcprobe output related to your adapter is the first part of ddcprobe output (that's why when you get only half the output and "edidfail" it means that it couldn't get to your screen).
What I did is make sure that Xmodes (which is normally created by Xvesa -listmodes) has got the 800x600 and 1024x768 modes, thus the user will be offered them, being told "ok with card, maybe NOT ok with screen".

[Dougal]

I load Pup214R v1.00 with pfix=debug command.
The following message come:
"Could not find kernel image for pfix=debug"

It occured to me that maybe you tried "pfix=debug" and not "puppy pfix=debug" and maybe it has some effect...

If you get it working, look in the output for the line

Code: Select all

PUPMODE=|13|

I think I found the problem and fixed it, but just to make sure...

[pdrito]

Shame on me. !!!

You are absolutly right: I forget to put puppy on the sentence puppy pfix=debug

So,
with the puppy pfix=debug command I found:

PUPMODE is :12: [yes , 12 and not 13. I checked 3 times]
Coping /pup_214R.sfs to tmpfs ...done
/mnt/dev_save2007-12-10-01-13 No such file or directory
etc etc.
e2fsch 1.40.2 (12-Jul-2007)
ext2fs_check_if_mount No such file or directory
etc. etc.

Hope this info are good to you.
And sorry again for my mistake.

pdrito.

[Dougal]

PUPMODE is :12: [yes , 12 and not 13. I checked 3 times]

Oh, now that I think of it, it would actually be 12... So I think we're ok and it's fixed.

[8-bit]

I have to say KUDOs to you on the desktop drive/dev icons and the mount/unmount that is part of them. Compared to Pmount and MUT, it just flat flys in mounting a drive or partition.
My question here is:
Will there be a pet of this addition that can be made available to users of other versions of puppy that would like to add it?
I have pup214r installed (full hard drive install) on an OLD Compaq notebook 133mhz, 1.2gig hard dirve, no eth0, no wifi, no CD drive.
But It is running in 32 megs physical ram!
Just thought you would like to know!

[gerry]

Do we actually need both:

Menu > setup > setup wizards > etc

and

Menu > setup> wizard wizard > etc

since the end result is essentially the same?

Also, Menu > system > Xpdq printer management

gets you to the Xpdq gui, but Printer > Add printer does not do anything. It only works if you come via a setup wizard. A bit of a downer if you try this approach first!

Gerry

[Dougal]

Do we actually need both:

Menu > setup > setup wizards > etc

and

Menu > setup> wizard wizard > etc

since the end result is essentially the same?

I don't understand what you mean... Do you mean having the wizards sub-menu and the WizardWizard?

[ttuuxxx]

Hi i just tried it and i think its excellent, Great job guys, Only problem so far that i've had is when i did a screenshot using mtpaint, I had like 20+mtpaint windows open automtically, i had ezpup3.0 running at the time and that was it, also when you use ezpup 2.17r4 or 3.0 the menus are broken, you only have 2 items in the start menu. And yes i did the fixmenus thing and got some missing folders, other then that i really do like this puppy sorry about the image quality but i used mtpaint to get that and tried to make it smaller with it and it became pretty crappy ttuuxxx

[gerry]

Hi Dougal... yes.

Gerry

[rerwin]

Dougal,
Thanks for clarifying the significance of the "modes:" and "timing:" statements:

The "timing" lines list the modes supported by the screen and in the case of laptops it usually will be only the one, native, mode.
The part of ddcprobe output related to your adapter is the first part of ddcprobe output (that's why when you get only half the output and "edidfail" it means that it couldn't get to your screen).
What I did is make sure that Xmodes (which is normally created by Xvesa -listmodes) has got the 800x600 and 1024x768 modes, thus the user will be offered them, being told "ok with card, maybe NOT ok with screen".

So my Tecra gets described correctly by your fix. However, without a 800x600 timing line, cherriepuppy's 800x600 Portege with the same adapter will not be given the 800x600 option. To condense his posts re my 1024x768 fix:

works on toshiba portege 7010ct except it says that 1024x768 resolution is available but the screen only goes up to 800x600.

ddcprobe shows following:
# ddcprobe
vbe: VESA 2.0 detected.
oem: MagicGraph 256 AV 44K PRELIMINARY
. . .
edid:
edid: 1 0
id: 5081
eisa: TOS5081
serial: 00000000
manufacture: 20 1995
input: analog signal.
screensize: 23 17
gamma: 1.000000
dpms: RGB, no active off, no suspend, no standby
timing: 720x400@70 Hz (VGA 640x400, IBM)
timing: 640x480@75 Hz (VESA)
#

The absense of a "timing: 800x..." line would prevent the wizard from offering the actual native resolution of that Portege. I expect that laptops considered for Puppy would support at least 800x600. So, the logic to add this line could be conditioned upon there being no higher-resolution "timing:" line.

My problem with what I call the "fill in the gaps" approach is that it must get it right for all affected adapters and screens, an open-ended maintenance issue. The solution I settled on simply takes the default used in the absense of (sufficient) screen information; that is the case here, although with 1024x768 screens, accepting the "8514A" 1024x768 line supplies the correct option. (With the "default" approach, we would not be discussing details of the FITG fix for 10-year-old laptops, conserving energy for the greater-impact stuff.)

BTW, dalderton's Toshiba TE 2000 produces:

oem: Trident CYBER 8820
. . .
timing: 720*400@70Hz (VGA 640*400, IBM)
timing: 640*480@70Hz (VESA)
timing: 800*600@72Hz (VESA)
timing:1024*768@87Hz Interlaced (8514a)
ctiming: 1280*1024@60
ctiming: 1600*1200@60
dtiming: 1024*768@74

telling me that it supports resolutions lower than native. But, for Puppy, I see no need to supply the lower resolutions if ddcprobe omits them.
Richard

[ttuuxxx]

so basically if its really nice, we can't jazzz it up a bit???