Page 1 of 3
puppy boot options.
Posted: Thu 10 Nov 2011, 09:34
by HiDeHo
Here are the default puppy boot options for LUPUP 5.2.0 and all other lupu puppies. (most puppy versions should also use similar boot options but specialised ones may not). its a good idea to have these boot options when you have to configure a bootloader such as Grub, Grub2 or syslinux. grub4dos can automatically detect and configure the boot loader for you even with a frugal install.
- acpi=off Default on for PCs >2001, may give boot/shutdown Probs
pfix=ram Run totally in RAM ignore saved sessions
pfix=nox commandline only, do not start x
pfix=copy coppy .sfs files to RAM (slower boot, faster running)
pfix=nocopy do not copy .sfs to RAM (faster boot, slower running
pfix=fsck do filesystem check on lupusave (and host partition)
pfix=clean file cleanup (simulate version upgrade)
pfix=purge more radical file cleanup (to fix broken systems)' {
pfix=<n> Number of save files to ignore
If you know of the boot options for wary, slacko, quirky or any other puplet please post them here stating the version of puppy they are from.
Edit: These options can be useful if you want to edit your bootloader like this grub 2 setup for puppy linux
click here
Here is a good post about the different installs you can do with puppy.
click here and
here
Edit 2: Also i just found this about the boot options that explains in more detail
click here
Posted: Thu 10 Nov 2011, 10:24
by nooby
If you have a Netbook with an Atom CPU and if it sometimes refuse
to boot on Lupu 510, 525, 528? then add this to boot code
nosmp
then it most likely always boot.
Posted: Thu 10 Nov 2011, 17:58
by ICPUG
What do you mean by 'default boot options'?
What is usually meant is that these are the options that are set by default so will take effect UNLESS the user specifies something else.
The reason I ask the question is that I don't know of any puppy that runs pfix=ram by default. Indeed, by default, they will always load a save file if it exists - sometimes causing pain if it comes from a different version of Puppy!
Obviously pfix=nox is NOT a default.
I think you meant to say that here is a list of boot options that are available to be used with Lupu. If so, then the list is not complete.
Re: puppy boot options.
Posted: Thu 10 Nov 2011, 18:16
by rjbrewer
HiDeHo wrote:Here are the default puppy boot options for LUPUP 5.2.0 and all other lupu puppies. (most puppy versions should also use similar boot options but specialised ones may not). its a good idea to have these boot options when you have to configure a bootloader such as Grub, Grub2 or syslinux. grub4dos can automatically detect and configure the boot loader for you even with a frugal install.
- acpi=off Default on for PCs >2001, may give boot/shutdown Probs
pfix=ram Run totally in RAM ignore saved sessions
pfix=nox commandline only, do not start x
pfix=copy coppy .sfs files to RAM (slower boot, faster running)
pfix=nocopy do not copy .sfs to RAM (faster boot, slower running
pfix=fsck do filesystem check on lupusave (and host partition)
pfix=clean file cleanup (simulate version upgrade)
pfix=purge more radical file cleanup (to fix broken systems)' {
pfix=<n> Number of save files to ignore
If you know of the boot options for wary, slacko, quirky or any other puplet please post them here stating the version of puppy they are from.
edit.
These options can be useful if you want to edit your bootloader like this grub 2 setup for puppy linux
click here
Here is a good post about the different installs you can do with puppy.
click here and
here
Those are more commonly known as "cheat codes", which
are used for special cases.
A longer list can be found on earlier cds; such as Puppy4.12.
Posted: Thu 10 Nov 2011, 19:40
by Béèm
Posted: Mon 14 Nov 2011, 07:59
by HiDeHo
ICPUG wrote:What do you mean by 'default boot options'?
What is usually meant is that these are the options that are set by default so will take effect UNLESS the user specifies something else.
The reason I ask the question is that I don't know of any puppy that runs pfix=ram by default. Indeed, by default, they will always load a save file if it exists - sometimes causing pain if it comes from a different version of Puppy!
Obviously pfix=nox is NOT a default.
I think you meant to say that here is a list of boot options that are available to be used with Lupu. If so, then the list is not complete.
by default options i mean the default ones given when booting puppy and pressing f2 it shows a list of the options for booting puppy..
the ones there are the most common ones and yes there are probably more you can do than you get in the list.
Posted: Mon 14 Nov 2011, 12:47
by ICPUG
Thanks HiDeHo.
I understand what you mean now.
Posted: Thu 17 Nov 2011, 22:11
by rhadon
pfix=fsck do filesystem check on lupusave (and host partition)
Are you sure? IIRC it checks only the save file.
The exception is an improper shutdown. In this case Lupu checks both automatically, no pfix=fsck needed.
~Rolf
Posted: Fri 18 Nov 2011, 05:32
by HiDeHo
rhadon wrote:pfix=fsck do filesystem check on lupusave (and host partition)
Are you sure? IIRC it checks only the save file.
The exception is an improper shutdown. In this case Lupu checks both automatically, no pfix=fsck needed.
~Rolf
i have explained and pointed to another post that explains each option better.
click here
Posted: Fri 18 Nov 2011, 06:40
by rhadon
HiDeHo wrote:i have explained and pointed to another post that explains each option better.
The post you pointed to, doesn't explain pfix=fsck.
Please don't get me wrong. I like your list and explanations.
But it should be correct.
~Rolf
Posted: Mon 21 Nov 2011, 11:28
by rhadon
Maybe people who are interested in the first part of the boot options also want to know about the 2nd part (from Lupu-525):
The following are mostly in GRUB/Syslinux setup for installed Puppy. Files are
found automatically at bootup but these can help the 'init' script. Examples:
pdev1=sdc1 The boot partition.
psubdir=puppies/wary501 Path in which Puppy is installed.
psavemark=2 Partition no. (in boot drive) to save session to.
pmedia=usbflash Type of media booting from. Choose one of these:
usbflash usbhd usbcd ataflash atahd atacd atazip scsihd scsicd cd
pupsfs=sdc1:/puppies/wary501/puppy.sfs Override auto search.
zdrv=sdc1:/puppies/wary501/zdrv.sfs Override auto search.
The following are for debugging, for experts only:
loglevel=<n> Bootup verbosity. 7 is high verbosity for debugging.
pfix=rdsh Execute 'init' then dropout to prompt in initramfs.
pfix=rdsh0 Dropout early, before loading kernel drivers.
pfix=rdsh6 Dropout just before mount layered filesystem.
More help here:
http://kernel.org/doc/Documentation/ker ... meters.txt
~Rolf
Posted: Mon 02 Jan 2012, 19:08
by amigo
It's worth mentioning here, that 'acpi=off', 'nosmp' and many other possibilities are not part of the puppy 'cheat codes'. They are kernel parameters and there are many of them. There are also a few possible ones which are paramaters to the 'init' program, although this does not apply to the puppy init.
Since you are trying to explain/rationalize, it would be good to keep the difference between kernel parameters, init parameters and puppy-specific 'cheat codes' in mind. Most puppy users are unaware of the difference, so that don't understand why options which work for other distros do not work here.
Posted: Sun 15 Jan 2012, 12:11
by TheProphet
Ordinarily I don't have any problem bringing up my keyboard layout because it's the first thing that gets started when Puppy gets to the "setup X" environment. I use the Dvorak layout and have quite forgotten, by way of 'muscle memory" how to touch type on the QWERTY aka The Short Road To Carpal Tunnel Syndrome.
So I tried out the new Attack Puppy release. (a security testing suite, very nice) and damned if the "choose keyboard layout" dialogue had disappeared.
Is there any way to cheat-code to load, at the boot prompt, the Dvorak?
Or, simple for me now, what's the name of the app, to start it from the terminal, for that particular segment?
I'm using the Command Line a lot nowadays.
Also, a bash command to simply change the layout?
solved my previous question
Posted: Mon 16 Jan 2012, 05:29
by TheProphet
By accidentally right clicking on the desktop thus bringing up a menu, mouseandkeyboard settings, a button near the bottom for Xorg users, layout variants for my Keyboard (us, started with Qwerty The HandBreaker) et voila ici la!
Now to explore the new release.
After first surfing around and driving myself mad, which many will claim to be the shortest trip in the history of driving.
Posted: Wed 19 Dec 2012, 22:32
by xan
TheProphet wrote:
Is there any way to cheat-code to load, at the boot prompt, the Dvorak?
pkeys=dvorak
Pfix=copy
Posted: Tue 16 Apr 2013, 15:01
by blopa6
I'm using Slacko 5.5, and I have the iso file saved on a USB stick, I want to load everything in RAM and get the USB power by default will not let me
the command that I use is pfix = copy?
from already thank you very much
Estoy usando Slacko 5.5 , tengo la iso y el archivo de guardar en en una memoria USB , quiero que cargue todo en Ram y poder sacar el USB que por default no me deja
el comando que debo usar es pfix=copy ?
desde ya muchas gracias
Boot profile
Posted: Tue 23 Apr 2013, 13:29
by tmoulder
I've been using puppy off and on for a few years, and now have slacko running full install on an older PC with the Nouveau nvidia driver. It's the first distro I've run on this hardware that did not need a mess of teaking out of the box to get that card to work. Kudos!
Anyway, since this is a discussion on boot options, I've been checking out various posts about speeding up puppy boot time. I saw the emphasis was on hardware detection, and this can be one reason it takes so long to boot for such a comparatively small distro (my time is about 45 seconds, good but not great).
So I was wondering - and I have no idea how difficult this would be - what about a boot option like ubuntu offers to create a profile? The profile would create a file of the drivers actually used in the hardware on the computer, and load those only instead of doing a search at boot time.
This could be automatically disabled on a live disc / usb / what-have-you (since you never know the hardware in such a case). On a frugal install, the profile could be checked first and executed if found.
Just throwing it out there.
Thanks!
TM
Posted: Wed 09 Apr 2014, 08:22
by live
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.
PF3 boot options : puppy psavemark=" " (partition nr)
Posted: Sat 20 Sep 2014, 08:32
by Pelo
label puppy
kernel vmlinuz
append initrd=initrd.gz pmedia=usb
Add psubdir=XXXXXX
synthèse en français ici, claquez !
puppy psavemark= (number of your partition)
Boot options
Posted: Sun 21 Sep 2014, 12:55
by SugarSweetStarr
A small extract:
Code: Select all
acpi= [HW,ACPI,X86]
Advanced Configuration and Power Interface
Format: { force | off | strict | noirq | rsdt }
force -- enable ACPI if default was off
off -- disable ACPI if default was on
noirq -- do not use ACPI for IRQ routing
strict -- Be less tolerant of platforms that are not
strictly ACPI specification compliant.
rsdt -- prefer RSDT over (default) XSDT
copy_dsdt -- copy DSDT to memory
See also Documentation/power/runtime_pm.txt, pci=noacpi
from
https://www.kernel.org/doc/Documentatio ... meters.txt
There's heaps more listed there; here's another sample:
Code: Select all
pci=option[,option...] [PCI] various PCI subsystem options:
earlydump [X86] dump PCI config space before the kernel
changes anything
off [X86] don't probe for the PCI bus
bios [X86-32] force use of PCI BIOS, don't access
the hardware directly. Use this if your machine
has a non-standard PCI host bridge.
nobios [X86-32] disallow use of PCI BIOS, only direct
hardware access methods are allowed. Use this
if you experience crashes upon bootup and you
suspect they are caused by the BIOS.
conf1 [X86] Force use of PCI Configuration
Mechanism 1.
conf2 [X86] Force use of PCI Configuration
Mechanism 2.
noaer [PCIE] If the PCIEAER kernel config parameter is
enabled, this kernel boot option can be used to
disable the use of PCIE advanced error reporting.
nodomains [PCI] Disable support for multiple PCI
root domains (aka PCI segments, in ACPI-speak).
nommconf [X86] Disable use of MMCONFIG for PCI
Configuration
check_enable_amd_mmconf [X86] check for and enable
properly configured MMIO access to PCI
config space on AMD family 10h CPU
nomsi [MSI] If the PCI_MSI kernel config parameter is
enabled, this kernel boot option can be used to
disable the use of MSI interrupts system-wide.
noioapicquirk [APIC] Disable all boot interrupt quirks.
Safety option to keep boot IRQs enabled. This
should never be necessary.
ioapicreroute [APIC] Enable rerouting of boot IRQs to the
primary IO-APIC for bridges that cannot disable
boot IRQs. This fixes a source of spurious IRQs
when the system masks IRQs.
noioapicreroute [APIC] Disable workaround that uses the
boot IRQ equivalent of an IRQ that connects to
a chipset where boot IRQs cannot be disabled.
The opposite of ioapicreroute.
biosirq [X86-32] Use PCI BIOS calls to get the interrupt
routing table. These calls are known to be buggy
on several machines and they hang the machine
when used, but on other computers it's the only
way to get the interrupt routing table. Try
this option if the kernel is unable to allocate
IRQs or discover secondary PCI buses on your
motherboard.
rom [X86] Assign address space to expansion ROMs.
Use with caution as certain devices share
address decoders between ROMs and other
resources.
norom [X86] Do not assign address space to
expansion ROMs that do not already have
BIOS assigned address ranges.
nobar [X86] Do not assign address space to the
BARs that weren't assigned by the BIOS.
irqmask=0xMMMM [X86] Set a bit mask of IRQs allowed to be
assigned automatically to PCI devices. You can
make the kernel exclude IRQs of your ISA cards
this way.
pirqaddr=0xAAAAA [X86] Specify the physical address
of the PIRQ table (normally generated
by the BIOS) if it is outside the
F0000h-100000h range.
lastbus=N [X86] Scan all buses thru bus #N. Can be
useful if the kernel is unable to find your
secondary buses and you want to tell it
explicitly which ones they are.
assign-busses [X86] Always assign all PCI bus
numbers ourselves, overriding
whatever the firmware may have done.
usepirqmask [X86] Honor the possible IRQ mask stored
in the BIOS $PIR table. This is needed on
some systems with broken BIOSes, notably
some HP Pavilion N5400 and Omnibook XE3
notebooks. This will have no effect if ACPI
IRQ routing is enabled.
noacpi [X86] Do not use ACPI for IRQ routing
or for PCI scanning.
use_crs [X86] Use PCI host bridge window information
from ACPI. On BIOSes from 2008 or later, this
is enabled by default. If you need to use this,
please report a bug.
nocrs [X86] Ignore PCI host bridge windows from ACPI.
If you need to use this, please report a bug.
routeirq Do IRQ routing for all PCI devices.
This is normally done in pci_enable_device(),
so this option is a temporary workaround
for broken drivers that don't call it.
skip_isa_align [X86] do not align io start addr, so can
handle more pci cards
firmware [ARM] Do not re-enumerate the bus but instead
just use the configuration from the
bootloader. This is currently used on
IXP2000 systems where the bus has to be
configured a certain way for adjunct CPUs.
noearly [X86] Don't do any early type 1 scanning.
This might help on some broken boards which
machine check when some devices' config space
is read. But various workarounds are disabled
and some IOMMU drivers will not work.
bfsort Sort PCI devices into breadth-first order.
This sorting is done to get a device
order compatible with older (<= 2.4) kernels.
nobfsort Don't sort PCI devices into breadth-first order.
pcie_bus_tune_off Disable PCIe MPS (Max Payload Size)
tuning and use the BIOS-configured MPS defaults.
pcie_bus_safe Set every device's MPS to the largest value
supported by all devices below the root complex.
pcie_bus_perf Set device MPS to the largest allowable MPS
based on its parent bus. Also set MRRS (Max
Read Request Size) to the largest supported
value (no larger than the MPS that the device
or bus can support) for best performance.
pcie_bus_peer2peer Set every device's MPS to 128B, which
every device is guaranteed to support. This
configuration allows peer-to-peer DMA between
any pair of devices, possibly at the cost of
reduced performance. This also guarantees
that hot-added devices will work.
cbiosize=nn[KMG] The fixed amount of bus space which is
reserved for the CardBus bridge's IO window.
The default value is 256 bytes.
cbmemsize=nn[KMG] The fixed amount of bus space which is
reserved for the CardBus bridge's memory
window. The default value is 64 megabytes.
resource_alignment=
Format:
[<order of align>@][<domain>:]<bus>:<slot>.<func>[; ...]
Specifies alignment and device to reassign
aligned memory resources.
If <order of align> is not specified,
PAGE_SIZE is used as alignment.
PCI-PCI bridge can be specified, if resource
windows need to be expanded.
ecrc= Enable/disable PCIe ECRC (transaction layer
end-to-end CRC checking).
bios: Use BIOS/firmware settings. This is the
the default.
off: Turn ECRC off
on: Turn ECRC on.
hpiosize=nn[KMG] The fixed amount of bus space which is
reserved for hotplug bridge's IO window.
Default size is 256 bytes.
hpmemsize=nn[KMG] The fixed amount of bus space which is
reserved for hotplug bridge's memory window.
Default size is 2 megabytes.
realloc= Enable/disable reallocating PCI bridge resources
if allocations done by BIOS are too small to
accommodate resources required by all child
devices.
off: Turn realloc off
on: Turn realloc on
realloc same as realloc=on
noari do not use PCIe ARI.
pcie_scan_all Scan all possible PCIe devices. Otherwise we
only look for one device below a PCIe downstream
port.