It does seem to be pointing to a hardware specific problem.
Not on all hardware, as wizard is not having issues.
Thanks for checking wizard!
Thanks retiredt00 for your ideas on what to look at for clues!
Are we having fun now?
Moderator: Forum moderators
It does seem to be pointing to a hardware specific problem.
Not on all hardware, as wizard is not having issues.
Thanks for checking wizard!
Thanks retiredt00 for your ideas on what to look at for clues!
Are we having fun now?
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
@bigpup
You may want to change the 60 seconds to a shorter period like 5 seconds for convenience. Script to edit is normally /usr/sbin/shutdownconfig.
I noticed such similar behavior a few months ago in vdpup64 (v. 9.2.x).
No one else confirmed it at the time. I solved it by shortening the interval in /etc/rc.d/rc.shutdown from 60 sec to a lower value (I never save on shutdown so no problem).
This mechanism worked for me without a problem in Bionicpup64 and in Fossapup64 9.5.
If I remember correctly, in earlier releases of FP96, everything also worked as it should. However, I noticed this small problem in FP-96_2 (as you did). So I shortened the interval again and hope everything will be ok. I have no idea what could be the cause.
I have a feeling that the problem is with the boot stanza synrtax and the pmedia=
setting changes made because of a boot problem.
The fix switched the pmedia=
from CD to use USB as the setting and this might be the difference.
You have to be using the boot menu entry, that has pmedia=usbflash, to get an option to save or not save, at shutdown or reboot.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
Big, I've tried a couple of different configurations:
1. Conventional UEFI, small fat32 with only the boot files, Puppy and save folder on a second ext3 partition.
2. 1gb fat32 with both UEFI boot files and Puppy, Save folder on second ext3 partition.
Haven't been able to replicate the errors you had.
Thanks
wizard
Big pile of OLD computers
Thanks!
Well I always tell people with a strange issue.
Delete the install.
Do a fresh new download of the ISO
Do a new clean install.
I am going to try that and see what happens.
You can all flame me if that works
Update:
No change.
That did not help to fix!
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
I'm not sure how many of these changes are woof-CE changes or F96_CE-specific
F96-CE was built from a woof-CE generated Fossapup64-9.6 and there are no specific changes that we made for F96. What ever is going on to freeze the save selection crept in somewhere. We'll keep on debugging this but I still have not replicated it yet.
Working at it.....
The things you do not tell us, are usually the clue to fixing the problem.
Who said that??
Give me details of how you created your USB so I can duplicate that.
wizard
Big pile of OLD computers
I used Unetbootin v702 running in Fossapup64 9.5
The USB stick has one partition formatted fat32.
----------------------------------------------------------------------------------------------------------
This really seems to be a specific computer hardware issue.
I tried using the USB stick on a different computer.
It shutdown normal.
Offered save or no save.
Could select save or no save .
Press enter and it did what I selected.
-----------------------------------------------------------------------------------------------------------------------
So something about that first computer and it's hardware is the issue.
The computer is a very new desktop with case front USB ports.
The USB stick is plugged into one of the case front ports.
The USB ports are cable connected to a motherboard front port connector, so not direct USB ports on the motherboard.
Unless you have some idea that just jumps out at you!
I will work with it, as it is, and keep throwing ideas at it, when they come up in my brain!
It is going to be one of those problems, that one day the light will come on, smack your head, and that is the fix!
I have stopped having fun right now
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
Have you tried booting using Grub2config?Maybe worth an elimination test.
What make and model is this desktop PC?
Notice:
Anyone that has been posting in this topic about issues retiredt00 has been having.
He/she have their own topic to discuss the issue specific to them.
viewtopic.php?t=8185
Let's keep this one about original issue.
Thanks!!
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
Note:
This issue is showing up only on one computer I have.
So must be hardware dependent.
viewtopic.php?p=83483#p83483
If this F96-CE_2 is loosely based on Fossapup64 9.5
Fossapup64 9.5 shuts down asking to save or not save and you can choose.
So it works in Fossapup64 9.5 on this computer.
Is F96-CE_2 still using the same shutdown script files or are they modified in some way?
I am not sure what all gets used, when you do a shutdown or reboot.
rc.shutdown seems to have the coding for asking to save or not save.
I guess I need to figure out what Fossapup64 9.5 is using and compare it's files to F96-CE_2 files.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
Yes,
Grub.cfg file on the USB stick is what boot menu entries are being used. UEFI computer.
--------------------------------------------------------------------------------------------------------------------------------------
Desktop home built PC specs:
Motherboard Vendor: Micro-Star International Co., Ltd.
Product Name: MPG Z390 GAMING PLUS (MS-7B51)
CPU:
Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz
Min/Max Speed: 800/4700 MHz
Current Speed of Core 0:4497 MHz, 1:4428 MHz, 2:4487 MHz, 3:4412 MHz, 4:4415 MHz, 5:4482 MHz, 6:4458 MHz, 7:4493 MHz
Core Count: 8
Thread Count: 8
32GB of RAM
Graphics hardware:
Nvidia Geforce RTX 2060
6 GB of memory on card.
Using Nvidia 450.57 driver and graphics control program.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected