Date: Sun, 28 Oct 2012 12:05:37 -0700 From: Tim Kientzle <tim@kientzle.com> To: Takeshi Taguchi <taguchi@ff.iij4u.or.jp> Cc: freebsd-arm@freebsd.org Subject: Re: Towards an ARM system-building script Message-ID: <25C276C7-EC77-4EF1-A4B0-DE4606E1133D@kientzle.com> In-Reply-To: <508D3C83.6020101@ff.iij4u.or.jp> References: <508D3C83.6020101@ff.iij4u.or.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 28, 2012, at 7:09 AM, Takeshi Taguchi wrote: > My Pandaboard ES (Rev.B1) said: > panic: bootpc_init: Could not find interface specified by > BOOTP_WIRED_TO: ue0 > > so I'd commented out following lines: > #options BOOTP_NFSROOT > #options BOOTP_COMPAT > #options BOOTP > #options BOOTP_NFSV3 > #options BOOTP_WIRED_TO=ue0 I just commented these out of the PANDABOARD config in -CURRENT. So this should no longer be needed. > login prompt was displaied. That's good news! Is the system usable overall? (You can login as root, run basic commands, etc?) > But the ethernet isn't working at all. Do any other USB devices work? Someone else mentioned that it worked if they asked U-Boot to initialize the USB hardware via "usb start" at the U-Boot prompt. This suggests that the FreeBSD USB driver is missing something in its initialization code. > following is a dmesg. what should i do? I don't see ue0 listed. Is the ue driver in the kernel? If not, try adding it. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?25C276C7-EC77-4EF1-A4B0-DE4606E1133D>