RE: [expert] Network Card Problems

[Carl Lafferty]

That's true.  Ill have to give it a shot this weekend if I can
get my wife off of ebay long enough to boot the PC into linux
and get connectiong sharing working there so I can use either OS
I wanna with no interruption to the boss :)



--
"'Tis some script kidd3z," I muttered, "tapping at my server port-
Only this, and nothing more."
Edgar root Poe


> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Karl Cunningham
> Sent: Thursday, March 08, 2001 4:34 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [expert] Network Card Problems
>
>
> Consider setting the PCI IRQ's manually via BIOS rather than
> letting the
> mobo set them itself on bootup.  And use setup programs that
> usually come
> with PNP ISA cards to set their IRQs.  I've done this on the last few
> systems I've put together and have had a no problems at all with IRQs.
>
> Most newer BIOSes will let you do this and almost every PCI
> card uses IRQ
> A, so you can set them up however you like.  Watch out for
> things like the
> Realtek-based NICs that can't reliably share IRQs.
>
> At least you know what's going on if you set them up manually.
>
> Karl
>
>
> At 02:48 PM 3/6/2001 +0100, you wrote:
> >
> >I had a similar problem lately. I had a defective mobo
> replaced, and after
> >that the soundblaster didn't work. After switching the
> soundblaster and the
> >NIC from their respective slots, the NIC didn't work...
> >
> >Then I put the NIC in a different PCI-slot, assuming the
> previous slot must
> >have been broken. Then it appeared to work, linux detected
> the NIC, the
> >modules loaded OK, everything went cool, untill I actually
> tried to use the
> >network.
> >
> >Further testing revealed that the replacement mobo had 2
> total dead and 1
> >cripple PCI-slot. After sending it back, and getting 2 more
> mobos (next
> >replacement came with defective PS/2 connections... Djees!)
> it finally
> >works.
> >
> >Bottom line: screw open the case, and try putting the NIC in
> a different
> >PCI slot, and see if it helps. If it does, either the mobo
> is defective, or
> >you got one of them PCI incompatibility things that occurs
> on the last (or
> >is it first) slot of a PCI-system... Which is completely
> normal, btw...
>
>

Re: [expert] Network Card Problems

[Karl Cunningham]

Consider setting the PCI IRQ's manually via BIOS rather than letting the
mobo set them itself on bootup.  And use setup programs that usually come
with PNP ISA cards to set their IRQs.  I've done this on the last few
systems I've put together and have had a no problems at all with IRQs.

Most newer BIOSes will let you do this and almost every PCI card uses IRQ
A, so you can set them up however you like.  Watch out for things like the
Realtek-based NICs that can't reliably share IRQs.

At least you know what's going on if you set them up manually.

Karl


At 02:48 PM 3/6/2001 +0100, you wrote:
>
>I had a similar problem lately. I had a defective mobo replaced, and after
>that the soundblaster didn't work. After switching the soundblaster and the
>NIC from their respective slots, the NIC didn't work...
>
>Then I put the NIC in a different PCI-slot, assuming the previous slot must
>have been broken. Then it appeared to work, linux detected the NIC, the
>modules loaded OK, everything went cool, untill I actually tried to use the
>network.
>
>Further testing revealed that the replacement mobo had 2 total dead and 1
>cripple PCI-slot. After sending it back, and getting 2 more mobos (next
>replacement came with defective PS/2 connections... Djees!) it finally
>works.
>
>Bottom line: screw open the case, and try putting the NIC in a different
>PCI slot, and see if it helps. If it does, either the mobo is defective, or
>you got one of them PCI incompatibility things that occurs on the last (or
>is it first) slot of a PCI-system... Which is completely normal, btw...

RE: [expert] Network Card Problems

[Carl Lafferty]

