Not the only, or last, flaw in my thinking.mikeb wrote:I almost believed you until I got to the last 2 lines
it should be 8, 12 or 16
mike
pup-431.sfs not found
Weird: got this after my last post, then rewrote it only to find I'd double posted so I've deleted the double post here and re edited to mention this:
Running Firefox on Dpup at the moment......
What does making a forum post have to do with my (or its) mail server?Couldn't get mail server response codes
DEBUG MODE
Line : 116
File : smtp.php
Running Firefox on Dpup at the moment......
-
- Posts: 8
- Joined: Sat 14 Nov 2009, 19:08
problem persists on tosh portege 3110CT
This machine uses an external PC-card CD drive. I can initiate the boot from the CD, but then get the pup-431.sfs not found error.
I've tried 3.4 as well as the 2.16 retro version and tried various ram only , noapci options and still no luck. The CD's load ok on a newer laptop.
I have successfully loaded, live and then installed fluxbuntu, xubuntu (both 7.10) on this machine, so I think the kernel runs on the PC OK.
My best guess is that the remote CD does not have enough time to spin up and respond before the loader returns an error. I can still hear the CD spinning up after the load has failed.
Any ideas, anyone?
I've tried 3.4 as well as the 2.16 retro version and tried various ram only , noapci options and still no luck. The CD's load ok on a newer laptop.
I have successfully loaded, live and then installed fluxbuntu, xubuntu (both 7.10) on this machine, so I think the kernel runs on the PC OK.
My best guess is that the remote CD does not have enough time to spin up and respond before the loader returns an error. I can still hear the CD spinning up after the load has failed.
Any ideas, anyone?
Re: problem persists on tosh portege 3110CT
Yes, a hunch, but you didn't specify which kernel version, and what laptop you were using.linuxgeoff wrote:This machine uses an external PC-card CD drive. I can initiate the boot from the CD, but then get the pup-431.sfs not found error.
I've tried 3.4 as well as the 2.16 retro version and tried various ram only , noapci options and still no luck. The CD's load ok on a newer laptop.
Any ideas, anyone?
I'm using an old Dell CPx laptop with Puppy 4.3.1 frugal with the newer kernel (2.6.30.5) and it works fine. Furthermore, I'm using the old hda type nomenclature (actually, I forgot to even try sda and so on) and it works fine for me. Here is the extract from my menu.lst (I used to use grub4dos, but use normal grub now, so the entries may be slightly strange - I haven't checked and can't remember grub nomenclature now):vtpup wrote: The probable reason, in my opinion, that the earlier kernel works is that somewhere along the line in booting, drive designations become sda types (even for non serial drives) rather than hda types. The boot process seems to get confused by this switch on older machines. Therefore it can't find the puppy main file, even though it is present.
In a frugal install this can be seen if you inadvertently use the "hda" nomenclature in a newer kernel puppy's menu.lst. You will get the same "can't find" message on attempting to boot. However if you change this to sda, it will boot,
Code: Select all
title Puppy431 frugal on hda4
kernel (hd0,3)/puppy431/vmlinuz root=/dev/ram0 PMEDIA=idehd psubdir=puppy431
initrd (hd0,3)/puppy431/initrd.gz
boot
github mcewanw
Well, apparently what works for a Dell CPx doesn't work for a Thinkpad 600e. And the folks posting here. The problems in this thread are situations where 4.3.1 K2.6.30.5 doesn't boot -- not where it does, and the puppy sfs file is suddenly not found, despite its actual presence. This occurs in LiveCD as well as frugal install.mcewanw wrote: I'm using an old Dell CPx laptop with Puppy 4.3.1 frugal with the newer kernel (2.6.30.5) and it works fine. Furthermore, I'm using the old hda type nomenclature (actually, I forgot to even try sda and so on) and it works fine for me.
Yet in kernel 2.6.21.7 it is found properly -- at least on the 600e, Puppies using K 2.6.21.7 have the hd drive reference on the desktop, later kernel versions of puppy use the sd reference. My guess is there is a problem related to this change. Not a certainty. But it certainly would explain the loss of sight of the puppy sfs halfway through the boot.
-
- Posts: 8
- Joined: Sat 14 Nov 2009, 19:08
tosh portege 3110ct
Sorry, it was all buried in the post. The laptop was in the subject line: Tosh Portege 3110CT and the kernel is k2.6.21.7Yes, a hunch, but you didn't specify which kernel version, and what laptop you were using.
For completeness, the cd drive is the tosh unit that shipped with the laptop: f-to-tcd-24l
I have an update: I tried copying the sfs files to the root of the hard drive and both 4.2.1retro and 4.3 got past the error. 4.2.1retro booted and I'm using it now. 4.3 fell over trying to ues the layered file system. This seems to support a timeout on the cdrom causing the xxx.sts not found error
mcewanw,
The hda you refer to is on the title line of grub and doesn't have
an effect on booting.
I have tried many versions of puppy using titles similar to this
and they all boot fine:
title Boot you lazy fleabitten hound on hdplanet pluto
root (hd0,0)
kernel /boot/vmlinuz root=/dev/sda1 ro vga=normal pfix=fsck
The hda you refer to is on the title line of grub and doesn't have
an effect on booting.
I have tried many versions of puppy using titles similar to this
and they all boot fine:
title Boot you lazy fleabitten hound on hdplanet pluto
root (hd0,0)
kernel /boot/vmlinuz root=/dev/sda1 ro vga=normal pfix=fsck
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
-
- Posts: 8
- Joined: Sat 14 Nov 2009, 19:08
I'm starting to believe the time-out theory. Or at least that the problem is centered around the CD rom. Actually, I had similar problems in a much later computer: a Thinkpad T30 which booted fine on 4.1.2 later kernel, but which had problems accessing a DVD writer either through the puppy burning programs or K3b. I went through a whole painful thread trying to get that to work, before almost accidentally dropping back to 2.6.21.7 and suddenly having everything work. This is a pent 4 computer w 1 gig ram, yet I had to use the retro kernel.
One of the evident problems was K3b and Puppy drive mounter fighting for control of the DVD writer. That may well have been a timing problem. So I'm definitely listening to this theory of yours.
One of the evident problems was K3b and Puppy drive mounter fighting for control of the DVD writer. That may well have been a timing problem. So I'm definitely listening to this theory of yours.
no rj, I just didn't know if you could do a full install from a frugal. I've never done a Puppy full install. By booting, I took it to mean booting from manually installed HD frugal, not CD, which I assume still can't be booted from. I thought there might be problems in partitioning etc from the working drive.
Yes; full installs can be done from a frugal: but he needs the abilityvtpup wrote:Can he do a full install if he can't run from CD? I guess it depends on the drives and partitioning he already has... or maybe boot something else to do the preliminary partitioning. Maybe SystemRescueCD....if that one will boot?
to create partitions (as you said). I assumed he got a cd to boot, but his explanation of "installing the sfs files to the root of the hard drive"
leaves me perplexed.
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
Probably just did a manual frugal install. Copy the puppyxxx,sfs, vmlinuz and initrd.gz from CD to a top level directory ("root" he said -- probably did the copy from another linux), then make a grub menu.lst entry to point to it.rjbrewer wrote: Yes; full installs can be done from a frugal: but he needs the ability
to create partitions (as you said). I assumed he got a cd to boot, but his explanation of "installing the sfs files to the root of the hard drive"
leaves me perplexed.
That's what he was able to boot 4.2 from, as a guess, rather than the CD. Or, that's what I thought he was saying anyway.
That's also why I was inquiring about how the CD was working after he was running 4.2 -- are there still issues with it --possible timing problems-- particularly burning if it's a burner.