(old)Puppy Linux Discussion Forum

Posted: **Tue 11 Oct 2011, 13:22**

sc0ttman wrote:Boot with pfix=usbsave to get PUPMODE 13 on HD frugal installs

UGH...
Does this mean I'd need to MANUALLY enter this command at EVERY bootup?
Or is there a way to have it done automatically at each bootup [of a live CD with pupsave file]?

p.s I'm off to London tomorrow to visit my son [who has a Lupu-526 CD], but will take a copy of my 526 lupusave on a Flash Drive, and attempt to continue posting from there on his PC.

Posted: **Tue 11 Oct 2011, 13:53**

Hi Mick,

01micko wrote:Hi Charlie,
Strange your siliconmotions issue still as the pet I made for you and Indian is included.

Hmm...this post several times re-edited as I could not get reproducible results and a stable savefile;
«stable» is meant that the X desktop that comes after have ran xorgwizard is reproducible, and uses the siliconmotion driver + the «be» locale.

Instead what is only reproducible when booting fresh (pristine) on slacko 5.29.5 is:
- X desktop starts automaticaly OK with driver = vesa + fr_belgium keyboard if the <Probe> option is activated;
- if doing <Choose> , then xorgwizard displays the drivers full list; there the siliconmotion driver choice and <Test_X_now> brings return to the prompt; doing xwin returns to the prompt again + message «Starting X, specs...If X failed to start, type "xorgwizard" to setup X».
- /usr/lib/x/drivers and /usr/lib/x/drivers-backup folders are empty;

Later tests (before issuing slacko RC) with the xorg4charlie_indian.pet installed brought the drivers list as shown below when running xorgwizard and doing <Choose>. Choosing then siliconmotion and doing <Test_X_now> brings X to start. That 2-drivers list never got displayed using slacko 5.29.5.

Note: in slacko5.29.5 siliconmotion_drv.so and vesa_drv.so are still the earlier version (resp 109K and 21K: later are 119K and 26K sized).

Attached are screenshots of a current slacko5.29.5 with /usr/lib before (orange) and after (green) having copied the /usr/lib/x and /usr/lib/xorg contents from a fixed slackoB2.
Original 5.29.5's folders have been renamed /usr/lib/xX and /usr/lib/xorgX.

