Tested on Linaro 11.05 Alpha-2 headless with hwpack from 2011-02-01,
console correctly appears on the screen with a login prompt. Garbled
text on the serial console but thats another bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is definitely a different bug than the one that was originally
reported, then. I'm marking the Linaro task as resolved, so we don't
confuse the issue given that the original bug indicated an upstart race
condition that still hasn't been addressed. Tom, please open a new bug
report against Li
>From the pictured state in #32 using the 12-16 headless if on a fresh
boot, you Ctrl-Alt-F1 it does bring up tty1 on the beagle C4. You won't
see tty1 (or any of the other ttys) until you do the ctrl-alt-Fx magic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Here's a picture : http://yfrog.com/fyfnnj
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/652221
Title:
Headless on beagle, beagle XM, does not boot into tty
--
ubuntu-bugs mailing list
ubuntu-bugs
Tom,
What exactly do you see on tty1 at the end of boot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/652221
Title:
Headless on beagle, beagle XM, does not boot into tty
--
ubuntu-bugs mailing l
status openvt
openvt start/running, process 408
r...@localhost:~# status tty1
tty1 stop/waiting
r...@localhost:~# status tty2
tty2 start/running, process 360
r...@localhost:~# status tty3
tty3 start/running, process 362
r...@localhost:~# status tty4
tty4 start/running, process 354
if I flip over
Still fails on natty headless, 12-06 snapshot on Beagle Rev C4, using
omap3 hwpack dated 12-06 as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/652221
Title:
Headless on beagle, beagle XM, doe
Still fails on natty headless dated 12-01 on beagle Rev C4 using omap3
hwpack again dated 1201
--
Headless on beagle, beagle XM, does not boot into tty
https://bugs.launchpad.net/bugs/652221
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can someone confirm whether this is still present on the natty images we
are building now?
Please see:
http://snapshots.linaro.org/11.05-daily
--
Headless on beagle, beagle XM, does not boot into tty
https://bugs.launchpad.net/bugs/652221
You received this bug notification because you are a mem
On Wed, Nov 10, 2010 at 04:30:11AM -, Tom Gall wrote:
> r...@localhost:~# status openvt
> openvt start/running, process 365
Well, that's what we want to see. Can you get a screenshot (or
transcription) of VT1 in this case?
--
Steve Langasek Give me a lever long enough and
r...@localhost:~# status openvt
openvt start/running, process 365
r...@localhost:~# status tty1
tty1 stop/waiting
r...@localhost:~# status tty2
tty2 start/running, process 325
r...@localhost:~# status tty3
tty3 start/running, process 326
r...@localhost:~# status tty4
tty4 start/running, process 3
On Tue, Nov 09, 2010 at 03:49:23AM -, Tom Gall wrote:
> With the Nov 08 build #2, there continues to be no cons on the tty on my
> Rev C4 beagle.
Sounds like we might be chasing a couple of different bugs here, then.
Please show the output of 'status tty1' and 'status openvt' on this system.
On my beagle XM, there is a cons on the tty as well as the serial as
you'd expect. BUT and I guess I should raise this as a different bug,
the cursor is one line down from where it should be (and where test
shows up when typed) further the cursor is not solid but stripped where
solid white row of p
With the Nov 08 build #2, there continues to be no cons on the tty on my
Rev C4 beagle. Serial cons continues to be fine.
--
Headless on beagle, beagle XM, does not boot into tty
https://bugs.launchpad.net/bugs/652221
You received this bug notification because you are a member of Ubuntu
Bugs, whi
On Mon, Nov 08, 2010 at 01:24:34PM -, Alexander Sack wrote:
> didnt we have "on started tty1" initially anyway? ++ on changing this to
> "started" for release
No, it was 'start on starting' initially, and this *did* work for me - I
don't know when it broke or why.
The reason to prefer 'start
didnt we have "on started tty1" initially anyway? ++ on changing this to
"started" for release
--
Headless on beagle, beagle XM, does not boot into tty
https://bugs.launchpad.net/bugs/652221
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Fri, Oct 22, 2010 at 01:21:01PM -, Dave Martin wrote:
> Re the upstart problems, it seems bizarre to start getty in tty1 and
> then kill it and run something else. I expect that upstart jobs of like
> the below weren't really part of the original thinking...
> start on started x
> exec sto
Confirmed this still happens on RC candidate image from 20101101
# status tty1
tty1 stop/starting
# status openvt
openvt start/pre-start, process 475
Also, I noticed that if I try to manually run '/bin/openvt -e -c 1 --
/bin/auto-root-login', I get the following output on the tty1 console:
ioctl
(Also, please excuse the illiteracy of the previous two posts ...)
--
Headless on beagle, beagle XM, does not boot into tty
https://bugs.launchpad.net/bugs/652221
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
Interesting to note that kbd/src/deallocvt.c contains this:
} else if (num == 1) {
fprintf(stderr,
_("%s: VT 1 is the console and cannot be deallocated\n"),
progname);
exit(1);
}
This is decided in userspace without asking the kernel, suggesting tha
> openvt: vt 1 is in use; command aborted
> use `openvt -f' to force.
The weird thing about this is that getty does no check on VT_GETSTATE,
so it will happily let run multiple gettys on the same tty.
... os openvt looks a bit overzealous. tty1 only counts as "used"
because it is assigne
Opening a task on upstart for this bug; I have no explanation for why
the 'stop tty1' is hanging, so that definitely looks like an upstart bug
that should be looked at. If this is really so unreliable, we can
certainly work around it in Linaro for release ('start on started tty1'
is one option).
22 matches
Mail list logo
