LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-23-2015, 06:32 PM   #1
GazL
Senior Member
 
Registered: May 2008
Posts: 4,408
Blog Entries: 7

Rep: Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860
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.

Last edited by GazL; 08-23-2015 at 07:02 PM.
 
Old 08-23-2015, 07:01 PM   #2
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-Current
Posts: 6,397
Blog Entries: 15

Rep: Reputation: 1976Reputation: 1976Reputation: 1976Reputation: 1976Reputation: 1976Reputation: 1976Reputation: 1976Reputation: 1976Reputation: 1976Reputation: 1976Reputation: 1976
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.
 
Old 08-23-2015, 07:13 PM   #3
GazL
Senior Member
 
Registered: May 2008
Posts: 4,408
Blog Entries: 7

Original Poster
Rep: Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860
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.
 
Old 08-24-2015, 09:56 AM   #4
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-Current
Posts: 6,397
Blog Entries: 15

Rep: Reputation: 1976Reputation: 1976Reputation: 1976Reputation: 1976Reputation: 1976Reputation: 1976Reputation: 1976Reputation: 1976Reputation: 1976Reputation: 1976Reputation: 1976
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.

Last edited by ReaperX7; 08-24-2015 at 09:59 AM.
 
Old 08-24-2015, 02:12 PM   #5
atelszewski
Member
 
Registered: Aug 2007
Distribution: Slackware
Posts: 777

Rep: Reputation: Disabled
Hi,

I'm running Slackware 14.1 with kernel 4.1.x (now 4.1.6) for quite some time and have also observed this message.

--
Best regards,
Andrzej Telszewski
 
Old 08-24-2015, 02:43 PM   #6
GazL
Senior Member
 
Registered: May 2008
Posts: 4,408
Blog Entries: 7

Original Poster
Rep: Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860
If you don't want to wait for a fix, then just run the following as root:
Code:
echo '# No-op: 59-non-libata-devices.rules' > /etc/udev/rules.d/59-non-libata-devices.rules
 
Old 08-25-2015, 09:44 AM   #7
atelszewski
Member
 
Registered: Aug 2007
Distribution: Slackware
Posts: 777

Rep: Reputation: Disabled
Hi,

Quote:
Originally Posted by GazL View Post
If you don't want to wait for a fix, then just run the following as root:
Code:
echo '# No-op: 59-non-libata-devices.rules' > /etc/udev/rules.d/59-non-libata-devices.rules
Worked for me (Slackware 14.1, kernel 4.1.6).

--
Best regards,
Andrzej Telszewski
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Note about the "ethernet cable" q... what's "kernel" and what's "not" sundialsvcs Linux - Kernel 0 12-01-2012 11:45 PM
I need "libudev" or "udev-devel" for Red Hat 5. jaysolaris Linux - Software 1 08-14-2012 01:14 PM
[SOLVED] "udev: missing sysfs features; update kernel or ..." gregorian Linux - Newbie 5 12-23-2009 06:08 PM
Samba is behaving poorly and causing "unable to handle kernel paging request" errors system Linux - Networking 6 01-26-2002 08:42 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:21 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration