USB Install How?

daBee · Post by **daBee** » Fri Nov 12, 2021 7:01 pm

Hi folks. I can't seem to install. Wrote to the USB thumb drive, and I have a grub command line now. What am I doing wrong?

: IMG_8918.JPG (125.83 KiB) Viewed 2737 times

peterw · Post by **peterw** » Fri Nov 12, 2021 8:45 pm

Grub4dos is no good with a PC set to boot a UEFI installation so check that first.

rcrsn51 · Post by **rcrsn51** » Fri Nov 12, 2021 9:08 pm

Is there a menu.lst file on the USB drive?

peterw · Post by **peterw** » Fri Nov 12, 2021 9:38 pm

How did you prepare the USB stick? The easiest way as a starter is the dd command explained here: https://puppylinux.com/install.html

Post by **bigpup** » Sat Nov 13, 2021 12:07 am

Completely start over and use one of these installer programs:
viewtopic.php?p=528#p528

But to give you really good info.
What is the computer?
Make and model?
Is it UEFI or Legacy bios?
What operating system are you running, to do the USB install?

WHAT SPECIFIC PUPPY VERSION????, are you trying to install on the USB?

mikeslr · Post by **mikeslr** » Sat Nov 13, 2021 1:05 am

I would suggest using dd and USBImager only as a last resort. They will create a boot-able USB-Key, but one which doesn't enable you to Save new applications, customizations, setting or any kind of changes. See the discussion here, viewtopic.php?p=40673#p40673. To obtain a fully functional Puppy, you'd have to use the tools provided by your first Puppy-on-a-USB-Key to create a Puppy on a different USB-Key.
The same would be true of rufus, except that a 'work-around' was discovered. See, viewtopic.php?p=40522#p40522 for the recipe.

But do answer bigpup's questions. We can't give specific advise without knowing the specifics you are working with and your specific goals.

peterw · Post by **peterw** » Sat Nov 13, 2021 2:05 pm

Just an observation about ourselves making it easy for people to start using Puppy. There are various ways to make a bootable USB stick and it is an art that evolves rapidly. I don't control the Puppy https://puppylinux.com/ site but surely this must be the site where potential users can get a set of simple instructions on how to make their first bootable USB stick and they need to be clearly referenced there.
Once a user has made there first stick then there are Puppy programmes to make other sticks that can boot of UEFI and MBR systems, etc.

daBee · Post by **daBee** » Sat Nov 13, 2021 6:42 pm

peterw wrote: Fri Nov 12, 2021 9:38 pm
How did you prepare the USB stick? The easiest way as a starter is the dd command explained here: https://puppylinux.com/install.html

dd is what I used.

sudo dd if=/Volumes/Tug/storOSImages/Puppy_for_Atom/fossapup64-9.5.iso of=/dev/disk13 bs=10240 conv=sync

Puppy version: fossapup64-9.5.iso

I'm doing this on a Mac. Been doing it on Macs for years. No errors. I can't mount any filesystem on the Mac, so I don't know what files there are. I've tried to look for the startup files, but haven't seen the filesystem.

It's an old Atom box with legacy bios, but I can't seem to find it. CentOS8 is loading without any bios check (on current boot volume). I've been using dd for many years. This USB boot load for installation, doesn't seem to work. My goals...are to install Puppy OS onto this box. This box has no make, as it's just put together:

Code: Select all

[Sun Feb 15 01:16 PM rich@shuttle /usr/ports/sysutils/dmidecode] sudo dmidecode
# dmidecode 2.12
SMBIOS 2.5 present.
38 structures occupying 1138 bytes.
Table at 0x000F0000.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
	Vendor: Phoenix Technologies, LTD
	Version: 6.00 PG
	Release Date: 04/21/2008
	Address: 0xE0000
	Runtime Size: 128 kB
	ROM Size: 1024 kB
	Characteristics:
		ISA is supported
		PCI is supported
		PNP is supported
		APM is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		BIOS ROM is socketed
		EDD is supported
		5.25"/360 kB floppy services are supported (int 13h)
		5.25"/1.2 MB floppy services are supported (int 13h)
		3.5"/720 kB floppy services are supported (int 13h)
		3.5"/2.88 MB floppy services are supported (int 13h)
		Print screen service is supported (int 5h)
		8042 keyboard services are supported (int 9h)
		Serial services are supported (int 14h)
		Printer services are supported (int 17h)
		CGA/mono video services are supported (int 10h)
		ACPI is supported
		USB legacy is supported
		LS-120 boot is supported
		ATAPI Zip drive boot is supported
		BIOS boot specification is supported
		Targeted content distribution is supported

