| View previous topic :: View next topic |
| Author |
Message |
serial_penguin
Tux's lil' helper
Joined: 23 Aug 2005
Posts: 96
Location: US / Minnesota
|
 Posted: Sat Sep 02, 2006 6:27 pm Post subject: udevd-events |
 |
|
I'm not sure if this is the best forum to post this but it does occur on an amd64 laptop. The following occurs during boot :
* letting udev process events ...
udevd-events[1983]: find_free_number: %e depricated, will be removed and is unlikely to work correctly. Don't use it.
* finalizing udev configuration
The above is typed since I'm unable to log the boot screen info. What does the "udevd-events" mean and how do I get rid of it? The number "1983" does occasionally change. I'm not sure when the statement first appeared. It may have been after a baselayout emerge. Here are the first few lines of
| Code: |
emerge --info
Portage 2.1-r2 (default-linux/amd64/2005.1, gcc-3.4.6, glibc-2.3.6-r4, 2.6.17-gentoo-r4 x86_64)
=================================================================
System uname: 2.6.17-gentoo-r4 x86_64 AMD Turion(tm) 64 Mobile Technology ML-37
Gentoo Base System version 1.12.4
app-admin/eselect-compiler: [Not Present]
dev-lang/python: 2.3.5-r2, 2.4.3-r1
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache: [Not Present]
dev-util/confcache: [Not Present]
sys-apps/sandbox: 1.2.17
sys-devel/autoconf: 2.13, 2.59-r7
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils: 2.16.1-r3
sys-devel/gcc-config: 1.3.13-r3
sys-devel/libtool: 1.5.22
virtual/os-headers: 2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=k8 -Os -pipe"
CHOST="x86_64-pc-linux-gnu"
...
|
|
|
| Back to top |
|
 |
PaulBredbury
Watchman
Joined: 14 Jul 2005
Posts: 7310
|
| Posted: Sat Sep 02, 2006 8:31 pm Post subject: |
|
|
See thread. I'd recommend:
|
|
| Back to top |
|
|
serial_penguin
Tux's lil' helper
Joined: 23 Aug 2005
Posts: 96
Location: US / Minnesota
|
| Posted: Sun Sep 03, 2006 10:03 pm Post subject: |
|
|
| PaulBredbury wrote: | See thread. I'd recommend:
|
udev- 087-r1 was installed, so I emerged udev-094. This seemed to remove the warning when booting. However, the new udev produced a nightmare relative to hotplugging my network interfaces. My wireless interface was assigned eth0 if my wired interface was unplugged, otherwise it was assigned eth1 and the wired was assigned eth0. I was unable to blacklist certain in-kernel wireless modules so that ndiswrapper could be used. The in-kernel module was always hotplugged. I suspect the warning is a "syntax" error in /etc/udev/rules.d/50-udev.rules, perhaps:
ENV{ID_CDROM}=="?*", SYMLINK+="cdrom%e", GROUP="cdrom"
ENV{ID_CDROM_CD_RW}=="?*", SYMLINK+="cdrw%e"
ENV{ID_CDROM_DVD}=="?*", SYMLINK+="dvd%e"
ENV{ID_CDROM_DVD_R}=="?*", SYMLINK+="dvdrw%e"
I'm not sure if it (the warning) has any implications. It would be nice to get rid of it and at the same time be able to consistently configure my network interfaces. Are there others using udev-087-r1 who see this same warning when udev processes events? |
|
| Back to top |
|
|
mark_alec
Bodhisattva
Joined: 11 Sep 2004
Posts: 6066
Location: Melbourne, Australia
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Duplicate Threads
