I am using Xenialpup64 on a USB3 stick and a Lenovo laptop with Core I3 chip. Sandybridge.
I read somewhere that Puppy doesn't like USB3, but except for booting with a 2FS file it doesn't seem to cause a problem.
Any ideas?
2FS file causes Puppy to crash during boot up.
What 2fs file?
Are you talking about a save file you made?
If yes.
Was the save made on this computer and made with this Xenialpup64?
How did you put Xenialpup64 on the USB stick?
What format is the partition on the USB stick?
Was the USB stick totally empty before the install?
If no.
If Windows did any writing to it.
The file system on it could be fragmented and putting a save file on it, could fragment the save.
That could cause the save to not work correctly.
However, if the USB3 stick is correctly made to the USB3 standards. It should be backwards compatible with USB1 and USB2.
Are you talking about a save file you made?
If yes.
Was the save made on this computer and made with this Xenialpup64?
What exactly does it do?crash during boot up
How did you put Xenialpup64 on the USB stick?
What format is the partition on the USB stick?
Was the USB stick totally empty before the install?
If no.
If Windows did any writing to it.
The file system on it could be fragmented and putting a save file on it, could fragment the save.
That could cause the save to not work correctly.
USB3 support by the hardware on the computer is the only thing that would affect Puppy.I read somewhere that Puppy doesn't like USB3
However, if the USB3 stick is correctly made to the USB3 standards. It should be backwards compatible with USB1 and USB2.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Thank you for your reply. My responses follow your questions.
It's a bit odd, isn't it?bigpup wrote:What 2fs file?
Are you talking about a save file you made?
Yes.
If yes.
Was the save made on this computer and made with this Xenialpup64?
Yes. It is named Xenialpup64save.2fs and its creation was prompted when I exited Puppy.
What exactly does it do?crash during boot up
When the computer is switched on, a blue screen appears asking how to install. With save file, without save file, with file checking, etc. It I select with save file, and with or without file checking, the boot proceeds happily until a black screen appears which starts by identifying the computer and proceeds to the words Call Trace, which are followed by various lines of which the last is:
[<ffffffffff819336a0>] ? entry_SYSCALL_64_fastpath+0x13/0x94, followed by end trace fa6b2...........etc.
How did you put Xenialpup64 on the USB stick?
I used Unetbootin on a PC running Windows 10. I have done this before with Slacko and Tahrpup without problems, but on a USB2 stick which has died.
What format is the partition on the USB stick?
vfat
Was the USB stick totally empty before the install?
No, but only a few Sandisk windows files which would have been wiped when the drive was formatted to vfat. The drive is a brand new 16GB Sandisk. Nowadays USB sticks tend to be USB3.
If no. If Windows did any writing to it.
See previous answer.
The file system on it could be fragmented and putting a save file on it, could fragment the save.
In that case, Unetbootin would appear to be the culprit. However, Puppy appears to think that the drive is OK. It reads it and writes to it.
That could cause the save to not work correctly.
Indeed.
USB3 support by the hardware on the computer is the only thing that would affect Puppy.I read somewhere that Puppy doesn't like USB3
However, if the USB3 stick is correctly made to the USB3 standards. It should be backwards compatible with USB1 and USB2.
Yes, and apart from crashing on boot up when trying to use the save file it seems to work. I can boot up successfully by choosing NOT to use the save file.
Well, I have found a workaround, which is to use an old usb2 stick which I found in a drawer. It boots happily now with the save file.
The only problem is that USB2 drives are now close to extinction, so a solution to the USB3 problem will become increasingly urgent.
That's assuming that USB3 IS the culprit of course, but the finger of suspicion points that way.
The only problem is that USB2 drives are now close to extinction, so a solution to the USB3 problem will become increasingly urgent.
That's assuming that USB3 IS the culprit of course, but the finger of suspicion points that way.
I need to know for sure.
You are using Xenialpup64-7.5?
Again any USB3 related problems are all about how the computer hardware handles USB3 devices.
I boot many Puppy versions on USB3 sticks with no problem.
I am still thinking something could be wrong with the VFAT file system on this drive.
Even if the file system is corrupted.
Puppy will still access it and use it.
The main corruption problem is caused by fragmentation of the save file.
The save gets made, but the contents are all over the drive, not in a continuous, all in one place location.
Do this check of the drive.
Run Gparted
Have the USB stick NOT mounted.
Delete the partition or partitions on it.
Repartition to one partition for the complete drive.
Format to fat32.
Flag partition as boot.
Right click on the partition.
Select check.
It should do a complete check of the partition and report no problems.
Try a new reinstall of Xenialpup64 and making a save file.
Unetbootin should be able to do the install, with no need to reformat it.
One possible problem is Unetbootin does not know about changing the pmedia= option for booting Puppy from different type devices.
Look on the USB stick for the syslinux.cfg file.
Open it in a text editor.
Anyplace you see an entry for pmedia=
Change it to pmedia=usbflash
There is also a grub.cfg file.
Do the same thing in it.
Even better would be do the install from a running Puppy and using the Puppy Universal Installer.
You are using Xenialpup64-7.5?
Again any USB3 related problems are all about how the computer hardware handles USB3 devices.
I boot many Puppy versions on USB3 sticks with no problem.
I am still thinking something could be wrong with the VFAT file system on this drive.
Even if the file system is corrupted.
Puppy will still access it and use it.
The main corruption problem is caused by fragmentation of the save file.
The save gets made, but the contents are all over the drive, not in a continuous, all in one place location.
Do this check of the drive.
Run Gparted
Have the USB stick NOT mounted.
Delete the partition or partitions on it.
Repartition to one partition for the complete drive.
Format to fat32.
Flag partition as boot.
Right click on the partition.
Select check.
It should do a complete check of the partition and report no problems.
Try a new reinstall of Xenialpup64 and making a save file.
Unetbootin should be able to do the install, with no need to reformat it.
One possible problem is Unetbootin does not know about changing the pmedia= option for booting Puppy from different type devices.
Look on the USB stick for the syslinux.cfg file.
Open it in a text editor.
Anyplace you see an entry for pmedia=
Change it to pmedia=usbflash
There is also a grub.cfg file.
Do the same thing in it.
Even better would be do the install from a running Puppy and using the Puppy Universal Installer.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Just to make sure I was not telling you something wrong.
I just did a Unetbootin install of Xenialpup64 7.5 to a USB3 stick.
Stick formatted fat32.
Booted it OK.
Shutdown making a save file.
Rebooted using the save.
Works OK for me.
Posting this from it now.
I did make a .3fs save file, which uses a Exit3 file system in it.
A .2fs save is using exit2.
Exit2 is easy to get corrupted.
Puppy usually gets around that problem by doing a file system check each time it boots.
In the boot menu.
Try using the boot entry that says it does a file system check.
It just takes a few seconds longer to boot.
I just did a Unetbootin install of Xenialpup64 7.5 to a USB3 stick.
Stick formatted fat32.
Booted it OK.
Shutdown making a save file.
Rebooted using the save.
Works OK for me.
Posting this from it now.
I did make a .3fs save file, which uses a Exit3 file system in it.
A .2fs save is using exit2.
Exit2 is easy to get corrupted.
Puppy usually gets around that problem by doing a file system check each time it boots.
In the boot menu.
Try using the boot entry that says it does a file system check.
It just takes a few seconds longer to boot.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Sorry, have to ask.
You are sure the save file is being placed on the USB3 stick?
You are sure the save file is being placed on the USB3 stick?
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Hello olddog.
Welcome to the kennels!
You're in good hands with bigpup and his various advices.
May I add something that was not mentioned? The quality or integrity of
the pupsave that was created.
I had the same problem the other day with a corrupted pupsave file. It
happens because of a power outage, or too early termination of a
process, or maybe another file was (re)named by accident with a 2fs or
3fs extension, and that file was not a real pupsave?
If a bad pupsave is the problem, at this early stage, the best and simplest
solution is to create a new one.
My 2¢. Bye for now.
Welcome to the kennels!
You're in good hands with bigpup and his various advices.
May I add something that was not mentioned? The quality or integrity of
the pupsave that was created.
I had the same problem the other day with a corrupted pupsave file. It
happens because of a power outage, or too early termination of a
process, or maybe another file was (re)named by accident with a 2fs or
3fs extension, and that file was not a real pupsave?
If a bad pupsave is the problem, at this early stage, the best and simplest
solution is to create a new one.
My 2¢. Bye for now.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Thank you for the kind words, and you are not wrong about Bigpup.
I shall remember your advice concerning corrupted save files, and take copies.
I shall remember your advice concerning corrupted save files, and take copies.
musher0 wrote:Hello olddog.
Welcome to the kennels!
You're in good hands with bigpup and his various advices.
May I add something that was not mentioned? The quality or integrity of
the pupsave that was created.
I had the same problem the other day with a corrupted pupsave file. It
happens because of a power outage, or too early termination of a
process, or maybe another file was (re)named by accident with a 2fs or
3fs extension, and that file was not a real pupsave?
If a bad pupsave is the problem, at this early stage, the best and simplest
solution is to create a new one.
My 2¢. Bye for now.
Good to see it worked.
I am not too sure the stuff in Windows that does formats is all that good a program.
Seems they care more about giving good support for ntfs and newer Windows formats.
That is a very simple formatting program in Windows.
That is why I always use Gparted.
More options.
And it check what it does when completed.
There is always the chance you got a USB stick going bad or has a manufacturing defect.
However, I have seen a lot of issues fixed by just doing a new partitioning, formatting, and fresh do over.
I am not too sure the stuff in Windows that does formats is all that good a program.
Seems they care more about giving good support for ntfs and newer Windows formats.
That is a very simple formatting program in Windows.
That is why I always use Gparted.
More options.
And it check what it does when completed.
There is always the chance you got a USB stick going bad or has a manufacturing defect.
However, I have seen a lot of issues fixed by just doing a new partitioning, formatting, and fresh do over.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Partitioning is something I do about once every seven years. Within that time memory fades and the software changes so it's always like starting again from scratch.
I have to say I found Gparted pretty good, and no trouble at all.
I have to say I found Gparted pretty good, and no trouble at all.
bigpup wrote:Good to see it worked.
I am not too sure the stuff in Windows that does formats is all that good a program.
Seems they care more about giving good support for ntfs and newer Windows formats.
That is a very simple formatting program in Windows.
That is why I always use Gparted.
More options.
And it check what it does when completed.
There is always the chance you got a USB stick going bad or has a manufacturing defect.
However, I have seen a lot of issues fixed by just doing a new partitioning, formatting, and fresh do over.