Tiny Core Base > Corepure64
How do I get rid of udev messages during boot?
nurbles:
I've got just about everything working on my fresh new TinyCorePure64-14.0 system. I've noticed some unexpected messages during boot. The first messages flash up and disappear too fast to capture in between the BIOS messages and the screen that starts with the TinyCore version number, but I think they are some sort of failure -- clearly non-fatal, but that type of messages doesn't look good to customers. :)
I took a photo of the first page of the longer set of messages. They appear between 'loading modules...' and the GUI starting up. There is at least a screenful of these, perhaps more. They're only visible for a second or two, so not a real problem, except again for customer optics: Apparent(?) Warning/Error messages never look good to customers. :( Here's what I see (transcribed by hand from a photo because the POST button stopped working after the preview showed that I'd added the photo correctly):
Loading extensions...udevd[164]: IMPORT{builtin}: 'hwdb --subsystem:input '--loo
kup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libuacon.ru
les:18
udevd[164]: IMPORT{builtin): 'hwdb --subsystem:input '--lookup-prefix:libwacon:n
ame:$ATTR{name}:'' unknown /etc/udev/rules.d/65-libuacon.rules:18
udevd[164]: IMPORT{builtin): 'hwdb --subsystem:input '--lookup-prefix:libwacon:n
ame:$ATTR{name}:'' unknown /etc/udev/rules.d/65-libuacon.rules:18
udevd[164]: IMPORT{builtin): 'hwdb --subsystem:input '--lookup-prefix:libwacon:n
ame:$ATTR{name}:'' unknown /etc/udev/rules.d/65-libuacon.rules:18
udevd[164]: IMPORT{builtin): 'hwdb --subsystem:input '--lookup-prefix:libwacon:n
ame:$ATTR{name}:'' unknown /etc/udev/rules.d/65-libuacon.rules:18
Whatever all these messages mean, they don't appear to be affecting anything that we care about, if they are affecting anything at all.
jazzbiker:
Hi nurbles,
You may turn the system log on, adding for example "syslog loglevel=3" bootcodes to Your bootloader config. If I am not mistaken You installed TC with the help of official installer?
Rich:
Hi nurbles
It has something to do with hwdb:
https://forum.tinycorelinux.net/index.php/topic,25577.0.html
curaga:
The first messages are from your bootloader, just reporting it loaded the kernel and so on. How to remove those depends on your bootloader.
nurbles:
@jazzbiker: Thanks! Adding the syslog settings you provided moved the messages from the boot screen to /var/log/messages where I can now report that the ERROR occurs 18 times in a row (I included a couple lines before and after the messages for context in case someone familiar with the TC boot process looks at this):
--- Code: ---Jul 31 07:21:08 box authpriv.notice sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/chown -R root.staff /usr/local/tce.installed
Jul 31 07:21:08 box authpriv.notice sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/chmod -R 775 /usr/local/tce.installed
Jul 31 07:21:08 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:08 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:08 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:08 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:10 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:10 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:10 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:10 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:10 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:19 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:19 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:19 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:19 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:19 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:19 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:19 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:19 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:19 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:19 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:19 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:19 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:19 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:19 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:19 box daemon.err udevd[164]: IMPORT{builtin}: 'hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'' unknown /etc/udev/rules.d/65-libwacom.rules:18
Jul 31 07:21:20 box authpriv.notice sudo: root : TTY=console ; PWD=/ ; USER=root ; COMMAND=/bin/tar -C / -zxf /mnt/sda1/tce/mydata.tgz
Jul 31 07:21:20 box daemon.info init: starting pid 6053, tty '/dev/tty1': '/sbin/getty -nl /sbin/autologin 38400 tty1'
--- End code ---
All errors are referring to the uncommented line (from /etc/udev/rules.d/65-libwacom.rules) that starts with KERNELS:
--- Code: ---# use the /sys/class/input/eventXXX/device/modalias as lookup key, prefixed
# by libwacom:<device name>:
# This lookup key is a contract between the udev rules and the hwdb entries.
# It is not considered public API and may change.
KERNELS=="input*", IMPORT{builtin}="hwdb --subsystem=input '--lookup-prefix=libwacom:name:$attr{name}:'"
--- End code ---
It makes me wonder if the comment is correct and whatever this is doing has changed, making this line no longer correct?
So, the messages are now hidden from the boot screen, but are now clearly listed as 18 ERRORS in /var/log/messages. Overall, this is a big improvement, but I would prefer messages that are informational or warnings at the worst when my embedded system boots. The developers may know for certain that these errors are "innocuous" for John Q. Customer almost certainly WILL NOT.
Navigation
[0] Message Index
[#] Next page
Go to full version