Re: How does one get into ddb on adb?
Jaime A Fournier <[email protected]> Wed, 4 Oct 2006 20:42:41 -0500 (CDT)
| Newsgroups | gmane.os.netbsd.ports.next68k |
|---|---|
| Message-ID | <[email protected]> |
So harddrives are supported? I guess I could look at getting a drive for it. For some reason I have been netbooting, I guess because it's easier. Still running 1.6.2. here till I can find a way around this. It appears to just read the kernel and stop. 4602 38.493842 24.153.xxx.xxx -> 24.153.xxx.xxx NFS V2 READ Call, FH:0x95ea1e28 Offset:2327500 Count:843 TotalCount:0 4603 38.493865 24.153.xxx.xxx -> 24.153.xxx.xxx NFS V2 READ Reply (Call In 4602) - No further contacts or queries... Will pull src from 1.6.2+ and move forward till I can find the offending code change. -Ober On Wed, 4 Oct 2006, Dustin Smous wrote: > Date: Wed, 04 Oct 2006 21:04:18 -0400 > From: Dustin Smous <[email protected]> > To: Jaime A Fournier <[email protected]> > Cc: [email protected] > Subject: Re: How does one get into ddb on adb? > > I started having the same problem... > > It started the day the stock hd failed, and was removed... > > We can't be the only two with this problem... > > On Wed, 2006-10-04 at 19:54 -0500, Jaime A Fournier wrote: >> I am trying to determine why since 2.0 the kernel hangs at >> nfs_boot: trying DHCP/BOOTP. >> >> my dhcp entry for it is >> host next { >> hardware ethernet 00:00:0f:00:e4:31; # Adjust to your >> MAC add >> ress >> fixed-address 24.153.xxx.xxx; # Adjust >> always-reply-rfc1048 false; >> filename "/next"; # XXX Do NOT set! >> option root-path "/stuff/next162"; >> server-name="24.153.xxx.xxx"; >> option broadcast-address 24.153.xxx.255; >> option domain-name "linbsd.org"; >> option domain-name-servers dns.linbsd.org; >> option subnet-mask 255.255.255.0; >> next-server 24.153.xxx.xxx; >> } >> And the /etc/bootptab entry is >> next.linbsd.org:\ >> :ht=ether:\ >> :sm=255.255.255.0:\ >> :lg=24.153.xxx.xxx:\ >> :ip=24.153.xxx.xxx:\ >> :hn:\ >> :bf=next:\ >> :bs=auto:\ >> :rp=/stuff/next/:\ >> :vm=auto:\ >> :tc=.test: >> >> 1.6.2 kernels work fine, but anything newer fails at the above mentioned >> prompt. I wanted to get into ddb> to see if I could find out where it's >> at. >> >> Thanks in advance. >> >> -Ober >> >