public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christophe Gimenez" <chris@kandji.com>
To: Linux 8086 <linux-8086@vger.kernel.org>
Subject: Re: Elks freeze after login
Date: Fri, 2 Aug 2002 08:07:07 +0200	[thread overview]
Message-ID: <001901c239ea$d4b30df0$0101a8c0@workstation> (raw)
In-Reply-To: Pine.LNX.4.21.0208012345260.30515-100000@Consulate.UFP.CX


----- Original Message -----
From: "Riley Williams" <rhw@InfraDead.Org>
To: "Christophe Gimenez" <chris@kandji.com>
Cc: "Linux 8086" <linux-8086@vger.kernel.org>
Sent: Friday, August 02, 2002 12:48 AM
Subject: Re: Elks freeze after login


> Hi Christopher.
>
> This sounds suspiciously like a problem that was recently fixed in the
> ELKS CVS tree, so I would ask which version of ELKS you are running when
> this happens to rule that out.
>
> Assuming it's not that, I'd ask you to list the actual hardware
> configuration of the CompaQ as that is one brand that is known to use
> non-standard hardware, and it's quite possible that we're seeing some
> incompatibility between the CompaQ version of the serial ports and the
> standard versions.
>

Hello Riley,

I'm using the disk images downloaded from sf and seems to be the 0.1.0
version.
This compaq has :
- a 20286
- a 20287 (but I'm not sure, I've not used this computer since 1991), I will
test for it
- 1,6 MB of ram
- a 40 MB IDE disk
- two serial ports

The two serial ports are detected at boot time as
ttys0 at 0x3F8 (irq = 4) with 16450
ttys1 at 0x2F8 (irq = 3) with 16450

and lp0 at 0x3BC

I've been able to fdisk and mkfs (but not mount due to my lack of knowledge
of mount parameters, the simple mount /dev/bda1 /mnt provided in the faq
doesn't work).
Just for information : I must say I've not been able to run minix 2.0.3 on
it. I had problems with mkswap or something like that and switched to elks
that seems more fun to explore.

I'm really interested on having tcpip services working because I would like
to use a null modem wire (with pppd when it will be available if not
allready done) to transfer compiled files from my linux gateway to the 286
instead of having to write floppy, unmount, mount, launch and so on...




  reply	other threads:[~2002-08-02  6:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020727072846Z318708-685+18874@vger.kernel.org>
2002-07-27  8:54 ` elks newbie.....kindly help!! Seemanta Dutta
2002-07-27  9:02   ` Paul Nasrat
2002-07-27  9:18     ` Paul Nasrat
2002-07-27  9:30     ` thanks from elks newbie...!! Seemanta Dutta
2002-07-27  9:37       ` Paul Nasrat
2002-07-30  7:17         ` Seemanta Dutta
2002-07-30  8:17           ` Paul Nasrat
2002-07-31 21:26             ` Dan Olson
2002-07-31 21:53               ` Elks freeze after login Christophe Gimenez
2002-08-01 22:48                 ` Riley Williams
2002-08-02  6:07                   ` Christophe Gimenez [this message]
2002-08-02 12:02                     ` Can't compile elksnet Christophe Gimenez
2002-08-02 15:18                     ` Elks freeze after login [machine config] Harry Kalogirou
2002-08-02 16:02                       ` Pat Gilliland
2002-08-02 19:02                       ` Riley Williams
2002-08-03 10:17                         ` Harry Kalogirou
2002-07-30  8:22           ` thanks from elks newbie...!! Javier Sedano

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='001901c239ea$d4b30df0$0101a8c0@workstation' \
    --to=chris@kandji.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