Handle 0x0001, DMI type 1, 27 bytes
System Information
	Manufacturer: Shuttle Inc
	Product Name: SK45
	Version: V10
	Serial Number: 0
	UUID: 01020907-0301-0400-0807-060504030201
	Wake-up Type: Power Switch
	SKU Number:
	Family:

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
	Manufacturer: Shuttle Inc
	Product Name: FM10
	Version: V10
	Serial Number: 0

Handle 0x0003, DMI type 3, 17 bytes
Chassis Information
	Manufacturer: Shuttle Inc
	Type: Desktop
	Lock: Not Present
	Version: K
	Serial Number:
	Asset Tag:
	Boot-up State: Unknown
	Power Supply State: Unknown
	Thermal State: Unknown
	Security Status: Unknown
	OEM Information: 0x00000000

Handle 0x0004, DMI type 4, 40 bytes
Processor Information
	Socket Designation: Socket 775
	Type: Central Processor
	Family: Celeron
	Manufacturer: Intel
	ID: FD 06 00 00 FF FB EB BF
	Signature: Type 0, Family 6, Model 15, Stepping 13
	Flags:
		FPU (Floating-point unit on-chip)
		VME (Virtual mode extension)
		DE (Debugging extension)
		PSE (Page size extension)
		TSC (Time stamp counter)
		MSR (Model specific registers)
		PAE (Physical address extension)
		MCE (Machine check exception)
		CX8 (CMPXCHG8 instruction supported)
		APIC (On-chip APIC hardware supported)
		SEP (Fast system call)
		MTRR (Memory type range registers)
		PGE (Page global enable)
		MCA (Machine check architecture)
		CMOV (Conditional move instruction supported)
		PAT (Page attribute table)
		PSE-36 (36-bit page size extension)
		CLFSH (CLFLUSH instruction supported)
		DS (Debug store)
		ACPI (ACPI supported)
		MMX (MMX technology supported)
		FXSR (FXSAVE and FXSTOR instructions supported)
		SSE (Streaming SIMD extensions)
		SSE2 (Streaming SIMD extensions 2)
		SS (Self-snoop)
		HTT (Multi-threading)
		TM (Thermal monitor supported)
		PBE (Pending break enabled)
	Version: Intel(R) Celeron(R)
	Voltage: 1.8 V
	External Clock: 200 MHz
	Max Speed: 3066 MHz
	Current Speed: 1600 MHz
	Status: Populated, Enabled
	Upgrade: ZIF Socket
	L1 Cache Handle: 0x000A
	L2 Cache Handle: 0x000B
	L3 Cache Handle: Not Provided
	Serial Number:
	Asset Tag:
	Part Number:
	Core Count: 2
	Core Enabled: 2
	Thread Count: 2
	Characteristics:
		64-bit capable

Handle 0x0005, DMI type 5, 24 bytes
Memory Controller Information
	Error Detecting Method: 8-bit Parity
	Error Correcting Capabilities:
		None
	Supported Interleave: One-way Interleave
	Current Interleave: One-way Interleave
	Maximum Memory Module Size: 1024 MB
	Maximum Total Memory Size: 4096 MB
	Supported Speeds:
		Other
	Supported Memory Types:
		Other
	Memory Module Voltage: 5.0 V
	Associated Memory Slots: 4
		0x0006
		0x0007
		0x0008
		0x0009
	Enabled Error Correcting Capabilities:
		None

Handle 0x0006, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: A0
	Bank Connections: 0
	Current Speed: Unknown
	Type: Other
	Installed Size: 512 MB (Single-bank Connection)
	Enabled Size: 512 MB (Single-bank Connection)
	Error Status: OK

Handle 0x0007, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: A1
	Bank Connections: None
	Current Speed: Unknown
	Type: Unknown
	Installed Size: Not Installed
	Enabled Size: Not Installed
	Error Status: OK

Handle 0x0008, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: A2
	Bank Connections: 4
	Current Speed: Unknown
	Type: Other
	Installed Size: 512 MB (Single-bank Connection)
	Enabled Size: 512 MB (Single-bank Connection)
	Error Status: OK

