puppy boot options.

Using applications, configuring, problems
Message
Author
sindi
Posts: 1087
Joined: Sun 16 Aug 2009, 13:30
Location: Ann Arbor MI USA

Booting puppy 1.07 without X

#21 Post by sindi »

Trying to boot Puppy 1.07 off CD. Last version with OSS sound and first version with Xorg.
Toshiba Satellite 1805-S203 which when booting later puppies tells me Xvesa will not work.
Xorg does not work on here - gives me a blinking cursor on a black screen but no prompts
and no X. I can type characters, or move the cursor around with arrow keys.

The laptop has Ali5451 (trident) sound which is not working with ALSA. I got a much older
HP Omnibook working with OSS sound in Puppy 1.07 when ALSA failed. Puppy 1.07 (booted
to an older laptop) has Ali5455.o.gz, which I want to try on the Toshiba.

When I boot 1.07 I get five choices (whether to use a save file, ACPI, etc.).

I tried
boot: vmlinuz,pfix=nox

Could not find kernel image: vmlinuz,pfix=nox

How can I boot Puppy 1.07 without X? I ran across mention that pfix=nox works only on puppy
2 or later. Do I need to take apart and rewrite initrd.gz or equivalent?

Wognath
Posts: 423
Joined: Sun 19 Apr 2009, 17:23

psave parameter

#22 Post by Wognath »

