"PAM failure" after 1st reboot of Fossapup from USB (Solved)

[t0c]

Hi ppl,

i'm new to puppy linux, and this Fossapup64 is really great, finally small distro that can use my built-in wifi card, and got workable samba gui apps, its fast, all good until i do first reboot

1. clone ISO on USB
2. first boot, start live Puppy, no problem, easy config and stuff, really friendly enviroment
3. connect to router, connect and mount win10 shared folders, install nautilus, install plex media server, etc...
4. reboot (save session - yes)
5. "PAM failure, aborting: Critical error - immediate abort" computer hangs and no login possible

------------

6. had to clone ISO on USB again (bcs PAM error is on my every next boot tryout)
7. again fresh first live boot
8. now i tried - ok, lets install it on hdd
9. gpart, format, partitions, install, grub... all good.
10. first boot of FossaPup64 fromm HDD - all good,
11. installing few apps, connecting and mounting shares, testing PLEX media server, all good
12. reboot - and again some PAM failure, critical, aborting, ... nothing else is possible except to hard reset of laptop....

or, should i say - problem is after I save session for the 1st time and reboot

EDIT: i can get in system if i choose to start with "copy files to ram" option, and then i am again at zero, fresh system...

Any help please?

ps. sorry for my bad english

[bigpup]

If you look on the USB drive are there several .sfs files?
The Puppy Fossapup64, adrv, fdrv, and zdrv?

Delete the save you made and boot fresh again, not using a save.
Make simple settings and maybe the network connection.
Do nothing else.
Shutdown and make a save.
If only offered to make a save file. Make it 3 0r 4 GB size.

Boot now using normal boot menu entry and using the new save.

What now happens?

[t0c]

tnx

that worked, i do 2-3 operations and Save, reboot, and now it works like a charm

[bigpup]

You can put stuff outside of the save.
Stuff that is not installed or setting changes.
/mnt/home is a good place outside of the save.
Documents, downloaded stuff, videos, pictures, etc.... anything not actually installed into the OS.

[mikewalsh]

@t0c :-

I discovered, long ago, that if you try to do too much stuff before shutting-down and creating the "save", something 'trips a switch', somewhere, deep in the canine's bowels, and it throws a wobbly.

If your USB drive is still formatted as FAT32 - this is normal, as-it-comes-from-the-factory - you are in any case limited to no bigger than 4 GB. This is a limitation of the FAT32 file-system, and nothing can change that. Trouble is, with FAT32 you will only be offered a save-file, NOT the more flexible save-folder; that requires a Linux-formatted file-system, such as ext2, ext3 or ext4.

Bigpup's advice here is sound; much stuff like folders for 'Documents', 'Music', 'Videos', etc., can be situated outside the save, then sym-linked back into /root for easier access. I rather suspect you were installing more stuff than the maximum ability of Puppy to create a "save" for it.......with the "code bloat" of a lot of modern software, that's NOT hard to do.

Any questions, just ask.

Mike.

[mikeslr]

Hi t0c, welcome to the kennels ,

If the mention of "sym-linked back" went over your head, this post explains how to do it: viewtopic.php?p=2235#p2235. It's long-winded/information-packed. But you can skip down to the paragraph beginning "There’s an easy Workaround. And it forms the basis for all others.". Sym-links, AKA symbolic links, are Linux's more powerful version of what under Windows is known as 'short-cuts'.

You can skip down. But especially as you are running from a fat32 partition I recommend that you take the time to read the post.

[Clarity]

@t0c I seemed to remember similar problem.

Test the checksum of your downloaded ISO.

Code: Select all

md5sum fossapup...iso

Compare that with the md5 advertised with the ISO.

If it does not match, redownload and check again.