You are not logged in.
I have an old Dell Inspiron 1100. I just did an upgrade (which included the 2.6.39 kernel, I believe). I'm now getting Udev daemon fail (fails to start)--and possibly an aspci fail?
I'm running gnome 3...
Anyone else run into this?
I'm semi-new to arch--any suggested remedies?
[edit] Just saw this in the "news" section--sounds like it could be related. Not sure what to do with this info, though...
initscripts update
2011-05-11
Due to a clash with another package we have moved our newly introduced script from /sbin/rc to /sbin/rc.d.
rc.d allows you to start and stop daemons, as well as show the status of the daemons on your system.
Last edited by wilberfan (2011-05-21 04:35:00)
Hey, be nice...I'm new at this!
Offline
I have an old Dell Inspiron 1100. I just did an upgrade (which included the 2.6.39 kernel, I believe). I'm now getting Udev daemon fail (fails to start)--and possibly an aspci fail?
I'm running gnome 3...
Anyone else run into this?
I'm semi-new to arch--any suggested remedies?
Are you using testing repository? 2.6.39 is in testing. You can check what you have installed in /var/log/pacman.log and downgrade/upgrade what is necessary.
Are your whole system up-to date?
Last edited by einhard (2011-05-21 08:09:37)
Offline
Now that you mention it, yeah, I think Testing is still enabled--I used it to install gnome 3. (Gnome 3 has since moved into...extra?) I'll check, thanks!
Hey, be nice...I'm new at this!
Offline
Now that you mention it, yeah, I think Testing is still enabled--I used it to install gnome 3. (Gnome 3 has since moved into...extra?) I'll check, thanks!
are you sure it was the kernel and not udev updates that broke your input devices?
Offline
Moved to [testing].
ᶘ ᵒᴥᵒᶅ
Offline
I'm experiencing the same udev failure on an HP G71; udev fails to start at boot, and as such, I don't have access to any USB devices, the resolution is off, and I can't use the mouse/keyboard on the laptop. I think it's the update to the udev package itself, and not the kernel which is causing the issue, but I'm going to downgrade udev and see if that does it; if not, I'll look more closely at the kernel.
Offline
I'm experiencing the same udev failure on an HP G71; udev fails to start at boot, and as such, I don't have access to any USB devices, the resolution is off, and I can't use the mouse/keyboard on the laptop. I think it's the update to the udev package itself, and not the kernel which is causing the issue, but I'm going to downgrade udev and see if that does it; if not, I'll look more closely at the kernel.
Same thing happened to me. udev-170 and linux-2.6.39 were upgraded together.
The thing is, with the LTS kernel, it seems to work fine. At least the laptop's keyboard and "mouse" work under X.
Jabber/XMPP rocks!
Offline
So after a quick downgrade to udev, problem continued to occur. I reverted back to 2.6.38.6-2 for the kernel, and everything went back to normal; ergo, it's not the update to udev, but rather, the new kernel version that's causing the problems. I'll take a closer look at what changed between the two when I can find some free time later.
Offline
This doesn't really help, except to confirm that it's the kernel, and not udev:
I have the same problem with the stock kernel, but my own 2.6.39 build works as expected. FYI I don't use the Arch patches, and I have a stripped down config tailored to my laptop.
Offline
I'm not sure if this is the same problem, but I too have enabled the Testing repositories on my eeepc 900 and upon installing kernel 2.6.39 and udev170 I lost keyboard and trackpad on X, networking, usb support, battery status, etc.
I solved the problem by downloading udev170-1 on a livecd and doing a local pacman install back on arch.
Offline
I got same issue here.
udevd: unable to receive user udevd message: Resource temporarily unavailable
After few hours, I solved updating my rc.conf with not-so-recently introduced options:
# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30
This solved for me (kernel 2.6.39 - udev 170). Give it a try...
Offline
As of yesterday, I reinstalled both Kernel 2.6.39-ARCH and udev-170, and the bug seems to have been fixed by the developers, all is resolved on this end.
Offline
As of yesterday, I reinstalled both Kernel 2.6.39-ARCH and udev-170, and the bug seems to have been fixed by the developers, all is resolved on this end.
I took your experience as a good sign, so tried an upgrade again last night. Something very bad happened during the procedure (not really sure what)--and now my system is unbootable. (GRUB Error, Step 1.5, Error 2).
Guess there's a re-install in my future! And this time I'm going to stay away from the Testing repo!
Hey, be nice...I'm new at this!
Offline
Apologies if I led you to toast your system... but are you sure it's the kernel/udev combination that's causing problems for you? I initially had the same issues (and those I described in my initial post), but after waiting a day and running pacman -Syu with the [testing] repo enabled, my problems were solved without any other intervention on my part.
Offline
I could have easily did something stupid. I removed the testing repo--did a couple of updates--then put testing back... Who knows what kind of mischief I caused. Plus, it's a pretty old lappie--not sure how tolerant it is of brand new kernels n' such...
Hey, be nice...I'm new at this!
Offline