From: Harry Kalogirou <harkal@gmx.net>
To: pauln@truemesh.com
Cc: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: ELKS not runnable.... (once again)
Date: 15 May 2002 22:30:40 +0300 [thread overview]
Message-ID: <1021490158.469.16.camel@cool> (raw)
In-Reply-To: <20020515184633.GA15443@raq465.uk2net.com>
Την Τετ, 15-05-2002 στις 21:46, ο/η pauln@truemesh.com έγραψε:
> Just trying to compile without HD support, however get:
>
> undefined symbol: _bioshd_getfdinfo
> tools/build boot/bootsect boot/setup boot/system FLOPPY > boot/Image
> Root device is (0, 0)
> Boot sector 512 bytes.
> Setup is 1648 bytes.
> Unable to open 'system'
> make[1]: *** [Image] Error 1
> make[1]: Leaving directory `/home/pauln/src/elks/arch/i86'
> make: *** [Image] Error 2
>
> Which needs to be fixed, biosfd depends on bioshd by the looks.
>
> Can someone explain the difference between no h/w hd and bios hd
>
> Paul
>
the bioshd also handles the floppy drives. If you disable bioshd you
loose floppies along with the HDs. So when an error from bioshd shows
up, it not always the hard drive.
Harry
-
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 prev parent reply other threads:[~2002-05-15 19:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 17:31 ELKS not runnable.... (once again) Harry Kalogirou
2002-05-15 18:46 ` pauln
2002-05-15 19:30 ` Harry Kalogirou [this message]
2002-05-17 20:15 ` ELKS not runnable.... (other thing) Stefan de Konink
2002-05-17 19:40 ` Harry Kalogirou
2002-05-15 21:25 ` ELKS not runnable.... (once again) Riley Williams
2002-05-15 23:11 ` Riley Williams
2002-05-16 9:40 ` Riley Williams
2002-05-16 21:53 ` Harry Kalogirou
2002-05-16 22:42 ` Riley Williams
2002-05-16 22:47 ` Dan Olson
2002-05-17 14:10 ` Harry Kalogirou
2002-05-17 17:59 ` Riley Williams
2002-05-17 19:28 ` Harry Kalogirou
2002-05-16 9:52 ` Harry Kalogirou
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=1021490158.469.16.camel@cool \
--to=harkal@gmx.net \
--cc=linux-8086@vger.kernel.org \
--cc=pauln@truemesh.com \
/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