Bug 630578

Summary: udevd reports SYSFS()=will be removed - use ATTR{} to match it
Product: [openSUSE] openSUSE 11.3 Reporter: Lyle Bickley <lbickley>
Component: Update ProblemsAssignee: E-mail List <bnc-team-screening>
Status: RESOLVED WORKSFORME QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P3 - Medium CC: forgotten_7Vd19u3Vod, jreuter, meissner, seife
Version: Final   
Target Milestone: ---   
Hardware: i686   
OS: openSUSE 11.3   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: udev rule file creating errors
udev rule file creating errors

Description Lyle Bickley 2010-08-12 01:41:31 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.99 Safari/533.4

Boot logging started on /dev/char/../tty1(/dev/console) at Tue Aug 10 16:22:35 2010

<notice -- Aug 10 16:22:35.794815000> service boot.startpreload startdone
<notice -- Aug 10 16:22:36.277575000> service boot.startpreload done<notice -- Aug 10 16:22:36.277724000> se
rvice boot.udev startok
Starting udevd: udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match t
he event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-gpsd.rules:10

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-gpsd.rules:12
udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-gpsd.rules:14

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-gpsd.rules:16

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-gpsd.rules:18

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:73

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:76

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:77

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:78

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:79

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:80

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:81

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,

 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:82

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:83

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:84

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:85

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:86

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:87

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:88

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:89

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:90

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:91

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:92

 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:82

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:83

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:84

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:85

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:86

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:87

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:88

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:89

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:90

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:91

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:92

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:93

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:94

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:95

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:96

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:97

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:98

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:99

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:100

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:101

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:105
udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:106

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:107

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:108

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:109

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:110

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:111

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:112

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:113

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:114

udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device,
 or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:115

udevd[429]: NAME="%k" is ignored, because it breaks kernel supplied names, please remove it from /etc/udev/r

ules.d/51-hso-udev.rules:124

udevd[429]: can not read '/etc/udev/rules.d/79-yast2-drivers.rules'

done
Loading drivers, configuring devices: done


Reproducible: Always

Steps to Reproduce:
1. Boot System
2. Review boot.msg
3.
Actual Results:  
See Details

Expected Results:  
The indicated files in /etc/udev/rules.d should have been upgraded along with the upgrade from 11.2 to 11.3 to prevent this series of error messages
Comment 1 Lyle Bickley 2010-08-12 17:56:11 UTC
Created attachment 382661 [details]
udev rule file creating errors
Comment 2 Lyle Bickley 2010-08-12 17:57:24 UTC
Created attachment 382662 [details]
udev rule file creating errors
Comment 3 Marcus Meissner 2010-08-13 13:14:00 UTC
51-hso-udev.rules is from ozerocdoff  , maintbainer seife

51-gpsd.rules is from gpsd. maintainer jreuter

seife, when fixed, reassign to joerg please
Comment 4 Stefan Seyfried 2010-08-13 18:10:34 UTC
I requested ozerocdoff to be dropped a long time ago, those who did not obey the wish will need to fix it.

(Even if the fix is trivial, if I do it now, I will forever be responsible for the package ;-)
Comment 5 Lyle Bickley 2010-08-31 23:03:16 UTC
What is the status of this bug? - it doesn't seem to have "moved" since Stefan's comment...
Comment 6 Forgotten User 7Vd19u3Vod 2010-10-26 09:58:14 UTC
I have the same issue since I upgraded from 11.2 to 11.3

Can I do something about this myself, i.e. get rid of these messages?
Comment 7 Joerg Reuter 2010-10-26 10:53:43 UTC
These are just harmless (for now) warnings.

Unless you have a UMTS (3G) modem which requires ozerocdoff to switch from mass storage mode to modem modem, "rpm -e ozerocdoff" will fix the 51-hso-udev.rules complaints.

If you don't have USB GPS hardware attached, removing /etc/udev/rules.d/51-gpsd.rules will do as a workaround.

If you need one of these, either ignore the messages or configure your favourite syslog daemon to discard them.

I'll need to have a look at the current status of gpsd package, I remember having fixed this before 11.3 but probably forgot to properly check it in.
Comment 8 Joerg Reuter 2010-10-26 11:08:27 UTC
Oh, wait a minute... I did.

# wget http://download.opensuse.org/distribution/11.3/repo/oss/suse/x86_64/gpsd-2.92-1.30.x86_64.rpm
[..]
# rpm2cpio gpsd-2.92-1.30.x86_64.rpm | cpio -id
222 blocks
# grep ^KERNEL rules.d/51-gpsd.rules 
KERNEL=="ttyUSB*", RUN="/lib/udev/gpsd.sh"
KERNEL=="ttyUSB*", ATTR{idVendor}=="067b", ATTR{idProduct}=="2303", RUN="/lib/udev/gpsd.sh"
KERNEL=="ttyUSB*", ATTR{idVendor}=="0403", ATTR{idProduct}=="6001", RUN="/lib/udev/gpsd.sh"
KERNEL=="ttyUSB*", ATTR{idVendor}=="1163", ATTR{idProduct}=="0100", RUN="/lib/udev/gpsd.sh"
KERNEL=="ttyUSB*", ATTR{idVendor}=="1163", ATTR{idProduct}=="0200", RUN="/lib/udev/gpsd.sh"
KERNEL=="ttyUSB*", ATTR{idVendor}=="067b", ATTR{idProduct}=="aaa0", RUN="/lib/udev/gpsd.sh"
KERNEL=="ttyUSB*", ATTR{idVendor}=="10c4", ATTR{idProduct}=="ea60", RUN="/lib/udev/gpsd.sh"
# 

