Created attachment 562428 [details]
Description of problem:
anaconda suspend at first reboot if using the text mode installer
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot the installation passing the command line argument text.
2. Proceed and complete installation.
3. Reboot when installation completed.
System halts after the "Started OpenSSH server deamon [OK]".
Reboot successfully into installed system
If you hit enter, does it redisplay the login prompt? This is quite obviously not an anaconda problem, as it's got nothing to do with installation. I don't really know whose problem it is, though, so let's send it to systemd since they handle process startup now.
We can do something to shut up the boot messages before starting getty, because they obviously confuse people.
But first I'd like to know the answer to Chris's question. Does hitting Enter make the prompt appear? If not, can you switch to a different VT and login there? If not, does Ctrl+Alt+Del reboot the system?
Is this the same as #787461?
Fedora Bugzappers volunteer triage team
FYI the suspending part is not systemd issue it's either an xorg-x11-drv-intel ( or potentially some other driver ) + kernel 3.+ regression ( there seem to be few of those floating around atleast with i915 ) or plymouth.
So Tao what kind of graphics card do you have?
(In reply to comment #4)
> FYI the suspending part is not systemd issue it's either an xorg-x11-drv-intel
> ( or potentially some other driver ) + kernel 3.+ regression ( there seem to be
> few of those floating around atleast with i915 ) or plymouth.
> So Tao what kind of graphics card do you have?
Mine is nVidia Corporation G96 [Quadro FX 380].
(In reply to comment #3)
> Is this the same as #787461?
> Fedora Bugzappers volunteer triage team
I don't think they are same, this one is about how to avoid the boot messages before starting getty.
I don't see a direct answer to my question, but from your latest comment I am deducing that the system is in fact fully alive and the only problem is the boot messages being printed after the login prompt.
[Changing title accordingly.]
mschmidt: I suspect it's to do with plymouth being missing (even in RC4 it's still missing in a minimal install, unfortunately, because I put it in comps Base not Core, and minimal install doesn't install Base).
Fedora Bugzappers volunteer triage team
Yes, plymouth influences what we print. But still, I want to fix this even for the case when plymouth is not used.
*** Bug 801405 has been marked as a duplicate of this bug. ***
(In reply to comment #2)
> Does hitting Enter make the prompt appear?
In F17, <ENTER> draws a new release/kernel/prompt below the last boot message.
There is already a release/kernel/prompt beginning on the top line, after which various boot messages (all networking related here) appear.
In upstream systemd the getty services use a new feature to workaround the problem. It's "Type=idle", which delays the actual execution of the getty process by up to 5 seconds if the boot has not finished completely yet. I am not a big fan of it, but it does make the cosmetic issue go away in most cases. It will likely be included in a future update.
systemd-44-13.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-44-14.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
I would have left positive feedback in response to comment 14, but there's no way I can comply with the password requirements. I haven't had the memory of a teenager in over 50 years.
Considered using a password manager? It's a really good idea.
I suppose that could be useful to someone who doesn't use 100+ logins across 30+ multiboot puters running disparate operating systems and web browsers.
(In reply to comment #15)
> I would have left positive feedback in response to comment 14, but [...]
Counting of the karma points is not very useful anyway. I don't enable karma automatism. The critical threshold for update approval is usually reached quite soon for systemd. Then I wait for a few more days to let people notice any regressions. I pay attention to other kinds of feedback besides karma.
systemd-44-14.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.