mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tim Coleman <tim@epenguin.org>
To: linux-kernel@vger.kernel.org
Subject: Re: RTL8139 conflicting with hard drive?
Date: Fri, 30 Mar 2001 13:16:14 -0500	[thread overview]
Message-ID: <20010330131614.A744@tux.epenguin.org> (raw)
In-Reply-To: <20010330085208.A428@tux.epenguin.org>
In-Reply-To: <20010330085208.A428@tux.epenguin.org>; from tim@epenguin.org on Fri, Mar 30, 2001 at 08:52:08AM -0500

On Fri, Mar 30, 2001 at 08:52:08AM -0500, Tim Coleman wrote:
> I'm having a problem with a NIC I tried to install this morning.
> The chip on the NIC says its an RTL-8139B (it's a generic brand
> NIC, and I didn't really need anything fancy).
> 
> When I install the NIC, and try to boot, the kernel complains
> about not being able to find the root device.  If I take it out,
> everything is fine.  I'm using kernel version 2.4.1, and my 
> motherboard is an Asus A7V.  
> 
> I already have one RTL-8139B NIC installed, and it's just fine.
> 
> I also noticed that the kernel seemed to detect it as an IDE
> controller, because two more IDE devices showed up in the boot
> messages.
> 
> What could cause this?  More importantly, what's a good remedy?

Sorry about posting that.  I figured out what I was doing wrong,
and everything works now.  The new NIC I put in was stealing the
hardware addresses used by my IDE controller.

A change to lilo.conf fixed everything.

-- 
Tim Coleman <tim@epenguin.org>                         [43.28 N 80.31 W]
Software Developer/Systems Administrator/RDBMS Specialist/Linux Advocate
University of Waterloo Honours Co-op Combinatorics & Optimization
"Go to Heaven for the climate, Hell for the company." -- Mark Twain


      reply	other threads:[~2001-03-30 18:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-30 13:52 Tim Coleman
2001-03-30 18:16 ` Tim Coleman [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=20010330131614.A744@tux.epenguin.org \
    --to=tim@epenguin.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®