I cannot boot my system normally (by choosing the "Arch Linux" grub option) after updating recently. It appears that systemd starts to work. I get the "Welcome to Arch Linux!" message and several things marked "[ OK ]" fly by too quickly to see. After that, the monitor goes blank and tells me that it's going into power saving mode. I cannot get a TTY terminal (i.e. ctl-alt-F2 does nothing). I cannot ping the machine on the network.
I can however boot all the way to graphical when I choose the "Arch Fallback" option in grub (has nomodeset on the kernel line and points to the fallback initramfs). The video is low resolution and only one monitor, but my nvidia card using nouveau drivers appears to be in use (lsmod).
I guess this means there is a problem with my video somewhere, but how can I isolate what the problem is? The journalctl log does not show information from the times that I boot using the normal method.
B. J. Potter
Last edited by bjcubsfan (2013-02-08 15:53:38)
The journalctl log does not show information from the times that I boot using the normal method.
So specifically, this morning, I rebooted to normal mode at 8:20 and let it fail as described. I then waited 9 minutes to make the timestamps obvious and allow perhaps journal/logs to write (even though the system appears to be dead by any view). I then slowly restarted the system via alt-prtscn-R. E. I. S. U. B. This time I booted into fallback mode to check the logs. There are no entries in journalctl from the boot that failed. See the relevant part of my log at the link below.
Here's some more information. I have changed the target to multi-user (same as the old 3). The boot fails even with this in normal mode. In fallback mode I get the console login as expected. So maybe the problem is not with video? I am still just completely unsure how to track down the exact problem.
Last edited by bjcubsfan (2013-02-08 14:49:08)
I will try that again on Monday, but I think I tried it before and it does NOT work. Is the lack of logs just something I have to live with because of systemd? Should I try running syslog in conjunction (like https://wiki.archlinux.org/index.php/Sy … th_syslog)? Is there another way to turn on more logging output?
I will try enabling syslog. I breezed through the Xorg logs, but I don't think I'm getting that far in the boot process. Also, it's hard to correlate times to see if it was from the current or previous boot since the xorg logs just have numbers like [366.3253].
The logs that were updated today were several binary logs, like 'lastlog'. The only one I got anything useful out of was Xorg. Perhaps I missed enabling some logs several months ago when switching to systemd?
What exactly got updated?
Sounds like this reoccurring bug with nouveau to me.
Try downgrading your kernel. Or switch to the propriety nvidia module.
Mobo: ASUS P8Z77-V PRO // Processor: Intel Core i7-3770K 3.4GHz // GFX: nVidia GeForce GTX 970 Ti // RAM: 32GB (4x 8GB) Corsair DDR3 (@ 2133MHz) // Storage: 1x 3TB Seagate SATAII 5x 1TB Samsung SATAII, 2x 120GB Corsair SSD
Making lemonade from lemons since 2015.
This link below shows what was upgraded:
I will try downgrading the kernel or switching to nvidia on Monday.
I tried several things today. Booting the normal kernal with 'nomodeset' does complete booting. This leads me to believe it's something to do with my video system (NVIDIA Corporation G98 [Quadro NVS 295] (rev a1) using the nouveau drivers). I tried enabling syslog to get more information out of the logs, but just as with 'journalctl' nothing is in the logs from the failed boots.
I decided to try downgrading the kernel next, and that worked. I went to the version of the kernel that was used when I last had my system working, and I booted normally. I think I'll not upgrade for a while and hope this bug is fixed somehow in the meantime.