Date: Wed, 23 May 2007 11:56:50 -0700 From: Sean Bruno <sbruno@miralink.com> To: freebsd-embedded@FreeBSD.org Subject: Re: [nanobsd] Calculation of new flash image size Message-ID: <46548E72.4040400@miralink.com> In-Reply-To: <4654588F.8090002@miralink.com> References: <465233FF.8060100@miralink.com> <20070522.094257.74690293.imp@bsdimp.com> <4653DCC9.5060108@bulinfo.net> <20070523.091856.-1253046332.imp@bsdimp.com> <4654588F.8090002@miralink.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sean Bruno wrote: > M. Warner Losh wrote: >> In message: <4653DCC9.5060108@bulinfo.net> >> Krassimir Slavchev <krassi@bulinfo.net> writes: >> : What about diskinfo? >> : I always use output from diskinfo -v without any problems. >> > diskinfo reports the same information when I ran it, but thanks! >> diskinfo and fdisk -I use the same data, that is often wrong with SCSI >> adapters. If it works for you, then you are lucky. The problem is >> the geometry that's reported by the adapters. >> >> Warner >> > As far as I know, my disk is not SCSI. I am using an IDE flash disk > and the drive is coming up as 'ad0' > > If I am calculating the disk size correctly, what else could be > causing nanobsd to hang at the boot loader startup? > > Sean > _______________________________________________ > freebsd-embedded@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-embedded > To unsubscribe, send any mail to > "freebsd-embedded-unsubscribe@freebsd.org" Ok...I'm a total idiot. I have the customize_cmd cust_comconsole in my nano configuration. This causes it to only have a console on a the serial port, DUH! /me waves his hands in a jedi fashion and says "This isn't the bug you are looking for." Sean
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46548E72.4040400>