Date: Fri, 28 Sep 2012 11:44:54 -0600 From: Ian Lepore <freebsd@damnhippie.dyndns.org> To: Hans Petter Selasky <hselasky@c2i.net> Cc: freebsd-arm@freebsd.org Subject: Re: Unable to boot Pi successfully with ethernet interface configured Message-ID: <1348854294.1113.57.camel@revolution.hippie.lan> In-Reply-To: <201209281933.37291.hselasky@c2i.net> References: <506327AD.8030103@gmail.com> <1348852114.1113.43.camel@revolution.hippie.lan> <201209281925.13209.hselasky@c2i.net> <201209281933.37291.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2012-09-28 at 19:33 +0200, Hans Petter Selasky wrote: > On Friday 28 September 2012 19:25:13 Hans Petter Selasky wrote: > > On Friday 28 September 2012 19:08:34 Ian Lepore wrote: > > > On Fri, 2012-09-28 at 17:57 +0100, Sevan / Venture37 wrote: > > > > Oh cool, will report back once I've had a chance to play tonight. > > > > Btw, I'm using a USB > TTL adapter connected to the GPIO pins which > > > > gives me output from the kernel on booting but I'd like to be able to > > > > login, looking at /etc/ttys ttyv0 is switched on by default, I've > > > > modified it to std.115200 & I see the login prompt now but the > > > > console > > > > locks up & wont take any input. > > > > > > It might be worth trying 3wire.115200 rather than std.115200, in case > > > flow control is why it seems to be locked up. > > > > > > -- Ian > > > > Hi Ian, > > > > # cat /etc/ttys > > ttyU0 "/usr/libexec/getty 3wire.115200" vt100 on secure > > ttyu0 "/usr/libexec/getty 3wire.115200" vt100 on secure > > ttyv0 "/usr/libexec/getty Pc" cons25 on secure > > ttyv1 "/usr/libexec/getty Pc" cons25 on secure > > ttyv2 "/usr/libexec/getty Pc" cons25 on secure > > ttyv3 "/usr/libexec/getty Pc" cons25 on secure > > ttyv4 "/usr/libexec/getty Pc" cons25 on secure > > ttyv5 "/usr/libexec/getty Pc" cons25 on secure > > ttyv6 "/usr/libexec/getty Pc" cons25 on secure > > ttyv7 "/usr/libexec/getty Pc" cons25 on secure > > > > Only USB TTY port works. > > > > If I do something like: > > > > echo "test" > ttyu0 > > > > Nothing is printed on the serial port. Don't know why. > > > > ps auxw > > > > root 554 0.0 1.2 10076 1564 u0 Ss+ 5:23PM 0:00.02 /usr/libexec/getty > > 3wire.115200 ttyu0 > > > > --HPS > > FYI > > Top of backtrace for getty looks like this: > > sleepq_wait_sig() at sleepq_wait_sig+12 > scp=0xc0222dd4 rlv=0xc018fa28 (_cv_wait_sig+472) > rsp=0xc7972c6c rfp=0xc7972c98 > r5=0x00000000 r4=0x00000000 > _cv_wait_sig() at _cv_wait_sig+12 > scp=0xc018f85c rlv=0xc0237ff4 (tty_wait+32) > rsp=0xc7972c9c rfp=0xc7972cb0 > r10=0x00000000 r9=0xc101d900 > r8=0x00000001 r7=0x00000000 r6=0xc7972db4 r5=0xc0f83600 > r4=0x0000000b > tty_wait() at tty_wait+12 > scp=0xc0237fe0 rlv=0xc02406f4 (ttydisc_read+432) > rsp=0xc7972cb4 rfp=0xc7972ce4 > r5=0x00000001 r4=0xc0f83600 > ttydisc_read() at ttydisc_read+12 > scp=0xc0240550 rlv=0xc02390f8 (tty_alloc+408) > rsp=0xc7972ce8 rfp=0xc7972d08 > r10=0x00000000 r8=0x00000000 > r7=0x00000000 r6=0xc7972db4 r5=0xc0f83600 r4=0x00000000 > > Don't have time to debug right now. Offhand, I'd say that looks right -- it's parked in the tty layer waiting for a character to arrive from the low-level hardware driver. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1348854294.1113.57.camel>