I've burned slacko-6.3.2-uefi.iso to a CD and am trying to boot HP/Compaq dc5700 desktop Intel Core 2 Duo, 4Gb RAM, no HDD. It prints the subject message and drops into some # prompt. What does this mean?
I've earlier tried slacko-6.3.0.iso and got the same symptom.
I've tried each of these commands:
puppy ide=nodma acpi=off
puppy acpi=force irqpoll
but they changed nothing.
I tried the same CD on a Lenovo ThinkPad laptop and it boots fine.
"puppy_slacko_6.3.2.sfs not found" error message
Specs:
https://support.hp.com/au-en/document/c00808962
::::::::
"I tried the same CD on a Lenovo ThinkPad laptop and it boots fine."
It seems that you have taken all reasonable steps, therefore try another Puppy.
Woof CE Debian Stretch
http://murga-linux.com/puppy/viewtopic.php?t=109789
Download from here:
http://smokey01.com/ttuuxxx/WoofCe/
stretch-7.0.0a1.iso 22-Mar-2017 05:39 285M
Boot off usb....cheap...you can make save files.
Chris.
https://support.hp.com/au-en/document/c00808962
::::::::
"I tried the same CD on a Lenovo ThinkPad laptop and it boots fine."
It seems that you have taken all reasonable steps, therefore try another Puppy.
Woof CE Debian Stretch
http://murga-linux.com/puppy/viewtopic.php?t=109789
Download from here:
http://smokey01.com/ttuuxxx/WoofCe/
stretch-7.0.0a1.iso 22-Mar-2017 05:39 285M
Boot off usb....cheap...you can make save files.
Chris.
In the specs for the computer.
That Serial, Parallel Enable/Disable, maybe
Could try Tahrpup 6.0.5 it uses an older Linux kernel that may have better support for the hardware.
Because it boots OK on another computer.
This is looking like hardware support issue.
Not all Puppies support all hardware.
That is why there are so many versions.
You really should have posted this in the other topic you made.
Could be a bios setting causing this issue.HP ProtectTools Security Software Suite with BIOS Configuration (Serial, Parallel, USB Enable/Disable), Credential Manager, Smart Card Manager
That Serial, Parallel Enable/Disable, maybe
Could try Tahrpup 6.0.5 it uses an older Linux kernel that may have better support for the hardware.
Because it boots OK on another computer.
This is looking like hardware support issue.
Not all Puppies support all hardware.
That is why there are so many versions.
You really should have posted this in the other topic you made.
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)
Try to go through a basic frugal install: copy at root dir of some partition of the hd initrd.gz, vmlinuz, puppy_slacko_6.3.2.sfs, zdrv_slacko_6.3.2.sfs and isolinux.cfg: then boot the cd and type the boot option:
In isolinux.cfg copied on the hd you should change pmedia=cd with pmedia=atahd.
Sometimes the main sfs not found on the cd is correctly discovered when copied on the hd.
Code: Select all
[boot:] puppy pmedia=atahdSometimes the main sfs not found on the cd is correctly discovered when copied on the hd.
tahr-6.0.5_noPAE.iso behaves exactly the same: "puppy_tahr_6.0.5.sfs not found". Here is how it looks from Win7:
D:\>dir
Volume in drive D is CDROM
Volume Serial Number is 8690-D680
Directory of D:\
12/21/2015 12:28 2,048 BOOT.CAT
12/21/2015 12:28 126 BOOT.MSG
12/21/2015 12:28 1,463 HELP.MSG
12/21/2015 12:28 1,247 HELP2.MSG
12/21/2015 12:20 1,320,539 INITRD.GZ
01/25/2009 21:21 14,336 ISOLINUX.BIN
12/21/2015 12:28 151 ISOLINUX.CFG
12/21/2015 12:28 7,566 LOGO.16
12/21/2015 12:28 181,592,096 PUPPY_TA.SFS
12/21/2015 12:28 3,231 README.HTM
12/21/2015 12:20 3,556,336 VMLINUZ
12/21/2015 12:20 27,369,504 ZDRV_TAH.SFS
12 File(s) 213,868,643 bytes
0 Dir(s) 0 bytes free
D:\>dir
Volume in drive D is CDROM
Volume Serial Number is 8690-D680
Directory of D:\
12/21/2015 12:28 2,048 BOOT.CAT
12/21/2015 12:28 126 BOOT.MSG
12/21/2015 12:28 1,463 HELP.MSG
12/21/2015 12:28 1,247 HELP2.MSG
12/21/2015 12:20 1,320,539 INITRD.GZ
01/25/2009 21:21 14,336 ISOLINUX.BIN
12/21/2015 12:28 151 ISOLINUX.CFG
12/21/2015 12:28 7,566 LOGO.16
12/21/2015 12:28 181,592,096 PUPPY_TA.SFS
12/21/2015 12:28 3,231 README.HTM
12/21/2015 12:20 3,556,336 VMLINUZ
12/21/2015 12:20 27,369,504 ZDRV_TAH.SFS
12 File(s) 213,868,643 bytes
0 Dir(s) 0 bytes free
Looking into the iso-file wiith a binary viewer, it seems to have 2 names for every file - a short 8.3 DOS name (as Win7 dir command shows) and a full lower-case name. In particular, "PUPPY_TA.SFS" and "puppy_tahr_6.5.0.sfs" appear next to each other, and the same for all other files.
Thus, it looks like the bootloader or whatever is running the show can't see the long names on my HP desktop. However, since Lenovo ThinkPad has no problem with this CD, I gather the long names are there, but unusable on the HP.
The only thing that comes to mind is that the bootloader accesses the CD through some CD file system driver in the PC BIOS, and HP's BIOS can't use the long names, while ThinkPad's can. Is this possible?
Thus, it looks like the bootloader or whatever is running the show can't see the long names on my HP desktop. However, since Lenovo ThinkPad has no problem with this CD, I gather the long names are there, but unusable on the HP.
The only thing that comes to mind is that the bootloader accesses the CD through some CD file system driver in the PC BIOS, and HP's BIOS can't use the long names, while ThinkPad's can. Is this possible?
I have the HP Compaq dx2400 Microtower.stan166 wrote:tahr-6.0.5_noPAE.iso behaves exactly the same: "puppy_tahr_6.0.5.sfs not found". Here is how it looks from Win7:
D:\>dir
Volume in drive D is CDROM
Volume Serial Number is 8690-D680
Directory of D:\
12/21/2015 12:28 2,048 BOOT.CAT
12/21/2015 12:28 126 BOOT.MSG
12/21/2015 12:28 1,463 HELP.MSG
12/21/2015 12:28 1,247 HELP2.MSG
12/21/2015 12:20 1,320,539 INITRD.GZ
01/25/2009 21:21 14,336 ISOLINUX.BIN
12/21/2015 12:28 151 ISOLINUX.CFG
12/21/2015 12:28 7,566 LOGO.16
12/21/2015 12:28 181,592,096 PUPPY_TA.SFS
12/21/2015 12:28 3,231 README.HTM
12/21/2015 12:20 3,556,336 VMLINUZ
12/21/2015 12:20 27,369,504 ZDRV_TAH.SFS
12 File(s) 213,868,643 bytes
0 Dir(s) 0 bytes free
When the 2 terabyte hard drive is blank, the computer boots fine from the Puppy DVD.
When Puppy is installed on the hard drive, I get a "puppy_slacko64_6.3.2.sfs not found. Dropping out to initial-ramdisk console." when booting from the DVD.
The only time I do this is when tweaking the hard drive partitions, in which case I just boot from a Puppy 5.7 CD and run GParted from there.
My case is different - I have no HDD attached and don't plan to. I want to boot and run from CD, so everything is the same after every boot.
This HP dc5700 desktop runs Windows XP just fine. The BIOS is dated from 2011. I hope somebody can offer a clue as to what is going on.
I tried some more commands:
puppy pupsfs=sr0:/PUPPY_SL.SFS zdrv=sr0:/ZDRV_SLA.SFS
(sr0 is my CD drive, according to dmesg)
This seems to get it past finding the SFS file, but then kernel panics because init has exited.
---
Actually, I'm very happy with slacko_6.3.0,iso on ThinkPad - it can use WiFi and all www sites I care about seem to work, even youtube. Except this is not the PC I want to run it on
This HP dc5700 desktop runs Windows XP just fine. The BIOS is dated from 2011. I hope somebody can offer a clue as to what is going on.
I tried some more commands:
puppy pupsfs=sr0:/PUPPY_SL.SFS zdrv=sr0:/ZDRV_SLA.SFS
(sr0 is my CD drive, according to dmesg)
This seems to get it past finding the SFS file, but then kernel panics because init has exited.
---
Actually, I'm very happy with slacko_6.3.0,iso on ThinkPad - it can use WiFi and all www sites I care about seem to work, even youtube. Except this is not the PC I want to run it on
I have an Acer Aspire 5570Z laptop with the Pentium Dual Core T2080 processor which originally shipped with Vista. It's chipset is 32-bit only and I'm successfully booting Puppy 6.3.0 noPAE from USB.stan166 wrote:My case is different - I have no HDD attached and don't plan to. I want to boot and run from CD, so everything is the same after every boot.
This HP dc5700 desktop runs Windows XP just fine. The BIOS is dated from 2011. I hope somebody can offer a clue as to what is going on.
I tried some more commands:
puppy pupsfs=sr0:/PUPPY_SL.SFS zdrv=sr0:/ZDRV_SLA.SFS
(sr0 is my CD drive, according to dmesg)
This seems to get it past finding the SFS file, but then kernel panics because init has exited.
---
Actually, I'm very happy with slacko_6.3.0,iso on ThinkPad - it can use WiFi and all www sites I care about seem to work, even youtube. Except this is not the PC I want to run it on
You could always install Puppy 5.7 - it will just take a little longer to get everything up to date.
-
perdido
- Posts: 1528
- Joined: Mon 09 Dec 2013, 16:29
- Location: ¿Altair IV , Just north of Eeyore Junction.?
Could be puppy not seeing your optical drive.
Here is a way to check that - if you have a flash drive to copy files to.
Courtesy of rcrsn51
http://murga-linux.com/puppy/viewtopic. ... 41&start=9
.
Here is a way to check that - if you have a flash drive to copy files to.
Courtesy of rcrsn51
http://murga-linux.com/puppy/viewtopic. ... 41&start=9
.
Something to look at.
This computer has Computer Setup (F10) Utility that basically setup the bios settings.
Info here:
https://support.hp.com/ie-en/document/c00814591
A lot of things that could be affecting booting from a Live Puppy CD.
Maybe some setting in the security section.
Maybe some setting about what device can work or not work
Just look for anything that could affect using a CD or an OS.
This computer has Computer Setup (F10) Utility that basically setup the bios settings.
Info here:
https://support.hp.com/ie-en/document/c00814591
A lot of things that could be affecting booting from a Live Puppy CD.
Maybe some setting in the security section.
Maybe some setting about what device can work or not work
Just look for anything that could affect using a CD or an OS.
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)
A lot of those names are wrong and they should all be in lower case.tahr-6.0.5_noPAE.iso behaves exactly the same: "puppy_tahr_6.0.5.sfs not found". Here is how it looks from Win7:
D:\>dir
Volume in drive D is CDROM
Volume Serial Number is 8690-D680
Directory of D:\
12/21/2015 12:28 2,048 BOOT.CAT
12/21/2015 12:28 126 BOOT.MSG
12/21/2015 12:28 1,463 HELP.MSG
12/21/2015 12:28 1,247 HELP2.MSG
12/21/2015 12:20 1,320,539 INITRD.GZ
01/25/2009 21:21 14,336 ISOLINUX.BIN
12/21/2015 12:28 151 ISOLINUX.CFG
12/21/2015 12:28 7,566 LOGO.16
12/21/2015 12:28 181,592,096 PUPPY_TA.SFS
12/21/2015 12:28 3,231 README.HTM
12/21/2015 12:20 3,556,336 VMLINUZ
12/21/2015 12:20 27,369,504 ZDRV_TAH.SFS
However, it is probably just the way Windows 7 sees them.
It would be better if you read this in a running Puppy.
If the names look like this from the file manager in Puppy.
That is a big problem.
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)
I am wondering if the ISO was burned without long filename support? As far as I can see, there should be no reason why a windows7 command prompt will not see long filenames on an iso9660 image.
If using the commandline program mkisofs, it should be told to use longfilename support, see
http://www.murga-linux.com/puppy/viewto ... 781#190781
Here is a screen dump of my Puppy Tahr live DVD with long filenames
If using the commandline program mkisofs, it should be told to use longfilename support, see
http://www.murga-linux.com/puppy/viewto ... 781#190781
Here is a screen dump of my Puppy Tahr live DVD with long filenames
- Attachments
-
- SCREENDUMP.JPG
- (40.09 KiB) Downloaded 645 times
There is nothing wrong with the ISOs. There is a README file on all Puppy ISOs that discusses the issue.
The "sfs file not found" problem comes from two sources.
1. The optical drive itself which cannot locate the file. This can sometimes be fixed with certain kernel options.
2. A timing problem in the Puppy init scripts. There is some evidence that older Puppies are less susceptible.
The "sfs file not found" problem comes from two sources.
1. The optical drive itself which cannot locate the file. This can sometimes be fixed with certain kernel options.
2. A timing problem in the Puppy init scripts. There is some evidence that older Puppies are less susceptible.
-
Sailor Enceladus
- Posts: 1543
- Joined: Mon 22 Feb 2016, 19:43
I'm curious what program did you use to burn the CD? I used BURNCDCC here and it worked (both Slacko 5.7 and 6.3.2):
http://puppylinux.org/wikka/LiveDVD
http://puppylinux.org/wikka/LiveDVD
Did you ever try this?
bigpup wrote:Something to look at.
This computer has Computer Setup (F10) Utility that basically setup the bios settings.
Info here:
https://support.hp.com/ie-en/document/c00814591
A lot of things that could be affecting booting from a Live Puppy CD.
Maybe some setting in the security section.
Maybe some setting about what device can work or not work
Just look for anything that could affect using a CD or an OS.
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)
Hi,
I would like to revive this thread, since I have the same issue and the OP did not post any solution to it.
I am still a beginner to (Puppy) Linux OS however, in the recent past, I successfuly installed Puppy on two PC's (dual boot) running Windows XP. Lately, I wanted to run Puppy on my desktop and netbook PC's. So I popped the old Live CD into my Dell Optiplex 390, Intel Core i5-2400, 3.10 GHz, 4GB RAM running Win7 64bit and it booted to a point where a message appears: "puppy_slacko_5.7.sfs not found. Dropping out to initial-ramdisk console" That live CD was working fine on the older XP PC's.
Next, I downloaded the new Puppy version slacko-6.3.2-uefi.iso (32bit) und burned the iso to a new DVD using FreeIsoBurner software. No luck, same message. Then I created a bootable USB Flash drive with the same iso using "Unetbootin" software. This worked and I could boot both PC's. So why is the Flash drive booting and not the DVD?
I prefer to boot from the CD/DVD as the Flash drive gets often corrupted. Please help.
I would like to revive this thread, since I have the same issue and the OP did not post any solution to it.
I am still a beginner to (Puppy) Linux OS however, in the recent past, I successfuly installed Puppy on two PC's (dual boot) running Windows XP. Lately, I wanted to run Puppy on my desktop and netbook PC's. So I popped the old Live CD into my Dell Optiplex 390, Intel Core i5-2400, 3.10 GHz, 4GB RAM running Win7 64bit and it booted to a point where a message appears: "puppy_slacko_5.7.sfs not found. Dropping out to initial-ramdisk console" That live CD was working fine on the older XP PC's.
Next, I downloaded the new Puppy version slacko-6.3.2-uefi.iso (32bit) und burned the iso to a new DVD using FreeIsoBurner software. No luck, same message. Then I created a bootable USB Flash drive with the same iso using "Unetbootin" software. This worked and I could boot both PC's. So why is the Flash drive booting and not the DVD?
I prefer to boot from the CD/DVD as the Flash drive gets often corrupted. Please help.
Try this.
Copy the puppy_slacko_5.7.sfs and place it in the first partition of the hard drive.
Just in the partition do not place it in any folder
Probably some kind of timing problem with the DVD drive.
Could be how Puppy sees the drive, after the initial boot process starts identifying hardware type.
Just seems like the newer the Drives are the harder it is to get a Live Puppy CD/DVD to boot.
About USB drive corruption.
If you start with a freshly partitioned and formatted drive.
Never let Windows use it for storage.
The drive is probably formatted Fat32. Windows, over time, will fragment the file system, as part of deleting and adding to it.
It should stay uncorrupted with Puppy using it.
If you look in the boot menu entry for Puppy.
Add pfix=fsck to the end of the kernel line.
That will tell Puppy to do a file system check and repair when it boots.
Copy the puppy_slacko_5.7.sfs and place it in the first partition of the hard drive.
Just in the partition do not place it in any folder
Probably some kind of timing problem with the DVD drive.
Could be how Puppy sees the drive, after the initial boot process starts identifying hardware type.
Just seems like the newer the Drives are the harder it is to get a Live Puppy CD/DVD to boot.
About USB drive corruption.
If you start with a freshly partitioned and formatted drive.
Never let Windows use it for storage.
The drive is probably formatted Fat32. Windows, over time, will fragment the file system, as part of deleting and adding to it.
It should stay uncorrupted with Puppy using it.
If you look in the boot menu entry for Puppy.
Add pfix=fsck to the end of the kernel line.
That will tell Puppy to do a file system check and repair when it boots.
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)
I have only two partitions. The first one is 210GB win7 boot NTFS and the other is 10GB ext3. You mean the ext3 partition?
Also, I compared the files on the DVD and the flash drive. The following files are MISSING on the DVD:
menu.C32
syslinux.cfg
ubnfield.txt
ubnpathl.txt
vesamenu.c32
zdrv_slacko_6.3.2.sfs
Also, I compared the files on the DVD and the flash drive. The following files are MISSING on the DVD:
menu.C32
syslinux.cfg
ubnfield.txt
ubnpathl.txt
vesamenu.c32
zdrv_slacko_6.3.2.sfs