[Buildroot] Can't Login to New System

[Buildroot] Can't Login to New System

[Andrew Wiley]

I've been trying to get a linux system running on a Qwerk, which is
basically a nicely packaged Cirrus Labs EDB9302. I can use buildroot
to get a root filesystem, and use the cross compiler in buildroot's
staging directory to build a working kernel, and the system will boot,
but when I go to login, I just get another login prompt, as you can
see below:
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 120K



Welcome to the Erik's uClibc development environment.
uclibc login: root



Welcome to the Erik's uClibc development environment.
uclibc login: default



Welcome to the Erik's uClibc development environment.
uclibc login:

As you can see, I didn't change the login message or anything. All
I've done to the root filesystem is moved /dev from an out of date
(but working) root to buildroot's root. As far as I can tell, this has
caused no problems. The lines in /etc/inittab that start the getty you
see here are:

# Put a getty on the serial port
ttyAM0::respawn:/sbin/getty -L ttyAM0 57600 vt100

ttyAM0 is a serial port.
I haven't changed /etc/passwd and /etc/shadow from the defaults that
buildroot makes. The defaults are to create a user called default and
give that user and the root user no password, right?
I'm either misinterpreting how I should log in, or something is wrong
with my system.
I'm not sure if I should post my buildroot config. I'm really
desperate to resolve this (I'm so close!), and any help would be
greatly appreciated.

Andrew Wiley

[Buildroot] Can't Login to New System

[Jeremy Kerr]

Hi Andrew,

> ttyAM0 is a serial port.

You'll need to add ttyAM0 to /etc/securetty in order to log in as root 
on this console.

Cheers,


Jeremy

[Buildroot] Can't Login to New System

[Peter Korsgaard]

>>>>> "Andrew" == Andrew Wiley <debio264@gmail.com> writes:

Hi,

 Andrew> As you can see, I didn't change the login message or
 Andrew> anything. All I've done to the root filesystem is moved /dev
 Andrew> from an out of date (but working) root to buildroot's
 Andrew> root. As far as I can tell, this has caused no problems. The
 Andrew> lines in /etc/inittab that start the getty you see here are:

 Andrew> # Put a getty on the serial port
 Andrew> ttyAM0::respawn:/sbin/getty -L ttyAM0 57600 vt100

 Andrew> ttyAM0 is a serial port.

You need to add ttyAMx to /etc/securetty. If you tell me the
major/minor numbers of /dev/ttyAMx, then I'll add device nodes +
securetty entries for them to the default rootfs.

-- 
Bye, Peter Korsgaard

[Buildroot] Can't Login to New System

[Andrew Wiley]

On Wed, Dec 31, 2008 at 1:26 AM, Peter Korsgaard <jacmet@uclibc.org> wrote:
>>>>>> "Andrew" == Andrew Wiley <debio264@gmail.com> writes:
>
> Hi,
>
>  Andrew> As you can see, I didn't change the login message or
>  Andrew> anything. All I've done to the root filesystem is moved /dev
>  Andrew> from an out of date (but working) root to buildroot's
>  Andrew> root. As far as I can tell, this has caused no problems. The
>  Andrew> lines in /etc/inittab that start the getty you see here are:
>
>  Andrew> # Put a getty on the serial port
>  Andrew> ttyAM0::respawn:/sbin/getty -L ttyAM0 57600 vt100
>
>  Andrew> ttyAM0 is a serial port.
>
> You need to add ttyAMx to /etc/securetty. If you tell me the
> major/minor numbers of /dev/ttyAMx, then I'll add device nodes +
> securetty entries for them to the default rootfs.
>
> --
> Bye, Peter Korsgaard
>

There's a good chance you already have these somewhere, but when I
moved the old /dev filesystem over, I had little to no idea what I was
doing (I'm used to having good old uDev there to work magic for me).
Anyway, hopefully this is all the info you need:
[arew264 at CaitSith dev]$ stat ttyAM*
 File: `ttyAM0'
 Size: 0               Blocks: 0          IO Block: 1024   character
special file
Device: 702h/1794d      Inode: 113         Links: 1     Device type: cc,10
Access: (0640/crw-r-----)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2007-09-28 14:15:05.000000000 -0500
Modify: 2007-09-28 14:15:05.000000000 -0500
Change: 2008-12-30 16:10:00.000000000 -0600
 File: `ttyAM1'
 Size: 0               Blocks: 0          IO Block: 1024   character
special file
Device: 702h/1794d      Inode: 114         Links: 1     Device type: cc,11
Access: (0640/crw-r-----)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2007-09-28 14:15:05.000000000 -0500
Modify: 2007-09-28 14:15:05.000000000 -0500
Change: 2008-12-30 16:10:00.000000000 -0600
[arew264 at CaitSith dev]$

These are the two serial ports on the EDB9302. There are actually
three, but the third one isn't actually connected to a jack, and thus
can't be used.

Anyway, my /etc/securetty looks like this:
[arew264 at CaitSith etc]$ cat securetty
tty1
tty2
tty3
tty4
tty5
tty6
tty7
tty8
ttyS0
ttyS1
ttyS2
ttyS3
ttyAMA0
ttyAMA1
ttyAMA2
ttyAMA3
ttyUL0
ttyUL1
ttyUL2
ttyUL3
ttyPSC0
ttyPSC1
ttyPSC2
ttyPSC3
ttyAM0
ttyAM1

[arew264 at CaitSith etc]$

The issue is still there.

Thanks for the help so far,
Andrew Wiley

[Buildroot] Can't Login to New System

[Andrew Wiley]

Is there any way to tell what's going on when I try to login? Could
Busybox be segfaulting? Could there be some sort of conflict between
the kernel and the console (I launch the kernel with the argument
"console=ttyAM0")?

Andrew Wiley

[Buildroot] Can't Login to New System

[Peter Korsgaard]

>>>>> "Andrew" == Andrew Wiley <debio264@gmail.com> writes:

 Andrew> Is there any way to tell what's going on when I try to login?
 Andrew> Could Busybox be segfaulting? Could there be some sort of
 Andrew> conflict between the kernel and the console (I launch the
 Andrew> kernel with the argument "console=ttyAM0")?

Sure, add strace to your build, boot the kernel with init=/bin/sh and
see what strace -f login gives you. If that fails, add printf calls to
login (busybox) till you figure out what's going wrong.

-- 
Bye, Peter Korsgaard

[Buildroot] Can't Login to New System

[Andrew Wiley]

On Wed, Jan 7, 2009 at 2:23 AM, Bernhard Weirich
<bernhard.weirich@riedel.net> wrote:
> Hi Andrew,
>
> just a wild guess, but I had the same problem and the issue was that neither
> uclib nor kernel was built with floating point support.
> so maybe check if you have floats...
>
> Regards Bernhard
>

This may be a stupid question, but is that setting somewhere in the
buildroot toolchain config, in the kernel config, or somewhere else
entirely? I've looked for it, but I can't seem to find it.
I'm pretty sure the Cirrus Labs cross toolchain uses software floating
point, because in the guide for setting it up, you have to run this
command:
$ sudo mkdir -p /opt/buildroot/toolchain_build_arm_nofpu/ccache-2.4/cache
I thought that was pretty funny when I noticed it. I may be
misinterpretting that, because I'm pretty sure the EDB9302 does have a
FPU, but it may be something wierd about the Qwerk, or I may just be
an idiot. That instruction is found at
http://terk.svn.sourceforge.net/viewvc/terk/embed/trunk/share/docs/QwerkDevelopmentGuide.html#SettingUpTheARMCompiler

Andrew Wiley