You are not logged in.
After recent upgrade I started to get a warning on boot:
$ grep -F nvram /var/log/boot
Fri Nov 25 13:24:05 2011: :: Waiting for UDev uevents to be processed [BUSY] udevd[241]: kernel-provided name 'nvram' and NAME= 'misc/nvram' disagree, please use SYMLI
Seems that it's caused by /etc/udev/rules.d/tpb.rules, which I created (long time ago, when I installed Arch) according to https://wiki.archlinux.org/index.php/ThinkPad_OSD
$ cat /etc/udev/rules.d/tpb.rules
KERNEL=="nvram", NAME="misc/%k", SYMLINK+="%k", MODE="0660", GROUP="users"
Can someone suggest what I should do to eliminate the warning? I don't understand what the warning message tries to tell me on boot time.
Feel free to tell me if I should choose other forum for this topic.
Last edited by statc (2011-11-26 18:37:20)
Offline
I do not get the error and here is what I have in /etc/udev/rules.d/51-arch.rules
KERNEL=="nvram", NAME="misc/%k", SYMLINK+="%k", GROUP="kmem", MODE="0666"I have nvram in the DAEMONS line of /etc/rc.conf
It's all irrelevant to me though because tbp refuses to work. I got xosd to work by installing xosd-2.2.14 from source, but I can't get tpb to work.
Offline
I do not get the error and here is what I have in /etc/udev/rules.d/51-arch.rules
KERNEL=="nvram", NAME="misc/%k", SYMLINK+="%k", GROUP="kmem", MODE="0666"I have nvram in the DAEMONS line of /etc/rc.conf
It's all irrelevant to me though because tbp refuses to work. I got xosd to work by installing xosd-2.2.14 from source, but I can't get tpb to work.
nvram is a module, not a daemon. I can only assume you're not actually paying attention to your logs or bootup messages, because NAME= rules are forbidden by the kernel and rc.multi will throw an error about your bogus daemon name.
Offline
nvram is a module, not a daemon. I can only assume you're not actually paying attention to your logs or bootup messages, because NAME= rules are forbidden by the kernel and rc.multi will throw an error about your bogus daemon name.
I am not seeing any error messages related to NAME= or nvram.
Right file, wrong place: you are correct about nvram being a module - I misread the wiki page.
Regarding NAME= rules being forbidden, I didn't know that. The Wiki page for Arch ThinkPad OSD says to put it in there.
https://wiki.archlinux.org/index.php/ThinkPad_OSD
At any rate, the tpb OSD still doesn't work for me.
Offline
It's me again. I removed NAME="misc/%k" and on the next boot got a different warning:
Sun Nov 27 13:40:58 2011: :: Waiting for UDev uevents to be processed [BUSY] udevd[246]: device node '/dev/nvram' already exists, link to '/dev/nvram' will not overwriIf I remove tpb.rules completely, after reboot tpb stops working, maybe because of different access rights:
$ ls -l /dev/nvram
crw-r----- 1 root kmem 10, 144 2011-11-27 13:42:58 /dev/nvram
So, the problem is not solved.
David Batson: tpb is working for me (with tpb.rules given above and "nvram" in MODULES). It even works despite of the warning about nvram during boot.
Offline
I also removed the SYMLINK= part, and the warning disappeared, and OSD works. Thanks for your help!
For reference, my /etc/udev/rules.d/tpb.rules now contains
KERNEL=="nvram", MODE="0660", GROUP="users"Offline
Maybe tpb OSD just doesn't work with the Lenovo X220 ThinkPad or with XFCE. I had it working in the past with my T42 ThinkPad in Fedora 14 Gnome (2) and Mandriva 2010.2 KDE. When I get a chance in some weeks from now, maybe I'll install Arch XFCE on there and see if tpb OSD works.
Offline