On 08/10/2014 04:55 AM, Gordan Bobic wrote:
On 08/10/2014 05:19 AM, Robert Moskowitz wrote:

On 08/08/2014 05:57 PM, Gordan Bobic wrote:
On 08/08/2014 10:52 PM, Robert Moskowitz wrote:
On 08/08/2014 03:49 PM, Robert Moskowitz wrote:
On 08/07/2014 09:47 PM, Karanbir Singh wrote:
On 08/08/2014 02:16 AM, Robert Moskowitz wrote:
On 08/07/2014 08:27 PM, Karanbir Singh wrote:
Hi guys,

as a show of hands, can we get a list of :
1) boards we have at the moment
Cubieboard 2
I've got a bunch of Cubietrucks,
Interesting.  Do you have Redsleeve working on any of them?  I have
built a boot SDcard for my Cubieboard2 based on a F19 kernel and stuff
and am up to being able to login on the serial console.

But I do not get any login on the video monitor.  Mouse moves and
typing
is echoed.  But no login prompt.
This has been solved with <alt-F2>.  Now why that is needed...
Because some bright-spark at RH decided it would be a great idea to
clobber the boot progress log on the console. I know the plymouth boot
animation does that as well, but if that's the attitude they are taking
they might as well just pipe it all to /dev/null for all the usefulness.
For me that wasn't acceptable, so getty on the first terminal is
disabled.

If you want it back, make sure this line:

ACTIVE_CONSOLES=/dev/tty[1-5]

is set to include terminal one. By default it starts at 2. This will
need to be set in /etc/sysconfig/init and /etc/init/start-ttys.conf.

I am good with looking at /var/log/messages to get this info. If the
boot does not get to login, then there will be the messages to read anyway.

Service load failures in most cases don't result in anything indicative being written to /var/log/messages. It is also not just about not getting to the login prompt. The service might just print "FAILED" in big red letters when it tries to start up, which will get cleared as soon as the getty loads.

And when I have something FAIL, it is long since scrolled off the screen. But thatnk you for all that you are doing and I have made the change and will be including it in my build documentation as well.


On EL5 and earlier you could set --noclear option on the getting for the first VT, but EL6 changed this due to upstart working differently to SysVInit so you can no longer easily toggle it just on the first VT.

If it bothers you it's a one-liner change and it is documented on the wiki. There are only a few lines on the RootFS wiki page so it's not like it's burried in an obscure paragraph on a long page.

Gordan
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users


_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users

Reply via email to