Some issues with RC1 and old ones.
 

Hello all! Congratulations for the good job and i am waiting the new Slack soon and sane!
With respect to all of the problem-solving people i want to share some issues, which i am not able to dissolve alone.
The system is Slackware64-current, up to date - RC1.
1) when the system boot, there is a message in the console:
"Starting udev events: /sbin/udevadm trigger --action=add
udevd[1071]: could not find module by name -"rtc_cmos"
udevd[....] worker [....] timeout, kill it
udevd: seq 1211 '/devices/ pc i0000:00/0000:00:1c.0/0000:02.0' killed"
This takes long time, may be about 5-6 seconds, then the boot process continue normally. Later i can see in dmesg this line:
5.195579] rtc_cmos 00:04: setting system clock to 2012-08-10 22:39:39 UTC (1344638379)
When i boot custom kernel this appear immedeately after the system start and with the generic kernel - later, a second or 2 befor the grafic login screen appears. I saw that for first time with 3.2.21 kernel, may be the time udev was upgrated. So i think it is somehow related to udev.
2) I use Xfce-4.10 from the official tree and i have some problems mounting devices.
I have a 3g usb modem, HUAWEY E173, wich has 2 slots - for sim card, which is used for internet connection, and a microSD slot which is used as a storage device. I use that slot to connect the microSD card from my telefon. The device seems to be mounted and can be opened with Dolphyn or accessed in console terminal, but trying open it with Thunar gives an error: Device is not accessible" even when i try with Thunar started with root privilages.
No problems hire to mount a usb memory stick and access it with Thunar.
3)Clipboard. When i copy something with the mouse i am not able to place it with a key-combination (Ctrl+V); this appears betwean any two program windows.
4)network-manager-applet. After login in the system there is a boring dialog window asking me to write my wallet password. Can i stop this? :)
5)Multilib, compiling a program in 32 bit mode. I am trying to cimpile freetype and the other font related programs in compat32 packages having nice fonts in skype. I fallow Erik Hameleer's instructions: 1) ". /etc/profile.d/32.dev.sh" and 2) remove the "64" from LIBDIRSUFFIX in the SlackBuild. When the process reaches the moment searching for gcc, something fell the RAM and slap memory, and in a minute or two the system is going out of control - no reaction to keyboard or mouse, even sysrq key combination is not able to place the keyboard under control and to restart the system. Htop is showing a lot of gcc processes each eating 1% of the cpu. Do i miss something or mess where is not my place? :)
If more information is needed i should be happy to receive an instruction how to obtain it. Thanks to all in advance!

1. Did you compile your custom kernel with RTC support?

I think so. I use the official config and only remove some hardware drivers, which are redundant on my system.
But as i said, it occur also with the generic kernel.

you can test it by using

It's long:

CONFIG_HPET_EMULATE_RTC=y
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set
# RTC interfaces
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
CONFIG_RTC_INTF_DEV_UIE_EMUL=y
CONFIG_RTC_DRV_TEST=m
# I2C RTC drivers
CONFIG_RTC_DRV_DS1307=m
CONFIG_RTC_DRV_DS1374=m
CONFIG_RTC_DRV_DS1672=m
CONFIG_RTC_DRV_DS3232=m
CONFIG_RTC_DRV_MAX6900=m
CONFIG_RTC_DRV_RS5C372=m
CONFIG_RTC_DRV_ISL1208=m
CONFIG_RTC_DRV_ISL12022=m
CONFIG_RTC_DRV_X1205=m
CONFIG_RTC_DRV_PCF8563=m
CONFIG_RTC_DRV_PCF8583=m
CONFIG_RTC_DRV_M41T80=m
CONFIG_RTC_DRV_M41T80_WDT=y
CONFIG_RTC_DRV_BQ32K=m
CONFIG_RTC_DRV_S35390A=m
CONFIG_RTC_DRV_FM3130=m
CONFIG_RTC_DRV_RX8581=m
CONFIG_RTC_DRV_RX8025=m
CONFIG_RTC_DRV_EM3027=m
CONFIG_RTC_DRV_RV3029C2=m
# SPI RTC drivers
# Platform RTC drivers
CONFIG_RTC_DRV_CMOS=y
CONFIG_RTC_DRV_DS1286=m
CONFIG_RTC_DRV_DS1511=m
CONFIG_RTC_DRV_DS1553=m
CONFIG_RTC_DRV_DS1742=m
CONFIG_RTC_DRV_STK17TA8=m
CONFIG_RTC_DRV_M48T86=m
CONFIG_RTC_DRV_M48T35=m
CONFIG_RTC_DRV_M48T59=m
CONFIG_RTC_DRV_MSM6242=m
CONFIG_RTC_DRV_BQ4802=m
CONFIG_RTC_DRV_RP5C01=m
CONFIG_RTC_DRV_V3020=m
CONFIG_RTC_DRV_PCF50633=m
# on-CPU RTC drivers

cd /boot/initrd-tree/lib/udev/
file *

You can see udev-add-printer it needs python

Another script wants tcl. Some parts of udev fail from inside the initrd without dependencies added to the initrd-tree. I had to add the whole bash packages to my initrd-tree to make one of the udev rules IMPORT{program} lines work.

udev is a little messy in this way where different rules want to use different shells and script languages

I'm not sure why udevd is wanting to load module rtc-cmos, but it is listed in /lib/modules/$(uname -r)/modules.builtin

If you don't need rtc_cmos just blacklist it. I had the same message show up and I know I don't need it, so I added the following to the top of /etc/modprobe.d/blacklist.conf
You shouldn't see the message on the next boot.

Same issue with rtc_cmos here. I have three boxes, all running 64-current and stock kernel.

1st box uses an initrd and gives me the rtc_cmos error. FUJITSU SIEMENS ESPRIMO EDITION P2540
2nd box uses an initrd and doesn`t give me the rtc_cmos error. FUJITSU ESPRIMO P2550
3rd box uses the huge kernel without an initrd and gives me the rtc_cmos error. FUJITSU PRIMERGY TX100 S1

This error message is a result of the module alias definitions in /lib/modprobe.d/isapnp.conf. I've sent a query to Pat asking whether these still have any value, but in the meantime, if you copy /lib/modprobe.d/isapnp.conf into directory /etc/modprobe.d and then remove the aliases relating to the rtc it should stop the error message.

Good catch! Apparently with 14.0 isapnp.conf is under /lib/modprobe.d, but in 13.37 it is under /etc/modprobe.d. Since I did an upgrade I had it in both places and the default file was being used. Taking out the rtc_cmos entries and any others should make it so I don't need to blacklist them. Thanks!