Date: Thu, 8 Aug 2002 00:52:17 -0400 (EDT) From: Chris Jackman <cjack@klatsch.org> To: freebsd-sparc@freebsd.org Subject: Re: Help booting Ultra2 from cdrom Message-ID: <20020806085041.R20908-100000@whiskey.klatsch.org> In-Reply-To: <20020731130010.N4442@locore.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
<snip> > > but I still get a mountroot> prompt. > > Sounds like you don't have the nfsroot kernel; it should do a bootp > request, you can't specify it at the mountroot prompt. There should > be a kernel.nfsroot in the development directly on the ftp site. You were correct. I had not changed the kernel. I have changed it. Now when I boot, it gets the loader, gets the kernel, and then displays: <snip boot messages> nexus0: <SUNW,ffb>, type display (no driver attached) Sending DHCP Discover packet from interface hme0 (08:00:20:9a:76:f4) hme0: device timeout DHCP/BOOTP timeout for server 255.255.255.255 hme0: device timeout DHCP/BOOTP timeout for server 255.255.255.255 These repeat. I tcpdump'd from the OpenBSD box that I'm trying to do the netboot from, and I see this when these messages come out: <snip getting kernel> 08:42:59.992763 sunrise.1018 > uranium.603: udp 76 08:43:15.993812 sunrise.2287 > uranium.tftp: 19 RRQ "/etc/fstab" 08:43:16.006403 uranium.1582 > sunrise.2287: udp 44 08:43:21.010232 uranium.1582 > sunrise.2287: udp 44 08:43:21.669937 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0xffff0001 secs:3 flags:0x8000 [|bootp] [ttl 1] 08:43:21.671029 uranium.bootps > 255.255.255.255.bootpc: xid:0xffff0001 secs:3 flags:0x8000 Y:sunrise S:uranium.nexthop.net file ""[|bootp] [tos 0x10] 08:43:24.770408 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0xffff0001 secs:6 flags:0x8000 [|bootp] [ttl 1] 08:43:24.771523 uranium.bootps > 255.255.255.255.bootpc: xid:0xffff0001 secs:6 flags:0x8000 Y:sunrise S:uranium.nexthop.net [|bootp] [tos 0x10] 08:43:26.020237 uranium.1582 > sunrise.2287: udp 44 After this the Sun rarps again, RRQ's the loader again, and then the kernel again, all the while displaying the hme0: device timeout message followed by DHCP/BOOTP timeout for server 255.255.255.255. Does this look like the OpenBSD box not replying correctly to the sun's requests ? Do the hme0: device timeout messages on the sun box indicate something wrong with the hme0 interface/driver/i dunno ? Thanks again. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-sparc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020806085041.R20908-100000>