(old)Puppy Linux Discussion Forum

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 .

shinobar wrote:

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 .

thanks,shinobar.I don't understand the word"Comfirmation".

Hi shinobar

I am still working on a usb based system (in slackpup) and was thinking what was the easiest/simplest way to make a frugal install work when extracted from a package to a usb stick. I was wanting to use an ext file system so the boot to usb is out. Obviously with the way grub4dos is working I thought of you.

Do you think it would be possible to modify grub4dos to make it Independent so if it was placed with a frugal install on a usb stick, when run it would automatically detect the puppy, make the usb boot-able and produce the menu? or even just make the usb boot-able so the puppy would run?

Sorry for being a nuisance

Stripe

Stripe wrote:Do you think it would be possible to modify grub4dos to make it Independent so if it was placed with a frugal install on a usb stick, when run it would automatically detect the puppy, make the usb boot-able and produce the menu? or even just make the usb boot-able so the puppy would run?

Do you mean this?

Sorry shinobar if I was not clear

what I was thinking was a static version that could be packaged with the vmlniuz, intrid.gz and the pup-xxx-sfs in a tgz

so that when the package was unpacked on the usb stick, you would just click on the grub4dos and it would automaticaly install on that usb stick making the puppy able to run on that usb stick

Hope I explained it better this time

Thanks
Stripe

Stripe wrote:what I was thinking was a static version that could be packaged with the vmlniuz, intrid.gz and the pup-xxx-sfs in a tgz

so that when the package was unpacked on the usb stick, you would just click on the grub4dos and it would automaticaly install on that usb stick making the puppy able to run on that usb stick

Sounds interesting.
I don't know the detail but the puppeee by jemimah has some installer...

Well, you mean it works on Puppy?
Maybe i don't clealy understand your idea.

Thanks Shinobar

I will go and check that out, I just thought if we could give people a simple option of downloading a usb image as well as an iso. It would broaden the appeal of puppy

Thanks again

Stripe

@Shinobar
This appears to add a feature where a CD can be booted from GRUB.

I haven't tried this: but

• Would this work for GRUB4DOS?
• Would this provide an ability to select and boot a CD on bios-PCs that won't boot from CD?
• Do you have a similar procedure somewhere that's an example of booting a LiveCD thru Grub4DOS?

Thanks in advance
P.S. Here's another discussion you may find of interest.

P.S. I run a LiveCD environment on PCs that have 2 CD/DVD drives and diskette readers if theres concern on what types of PCs I use.

gcmartin wrote:This appears to add a feature where a CD can be booted from GRUB.

Thanks for the information, gcmartin.
Me too havn't tried, but form the liteature, the Grub4Dos can boot some kind of .iso files but does not work with Puppy i guess.
It is somewhat simmilar with PXE boot.
We can boot Puppy with this method if we make the initrd.gz contains the main sfs.

P.S.
There is the UNetBootin for the PC without CD.
Unfortunately, most recent Lupu-520 and Wary/Quirky fails unless manually editing the syslinux.cfg file.

One can boot but can one save things? Puppy though can not do iso boot.

Slitaz can be iso booted.

They had a thread on ubuntu forums a guys that listed how he made an USB mem stick do to iso boots of many OS. But very few seemed to be interested in it.

I was but I am a propeller head so I an too confused to grasp what is going on. But I did manage to boot a few too so even on my level if one follow instructions it can work. But that is for USB it does not work for frugal iso booting unless the OS is set up that way by the developer to allow it.

But from CD/DVD most likely it would work. The USB iso boot is trying to emulate a CD boot so CD should work even better.

The reason Puppy fail to do iso boot is explained by Shinobar above.

the sfs file is separate. On other OS they have it in two files or one file and that make them available for iso boot but then they can only save on nother partition or on a special "casper" file or a special save file for that OS.

But I know too little but wanted to do it too. I have the motivation bit not the means.

Now available the test release which supports Partition Boot Sector(PBS) install and Reiserfs(limited support).

grub4dos-0.4.4.v1.6.9.pet (Update: 16 Jan 2011) Download from here
See the document for the detail.

Testing and feed back are welcomed.

To boot a CD with Grub4dos add this entry to the menu.lst.

title Boot CD-ROM - (cd0)
cdrom --init
map --hook
chainloader (cd0)
rootnoverify (cd0)

Insert the CD after the boot menu comes up. Make sure to move off of the first menu choice so that does not get booted while you insert the CD.
Worked for me.

From info in the Grub4dos guide.
http://diddy.boot-land.net/grub4dos/files/boot.htm#cd