Date: Fri, 30 Nov 2012 10:31:11 -0700 From: Ian Lepore <freebsd@damnhippie.dyndns.org> To: Mats Mellstrand <mats@exmandato.se> Cc: freebsd-arm@freebsd.org Subject: Re: FreeBSD on Raspberry Pi 512MB (with U-Boot + ubldr) Message-ID: <1354296671.69940.429.camel@revolution.hippie.lan> In-Reply-To: <67266790-55B9-4CAB-992B-A68C73912995@exmandato.se> References: <3988C1622A974F19A9D3888F0334FF10@ad.peach.ne.jp> <EDA5788A-A74B-47A5-88C7-4CAD9B572EE2@exmandato.se> <D0C85770-572C-492D-82A4-7CB19F114F01@bluezbox.com> <C956325DD85D4E1E9739709F94FEEA76@ad.peach.ne.jp> <67266790-55B9-4CAB-992B-A68C73912995@exmandato.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2012-11-30 at 18:22 +0100, Mats Mellstrand wrote: > Hi > > > > On 30 nov 2012, at 17:53, Daisuke Aoyama <aoyama@peach.ne.jp> wrote: > > > Hi, > > > >>> uhub0: <DWCOTG OTG Root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0 > >>> mmcsd0: 14GB <SDHC SD16G 8.0 SN 53686086 MFG 08/2012 by 3 SD> at mmc0 25.0MHz/4bit/65535-block > >>> mmcsd0: Error indicated: 2 Bad CRC > >>> mmcsd0: Error indicated: 2 Bad CRC > >> > >> This issue must be fixed by r243688 and r243689 > > > > It seems fixed. But found another problem. SWAP never used even if I set GPU=384MB. > > Also, around freemem=260MB(GPU=16MB), get the program crashed. > > > > > > I've recreated the image based on build-pi-image.sh + SVN 243703 + my custom settings. > > All settings are the same as previous mail. (FreeBSD source tree is not modified) > > Please try this instead. > > Success! > > I tried ifconfig_ue0="DHCP" in /etc/rc.local, this however don't work: > > This gives : > > /etc/rc.d/dhclient: WARNING: failed to start dhclient > > in the boot message > > But I can start dhclient manually after boot. > I've seen variations of this appear on the lists several times in the past few months, always relating to usb ethernet. Since enumerating the usb bus is asynch it's often still in progress when the rc world starts running. It seems like the right thing would be for rc.d/dhclient to do nothing and then devd should launch dhclient when the ue interface appears. I'm not sure why the devd part isn't working now, unless something about the ue interface is different enough that it isn't trigging the existing devd rules for ethernet interfaces coming and going. At work we've had problems with local rc scripts failing because the uftdi devices they need haven't been enumerated yet. It seems like the rc system needs some way to wait for usb enumeration to complete. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1354296671.69940.429.camel>