When I attah my dvb-t usb box before booting gentoo, the module is inserted during coldplugging and the firmware gets loaded as expected, but wrong device nodes are created: crw-rw---- 1 root root 212, 4 Mar 4 05:25 /dev/dvb0.demux0 crw-rw---- 1 root root 212, 5 Mar 4 05:25 /dev/dvb0.dvr0 crw-rw---- 1 root root 212, 3 Mar 4 05:25 /dev/dvb0.frontend0 crw-rw---- 1 root root 212, 7 Mar 4 05:25 /dev/dvb0.net0 (I would expect them in a directory dvb) When I detach the box and reattach it (hotplugging it) the module will get loaded but fails to load the firmware ... no device nodes will be created (which seems obvious, since the firmware loading fails and the additional modules needed won't be loaded). After issuing a rmmod and modprobing the dvb_dibusb module again, the firmware gets loaded, all needed modules are loaded, the device nodes are created but again in the wrong place. Obviously coldplugging the device is similiar to hotplugging it, the question though is, why the creation of the device nodes is not handled properly. In the case of hotplugging the question is: why does the firmware loading fail. See attachment for further info. Reproducible: Always Steps to Reproduce: 1. 2. 3. Portage 2.0.51.19 (default-linux/x86/2004.3, gcc-3.4.3-20050110, glibc-2.3.4.20050125-r0, 2.6.11-verfeiert i686) ================================================================= System uname: 2.6.11-verfeiert i686 Intel(R) Xeon(TM) CPU 2.66GHz Gentoo Base System version 1.6.9 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Mar 3 2005, 18:08:14)] ccache version 2.3 [enabled] dev-lang/python: 2.3.5 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.4_p6, 1.5, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r4 sys-devel/libtool: 1.5.10-r5 virtual/os-headers: 2.6.10 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium4" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=pentium4" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" LANG="en_US.utf8" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X X509 aac aalib acl acpi alsa aotuv artworkextra avi berkdb bidi bitmap-fonts cdparanoia cdr cjk crypt css cups curl dga directfb divx4linux djbfft doc dv dvd dvdr dvdread eds emboss encode esd f77 fam fbcon flac font-server foomaticdb fortran gcj gdbm gif gimpprint gnome gnutls gpm gstreamer gtk gtk2 gtkhtml guile hal howl idea ieee1394 imagemagick imlib ipv6 jack java javascript jpeg kerberos krb4 ldap libcaca libg++ libgda libwww lzo mad mikmod mmap mmx mmx2 motif mozilla mpeg nas ncurses network nls nntp nptl nptlonly nvidia objc odbc offensive oggvorbis opengl pam pcre pdflib perl png postgres pwdb python quicktime quotas readline real rtc ruby samba sdl sftplogging skey slang socks5 speex spell sse sse2 ssl svg tcltk tcpd tetex tga theora threads tiff truetype truetype-fonts type1-fonts unicode v4l v4l2 wmf xanim xml xml2 xmms xprint xv xvid xvmc zlib"Unset: ASFLAGS, CBUILD, CTARGET, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
Created attachment 52615 [details] Log extracts for hotplugging the box/modprobing the module afterwards
same firmware loading problems for me here. with manual rmmod/modprobe it is working.
Concernign the creation of the wrong inodes: From Time to time when the device is colplugged, the right inodes are created under /dev/dvb/adapter0 instead of /dev/dvb0.* . It doesn't seem to be reproducable in anyway, what causes which behaviour.
Take a look in /usr/src/linux/Documentation/dvb/udev.txt it tells you exactly how to setup udev to configure your device entries correctly. P.S. I believe that linuxtv-dvb has the required changes included, however I'm unable to install that for some reason.
udev is set up properly, as recommended in the text file, the script is there as well as the rules, yet, udev doesn't seems to always create the device nodes at the same place ... And yes, I did read the txt file coming with the dvb module and did put the firmware in all the possible locations ... and isn't it stunning - coldplugging works and loads the firmware and all modules, while hotplugging doesn't ...
Well, seems all of a sudden neither is working for me on a newly installed system, coldplugging/hotplugging.. nada. Works fine with devfsd but not udev. Seems the required changes are already present too. Puzzling.
Is this still an issue? If so, please reopen with new info.
