After more than a month of trying to fix my 528 because of a careless deletion process it occurred to me that in my grub menu I had a more or less well-behaved 511, which I'm actually running; so, if linux is usually used to fix windows machines why not using it for fixing a linux one...
So, here I am, ready to add or substitute the grub menu entry for Puppy Linux 528 for the new one, ready except for the name I should use to make the entry. In any case, I'll put it in first place (default). I've a certain doubt in relation to this because after I moved + resized my partitions 2 of my puppies (Wary & 525) stopped booting up, which I hope & expect won't happen with an additional os added to my menu. Still, I don't want to substitute my 528 yet, just in case...
Should I simply comment the 528 entries & use the same names es appear there or (especially in the case of the 528.005 name) or there's no conflict with saved files because they are located in a different folder?
Thanks for any help on this!
What to put in menu.lst title line in grub --PL528.005?
Re: What to put in menu.lst title line in grub --PL528.005?
If you boot your system with legacy GRUB and you move your partitions around, you will need to reinstall GRUB. That's why Grub4Dos is a better choice for your bootloader.benny7440 wrote:I've a certain doubt in relation to this because after I moved + resized my partitions 2 of my puppies (Wary & 525) stopped booting up,
It might be easiest if you do the following.
1. Post your current menu.lst file here.
2. State the current location of the 528 files.
???? Please explain. Either it boots or it doesn't.Have a semi-broken PL528 running, need to fix it...
Thanks for responding, rcrsn51!
I don't understand what you mean with "reinstall grub"; do you mean running 'Grub bootloader config'?
With respect to my menu.lst file, it's shown below:
# GRUB configuration file '/boot/grub/menu.lst'.
# generated by 'grubconfig'. Sun Jul 3 04:15:57 2011
#
# Start GRUB global section
timeout 20
color light-gray/blue black/light-gray
# End GRUB global section
# Other bootable partition config begins
# title Windows (on /dev/sda1)
# rootnoverify (hd0,0)
# makeactive
# chainloader +1
# Other bootable partition config ends
# LINUX BOOTABLE PARTITION CONFIG BEGINS
TITLE PUPPY LINUX 528 FRUGAL IN SDA2 DIR PUPPY528
ROOTNOVERIFY (HD0,1)
KERNEL /PUPPY528/VMLINUZ PMEDIA=ATAHD PSUBDIR=PUPPY528
INITRD /PUPPY528/INITRD.GZ
# LINUX BOOTABLE PARTITION CONFIG ENDS
# Linux bootable partition config begins
title Puppy Linux 528 frugal in sda2 dir puppy528
rootnoverify (hd0,1)
kernel /puppy528/vmlinuz pmedia=atahd psubdir=puppy528
initrd /puppy528/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy Linux 525 frugal in sda2 dir puppy525
rootnoverify (hd0,1)
kernel /puppy525/vmlinuz pmedia=atahd psubdir=puppy525
initrd /puppy525/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy Linux 511 frugal in sda2 dir puppy511
rootnoverify (hd0,1)
kernel /puppy511/vmlinuz pmedia=atahd psubdir=puppy511
initrd /puppy511/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy Wary 512 frugal in sda2 dir wary-512
rootnoverify (hd0,1)
kernel /wary-512/vmlinuz pmedia=atahd psubdir=wary-512 acpi=off
initrd /wary-512/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy Studio frugal in sda2 dir puppystudio
rootnoverify (hd0,1)
kernel /puppystudio/vmlinuz pmedia=atahd psubdir=puppystudio
initrd /puppystudio/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title DSL frugal in sda1 dir dsl
rootnoverify (hd0,0)
kernel /linux24 ramdisk_size=100000 init=etc/init/ lang=us apm=power-off vga=773 initrd=/minirt24.gz nomce noapic quiet BOOT_IMAGE=knoppix
initrd /minirt24.gz
# Linux bootable partition config ends
# title Install GRUB to floppy disk (on /dev/fd0)
# pause Insert a formatted floppy disk and press enter.
# root (hd0,1)
# setup (fd0)
# pause Press enter to continue.
title Install GRUB to Linux partition (on /dev/sda2)
root (hd0,1)
setup (hd0,1)
# pause Press enter to continue.
title - For help press 'c', then type: 'help'
root (hd0)
title - For usage examples, type: 'cat /boot/grub/usage.txt'
root (hd0)
The entry in ALL CAPS is my intended location for the new 528.005 iso files within the menu.lst file.
As to my 528 files location they're in hdo,1 (a 120 GB HD with 3 partitions) > /mnt/home/puppy528 as seen from 511.
My 528 boot up with an error message (sorry, don't remember what it was), black screen background, no desktop icons, many Menu entries don't respond (specially, Rox File Manager), etc..
At the beginning I was inclined (obfuscated) to repair my 528 os by putting back in the libs/files I deleted, I thought it wasn't prove to be so hard to have someone make a search, post the results &, hopefully, make those needed available/downloadable. After all, I don't beleive we're talking here of more than a 3-4 MB .gz bundle.
I don't understand what you mean with "reinstall grub"; do you mean running 'Grub bootloader config'?
With respect to my menu.lst file, it's shown below:
# GRUB configuration file '/boot/grub/menu.lst'.
# generated by 'grubconfig'. Sun Jul 3 04:15:57 2011
#
# Start GRUB global section
timeout 20
color light-gray/blue black/light-gray
# End GRUB global section
# Other bootable partition config begins
# title Windows (on /dev/sda1)
# rootnoverify (hd0,0)
# makeactive
# chainloader +1
# Other bootable partition config ends
# LINUX BOOTABLE PARTITION CONFIG BEGINS
TITLE PUPPY LINUX 528 FRUGAL IN SDA2 DIR PUPPY528
ROOTNOVERIFY (HD0,1)
KERNEL /PUPPY528/VMLINUZ PMEDIA=ATAHD PSUBDIR=PUPPY528
INITRD /PUPPY528/INITRD.GZ
# LINUX BOOTABLE PARTITION CONFIG ENDS
# Linux bootable partition config begins
title Puppy Linux 528 frugal in sda2 dir puppy528
rootnoverify (hd0,1)
kernel /puppy528/vmlinuz pmedia=atahd psubdir=puppy528
initrd /puppy528/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy Linux 525 frugal in sda2 dir puppy525
rootnoverify (hd0,1)
kernel /puppy525/vmlinuz pmedia=atahd psubdir=puppy525
initrd /puppy525/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy Linux 511 frugal in sda2 dir puppy511
rootnoverify (hd0,1)
kernel /puppy511/vmlinuz pmedia=atahd psubdir=puppy511
initrd /puppy511/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy Wary 512 frugal in sda2 dir wary-512
rootnoverify (hd0,1)
kernel /wary-512/vmlinuz pmedia=atahd psubdir=wary-512 acpi=off
initrd /wary-512/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy Studio frugal in sda2 dir puppystudio
rootnoverify (hd0,1)
kernel /puppystudio/vmlinuz pmedia=atahd psubdir=puppystudio
initrd /puppystudio/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title DSL frugal in sda1 dir dsl
rootnoverify (hd0,0)
kernel /linux24 ramdisk_size=100000 init=etc/init/ lang=us apm=power-off vga=773 initrd=/minirt24.gz nomce noapic quiet BOOT_IMAGE=knoppix
initrd /minirt24.gz
# Linux bootable partition config ends
# title Install GRUB to floppy disk (on /dev/fd0)
# pause Insert a formatted floppy disk and press enter.
# root (hd0,1)
# setup (fd0)
# pause Press enter to continue.
title Install GRUB to Linux partition (on /dev/sda2)
root (hd0,1)
setup (hd0,1)
# pause Press enter to continue.
title - For help press 'c', then type: 'help'
root (hd0)
title - For usage examples, type: 'cat /boot/grub/usage.txt'
root (hd0)
The entry in ALL CAPS is my intended location for the new 528.005 iso files within the menu.lst file.
As to my 528 files location they're in hdo,1 (a 120 GB HD with 3 partitions) > /mnt/home/puppy528 as seen from 511.
My 528 boot up with an error message (sorry, don't remember what it was), black screen background, no desktop icons, many Menu entries don't respond (specially, Rox File Manager), etc..
At the beginning I was inclined (obfuscated) to repair my 528 os by putting back in the libs/files I deleted, I thought it wasn't prove to be so hard to have someone make a search, post the results &, hopefully, make those needed available/downloadable. After all, I don't beleive we're talking here of more than a 3-4 MB .gz bundle.
Since your 528 is booting, this is not a GRUB issue. There is no need to change your menu.lst.
It sounds like your save file has gotten badly corrupted. The easiest solution is to delete it and start another one. There are two approaches:
1. Boot off a Puppy Live CD using the "pfix=ram" option. Mount the 528 partition and delete its save file.
2. Boot another Puppy from your hard drive, mount the 528 partition and delete its save file.
It sounds like your save file has gotten badly corrupted. The easiest solution is to delete it and start another one. There are two approaches:
1. Boot off a Puppy Live CD using the "pfix=ram" option. Mount the 528 partition and delete its save file.
2. Boot another Puppy from your hard drive, mount the 528 partition and delete its save file.
Yes. Or run Grub4Dos bootloader config. It is very good at detecting your various Puppy install.I don't understand what you mean with "reinstall grub"; do you mean running 'Grub bootloader config'?
Thanks rcrsn51 for responding!
I guess there's no way to see all the screens right from the beginning if I'm using an external monitor for the notebook, am I right on this? I mention it because the screen of the notebook is showing just vertical stripes, black & white. For BIOS setup AWA other system wide configurations (before an os is running) I NEED the onboard screen. This's the reason I haven't done anything with a cdrom in this machine after the screen completely failed. All configurations were made before, & in preparation to this approaching event.
I remember having managed to do certain things blindly just because I knew by practice what was been asked & where were the included options for selection as in the screen resolution & the times required to show the entries...This's no longer the case, I've tried to boot 431 from a cd in order to do what you're saying but no luck there for me.
The less convoluted option I see is your last one: now that I'm running 511 is a good moment to delete that file but, when I boot, if I can, 528 again, at the end it will ask for a name & other things IN A DIFFERENT DESKTOP setting, which I won't be able to see &, unless I know in advance what's in there I'm not going to be able to set anything. I know it's not a long list of things so, if you post screenshots of them or a list of ?'s & suitable answers I would try it.
Thanks for your effort!
I guess there's no way to see all the screens right from the beginning if I'm using an external monitor for the notebook, am I right on this? I mention it because the screen of the notebook is showing just vertical stripes, black & white. For BIOS setup AWA other system wide configurations (before an os is running) I NEED the onboard screen. This's the reason I haven't done anything with a cdrom in this machine after the screen completely failed. All configurations were made before, & in preparation to this approaching event.
I remember having managed to do certain things blindly just because I knew by practice what was been asked & where were the included options for selection as in the screen resolution & the times required to show the entries...This's no longer the case, I've tried to boot 431 from a cd in order to do what you're saying but no luck there for me.
The less convoluted option I see is your last one: now that I'm running 511 is a good moment to delete that file but, when I boot, if I can, 528 again, at the end it will ask for a name & other things IN A DIFFERENT DESKTOP setting, which I won't be able to see &, unless I know in advance what's in there I'm not going to be able to set anything. I know it's not a long list of things so, if you post screenshots of them or a list of ?'s & suitable answers I would try it.
Thanks for your effort!
TITLE PUPPY LINUX 528 FRUGAL IN SDA2 DIR PUPPY528
ROOTNOVERIFY (HD0,1)
KERNEL /PUPPY528/VMLINUZ PMEDIA=ATAHD PSUBDIR=PUPPY528
INITRD /PUPPY528/INITRD.GZ
title Puppy Linux 528 frugal in sda2 dir puppy528
rootnoverify (hd0,1)
kernel /puppy528/vmlinuz pmedia=atahd psubdir=puppy528
initrd /puppy528/initrd.gz
...
The entry in ALL CAPS is my intended location for the new 528.005 iso files within the menu.lst file.
You have to do like this
title Puppy Linux 528-005 frugal in sda2 dir puppy528-005
rootnoverify (hd0,1)
kernel /puppy528-005/vmlinuz pmedia=atahd psubdir=puppy528-005
initrd /puppy528-005/initrd.gz
title Puppy Linux 528 frugal in sda2 dir puppy528
rootnoverify (hd0,1)
kernel /puppy528/vmlinuz pmedia=atahd psubdir=puppy528
initrd /puppy528/initrd.gz
So you have two directories for 528 one for the old one and another one
for 528-005 so the boot loader can differentiate between them.
Later when you create the savefile indicate it is for the -005 or
maybe reuse the old one but then rename it so you have a spare to
use as backup.
rcrsn51 is the one with know how I only jump in to point out something
I catch but could have misunderstood. Maybe you want to upgrade and
not keep the old entry?
Last edited by nooby on Wed 09 May 2012, 05:53, edited 1 time in total.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Thanks for replying, nooby!
I had such an idea as you posted but was unsure of it. Does the - instead of the . in the folders' name crucial?
To rcrsn51: I tried today to find the pupsave file from within 511 but didn't see it, I'll try later because I've to reboot: I'm now with 528. I'll post below the results of that...
EDIT: The Openbox Syntax Error cited in my 2nd post above follows:
"One or more XML syntax errors were found while parsing the Openbox configuration files. See stdout for more information. The last error seen was in the /root/.config/openbox/menu.xml" line 592, with message: Premature end of data in tag openbox_menu line 2."
Sorry, the utilities for capturing screenshots aren't working.
I had such an idea as you posted but was unsure of it. Does the - instead of the . in the folders' name crucial?
To rcrsn51: I tried today to find the pupsave file from within 511 but didn't see it, I'll try later because I've to reboot: I'm now with 528. I'll post below the results of that...
EDIT: The Openbox Syntax Error cited in my 2nd post above follows:
"One or more XML syntax errors were found while parsing the Openbox configuration files. See stdout for more information. The last error seen was in the /root/.config/openbox/menu.xml" line 592, with message: Premature end of data in tag openbox_menu line 2."
Sorry, the utilities for capturing screenshots aren't working.