What is the output of "rpm -qi gpsd" on your system?
Comment 9 Joerg Reuter 2010-10-26 11:13:26 UTC
And the only occurrence of the SYSFS hash in 51-hso-udev.rules is in some comments on openSUSE 11.3...
Comment 10 Joerg Reuter 2010-10-26 15:50:17 UTC
*** Bug 626949 has been marked as a duplicate of this bug. ***
Comment 11 Forgotten User 7Vd19u3Vod 2010-10-26 18:49:49 UTC
(In reply to comment #8)
> Oh, wait a minute... I did.
> 
> # wget
> http://download.opensuse.org/distribution/11.3/repo/oss/suse/x86_64/gpsd-2.92-1.30.x86_64.rpm
> [..]
> # rpm2cpio gpsd-2.92-1.30.x86_64.rpm | cpio -id
> 222 blocks
> # grep ^KERNEL rules.d/51-gpsd.rules 
> KERNEL=="ttyUSB*", RUN="/lib/udev/gpsd.sh"
> KERNEL=="ttyUSB*", ATTR{idVendor}=="067b", ATTR{idProduct}=="2303",
> RUN="/lib/udev/gpsd.sh"
> KERNEL=="ttyUSB*", ATTR{idVendor}=="0403", ATTR{idProduct}=="6001",
> RUN="/lib/udev/gpsd.sh"
> KERNEL=="ttyUSB*", ATTR{idVendor}=="1163", ATTR{idProduct}=="0100",
> RUN="/lib/udev/gpsd.sh"
> KERNEL=="ttyUSB*", ATTR{idVendor}=="1163", ATTR{idProduct}=="0200",
> RUN="/lib/udev/gpsd.sh"
> KERNEL=="ttyUSB*", ATTR{idVendor}=="067b", ATTR{idProduct}=="aaa0",
> RUN="/lib/udev/gpsd.sh"
> KERNEL=="ttyUSB*", ATTR{idVendor}=="10c4", ATTR{idProduct}=="ea60",
> RUN="/lib/udev/gpsd.sh"
> # 
> 
> What is the output of "rpm -qi gpsd" on your system?

asterix:~ # rpm -qi gpsd
Name        : gpsd                         Relocations: (not relocatable)
Version     : 2.37                              Vendor: openSUSE
Release     : 73.1                          Build Date: Tue Oct 20 13:08:18 2009
Install Date: Tue Nov  3 01:14:12 2009         Build Host: build33
Group       : Hardware/Other                Source RPM: gpsd-2.37-73.1.src.rpm
Size        : 377079                           License: BSD 3-clause (or similar)
Signature   : RSA/8, Tue Oct 20 13:09:06 2009, Key ID b88b2fd43dbdc284
Packager    : http://bugs.opensuse.org
URL         : http://gpsd.berlios.de/
Summary     : Service daemon for mediating access to a GPS
Description :
gpsd is a service daemon that mediates access to a GPS sensor connected
to the host computer by serial or USB interface, making its data on the
location/course/velocity of the sensor available to be queried on TCP
port 2947 of the host computer.  With gpsd, multiple GPS client
applications (such as navigational and wardriving software) can share
access to a GPS without contention or loss of data.  Also, gpsd
responds to queries with a format that is substantially easier to parse
than NMEA 0183.  A client library is provided for applications.

After installing this RPM, gpsd will automatically connect to USB GPSes
when they are plugged in and requires no configuration.  For serial
GPSes, you will need to start gpsd by hand.  Once connected, the daemon
automatically discovers the correct baudrate, stop bits, and protocol.
The daemon will be quiescent when there are no clients asking for
location information, and copes gracefully when the GPS is unplugged
and replugged.



Authors:
--------
    Remco Treffkorn <remco@rvt.com>
    Derrick J. Brashear <shadow@dementia.org>
    Russ Nelson <nelson@crynwyr.com>
    Eric S. Raymond <esr@thyrsus.com>
    Gary E. Miller <gem@rellim.com>
    Jeff Francis <jeff@gritch.org>
    Amaury Jacquot <sxpert@esitcom.org>                                                                                                         
    Chris Kuethe <chris.kuethe@gmail.com>                                                                                                       
    Ville Nuorvala <vnuorval@tcs.hut.fi>                                                                                                        
Distribution: openSUSE 11.2 

  

OOps! Is this a left over from my 11.2 not udated during upgrade?
Comment 12 Forgotten User 7Vd19u3Vod 2010-10-26 19:07:20 UTC
After removing the ozerocdoff package the number of these messages reduced to a few.
After removing gpsd as well (I don't need GPS on my desktop) all those messages disappeared.
Comment 13 Joerg Reuter 2010-10-27 08:04:22 UTC
Next "zypper up" might pull it in again though if some package probably still has a dependency to gpsd-2.37 (likely also an old one.) OTOH, if "zypper rm" didn't complain, it probably was really just an artifact.