Re: Make errors while building snapgear-4.0.0.7

On Tue, Aug 26, 2014 at 8:44 PM, Greg Ungerer <[email protected]> wrote:

> Hi,
>
>>
>>
>> I'm assuming this was the last step,
>>
>
> That is the last step. Easiest fix is to just create a /tftpboot
> directory that is world read/write. Doesn't really matter whether
> you actually have tftp server enabled or not.
>
>
Yeah, I was able to figure that out and with the help of the SG manual
(amazing, those!) found out about the "recovery" process of holding down
ERASE and booting.  With Wireshark, I was able to see it pick up an IP from
tftpd's DHCP service and successfully download my image.bin.


>
> Maybe, maybe not. What are the front LEDs doing?
> If the heartbeat (HB) is flashing then it was probably successful.
>
> A serial port console is not enabled by default, so you won't get
> anything on the serial port without doing extra steps.
>
>



>
>  Now that I have that out of my system, my next step is to install tftpd
>> and (I'm assuming) do a TFTP based install?  Don't see that part on the
>> snapgear.org <http://snapgear.org> documentation on archive.org <
>> http://archive.org>, but maybe I'm missing something.
>>
>
> SnapGear has been shutdown so I don't know they have on the web anymore.
> But the tftp network load is pretty simple. To see what is going on hook
> up the serial port at 115200,8,n,1. Then hold in the ERASE button and
> plug in the power. It will come up with a simple boot loader prompt.
> After a few seconds it will timeout and try a network load - doing a
> dhcp address lookup and then trying a tftp load of a system image
> (that is the image.bin file that your compile generated).
>

Well, getting a kernel panic; don't think it can find the flash device...

XScale DSP coprocessor detected.
VFS: Cannot open root device "ram0" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available
partitions:
1f00        128 mtdblock0 (driver?)
1f01        512 mtdblock1 (driver?)
1f02       7424 mtdblock2 (driver?)
1f03       8192 mtdblock3 (driver?)
1f04        128 mtdblock4 (driver?)
1f05        128 mtdblock5 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)