Here is a link for downloading a nice working slackosave-4992becy.3fs (except that locale is 'us' which has been updated for slacko5.29.5 - size= 64MB:
http://www.datafilehost.com/download-8b3e6f81.html

Hope this could help!

Cheers, charlie

Posted: **Tue 11 Oct 2011, 15:21**

Sylvander wrote:
sc0ttman wrote:Boot with pfix=usbsave to get PUPMODE 13 on HD frugal installs
UGH...
Does this mean I'd need to MANUALLY enter this command at EVERY bootup?
Or is there a way to have it done automatically at each bootup [of a live CD with pupsave file]?

p.s I'm off to London tomorrow to visit my son [who has a Lupu-526 CD], but will take a copy of my 526 lupusave on a Flash Drive, and attempt to continue posting from there on his PC.

If I get you. When you visit your son then you boot up like this

will take a copy of my 526 lupusave on a Flash Drive

then you can put it on the boot code for the usb.

Is it iso linux? or do you have grub4dos on the usb?

I try to show on both. I almost never use usb so not sure.
I take an official code as example

Code: Select all

default puppy
display boot.msg
prompt 1
timeout 50

F1 boot.msg
F2 help.msg
F3 help2.msg

label puppy
kernel vmlinuz
append initrd=initrd.gz pmedia=usb pfix=usbsave

But note this it does say:

scottman wrote:Boot with pfix=usbsave to get PUPMODE 13 on HD frugal installs

So does that really apply to CD or DVD or USB? it says it only apply to frugal on HDD

So maybe me misunderstand what is supposed to happen?

if you have grub4dos then you add it here

Code: Select all

 title Slacko-5295 B5 
  root (hd0,0)
  kernel /slacko5295/vmlinuz psubdir=slacko5295 puppy pfix=usbsave
  initrd /slacko5295/initrd.gz

So if I get it then you boot on your son's puppy but want to boot fresh and save on your usb but not boot from the usb then you have to edit by hitting e during the 5 seconds at the start. Ot edit his boot code

Posted: **Tue 11 Oct 2011, 15:36**

01micko wrote:
jim3630 wrote:01micko,

this problem is beyond my skill level and looks like it is not my hardware since in other pups once the speakers are chosen via multi-sound card wizard on reboot sound continues to go to those speakers. have looked in other pups multi-sound card wizard and the choices are the same as in the pic of my first post here in RC. any ideas?
Was this a problem in any of the betas? If not I have a possible fix. Let me know please before I post it. Thanks.

01mikco yes a problem I reported in prior betas.

Posted: **Tue 11 Oct 2011, 16:56**

When the final is released, what will it be called?

Posted: **Tue 11 Oct 2011, 16:57**

DaveS wrote:When the final is released, what will it be called?

Awesome?

Posted: **Tue 11 Oct 2011, 16:59**

tubeguy wrote:
DaveS wrote:When the final is released, what will it be called?
Awesome?

OK.. we go with that

Posted: **Tue 11 Oct 2011, 17:01**

There is a report in the Printers section that a full install of Slacko5295RC may be making a /tmp folder that is lacking a full set of write permissions.

Can anyone confirm this?

Posted: **Tue 11 Oct 2011, 17:14**

When the final is released

It may be great- even I like it - but still too many issues. Far too early. Couple of RC s, I'd say. Aim for perfection!

Posted: **Tue 11 Oct 2011, 17:28**

Sage wrote:
When the final is released
It may be great- even I like it - but still too many issues. Far too early. Couple of RC s, I'd say. Aim for perfection!

But what is it going to be called? Slacko? Spup? Spup5?

Posted: **Tue 11 Oct 2011, 17:56**

DaveS wrote:When the final is released, what will it be called?

I thought the final release would become Puppy Linux 5.3

Posted: **Tue 11 Oct 2011, 22:46**

Sylvander wrote: p.s I'm off to London tomorrow to visit my son [who has a Lupu-526 CD], but will take a copy of my 526 lupusave on a Flash Drive, and attempt to continue posting from there on his PC.

About save files.
A save file made on a computer has settings for that computer.
If used on another computer it will probably have problems.

Posted: **Tue 11 Oct 2011, 23:08**

My problems with rc.shutdown were due to a corrupted rc.shutdown file and any attempt to fix it was not done due to that.
I ended up copying it from the original in the SFS and that cured it.
The only other change I made was to set the save session value to zero so as to keep the session from being saved while I was running Slacko.
Also when I would clink on the Save button on the desktop, the popup message of "Saving Ram to file..." never would disappear.

That I still have to check.

Posted: **Tue 11 Oct 2011, 23:11**

bigpup wrote:About save files.
A save file made on a computer has settings for that computer.
If used on another computer it will probably have problems.

So far my experience shows that not to be the case.
e.g. When I copied a couple of my own pupsave files [for lupu-526 and Midnightsun-003-tmix made on my desktop PC] to my sons laptop...
They asked me to make new and suitable configuration choices to suit the different hardware [e.g. screensize]...
And then worked perfectly.

He then left for London taking the laptop with him [plus the copies of the appropriate Puppy CD's].
So his laptop is already functioning well with those Puppies using older copies of my pupsave files.
My latest lupusave file includes a functioning copy of the Puppy Phone program, which is why I want to take it.

Posted: **Wed 12 Oct 2011, 00:04**

# uname -r
2.6.39.4

A problem is that Barry uses the same name '2.6.39.4' for Racy-5.1.101, Pemasu in Dpup Exprimo 5.X.8 SMP and Slacko also has same name.
Three different kernels in the same name...

Posted: **Wed 12 Oct 2011, 00:12**

8-bit wrote:Is anyone else having problems with the desktop SAVE button application?
I have a 512 meg save file and after the initial message displays and then the Saving Ram to file.... appears, it never disappears and I do not know if the save to USB has completed.

Sometime occurs. I suspect a woof bug.

Posted: **Wed 12 Oct 2011, 00:21**

I thought the final release would become Puppy Linux 5.3

It will.

Lucid was briefly known as 'Meerkat' as it developed
as some binaries came from Ubuntu 'maverick meerkat'
'Wary' for pre 2000 hardware has gone into Beta and is Puppy compiled in Puppy
http://bkhome.org/blog/?viewDetailed=02538
'Slacko' was originally known as 'Spot'
These are developer code names
Any Puppy using Slackware binaries during the Woof compilation process is known as an Spup - just as Lucid is a Upup

Slacko will as far as I know, become Puppy Linux 5.3 'Slacko'
or Slacko Puppy 5.3 or just Puppy Linux 5.3
http://puppylinux.org/wikka/Puppy53

Puppy
Awesome Linux

Posted: **Wed 12 Oct 2011, 00:22**

The Nvidia driver Slaco provides is lacking glx support.

I have made Nvidia driver with glx in SFS.
nvidia-glx-sdl-285.05.09-slacko.sfs for both kernel 2.6.37.6 and 2.6.39.4.
http://www.murga-linux.com/puppy/viewtopic.php?t=72405
It also contains OpenGL and replaces the SDL in Slaco. The SDL in Slaco main sfs is incompatible with OpenGL.

Posted: **Wed 12 Oct 2011, 00:27**

shinobar wrote:# uname -r
2.6.39.4

A problem is that Barry uses the same name '2.6.39.4' for Racy-5.1.101, Pemasu in Dpup Exprimo 5.X.8 SMP and Slacko also has same name.
Three different kernels in the same name...

Guess it would really be confusing if I uploaded Three_Headed_Dog with 2.6.39.4 too....

Posted: **Wed 12 Oct 2011, 00:35**

James C wrote:
shinobar wrote:# uname -r
2.6.39.4

A problem is that Barry uses the same name '2.6.39.4' for Racy-5.1.101, Pemasu in Dpup Exprimo 5.X.8 SMP and Slacko also has same name.
Three different kernels in the same name...
Guess it would really be confusing if I uploaded Three_Headed_Dog with 2.6.39.4 too....

Ok, 4 (or more) kernels!
Think they are better to be '2.6.39.4-s' or something.

(old)Puppy Linux Discussion Forum

Slacko RC

kernel naming

SAVE freaze?

Nvidia driver and SDL in slaco

Re: kernel naming

Re: kernel naming