Red Hat Bugzilla – Bug 465706
When a problem arises during boot and you are forced into a shell the terminal is broken
Last modified: 2013-01-09 23:50:00 EST
When a problem arises during boot and you are forced into a shell (i.e. when one partition couldn't be mounted during boot) the terminal is broken. It seems as if plymouthd interferes with the terminal in some way that eats the cursor and only a part of the character typed reach the shell.
This is actually most likely just another manfestation of bug 464216
Normally we do
before starting up the shell. since plymouth depends on /usr being available it would fail and plymouth wouldn't give up the tty.
*** This bug has been marked as a duplicate of bug 464216 ***
Sorry, still doesn't work. The console goes completely bonkers when I switch to it by pressing Esc during the plymouth screen. When I press enter I get ^M on the screen. Not particularly helpful. Still no cursor.
Booting with a serial console has simliar terminal/display issues (same bug?):
System boots up fine. At some point in the middle of the boot process the cursor disappears and the cursor position seems to jump to the top of the screen, making following boot messages scribble over the previous ones. Finally the login prompt appears, the cursor is still invisible. Login works nevertheless. Running the "reset" command brings the terminal back into normal state.
[root@fedora ~]# cat /proc/cmdline
ro root=/dev/VolGroup00/LogVol00 console=ttyS0
[root@fedora ~]# rpm -q plymouth
Hi Gerd, your issue should already be fixed with latest rawhide.
Lennart, I believe your issue should be fixed by plymouth-0.6.0-0.2008.10.27.6.fc10
Can you confirm?
Sorry, still doesn't work with plymouth-0.6.0-0.2008.10.27.7.fc10.i386.
BTW, maybe I should mention than I only get the text-version of plymouth (intel gfx) -- that's where i press Esc. Also, when I press Esc early during bootup the hdd pasword stuff is completely borked -- you get a lot of erros about "partition not found" and then a root password prompt for a shell -- but of course you cannot type the password in, since your terminal is broken.
Also, at about half the boot the plymouth screen already reaches 100% and I am swicthed back to the classic boot screen with all those "... [done]" lines for the remaining half.
sounds impressively broken
Re #4: yes, serial console works ok now.
Testing by forcing a drop to one of the emergency shelsl in rc.sysinit yields, for me:
- Text mode - echo works, cursor works (i.e., everything normal)
- GUI mode (solar) - echo works, no cursor (reset fixes the cursor)
which emergency shell?
What i did is:
echo "AUTOFSCK_SINGLEUSER=yes" >> /etc/sysconfig/autofsck
*pull power plug*
It brought me to an emergency shell and everything worked fine.
What am I doing differently than you?
(In reply to comment #10)
> which emergency shell?
The same one.
> What am I doing differently than you?
Dunno. I'm using vesafb for testing the GUI plymouth - that may be it.
The no cursor issue is fixed now along with some other issues with sulogin. I don't know if lennart's original problem is fixed though (since I can't reproduce and haven't made any changes to that effect).
Lennart, mind trying with the latest version?
(by latest i mean plymouth-0.6.0-0.2008.11.10.4 or later)
plymouth-0.6.0-0.2008.11.10.5.fc10 will be tagged today, I'd like it if everybody involved re-tests this issue and see if it still shows up.
I'm going to close this out. Lennart, if you're still seeing the original problem, please reopen.
If the other issues you mentioned in comment 6 didn't get independently fixed in the interim, please file separate reports for those issues.