ok, now we're getting somewhere.
dyne:bolic loads the tulip driver for a Davicom NIC.
I've found that the tulip driver does not work well at all.
you should try loading the dmfe driver instead.
do the following
ifconfig eth0 down
rmmod tulip
modprobe dmfe
wait a few minutes (cargo cult, I know, but trust me)
ifconfig eth0 192.168.0.4 netmask 255.255.255.0 up
trying pinging
if it doesn't work, do
ifconfig eth0 down
rmmod dmfe
modprobe dmfe
ifconfig eth0 192.168.0.4 netmask 255.255.255.0 up
trying pinging again
the second time the dmfe driver loads, it generally works. I don't
know why it needs to be done twice, but try it anyhow.
I have had problems with the tulip driver under different distros.
Let me know how it goes.
On 12/5/06, Kristofer Dale <barefoot@???> wrote:
>
> (from Richard Hamel-Smith, 02 Dec 06)
>
> >Now, is the Ethernet card working? Does 'dmesg|grep -i eth' give ANY
> >ERRORS at all?
> >For instance, is the IRQ used by something else as all?
>
> >Does 'lspci' should the card as recognised?
>
> Here's the output:
>
> [d:b] ~ #lspci
> 17:13
> 00:00.0 Host bridge: ALi Corporation M1541 (rev 04)
> 00:01.0 PCI bridge: ALi Corporation M1541 PCI to AGP Controller (rev 04)
> 00:02.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
> 00:03.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU]
> 00:07.0 ISA bridge: ALi Corporation M1533/M1535 PCI to ISA Bridge [Aladdin
> IV/V/V+] (rev c3)
> 00:09.0 Ethernet controller: Davicom Semiconductor, Inc. 21x4x DEC-Tulip
> compatible 10/100 Ethernet (rev 31)
> 00:0a.0 Multimedia audio controller: Aureal Semiconductor AU8810 Vortex
> Digital Audio Processor (rev 02)
> 00:0b.0 Multimedia video controller: Zoran Corporation ZR36057PQC Video
> cutting chipset (rev 02)
> 00:0f.0 IDE interface: ALi Corporation M5229 IDE (rev c1)
> 01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 86C326
> 5598/6326 (rev 0b)
> [d:b] ~ #lspci
> 17:30
> 00:00.0 Host bridge: ALi Corporation M1541 (rev 04)
> 00:01.0 PCI bridge: ALi Corporation M1541 PCI to AGP Controller (rev 04)
> 00:02.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
> 00:03.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU]
> 00:07.0 ISA bridge: ALi Corporation M1533/M1535 PCI to ISA Bridge [Aladdin
> IV/V/V+] (rev c3)
> 00:09.0 Ethernet controller: Davicom Semiconductor, Inc. 21x4x DEC-Tulip
> compatible 10/100 Ethernet (rev 31)
> 00:0a.0 Multimedia audio controller: Aureal Semiconductor AU8810 Vortex
> Digital Audio Processor (rev 02)
> 00:0b.0 Multimedia video controller: Zoran Corporation ZR36057PQC Video
> cutting chipset (rev 02)
> 00:0f.0 IDE interface: ALi Corporation M5229 IDE (rev c1)
> 01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 86C326
> 5598/6326 (rev 0b)
> [d:b] ~ #dmesg|grep -i eth
> 17:40
> eth0: Davicom DM9102/DM9102A rev 49 at 0001b800, 00:80:AD:78:F6:87, IRQ 3.
> eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
> [d:b] ~ #lspci|grep -i eth
> 17:40
> 00:09.0 Ethernet controller: Davicom Semiconductor, Inc. 21x4x DEC-Tulip
> compatible 10/100 Ethernet (rev 31)
> [d:b] ~ #
> 17:43
>
>
> If this was a hardware issue, I think it would cause the same problem with
> v1.4.1, but it doesn't. I'm not changing a thing in either computer except
> the version of dyne, v.1.4.1 works fine, none of the v.2x series. Since
> it's a problem with both computers, I'm now wondering if there is something
> about the gateway that is causing the problem. Does anyone know if there is
> something different in the way v.2.x handles the LAN compared to v.1.4.1?
>
> .
> . _o Kristofer Dale,
> . _ \<,_ ragged individualist,
> . ( )/ ( ) statistic at large...
> .
>
> p.s. Learn and live, http://www.vitaletherapeutics.org
> _______________________________________________
> dynebolic mailing list
> dynebolic@???
> http://mailinglists.dyne.org/mailman/listinfo/dynebolic
>