It means it cannot locate the ethernet address in an ISV
	or DEC format SROM. The old 'de' driver might handle it,
	but I don't believe that works particularly well on non
	i386 platforms (hence Jason's rewritten tlp driver).

	Jason has said he plans to finish up support in tlp for
	the oddball hardware, I'm sure he'd be interested in patches
	if you wanted to work out how to get the ethernet address
	on your 'cards'.

	You might be able to get the machine up as a temporary
	measure by hacking sys/dev/pci/if_tlp_pci.c:749 and replacing
	the 'goto cant_cope' with something ugly like
	    memcpy(enaddr, "123456", ETHER_ADDR_LEN);
	Just please don't tell anyone I suggested that :)

	Another option is to stick a pci network card in the pci
	slot and run with that for now.

-- 
		David/absolute		-- www.netbsd.org: No hype required --


On Fri, 27 Jul 2001, Shaun Jurrens wrote:

> Hi guys,
>
> I have been working at getting a RaQ2 box off the linux wagon and over to
> NetBSD and got a good deal help from Hubert already, but things seem to hang
> now that I've got the kernel to netboot.  I'm netbooting from my fbsd
> workstation and can see that rpc calls are going out and it seems like the
> nfs mount works (it does, after all, get the kernel), but after booting,
> it tells me the following:
>
> Built Tue May 25 15:58:41 PDT 1999
>
>  1.LCD Test................................PASS
>  2.Controller Test.........................PASS
>  5.Bank 0:.................................64M
>  6.Bank 1:.................................64M
>  7.Bank 2:.................................64M
>  8.Bank 3:.................................64M
>  9.Serial Test.............................PASS
> 10.PCI Expansion Slot....................**EMPTY**
> 12.IDE Test................................PASS
> 13.Ethernet Test...........................PASS
> 16.RTC Test................................PASS
>
> Cobalt: bfd /netbsd.gz root=/dev/nfs nfsroot=/pub/cobalt
> Decompressing done
> Executing bootloader kernel...
> Decompressing -- done.
> Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001
>     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 1.5.1 (GENERIC) #3: Wed Jul  4 19:58:41 CEST 2001
>     root@raq:/usr/1-5-release/src/sys/arch/cobalt/compile/GENERIC
> 256 MB memory, 234 MB free, 13208 KB in 3302 buffers
> mainbus0 (root)
> com0 at mainbus0 addr 0x1c800000 level 3: st16650a, working fifo
> com0: console
> cpu0 at mainbus0: QED RM5200 CPU (0x28a0) Rev. 10.0 with built-in FPU Rev. 10.0
> cpu0: L1 cache: 32KB/32B instruction, 32KB/32B data, two way set associative
> cpu0: No L2 cache
> gt0 at mainbus0 addr 0x14000000
> pci0 at gt0
> pci0: i/o space, memory space enabled, rd/line, wr/inv ok
> pchb0 at pci0 dev 0 function 0: Galileo GT-64111 System Controller, rev 1
> tlp0 at pci0 dev 7 function 0: DECchip 21143 Ethernet, pass 4.1
> tlp0: sorry, unable to handle your board
> ^^^^^^^^^^^
> Symbios Logic 53c860 (SCSI mass storage, revision 0x02) at pci0 dev 8 function d
> pcib0 at pci0 dev 9 function 0
> pcib0: VIA Technologies VT82C586 (Apollo VP) PCI-ISA Bridge, rev 37
> pciide0 at pci0 dev 9 function 1: VIA Technologies VT82C586 (Apollo VP) ATA33 cr
> pciide0: bus-master DMA support present
> pciide0: primary channel configured to compatibility mode
> wd0 at pciide0 channel 0 drive 0: <QUANTUM FIREBALL CR4.3A>
> wd0: drive supports 16-sector pio transfers, lba addressing
> wd0: 4110 MB, 14848 cyl, 9 head, 63 sec, 512 bytes/sect x 8418816 sectors
> wd0: 32-bit data port
> wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4
> pciide0: primary channel interrupting at irq 14
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 (using DMA data transfers)
> pciide0: secondary channel configured to compatibility mode
> pciide0: disabling secondary channel (no drives)
> VIA Technologies VT83C572 USB Controller (USB serial bus, revision 0x02) at pcid
> tlp1 at pci0 dev 12 function 0: DECchip 21143 Ethernet, pass 4.1
> tlp1: sorry, unable to handle your board
> ^^^^^^^^^^^
> boot device: <unknown>
> root device:
>
> 	   ^^^^^^^
>
> 	Here is there where it all kinda goes to hell.  You can see that the
> 	tlp drivers are having problems for some reason and it can't mount
> 	root after the kernel is booted.  Guess I could use some suggestions.
>
> 	Thanks in advance for any help you can offer.
>