(OLD) (ARCHIVED) Puppy Linux Discussion Forum

[Sage]

[James C]

Hit the top 10 on Distrowatch.....

[Sage]

Oh dear! Gave it some swap space, but the initial booting didn't seem to look/find/use it. KP after switch-root, not sync-ing, etc. This can be a major issue on old kit that it is designed to use, and almost (but not quite!) the death knell for old laptops, for which additional memory may not be available and/or insertable. In all these instances, it will be necessary to install remotely on modern HW, hardly meeting the prime directive? Some folks have difficulty mounting 2.5" IDE drives into new machines on account of needing an adapter, either 40w to 44w IDE or IDE-to-SATA. No idea what options are for jiggling with the boot up coding? if any...

[James C]

I've already successfully booted Legacy OS4 Mini on several machines, so I grabbed an old Windows 98 box off the shelf. 384 Mb of ram.... no swap.

Default boot, just hitting "enter" .... kernel panic.
Booting pfix=no ram ....... kernel panic.
Booting pfix=nocopy ..... kernel panic.

Running the latest Slacko live so no hardware issues.

-Computer-
Processor : Celeron (Mendocino)
Memory : 384MB (137MB used)

-Version-
Kernel : Linux 3.1.10-slacko_4gA (i686)
Compiled : #1 SMP Tue Mar 13 14:58:11 EST 2012

-Processor-
Name : Celeron (Mendocino)
Family, model, stepping : 6, 6, 5 (Pentium II/Pentium II Xeon/Celeron)
Vendor : Intel
-Configuration-
Cache Size : 128kb
Frequency : 434.24MHz
BogoMIPS : 868.66
Byte Order : Little Endian

Might need to reconsider those minimum specs.

[Sage]

Thanks for that confirmation, James. Just wondering: Celeron & Duron are low on cache. Needs further investigating!

[russoodle]

[john biles]

Hello Everyone,
Sorry about the kernel panic problem for some of you with Ram less then 512Mb's. On some test PC's Legacy OS 4 Mini refuses to load from the CD and tries to load itself in to Ram which it can't causing the Kernel Panic error. One fix is to temporary increase the Ram to 512Mb's do the install to Hard Drive before removing the added Ram.

I'm as unhappy about this as you are. I need help / advice on finding a fix to this. I know it comes down to a bug in one of the scripts during boot up. If someone finds the bug please let me know so I can fix this problem.

[russoodle]

[nooby]

I guess my machine is too new? You care about the
older equipments so a Netbook from 2009 or 2010 or so
has LAN cards integrated into the motherboard that the
kernel has no driver for?

The LAN drivers for Acer D255 fail to get loaded in a way
that allow it to get internet

Is that situation something that comes with the goal and
nothing to do about? I like all the other things about it.

It looks incredibly nice and pleasant to use apart from no internet.

Thanks Russ,

It is not that important to me. I do have many other linux to play with.

[Sage]

[Sage]

More bad news, John!
For reasons you may be aware of, when I first tested your L4, I had all new kit (<= couple of months old) on the bench.
Now I have changed back to old (but certainly not ancient) kit, I find L4 won't boot. Saluki 15 and LupuPlus boot just fine (I have these at hand, and although considerably smaller than L4, they, too, are very new). Tried everything - either get an early KP as described above, or, if the memory is increased to 512, booting stalls later in the process. The only other distro to exhibit similar problems on older kit is BK's PrecisePuppy, which is highly experimental and an unfair comparison. Assume I've rung all the changes of HW, including mem., video cards, etc. I may not know a jot about code, but HW is definitely my bag.
'Fraid it looks essential to urgently fix this issue or modify claims?

Later: to be fair, I tried Anti-X M11-486. No issues. Of course, this is not a RAM only resident distro (is it?) but Puppy always used to run regardless. In the event of insufficent memory, it retained control of the CD and access thereto when required, ie exactly like other liveCD s of similar size to L4.

[russoodle]

Hello Nooby
Why not post a request for drivers on this thread: http://www.murga-linux.com/puppy/index.php?f=62, remembering that this release is based on Puppy 4.1...

On the subject of Psip....i downloaded, installed and successfully ran Psip 0.26 tonight, after i figured out KMix and correctly configured my sound. As previously mentioned, later versions of Psip are incompatible with 4 series Puppys but 0.26 works like a charm. I was running Legacy OS 4 Mini live on a T42P lappie with 1GB RAM.

I've attached screenies of the interface and my KMix configuration:

[James C]

I did notice that even though I attempted booting "pfix=noram" and "pfix=nocopy" Puppy overrode the boot parameters and still attempted to load into ram which led to the kernel panic.
I'm not that familiar with the startup scripts but I seem to recall that if Puppy detects a certain amount of ram while booting it will override and load into ram.With the larger size of Legacy OS4 I'd assume that parameter would need to be tweaked upwards.
That's my guess anyway......

[James C]

Believe this is based on Puppy 4.21 with the 2.6.25.16 kernel.The thread with extra drivers is at http://www.murga-linux.com/puppy/viewtopic.php?p=237739#237739 . Same kernel as 4.1 anyway.

[russoodle]

Thanks James - brain's asleep while eyes are still partially open.....5.40am here