Handle 0x0009, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: A3
	Bank Connections: None
	Current Speed: Unknown
	Type: Unknown
	Installed Size: Not Installed
	Enabled Size: Not Installed
	Error Status: OK

Handle 0x000A, DMI type 7, 19 bytes
Cache Information
	Socket Designation: Internal Cache
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 32 kB
	Maximum Size: 32 kB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Unknown
	Associativity: Unknown

Handle 0x000B, DMI type 7, 19 bytes
Cache Information
	Socket Designation: External Cache
	Configuration: Enabled, Not Socketed, Level 2
	Operational Mode: Write Back
	Location: External
	Installed Size: 32 kB
	Maximum Size: 32 kB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Unknown
	Associativity: Unknown

Handle 0x000C, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: PRIMARY IDE
	Internal Connector Type: On Board IDE
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: SECONDARY IDE
	Internal Connector Type: On Board IDE
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x000E, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: COM1
	Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
	External Reference Designator:
	External Connector Type: DB-9 male
	Port Type: Serial Port 16450 Compatible

Handle 0x000F, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: COM2
	Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
	External Reference Designator:
	External Connector Type: DB-9 male
	Port Type: Serial Port 16450 Compatible

Handle 0x0010, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: LPT1
	Internal Connector Type: DB-25 female
	External Reference Designator:
	External Connector Type: DB-25 female
	Port Type: Parallel Port ECP/EPP

Handle 0x0011, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Keyboard
	Internal Connector Type: PS/2
	External Reference Designator:
	External Connector Type: PS/2
	Port Type: Keyboard Port

Handle 0x0012, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: PS/2 Mouse
	Internal Connector Type: PS/2
	External Reference Designator:
	External Connector Type: PS/2
	Port Type: Mouse Port

Handle 0x0013, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Specified
	Internal Connector Type: None
	External Reference Designator: USB0
	External Connector Type: Other
	Port Type: USB

Handle 0x0014, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Specified
	Internal Connector Type: None
	External Reference Designator: USB1
	External Connector Type: Other
	Port Type: USB

Handle 0x0015, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI0
	Type: 32-bit PCI
	Current Usage: Available
	Length: Long
	ID: 1
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x0016, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI1
	Type: 32-bit PCI
	Current Usage: Available
	Length: Long
	ID: 2
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x0017, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI2
	Type: 32-bit PCI
	Current Usage: Available
	Length: Long
	ID: 3
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x0018, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI3
	Type: 32-bit PCI
	Current Usage: Available
	Length: Long
	ID: 4
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x0019, DMI type 13, 22 bytes
BIOS Language Information
	Language Description Format: Long
	Installable Languages: 3
		n|US|iso8859-1
		n|US|iso8859-1
		r|CA|iso8859-1
	Currently Installed Language: n|US|iso8859-1

Handle 0x001A, DMI type 16, 15 bytes
Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: None
	Maximum Capacity: 4 GB
	Error Information Handle: Not Provided
	Number Of Devices: 4

Handle 0x001B, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x001A
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 512 MB
	Form Factor: DIMM
	Set: None
	Locator: A0
	Bank Locator: Bank0/1
	Type: DDR2
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: None
	Serial Number: None
	Asset Tag: None
	Part Number: None

Handle 0x001C, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x001A
	Error Information Handle: Not Provided
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: None
	Locator: A1
	Bank Locator: Bank2/3
	Type: Unknown
	Type Detail: Unknown
	Speed: Unknown
	Manufacturer: None
	Serial Number: None
	Asset Tag: None
	Part Number: None

Handle 0x001D, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x001A
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 512 MB
	Form Factor: DIMM
	Set: None
	Locator: A2
	Bank Locator: Bank4/5
	Type: DDR2
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: None
	Serial Number: None
	Asset Tag: None
	Part Number: None

Handle 0x001E, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x001A
	Error Information Handle: Not Provided
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: None
	Locator: A3
	Bank Locator: Bank6/7
	Type: Unknown
	Type Detail: Unknown
	Speed: Unknown
	Manufacturer: None
	Serial Number: None
	Asset Tag: None
	Part Number: None

Handle 0x001F, DMI type 19, 15 bytes
Memory Array Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0003FFFFFFF
	Range Size: 1 GB
	Physical Array Handle: 0x001A
	Partition Width: 1

