Back on Puppy, still problems
-
- Posts: 218
- Joined: Sat 05 Jan 2008, 17:41
Back on Puppy, still problems
Same error as before but now it's on booting CD of 2.14.
Puppy starts booting, I use the "puppy pfix=ram,acpi=off" settings, boot continues about 2 steps then gives the error repeatedly.
Puppy 2.14 controls the boot menu and it works but 2.14 on sda3 won't boot from it either but the copy on sdb3 will. The menu.lst entry is the same for both versions.
Several other puppies will boot from the menu too.
The node on sda3 is 128 so that's not it either.
Teen pup does the same thing.
I know this isn't the specific information you need but I'm looking for general answers.
Roger
Puppy starts booting, I use the "puppy pfix=ram,acpi=off" settings, boot continues about 2 steps then gives the error repeatedly.
Puppy 2.14 controls the boot menu and it works but 2.14 on sda3 won't boot from it either but the copy on sdb3 will. The menu.lst entry is the same for both versions.
Several other puppies will boot from the menu too.
The node on sda3 is 128 so that's not it either.
Teen pup does the same thing.
I know this isn't the specific information you need but I'm looking for general answers.
Roger
I'm not that familiar with the older versions, but it appears yours are frugal installations and they are not installed in their own subdirectories. Therefore, you are booting from the first pupsave seen. To make sure the proper pup is booting when you have multiple pups, they need to be in their own subdirectories. Your menu.lst entry should be similar to mine below, Note that the psubdir is located in three places.
If this doesn't help, you need to post additional information about your hardware, partitions, pups, menu.lst, etc. and then maybe some can help.
Code: Select all
# Linux bootable partition config begins
title Lighthouse (on /dev/sda2)
root (hd0,1)
kernel /Lighthouse/vmlinuz pmedia=idehd pfix=fsck pdev1=sda2 psubdir=Lighthouse
initrd /Lighthouse/initrd.gz
# Linux bootable partition config ends
-
- Posts: 218
- Joined: Sat 05 Jan 2008, 17:41
john1911;
No, I use full installs in separate partitions for each distro.
The puppy 2.14 in sda3 controls the boot menu and grub is installed in the MBR of sda.
My menu.lst looks much like yours.
I'm running a Compaq Presario sr1000v with 1Gb RAM and 2 HD. sda is an 80Gb, sdb is a 250Gb
But what does this have to do with booting a live CD, which also gives the error.
Roger
No, I use full installs in separate partitions for each distro.
The puppy 2.14 in sda3 controls the boot menu and grub is installed in the MBR of sda.
My menu.lst looks much like yours.
I'm running a Compaq Presario sr1000v with 1Gb RAM and 2 HD. sda is an 80Gb, sdb is a 250Gb
But what does this have to do with booting a live CD, which also gives the error.
Roger
- Bronco Billy
- Posts: 122
- Joined: Sun 27 Dec 2009, 05:51
A Shot in the Dark.......
Two Programs are Fighting for the Main Memory.... And Yor Disrupting the War with "puppy pfix=ram,acpi=off.... Take it out and Reboot for a Possible Fix..... Have a Great Day....Roger Hunter wrote:Same error as before but now it's on booting CD of 2.14.
Puppy starts booting, I use the "puppy pfix=ram,acpi=off" settings, boot continues about 2 steps then gives the error repeatedly.
Puppy 2.14 controls the boot menu and it works but 2.14 on sda3 won't boot from it either but the copy on sdb3 will. The menu.lst entry is the same for both versions.
Several other puppies will boot from the menu too.
The node on sda3 is 128 so that's not it either.
Teen pup does the same thing.
I know this isn't the specific information you need but I'm looking for general answers.
Roger
-
- Posts: 218
- Joined: Sat 05 Jan 2008, 17:41
- Bronco Billy
- Posts: 122
- Joined: Sun 27 Dec 2009, 05:51
Live CD.....
Are You Saying it Won't Boot from a LIVE CD? Or Something Else....Roger Hunter wrote:BB;
Nope.
I've tried all the various cheat code combinations (including none).
Same result
Roger
-
- Posts: 218
- Joined: Sat 05 Jan 2008, 17:41
Yes, that's right. It won't boot from that CD or the installed version in sda3 but it will boot from the installed version in sdb3.
But it would do both before I messed up sda with gparted.
Sda1 is WinXP, sda2 is unused at the moment.
I was going to reinstall puppy 2.14 in sda3 until it failed to boot. A new CD of puppy 2.15 won't boot either.
I'd suspect the drive but other things work in it.
Roger
But it would do both before I messed up sda with gparted.
Sda1 is WinXP, sda2 is unused at the moment.
I was going to reinstall puppy 2.14 in sda3 until it failed to boot. A new CD of puppy 2.15 won't boot either.
I'd suspect the drive but other things work in it.
Roger
- Bronco Billy
- Posts: 122
- Joined: Sun 27 Dec 2009, 05:51
BIOS............
Force Your BIOS to Boot from the LIVE CD and ONLY the LIVE CD.... If It Does Boot then it is Probably the way you set up Your Boot parameters....I Don't Want to Bring up the GOLDEN RULE But........ Have a Great Day...Roger Hunter wrote:Yes, that's right. It won't boot from that CD or the installed version in sda3 but it will boot from the installed version in sdb3.
But it would do both before I messed up sda with gparted.
Sda1 is WinXP, sda2 is unused at the moment.
I was going to reinstall puppy 2.14 in sda3 until it failed to boot. A new CD of puppy 2.15 won't boot either.
I'd suspect the drive but other things work in it.
Roger
-
- Posts: 218
- Joined: Sat 05 Jan 2008, 17:41
-
- Posts: 218
- Joined: Sat 05 Jan 2008, 17:41
-
- Posts: 218
- Joined: Sat 05 Jan 2008, 17:41
Could be all the ram isn't being seen, or it's going bad. What does the bios say for ram?
Sometimes pulling and reinserting the ram fixes a poor connection.
Also possible cmos battery is nearly depleted.
Does seem like a problem with those 2.1 cds though.
What is the exact message when the boot hangs up?
Sometimes pulling and reinserting the ram fixes a poor connection.
Also possible cmos battery is nearly depleted.
Does seem like a problem with those 2.1 cds though.
What is the exact message when the boot hangs up?
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
- Bronco Billy
- Posts: 122
- Joined: Sun 27 Dec 2009, 05:51
Bad CD's????????
Will those Live CD's Boot Puppy in a DIFFERENT Machine? If ~ ---> Bad Cds...Roger Hunter wrote:rjbrewer;
Ok, same story.
I'm on Turbo Pup v1.0 liveCD with both hard drives unplugged.
2.14 and 2.15 will not boot
But they would before....
Not much left but the BIOS but I haven't touched that before using it to bypass the hard drives.
WTF?
Roger.
Golden Rule Those who Have the Gold Rule......
-
- Posts: 218
- Joined: Sat 05 Jan 2008, 17:41
Hmmmm..
My last post vanished.
Since 2.14 wouldn't boot on either of my CD drives I thought "bad cable" and replaced it.
Wrong. Still no good.
Then I tried 2.14 in another machine. Worked perfectly so the disk is good.
Both CD drives are fairly new and other puppys boot in them so the drives should be ok.
The memory passes the boot memory test
When booting, it gets to the kernel line and then says "Unknown interrupt or file" followed by a very long address. This repeats a dozen times or so, then the system reboots.
Trying to boot the copy on hard disk gives a kernel panic freezup.
I'm stumped.
Roger
My last post vanished.
Since 2.14 wouldn't boot on either of my CD drives I thought "bad cable" and replaced it.
Wrong. Still no good.
Then I tried 2.14 in another machine. Worked perfectly so the disk is good.
Both CD drives are fairly new and other puppys boot in them so the drives should be ok.
The memory passes the boot memory test
When booting, it gets to the kernel line and then says "Unknown interrupt or file" followed by a very long address. This repeats a dozen times or so, then the system reboots.
Trying to boot the copy on hard disk gives a kernel panic freezup.
I'm stumped.
Roger
Unknown interrupt or fault; that's a new one for me.
Seems to be a kernel issue on some other linux.
https://launchpad.net/ubuntu/+bug/71594
Seems to be a kernel issue on some other linux.
https://launchpad.net/ubuntu/+bug/71594
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: 218
- Joined: Sat 05 Jan 2008, 17:41
-
- Posts: 218
- Joined: Sat 05 Jan 2008, 17:41