https://bugzilla.novell.com/show_bug.cgi?id=335108 Matej Horvath changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |ro@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=335108#c2 --- Comment #2 from Thomas Göbel 2007-10-22 05:40:48 MST --- Yes, the /usr/share/doc/packages/pcfclock/README file is available, but there is no description in that file, how to create the devices. The needed files are not delivered. /usr/share/doc/packages/pcfclock/README: .. Files you might look into: `COPYING' - copying conditions `INSTALL' - compilation and installation rules `NEWS' - major changes in the current version `THANKS' - list of contributors .. The modeprobe entry "alias char-major-181 pcfclock" is also absent! Sorry, my initial description was not clear. I have updated to opensuse 10.3 from 10.2. Then i have done a online update. Then i created the pcfclock devices (because i know that the devices ware never created in previous opensuse releases). Then i tried to get the date/time with "pcfclock -s" and i get: pcfdate: /dev/pcfclock0: No such address pcfdate: /dev/pcfclock1: No such device pcfdate: /dev/pcfclock2: No such device After some search i downloaded the src rpm, and created my own rpm. After have have installed this pcflock.rpm i recreated the pcfclock devices and it works. So the problem was NOT, that the devices was not present! The devices ware present but i get no date and time! Regards, Thomas -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=335108#c4 Ruediger Oertel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |kasievers@novell.com --- Comment #4 from Ruediger Oertel 2007-10-23 16:39:29 MST --- well, as mentioned before, the devices should be created after module load with the udev rule. Using access to a device to trigger a module load is no longer the method of choice with the use of udev. The question is how to trigger the load of this module, I'm not sure there is such a thing as autoprobing on the paralell port. Kay: any ideas ? pcfclock is a module to drive a dcf-clock that is attached to the parellel port (usually built in-line into the parport wire to the printer). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=335108#c6 --- Comment #6 from Ruediger Oertel 2007-10-23 17:01:10 MST --- okay, so I really have to resort to creating the device nodes in the package. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=335108#c8 Ruediger Oertel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #8 from Ruediger Oertel 2007-10-23 17:27:09 MST --- okay adding this to the spec file: install section: +mkdir -p $RPM_BUILD_ROOT/etc/modprobe.d +echo "alias char-major-181 pcfclock" > $RPM_BUILD_ROOT/etc/modprobe.d/pcfclock +mkdir -p $RPM_BUILD_ROOT/lib/udev/devices filelist: +/etc/modprobe.d/pcfclock +%dir /lib/udev +%dir /lib/udev/devices +%attr(444,root,root) %dev(c,181,0) /lib/udev/devices/pcfclock0 +%attr(444,root,root) %dev(c,181,1) /lib/udev/devices/pcfclock1 +%attr(444,root,root) %dev(c,181,2) /lib/udev/devices/pcfclock2 fixed for STABLE/FACTORY/11.0 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.