You are not logged in.
Pages: 1
Hi guys!
Maybe someone can help me out? I am having a weird boot problem. The system starts up normally but then I get a blinking cursor that sits there for up to 90 seconds unless I move my mouse. If I move the mouse, the system boots right through to Gnome. I am using GDM but it doesn't seem like my problem is related to the usual "blinking cursor" issue.
I am fairly new to Arch and - at least for now - I don't exactly know what I am doing. If you need some output from the terminal or such, please tell me exactly what I would need to type in. Copy & paste I already manage. ![]()
Thanks in advance!
Last edited by Tumultus (2019-07-06 17:58:05)
Listing spec's is not a review!
Offline
Sounds like a lack of entropy: https://wiki.archlinux.org/index.php/Ra … generation
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
Ok, installing and enabling haveged solved the delay problem on boot. However, now auto login doesn't work anymore. Maybe I shouldn't have opened this can of worms. ![]()
Listing spec's is not a review!
Offline
That seems like a unrelated issue.
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
How so? If I disable haveged, auto login works again. I am really confused.
Listing spec's is not a review!
Offline
That really sounds strange. Haveged should not interfere in such a way.
Maybe the fact that the autologin works is a bug in GDM caused by lack of entropy.
Can you show us your /etc/gdm/custom.conf ?
Last edited by schard (2019-07-04 12:56:32)
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
Weird. I downgraded in between to the LTS kernel - no change. I then went ahead and installed the missing aic94xx and wd719x firmware from the AUR and now it works with haveged enabled. Not sure why this would be the case since the entire internet insists that the mentioned firmware isn't essential and should just be ignored.
Will have to try later to see what happens if I switch back to the current kernel.
Thanks for your help, schard!
Listing spec's is not a review!
Offline
It's more likely that you are simply starting up too fast now and your graphics driver not yet being completely initialized when you are running into graphical target, should be a more maintainable and permanent fix fwiw it would probably help if you posted a journal log of a "faulty" boot.
Offline
Well, other than some ACPI BIOS errors under dmesg I can't find anything. After researching those errors, I learned that they don't need fixing and it is simply that those simply don't meet kernel expectations.
But, as stated earlier, my system seems to work flawlessly now. I even switched back to the current kernel; no more hick ups or boot delays. You're probably right and my computer is simply too fast! Should have never installed a SSD. ![]()
Last edited by Tumultus (2019-07-04 19:45:06)
Listing spec's is not a review!
Offline
Pages: 1