PDA

View Full Version : Hauppauge HVR-2250 With Mythbuntu



Pages : [1] 2

paulin
October 9th, 2008, 12:10 PM
Hello everyone.

Well I've finally decided to try and build my first PVR. Anyway I'm still in the early research phase and I'm stuck on the Capture Card. Anyway I found the Hauppauge HVR-2250 which seems like a good option. However I've been searching around to see if it is supported by Linux and MythTV.

Is anyone using it and how is it working?

Thanks
steve

paulin
October 9th, 2008, 04:16 PM
I did find this

http://www.gossamer-threads.com/lists/mythtv/users/343983



Re: Need a Dual turner Capture card for myCable, WinTV-PVR 500 is discontinued* CONFIRMED * so what do you recommend ?

well I started the thread so I will close it, I finally ended up buying the hauppauge 2250, linux drivers are on their way ( it is even stated on hauppauge webpage ), basically this will be the replacement for the PVR 500, since they are getting a lot of heat from FCC to not sell any cards that can't decode digital, as I said on a post before, I think this card will serve 2 purposes, first the intended one and second I could help do a lot of beta testing ( or even dust my old C knowledge and work a bit on the driver )

Thank you all for your responses.
Roberto.


But I'm still not sure if this answer if it fully works or not.

Thoughts or anyone using it?
steve

agamotto
October 13th, 2008, 02:59 AM
I did find this

http://www.gossamer-threads.com/lists/mythtv/users/343983




But I'm still not sure if this answer if it fully works or not.

Thoughts or anyone using it?
steve

No drivers as of today. I contacted Hauppauge about this a month or two back, and they don't do any in-house linux support for any of their product.

pompeyjohn
October 24th, 2008, 11:11 PM
according to the mythtv wiki work is preceding on getting this to work.

I have one of these cards, and I'll be using it for mythtv - until the, mediaportal it is...

pompeyjohn
November 5th, 2008, 02:16 AM
anybody have an update on this?

smgendler
January 10th, 2009, 07:15 PM
Development is on ice...which is very disappointing because it does look like the perfect tuner card. See http://article.gmane.org/gmane.linux.drivers.dvb/46504

janascii
March 3rd, 2009, 05:05 AM
The development may be starting up again. http://www.steventoth.net/blog/hvr-2250/ this is the blog of the developer that originally started the driver for the hvr-2250. Apparently enough people have been bugging him to start on the 2250 that he is accepting donations to work on the project. I'm keeping an eye on this before I buy the card. Thought others would want to know.

LowSky
May 24th, 2009, 07:46 AM
there seems to be a beta driver, but I have no idea how to install it, anyone care to help, http://www.steventoth.net/blog/products/hvr-2250/

I would live to get mythtv up and running.
I'm not really happy with Win7 media center

squidboy
May 24th, 2009, 06:13 PM
Use this to understand how to setup and build the drivers-

http://www.linuxtv.org/wiki/index.php/How_to_Obtain%2C_Build_and_Install_V4L-DVB_Device_Drivers


then this is where you get the drivers

http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-2250

Tell me if you have any luck!!
Thanks

LowSky
May 25th, 2009, 07:01 PM
Hello Mythbuntu users. Here is a new EDIT for 11.04 and 11.10.

I want to give credit to Sketchy's post: #420 (http://ubuntuforums.org/showpost.php?p=10980475&postcount=420) I'm pretty sure this works

No one should need to upload any kernel drivers using 11.04+, only the firmware is needed.

I created a link on my server to host all of the firmware versions made a while back and will host as long as possible. I may move them to a public dropbox location later. I will update if needed.


Grab the firmware.

wget -c http://www.robotbeard.com/hvr-2250/HVR-2250_firmware.zip

Unzip the files

unzip HVR-2250_firmware.zip

copy the files to the /lib/firmware folder

sudo cp *fw /lib/firmware

Now check if the card can be located and what value the system has given it

dmesg | grep saa7164

on the 3rd or 4th line you should see what you are looking for it will look like this

[card=8,autodetected]
What this says is my HVR-2250 was detected at card 8, you may (probably will) get a diferent number. If your card says "unknown" choose the last option, usually 8.

Now we need to enter this card number into modprobe.d/options.conf file (I like to use gedit)

sudo gedit /etc/modprobe.d/options.conf

place this line of code in the file

options saa7164 card=x
*x = your card's number*

Reboot and check mythtv backend to see if it is listed correctly.


Here are the older instructions if still needed for users still using older distros.


EDIT: I have updated this tutorial for use with 10.04, here is a direct link:
http://ubuntuforums.org/showpost.php?p=9219191&postcount=212


OK here is the awesome news, I got it working, but it took forever as I had to go through miles of web pages just to get this to work! I'll list my sources at the bottom if I missed something and you need to look through it for answers.

So I'm going to be nice and do some people some favours and post what I did to get it working in MythTV.

This driver is a BETA and only works on digital side of the tuner,

NO ANALOGUE and please be careful using.

I am not responsible for the outcome of you using my tutorial.

As I think my tutorial is rather crude and may miss an important step, please see the sources listed below. This is not for people new to Linux, as it might break (and it might, I've only had this running for about 30 minutes, so fingers crossed).

If you really need to use this card for analogue and need a free OS, try the Windows 7 MCE, the free RC is currently available and should work until May 2010 before MS make you purchase a real copy and works completely with this tuner card.

Instructions for using HVR-2250 in MythTV (also works on HVR-2200 or any video capture card using the SAA7164 chipset)

EDIT:this has been updated for Mythbuntu 10.04 but will work for versions of *buntu 8.10 and higher

Enter this into your Terminal it is the code for the firmware and to install it


wget http://www.steventoth.net/linux/hvr22xx/22xxdrv_27086.zip
wget http://www.steventoth.net/linux/hvr22xx/HVR-12x0-14x0-17x0_1_25_25271_WHQL.zip
wget http://www.steventoth.net/linux/hvr22xx/extract.sh


sh extract.sh
sudo cp *fw /lib/firmware

you need to install mercurial and build essential for the next steps

sudo apt-get install mercurial libncurses5-dev

then we need the driver using this command to fetch

hg clone http://kernellabs.com/hg/saa7164-stable/

now change to the directory

cd saa7164-stable

then run make

make CONFIG_DVB_FIREDTV:=n

that will take some time, go grab a drink and wait it out, when it completes run this command

sudo make install

wait for that to complete and reboot
from the command line

sudo reboot

Note that an application like TVtime will not work, TVtime only works on Analog signals, and so far this driver only gets the digital stuff working.

then install MythTV using whatever method you like, I personally went into synaptic and installed the frontend and backend and extra plug-ins

once installed and you set up your passwords go to
System> administration> MythTV backend setup

once there go to Capture Cards, Should be choice #2
choose new capture card, you will ave to do this step twice (this card has two tuners)
At card Type, pick DTB DTV
the first will be device number 0,
repeats choosing capture card to add the second tuner
the second device will be #1 (Linux starts counting at 0, good thing to know, especially for hard drives)

then go to video sources, pick your options, will vary so mine will not work with yours most likely, so I dont want to post something I dont know)

then go to Input Connections, again you will have 0 and 1, configure both

then edit channels and directories as needed.

close let it fill database, for some reason mine keeps running in a loop, just exit after you see it finish the first or second time

now go to Applications > Sound & Video > MythTV Frontend

And you should be able to watch TV

I must say the Linux HTPC community is way too technical for most people, they need to make these things simpler, Windows 7 MCE is 10 times better at setting up these things.

Notes
I used Ubuntu 9.04, results should work for anyone using *buntu 8.10 releases, including Mythbuntu
I must say the configuring MythTV is exhausting so if I missed something or it doens't work please post better steps.
Special thanks to Steven over at KernelLabs (http://www.kernellabs.com/blog/?page_id=17), the person who made the drivers.


Sources

http://www.linuxtv.org/wiki/index.php/How_to_Obtain%2C_Build_and_Install_V4L-DVB_Device_Drivers
http://www.kernellabs.com/blog/?page_id=17
http://kernellabs.com/hg/saa7164-stable/
http://parker1.co.uk/mythtv_ubuntu.php
http://www.linuxtv.org/wiki/index.php/How_to_Obtain%2C_Build_and_Install_V4L-DVB_Device_Drivers#Using_Mercurial
http://www.steventoth.net/blog/products/hvr-2250/
http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-2200

epi 1:10,000
May 29th, 2009, 02:36 AM
Thx LowSky your tutorial works a treat!!!

I followed your instructions but a little modified

I started with my old 9.04 x86_64 mythbuntu JAvenard VDPAU patches install.
I opened the frontend and deleted all upcoming recordings for the day and shut down the frontend.
Then I stoped my backend w/ a

sudo /etc/init.d/mythtv-backend stop

command in the terminal and then proceeded to the beginning of your tutorial @
wget http://www.steventoth.net/linux/hvr22xx/22xxdrv_27086.zip
wget http://www.steventoth.net/linux/hvr22xx/HVR-12x0-14x0-17x0_1_25_25271_WHQL.zip
wget http://www.steventoth.net/linux/hvr22xx/extract.sh


and followed you instructions all the way to
sudo make install


I rebooted and entered the backend setup and configured the 2 new tuners. When I started the frontend and went to Live TV both the tuners on my new HVR-2250 were receiving a perfect OTA ATSC signal. I will test their ability to record over the next few days

On a side note the analog tuner on my HVR-1600 works better now. There is no shuttering video on the first capture after startup and there seem to be less interference defects. It might just be all in my head..... placebo effect

LowSky
May 29th, 2009, 04:25 AM
Thx LowSky your tutorial works a treat!!!

On a side note the analog tuner on my HVR-1600 works better now. There is no shuttering video on the first capture after startup and there seem to be less interference defects. It might just be all in my head..... placebo effect

Thanks for the feedback.

your other tuner probably works better because of a channel rescan or better placement of your antenna.

scotto
May 30th, 2009, 04:09 AM
Yeah thanks for the great howto! I've been hoping someone would put it all together for the 2250.

So I tried this procedure on Knoppmyth R6 2nd preview release, which is now based on Arch Linux instead of Debian. I'm able to compile and install the driver, and I'm even able to set up the DTB card under mythtv, but I can't seem to pull any QAM channels off of Comcast, even tho my TV pulls them fine. Either of you have luck with QAM channels with this driver under Mythbuntu? I'd like to figure out if this is a driver issue or a Linux issue.

Thanks much.
--sa

LowSky
May 30th, 2009, 05:54 PM
QAM works fine for me, I have Cablevision. One thing I noticed is some cable splitters can effect channel grabbing. If you can try to connect your cable as directly as you can. Once you have scanned for channels you can rehook up the splitter as needed. and all should work.

epi 1:10,000
May 31st, 2009, 12:19 AM
Update:

Recording 2 ota ATSC channels at the same time works w/o problems.

experimental design-
recording CBS's Latt late show and NBS's Late night w/ Jimmy fallon concurently on the HVR-2250. Show were watched by scaned through the recordings to to make sure that there were no picture artifacts or audio sinc problems.
experiment repeated 3 times

equipment-
Mythbuntu 9.04 x86_64 w/ Avenard VDPAU patches Nvidia 180.51 drivers
ANTEC|THREE HUNDRED BK RT
GIGABYTE GA-EP43-UD3L 775 P43 R
GIGABYTE GV-N95TD3-512I 9500GT
TV TUNER HAUPPAUGE| HVR-2250 MC Model 1229
HAUPPAUGE|1183 RT HVR-1600
HAUPPAUGE 1196 HVR-1250 RT
PSU FSP|FSP350-60GLN(80) 350W
C2D E7400 2.8G
MEM 1Gx2|PNY MD2048KD2-800-X4 R
1.5T Seagate ST31500341AS 32M
KB ADESSO|WKB-3000UB RT
DVD ROM LITE-ON|iHDP118-08 18X RTL
DVD BURN LG|GH22NS30 22X SATA
Antenna RCA ANT3020X NA CAW 03



Bug-
After a reboot the frontend fails to to see the 2 HVR-2250 tuners in Live TV.

Fix-
After every reboot you need to enter the backend settup and exit in order for the frontend to see the 2 HVR-2250 tuners

LowSky
May 31st, 2009, 01:58 AM
make sure to add the mythtv backend to your starting applications at login

epi 1:10,000
May 31st, 2009, 04:57 PM
I assumed it was installed that way by default... Am I mistaken?

LowSky
June 1st, 2009, 04:25 PM
It think it is, but make sure, it cant hurt

epi 1:10,000
June 13th, 2009, 04:55 PM
The previous problem with the Frontend not detecting the HVR-2250 on strartup has bin fixed!!!

I rescaned after the digital transition and then one of my HVR-2250 tuners stoped locking onto channels. I restarted a couple times and rechecked my conections and the problem persisted. I figured now is as good a time as any to update so I backed up the DB and updated then restarted and everything is fixed. It seems if you install this card its best to follow LowSky's instructions fully and update or install MythTV after you instal the drivers/firmware.

theotherguy27
June 17th, 2009, 11:19 PM
Hello Im in the process of trying to get this to work using a fresh in stal of the Mythbuntu distro.
and i Kept getting an unzip error while trying to process the part of code that follows

sh extract.sh
sudo cp *fw /lib/firmware

well i figured out what the issue was, and im a newbie to Linux, and maybe this is something that is common knowledge, but apperently this distro doesnt have the unzip program complied into it so you need to use the following command

sudo apt-get install unzip

Hope this Helps Other Newbies Out there!
Peace Out~
H/NK

vronp
August 16th, 2009, 11:36 PM
Hi all,

I'd like to insert a NOOB question here.

I am building a MythTV front/back end box now and I play to use the 2250.

Here is my question. In addition to getting OTA signals, can I pipe the output from a DirecTV HD receiver into this card?

thanks !

vronp
August 16th, 2009, 11:58 PM
To expand on my post a bit.

To get OTA (digital obviously) AND HD DirecTV into Mythbuntu, do I need both the HVR-2250 AND the Hauppage HD-PVR ?

LowSky
August 17th, 2009, 04:53 PM
The HVR-2250 only has one input for TV signals, so no it will not work with two different signals. So yes you will need another card to do what you are looking to do.

hope that helps.

vronp
August 17th, 2009, 04:57 PM
The HVR-2250 only has one input for TV signals, so no it will not work with two different signals. So yes you will need another card to do what you are looking to do.

hope that helps.

Well, I have since determined that the HD PVR is a "must have" for recording HD content from a DirecTV receiver. So, I am going to order one of those.

So, let me change the question a bit. What is the hot setup for just an OTA card?

thanks again,
Dave

LowSky
August 17th, 2009, 05:23 PM
HVR-2250 ius a great card, it has basically 4 built in tuners, with the ability to record two shows at the same time., its only downside is it having one input so you cannot use two different sources. but the qualtiy is great, it has onboard encoding to save processor speed. So for OTA the card is worth it., just get a good antenna, as digital signals in some areas can be weak.

EternalStudent
August 17th, 2009, 11:48 PM
vronp (http://ubuntuforums.org/member.php?u=150212), I'm not very familiar with this (seen it, never done it). But I know it is possible to combine cable inputs into one line if you have the correct coaxial combiner. I did some research last year when setting up my outdoor OTA antenna. Depending on your setup, a simple coax combiner may be able to work. They also make channel restrictive combiners. I don't have any idea if the 2250 can handle it though, since that may mean OTA digital and possibly cable analog.

xinix
August 20th, 2009, 04:11 PM
Just dropping in a note to confirm that this card works as expected for me as well. The hardest part was finding the mplex for some channels and then having to manually enter them into the db.

Tomlin
August 26th, 2009, 05:24 PM
I'm getting:

"abort: error: Connection timed out"

when trying to connect to http://kernellabs.com

Is this site still active, or maybe just temporarily down?

Thanks

ktmom
August 28th, 2009, 11:03 PM
I'm getting:

"abort: error: Connection timed out"

when trying to connect to http://kernellabs.com

Is this site still active, or maybe just temporarily down?

Thanks
FWIW - I have been on the http://kernellabs.com site today

thesponge
September 3rd, 2009, 06:31 PM
ok so I had it all working in mythbuntu 8.10. Then I upgraded to 9.04 and the 2250 drivers are no longer listed in Hardware drivers and if I try and go through the steps again it errors out like the drivers are already installed. I am fairly new to linux so kid gloves are appreciated.

LowSky
September 3rd, 2009, 07:48 PM
ok so I had it all working in mythbuntu 8.10. Then I upgraded to 9.04 and the 2250 drivers are no longer listed in Hardware drivers and if I try and go through the steps again it errors out like the drivers are already installed. I am fairly new to linux so kid gloves are appreciated.

First things first, you will need to reinstall the drivers. the drivers are related to the kernel, so any kernel upgrade and they will break.

Second, for HTPC the best thing to do is to not upgrade versions often. Best thing is to use the LTS or keep a current version for longer. But don't upgrade as things will break, and you will have to reload the drivers and modules all over again.

thesponge
September 4th, 2009, 03:17 AM
Thanks, I was having trouble reloading the drivers. Finally I just renamed the saa7164-stable to saa7164-stable_old and, followed the steps from the hg clone step and my tuners seem to be installed. Having trouble connecting to the backend server database so I will have to research that now

williammanda
September 6th, 2009, 03:44 PM
To troubleshoot the database issue:
1. Goto /home/william/.mythtv/mysql.txt and retreive the password.
2. Open mythbuntu control center and launch mythtv setup and edit the password.
Thanks

jgull8502
September 21st, 2009, 12:47 AM
I'm thinking of buying a card for my desktop so I can get MythTV set up on it. This card looks like a good option and it seems people have it working in linux. This may be a stupid question, but I'll ask it anyway. Right now, I have comcast cable (no HD stations) and just have the coaxial cable plugged into the back of the TV. I'm assuming this card will be able to handle the stream like my TV does.

jgull8502
September 21st, 2009, 01:06 AM
Check that. I just realized that this card is PCI-Express and I only have PCI. I guess that means that the HVR-1600 would be my best bet.

LowSky
September 21st, 2009, 05:42 AM
Regardless of what model you have you will pick up cable, but not all your channels, only what is availible without a box. Even HD as Cable usually offers it for free over the line.

silverdulcet
September 21st, 2009, 05:54 AM
Thanks, I was having trouble reloading the drivers. Finally I just renamed the saa7164-stable to saa7164-stable_old and, followed the steps from the hg clone step and my tuners seem to be installed. Having trouble connecting to the backend server database so I will have to research that now

Just a follow-up. Instead of downloading the source from the mercurial repo with the hg clone command each time there is a kernal update, just follow the instructions detailed in this post:
http://ubuntuforums.org/showpost.php?p=7749033&postcount=12

ktmom
September 22nd, 2009, 01:07 AM
Right now, I have comcast cable (no HD stations) and just have the coaxial cable plugged into the back of the TV. I'm assuming this card will be able to handle the stream like my TV does.


This card only works for digital signals (HD) under linux at this time. The drivers are being developed by Steven Toth independently of manufacturer support. Your Comcast cable probably has a few (couple) HD signals but all of the analog will not work on linux as of yet.

http://www.steventoth.net/blog/products/hvr-2250/

http://www.kernellabs.com/blog/?p=721

bsntech
September 22nd, 2009, 02:27 PM
I think the HVR-1600 is probably the best card at the moment - especially for those that need two inputs. the HVR-1600 has a separate analog and digital tuner so you can put two inputs into the unit. As an example, you can run your coax from cable TV through the analog, and then use an antenna for OTA HD local stations. Of course, you can always hook another coax from cable TV to the digital tuner as well.

Just seems like it gives more room for inputs. The HVR-2250 is nice that it has two tuners and both will do analog or digital, but only one input for one connection. However, the analog does not work with Linux - hence another reason to choose the HVR-1600 (at least at the present time).

juicedM3
September 23rd, 2009, 09:27 PM
Has anybody tried the lastest drivers? Just wondering.

Name: 22xxdrv_27223.zip
Size: 9.2 MB
Updated: 8/18/2009

http://hauppauge.lightpath.net/software/drivers/22xxdrv_27223.zip

The extract.sh script needs to be modified slightly, for example:



unzip -jo $IFILE 22xxdrv_27086/Driver89/HcwWiltF103.bin
unzip -jo $IFILE 22xx_drv_27223/Driver89/HcwWiltF103.bin


Thanks,
Justin

jgull8502
September 23rd, 2009, 10:00 PM
Thanks for the input! Perhaps I'll go with the 1600 then!

Tomlin
September 24th, 2009, 02:33 PM
I had no success with Mythbuntu 9.04 and the 2250. I went with 9.04 and the HVR-1250 - it works great BTW. I still would like the dual tuner option though. Are you guys saying if I drop back to 8.10 I should be good to go?

I may have a spare drive that I could swap with the currently installed (9.04) one.

Thanks.

ktmom
September 26th, 2009, 01:48 PM
I had no success with Mythbuntu 9.04 and the 2250. I went with 9.04 and the HVR-1250 - it works great BTW. I still would like the dual tuner option though. Are you guys saying if I drop back to 8.10 I should be good to go?


I'm using Mythbuntu 9.04 with the 2250 (digital tuner only) with no problems. Have you installed the drivers are directed in this thread?

Tomlin
September 28th, 2009, 05:38 PM
I'm using Mythbuntu 9.04 with the 2250 (digital tuner only) with no problems. Have you installed the drivers are directed in this thread?

Yup...I did this:


Enter this into your Terminal it is the code for the firmware and to install it
Code:

wget http://www.steventoth.net/linux/hvr22xx/22xxdrv_27086.zip
wget http://www.steventoth.net/linux/hvr22xx/HVR-12x0-14x0-17x0_1_25_25271_WHQL.zip
wget http://www.steventoth.net/linux/hvr22xx/extract.sh

Code:

sh extract.sh
sudo cp *fw /lib/firmware

you need to install mercurial and build essential for the next steps
Code:

sudo apt-get install mercurial build-essential

then we need the driver using this command to fetch
Code:

hg clone http://kernellabs.com/hg/saa7164-stable/

now change to the directory
Code:

cd saa7164-stable

then run make
Code:

make

that will take some time, go grab a drink and wait it out, when it completes run this command
Code:

sudo make install

wait for that to complete and reboot
from the command line
Code:

sudo reboot



Here's a snippet of the output from dmesg:


[ 18.514907] nvidia: module license 'NVIDIA' taints kernel.
[ 18.771436] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
[ 18.771448] nvidia 0000:01:00.0: PCI INT A -> Link[APC1] -> GSI 16 (level, low) -> IRQ 16
[ 18.771455] nvidia 0000:01:00.0: setting latency timer to 64
[ 18.772618] NVRM: loading NVIDIA UNIX x86 Kernel Module 180.44 Mon Mar 23 14:59:10 PST 2009
[ 18.947600] saa7164 driver loaded
[ 18.947659] saa7164 0000:02:00.0: PCI INT A -> Link[APC1] -> GSI 16 (level, low) -> IRQ 16
[ 18.947664] saa7164[0]: Your board isn't known (yet) to the driver.
[ 18.947665] saa7164[0]: Try to pick one of the existing card configs via
[ 18.947666] saa7164[0]: card=<n> insmod option. Updating to the latest
[ 18.947668] saa7164[0]: version might help as well.
[ 18.947671] saa7164[0]: Here are valid choices for the card=<n> insmod option:
[ 18.947674] saa7164[0]: card=0 -> Unknown
[ 18.947676] saa7164[0]: card=1 -> Generic Rev2
[ 18.947677] saa7164[0]: card=2 -> Generic Rev3
[ 18.947679] saa7164[0]: card=3 -> Hauppauge WinTV-HVR2250
[ 18.947681] saa7164[0]: card=4 -> Hauppauge WinTV-HVR2200
[ 18.947683] saa7164[0]: card=5 -> Hauppauge WinTV-HVR2200
[ 18.947685] saa7164[0]: card=6 -> Hauppauge WinTV-HVR2200
[ 18.947687] saa7164[0]: card=7 -> Hauppauge WinTV-HVR2250
[ 18.947689] saa7164[0]: card=8 -> Hauppauge WinTV-HVR2250
[ 18.947984] CORE saa7164[0]: subsystem: 1131:0000, board: Unknown [card=0,autodetected]
[ 18.947991] saa7164[0]/0: found at 0000:02:00.0, rev: 129, irq: 16, latency: 0, mmio: 0xd3000000
[ 18.947997] saa7164 0000:02:00.0: setting latency timer to 64
[ 18.948031] saa7164_initdev() Unsupported board detected, registering without firmware


Anyone???

xinix
October 17th, 2009, 05:25 PM
How can I revert to an older version of the driver? I just updated after seeing that new patches were moved into the stable branch. Unfortunately I cannot tune some channels that I could (and had recorded) shortly before doing the upgrade.

Thanks

Edit::Well, I went with the -dev version and the channels are tuning in again.

ScottBla
October 25th, 2009, 02:08 AM
Trying to do this on the Mythbuntu 9.10 pre-release and getting a bunch of no such file errors trying to build. I imagine I'm just missing some package, but I haven't figured out whichone yet...Any suggestions? Thanx!

CC [M] /home/scott/Downloads/hvr22xx/saa7164-stable/v4l/firedtv-1394.o
/home/scott/Downloads/hvr22xx/saa7164-stable/v4l/firedtv-1394.c:21:17: error: dma.h: No such file or directory
/home/scott/Downloads/hvr22xx/saa7164-stable/v4l/firedtv-1394.c:22:21: error: csr1212.h: No such file or directory
/home/scott/Downloads/hvr22xx/saa7164-stable/v4l/firedtv-1394.c:23:23: error: highlevel.h: No such file or directory
/home/scott/Downloads/hvr22xx/saa7164-stable/v4l/firedtv-1394.c:24:19: error: hosts.h: No such file or directory
/home/scott/Downloads/hvr22xx/saa7164-stable/v4l/firedtv-1394.c:25:22: error: ieee1394.h: No such file or directory
/home/scott/Downloads/hvr22xx/saa7164-stable/v4l/firedtv-1394.c:26:17: error: iso.h: No such file or directory
/home/scott/Downloads/hvr22xx/saa7164-stable/v4l/firedtv-1394.c:27:21: error: nodemgr.h: No such file or directory

ScottBla
October 25th, 2009, 03:38 AM
So...I did some research to find that it looks like I need the full kernel source instead of just the linux-headers pkg. So I grabbed the linux-source, extracted it and it still fails because its looking under the /lib/modules/2.6.31-14-generic/build dir (matching my `uname -r` value)...but that's a symlink pointing into the -headers dir tree. I tried changing the symlink to point at my extracted linux-source, but then it starts looking for a .config file. Copied the .config file over from the -headers dir, but there are a whole pile more errors trying to build.

It seems that I've got to be missing some basic trick here...I suppose I could do a full build, but I have a feeling that will end up being a whole can o worms I don't want to step into... :)

xinix
October 25th, 2009, 04:27 AM
It seems that I've got to be missing some basic trick here...I suppose I could do a full build, but I have a feeling that will end up being a whole can o worms I don't want to step into... :)

I tried building this on Karmic. it would not build using the headers, going with the linux-source route worked; sort of. It built but would not load. I forget the exact error but it is the same one you'd get if you try to load a module on the wrong kernel.

look here for what seems like a working 'fix' to get it to build using the headers:
http://ubuntuforums.org/showthread.php?t=1281341

If you really want to use the linux-source you need to do more than copy the .config file. You need to do these steps (as sudo/root) after you copy the .config file.

make oldconfig
make prepare0
make scripts

ScottBla
October 25th, 2009, 04:44 AM
look here for what seems like a working 'fix' to get it to build using the headers:
http://ubuntuforums.org/showthread.php?t=1281341

Thanx! That helps a lot!


If you really want to use the linux-source you need to do more than copy the .config file. You need to do these steps (as sudo/root) after you copy the .config file....


Cool - I'll keep that in mind if end up needing to build it for some reason...

danbaatar
October 27th, 2009, 05:08 AM
@ScottBla The problem you're seeing is a result of the fact that repository you download in these instructions is a complete branch of the v4l tree and one of the drivers (the firedtv one) needs the full kernel source to compile. You can disable the compilation of that driver by executing:


make CONFIG_DVB_FIREDTV:=n || return

instead of the first make command and then running the


make install

wartstew
October 31st, 2009, 09:13 PM
Hi thanks for the tip (disabling the FireDTV device).

I had been pursuing down the "installing the kernel source" route, and found that the original kernel would not accept the module do to the versioning restrictions it was configured with (how do you deal with this?). This was leading me needing to compile a whole new kernel. Since this MythTV box is not even mine (I am helping a friend and Linux Newbie with his and was working on his box remotely through an SSH tunnel), I did not want to get things too non-stock on this box which could likely confuse him later.

By the way, if you want to do the "menuconfig" instead of the "CONFIG_DVB_FIREDTV:=n" thing, then you have to install the ncurses developer package:

sudo apt-get install libncurses5-dev

before the ncurses based "menuconfig" will come up.

--------------

So now he is going to try to get the IR remote to the HVR to work, so he may be calling on me again if any instructions he might follow doesn't work out.

xinix
October 31st, 2009, 10:55 PM
You don't need to use the full kernel source if you disable the "FireDTV" option. If you just want the driver, I would use the headers way. It works just fine.

sgreene59
November 5th, 2009, 03:23 AM
Using the latest sources the drivers fail to compile even with the FIREDTV module excluded.


/home/[account]/saa7164-stable-da41142e212f/v4l/dib7000p.h: In function 'dib7000p_pid_filter':
/home/[account]/saa7164-stable-da41142e212f/v4l/dib7000p.h:100: error: parameter name omitted
make[3]: *** [/home/sgreene/saa7164-stable-da41142e212f/v4l/cx23885-dvb.o] Error 1
make[2]: *** [_module_/home/sgreene/saa7164-stable-da41142e212f/v4l] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.31-14-generic'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/home/[account]/saa7164-stable-da41142e212f/v4l'
make: *** [all] Error 2

golond
November 5th, 2009, 08:42 PM
Danbaatar resolved it for me with 'make CONFIG_DVB_FIREDTV:=n'. Thanks a ton.

aflores3
November 19th, 2009, 03:21 AM
Even when I try with "make CONFIG_DVB_FIREDTV:=n" I get:

make -C /2250/saa7164-stable/v4l
make[1]: Entering directory `/2250/saa7164-stable/v4l'
Updating/Creating .config
Preparing to compile for kernel version 2.6.31
File not found: /lib/modules/2.6.31-14-server/build/.config at ./scripts/make_kconfig.pl line 32, <IN> line 4.
make[1]: *** No rule to make target `.myconfig', needed by `config-compat.h'. Stop.
make[1]: Leaving directory `/2250/saa7164-stable/v4l'
make: *** [all] Error 2
bash: return: can only `return' from a function or sourced script

Not sure why its not making the .config file...

aflores3
November 19th, 2009, 04:56 AM
Not sure why its not making the .config file...

Ok, I managed to work this out...

In case anyone is having the same problem, check out: http://www.linuxtv.org/wiki/index.php/Talk:How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers

aflores3
November 19th, 2009, 06:06 AM
Ok, so I finally got the drivers installed. Thank you to all who have posted.

Now, when I go to mythtv-setup and try to add a card (type DVB DTV), it says:
Frontend ID: Could not get card info for card '/dev/dvb/adapter0/frontend0' Subtype: Unknown

dmesg|grep -i dvb spits out

[ 20.080374] tveeprom 1-0000: TV standards NTSC(M) ATSC/DVB Digital (eeprom 0x88)
[ 20.884666] DVB: registering new adapter (saa7164)
[ 20.884670] DVB: registering adapter 0 frontend 0 (Samsung S5H1411 QAM/8VSB Frontend)...
[ 24.388210] DVB: registering new adapter (saa7164)
[ 24.388215] DVB: registering adapter 1 frontend 0 (Samsung S5H1411 QAM/8VSB Frontend)...

