Kernel 4.1.6 causing "ata_id[] node not specified" from udev.
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Kernel 4.1.6 causing "ata_id[] node not specified" from udev.
Since the bump to 4.1.6 I'm seeing the following message when udev is triggered during boot:
Code:
ata_id [288] node not specified
As far as I can tell it's being caused by the following rule in
59-non-libata-devices.rules:
Code:
# by-id (hardware serial number)
KERNEL=="hd*[!0-9]", IMPORT{program}="ata_id --export $tempnode"
My guess is that its a false match against the 'hdaudio' device(s), which appears to have had a name change compared with older kernels (3.14).
Adding SUBSYSTEM=="block" or something similar to tighten up the match is one possible approach to fixing this, but given that the old ide stuff is obsolete now and has been removed from upstream udev it might be better to just remove this rules file completely. Does udev even have a '$tempnode' now? The udev man page doesn't mention it.
I haven't seen these messages in eudev myself, yet, but I know since Slackware's udev-182 has been out, a lot of changes were made to the kernel and udev both, so some legacy stuff might be getting phased out.
By the looks of it, the file is a concatenation of a number of old rules files that Pat has carried forward from previous versions of udev. I doubt you'd encounter the issue outside of the slackware implementation, so I'm not surprised you're not seeing it with eudev.
I have the original rules, and they are installed, but I don't think eudev is using them for some reason. 3.1.2 from what I can detect, has been using its own self generated rules and automatic detections for some devices. I was thinking of trying to grab a few extra rules from LFS, for example, as well as their rule generator scripts to see if I'm missing anything.
That was one of the reasons I had to import 70-persistent-net.rules to get control of eth0 as a device node.
I did some reading and it seems some syntax was changed after udev-197, but to what degree I have no idea, yet.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.