Problems remastering bionicpup32

[maoo]

Hi people...
after my other question "how to remaster bionicpup32 from full installed one" ( viewtopic.php?f=2&t=715 ) ive frugally instaled bionicpup32 in my another "old pc" (specifications listed bellow). Ive installed all the software i need and love, and then ive tryed to remaster it for installing it to another "old PC",a desktop one (many old pcs are throwed away this days,for considering them obsolete... thanks team for making it easier for us to keep them alive) . But after creating the ISO file and creating a booteable usb stick with unetbooting and booting it something went wrong.
after some RED lines it says:

pausing for 60 seconds..."
loading puppy main sfs file.
Dumping last lines of /tmp/bootinit.log
4:ONE_PART=sdb
MENU_MAX_PUPSAVES=
5:ONE_PART=sdb PSUBDIR= P_BP_FN= P_DEF_FN=puppy_upupbb_19.03.sfs
6: ONE_PART=sdb ONE_TRY_FN=/puppy_upupbb_19.03.sfs PDRV=sdb, iso9660, /puppy_upupbb_19.03.sfs
Dumping last lines of kernel log...
sdb: sdb1
sd 4:0:0:0: (sdb) Attached SCSI removable disk
ISO 9660 Extensions: RRIP_1991A
random: crng init done
*** sdb /puppy_upupbb_19.03.sfs mount of sfs failed
***Error is too critical, dropping out to console....
***To save debug info to partition, type "debugsave"
/#

---------------------------------------------------------wow.... what happened?

So, the pc in wich i have made the ISO image and the booteable USB specifications are these:

