| Author |
Message |
Roger Hunter
Joined: 05 Jan 2008 Posts: 194
|
Posted: Sun 24 Jan 2010, 14:56 Post subject:
Back on Puppy, still problems Subject description: Unknown interrupt error |
|
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
|
|
Back to top
|
|
 |
Jim1911
Joined: 19 May 2008 Posts: 2353 Location: Texas, USA
|
Posted: Sun 24 Jan 2010, 15:15 Post subject:
|
|
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.
| Code: | # 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 |
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.
|
|
Back to top
|
|
 |
Roger Hunter
Joined: 05 Jan 2008 Posts: 194
|
Posted: Sun 24 Jan 2010, 16:21 Post subject:
|
|
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
|
|
Back to top
|
|
 |
Bronco Billy

Joined: 27 Dec 2009 Posts: 122
|
Posted: Sun 24 Jan 2010, 17:59 Post subject:
A Shot in the Dark....... Subject description: One Big Puppy WAG..... |
|
| 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 |
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....
|
|
Back to top
|
|
 |
Roger Hunter
Joined: 05 Jan 2008 Posts: 194
|
Posted: Sun 24 Jan 2010, 18:28 Post subject:
|
|
BB;
Nope.
I've tried all the various cheat code combinations (including none).
Same result
Roger
|
|
Back to top
|
|
 |
Bronco Billy

Joined: 27 Dec 2009 Posts: 122
|
Posted: Sun 24 Jan 2010, 18:42 Post subject:
Live CD..... |
|
| Roger Hunter wrote: | BB;
Nope.
I've tried all the various cheat code combinations (including none).
Same result
Roger |
Are You Saying it Won't Boot from a LIVE CD? Or Something Else....
|
|
Back to top
|
|
 |
Roger Hunter
Joined: 05 Jan 2008 Posts: 194
|
Posted: Sun 24 Jan 2010, 19:02 Post subject:
|
|
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
|
|
Back to top
|
|
 |
Bronco Billy

Joined: 27 Dec 2009 Posts: 122
|
Posted: Sun 24 Jan 2010, 19:20 Post subject:
BIOS............ |
|
| 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 |
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...
|
|
Back to top
|
|
 |
Roger Hunter
Joined: 05 Jan 2008 Posts: 194
|
Posted: Sun 24 Jan 2010, 19:45 Post subject:
|
|
BroncoBilly;
Nope, makes no difference.
LiveCD will not boot in either drive. Neither will brand new liveCD for 2.15.
But others made earlier will boot. Stardust 006 for example.
TinyCore made today boots too.
Very strange.
CD drivers check out ok too.
Roger
|
|
Back to top
|
|
 |
rjbrewer

Joined: 22 Jan 2008 Posts: 4360 Location: merriam, kansas
|
Posted: Sun 24 Jan 2010, 20:02 Post subject:
|
|
Live cds do not boot "into" the drives.
Disconnect power leads to both drives and see which cds will boot.
_________________
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Full installs
|
|
Back to top
|
|
 |
Roger Hunter
Joined: 05 Jan 2008 Posts: 194
|
Posted: Sun 24 Jan 2010, 20:10 Post subject:
|
|
rjbrewer;
I'd be really amazed if an unpowered drive did anything, let alone boot from a CD in it.
Or do you mean to unplug the hard drives?
Roger
|
|
Back to top
|
|
 |
rjbrewer

Joined: 22 Jan 2008 Posts: 4360 Location: merriam, kansas
|
Posted: Sun 24 Jan 2010, 20:44 Post subject:
|
|
Yes; disconnect the drives.
_________________
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Full installs
|
|
Back to top
|
|
 |
Roger Hunter
Joined: 05 Jan 2008 Posts: 194
|
Posted: Sun 24 Jan 2010, 21:11 Post subject:
|
|
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.
|
|
Back to top
|
|
 |
rjbrewer

Joined: 22 Jan 2008 Posts: 4360 Location: merriam, kansas
|
Posted: Sun 24 Jan 2010, 21:33 Post subject:
|
|
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?
_________________
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Full installs
|
|
Back to top
|
|
 |
Bronco Billy

Joined: 27 Dec 2009 Posts: 122
|
Posted: Sun 24 Jan 2010, 22:18 Post subject:
Bad CD's???????? |
|
| 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. |
Will those Live CD's Boot Puppy in a DIFFERENT Machine? If ~ ---> Bad Cds...
Golden Rule Those who Have the Gold Rule......
|
|
Back to top
|
|
 |
|