There was a patch that I never applied as I wasn't sure what the
architecture was for these, but seeing this in the boot message ("CPU:
XScale-IXP42x Family [690541f2] revision 2 (ARMv5TE), cr=000039ff"), it
jogged my memory of this, from the archive.org's snapgear documentation
page:

"Also available is a patch package that can be used to build the Intel
IXP4xx Access Library code as part of the SnapGear distribution. This patch
set contains support for the Intel CSR-1.4 with DSR-2.6.2 combination, and
the Intel CSR-2.4 library (on both 2.4 and 2.6 linux kernels)."

There's also this, but it appears as those RedBoot has already been
configured:
https://gitorious.org/linux-nios2/uclinux-dist/source/5316285bb1b0a07bd2a2a562ec9397af22dc465d:vendors/SecureComputing/SG560/README



>
> I would suggest hard setting a command line in your kernel config so that
> you have console=ttyS0,115200 set.
>

I think I saw an old post on how to do that; if I get past the kernel
panic, this will be the first thing I do.


>
> Regards
> Greg
>
>
>
>  On Mon, Aug 25, 2014 at 9:40 AM, GravyFace <[email protected] <mailto:
>> [email protected]>> wrote:
>>
>>     Thanks, I'll give that a go now.
>>
>>
>>     On Mon, Aug 25, 2014 at 2:24 AM, Greg Ungerer <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>         Hi,
>>
>>
>>         On 24/08/14 03:26, gravyface wrote:
>>
>>             Hi all,
>>
>>             First time attempting to compile really anything in Linux
>> (why not try this? <g>), and hitting a wall with a seemingly pam-auth
>> related error.
>>
>>             Build Environment:
>>
>>             - Ubuntu Server 12.04.5 LTS with apt versions of binutils,
>> build-essentials, gcc, gdb, curses (libncurses5-dev libncursesw5-dev).  I
>> downloaded the arm-linux-tools-20061213.tar.__gz <
>> https://web.archive.org/web/__20100715203220/http://ftp.__
>> snapgear.org/pub/snapgear/__tools/arm-linux/arm-linux-__
>> tools-20061213.tar.gz <https://web.archive.org/web/
>> 20100715203220/http://ftp.snapgear.org/pub/snapgear/
>> tools/arm-linux/arm-linux-tools-20061213.tar.gz>> from Web Archive's
>> copy, but have no idea how to use it.
>>
>>
>>
>>             I can get whatever versions of packages needed; just let me
>> know.
>>
>>             Target:
>>
>>             - I have more SG560s than I know what to do with after
>> dismantling a large site-to-site client network; I'm interested in building
>> simple network testing appliances (ping/arp-scan/nc/ssh) I can use when
>> configuring various networking devices, so I think the default libraries
>> and utilities should be more than adequate in the base image.
>>
>>             What I've done:
>>
>>             - Extracted http://ftp.snapgear.org/pub/__
>> snapgear/src/snapgear-4.0.7.__tar.bz2 <http://ftp.snapgear.org/pub/
>> snapgear/src/snapgear-4.0.7.tar.bz2> to my home directory in a
>> sub-folder called uclinux (full path is /home/gravyface/uclinux/__snapgear-4.0.7).
>> From that directory, ran "make SecureComputing/SG560_default" which ran for
>> 15 minutes or so, happily compiling, until it exited with Error 2, and not
>> a whole lot more:
>>
>>
>>
>>         By default the build is parallel across the number of CPUs you
>> have.
>>         It may be that the actuall error was way back in the compile
>> output.
>>
>>         Try running:
>>
>>            make NON_SMP_BUILD=1 SecureComputing/SG560_default
>>
>>         It will be a lot slower, only running on 1 CPU. But it will much
>>         more likely stop at the failure point.
>>
>>         Regards
>>         Greg
>>
>>
>>
>>             ucfront-gcc arm-linux-gcc -mbig-endian -mcpu=xscale
>> -mtune=xscale -msoft-float -DHOST_NAME_MAX=255 -shared  .libs/pam_xauth.o
>> -Wl,--rpath -Wl,/home/gravyface/uclinux/__snapgear-4.0.7/lib/libpam/__build/libpam/.libs
>> -L/home/gravyface/uclinux/__snapgear-4.0.7/lib/libpam/__build/libpam
>> /home/gravyface/uclinux/__snapgear-4.0.7/lib/libpam/__build/libpam/.libs/libpam.so
>> -mbig-endian -mcpu=xscale -mtune=xscale -msoft-float
>> -Wl,--version-script=../../../__modules/pam_xauth/../modules.__map
>> -Wl,-S -Wl,-soname -Wl,pam_xauth.so -o .libs/pam_xauth.so
>>             creating pam_xauth.la <http://pam_xauth.la> <
>> http://pam_xauth.la/>
>>             (cd .libs && rm -f pam_xauth.la <http://pam_xauth.la> <
>> http://pam_xauth.la/> && ln -s ../pam_xauth.la <http://pam_xauth.la> <
>> http://pam_xauth.la/> pam_xauth.la <http://pam_xauth.la> <
>> http://pam_xauth.la/>)
>>
>>             make[8]: Leaving directory `/home/gravyface/uclinux/__
>> snapgear-4.0.7/lib/libpam/__build/modules/pam_xauth'
>>             make[8]: Entering directory `/home/gravyface/uclinux/__
>> snapgear-4.0.7/lib/libpam/__build/modules'
>>
>>             make[8]: Nothing to be done for `all-am'.
>>             make[8]: Leaving directory `/home/gravyface/uclinux/__
>> snapgear-4.0.7/lib/libpam/__build/modules'
>>             make[7]: Leaving directory `/home/gravyface/uclinux/__
>> snapgear-4.0.7/lib/libpam/__build/modules'
>>             Making all in po
>>             make[7]: Entering directory `/home/gravyface/uclinux/__
>> snapgear-4.0.7/lib/libpam/__build/po'
>>
>>             make[7]: Nothing to be done for `all'.
>>             make[7]: Leaving directory `/home/gravyface/uclinux/__
>> snapgear-4.0.7/lib/libpam/__build/po'
>>             Making all in conf
>>             make[7]: Entering directory `/home/gravyface/uclinux/__
>> snapgear-4.0.7/lib/libpam/__build/conf'
>>             make[8]: Entering directory `/home/gravyface/uclinux/__
>> snapgear-4.0.7/lib/libpam/__build/conf'
>>
>>             make[8]: Nothing to be done for `all-am'.
>>             make[8]: Leaving directory `/home/gravyface/uclinux/__
>> snapgear-4.0.7/lib/libpam/__build/conf'
>>             make[7]: Leaving directory `/home/gravyface/uclinux/__
>> snapgear-4.0.7/lib/libpam/__build/conf'
>>             make[7]: Entering directory `/home/gravyface/uclinux/__
>> snapgear-4.0.7/lib/libpam/__build'
>>
>>             make[7]: Nothing to be done for `all-am'.
>>             make[7]: Leaving directory `/home/gravyface/uclinux/__
>> snapgear-4.0.7/lib/libpam/__build'
>>             make[6]: Leaving directory `/home/gravyface/uclinux/__
>> snapgear-4.0.7/lib/libpam/__build'
>>             make[5]: Leaving directory `/home/gravyface/uclinux/__
>> snapgear-4.0.7/lib/libpam/__build'
>>             make[4]: Leaving directory `/home/gravyface/uclinux/__
>> snapgear-4.0.7/lib/libpam'
>>             make[3]: Leaving directory `/home/gravyface/uclinux/__
>> snapgear-4.0.7/lib'
>>
>>             make[2]: *** [all] Error 2
>>             make[2]: Leaving directory `/home/gravyface/uclinux/__
>> snapgear-4.0.7/lib'
>>
>>             make[1]: *** [subdirs] Error 1
>>             make[1]: Leaving directory `/home/gravyface/uclinux/__
>> snapgear-4.0.7'
>>             make: *** [SecureComputing/SG560___default] Error 2
>>
>>
>>
>>             Looks to be pam-related, but with no error, I'm kind of at a
>> loss here.
>>
>>             Thanks in advance!
>>
>>
>>             _________________________________________________
>>             uClinux-dev mailing list
>>             [email protected] <mailto:[email protected]>
>>             http://mailman.uclinux.org/__mailman/listinfo/uclinux-dev <
>> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev>
>>             This message was resent by [email protected] <mailto:
>> [email protected]>
>>             To unsubscribe see:
>>             http://mailman.uclinux.org/__mailman/options/uclinux-dev <
>> http://mailman.uclinux.org/mailman/options/uclinux-dev>
>>
>>
>>         _________________________________________________
>>         uClinux-dev mailing list
>>         [email protected] <mailto:[email protected]>
>>         http://mailman.uclinux.org/__mailman/listinfo/uclinux-dev <
>> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev>
>>         This message was resent by [email protected] <mailto:
>> [email protected]>
>>         To unsubscribe see:
>>         http://mailman.uclinux.org/__mailman/options/uclinux-dev <
>> http://mailman.uclinux.org/mailman/options/uclinux-dev>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> uClinux-dev mailing list
>> [email protected]
>> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
>> This message was resent by [email protected]
>> To unsubscribe see:
>> http://mailman.uclinux.org/mailman/options/uclinux-dev
>>
>>
> _______________________________________________
> uClinux-dev mailing list
> [email protected]
> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
> This message was resent by [email protected]
> To unsubscribe see:
> http://mailman.uclinux.org/mailman/options/uclinux-dev
>

_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev