From: Dan Olson <dano@agora.rdrop.com>
To: Liste ELKS <linux-8086@vger.kernel.org>
Subject: Re: ELKS on Amstrad PPC 512
Date: Mon, 18 Nov 2002 21:33:51 -0800 (PST) [thread overview]
Message-ID: <20021118213045.A46708-100000@agora.rdrop.com> (raw)
In-Reply-To: <3DD3B2560015C471@mel-rta7.wanadoo.fr> (added by postmaster@wanadoo.fr)
It took me a minute, but I finally figured out what makes this system
"different" enough that it won't run ELKS, it only has 512k of RAM! This
may not mean that it's impossible to get ELKS running on this system, but
the pre-compiled versions of the OS expect 640k or RAM. I suppose someone
else can better answer this, but I believe there is a kernal option that
can be changed at compile time to use less memory. Being a laptop, I
suppose sticking a little more memory on the bus isn't that easy (on a
machine with ISA slots, a memory board could be added).
Dan
> Hello happy old computers users :-)
>
> I'm trying to install ELKS on an Amstrad laptop :
> http://www.bolo.ch/?list=2&obj=131 ... This strange PC has a NecV30,
> two 720 kb floppies and 512kb of ram (impossible to upgrade).
>
> Using the boot & root images from elks.images-0.1.0.zip, I obtain a
> message with the root disk :
>
> ---------
> Unable to open /dev/tty (error 2)
> dup failed
> No init - running /bin/sh
>
> panic: No init or sh found
> apparant call stack :
> ---------
>
> Before writing to the list, I've searched via Google groups. A message
> was about compiling with option "BIOS console" as Character device
> driver. But the compilation doesn't succeed :
>
> ---------
> (cd ../.. ; ld86 -0 -i \
> arch/i86/boot/crt0.o arch/i86/boot/crt1.o \
> init/main.o kernel/kernel.a fs/fs.a lib/lib.a net/net.a
> fs/minix/minixfs.a arch/i86/kernel/akernel.a arch/i86/lib/lib86.a
> arch/i86/mm/mm.a arch/i86/drivers/char/chr_drv.a
> arch/i86/drivers/block/blk_drv.a \
> -t -M -o arch/i86/boot/system > System.tmp ; \
> sort -k4 System.tmp > System.map ; rm -f System.tmp )
> undefined symbol: _debug1
> tools/build boot/bootsect boot/setup boot/system > boot/Image
> Root device is (3, -128)
> Boot sector 512 bytes.
> Setup is 1472 bytes.
> Unable to open 'system'
> make[1]: *** [Image] Error 1
> make[1]: Leaving directory `/usr/src/elks-0.1.1/arch/i86'
> make: *** [Image] Error 2
> ---------
>
> Any idea ?
>
> I've found messages showing that ELKS runs well on an Amstrad PPC 640
> (the model with 640 kb of ram). Has anyone succeeded with a PPC 512 ?
> --
> "S'il n'y a pas de solution,
> c'est qu'il n'y a pas de problème"
> Proverbe Shadok
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
-
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2002-11-19 5:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3DD3B2560015C471@mel-rta7.wanadoo.fr>
2002-11-19 5:33 ` Dan Olson [this message]
2002-11-19 13:13 ` ELKS on Amstrad PPC 512 Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021118213045.A46708-100000@agora.rdrop.com \
--to=dano@agora.rdrop.com \
--cc=linux-8086@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox