All of lore.kernel.org
 help / color / mirror / Atom feed
From: caslivkoff@telocity.com
To: Matthew Wilcox <willy@debian.org>, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Errors trying to compile 2.4.6-pa22
Date: Wed, 01 Aug 2001 00:59:51 -0400	[thread overview]
Message-ID: <3B678CC7.6AC58107@telocity.com> (raw)
In-Reply-To: 20010730143254.A25867@parcelfarce.linux.theplanet.co.uk

Matthew Wilcox wrote:
> 
> On Mon, Jul 30, 2001 at 01:31:07AM -0400, caslivkoff@telocity.com wrote:
> > Hi list,
> >
> > I've been trying to compile a new kernel on my 712/80 (128MB RAM) while
> > running 2.4.0-pa25. I downloaded linux-latest.tar.gz (2.4.6-pa22),
> 
> > drivers/char/char.o: In function `read_port':
> > drivers/char/char.o(.text.read_port+0x6c): undefined reference to `inb'
> 
> You turned off CONFIG_PCI.  This is not currently supported; but we were
> discussing how to fix it yesterday.  For the moment, enable it.

Thanks, that got it to build.

But, when I booted from this kernel, the STI console was unusable. 
Unfortunately, the network did not come up either (using dhcp), so I was
forced to pull the plug and boot the older kernel.

The only signficant thing I noticed was that the PS/2 mouse port was
active, but no device attached. I attached mouse (old Logitech) &
rebooted.
The keyboard was still unusable, but since gpm did start OK, I was able
to
carefully select/paste to login. I did get a look at the process table
and
the gettys were running, but dhcpcd was not. I suppose I could have
tried
to start it, but I didn't recall the syntax. 

Any ideas/suggestions/thoughts?

      reply	other threads:[~2001-08-01  4:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30  5:31 [parisc-linux] Errors trying to compile 2.4.6-pa22 caslivkoff
2001-07-30  5:51 ` Randolph Chung
2001-07-30 13:32 ` Matthew Wilcox
2001-08-01  4:59   ` caslivkoff [this message]

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=3B678CC7.6AC58107@telocity.com \
    --to=caslivkoff@telocity.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=willy@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.