From: Edoardo Liverani <eddyx89@gmail.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: What still need works and what works
Date: Sat, 26 Apr 2014 22:30:31 +0200 [thread overview]
Message-ID: <CALNwxeyPG9Nd3S6Q=GpLqjsD_ntcg8RV0-Rg++iirvFjcnuigQ@mail.gmail.com> (raw)
Hi all,
I'm following Jody development and testing after him.
Here's a list of things that are still tricky to do before obtaining a
build of a working elks from github sources:
Kernel:
-[SOLVED] Elks kernel won't build correctly in x86_64 environment ->
now it works great
-It's impossible to set "Base memory size" (CONFIG_MEM_PAGES) because
pressing enter makes it looping on help page and you can't return to
previous menu. (btw... it's this setting used?)
Apart from this, make dep and make Image creates a good working image
with boot sector to boot from floppy.
There's just a strange thing: why if I set XT machine and 8086
processor, the boot log console talks about XMS memory?
elkscmd:
I got some bigger troubles for this:
-It needed "compress" executable that was not found by default on my
system, just had to put it.
-It want to have dev86's bootblocks folder in (GITHUB_ROOT)/linux-86/,
I put it and it worked, but I don't know if it's correct, as it's part
of another project. Furthermore we maybe should not rely on it and
fork to a dedicated boot loader "suite" for ELKS (I'm thinking of
MINIX monitor) integrated in the project
-In order to make dev86 bootblocks I had to manually add as86_encap
because my dev86 package (ebuild) is not putting it in default PATHS,
but I think this is just a problem on my system.
-Every time an error occours making elkscmd images, the loop file
remains mounted and I have to manually unmount it
-If I try make -j n, it mounts at the same time different images on
the same path, it should not.
-If it fails to create an image during the last steps, doing make
again says that it's up to date and do nothing, so I have to do a make
clean.
- [I'm working on this one] It's not possible to make a complete root
separated from a boot floppy image, I would like to make a root "tar"
in order to use it as I like (e.g. an already ready root image, an hd
image, etc)
Overcoming these issues it can build a good image (I tried "comb")
that boots and works (partially).
I tested the result on different (emulated, sigh.) environments, and
compared to minix 2:
-Hyper-V
- ELKS: boot correctly from floppy ("comb" image), but hangs after
some time (if you are fast enough, you can login, but it hangs after
some seconds)
- MINIX: (hd minix.mnx image) 203 -> black screen. 204 -> works
-Dosbox (with minix boot.com)
- MINIX: works fine
- ELKS: minix's boot.com just works with minix.
-Dosbox (with imgmount and boot -l)
-ELKS: prints "Booting ELKS.....:" then hangs.
-MINIX: don't even try to start.
-fake86 (a nice 8086 emulator for windows)
-ELKS: prints "Booting ELKS.....:" then hangs, making strange noises
-MINIX: boots, but hangs at "Multiuser startup in progress.
I think for now it's a good result, but it still needs some work.
What do you think? What are your experiences?
Regards,
Edoardo
next reply other threads:[~2014-04-26 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-26 20:30 Edoardo Liverani [this message]
2014-04-27 3:41 ` Terse build instructions (was Re: What still need works) Jody Bruchon
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='CALNwxeyPG9Nd3S6Q=GpLqjsD_ntcg8RV0-Rg++iirvFjcnuigQ@mail.gmail.com' \
--to=eddyx89@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).