Handle 0x0020, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0001FFFFFFF
	Range Size: 512 MB
	Physical Device Handle: 0x001B
	Memory Array Mapped Address Handle: 0x001F
	Partition Row Position: 1

Handle 0x0021, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x000000003FF
	Range Size: 1 kB
	Physical Device Handle: 0x001C
	Memory Array Mapped Address Handle: 0x001F
	Partition Row Position: 1

Handle 0x0022, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00020000000
	Ending Address: 0x0003FFFFFFF
	Range Size: 512 MB
	Physical Device Handle: 0x001D
	Memory Array Mapped Address Handle: 0x001F
	Partition Row Position: 1

Handle 0x0023, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x000000003FF
	Range Size: 1 kB
	Physical Device Handle: 0x001E
	Memory Array Mapped Address Handle: 0x001F
	Partition Row Position: 1

Handle 0x0024, DMI type 32, 11 bytes
System Boot Information
	Status: No errors detected

Handle 0x0025, DMI type 127, 4 bytes
End Of Table

Post by **bigpup** » Sat Nov 13, 2021 8:14 pm

Fossapup64 has a small bug in the boot process.
If it is not the only USB drive plugged in.
It sometimes looks on the wrong USB for the Fossapup64 files.
So, boot only having the Fossapup64 USB drive plugged into computer.
No other USB drives plugged in.

First you are sure you got a good download of the Fossapup64 9.5 ISO?
It is stored at a location the file system is not fragmented?

sudo dd if=/Volumes/Tug/storOSImages/Puppy_for_Atom/fossapup64-9.5.iso of=/dev/disk13 bs=10240 conv=sync

Try this dd command:

Code: Select all

sudo dd if=/Volumes/Tug/storOSImages/Puppy_for_Atom/fossapup64-9.5.iso of=/dev/disk13

I assume, to the mac computer, disk13 is the USB drive?

I know it is missing some commands you may want to use, but try it.

Mind: it deletes everything on the usb, it occupies just the space it needs for the iso
and the rest of the usb is unusable.

If still not booting.

Can you provide image showing what Puppy files are on the USB?
Or tell us?

Unetbootin installer has a mac version.
The USB can be formatted fat32
Puppy installed to a fat32 format, can use the USB to store the Puppy save file, and any other stuff you want to store on it.
Using the dd command, the USB is like a CD, with an iso9660 format. Cannot be written to.

peterw · Post by **peterw** » Sat Nov 13, 2021 11:16 pm

Not a Mac user but your dd command seems fine and if it works for other distro's then it will work for Puppy. The display is showing that the boot process is looking for the menu.1st and has looked were it could be but has not found it. Without the instruction it contains Puppy doesn't know what to do. If I open up the fossapup64-9.5.iso and in /boot/grub you will find the menu.1st file the contents are listed below and you will get those titles listed together with where it will find the files it needs.

That Celeron PC should work fine with Puppy and should be good. It is just Legacy/MBR and not UEFI. These days I just use frugal installs to either a USB stick/SSD/hard drive. You can happily have many Puppies on the same partition.

It might be that you have another USB stick plugged in or something that is confusing the boot process or it might be that you have a corrupt iso download. If you can get any Puppy Linux to boot on that PC then it is very easy to manually install others and run grub4dos to create a menu.1st.

#
# menu.lst
#

#color NORMAL HIGHLIGHT HELPTEXT HEADING
# f/b f/b f/b f/b
color light-gray/black yellow/red cyan/black light-blue/black

timeout 10
default 0

# 0.4.6a
graphicsmode -1 800 600
splashimage /boot/splash.jpg

title fossapup64 9.5
kernel /vmlinuz pfix=fsck pmedia=cd
initrd /initrd.gz

title fossapup64 9.5 - Copy SFS files to RAM\n
kernel /vmlinuz pmedia=cd pfix=fsck,copy
initrd /initrd.gz

title fossapup64 9.5 - Don't copy SFS files to RAM\nIf you want more RAM available
kernel /vmlinuz pmedia=cd pfix=fsck,nocopy
initrd /initrd.gz

title fossapup64 9.5 - Force xorgwizard (xorgwizard)\nForce xorgwizard (if you are having problems booting puppy)...
kernel /vmlinuz pmedia=cd pfix=xorgwizard,fsck
initrd /initrd.gz

