I don't think Tim's patches were ever commited. if_mc.c and friends
haven't been changed in 9 months according to cvsweb.

On Sun, 9 Oct 2005, Tomas D wrote:

>  Hi, I'm trying to netboot my macppc 9500/200 via mc0 and having few problems with that... it
> looks like it's all due to mc0 drivers which Tim and others tried to sort out since last year
> (even earlier than that I guess) my opinion things have improved cause now when I ping my macppc
> host I'm getting 2 replys and 2 timeouts and again 2 replys and 2 timeouts...
>
> Open Firmware, 1.0.5
> To continue booting the MacOS type:
> BYE<return>
> To continue booting from the default boot device type:
> BOOT<return>
>  ok
> 0 > boot enet:,ofwboot.xcf
> file: 192.168.100.200,ofwboot.xcf loading XCOFF
> tsize=C860 dsize=28C bsize=25C0 entry=E00000
> SECTIONS:
> .text    00E00000 00E00000 0000C860 000000E0
> .data    00E0D000 00E0D000 0000028C 0000C940
> .bss     00E0D290 00E0D290 000025C0 00000000
> loading .text, done..
> loading .data, done..
> clearing .bss, done..
>
> >> NetBSD/macppc OpenFirmware Boot, Revision 1.10
> >> (riz@faith.netbsd.org, Mon Sep 19 20:25:31 UTC 2005)
> file: 192.168.100.200,ofwboot.xcfnet_open: client addr: 192.168.100.254
> net_open: subnet mask: 255.255.255.0
> net_open: net gateway: 192.168.100.100
> net_open: server addr: 192.168.100.200
> net_open: server path: /var/export/macppc/root
> net_open: file name: ofwboot.xcf
> Using IP address: 192.168.100.254
> root addr=192.168.100.200 path=/var/export/macppc/root
> ]=0x5514b0
>  start=0x100000
> Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005
>
>     The NetBSD Foundation, Inc.  All rights reserved.
>
> Copyright (c) 1982, 1986, 1989, 1991, 1993
>
>     The Regents of the University of California.  All rights reserved.
>
>
> NetBSD 2.1_RC5 (GENERIC) #0: Mon Sep 19 20:54:23 UTC 2005
>
>
> riz@faith.netbsd.org:/home/builds/ab/netbsd-2-1-RC5/macppc/200509182312Z-obj/home/builds/ab/netbsd-2-1-RC5/src/sys/arch/macppc/compile/GENERIC
> total memory = 65536 KB
> avail memory = 56816 KB
> no active packagemainbus0 (root)
> cpu0 at mainbus0: 604ev (Revision 2.4), ID 0 (primary)
> cpu0: HID0 8090c084<EMCP,DOZE,DPM,ICE,DCE,SGE,BHT>
> bandit0 at mainbus0
> pci0 at bandit0 bus 0
> pci0: i/o space, memory space enabled
> pchb0 at pci0 dev 11 function 0
> pchb0: Apple Computer Bandit Host-PCI Bridge (rev. 0x03)
> ofb0 at pci0 dev 14 function 0: ATI Technologies Mach64 GX
> ofb0: 640 x 480, 8bpp
> wsdisplay0 at ofb0 kbdmux 1
> wsmux1: connecting to wsdisplay0
> obio0 at pci0 dev 16 function 0: addr 0xf3000000
> esp0 at obio0 offset 0x10000 irq 12: NCR53C94, 25MHz, SCSI ID 7
> scsibus0 at esp0: 8 targets, 8 luns per target
> mc0 at obio0 offset 0x11000: irq 14,2,3: address 00:a0:40:34:ec:16
> zsc0 at obio0 offset 0x13000: irq 15,16
> zstty0 at zsc0 channel 0 (console)
> zstty1 at zsc0 channel 1
> awacs at obio0 offset 0x14000 not configured
> swim3 at obio0 offset 0x15000 not configured
> adb0 at obio0 offset 0x16000 irq 18: 1 targets
> aed0 at adb0 addr 0: ADB Event device
> akbd0 at adb0 addr 2: extended keyboard (ISO layout)
> wskbd0 at akbd0 mux 1
> wskbd0: connecting to wsdisplay0
> mesh0 at obio0 offset 0x18000 irq 13: 50MHz, SCSI ID 7
> scsibus1 at mesh0: 8 targets, 8 luns per target
> nvram0 at obio0 offset 0x1d000
> bandit1 at mainbus0
> pci1 at bandit1 bus 1
> pci1: i/o space, memory space enabled
> pchb1 at pci1 dev 11 function 0
> pchb1: Apple Computer Bandit Host-PCI Bridge (rev. 0x03)
> vr0 at pci1 dev 14 function 0: VIA VT6105 (Rhine III) 10/100 Ethernet
> vr0: interrupting at irq 28
> vr0: Ethernet address: 00:11:95:80:55:d9
> ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface
> ukphy0: OUI 0x0002c6, model 0x0034, rev. 4
> ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> scsibus0: waiting 2 seconds for devices to settle...
> scsibus1: waiting 2 seconds for devices to settle...
> sd0 at scsibus1 target 0 lun 0: <QUANTUM, FIREBALL SE3.2S, PJ0A> disk fixed
> sd0: drive offline
> cd0 at scsibus1 target 6 lun 0: <TOSHIBA, DVD-ROM SD-M1401, 1007> cdrom removable
> boot device: mc0
> root on mc0
> nfs_boot: trying DHCP/BOOTP
> nfs_boot: DHCP next-server: 192.168.100.200
> nfs_boot: my_name=macppc
> nfs_boot: my_domain=clapton.net
> nfs_boot: my_addr=192.168.100.254
> nfs_boot: my_mask=255.255.255.0
> nfs_boot: gateway=192.168.100.100
> root on 192.168.100.200:/var/export/macppc/root
> root file system type: nfs
>
> and here it stuck I'm trying to do tcpdump from the server (192.168.100.200) but can't see no
> activity from 192.168.100.254 or macppc.clapton.net which is really the same.
> My question is- is it possible to somehow get kernel loaded via mc0 and all the rest via vr0 by
> changing
> boot device: mc0
> root on mc0
> to
> boot device: vr0
> root on vr0
> I'm not sure if that would fix the problem, but I cant really see no other reasons why it
> shouldn't work, cause root path which is sent by dhcpd which is /var/export/macppc/root is right
> and kernel gets loaded aswell. I've checked nfsstat, but couldnt understand much, if somebody had
> similar problem please share your experience and how you've dealt with it.
>
> /var/log/messages from the server (192.168.100.200)
> Oct  9 16:12:01 upgrader dhcpd: BOOTREQUEST from 00:a0:40:34:ec:16 via bce0
> Oct  9 16:12:01 upgrader dhcpd: BOOTREPLY for 192.168.100.254 to macppc.clapton.net
> (00:a0:40:34:ec:16) via bce0
> Oct  9 16:12:01 upgrader tftpd[229]: 192.168.100.254: read request for ofwboot.xcf: success
> Oct  9 16:12:01 upgrader tftpd[231]: 192.168.100.254: read request for ofwboot.xcf: success
> Oct  9 16:12:01 upgrader tftpd[233]: 192.168.100.254: read request for ofwboot.xcf: success
> Oct  9 16:12:01 upgrader dhcpd: DHCPDISCOVER from 00:a0:40:34:ec:16 via bce0
> Oct  9 16:12:01 upgrader dhcpd: DHCPOFFER on 192.168.100.254 to 00:a0:40:34:ec:16 via bce0
> Oct  9 16:12:01 upgrader dhcpd: DHCPREQUEST for 192.168.100.254 (192.168.100.200) from
> 00:a0:40:34:ec:16 via bce0
> Oct  9 16:12:01 upgrader dhcpd: DHCPACK on 192.168.100.254 to 00:a0:40:34:ec:16 via bce0
> Oct  9 16:12:18 upgrader dhcpd: DHCPDISCOVER from 00:a0:40:34:ec:16 via bce0
> Oct  9 16:12:18 upgrader dhcpd: DHCPOFFER on 192.168.100.254 to 00:a0:40:34:ec:16 via bce0
> Oct  9 16:12:18 upgrader dhcpd: DHCPREQUEST for 192.168.100.254 (192.168.100.200) from
> 00:a0:40:34:ec:16 via bce0
> Oct  9 16:12:18 upgrader dhcpd: DHCPACK on 192.168.100.254 to 00:a0:40:34:ec:16 via bce0
> Oct  9 16:12:19 upgrader dhcpd: DHCPREQUEST for 192.168.100.254 (192.168.100.200) from
> 00:a0:40:34:ec:16 via bce0
> Oct  9 16:12:19 upgrader dhcpd: DHCPACK on 192.168.100.254 to 00:a0:40:34:ec:16 via bce0
>
>
> thanks Tomas
>
>
>
>
> __________________________________
> Yahoo! Mail - PC Magazine Editors' Choice 2005
> http://mail.yahoo.com
>
> !DSPAM:43493c1e54931206613928!
>

-- 
The nice thing about Windows is - It does not just crash, it displays a
dialog box and lets you press 'OK' first.
						-- Arno Schaefer