linux-alpha.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: SA <bullet.train@ntlworld.com>
To: linux-alpha@vger.kernel.org
Subject: kernel compile problems (tulip / tulip_old) + more
Date: Tue, 20 Aug 2002 10:09:28 +0100	[thread overview]
Message-ID: <200208201009.28318.bullet.train@ntlworld.com> (raw)


Dear list,

I need to recompile the kernel to include osf partition support, however
it fails to compile because of a conflict between the tulip driver and the
tulip_old driver - (some errors below) - in the config menus I can only find 
an option relating to the tulip driver (I have a tulip network card). Any
ideas ? 

thanks SA

Also, I have an alpha machine that had its PROM trashed by a firmware update
(update firmware (y/n) y / erasing PROM / updating PROM / Failed....) now the
computer is dead and won't even perform the hardware jumpered "failsafe
booot from floppy" -  has anyone had any experience with this?, Is it possible 
to get a new PROM?

thanks SA








-----

some errors

tulip_old/tulip_old.o(.data+0x0): multiple definition of `tulip_tbl'
tulip/tulip.o(.data+0x0): first defined here
tulip_old/tulip_old.o: In function `mxic_timer':
tulip_old/tulip_old.o(.text+0x2f70): multiple definition of `mxic_timer'
tulip/tulip.o(.text+0x2ff0): first defined here
make[3]: *** [net.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.4.9-32.5/drivers/net'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.9-32.5/drivers/net'
make[1]: *** [_subdir_net] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.9-32.5/drivers'
make: *** [_dir_drivers] Error 2

             reply	other threads:[~2002-08-20  9:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-20  9:09 SA [this message]
2002-08-20 12:23 ` kernel compile problems (tulip / tulip_old) + more Kurt Garloff

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=200208201009.28318.bullet.train@ntlworld.com \
    --to=bullet.train@ntlworld.com \
    --cc=linux-alpha@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 NNTP newsgroup(s).