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.
Hello!
I upgrade 13.37 to 14.0 rc3 today.
And found some strange message in syslog Aug 28 13:04:52 router udevd[1481]: IMPORT{} type missing, ignoring IMPORT /lib/udev/rules.d/79-fstab_import.rules:1
Aug 28 13:04:52 router udevd[1481]: RUN+="socket:..." support will be removed from a future udev release. Please remove it from: /lib/udev/rules.d/90-hal.rules:2 and use libudev to subscribe to events.
Aug 28 13:04:53 router udevd[1501]: could not find module by name='rtc_cmos'
This is normal, or need some edit or adjust system?
I think this bit from CHANGES_AND_HINTS.TXT would fix your "rtc_cmos" message.
Quote:
If you are upgrading (as opposed to a new install), there are some stale files
in /etc/modprobe.d/ that you will need to remove: blacklist.conf,
bluetooth.conf, isapnp.conf, psmouse.conf, and usb-controller.conf
See /etc/modprobe.d/README for a more detailed explanation.
Although the thread is a tad old, I ran across this recently after I began updating another system. To resolve the problem, open /etc/modprobe.d/isapnp.conf with a text editor and comment out the following:
I think that's because you still have files in /etc/modprobe.d/: this folder, from 14.0 on, should start empty and contain just the customizations that override the configurations in the default scanned folder, /lib/modprobe.d/ (in /lib/modprobe.d/isapnp.conf that line is already commented out ).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.