descripción: Notebook
producto: HP 530 Notebook PC (KR381AA#ABM)
fabricante: Hewlett-Packard
versión: F.06
serie: CND8122DBM
anchura: 32 bits
capacidades: smbios-2.4 dmi-2.4
configuración: boot=normal chassis=notebook family=103C_5336AN sku=KR381AA#ABM uuid=B526F1D1-E0F6-DC11-4D88-66991015D529
*-core
descripción: Placa base
producto: 30D5
fabricante: Hewlett-Packard
id físico: 0
versión: KBC Version 82.15
*-firmware
descripción: BIOS
fabricante: Hewlett-Packard
id físico: 0
versión: 68MVU Ver. F.06
date: 12/10/2007
tamaño: 128KiB
capacidad: 960KiB
capacidades: pci pcmcia pnp upgrade shadowing cdboot bootselect edd int13floppy720 int5printscreen int9keyboard int14serial int17printer acpi usb ls120boot smartbattery biosbootspecification netboot
*-cpu
descripción: CPU
producto: Intel(R) Core(TM) Duo CPU T2600 @ 2.16GHz
fabricante: Intel Corp.
id físico: 4
información del bus: cpu@0
versión: 6.14.12
serie: 0000-06EC-0000-0000-0000-0000
ranura: U10
tamaño: 1262MHz
capacidad: 2167MHz
anchura: 32 bits
reloj: 166MHz
capacidades: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon bts cpuid aperfmperf pni monitor vmx est tm2 xtpr pdcm dtherm cpufreq
configuración: id=0
*-cache:0
descripción: L1 caché
id físico: 5
ranura: Internal L1 Cache
tamaño: 64KiB
capacidad: 64KiB
capacidades: burst internal write-back unified
configuración: level=1
*-cache:1
descripción: L2 caché
id físico: 6
ranura: Internal L2 Cache
tamaño: 2MiB
capacidad: 2MiB
capacidades: burst external write-back unified
configuración: level=2
*-logicalcpu:0
descripción: CPU lógica
id físico: 0.1
anchura: 32 bits
capacidades: logical
*-logicalcpu:1
descripción: CPU lógica
id físico: 0.2
anchura: 32 bits
capacidades: logical
*-memory
descripción: Memoria de sistema
id físico: a
ranura: Placa de sistema o placa base
tamaño: 1GiB
*-bank:0
descripción: SODIMM DDR2 Síncrono 667 MHz (1,5 ns)
producto: 64T128021EDL3SB2
fabricante: Infineon (Siemens)
id físico: 0
serie: 0300C514
ranura: DIMM #1
tamaño: 1GiB
anchura: 64 bits
reloj: 667MHz (1.5ns)
*-bank:1
descripción: SODIMM DDR2 Síncrono [vacío]
id físico: 1
ranura: DIMM #2
*-pci
descripción: Host bridge
producto: Mobile 945GSE Express Memory Controller Hub
fabricante: Intel Corporation
id físico: 100
información del bus: pci@0000:00:00.0
versión: 03
anchura: 32 bits
reloj: 33MHz
*-display:0
descripción: VGA compatible controller
producto: Mobile 945GSE Express Integrated Graphics Controller
fabricante: Intel Corporation
id físico: 2
información del bus: pci@0000:00:02.0
versión: 03
anchura: 32 bits
reloj: 33MHz
capacidades: msi pm vga_controller bus_master cap_list rom
configuración: driver=i915 latency=0
recursos: irq:16 memoria:f0400000-f047ffff ioport:3000(size=8) memoria:e0000000-efffffff memoria:f0480000-f04bffff memoria:c0000-dffff
*-display:1 NO RECLAMADO
descripción: Display controller
producto: Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller
fabricante: Intel Corporation
id físico: 2.1
información del bus: pci@0000:00:02.1
versión: 03
anchura: 32 bits
reloj: 33MHz
capacidades: pm bus_master cap_list
configuración: latency=0
recursos: memoria:f0500000-f057ffff
*-multimedia
descripción: Audio device
producto: NM10/ICH7 Family High Definition Audio Controller
fabricante: Intel Corporation
id físico: 1b
información del bus: pci@0000:00:1b.0
versión: 01
anchura: 64 bits
reloj: 33MHz
capacidades: pm msi pciexpress bus_master cap_list
configuración: driver=snd_hda_intel latency=0
recursos: irq:25 memoria:f0580000-f0583fff
*-pci:0
descripción: PCI bridge
producto: NM10/ICH7 Family PCI Express Port 1
fabricante: Intel Corporation
id físico: 1c
información del bus: pci@0000:00:1c.0
versión: 01
anchura: 32 bits
reloj: 33MHz
capacidades: pci pciexpress msi pm normal_decode bus_master cap_list
configuración: driver=pcieport
recursos: irq:16 ioport:4000(size=4096) memoria:40000000-401fffff ioport:40200000(size=2097152)
*-pci:1
descripción: PCI bridge
producto: NM10/ICH7 Family PCI Express Port 2
fabricante: Intel Corporation
id físico: 1c.1
información del bus: pci@0000:00:1c.1
versión: 01
anchura: 32 bits
reloj: 33MHz
capacidades: pci pciexpress msi pm normal_decode bus_master cap_list
configuración: driver=pcieport
recursos: irq:17 ioport:5000(size=4096) memoria:f0000000-f00fffff ioport:40400000(size=2097152)
*-network
descripción: Interfaz inalámbrica
producto: PRO/Wireless 3945ABG [Golan] Network Connection
fabricante: Intel Corporation
id físico: 0
información del bus: pci@0000:10:00.0
nombre lógico: wlp16s0
versión: 02
serie: 00:1f:3c:00:27:f5
anchura: 32 bits
reloj: 33MHz
capacidades: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuración: broadcast=yes driver=iwl3945 driverversion=4.15.0-20-generic firmware=15.32.2.9 ip=192.168.5.119 latency=0 link=yes multicast=yes wireless=IEEE 802.11
recursos: irq:24 memoria:f0000000-f0000fff
*-usb:0
descripción: USB controller
producto: NM10/ICH7 Family USB UHCI Controller #1
fabricante: Intel Corporation
id físico: 1d
información del bus: pci@0000:00:1d.0
versión: 01
anchura: 32 bits
reloj: 33MHz
capacidades: uhci bus_master
configuración: driver=uhci_hcd latency=0
recursos: irq:20 ioport:3020(size=32)
*-usbhost
producto: UHCI Host Controller
fabricante: Linux 4.15.0-20-generic uhci_hcd
id físico: 1
información del bus: usb@2
nombre lógico: usb2
versión: 4.15
capacidades: usb-1.10
configuración: driver=hub slots=2 speed=12Mbit/s
*-usb
descripción: Ratón
producto: USB Optical Mouse
fabricante: Sunplus Innovation Technology Inc.
id físico: 2
información del bus: usb@2:2
versión: 0.13
capacidades: usb-2.00
configuración: driver=usbhid maxpower=98mA speed=1Mbit/s
*-usb:1
descripción: USB controller
producto: NM10/ICH7 Family USB2 EHCI Controller
fabricante: Intel Corporation
id físico: 1d.7
información del bus: pci@0000:00:1d.7
versión: 01
anchura: 32 bits
reloj: 33MHz
capacidades: pm debug ehci bus_master cap_list
configuración: driver=ehci-pci latency=0
recursos: irq:20 memoria:f0584000-f05843ff
*-usbhost
producto: EHCI Host Controller
fabricante: Linux 4.15.0-20-generic ehci_hcd
id físico: 1
información del bus: usb@1
nombre lógico: usb1
versión: 4.15
capacidades: usb-2.00
configuración: driver=hub slots=8 speed=480Mbit/s
*-pci:2
descripción: PCI bridge
producto: 82801 Mobile PCI Bridge
fabricante: Intel Corporation
id físico: 1e
información del bus: pci@0000:00:1e.0
versión: e1
anchura: 32 bits
reloj: 33MHz
capacidades: pci subtractive_decode bus_master cap_list
recursos: ioport:2000(size=4096) memoria:f0100000-f03fffff
*-pcmcia
descripción: CardBus bridge
producto: CB1410 Cardbus Controller
fabricante: ENE Technology Inc
id físico: 6
información del bus: pci@0000:02:06.0
versión: 01
anchura: 32 bits
reloj: 33MHz
capacidades: pcmcia bus_master cap_list
configuración: driver=yenta_cardbus latency=176 maxlatency=5 mingnt=192
recursos: irq:18 memoria:f0100000-f0100fff ioport:2400(size=256) ioport:2800(size=256) memoria:44000000-47ffffff memoria:48000000-4bffffff
*-network
descripción: Ethernet interface
producto: 82562ET/EZ/GT/GZ - PRO/100 VE (LOM) Ethernet Controller Mobile
fabricante: Intel Corporation
id físico: 8
información del bus: pci@0000:02:08.0
nombre lógico: enp2s8
versión: 01
serie: 00:1e:ec:1a:73:d4
tamaño: 10Mbit/s
capacidad: 100Mbit/s
anchura: 32 bits
reloj: 33MHz
capacidades: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuración: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.24-k2-NAPI duplex=half latency=64 link=no maxlatency=56 mingnt=8 multicast=yes port=MII speed=10Mbit/s
recursos: irq:20 memoria:f0101000-f0101fff ioport:2000(size=64)
*-isa
descripción: ISA bridge
producto: 82801GBM (ICH7-M) LPC Interface Bridge
fabricante: Intel Corporation
id físico: 1f
información del bus: pci@0000:00:1f.0
versión: 01
anchura: 32 bits
reloj: 33MHz
capacidades: isa bus_master cap_list
configuración: driver=lpc_ich latency=0
recursos: irq:0
*-ide
descripción: IDE interface
producto: 82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode]
fabricante: Intel Corporation
id físico: 1f.2
información del bus: pci@0000:00:1f.2
versión: 01
anchura: 32 bits
reloj: 66MHz
capacidades: ide pm bus_master cap_list
configuración: driver=ata_piix latency=0
recursos: irq:21 ioport:1f0(size=8) ioport:3f6 ioport:170(size=8) ioport:376 ioport:3040(size=16)
*-scsi:0
id físico: 1
nombre lógico: scsi0
capacidades: emulated
*-disk
descripción: ATA Disk
producto: WDC WD1200BEVS-6
fabricante: Western Digital
id físico: 0.0.0
información del bus: scsi@0:0.0.0
nombre lógico: /dev/sda
versión: 1A01
serie: WD-WXE208493060
tamaño: 111GiB (120GB)
capacidades: partitioned partitioned:dos
configuración: ansiversion=5 logicalsectorsize=512 sectorsize=512 signature=31a431a3
*-volume:0
descripción: Windows NTFS volumen
id físico: 1
información del bus: scsi@0:0.0.0,1
nombre lógico: /dev/sda1
versión: 3.1
serie: c4a2e1e9-ba90-1440-bdb4-050828be350e
tamaño: 37GiB
capacidad: 37GiB
capacidades: primary bootable ntfs initialized
configuración: clustersize=4096 created=2012-02-26 08:07:46 filesystem=ntfs state=clean
*-volume:1
descripción: Extended partition
id físico: 2
información del bus: scsi@0:0.0.0,2
nombre lógico: /dev/sda2
tamaño: 74GiB
capacidad: 74GiB
capacidades: primary extended partitioned partitioned:extended
*-logicalvolume
descripción: partición EXT4
fabricante: Linux
id físico: 5
nombre lógico: /dev/sda5
nombre lógico: /
versión: 1.0
serie: 98a0cb88-4d56-4edc-91a5-c218cdc98e49
tamaño: 74GiB
capacidad: 74GiB
capacidades: journaled extended_attributes large_files huge_files dir_nlink recover 64bit extents ext4 ext2 initialized
configuración: created=2018-05-29 01:57:01 filesystem=ext4 lastmountpoint=/ modified=2020-09-09 11:18:14 mount.fstype=ext4 mount.options=rw,relatime,errors=remount-ro,data=ordered mounted=2020-09-09 11:18:20 state=mounted
*-scsi:1
id físico: 2
nombre lógico: scsi1
capacidades: emulated
*-cdrom
descripción: DVD-RAM writer
producto: DVDRAM GSA-T20N
fabricante: HL-DT-ST
id físico: 0.0.0
información del bus: scsi@1:0.0.0
nombre lógico: /dev/cdrom
nombre lógico: /dev/cdrw
nombre lógico: /dev/dvd
nombre lógico: /dev/dvdrw
nombre lógico: /dev/sr0
versión: WC05
capacidades: removable audio cd-r cd-rw dvd dvd-r dvd-ram
configuración: ansiversion=5 status=nodisc