The kernel line parameter psave (see http://puppylinux.org/wikka/BootParametersPuppy) is not recognized in all versions of puppy, but it can be activated using CatDude's edits of the init script contained in initrd.gz, based on the idea of forum member Crash.
How to unpack & repack initrd.gz
CatDude's edited init script (second post here) works as is in unicorn-6.0 and in unicornpup (cutdown version of Tahrpup), and might work in others, or else the edits can be added to your init script.

User avatar
gychang
Posts: 414
Joined: Sat 29 Nov 2008, 20:30
Location: San Diego, CA

does not work well puppy pfix=ram, tahrPup

#23 Post by gychang »

when I boot with a USB with the same puppy already installed on HD (frugal), it almost always find the sfs on the HD!!.

is there a problem or am I doing something wrong?

User avatar
gychang
Posts: 414
Joined: Sat 29 Nov 2008, 20:30
Location: San Diego, CA

#24 Post by gychang »

live wrote:I propose to add one option to the boot menu.

"Boot with sfs on current media"

This way when booting starts, puppies wouldn't be looking for all partition, but only on the booting one, which would result in a faster boot.
this is excellent idea, since puppy pfix=ram usually does not work.

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

Re: does not work well puppy pfix=ram, tahrPup

#25 Post by bigpup »

gychang wrote:when I boot with a USB with the same puppy already installed on HD (frugal), it almost always find the sfs on the HD!!.

is there a problem or am I doing something wrong?
puppy pfix=ram is the command to boot and not use any save file or folder.

If the Tahrpup sfs file is on the hard drive, the boot process will use it, because the hard drive is faster to read from.
Thus, you get a faster boot.

The Tahrpup sfs file on the USB and the one on the hard drive are the same file.
Those sfs files never change.
They are only used as read only files.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

User avatar
gychang
Posts: 414
Joined: Sat 29 Nov 2008, 20:30
Location: San Diego, CA

Re: does not work well puppy pfix=ram, tahrPup

#26 Post by gychang »

bigpup wrote:
gychang wrote: puppy pfix=ram is the command to boot and not use any save file or folder.

If the Tahrpup sfs file is on the hard drive, the boot process will use it, because the hard drive is faster to read from.
Thus, you get a faster boot.

The Tahrpup sfs file on the USB and the one on the hard drive are the same file.
Those sfs files never change.
They are only used as read only files.
thanks for the info. Is there a command on boot to only load files on the USB stick when HD also contains same version from frugal install?

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#27 Post by rcrsn51 »

@gychang: Please post the syslinux.cfg or menu.lst file from your USB stick. You probably want the option

Code: Select all

pmedia=usbflash

User avatar
gychang
Posts: 414
Joined: Sat 29 Nov 2008, 20:30
Location: San Diego, CA

#28 Post by gychang »

rcrsn51 wrote:@gychang: Please post the syslinux.cfg or menu.lst file from your USB stick. You probably want the option

Code: Select all

pmedia=usbflash
thanks!!

User avatar
Mike7
Posts: 400
Joined: Tue 19 Feb 2013, 00:31

#29 Post by Mike7 »

Hi, all.

Rhadon's install for Carolite-1-2 worked (copy files from iso then use grub4dosconfig), but I don't understand how to use the advanced grub4dos menu, nor how to add bootcodes. These are my main questions:
  • -- Does Carolite install itself in RAM automatically at boot, or does this have to be commanded at boot? (In Puppeee4.4 it's an option on the boot screen.)

    -- Aren't these frugal-install Puppies all supposed to run in RAM?

    -- If Carolite isn't installing itself to RAM at boot, should I put a copy2ram bootcode in to force it? (Is copy2ram the right code for this?)

    -- How (where) do you add bootcodes: grub4dos commandline at boot?, in a particular boot config file? (what file?), after Carolite boots?

    -- Is there a bootcode to activate zswap? Is that needed to turn on zswap (which I was told is a good thing on pendrives)?

    -- Any other boot codes I should add?

    -- When should a PBS bootloader be used? (When I installed a Puppy to a 4gb ext2 partition (sba1) on an 8gb stick (sba), it would only boot if the bootloader was installed in sba, not in sba1 (the Puppy partition). Why? Can someone explain it to me, when and how to use PBS?

    -- What is the terminal command for viewing all the installed bootcpdes and kernel parameters?
Thanks.

Mike
Carolite-1.2 w/FF38 on bootable 16G flash drive; Asus eeePC 1000HA, Atom CPU, 2G RAM, 160G HDD.

User avatar
MrAccident
Posts: 361
Joined: Mon 31 Mar 2014, 20:53

#30 Post by MrAccident »

I'm posting here because I can't find a way to make a new topic in the forum. Please tell me how to do that.

starhawk
Posts: 4906
Joined: Mon 22 Nov 2010, 06:04
Location: Everybody knows this is nowhere...

#31 Post by starhawk »

Do you see the "post reply" button...?

Look just to the left of it, you should see another button... it will be very helpful...

;)

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#32 Post by bigpup »

MrAccident wrote:I'm posting here because I can't find a way to make a new topic in the forum. Please tell me how to do that.
Go to the section of the forum you want to post in.
Click on new topic.
Your post will be a new topic in that section of the forum.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

User avatar
MrAccident
Posts: 361
Joined: Mon 31 Mar 2014, 20:53

#33 Post by MrAccident »

OK; today I see it. Pretty sure it wasn't there yesterday. Thanks.

gcmartin

Puppy Linux Boot Parameters & General Linux Boot Parms

#34 Post by gcmartin »

First
In reviewing this page which supports Puppy Linux boot parameters, I can find no mentions of the syntax requirements or defaults for the Puppy Boot Parameters themselves (those are the options BEFORE the equal sign).

Questions
  • Are boot options case sensitive? OR is case NOT a factor and spelling is the only factor?
    What are the default values?
Next
In reviewing this page which supports Puppy Linux boot parameters, I can find no mentions of the case requirements for the General Boot Parameters shown. The parms begin their topic area in UPPER case while the supporting paragraphs show lower case. Defaults, on this page, are usually shown.

Questions
  • Are these boot options case sensitive? OR is case NOT a factor?
Last
There is a 2nd, separate, page showing additional Puppy Linux Parameters. In reviewing this page which supports additional Puppy Linux boot parameters, I can find no mentions of its relationship to the Puppy Boot Parameters themselves (those are the options BEFORE the equal sign).

Questions
  • Are these boot options related and to be used in conjunction with the first mentioned set, above? Why are they separate?
Thanks in advance for any clarity on options used in booting Puppy Linux.

boof
Posts: 579
Joined: Wed 26 Sep 2012, 22:53

#35 Post by boof »

Please move post if in wrong place:

Slacko-6.5.0:
Want to boot from USB-which works,
and save to sda2-which is either forbidden or beyond my ability. Is there a boot parameter I could set? Like:

kernel /vmlinuz pmedia=usbflash pfix=fsck, PupSfs=/sda2/slackosave_crypta.2fs

I've tried editing the SAVEFILE contents to be /../sda2
but no good there either. I can't get it to save. I'll try (0,1) and see if that helps later. I know it's nooking for a partition number on the same drive, I'm hoping it can be tricked into another drive. I won't do it now, I've got too much stuff running and it's a PITA to start again from scratch if it doesn't work, although I suppos I could just save a slackosave.2fs in sdb3, to keep what I have, and reconfigure SAVEFILE for testing? The old brain is a bit slow these days.

With Tahr-6.0.5 I could boot from a cd and save on sda2.


BTW. I've discovered the when using a USB 2.0 memory stick in a 3.0 port, I need to lock the port to 2.0 or a puppy USB stick won't find the sfs file. It defaults back to 3.0 and can't read the device. It probably just need more time, but a BIOS change is not difficult.

Pelo

Sda2 for your Slacko

#36 Post by Pelo »

There is no reason why a Slacko could not use sda2 if tahrpup use it, in my knowledge.

hamoudoudou

LICK makes our Puppies run on Windows partitions..

#37 Post by hamoudoudou »

of course. LICK makes our Puppies run on Windows partitions..

User avatar
RetroTechGuy
Posts: 2947
Joined: Tue 15 Dec 2009, 17:20
Location: USA

Re: LICK makes our Puppies run on Windows partitions..

#38 Post by RetroTechGuy »

hamoudoudou wrote:of course. LICK makes our Puppies run on Windows partitions..
There hasn't really been a problem until Windows10 (which, for your convenience, removes any files not placed there by Windows10).

Cutting into the boot sequence is a little harder for Win7 and on (I run Lin'N'Win on my XP and Win98 machines). I bypassed mucking with the Win7 boot sequence by simply booting from an external SD card (then pointing to the files stored on the Windows hard drive). Win10 broke it so I moved them onto an external USB drive...
[url=http://murga-linux.com/puppy/viewtopic.php?t=58615]Add swapfile[/url]
[url=http://wellminded.net63.net/]WellMinded Search[/url]
[url=http://puppylinux.us/psearch.html]PuppyLinux.US Search[/url]

hamoudoudou

About Windows 10 :

#39 Post by hamoudoudou »

About Windows 10 :
1 Windows 10 updating a computer bought with Window seven or eight

2 Computer bought with windows 10 and build for windows 10, build in respect of windows 10 specifications.. Linux is still searching for drivers..

s243a
Posts: 2580
Joined: Tue 02 Sep 2014, 04:48
Contact:

#40 Post by s243a »

It also helps to look at the code. Here is the part of the source which contains all the paramaters; lines 836-883 of /initrd/init tahrpup:

Code: Select all

#pmedia= usbflash|usbhd|usbcd|ataflash|atahd|atacd|atazip|scsihd|scsicd|cd
[ $pmedia ] && PMEDIA=$pmedia #boot parameter, broad category of boot media. ex: cd.
[ $psubdir ] && PSUBDIR=$psubdir #boot parameter, directory for puppy files. ex: puppy220
[ $psavemark ] && PSAVEMARK=$psavemark #100913 partition number that has/will-have save-file.

[ $PSUBDIR ] && [ "${PSUBDIR:0:1}" != "/" ] && PSUBDIR="/${PSUBDIR}" #add leading /.

[ $pdev1 ] && PDRV=$pdev1 #boot parameter, partition have booted off. ex: hda3
#100915 requested by technosaurus (formats get changed further down)...
[ $pdrv ] && PDRV=$pdrv #format partition:<path><filename> ex: sda2:/slacko/puppy_slacko_6.3.0.sfs
[ $pupsfs ] && PDRV=$pupsfs
[ $zdrv ] && ZDRV=$zdrv #ex: sda2:/slacko/zdrv_slacko_6.3.0.sfs
[ $fdrv ] && FDRV=$fdrv
[ $adrv ] && ADRV=$adrv
[ $ydrv ] && YDRV=$ydrv
#<partition>:<filename>, for savefile/savefolder. <partition> can be a name or Label or UUID
[ $psave ] && PSAVE=$psave #ex: sdb4:/puppy/tahr/tahrsave or smark or 49baa82d-8c69:tahrsave
#list of kernel modules to load, ex: pimod=hid-logitech-dj.ko,kernel/drivers/hid/hid-multitouch.ko 
[ $pimod ] && PIMOD=$pimod
#specify partition for Underdog Linux (refer also underdog.lnx).
[ $underdog ] && UNDERDOG=$underdog
#[ $pdebug ] && PDEBUG=$pdebug
PDEBUG=1
TOTAL_SIZEK_SFS_RAM=0

# show menu with pupsaves
[ $psavemenu ] && PSAVEMENU=$psavemenu

RDSH=""
if [ "$pfix" ];then
 for ONEFIX in $(echo -n "$pfix" | tr ',' ' ')
 do
  case $ONEFIX in
   ram)     PRAMONLY="yes";;      #run in ram only (do not load ${DISTRO_FILE_PREFIX}save).
   rdsh)    RDSH="yes";;          #exit to shell in initial ramdisk.
   nox)     PNOX="yes";;          #do not start X.
   clean)   PCLEAN="yes";;        #force version upgrade and cleanup.
   trim)    PTRIM="yes";;         #add "discard" to mount options if SSD
   copy)    PCOPY="yes";;         #copy .sfs files into ram.
   nocopy)  PNOCOPY="yes";;        #do not copy .sfs files into ram (default is copy if enough ram).
   fsck)    PFSCK="yes";;         #do a fsck of ${DISTRO_FILE_PREFIX}save file.
   fsckp)   PFSCKP="yes";;        #do fsck before first mount of ext partitions
   [0-9]*)  PIGNORELAST=$ONEFIX;; #blacklist last $ONEFIX folders (multisession).
   psavebkp)PSAVEBKP='yes';;      #don't ignore pupsaves created by Pupsave Backup
   *)       echo "pfix=$ONEFIX is not a known boot parameter";;
  esac
 done
fi
pastbin, pearltrees, github

Post Reply