(old)Puppy Linux Discussion Forum

nooby wrote:the older version of your program placed the menu.lst on Sda1 instead of Sda3 where mnt/home is and all the pup folders and other programs.
How can I move them from Sda1 to Sda3? Drag and drop or do I need to do something more involved? The sda_mbr.bak should that one still be in Sda1 then?
What about bootmgr and grldr where should they be?

The bootmgr is of Windows, you cannot move it.

The grldr and menu.lst can be on any partition.
But notice that they are searched from the first partition and then next.

There is a trap. If there is a ext4 partition in the grldr search process, it hungs up.
One of the reason the grub4dosconfig put grldr on the first partition is escaping this trap.

The MBR which grub4dosconfig made should be on the drive that is selected as the boot device by the BIOS.

Thanks indeed for your answer.


it worked as expected and I should have asked you this a long time ago.
This is so much more practical

peebee wrote:

amigo wrote: fdisk will do that -when you press 'n' to add a partition it gives you the option of specifying the number.

I used gparted to format the zip drive - was this incorrect?
Where do I find fdisk? - I can find pdisk in the menu but not fdisk....
Thanks
Peter

@PeeBee ... fdisk is a command that is BUILT-IN to all Linux systems (that I am aware of). To use it, open a terminal window and type fdisk ... and if I were you, when fdisk starts up, type m
"m" <=== will give you a list of options for using fdisk and "q" will quit.

There are all sorts of help on the Internet for fdisk.

