/etc/hotplug/firmware.agent defines /lib/firmware for files. This dir doesn't exist on my system. /usr/lib/hotplug/firmware/ does exist although I'm not sure if I created it at some time or if it is created on installation. Could this be the udev firware dir? tried experiment with ivtv 4.1 and it only works with /lib/firmware, not /usr/lib/hotplug/firmware. According to the ivtv docs this is because of firmware.agent FIRWARE_DIR=/lib/firmware. Do hotplug/coldplug users need to create the /lib/firmware dir manually or should firware.agent point to another dir? from firmware.agent: # directory of the firmware files FIRMWARE_DIR=/lib/firmware * sys-apps/hotplug Latest version available: 20040923-r1 Latest version installed: 20040923-r1 * sys-apps/hotplug-base Latest version available: 20040401 Latest version installed: 20040401 * sys-fs/udev Latest version available: 079-r1 Latest version installed: 079-r1 * sys-apps/baselayout Latest version available: 1.11.14-r3 Latest version installed: 1.11.14-r3 # emerge info Portage 2.0.54 (default-linux/amd64/2005.1, gcc-3.4.4, glibc-2.3.5-r2, 2.6.14-gentoo-r5 x86_64) ================================================================= System uname: 2.6.14-gentoo-r5 x86_64 AMD Athlon(tm) 64 Processor 2800+ Gentoo Base System version 1.6.14 dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 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 -O2 -pipe -fomit-frame-pointer" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.osuosl.org" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://192.168.2.184/gentoo-portage" USE="amd64 X a52 aac acpi alsa audiofile avi berkdb bitmap-fonts bzip2 crypt curl dvd dvdr dvdread emboss encode exif expat fam ffmpeg fftw flac font-server foomaticdb fortran gdbm gif gpm gstreamer gtk2 imlib ipv6 java jpeg kde kdeenablefinal lcms libwww lzw lzw-tiff mad mjpeg mng mp3 mpeg mysql mythtv ncurses nls nptl ogg oggvorbis opengl oss pam pcre pdflib perl png python qt quicktime readline sdl slang spell ssl tcpd threads tiff transcode truetype truetype-fonts type1-fonts udev usb userlocales v4l2 vorbis xine xml2 xpm xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
/lib/firmware is correct directory.
Ok, but shouldn't that dir exist? Why not have either hotplug or some other package create the proper dir?
(In reply to comment #2) > Ok, but shouldn't that dir exist? Why not have either hotplug or some other > package create the proper dir? Why should hotplug create such stuff? If you install some drivers that require and install firmware, then it will create the directory.