LinuxQuestions.org - Multibooting Puppy linux

- Puppy (https://www.linuxquestions.org/questions/puppy-71/)

- - Multibooting Puppy linux - can anyone see my mistake? (https://www.linuxquestions.org/questions/puppy-71/multibooting-puppy-linux-can-anyone-see-my-mistake-4175427546/)

Multibooting Puppy linux - can anyone see my mistake?

Hi Everyone,

I have multibooted my machine for sometime now to play around with other distributions. I have been using OpenSuse for some years now. However,I can't afford to replace my machine very often, so only a couple of months ago moved from 512mb memory to 1gb memory. OpenSuse KDE, Firefox and Thunderbird really take it out of the machine. So I am looking at changing distributions. I like the look of Puppy linux, but I cannot get it to boot. I think I have everything correct, but I am not used to Puppy Linux. I am not sure that I have answered the questions correctly.

You do the full install to the partition, then it tells you to go to Grub and then you are asked various questions, which I don't think I have answered correctly. I have searched for a tutorial, for installing Puppylinux, but I have not found one suitable.

Some further information:

Code:

fdisk -l



Disk /dev/sda: 80.0 GB, 80026361856 bytes

255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x2ece0b7c



  Device Boot      Start        End      Blocks  Id  System

/dev/sda1              63    20000924    10000431    7  HPFS/NTFS/exFAT

/dev/sda2  *    20000986  156296384    68147699+  5  Extended

/dev/sda5        20000988    20209769      104391  83  Linux

/dev/sda6        20209833    22394609    1092388+  82  Linux swap / Solaris

/dev/sda7        22394673    65513069    21559198+  83  Linux

/dev/sda8        65513133  131058269    32772568+  83  Linux

/dev/sda9      131058333  156296384    12619026  83  Linux



Disk /dev/sdb: 82.0 GB, 81964302336 bytes

255 heads, 63 sectors/track, 9964 cylinders, total 160086528 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0xf24ef24e



  Device Boot      Start        End      Blocks  Id  System

/dev/sdb1  *          63    8000369    4000153+  7  HPFS/NTFS/exFAT

/dev/sdb2        8000370  160071659    76035645    5  Extended

/dev/sdb5        8000433    29896964    10948266  83  Linux

/dev/sdb6        29897028    50990309    10546641  83  Linux

/dev/sdb7        50990373    63424619    6217123+  83  Linux

/dev/sdb8        63424683  160071659    48323488+  83  Linux

Code:

cat /boot/grub/menu.lst

# Modified by YaST2. Last modification on Sun Aug 26 16:20:48 BST 2012

# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader

# For the new kernel it try to figure out old parameters. In case we are not able to recognize it (e.g. change of flavor or strange install order ) it it use as fallback installation parameters from /etc/sysconfig/bootloader



default 0

timeout 9

##YaST - generic_mbr

gfxmenu (hd0,4)/message

##YaST - activate



###Don't change this comment - YaST2 identifier: Original name: linux###

title openSUSE 12.1 - 3.1.10-1.16

    root (hd0,4)

    kernel /vmlinuz-3.1.10-1.16-default root=/dev/disk/by-id/ata-SAMSUNG_SP0842N_S0WCJDPP800779-part7 resume=/dev/disk/by-id/ata-SAMSUNG_SP0842N_S0WCJDPP800779-part6 splash=silent quiet showopts vga=0x317

    initrd /initrd-3.1.10-1.16-default



###Don't change this comment - YaST2 identifier: Original name: failsafe###

title Failsafe -- openSUSE 12.1 - 3.1.10-1.16

    root (hd0,4)

    kernel /vmlinuz-3.1.10-1.16-default root=/dev/disk/by-id/ata-SAMSUNG_SP0842N_S0WCJDPP800779-part7 showopts apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x317

    initrd /initrd-3.1.10-1.16-default



###Don't change this comment - YaST2 identifier: Original name:  linux (/dev/sda9)###

title Mandriva (/dev/sda9)

    rootnoverify (hd0,8)

    chainloader +1



###Don't change this comment - YaST2 identifier: Original name: Linux other 1 (/dev/sdb5)###

title Linux Mint (/dev/sdb5)

    rootnoverify (hd1,4)

    chainloader +1



###Don't change this comment - YaST2 identifier: Original name: other###

title Puppy Linux (dev/sdb6)

    rootnoverify (hd1,5)

    chainloader +1



###Don't change this comment - YaST2 identifier: Original name: other###

title Slitaz 4.0 (/dev/sdb7)

    rootnoverify (hd1,6)

    chainloader +1



###Don't change this comment - YaST2 identifier: Original name: windows 1###

title Windows XP

    rootnoverify (hd0,0)

    chainloader +1



###Don't change this comment - YaST2 identifier: Original name: windows 2###

title windows 2

    map (hd1) (hd0)

    map (hd0) (hd1)

    rootnoverify (hd1,0)

    makeactive

    chainloader +1



###Don't change this comment - YaST2 identifier: Original name: floppy###

title Floppy

    rootnoverify (fd0)

    chainloader +1

/sda1 is windows xp
/sda5 is boot
/sda6 is swap
/sda7 is root
/sda8 is home
/sda9 is Mandriva

/sdb1 not sure why this is there
/sdb5 is Linux Mint
/sdb6 will be Puppylinux
/sdb7 will be Slitaz
/sdb8 partition for data storage

I can boot into Mandriva and Linux Mint and get online with both of them, I haven't got much further.

The puppy linux live CD says there is an installation at sdb6, but I get this message when I try to boot:

Code:

rootnoverify (hd1,5)

chainloader +1

Error 13: Invalid or unsupported executable format

If you are using (and planning to use) the Opensuse Grub bootloader, you should have selected to install Grub to the partition on which you installed Puppy (sda6?). If you can boot Opensuse, do so and mount sda6 and check to see if you actually have the kernel and boot directory and files. You might also google "bootinfoscript" and go to its site, read the instructions and download and run it. There will be a results.txt file output which you can review for assistance or post here for help.

Quote:

Originally Posted by yancek (Post 4781921)

Hi,
I checked I did install Grub to sdb6
I am not sure if I have the files but see screenshot here:
http://www.imagebam.com/image/9f22eb211622175

I found 'bootinfoscript', but I wasn't able to get it to work. I ran it, but I could not see a results.txt file.

So I went back and did the (recommended) frugal install. I also inserted the suggested script into the menu.lst. See here:

Code:

cat /boot/grub/menu.lst

# Modified by YaST2. Last modification on Sun Aug 26 16:20:48 BST 2012

# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader

# For the new kernel it try to figure out old parameters. In case we are not able to recognize it (e.g. change of flavor or strange install order ) it it use as fallback installation parameters from /etc/sysconfig/bootloader



default 0

timeout 9

##YaST - generic_mbr

gfxmenu (hd0,4)/message

##YaST - activate



###Don't change this comment - YaST2 identifier: Original name: linux###

title openSUSE 12.1 - 3.1.10-1.16

    root (hd0,4)

    kernel /vmlinuz-3.1.10-1.16-default root=/dev/disk/by-id/ata-SAMSUNG_SP0842N_S0WCJDPP800779-part7 resume=/dev/disk/by-id/ata-SAMSUNG_SP0842N_S0WCJDPP800779-part6 splash=silent quiet showopts vga=0x317

    initrd /initrd-3.1.10-1.16-default



###Don't change this comment - YaST2 identifier: Original name: failsafe###

title Failsafe -- openSUSE 12.1 - 3.1.10-1.16

    root (hd0,4)

    kernel /vmlinuz-3.1.10-1.16-default root=/dev/disk/by-id/ata-SAMSUNG_SP0842N_S0WCJDPP800779-part7 showopts apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x317

    initrd /initrd-3.1.10-1.16-default



###Don't change this comment - YaST2 identifier: Original name:  linux (/dev/sda9)###

title Mandriva (/dev/sda9)

    rootnoverify (hd0,8)

    chainloader +1



###Don't change this comment - YaST2 identifier: Original name: Linux other 1 (/dev/sdb5)###

title Linux Mint (/dev/sdb5)

    rootnoverify (hd1,4)

    chainloader +1



###Don't change this comment - YaST2 identifier: Original name: other###

title Puppy Linux 5.3.3 frugal (dev/sdb6)

rootnoverify (hd1,5)

kernel /vmlinuz pmedia=atahd

initrd /initrd.gz



###Don't change this comment - YaST2 identifier: Original name: other###

title Slitaz 4.0 (/dev/sdb7)

    rootnoverify (hd1,6)

    chainloader +1



###Don't change this comment - YaST2 identifier: Original name: windows 1###

title Windows XP

    rootnoverify (hd0,0)

    chainloader +1



###Don't change this comment - YaST2 identifier: Original name: windows 2###

title windows 2

    map (hd1) (hd0)

    map (hd0) (hd1)

    rootnoverify (hd1,0)

    makeactive

    chainloader +1



###Don't change this comment - YaST2 identifier: Original name: floppy###

title Floppy

    rootnoverify (fd0)

    chainloader +1

Now I get this:

Code:

Loading drivers needed to access disk drives - done

searching Puppy files................. puppy_slacko_5.3.3sfs not found

Dropping to initial -ramdisk console

I am not sure what is happening now? It looks to me as if it is there?

Any help gratefully received.

Regards

No idea but the filesystem type might give problems .

On the other hand the ram disk shell is kind of fun to try different commands . :p
I would

Code:

for file in `ls -1 /tmp/*` ; do

echo $file

cat $file

done

run this to gain a little more info . The dmesg command output should be informative too .
:D;)

The error you report in your initial post indicates an unsupported filesystem type. What filesystem do you have on sdb6, the Puppy partition. Run the following in a terminal:

Code:

df -T /dev/sdb6

Quote:

Originally Posted by yancek (Post 4786327)

The error you report in your initial post indicates an unsupported filesystem type. What filesystem do you have on sdb6, the Puppy partition. Run the following in a terminal:

Code:

df -T /dev/sdb6

Code:

df -T /dev/sdb6

Filesystem    Type 1K-blocks  Used Available Use% Mounted on

/dev/sdb6      ext3  10381004 638752  9214920  7% /puppy

PCPARTSALL0=`probepart_init -k` is the VARIABLE that should contain all devices .

The normal running PUPPY has got a ` probepart ' script that does output like

Quote:

pmedia=atahd does this :

Quote:

*hd|*flash|*zip) #internal boot media. ex: idehd, satahd, ideflash, idezip, scsihd
USE_PARTS0="$FASTPARTS0"

and
FASTPARTS gets created like this :

Quote:

for ONEFAST in $ATADRIVES `cat /proc/partitions | grep "hd[a-z]$" | tr -s " " | cut -f 5 -d " " | tr "\n" " "`
do
APATTERN="^${ONEFAST}"
FASTPARTS="${FASTPARTS}`echo "$PCPARTS0_NOCDS" | grep "$APATTERN" | tr '\n' ' '`"
USB_PARTS0=`echo "$USB_PARTS0" | grep -v "$APATTERN"`
done
FASTPARTS0=`echo "$FASTPARTS" | tr -s ' ' | tr ' ' '\n'`

I would try to use a grub kernel line like this :

Code:

kernel /puppy/vmlinuz pdev1=sdb6 psubdir=puppy

initrd /puppy/initrd.gz

to direct it there .
If that does not help, it may be that the initrd.gz is missing some harddrive (scsi) drivers but since the CD did boot this is unlikely since it uses the same initrd.gz ( except you have mixed the wrong initrd.gz that does not contain the appropriate kernel-version-modules ) :
Download Slacko 5.3.3 from nluug.nl: Get slacko-5.3.3-4g-SCSI.iso http://puppylinux.org/main/Download%...%20Release.htm

Puppy is finally installed on my computer. I still don't know why it didn't work. I started all over again and now it boots.

In OpenSuse, I reformatted sbd6. I then installed Puppy from the CD, when it asked about booting I chose sdb6. When the installation was finished, I tried booting to sdb6, I got this error:

Code:

rootnoverify (hd1,5)

chainloader +1

Error 13: Invalid or unsupported executable format

I then changed the menu.lst in OpenSuse to:

Code:

rootnoverify (hd1,5)

kernel /vmlinuz pmedia=atahd

initrd /initrd.gz

And it now boots to Puppy.

Thank you for your assistance.

Your original mistakes, generally, may have inlcuded:
1. not discerning GRUBv0.97/Legacy vs. GRUBv1.99(aka 2) vs. GRUB4dOS
2. assuming Puppy Linux boot parameters are well-documented and easily found (!)
3. not putting boot code in the Partition Boot Record area, and chainloading to it
...
Consider running Live from a flash stick, or a "frugal" install.
"pmedia=<interface><device>" is a filter - searching may go wider without it;
"<something>.sfs not found" when you SEE it there means it's not looking there,
try "psubok=TRUE" and "psubdir=rootdir/pupdir" and remember initrd isn't very bright about parameters - changing their order or removing blanks may help.