-------------------------------------------- I apreciate your time, im loving the puppy project, thanks a lot. Good work!

[mikeslr]

Sorry maoo, reading computerese is not among my strong suites. However, maybe this may help.
How did you do the remaster? I find the builtin remaster confusing.
Below I’ll discuss three alternatives to the “remaster” built into Puppies: two remaster alternative’s and nic007’s Save2sfs. If you use ANY REMASTER application, during the remaster process you’ll still be asked if you want to modify /root or /etc. Don’t. This is where things get screwed up especially if you do not intend to use the remaster on the same computer. The purpose modifying /root or /etc is that you can include setting and customizations. But many of these setting and customization were made for that specific computer.

Shinobar's remasterx can be found here, http://hg.shinobar.server-on.net/puppy/opt/. It is almost identical to the builtin except that you make all your decisions at the very beginning rather than as the process takes place. You can find a screenshot of the GUI here, http://www.murga-linux.com/puppy/viewtopic.php?t=94033

Important points on filling out the GUI. I do make zdrv as a seperate sfs. The zdrv.sfs holds drivers and firmware. Later I may want to change the kernel or use a kernel which works better on a different computer. Drivers are kernel-specific. If I change kernels, I also have use the drivers for that kernel. That’s much easier to do if zdrv is separate [almost impossible if it isn't].
“The Bootable CD” is the folder of your current Puppy. That folder should have all the files from the ISO.
I don’t check “Check the kernel ID” as I may already have changed it.
I don’t “Localize”. As shinobar used that term it mean to only include the drivers and firmware in use on the computer running that Puppy. Drivers and firmware for other computer’s will be lacking.
FYI, xz compression results in smaller files, but takes slightly longer to boot.
Shinobar’s remasterx does will not include boot files needed to boot UEFI even if they were in the original ISO. Nor will it create a top level /home folder. It predates their implementation in Puppies.

Nic007 has published a suite of utilities, viewtopic.php?f=106&t=196 which also includes a User-friendly Remaster module. My experience is that it is faster than shinobar’s, but doesn’t retain the initial boot into “QuickSetup first-run settings”. Maybe that’s been changed since I last used it. But it’s only important if you’re not already familiar with Puppy: you can always run Menu>Setup> QuickSetup first-run settings. You only need to know to do that. When using nicOS-remaster, you’ll recognize the same choices as I mentioned above.

Frankly, I much prefer the nicOS-Save2SFS. What this does is save the contents of the SaveFile/Folder into your choice of either an adrv.sfs or a ydrv.sfs. Let’s say you chose to make an adrv.sfs. After you've made an adrv.sfs, move the it next to the other ‘system’ files on the originating computer. Boot pfix=ram so as not to use the SaveFile/Folder. [If using grub4dos, scroll to choose Advanced Menu; pfix=ram is the 2nd listing]. Everything should be as it was when using the SaveFile/Folder except perhaps some setting may not having been preserved. [At this point I usually move the old SaveFile/Folder someplace where Puppy won’t find/use it. I’ll keep it for a few days to make certain ‘all is well’, then delete it]. You can make any necessary adjustments and create a SaveFile/Folder.

On the other computer just place the adrv.sfs with the other system files before booting the first time. It will be as if the Puppy’s Dev had included it in the ISO.

The reason this works has to do with how a Puppy prioritizes the file-systems it uses. The applications the Puppy’s dev included are located in the Puppy_VERSIONS_NUMBER.sfs. The applications in an adrv.sfs or a ydrv.sfs have a higher priority and will be used if two versions of an application are available. The applications, settings and customizations you preserve in a SaveFile/Folder have the highest priority. If settings in an adrv/ydrv.sfs won’t work on a different computer, Puppy will try to use the application’s default setting and if that fails not run the application. But the application is present so you should be able to configure it for this other computer.
Having the ability to create a ‘new’ SaveFile/Folder, you can include new applications in that. Then, when you are ready, having previously created an adrv.sfs you can, again, unload application.sfses* but with the adrv.sfs in use, re-run nicOS-Save2sfs, choosing to create a ydrv.sfs. This ydrv.sfs will include those applications which were in the adrv.sfs and your SaveFile/Folder. Before rebooting –again pfix=ram-- rename the adrv.sfs, say 1adrv.sfs, so that it Puppy won’t use it on reboot.
I should mention that creating an adrv.sfs or a ydrv.sfs takes much less time than remastering. In fact, only a couple of minutes. So, if you wanted you could 'update' your system often.

I know there as way to use application.sfs without a SaveFile/Folder. I just don't know the recipe. It's how nic runs his systems. As a SaveFile/Folder is Puppy's only READ/WRITE system file, running with READ only system files is safer.

-----
* By an 'application.sfs' I mean an application or suites packaged as an sfs. Examples are LibreOffice.sfs and firefox.sfs.

[nic007]

Looks more like a booting problem than anything else. I would do a manual frugal install on the USB drive. Don't know anything about unetbootin.

[maoo]

hi guys, problem solved: I just did everything again from the native remastering tool and then i just make a booteable usb by the puppy native way, and it worked, but...
Everything was going well, but when i boot my device, it cames up the system with the themes, icons, buttons, etc as i have configured it, but, without my wall paper, i dont care about it, but the software that i had installed wasnt there either... And my intentions where to install all software only once in one computer and then make an iso file and install it to some others computers around my neighborhood, saving that way a hole lot of time and giving a second time to some obsolete hardware round here. So, now the question is this:

How can i make a puppy based distribution with my favourite software on an iso file?

thanx again for your time community.

[nic007]

Hi, Mike.

Nor will it create a top level /home folder. It predates their implementation in Puppies.

Well, the /home folder is well-known (even with older Puppys) but is explicitly excluded (deleted) by the remaster script. This is problably because it contained all sorts of crap in the past which should not be included in a remaster. It seems some applications now install to this folder, maybe you can let us know what is being stored in that folder and how those applications have been installed.

but doesn’t retain the initial boot into “QuickSetup first-run settings”

Correct but done so on purpose because the QuickSetup is inadequate. It will start with the second user screen (which follows the QuickSetup screen anyway). The second screen has a Setup button with full access to all setups.

On the other computer just place the adrv.sfs with the other system files before booting the first time.

Keep in mind that the save2sfs utility would have saved the hardware settings of the other computer so you may have problems booting with the new computer (this is one benefit of remastering as you can choose to retain hardware settings or not). However, you will probably succeed in booting by using the pfix=nox parameter. In the latter case, the booting process will stop so that you can run xorgwizard. PS. I may have a look at the save2sfs script again and add the option to ignore the current hardware settings.

I know there as way to use application.sfs without a SaveFile/Folder. I just don't know the recipe.

Very easy actually. All the newer Pyppys have sfs_load already installed. So you can load an sfs file on-the-fly during a session by left-clicking the sfs file and follow the instructions. I have a few sfs files that I always want to load beforehand because I use it every session. So, I place a command for these in /etc/rc.d/rc.local. For example, I want palemoon.sfs to load automatically after bootup so place the following command in /etc/rc.d/rc.local:
sfs_load -c -q /NAME OF DIRECTORY/palemoon.sfs

[nic007]

hi guys, problem solved: I just did everything again from the native remastering tool and then i just make a booteable usb by the puppy native way, and it worked, but...
Everything was going well, but when i boot my device, it cames up the system with the themes, icons, buttons, etc as i have configured it, but, without my wall paper, i dont care about it, but the software that i had installed wasnt there either... And my intentions where to install all software only once in one computer and then make an iso file and install it to some others computers around my neighborhood, saving that way a hole lot of time and giving a second time to some obsolete hardware round here. So, now the question is this:

How can i make a puppy based distribution with my favourite software on an iso file?

thanx again for your time community.

How did you install the software? My utility suite has two remaster scripts. You can try both.

[maoo]

Hi @nic007, ive installed the software throw the package installing tool, the native one. And i installed wordpress and lamp stack throw bitnami installer. I havent tryed your tool nic, do you think it will package my software into the iso file? if you say so ill try it today if i count with enough energy after my journey. If not, tomorrow. Then i post the results. Any other consideration?
For being more clear: What i want is to pack my installed software (important: firefox plugins too) and the look and feel (wallpaper, compton:ON, themes, icons, buttons as i had configurated it) on an ISO to make a bionicpup32 booteable (and installable) USB. In order to make the work only once and share it with my neighbors -they know even less than me, and also have slow and "obsoletes" equipment-
Ok, if you have some extra consideration, please let me know. As i sayd, when i have the results ill let you know. Thanks for your time.

[nic007]

Hi @nic007, ive installed the software throw the package installing tool, the native one. And i installed wordpress and lamp stack throw bitnami installer. I havent tryed your tool nic, do you think it will package my software into the iso file? if you say so ill try it today if i count with enough energy after my journey. If not, tomorrow. Then i post the results. Any other consideration?
For being more clear: What i want is to pack my installed software (important: firefox plugins too) and the look and feel (wallpaper, compton:ON, themes, icons, buttons as i had configurated it) on an ISO to make a bionicpup32 booteable (and installable) USB. In order to make the work only once and share it with my neighbors -they know even less than me, and also have slow and "obsoletes" equipment-
Ok, if you have some extra consideration, please let me know. As i sayd, when i have the results ill let you know. Thanks for your time.

The remaster tool should include all changes to your system, ie. the contents of your savefile/folder. The software you install via the puppy's package manager should be included. I'm not familiar with the wordpress installation. It installs to where?