Keyboard,touchpad NOT work after Remaster right after install to USB,Bookworm

[Lightsky]

Hi!

I installed BookwormPup64_10.0.8.iso to USB flash drive from VM, using Frugalpup->e4stickpup.

Next I boot physical Intel laptop from this freshly installed USB drive, and all I do is only one very simple change like enable touchpad via GUI (its disabled on boot).
Next reboot with saving session (still everything looks good after reboot w/o remaster).

Next do Menu->setup-> Remaster puppy classic.
Remaster doesn't show any error.
Tried both RAM and USB work dir for remaster.

After this very simple remaster and reboot none of the keyboard,touchpad, nor trackpad work.
I.e. all the input devices are disabled and no reaction to any button nor touchpad.

Also resolution becomes smth like 640x480 (have to guess, but pointer looks huge).

Tried both default options #2 & # 4 (i.e. rebuild SFS) selected), and also #2 & # 4 +#3 selected - always same behaviour as above.
System monitoring widget on the right still works, so its not a deadfreeze.

Any advice?

Is there a way to modify fstab/etc files w/o remaster?
My understanding is that upper overlay is not used until its too late in the boot process.
Even adding a script to the end of ~/.profile didn't give any reaction.

Haven't tried external input devices yet.
Thank you.

[Jasper]

What did you remove/add to the 'remastering'?

Do you mean 'advice' ?

Your topic respondents will be advisors.

[ozsouth]

@Lightsky - Welcome!
No need to remaster. You can put your settings in a ydrv, which loads later than puppy drv & is used for settings like yours.

EITHER:

1. Make an empty folder (let's call it myset) - in a terminal run: mkdir /myset
2. inside that folder, make your structure, i.e. in a terminal run: mkdir /myset/etc
3. copy your changed settings/files into that, i.e. /myset/etc/fstab
4. in a terminal run: cd / and then run: mksquashfs /myset ydrv_dpupbw64_10.0.8.sfs
5. copy ydrv_dpupbw64_10.0.8.sfs into same folder as puppy_dpupbw64_10.0.8.sfs & reboot

OR:

If there is nothing in /mnt/data , can create a blank sfs thus:
In a terminal run: mksquashfs /mnt/data ydrv_dpupbw64_10.0.8.sfs

THEN:

Once you have a ydrv, you can edit it via this program: viewtopic.php?p=128286#p128286

[Lightsky]

What did you remove/add to the 'remastering'?

Did not remove/add anything to the remastering.
The only change I did is enabled touchpad via GUI as described in 1st post.

[Lightsky]

Do you mean 'advice' ?

Fixed.

[Lightsky]

No need to remaster. You can put your settings in a ydrv, which loads later than puppy drv & is used for settings like yours.

Thank you!
Do I need to merge my fstab with default puppy fstab so that it boots correctly?
Not sure if puppy uses any default fstab?

If yes, were can I find original puppy fstab?

[bigpup]

For what you are trying to do.

Just boot and make the config and settings changes.

Shutdown making a save file or folder to store these changes, placing the save on the USB drive.

Now when you boot using the save, everything is setup how you want it.
The save is specifically setup for that computer it was made on.

If you boot on a different computer.
The settings in the save may or may not be correct for this computer.
But they are easy to now change for it.

If you remaster with specific settings and configurations for a specific computer and hardware.
You have made a Puppy version that is just for that specific computer.

Puppy is designed to boot using a save that was setup on a different computer.
If settings in the save are not going to work on a different computer.
It will still boot to a working desktop.
Now you adjust settings for this computer.
Usually always needed to change settings for network setup, because no two computers are usually using the same network connection hardware.

If you go back and forth between computers.
You can make a specific save for each one.
choose which save to use on boot up.

[Lightsky]

I already implemented ozsouth's approach with ydrv (still not sure about fstab questions above though).

Now need to install some service supporting LUKS/crypttab or similar - I believe its missing.
Quick search on this forum didn't show many pages about auto mounting LUKS partition or crypttab.

Should I install services with APT?
Which type of services system Bookworm uses? openrc?

Not trying to boot Puppy from LUKS, its on another internal drive, just hope to automate "cryptsetup luksOpen" for another internal drive and following mounting steps some time after boot.

[ozsouth]

@Lightsky - puppy doesn't use fstab these days (by default drives are detected on boot or insertion), so whatever suits your purposes should be ok. Your Bookworm specifics are not commonly sought, so it's best someone with more debian experience answers that.

[bigpup]

Start a new topic on this question?

It is best for getting help, if the subject of the topic is about one single issue or question.

So make a new topic for this new question.

[Lightsky]

If you remaster with specific settings and configurations for a specific computer and hardware.
You have made a Puppy version that is just for that specific computer.

Thats perfectly fine. No portability is needed for my use case.

[Lightsky]

So make a new topic for this new question.

Done.
viewtopic.php?t=12967
It would still be great to be able to do a remastering or backup or an image of my flash drive setup though, especially given that there's a quite a bit of learning curve for me with puppy.
Currently, the built-in GUI remastering is unusable on my laptop.

Likely "dd" will not work e.g. to migrate it to another USB drive.

[bigpup]

For what you want to do the ydrv method is probably the option to use.

But if you make a save that has the setup you want.

It is going to get layered into the file system just like a ydrv.sfs does.

Actually anything that is in the save is used instead of anything that is in any of the other Puppy SFS files.
The stuff in the save, will change what has been provided by the other SFS files, to make the complete operating file system.

All of these different SFS's and the save are a Linux file system inside a file.
Layered together, they form the complete operating file system.

Example of what the save does:
A program in the Puppy version has a configuration file, with default settings.
You change the settings for this program.
In the save is stored a copy of this configuration file, with the changes in it.
When Puppy boots using the save.
The operating file system will be using the configuration file that the save is providing. Not the original configuration file.

[Lightsky]

It is going to get layered into the file system just like a ydrv.sfs does.

Actually anything that is in the save is used instead of anything that is in any of the other Puppy SFS files.
The stuff in the save, will change what has been provided by the other SFS files, to make the complete operating file system.

All of these different SFS's and the save are a Linux file system inside a file.
Layered together, they form the complete operating file system.

Thank you, I have some experience with overlayfs (not with such a complex setup as in Bookworm though).
The main question here is at what point in boot process overlayfs gets mounted for ROOTFS and what happens next?
It may be mounted late in boot process and then fstab in "save" SFS may not have affect on boot.