Suse 11.4-KDE: udevd-work error while booting

English Install/Boot/Login
1

I am seeing a udev error message on booting that I have not seen before with LInux and which I cannot interpret. My Suse 11.4-KDE installation is fairly new. My system is a System 76 PanP4 Pangolin that originally ran Ubuntu.

Uname -a returns: Linux linux-zcga 2.6.37.6-0.5-desktop #1 SMP PREEMPT 2011-04-25 21:48:33 +0200 x86_64 x86_64 x86_64 GNU/Linux. My video is a Geforce 9300M with an nVidia driver.

The error reads something like this (I had to scribble pretty rapidly to get this much):

udevd-work [436] error configuring devices ATTR {/sys/devices/pci 0000:00/0000:00 :11.0/USB3/3-2: 1.0/ power/level} FOR WRITING: No such file or directory.

It then repeats essentially this same message with a slightly different opening: udevd-work [436] err Opening ATTR …the rest seems identical to the above line.

A Google search turns up the fact that similar error messages have been reported with Fedora, Ubuntu, Meego and Gentoo. These frequently have had something to do with sound and in at least one case the advised correction was to reinstall udev. I can see where bugs were filed but with no clear response. Some of these go back several years, the most recent is within the last few months. I did not see a posting that involved Suse.

  1. Can someone tell me what these error messages mean?

  2. Does this pose a problem? Everything seems to work normally on my system once I am through the boot process.

  3. If this is a problem how does one fix it?

Thanks for any help!

2

On 06/25/2011 05:36 PM, julian516 wrote:
>
> I am seeing a udev error message on booting that I have not seen before
> with LInux and which I cannot interpret. My Suse 11.4-KDE installation
> is fairly new. My system is a System 76 PanP4 Pangolin that originally
> ran Ubuntu.
>
> Uname -a returns: Linux linux-zcga 2.6.37.6-0.5-desktop #1 SMP PREEMPT
> 2011-04-25 21:48:33 +0200 x86_64 x86_64 x86_64 GNU/Linux. My video is a
> Geforce 9300M with an nVidia driver.
>
> The error reads something like this (I had to scribble pretty rapidly
> to get this much):
>
> udevd-work [436] error configuring devices ATTR {/sys/devices/pci
> 0000:00/0000:00 :11.0/USB3/3-2: 1.0/ power/level} FOR WRITING: No such
> file or directory.
>
> It then repeats essentially this same message with a slightly different
> opening: udevd-work [436] err Opening ATTR …the rest seems
> identical to the above line.
>
> A Google search turns up the fact that similar error messages have been
> reported with Fedora, Ubuntu, Meego and Gentoo. These frequently have
> had something to do with sound and in at least one case the advised
> correction was to reinstall udev. I can see where bugs were filed but
> with no clear response. Some of these go back several years, the most
> recent is within the last few months. I did not see a posting that
> involved Suse.
>
> 1. Can someone tell me what these error messages mean?
>
> 2. Does this pose a problem? Everything seems to work normally on my
> system once I am through the boot process.
>
> 3. If this is a problem how does one fix it?
>
> Thanks for any help!

If you are absolutely sure of the USB3 part of the message, I think that your
motherboard has USB3.0 devices that are not supported by your kernel.

I do not think it is a problem other than you do not have support for USB3
devices. You might try using a newer kernel such as 2.6.39 of 3.0-rcX, which
will have better support.

Incidentally, the message should have been captured in /var/log/boot.msg.

3

I have a script file that can be used to look at the boot log file, among others. Look at message #12 for version 2.10 of slave:

S.L.A.V.E. - SuSE Logfile Automated Viewer Engine - Version 2.00 - Page 2

I also have a script that can be used to compile a newer kernel you can find here:

S.A.K.C. - SUSE Automated Kernel Compiler - Version 2.50 - Blogs - openSUSE Forums

I happen to have a couple of USB 3 hard drives that work fine with openSUSE. I can’t say I had an issue with kernel 2.6.37 and USB 3, but improvements for USB 3.0 have been made. The newest stable kernel is up to 2.6.39.2 right now and it works just fine with openSUSE. Why not give it a try and get back to us on the results.

Thank You,

4

jdmcdaniel3, I’ll be glad to try that though it may take a few days. I’ve got some family birthdays to attend to! But I’ll get back to this. What you suggest sounds very interesting. And if I can help another good project all the better!

lwfinger you may have a point. I do not think this laptop does have a usb3 capability but now that I rad it again it dos look as though that is what udev is seeking. Kernel change might make good sense. Thanks for reminding me of var/log. For some reason I just cannot keep that resource in my foggy head. Surely does make sense to look there.

Thanks to both of you!

5

jdmcdaniel3, I’ll be glad to try that though it may take a few days. I’ve got some family birthdays to attend to! But I’ll get back to this. What you suggest sounds very interesting. And if I can help another good project all the better!

lwfinger you may have a point. I do not think this laptop does have a usb3 capability but now that I rad it again it dos look as though that is what udev is seeking. Kernel change might make good sense. Thanks for reminding me of var/log. For some reason I just cannot keep that resource in my foggy head. Surely does make sense to look there.

Thanks to both of you!

You are very welcome julian516. By the way, birthdays are way more important than this, so please take care of them first. Also, lwfinger who has provided you with some help today, is very prominent with kernel and wifi development. I would read his advice very carefully. I wish you luck with your problem and please, just ask if you need more assistance.

Thank You,

6

S.L.A.V.E. looks useful indeed! Any new Suse user perusing this thread ought to take a look at it. Certainly I am going to use it.

Meanwhile, a progress report on lwfinger’s suggestion regarding USB3 status and alternative kernel(s).

My Pangolin PanP4 does not contain any USB-3 technology. If that is what udev
is set up to find it will not find it, so that is what it apparently reports as
we go through the boot process. Here are the results of lsusb:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 5986:0300 Acer, Inc
Bus 003 Device 002: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint
Sensor
Bus 005 Device 002: ID 046d:c526 Logitech,Inc. Nano Receiver

The last device listed is a USB wireless Logitech mouse.

I did finally find this page on the Suse site:

software.opensuse.org: Search Results
%3A11.4&lang=en&exclude_debug=true

So now I am looking at a list of kernels that apparently are available for
installation.

I have a 64-bit installation so I am looking at AMD-64 kernels.

Before I do anything further should I be making a change in my repositories?

Do I assume I want the version with the most recent time/date stamp?

Do I want to do the “One-Click Install” of “kernel-desktop-base”?

Does this process over-write or replace my existing kernel?

Can I revert back to my present kernel if need be?

Sorry for so many questions! If I am on my Debian system doing apt-get or
using Synaptic I know a bit more about what I am doing. Suse is strange (but attractive!) territory. If
something like zypper is useful, for example, I know nothing (yet!) about its
syntax. Obviously I have a lot to learn.

So until I can get that done, any help appreciated!