title fossapup64 9.5 - No X\nTry 'xorgwizard' after bootup succeed to start graphic mode.
kernel /vmlinuz pmedia=cd pfix=nox,fsck
initrd /initrd.gz

title fossapup64 9.5 - No Kernel Mode Setting\nNo KMS
kernel /vmlinuz pmedia=cd nomodeset pfix=fsck
initrd /initrd.gz

title fossapup64 9.5 - Safe mode, no X\nTry 'xorgwizard' after bootup succeed to start graphic mode.
kernel /vmlinuz pmedia=cd pfix=ram,nox,fsck
initrd /initrd.gz

title fossapup64 9.5 - RAM only - no pupsave\nBoot up Puppy without pupsave
kernel /vmlinuz pmedia=cd pfix=ram,fsck
initrd /initrd.gz

title fossapup64 9.5 - Ram Disk SHell\nExecute 'init' then dropout to prompt in initramfs
kernel /vmlinuz pmedia=cd pfix=rdsh
initrd /initrd.gz

title
root

title Help - Boot Params
configfile /boot/grub/menu_phelp.lst

title
root

# Boot from Partition Boot Sector

title Boot first hard drive (hd0,0)
root (hd0,0)
chainloader +1 || chainloader /grldr || chainloader /bootmngr

title
root

# additionals

title Grub4Dos commandline\n(for experts only)
commandline

title Reboot computer
reboot

title Halt computer
halt

daBee · Post by **daBee** » Sun Nov 14, 2021 6:05 pm

bigpup wrote: Sat Nov 13, 2021 8:14 pm
Fossapup64 has a small bug in the boot process.
If it is not the only USB drive plugged in.
It sometimes looks on the wrong USB for the Fossapup64 files.
So, boot only having the Fossapup64 USB drive plugged into computer.
No other USB drives plugged in.
...

Nothing is showing up on the USB drive at all. Tried my version twice, your version once. I couldn't see anything on the Mac, and on a Raspberry Pi 4, same thing. The volume seems void of anything. I found the BIOS management and it's properly set. There's just nothing on this USB drive.

I'm going to try an installation on the Pi itself. Well, this time the OS showed up. Same error. But, /boot/grub/menu.1st exists, as well as /grub.cfg.

There is no other USB drive in there. So not really sure how to make that startup boot file take hold.

Code: Select all

$ tree
.
├── adrv_fossapup64_9.5.sfs
├── boot
│   ├── boot.catalog
│   ├── efi.img
│   ├── grub
│   │   ├── font.pf2
│   │   ├── grldr
│   │   ├── grub.cfg
│   │   ├── loopback.cfg
│   │   ├── menu.lst
│   │   └── menu_phelp.lst
│   ├── isolinux
│   │   ├── chain.c32
│   │   ├── isohybrid
│   │   ├── isohybrid64
│   │   ├── isohybrid.pl
│   │   ├── isolinux.bin
│   │   └── isolinux.cfg
│   ├── splash.jpg
│   └── splash.png
├── fdrv_fossapup64_9.5.sfs
├── grub.cfg
├── initrd.gz
├── isolinux.bin
├── puppy_fossapup64_9.5.sfs
├── README.txt
├── vmlinuz
├── Windows_Installer
│   ├── readme.html
│   └── readme.txt
└── zdrv_fossapup64_9.5.sfs

daBee · Post by **daBee** » Sun Nov 14, 2021 6:11 pm

/boot/grub/menu.1st:

Code: Select all

$ cat menu.lst
#
# menu.lst
#

#color NORMAL            HIGHLIGHT       HELPTEXT       HEADING
#       f/b               f/b              f/b           f/b
color light-gray/black yellow/red cyan/black light-blue/black

timeout 10
default 0

# 0.4.6a
graphicsmode -1 800 600
splashimage /boot/splash.jpg

title fossapup64 9.5
  kernel /vmlinuz    pfix=fsck pmedia=cd
  initrd /initrd.gz

title fossapup64 9.5 - Copy SFS files to RAM\n
  kernel /vmlinuz    pmedia=cd pfix=fsck,copy
  initrd /initrd.gz

title fossapup64 9.5 - Don't copy SFS files to RAM\nIf you want more RAM available
  kernel /vmlinuz    pmedia=cd pfix=fsck,nocopy
  initrd /initrd.gz

title fossapup64 9.5 - Force xorgwizard (xorgwizard)\nForce xorgwizard (if you are having problems booting puppy)...
  kernel /vmlinuz    pmedia=cd pfix=xorgwizard,fsck
  initrd /initrd.gz

title fossapup64 9.5 - No X\nTry 'xorgwizard' after bootup succeed to start graphic mode.
  kernel /vmlinuz    pmedia=cd pfix=nox,fsck
  initrd /initrd.gz

title fossapup64 9.5 - No Kernel Mode Setting\nNo KMS
  kernel /vmlinuz    pmedia=cd nomodeset pfix=fsck
  initrd /initrd.gz

title fossapup64 9.5 - Safe mode, no X\nTry 'xorgwizard' after bootup succeed to start graphic mode.
  kernel /vmlinuz    pmedia=cd pfix=ram,nox,fsck
  initrd /initrd.gz

title fossapup64 9.5 - RAM only - no pupsave\nBoot up Puppy without pupsave
  kernel /vmlinuz    pmedia=cd pfix=ram,fsck
  initrd /initrd.gz

title fossapup64 9.5 - Ram Disk SHell\nExecute 'init' then dropout to prompt in initramfs
  kernel /vmlinuz    pmedia=cd pfix=rdsh
  initrd /initrd.gz

title
  root

title Help - Boot Params
  configfile /boot/grub/menu_phelp.lst

title
  root

# Boot from Partition Boot Sector

title Boot first hard drive (hd0,0)
  root (hd0,0)
  chainloader +1 || chainloader /grldr || chainloader /bootmngr

title
  root

# additionals

title Grub4Dos commandline\n(for experts only)
  commandline

title Reboot computer
  reboot

title Halt computer
  halt

rcrsn51 · Post by **rcrsn51** » Sun Nov 14, 2021 6:51 pm

Are you still using the USB drive to boot the old Atom box you described above?

It may be that its old BIOS cannot cope with modern UEFI-compatible ISOs like Fossapup.

I would try an older ISO like Tahrpup.

daBee · Post by **daBee** » Sun Nov 14, 2021 6:56 pm

No, I'm trying to get the installer for the OS.

I was told that Puppy would be good for older machines. OK, thank you.

rcrsn51 · Post by **rcrsn51** » Sun Nov 14, 2021 7:02 pm

Your very first post shows a machine trying to boot off the USB drive.

What machine is that?

daBee · Post by **daBee** » Sun Nov 14, 2021 7:06 pm

Yes. That USB drive is the ISO image. Is there not an installer on there? Regardless, the machine can't boot from that USB Drive, so that ISO image on an SSD won't make any difference.

That machine is the target machine I want to install the OS onto.

rcrsn51 · Post by **rcrsn51** » Sun Nov 14, 2021 7:10 pm

I am suggesting that you get the Tahrpup ISO and use your dd technique to put it on the USB instead of Fossapup.

daBee · Post by **daBee** » Sun Nov 14, 2021 7:14 pm

Ya I hear ya. I'm going to investigate other options at this point. I was hoping this would be a quick distro installation and it seems it's already having trouble. Packages at that point won't be supported, and I want to make sure this has a future. Looking for older versions just sounds like more work than just finding a compatible distro.

Cheers

rcrsn51 · Post by **rcrsn51** » Sun Nov 14, 2021 7:16 pm

If you can get the machine booted with a Tahrpup USB, you could eventually do a hard drive install of Fossapup.

Post by **bigpup** » Sun Nov 14, 2021 9:24 pm

Nothing is showing up on the USB drive at all. Tried my version twice, your version once. I couldn't see anything on the Mac, and on a Raspberry Pi 4, same thing.
The volume seems void of anything.
I found the BIOS management and it's properly set. There's just nothing on this USB drive.

Are you saying you tried to use dd to put Fossapup64 on this USB, but when you look at it, nothing is on it?
Then the USB is broken and no good.
Maybe something is missing with dd software itself, on the computer you are trying to do this with.

peterw · Post by **peterw** » Sun Nov 14, 2021 9:25 pm

Have tried fossapup64 with dd method and got same result that menu.1st can't be found but with tahrpup it works. I think that the fossapup iso is for UEFI PCs. I must admit I have not used the dd method for a while and not with modern pups. I had not realised that iso's have changed.
On old MBR PCs I just format the hard drive to EXT4 create a directory with the Puppy name and copy the iso contents to it. I then run grub4dos which install the boot loader. It works and I suggest that you do that by having tahrpup on the USB stick to boot the PC and load fossapup on the hard drive as I described. Do a frugal install.