Thanks in advance


**Edit**
Could this be because I'm trying to go through a set-top box from the cable company? I'm at work right now, so I can't test it... maybe I'll go home for lunch.

damies
November 22nd, 2009, 12:53 PM
Hi,

I get stuck at this point:

hg clone http://kernellabs.com/hg/saa7164-stable/

abort: error: Connection timed out

is there another site where we can get this file? any suggestions?

Dave.

Barry_IA
November 23rd, 2009, 02:40 AM
Hi,

I get stuck at this point:

hg clone http://kernellabs.com/hg/saa7164-stable/

abort: error: Connection timed out

is there another site where we can get this file? any suggestions?

Dave.

Dave:

Looks correct to me; perhaps there is a problem in an earlier step, which is why this one doesn't work? I'm presuming your Internet connection works correctly -- try Firefox (can either access it via the Applications pull-down or typing Firefox in Terminal).

LowSky's instructions work, however I found I needed to start with "sudo apt-get install unzip" before the first 'wget' command. Should get an error message at the "sh extract.sh" command line, though.

And should you get an error message with 'sudo apt-get install unzip' command, do the following:

1. Make sure your Internet connection is working. (Test using Firefox to the outside world.)

2. "sudo apt-get check" (Not sure if this command is necessary: I was following instructions in a book.)

3. "sudo apt-get --install-recommends update" (Note the two hyphens before 'install'.)

Good Luck!

scotthew1
December 18th, 2009, 04:33 AM
gah help!!!
i've gotten the driver to install and myth tv seems to be recognizing the card correctly and everything. however, once i do a scan for channels (i'm not even sure if i'm doing the right scan even there're so many scan options) it comes up with a quite a few possible channels. however, when i go into the frontend, either nothing is really displayed, or the channel seems to tune, but it is shown in a very distorted double with no audio. am i doing something wrong? my tv itself can tune channels just fine and i know that they're all clear qam digital. it's very frustrating that i can't get to get the card to tune any channels!! also i have fios. can anyone please help?

JeepFreak
December 18th, 2009, 08:01 AM
gah help!!!
i've gotten the driver to install and myth tv seems to be recognizing the card correctly and everything. however, once i do a scan for channels (i'm not even sure if i'm doing the right scan even there're so many scan options) it comes up with a quite a few possible channels. however, when i go into the frontend, either nothing is really displayed, or the channel seems to tune, but it is shown in a very distorted double with no audio. am i doing something wrong? my tv itself can tune channels just fine and i know that they're all clear qam digital. it's very frustrating that i can't get to get the card to tune any channels!! also i have fios. can anyone please help?

I came her to post, basically, the exact same thing. Although, I haven't tried to watch the few channels that came up in the scan yet. I'm trying to find more info on the settings that should be used for the scan. I'm in the US btw and using OTA digital cable from Comcast (in case it matters).

TIA!
Billy

JeepFreak
December 19th, 2009, 01:44 AM
I came her to post, basically, the exact same thing. Although, I haven't tried to watch the few channels that came up in the scan yet. I'm trying to find more info on the settings that should be used for the scan. I'm in the US btw and using OTA digital cable from Comcast (in case it matters).

TIA!
Billy

OK, so now I get a great picture, but the scan only finds a dozen or so channels. I've tried running it multiple times. Of the channels that it does find, many are mislabeled in the guide (ie, it says FOX, but it's actually CSPAN.) I'm pulling the listings from SchedulesDirect. I've already created a new lineup with the channels that my TV gets straight from the cable outlet. I'm going to mess with it again tonight, but if anybody knows what I should try, I'd appreciate it!

Thanks,
Billy

damies
December 19th, 2009, 11:45 AM
The site was just down when i tried it. its working again now the same as it had for previous builds.

perhaps a mirror site would be a good idea?

cheers,

Dave

LowSky
December 21st, 2009, 09:45 PM
I've been away from this project for a while, and maybe I should revise it. If anyone wants to send me suggestions or notes on some issues I will look into them, maybe collaborate with me in testing and what not too. It will be a few weeks before a new guide is posted, because of the holiday's and then my weeklong vacation to Vegas. So I cant really start until maybe January 15 2010.

scotthew1
December 23rd, 2009, 02:45 AM
hey thanks for the offer!

i ran through the entirety of your setup instructions except i had to use

make CONFIG_DVB_FIREDTV:=n
instead of just "make"

