This is during installation when I am trying to configure the network. I
select DHCP and it tries to query the network. The message appears after a
few seconds after the attempt.

I should add that I am an embedded developer (VxWorks) and I am not afraid
of using gdb or any other tools you can throw my way. Just point me to the
info on how to use the tool and what to look for. 


-----Original Message-----
From: village idiot [mailto:village_ldi0t@yahoo.com]
Sent: Wednesday, May 15, 2002 6:50 AM
To: Rose, Brian; 'netbsd-help@netbsd.org'
Subject: Re: Installation help


Brian,

what do you actually type, before the error message
comes up?


--- "Rose, Brian" <Brian.Rose@icn.siemens.com> wrote:
> 
> I have just installed NetBSD 1.5.2 onto a Sony Vaio
> FXA32 notebook computer
> and I cannot get the network interface working.
> 
> Every time I start sysinst and try to configure my
> network adapter, I get a
> "rtk0: watdchdog timeout" error message.
> 
> I checked the supported hardware page and the
> Realtek 8139 card that I have
> is supported. My dmesg output (below) also indicates
> that the card has been
> successfully initialized.
> 
> Any ideas as to how can I resolve this issue?
> 
> 
> ---
> 
> NetBSD 1.5.2 (GENERIC) #3: Sat Aug 18 23:37:05 CEST
> 2001
>    
>
he@hamster.urc.uninett.no:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: AMD K7 (Athlon) (686-class), 900.08 MHz
> total memory = 126 MB
> avail memory = 112 MB
> using 1645 buffers containing 6580 KB of memory
> BIOS32 rev. 0 found at 0xfd6a0
> mainbus0 (root)
> pci0 at mainbus0 bus 0: configuration mode 1
> pci0: i/o space, memory space enabled
> pchb0 at pci0 dev 0 function 0
> pchb0: VIA Technologies product 0x0305 (rev. 0x03)
> ppb0 at pci0 dev 1 function 0: VIA Technologies
> product 0x8305 (rev. 0x00)
> pci1 at ppb0 bus 1
> pci1: i/o space, memory space enabled
> vga1 at pci1 dev 0 function 0: ATI Technologies
> Mach64 LM (rev. 0x64)
> wsdisplay0 at vga1: console (80x25, vt100 emulation)
> pcib0 at pci0 dev 7 function 0
> pcib0: VIA Technologies VT82C686A (Apollo KX133)
> PCI-ISA Bridge (rev. 0x42)
> pciide0 at pci0 dev 7 function 1: VIA Technologies
> VT82C686A (Apollo KX133)
> ATA100 controller
> pciide0: bus-master DMA support present
> pciide0: primary channel configured to compatibility
> mode
> wd0 at pciide0 channel 0 drive 0: <TOSHIBA
> MK4018GAP>
> wd0: drive supports 16-sector pio transfers, lba
> addressing
> wd0: 38154 MB, 16383 cyl, 16 head, 63 sec, 512
> bytes/sect x 78140160 sectors
> wd0: 32-bit data port
> wd0: drive supports PIO mode 4, DMA mode 2,
> Ultra-DMA mode 5
> pciide0: primary channel interrupting at irq 14
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
> (using DMA data
> transfers)
> pciide0: secondary channel configured to
> compatibility mode
> atapibus0 at pciide0 channel 1
> cd0 at atapibus0 drive 0: <QSI DVD-ROM SDR-081, ,
> ESC9> type 5 cdrom
> removable
> cd0: 32-bit data port
> cd0: drive supports PIO mode 4, DMA mode 2,
> Ultra-DMA mode 2
> pciide0: secondary channel interrupting at irq 15
> cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
> (using DMA data
> transfers)
> uhci0 at pci0 dev 7 function 2: VIA Technologies
> VT83C572 USB Controller
> (rev. 0x1a)
> uhci0: interrupting at irq 9
> usb0 at uhci0: USB revision 1.0
> uhub0 at usb0
> uhub0: VIA Technologie UHCI root hub, class 9/0, rev
> 1.00/1.00, addr 1
> uhub0: 2 ports with 2 removable, self powered
> uhci1 at pci0 dev 7 function 3: VIA Technologies
> VT83C572 USB Controller
> (rev. 0x1a)
> uhci1: interrupting at irq 9
> usb1 at uhci1: USB revision 1.0
> uhub1 at usb1
> uhub1: VIA Technologie UHCI root hub, class 9/0, rev
> 1.00/1.00, addr 1
> uhub1: 2 ports with 2 removable, self powered
> VIA Technologies VT82C686A SMBus Controller (ISA
> bridge, revision 0x40) at
> pci0 dev 7 function 4 not configured
> auvia0 at pci0 dev 7 function 5: VIA VT82C686A AC'97
> Audio (rev 0x50)
> auvia0: interrupting at irq 5
> auvia0: ADS72 codec; headphone, Analog Devices Phat
> Stereo
> audio0 at auvia0: full duplex, mmap, independent
> VIA Technologies VT82C686A MC-97 Modem Controller
> (miscellaneous
> communications, revision 0x30) at pci0 dev 7
> function 6 not configured
> Texas Instruments PCI1420 PCI-CardBus Bridge
> (CardBus bridge) at pci0 dev 10
> function 0 not configured
> Texas Instruments PCI1420 PCI-CardBus Bridge
> (CardBus bridge) at pci0 dev 10
> function 1 not configured
> Texas Instruments TSB12LV26 OHCI IEEE 1394 Host
> Controller (Firewire serial
> bus, interface 0x10) at pci0 dev 14 function 0 not
> configured
> rtk0 at pci0 dev 16 function 0: RealTek 8139
> 10/100BaseTX
> rtk0: interrupting at irq 10
> rtk0: Ethernet address 08:00:46:2f:5d:0b
> ukphy0 at rtk0 phy 7: Generic IEEE 802.3u media
> interface
> ukphy0: OUI 0x000000, model 0x0000, rev. 0
> ukphy0: 10baseT, 10baseT-FDX, 100baseTX,
> 100baseTX-FDX, auto
> isa0 at pcib0
> com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a,
> working fifo
> pckbc0 at isa0 port 0x60-0x64
> pckbd0 at pckbc0 (kbd slot)
> pckbc0: using irq 1 for kbd slot
> wskbd0 at pckbd0: console keyboard, using wsdisplay0
> pms0 at pckbc0 (aux slot)
> pckbc0: using irq 12 for aux slot
> wsmouse0 at pms0 mux 0
> lpt0 at isa0 port 0x378-0x37b irq 7
> pcppi0 at isa0 port 0x61
> midi0 at pcppi0: PC speaker
> sysbeep0 at pcppi0
> isapnp0 at isa0 port 0x279: ISA Plug 'n Play device
> support
> npx0 at isa0 port 0xf0-0xff: using exception 16
> fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
> fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
> pcic0 at isa0 port 0x3e0-0x3e1 iomem 0xd0000-0xdffff
> pcic0: controller 0 (Intel 82365SL Revision 1) has
> sockets A and B
> pcic0: controller 1 (Intel 82365SL Revision 1) has
> no sockets
> pcmcia0 at pcic0 controller 0 socket 0
> pcmcia1 at pcic0 controller 0 socket 1
> isapnp0: no ISA Plug 'n Play devices found
> biomask eb4d netmask ef4d ttymask ffcf
> pcic0: controller 0 detecting irqs with mask
> 0xdeb8:..3..11
> pcic0: using irq 3 for socket events
> boot device: wd0
> root on wd0a dumps on wd0b
> root file system type: ffs
> wsdisplay0: screen 1 added (80x25, vt100 emulation)
> wsdisplay0: screen 2 added (80x25, vt100 emulation)
> wsdisplay0: screen 3 added (80x25, vt100 emulation)
> wsdisplay0: screen 4 added (80x25, vt100 emulation)
> wsmux1: connecting to wsdisplay0
> 
> 
> 
> 
> 
> Brian Rose 
> Brian dot Rose at icn dot siemens dot com 
> 407-942-6934 
> To understand recursion, one must first understand
recursion


__________________________________________________
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com