public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
* ethernet nic install
@ 2004-08-03 10:30 Andrew
  2004-08-03 19:20 ` pa3gcu
  0 siblings, 1 reply; 6+ messages in thread
From: Andrew @ 2004-08-03 10:30 UTC (permalink / raw)
  To: linux-newbie

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: ethernet nic install
  2004-08-03 10:30 ethernet nic install Andrew
@ 2004-08-03 19:20 ` pa3gcu
  2004-08-04 16:49   ` Andrew
  0 siblings, 1 reply; 6+ messages in thread
From: pa3gcu @ 2004-08-03 19:20 UTC (permalink / raw)
  To: Andrew; +Cc: linux-newbie

On Tuesday 03 August 2004 12:30, Andrew wrote:
> Hello,
> I am having trouble trying to install an rtl8139 nic on a 486 running
> Slackware 9.0.

Firstly, you said "486" that means your bios needs to be setup in a completly 
different way that presant day BIOS's are, we have today whats called 
plug-and-play, you have an old motherboard which only supports plug-and-pray.
That meaning if you set your BIOS to (if i remember correctly) "user define" 
then i can imagen why you are having so many problems as PCI cards cannot get 
an IRQ because you have set them all aside for ISA cards.

Now secondly, why i ask are you using the 8139cp driver when your type of card 
needs the 8139too driver.?????

If i was you i would setup my BIOS to have at least one IRQ for PCI, that way 
you get automatic allocation of IRQ's for PCI cards, i am convinced that you 
have set your BIOS to something other than what i stated.

I would place into /etc/rc.d/rc.netdevice the following;

/sbin/modprobe 8139too

Another thing here is that you state "eth1" is the interface concerned, that 
means its the second ethernet device in your system, do you have a working 
eth0 device and if so what is it and is it working.???

>  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

Possably, but it is saying, i am here but i am having many problems due to 
misconfiguration.
The error in itself is unexplanatry, possably due to what i have written 
above.

>
> 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.

Ok if it works fine in another machine, what is the other machine and how is 
the BIOS setup to detect the card.???

It means set the IRQ to what i set aside in my BIOS, but you have not (if i am 
wrong correct me) done that.

>
> 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:

google is a wonderfull machine, what it does not tell you is that you 
sometimes need to read between lines.

>
> PCI: Error b1 when fetching IRQ routing table.

That is understandable, your BIOS is not setup correctly.

> Any insights?

Plenty more if what i have explained is not your answer.
I have a few 486 machines running at remote sites with rtl8139 nic's, take it 
from me they all work and they use the 8139too driver.

> 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

-- 
If the Linux community is a bunch of thieves because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

-
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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: ethernet nic install
  2004-08-03 19:20 ` pa3gcu
@ 2004-08-04 16:49   ` Andrew
  2004-08-04 18:41     ` pa3gcu
  0 siblings, 1 reply; 6+ messages in thread
From: Andrew @ 2004-08-04 16:49 UTC (permalink / raw)
  To: linux-newbie

pa3gcu wrote:
> 
> Firstly, you said "486" 

Sorry. I was suffering from heatstroke. It's a very ancient pentium 60Mhz.

> Now secondly, why i ask are you using the 8139cp driver when your type of card 
> needs the 8139too driver.?????