mikeslr · Post by **mikeslr** » Sun Nov 14, 2021 9:49 pm

Basically I agree with peterw. But while you're at it, I'd also unpack xenialpup64 and bionicpup64 as well as fossapup64 to folders on the hard-drive; then run grub4dos. Fossapup64 will run from non-UEFI computers; but yours may be too old. On the other hand, tarhpup64 is now struggling to handle web-browsers. One run of grub4dos will then give you three OSes to try. You can delete any if tests reveal problems.

daBee · Post by **daBee** » Mon Nov 15, 2021 1:38 am

On the `Mac`, using `dd`, which I've installed SO MANY operating systems onto USB drives before, I couldn't see anything, on both the `Mac` and on `Raspberry Pi`. Maybe an issue with the `ISO` image, I'm not sure. Checksum checked out fine.

I used the same `dd` command on the `Raspberry Pi` (since it was plugged in), then I saw it.

daBee · Post by **daBee** » Mon Nov 15, 2021 1:39 am

Ya I was interested in Puppy because I was told it fit my specs, with an older box and a lightweight quick solution that's modern for this. Jumping through hoops isn't what I need to adopt.

Post by **bigpup** » Mon Nov 15, 2021 3:54 am

If you used dd command to try and do an install.
If it worked at all.
There should be a bunch of files on the USB drive.

They are when I do it using dd commands

This install was done using dd.
It should look like this, when a file manger is looking at the contents of the drive:
.

: Screenshot(2).jpg (20.43 KiB) Viewed 2018 times

.

peterw · Post by **peterw** » Mon Nov 15, 2021 9:26 am

daBee
Don't give up with Puppy. It is unfortunate that your venture into Puppy has proved frustrating. Many, many years ago I found Puppy which proved to be my route into Linux. Whilst I use other Distros, Puppy or should I say Puppies are and have always been part of my Linux computing experience. If you persist and once you get over the immediate hurdles and learn a little about Puppy's unique features you will appreciate it and it will be part of your life. In particular, once you have a Puppy working then getting more Puppies working becomes so much easier.
I mentioned in a previous post on this topic that the Puppy Introduction pages need to have clear and working instructions for potential Puppy users. I wish they were. I had not realised that the iso's were not so good for making a MBR booting USB stick if you used the dd command.

