Hi, Are you bound to the 2.4.20 kernel? If not you could upgrade to 2.6.x and use the flexcop-driver. Or you use the skystar2-driver in 2.4, but it doesn't have ATSC support. Anyway, the driver you are using is the proprietary driver (with a proprietary API in Linux) from B2C2. This driver is discontinued and incompatible with all linux DVB-API applications. Again, if you can don't use the B2C2-driver and migrate to a newer linux and use the OpenSource-driver. HTH, Patrick. On Thu, 14 Jul 2005, kim young hun wrote: >> On Thursday 14 July 2005 08:59, kim young hun wrote: > >>> I made special device file with below command according to advise of >>> product comapny's partner (www.bbti.us) >>> >>> # mknod /dev/B2C2AV.TS c 254 0 >>> # mknod /dev/B2C2AV.VID c 254 1 >>> # mknod /dev/B2C2AV.AUD c 254 > >> I have no experience of this card - this is generic Linux advice. > >> execute 'cat /proc/devices' and make sure you see the card at device '254' ... >> if you see it at 253, 252, 251 etc. then you must 'mknod' for that major >> device number. > >> Cheers, >> Gavin. > > Thank for your reply. > I executed 'cat /proc/devices', but I didn't find the information of card. > the result is below. > > > [root@61-250-140-101 root]# cat /proc/devices > Character devices: > 1 mem > 2 pty > 3 ttyp > 4 ttyS > 5 cua > 7 vcs > 10 misc > 13 input > 14 sound > 29 fb > 36 netlink > 109 lvm > 128 ptm > 129 ptm > 130 ptm > 131 ptm > 132 ptm > 133 ptm > 134 ptm > 135 ptm > 136 pts > 137 pts > 138 pts > 139 pts > 140 pts > 141 pts > 142 pts > 143 pts > 162 raw > 180 usb > > Block devices: > 1 ramdisk > 2 fd > 3 ide0 > 7 loop > 9 md > 12 unnamed > 14 unnamed > 22 ide1 > 38 unnamed > 39 unnamed > 58 lvm > [root@61-250-140-101 root]# ls -al /dev/ | grep B2C2 > crw-r--r-- 1 root root 254, 2 7month 13 19:24 B2C2AV.AUD > crw-r--r-- 1 root root 254, 0 7month 13 19:23 B2C2AV.TS > crw-r--r-- 1 root root 254, 1 7month 13 19:23 B2C2AV.VID >