my computer seems to recognize the drivers and the card itself. i was also able to set up the tuners in mythtv just as you said to. then i went to scan for channels and everything seemed to go well. i found a lot of "possible channels." i have verizon fios and i know that they do send some clear qam channels and i've gotten them all to tune just fine by plugging the cable directly into my tv. however, when i go to watch tv in mythtv. it only seems to be able to tune just a very few channels (i can get a few dozen on the tv by itself), and the few channels it does tune are sown on the tv twice (two stretched pictures on the screen). also there seems to be no sound, although i have recently found that mythtv itself hasn't been outputting any sound on my computer for a still unknown reason... if you could offer any suggestions i would be so grateful. getting everything to work has been very frustrating and so far the $100 purchase for this card has felt like a waste =[
also i'm using 9.10 if that is of any help to you.

thanks!
-scott

scotthew1
December 23rd, 2009, 06:23 AM
and now i've discovered that the driver for the tuner must somehow be restricting mythtv from outputting audio... i'm not sure if this makes any sense at all, but i just earlier installed updates on my computer (which apparently required me to reinstall the driver for the tuner). so before the updates, i couldn't get mythtv to output any sound. after i did the update, i was able to play videos thru mythtv and the sound worked, i was so happy! but then i realized that i needed to reinstall the driver for the tuner. after i did that i can't get mythtv to output any sound....
i really don't understand why it would be the drivers for the card but that seems to be the case...

LowSky
December 23rd, 2009, 01:05 PM
I doubt MYthTV is restricting the sounds, your case might be a simple one all you might have to do is change the audio source. It cold be something simple like going to the sound preferences and checking the hardware tab and making sure all devices are functioning.

I would also check to see if pulse audio is working correctly
https://wiki.ubuntu.com/PulseAudio

and if you have intel chipset take a look at this
https://help.ubuntu.com/community/HdaIntelSoundHowto

scotthew1
December 27th, 2009, 03:11 AM
no its nothing with the system itself i don't think. outside of mythtv all my audio works just fine. its only mythtv itself that doesn't seem to produce any sound. and i think it is because of something in this driver... i have no idea why that would be but i'm trying to figure out how to uninstall the driver to see if this is really the case. how would i uninstall the driver?

nPoc
December 30th, 2009, 11:18 AM
So I've been following this thread, and I wanted to make sure everyone was aware that the drivers from Steven Toth have been merged into the linuxtv repositories.

I'm not sure how much active maintenance is going on at the kernellabs site, but I'm more concerned about bug fixes for my other cards.

So I'm going to try building off the repository available at linuxtv. Wish me luck. If I remember, I'll post back here on the results. Also did someone end up trying the new firmware *(I might have missed a post, but I'm not sure).

http://www.linuxtv.org/wiki/index.php/How_to_Obtain%2C_Build_and_Install_V4L-DVB_Device_Drivers

nPoc
December 30th, 2009, 09:12 PM
So I tried building off the linuxtv.org repo on 9.10, and was able to successfully get my 2250 up and running unfortunately my wintv 250 and fusionhdtv 5 stopped working.

Dec 30 13:19:50 bonus kernel: [30982.637274] cx88xx: disagrees about version of symbol v4l2_i2c_new_subdev_cfg
Dec 30 13:19:50 bonus kernel: [30982.637285] cx88xx: Unknown symbol v4l2_i2c_new_subdev_cfg
.... and it goes on.

the ivtv driver has a similar issue.
Dec 30 04:43:39 bonus kernel: [ 11.669010] ivtv: Unknown symbol ir_codes_hauppauge_new_table
Dec 30 04:43:39 bonus kernel: [ 11.671008] ivtv: Unknown symbol ir_codes_rc5_tv_table


Back to the drawing board. I'm going to try installing only the saa7164 driver, and try to follow the dependency tree on down.

Any ideas would be greatly appreciated.

YogiPaolo
January 2nd, 2010, 08:40 AM
This sounds really great. thanks everyone for all the information.

I'm building a little HTPC right now. All the parts are on order from NewEgg save for the tuner card which I cannot decide on. I found this thread and I'm leaning towards the 2250.

This box will also double as a file server. The specs should have enough juice. Here are the details for your purusal:


Mushkin Enhanced Blackline 2GB 240-Pin DDR2 SDRAM DDR2 1066

3 for a raid 5 SAMSUNG EcoGreen F2 HD103SI 1TB 5400 RPM SATA 3.0Gb/s 3.5"

ASUS M3A78-CM AM2+/AM2 AMD 780V Micro ATX AMD Motherboard

CORSAIR CMPSU-400CX 400W ATX12V V2.2 80 PLUS Certified Power Supply

AMD Phenom 9150E 1.8GHz Socket AM2+ 65W Quad-Core Processor

Thermaltake LANBOX Lite VF6000BWS Black SECC Japanese steel Gaming Cube Computer Case

I believe that I'll take the leap with the 2250.

Be sure to look back here for my progress...

YogiPaolo
January 12th, 2010, 01:22 AM
hey thanks for the offer!

i ran through the entirety of your setup instructions except i had to use

make CONFIG_DVB_FIREDTV:=n
instead of just "make"

my computer seems to recognize the drivers and the card itself. i was also able to set up the tuners in mythtv just as you said to. then i went to scan for channels and everything seemed to go well. i found a lot of "possible channels." i have verizon fios and i know that they do send some clear qam channels and i've gotten them all to tune just fine by plugging the cable directly into my tv. however, when i go to watch tv in mythtv. it only seems to be able to tune just a very few channels (i can get a few dozen on the tv by itself), and the few channels it does tune are sown on the tv twice (two stretched pictures on the screen). also there seems to be no sound, although i have recently found that mythtv itself hasn't been outputting any sound on my computer for a still unknown reason... if you could offer any suggestions i would be so grateful. getting everything to work has been very frustrating and so far the $100 purchase for this card has felt like a waste =[
also i'm using 9.10 if that is of any help to you.

thanks!
-scott

This seems to be working for me, but it's still compiling. Once again I'm grateful to everyone for help. I'd like to contribute back by describing my project. I've taken notes this time and would like to share. Would it be wise to start a new thread or might someone suggest a thread in the way of mythbox building ?

AH! it seems to have compiled sucessfully!!!

more later...

AJBalettie
January 14th, 2010, 04:39 AM
Ok, so I am trying to get this card to work with MythTV in Karmic (9.10) by running the scripts detailed on the first page. Is there something else I'm missing?

TIA

-Andrew :popcorn:

YogiPaolo
January 14th, 2010, 04:47 AM
Ok, so I am trying to get this card to work with MythTV in Karmic (9.10) by running the scripts detailed on the first page. Is there something else I'm missing?

TIA

-Andrew :popcorn:

I'm not sure, but I'd be happy to help. I got the card working, but there are a few wrinkles that I'm checking back here to try solving.

That's how I found your post.

Could you be more specific?
When you restart and run lsmod, do you see the mmodules saa7164?
Did the scripts build with no errors?

Feed us more info and we can help. I'll be posting later...

silverdulcet
January 14th, 2010, 06:25 AM
I'm not sure, but I'd be happy to help. I got the card working, but there are a few wrinkles that I'm checking back here to try solving.

That's how I found your post.

Could you be more specific?
When you restart and run lsmod, do you see the mmodules saa7164?
Did the scripts build with no errors?

Feed us more info and we can help. I'll be posting later...

You can also issue this command at a Terminal:

dmesg | grep saa

If the driver compiled correctly and you have the firmware in the correct place it should return something similar to this:

[ 12.552294] saa7164 driver loaded
[ 12.552328] saa7164 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 12.552676] CORE saa7164[0]: subsystem: 0070:8851, board: Hauppauge WinTV-HVR2250 [card=7,autodetected]
[ 12.552681] saa7164[0]/0: found at 0000:02:00.0, rev: 129, irq: 16, latency: 0, mmio: 0xfd400000
[ 12.552685] saa7164 0000:02:00.0: setting latency timer to 64
[ 12.712533] saa7164_downloadfirmware() no first image
[ 12.712571] saa7164_downloadfirmware() Waiting for firmware upload (v4l-saa7164-1.0.3.fw)
[ 12.712574] saa7164 0000:02:00.0: firmware: requesting v4l-saa7164-1.0.3.fw
[ 13.739734] saa7164_downloadfirmware() firmware read 3978608 bytes.
[ 13.739737] saa7164_downloadfirmware() firmware loaded.
[ 13.739743] saa7164_downloadfirmware() SecBootLoader.FileSize = 3978608
[ 13.739749] saa7164_downloadfirmware() FirmwareSize = 0x1fd6
[ 13.739750] saa7164_downloadfirmware() BSLSize = 0x0
[ 13.739751] saa7164_downloadfirmware() Reserved = 0x0
[ 13.739752] saa7164_downloadfirmware() Version = 0x51cc1
[ 20.596027] saa7164_downloadimage() Image downloaded, booting...
[ 20.700026] saa7164_downloadimage() Image booted successfully.
[ 22.744026] saa7164_downloadimage() Image downloaded, booting...
[ 24.408017] saa7164_downloadimage() Image booted successfully.
[ 24.445211] saa7164[0]: Hauppauge eeprom: model=88061
[ 25.048429] DVB: registering new adapter (saa7164)
[ 27.930326] DVB: registering new adapter (saa7164)


Have you configured the tuner(s) in mythtv-setup?

kpholmes
January 14th, 2010, 06:46 AM
i was just looking at cards for mythTV and i cant believe i stumbled upon this thread cause i was thinking about getting the 2250. knowing what you know now, would you recommend this card or maybe another one? thanks

AJBalettie
January 14th, 2010, 07:08 AM
You can also issue this command at a Terminal:

dmesg | grep saa

this didn't do anything in my terminal :(

also, i can't configure the card in the mythtv backend because they don't show up as devices, which is why i don't think i did the driver correctly.

silverdulcet
January 14th, 2010, 07:11 AM
i was just looking at cards for mythTV and i cant believe i stumbled upon this thread cause i was thinking about getting the 2250. knowing what you know now, would you recommend this card or maybe another one? thanks

I'd absolutely recommend this card.
Pros:
* 2 tuners with internal splitter, record 2 ATSC shows or 2 cable QAM shows.

* Multirec works, meaning you can record multiple shows that are on the same multiplex (eg, PBS 2.1, 2.2, 2.3) and only use one of the tuners.

* PCIE card, includes low profile bracket as well.

Cons:
* Internal PCIE card, if you don't have room in your case or lack a PCIE slot, perhaps a usb tuner or HDHomerun (network tuner) would be better for you.

* There is no support for in the driver for the analog encoder yet.

* The driver does not support the IR remote chip that is on this card, so you'll need either a USB IR receiver, IR module included on your case, or the IR from another tuner.

* Not really a con, but if you don't need 2 tuners, there are cheaper single tuner cards available as well.

Just an update on the drivers, as of Sept. 17 2009 they are included in the linuxtv.org v4l-dvb mercurial repo, see http://www.kernellabs.com/blog/?p=721

This means if you have other cards that are not supported by the current release of mythbuntu you can compile the updated drivers all from one place.

silverdulcet
January 14th, 2010, 07:19 AM
this didn't do anything in my terminal :(

also, i can't configure the card in the mythtv backend because they don't show up as devices, which is why i don't think i did the driver correctly.

Ok, when you are on this step:
now change to the directory

cd saa7164-stable

then run make

make

Can you post the output of this command? Perhaps the last ~20 or so lines. Look for any "Error" messages.

AJBalettie
January 14th, 2010, 07:25 AM
/home/andrew/saa7164-stable/v4l/firedtv-1394.c: In function 'fcp_request':
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:167: error: dereferencing pointer to incomplete type
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:168: error: dereferencing pointer to incomplete type
/home/andrew/saa7164-stable/v4l/firedtv-1394.c: In function 'node_probe':
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:182: error: dereferencing pointer to incomplete type
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:182: warning: type defaults to 'int' in declaration of '__mptr'
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:182: warning: initialization from incompatible pointer type
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:182: error: invalid use of undefined type 'struct unit_directory'
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:187: error: dereferencing pointer to incomplete type
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:187: error: 'quadlet_t' undeclared (first use in this function)
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:188: error: implicit declaration of function 'CSR1212_TEXTUAL_DESCRIPTOR_LEAF_DATA'
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:188: error: dereferencing pointer to incomplete type
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:188: warning: assignment makes pointer from integer without a cast
/home/andrew/saa7164-stable/v4l/firedtv-1394.c: At top level:
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:243: warning: 'struct unit_directory' declared inside parameter list
/home/andrew/saa7164-stable/v4l/firedtv-1394.c: In function 'node_update':
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:245: error: dereferencing pointer to incomplete type
/home/andrew/saa7164-stable/v4l/firedtv-1394.c: At top level:
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:253: error: variable 'fdtv_driver' has initializer but incomplete type
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:254: error: unknown field 'name' specified in initializer
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:254: warning: excess elements in struct initializer
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:254: warning: (near initialization for 'fdtv_driver')
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:255: error: unknown field 'update' specified in initializer
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:255: warning: excess elements in struct initializer
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:255: warning: (near initialization for 'fdtv_driver')
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:256: error: unknown field 'driver' specified in initializer
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:256: error: extra brace group at end of initializer
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:256: error: (near initialization for 'fdtv_driver')
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:259: warning: excess elements in struct initializer
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:259: warning: (near initialization for 'fdtv_driver')
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:262: error: variable 'fdtv_highlevel' has initializer but incomplete type
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:263: error: unknown field 'name' specified in initializer
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:263: warning: excess elements in struct initializer
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:263: warning: (near initialization for 'fdtv_highlevel')
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:264: error: unknown field 'fcp_request' specified in initializer
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:264: warning: excess elements in struct initializer
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:264: warning: (near initialization for 'fdtv_highlevel')
/home/andrew/saa7164-stable/v4l/firedtv-1394.c: In function 'fdtv_1394_init':
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:271: error: implicit declaration of function 'hpsb_register_highlevel'
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:272: error: invalid use of undefined type 'struct hpsb_protocol_driver'
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:273: error: implicit declaration of function 'hpsb_register_protocol'
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:276: error: implicit declaration of function 'hpsb_unregister_highlevel'
/home/andrew/saa7164-stable/v4l/firedtv-1394.c: In function 'fdtv_1394_exit':
/home/andrew/saa7164-stable/v4l/firedtv-1394.c:283: error: implicit declaration of function 'hpsb_unregister_protocol'
make[3]: *** [/home/andrew/saa7164-stable/v4l/firedtv-1394.o] Error 1
make[2]: *** [_module_/home/andrew/saa7164-stable/v4l] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.31-17-generic'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/home/andrew/saa7164-stable/v4l'
make: *** [all] Error 2

silverdulcet
January 14th, 2010, 07:37 AM
make[3]: *** [/home/andrew/saa7164-stable/v4l/firedtv-1394.o] Error 1
make[2]: *** [_module_/home/andrew/saa7164-stable/v4l] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.31-17-generic'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/home/andrew/saa7164-stable/v4l'
make: *** [all] Error 2


See post #65:

i ran through the entirety of your setup instructions except i had to use

make CONFIG_DVB_FIREDTV:=n
instead of just "make"

Try it with that command and see if it compiles correctly. Alternatively you could use the linuxtv.org mercurial repository instead. See this Howto: http://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers

It just pulls the drivers from a different place and you have to change to a different directory:

cd v4l-dvb
then

make
or if you get that firedtv error

make CONFIG_DVB_FIREDTV:=n
as above.

finally

sudo make install

Then reboot and try that dmesg command once more to see if the drivers were successfuly loaded.

AJBalettie
January 14th, 2010, 08:37 PM
forgive me for being noob-ish, but when am I entering these lines?

silverdulcet
January 14th, 2010, 09:00 PM
forgive me for being noob-ish, but when am I entering these lines?

To use the saa7164-stable source you've already downloaded just issue the "make" command as before. Instead of using just the "make" command we are telling it to not build support for the firedtv module which is causing those errors that you posted above.

Ok, when you are on this step:
now change to the source directory


cd saa7164-stable

then run make, with the switch to not build the firedtv module


make CONFIG_DVB_FIREDTV:=n

It will start building the modules, and when it completes you should not see any of those "Error" lines at the end. If there are "Error" lines please post them here. If not then proceed to with the install step:


sudo make install

Once the modules are installed you can now reboot, and check to see if the driver and firmware loaded correctly with the command:


dmesg | grep saa

See my previous post that gives you an example of what the driver and firmware loading looks like.

YogiPaolo
January 15th, 2010, 01:20 AM
I'm having a new and interesting problem with the 2250 card.

I can record TV and watch live TV while recording. Things are going along smoothly and then without warning, I can't tune any channels. It's as if the card does not exist anymore. The tedius process of removing and adding the tuners in mythbackend solves the problem for a while. The problem returns repeatedly for three days now.

I did some digging in dmesg and found this interesting tidbit:


IRQ 16/saa7164[0]: IRQF_DISABLED is not guaranteed on shared IRQs

I am assuming that my 2.6.31-17-generic kernel is compiled with IRQF_DISABLED set to Y.

If this is the case, then why?
How can I check what options my kernel is compiled with?
I tried to download the source as per the Kernel compile wiki:https://help.ubuntu.com/community/Kernel/Compile#AltBuildMethod

But apt-get says it's not available.

How do I check the config of the current kernel?

I remember from my masochistic days running Gentoo the basics of how to compile. I'm looking into compiling another kernel...

AJBalettie
January 15th, 2010, 09:24 AM
I can not thank you guys enough for the help! My mythtv box now recognizes that there is a tv tuner in it!

now, when i scan for channels in the backend, it doesn't pick any up :-(

AJBalettie
January 15th, 2010, 09:28 AM
crap...i just read that this driver supports digital broadcast only...so if i have basic cable, i'm screwed right?

JeepFreak
January 16th, 2010, 09:17 PM
crap...i just read that this driver supports digital broadcast only...so if i have basic cable, i'm screwed right?

You should get some channels in HD. I have Comcast basic cable and I get 8 to 12 channels I think.

On to my own somewhat related question...
Programs that are "broadcast in high definition" on "standard definition" channels - can these programs be viewed with the HVR-2250? I'm currently viewing them on my PVR-250 because the channel didn't come up on the channel scan and the quality is clearly not HD. Should I be doing something different?

Thanks a bunch!
Billy

jeremycobert
January 18th, 2010, 01:43 AM
crap...i just read that this driver supports digital broadcast only...so if i have basic cable, i'm screwed right?

if you have an hdtv with a built in tuner card, you can try to scan everything and see if it picks up some unencrypted QAM channels. i get 7 of them on my basic cable. if you do get some to show up, then just setup the card and scan for QAM 256 and see if your mythbox finds any channels. if you do get this far, listen to mythtvcast epidsode 3 (i think) it explains how to re align the QAM channels to match your guide. http://mythtvcast.com/

kpholmes
January 19th, 2010, 07:44 PM
so i purchased the 2250 and i have it in a frontEnd/backEnd config running mythbuntu, but i have ran into a problem. i followed the thread and was able to get the capture card drivers installed and mythTV recognizes the card just fine, but when i go to watch live tv, it shows a black screen with the program info from schedules direct; and tells me my signal strength is 0%, and then closes with a pop up saying "error opening jump program file"

i've done a full QAM-256, and 64 scan, but cant seem to get any channels.

i have time warner cable and live in southern california if that helps, but im just trying to pick up the channels from 3 to 90. it would be greatly appreciated if someone could point me in the right direction on fixing this or if they need more info just let me know.

thanks

LowSky
January 19th, 2010, 08:32 PM
kpholmes did you scan for channels?

kpholmes
January 19th, 2010, 08:56 PM
ya. I scanned for QAM-64 and 256. Didn't find anything. I'm going to try 128 and see if I get anything.

kpholmes
January 19th, 2010, 09:17 PM
During the scans it can find encrypted channels but it also gets a fair amount of "time outs" and "possible channels"

cedyathome
January 19th, 2010, 10:03 PM
Does the Scan command give you any channels? See this link http://parker1.co.uk/mythtv_dvb.php Also, increase the timeouts in mythtv. It is in the capture card menu. I found that worked for me with a Pinnacle HD PCI (800i) card.

LowSky
January 19th, 2010, 10:10 PM
Check your connections, if you have cable splitter installed it can effect quality. I have seen the same problem occur when channel scanning. The purer the signal the better reception for picking up the channel. Note: once you have tuned the channels reinstall the splitter, it may not be an issue once the Tuner has the correct frequencies.

read this it might help if you still have problems
http://www.mythtv.org/wiki/Working_QAM_cable_layout

kpholmes
January 20th, 2010, 03:13 PM
well turns out its not going to work.


Digital Cable is typically encrypted, or encoded so that you need a cable box or CableCARD to view it. If you have 500 digital cable channels that you receive with a cable box, then the majority of these channels will be encrypted. A Clear QAM tuner cannot receive encrypted digital cable; it cannot receive the majority of your digital cable channels.
Therefore, you cannot use a cable box via Clear QAM, and you cannot receive most of your channels via Clear QAM.

thats what time warner told me when i sent them an email, i should of asked first :(

i was at a linux users group and they mentioned something about a card that my cable provider has to supply for this kind of situation where a customer wants a DVR but doesn't want to rent the cable providers hardware.

well im going to be off searching around why i can watch cable on my tv and not my computer. if i find anything useful ill be sure to post it, or if anyone has any ideas or info that might help im all ears.

thanks

LowSky
January 20th, 2010, 05:57 PM
kpholmes, I dont have TW but you should get a few channels in HD without a cable box, usually the local broadcastors or their affiliates like NBC, CBS, FOX, and ABC.

if your using a cable box that goes into the PC tuner, then you might have issues. because using a cable box with coax is actually a analog signal and wont work with this tuner card.

cedyathome
January 20th, 2010, 07:36 PM
Make sure the cable is connected to the top connector. I wasted a couple of hours because my cable was connected to the FM-input. Now, I'm struggling with jerky live-tv & horrible video quality.

LowSky
January 20th, 2010, 09:28 PM
Make sure the cable is connected to the top connector. I wasted a couple of hours because my cable was connected to the FM-input. Now, I'm struggling with jerky live-tv & horrible video quality.

Good thing to bring up.

kpholmes
January 20th, 2010, 10:10 PM
that makes sense since there isnt an analog driver for this card. haha : /

thanks for all the help. im going to try use a set top box connected to myth tv via firewire and see if i get any luck.

kpholmes
January 20th, 2010, 10:10 PM
Make sure the cable is connected to the top connector. I wasted a couple of hours because my cable was connected to the FM-input.

haha ya i remembered to double check that. i wish that was the problem though:D

lokness
January 21st, 2010, 05:29 AM
im having the same problem... but i have a time warner STB. i have a coax from the STB to the pvr2250 (the top coax) and im not getting any channels.

i am going to try and increase the max time outs and see what that does for me

lpnb
January 21st, 2010, 04:03 PM
Hi guys, don't know if anyone is subscribed to this tread but I really need some help.... maybe I am getting old but I have been working with linux for a few years now and built many Mythtv in various distros but this is driving me crazy....I normally try to figure things out but I am at the end of my rope on this one.

HVR-2250, mythbuntu 9.10, athon x64 5000+ ...the install went smoothly with the 64 bit version of mythbuntu:


dmesg | grep saa
or

dmesg | grep dvb
or

dmesg | grep hvr

yield nothing . so that's one thing, but should that stop the install of the driver.

I have followed a few of the install howto's including the one that I think is in this thread.

I had to install unzip as the first hurdle, and I also got an error after running


make menuconfig

I got an error :


*** Unable to find the ncurses libraries or the
*** required header files.
*** 'make menuconfig' requires the ncurses libraries.
***
*** Install ncurses (ncurses-devel) and try again.
***
make[3]: *** [scripts/kconfig/dochecklxdialog] Error 1
make[2]: *** [v4l-mconf] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.31-14-generic'
make[1]: *** [/lib/modules/2.6.31-14-generic/build/scripts/kconfig/mconf] Error 2
make[1]: Leaving directory `/home/lpnb/Downloads/saa7164-stable/v4l'
make: *** [menuconfig] Error 2


Now, I suspect this is related the the error I get when I run 'make'.

I have tried install ncurses devel but this does not fix the problem.

one of the howto's misses the
make menuconfig step which I don't understand.

I tried both the stable and the Devel releases no dice either way.

O.K. so there is two issues one is that I can't see it at all with dmesg and the other is the driver install errors. I had this driver installed on exactly the same system (sans new sata DVD drive) and it worked....I rebuilt because it was very unstable due to the massive amount customisation and it was broken. So I thought I would upgrade in the hope it would be more stable and see more of my hardware.

FYI,
the system also has a biostar TF560+ mobo, 750GB Green and quiet drive, nvidia Gigabyte 9600GT Silent graphics, 3 Noctua fans tuned to an acceptable speed for noise, MX-810 "universal remote control" (very nice but pricey) 100% custom made black anodised case. When I say custom I mean custom....even the HDD and CD brackets are hand made.... I started this damn thing 4 years ago and it has never been 100% with remote and tuner card working correctly. I have the remote working now....just need this nice tuner working.

thanks for listening!
Lachlan

LowSky
January 21st, 2010, 05:47 PM
you would you need make menuconfig?

your tuner should get up and running using my tutorial on page 1

lpnb
January 21st, 2010, 11:05 PM
Thankyou very much for the reply.

yes I followed that one, it is much the same as one I followed on a wiki site .....can't remember where that was but it was the same Except for the make menuconfig that I mentioned I have tried both..



you would you need make menuconfig?

your tuner should get up and running using my tutorial on page 1

lpnb
January 22nd, 2010, 01:46 AM
O.K. so I tried this little nugget of information:

http://www.mail-archive.com/ubuntu-devel-discuss@lists.ubuntu.com/msg09422.html

which basically says:


For anyone else having this problem I was able to get some resolution from
the guys in #v4l on IRC.

Basically the Firedtv driver needs the entire kernel source to compile - not
just the headers. They said they are aware of the problem and will address
it at some point.

So a quick work around is to disable the firedtv driver by modifying the
./v4l/.config file and changing '=m' to '=n' on the firedtv line.

The longer solution is to install the kernel source and then modify the
makefile configuration options to use that instead of the headers (it will
default to using the headers still if not configured correctly). If you're
not using firedtv, this is not worth it.

Thanks all who helped!

Now that was for v4l which I actually also tried to install but still could not see the card.

anyhow I found the same .config file in the /saa7164-stable/v4l directory and changed the line mentioned above....I did new


make
sudo make install

seemed to install now without any errors this time and rebooted.

dmesg | grep saa still does not yield anything. :-(

lpnb
January 22nd, 2010, 02:03 AM
O.K. so I also checked that the fw files were there also:

l
test@mythbox:~/Downloads/saa7164-stable$ cd /lib/firmware/
test@mythbox:/lib/firmware$ ls | grep 7164
v4l-saa7164-1.0.2.fw
v4l-saa7164-1.0.3.fw
test@mythbox:/lib/firmware$

I also notice the the 2.6.31-14 headers were installed so I removed them....as when the make was running I noticed that is says that it is using them.....I'll try again.

lpnb
January 22nd, 2010, 02:25 AM
O.K. looks like it installed but still not listed in dmesg

but


test@mythbox:/lib/modules/2.6.31-17-generic/kernel/drivers/media/video/saa7164$ ls
saa7164.ko
test@mythbox:/lib/modules/2.6.31-17-generic/kernel/drivers/media/video/saa7164$





~$ modprobe saa7164
FATAL: Module saa7164 not found.

lpnb
January 22nd, 2010, 04:15 AM
more:


$ lspci |grep 7164
03:00.0 Multimedia controller: Philips Semiconductors Device 7164 (rev 81)



$ modprobe -l | grep saa71
kernel/drivers/media/common/saa7146.ko
kernel/drivers/media/common/saa7146_vv.ko
kernel/drivers/media/video/saa7110.ko
kernel/drivers/media/video/saa7115.ko
kernel/drivers/media/video/saa717x.ko
kernel/drivers/media/video/saa7127.ko
kernel/drivers/media/video/saa7185.ko
kernel/drivers/media/video/saa7134/saa6752hs.ko
kernel/drivers/media/video/saa7134/saa7134.ko
kernel/drivers/media/video/saa7134/saa7134-empress.ko
kernel/drivers/media/video/saa7134/saa7134-alsa.ko
kernel/drivers/media/video/saa7134/saa7134-dvb.ko
$


$ modprobe -l | grep dvb-core
kernel/drivers/media/dvb/dvb-core/dvb-core.ko


Also there is no /dev/dvb

dvb-core does not seem to be loading either.

lokness
January 23rd, 2010, 09:17 AM
so, does using a coax cable from an STB to the 2250 card mean that the signal is not digital?

if so, should i be using s-video connection from STB to 2250 card?

dmacindoe
January 24th, 2010, 03:15 AM
I downloaded the HVR-2250 firmware and drivers this afternoon (Jan 23). As the MAKE process progressed, several errors were displayed, such as:

CC [M] /home/david/saa7164-stable/v4l/et61x251_core.o
/home/david/saa7164-stable/v4l/et61x251_core.c: In function 'et61x251_ioctl_v4l2':
/home/david/saa7164-stable/v4l/et61x251_core.c:2493: warning: the frame size of 1256 bytes is larger than 1024 bytes

CC [M] /home/david/saa7164-stable/v4l/firedtv-fe.o
CC [M] /home/david/saa7164-stable/v4l/firedtv-1394.o
/home/david/saa7164-stable/v4l/firedtv-1394.c:21:17: error: dma.h: No such file or directory
/home/david/saa7164-stable/v4l/firedtv-1394.c:22:21: error: csr1212.h: No such file or directory
/home/david/saa7164-stable/v4l/firedtv-1394.c:23:23: error: highlevel.h: No such file or directory

finishing up with:

/home/david/saa7164-stable/v4l/firedtv-1394.c: In function 'fdtv_1394_exit':
/home/david/saa7164-stable/v4l/firedtv-1394.c:283: error: implicit declaration of function 'hpsb_unregister_protocol'
make[3]: *** [/home/david/saa7164-stable/v4l/firedtv-1394.o] Error 1
make[2]: *** [_module_/home/david/saa7164-stable/v4l] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.31-14-generic'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/home/david/saa7164-stable/v4l'
make: *** [all] Error 2

Has anything recently changed in the driver?

Thanks for the help!

David

silverdulcet
January 24th, 2010, 04:52 AM
I downloaded the HVR-2250 firmware and drivers this afternoon (Jan 23). As the MAKE process progressed, several errors were displayed, such as:

CC [M] /home/david/saa7164-stable/v4l/et61x251_core.o
/home/david/saa7164-stable/v4l/et61x251_core.c: In function 'et61x251_ioctl_v4l2':
/home/david/saa7164-stable/v4l/et61x251_core.c:2493: warning: the frame size of 1256 bytes is larger than 1024 bytes

CC [M] /home/david/saa7164-stable/v4l/firedtv-fe.o
CC [M] /home/david/saa7164-stable/v4l/firedtv-1394.o
/home/david/saa7164-stable/v4l/firedtv-1394.c:21:17: error: dma.h: No such file or directory
/home/david/saa7164-stable/v4l/firedtv-1394.c:22:21: error: csr1212.h: No such file or directory
/home/david/saa7164-stable/v4l/firedtv-1394.c:23:23: error: highlevel.h: No such file or directory

finishing up with:

/home/david/saa7164-stable/v4l/firedtv-1394.c: In function 'fdtv_1394_exit':
/home/david/saa7164-stable/v4l/firedtv-1394.c:283: error: implicit declaration of function 'hpsb_unregister_protocol'
make[3]: *** [/home/david/saa7164-stable/v4l/firedtv-1394.o] Error 1
make[2]: *** [_module_/home/david/saa7164-stable/v4l] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.31-14-generic'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/home/david/saa7164-stable/v4l'
make: *** [all] Error 2

Has anything recently changed in the driver?

Thanks for the help!

David

Post #81 (http://ubuntuforums.org/showpost.php?p=8662140&postcount=81) on Page 9 (http://ubuntuforums.org/showthread.php?t=942403&page=9) addresses this very same problem. Earlier somewhere around Post #65 the work-around was posted. Search this Thread is your friend. ;)

If you only have this tuner. I'd recommend using the main linuxtv.org v4l-dvb mercurial repo instead of just the driver that is posted in the original how-to. The reason for this is that you won't run into the firedtv errors anymore.

This includes the fixes for all the tuners supported by v4l-dvb. A warning however, its possible that other cards supported by v4l-dvb might stop working. In my experience they fix problems like that fairly quickly. I am currently using the linuxtv.org v4l-dvb mercurial repo for my HVR-2250 and my HVR-1600.

If you insist on using the driver from kernellabs, then use the option mentioned in the posts I linked above to exclude the firedtv module.

lpnb
January 24th, 2010, 04:55 AM
so, does using a coax cable from an STB to the 2250 card mean that the signal is not digital?

if so, should i be using s-video connection from STB to 2250 card?

It depends on the set top box. but this driver only supports a digital signal. so if you have it working and you are watching TV under linux then it must be digital.

do you change channels via the STB or the linux box. if it is the linux box then the signal that you are receiving is just a passed through signal from the antenna so it is as if you just have the antenna connected to the linux box.

lokness
January 24th, 2010, 07:19 AM
thanks lpnb, i am not seeing anything and i cant even get the backend setup to pickup a channel. must not be digital. it seems like the rest of the setup has worked but i cant get any channels. bummer.

thanks

lokness
January 24th, 2010, 07:43 AM
just for the rest of the community who might have what i have and its working for you and im just missing something.

i have a scientific atlanta explorer 4240HDC time warner digital cable STB
-- digital channels from 104-178 (San Antonio, Tx with TW Digital Basic Cable)

my box:
Acer X1200 X2 X64
Athlon X2 Dual Core 2.5GHz
Integrated NVIDIA GeForce 8200
and of course
Hauppauge hvr 2250

[ 5.306241] saa7164 driver loaded
[ 5.306358] saa7164 0000:04:00.0: PCI INT A -> Link[AE2A] -> GSI 16 (level, low) -> IRQ 16
[ 5.306669] CORE saa7164[0]: subsystem: 0070:8891, board: Hauppauge WinTV-HVR2250 [card=7,autodetected]
[ 5.306675] saa7164[0]/0: found at 0000:04:00.0, rev: 129, irq: 16, latency: 0, mmio: 0xfd400000
[ 5.306680] saa7164 0000:04:00.0: setting latency timer to 64
[ 5.306684] IRQ 16/saa7164[0]: IRQF_DISABLED is not guaranteed on shared IRQs
[ 5.510018] saa7164_downloadfirmware() no first image
[ 5.510028] saa7164_downloadfirmware() Waiting for firmware upload (v4l-saa7164-1.0.3.fw)
[ 5.510032] saa7164 0000:04:00.0: firmware: requesting v4l-saa7164-1.0.3.fw
[ 6.462109] saa7164_downloadfirmware() firmware read 3978608 bytes.
[ 6.462112] saa7164_downloadfirmware() firmware loaded.
[ 6.462120] saa7164_downloadfirmware() SecBootLoader.FileSize = 3978608
[ 6.462126] saa7164_downloadfirmware() FirmwareSize = 0x1fd6
[ 6.462127] saa7164_downloadfirmware() BSLSize = 0x0
[ 6.462129] saa7164_downloadfirmware() Reserved = 0x0
[ 6.462130] saa7164_downloadfirmware() Version = 0x51cc1
[ 13.640014] saa7164_downloadimage() Image downloaded, booting...
[ 13.740013] saa7164_downloadimage() Image booted successfully.
[ 16.130017] saa7164_downloadimage() Image downloaded, booting...
[ 17.570016] saa7164_downloadimage() Image booted successfully.
[ 17.610480] saa7164[0]: Hauppauge eeprom: model=88061
[ 18.334677] DVB: registering new adapter (saa7164)
[ 21.688068] DVB: registering new adapter (saa7164)
.
.
.
[ 17.610463] tveeprom 2-0000: Hauppauge model 88061, rev C3F2, serial# 6446729
[ 17.610466] tveeprom 2-0000: MAC address is 00-0D-FE-62-5E-89
[ 17.610469] tveeprom 2-0000: tuner model is NXP 18271C2_716x (idx 152, type 4)
[ 17.610471] tveeprom 2-0000: TV standards NTSC(M) ATSC/DVB Digital (eeprom 0x88)
[ 17.610474] tveeprom 2-0000: audio processor is SAA7164 (idx 43)
[ 17.610476] tveeprom 2-0000: decoder processor is SAA7164 (idx 40)
[ 17.610478] tveeprom 2-0000: has radio, has IR receiver, has no IR transmitter


i guess the blaster isnt supported? when i plug it in, the blaster light stays on - hmm weird.

well, like i said, i believe it is working, i just cant seem to get any channels using mythbuntu's scanning function in the backend setup.

i have scanned using 'Cable High' QAM256 and QAM64. i have also changed the tuning and scan interval from their defaults to greater values.

lokness
January 24th, 2010, 07:52 AM
arrrgghh, i forgot to add that the acer has an hdmi output and that is what i am using to connect to my TV.

silverdulcet
January 24th, 2010, 07:55 AM
just for the rest of the community who might have what i have and its working for you and im just missing something.

i have a scientific atlanta explorer 4240HDC time warner digital cable STB
-- digital channels from 104-178 (San Antonio, Tx with TW Digital Basic Cable)

my box:
Acer X1200 X2 X64
Athlon X2 Dual Core 2.5GHz
Integrated NVIDIA GeForce 8200
and of course
Hauppauge hvr 2250

[ 5.306241] saa7164 driver loaded
[ 5.306358] saa7164 0000:04:00.0: PCI INT A -> Link[AE2A] -> GSI 16 (level, low) -> IRQ 16
[ 5.306669] CORE saa7164[0]: subsystem: 0070:8891, board: Hauppauge WinTV-HVR2250 [card=7,autodetected]
[ 5.306675] saa7164[0]/0: found at 0000:04:00.0, rev: 129, irq: 16, latency: 0, mmio: 0xfd400000
[ 5.306680] saa7164 0000:04:00.0: setting latency timer to 64
[ 5.306684] IRQ 16/saa7164[0]: IRQF_DISABLED is not guaranteed on shared IRQs
[ 5.510018] saa7164_downloadfirmware() no first image
[ 5.510028] saa7164_downloadfirmware() Waiting for firmware upload (v4l-saa7164-1.0.3.fw)
[ 5.510032] saa7164 0000:04:00.0: firmware: requesting v4l-saa7164-1.0.3.fw
[ 6.462109] saa7164_downloadfirmware() firmware read 3978608 bytes.
[ 6.462112] saa7164_downloadfirmware() firmware loaded.
[ 6.462120] saa7164_downloadfirmware() SecBootLoader.FileSize = 3978608
[ 6.462126] saa7164_downloadfirmware() FirmwareSize = 0x1fd6
[ 6.462127] saa7164_downloadfirmware() BSLSize = 0x0
[ 6.462129] saa7164_downloadfirmware() Reserved = 0x0
[ 6.462130] saa7164_downloadfirmware() Version = 0x51cc1
[ 13.640014] saa7164_downloadimage() Image downloaded, booting...
[ 13.740013] saa7164_downloadimage() Image booted successfully.
[ 16.130017] saa7164_downloadimage() Image downloaded, booting...
[ 17.570016] saa7164_downloadimage() Image booted successfully.
[ 17.610480] saa7164[0]: Hauppauge eeprom: model=88061
[ 18.334677] DVB: registering new adapter (saa7164)
[ 21.688068] DVB: registering new adapter (saa7164)


i guess the blaster isnt supported? when i plug it in, the blaster light stays on - hmm weird.

well, like i said, i believe it is working, i just cant seem to get any channels using mythbuntu's scanning function in the backend setup.

Just to clarify the analogue part of this card is not supported in the drivers yet.

You can either tune OTA ATSC with an antenna or with some cable providers you can plug the cable feed directly from the wall into the card and scan for unencrypted QAM channels. There are several modes to try in mythtv-setup.

If you want to use a set-top box you need a card that can record by connecting the box via SVIDEO, or component cables (such as the Hauppauge HD-PVR, which is an external box).

Yes, the blaster is not yet supported AFAIK. This is also mentioned earlier in this thread.

lpnb
January 24th, 2010, 11:25 PM
:D fixed it!

I used the repo and the info here:
www.linuxtv.org/rep

I thought that I had tried it before but anyway this time it worked.

Thanks silverdulcet for your suggestions and help!!!

now I just need to get it to scan....its not getting anything.

last time I had this card working under another build I had to manual specify the transports....anyway I am sure it won't take too long.

gmoser
January 25th, 2010, 03:16 AM
So does anyone know why:
cp *fw /lib/firmware

Results in:

cp: cannot create regular file `/lib/firmware/dvb-fe-tda10048-1.0.fw': Permission denied
cp: cannot create regular file `/lib/firmware/v4l-saa7164-1.0.2.fw': Permission denied
cp: cannot create regular file `/lib/firmware/v4l-saa7164-1.0.3.fw': Permission denied

Big Linux fan but it's stuff like this that is forcing me back to Windows :(

lpnb
January 25th, 2010, 04:34 AM
This is may be the first time I have ever offered linux help!! but for me I needed:


sudo cp *fw /lib/firmware

mostly normal users don't have the permissions required for lots of system directories.

I feel like that occasionally myself. but for some reason I am sticking with it. I just get a lot of satisfaction once it is going. :-) and I have a passionate about my dislike of M$ and what they stand for....off topic...sorry...

Anyway, I'll help if I can but there are much more qualified people on this forum than I.

Also I can recommend the v4l post I put up just before and was very successfull for me....though I am still having trouble scanning for channels.


So does anyone know why:
cp *fw /lib/firmware

Results in:

cp: cannot create regular file `/lib/firmware/dvb-fe-tda10048-1.0.fw': Permission denied
cp: cannot create regular file `/lib/firmware/v4l-saa7164-1.0.2.fw': Permission denied
cp: cannot create regular file `/lib/firmware/v4l-saa7164-1.0.3.fw': Permission denied

Big Linux fan but it's stuff like this that is forcing me back to Windows :(

cedyathome
January 25th, 2010, 10:52 PM
I see that there is a new firmware version on the Happaugue site.
How do I extract the firmware from that release?
Are the drivers dependent on the firmware release?
There are instructions on post #40, but no one confirmed that it works.

Secondly, in MythTV, I always see a signal strength of 0 (or a blank field).
Does anyone else see a signal strength?
My TV works just fine and I seem to be seeing most channels in my scan.

Thank you.

LowSky
January 25th, 2010, 11:56 PM
I see that there is a new firmware version on the Happaugue site.
How do I extract the firmware from that release?
Are the drivers dependent on the firmware release?
There are instructions on post #40, but no one confirmed that it works.

Thank you.

That isn't firmware it's a Windows driver, The V4L driver is newer, please use that.

LowSky
January 26th, 2010, 12:01 AM
By this weekend I hope to get the Tutorial updated, Sorry I have not done it sooner I have just been really busy and wish I didn't have so much work to do.

If anyone feels I should use a certain method or step I forget to include before please feel free to PM me or leave a note in this thread.

lpnb
January 26th, 2010, 01:36 AM
I am now watching Tellie!!

woo hoo.... its working well and hasn't crashed yet!!!

I was scanning the channels before and was getting NOTHING just timeouts....but in my efforts to get the driver installed I had re-compiled the kernel to make sure all the modules installed (dvb-core was not loading). after re-compiling I had some luck and got it to install the driver with the v4l-org install but I don't think that the kernel was what helped in this case.

So Anyway, after getting the device to be detected I could not scan successfully even with specifying the transports manually. I reverted back to the old generic kernel 2.6.31.17-generic (I think) suddenly and with no other changes it successfully scanned all channels without any specified transports. woohooo.....

Well I can say that it seems to me to be a bit faster than the DViCO Dual Digital to that eventually died and jut never worked right and it also seems a lot more stable with this newer Mythbuntu release. 9.10 ....

lots of tweaking to do and set up the graphics driver for my silly 1366x768 TV but thats o.k. I have done that a million times.

Anybody that has had similar problems I will do my best to help.

Hwy120
January 26th, 2010, 01:44 PM
By this weekend I hope to get the Tutorial updated, Sorry I have not done it sooner I have just been really busy and wish I didn't have so much work to do.

If anyone feels I should use a certain method or step I forget to include before please feel free to PM me or leave a note in this thread.

I am fairly new to Linux/Ubuntu and Myth TV. In addition to updating the procedure, please provide the correct steps to use when the kernel is updated and the drivers need to be reinstalled. I have had problems with reinstalling the drivers. The error I received was about directories not being empty. So I assume that reinstalling the drivers should be done differently.

Thank you for the guidance you, and others, have provided in this thread.

cedyathome
January 26th, 2010, 10:28 PM
Lowsky,
I followed your tutorial right after installing mythbuntu 9.10. Here are the only 2 points where I needed to deviate from the scripts (both have been covered in previous posts on this thread)

1. install unzip. this isn't included in mythbuntu 9.10. so, the


# sudo apt-get install unzip should be added right at the beginning.

2. The "make" command bombs out because some card in there needs the whole kernel source. DanBataar pointed out the command to exclude that card.

make CONFIG_DVB_FIREDTV:=n || returnThanks for taking the time to create the tutorial.

cedyathome
January 26th, 2010, 10:30 PM
bump. Anyone?


...

Secondly, in MythTV, I always see a signal strength of 0 (or a blank field).
Does anyone else see a signal strength?
My TV works just fine and I seem to be seeing most channels in my scan.

Thank you.

LowSky
January 27th, 2010, 12:09 AM
cedyathome I will try to look into your signal issue. I could have sworn that was a minor issue with the 2250 driver... I'll keep an eye out.

Just to clarify My original tutorial used regular Ubuntu, and MythTV was installed on a current system, so maybe I didn't notice a few packages that are required.

I'm really bummed I haven't been working on this project to update it. I've been just too busy. I wanted to begin after getting back from CES, but too much work mixed with family and friend obligations are keeping me away. It's one thing to post a comment on the forum for help, but building a new system and documenting the process is a lot of work.

To shed more light on my new project I will at least start off by listing the components I will use



Ubuntu 9.10, I will used the MythTV packages from the Repo's. Sorry if this offends anyone but I prefer it over Mythbuntu
AMD Phenom 9950 Agena 2.6GHz
GIGABYTE GA-MA78GM-S2H AM2+/AM2 AMD 780G HDMI Micro ATX AMD Motherboard
SAPPHIRE 100252HDMI Radeon HD 4550 512MB 64-bit GDDR3 PCI Express 2.0 x16 HDCP Ready CrossFireX Support Low Profile Ready Video Card
Hauppauge WinTV-HVR-2250 Media Center Kit Dual TV Tuner 1213 PCI-Express x1
Samsung 750GB SATA Hard Drive - for OS and Video recording
Seagate 500GB SATA Hard Drive - For backed up movies and music.

clutzer
January 29th, 2010, 12:40 AM
Has anyone figured out how to get the remote (which is NOT USB) working with this card? I suspect LIRC (lirc_i2c) needs be updated to support it. I say this because the IR cable and plug seem almost exactly the same as my old Hauppage PVR-250 card which used lirc_i2c. Thoughts?

lpnb
January 29th, 2010, 03:21 AM
Don't know but I bought a HP OVU400102/71 Media centre remote receiver and remote off ebay for a few dollars which works straight out of the box. although it controls my partners HP Laptop at the same time which has some interesting results!! LOL


Has anyone figured out how to get the remote (which is NOT USB) working with this card? I suspect LIRC (lirc_i2c) needs be updated to support it. I say this because the IR cable and plug seem almost exactly the same as my old Hauppage PVR-250 card which used lirc_i2c. Thoughts?

lokness
January 29th, 2010, 07:52 AM
[ 5.481365] saa7164 driver loaded
[ 5.481450] saa7164 0000:04:00.0: PCI INT A -> Link[AE2A] -> GSI 16 (level, low) -> IRQ 16
[ 5.481795] CORE saa7164[0]: subsystem: 0070:8891, board: Hauppauge WinTV-HVR2250 [card=7,autodetected]
[ 5.481801] saa7164[0]/0: found at 0000:04:00.0, rev: 129, irq: 16, latency: 0, mmio: 0xfd400000
[ 5.481806] saa7164 0000:04:00.0: setting latency timer to 64
[ 5.481810] IRQ 16/saa7164[0]: IRQF_DISABLED is not guaranteed on shared IRQs
[ 5.690012] saa7164_downloadfirmware() no first image
[ 5.690022] saa7164_downloadfirmware() Waiting for firmware upload (v4l-saa7164-1.0.3.fw)
[ 5.690026] saa7164 0000:04:00.0: firmware: requesting v4l-saa7164-1.0.3.fw
[ 6.143458] saa7164_downloadfirmware() firmware read 3978608 bytes.
[ 6.143461] saa7164_downloadfirmware() firmware loaded.
[ 6.143469] saa7164_downloadfirmware() SecBootLoader.FileSize = 3978608
[ 6.143474] saa7164_downloadfirmware() FirmwareSize = 0x1fd6
[ 6.143475] saa7164_downloadfirmware() BSLSize = 0x0
[ 6.143477] saa7164_downloadfirmware() Reserved = 0x0
[ 6.143478] saa7164_downloadfirmware() Version = 0x51cc1
[ 13.430043] saa7164_downloadimage() Image downloaded, booting...
[ 13.540019] saa7164_downloadimage() Image booted successfully.
[ 15.930014] saa7164_downloadimage() Image downloaded, booting...
[ 17.360017] saa7164_downloadimage() Image booted successfully.
[ 17.400598] saa7164[0]: Hauppauge eeprom: model=88061
[ 18.154789] DVB: registering new adapter (saa7164)
[ 21.418377] DVB: registering new adapter (saa7164)

[ 17.400581] tveeprom 2-0000: Hauppauge model 88061, rev C3F2, serial# 6446729
[ 17.400585] tveeprom 2-0000: MAC address is 00:0d:fe:62:5e:89
[ 17.400587] tveeprom 2-0000: tuner model is NXP 18271C2_716x (idx 152, type 4)
[ 17.400590] tveeprom 2-0000: TV standards NTSC(M) ATSC/DVB Digital (eeprom 0x88)
[ 17.400592] tveeprom 2-0000: audio processor is SAA7164 (idx 43)
[ 17.400594] tveeprom 2-0000: decoder processor is SAA7164 (idx 40)
[ 17.400596] tveeprom 2-0000: has radio, has IR receiver, has no IR transmitter


ok, i see this from dmesg but i still cant get any channels to come up. i also dont see QAM in the TV standards line. could this be my problem?

i am connected from my STB to the 2250 using s-video

arrrgghh, what am i doing wrong?

LowSky
January 29th, 2010, 03:24 PM
ok, i see this from dmesg but i still cant get any channels to come up. i also dont see QAM in the TV standards line. could this be my problem?

i am connected from my STB to the 2250 using s-video

arrrgghh, what am i doing wrong?

S-video does not work, only digital cable works. Take the cable box out of the equation connect your cable directly to the PC and scan for channels. Note you will not get anywhere near the number you have with a cable box.

Sorry but if you want to watch from your cable box you will need a different TV card. Specifically one that has analog support.

gmoser
January 30th, 2010, 02:58 PM
This is may be the first time I have ever offered linux help!! but for me I needed:


sudo cp *fw /lib/firmware

mostly normal users don't have the permissions required for lots of system directories.

I feel like that occasionally myself. but for some reason I am sticking with it. I just get a lot of satisfaction once it is going. :-) and I have a passionate about my dislike of M$ and what they stand for....off topic...sorry...



Thanks for that! I tried Sudo as well and no luck. I figured this was just outdated so I await the re-release of the tutorial. I may pick up a different card as analog support may be required down the road. If by "digital" I will only receive the HD broadcasted signals via coax it will net me about 10 channels. Hardly enough! How do I go on with life missing people getting Tazed on Cops??

lokness
January 30th, 2010, 03:53 PM
has anyone here tried to use the channels.conf option when scanning for channels? i would like to maybe build a channels.conf file but dont know how.

and im still not getting any channels either directly using the coax cable and taking the STB out or through the STB using s-video - bummer.

the scan doesnt seem to use the broadcast-digital (4-1) channels. it seems to skip over them.

gmoser
January 30th, 2010, 08:56 PM
and im still not getting any channels either directly using the coax cable and taking the STB out or through the STB using s-video - bummer.

the scan doesnt seem to use the broadcast-digital (4-1) channels. it seems to skip over them.

You won't get any thru the S-video since analog is not supported. It's in about every page of this 14 page thread. I hope that is resolved shortly though.

lpnb
January 31st, 2010, 10:57 AM
Take the STB out of the equation altogether. plug your antenna into the card and try a scan.

you could also try manually adding the transports and then do a scan. once before that worked for me but that was on an earlier version of the beta driver for this card.

here is a link to a thread containing some transport for newcastle. (are you in Australia?)
http://www.mythtvtalk.com/forum/installation-issues/6993-channel-scan-abc-australia.html

I never have been able to find a list of all the transports for all the transmitters around Australia.

Also try using w_scan:
http://edafe.org/vdr/w_scan/




has anyone here tried to use the channels.conf option when scanning for channels? i would like to maybe build a channels.conf file but dont know how.

and im still not getting any channels either directly using the coax cable and taking the STB out or through the STB using s-video - bummer.

the scan doesnt seem to use the broadcast-digital (4-1) channels. it seems to skip over them.

440corbon
February 7th, 2010, 06:04 PM
I have finally managed to get the drivers installed and scan for channels with a set top antenna hooked up. I am locking on possible channels but getting no signal lock. I am wondering if this is an issue with the card(have it in a pcie 2 slot,I don't have pcie 1 slots on my motherboard) or if this is just too week of a signal. If anyone has an answer to this it would help me out a lot. TIA

440corbon
February 8th, 2010, 12:29 AM
OK. I'm an idiot. I thought it wasn't working. But I'm watching the Super Bowl right now. However it still shows no signal strength. I also added a few permissions in ubuntu I didn't have ticked.

perato
February 8th, 2010, 01:13 AM
You might need to increase the time mythtv waits for the signal to lock on. There is an option buried in mythtv-setup. I'm using archlinux with mythtv from the extra repository. I recommend setting it to 7 to 10 seconds.

gmoser
February 8th, 2010, 03:34 AM
So I re-tried the steps listed on page one, and its still no go. I run LSPCI and here's what I get:


00:00.0 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a1)
00:01.0 ISA bridge: nVidia Corporation MCP61 LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation MCP61 SMBus (rev a2)
00:01.2 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a2)
00:02.0 USB Controller: nVidia Corporation MCP61 USB Controller (rev a3)
00:02.1 USB Controller: nVidia Corporation MCP61 USB Controller (rev a3)
00:04.0 PCI bridge: nVidia Corporation MCP61 PCI bridge (rev a1)
00:05.0 Audio device: nVidia Corporation MCP61 High Definition Audio (rev a2)
00:07.0 Bridge: nVidia Corporation MCP61 Ethernet (rev a2)
00:08.0 IDE interface: nVidia Corporation MCP61 SATA Controller (rev a2)
00:08.1 IDE interface: nVidia Corporation MCP61 SATA Controller (rev a2)
00:09.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2)
00:0b.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2)
00:0c.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2)
00:0d.0 VGA compatible controller: nVidia Corporation C61 [GeForce 6150SE nForce 430] (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Link Control
03:00.0 Multimedia controller: Philips Semiconductors Device 7164 (rev 81)
04:00.0 Communication controller: Agere Systems Device 0630 (rev 01)


I don't think its in there... ARRRGGG! Lil help?

440corbon
February 8th, 2010, 03:37 AM
Perato....it is working.I can watch tv. I did increase my scan times to 7ooo ms. I still don't get anything on the strength meter though. In the spring I will mount a roof antenna and see how things work out. But I thank you for the input. I know it may help some others

440corbon
February 8th, 2010, 04:05 AM
here is what I get from dmesg | grep saa
[ 21.335540] saa7164 driver loaded
[ 21.335785] saa7164 0000:01:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[ 21.335997] CORE saa7164[0]: subsystem: 0070:8851, board: Hauppauge WinTV-HVR2250 [card=7,autodetected]
[ 21.336002] saa7164[0]/0: found at 0000:01:00.0, rev: 129, irq: 19, latency: 0, mmio: 0xf9800000
[ 21.336006] saa7164 0000:01:00.0: setting latency timer to 64
[ 21.336010] IRQ 19/saa7164[0]: IRQF_DISABLED is not guaranteed on shared IRQs
[ 21.540035] saa7164_downloadfirmware() no first image
[ 21.540081] saa7164_downloadfirmware() Waiting for firmware upload (v4l-saa7164-1.0.3.fw)
[ 21.540084] saa7164 0000:01:00.0: firmware: requesting v4l-saa7164-1.0.3.fw
[ 21.553090] saa7164_downloadfirmware() firmware read 3978608 bytes.
[ 21.553092] saa7164_downloadfirmware() firmware loaded.
[ 21.553098] saa7164_downloadfirmware() SecBootLoader.FileSize = 3978608
[ 21.553138] saa7164_downloadfirmware() FirmwareSize = 0x1fd6
[ 21.553139] saa7164_downloadfirmware() BSLSize = 0x0
[ 21.553140] saa7164_downloadfirmware() Reserved = 0x0
[ 21.553141] saa7164_downloadfirmware() Version = 0x51cc1
[ 28.420070] saa7164_downloadimage() Image downloaded, booting...
[ 28.530075] saa7164_downloadimage() Image booted successfully.
[ 30.890073] saa7164_downloadimage() Image downloaded, booting...
[ 32.320055] saa7164_downloadimage() Image booted successfully.
[ 32.360733] saa7164[0]: Hauppauge eeprom: model=88061
[ 33.084657] DVB: registering new adapter (saa7164)
[ 36.398085] DVB: registering new adapter (saa7164)

440corbon
February 8th, 2010, 04:25 AM
from low sky's post in the become famous thread.


wget http://www.steventoth.net/linux/hvr22xx/22xxdrv_27086.zip
wget http://www.steventoth.net/linux/hvr22xx/HVR-12x0-14x0-17x0_1_25_25271_WHQL.zip
wget http://www.steventoth.net/linux/hvr22xx/extract.sh

sh extract.sh
sudo cp *fw /lib/firmware


you need to install mercurial and build essential for the next steps


sudo apt-get install mercurial build-essential



then we need the driver using this command to fetch


hg clone http://kernellabs.com/hg/saa7164-stable/

now change to the directory


cd saa7164-stable

for fixing after kernal update only otherwise go to next step


make distclean

then from silver dulcet on page 9 of this thread


make CONFIG_DVB_FIREDTV:=n


sudo make install

sudo reboot

dmesg | grep saa
if everything worked out you will have something like my previous post as a result.

LowSky
February 8th, 2010, 06:27 PM
440corbon I hope all is working...

Sorry I havent been around. I went to to do my upgrade and found out the RAM I'm using is bad, and it needs more testing to find out if its one stick or both, and then an RMA for replacement. I know Awesome... Right!

440corbon
February 8th, 2010, 07:58 PM
Everything was good until this morning. I broke something. I couldn't access my server. So I just reformatted. I'll be back up and running in a few hours. I actually pieced together your guide to help someone out last night. lol...Now I am going to be using it again.
And a Major THANKS for the work you have done.

gmoser
February 11th, 2010, 02:23 PM
Thanks bud! Seemed like the piece mail instructions weren't doing anything, but followed this one line by line and I have them listed in myth now.

Still trying to get channels listed and live TV but at least one portion is working correctly!

jjwest85
February 13th, 2010, 01:38 AM
These instructions worked perfectly for me too!

I would like to bring up the issue with the packaged remote control. I know the driver does not support it currently, but I was curious if there are plans to get this working?

If there are no plans, then I was curious if anybody has a good recommendation for a remote/receiver that works with Ubuntu 9.10 out of the box?

Hwy120
February 13th, 2010, 11:00 PM
Do the TV tuner drivers eventually get integrated into the product, or will we always have to reinstall them after every kernel update?

440corbon
February 14th, 2010, 02:45 PM
I would really like them to get integrated into the kernel. as well as the fm capabilities

jimko
February 14th, 2010, 04:54 PM
The DVB wiki page (http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-2250) for the Hauppauge2250, updated in Dec '09, says support is expected in the 2.6.32 kernel.

i just installed this card yesterday and seems to be working correctly in Mythbuntu Karmic on AMD64. However, it went crazy overnight and filled my disk with log messages like the following:


Feb 14 07:47:09 myth1 kernel: [55883.613679] saa7164_api_i2c_read() error, ret(1) = 0xc
Feb 14 07:47:09 myth1 kernel: [55883.613683] s5h1411_readreg: readreg error (ret == -5)
Feb 14 07:47:09 myth1 kernel: [55883.663584] saa7164_cmd_send() No free sequences


It repeated this enough to write out about 2G of log messages before it ran out of resources. It's cyclic, so I don't know if I've displayed the sequence in the correct order. I built the drivers from the stable branch of the drivers and it seemed to finish clean.

After I cleared the space and rebooted, mythfrontend status reported both tuners as "asleep." Starting and stopping mythbackend woke them back up and they seem to be functioning normally again.

Right now, my plan is to hope it doesn't happen again.

rayok
February 16th, 2010, 12:50 AM
Hello.. as a "noob" I'm having problems with this card. I'm running Mythbuntu 9.10 AMD64, kernel 2.6.31-19-generic, all updates. I first followed 440carbon's instructions above. The compile and install went fine but when watching TV I get a duplicate view. That is, the image is shown twice, on the top-half and bottom-half of the screen. I figured it was the driver so I ran sudo make unload and sudo make rminstall to hopefully remove that driver and try the V4L-DVB linuxtv driver. Well, after using the same CONFIG_DVB_FIRETV:=n on that it compiles and installs but same exact duplicate view. What gives? :???:

Also when switching channels it sometimes errors with the message "Error opening jump program file buffer" but I think this one is fixed in future releases but have no idea about those..

Thanks in advance..

Xailia
February 16th, 2010, 04:40 AM
Rayok - I forget the exact setting, but instead the playback settings you have to adjust the interlacing. Guess and check unless someone else knows off the top of their head.

Xailia
February 16th, 2010, 04:43 AM
Thanks for all the instructions and suggestions on getting this working - I appreciate the time you guys have put into this.

After getting my first HVR-2250 working with myth I was encouraged to buy a second one. The strange this is that the second one seems to only work after I delete all the tuner cards from the mythtv-setup. After a little while of idle time (maybe an hour) I am unable to get a signal from the second card. (deleting all tuners fixes the issue).

Any thoughts on where to start with this issue? I am at a lose.

xinix
February 16th, 2010, 06:39 AM
I'm having an annoying issue with this card. The card itself works really well after I restart the backend. I think it is because the driver is loading after the backend has been started, just my best guess though. After a cold boot the tuner is reported as offline even though dmesg clearly shows the driver loaded just fine. It is reported as online once the backend is restarted.

Any ideas?

Never mind, I found a thread with a solution.

rayok
February 16th, 2010, 07:25 AM
Rayok - I forget the exact setting, but instead the playback settings you have to adjust the interlacing. Guess and check unless someone else knows off the top of their head.

Yay! That kinda fixed it :) After a while of searching I finally hit the magical M (menu) key and found the only place that setting exists. It's under Video Scan and it was set to "Detect" (ha!) and had to set it to Progressive (even though I think its 1080i) and it worked fine. Thanks again..

The picture itself is OK. Its a little washed out/too bright compared to the TV itself and I can see horizontal interlacing artifacts albeit very small. My guess is either the video driver (ATI resticted on integrated HD4200) or the fact its not live and is being recorded. I'm not sure how to set it to 100% live TV, its always 4-5 seconds behind. On top of all this I tried recording. I mean, I think its recording but I'm not sure. After a few hours of "recording" I went back to check on it and it crashed saying something like the video buffer failed too many times. After that I could not get back to watching TV or see if the recording worked. When I checked system status it says its recording and the HD light is blinking but I have no idea how to confirm anything. I exited the frontend and tried to kill it but it wouldn't let me. I gave up and shut down for the night..

So anyway, I'm happy that I got this far but then again I'm so frustrated at how many retarded things I have to go through to get there.. I would like to help if I can but don't have the time outside of work and other projects. In the meantime I think I'll take a look at Linux MCE..

440corbon
February 19th, 2010, 01:03 AM
Glad to see people getting things working. I just want to clarify that my prior post were taken from Silver and lowsky. They are the ones that deserve the thanks not me.
Now for those who have not been able to get their cards to scan for channels. In the video sources section of your backend setup label it. Run this twice giving it a different name for each one. I just called it schedule0 and the second one schedule1. In input connections (which you will also need to run twice. Put the name of one of your video sources. This was the hiccup I had when trying to scan for channels. I hadn't labeled where it should look fo information.

dwhecht
February 21st, 2010, 07:00 PM
Thanks for your help here. I followed the directions and I'm successfully recording digital TV now. Quality looks great and seems reliable.

I have a related question. I see an absence of information regarding the IR receiver and blaster that come with the 2250 product. The IR receiver and blaster do not have linux drivers that work for them, correct? I see people asking for it on some kernellabs posts for the saa1764, but I wanted some additional confirmation.

Thanks,

David

440corbon
February 22nd, 2010, 02:53 AM
I have not seen anything positive about the ir yet. But this is an incredible group of people and I am hopeful it will be resolved.

gmoser
February 22nd, 2010, 02:11 PM
i was reading on the hvr-1600 and it looks like that one has ir as well and should work. i may pick one up and test it out. can never have too many tuner cards right

LowSky
February 22nd, 2010, 03:56 PM
I'm having an annoying issue with this card. The card itself works really well after I restart the backend. I think it is because the driver is loading after the backend has been started, just my best guess though. After a cold boot the tuner is reported as offline even though dmesg clearly shows the driver loaded just fine. It is reported as online once the backend is restarted.

Any ideas?

Never mind, I found a thread with a solution.

Could you post a copy of the thread here, it may help others.

xinix
February 22nd, 2010, 04:14 PM
Could you post a copy of the thread here, it may help others.

I haven't taken the time to implement the fix, but here is the thread.

http://ubuntuforums.org/showthread.php?t=1345079

LowSky
February 22nd, 2010, 04:18 PM
Thanks xinix, I'll look into it, I seem to be having the same issue, so I'm hoping this will fix it

LowSky
February 24th, 2010, 07:03 PM
I've run into a few snags with Hulu Desktop running when the frontend is up.
It seems to be a pulseaudio/HDMI sound issue, something I'm a bit sketchy about

also Xinix that link you gave me is breaking my backend too. I think it fixes the driver issue, but then causes a nice MySQL problem, which then breaks the server connection from backend to fronted. Not good...Sure my Machine stays on most of the time, so having to restart the backend after a reboot might not be that annoying. The fix is to create scripts to delay the startup of other apps, but This is becoming too much work for me, I'm going cross eyed.

Also having an issue with deleting saved recordings, i think its just me being tired, but probably not...

This project is being a huge bummer...


also why is the program guide super slow, it was faster for me to look up program names, forget trying to see what on later tonight and just recording on impulse. This is a major issue...

Is it me or is MythTv not so polished after all these years? Boxee is a lot younger and it looks lightyears ahead. Heck Windows 7 Media center runs flawlessly compared to MytTv, I would run tha if the DRM wasn't killing my streaming ability

xinix
February 24th, 2010, 07:12 PM
Too bad the thread was a dud. I was going to try it out tonight while I did a little maintenance to the computer (new vid card). I may still give it a try to see if the concept can still be applied, that is tell the startup script to wait for the driver to finish loading.

Xailia
February 24th, 2010, 09:08 PM
Is it me or is MythTv not so polished after all these years? Boxee is a lot younger and it looks lightyears ahead. Heck Windows 7 Media center runs flawlessly compared to MytTv, I would run that if the DRM wasn't killing my streaming ability

I agree on some fronts that MythTV isn't polished (one example: having to manually setup the trans-coding settings after install...the defaults intentionally are not set or having to reset all the IPs addresses manually so they don't point to localhost, etc.). The problem is not always MythTV though.

The drivers for the 2250 are a perfect example. The number of (not so obvious) steps you have to go through to get this working is kind of crazy. Even now, I am still getting an error with my second card that fills up my kern.log each day and I have to do a cold boot to fix the issue.

The reality is that the hardware companies put all their efforts into Windows and leave us Linux folk on our own. We are fortunate to have people like Steven, who developed the 2250 drivers that we are using.

It is frustrating though - MythTV has just enough benefits over Media Center that I would prefer to get MythTV working. The issue is that configuring MythTV to work properly takes a long time and is somewhat different for each system. In Windows Land, you just click "Install" and everything is done for you...

Sorry, I will get off my soap-box. I enjoy the Ubuntu/Myth community and intend to keep helping where I can, but I just wish things would just work out of the box sometimes...you know?

jjwest85
February 25th, 2010, 01:25 PM
So I've been doing some on-line research and I came across this old thread that talks about hooking an IR receiver to a normal microphone input. I went to radioshack and found a converter that I think works for the Hauppauge IR receiver. It is a female 2.5mm stereo to male 3.5mm stereo and only cost $3!! I haven't gotten too far in this thread:

http://ubuntuforums.org/showthread.php?t=477958

but I have some hope for it. I tried having my IR receiver plugged into my 'line-in' port and got the microphone input level scale in sound preferences to go up when I would push buttons on the remote. Let me know if anyone has heard about this before?

LowSky
February 25th, 2010, 06:41 PM
jjwest85 thats a great idea. Also just buying a USB IR reciever would work too.

iQuizzle
February 28th, 2010, 08:34 PM
Hi guys, don't know if anyone is subscribed to this tread but I really need some help.... maybe I am getting old but I have been working with linux for a few years now and built many Mythtv in various distros but this is driving me crazy....I normally try to figure things out but I am at the end of my rope on this one.

HVR-2250, mythbuntu 9.10, athon x64 5000+ ...the install went smoothly with the 64 bit version of mythbuntu:


dmesg | grep saa
or

dmesg | grep dvb
or

dmesg | grep hvr

yield nothing . so that's one thing, but should that stop the install of the driver.

I have followed a few of the install howto's including the one that I think is in this thread.

I had to install unzip as the first hurdle, and I also got an error after running


make menuconfig

I got an error :


*** Unable to find the ncurses libraries or the
*** required header files.
*** 'make menuconfig' requires the ncurses libraries.
***
*** Install ncurses (ncurses-devel) and try again.
***
make[3]: *** [scripts/kconfig/dochecklxdialog] Error 1
make[2]: *** [v4l-mconf] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.31-14-generic'
make[1]: *** [/lib/modules/2.6.31-14-generic/build/scripts/kconfig/mconf] Error 2
make[1]: Leaving directory `/home/lpnb/Downloads/saa7164-stable/v4l'
make: *** [menuconfig] Error 2


Now, I suspect this is related the the error I get when I run 'make'.

I have tried install ncurses devel but this does not fix the problem.

one of the howto's misses the
make menuconfig step which I don't understand.

I tried both the stable and the Devel releases no dice either way.

O.K. so there is two issues one is that I can't see it at all with dmesg and the other is the driver install errors. I had this driver installed on exactly the same system (sans new sata DVD drive) and it worked....I rebuilt because it was very unstable due to the massive amount customisation and it was broken. So I thought I would upgrade in the hope it would be more stable and see more of my hardware.

FYI,
the system also has a biostar TF560+ mobo, 750GB Green and quiet drive, nvidia Gigabyte 9600GT Silent graphics, 3 Noctua fans tuned to an acceptable speed for noise, MX-810 "universal remote control" (very nice but pricey) 100% custom made black anodised case. When I say custom I mean custom....even the HDD and CD brackets are hand made.... I started this damn thing 4 years ago and it has never been 100% with remote and tuner card working correctly. I have the remote working now....just need this nice tuner working.

thanks for listening!
Lachlan

That's weird. I haven't tried to install the driver, but did you try installing libncurses5-dev? It doesn't install with the ncurses-base from the repository... maybe that's what it needs. :confused:

xinix
February 28th, 2010, 09:54 PM
oddly I have found that I have to do "sudo make menuconfig" for it to work.

LowSky
March 1st, 2010, 11:15 PM
OK so I've been sort of running for about a week. This week I will try to record as much as possible and hope it all works as planned. the stuff I ran last week looked better and had much better sound (volume) than my Windows 7 Media Center experiences.

Side Note: I had a huge power outage starting Thursday night going into Saturday, in fact many homes are still without power in my area, thanks to a massive snow storm that cripples nearly 140,000 homes.

I have been documenting some of the issues I think many people would like to learn about if they are new to MythTV. I wasn't able to look into fixes for the issues I'm having so I cant fix them yet. Hopefully soon.

1. If you are using a router give you media center a reserved address. Not doing do might cause the frontend to fail and many people will mistake it for a MySQL or Backend problem.

2. Still some issue with MythTV at boot. the issue is Myth starting before the TV tuner card drivers load completely cause them to seem offline., my only fix is to restart MythTV Backend once a boot is complete. Otherwise look into stretching the time between the driver is loaded and the time Myth and MySQL start.

3. Trying to run another application on top of the frontend (like Hulu Desktop) and using HDMI for sound equals no sound... special thanks to PulseAudio. Exit from the frontend and sound will work on other applications, not preferred but it's helpful. Many people will be moving to HDMI as VGA is slowly dying away on HDTV's. This is important for fixing.

440corbon
March 5th, 2010, 01:22 AM
I'm pretty sure the kernel update broke my driver for the card. If anyone else has an issue give a shout out.

pjgroudas
March 6th, 2010, 02:19 PM
I'm pretty sure the kernel update broke my driver for the card. If anyone else has an issue give a shout out.

I have the same problem. I remember jumping through all these hoops a couple months ago and then I did a system update and mythtv stopped working. I totally forgot that i needed to recompile the saa7164 driver whenever the kernel updates. How does everyone else deal with this problem? Just remember? Is there a simple way to automate the process?

I'm going to use this as an oppurtunity to upgrade my hard drive and go through this process on a fresh 9.10 image. Hopefully with this thread as reference it won't be so bad! :D

440corbon
March 6th, 2010, 03:36 PM
Right now I am just playing with things. I am still putting my server together. But by June I would like to have everything up and running. Complete with a fresh install of Mythbuntu 10.4 On the next setup there will be no desktop. and an outdoor antenna set up.

jimko
March 6th, 2010, 09:56 PM
I had problems after the 2.6.31.20 update too. The saa7164 drivers aren't expected to be in the kernel until 2.6.32 at best, so you (we) have to compile whenever there is an update. My problem was the "make" step seemed to want to use the 2.6.31.19 headers and the "make install" step tried to install to the /lib/modules/2.6.31.19 directory. I was in a hurry, so I just made symlinks to the right headers and lib/modules folders and it seems to have fooled it. Check the output of your make/make install steps, look at the versions carefully and compare to the output from "uname -a" to see if your getting a mismatch.

cgfirecoral
March 7th, 2010, 02:49 AM
...
i just installed this card yesterday and seems to be working correctly in Mythbuntu Karmic on AMD64. However, it went crazy overnight and filled my disk with log messages like the following:


Feb 14 07:47:09 myth1 kernel: [55883.613679] saa7164_api_i2c_read() error, ret(1) = 0xc
Feb 14 07:47:09 myth1 kernel: [55883.613683] s5h1411_readreg: readreg error (ret == -5)
Feb 14 07:47:09 myth1 kernel: [55883.663584] saa7164_cmd_send() No free sequences
It repeated this enough to write out about 2G of log messages before it ran out of resources...


I've been suffering from the same problem pretty much since I built my system in January. Have you found a solution to this? I did send a note to Steve Toth, but didn't hear anything back. (It's kind of hard to find a place to report or discuss these issues).
Thanks much!

pjgroudas
March 7th, 2010, 04:09 AM
I've been suffering from the same problem pretty much since I built my system in January. Have you found a solution to this? I did send a note to Steve Toth, but didn't hear anything back. (It's kind of hard to find a place to report or discuss these issues).
Thanks much!

What logs are you looking at? I'd like to check mine in the morning and see if I'm suffering the same thing.

cgfirecoral
March 7th, 2010, 04:29 AM
What logs are you looking at? I'd like to check mine in the morning and see if I'm suffering the same thing.

/var/log/kern.log


Mar 6 18:42:18 mythback1 kernel: [862821.943006] saa7164_cmd_send() No free sequences
Mar 6 18:42:18 mythback1 kernel: [862821.943016] saa7164_api_i2c_read() error, ret(1) = 0xc
Mar 6 18:42:18 mythback1 kernel: [862821.943021] s5h1411_readreg: readreg error (ret == -5)
Mar 6 18:42:18 mythback1 kernel: [862821.943027] saa7164_cmd_send() No free sequences
Mar 6 18:42:18 mythback1 kernel: [862821.943031] saa7164_api_i2c_read() error, ret(1) = 0xc
Mar 6 18:42:18 mythback1 kernel: [862821.943035] s5h1411_readreg: readreg error (ret == -5)
Mar 6 18:42:18 mythback1 kernel: [862821.943044] saa7164_cmd_send() No free sequences
Mar 6 18:42:18 mythback1 kernel: [862821.943048] saa7164_api_i2c_read() error, ret(1) = 0xc
Mar 6 18:42:18 mythback1 kernel: [862821.943052] s5h1411_readreg: readreg error (ret == -5)reboot fixes it briefly, but within 48 hours, it hits again.

silverdulcet
March 8th, 2010, 04:14 AM
I had problems after the 2.6.31.20 update too. The saa7164 drivers aren't expected to be in the kernel until 2.6.32 at best, so you (we) have to compile whenever there is an update. My problem was the "make" step seemed to want to use the 2.6.31.19 headers and the "make install" step tried to install to the /lib/modules/2.6.31.19 directory. I was in a hurry, so I just made symlinks to the right headers and lib/modules folders and it seems to have fooled it. Check the output of your make/make install steps, look at the versions carefully and compare to the output from "uname -a" to see if your getting a mismatch.

Following a kernel update you need to run the command to clear the previous build files from the source directory

make distclean

Run that command from within the src directory prior to running your

make
make install
commands

Xailia
March 8th, 2010, 04:08 PM
Update (3/10/10): Since my original post on 3/8/10 I decided to try out a theory: what would happen if I never watched liveTV, only recordings. It has been two days and I have not had the error occur yet. I have recorded shows on all 4 tuners and have played back the recordings on two different frontends. Also, I also changed from getting listing data OTA to using schedules direct. I will keep this post updated as I further track down the issue.


/var/log/kern.log

reboot fixes it briefly, but within 48 hours, it hits again.

I am so happy I am not alone with this! I have been trying to track this down for a few weeks.

I have a similar issue, but mildly different. I have two separate HVR-2250s in my system. One of them always works, and the second one errors out the same way both of yours does.

Here is the output (when both are working from my dmesg):


[ 7.363018] saa7164 driver loaded
[ 7.363102] saa7164 0000:05:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 7.363441] CORE saa7164[0]: subsystem: 0070:8851, board: Hauppauge WinTV-HVR2250 [card=7,autodetected]
[ 7.363452] saa7164[0]/0: found at 0000:05:00.0, rev: 129, irq: 16, latency: 0, mmio: 0xfa000000
[ 7.363462] saa7164 0000:05:00.0: setting latency timer to 64
[ 7.363469] IRQ 16/saa7164[0]: IRQF_DISABLED is not guaranteed on shared IRQs
[ 7.529015] saa7164_downloadfirmware() no first image
[ 7.529027] saa7164_downloadfirmware() Waiting for firmware upload (v4l-saa7164-1.0.3.fw)
[ 7.529033] saa7164 0000:05:00.0: firmware: requesting v4l-saa7164-1.0.3.fw
[ 7.887837] saa7164_downloadfirmware() firmware read 3978608 bytes.
[ 7.887842] saa7164_downloadfirmware() firmware loaded.
[ 7.887863] saa7164_downloadfirmware() SecBootLoader.FileSize = 3978608
[ 7.887872] saa7164_downloadfirmware() FirmwareSize = 0x1fd6
[ 7.887876] saa7164_downloadfirmware() BSLSize = 0x0
[ 7.887879] saa7164_downloadfirmware() Reserved = 0x0
[ 7.887883] saa7164_downloadfirmware() Version = 0x51cc1
[ 14.748122] saa7164_downloadimage() Image downloaded, booting...
[ 14.852023] saa7164_downloadimage() Image booted successfully.
[ 17.005022] saa7164_downloadimage() Image downloaded, booting...
[ 18.672753] saa7164_downloadimage() Image booted successfully.
[ 18.727525] saa7164[0]: Hauppauge eeprom: model=88061
[ 19.537167] DVB: registering new adapter (saa7164)
[ 22.525980] DVB: registering new adapter (saa7164)
[ 22.526386] saa7164 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 22.526734] CORE saa7164[1]: subsystem: 0070:8851, board: Hauppauge WinTV-HVR2250 [card=7,autodetected]
[ 22.526745] saa7164[1]/0: found at 0000:03:00.0, rev: 129, irq: 18, latency: 0, mmio: 0xfa800000
[ 22.526755] saa7164 0000:03:00.0: setting latency timer to 64
[ 22.526762] IRQ 18/saa7164[1]: IRQF_DISABLED is not guaranteed on shared IRQs
[ 22.692023] saa7164_downloadfirmware() no first image
[ 22.692069] saa7164_downloadfirmware() Waiting for firmware upload (v4l-saa7164-1.0.3.fw)
[ 22.692075] saa7164 0000:03:00.0: firmware: requesting v4l-saa7164-1.0.3.fw
[ 22.704063] saa7164_downloadfirmware() firmware read 3978608 bytes.
[ 22.704068] saa7164_downloadfirmware() firmware loaded.
[ 22.704090] saa7164_downloadfirmware() SecBootLoader.FileSize = 3978608
[ 22.704099] saa7164_downloadfirmware() FirmwareSize = 0x1fd6
[ 22.704103] saa7164_downloadfirmware() BSLSize = 0x0
[ 22.704106] saa7164_downloadfirmware() Reserved = 0x0
[ 22.704109] saa7164_downloadfirmware() Version = 0x51cc1
[ 29.568024] saa7164_downloadimage() Image downloaded, booting...
[ 29.672036] saa7164_downloadimage() Image booted successfully.
[ 31.796022] saa7164_downloadimage() Image downloaded, booting...
[ 33.460072] saa7164_downloadimage() Image booted successfully.
[ 33.496508] saa7164[1]: Hauppauge eeprom: model=88061
[ 34.080780] DVB: registering new adapter (saa7164)
[ 36.970107] DVB: registering new adapter (saa7164)

I think it is a little strange both of them are "[card =7,autodetect]" - should these be different cards? Could this be related?

Here is my kern.log right as the error began (March 2nd was the last time the log was written too before this) :



Mar 5 01:22:57 media-desktop kernel: [183711.464017] Event timed out
Mar 5 01:22:57 media-desktop kernel: [183711.464026] saa7164_api_i2c_read() error, ret(1) = 0x32
Mar 5 01:22:57 media-desktop kernel: [183711.464031] s5h1411_readreg: readreg error (ret == -5)
Mar 5 01:22:58 media-desktop kernel: [183712.488017] Event timed out
Mar 5 01:22:58 media-desktop kernel: [183712.488026] saa7164_api_i2c_read() error, ret(1) = 0x32
Mar 5 01:22:58 media-desktop kernel: [183712.488030] s5h1411_readreg: readreg error (ret == -5)
Mar 5 01:23:07 media-desktop kernel: [183721.464023] Event timed out
Mar 5 01:23:07 media-desktop kernel: [183721.464031] saa7164_api_i2c_read() error, ret(1) = 0x32
Mar 5 01:23:07 media-desktop kernel: [183721.464036] s5h1411_readreg: readreg error (ret == -5)
Mar 5 01:23:08 media-desktop kernel: [183722.488024] Event timed out
Mar 5 01:23:08 media-desktop kernel: [183722.488039] saa7164_api_i2c_read() error, ret(1) = 0x32
Mar 5 01:23:08 media-desktop kernel: [183722.488044] s5h1411_readreg: readreg error (ret == -5)

Finally, here is my mythbackend log outputted at the same time:

2010-03-05 01:21:21.100 [mpeg2video @ 0x6a426c0]ac-tex damaged at 26 60
2010-03-05 01:21:21.118 [mpeg2video @ 0x6a426c0]skipped MB in I frame at 10 64
2010-03-05 01:21:21.136 [mpeg2video @ 0x6a426c0]ac-tex damaged at 81 66
2010-03-05 01:21:21.154 [mpeg2video @ 0x6a426c0]ac-tex damaged at 66 67
2010-03-05 01:22:37.346 DVBSM(/dev/dvb/adapter1/frontend0), Warning: Can not measure S/N
eno: Invalid argument (22)
2010-03-05 01:23:00.120 DVBSM(/dev/dvb/adapter3/frontend0), Warning: Can not measure S/N
eno: Invalid argument (22)
2010-03-05 01:23:12.836 DevRdB(/dev/dvb/adapter0/frontend0) Error: Poll giving up
2010-03-05 01:23:12.859 DVBSH(/dev/dvb/adapter0/frontend0) Error: Device error detected
2010-03-05 01:23:41.507 Reschedule requested for id -1.
2010-03-05 01:23:41.626 Scheduled 1 items in 0.1 = 0.05 match + 0.07 place
2010-03-05 01:23:42.935 DVBRec(1:/dev/dvb/adapter0/frontend0) Error: Stream handler died unexpectedly.
2010-03-05 01:23:43.142 TVRec(1): Changing from Watching RecordingOnly to None
2010-03-05 01:23:43.227 Reschedule requested for id 0.
2010-03-05 01:23:43.336 Recording designated 1080i/p because width was 1920
2010-03-05 01:23:43.382 Scheduled 1 items in 0.1 = 0.04 match + 0.10 place

I wasn't actually watching TV at this point - the system was autoflagging commercials.

I too emailed Steven Toth, he replied initially acknowledging that other had reported the issue; I haven't heard back from him since.

Before installing MythTV I tried using Kaffiene's TV viewer for a few days on all 4 of my inputs and never had these errors occur. I am not sure if this issue is within the MythTV code, the drivers, or some combination.

Any thoughts on what to check/testing ideas would be fantastic. If we can't figure this out, I am going to see if the MythTV-users list has any ideas...

Thanks!

jjwest85
March 27th, 2010, 03:42 PM
Does anyone know if the saa7164 driver is going to be included in the ubuntu 10.04 kernal? I believe ubuntu 10.04 is coming with 2.6.32. Has anyone heard for sure one way or another?

440corbon
March 27th, 2010, 04:05 PM
Silver I added the make distclean command to the compilation on page 15 thank for the input.

xinix
March 31st, 2010, 03:15 AM
Ok I've been putting up with something long enough and it's time to fix it. My HVR-2250 keeps trying to change to analog channels when I'm watching tv. I have a PVR-150 in the machine too and when I browse to a non digital channel the HVR-2250 tries to switch to it instead. In schedulesdirect I have two lineups, one for the PVR-150 with all the analog channels I want selected and a second with only the clear qam digital channels selected. Is there a better way to set this up.

If I navigate the OSD menu and switch to the analog tuner then there are no problems

dallas8101
April 2nd, 2010, 03:20 PM
I am having an issue with about half of my recordings on the HVR2250. I use the removecommercials script to cut the commercials. During the run it often errors out with an error 232. I can play the files, but they do appear to be corrupted in some fashion. I have had the HVR2250 drivers installed since about the time Steven released the original stable last year. Has anyone run into this and found a solution?

I have also tried the "ffmpeg -acodec copy -vcodec copy" to remux the file that is often suggested for this, but that does not complete either.

removecommercials: mythtranscode: Transcoding cruft out of original file (2111_20100201190000.mpg)
+ mythtranscode -c 2111 -s 2010-02-01-19-00-00 --mpeg2 --honorcutlist -o /var/lib/mythtv/recordings/2111_20100201190000.mpg.mpeg
2010-04-02 09:08:56.038 Using runtime prefix = /usr
2010-04-02 09:08:56.086 Empty LocalHostName.
2010-04-02 09:08:56.176 New DB connection, total: 1
2010-04-02 09:08:56.197 Closing DB connection named 'DBManager0'
2010-04-02 09:08:56.198 Enabled verbose msgs: important
2010-04-02 09:08:56.200 New DB connection, total: 2
2010-04-02 09:08:57.093 Deadlock detected. One buffer is full when
the other is empty! Aborting

+ ERROR=232
+ '[' 232 -ne 0 ']'
+ echo 'removecommercials: mythtranscode: Transcoding failed for 2111_20100201190000.mpg with error 232'

440corbon
April 3rd, 2010, 01:29 PM
I am having an issue with card being busy after ripping dvds using handbrake. Is this an issue with the card drivers or using gnome desktop with myth? it is easily resolved by restarting backend but I was wondering the root cause.

Wild Man
April 3rd, 2010, 11:54 PM
Hi, I wanted to ask if anyone can tell me how to purge the driver and firmware for this card, I have not been able to get it to work I have tried several times but the card does not show up, so I think I need a fresh start but I do not know how to get rid of the old driver and firmware. If anyone can help it will be greatly appreciated, I love the 2250 card but I want to use it with ubuntu not windows.

LowSky
April 5th, 2010, 04:57 PM
I am having an issue with card being busy after ripping dvds using handbrake. Is this an issue with the card drivers or using gnome desktop with myth? it is easily resolved by restarting backend but I was wondering the root cause.

this is an odd issue, and would put the blame on the cards drivers, but I think it has more to do with handbrake. More than likely handbrake and Myth are both using the same application for use and one is corrupting the other. basically a Multitasking error.

what if you use another application for ripping like Acidrip, do you get the same errors?

LowSky
April 5th, 2010, 05:06 PM
Hi, I wanted to ask if anyone can tell me how to purge the driver and firmware for this card, I have not been able to get it to work I have tried several times but the card does not show up, so I think I need a fresh start but I do not know how to get rid of the old driver and firmware. If anyone can help it will be greatly appreciated, I love the 2250 card but I want to use it with ubuntu not windows.

Hi Wildmanne,

what instruction set are you using to install the firmware and drivers? hopefully it mine (shameless plug). What application are you using to play incoming feeds and how is the tuner hooked up. Have you done a channel scan? One big error many people fail to notice is that the 2250 only works as a digital tuner for Linux, which means it will not work with analog feeds. This sometimes causes confusion especially when people try to use this card with a cable box.

One of my issues currently is needing to manual reboot MythTV when the computer is turned on because of how the drivers get loaded at boot time. This issue could be yours and is simple to fix by restarting the MythTv backend.

Sorry for all the questions but its important to get an idea of what is wrong

milesnorth
April 5th, 2010, 11:14 PM
I followed the 440corbon summary of the lowsky procedure for the Hauppauge HVR-2250 drivers on page 15 of this thread and got following errors:

kurt@mythbuntu:~/Downloads/saa7164-stable$ make CONFIG_DVB_FIREDTV:=n

make -C /home/kurt/Downloads/saa7164-stable/v4l
make[1]: Entering directory `/home/kurt/Downloads/saa7164-stable/v4l'
No version yet, using 2.6.31-20-generic
make[1]: Leaving directory `/home/kurt/Downloads/saa7164-stable/v4l'
make[1]: Entering directory `/home/kurt/Downloads/saa7164-stable/v4l'
scripts/make_makefile.pl
make[1]: execvp: scripts/make_makefile.pl: Permission denied
Updating/Creating .config
/bin/sh: ./scripts/make_kconfig.pl: Permission denied
make[1]: *** No rule to make target `.myconfig', needed by `config-compat.h'. Stop.
make[1]: Leaving directory `/home/kurt/Downloads/saa7164-stable/v4l'
make: *** [all] Error 2

I'm a linux neophyte running mythbuntu 9.10 with a Kubuntu KDE 4.3.2 frontend. Had everything working originally using the lowsky procedure. I likely broke something trying to mount ~home on a different hard drive partition. Then I could only run the tv card in Mythtv after first running the mythtv backend and mythfill modules after every reboot.

Now that I updated the kernel two days ago, I can't reinstall the 2250 drivers. I wondered if these two problems might be related to my somehow incorrectly mounting ~home on a new partition with some incorrect permissions ???

I first tried a distclean & make to update the kernel and got the same errors. Then I tried to remove the v4l-saa files and started over from the beginning to load the drivers, which is where I am now.

Please let me know what additional information might be required and thanks for any help.

JohnAStebbins
April 6th, 2010, 12:02 AM
this is an odd issue, and would put the blame on the cards drivers, but I think it has more to do with handbrake. More than likely handbrake and Myth are both using the same application for use and one is corrupting the other. basically a Multitasking error.

what if you use another application for ripping like Acidrip, do you get the same errors?

Umm, ...no. HandBrake doesn't use any external programs to do it's job. It is completely self contained, even to the point that most of the libraries it uses are statically linked.

But handbrake is a multithreaded application that puts a heavy load on the computer. If there are any hardware stability issues with the machine, handbrake will certainly expose them.

jlp_engineer
April 6th, 2010, 02:12 AM
I have been monitoring progress on the HVR-2250 with respect to Mythbuntu and have to admire everyone with the stamina to keep up the effort on this card. On the surface, this card seems the perfect addition to anyone's home theater setup.

I got my feet wet with Mythbuntu using an old P4 system and three PVR-150's. I wanted to move to a tuner card that would tune digital channels and work under Mythbuntu. I found an ATi HDTV Wonder card, and while I was never able to get it to work 100%, I learned a lot about Mythbuntu in the process.

I don't really care much about the IR support for the card, but I am interested in support for the analog tuners. It's because our local cable company does not offer that many unencrypted digital channels, so most of what I watch is still on analog cable. I don't believe in purchasing anything that I cannot fully use...maybe because of some deep seated OCD issues. Is there even a whisper or rumor when the analog side of this card will be supported?

TIA

DurkenV
April 6th, 2010, 08:34 AM
OK here is the awesome news, I got it working, but it took forever as I had to go through miles of web pages just to get this to work! I'll list my sources at the bottom if I missed something and you need to look through it for answers.

So I'm going to be nice and do some people some favours and post what I did to get it working in MythTV.

This driver is a BETA and only works on digital side of the tuner,

NO ANALOGUE and please be careful using.

I am not responsible for the outcome of you using my tutorial.

As I think my tutorial is rather crude and may miss an important step, please see the sources listed below. This is not for people new to Linux, as it might break (and it might, I've only had this running for about 30 minutes, so fingers crossed).

If you really need to use this card for analogue and need a free OS, try the Windows 7 MCE, the free RC is currently available and should work until May 2010 before MS make you purchase a real copy and works completely with this tuner card.

Instructions for using HVR-2250 in MythTV (also works on HVR-2200 or any video capture card using the SAA7164 chipset)

you need to be running Ubuntu 8.10 or higher for these drivers

Enter this into your Terminal it is the code for the firmware and to install it


wget http://www.steventoth.net/linux/hvr22xx/22xxdrv_27086.zip
wget http://www.steventoth.net/linux/hvr22xx/HVR-12x0-14x0-17x0_1_25_25271_WHQL.zip
wget http://www.steventoth.net/linux/hvr22xx/extract.sh


sh extract.sh
sudo cp *fw /lib/firmware

you need to install mercurial and build essential for the next steps

sudo apt-get install mercurial build-essential

then we need the driver using this command to fetch

hg clone http://kernellabs.com/hg/saa7164-stable/

now change to the directory

cd saa7164-stable

then run make

make

that will take some time, go grab a drink and wait it out, when it completes run this command

sudo make install

wait for that to complete and reboot
from the command line

sudo reboot

Note that an application like TVtime will not work, TVtime only works on Analog signals, and so far this driver only gets the digital stuff working.

then install MythTV using whatever method you like, I personally went into synaptic and installed the frontend and backend and extra plug-ins

once installed and you set up your passwords go to
System> administration> MythTV backend setup

once there go to Capture Cards, Should be choice #2
choose new capture card, you will ave to do this step twice (this card has two tuners)
At card Type, pick DTB DTV
the first will be device number 0,
repeats choosing capture card to add the second tuner
the second device will be #1 (Linux starts counting at 0, good thing to know, especially for hard drives)

then go to video sources, pick your options, will vary so mine will not work with yours most likely, so I dont want to post something I dont know)

then go to Input Connections, again you will have 0 and 1, configure both

then edit channels and directories as needed.

close let it fill database, for some reason mine keeps running in a loop, just exit after you see it finish the first or second time

now go to Applications > Sound & Video > MythTV Frontend

And you should be able to watch TV

I must say the Linux HTPC community is way too technical for most people, they need to make these things simpler, Windows 7 MCE is 10 times better at setting up these things.

Notes
I used Ubuntu 9.04, results should work for anyone using *buntu 8.10 releases, including Mythbuntu
I must say the configuring MythTV is exhausting so if I missed something or it doens't work please post better steps.
Special thanks to Steven over at KernelLabs (http://www.kernellabs.com/blog/?page_id=17), the person who made the drivers.


Sources

http://www.linuxtv.org/wiki/index.php/How_to_Obtain%2C_Build_and_Install_V4L-DVB_Device_Drivers
http://www.kernellabs.com/blog/?page_id=17
http://kernellabs.com/hg/saa7164-stable/
http://parker1.co.uk/mythtv_ubuntu.php
http://www.linuxtv.org/wiki/index.php/How_to_Obtain%2C_Build_and_Install_V4L-DVB_Device_Drivers#Using_Mercurial
http://www.steventoth.net/blog/products/hvr-2250/
http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-2200

I've done all the steps as above. All went great till I had to add the capture card. When I add the card I can not edit the DVB Device Number field. Please help.... Trying to get this to work on very slow Internet connection. Finally all done and now sitting with new problem.

At card Type, pick DTB DTV
the first will be device number 0,
repeats choosing capture card to add the second tuner
the second device will be #1 (Linux starts counting at 0, good thing to know, especially for hard drives)

This part is it. Please help

DurkenV
April 6th, 2010, 08:42 AM
OK here is the awesome news, I got it working, but it took forever as I had to go through miles of web pages just to get this to work! I'll list my sources at the bottom if I missed something and you need to look through it for answers.

So I'm going to be nice and do some people some favours and post what I did to get it working in MythTV.

This driver is a BETA and only works on digital side of the tuner,

NO ANALOGUE and please be careful using.

I am not responsible for the outcome of you using my tutorial.

As I think my tutorial is rather crude and may miss an important step, please see the sources listed below. This is not for people new to Linux, as it might break (and it might, I've only had this running for about 30 minutes, so fingers crossed).

If you really need to use this card for analogue and need a free OS, try the Windows 7 MCE, the free RC is currently available and should work until May 2010 before MS make you purchase a real copy and works completely with this tuner card.

Instructions for using HVR-2250 in MythTV (also works on HVR-2200 or any video capture card using the SAA7164 chipset)

you need to be running Ubuntu 8.10 or higher for these drivers

Enter this into your Terminal it is the code for the firmware and to install it


wget http://www.steventoth.net/linux/hvr22xx/22xxdrv_27086.zip
wget http://www.steventoth.net/linux/hvr22xx/HVR-12x0-14x0-17x0_1_25_25271_WHQL.zip
wget http://www.steventoth.net/linux/hvr22xx/extract.sh


sh extract.sh
sudo cp *fw /lib/firmware

you need to install mercurial and build essential for the next steps

sudo apt-get install mercurial build-essential

then we need the driver using this command to fetch

hg clone http://kernellabs.com/hg/saa7164-stable/

now change to the directory

cd saa7164-stable

then run make

make

that will take some time, go grab a drink and wait it out, when it completes run this command

sudo make install

wait for that to complete and reboot
from the command line

sudo reboot

Note that an application like TVtime will not work, TVtime only works on Analog signals, and so far this driver only gets the digital stuff working.

then install MythTV using whatever method you like, I personally went into synaptic and installed the frontend and backend and extra plug-ins

once installed and you set up your passwords go to
System> administration> MythTV backend setup

once there go to Capture Cards, Should be choice #2
choose new capture card, you will ave to do this step twice (this card has two tuners)
At card Type, pick DTB DTV
the first will be device number 0,
repeats choosing capture card to add the second tuner
the second device will be #1 (Linux starts counting at 0, good thing to know, especially for hard drives)

then go to video sources, pick your options, will vary so mine will not work with yours most likely, so I dont want to post something I dont know)

then go to Input Connections, again you will have 0 and 1, configure both

then edit channels and directories as needed.

close let it fill database, for some reason mine keeps running in a loop, just exit after you see it finish the first or second time

now go to Applications > Sound & Video > MythTV Frontend

And you should be able to watch TV

I must say the Linux HTPC community is way too technical for most people, they need to make these things simpler, Windows 7 MCE is 10 times better at setting up these things.

Notes
I used Ubuntu 9.04, results should work for anyone using *buntu 8.10 releases, including Mythbuntu
I must say the configuring MythTV is exhausting so if I missed something or it doens't work please post better steps.
Special thanks to Steven over at KernelLabs (http://www.kernellabs.com/blog/?page_id=17), the person who made the drivers.


Sources

http://www.linuxtv.org/wiki/index.php/How_to_Obtain%2C_Build_and_Install_V4L-DVB_Device_Drivers
http://www.kernellabs.com/blog/?page_id=17
http://kernellabs.com/hg/saa7164-stable/
http://parker1.co.uk/mythtv_ubuntu.php
http://www.linuxtv.org/wiki/index.php/How_to_Obtain%2C_Build_and_Install_V4L-DVB_Device_Drivers#Using_Mercurial
http://www.steventoth.net/blog/products/hvr-2250/
http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-2200

My Mythbuntu installation worked up untill
At card Type, pick DTB DTV
the first will be device number 0,
repeats choosing capture card to add the second tuner
the second device will be #1 (Linux starts counting at 0, good thing to know, especially for hard drives)

I can't edit the DVB Device Number field to "0" or "1" so can't add 2nd card or get the 1st one to work. Please Help.

kuehlc
April 23rd, 2010, 03:38 AM
/var/log/kern.log

reboot fixes it briefly, but within 48 hours, it hits again.

I'm having this same I2C error problem on a mythbuntu system I built a few months ago. Is anyone aware of a fix for this? Unless this gets resolved soon I'm going to bite the bullet and try a windows DVR for awhile.

dividehex
April 23rd, 2010, 07:57 PM
The DVB wiki page (http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-2250) for the Hauppauge2250, updated in Dec '09, says support is expected in the 2.6.32 kernel.

i just installed this card yesterday and seems to be working correctly in Mythbuntu Karmic on AMD64. However, it went crazy overnight and filled my disk with log messages like the following:


Feb 14 07:47:09 myth1 kernel: [55883.613679] saa7164_api_i2c_read() error, ret(1) = 0xc
Feb 14 07:47:09 myth1 kernel: [55883.613683] s5h1411_readreg: readreg error (ret == -5)
Feb 14 07:47:09 myth1 kernel: [55883.663584] saa7164_cmd_send() No free sequences
It repeated this enough to write out about 2G of log messages before it ran out of resources. It's cyclic, so I don't know if I've displayed the sequence in the correct order. I built the drivers from the stable branch of the drivers and it seemed to finish clean.

After I cleared the space and rebooted, mythfrontend status reported both tuners as "asleep." Starting and stopping mythbackend woke them back up and they seem to be functioning normally again.

Right now, my plan is to hope it doesn't happen again.

I've experienced the I2C error also for the past 8 months and I don't believe there is a fix to it yet. Just have to reboot the system for a temporary fix (2 - 36 hours). I have been compiling the latest saa7164-dev tree every time i see an update to it but nothing changed so far to have fixed the problem. One thing I have noticed is it only seems to be triggered when both tuners are recording. Sometimes it only takes a couple hours of uptime to be triggered and sometimes it will run for a few days before it happens.

Ive been holding off on buying another HVR-2250 for my box and/or build mythtv systems for my family members until this bug has been found and squashed.

As for the tuners being asleep after a reboot, this seems to be an upstart timing issue. I believe the mythtv-backend is coming up before the drivers are ready. Yes restarting the mythtv-backend manually after a reboot is annoying but it is now where close to the I2C hassle.

If anyone else has found a solution to the I2C bug or have heard anything from Steve about it, I would like to hear about it.

LowSky
April 23rd, 2010, 09:44 PM
Hmm -- I am not receiving this I2C error, which Version of the card do you own? My uptime has been a few weeks.
I need to check the to see what Kernel I'm using when I get home. Maybe rolling back is the answer.
I too suffer the issue of the cards being asleep after a fresh boot. I'm still trying to figure that out.

Anyone using 10.04 yet. Can anyone confirm the same issue or lack thereof.

dividehex
April 23rd, 2010, 10:49 PM
Hmm -- I am not receiving this I2C error, which Version of the card do you own? My uptime has been a few weeks.
You would know if you were receiving I2C error since your HD would fill up with a constant stream of errors to the kern.log and your recordings will be 0 byte files from that point on. I'm not sure which version of the card I have. Anyway to probe for it? Or tell from the card itself?



I need to check the to see what Kernel I'm using when I get home. Maybe rolling back is the answer.
I'm running Linux mythtv 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux



I too suffer the issue of the cards being asleep after a fresh boot. I'm still trying to figure that out.
Anyone using 10.04 yet. Can anyone confirm the same issue or lack thereof.
I am going to rebuild my system tonight with 10.04 in hopes that it will fix the 'asleep after reboot' issue. I'll post a reply when I'm done. :P

LowSky
April 23rd, 2010, 11:04 PM
You would know if you were receiving I2C error since your HD would fill up with a constant stream of errors to the kern.log and your recordings will be 0 byte files from that point on. I'm not sure which version of the card I have. Anyway to probe for it? Or tell from the card itself?
As far as I know there are 2 models.
One has the IR blaster soldered to the card, and well, doesn't work, the other, original card (and the one I have) uses a USB blaster/reciever



I'm running Linux mythtv 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux

I Believe Im still using 2.6.29 (I'm at work so I can't check it), I haven't updated my system since getting mythtv fully running. I decided to only d Ubuntu version upgrades.



I am going to rebuild my system tonight with 10.04 in hopes that it will fix the 'asleep after reboot' issue. I'll post a reply when I'm done. :P

thanks for the pioneer work. I know many of us will love to know the results.

dividehex
April 24th, 2010, 02:50 AM
It just gets worst from here on...

So I completely rebuilt my mythtv system with 10.04 and it seems nice. No big hangups except that I just figured out that my cable company (Comcast - SF Bay Area) switched over digital channels above 33 to encryption a few days ago. ](*,)

It also seems that the 'tuner asleep after reboot' issue hasn't gone away and it is too early to start seeing I2C errors but I'm sure they're just around the corner...

And here they are after about 7 mins into a dual recording. The system had only been up for about 40 mins and had successfully recorded dual shows on the previous 30min block.


[110261.945417] s5h1411_readreg: readreg error (ret == -5)
[110261.945424] saa7164_cmd_send() No free sequences
[110261.945427] saa7164_api_i2c_read() error, ret(1) = 0xc
[110261.945432] s5h1411_readreg: readreg error (ret == -5)
[110261.945438] saa7164_cmd_send() No free sequences
[110261.945442] saa7164_api_i2c_read() error, ret(1) = 0xc
[110261.945446] s5h1411_readreg: readreg error (ret == -5)
[110261.980267] saa7164_cmd_send() No free sequences
[110261.980272] saa7164_api_i2c_read() error, ret(1) = 0xc
[110261.980277] s5h1411_readreg: readreg error (ret == -5)
[110261.980285] saa7164_cmd_send() No free sequences
[110261.980289] saa7164_api_i2c_write() error, ret(1) = 0xc

greensoap
April 28th, 2010, 01:46 AM
I get these same errors. I am on Ubuntu 9.10.

I was able to track the error messages to saa7164_cmd_send() in saa7164-cmd.c. Search for "Event timed out" as it is the first error in kern.log before the errors start dumping continuously.

It looks like the driver is keeping track of some list of commands to send to the I2C bus and eventually the command buffer fills up and has no more run to store commands. I would also guess that the card is basically timing out and so old commands cannot get sent to clear the command buffer.

I was able to track -5 to be the EIO error from asm/errno-base.h which seems to get assigned in master_xfer() which is called in i2c_transfer().


#define EIO 5 /* I/O error */

I really don't know anything about Linux Kernel programming so I doubt I will be able to figure out how to recompile and update drivers to test out ways of avoiding the error. Maybe a longer timeout on the command would help?

The first set of errors appear every ten seconds once the initial timeout occurs.



Apr 26 01:08:17 backuppc kernel: [49014.404031] tda18271_init: [2-0060|S] error -5 on line 831
Apr 26 01:08:17 backuppc kernel: [49014.404035] tda18271_tune: [2-0060|S] error -5 on line 909
Apr 26 01:08:17 backuppc kernel: [49014.404039] tda18271_set_params: [2-0060|S] error -5 on line 990
Apr 26 01:08:17 backuppc kernel: [49014.404479] saa7164_irq_dequeue() found timed out command on the bus
Apr 26 01:08:27 backuppc kernel: [49023.888013] Event timed out
Apr 26 01:08:27 backuppc kernel: [49023.888022] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 26 01:08:27 backuppc kernel: [49023.888027] s5h1411_writereg: writereg error 0x19 0xf5 0x0000, ret == -5)
Apr 26 01:08:27 backuppc kernel: [49023.888434] saa7164_irq_dequeue() found timed out command on the bus

This next set appear almost continuously until I reboot my computer. I should mention that I don't have any recordings or live TV going on when these occur. Sometimes I get a few hours without error sometimes I get less than an hour.


Apr 26 01:25:34 backuppc kernel: [50050.888515] saa7164_api_i2c_read() error, ret(1) = 0xc
Apr 26 01:25:34 backuppc kernel: [50050.888518] s5h1411_readreg: readreg error (ret == -5)
Apr 26 01:25:34 backuppc kernel: [50050.888521] saa7164_cmd_send() No free sequences
Apr 26 01:25:34 backuppc kernel: [50050.888523] saa7164_api_i2c_read() error, ret(1) = 0xc
Apr 26 01:25:34 backuppc kernel: [50050.888526] s5h1411_readreg: readreg error (ret == -5)
Apr 26 01:25:34 backuppc kernel: [50050.888530] saa7164_cmd_send() No free sequences
Apr 26 01:25:34 backuppc kernel: [50050.888533] saa7164_api_i2c_write() error, ret(1) = 0xc
Apr 26 01:25:34 backuppc kernel: [50050.888536] s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)
Apr 26 01:25:34 backuppc kernel: [50050.888539] saa7164_cmd_send() No free sequences
Apr 26 01:25:34 backuppc kernel: [50050.888542] saa7164_api_i2c_write() error, ret(1) = 0xc

LowSky
April 28th, 2010, 04:05 PM
I can think of two issues. One the card is bad or Two the driver installation went wrong.

If its neither I would send an email to Steven Toth over at Kernel Labs:
stoth@kernellabs.com
Let him know the issue, it might be something he can look into and fix.

dividehex
April 28th, 2010, 05:09 PM
I think in my case, it would be safe to say the card isn't bad since I had it running successfully for over 5 months in a windows box without any issue. Although, it could have been damaged when I installed it in my current linux system.
I also don't think the driver installation has been bad, I have been following SkyLows awesome install instructions. :)
There is one thing I have always wondered about which weren't in the driver installation instructions. I have always assumed that since the card has 2 tuners and each tuner can record 1 channel at a time, I have been changing the Mythtv default 'max recordings' under the 'recording options' to from 2 to 1 for each tuner on the card. Is this correct?

My next test is going to be running Myth with only one side of the card (single tuner), since my timeouts only seem to appear in the middle of a dual recordings.
I will report back in a few days.... <see my post on page 22>

greensoap
April 28th, 2010, 07:15 PM
As dividehex mentioned, the card works fine in Windows and works beautifully in mythtv when the errors are not present. They leads me away from the card being the issue. Though it is entirely possible. I was also think that it might be the firmware that is being used during the installation process.

I used LowSky's install instructions as well. What I noticed is that the drivers from which the firmware is extracted are different versions than the windows drivers that ship with the card. Now whether the frimware has changed is another story.

I did find one piece of advise about disabling the EIT (Over the air guide broadcast) for all the channels. I tried that and have not had any errors yet today. But nothing is recording right now. I will start a couple of recordings and see if anything happens.

dividehex, I look forward to your test results.

LowSky
April 28th, 2010, 07:33 PM
dividehex the name is LowSky LOL :P

Also I REALLY REALLY need to make time to update this tutorial with 10.04 around the corner. My biggest concern is the driver, as it has not been updated in 3 months over at Kernel Labs, and its supposed inclusion into the Linux Kernel. Hopefully these new issues are not something we will see more of.

I will also point out my HTPC hasn't done an Ubuntu update since loading the drivers a few months ago. Maybe an Ubuntu Update broke something? I hope not. It doesn't seem many others are having this issue. I'm thinking of buying a second card for a 'test box' but I'm broke due to spending my money on my education (earning my BS in International Business).
Anybody what to donate to my test computer? I will accept PayPal. LOL!

greensoap
April 28th, 2010, 08:49 PM
dividhex,

I created a script that will email me when my Myth Box dies so I can log on and reboot. Just thought I would share.

The script uses ssmptp but sendmail could be used as well.


#!/bin/bash
tail -n10 /var/log/kern.log | grep -q "saa7164_api_i2c_read() error"

if [ $? -eq 0 ] ## MythTV Error
then

touch -d '-1 hour' limit

if [ limit -nt last_notification ]; then

/usr/sbin/ssmtp **YOUR EMAIL HERE** < ***PATH TO YOUR ERROR MESSAGE FILE***
touch last_notification
fi

fi

dividehex
April 29th, 2010, 04:21 AM
dividehex the name is LowSky LOL :razz:Yeah, SkyLow, SkyWalker.... LowSky... whatever your name is. I'm really sorry, dyslexia is a bchit.

On another note, I would like to point out that this has been a problem on all the installs I have done with this card over the past year or so from 8.10, 9.10 and now 10.04. And I also never do an updates once installed.

greensoap, thanks for the script. I will put it to use asap.

greensoap
April 29th, 2010, 07:53 PM
Dividehex,

I unset useonairguide on all my channels (useonairguide=0) and since then I have not had a single crash. Being up for about 24 hours, which is a record for me.

Maybe you can try unsetting this option as well and see if it clears up the issue.

For the record, I am using Schedules Direct for my guide info.

LowSky
April 29th, 2010, 08:31 PM
I upgraded last night to lucid and myth broke. The frontend wouldn't work and I could figure it out at all. I tried nearly everything and nothing worked. So I gave up and decided to do clean install. So far the install failed and I hadto use the alt install cd. Hopefully I can have this working tonight. Looks like upgrading is going to be nightmare for us. I'll keep everyone posted.

dividehex
April 30th, 2010, 05:33 PM
Dividehex,

I unset useonairguide on all my channels (useonairguide=0) and since then I have not had a single crash. Being up for about 24 hours, which is a record for me.

Maybe you can try unsetting this option as well and see if it clears up the issue.

For the record, I am using Schedules Direct for my guide info.


Thanks for the info. I found these were already unchecked so I am not sure that is causing my problems, although I hope it is successful for you. Currently, I have disabled one of the tuners on my card and it seems be stable so far with a 2 day uptime. Obviously, this is not a final solution, but I hope it help determine what is the problem is.

I'm also using schedule direct for my guide info.

cgfirecoral
May 1st, 2010, 03:47 PM
As one of the original posters of the saa7164_api_i2c_read() error, ret(1) = 0xc issues, I've been following this post hoping for a solution. Email to Steve Toth went unanswered.

Eventually, I gave up trying to work with the 2250 and went out and bought a 1600 which I threw in the available PCI slot in my backend server. After seeing the post about the problems cropping up when the 2250 is recording two shows, I turned on one of the 2250 tuners last week (so now I'm running the 1600 and a single 2250 tuner). The backend has been solid over the last week, with a number of dual recordings taking place.

I bought my 2250 in January. I suspect this problem may afflict recent production models, but that's purely anecdotal and I don't feel like pulling the card out to read the detailed numbers, unless it can really help debugging.

tjbron
May 1st, 2010, 09:20 PM
dividhex,

I created a script that will email me when my Myth Box dies so I can log on and reboot. Just thought I would share.

The script uses ssmptp but sendmail could be used as well.


#!/bin/bash
tail -n10 /var/log/kern.log | grep -q "saa7164_api_i2c_read() error"

if [ $? -eq 0 ] ## MythTV Error
then

touch -d '-1 hour' limit

if [ limit -nt last_notification ]; then

/usr/sbin/ssmtp **YOUR EMAIL HERE** < ***PATH TO YOUR ERROR MESSAGE FILE***
touch last_notification
fi

fi



Ok, dumb question time. I would love to use this, (maybe to make the box beep) but I don't do Linux a lot and I'm still learning. Do you run this as a cron job, or what? If you set it up to run on startup, won't it only run once? How did you get it to run continuously?

Thanks!

greensoap
May 2nd, 2010, 03:12 AM
So I create a file called checkMyth and chmod 777 the file (to make it executable). The script I pasted above goes in the checkMyth file.

Then I used crontab -e to open up the cron file for editing. This is the file that cron uses to run scheduled jobs. (I am sort of glossing the details there, but just google cron, crontab, or scheduling jobs).

This is a quick job, so I set it to run every minute. Here is the text from my crontab file


# m h dom mon dow command
* * * * * /home/**USERNAME**/checkMyth

So, this runs every minute but will only send an email once an hour. If you look at the script it "touches" a file called limit and marks the time of that file as one hour prior to the current time. It then checks the timestamp of the last_notification file. If the last notification file is older (meaning a notification was sent more than an hour ago), then it notifies me again by email. This way I don't get an email every minute, but I do get one every hour. It might be a little overkill, but I have some simple scripts setup so that I can SSH via my iphone (yes, there is an app for that) and restart my box and mythTV. This way, I can usually restart everything before any recordings get missed.

I hope that explanation helps.

tjbron
May 2nd, 2010, 04:20 PM
Yup, that answers my question. I had figured out what the script was doing, just wasn't sure how you kept it running. cron is the key!
Thanks again.

An interesting thing yesterday. My 2250 crashed as we've been discussing, and the dd, syslogd and klogd were running in top, but my kern.log file doesn't show any entries since April 9 when I was getting the saa7164_api_i2c_read() error once before. The file was 2GB so I cleaned it out and started fresh. Dunno. :confused:

LowSky
May 2nd, 2010, 05:59 PM
Ok so Here's the Tutorial for using 10.04.

I don't recommended using it, but maybe you will have better luck. I'm having a few issues with mythconverge, HDMI sound, andchanging channels without a tuner crashing.

This is the update to the guide I posted a while ago. Most is very much the same but a few differences.

This driver only works for digital recording, sorry there is no analog support and please be careful using.

I am not responsible for the outcome of you using my tutorial. This tutorial is based on my equipment and needs. If a setting I use does not work for you, I encourage people to post problems and/or solutions. This is not for people new to Linux, as it might break (and it might, as Mythbuntu 10.04 uses MythTV 0.23 which isn't a stable release version yet). I have placed little notes about certain thing to be careful of. If you see a number with a plus symbol (example: +47) look a few lines down for the note on this section.

If you really need to use this card for analog, try Windows 7. The card is fully supported with that operating system.

These instructions are for using the Hauppauge WinTV-HVR-2250 in MythTV (also works on HVR-2200 or any video capture card using the SAA7164 chipset).

This Tutorial is for Mythbuntu 10.04 but may work for versions of *buntu 8.10 and higher. Versions 8.04 and lower will not work because of the required kernel support for the drivers. +1

+1 Mythbuntu 10.04 uses MythTV 0.23, which as of May 1, 2010 is not a stable release. If you experience problems using Mythbuntu 9.10 might be a better option for you.



Let's Get Started


1. Open a Terminal

You will need to install these applications to install the drivers and firmware

sudo apt-get install mercurial libncurses5-dev unzip

2. This next part is to download and install the firmware. Download them to your /home/user folder and not the desktop.

To change directories

cd /home/username

Now download the firmware


wget http://www.steventoth.net/linux/hvr22xx/22xxdrv_27086.zip
wget http://www.steventoth.net/linux/hvr22xx/HVR-12x0-14x0-17x0_1_25_25271_WHQL.zip
wget http://www.steventoth.net/linux/hvr22xx/firmwares/4038864/v4l-saa7164-1.0.3-3.fw
wget http://www.steventoth.net/linux/hvr22xx/extract.sh


The next commands will extract the files and the copy them to Mythbuntu's /lib/firmware folder

sh extract.sh
sudo cp *fw /lib/firmware


3a. This part is for people using a version of Ubuntu 8.10 - 9.10. 10.04 alredy has the driver install. 10.04 users should know that if the drivers become updated before a new Linux Kernel release they can use this method for installation. If you are using 10.04 you may skip to step 3b. You may wish to use this step to install a newer kernel driver than the one included in 10.04.

lspci
If see a line that says Phillips SAA-7164 or something close to that, you can skip to instruction 3b.

Next we need download the driver using these command to fetch and install, I'm using the stable branch from Kernel labs, but you can use Linuxtv.org version if you wish.

hg clone http://kernellabs.com/hg/saa7164-stable/

now change to the directory:

cd saa7164-stable

Then run the command make:

make CONFIG_DVB_FIREDTV:=n

That will take some time, go grab a drink and wait it out, when it completes run this command:

sudo make install

3b. Next Reboot the system to insure the driver and firmware are installed and running:

sudo reboot

4. To get the card running open the MythTV Backend Setup (Applications>System>MythTV Backend Setup)

Once it is running go to Capture Cards, choice #2.
Choose new capture card, you will have to do this step twice (this card has two tuners)
At card Type, pick DTB DTV.
The first will be device number 0,
Repeat choosing capture card to add the second tuner. The second device will be number 1 (Linux starts counting at 0, a good thing to know, especially for hard drives). Important but I'm not at the machine at the time of edit. There is a menu here once you choose the adapter, one is for satellites the other for tuner options I think. Choose the tuner options, or the one on the right of satellite optins, Make sure the number of tuners or recordings (sorry drawing a blank) numbered 1, and not 2 like it is by default. The system will think each tuner is two tuners (total of 4...its messy). This will cause recordings to fail if you don't.

5. Go to video sources, pick your options, I had to setup an account with SchedulesDirect.org, so that I could get local channel guide information in the USA. Your country may have other options.

6. Next go to Input Connections, again you will have 0 and 1, configure for both.

7. Edit channels and directories as needed. Sorry I can't really help with this. A word of suggestion is learn the directories that data is stored. If you setup your machine and didn't use the entire disk, make sure to change the directories for recorded data as they will fill the root partition if you are not careful. Remember that the directories you create need to have write access for the MythTV group. Since my /home directory was on a separate 500GB hard drive I wanted to use that. I created a Folder named within the /home/mythtv/ folder. I added over 80 or so hours of record time doing this. I found out 1.2TB is roughly 200+ hours of recording time for HD video.

8. Close MythTV Backend by hitting ESC, it will then ask to fill the database, let it. The Database will take a good amount of time, and may look like it is running in a loop. Don't worry its collecting data for 14 days worth of channel listings if you used ShedulesDirect.org. This may take up to a half hour. The more channels you have the longer.

9. Now go to Applications >Multimedia > MythTV Frontend.

The next part is from my setup, but for many it might be required (I would love feedback).

First go to Utilities / Setup, its the last option. Choose Setup, then Appearance.

The first page is to choose your theme (A little about me: my choice is MythCenter-wide).
Next page is important: If you have more than one monitor, pick the one you want to display the GUI on. The second is the Monitor Aspect Ratio, be sure to set it to your TV or monitor's correct display size, Mine is 16:9 your's may be 16:10 or 4:3. A good rule of thumb I follow is most HDTV's are 16:9, most PC monitors are 16:10, SDTV is 4:3. Failure to set this might result in a horrible picture. Also on this page is to hide the mouse cursor. If you want to use a mouse over a keyboard or remote, then uncheck the box.
The next few pages I don't touch, sorry your on your own if you want to edit those.

10. Now back to Utilities / Setup > Setup

Choose TV Settings. Again for most of this its all your preference. But one thing I found odd and I needed it fixed. On the Page 3/8 (labeled Playback Profiles), I had to set the Current Video Playback Profile to High Quality(+2). If I didn't I got a TV screen showing the image twice as if playing a FPS like GoldenEye in multiplayer. I'm know, I'm dating myself, but that game rocked back in the day. Anyway; go to the main menu and try to watch live TV. If you are using HDMI output on your TV and there is no sound, don't panic just yet, keep reading, I'm getting to that.

+2 If you are using Nvidia graphics card choosing, VDPUA might be a good option. I have an ATI video card so I have no idea if this works as it should. (again: feedback please)

11. This next part is for users who need sound through HDMI.
Right now I only have sound working with MythTV using this part of the Tutorial. Sound isn't working for the regular desktop through the HDMI feed, so if you are using this for a PC that will be used for web browsing or services like Hulu Desktop, you will need a set of speakers or headphones plugged into the normal stereo jack on your PC for that to work. If your HDTV has a VGA port using that with a speaker connection or have a dual monitor set up and/or desktop speakers will get around this issue as well. I have instructions for certain newer Nvidia card on 11b.

So that I'm clear: This is really for those who are only looking to use MythTV (and MythTV only) on their Mythbuntu setup and need HDMI sound.

11a. Exit MythTV, and Go to Applications>Multimedia>Sound Mixer

In the drop down box pick you HDMI output
Make sure the option for IEC958 or whatever is checked, then close the Mixer.

Next open a Terminal, we will now check for what channel your HDMI device is using for playback.

aplay -l
look for the data that has HDMI in the title, on mine it was

Card 1: HDMI [HDA ATI HDMI], device 3: ATI HDMI [ATI HDMI]
Now we need to add the next few lines to the asound.conf file, the file is normally empty, so be sure your editing the correct file.
[code]sudo nano /etc/asound.conf


ctl.!default {
type hw
card 1
}
NOTE: My card was card 1, yours might be different.

Then reboot the system (+3). Then restart MythTV frontend. Go into Utilities / Setup > General. Hit next until you get to the 4th screen the page's title is: Audio System.

Now we need to change the line named Audio output device to


ALSA:plughw:x,y
x is the sound card number from the asound -l command.
y is the device number from the asound -l command.
For example here is mine

ALSA:plughw:1,3

+3 Another issue currently is that the Tuner card will only work if you first start up the MythTV backend after a reboot or powering on so that the tuner card will work. If anyone can help me with this part. That would be great. I cant seem to find a way around this, but I leave my system on 24/7 so its a small problem. This issue is resolved if you upgrade MythTV to version .23.1. Use the Mythbuntu Autobuild package from their website to upgrade or the 23.1 PPA.


11b.
...For anyone with an nVidia card and not able to get sound to go through their HDMI cable and does not even show HDMI or digital as an option in sound preferences this may be able to help:

1. Add "ppa:ubuntu-audio-dev/ppa" to the repository in synaptic. Refresh synaptic.

2. Upgrade all the pulse-audio packages

3. find out your kernel version: type "uname -r" in a terminal. Mine came out to be 2.6.32-21-generic (default ubuntu 10.04).

4. install "linux-alsa-driver-modules-2.6.32-21-generic" (your kernel may be different).

I got this package from a launchpad bug that listed it as a possible fix to the dreaded sound through HDMI cables problem. Installing this package gave me the options in sound preferences to choose digital sound/HDMI (IEC958 ). I'm not 100% sure that being able to see IEC958 in sound preferences came right after updating all pulse-audio packages or if it only came after installing this package.

I did also have to change some sound setting on MythTV's frontend. Go to Utilities/Setup -> General -> Audio system -> Audio output device -> change to ALSA:spdif

Let me know if anyone else had/has this problem



Other options that MythTV includes are all up to you, hopefully following this guide gives you a working system. If not ask a question and I or someone else on the forums will answer it.

You should now be able to watch/record TV.



A Few Things:

I must say the Linux HTPC community is way too technical for many people, they need to make these things simpler, Windows 7 MCE is 10 times better at setting up these things, oh and it supports this tuner completely so if you want or need Analog support, right now Windows is the answer for people who want things to "just work". Think about the cost, as Windows Home Premium is about $100US for an OEM copy, and while Mythbuntu is free, the channel guide from ScheduleDirect.org is $20US a year. So if you expect 5 years from your machine and don't want to worry about an update breaking the system then Windows pays for itself. I like using MythTV over Windows Media Center for a few reasons, the first being no DRM, the second being better network options. Lastly I turn updates off once the system is running to ensure nothing changes. You might not think its a safe option but for a system that is working properly and is not used for other purposes its more than likely fine.

A special thanks to Steven over at KernelLabs (http://www.kernellabs.com/blog/?page_id=17), the person who made the drivers.


Sources
http://www.linuxtv.org/wiki/index.php/How_to_Obtain%2C_Build_and_Install_V4L-DVB_Device_Drivers
http://www.kernellabs.com/blog/?page_id=17
http://kernellabs.com/hg/saa7164-stable/
http://parker1.co.uk/mythtv_ubuntu.php
http://www.linuxtv.org/wiki/index.php/How_to_Obtain%2C_Build_and_Install_V4L-DVB_Device_Drivers#Using_Mercurial
http://www.steventoth.net/blog/products/hvr-2250/
http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-2200

dividehex
May 3rd, 2010, 05:31 AM
Once again, Great instructions! One thing I would like to point out is I did not have to download/compile/install the driver source since the default kernel (2.6.32-21) with 10.04 already has it. The only thing I had to do was download/unzip/install the firmware. Once I did that, the card was detected and initialized properly on reboot.

BTW, running on HVR-2250 with only one tuner setup in mythtv is going strong with 5 days uptime. This is the longest uptime I've ever seen on my hvr-2250+mythtv system.

LowSky
May 3rd, 2010, 06:18 AM
Once again, Great instructions! One thing I would like to point out is I did not have to download/compile/install the driver source since the default kernel (2.6.32-21) with 10.04 already has it. The only thing I had to do was download/unzip/install the firmware. Once I did that, the card was detected and initialized properly on reboot.

BTW, running on HVR-2250 with only one tuner setup in mythtv is going strong with 5 days uptime. This is the longest uptime I've ever seen on my hvr-2250+mythtv system.

Thanks for the info. Any reason why the other tuner isn't working? my own system wouldnt keep stable using 10.04 so I reverted back to 9.10. Things like sound over HDMI and channel changing were more important. I left the driver info in because at anytime new drivers could come out supporting the analog capabilities. Maybe i'll fix that part so that its more universal. We will see. This thing cost me my whole weekend, I need some sleep!

dividehex
May 3rd, 2010, 06:42 PM
Any reason why the other tuner isn't working?
It really isn't an issue of my second tuner not working. In fact, both tuners work fine by the driver point of view. I purposely did not configure the second tuner to show that the i2c errors were only triggered when both tuners would record. Since I only configured one tuner and therefore can record only one thing at a time the system has be very stable. If I were to configure the second tuner and wait for the hvr-2250 to begin recording from both tuners, the driver would inevitably crash and flood the kern.log with i2c errors. When I have some time, I will see it if I can force the i2c errors outside of mythtv. If I can recreate the errors manual, I will send Steve an email with the info in the hopes that he might spare some of his time to find and fix the issue.

tjbron
May 3rd, 2010, 07:14 PM
dividehex,
For what it's worth, I set up that script to beep at me when the i2c read errors start showing up in the kern.log. What I discovered is that I get them occasionally even when the tuners are still working. Just thought that was interesting.

dividehex
May 3rd, 2010, 10:42 PM
dividehex,
For what it's worth, I set up that script to beep at me when the i2c read errors start showing up in the kern.log. What I discovered is that I get them occasionally even when the tuners are still working. Just thought that was interesting.

1. Out of curiosity, when was the last time you updated the saa-7164 driver?
2. Also, when you say you get i2c errors occasionally when both tuners are working, do you mean when both tuners are recording at the same time or when both tuners are configured but only one is recording?
3. Last, when you get an i2c error does the card stop working and then flood kern.log with more i2c errors or does it just report a few errors and then continue working?

tjbron
May 3rd, 2010, 11:31 PM
1. Out of curiosity, when was the last time you updated the saa-7164 driver?
2. Also, when you say you get i2c errors occasionally when both tuners are working, do you mean when both tuners are recording at the same time or when both tuners are configured but only one is recording?
3. Last, when you get an i2c error does the card stop working and then flood kern.log with more i2c errors or does it just report a few errors and then continue working?

1. yeesh, uh, I don't think I've touched it since I built the system. Early 2009 maybe? I can check the version.

2. Sorry, I meant both tuners are configured. At the time I noticed the errors, I would have been recording on only one or none, however I do make use of the over-the-air schedule. So that could make things more convoluted. It very well may have been using both tuners (one for recording, one for OTA schedule).

3. In the past, I have only looked at the kern.log when it was flooding with errors, so I assumed that was the only time it happened. Last night after I set up the alarm script, it was beeping at me (a few kern.log i2c errors within a few minutes) but the tuners seemed to be working still. I could still go to live tv, for instance.

I will correlate my myth and kern logs and try to figure out the circumstances of the error message.

Thanks for being involved in this, by the way. For awhile, I couldn't find anyone else who was having these issues and I figured it was just because it was my first linux system.

kuehlc
May 3rd, 2010, 11:56 PM
1. yeesh, uh, I don't think I've touched it since I built the system. Early 2009 maybe? I can check the version.

2. Sorry, I meant both tuners are configured. At the time I noticed the errors, I would have been recording on only one or none, however I do make use of the over-the-air schedule. So that could make things more convoluted. It very well may have been using both tuners (one for recording, one for OTA schedule).

3. In the past, I have only looked at the kern.log when it was flooding with errors, so I assumed that was the only time it happened. Last night after I set up the alarm script, it was beeping at me (a few kern.log i2c errors within a few minutes) but the tuners seemed to be working still. I could still go to live tv, for instance.

I will correlate my myth and kern logs and try to figure out the circumstances of the error message.

Thanks for being involved in this, by the way. For awhile, I couldn't find anyone else who was having these issues and I figured it was just because it was my first linux system.

Well you are definitely not alone as I'm having the same issue. I haven't had a ton of time to debug this but have been watching your thread for awhile. I did email Steve Toth regarding this a few weeks ago and was surprised to get a prompt response asking if I was running the current version. I replied that I hadn't seen any changes in the driver that seemed relevant so I hadn't updated anything. To that I received the reply "so thats a no then?" and haven't heard anything else.

Is anyone seeing this error in 10.04 with the new driver in the kernel?

dividehex
May 4th, 2010, 12:50 AM
Is anyone seeing this error in 10.04 with the new driver in the kernel?

Yes, I have been running 10.04 with the stock driver and it is the same problem i had with the previous ubuntu versions.

tjbron
May 4th, 2010, 04:29 AM
1. yeesh, uh, I don't think I've touched it since I built the system. Early 2009 maybe? I can check the version.
Update: I installed the driver in July 2009, running the jackalope.

2. Sorry, I meant both tuners are configured. At the time I noticed the errors, I would have been recording on only one or none, however I do make use of the over-the-air schedule. So that could make things more convoluted. It very well may have been using both tuners (one for recording, one for OTA schedule).
Update: it was ticking away the errors this evening while the tuners were still operational. I was not running them, but the OTA schedule may have been updating. kern.log included below.

3. In the past, I have only looked at the kern.log when it was flooding with errors, so I assumed that was the only time it happened. Last night after I set up the alarm script, it was beeping at me (a few kern.log i2c errors within a few minutes) but the tuners seemed to be working still. I could still go to live tv, for instance.

I will correlate my myth and kern logs and try to figure out the circumstances of the error message.



Hopefully this is helpful to someone. If you scroll down a bit you will start seeing read as well as write errors (i2c). My tuners were still operational during this.
Thanks again.


May 3 17:17:18 bronson-myth kernel: [ 6.509069] lirc_mceusb2[2]: Topseed Technology Corp. eHome Infrared Transceiver on usb2:2
May 3 17:17:18 bronson-myth kernel: [ 6.509120] usbcore: registered new interface driver lirc_mceusb2
May 3 17:17:18 bronson-myth kernel: [ 6.588198] Linux agpgart interface v0.103
May 3 17:17:18 bronson-myth kernel: [ 6.910058] ACPI: I/O resource piix4_smbus [0x400-0x407] conflicts with ACPI region SM00 [0x400-0x407]
May 3 17:17:18 bronson-myth kernel: [ 6.910062] ACPI: Device needs an ACPI driver
May 3 17:17:18 bronson-myth kernel: [ 6.910069] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0x400, revision 0
May 3 17:17:18 bronson-myth kernel: [ 6.932151] ppdev: user-space parallel port driver
May 3 17:17:18 bronson-myth kernel: [ 6.975825] synaptics was reset on resume, see synaptics_resume_reset if you have trouble on resume
May 3 17:17:18 bronson-myth kernel: [ 7.453541] psmouse serio1: ID: 10 00 64<4>nvidia: module license 'NVIDIA' taints kernel.
May 3 17:17:18 bronson-myth kernel: [ 7.893632] nvidia 0000:02:09.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
May 3 17:17:18 bronson-myth kernel: [ 7.899690] NVRM: loading NVIDIA UNIX x86 Kernel Module 173.14.20 Thu Jun 25 19:23:24 PDT 2009
May 3 17:17:18 bronson-myth kernel: [ 7.954185] saa7164 driver loaded
May 3 17:17:18 bronson-myth kernel: [ 7.954313] saa7164 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
May 3 17:17:18 bronson-myth kernel: [ 7.954610] CORE saa7164[0]: dev->lmmio = 0xe0b00000
May 3 17:17:18 bronson-myth kernel: [ 7.954611] CORE saa7164[0]: dev->lmmio2 = 0xe1980000
May 3 17:17:18 bronson-myth kernel: [ 7.954613] CORE saa7164[0]: dev->bmmio = 0xe0b00000
May 3 17:17:18 bronson-myth kernel: [ 7.954615] CORE saa7164[0]: dev->bmmio2 = 0xe1980000
May 3 17:17:18 bronson-myth kernel: [ 7.954617] CORE saa7164[0]: subsystem: 0070:8891, board: Hauppauge WinTV-HVR2250 [card=7,autodetected]
May 3 17:17:18 bronson-myth kernel: [ 7.954623] saa7164[0]/0: found at 0000:01:00.0, rev: 129, irq: 18, latency: 0, mmio: 0xfd800000
May 3 17:17:18 bronson-myth kernel: [ 7.954629] saa7164 0000:01:00.0: setting latency timer to 64
May 3 17:17:18 bronson-myth kernel: [ 8.051033] ATI IXP AC97 controller 0000:00:14.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
May 3 17:17:18 bronson-myth kernel: [ 8.092479] input: ImPS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio1/input/input5
May 3 17:17:18 bronson-myth kernel: [ 8.120026] saa7164_downloadfirmware() no first image
May 3 17:17:18 bronson-myth kernel: [ 8.120038] saa7164_downloadfirmware() Waiting for firmware upload (v4l-saa7164-1.0.3.fw)
May 3 17:17:18 bronson-myth kernel: [ 8.120042] saa7164 0000:01:00.0: firmware: requesting v4l-saa7164-1.0.3.fw
May 3 17:17:18 bronson-myth kernel: [ 10.327185] saa7164_downloadfirmware() firmware read 3978608 bytes.
May 3 17:17:18 bronson-myth kernel: [ 10.327188] saa7164_downloadfirmware() firmware loaded.
May 3 17:17:18 bronson-myth kernel: [ 10.327190] Firmware file header part 1:
May 3 17:17:18 bronson-myth kernel: [ 10.327191] .FirmwareSize = 0x0
May 3 17:17:18 bronson-myth kernel: [ 10.327192] .BSLSize = 0x0
May 3 17:17:18 bronson-myth kernel: [ 10.327194] .Reserved = 0x3cb57
May 3 17:17:18 bronson-myth kernel: [ 10.327195] .Version = 0x3
May 3 17:17:18 bronson-myth kernel: [ 10.327196] saa7164_downloadfirmware() SecBootLoader.FileSize = 3978608
May 3 17:17:18 bronson-myth kernel: [ 10.327202] saa7164_downloadfirmware() FirmwareSize = 0x1fd6
May 3 17:17:18 bronson-myth kernel: [ 10.327204] saa7164_downloadfirmware() BSLSize = 0x0
May 3 17:17:18 bronson-myth kernel: [ 10.327205] saa7164_downloadfirmware() Reserved = 0x0
May 3 17:17:18 bronson-myth kernel: [ 10.327207] saa7164_downloadfirmware() Version = 0x51cc1
May 3 17:17:18 bronson-myth kernel: [ 11.381103] usb-storage: device scan complete
May 3 17:17:18 bronson-myth kernel: [ 11.387089] scsi 4:0:0:0: Direct-Access Generic USB SD Reader 1.00 PQ: 0 ANSI: 0
May 3 17:17:18 bronson-myth kernel: [ 11.393083] scsi 4:0:0:1: Direct-Access Generic USB CF Reader 1.01 PQ: 0 ANSI: 0
May 3 17:17:18 bronson-myth kernel: [ 11.399079] scsi 4:0:0:2: Direct-Access Generic USB SM Reader 1.02 PQ: 0 ANSI: 0
May 3 17:17:18 bronson-myth kernel: [ 11.405078] scsi 4:0:0:3: Direct-Access Generic USB MS Reader 1.03 PQ: 0 ANSI: 0
May 3 17:17:18 bronson-myth kernel: [ 11.415238] sd 4:0:0:0: [sdb] Attached SCSI removable disk
May 3 17:17:18 bronson-myth kernel: [ 11.415340] sd 4:0:0:0: Attached scsi generic sg2 type 0
May 3 17:17:18 bronson-myth kernel: [ 11.427182] sd 4:0:0:1: [sdc] Attached SCSI removable disk
May 3 17:17:18 bronson-myth kernel: [ 11.427292] sd 4:0:0:1: Attached scsi generic sg3 type 0
May 3 17:17:18 bronson-myth kernel: [ 11.436271] sd 4:0:0:2: [sdd] Attached SCSI removable disk
May 3 17:17:18 bronson-myth kernel: [ 11.436396] sd 4:0:0:2: Attached scsi generic sg4 type 0
May 3 17:17:18 bronson-myth kernel: [ 11.456241] sd 4:0:0:3: [sde] Attached SCSI removable disk
May 3 17:17:18 bronson-myth kernel: [ 11.456344] sd 4:0:0:3: Attached scsi generic sg5 type 0
May 3 17:17:18 bronson-myth kernel: [ 17.184026] saa7164_downloadimage() Image downloaded, booting...
May 3 17:17:18 bronson-myth kernel: [ 17.288017] saa7164_downloadimage() Image booted successfully.
May 3 17:17:18 bronson-myth kernel: [ 17.288041] starting firmware download(2)
May 3 17:17:18 bronson-myth kernel: [ 19.412025] saa7164_downloadimage() Image downloaded, booting...
May 3 17:17:18 bronson-myth kernel: [ 21.076021] saa7164_downloadimage() Image booted successfully.
May 3 17:17:18 bronson-myth kernel: [ 21.076042] firmware download complete.
May 3 17:17:18 bronson-myth kernel: [ 21.076999] saa7164[0]: i2c bus 0 registered
May 3 17:17:18 bronson-myth kernel: [ 21.077080] saa7164[0]: i2c bus 1 registered
May 3 17:17:18 bronson-myth kernel: [ 21.077160] saa7164[0]: i2c bus 2 registered
May 3 17:17:18 bronson-myth kernel: [ 21.112265] tveeprom 1-0000: Hauppauge model 88061, rev C3F2, serial# 6225133
May 3 17:17:18 bronson-myth kernel: [ 21.112268] tveeprom 1-0000: MAC address is 00-0D-FE-5E-FC-ED
May 3 17:17:18 bronson-myth kernel: [ 21.112270] tveeprom 1-0000: tuner model is NXP 18271C2_716x (idx 152, type 4)
May 3 17:17:18 bronson-myth kernel: [ 21.112272] tveeprom 1-0000: TV standards NTSC(M) ATSC/DVB Digital (eeprom 0x88)
May 3 17:17:18 bronson-myth kernel: [ 21.112274] tveeprom 1-0000: audio processor is SAA7164 (idx 43)
May 3 17:17:18 bronson-myth kernel: [ 21.112276] tveeprom 1-0000: decoder processor is SAA7164 (idx 40)
May 3 17:17:18 bronson-myth kernel: [ 21.112278] tveeprom 1-0000: has radio, has IR receiver, has no IR transmitter
May 3 17:17:18 bronson-myth kernel: [ 21.112280] saa7164[0]: Hauppauge eeprom: model=88061
May 3 17:17:18 bronson-myth kernel: [ 21.505221] tda18271 2-0060: creating new instance
May 3 17:17:18 bronson-myth kernel: [ 21.509576] TDA18271HD/C2 detected @ 2-0060
May 3 17:17:18 bronson-myth kernel: [ 21.760963] DVB: registering new adapter (saa7164)
May 3 17:17:18 bronson-myth kernel: [ 21.760970] DVB: registering adapter 0 frontend 611647248 (Samsung S5H1411 QAM/8VSB Frontend)...
May 3 17:17:18 bronson-myth kernel: [ 22.045258] tda18271 3-0060: creating new instance
May 3 17:17:18 bronson-myth kernel: [ 22.049734] TDA18271HD/C2 detected @ 3-0060
May 3 17:17:18 bronson-myth kernel: [ 22.300741] DVB: registering new adapter (saa7164)
May 3 17:17:18 bronson-myth kernel: [ 22.300748] DVB: registering adapter 1 frontend 0 (Samsung S5H1411 QAM/8VSB Frontend)...
May 3 17:17:18 bronson-myth kernel: [ 22.401630] lp0: using parport0 (interrupt-driven).
May 3 17:17:18 bronson-myth kernel: [ 22.608972] Adding 2385644k swap on /dev/sda4. Priority:-1 extents:1 across:2385644k
May 3 17:17:18 bronson-myth kernel: [ 23.239565] EXT3 FS on sda2, internal journal
May 3 17:17:18 bronson-myth kernel: [ 24.129254] kjournald starting. Commit interval 5 seconds
May 3 17:17:18 bronson-myth kernel: [ 24.129525] EXT3 FS on sda3, internal journal
May 3 17:17:18 bronson-myth kernel: [ 24.129530] EXT3-fs: mounted filesystem with ordered data mode.
May 3 17:17:18 bronson-myth kernel: [ 24.602595] type=1505 audit(1272932236.482:2): operation="profile_load" name="/sbin/dhclient-script" name2="default" pid=1996
May 3 17:17:18 bronson-myth kernel: [ 24.602743] type=1505 audit(1272932236.482:3): operation="profile_load" name="/sbin/dhclient3" name2="default" pid=1996
May 3 17:17:18 bronson-myth kernel: [ 24.602788] type=1505 audit(1272932236.482:4): operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-client.action" name2="default" pid=1996
May 3 17:17:18 bronson-myth kernel: [ 24.602830] type=1505 audit(1272932236.482:5): operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" name2="default" pid=1996
May 3 17:17:18 bronson-myth kernel: [ 24.747091] type=1505 audit(1272932236.626:6): operation="profile_load" name="/usr/lib/cups/backend/cups-pdf" name2="default" pid=2001
May 3 17:17:18 bronson-myth kernel: [ 24.747296] type=1505 audit(1272932236.626:7): operation="profile_load" name="/usr/sbin/cupsd" name2="default" pid=2001
May 3 17:17:18 bronson-myth kernel: [ 24.774153] type=1505 audit(1272932236.654:8): operation="profile_load" name="/usr/sbin/mysqld" name2="default" pid=2005
May 3 17:17:18 bronson-myth kernel: [ 24.800814] type=1505 audit(1272932236.682:9): operation="profile_load" name="/usr/sbin/tcpdump" name2="default" pid=2009
May 3 17:17:18 bronson-myth kernel: [ 26.809399] slamr: SmartLink AMRMO modem.
May 3 17:17:18 bronson-myth kernel: [ 26.809416] slamr: device 1057:3052 is grabbed by another driver
May 3 17:17:28 bronson-myth kernel: [ 36.396796] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
May 3 17:17:28 bronson-myth kernel: [ 36.396799] Bluetooth: BNEP filters: protocol multicast
May 3 17:17:28 bronson-myth kernel: [ 36.418773] Bridge firewalling registered
May 3 17:17:29 bronson-myth kernel: [ 37.296571] tda18271: performing RF tracking filter calibration
May 3 17:17:32 bronson-myth kernel: [ 40.501767] tda18271: RF tracking filter calibration complete
May 3 17:17:34 bronson-myth kernel: [ 42.118249] eth0: link down
May 3 17:17:34 bronson-myth kernel: [ 42.118358] ADDRCONF(NETDEV_UP): eth0: link is not ready
May 3 17:17:34 bronson-myth kernel: [ 42.164020] Event timed out
May 3 17:17:34 bronson-myth kernel: [ 42.164026] saa7164_api_i2c_write() error, ret(1) = 0x32
May 3 17:17:34 bronson-myth kernel: [ 42.164030] s5h1411_writereg: writereg error 0x19 0x3e 0x77ee, ret == -5)
May 3 17:17:34 bronson-myth kernel: [ 42.164455] found timed out command on the bus
May 3 17:17:34 bronson-myth kernel: [ 42.164483] ret = 0
May 3 17:17:34 bronson-myth kernel: [ 42.164484] timeout continue
May 3 17:17:34 bronson-myth kernel: [ 42.465264] tda18271: performing RF tracking filter calibration
May 3 17:17:36 bronson-myth kernel: [ 44.921844] tda18271: RF tracking filter calibration complete
May 3 17:18:37 bronson-myth kernel: [ 105.992203] Clocksource tsc unstable (delta = -272837835 ns)
May 3 17:44:11 bronson-myth kernel: [ 1639.164030] Event timed out
May 3 17:44:11 bronson-myth kernel: [ 1639.164039] saa7164_api_i2c_read() error, ret(1) = 0x32
May 3 17:44:11 bronson-myth kernel: [ 1639.164045] s5h1411_readreg: readreg error (ret == -5)
May 3 17:44:11 bronson-myth kernel: [ 1639.164495] found timed out command on the bus
May 3 17:44:11 bronson-myth kernel: [ 1639.164525] ret = 0
May 3 17:44:11 bronson-myth kernel: [ 1639.164528] timeout continue
May 3 17:45:17 bronson-myth kernel: [ 1705.736028] Event timed out
May 3 17:45:17 bronson-myth kernel: [ 1705.736037] saa7164_api_i2c_write() error, ret(2) = 0x32
May 3 17:45:17 bronson-myth kernel: [ 1705.736044] s5h1411_writereg: writereg error 0x19 0xf5 0x0000, ret == -5)
May 3 17:45:17 bronson-myth kernel: [ 1705.736455] found timed out command on the bus
May 3 17:45:17 bronson-myth kernel: [ 1705.736688] ret = 0
May 3 17:45:17 bronson-myth kernel: [ 1705.736690] timeout continue
May 3 17:55:51 bronson-myth kernel: [ 2339.784037] Event timed out
May 3 17:55:51 bronson-myth kernel: [ 2339.784047] saa7164_api_i2c_read() error, ret(2) = 0x32
May 3 17:55:51 bronson-myth kernel: [ 2339.784053] s5h1411_readreg: readreg error (ret == -5)
May 3 17:55:51 bronson-myth kernel: [ 2339.784467] found timed out command on the bus
May 3 17:55:51 bronson-myth kernel: [ 2339.784699] ret = 0
May 3 17:55:51 bronson-myth kernel: [ 2339.784702] timeout continue
May 3 17:59:16 bronson-myth kernel: [ 2544.568034] Event timed out
May 3 17:59:16 bronson-myth kernel: [ 2544.568044] saa7164_api_i2c_read() error, ret(2) = 0x32
May 3 17:59:16 bronson-myth kernel: [ 2544.568050] s5h1411_readreg: readreg error (ret == -5)
May 3 17:59:16 bronson-myth kernel: [ 2544.568495] found timed out command on the bus
May 3 17:59:16 bronson-myth kernel: [ 2544.568727] ret = 0
May 3 17:59:16 bronson-myth kernel: [ 2544.568730] timeout continue
May 3 18:12:36 bronson-myth kernel: [ 3344.956059] Event timed out
May 3 18:12:36 bronson-myth kernel: [ 3344.956069] saa7164_api_i2c_read() error, ret(2) = 0x32
May 3 18:12:36 bronson-myth kernel: [ 3344.956076] tda18271_read_regs: ERROR: i2c_transfer returned: -5
May 3 18:12:36 bronson-myth kernel: [ 3344.957163] found timed out command on the bus
May 3 18:12:36 bronson-myth kernel: [ 3344.957303] ret = 0
May 3 18:12:36 bronson-myth kernel: [ 3344.957306] timeout continue
May 3 18:24:17 bronson-myth kernel: [ 4045.536032] Event timed out
May 3 18:24:17 bronson-myth kernel: [ 4045.536042] saa7164_api_i2c_read() error, ret(2) = 0x32
May 3 18:24:17 bronson-myth kernel: [ 4045.536047] s5h1411_readreg: readreg error (ret == -5)
May 3 18:24:17 bronson-myth kernel: [ 4045.536759] found timed out command on the bus
May 3 18:24:17 bronson-myth kernel: [ 4045.536993] ret = 0
May 3 18:24:17 bronson-myth kernel: [ 4045.536996] timeout continue
May 3 18:44:00 bronson-myth kernel: [ 5228.964038] Event timed out
May 3 18:44:00 bronson-myth kernel: [ 5228.964048] saa7164_api_i2c_read() error, ret(1) = 0x32
May 3 18:44:00 bronson-myth kernel: [ 5228.964054] s5h1411_readreg: readreg error (ret == -5)
May 3 18:44:00 bronson-myth kernel: [ 5228.964489] found timed out command on the bus
May 3 18:44:00 bronson-myth kernel: [ 5228.964523] ret = 0
May 3 18:44:00 bronson-myth kernel: [ 5228.964525] timeout continue
May 3 19:39:28 bronson-myth kernel: [ 8556.524030] Event timed out
May 3 19:39:28 bronson-myth kernel: [ 8556.524040] saa7164_api_i2c_read() error, ret(2) = 0x32
May 3 19:39:28 bronson-myth kernel: [ 8556.524047] s5h1411_readreg: readreg error (ret == -5)
May 3 19:39:28 bronson-myth kernel: [ 8556.524526] found timed out command on the bus
May 3 19:39:28 bronson-myth kernel: [ 8556.524659] ret = 0
May 3 19:39:28 bronson-myth kernel: [ 8556.524662] timeout continue
May 3 19:40:30 bronson-myth kernel: [ 8618.240030] Event timed out
May 3 19:40:30 bronson-myth kernel: [ 8618.240040] saa7164_api_i2c_read() error, ret(2) = 0x32
May 3 19:40:30 bronson-myth kernel: [ 8618.240046] s5h1411_readreg: readreg error (ret == -5)
May 3 19:40:30 bronson-myth kernel: [ 8618.240515] found timed out command on the bus
May 3 19:40:30 bronson-myth kernel: [ 8618.240648] ret = 0
May 3 19:40:30 bronson-myth kernel: [ 8618.240651] timeout continue
May 3 19:40:31 bronson-myth kernel: [ 8619.404030] Event timed out
May 3 19:40:31 bronson-myth kernel: [ 8619.404039] saa7164_api_i2c_write() error, ret(2) = 0x32
May 3 19:40:31 bronson-myth kernel: [ 8619.404046] tda18271_write_regs: ERROR: i2c_transfer returned: -5
May 3 19:40:31 bronson-myth kernel: [ 8619.404838] found timed out command on the bus
May 3 19:40:31 bronson-myth kernel: [ 8619.404972] ret = 0
May 3 19:40:31 bronson-myth kernel: [ 8619.404974] timeout continue

dividehex
May 4th, 2010, 07:10 AM
Hmmm. Interesting. I wonder if these are two different bugs. I've never gotten i2c errors without the card going completely fubar. In my setup, I am connected to cable (comcast SF Bay Area) and not using OTA. I use schedule direct to get programming data.

Here is a snippet of my kern.log when it first begins.

Apr 26 23:09:14 mythtv kernel: [ 17.301416] CPU1 attaching sched-domain:
Apr 26 23:09:14 mythtv kernel: [ 17.301417] domain 0: span 0-1 level MC
Apr 26 23:09:14 mythtv kernel: [ 17.301419] groups: 1 0
Apr 26 23:09:18 mythtv kernel: [ 21.780249] saa7164_downloadimage() Image downloaded, booting...
Apr 26 23:09:18 mythtv kernel: [ 21.890080] saa7164_downloadimage() Image booted successfully.
Apr 26 23:09:18 mythtv kernel: [ 21.890105] starting firmware download(2)
Apr 26 23:09:21 mythtv kernel: [ 24.230107] saa7164_downloadimage() Image downloaded, booting...
Apr 26 23:09:22 mythtv kernel: [ 25.660061] saa7164_downloadimage() Image booted successfully.
Apr 26 23:09:22 mythtv kernel: [ 25.660089] firmware download complete.
Apr 26 23:09:22 mythtv kernel: [ 25.700421] tveeprom 4-0000: Hauppauge model 88061, rev C3F2, serial# 6236058
Apr 26 23:09:22 mythtv kernel: [ 25.700425] tveeprom 4-0000: MAC address is 00-0D-FE-5F-27-9A
Apr 26 23:09:22 mythtv kernel: [ 25.700427] tveeprom 4-0000: tuner model is NXP 18271C2_716x (idx 152, type 4)
Apr 26 23:09:22 mythtv kernel: [ 25.700430] tveeprom 4-0000: TV standards NTSC(M) ATSC/DVB Digital (eeprom 0x88)
Apr 26 23:09:22 mythtv kernel: [ 25.700432] tveeprom 4-0000: audio processor is SAA7164 (idx 43)
Apr 26 23:09:22 mythtv kernel: [ 25.700434] tveeprom 4-0000: decoder processor is SAA7164 (idx 40)
Apr 26 23:09:22 mythtv kernel: [ 25.700437] tveeprom 4-0000: has radio, has IR receiver, has no IR transmitter
Apr 26 23:09:22 mythtv kernel: [ 25.700439] saa7164[0]: Hauppauge eeprom: model=88061
Apr 26 23:09:22 mythtv kernel: [ 26.098479] tda18271 5-0060: creating new instance
Apr 26 23:09:22 mythtv kernel: [ 26.102797] TDA18271HD/C2 detected @ 5-0060
Apr 26 23:09:23 mythtv kernel: [ 26.445053] DVB: registering new adapter (saa7164)
Apr 26 23:09:23 mythtv kernel: [ 26.445060] DVB: registering adapter 0 frontend 0 (Samsung S5H1411 QAM/8VSB Frontend)...
Apr 26 23:09:23 mythtv kernel: [ 26.729896] tda18271 6-0060: creating new instance
Apr 26 23:09:23 mythtv kernel: [ 26.734056] TDA18271HD/C2 detected @ 6-0060
Apr 26 23:09:23 mythtv kernel: [ 26.740128] eth0: no IPv6 routers present
Apr 26 23:09:23 mythtv kernel: [ 27.084739] tda18271: performing RF tracking filter calibration
Apr 26 23:09:26 mythtv kernel: [ 29.717802] tda18271: RF tracking filter calibration complete
Apr 26 23:09:26 mythtv kernel: [ 29.718073] DVB: registering new adapter (saa7164)
Apr 26 23:09:26 mythtv kernel: [ 29.718079] DVB: registering adapter 1 frontend 0 (Samsung S5H1411 QAM/8VSB Frontend)...
Apr 26 23:10:14 mythtv kernel: [ 78.011310] Clocksource tsc unstable (delta = -289910092 ns)
Apr 26 23:13:58 mythtv kernel: [ 301.953817] CE: hpet increasing min_delta_ns to 15000 nsec
Apr 27 00:43:22 mythtv kernel: [ 5665.500599] tda18271: performing RF tracking filter calibration
Apr 27 00:43:25 mythtv kernel: [ 5668.139518] tda18271: RF tracking filter calibration complete
Apr 27 12:58:43 mythtv kernel: [49786.691293] CE: hpet increasing min_delta_ns to 22500 nsec
Apr 27 21:40:32 mythtv kernel: [81095.341654] Event timed out
Apr 27 21:40:32 mythtv kernel: [81095.341668] saa7164_api_i2c_read() error, ret(1) = 0x32
Apr 27 21:40:32 mythtv kernel: [81095.341676] s5h1411_readreg: readreg error (ret == -5)
Apr 27 21:40:32 mythtv kernel: [81095.710180] Event timed out
Apr 27 21:40:32 mythtv kernel: [81095.710194] saa7164_api_i2c_read() error, ret(1) = 0x32
Apr 27 21:40:32 mythtv kernel: [81095.710201] s5h1411_readreg: readreg error (ret == -5)
Apr 27 21:40:42 mythtv kernel: [81105.340173] Event timed out
Apr 27 21:40:42 mythtv kernel: [81105.340186] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:40:42 mythtv kernel: [81105.340196] s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)
Apr 27 21:40:42 mythtv kernel: [81105.710233] Event timed out
Apr 27 21:40:42 mythtv kernel: [81105.710247] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:40:42 mythtv kernel: [81105.710255] s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)
Apr 27 21:40:52 mythtv kernel: [81115.340066] Event timed out
Apr 27 21:40:52 mythtv kernel: [81115.340081] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:40:52 mythtv kernel: [81115.340089] s5h1411_writereg: writereg error 0x19 0xf7 0x0001, ret == -5)
Apr 27 21:40:52 mythtv kernel: [81115.710201] Event timed out
Apr 27 21:40:52 mythtv kernel: [81115.710214] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:40:52 mythtv kernel: [81115.710223] s5h1411_writereg: writereg error 0x19 0xf7 0x0001, ret == -5)
Apr 27 21:40:56 mythtv kernel: [81119.480196] Event timed out
Apr 27 21:40:56 mythtv kernel: [81119.480209] saa7164_api_transition_port() error, ret = 0x32
Apr 27 21:40:56 mythtv kernel: [81119.480215] saa7164_dvb_pause_tsport() pause transition failed, ret = 0x32
Apr 27 21:40:56 mythtv kernel: [81119.500218] Event timed out
Apr 27 21:40:56 mythtv kernel: [81119.500232] saa7164_api_transition_port() error, ret = 0x32
Apr 27 21:40:56 mythtv kernel: [81119.500238] saa7164_dvb_pause_tsport() pause transition failed, ret = 0x32
Apr 27 21:41:02 mythtv kernel: [81125.340047] Event timed out
Apr 27 21:41:02 mythtv kernel: [81125.340061] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:41:02 mythtv kernel: [81125.340070] s5h1411_writereg: writereg error 0x19 0xf5 0x0001, ret == -5)
Apr 27 21:41:02 mythtv kernel: [81125.710060] Event timed out
Apr 27 21:41:02 mythtv kernel: [81125.710080] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:41:02 mythtv kernel: [81125.710088] s5h1411_writereg: writereg error 0x19 0xf5 0x0001, ret == -5)
Apr 27 21:41:06 mythtv kernel: [81129.480216] Event timed out
Apr 27 21:41:06 mythtv kernel: [81129.480231] saa7164_api_transition_port() error, ret = 0x32
Apr 27 21:41:06 mythtv kernel: [81129.480238] saa7164_dvb_acquire_tsport() acquire transition failed, ret = 0x32
Apr 27 21:41:06 mythtv kernel: [81129.500172] Event timed out
Apr 27 21:41:06 mythtv kernel: [81129.500187] saa7164_api_transition_port() error, ret = 0x32
Apr 27 21:41:06 mythtv kernel: [81129.500193] saa7164_dvb_acquire_tsport() acquire transition failed, ret = 0x32
Apr 27 21:41:12 mythtv kernel: [81135.340076] Event timed out
Apr 27 21:41:12 mythtv kernel: [81135.340092] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:41:12 mythtv kernel: [81135.340101] tda18271_write_regs: ERROR: idx = 0x5, len = 1, i2c_transfer returned: -5
Apr 27 21:41:12 mythtv kernel: [81135.340108] tda18271_init: error -5 on line 826
Apr 27 21:41:12 mythtv kernel: [81135.340113] tda18271_tune: error -5 on line 904
Apr 27 21:41:12 mythtv kernel: [81135.340118] tda18271_set_params: error -5 on line 985
Apr 27 21:41:12 mythtv kernel: [81135.710069] Event timed out
Apr 27 21:41:12 mythtv kernel: [81135.710082] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:41:12 mythtv kernel: [81135.710091] tda18271_write_regs: ERROR: idx = 0x5, len = 1, i2c_transfer returned: -5
Apr 27 21:41:12 mythtv kernel: [81135.710098] tda18271_init: error -5 on line 826
Apr 27 21:41:12 mythtv kernel: [81135.710102] tda18271_tune: error -5 on line 904
Apr 27 21:41:12 mythtv kernel: [81135.710108] tda18271_set_params: error -5 on line 985
Apr 27 21:41:16 mythtv kernel: [81139.480059] Event timed out
Apr 27 21:41:16 mythtv kernel: [81139.480074] saa7164_api_transition_port() error, ret = 0x32
Apr 27 21:41:16 mythtv kernel: [81139.480079] saa7164_dvb_stop_tsport() stop transition failed, ret = 0x32
Apr 27 21:41:16 mythtv kernel: [81139.501622] Event timed out
Apr 27 21:41:16 mythtv kernel: [81139.501635] saa7164_api_transition_port() error, ret = 0x32
Apr 27 21:41:16 mythtv kernel: [81139.501641] saa7164_dvb_stop_tsport() stop transition failed, ret = 0x32
Apr 27 21:41:22 mythtv kernel: [81145.340049] Event timed out
Apr 27 21:41:22 mythtv kernel: [81145.340065] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:41:22 mythtv kernel: [81145.340074] s5h1411_writereg: writereg error 0x19 0xf5 0x0000, ret == -5)
Apr 27 21:41:22 mythtv kernel: [81145.710175] Event timed out
Apr 27 21:41:22 mythtv kernel: [81145.710190] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:41:22 mythtv kernel: [81145.710199] s5h1411_writereg: writereg error 0x19 0xf5 0x0000, ret == -5)
Apr 27 21:41:32 mythtv kernel: [81155.342056] Event timed out
Apr 27 21:41:32 mythtv kernel: [81155.342073] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:41:32 mythtv kernel: [81155.342082] s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)
Apr 27 21:41:32 mythtv kernel: [81155.710305] Event timed out
Apr 27 21:41:32 mythtv kernel: [81155.710319] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:41:32 mythtv kernel: [81155.710327] s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)
Apr 27 21:41:42 mythtv kernel: [81165.340448] Event timed out
Apr 27 21:41:42 mythtv kernel: [81165.340463] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:41:42 mythtv kernel: [81165.340472] s5h1411_writereg: writereg error 0x19 0xf7 0x0001, ret == -5)
Apr 27 21:41:42 mythtv kernel: [81165.710194] Event timed out
Apr 27 21:41:42 mythtv kernel: [81165.710213] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:41:42 mythtv kernel: [81165.710222] s5h1411_writereg: writereg error 0x19 0xf7 0x0001, ret == -5)
Apr 27 21:41:53 mythtv kernel: [81176.340105] Event timed out
Apr 27 21:41:53 mythtv kernel: [81176.340121] saa7164_api_i2c_read() error, ret(1) = 0x32
Apr 27 21:41:53 mythtv kernel: [81176.340130] s5h1411_readreg: readreg error (ret == -5)
Apr 27 21:41:53 mythtv kernel: [81176.710513] Event timed out
Apr 27 21:41:53 mythtv kernel: [81176.710529] saa7164_api_i2c_read() error, ret(1) = 0x32
Apr 27 21:41:53 mythtv kernel: [81176.710537] s5h1411_readreg: readreg error (ret == -5)
Apr 27 21:42:03 mythtv kernel: [81186.340372] Event timed out
Apr 27 21:42:03 mythtv kernel: [81186.340386] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:42:03 mythtv kernel: [81186.340395] s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)
Apr 27 21:42:03 mythtv kernel: [81186.711626] Event timed out
Apr 27 21:42:03 mythtv kernel: [81186.711640] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:42:03 mythtv kernel: [81186.711648] s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)
Apr 27 21:42:13 mythtv kernel: [81196.340041] Event timed out
Apr 27 21:42:13 mythtv kernel: [81196.340055] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:42:13 mythtv kernel: [81196.340063] s5h1411_writereg: writereg error 0x19 0xf7 0x0001, ret == -5)
Apr 27 21:42:13 mythtv kernel: [81196.710070] Event timed out
Apr 27 21:42:13 mythtv kernel: [81196.710093] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:42:13 mythtv kernel: [81196.710103] s5h1411_writereg: writereg error 0x19 0xf7 0x0001, ret == -5)
Apr 27 21:42:23 mythtv kernel: [81206.340063] Event timed out
Apr 27 21:42:23 mythtv kernel: [81206.340080] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:42:23 mythtv kernel: [81206.340089] s5h1411_writereg: writereg error 0x19 0xf5 0x0001, ret == -5)
Apr 27 21:42:23 mythtv kernel: [81206.710074] Event timed out
Apr 27 21:42:23 mythtv kernel: [81206.710088] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:42:23 mythtv kernel: [81206.710096] s5h1411_writereg: writereg error 0x19 0xf5 0x0001, ret == -5)
Apr 27 21:42:33 mythtv kernel: [81216.340215] Event timed out
Apr 27 21:42:33 mythtv kernel: [81216.340231] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:42:33 mythtv kernel: [81216.340240] tda18271_write_regs: ERROR: idx = 0x5, len = 1, i2c_transfer returned: -5
Apr 27 21:42:33 mythtv kernel: [81216.340246] tda18271_init: error -5 on line 826
Apr 27 21:42:33 mythtv kernel: [81216.340257] tda18271_tune: error -5 on line 904
Apr 27 21:42:33 mythtv kernel: [81216.340262] tda18271_set_params: error -5 on line 985
Apr 27 21:42:33 mythtv kernel: [81216.710049] Event timed out
Apr 27 21:42:33 mythtv kernel: [81216.710064] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 21:42:33 mythtv kernel: [81216.710073] tda18271_write_regs: ERROR: idx = 0x5, len = 1, i2c_transfer returned: -5
Apr 27 21:42:33 mythtv kernel: [81216.710079] tda18271_init: error -5 on line 826
Apr 27 21:42:33 mythtv kernel: [81216.710084] tda18271_tune: error -5 on line 904
Apr 27 21:42:33 mythtv kernel: [81216.710089] tda18271_set_params: error -5 on line 985
Apr 27 21:42:43 mythtv kernel: [81226.340399] Event timed out
And here the errors seem to change... (maybe from mythtv trying to start a new recording?)

Apr 27 22:00:57 mythtv kernel: [82320.340090] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 22:00:57 mythtv kernel: [82320.340100] s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)
Apr 27 22:00:57 mythtv kernel: [82320.710355] Event timed out
Apr 27 22:00:57 mythtv kernel: [82320.710370] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 22:00:57 mythtv kernel: [82320.710379] s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)
Apr 27 22:01:07 mythtv kernel: [82330.341284] Event timed out
Apr 27 22:01:07 mythtv kernel: [82330.341299] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 22:01:07 mythtv kernel: [82330.341308] s5h1411_writereg: writereg error 0x19 0xf7 0x0001, ret == -5)
Apr 27 22:01:07 mythtv kernel: [82330.710306] Event timed out
Apr 27 22:01:07 mythtv kernel: [82330.710320] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 22:01:07 mythtv kernel: [82330.710329] s5h1411_writereg: writereg error 0x19 0xf7 0x0001, ret == -5)
Apr 27 22:01:17 mythtv kernel: [82340.341289] Event timed out
Apr 27 22:01:17 mythtv kernel: [82340.341306] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 22:01:17 mythtv kernel: [82340.341315] s5h1411_writereg: writereg error 0x19 0xf5 0x0001, ret == -5)
Apr 27 22:01:17 mythtv kernel: [82340.710117] Event timed out
Apr 27 22:01:17 mythtv kernel: [82340.710131] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 22:01:17 mythtv kernel: [82340.710140] s5h1411_writereg: writereg error 0x19 0xf5 0x0001, ret == -5)
Apr 27 22:01:27 mythtv kernel: [82350.340284] Event timed out
Apr 27 22:01:27 mythtv kernel: [82350.340299] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 22:01:27 mythtv kernel: [82350.340308] tda18271_write_regs: ERROR: idx = 0x5, len = 1, i2c_transfer returned: -5
Apr 27 22:01:27 mythtv kernel: [82350.340315] tda18271_init: error -5 on line 826
Apr 27 22:01:27 mythtv kernel: [82350.340320] tda18271_tune: error -5 on line 904
Apr 27 22:01:27 mythtv kernel: [82350.340325] tda18271_set_params: error -5 on line 985
Apr 27 22:01:27 mythtv kernel: [82350.340344] saa7164_cmd_send() No free sequences
Apr 27 22:01:27 mythtv kernel: [82350.340348] saa7164_api_i2c_write() error, ret(1) = 0xc
Apr 27 22:01:27 mythtv kernel: [82350.340353] s5h1411_writereg: writereg error 0x19 0xf5 0x0000, ret == -5)
Apr 27 22:01:27 mythtv kernel: [82350.340359] saa7164_cmd_send() No free sequences
Apr 27 22:01:27 mythtv kernel: [82350.340363] saa7164_api_i2c_write() error, ret(1) = 0xc
Apr 27 22:01:27 mythtv kernel: [82350.340368] s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)
Apr 27 22:01:27 mythtv kernel: [82350.340373] saa7164_cmd_send() No free sequences
Apr 27 22:01:27 mythtv kernel: [82350.340377] saa7164_api_i2c_write() error, ret(1) = 0xc
Apr 27 22:01:27 mythtv kernel: [82350.340382] s5h1411_writereg: writereg error 0x19 0xf7 0x0001, ret == -5)
Apr 27 22:01:27 mythtv kernel: [82350.710390] Event timed out
Apr 27 22:01:27 mythtv kernel: [82350.710405] saa7164_api_i2c_write() error, ret(1) = 0x32
Apr 27 22:01:27 mythtv kernel: [82350.710414] tda18271_write_regs: ERROR: idx = 0x5, len = 1, i2c_transfer returned: -5
Apr 27 22:01:27 mythtv kernel: [82350.710420] tda18271_init: error -5 on line 826
Apr 27 22:01:27 mythtv kernel: [82350.710425] tda18271_tune: error -5 on line 904
Apr 27 22:01:27 mythtv kernel: [82350.710431] tda18271_set_params: error -5 on line 985
Apr 27 22:01:27 mythtv kernel: [82350.710452] saa7164_cmd_send() No free sequences
Apr 27 22:01:27 mythtv kernel: [82350.710456] saa7164_api_i2c_write() error, ret(1) = 0xc
Apr 27 22:01:27 mythtv kernel: [82350.710462] s5h1411_writereg: writereg error 0x19 0xf5 0x0000, ret == -5)
Apr 27 22:01:27 mythtv kernel: [82350.710468] saa7164_cmd_send() No free sequences
Apr 27 22:01:27 mythtv kernel: [82350.710472] saa7164_api_i2c_write() error, ret(1) = 0xc
Apr 27 22:01:27 mythtv kernel: [82350.710477] s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)
Apr 27 22:01:27 mythtv kernel: [82350.710482] saa7164_cmd_send() No free sequences
Apr 27 22:01:27 mythtv kernel: [82350.710486] saa7164_api_i2c_write() error, ret(1) = 0xc
Apr 27 22:01:27 mythtv kernel: [82350.710490] s5h1411_writereg: writereg error 0x19 0xf7 0x0001, ret == -5)
Apr 27 22:01:28 mythtv kernel: [82351.341094] saa7164_cmd_send() No free sequences
Apr 27 22:01:28 mythtv kernel: [82351.341106] saa7164_api_i2c_read() error, ret(1) = 0xc
Apr 27 22:01:28 mythtv kernel: [82351.341111] s5h1411_readreg: readreg error (ret == -5)
Apr 27 22:01:28 mythtv kernel: [82351.341119] saa7164_cmd_send() No free sequences
Apr 27 22:01:28 mythtv kernel: [82351.341124] saa7164_api_i2c_write() error, ret(1) = 0xc
Apr 27 22:01:28 mythtv kernel: [82351.341130] s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)
Apr 27 22:01:28 mythtv kernel: [82351.341136] saa7164_cmd_send() No free sequences
Apr 27 22:01:28 mythtv kernel: [82351.341139] saa7164_api_i2c_write() error, ret(1) = 0xc

LowSky
May 4th, 2010, 07:15 PM
tjbron do you get these error messages if you turn off OTA scheduling?


dividehex and tjbron are either of you using Power-saving features like suspend? What kind of hardware are you using, especially the Motherboard model? Its a long shot but some motherboards have BIOS enabled power saving modes that might be interfering with this card functioning optimally

Lastly has anyone tried another Linux Distro, like Fedora, Debian KnoppMyth, or Opensuse? Dare I say Arch?

greensoap
May 4th, 2010, 10:36 PM
In the interest of helping to debug things. I mentioned that I was going to disable the OTA guide for each channel and use only Schedules Direct. I did this 6 days ago and I have not had a single error or downtime since. Using the mythweb interface I navigated to http://ipaddress/mythweb/settings/tv/channels and unchecked useonairguide for each individual channel.

I should mention that I am using just the hvr-2250 in my setup, unlike dividehex who is using two cards (the 1650? and 2250, I believe).

Also, like dividehex, I never received the i2c error (to my knowledge) without the entire card crashing.

Dividehex, in regards to the log changing, I believe there is a command buffer that fills up eventually and that is when the "no free sequences" start. I don't think it has anything to do with a channel change or start of recording, just an internal buffer in the driver filling up after all the commands were buffered and not flushed because the commands are trying to execute and are timing out.

greensoap
May 4th, 2010, 10:42 PM
One thing to note with tjbron's log, is that the errors are not occurring in rapid succession. When this happened to me, I received blocks of error messages every ten seconds, which is what can be found in dividehex's log. tjbron's log on the other hand has full minutes inbetween. It seems that his system is "recovering" from the time out and able to reprocess the failed command without the card dying completely.

Lastly, when I got these errors before, the only thing that corrected the issue was a reboot of my computer followed by a restart of myth-tv because for some reason myth-tv tends to start up before the hvr-2250 is initialized.


Hopefully this is helpful to someone. If you scroll down a bit you will start seeing read as well as write errors (i2c). My tuners were still operational during this.
Thanks again.


May 3 17:17:18 bronson-myth kernel: [ 6.509069] lirc_mceusb2[2]: Topseed Technology Corp. eHome Infrared Transceiver on usb2:2
May 3 17:17:18 bronson-myth kernel: [ 6.509120] usbcore: registered new interface driver lirc_mceusb2
May 3 17:17:18 bronson-myth kernel: [ 6.588198] Linux agpgart interface v0.103
May 3 17:17:18 bronson-myth kernel: [ 6.910058] ACPI: I/O resource piix4_smbus [0x400-0x407] conflicts with ACPI region SM00 [0x400-0x407]
May 3 17:17:18 bronson-myth kernel: [ 6.910062] ACPI: Device needs an ACPI driver
May 3 17:17:18 bronson-myth kernel: [ 6.910069] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0x400, revision 0
May 3 17:17:18 bronson-myth kernel: [ 6.932151] ppdev: user-space parallel port driver
May 3 17:17:18 bronson-myth kernel: [ 6.975825] synaptics was reset on resume, see synaptics_resume_reset if you have trouble on resume
May 3 17:17:18 bronson-myth kernel: [ 7.453541] psmouse serio1: ID: 10 00 64<4>nvidia: module license 'NVIDIA' taints kernel.
May 3 17:17:18 bronson-myth kernel: [ 7.893632] nvidia 0000:02:09.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
May 3 17:17:18 bronson-myth kernel: [ 7.899690] NVRM: loading NVIDIA UNIX x86 Kernel Module 173.14.20 Thu Jun 25 19:23:24 PDT 2009
May 3 17:17:18 bronson-myth kernel: [ 7.954185] saa7164 driver loaded
May 3 17:17:18 bronson-myth kernel: [ 7.954313] saa7164 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
May 3 17:17:18 bronson-myth kernel: [ 7.954610] CORE saa7164[0]: dev->lmmio = 0xe0b00000
May 3 17:17:18 bronson-myth kernel: [ 7.954611] CORE saa7164[0]: dev->lmmio2 = 0xe1980000
May 3 17:17:18 bronson-myth kernel: [ 7.954613] CORE saa7164[0]: dev->bmmio = 0xe0b00000
May 3 17:17:18 bronson-myth kernel: [ 7.954615] CORE saa7164[0]: dev->bmmio2 = 0xe1980000
May 3 17:17:18 bronson-myth kernel: [ 7.954617] CORE saa7164[0]: subsystem: 0070:8891, board: Hauppauge WinTV-HVR2250 [card=7,autodetected]
May 3 17:17:18 bronson-myth kernel: [ 7.954623] saa7164[0]/0: found at 0000:01:00.0, rev: 129, irq: 18, latency: 0, mmio: 0xfd800000
May 3 17:17:18 bronson-myth kernel: [ 7.954629] saa7164 0000:01:00.0: setting latency timer to 64
May 3 17:17:18 bronson-myth kernel: [ 8.051033] ATI IXP AC97 controller 0000:00:14.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
May 3 17:17:18 bronson-myth kernel: [ 8.092479] input: ImPS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio1/input/input5
May 3 17:17:18 bronson-myth kernel: [ 8.120026] saa7164_downloadfirmware() no first image
May 3 17:17:18 bronson-myth kernel: [ 8.120038] saa7164_downloadfirmware() Waiting for firmware upload (v4l-saa7164-1.0.3.fw)
May 3 17:17:18 bronson-myth kernel: [ 8.120042] saa7164 0000:01:00.0: firmware: requesting v4l-saa7164-1.0.3.fw
May 3 17:17:18 bronson-myth kernel: [ 10.327185] saa7164_downloadfirmware() firmware read 3978608 bytes.
May 3 17:17:18 bronson-myth kernel: [ 10.327188] saa7164_downloadfirmware() firmware loaded.
May 3 17:17:18 bronson-myth kernel: [ 10.327190] Firmware file header part 1:
May 3 17:17:18 bronson-myth kernel: [ 10.327191] .FirmwareSize = 0x0
May 3 17:17:18 bronson-myth kernel: [ 10.327192] .BSLSize = 0x0
May 3 17:17:18 bronson-myth kernel: [ 10.327194] .Reserved = 0x3cb57
May 3 17:17:18 bronson-myth kernel: [ 10.327195] .Version = 0x3
May 3 17:17:18 bronson-myth kernel: [ 10.327196] saa7164_downloadfirmware() SecBootLoader.FileSize = 3978608
May 3 17:17:18 bronson-myth kernel: [ 10.327202] saa7164_downloadfirmware() FirmwareSize = 0x1fd6
May 3 17:17:18 bronson-myth kernel: [ 10.327204] saa7164_downloadfirmware() BSLSize = 0x0
May 3 17:17:18 bronson-myth kernel: [ 10.327205] saa7164_downloadfirmware() Reserved = 0x0
May 3 17:17:18 bronson-myth kernel: [ 10.327207] saa7164_downloadfirmware() Version = 0x51cc1
May 3 17:17:18 bronson-myth kernel: [ 11.381103] usb-storage: device scan complete
May 3 17:17:18 bronson-myth kernel: [ 11.387089] scsi 4:0:0:0: Direct-Access Generic USB SD Reader 1.00 PQ: 0 ANSI: 0
May 3 17:17:18 bronson-myth kernel: [ 11.393083] scsi 4:0:0:1: Direct-Access Generic USB CF Reader 1.01 PQ: 0 ANSI: 0
May 3 17:17:18 bronson-myth kernel: [ 11.399079] scsi 4:0:0:2: Direct-Access Generic USB SM Reader 1.02 PQ: 0 ANSI: 0
May 3 17:17:18 bronson-myth kernel: [ 11.405078] scsi 4:0:0:3: Direct-Access Generic USB MS Reader 1.03 PQ: 0 ANSI: 0
May 3 17:17:18 bronson-myth kernel: [ 11.415238] sd 4:0:0:0: [sdb] Attached SCSI removable disk
May 3 17:17:18 bronson-myth kernel: [ 11.415340] sd 4:0:0:0: Attached scsi generic sg2 type 0
May 3 17:17:18 bronson-myth kernel: [ 11.427182] sd 4:0:0:1: [sdc] Attached SCSI removable disk
May 3 17:17:18 bronson-myth kernel: [ 11.427292] sd 4:0:0:1: Attached scsi generic sg3 type 0
May 3 17:17:18 bronson-myth kernel: [ 11.436271] sd 4:0:0:2: [sdd] Attached SCSI removable disk
May 3 17:17:18 bronson-myth kernel: [ 11.436396] sd 4:0:0:2: Attached scsi generic sg4 type 0
May 3 17:17:18 bronson-myth kernel: [ 11.456241] sd 4:0:0:3: [sde] Attached SCSI removable disk
May 3 17:17:18 bronson-myth kernel: [ 11.456344] sd 4:0:0:3: Attached scsi generic sg5 type 0
May 3 17:17:18 bronson-myth kernel: [ 17.184026] saa7164_downloadimage() Image downloaded, booting...
May 3 17:17:18 bronson-myth kernel: [ 17.288017] saa7164_downloadimage() Image booted successfully.
May 3 17:17:18 bronson-myth kernel: [ 17.288041] starting firmware download(2)
May 3 17:17:18 bronson-myth kernel: [ 19.412025] saa7164_downloadimage() Image downloaded, booting...
May 3 17:17:18 bronson-myth kernel: [ 21.076021] saa7164_downloadimage() Image booted successfully.
May 3 17:17:18 bronson-myth kernel: [ 21.076042] firmware download complete.
May 3 17:17:18 bronson-myth kernel: [ 21.076999] saa7164[0]: i2c bus 0 registered
May 3 17:17:18 bronson-myth kernel: [ 21.077080] saa7164[0]: i2c bus 1 registered
May 3 17:17:18 bronson-myth kernel: [ 21.077160] saa7164[0]: i2c bus 2 registered
May 3 17:17:18 bronson-myth kernel: [ 21.112265] tveeprom 1-0000: Hauppauge model 88061, rev C3F2, serial# 6225133
May 3 17:17:18 bronson-myth kernel: [ 21.112268] tveeprom 1-0000: MAC address is 00-0D-FE-5E-FC-ED
May 3 17:17:18 bronson-myth kernel: [ 21.112270] tveeprom 1-0000: tuner model is NXP 18271C2_716x (idx 152, type 4)
May 3 17:17:18 bronson-myth kernel: [ 21.112272] tveeprom 1-0000: TV standards NTSC(M) ATSC/DVB Digital (eeprom 0x88)
May 3 17:17:18 bronson-myth kernel: [ 21.112274] tveeprom 1-0000: audio processor is SAA7164 (idx 43)
May 3 17:17:18 bronson-myth kernel: [ 21.112276] tveeprom 1-0000: decoder processor is SAA7164 (idx 40)
May 3 17:17:18 bronson-myth kernel: [ 21.112278] tveeprom 1-0000: has radio, has IR receiver, has no IR transmitter
May 3 17:17:18 bronson-myth kernel: [ 21.112280] saa7164[0]: Hauppauge eeprom: model=88061
May 3 17:17:18 bronson-myth kernel: [ 21.505221] tda18271 2-0060: creating new instance
May 3 17:17:18 bronson-myth kernel: [ 21.509576] TDA18271HD/C2 detected @ 2-0060
May 3 17:17:18 bronson-myth kernel: [ 21.760963] DVB: registering new adapter (saa7164)
May 3 17:17:18 bronson-myth kernel: [ 21.760970] DVB: registering adapter 0 frontend 611647248 (Samsung S5H1411 QAM/8VSB Frontend)...
May 3 17:17:18 bronson-myth kernel: [ 22.045258] tda18271 3-0060: creating new instance
May 3 17:17:18 bronson-myth kernel: [ 22.049734] TDA18271HD/C2 detected @ 3-0060
May 3 17:17:18 bronson-myth kernel: [ 22.300741] DVB: registering new adapter (saa7164)
May 3 17:17:18 bronson-myth kernel: [ 22.300748] DVB: registering adapter 1 frontend 0 (Samsung S5H1411 QAM/8VSB Frontend)...
May 3 17:17:18 bronson-myth kernel: [ 22.401630] lp0: using parport0 (interrupt-driven).
May 3 17:17:18 bronson-myth kernel: [ 22.608972] Adding 2385644k swap on /dev/sda4. Priority:-1 extents:1 across:2385644k
May 3 17:17:18 bronson-myth kernel: [ 23.239565] EXT3 FS on sda2, internal journal
May 3 17:17:18 bronson-myth kernel: [ 24.129254] kjournald starting. Commit interval 5 seconds
May 3 17:17:18 bronson-myth kernel: [ 24.129525] EXT3 FS on sda3, internal journal
May 3 17:17:18 bronson-myth kernel: [ 24.129530] EXT3-fs: mounted filesystem with ordered data mode.
May 3 17:17:18 bronson-myth kernel: [ 24.602595] type=1505 audit(1272932236.482:2): operation="profile_load" name="/sbin/dhclient-script" name2="default" pid=1996
May 3 17:17:18 bronson-myth kernel: [ 24.602743] type=1505 audit(1272932236.482:3): operation="profile_load" name="/sbin/dhclient3" name2="default" pid=1996
May 3 17:17:18 bronson-myth kernel: [ 24.602788] type=1505 audit(1272932236.482:4): operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-client.action" name2="default" pid=1996
May 3 17:17:18 bronson-myth kernel: [ 24.602830] type=1505 audit(1272932236.482:5): operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" name2="default" pid=1996
May 3 17:17:18 bronson-myth kernel: [ 24.747091] type=1505 audit(1272932236.626:6): operation="profile_load" name="/usr/lib/cups/backend/cups-pdf" name2="default" pid=2001
May 3 17:17:18 bronson-myth kernel: [ 24.747296] type=1505 audit(1272932236.626:7): operation="profile_load" name="/usr/sbin/cupsd" name2="default" pid=2001
May 3 17:17:18 bronson-myth kernel: [ 24.774153] type=1505 audit(1272932236.654:8): operation="profile_load" name="/usr/sbin/mysqld" name2="default" pid=2005
May 3 17:17:18 bronson-myth kernel: [ 24.800814] type=1505 audit(1272932236.682:9): operation="profile_load" name="/usr/sbin/tcpdump" name2="default" pid=2009
May 3 17:17:18 bronson-myth kernel: [ 26.809399] slamr: SmartLink AMRMO modem.
May 3 17:17:18 bronson-myth kernel: [ 26.809416] slamr: device 1057:3052 is grabbed by another driver
May 3 17:17:28 bronson-myth kernel: [ 36.396796] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
May 3 17:17:28 bronson-myth kernel: [ 36.396799] Bluetooth: BNEP filters: protocol multicast
May 3 17:17:28 bronson-myth kernel: [ 36.418773] Bridge firewalling registered
May 3 17:17:29 bronson-myth kernel: [ 37.296571] tda18271: performing RF tracking filter calibration
May 3 17:17:32 bronson-myth kernel: [ 40.501767] tda18271: RF tracking filter calibration complete
May 3 17:17:34 bronson-myth kernel: [ 42.118249] eth0: link down
May 3 17:17:34 bronson-myth kernel: [ 42.118358] ADDRCONF(NETDEV_UP): eth0: link is not ready
May 3 17:17:34 bronson-myth kernel: [ 42.164020] Event timed out
May 3 17:17:34 bronson-myth kernel: [ 42.164026] saa7164_api_i2c_write() error, ret(1) = 0x32
May 3 17:17:34 bronson-myth kernel: [ 42.164030] s5h1411_writereg: writereg error 0x19 0x3e 0x77ee, ret == -5)
May 3 17:17:34 bronson-myth kernel: [ 42.164455] found timed out command on the bus
May 3 17:17:34 bronson-myth kernel: [ 42.164483] ret = 0
May 3 17:17:34 bronson-myth kernel: [ 42.164484] timeout continue
May 3 17:17:34 bronson-myth kernel: [ 42.465264] tda18271: performing RF tracking filter calibration
May 3 17:17:36 bronson-myth kernel: [ 44.921844] tda18271: RF tracking filter calibration complete
May 3 17:18:37 bronson-myth kernel: [ 105.992203] Clocksource tsc unstable (delta = -272837835 ns)
May 3 17:44:11 bronson-myth kernel: [ 1639.164030] Event timed out
May 3 17:44:11 bronson-myth kernel: [ 1639.164039] saa7164_api_i2c_read() error, ret(1) = 0x32
May 3 17:44:11 bronson-myth kernel: [ 1639.164045] s5h1411_readreg: readreg error (ret == -5)
May 3 17:44:11 bronson-myth kernel: [ 1639.164495] found timed out command on the bus
May 3 17:44:11 bronson-myth kernel: [ 1639.164525] ret = 0
May 3 17:44:11 bronson-myth kernel: [ 1639.164528] timeout continue
May 3 17:45:17 bronson-myth kernel: [ 1705.736028] Event timed out
May 3 17:45:17 bronson-myth kernel: [ 1705.736037] saa7164_api_i2c_write() error, ret(2) = 0x32
May 3 17:45:17 bronson-myth kernel: [ 1705.736044] s5h1411_writereg: writereg error 0x19 0xf5 0x0000, ret == -5)
May 3 17:45:17 bronson-myth kernel: [ 1705.736455] found timed out command on the bus
May 3 17:45:17 bronson-myth kernel: [ 1705.736688] ret = 0
May 3 17:45:17 bronson-myth kernel: [ 1705.736690] timeout continue
May 3 17:55:51 bronson-myth kernel: [ 2339.784037] Event timed out
May 3 17:55:51 bronson-myth kernel: [ 2339.784047] saa7164_api_i2c_read() error, ret(2) = 0x32
May 3 17:55:51 bronson-myth kernel: [ 2339.784053] s5h1411_readreg: readreg error (ret == -5)
May 3 17:55:51 bronson-myth kernel: [ 2339.784467] found timed out command on the bus
May 3 17:55:51 bronson-myth kernel: [ 2339.784699] ret = 0
May 3 17:55:51 bronson-myth kernel: [ 2339.784702] timeout continue
May 3 17:59:16 bronson-myth kernel: [ 2544.568034] Event timed out
May 3 17:59:16 bronson-myth kernel: [ 2544.568044] saa7164_api_i2c_read() error, ret(2) = 0x32
May 3 17:59:16 bronson-myth kernel: [ 2544.568050] s5h1411_readreg: readreg error (ret == -5)
May 3 17:59:16 bronson-myth kernel: [ 2544.568495] found timed out command on the bus
May 3 17:59:16 bronson-myth kernel: [ 2544.568727] ret = 0
May 3 17:59:16 bronson-myth kernel: [ 2544.568730] timeout continue
May 3 18:12:36 bronson-myth kernel: [ 3344.956059] Event timed out
May 3 18:12:36 bronson-myth kernel: [ 3344.956069] saa7164_api_i2c_read() error, ret(2) = 0x32
May 3 18:12:36 bronson-myth kernel: [ 3344.956076] tda18271_read_regs: ERROR: i2c_transfer returned: -5
May 3 18:12:36 bronson-myth kernel: [ 3344.957163] found timed out command on the bus
May 3 18:12:36 bronson-myth kernel: [ 3344.957303] ret = 0
May 3 18:12:36 bronson-myth kernel: [ 3344.957306] timeout continue
May 3 18:24:17 bronson-myth kernel: [ 4045.536032] Event timed out
May 3 18:24:17 bronson-myth kernel: [ 4045.536042] saa7164_api_i2c_read() error, ret(2) = 0x32
May 3 18:24:17 bronson-myth kernel: [ 4045.536047] s5h1411_readreg: readreg error (ret == -5)
May 3 18:24:17 bronson-myth kernel: [ 4045.536759] found timed out command on the bus
May 3 18:24:17 bronson-myth kernel: [ 4045.536993] ret = 0
May 3 18:24:17 bronson-myth kernel: [ 4045.536996] timeout continue
May 3 18:44:00 bronson-myth kernel: [ 5228.964038] Event timed out
May 3 18:44:00 bronson-myth kernel: [ 5228.964048] saa7164_api_i2c_read() error, ret(1) = 0x32
May 3 18:44:00 bronson-myth kernel: [ 5228.964054] s5h1411_readreg: readreg error (ret == -5)
May 3 18:44:00 bronson-myth kernel: [ 5228.964489] found timed out command on the bus
May 3 18:44:00 bronson-myth kernel: [ 5228.964523] ret = 0
May 3 18:44:00 bronson-myth kernel: [ 5228.964525] timeout continue
May 3 19:39:28 bronson-myth kernel: [ 8556.524030] Event timed out
May 3 19:39:28 bronson-myth kernel: [ 8556.524040] saa7164_api_i2c_read() error, ret(2) = 0x32
May 3 19:39:28 bronson-myth kernel: [ 8556.524047] s5h1411_readreg: readreg error (ret == -5)
May 3 19:39:28 bronson-myth kernel: [ 8556.524526] found timed out command on the bus
May 3 19:39:28 bronson-myth kernel: [ 8556.524659] ret = 0
May 3 19:39:28 bronson-myth kernel: [ 8556.524662] timeout continue
May 3 19:40:30 bronson-myth kernel: [ 8618.240030] Event timed out
May 3 19:40:30 bronson-myth kernel: [ 8618.240040] saa7164_api_i2c_read() error, ret(2) = 0x32
May 3 19:40:30 bronson-myth kernel: [ 8618.240046] s5h1411_readreg: readreg error (ret == -5)
May 3 19:40:30 bronson-myth kernel: [ 8618.240515] found timed out command on the bus
May 3 19:40:30 bronson-myth kernel: [ 8618.240648] ret = 0
May 3 19:40:30 bronson-myth kernel: [ 8618.240651] timeout continue
May 3 19:40:31 bronson-myth kernel: [ 8619.404030] Event timed out
May 3 19:40:31 bronson-myth kernel: [ 8619.404039] saa7164_api_i2c_write() error, ret(2) = 0x32
May 3 19:40:31 bronson-myth kernel: [ 8619.404046] tda18271_write_regs: ERROR: i2c_transfer returned: -5
May 3 19:40:31 bronson-myth kernel: [ 8619.404838] found timed out command on the bus
May 3 19:40:31 bronson-myth kernel: [ 8619.404972] ret = 0
May 3 19:40:31 bronson-myth kernel: [ 8619.404974] timeout continue

dividehex
May 5th, 2010, 04:45 AM
dividehex and tjbron are either of you using Power-saving features like suspend? What kind of hardware are you using, especially the Motherboard model? Its a long shot but some motherboards have BIOS enabled power saving modes that might be interfering with this card functioning optimally No, I do not use any powersaving feature except for a black screen saver. The motherboard I am using is Asus M3N78-EM.


Lastly has anyone tried another Linux Distro, like Fedora, Debian KnoppMyth, or Opensuse? Dare I say Arch? Nope. And I don't think I am that adventurous.


I should mention that I am using just the hvr-2250 in my setup, unlike dividehex who is using two cards (the 1650? and 2250, I believe).I am not using any other card. Just a hvr-2250. The only thing I have done differently is configure one tuner in mythtv and not the other (hvr-2250 has 2 tuners). Since doing this, I have not had any i2c errors and the system is completely stable. The obvious downside is that I can only record one thing at a time.


Dividehex, in regards to the log changing, I believe there is a command buffer that fills up eventually and that is when the "no free sequences" start. I don't think it has anything to do with a channel change or start of recording, just an internal buffer in the driver filling up after all the commands were buffered and not flushed because the commands are trying to execute and are timing out. And this is why I believe the issue lies in the driver or the combination of the driver and mythtv.

jjwest85
May 6th, 2010, 12:06 AM
I hate to change the subject to something else with such productive talk on this error is occuring. I wanted to bring up LowSky's sound problem one more time. I also have my computer connected to an HDTV. I have an nVidia card as opposed to an ATI graphics card.

For anyone with an nVidia card and not able to get sound to go through their HDMI cable and does not even show HDMI or digital as an option in sound preferences this may be able to help:

1. Add "ppa:ubuntu-audio-dev/ppa" to the repository in synaptic. Refresh synaptic.

2. Upgrade all the pulse-audio packages

3. find out your kernel version: type "uname -r" in a terminal. Mine came out to be 2.6.32-21-generic (default ubuntu 10.04).

4. install "linux-alsa-driver-modules-2.6.32-21-generic" (your kernel may be different).

I got this package from a launchpad bug that listed it as a possible fix to the dreaded sound through HDMI cables problem. Installing this package gave me the options in sound preferences to choose digital sound/HDMI (IEC958 ). I'm not 100% sure that being able to see IEC958 in sound preferences came right after updating all pulse-audio packages or if it only came after installing this package.

I did also have to change some sound setting on MythTV's frontend. Go to Utilities/Setup -> General -> Audio system -> Audio output device -> change to ALSA:spdif

Let me know if anyone else had/has this problem

dividehex
May 6th, 2010, 04:49 PM
Just to wrap up the i2c error, I email Steve and got a prompt reply stating that he was aware of the issues and believes they are localized to AMD systems. He also indicated he will be looking in to the problem. So sit tight everyone and I will post an update when I get any new information. :-D

LowSky
May 6th, 2010, 06:55 PM
jjwest85 - I'm going to include what you mentioned in my tutorial. Thanks for the info, it will help people out


dividehex -- AMD systems? My system is AMD based and working fine with 9.10 but not 10.04. I can see this being a driver issue, but I can't test it without buying an Intel processor and motherboard. donations are wlecomed. LOL. Its probably a problem on how the motherboard's driver communicates PCI channels.

jjwest85
May 6th, 2010, 10:57 PM
LowSky - thanks for adding my info. In case people wanted to know my specific graphics card it is an nVidia 9800 gtx+ from Asus.

As for the i2c error. My system is running on an i5 Intel processor. I did "tail kern.log" and found out I also have this i2c error. See below. (my system has been up and running for 3 days at this point)



May 6 16:36:22 maximus2 kernel: [336613.205470] s5h1411_readreg: readreg error (ret == -5)
May 6 16:36:22 maximus2 kernel: [336613.205475] saa7164_cmd_send() No free sequences
May 6 16:36:22 maximus2 kernel: [336613.205478] saa7164_api_i2c_read() error, ret(1) = 0xc
May 6 16:36:22 maximus2 kernel: [336613.205481] s5h1411_readreg: readreg error (ret == -5)
May 6 16:36:22 maximus2 kernel: [336613.205486] saa7164_cmd_send() No free sequences
May 6 16:36:22 maximus2 kernel: [336613.205488] saa7164_api_i2c_read() error, ret(1) = 0xc
May 6 16:36:22 maximus2 kernel: [336613.205491] s5h1411_readreg: readreg error (ret == -5)
May 6 16:36:22 maximus2 kernel: [336613.205496] saa7164_cmd_send() No free sequences
May 6 16:36:22 maximus2 kernel: [336613.205498] saa7164_api_i2c_read() error, ret(1) = 0xc
May 6 16:36:22 maximus2 kernel: [336613.205501] s5h1411_readreg: readreg error (ret == -5)
I also noticed that my kern.log file is 18Gb. When I went to Mythtv Frontend -> Information Center -> System Status, I also noticed that my RAM only had 1% of the 3.9Gb free. When I tried to watch live TV, I did not get any error and it looked like it would have worked if I had some free space. It only gave me a black screen with the channel identification pop-up on screen, but would not lock onto a channel. Restarting my computer and then MythTV backend did let me watch live TV again.

LowSky
May 6th, 2010, 11:31 PM
I did some digging I havent read all of it but it seems Austrailia has has similar issues with the HVR-2200
http://www.xpmediacentre.com.au/community/linux-general-setup-support-discussion/38038-hvr-2200-install-issues.html
http://www.kernellabs.com/blog/?p=676

sidesh0w
May 7th, 2010, 12:27 AM
Greetings from Australia :)

I have this tuner running on mythbuntu 9.10 and manually compiled drivers - works perfect.

I heard 10.04 has native drivers which would be great as everytime I update my kernel at the moment I have to re-compile the tuner drivers to get tv working again.

Can anyone confirm that 10.04 works out of the box with this tuner? Any guides out there?

Thanks for any info

LowSky
May 7th, 2010, 12:47 AM
Greetings from Australia :)

I have this tuner running on mythbuntu 9.10 and manually compiled drivers - works perfect.

I heard 10.04 has native drivers which would be great as everytime I update my kernel at the moment I have to re-compile the tuner drivers to get tv working again.

Can anyone confirm that 10.04 works out of the box with this tuner? Any guides out there?

Thanks for any info

Page 1 with my original tutorial has been updated with the new instructions with the link at the top. Yes the driver is in the kernel, but me and a few others are experiencing issues while recording tv. Read the last few pages here for more info. The issue is more than likely with mythtv because the newest version of Ubuntu uses an development version of mythtv. This weekend I'm thinking of installing another distro and using the stable version of mythtv to try and find more info on what's effected.

greensoap
May 7th, 2010, 02:20 AM
Just to wrap up the i2c error, I email Steve and got a prompt reply stating that he was aware of the issues and believes they are localized to AMD systems. He also indicated he will be looking in to the problem. So sit tight everyone and I will post an update when I get any new information. :-D


Just to mention, I am running an Intel CPU, not an AMD, and an ATI Radeon X1600.


*-cpu
product: Intel(R) Pentium(R) D CPU 3.00GHz
vendor: Intel Corp.
physical id: 1
bus info: cpu@0
version: 15.6.2
size: 3GHz
width: 64 bits
capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx x86-64 constant_tsc
pebs bts pni dtes64 monitor ds_cpl vmx cid cx16 xtpr pdcm lahf_lm tpr_shadow
configuration: id=0
*-logicalcpu:0
description: Logical CPU
physical id: 0.1
width: 64 bits
capabilities: logical
*-logicalcpu:1
description: Logical CPU
physical id: 0.2
width: 64 bits
capabilities: logical

sidesh0w
May 7th, 2010, 02:42 AM
Page 1 with my original tutorial has been updated with the new instructions with the link at the top. Yes the driver is in the kernel, but me and a few others are experiencing issues while recording tv. Read the last few pages here for more info. The issue is more than likely with mythtv because the newest version of Ubuntu uses an development version of mythtv. This weekend I'm thinking of installing another distro and using the stable version of mythtv to try and find more info on what's effected.

Found it, thanks for that.

Looks really detailed and I am also on HDMI video / sound.

Think I will try an upgrade and keep my recordings and if I fail miserably ill do a clean.

Thanks again!

tjbron
May 7th, 2010, 04:23 PM
As for the i2c error. My system is running on an i5 Intel processor. I did "tail kern.log" and found out I also have this i2c error. See below. (my system has been up and running for 3 days at this point)
I also noticed that my kern.log file is 18Gb. When I went to Mythtv Frontend -> Information Center -> System Status, I also noticed that my RAM only had 1% of the 3.9Gb free. When I tried to watch live TV, I did not get any error and it looked like it would have worked if I had some free space. It only gave me a black screen with the channel identification pop-up on screen, but would not lock onto a channel. Restarting my computer and then MythTV backend did let me watch live TV again.

Yep, those are the exact symptoms. Also, you will notice that any show that it tried to record will have a zero file size.

My i2c error "alarm" is now a joke at my house because it beeps every half hour even if the system is working :) (I get those errors randomly even while things are working). FWIW, I have an AMD system, but it looks like jjwest85 has Intel.

Also, I spoke with a guy I work with and he has no problems with the 2250 on an AMD system, but he is running LINHES, not Ubuntu.

Hwy120
May 8th, 2010, 08:46 PM
[QUOTE=LowSky;9219191]Ok so Here's the Tutorial for using 10.04.

[code]hg clone http://kernellabs.com/hg/saa7164-stable/

LowSky, if I do the instructions listed above on my system, that has had drivers installed before, I get the following error:
abort: destination 'saa7164-stable' is not empty

I then need to:
rm -r saa7146-stable
this will remove the directory and allow me to continue.

I do not know if this is just my system, but it may be something to add to your very helpful instructions for those of us who are new to Linux.

LowSky
May 8th, 2010, 10:44 PM
Hwy120, If you have the drivers installed before, why whould you re-add them?

I want to bring up that this forum is not very keen on the use of rm codes. Due to how easily they can brick a system if one is not careful.

It is easier to ask a person to delete the folder in question through using the GUI, by going into nautilus and deleting the folder that way.

If you wish to update the drivers there is another option:


cd saa7164-stable
hg pull -u http://kernellabs.com/hg/saa7164-stable/

dividehex
May 8th, 2010, 10:53 PM
I just got an email from Steve and he has made some changes to the saa-7164 stable tree. I'm going to compile and test it now.

xinix
May 9th, 2010, 07:47 AM
Having just upgraded to 10.4, I'm curious about the i2c problem some folk have been having. Is this an error that appears in the log right away or does the system work perfectly with no errors and then seemingly randomly starts filling the log with the message? I've been using a fresh install without compiling the driver and have not seen this error (yet).
I'd like to try to reproduce the channel change crash that has been mentioned as well. I don't watch much live tv but a quick run through the channels worked for me.

LowSky
May 9th, 2010, 03:54 PM
Having just upgraded to 10.4, I'm curious about the i2c problem some folk have been having. Is this an error that appears in the log right away or does the system work perfectly with no errors and then seemingly randomly starts filling the log with the message? I've been using a fresh install without compiling the driver and have not seen this error (yet).
I'd like to try to reproduce the channel change crash that has been mentioned as well. I don't watch much live tv but a quick run through the channels worked for me.

Its an odd error from what I'm told. Some people get a warning ever 1/2 hour, even with the card working fine, some go days between error log filling up until it cripples the system.

As for the channel change error, but I can confirm it happening to me. I have little knowledge of it as I reinstalled 9.10 to quickly get a working system again.

I compiled the new update for the driver last night and with 9.10 it seems to run great. No issues at all. Hopefully the same for 10.04

xinix
May 10th, 2010, 01:44 AM
So I started to encounter problems with 10.4. Now that I've reverted to 9.10 I cannot get the firmware to load with the new drivers. It complains that it cannot find the right file. Did the firmware change?

tjbron
May 10th, 2010, 04:34 PM
Its an odd error from what I'm told. Some people get a warning ever 1/2 hour, even with the card working fine, some go days between error log filling up until it cripples the system.

I compiled the new update for the driver last night and with 9.10 it seems to run great. No issues at all. Hopefully the same for 10.04

Sorry for the confusion, I have a script that watches the log every 30 minutes for the i2c error. That's where the 1/2 hour comes from. The log seems to be clear for a few hours, then starts logging the error every few minutes randomly (maybe tied to updating the OTA schedule or other usage of the box). Then sometimes it goes full-on logfile loading with a crashed tuner.

Also, that's great news on the driver update! Thanks for contacting Steve Toth about it. Please keep us updated on your uptime and if the problems appear to stay fixed.

dividehex
May 10th, 2010, 04:54 PM
Also, that's great news on the driver update! Thanks for contacting Steve Toth about it. Please keep us updated on your uptime and if the problems appear to stay fixed.I really don't want to jump the gun here and declare the issue fixed just yet, but I will say that my uptime right now is 41 hours and that is pretty good for my system considering it's uptime history. I really hope other people with the i2c errors will update their driver (http://www.kernellabs.com/hg/saa7164-stable/) and report back here.

dividehex
May 10th, 2010, 05:12 PM
So I started to encounter problems with 10.4. Now that I've reverted to 9.10 I cannot get the firmware to load with the new drivers. It complains that it cannot find the right file. Did the firmware change?

If you upgrade to 10.04 and want to use the stock driver, you will probably need to install a new firmware in /lib/firmware



wget http://www.steventoth.net/linux/hvr22xx/firmwares/3978608/v4l-saa7164-1.0.3.fw
sudo cp v4l-saa7164-1.0.3.fw /lib/firmware
If you compile the the new driver directly from the repository then you will need this firmware


wget http://www.steventoth.net/linux/hvr22xx/firmwares/4038864/v4l-saa7164-1.0.3-3.fw
sudo cp v4l-saa7164-1.0.3-3.fw /lib/firmware

tjbron
May 10th, 2010, 05:30 PM
I really don't want to jump the gun here and declare the issue fixed just yet, but I will say that my uptime right now is 41 hours and that is pretty good for my system considering it's uptime history. I really hope other people with the i2c errors will update their driver (http://www.kernellabs.com/hg/saa7164-stable/) and report back here.


I'd love to try the new driver. Do I have to follow LowSky's original how-to again, or is there a way to update the driver more directly? I am running 9.04.

Thanks!

dividehex
May 10th, 2010, 06:09 PM
I'd love to try the new driver. Do I have to follow LowSky's original how-to again, or is there a way to update the driver more directly? I am running 9.04.

Thanks!

Follow LowSky's how-to. It is as direct as you can get. ;-)

tjbron
May 10th, 2010, 06:38 PM
Follow LowSky's how-to. It is as direct as you can get. ;-)

:oops: It is a great how-to, I just meant I didn't know if there was an "update" procedure, or if I just needed to start over, delete some things, etc.
Seems like last time I had to uninstall MythTV before doing the LowSky how-to. Sorry, still a newb. :confused:

dividehex
May 10th, 2010, 10:45 PM
:oops: It is a great how-to, I just meant I didn't know if there was an "update" procedure, or if I just needed to start over, delete some things, etc.
Seems like last time I had to uninstall MythTV before doing the LowSky how-to. Sorry, still a newb. :confused:
That's no problem. You have to start somewhere. :P If you have followed LowSky instructions already and already have the driver working, you can update it by running a portion of the instructions.

NOTE: See here for LowSky's entire how-to: http://ubuntuforums.org/showpost.php?p=9219191&postcount=212

This downloads the lastest source code from the authors website

hg clone http://kernellabs.com/hg/saa7164-stable/Change directory

cd saa7164-stableThis compiles and links the source

make CONFIG_DVB_FIREDTV:=nThis will install the newly compiled driver to the OS

sudo make installNow reboot so the new driver will load

sudo rebootAfter the reboot, check to see if the driver is finding the firmware properly.

dmesg | grep saa7164_downloadfirmwareIf the output looks like this, then the driver loaded the firmware properly and your done.

saa7164_downloadfirmware() no first image
saa7164_downloadfirmware() Waiting for firmware upload (v4l-saa7164-1.0.3-3.fw)
saa7164_downloadfirmware() firmware read 4038864 bytes.
saa7164_downloadfirmware() firmware loaded.
saa7164_downloadfirmware() SecBootLoader.FileSize = 4038864
saa7164_downloadfirmware() FirmwareSize = 0x1fd6
saa7164_downloadfirmware() BSLSize = 0x0
saa7164_downloadfirmware() Reserved = 0x0
saa7164_downloadfirmware() Version = 0x1d1cOtherwise, if the output looks like this, then you will need to install the firmware

saa7164_downloadfirmware() no first image
saa7164_downloadfirmware() Waiting for firmware upload (v4l-saa7164-1.0.3-3.fw)
saa7164_downloadfirmware() Upload failed. (file not found?)Download the extracted firmware

wget http://www.steventoth.net/linux/hvr22xx/firmwares/4038864/v4l-saa7164-1.0.3-3.fw Copy the firmware to /lib/firmware

sudo cp v4l-saa7164-1.0.3-3.fw /lib/firmware
Reboot once more

sudo reboot
Hope this is more informative and helpful.

Hwy120
May 11th, 2010, 12:34 PM
Hwy120, If you have the drivers installed before, why whould you re-add them?

The reason I would reinstall the drivers is that after each kernel update was that it seemed to be the only way I could get the 2250 working again. If I skipped any steps I had errors and no video capture card.



I want to bring up that this forum is not very keen on the use of rm codes. Due to how easily they can brick a system if one is not careful.

It is easier to ask a person to delete the folder in question through using the GUI, by going into nautilus and deleting the folder that way.I am still learning, but I do not see nautilus as a choice under any of the Gnome menus.


If you wish to update the drivers there is another option:


cd saa7164-stable
hg pull -u http://kernellabs.com/hg/saa7164-stable/Thank you for the update driver information.