[Clfs-support] Cannot login on serial port (embedded ARM, busybox)

[Lance Jump]

I started from a brand new Ubuntu 10.04LTS installation and have gotten to
the same point.  I am beginning to suspect that it has something to do with
my linux configuration since that is the one part that is not covered in
detail so I would be easy for me to mess up.  Can you send me the config
file from your working Beagle Board build?  Or any build based on the latest
ARM CLFS?

I found what I believe are two additional bugs, but I don't either are the
cause of the problem.  The first is in section 16.2 where has the
/dev/console and null nodes made in ${CLFS}.  I think they should be made in
${CLFS}-final at that point.

The other is in the clfs-embedded-bootscripts Makfile.  The line:

   install -d -m ${DIRMODE} ${EXTDIR}/rc.d/{init.d,start,stop}

appears to actually make a directory named "{init.d,start,stop}" instead of
three directories.  It is strange because I ran that exact same thing under
Linux-live chroot and it worked.  But in Ubuntu it failed.  I split into
three install statements.

On Thu, Oct 13, 2011 at 4:47 PM, Lance Jump <lancej29 at gmail.com> wrote:

>
>
> On Tue, Oct 11, 2011 at 7:55 AM, Andrew Bradford <bradfa at gmail.com> wrote:
>
>> On Mon, Oct 10, 2011 at 3:14 PM, Lance Jump <lancej29 at gmail.com> wrote:
>> > Yes, the symlink is there.  As a test, I changed the script name in the
>> > inittab file and and I get an error:
>> >
>> > VFS: Mounted root (nfs filesystem) on device 0:13.
>> > Freeing init memory: 156K
>> > init started: BusyBox v1.18.4 (2011-10-07 23:48:57 GMT)
>> > can't run '/etc/rc.d/startupx': No such file or directory
>> >
>> > This suggests two things.  First, it is finding the correct file
>> (without
>> > the change) since I get no error and, second, that something is properly
>> > processing inittab. What I can't tell is whether the message is coming
>> from
>> > the shell processor or something else (Busybox init?).
>>
>> Interesting...
>> As a somewhat quick sanity check, if you build BusyBox 1.17.3 and
>> apply the proper patches from that generation of the embedded book, do
>> you get the same operation?
>>
>> Apply both the fixes and config patches at the beginning of the
>> BusyBox build, section 7.4.  As I have output from a successful boot
>> with this version, that might be a good sanity check.
>> https://gist.github.com/874183
>>
>> Downloads you'll need:
>> http://busybox.net/downloads/busybox-1.17.3.tar.bz2
>>
>> http://svn.cross-lfs.org/svn/repos/patches/busybox/busybox-1.17.3-fixes-1.patch
>>
>> http://svn.cross-lfs.org/svn/repos/patches/busybox/busybox-1.17.3-config-1.patch
>>
>> If you grab a copy of the git repo for the embedded book, you can
>> checkout commit 1b109e6eae092a7a1fe4a5580683e93507fa7e02 to get the
>> old instructions at the last point where BusyBox was version 1.17.3.
>>
>
> I tried busybox 1.17.3 and got the same results.  I am running out of
> ideas.  I was thinking about doing this directly in Ubuntu (10.4LTS) rather
> than in the Linux Live chroot.  But I don't see how that should matter since
> everything builds without complaint.  Can you suggest anything else to try?
>
>
>>
>> -Andrew
>> _______________________________________________
>> Clfs-support mailing list
>> Clfs-support at lists.cross-lfs.org
>> http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clfs.org/pipermail/clfs-support-clfs.org/attachments/20111014/cc548b5a/attachment-0001.htm>