On Tue, Sep 27, 2011 at 9:39 AM, Patrick Burroughs wrote:

On Tue, Sep 27, 2011 at 00:33, Jorge Almeida wrote:

...

There has been some recent change somewhere in the startup process that makes startup messages disappear once the process is completed and the login prompt appears. I had (and have) in /etc/initttab:

c1:2345:respawn:/sbin/agetty -i -8 38400 tty1 linux

I added the "-i" to prevent clearing the terminal, and it worked. Not any more. Not even with  Shift+PageUp. Anyone knows what changed?

TIA

Jorge Almeida

There's a special character at the beginning of /etc/issue that clears the screen. Try removing that.

~Celti

https://wiki.archlinux.org/index.php/Disable_Clearing_of_Boot_Messages

On Tue, Sep 27, 2011 at 3:16 PM, Jorge Almeida wrote:

...

https://wiki.archlinux.org/index.php/Disable_Clearing_of_Boot_Messages

Thank you. It seems the behaviour of agetty changed. The --noclear option appears to be the relevant one. I think it wasn't there before, but I may be wrong.

Jorge

Yes, it's one of the new things. http://userweb.kernel.org/~kzak/util-linux-ng/ is still down, so you have to use 'man agetty' if you want to check other options.

On Tue, Sep 27, 2011 at 12:12:29PM +0200, Tom Gundersen wrote:

FYI: All the special characters in /etc/issue will go away in the next filesystems release (as agetty deals with it now).

Also, if you want to see what happened during boot, there is /var/log/boot

Something remotely related for which I'd appreciate a solution: On one of the laptops I use, at some point during the boot sequence the display brightness is reduced to almost invisible. Any ideas of where to look to fix this ? TIA, -- FA

hey this quick and minimalistic patch [1] to rc.{sysinit,single,multi} here works to capture almost the complete boot output in per-script manner in /bootlog. don't forget to mkdir /bootlog when you apply it. use less -r to read them, and don't be irritated, it will change the results for right-aligned output (like [DONE]). dmesg errors aren't recorded, but those go to /var/log/dmesg.log anyway. [1] http://ix.io/1Tx/diff

On Tue, Sep 27, 2011 at 8:39 AM, Patrick Burroughs wrote:

...

There has been some recent change somewhere in the startup process that makes startup messages disappear once the process is completed and the login prompt appears. I had (and have) in /etc/initttab:

c1:2345:respawn:/sbin/agetty -i -8 38400 tty1 linux

I added the "-i" to prevent clearing the terminal, and it worked. Not any more. Not even with  Shift+PageUp. Anyone knows what changed? There's a special character at the beginning of /etc/issue that clears

On Tue, Sep 27, 2011 at 00:33, Jorge Almeida wrote: the screen. Try removing that.

The -i makes the contents of /etc/issue irrelevant. That's why I put in /etc/inittab, although it's not the best solution. Thanks J.A.

On Tue, Sep 27, 2011 at 11:30 AM, cantabile wrote:

On 09/27/2011 10:33 AM, Jorge Almeida wrote:

...

agetty(8) says: --noclear   Do not clear the screen before prompting for the login name   (the screen is normally cleared).

So try that and let me know if it works (don't remove -i). I'm also interested in this but I can't reboot atm.

I can't reboot either, but I'm pretty sure you're right. I suppose the --noclear is new and was not "advertised" Thanks Jorge

Not sure if someone already posted this: https://bugs.archlinux.org/task/25980

That's it. I already rebooted and it comes out OK. "--noclear" is the option to use. J.A.

On Tue, Sep 27, 2011 at 6:00 PM, SanskritFritz wrote:

On Tue, Sep 27, 2011 at 6:44 PM, Jorge Almeida wrote:

...

...

Not sure if someone already posted this:

https://bugs.archlinux.org/task/25980

...

That's it. I already rebooted and it comes out OK. "--noclear" is the option to use.

Strange, it doesnt work for me :( here is what I have in /etc/inittab:

c1:2345:respawn:/sbin/agetty --noclear -8 -s 38400 tty1 linux

Can you try without the "-s"? (I will not pretend that I understand the issues with gettys, but I think the default, whatever this means, does not have the flag, only the 38400 argument.) J.

On Tue, Sep 27, 2011 at 7:46 PM, Tom Gundersen wrote:

Did you remember to delete the special characters from /etc/issue ?

Ah, you're right, I forgot about that. Now it works, thank you!