The time now is Sat 21 Apr 2018, 21:29
All times are UTC - 4 |
| Author |
Message |
blopa6
Joined: 15 Apr 2008
Posts: 32
|
 Posted: Tue 16 Apr 2013, 11:01 Post subject:
Pfix=copy |
|
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
|
|
Back to top
|
|
 |
tmoulder
Joined: 17 Jun 2011
Posts: 4
|
| Posted: Tue 23 Apr 2013, 09:29 Post subject:
Boot profile |
|
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
|
|
Back to top
|
|
|
live
Joined: 10 Feb 2010
Posts: 220
|
| Posted: Wed 09 Apr 2014, 04:22 Post subject:
|
|
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.
|
|
Back to top
|
|
|
Pelo
Joined: 10 Sep 2011
Posts: 12591
Location: Mer méditerrannée (1 kms°)
|
Posted: Sat 20 Sep 2014, 04:32 Post subject:
PF3 boot options : puppy psavemark=" " (partition nr)
Subject description: francophones : voir notre synthèse |
|
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)
_________________
Passenger Pelo ! don't ask him to repair the aircraft. Don't use him as a demining dog .... pleeease.
Last edited by Pelo on Sun 21 Sep 2014, 20:06; edited 3 times in total
|
|
Back to top
|
|
|
SugarSweetStarr
Joined: 18 Sep 2014
Posts: 11
|
Posted: Sun 21 Sep 2014, 08:55 Post subject:
 Boot options
Subject description: more Linux kernel options than Puppy-specific.... |
|
A small extract:
| Code: | 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/Documentation/kernel-parameters.txt
There's heaps more listed there; here's another sample:
| Code: | 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.
|
|
|
Back to top
|
|
|
sindi
Joined: 16 Aug 2009
Posts: 851
Location: Ann Arbor MI USA
|
| Posted: Tue 12 May 2015, 12:19 Post subject:
Booting puppy 1.07 without X |
|
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?
|
|
Back to top
|
|
|
Wognath
Joined: 19 Apr 2009
Posts: 405
|
| Posted: Thu 14 May 2015, 21:58 Post subject:
psave parameter |
|
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.
|
|
Back to top
|
|
|
gychang
Joined: 29 Nov 2008
Posts: 198
Location: Davis, CA
|
| Posted: Sat 04 Jul 2015, 20:11 Post subject:
does not work well puppy pfix=ram, tahrPup |
|
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?
|
|
Back to top
|
|
|
gychang
Joined: 29 Nov 2008
Posts: 198
Location: Davis, CA
|
| Posted: Sat 04 Jul 2015, 20:12 Post subject:
|
|
| 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.
|
|
Back to top
|
|
|
bigpup
Joined: 11 Oct 2009
Posts: 10303
Location: Charleston S.C. USA
|
| Posted: Sat 04 Jul 2015, 22:45 Post subject:
Re: does not work well puppy pfix=ram, tahrPup |
|
| 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.
_________________
I have found, in trying to help people, that 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 
|
|
Back to top
|
|
|
gychang
Joined: 29 Nov 2008
Posts: 198
Location: Davis, CA
|
| Posted: Sun 05 Jul 2015, 10:58 Post subject:
Re: does not work well puppy pfix=ram, tahrPup |
|
[quote="bigpup"] | 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?
|
|
Back to top
|
|
|
rcrsn51
Joined: 05 Sep 2006
Posts: 11889
Location: Stratford, Ontario
|
| Posted: Sun 05 Jul 2015, 11:04 Post subject:
|
|
@gychang: Please post the syslinux.cfg or menu.lst file from your USB stick. You probably want the option
|
|
Back to top
|
|
|
gychang
Joined: 29 Nov 2008
Posts: 198
Location: Davis, CA
|
| Posted: Sun 05 Jul 2015, 16:17 Post subject:
|
|
| rcrsn51 wrote: | @gychang: Please post the syslinux.cfg or menu.lst file from your USB stick. You probably want the option
|
thanks!!
|
|
Back to top
|
|
|
Mike7
Joined: 18 Feb 2013
Posts: 391
|
| Posted: Mon 06 Jul 2015, 10:19 Post subject:
|
|
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.
|
|
Back to top
|
|
|
MrAccident
Joined: 31 Mar 2014
Posts: 223
|
| Posted: Sun 13 Sep 2015, 01:21 Post subject:
|
|
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.
|
|
Back to top
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
Forum index » House Training » Users ( For the regulars )
