Fresh install (2012/11/01): Not reaching the command line after boot

neok · 2012-11-07 06:29:52

Hi

I just installed the latest 2012/11/01 base + base-devel Arch, but after booting in. the process stopped at the point were the last messages from the kernel were printed in the console. The boot process never reached the shell command line for logging in. I re-installed, thinking I did something wrong but again I had the same problem. Eventually. I accidentally found that by keying Enter, I could get the shell login request and I could login OK, having a seemingly functional base system. However, the console font I specified in vconsole.conf did not take effect and the halt command would hang, although reboot worked OK.

I have of course little experience with systemd, but I get the feeling the all this is due to systemd not running properly. I read whatever documentation I found relevant but since there is so much of it, I believe I must have missed the relevant info.

Please help me to get my new install run properly and please clarify whether have to explicitely enable systemd after completing the official installation instructions.

My thanks in advance.

SolarBoyMatt · 2012-11-07 19:36:38

The halt command will hang in systemd, use:

$ systemctl poweroff

If you're afraid you've missed something, go back through the beginner's guide or something and confirm you created all of the relevant files and such, during the chroot section. And you don't have to explicitely enable systemd anymore on new installs now that it's the default. If that doesn't work, then obviously something else is wrong...

Last edited by SolarBoyMatt (2012-11-07 19:37:12)

teateawhy · 2012-11-07 20:48:54

neok wrote:

please clarify whether have to explicitely enable systemd after completing the official installation instructions.

Read this news item.
https://www.archlinux.org/news/systemd- … allations/

neok wrote:

the console font I specified in vconsole.conf did not take effect

Please always post your configuration files if you reference them.

neok wrote:

the halt command would hang

The halt command does not turn off your computer. The "poweroff" command does.
Writing "systemctl poweroff" is not necessary, as /sbin/poweroff is a link to systemctl poweroff.

Last but not least search for suspicous lines in the log files. You can read them with this command.

$ journalctl

mhertz · 2012-11-08 03:06:31

neok wrote:

However, the console font I specified in vconsole.conf did not take effect[...].

That's probably the known issue about the graphics drm module resetting the fonts, which can be fixed by adding the module to /etc/mkinitcpio.conf(under 'Modules') and regenerating the initramfs with 'sudo mkinitcpio -p linux'. If you use intel graphics, then the module is i915.

neok · 2012-11-08 03:42:11

My thanks for all the replies. Looks like I better do some more reading ... ;-)

Arch Linux

#1 2012-11-07 06:29:52

Fresh install (2012/11/01): Not reaching the command line after boot

#2 2012-11-07 19:36:38

Re: Fresh install (2012/11/01): Not reaching the command line after boot

#3 2012-11-07 20:48:54

Re: Fresh install (2012/11/01): Not reaching the command line after boot

#4 2012-11-08 03:06:31

Re: Fresh install (2012/11/01): Not reaching the command line after boot

#5 2012-11-08 03:42:11

Re: Fresh install (2012/11/01): Not reaching the command line after boot

Board footer