I've seen this now a few times, but of course I didn't write them down, so I may have the wording a little off.
The new kernel seems to contain something in udevd that is now generating a whole slew of unknown attribute(or something like that) errors during the boot, before the part where dmesg picks up.
They don't seem to be causing any actual problems while the system is up and running, but....
Anyone know anything about this (and what)?
Curious.
mhr
MHR wrote:
I've seen this now a few times, but of course I didn't write them down, so I may have the wording a little off.
The new kernel seems to contain something in udevd that is now generating a whole slew of unknown attribute(or something like that) errors during the boot, before the part where dmesg picks up.
They don't seem to be causing any actual problems while the system is up and running, but....
Anyone know anything about this (and what)?
probably not the kernel, you might have installed some package since your previous reboot and you're just seeing the messages now I know I saw this with a rebuilt libnjb from FC7
check /var/log/messages, you should see what the message was. I suspect udevd stuff like: unknown key 'ATTRS{idVendor}'
Then grep the string in /etc/udev/rules.d/* to find the culprit
If you have eg some ATTRS{idVendor} you might try replacing them with SYSFS{idVendor}
On Feb 15, 2008 6:47 AM, Nicolas Thierry-Mieg Nicolas.Thierry-Mieg@imag.fr wrote:
probably not the kernel, you might have installed some package since your previous reboot and you're just seeing the messages now I know I saw this with a rebuilt libnjb from FC7
check /var/log/messages, you should see what the message was. I suspect udevd stuff like: unknown key 'ATTRS{idVendor}'
Then grep the string in /etc/udev/rules.d/* to find the culprit
libmtp.x86_64 0.1.5-1.fc5 installed
If you have eg some ATTRS{idVendor} you might try replacing them with SYSFS{idVendor}
There are a ton of them (it's ATTR, btw). I'll try this and see if it works, but it looks like a macro?
Anyway, thanks. I'll see what happens on next reboot....
mhr