Date: Thu, 24 Sep 2015 14:28:45 +0300 From: Daniel Braniss <danny@cs.huji.ac.il> To: Randy Westlund <rwestlun@gmail.com> Cc: freebsd-arm@freebsd.org Subject: Re: NFS Root with Raspberry Pi (nfs_diskless: no interface) Message-ID: <CFAAFAE2-F0B2-431B-93C6-61D66464B7FD@cs.huji.ac.il> In-Reply-To: <20150923174445.GE43653@gmail.com> References: <20150922052522.GA62140@gmail.com> <00C49FEB-E8EF-4469-85E2-0F901215CD11@cs.huji.ac.il> <20150923050414.GB43653@gmail.com> <91AAC64E-4C38-47AA-8910-48F7654A7524@cs.huji.ac.il> <20150923174445.GE43653@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 23 Sep 2015, at 20:44, Randy Westlund <rwestlun@gmail.com> wrote:
>=20
> On Wed, Sep 23, 2015 at 11:54:43AM +0300, Daniel Braniss wrote:
>> ok, thought it was too easy. Can you send me more info so that i can =
reproduce it here?
>> specially the ubldr stuff?
>>=20
>> ah! try if_smsc_load=3DYES
>>=20
>> danny
>=20
> Okay, that's definitely the correct driver. Looks like the pi uses a
> SMSC LAN9514 ethernet module. But I see the same output regardless of
> whether that's in loader.conf or not. The kernel seems to be finding
> smsc0 just fine. It just hasn't created the interface yet.
i=E2=80=99ll try this here tomorrow, but in the meantime some ideas:
did you compile the kernel with option BOOTP_NFSV3?
>=20
>> ugen0.1: <DWCOTG> at usbus0
>> uhub0: <DWCOTG OTG Root HUB, class 9/0, rev 2.00/1.00, addr 1> on =
usbus0
>> mmcsd0: 4GB <SDHC SU04G 8.0 SN 001FC92A MFG 12/2011 by 3 SD> at mmc0 =
41.6MHz/4bit/65535-block
>> nfs_diskless: no interface
>> Root mount waiting for: usbus0
>> uhub0: 1 port with 1 removable, self powered
>> ugen0.2: <vendor 0x0424> at usbus0
>> uhub1: <vendor 0x0424 product 0x9512, class 9/0, rev 2.00/2.00, addr =
2> on usbus0
>> uhub1: MTT enabled
>> Root mount waiting for: usbus0
>> uhub1: 3 ports with 2 removable, self powered
>> Root mount waiting for: usbus0
>> ugen0.3: <vendor 0x0424> at usbus0
>> smsc0: <vendor 0x0424 product 0xec00, rev 2.00/2.00, addr 3> on =
usbus0
>> Trying to mount root from nfs:192.168.1.254:/usr/raspi_root [rw]...
>> nfs_diskless: no interface
>> Mounting from nfs:192.168.1.254:/usr/raspi_root failed with error -1.
>>=20
>> Loader variables:
>> vfs.root.mountfrom=3Dnfs:192.168.1.254:/usr/raspi_root
>> vfs.root.mountfrom.options=3Drw
>=20
> Here's the fstab that the pi is using:
>=20
>> cat /usr/raspi_root/etc/fstab
>> 192.168.1.254:/usr/raspi_root / nfs rw 0 0
>=20
> Here's dhcp.conf on my router:
>=20
>> $ cat /etc/dhcpd.conf
>> authoritative;
>> option domain-name-servers 192.168.1.1;
>>=20
>> subnet 192.168.1.0 netmask 255.255.255.0 {
>> option routers 192.168.1.1;
>> range 192.168.1.2 192.168.1.150;
>> next-server 192.168.1.254;
>> option root-path "/usr/raspi_root";
>> }
>=20
> Here's what ubldr sees before it loads the kernel over NFS:
>=20
>> loader> show
>> LINES=3D24
>> autoboot_delay=3D10
>> boot.netif.gateway=3D0.0.0.0
>> boot.netif.hwaddr=3Db8:27:eb:28:a4:f8
>> boot.netif.ip=3D192.168.1.33
>> boot.netif.netmask=3D255.255.255.0
>> =
boot.nfsroot.nfshandle=3DX298684cadeaf78ee0a000400000000006ed9380000000000=
00000000X
>> boot.nfsroot.nfshandlelen=3D28
>> boot.nfsroot.path=3D/usr/raspi_root
>> boot.nfsroot.server=3D192.168.1.254
>> bootfile=3Dkernel
>> console=3Duboot
>> currdev=3Dnet0:
>> interpret=3DOK
>> kernel=3Dkernel
>> kernelname=3D/boot/kernel/kernel
>> loaddev=3Dnet0:
>> loader_conf_files=3D/boot/loader.conf /boot/loader.conf.local
>> module_path=3D/boot/kernel;/boot/kernel;/boot/modules;/boot/dtb
>> prompt=3Dloader>
>> twiddle_divisor=3D1
>=20
> The files I'm using are all taken from one of these two images (same
> result with both):
>=20
> FreeBSD-11.0-CURRENT-arm-armv6-RPI-B-20150826-r287169.img
> FreeBSD-10.2-STABLE-arm-armv6-RPI-B-20150917-r287929.img
>=20
> Let me know if you need any other info, and thanks for spending time =
on
> this.
>=20
> Randy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CFAAFAE2-F0B2-431B-93C6-61D66464B7FD>