It is surprising what combinations you can have with Puppy in the way of booting a PC that can give options for example of booting Windows, Ubuntu and various Puppies together with Fatdog. You can also have a USB stick loaded with Puppies that will happily boot off either UEFI or Legacy MBR working with whatever setting the PC has. Typically, I dual boot a Ubuntu variant together with Puppies. On a MBR booting laptop you can either use the Ubuntu Grub2
or grub4dos and I give a cut down list of the entries that I have added to the Ubuntu Grub2 on this laptop.
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-9cdaa924-709c-4e34-b57e-ed57a62761de' {
menuentry 'Memory test (memtest86+)' {
menuentry "Puppy slacko64 6.9.9.9 (sda1/slacko64)" {
set root=(hd0,1)
linux /slacko64/vmlinuz mem=1950m pmedia=atahd psubdir=slacko64
initrd /slacko64/initrd.gz
}
menuentry "slacko64new (sda1/slacko64new)" {
set root=(hd0,1)
linux /slacko64new/vmlinuz pmedia=atahd psubdir=slacko64new
initrd /slacko64new/initrd.gz
}
menuentry "Puppy-dpup-stretch-7.5" {
set root=(hd0,1)
linux /dpup/vmlinuz pmedia=atahd psubdir=dpup
initrd /dpup/initrd.gz
}
menuentry "Puppy slacko 6.3.2 (sda1/slacko)" {
set root=(hd0,1)
linux /slacko/vmlinuz mem=1950m pmedia=atahd psubdir=slacko
initrd /slacko/initrd.gz
}
All the Puppies are installed in a partition with frugal installs. Ubuntu (xfce) is installed on another partition. And there is a data partition. The reason I have done this is because: it is very easy to swap the Puppies; I can easily install another main stream Linux Distro instead of the Ubuntu if I want and I can keep data safe from any changes I might make. Having Puppies and Ubuntu means that on occasions when I need a feature not easily available in Puppy I can use Ubuntu. The laptop is an ex Chromebook Acer 720 with a dual core Celeron 2955u 1.4 GHz CPU and 2 GB of RAM and so not dissimilar in performance to your PC.

The way forward for you is to get any USB Puppy going no matter how old and use that to set up other Puppies and maybe a Ubuntu, Mint, etc, as you want.

mikeslr · Post by **mikeslr** » Mon Nov 15, 2021 5:16 pm

You've told us you have a Mac computer; but you also told us that you have CentOS8. Are you trying to create a boot-able Puppy-on-a-USB-Key using the MacOS or the CentOS8?

The newest is not always the best-est. I don't know why newbies are urged to use the latest Puppy as their first Puppy. I would think that doing so is counter indicated because:
(1) newbies are almost always trying to find a version of Linux which they can use on an 'older' computer, one which doesn't respond well to the demands of the latest Windows, or major Linux distro. The mantra used to be "Newer Puppys for Newer Computers; Older Puppys for Older Computers." It's why we continue to maintain 'older Puppys' long after the major Linux distro --whose binaries were employed in the Puppy's creation-- have declared End-of-Life for that variant.
(2) Puppy does not have the human and computer resources of billionaire-backed Ubuntu, nor the large cadre of volunteers of debian or Slackware. Each Puppy has one author and, at best, a handful of testers. That's why --with the exception of FatDog and its dedicated Team-- we don't compile components from scratch but, instead, make use of the binaries compiled for the aforementioned distros. Despite their greater resources, and their trial balloons and testing periods, those distros often require 'up-grades' and 'bug-fixes' during the first year or so of their general availability to the public'.
(3) Puppys are not a 'spin' or 'remaster' of the distro with which they are 'binary-compatible'. What Puppys leave out is a lot of the bloat required by the RAM demanding File-Managers and Window-Managers and the 'infra-structure' to make use of those that such distros come with; providing, instead, light-weight File-Managers and Window-Managers and an infra-structure unique to Puppies. But sometimes what's left out turns out to be important even to Puppys. Usage by Puppy fans will reveal both such problem and its solution.
(4) Puppy's almost unique method of operating --as a Frugal Install which merges file-systems in RAM on boot-up-- is NOT the system installation applications were designed to deploy.
(5) Puppy's 'stock' File-and-Window managers, not being those commonly employed by other Linux Distros, may present a learning curve to even the seasoned Linux user.
Having to undertake that learning curve while discovering the challenges of deploying the newest Puppy to one's computer is just not the best way to introduce any newbie to Puppys.
Bionicpup64 was published in March of 2019, binary compatible with Bionic Beaver published the prior year. The Slackos --binary compatible to Slackware with it's upgrade only as necessary philosophy-- over a year ago. By now most of their problems have been encountered and solved; most 'rough-edges' smoothed.
From any functioning Puppy the deployment of any other Puppy is 'a piece of cake': and if that deployment reveals a problem what it also almost always reveals is that the problem is one of incompatibility or the absence of some driver. In short, to paraphrase Donald Runsfeld, "a known, known" rather than "an unknown, unknown."

daBee · Post by **daBee** » Mon Nov 15, 2021 6:15 pm

I tried making a bootable USB drive with an installer on it (as I had assumed) on both the Mac and my RP4. The latter took, but it still wouldn't load. CentOS8 is on the box right now, which I intend to overwrite.

Sorry, but I have moved on.

baldronicus · Post by **baldronicus** » Mon Nov 15, 2021 11:36 pm

Hi @daBee . I apologise for making a post here, I realise that you have "moved on". However, something came to mind that may, or may not, be relevant in a wider sense.

You describe the Shuttle as an "Atom" box, but the listing you provided indicates/suggests that the processor is a Celeron. I am not familiar with either the history/timing of Intel's chips, nor the release date, kernel etc., relating to Centos8.

Essentially, I am not sure whether the system would be impacted by lack of support regarding the Spectre/Meltdown mitigations. If it is, then you might find that your options regarding more recent releases of any Linux distro might be limited.

I would expect that you, and others here, would be more aware of whether this could be an issue or not, but I thought I should mention it, just in case.

Thanks.

daBee · Post by **daBee** » Mon Nov 15, 2021 11:41 pm

Who knows, I might be back. I'm just going with what the CentOS8 report told me.

Cheers

Puppy Linux Discussion Forum

USB Install How?

USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?

Re: USB Install How?