Waiting for uevents to be processed [SOLVED]

lizardbrain · n00b Joined: 03 Jun 2007 Posts: 64 Location: the swamp

What happened between last May and now? Aside from the failed hard drive I had to replace, my hardware hasn't changed, but while the May 2014 install was successful now the boot process stalls at "Waiting for uevents to be processed...". I've reinstalled Gentoo several times and the problem persists. The forum threads have been notably unhelpful, with most of them talking about nvidia drivers, which I don't need.

The results of lspci:

AndrewAmmerlaan · Posted: Wed Nov 26, 2014 5:02 pm Post subject:

I had the same problem when I installed gentoo for the first time, I solved it by installing the firmware for my radeon GPU. If you haven't done that yet, I suggest you do, but it might not work, because this problem can have many causes. Maybe you could provide some more information, about what exactly you did and did not do during the installation process.
_________________
OS: Gentoo 6.7.3-gentoo-dist, ~amd64, 17.1/desktop/plasma/systemd/merged-usr
MB: MSI Z370-A PRO
CPU: Intel Core i9-9900KS
GPU: Intel Arc A770 16GB & Intel UHD Graphics 630
SSD: Samsung 970 EVO Plus 2 TB
RAM: Crucial Ballistix 32GB DDR4-2400

mv · Watchman Joined: 20 Apr 2005 Posts: 6747

uevents has a huge timeout (5 minutes or so). When you wait and it returns eventually, you might see something useful in the logs.

lizardbrain · n00b Joined: 03 Jun 2007 Posts: 64 Location: the swamp

Thanx to the both of you for your replies.

AndrewAmmerlaan, the link in your post on Monday to the wiki for Radeon firmware looks like it's worth a shot. I'll give it a try when I have some more time to devote to it.

mv, uevents has an even larger timeout on my system. After waiting an hour and a half, I finally forced a shutdown; during the wait, the boot process didn't just slow down, it halted: Ctrl-C was not responsive, nor could I switch to another terminal.

I have family commitments tomorrow, but I'll try to get back to this on Friday.

lizardbrain · n00b Joined: 03 Jun 2007 Posts: 64 Location: the swamp

AndrewAmmerlaan, I just realized that my reply to you was incomplete.

My install of Gentoo was straight out of the handbook using a minimal install iso on a USB thumb drive. The kernel was built using genkernel, to minimize the possibility of mistakes I might make. The only deviations were the addition to make.conf of EMERGE_DEFAULT_OPTS="--ask --verbose", ACCEPT_LICENSE="*" and -systemd to the global USE flags.

My apologies for the omission.

[edited to eliminate a typo]

AndrewAmmerlaan · Posted: Fri Nov 28, 2014 6:44 am Post subject:

lizardbrain · n00b Joined: 03 Jun 2007 Posts: 64 Location: the swamp

AndrewAmmerlaan,

Thank you.

Success! I installed linux-firmware, followed the directions in http://wiki.gentoo.org/wiki/Radeon, and recompiled the kernel. Uevents now processes in a reasonable time (1-2 seconds) and the boot process finishes as it should with no ominous warnings.

I'm updating the system right now, so there's still time for something to go awry, but the original problem has been solved and I'll mark it as such.

Again, thanx.

[edited for clarity and flow]

Faraclas · Tux's lil' helper Joined: 08 Dec 2014 Posts: 117

I have a similar problem and could use some help. I had a working system using the nouveau drivers for my nvidia card. I wanted to try and add the nvidia drivers so I did the following:

* In /etc/portage/make.conf I removed "nouveau" and added "nvidia" in VIDEO_CARDS
* ran emerge -avuDN world to get the changes
* edited /etc/X11/xorg.conf and replaced "nouveau" with "nvidia"

Now when I boot it is hanging at the udev: waiting for uevents to be processed.

Can someone help me?

--Edit
I went back and ran

AndrewAmmerlaan · Posted: Tue Dec 09, 2014 7:53 am Post subject:

Either remove nouveau from the kernel or enable it as module and blacklist it, if it is a module now just blacklist it. check the wiki for more information