From: Andrew <ald2@arrakis.es>
To: linux-newbie@vger.kernel.org
Subject: ethernet nic install
Date: Tue, 03 Aug 2004 12:30:04 +0200 [thread overview]
Message-ID: <410F692C.3070303@arrakis.es> (raw)
Hello,
I am having trouble trying to install an rtl8139 nic on a 486 running
Slackware 9.0.
From dmesg:
8139too Fast Ethernet driver 0.9.26
PCI: Enabling device 00:03.0 (0000 -> 0003)
PCI: No IRQ known for interrupt pin A of device 00:03.0. Please try
using pci=biosirq.
eth1: RealTek RTL8139 Fast Ethernet at 0xc1821000, (hw address), IRQ 0
eth1: Identified 8139 chip type 'RTL-8139C'
...
8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
lspci lists the nic OK. The module is loaded OK. ifconfig -a shows the
interface exists, hw addresss is correct, but no ip address. Trying to
bring it up or give it an ip address with ifconfig gets the reply:
SIOCSIFFLAGS: Device or resource busy
I've never heard of this pci=biosirq business. If I thought it might
help I would be delighted to 'use it', but where and how? BTW, this same
nic works fine in other machines.
Google turns up about 3,000 people asking what pci=biosirq means. One
reply pointed me to the kernel-documentation. It seems I should add
append="pci=biosirq" in lilo.conf. This has made no difference except
that I now get the following message in dmesg:
PCI: Error b1 when fetching IRQ routing table.
Any insights?
TIA,
Andrew
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next reply other threads:[~2004-08-03 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 10:30 Andrew [this message]
2004-08-03 19:20 ` ethernet nic install pa3gcu
2004-08-04 16:49 ` Andrew
2004-08-04 18:41 ` pa3gcu
2004-08-05 10:49 ` Andrew
-- strict thread matches above, loose matches on Subject: below --
2004-08-05 14:37 pa3gcu
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=410F692C.3070303@arrakis.es \
--to=ald2@arrakis.es \
--cc=linux-newbie@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 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.