[linux-dvb] Re: "Unable to get major 212"

["Kilian A. Foth" <foth@informatik.uni-hamburg.de>]

Kilian A. Foth writes:

 > [...]
 > 
 > $ ./insmod.sh load
 >   Inserting DVB modules into kernel
 >   FATAL: Module crc32 not found.
 >   FATAL: Module evdev already in kernel.
 >   insmod: error inserting './dvb-core.ko': -1 File exists
 > 
 > And dmesg says:
 > 
 >   Linux video capture interface: v1.00
 >   dvb-core: unable to get major 212
 >   ttusbdecfe: falsely claims to have parameter debug
 >   saa7146: register extension 'dvb'.
 >   saa7146: register extension 'budget dvb'.
 >   saa7146: register extension 'budget_ci dvb'.
 >   saa7146: register extension 'budget dvb /w video in'.
 >   usbcore: registered new driver Technotrend/Hauppauge USB-Nova
 >   usbcore: registered new driver ttusb-dec
 >   usbcore: registered new driver dvb_dibusb
 >   usbcore: registered new driver cinergyT2
 > 
 > And sure enough, the device isn't there:
 > 
 >   ./scan dvb-t/de-Berlin 
 >   scanning dvb-t/de-Berlin
 >   using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
 >   main:1882: FATAL: failed to open '/dev/dvb/adapter0/frontend0': 19 No such device
 > 
 > I did run MAKEDEV-DVB.sh, and my /etc/modules.conf says alias
 > char-major-212 dvb-core. What does "unable to get major 212" actually
 > mean, and what does one do about it?
 > 

OK, for the sake of the archives...

My dumb mistake was that during the various attempts to get the right
modules compiled I ended up having dvb-core both compiled into the
kernel and as a module - therefore insmod fails saying that someone is
already providing the device number char-major-212.

I haven't actually gotten as far as actually getting the card
recognized by any driver, so I *will* be back with more questions, but
in a new thread.