Hi,

Tom, your onboard ethernet (mc0) is not broken. I saw exactly the same behavior with my pmac 7600 and NetBSD 2.0 with the MACE ethernet (mc) and similar behavior with an Asante 10/100 PCI card (tlp). Patrick Cronin has already logged a PR for the Asante ethernet. 

I didn't worry too much about the MACE ethernet, as I have a 3Com 3c905-TX 10/100 Ethernet PCI card (ex) which is working well. When I get around to it I will investigate the others further...

You could confirm that the time and date is set correctly as outlined here; http://www.netbsd.org/Ports/macppc/faq.html#ethernet-bad-date
but this was not the problem in my case.

So, I can back you up. The MACE  Ethernet (mc) is not working in NetBSD 2.0

If you are able, see if you can find 3Com or other PCI Ethernet card to try.


On Wednesday, January 12, 2005, at 12:57PM, Tomas D <u0giene@yahoo.com> wrote:

> Hi All,
>I'm having a bit of a problem using onboard ethernet
>card on my mac ppc 9500. I've got 1 ethernet which can
>bee seen using ifcnfig and another one is token ring
>card which is not configured and I'm not gona be using
>anyway so let's not talk about it (;
>
>uogiene# ifconfig mc0
>mc0:
>flags=8822<BROADCAST,NOTRAILERS,SIMPLEX,MULTICAST> mtu
>1500
>        address: 00:a0:40:34:ec:16
>        media: Ethernet manual
>uogiene# ifconfig mc0 192.168.0.1 netmask
>255.255.255.0
>uogiene# ifconfig mc0
>mc0:
>flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST>
>mtu 1500
>        address: 00:a0:40:34:ec:16
>        media: Ethernet manual
>        inet 192.168.0.1 netmask 0xffffff00 broadcast
>192.168.0.255
>        inet6 fe80::2a0:40ff:fe34:ec16%mc0 prefixlen
>64 scopeid 0x1
>uogiene# dmesg | grep mc0
>mc0 at obio0 offset 0x11000: irq 14,2,3: address
>00:a0:40:34:ec:16
>uogiene# dmesg | grep obio0
>obio0 at pci0 dev 16 function 0: addr 0xf3000000
>esp0 at obio0 offset 0x10000 irq 12: NCR53C94, 25MHz,
>SCSI ID 7
>mc0 at obio0 offset 0x11000: irq 14,2,3: address
>00:a0:40:34:ec:16
>zsc0 at obio0 offset 0x13000: irq 15,16
>awacs at obio0 offset 0x14000 not configured
>swim3 at obio0 offset 0x15000 not configured
>adb0 at obio0 offset 0x16000 irq 18: 1 targets
>mesh0 at obio0 offset 0x18000 irq 13: 50MHz, SCSI ID 7
>nvram0 at obio0 offset 0x1d000
>
>so far everything seems fine but when I try to ping
>192.168.0.1 from other machine that's what I get:
>
>Request timed out.
>Request timed out.
>Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
>Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
>Request timed out.
>Request timed out.
>Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
>Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
>Request timed out.
>Request timed out.
>Request timed out.
>Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
>Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
>Request timed out.
>Request timed out.
>Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
>Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
>
>Ping statistics for 192.168.0.1:
>    Packets: Sent = 173, Received = 87, Lost = 86 (49%
>loss),
>Approximate round trip times in milli-seconds:
>    Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
>any ideas what can be causing that? I've got suspicion
>that onboard network card in my mac is faulty
>
>this is my /var/log/messages after I've done
>#ifconfig mc0 10.1.1.1 
>Jan  8 19:43:28 uogiene /netbsd: mc0: collision error
>Jan  8 19:43:28 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:43:28 uogiene /netbsd: mc0: collision error
>Jan  8 19:43:28 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:43:29 uogiene /netbsd: mc0: collision error
>Jan  8 19:43:29 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:43:33 uogiene /netbsd: mc0: collision error
>Jan  8 19:43:33 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:43:38 uogiene /netbsd: mc0: collision error
>Jan  8 19:43:38 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:41:23 uogiene syslogd: restart
>Jan  8 19:41:23 uogiene /netbsd: vrele: bad ref count:
>tag 1 type VDIR, usecount 0, writecount 8388608,
>refcount 1,
>Jan  8 19:41:23 uogiene /netbsd:        tag VT_UFS,
>ino 8444986, on dev 4, 0 flags 0x0, effnlink 2, nlink
>2
>Jan  8 19:41:23 uogiene /netbsd:        mode 040555,
>owner 0, group 0, size 512 not locked
>Jan  8 19:41:23 uogiene /netbsd: panic: vrele: ref cnt
>vp 0x2ec89e8
>Jan  8 19:41:23 uogiene /netbsd: syncing disks...
>panic: pmap_pvo_to_pte: pvo 0x3570700: has nomatching
>pte 0xd51d0 in pmap_pteg_table but valid in pvo
>
>then I've entered into kernel debugging mode which I
>have no idea what to do there so I've just typed
>restart 2 times.
>after assigning ip address again I've got these error
>messages
>
>Jan  8 19:42:00 uogiene /netbsd: mc0: collision error
>Jan  8 19:42:00 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:42:00 uogiene /netbsd: mc0: collision error
>Jan  8 19:42:00 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:42:01 uogiene /netbsd: mc0: collision error
>Jan  8 19:42:01 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:42:01 uogiene /netbsd: mc0: collision error
>Jan  8 19:42:01 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:42:04 uogiene /netbsd: mc0: collision error
>Jan  8 19:42:04 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:49:34 uogiene /netbsd: mc0: collision error
>Jan  8 19:49:34 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:49:35 uogiene /netbsd: mc0: collision error
>Jan  8 19:49:35 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:49:36 uogiene /netbsd: mc0: collision error
>Jan  8 19:49:36 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:49:37 uogiene /netbsd: mc0: collision error
>Jan  8 19:49:37 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:49:38 uogiene /netbsd: mc0: collision error
>Jan  8 19:49:38 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:49:39 uogiene /netbsd: mc0: collision error
>Jan  8 19:49:39 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:49:40 uogiene /netbsd: mc0: collision error
>Jan  8 19:49:40 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:49:41 uogiene /netbsd: mc0: collision error
>Jan  8 19:49:41 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:49:42 uogiene /netbsd: mc0: collision error
>Jan  8 19:49:42 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:49:43 uogiene /netbsd: mc0: collision error
>Jan  8 19:49:43 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:49:44 uogiene /netbsd: mc0: collision error
>Jan  8 19:49:44 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:49:45 uogiene /netbsd: mc0: collision error
>Jan  8 19:49:45 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:49:46 uogiene /netbsd: mc0: collision error
>Jan  8 19:49:46 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:49:47 uogiene /netbsd: mc0: collision error
>Jan  8 19:49:47 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:49:48 uogiene /netbsd: mc0: collision error
>Jan  8 19:49:48 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:49:49 uogiene /netbsd: mc0: collision error
>Jan  8 19:49:49 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:49:50 uogiene /netbsd: mc0: collision error
>Jan  8 19:49:50 uogiene /netbsd: mc0: lost carrier
>Jan  8 19:49:51 uogiene /netbsd: mc0: collision error
>Jan  8 19:49:51 uogiene /netbsd: mc0: lost carrier
>Jan  8 20:17:11 uogiene syslogd: Exiting on signal 15
>
>after I did
>#ifconfig mc0 stop
>#ifconfig mc0 start
>
>things seem to be fixed itself I don't get any error
>messages regarding to mc0 however I'm still having
>huge packet loss
>Ping statistics for 192.168.0.1:
>    Packets: Sent = 173, Received = 87, Lost = 86 (49%
>loss),
>Approximate round trip times in milli-seconds:
>    Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
>
>
>
>here's my full dmesg output (it might help)
[... snip ... snip ]
>
>		
>__________________________________ 
>Do you Yahoo!? 
>The all-new My Yahoo! - What will yours do?
>http://my.yahoo.com 
>
>


--

http://homepage.mac.com/andresk/