All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Bauer <ebauer71@centurytel.net>
To: Andy Walls <awalls@radix.net>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Problem Searching Channels
Date: Sun, 04 Jan 2009 14:44:41 -0600	[thread overview]
Message-ID: <49611FB9.2080409@centurytel.net> (raw)
In-Reply-To: <1231091162.3125.6.camel@palomino.walls.org>


[-- Attachment #1.1: Type: text/plain, Size: 4716 bytes --]

Hello Andy,

Thanks for the reply.  I am really stuck on this.  I am using Fedora8, 
so I did a yum install of the latest dvb-tools application, but I'm not 
sure which version it is.  I am executing this command:

$ scandvb 
/usr/share/dvb-apps/atsc/us-Cable-Standard-center-frequencies-QAM256

On your advice, I checked as discovered that I was running verison 1.0.0 
of the cx18 drive.  I downloaded the latest cx18 driver and installed 
it.  After running the modprobe as instructed, scandvb could no longer 
find the device in the /dev directory.  After rebooting, scandvb worked 
again and modinfo reports that I am running version 1.0.4 of cx18.  
Unfortunately, after several minutes of scanning, the same thing is 
happening.  The scan will not complete.

I don't know if this is important or not.  I tried scanning using a 
couple other firequency files.  us-Cable-IRC-center-frequencies-QAM256 
does the same thing, but us-Cable-HRC-center-frequencies-QAM256
 completes without error, it just does not find any channels. 

I found some interesting stuff in the dmesg output.  I have a Happaugue 
HVR-1600 model 1178, but tveeprom is reporting that it is model 74041.  
Seems like this might explain where my problem is coming from, but I 
don't know how to fix it.  Here is the dmesg output:

/cx18:  Start initialization, version 1.0.4
cx18-0: Initializing card #0
cx18-0: Autodetected Hauppauge card
ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 21 (level, low) -> IRQ 21
cx18-0: Unreasonably low latency timer, setting to 64 (was 32)
cx18-0: cx23418 revision 01010000 (B)
tveeprom 1-0050: Hauppauge model 74041, rev C5B2, serial# 2884991
tveeprom 1-0050: MAC address is 00-0D-FE-2C-05-7F
tveeprom 1-0050: tuner model is TCL M2523_5N_E (idx 112, type 50)
tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 1-0050: audio processor is CX23418 (idx 38)
tveeprom 1-0050: decoder processor is CX23418 (idx 31)
tveeprom 1-0050: has no radio, has IR receiver, has IR transmitter
cx18-0: Autodetected Hauppauge HVR-1600
cx18-0: Raw VBI supported; Sliced VBI is not yet supported
firewire_core: created device fw0: GUID 0090270001f82fe5, S400
tuner 2-0061: chip found @ 0xc2 (cx18 i2c driver #0-1)
cs5345 1-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
tuner-simple 2-0061: creating new instance
tuner-simple 2-0061: type set to 50 (TCL 2002N)
cx18-0: Registered device video0 for encoder MPEG (64 x 32 kB)
DVB: registering new adapter (cx18)
MXL5005S: Attached at address 0x63
DVB: registering adapter 0 frontend 3332 (Samsung S5H1409 QAM/8VSB 
Frontend)...
cx18-0: DVB Frontend registered
cx18-0: Registered DVB adapter0 for TS (32 x 32 kB)
cx18-0: Registered device video32 for encoder YUV (16 x 128 kB)
cx18-0: Registered device vbi0 for encoder VBI (60 x 17328 bytes)
cx18-0: Registered device video24 for encoder PCM audio (256 x 4 kB)
cx18-0: Initialized card #0: Hauppauge HVR-1600
cx18:  End initialization
/
And the a little further down...

f/irmware: requesting v4l-cx23418-cpu.fw
cx18-0: Unable to open firmware v4l-cx23418-cpu.fw
cx18-0: Did you put the firmware in the hotplug firmware directory?
cx18-0: Retry loading firmware
firmware: requesting v4l-cx23418-cpu.fw
cx18-0: Unable to open firmware v4l-cx23418-cpu.fw
cx18-0: Did you put the firmware in the hotplug firmware directory?
cx18-0: Failed to initialize firmware starting DVB feed
cx18-0: Failed to initialize firmware starting DVB feed
Press any key to continue.../


Any thoughts about this?

Thanks,

Eric


Andy Walls wrote:
> On Sun, 2009-01-04 at 09:28 -0600, Eric Bauer wrote:
>   
>> Hello,
>>
>> I'm trying to set up my new Happaugue HVR-1600 card.  During the scan, 
>> II get several minutes of output on the screen complaining about tuning 
>> failures,
>>     
>
> These are normal when no service is detected on those freqs.
>
>
>   
>>  and then I get the following message:
>>
>> start filter:1338: ERROR: ioctl DMX_SET_FILTER failed: 6 No such device 
>> or address
>>     
>
> Hmmm.  New one one me, I'll have to investigate.
>
> What specific tool, version and command line arguments are you using?
>
>
>   
>> I have to kill the scan with a control-c at this point.  Can anyone give 
>> me some advice with this problem?
>>     
>
> Make sure you are using the latest cx18 driver from:
>
> http://linuxtv.og/hg/v4l-dvb
>
> versions older than v1.0.4 of the cx18 driver have problems dealing with
> the occasional PCI bus error.
>
>
> Instructions can be found here:
>
> http://www.ivtvdriver.org/index.php/Cx18
>
>
> Make sure you have a good clean signal coming in:
>
> http://www.ivtvdriver.org/index.php/Howto:Improve_signal_quality
>
>
> Regards,
> Andy
>
>   
>> Thanks,
>>
>> Eric
>>     
>
>
>
>   


[-- Attachment #1.2: Type: text/html, Size: 5934 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  reply	other threads:[~2009-01-04 20:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-04 15:28 [linux-dvb] Problem Searching Channels Eric Bauer
2009-01-04 17:46 ` Andy Walls
2009-01-04 20:44   ` Eric Bauer [this message]
2009-01-04 22:01     ` Eric Bauer
2009-01-04 23:44       ` Andy Walls

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49611FB9.2080409@centurytel.net \
    --to=ebauer71@centurytel.net \
    --cc=awalls@radix.net \
    --cc=linux-dvb@linuxtv.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.