>
> Maybe if you tell it to use irq 9?
>
> In my /etc/modules.conf file i have the following entry
> alias eth0 3c59x
>
> if i wanted to tell it to use irq 9 i believe i would modify
> it like so:
> alias eth0 3c59x irq=9
>
I tried that.  No go.  I have tried turning off PNP in my bios
and even using a different driver (e100 as opposed to the one
that is there  eepro100 I think) thanks to another user with nearly
the same problem.  No go :(

I think this weekend I am going to play shuffle the PCI cards
and see what I can either break or fix with this..


--
"'Tis some script kidd3z," I muttered, "tapping at my server port-
Only this, and nothing more."
Edgar root Poe

Re: [expert] Network Card Problems

[John Wolford]

Maybe if you tell it to use irq 9?

In my /etc/modules.conf file i have the following entry
alias eth0 3c59x

if i wanted to tell it to use irq 9 i believe i would modify it like so:
alias eth0 3c59x irq=9

You could try that, but i don't say that it will work for you for sure.

Cheers,
j



--- Carl Lafferty <[EMAIL PROTECTED]> wrote:
> I have an Intel pro 100+ Network card (that's what windows idents it as)
> and since I upgraded my mobo from an asus p5ab to a p3b-f I can't get it to
> work in linux at all any more.  everything APPEARS to work fine however.
> it is apparently detected and it did work prior to the mobo change.. .. 
>  I even did a complete reinstall of linux mandrake 7.2 and no go.
> 
> I used the dmesg command to obtain some info:
> 
> eepro100.c:v1.09j-t 9/29/99 Donald Becker
> http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
> eepro100.c: $Revision: 1.20.2.10 $ 2000/05/31 Modified by Andrey V.
> Savochkin <[EMAIL PROTECTED]> and others
> eth0: OEM i82557/i82558 10/100 Ethernet, 00:D0:B7:7E:19:75, I/O at 0xd000,
> IRQ 0.
>   Receiver lock-up bug exists -- enabling work-around.
>   Board assembly 727095-007, Physical connectors present: RJ45
>   Primary interface chip i82555 PHY #1.
>   General self-test: passed.
>   Serial sub-system self-test: passed.
>   Internal registers self-test: passed.
>   ROM checksum self-test: passed (0x04f4518b).
> 
> 
> 
> I am unsure why it is showing the card as having IRQ 0.  Windows says
> it is on irq 9..
> 
> 
> 
> this is important since when I want to do things in linux at home
> my wife still has to be able to get out to the net thru internet
> connection sharing.
> 
> Any help is appreciated.
> 
> --
> Carl Lafferty
> System Administrator, Floyd County Public Library
> Registered Linux User #201131
> 


__
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail. 
http://personal.mail.yahoo.com/

Re: [expert] Network Card Problems

[Rial Juan]

I had a similar problem lately. I had a defective mobo replaced, and after
that the soundblaster didn't work. After switching the soundblaster and the
NIC from their respective slots, the NIC didn't work...

Then I put the NIC in a different PCI-slot, assuming the previous slot must
have been broken. Then it appeared to work, linux detected the NIC, the
modules loaded OK, everything went cool, untill I actually tried to use the
network.

Further testing revealed that the replacement mobo had 2 total dead and 1
cripple PCI-slot. After sending it back, and getting 2 more mobos (next
replacement came with defective PS/2 connections... Djees!) it finally
works.

Bottom line: screw open the case, and try putting the NIC in a different
PCI slot, and see if it helps. If it does, either the mobo is defective, or
you got one of them PCI incompatibility things that occurs on the last (or
is it first) slot of a PCI-system... Which is completely normal, btw...

On 2001.03.07 00:19 Carl Lafferty wrote:
> I have an Intel pro 100+ Network card (that's what windows idents it as)
> and since I upgraded my mobo from an asus p5ab to a p3b-f I can't get it
> to
> work in linux at all any more.  everything APPEARS to work fine however.
> it is apparently detected and it did work prior to the mobo change.. .. 
>  I even did a complete reinstall of linux mandrake 7.2 and no go.
> 
> I used the dmesg command to obtain some info:
> 
> eepro100.c:v1.09j-t 9/29/99 Donald Becker
> http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
> eepro100.c: $Revision: 1.20.2.10 $ 2000/05/31 Modified by Andrey V.
> Savochkin <[EMAIL PROTECTED]> and others
> eth0: OEM i82557/i82558 10/100 Ethernet, 00:D0:B7:7E:19:75, I/O at
> 0xd000,
> IRQ 0.
>   Receiver lock-up bug exists -- enabling work-around.
>   Board assembly 727095-007, Physical connectors present: RJ45
>   Primary interface chip i82555 PHY #1.
>   General self-test: passed.
>   Serial sub-system self-test: passed.
>   Internal registers self-test: passed.
>   ROM checksum self-test: passed (0x04f4518b).
> 
> 
> 
> I am unsure why it is showing the card as having IRQ 0.  Windows says
> it is on irq 9..
> 
> 
> 
> this is important since when I want to do things in linux at home
> my wife still has to be able to get out to the net thru internet
> connection sharing.
> 
> Any help is appreciated.
> 
> --
> Carl Lafferty
> System Administrator, Floyd County Public Library
> Registered Linux User #201131
> 
> 
-- 
Rial Juan
e-mail:  [EMAIL PROTECTED]
   ICQ:20135549
Belgiumtel:++3289856533
  cellular:   ++32496737018
ulyssis system admininstrator   

1010011010 : Binary of the Beast

[expert] Network Card Problems

[Carl Lafferty]

I have an Intel pro 100+ Network card (that's what windows idents it as)
and since I upgraded my mobo from an asus p5ab to a p3b-f I can't get it to
work in linux at all any more.  everything APPEARS to work fine however.
it is apparently detected and it did work prior to the mobo change.. .. 
 I even did a complete reinstall of linux mandrake 7.2 and no go.

I used the dmesg command to obtain some info:

eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
eepro100.c: $Revision: 1.20.2.10 $ 2000/05/31 Modified by Andrey V.
Savochkin <[EMAIL PROTECTED]> and others
eth0: OEM i82557/i82558 10/100 Ethernet, 00:D0:B7:7E:19:75, I/O at 0xd000,
IRQ 0.
  Receiver lock-up bug exists -- enabling work-around.
  Board assembly 727095-007, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x04f4518b).



I am unsure why it is showing the card as having IRQ 0.  Windows says
it is on irq 9..



this is important since when I want to do things in linux at home
my wife still has to be able to get out to the net thru internet
connection sharing.

Any help is appreciated.

--
Carl Lafferty
System Administrator, Floyd County Public Library
Registered Linux User #201131

Re: [expert] Network Card Problems

[Hidong Kim]

Nichols, Jason wrote:
> 
> I've got an Intel Etherexpress Pro (or compatible) ISA card.  During setup
> linux tried to autodetect the card and it froze.  How can I setup the
> network card after the original setup has already been completed?  I was
> looking at insmod...but that seemed to have hung my system (again).  Any
> ideas?  The mod I tried to install was eepro.o
> Thanks!
> Jason


Hi, Jason,

We have two Linux machines running Mandrake 5.3 with Intel EtherExpress
Pro/100 cards.  We installed these cards after recompiling a 2.2.9
kernel with EEPro100 support, which is actually a default setting in the
kernel config options.  Then we used Network Configurator in the Control
Panel to configure the cards.  Good luck,



Hidong

[expert] Network Card Problems

[Nichols, Jason]

I've got an Intel Etherexpress Pro (or compatible) ISA card.  During setup
linux tried to autodetect the card and it froze.  How can I setup the
network card after the original setup has already been completed?  I was
looking at insmod...but that seemed to have hung my system (again).  Any
ideas?  The mod I tried to install was eepro.o
Thanks!
Jason