Puppy Linux Discussion Forum

davec51 · Joined: 13 Apr 2006 Posts: 474 Location: Virginia

I tried to make a frugal install right from the iso, as I always do with new versions of Puppy. At first I couldn't boot because I had "root=/dev/sda1" instead of " . ./hda1." Then the boot went further. I put the main Puppy file directly in the root of the partition instead of in my "legacyos" folder, and it went a bit further. But I still can't get all the way to the desktop.

svgt · Joined: 26 Mar 2008 Posts: 107 Location: Hamburg, Germany

Hi,

I am twiddling half an hour with boot trials. The live cd is booting without problems.I did the full install, called here coexist.

I limited the installation to exactly one ext2 partition and a swap file. nothing else,

First I got from grub (in mbr) -file not found - because vmlinuz was not in /boot/vmlinuz. I changed it to /vmlinuz. The next message was a problem with initrd.

Kernel panic - no init found - proposal to hand over init= parameter

My grub parameters in menu.lst are:

root (hd0,0)
kernel /vmlinuz root=/dev/hda1 ro vga=normal

Regards
Svgt

DFI AZ30-TL - 1.7GHz single core Athlon - 768 MB RAM - 7 years old

john biles · Joined: 17 Sep 2006 Posts: 1331 Location: Australia

Hello Everyone,

Legacy OS is built on Puppy 2.14 and the only major change is the updating of glibc 2.3.5 to Puppy series 3's glibc 2.5 like ttuuxxx did with 2.14x

Nothing else system wise had been changed. So anything ttuuxxx incorporated in to 2.14x from later puppy series isn't included in Legacy OS sorry!

James C · Joined: 26 Mar 2009 Posts: 4768 Location: Kentucky

I've booted Legacy OS on 3 different machines, the two lower spec boxes I let boot normally.....no boot parameters added. The other box (2.6 dual-core w/2.5 gb ram booted pfix=ram.

James C · Joined: 26 Mar 2009 Posts: 4768 Location: Kentucky

For what its worth, Legacy OS has booted on 4 of 4 computers here.I grabbed another box off the shelf, booted pfix=ram and posting with it now.
AMD Duron 1.4 ghz w/384 mb ram and 1gb swap.

Using a lot of ram and swap but it's running pretty quick. Smile

sinc · Joined: 22 Jul 2009 Posts: 523 Location: Tampa, FL USA

only tried a manual frugal install but was not able to boot. i tried in a subdirectory and at / and was unsuccessful ion both situations. same as 8 bit described for the frugal install.

James C · Joined: 26 Mar 2009 Posts: 4768 Location: Kentucky

Me again................... Laughing

Went ahead and did a full install on the Duron box from the last post.Because I edit menu.lst instead of reinstalling grub I moved vmlinux into a new "boot" directory and messed with the syntax of menu.lst and it's booting and running fine. Smile

Resource usage dropped dramatically after Legacy OS was actually installed too.

svgt · Joined: 26 Mar 2008 Posts: 107 Location: Hamburg, Germany

Me again ....

James C: Please write your menu.lst

I moved vmlinuz to the /boot folder. Then I added to my menu.lst

initrd /initrd.gz

With or without this statement I got kernel panic. There is this screenshot with initrd:

MinHundHettePerro · Joined: 05 Feb 2009 Posts: 833 Location: SE

Hello

!

Booting from CD: OK Smile

Booting from manual frugal inst. on hdc13: not OK Sad

Created device nodes hdc9 - hdc15 in initrd.gz_/dev - now boots from frugal inst. on hdc13 Smile

.

Yes, I know, I have quite a few partitions Smile

.

Just in case someone else tried a manual frugal inst. on an "unsupported" partition:
Available device nodes in initrd suggest that frugal installations should be limited to hda1-15, hdb1-8, hdc1-8.

fwiw and hth Smile

/
MHHP

Roger Hunter · Joined: 05 Jan 2008 Posts: 194

Still no joy.

This thing just refuses to boot.

I got past the first failure and ended up on another one but no keyboard response there either.

Then I downloaded the iso again and burned it to a DVD thinking it was a bit too large.

Same result.

Very strange, especially since 2.14 is my old standby and has never failed to load on any of my systems.

Roger

Roger Hunter · Joined: 05 Jan 2008 Posts: 194

Tried again, same result.

Tried booting on a Dell D600 laptop. Same result.

The error message now is "access beyond end of device"

then

"squashfs error sb_bread failed 0xa9080"
"unable to read uid/gid table"

and eventually kernel panic.

Roger

technowomble · Posted: Sat 04 Sep 2010, 12:37 Post_subject:

DL'd and burned Legacy OS on my main Linux box, tried to test it but got the ' cannot find Puppy... ' message. Tried the same CD in my ca. 2000 laptop ( for which it was intended ) running as live CD ( Puppy pfix=ram ) and it booted OK. I've had problems testing Puppy on the ' big box ' before, Quirky NOP booted, but video set up gave ' out of range ', while it worked - at the second attempt - on the laptop. Yet it seems quite happy with 5 series puppies Go figure!

James C · Joined: 26 Mar 2009 Posts: 4768 Location: Kentucky

nooby · Joined: 29 Jun 2008 Posts: 9477 Location: SwedenEurope

I got this advice from MinHund...

svgt · Joined: 26 Mar 2008 Posts: 107 Location: Hamburg, Germany

Hello James,

In your root directory I count 17 files and folders. But I have got only six things:

boot lost&found idehd initrd.gz pup_214.sfs zdrv_214.sfs. Why is there this difference?

Why did you make a /boot directory? In my full installation /boot was there from the beginning, with /grub folder inside. My menu.lst is for Legacy the same, except this atahd parameter.

Regards
Svgt