Problems with Leadtek PVR 2000 card/driver and tv programs in Slackware 13.37
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Problems with Leadtek PVR 2000 card/driver and tv programs in Slackware 13.37
Hello,
I have the following problem:
I am using Leadtek PVR 2000 (RO) and when it loads the kernel sometimes it reports that it detected it but it waits 120 s. The same when it reaches the 'udeadm ... -type= failed'. But there are times when the kernel boots normaly, without this waiting time. I have 2 questions.
1. Is there any way to stop this module detection at boot time, i didn't found any kernel-module config file for this module that seems to be loaded.
2. Is there any way to make the card work, to configure it properly? I noticed that it makes reference to cx88 card type and seemingly the video4linux driver. Also, is there a tv application that works under Slack13.37? I have tried tvtime and xawtv but without success.
you have to drop the firmware that the kernel asks for at boot up time into /usr/lib/firmware and reboot then to get you .azap/channels.conf file do: scan /usr/share/dvb/atsc/us-ATSC-center-frequencies-8VSB > ~/.azap/channels.conf note: you'll probably want to symlinke that file into the following directories. .mplayer/ .vlc/ .tzap/ .xine/ you get the scan program & the firmware from: http://linuxtv.org/wiki/index.php/Zap
thanks for the response.
i have installed dvb-apps package. i don't know what file to put into /usr/lib/firmware. i noticed that there are the following sylinks:
cx88[0]/2-bb: Firmware and/or mailbox pointer not initialized or corrupted
cx88[0]/2-bb: ERROR: Hotplug firmware request failed (v4l-cx2341x-enc.fw).
cx88[0]/2-bb: Please fix your hotplug setup, the board will not work without firmware loaded!
i don't know where to get the v4l-cx2341x-enc.fw firmware from. I've found this archive http://dl.ivtvdriver.org/ivtv/firmwa...irmware.tar.gz which is said to contain the firmware but the archive is corupted. Any suggestion?
I've found the firmware on ubuntu. Now, on boot-up, it passes over the first point where it stayed for 120s before, but at the second point, the one with 'udevadm', it still waits, most of the boots. Here is the output:
(Note: video1 is a directory) ls -lra:
total 0
-rw-r--r-- 1 root root 4096 Nov 30 2011 uevent
lrwxrwxrwx 1 root root 0 Nov 30 2011 subsystem -> ../../../../../../class/video4linux/
drwxr-xr-x 2 root root 0 Nov 30 14:35 power/
-r--r--r-- 1 root root 4096 Nov 30 14:35 name
-r--r--r-- 1 root root 4096 Nov 30 14:35 index
lrwxrwxrwx 1 root root 0 Nov 30 14:35 device -> ../../../0000:01:01.2/
-r--r--r-- 1 root root 4096 Nov 30 14:35 dev
drwxr-xr-x 3 root root 0 Nov 30 2011 ../
drwxr-xr-x 3 root root 0 Nov 30 2011 ./
Now, i noticed there is a red link at: /dev/.udev/failed
The command 'ls -lra' shows:
total 0
lrwxrwxrwx 1 root root 64 Nov 30 14:17 video4linux:video1 -> /devices/pci0000:00/0000:00:1e.0/0000:01:01.2/video4linux/video1
So, the pointed file doesn't exist.
Now, here is a short fregment of the output of the dmesg:
Now, about the scan program, here is the result of running the command: 'scan /usr/share/dvb/dvb-t/ro-Bucharest':
scanning /usr/share/dvb/dvb-t/ro-Bucharest
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
main:2705: FATAL: failed to open '/dev/dvb/adapter0/frontend0': 2 No such file or directory
I'm at a loss here to be honest. The fact that udev is erroring and why you have dead links in your /dev is beyond me. The way I told you to get it working works for me, sorry to say.
I can tell you that without a proper /dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0 you will get no where fast So you're going to have to figure out what is going on with udev.
Do you have a 'full installation'? custom kernel? Maybe try a different PCI slot on the computer?
One thing I failed to mention in response to your original post is a good app to use (once you get it working) which is kaffeine which you can get buildscripts from Slackbuilds.org
Thanks a lot for your help. I'll see what can i do about this problem. Yes, it's a full installation of Slackware 13.37, with the default kernel, which works fine. I think the firmware might be the problem. You may be right about the PCI slot, i'll try another one, now it's not on the first one that's for sure. I'll see which one is the first ... and hope it will work.
Thank's for the tip about kaffeine. Anyway, do you know what app is good for Analog TV cable? I have both sygnal systems: digital and analog on the same cable, the digital one is decoded first, with a special device, before entering tv.
i have discovered another thing. when on successful boot-up, that means without the failure message from udev and without the 120 s waiting time, which has happened rarely, i looked into /dev/v4l/by-path/ and here there are now 3 symlinks instead of 2, like i metioned before. Now, there are /dev/vbi0, /dev/video0 and /dev/video1 (the 3 pointed files instead of 2, on failed boot-up). So, i looked to see on what PCI # is the card put on and it is on the 2-nd one. So, about the /dev/video1 linked to,the driver&firmware might have just recognized it and created the link to it.
About changing the card to the first PCI, i have tried but it messes with the bios setup in linux and apparently in windows too. So for this change to the system to be done, i need to install both of the OS-s again. So i guess i'll let it this way for now.
ok, i have changed the slot of the card with success and now the dead links are gone. This is the first boot without errors, i hope the next ones will be the same. It seems that the card is finally well configured. Now it remains to see what can be done with the apps.
WOW ! great news so far then Regarding analog tv, kaffeine will do that also. But I also use "tvtime" for analog tv as well. Alien Bob has a nice package at his site, and I believe that Slackbuilds.org has build scripts as well. Regarding windows, I would think that since your drivers are already installed once windows should pick it up on first boot in. Let's just hope that they dont hard code pci slot into the registry on some of the apps that came with the card, else yeah, you might have to reinstall the card in windows. But I would think that you should *not* have to do a full reinstall of windows. Good Luck
i have installed kafeine. it works but it doesn't have analog tv and the digital part has scanning button inactive. It is version 1.2.2. With tvtime, i couldn't find a working package. I would try too see analog tv with mplayer but i dont know the exact command to use. About the card config at linux boot, it might still be problems. Until now it detected and configured about 3 times well and 1 time bad. I'll see tomorrow, after cold booting how it works again. At least i know i found and supplied the firmware, for which i thank you again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.