Can't boot Puppy2 from LILO on Vector-was ok with ver. 1.0x

Please post any bugs you have found
Post Reply
Message
Author
kcin
Posts: 102
Joined: Wed 28 Sep 2005, 14:47
Location: Oakland CA

Can't boot Puppy2 from LILO on Vector-was ok with ver. 1.0x

#1 Post by kcin »

Hi all,

Since 1.07 I've been dual-booting Puppy from LILO on my Vector box (HP Omniboook Xe2). This is the lilo.conf entry that always worked before with 1.0x puppy-versions:
# Partition 1: Puppy
image = /boot/pup/vmlinuz
root = /dev/ram0
label = Puppy-1.09
initrd = /boot/pup/image.gz
append = "PFILE=pup001-none-262144 PHOME=hda2 ramdisk_size=65536"
read-only

And here is how I changed it for Puppy 2
# Partition 1: Puppy
image = /boot/pup/vmlinuz
root = /dev/ram0
label = Puppy-2.0
initrd = /boot/pup/initrd.gz
append = "PMEDIA=idehd PKEYS =us"
read-only
Of course I copied the new Puppy2 versions of vmlinuz and initrd.gz to /boot/pup/ in Vector's hda2 root, and pup_save.3fs was created in Vector's root just fine.

But Puppy keeps saying it can't find Puppy on idehd.

It keeps giving me this message: (last 10 lines)
Registering unionfs 20060417-0541
Ext2-fs warning: mounting unchecked fs, running e2fsck is recommended
usb 1-1: new low-speed usb device using uhci_hcd and address 2
usb 1-1: configuration #1 chosen from 1 choice
Using personal data file pup_save.3fs which is on partition hda2
Loading swap partition /dev/hda1...
Adding 499864k swap on /dev/hda1. Priority: -1 extents:1 across: 499864k
ERROR, cannot find Puppy on idehd boot media
PUPMODE=9 PDEV1=
Kernel panic - not syncing: Attempted to kill init!
I can't see why it's hanging there since it says it is finding pup_save.3fs, and since in the "How Puppy Works.html" file on Barry's site, it says under item #8 that "...Puppy will ransack the entitre PC and find the Puppy files." ...even if the PMEDIA parameter is omitted. ( I even tried omitting it and it still fails)

Can anyone help me with this?

I've tried endless permutations of the "append" line, moving vmlinuz and initrd.gz to root, (and adjusting the correponding lilo.conf lines to match), and after hours and hours of failures, I am tapped out. This issue is beyond my current knowledge.

Any and all clues, tips, or suggestions will be GREATLY appreciated!

Best Regards,

kcin

kcin
Posts: 102
Joined: Wed 28 Sep 2005, 14:47
Location: Oakland CA

Doh! - Figured it out.

#2 Post by kcin »

Hi all,

Ooop, nevermind. I hadn't realized I needed to copy pup_200.sfs to the hd manually... all is ok now.

Best Regards,

kcin

Post Reply