I like fdisk because it will change tables on my drive(s) without changing data. So, if after making some changes, I want to change it back, I can and my may be able to get back to the original data (assuming I didn't do anything stupid). Luck to you

shinobar,
I have grub4dos installed to the MBR of the hard drive.
Grub4dos config found all installed operating systems and they have working entries in the menu.lst.
However, there are some extra entries that do nothing. Not sure why they are there.
Lucid Puppy 243 is a full install to a partition.
Luci 237 is a frugal install, with a save to full partition option, on a usb flash drive.

Here is what they are:

# Boot from Partition Boot Record

title Lucid Puppy 243 (sda3/boot:PBR)
uuid b3722aa6-7a19-4c72-a387-3a83fb1b030b
chainloader +1

title Luci 237 (sdb1:PBR)
uuid 75f04685-1ccc-44aa-8ad8-0e556405ebd7
chainloader +1

The entire menu.lst


# menu.lst produced by grub4dosconfig-v
color white/blue black/cyan white/black cyan/black
timeout 10
default 0

# Frugal installed Puppy

title Luci 242 (sda1/puppy242)
find --set-root --ignore-floppies /puppy242/initrd.gz
kernel /puppy242/vmlinuz pmedia=atahd psubdir=puppy242 pfix=fsck
initrd /puppy242/initrd.gz

title Luci 242 (sda1/puppy242) RAM mode\nBoot up Puppy withot pupsave
find --set-root --ignore-floppies /puppy242/initrd.gz
kernel /puppy242/vmlinuz pmedia=atahd psubdir=puppy242 pfix=ram,fsck
initrd /puppy242/initrd.gz

title Lupu 511 (sda2/puppy511)
find --set-root --ignore-floppies /puppy511/initrd.gz
kernel /puppy511/vmlinuz pmedia=atahd psubdir=puppy511 pfix=fsck
initrd /puppy511/initrd.gz

title Luci 236 (sda5/puppy236)
find --set-root --ignore-floppies /puppy236/initrd.gz
kernel /puppy236/vmlinuz pmedia=atahd psubdir=puppy236 pfix=fsck
initrd /puppy236/initrd.gz

title Luci 237 (sdb1)
find --set-root --ignore-floppies /luci_237.sfs
kernel /vmlinuz pmedia=usbflash pfix=fsck
initrd /initrd.gz

# Full installed Linux

title Lucid Puppy 243 (sda3/boot)
uuid b3722aa6-7a19-4c72-a387-3a83fb1b030b
kernel /boot/vmlinuz root=/dev/sda3 ro

title Linux Mint 8 Helena - Main Edition (sda7)
uuid 2a7dc791-ef27-4a70-ae9e-f59d14bdfa18
kernel /vmlinuz root=/dev/sda7 ro
initrd /initrd.img

# Windows
# this entry searches Windows on the HDD and boot it up
title Windows\nBoot up Windows if installed
errorcheck off
find --set-root --ignore-floppies --ignore-cd /bootmgr
chainloader /bootmgr
find --set-root --ignore-floppies --ignore-cd /ntldr
chainloader /ntldr
find --set-root --ignore-floppies --ignore-cd /io.sys
chainloader /io.sys
errorcheck on

# Boot from Partition Boot Record

title Lucid Puppy 243 (sda3/boot:PBR)
uuid b3722aa6-7a19-4c72-a387-3a83fb1b030b
chainloader +1

title Linux Mint 8 Helena - Main Edition (sda7:PBR)
uuid 2a7dc791-ef27-4a70-ae9e-f59d14bdfa18
chainloader +1

title Luci 237 (sdb1:PBR)
uuid 75f04685-1ccc-44aa-8ad8-0e556405ebd7
chainloader +1

# additionals

title Find Grub2\nBoot up grub2 if installed
find --set-root --ignore-floppies --ignore-cd /boot/grub/core.img
kernel /boot/grub/core.img

title Grub4Dos commandline\n(for experts only)
commandline

title Reboot computer
reboot

title Halt computer
halt

bigpup wrote:Grub4dos config found all installed operating systems and they have working entries in the menu.lst.
However, there are some extra entries that do nothing. Not sure why they are there.
Lucid Puppy 243 is a full install to a partition.
Luci 237 is a frugal install, with a save to full partition option, on a usb flash drive.

Here is what they are:

# Boot from Partition Boot Record

title Lucid Puppy 243 (sda3/boot:PBR)
uuid b3722aa6-7a19-4c72-a387-3a83fb1b030b
chainloader +1

title Luci 237 (sdb1:PBR)
uuid 75f04685-1ccc-44aa-8ad8-0e556405ebd7
chainloader +1

Good question.
Yes, the new version of grub4dosconfig makes these extra entries.
They do not always work and in many case they are redundant.
You can remove them from the menu.lst after you confirm that the corresponding OS can boot up with other entries.

See the document:
http://shino.pos.to/linux/puppy/grub4do ... html#chain

mo- and po- and .desktop-file ...attached.

Regards,
Markus

Continuation of our discussion in the Lucid thread.

Perfectly working box with 3 full installs..... Vector 6 (sda1),Puppy 4.20 (sda6) and Puppy 4.31 (sda7).Legacy Grub in the mbr.
Did a frugal install of Lupu-515 and installed Grub4dos in the mbr as bootloader.The only 2 installs that would boot were the 2 full Puppy installs....no go on Vector and the Lupu frugal.Both had a kernel panic.I've since edited the menu.lst and have Vector booting.


# menu.lst produced by grub4dosconfig-v
color white/blue black/cyan white/black cyan/black
timeout 10
default 0

# Frugal installed Puppy

title Lupu 515 (sda7/puppy515)
find --set-root --ignore-floppies /puppy515/initrd.gz
kernel /puppy515/vmlinuz pmedia=atahd psubdir=puppy515 pfix=fsck
initrd /puppy515/initrd.gz

title Lupu 515 (sda7/puppy515) RAM mode\nBoot up Puppy withot pupsave
find --set-root --ignore-floppies /puppy515/initrd.gz
kernel /puppy515/vmlinuz pmedia=atahd psubdir=puppy515 pfix=ram,fsck
initrd /puppy515/initrd.gz

# Full installed Linux

title Vector6.0 (sda1/boot)
uuid 5b0174b6-0b72-11e0-9cae-a5a52175c61b
kernel /boot/vmlinuz root=0301 ro

title Puppy 420 (sda6/boot)
uuid 4777244e-4b25-4819-84b1-5020579e4bd4
kernel /boot/vmlinuz root=/dev/sda6 ro

title Puppy 431 (sda7/boot)
uuid 35132a1e-f6b8-4e35-9f9e-f4a593818cf1
kernel /boot/vmlinuz root=/dev/sda7 ro

# Windows
# this entry searches Windows on the HDD and boot it up
title Windows\nBoot up Windows if installed
errorcheck off
find --set-root --ignore-floppies --ignore-cd /bootmgr
chainloader /bootmgr
find --set-root --ignore-floppies --ignore-cd /ntldr
chainloader /ntldr
find --set-root --ignore-floppies --ignore-cd /io.sys
chainloader /io.sys
errorcheck on

# additionals

title Find Grub2\nBoot up grub2 if installed
find --set-root --ignore-floppies --ignore-cd /boot/grub/core.img
kernel /boot/grub/core.img

title Grub4Dos commandline\n(for experts only)
commandline

title Reboot computer
reboot

title Halt computer
halt


I had to change the kernel line for the Vector install from "root=/dev/sda1" to "root=0301" boots fine again now.
Now to get the Lupu frugal booting.

This is my munu.lst entry for luci 246 made by Grub4dos config and it works. Looks like yours for Lupu 515.
Why yours does not work?????

title Luci 246 (sda2/puppy246)
find --set-root --ignore-floppies /puppy246/initrd.gz
kernel /puppy246/vmlinuz pmedia=atahd psubdir=puppy246 pfix=fsck
initrd /puppy246/initrd.gz

Yours;

title Lupu 515 (sda7/puppy515)
find --set-root --ignore-floppies /puppy515/initrd.gz
kernel /puppy515/vmlinuz pmedia=atahd psubdir=puppy515 pfix=fsck
initrd /puppy515/initrd.gz

Where did you install Grub4dos?
Are all the files in /puppy515?

bigpup wrote:This is my munu.lst entry for luci 246 made by Grub4dos config and it works. Looks like yours for Lupu 515.
Why yours does not work?????

title Luci 246 (sda2/puppy246)
find --set-root --ignore-floppies /puppy246/initrd.gz
kernel /puppy246/vmlinuz pmedia=atahd psubdir=puppy246 pfix=fsck
initrd /puppy246/initrd.gz

Yours;

title Lupu 515 (sda7/puppy515)
find --set-root --ignore-floppies /puppy515/initrd.gz
kernel /puppy515/vmlinuz pmedia=atahd psubdir=puppy515 pfix=fsck
initrd /puppy515/initrd.gz

Where did you install Grub4dos?
Are all the files in /puppy515?

Grub4dos in the MBR.

I saw that the entries were basically the same,so it should boot. I suspect an installer error....I primarily do manual installs so I'm manually copying the files right now.
Back in a few.

After manually copying the files, it's booting.So,installer error.

Three out of four booting without editing is not too bad I guess.

I had to change the kernel line for the Vector install from "root=/dev/sda1" to "root=0301" boots fine again now.

I had to do something similar for an install of Mint. Mint has its own way of doing stuff. It puts files in strange places. Simple adjustment of the menu.lst entry.

I had to change the kernel line for the Vector install from "root=/dev/sda1" to "root=0301" boots fine again now.

Is that something that could allow me to boot Lupu and Luci on Acer D250?

Only Fluppy and Insidious does boot all the otehrs fail. What is that root=0301 doing.

I have my puppy on sda3 instead on sda1 so would that make it root=0303 or what?

nooby wrote:

I had to change the kernel line for the Vector install from "root=/dev/sda1" to "root=0301" boots fine again now.

Is that something that could allow me to boot Lupu and Luci on Acer D250?

Only Fluppy and Insidious does boot all the otehrs fail. What is that root=0301 doing.

I have my puppy on sda3 instead on sda1 so would that make it root=0303 or what?

The biggest thing that causes menu.lst entries to not work is the entry is looking for files in the wrong place.
Example;
In menu.lst an entry says initrd /puppy515/initrd.gz. It thinks initrd.gz is in folder /puppy515.
If initrd.gz is in say folder /root or /puppy linux/puppy515 it will not find the file and it will not boot.
Grub4dos config seems to be really good at finding stuff and setting up the menu.lst. with no manual input required.

James C wrote:After manually copying the files, it's booting.So,installer error.

Thanks for coming James.
You can now boot all 4 install, right?
As for the frugal installed Lucu-515, will you let me know what installing tool you used and what files you needed to manually copy, please?

shinobar wrote:

James C wrote:After manually copying the files, it's booting.So,installer error.

Thanks for coming James.
You can now boot all 4 install, right?
As for the frugal installed Lucu-515, will you let me know what installing tool you used and what files you needed to manually copy, please?

Yes, all four installs are booting now.

I used the Universal Installer to do the actual install,but I generally just manually copy the files when I do a frugal.
The lupu_515.sfs was an incorrect size after using the installer, which explains why it wouldn't boot, so I copied the lupu_515.sfs, initrd.gz and vmlinuz from a usb stick where the iso was stored.

James C wrote:The lupu_515.sfs was an incorrect size after using the installer, which explains why it wouldn't boot, so I copied the lupu_515.sfs, initrd.gz and vmlinuz from a usb stick where the iso was stored.

Thanks, James.
As for the Vector "root=0301", i am sorry but the grub4dosconfig cannot support.
Please copy the entry from the old menu.lst manually as you did.

As for the Mint i am not sure but i remember i got success with the menu.lst entry produced by the grub4dosconfig-1.5.3 and later.

BigPup, my text was misleading you.

It boots but goes into kernel panic something.

it always when I activate debug stop at

b43-pci-bridge ... IRQ 16 then a blinking cursor

Karl Godt in a thread suggested this:

It might be a problem if a driver is two times available ( b43legacy. ), but I am not sure about that.

Which rhymes with that some say that one should "REMOVING SSB and blacklisting the stock b43 wireless driver."

Jemimah must have set things up differently in her Fluppy because that one never goes into panic.

Insidious Puppy seems to always work too. But it would be cool to have all puppies boot.

As for the Mint i am not sure but i remember i got success with the menu.lst entry produced by the grub4dosconfig-1.5.3 and later.

Sorry, did not mean to make you think there was a problem. I was just using as an example of something I had to do in the past. Latest Grub4dos no problem.

Comfirmation should be Confirmation

Chinese support:

sasaqqdan wrote:Chinese support:

Thanks sasa, but isn't it outdated?
Grub4DosConfig 1.6.x uses gettext instead of simple localization.
You can find '/usr/share/doc/nls/grub4dosconfig/grub4dosconfig.pot' in the package, grub4dos-0.4.4.v1.6.3.pet .