Try assigning a lower i/o and a lower irq. Try irq 7 and i/o 350
on eth1. It looks like it recognized that second card okay. The
first one is what it doen't recognize. But since it works, i'd
just as soon leave it alone. Did you check the 3com website to
see if there's a newer driver you can compile? Or did you try
loading another module for that second card?
-----Original Message-----
From: Michael J. McGillick [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, January 18, 2000 9:41 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Ethernet Question - Take 2 :)
Ok:
I think I'm getting closer here :)
First of all, thanks to everyone who passed on information on how
to look
up ioports, irqs, etc. It's really appreciated. Here is what
I've been
able to gleen, and maybe someone will spot the problem right
away:
/proc/pci reveals:
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: Intel 440BX - 82443BX Host (no AGP) (rev 2).
Medium devsel. Master Capable. Latency=64.
Prefetchable 32 bit memory at 0x0 [0x8].
Bus 0, device 4, function 0:
ISA bridge: Intel 82371AB PIIX4 ISA (rev 2).
Medium devsel. Fast back-to-back capable. Master Capable.
No
bursts.
Bus 0, device 4, function 1:
IDE interface: Intel 82371AB PIIX4 IDE (rev 1).
Medium devsel. Fast back-to-back capable. Master Capable.
Latency=32.
I/O at 0xfcd0 [0xfcd1].
Bus 0, device 4, function 2:
USB Controller: Intel 82371AB PIIX4 USB (rev 1).
Medium devsel. Fast back-to-back capable. Master Capable.
Latency=32.
I/O at 0xfce0 [0xfce1].
Bus 0, device 4, function 3:
Bridge: Intel 82371AB PIIX4 ACPI (rev 2).
Medium devsel. Fast back-to-back capable.
Bus 0, device 7, function 0:
PCI bridge: Intel i960 (rev 3).
Medium devsel. Fast back-to-back capable. Master Capable.
Latency=56.
Min Gnt=7.Max Lat=6.
Bus 0, device 7, function 1:
Unknown class: Intel Unknown device (rev 3).
Vendor id=8086. Device id=1960.
Medium devsel. Fast back-to-back capable. BIST capable.
IRQ 9.
Master
Capable. Latency=32.
Prefetchable 32 bit memory at 0xfb000000 [0xfb000008].
Bus 0, device 8, function 0:
PCI bridge: DEC DC21152 (rev 2).
Medium devsel. Fast back-to-back capable. Master Capable.
Latency=57.
Min Gnt=7.Max Lat=2.
Bus 0, device 11, function 0:
System peripheral: Hewlett Packard Unknown device (rev 160).
Vendor id=103c. Device id=10c1.
Slow devsel.
Non-prefetchable 32 bit memory at 0xfedf8000 [0xfedf8000].
Bus 0, device 13, function 0:
VGA compatible controller: Cirrus Logic GD 5446 (rev 69).
Medium devsel.
Prefetchable 32 bit memory at 0xfc000000 [0xfc000008].
Non-prefetchable 32 bit memory at 0xfedf7000 [0xfedf7000].
Bus 1, device 4, function 0:
Ethernet controller: 3Com Unknown device (rev 116).
Vendor id=10b7. Device id=9200.
Medium devsel. IRQ 10. Master Capable. Latency=80. Min
Gnt=10.Max Lat=10.
I/O at 0xec00 [0xec01].
Non-prefetchable 32 bit memory at 0xfebff800 [0xfebff800].
Bus 1, device 7, function 0:
SCSI storage controller: NCR 53c895 (rev 1).
Medium devsel. IRQ 11. Master Capable. Latency=247. Min
Gnt=30.Max Lat=64.
I/O at 0xe800 [0xe801].
Non-prefetchable 32 bit memory at 0xfebff400 [0xfebff400].
Non-prefetchable 32 bit memory at 0xfebfe000 [0xfebfe000].
Bus 2, device 2, function 0:
Ethernet controller: 3Com 3C905B 100bTX (rev 100).
Medium devsel. IRQ 15. Master Capable. Latency=80. Min
Gnt=10.Max Lat=10.
I/O at 0xdc00 [0xdc01].
Non-prefetchable 32 bit memory at 0xfeaff800 [0xfeaff800].
/proc/interrupts reveals:
CPU0
0: 3932662 XT-PIC timer
1: 3211 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 1 XT-PIC soundblaster
8: 1 XT-PIC rtc
9: 21 XT-PIC megaraid
10: 75762 XT-PIC eth0
11: 14856 XT-PIC sym53c8xx
12: 2181 XT-PIC PS/2 Mouse
13: 1 XT-PIC fpu
14: 4 XT-PIC ide0
15: 7104078 XT-PIC eth1
NMI: 0
/proc/ioport reveals:
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
01f0-01f7 : ide0
0220-022f : soundblaster
02f8-02ff : serial(auto)
0330-0333 : MPU-401 UART
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(auto)
0620-0623 : sound driver (AWE32)
0a20-0a23 : sound driver (AWE32)
0e20-0e23 : sound driver (AWE32)
e800-e87f : sym53c8xx
ec00-ec7f : 3Com EtherLink PCI NIC
fcd0-fcd7 : ide0
Now, first thing I noticed was that /proc/pci is able to
determine what my
eth1 card is (IRQ 15), but lists it as 3Com unknown for eth0. I
have a
feeling this is an indication to start off with of part of the
problem.
Further, /proc/ioports does not show more than one Ethernet card.
If
there are two in the machine, I would think they would be using
two
different memory ranges, as that is what I orignally set up in my
lilo.conf line.
Anyone here see anything glaring that points to the problem right
away?
Someone mentioned that it may be my sound card interferring.
It's on IRQ
5, and the cards are on 10 and 15 respectively.
- Mike
On Tue, 18 Jan 2000, Jeff Graves wrote:
> Looks to me like a config issue with eth1. Check the irq and
i/o
> settings and make sure that they don't conflit with any other
> devices. Usually, if you have a sound card, they like to take
the
> 200-330 range so make the second card an i/o of 350 and irq of
> 10. That's what i usually use. Otherwise, try a different
module.
>
> -----Original Message-----
> From: Michael J. McGillick [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, January 18, 2000 3:44 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Ethernet Question - Take 2 :)
>
> Jeff:
>
> A quick check in /var/log/messages reveals this right after I
did
> the
> network restart command you suggested:
>
> Jan 18 15:24:30 universe pumpd[1734]: starting at Tue Jan 18
> 15:24:30 2000
> Jan 18 15:24:41 universe pumpd[1734]: configured interface eth0
> Jan 18 15:24:41 universe ifup: done.
> Jan 18 15:24:41 universe network: Bringing up interface eth0
> succeeded
> Jan 18 15:24:42 universe ifup: SIOCSIFFLAGS: No such device
> Jan 18 15:24:42 universe ifup: SIOCADDRT: Network is down
> Jan 18 15:24:42 universe network: Bringing up interface eth1
> succeeded
>
> Does this point to anything?
>
> - Mike
>
> On Tue, 18 Jan 2000, Jeff Graves wrote:
>
> > Which card is eth1? I would suggest changing the module for
> that
> > one. I remember you saying that it originally used 3c59x
> module.
> > I would try loading that one for eth1 so if it helps. Also,
> check
> > /var/log/messages to see if it has any relevant info.
> >
> > -----Original Message-----
> > From: Michael J. McGillick
[SMTP:[EMAIL PROTECTED]]
> > Sent: Tuesday, January 18, 2000 3:27 PM
> > To: '[EMAIL PROTECTED]'
> > Subject: RE: Ethernet Question - Take 2 :)
> >
> > Jeff:
> >
> > I just tried this on my machine:
> >
> > /etc/rc.d/init.d: ./network restart
> > Shutting down interface eth0 [
> OK
> > ]
> > Shutting down interface eth1 [
> OK
> > ]
> > Disabling IPv4 packet forwarding [
> OK
> > ]
> > Enabling IPv4 packet forwarding [
> OK
> > ]
> > Bringing up interface lo [
> OK
> > ]
> > Bringing up interface eth0 [
> OK
> > ]
> > Bringing up interface eth1 [
> OK
> > ]
> >
> > Then ifconfig shows this:
> >
> > eth0 Link encap:Ethernet HWaddr 00:50:DA:BD:88:60
> > inet addr:24.218.81.23 Bcast:24.218.83.255
> > Mask:255.255.252.0
> > UP BROADCAST RUNNING MTU:1500 Metric:1
> > RX packets:18926 errors:0 dropped:0 overruns:0
> frame:0
> > TX packets:7778 errors:0 dropped:0 overruns:0
> carrier:0
> > collisions:0 txqueuelen:100
> > Interrupt:10 Base address:0xec00
> >
> > lo Link encap:Local Loopback
> > inet addr:127.0.0.1 Mask:255.0.0.0
> > UP LOOPBACK RUNNING MTU:3924 Metric:1
> > RX packets:86 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:86 errors:0 dropped:0 overruns:0
carrier:0
> > collisions:0 txqueuelen:0
> >
> > Notice still no eth1. By the way, I thought network was
called
> > when the
> > machine booted up? Like I mentioned, when I first boot the
> > machine, all
> > three interfaces (eth0, eth1, and lo) show when I do an
> ifconfig.
> > After a
> > short period, eth1 goes away, and I'd like to try and figure
> out
> > why.
> >
> > - Mike
> >
> > On Tue, 18 Jan 2000, Jeff Graves wrote:
> >
> > > Did you do a /etc/rc.d/init.d/network restart after
bringing
> up
> > > interfaces?
> > >
> > > -----Original Message-----
> > > From: Michael J. McGillick
> [SMTP:[EMAIL PROTECTED]]
> > > Sent: Tuesday, January 18, 2000 1:26 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: Ethernet Question - Take 2 :)
> > >
> > > Morning Everyone:
> > >
> > > I just recently did a reinstall of Red Hat 6.1. Before
doing
> > the
> > > install,
> > > I put two new Ethernet cards in the machine, a 3Com
Etherlink
> > > 10/100 Mbps
> > > PCI (Model # 3c905C-TX-M) and a 3Com Fast Etherlink XL PCI
> > (3C90x
> > > family).
> > > Well, correct me if I'm wrong, but my assumption was that
> these
> > > cards
> > > should use the 3c90x module. After the install finished, I
> > > looked in
> > > conf.modules and saw the following:
> > >
> > > alias eth0 3c59x
> > >
> > > Oddly enough, my connection for eth0 seemed to come up
fine.
> I
> > > still
> > > didn't have anything for eth1, so I went into X and started
> up
> > > the
> > > control-panel and started up networking. It showed the
> second
> > > interface on my machine, but that it was disabled. I
> > configured
> > > it
> > > with a static IP address of 192.168.1.1, and selected to
have
> > it
> > > come
> > > up at boot. I then enabled it, and sure enough, the
> interface
> > > showed in
> > > ifconfig.
> > >
> > > After rebooting, I watched the start-up process, and
noticed
> > that
> > > eth0 was
> > > initialized with no problem. However, with eth1, I got the
> > error
> > > message
> > > about delaying initialization. Hmmm.
> > >
> > > I thought back to what others had said on this list, and
> > > remembered
> > > something about conf.modules and specifying which module to
> use
> > > for a
> > > particular card. Well, I changed the line in
> /etc/conf.modules
> > > to this:
> > >
> > > alias eth0 3c90x
> > > alias eth1 3c90x
> > >
> > > I rebooted the machine, and still got the same problem. I
> then
> > > further
> > > remembered about adding a line to lilo.conf for a machine
> that
> > > has two
> > > Ethernet cards. So, I added this line to lilo.conf:
> > >
> > > append="ether=10,0xec00,eth0 ether=15,0xdc00,eth1"
> > >
> > > This time when I rebooted, both cards initialized. Ok, I
was
> > > getting
> > > closer. I ran an ifconfig when the machine first booted
up,
> > and
> > > say both
> > > Ethernet cards listed. I went off to check the
configuration
> > of
> > > some
> > > other stuff, and came back a few minutes later. When I ran
> > > ifconfig
> > > again, eth1 was no longer listed, and I seemed to have
> problems
> > > getting
> > > the interface to come back up again.
> > >
> > > Well, stumped at this point, I read the Ethernet-HOWTO. It
> > > mentioned
> > > about compiling the driver as part of the kernel, so I
> > recompiled
> > > the
> > > kernel, and specified that the 3c90x driver be compiled
with
> > the
> > > kernel,
> > > and not be a module. I also made sure to remove the alias
> eth?
> > > entries
> > > from conf.modules.
> > >
> > > A subsequent boot revealed that both cards came up just
fine.
> > I
> > > ran an
> > > ifconfig, and both were listed there with no problems. I
> > worked
> > > on my
> > > machine this morning for about 30 minutes before going to
> work,
> > > and when I
> > > checked, both interfaces still showed in ifconfig. I
thought
> I
> > > had this
> > > problem solved.
> > >
> > > When I got to work, I did another ifconfig. In the
listing,
> > eth1
> > > is not
> > > listed as active. I'm stumped at this point. Can anyone
> tell
> > me
> > > what
> > > might be going on here? I originally had two DaynaPORT PCI
> > cards
> > > in the
> > > machine with the DEC Tulip chipset, and they just worked
> after
> > > the
> > > install. Maybe I got lucky, as I never had to do any of
this
> > > before. I
> > > would really appreciate any help or ideas people have on
> this.
> > >
> > > Thanks.
> > >
> > > - Mike
> > >
> > > P.S.
> > >
> > > Did I do something incorrect here by changing what the
> > installer
> > > detected
> > > my card as? Can both my Ethernet cards use the 3c59x
setting
> > > without any
> > > performance loss on the cards?
> > >
> > >
> > >
> > > --
> > > To unsubscribe: mail [EMAIL PROTECTED] with
> > > "unsubscribe"
> > > as the Subject.
> > >
> > >
> > > --
> > > To unsubscribe: mail [EMAIL PROTECTED] with
> > "unsubscribe"
> > > as the Subject.
> > >
> >
> >
> > --
> > To unsubscribe: mail [EMAIL PROTECTED] with
> > "unsubscribe"
> > as the Subject.
> >
> >
> > --
> > To unsubscribe: mail [EMAIL PROTECTED] with
> "unsubscribe"
> > as the Subject.
> >
>
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsu
> bscribe"
> as the Subject.
>
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe"
> as the Subject.
>
--
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe"
as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