Good question. I'm not. I have only used the 8139too driver and can't 
figure out why there is any reference at all to the 8139cp (I didn't 
even know it existed and didn't notice it until after my first post).

> 
> I would place into /etc/rc.d/rc.netdevice the following;
> 
> /sbin/modprobe 8139too

So far I have loaded it manually, from /etc.rc.d/rc.modules and with 
'netconfig', which detects the nic if I remove the other one (see below).

> Another thing here is that you state "eth1" is the interface concerned, that 
> means its the second ethernet device in your system, do you have a working 
> eth0 device and if so what is it and is it working.???

Yes, 3c509 isapnp and yes.

I shall have another go at the BIOS (It is the strangest I have ever 
seen) and maybe come back to you.

Thanks, anyway,

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: ethernet nic install
  2004-08-04 16:49   ` Andrew
@ 2004-08-04 18:41     ` pa3gcu
  2004-08-05 10:49       ` Andrew
  0 siblings, 1 reply; 6+ messages in thread
From: pa3gcu @ 2004-08-04 18:41 UTC (permalink / raw)
  To: Andrew; +Cc: linux-newbie

On Wednesday 04 August 2004 18:49, Andrew wrote:
> pa3gcu wrote:
> > Firstly, you said "486"
>
> Sorry. I was suffering from heatstroke. It's a very ancient pentium 60Mhz.
>
> > Now secondly, why i ask are you using the 8139cp driver when your type of
> > card needs the 8139too driver.?????
>
> Good question. I'm not. I have only used the 8139too driver and can't
> figure out why there is any reference at all to the 8139cp (I didn't
> even know it existed and didn't notice it until after my first post).
>
> > I would place into /etc/rc.d/rc.netdevice the following;
> >
> > /sbin/modprobe 8139too
>
> So far I have loaded it manually, from /etc.rc.d/rc.modules and with
> 'netconfig', which detects the nic if I remove the other one (see below).

Another indication that your BIOS is setup for PnP and NOT PCI or shared.

> > Another thing here is that you state "eth1" is the interface concerned,
> > that means its the second ethernet device in your system, do you have a
> > working eth0 device and if so what is it and is it working.???
>
> Yes, 3c509 isapnp and yes.

Ok i presume you know which IRQ this nic uses, so simply set that IRQ to PnP 
or ISA in your BIOS, leave the rest to PCI (presuming you only have one ISA 
card in the machine).

> I shall have another go at the BIOS (It is the strangest I have ever
> seen) and maybe come back to you.

Yes, they are somewhat differnet to todays BIOS's.

>
> Thanks, anyway,
>
> Andrew
>

-- 
If the Linux community is a bunch of thieves because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

-
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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: ethernet nic install
  2004-08-04 18:41     ` pa3gcu
@ 2004-08-05 10:49       ` Andrew
  0 siblings, 0 replies; 6+ messages in thread
From: Andrew @ 2004-08-05 10:49 UTC (permalink / raw)
  To: linux-newbie

pa3gcu wrote:
> Another indication that your BIOS is setup for PnP and NOT PCI or shared.
> 
>>I shall have another go at the BIOS (It is the strangest I have ever
>>seen) and maybe come back to you.
> 
> 
> Yes, they are somewhat differnet to todays BIOS's.

Perhaps you could help me with the settings:
PCI Slot Number: I think even I can manage that one.
Function Number of Device: Dunno (1-7)
Device Function: Presumably I choose Enabled (Enabled/Disabled)

IRQ Level for INTA Pin and ditto for INTB, INTC, INTD has me thrown.

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: ethernet nic install
@ 2004-08-05 14:37 pa3gcu
  0 siblings, 0 replies; 6+ messages in thread
From: pa3gcu @ 2004-08-05 14:37 UTC (permalink / raw)
  To: linux-newbie

> pa3gcu wrote:
> > Another indication that your BIOS is setup for PnP and NOT PCI or shared.
> >
> >>I shall have another go at the BIOS (It is the strangest I have ever
> >>seen) and maybe come back to you.
> >
> >
> > Yes, they are somewhat differnet to todays BIOS's.
>
> Perhaps you could help me with the settings:
> PCI Slot Number: I think even I can manage that one.
> Function Number of Device: Dunno (1-7)

Without knowing what type of bios you have i cant really say, however is there 
not some sort of help in the bios, where it says, 1 = pci 2 = legacy etc 
etc.?

> Device Function: Presumably I choose Enabled (Enabled/Disabled)

I would imagen so yes.

>
> IRQ Level for INTA Pin and ditto for INTB, INTC, INTD has me thrown.

Just leave those alone, choose default.

Old BIOS's can be a pian in the butt, but all you need to do is set the IRQ 
which you ISA nic uses too ISA and leave the PCI to PnP.

Another way to get more information on a BIOS is go to the manufactures web 
site, they may well have a FAQ sheet for you to review.

Sorry i'm vauge but as i said without knowing the bios manufacture it would be 
hard for anyone to advise.


>
> TIA,
>
> Andrew
-- 
If the Linux community is a bunch of thieves because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

-
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

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2004-08-05 14:37 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-08-03 10:30 ethernet nic install Andrew
2004-08-03 19:20 ` 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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox