[linux-dvb] Re: Cant_locate_module_char-major-250

[Ewald Maier <ewaldmai@gmx.de>]

On Tue, 2 Oct 2001 17:07:47 +0200 (CEST), you wrote:

Hi Rolf!
>
I start vdr with the script runvdr as described here:
http://home.t-online.de/home/hubertus.sandmann/
(I have all made as here described)

>Well yes, you quoted them already... But there are no error messages
>originating directly from the dvbdev module. Under bad circumstances
>there may appear something like
>
>... kernel: video_dev: unable to get major 250
>
>But it does not here, so this part also seems to be correct. 
the confusing for me is, that the device is always busy and not
synced, but as we see below, it is synced:

-------------------------------------------------------
/usr/local/src/VDR/runvdr
/usr/src/linux/scripts/pathdown.sh: TOPDIR: parameter null or not set
./makedev.napi
make
make[1]: Entering directory `/usr/local/src/DVB/driver'
DIR=`pwd`; (cd /usr/src/linux; make SUBDIRS=$DIR modules)
make[2]: Entering directory `/usr/src/linux-2.4.4'
make -C  /usr/local/src/DVB/driver CFLAGS="-D__KERNEL__
-I/usr/src/linux-2.4.4/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe
-mpreferred-stack-boundary=2 -march=i586 -DMODULE" MAKING_MODULES=1
modulesmake[3]: Entering directory `/usr/local/src/DVB/driver'
make[3]: Nothing to be done for `modules'.
make[3]: Leaving directory `/usr/local/src/DVB/driver'
make[2]: Leaving directory `/usr/src/linux-2.4.4'

make[1]: Leaving directory `/usr/local/src/DVB/driver'
(       \
insmod dvbdev.o; \
insmod dvb_net.o;                \
insmod i2c-core; \
insmod videodev;                \
insmod dvb_filter.o;                \
insmod dmxdev.o;                \
insmod VES1893.o;               \
insmod VES1820.o;               \
insmod L64781.o;                \
insmod tda8083.o;               \
insmod stv0299.o;               \
insmod tuner.o;                 \
insmod saa7146_core.o mode=0;   \
insmod saa7146_v4l.o;           \
insmod dvb_demux.o;             \
insmod dvb.o init_chan=2 pids_off=0;    \
)
Using /lib/modules/2.4.4-4GB/kernel/drivers/i2c/i2c-core.o
Using /lib/modules/2.4.4-4GB/kernel/drivers/media/video/videodev.o
sync
--------------------------------------------------------
>!------------------------
>! Hi Messrs. Metzlers!
>!
>! What about changing
>!
>!	printk("video_dev: unable to get major %d\n", DVB_MAJOR);
>!
>! to
>!
>!	printk(KERN_ERR "dvbdev: unable to get major %d\n",DVB_MAJOR);
>!
>! ?
>!------------------------
This one I don't understand (I think it's a _Vorschlag_ for the
developer..)
>> > And look at /proc/devices: A line with a "250" in
>> >left column and an "ost/<xyz>" string in right column must be visible.

------------------------------------------------
bash-2.05# cat /proc/devices
Character devices:
  1 mem
  2 pty
  3 ttyp
  4 ttyS
  5 cua
  7 vcs
 10 misc
 14 sound
 29 fb
 61 lirc_serial
 81 video_capture
128 ptm
136 pts
162 raw
250 DVB

Block devices:
  1 ramdisk
  2 fd
  3 ide0
  7 loop
----------------------------------------------------------
the 250 DVB is here...
>> [...]
>> -r--r--r--    1 root     root            0 Oct  2 00:50 devices
>> [...]
>
>Those are pseudo files. Run "cat /proc/devices" and you will get an output
>even if they seem to have zero length. For a dvb-0.9 driver the relevant
>lines look like
>    Character devices:
>      [...]
>     81 video_capture
>      [...]
>    250 DVB
^^^^^^^^^^^^^^^^^^^^^^
it's all there (driver is 0.96)
>for a dvb-0.8 driver:
>      [...]
>     81 video_capture
>      [...]
>    249 ost/ca
>    250 ost/video
>    251 ost/sec
>    252 ost/audio
>    253 ost/qpsk_fe
>    254 ost/demux
^^^^^^^^^^^^^^^^^^^^^^
then this must not be here
>The problem you described is rather strange. Maybe it's an issue of the
>devfs support in your system. But I'm afraid I can't help you on that.
perhaps somebody else here has solved the problem (as I seen more
people have similar probs)
>vdr is even a big lump of software with countless accesses to devices in 
>/dev/ost. What about simpler apps like ntuxzap, tuxzap or the "test"
>programs from the driver package? Do they cause comparable lamentations?
I was not able to compile one of these without errors yet..
(as I seen http://home.t-online.de/home/hubertus.sandmann/ too..)
>

--
ICQ: 62200899


--
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe linux-dvb" as subject.