Hello, your boot.conf should look like this:
set tty com0 stty com0 38400 set timeout 5 Last time I booted wrap via pxe was 3.9, but this should work. Regards Hagen Volpers -----Urspr|ngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von mgb Gesendet: Donnerstag, 7. Juni 2007 12:51 An: misc@openbsd.org Betreff: WRAP stalling at kernel entry point via pxeboot/tftp List, I am attempting to get pxeboot working on a WRAP board with openbsd 4.1 generic however the loading of either kernel, bsd or bsd.rd, is stalling. I've search around the archives and have taken the steps mentioned here: http://marc.info/?l=openbsd-misc&m=117978591113386&w=2 I have updated the BIOS on the wrap board with a PXE.BIN downloaded from rom-o-matic.net which uses etherboot 5.4.3 and the NIC type natsemi:dp83815. below is the output from the wrap board: PC Engines WRAP.2B/2C v1.11 640 KB Base Memory 130048 KB Extended Memory 01F0 - no drive found ! ROM segment 0xe000 length 0x8000 reloc 0x00000000 Etherboot 5.4.3 (GPL) http://etherboot.org Drivers: NATSEMI Images: NBI ELF Multiboot a.out PXE Exports: PXE Protocols: DHCP TFTP Relocating _text from: [0008bb80,0009fd90) to [07eebdf0,07f00000) Boot from (N)etwork (D)isk or (Q)uit? N Probing pci nic... [dp83815] natsemi_probe: MAC addr 00:0D:B9:04:47:F8 at ioaddr 0X1000 natsemi_probe: Vendor:0X100B Device:0X0020 dp83815: Transceiver default autoneg. enabled, advertise 100 full duplex. dp83815: Transceiver status 7869 advertising 05E1 dp83815: Setting full-duplex based on negotiated link capability. Searching for server (DHCP)..... Me: 192.168.1.200, DHCP: 192.168.1.1, TFTP: 192.168.1.1, Gateway 192.168.1.1 Loading 192.168.1.1:pxeboot ...(PXE)....................................done probing: pc0 com0 pci pxe![2.1] mem[640K 125M a20=on] disk: net: mac 00:0d:b9:04:47:f8, ip 192.168.1.200, server 192.168.1.1 >> OpenBSD/i386 PXEBOOT 1.11 boot> bsd1.rd booting tftp:bsd.rd: 4679892+742564 [52+169536+154918]=0x57b288 dp83815: Setting full-duplex based on negotiated link capability. entry point at 0x200120 the loading stalls at this point, tcpdump shows the following: 11:48:27.321421 IP 192.168.1.1.32831 > 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..........?.Y......&0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mf i_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devic es.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup. qsphy_ca.shmmaxpgs. 11:48:28.319634 IP 192.168.1.1.32831 > 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..........?.Y......&0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mf i_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devic es.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup. qsphy_ca.shmmaxpgs. 11:48:30.319653 IP 192.168.1.1.32831 > 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..........?.Y......&0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mf i_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devic es.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup. qsphy_ca.shmmaxpgs. 11:48:34.319901 IP 192.168.1.1.32831 > 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..........?.Y......&0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mf i_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devic es.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup. qsphy_ca.shmmaxpgs. 11:48:42.320416 IP 192.168.1.1.32831 > 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..........?.Y......&0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mf i_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devic es.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup. qsphy_ca.shmmaxpgs. 11:48:47.320663 arp who-has 192.168.1.200 tell 192.168.1.1 ..........Ze................ 11:48:48.320728 arp who-has 192.168.1.200 tell 192.168.1.1 ..........Ze................ 11:48:49.320787 arp who-has 192.168.1.200 tell 192.168.1.1 ..........Ze................ 11:48:58.325352 arp who-has 192.168.1.200 tell 192.168.1.1 ..........Ze................ 11:48:59.325417 arp who-has 192.168.1.200 tell 192.168.1.1 ..........Ze................ 11:49:00.325480 arp who-has 192.168.1.200 tell 192.168.1.1 I have used a boot.conf which contains this: set tty pc0 I have tried com0 and the output freezes whilst I type bsd.rd Many thanks for your time
