Page 11 of 13

Posted: Sun 03 Jul 2011, 23:38
by rjbrewer
Ahh, I see. Trying the frugal on sda2 first.

It shoud be /dev/sda2 in the grub config window.

Use legacy grub; might make that windows partition nonsense
go away.

edit:

You would need sda2 flagged as boot in gparted.

Posted: Mon 04 Jul 2011, 00:08
by Sky Aisling
I don't mind going back and starting from scratch.
My concern is that I will ruin something by inappropriately leaving this screen (like cold cutting the machine). I don't know how to leave the screen.

Will I be able to boot the Live CD again? (In order to try again).

Posted: Mon 04 Jul 2011, 00:17
by rjbrewer
Sky Aisling wrote:I don't mind going back and starting from scratch.
My concern is that I will ruin something by inappropriately leaving this screen (like cold cutting the machine). I don't know how to leave the screen.

Will I be able to boot the Live CD again? (In order to try again).
Booting the live cd is starting fresh;
should be able to do it a few thousand times if you don't scratch
the cd.

Posted: Mon 04 Jul 2011, 00:24
by Sky Aisling
So, how do I click out of the blue grub window?

edit - I'm writing this post from a different machine than the one I'm trying to install Puppy to.

Posted: Mon 04 Jul 2011, 00:47
by rjbrewer
Push and hold the power button till the machine turns off.

Posted: Mon 04 Jul 2011, 01:17
by Sky Aisling
Yes, that's what I need to know. Thank you.

I'm assuming there will be some sort of partition structure and boot registry there to boot a Live CD again? I haven't lost it by cold cutting the machine.

I'm hoping that the GParted work that I did will still be in effect.
If true,
I'll then use *GParted* to add a boot flag to sda1.
I'll redo CatDude's Step 5 and edit the *menu.lst* again making sure I *rename* the old list (just in case) and *save* the new edited list.
If not,
then I'll just start from scratch again. Can't Dance, too wet to plow.

(I have a feeling that when I took the *blank* option on the box *Grubconfig: Hard Drive MBR* that the menu.lst reverted back to a default list.)

Thanks rjbrewer.

Posted: Mon 04 Jul 2011, 10:15
by CatDude
Hello Sky

I am a little confused by your screenshot screenshot_GRUB1.png
That dialogue box looks different to the one i get in Puppy-431 retro
(see sequence of screenshots below)
  • NOTE:
    In image grub-3.png
    i eventually entered /dev/hda8 (after i took the screenshot )
    as you can see in images grub-5.png and grub-7.png

    This is where i told you to put /dev/sda1 (in step 4)
    as i assumed you to be using the normal version of Puppy-431 with the newer kernel.

Also, why is sda1 mounted in your screenshot ?
I don't think it should be.

I also see that sdb1 mounted
i am assuming that is your flash drive, from which you copied the files in step 3.
CatDude wrote:3. Mount /dev/sda2
and create a directory called: lupu520
Copy these files from the lupu-520.iso
  • initrd.gz
    lupu_520.sfs
    vmlinuz
and put them into /dev/sda2/lupu520

Unmount /dev/sda2
After doing that, unmount & remove your flash drive as well.

Then run the GRUB Installer


CatDude
.

Posted: Mon 04 Jul 2011, 12:18
by Sky Aisling
Good Morning CatDude,

I know we are in different time zones, so, I'm dropping this quick reply to let you know I'm reading your question in detail and will reply further as I study your words today.

The *screenshot_GRUB1.png* is a box that appeared in sequence where you saw *grub-7.png*. Instead of the box you saw, *grub-7.png*, I saw *screenshot_GRUB1.png* then a closure of the procedure after I chose a blank response.

Yes, sdb1 is the flash drive which contains the lupu-520.iso and associated files, initrd.gz,
lupu_520.sfs, vmlinuz. The lupu-520.iso and associated files are resident on the flash drive.

Posted: Wed 06 Jul 2011, 17:26
by Sky Aisling
[Situation Solved]
Successful Install :)

My error was in not *saving* the changed *menu.lst* when using the *Geany* text editor provided during the *Grub bootloader configuration*.

Note to readers just stepping into this thread: please read the special circumstances of the disc used to create this install. See my post of Thu 30 Jun 2011, 02:56
http://www.murga-linux.com/puppy/viewto ... 18556fece4

After I recouped from the error 15 page:

I followed exactly CatDude's suggestion on page:
http://www.murga-linux.com/puppy/viewto ... start=195.
(I did not need to repeat Step 2 or Step 3 as they had stayed in place even after a 'cold cut' of the machine.)

FYI - Here is the machine and Puppy OS configuration:
Machine:
Fujitsu Lifebook Pseries 256 RAM, 20 GIGS HDD, transmeta(tm) Crueso(tm) Processor TM5800 (painfully slow)
Puppy OS:
lupu-520

Thank you CatDude, once again. You are the best.
Thank you rjbrewer for getting me out of the error 15 hang up.

Edit: Update - Comparison of FULL and FRUGAL Installs on the Fujitsu Lifebook Pseries 256 RAM, 20 GIGS HDD, transmeta(tm) Crueso(tm) Processor TM5800

The *frugal* install grinds along at a miserable pace.
The *full* install moves much quicker. The *full* install doesn't exactly blaze around the machine but it definitely runs quicker than the *frugal*.

*Opera-10.63-Lucid* browser works best with lupu-520 in this situation. Opera appears to be a quick, clean browser, nice!

I am so glad I was shown how to install both the *frugal* and the *full* on the same machine giving me the opportunity to compare the two installs.
This is most helpful for further installs.

Edit: *Full* Install is not without it's perils. See discussion concerning effects on *full* install when *uninstalling* applications:
http://www.murga-linux.com/puppy/viewtopic.php?t=57010
Note rjbrewer's posts.

Posted: Sat 04 Aug 2012, 14:09
by carldhickman
Great post...solved all my problems and sorted out all the different questions i had...just need to get the GRUB to auto-boot to puppy now

Posted: Sat 04 Aug 2012, 15:21
by CatDude
Hello carldhickman

Welcome to the kennels
carldhickman wrote:Great post...solved all my problems and sorted out all the different questions i had
Glad you found it useful mate.
carldhickman wrote:...just need to get the GRUB to auto-boot to puppy now
Could you post the contents of your menu.lst file,
we may then be able to help you with that too.

CatDude
.

Posted: Sun 05 Aug 2012, 08:57
by carldhickman
Hiya...thanks...Lucid Puppy 5.2.8 FULL install on Thinkpad T43 (now it's back from the dead thanks...) GRUB menu:

# GRUB configuration file '/boot/grub/menu.lst'.
# generated by 'grubconfig'. Sat Aug 4 14:37:53 2012
#
# The backup copy of the MBR for drive '/dev/sda' is
# here '/boot/grub/mbr.sda.24058'. You can restore it like this.
# dd if=/boot/grub/mbr.sda.24058 of=/dev/sda bs=512 count=1
#
# Start GRUB global section
#timeout 0
color light-gray/blue black/light-gray
# End GRUB global section
# Linux bootable partition config begins
title Linux (on /dev/sda1)
root (hd0,0)
kernel /boot/vmlinuz root=/dev/sda1 ro vga=normal
# 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,0)
setup (fd0)
pause Press enter to continue.
title Install GRUB to Linux partition (on /dev/sda1)
root (hd0,0)
setup (hd0,0)
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)

Sits there at boot up waiting for me to select...like it to boot automatically.

Puppy on this laptop, Ubuntu on other laptop...is this the end for Windows...50:50 split in OS...

Posted: Sun 05 Aug 2012, 09:11
by CatDude
Hello carldhickman

Change your "global section"
from this:

Code: Select all

# Start GRUB global section
#timeout 0
color light-gray/blue black/light-gray
# End GRUB global section 
to this:

Code: Select all

# Start GRUB global section
timeout 0
default 0
color light-gray/blue black/light-gray
# End GRUB global section 
That should do it. :)

CatDude
.

Posted: Sun 05 Aug 2012, 09:53
by carldhickman
Awesome CatDude...worked a treat...now my resurrected old laptop lives again. You guys ever sleep?

Posted: Sun 05 Aug 2012, 10:01
by CatDude
Hi
carldhickman wrote:Awesome CatDude...worked a treat..
8) That's what we like to hear.
carldhickman wrote:You guys ever sleep?
Not a lot :lol:

CatDude
.

Posted: Fri 18 Sep 2015, 02:21
by rcracerguy
I'm stuck. I've gone through the whole first page. Now when I boot and load the hard drive it loads and stops at a # and that's it. I mean I boot to the grub screen then hit enter on the linux drive and it load through some things and stop with a #

Posted: Fri 18 Sep 2015, 13:03
by rokytnji
rcracerguy wrote:I'm stuck. I've gone through the whole first page. Now when I boot and load the hard drive it loads and stops at a # and that's it. I mean I boot to the grub screen then hit enter on the linux drive and it load through some things and stop with a #
First wondering if iso was md5sum checked.

Next would be has the hard drive ever ran anything and is not broken.
Then try Slitaz or some other puppy to make sure hard drive is ok.

http://puppylinux.org/wikka/BootParametersPuppy

Posted: Fri 18 Sep 2015, 15:35
by starhawk
...having NOT read the entire thread...

What's the text right above the # ?

If it says something about "Exited from X" -- that means that Puppy can't understand, at least initially, what graphics hardware you've got. A remarkably common problem.

If what I describe is the case -- at the # type xorgwizard and press [Enter]. That will take you through the video setup wizard, at the end of which you should have a working desktop.

A protip -- on newer Pups (such as Tahr and Slacko) -- skip the "Test X" by pressing [Esc] when you see that screen, and at the new # prompt, type xwin [Enter] -- either it works or it doesn't, there's not much need for a test. Besides, in my experience that 'test' just makes everything go screwballs anyways.

Posted: Fri 18 Sep 2015, 19:43
by rcracerguy
the xorgwizard worked but do I have to go through it every time? typing xwin worked also. still same question. do I have to do this every time?

Posted: Fri 18 Sep 2015, 20:40
by starhawk
Do you have a savefile/savefolder, or is this an initial install?

If you have a savefile/folder and it's working -- no.

If you don't -- set one up, and then you won't have to do that again unless it breaks. My understanding is that savefiles break more than savefolders. (Don't quote me on that -- I haven't used the savefolder option much, yet. It's quite new.)