OS: Suse 9.3 PRO I recently purchased the Hauppauge WinTV tv card. After installation the system seemed to recognize the card, but not its tuner. Using YAST "Manual TV selection" I've done the following: Vendor: Hauppauge Card: Hauppauge bt878 (chip on the card is Conexant 878a) Choose Tuner: Default (system then indicates tuner default (detected)) TV Channels: TV Norm: NTSC Frequency Table: us-cable I then "Scan the Channels" and get the following: ERROR: The kernel module for TV support could not be loaded SHOW DETAILS: sh: "card":"10":"tuner":-1": syntax error: operand expected (error token is "card":"10", "tuner":"-1") I have played around selecting other tuner options ... but no joy. Any suggestions/guidance would be appreciated. Bill
Hi William, I had a similar problem with my WinTV-GO under SuSE 9.3 along with a lot of other hardware and general stability problems that were all tied to the same thing: ACPI. Here are a couple of things to look into: 1. If you can, check you /var/log/messages for errors assigning an IRQ (or any other resource allocation errors for that matter) to you tv tuner (bt878). 2. Disable ACPI in your boot loader (by default GRUB). For your default SuSE 9.3 boot option if you don't already see acpi=off as one of your kernel parameters, put it in there and reboot the computer. I hope this helps. --Jason Snyder-- On Thursday 26 May 2005 13:23, William E. Shotts wrote:
OS: Suse 9.3 PRO
I recently purchased the Hauppauge WinTV tv card. After installation the system seemed to recognize the card, but not its tuner. Using YAST "Manual TV selection" I've done the following:
Vendor: Hauppauge Card: Hauppauge bt878 (chip on the card is Conexant 878a) Choose Tuner: Default (system then indicates tuner default (detected)) TV Channels: TV Norm: NTSC Frequency Table: us-cable
I then "Scan the Channels" and get the following: ERROR: The kernel module for TV support could not be loaded SHOW DETAILS: sh: "card":"10":"tuner":-1": syntax error: operand expected (error token is "card":"10", "tuner":"-1")
I have played around selecting other tuner options ... but no joy.
Any suggestions/guidance would be appreciated.
Bill
On Friday 27 May 2005 01:22 pm, Jason Snyder wrote:
Hi William, I had a similar problem with my WinTV-GO under SuSE 9.3 along with a lot of other hardware and general stability problems that were all tied to the same thing: ACPI. Here are a couple of things to look into:
1. If you can, check you /var/log/messages for errors assigning an IRQ (or any other resource allocation errors for that matter) to you tv tuner (bt878).
2. Disable ACPI in your boot loader (by default GRUB). For your default SuSE 9.3 boot option if you don't already see acpi=off as one of your kernel parameters, put it in there and reboot the computer.
I hope this helps.
--Jason Snyder--
On Thursday 26 May 2005 13:23, William E. Shotts wrote:
OS: Suse 9.3 PRO
I recently purchased the Hauppauge WinTV tv card. After installation the system seemed to recognize the card, but not its tuner. Using YAST "Manual TV selection" I've done the following:
Vendor: Hauppauge Card: Hauppauge bt878 (chip on the card is Conexant 878a) Choose Tuner: Default (system then indicates tuner default (detected)) TV Channels: TV Norm: NTSC Frequency Table: us-cable
I then "Scan the Channels" and get the following: ERROR: The kernel module for TV support could not be loaded SHOW DETAILS: sh: "card":"10":"tuner":-1": syntax error: operand expected (error token is "card":"10", "tuner":"-1")
I have played around selecting other tuner options ... but no joy.
Any suggestions/guidance would be appreciated.
Bill
-- Louis Richards
On Fri, 27 May 2005, Jason Snyder wrote:
Hi William, I had a similar problem with my WinTV-GO under SuSE 9.3 along with a lot of other hardware and general stability problems that were all tied to the same thing: ACPI. Here are a couple of things to look into:
The problem is that these don't use the bttv module. I have a Hauppauge WinTV-250. While SuSE have installed the kernel module (IVTV), it (a) dosen't show up in YaST and (b) installs the firmware it needs to operate in the wrong directory. To get it working I had to do the following steps: 1. Copy the firmware modules from /etc/modules to /etc/firmware - these are the files ivtv-fw-enc.bin and ivtv-fw-decode.bin 2. Do the following commands: lsmod (if ivtv shows up on the list skip to 3) modprobe ivtv depmod 3. Test it: cat /dev/video0 > my.mpg 4. If this works you can add /sbin/modprobe ivtv to your boot script. If this doesn't work, there's more information at http://ivtv.writeme.ch/tiki-index.php Oh and if you can get one of these cards working in any of the included tv programs, please let me know. I've been running it in MPlayer using a script from the tar download to change channels which isn't ideal (and a pain in the neck to get running). Good Luck Hilary Hilary L. Hertzoff From here to there, Mamaroneck Public Library a bunny goes where a bunny must. Mamaroneck, NY - Little Bunny on the Move hhertzof@panix.com by Peter McCarty
Hi Hilary, There is a big difference between the WinTV-250 PVR and the WinTV-GO. The WinTV-GO DOES use the bttv drivers while the WinTV-250 PVR does not. I actually specifically went after the WinTV-GO specifically for this reason. By the way I use mplayer to. I am actually stuck on a copy I custom compiled a while back (MPlayer-1.0pre5-pm.2.athlon.rpm) running under SuSE 9.2 because I cannot get the newer versions of mpalyer to initialize the capture card properly, SuSE 9.3 doesn't seem to come with the proper libraries, and I have been trying to avoid dependency hell. I have noticed under SuSE 9.2 and mplayer 1.0pre5 that if I first access the TV card under XawTV, close, and then open under mplayer 1.0pre5 it will work properly. Doing this on a mid range system (Athlon XP 3200) with filtering and encoding options up the ying yang yields results that are quite nice. I would like to hack a more recent version of mplayer to play well with TV tuners if I can find the time to do so. If you want to use the WinTV-250 PVR (mpeg2 encoder based as opposed to raw feed) you may want to check out MythTV. I have been reading on their website that they have been working on control modules for these types of cards. --Jason Snyder-- On Friday 27 May 2005 10:49, Hilary Hertzoff wrote:
On Fri, 27 May 2005, Jason Snyder wrote:
Hi William, I had a similar problem with my WinTV-GO under SuSE 9.3 along with a lot of other hardware and general stability problems that were all tied to the same thing: ACPI. Here are a couple of things to look into:
The problem is that these don't use the bttv module.
I have a Hauppauge WinTV-250.
While SuSE have installed the kernel module (IVTV), it (a) dosen't show up in YaST and (b) installs the firmware it needs to operate in the wrong directory.
To get it working I had to do the following steps: 1. Copy the firmware modules from /etc/modules to /etc/firmware - these are the files ivtv-fw-enc.bin and ivtv-fw-decode.bin
2. Do the following commands: lsmod (if ivtv shows up on the list skip to 3) modprobe ivtv depmod
3. Test it: cat /dev/video0 > my.mpg
4. If this works you can add /sbin/modprobe ivtv to your boot script. If this doesn't work, there's more information at http://ivtv.writeme.ch/tiki-index.php
Oh and if you can get one of these cards working in any of the included tv programs, please let me know. I've been running it in MPlayer using a script from the tar download to change channels which isn't ideal (and a pain in the neck to get running).
Good Luck Hilary
Hilary L. Hertzoff From here to there, Mamaroneck Public Library a bunny goes where a bunny must. Mamaroneck, NY - Little Bunny on the Move hhertzof@panix.com by Peter McCarty
On Friday 27 May 2005 16:04, Jason Snyder wrote:
Hi Hilary, There is a big difference between the WinTV-250 PVR and the WinTV-GO. The WinTV-GO DOES use the bttv drivers while the WinTV-250 PVR does not. I actually specifically went after the WinTV-GO specifically for this reason.
Ah, I hadn't realized that.
By the way I use mplayer to. I am actually stuck on a copy I custom compiled a while back (MPlayer-1.0pre5-pm.2.athlon.rpm) running under SuSE 9.2 because I cannot get the newer versions of mpalyer to initialize the capture card properly, SuSE 9.3 doesn't seem to come with the proper libraries, and I have been trying to avoid dependency hell. I have noticed under SuSE 9.2 and mplayer 1.0pre5 that if I first access the TV card under XawTV, close, and then open under mplayer 1.0pre5 it will work properly. Doing this on a mid range system (Athlon XP 3200) with filtering and encoding options up the ying yang yields results that are quite nice. I would like to hack a more recent version of mplayer to play well with TV tuners if I can find the time to do so.
Wish I could help you there. For 9.3 I used the packman package so you might want to try that one if you haven't already. http://packman.links2linux.org/?action=128
If you want to use the WinTV-250 PVR (mpeg2 encoder based as opposed to raw feed) you may want to check out MythTV. I have been reading on their website that they have been working on control modules for these types of cards.
I should. I tried it in 9.2 but I couldn't get it to compile properly. Dependancy hell. I've only had 9.3 running since Monday so I'm still tweaking things around. Good luck Hilary
participants (5)
-
Hilary Hertzoff -
Hilary L Hertzoff
-
Jason Snyder -
Louis Richards -
William E. Shotts