Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: ivtv: users

HVR-1600 frontend initialization failed

 

 

ivtv users RSS feed   Index | Next | Previous | View Threaded


gf20613 at yahoo

May 22, 2011, 7:10 PM

Post #1 of 7 (1033 views)
Permalink
HVR-1600 frontend initialization failed

Hi all,

I recently put a Hauppauge HVR-1600 model 1388 (p/n 74351) into my Fedora 14
machine (kernel 2.6.35.13-91.fc14.x86_64). It works fine under Windows 7 but won't
initialize under Linux, and /dev/video0 doesn't get created. dmesg says:


[ 17.851163] cx18: Start initialization, version 1.4.0
[ 17.856437] cx18-0: Initializing card 0
[ 17.861665] cx18-0: Autodetected Hauppauge card
[ 17.866992] alloc irq_desc for 21 on node 0
[ 17.866994] alloc kstat_irqs on node 0
[ 17.867014] cx18 0000:04:07.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 17.872239] cx18-0: Unreasonably low latency timer, setting to 64 (was 32)
[ 17.882716] cx18-0: cx23418 revision 01010000 (B)
[ 17.888235] alloc irq_desc for 16 on node 0
[ 17.888236] alloc kstat_irqs on node 0

...unrelated stuff deleted...

[ 18.123131] tveeprom 0-0050: Hauppauge model 74351, rev F1F5, serial# XXXXXXX
[ 18.128960] tveeprom 0-0050: MAC address is XX:XX:XX:XX:XX:XX
[ 18.134815] tveeprom 0-0050: tuner model is NXP 18271C2 (idx 155, type 54)
[ 18.140776] tveeprom 0-0050: TV standards PAL(B/G) NTSC(M) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
[ 18.146976] tveeprom 0-0050: audio processor is CX23418 (idx 38)
[ 18.153244] tveeprom 0-0050: decoder processor is CX23418 (idx 31)
[ 18.159462] tveeprom 0-0050: has no radio

[ 18.165605] cx18-0: Autodetected Hauppauge HVR-1600
[ 18.171759] cx18-0: Simultaneous Digital and Analog TV capture supported
[ 18.305638] cs5345 0-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
[ 18.318009] cx18-0: Registered device video0 for encoder MPEG (64 x 32.00 kB)
[ 18.324025] DVB: registering new adapter (cx18)
[ 18.362198] cx18-0: frontend initialization failed
[ 18.368189] cx18-0: DVB failed to register
[ 18.374081] cx18-0: Registered device video32 for encoder YUV (20 x 101.25 kB)
[ 18.380034] cx18-0: Registered device vbi0 for encoder VBI (20 x 51984 bytes)
[ 18.385956] cx18-0: Registered device video24 for encoder PCM audio (256 x 4.00 kB)
[ 18.391899] cx18-0: unregister DVB
[ 18.397944] cx18-0: Error -1 registering devices
[ 18.406194] cx18-0: Error -1 on initialization
[ 18.411999] cx18: probe of 0000:04:07.0 failed with error -1
[ 18.417802] cx18: End initialization

(Card s/n and system MAC address replaced by "XX")


I've got the firmware provided with Fedora: cx18-firmware-20080628-3.noarch


and the driver from ATrpms: video4linux-kmdl-2.6.35.13-91.fc14-20110208_132512-98.fc14.x86_64

Are these new enough to support this card, or should I get the ones from:


http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers


dheitmueller at kernellabs

May 22, 2011, 7:19 PM

Post #2 of 7 (992 views)
Permalink
Re: HVR-1600 frontend initialization failed [In reply to]

On Sun, May 22, 2011 at 10:10 PM, Greg Fruth <gf20613 [at] yahoo> wrote:
> Hi all,
> I recently put a Hauppauge HVR-1600 model 1388 (p/n 74351) into my Fedora 14
> machine (kernel 2.6.35.13-91.fc14.x86_64). It works fine under Windows 7
> but won't
> initialize under Linux, and /dev/video0 doesn't get created. dmesg says:

Hello Greg,

This is a relatively new variant of the HVR-1600 (support was added
for it in April), and as a result you need an up to date v4l-dvb
build.

See the LinuxTV wiki for instructions on installing the latest
"media_build" tree.

Regards,

Devin

--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


awalls at md

May 22, 2011, 7:30 PM

Post #3 of 7 (993 views)
Permalink
Re: HVR-1600 frontend initialization failed [In reply to]

Greg Fruth <gf20613 [at] yahoo> wrote:

>Hi all,
>
>I recently put a Hauppauge HVR-1600 model 1388 (p/n 74351) into my
>Fedora 14
>machine (kernel 2.6.35.13-91.fc14.x86_64).  It works fine under Windows
>7 but won't
>initialize under Linux, and /dev/video0 doesn't get created.  dmesg
>says:
>
>
>[   17.851163] cx18:  Start initialization, version 1.4.0
>[   17.856437] cx18-0: Initializing card 0
>[   17.861665] cx18-0: Autodetected Hauppauge card
>[   17.866992]   alloc irq_desc for 21 on node 0
>[   17.866994]   alloc kstat_irqs on node 0
>[   17.867014] cx18 0000:04:07.0: PCI INT A -> GSI 21 (level, low) ->
>IRQ 21
>[   17.872239] cx18-0: Unreasonably low latency timer, setting to 64
>(was 32)
>[   17.882716] cx18-0: cx23418 revision 01010000 (B)
>[   17.888235]   alloc irq_desc for 16 on node 0
>[   17.888236]   alloc kstat_irqs on node 0
>
>...unrelated stuff deleted...
>
>[   18.123131] tveeprom 0-0050: Hauppauge model 74351, rev F1F5,
>serial# XXXXXXX
>[   18.128960] tveeprom 0-0050: MAC address is XX:XX:XX:XX:XX:XX
>[   18.134815] tveeprom 0-0050: tuner model is NXP 18271C2 (idx 155,
>type 54)
>[   18.140776] tveeprom 0-0050: TV standards PAL(B/G) NTSC(M) PAL(I)
>SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
>[   18.146976] tveeprom 0-0050: audio processor is CX23418 (idx 38)
>[   18.153244] tveeprom 0-0050: decoder processor is CX23418 (idx 31)
>[   18.159462] tveeprom 0-0050: has no radio
>
>[   18.165605] cx18-0: Autodetected Hauppauge HVR-1600
>[   18.171759] cx18-0: Simultaneous Digital and Analog TV capture
>supported
>[   18.305638] cs5345 0-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
>[   18.318009] cx18-0: Registered device video0 for encoder MPEG (64 x
>32.00 kB)
>[   18.324025] DVB: registering new adapter (cx18)
>[   18.362198] cx18-0: frontend initialization failed
>[   18.368189] cx18-0: DVB failed to register
>[   18.374081] cx18-0: Registered device video32 for encoder YUV (20 x
>101.25 kB)
>[   18.380034] cx18-0: Registered device vbi0 for encoder VBI (20 x
>51984 bytes)
>[   18.385956] cx18-0: Registered device video24 for encoder PCM audio
>(256 x 4.00 kB)
>[   18.391899] cx18-0: unregister DVB
>[   18.397944] cx18-0: Error -1 registering devices
>[   18.406194] cx18-0: Error -1 on initialization
>[   18.411999] cx18: probe of 0000:04:07.0 failed with error -1
>[   18.417802] cx18:  End initialization
>
>(Card s/n and system MAC address replaced by "XX")
>
>
>I've got the firmware provided with Fedora:
>cx18-firmware-20080628-3.noarch
>
>
>and the driver from ATrpms:
>video4linux-kmdl-2.6.35.13-91.fc14-20110208_132512-98.fc14.x86_64
>
>Are these new enough to support this card, or should I get the ones
>from:
>
>
>http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers_______________________________________________
>ivtv-users mailing list
>ivtv-users [at] ivtvdriver
>http://ivtvdriver.org/mailman/listinfo/ivtv-users

Hi,

You really do need the bleeding edge cx18 and tda8290 driver from the media_tree git repository. The changes will be in either kernel v2.6.39 or 2.6.40 (I can't remember which right now).

The cx18 driver will report its version as 1.4.1 or greater.

Regards,
Andy

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


gf20613 at yahoo

May 24, 2011, 7:58 AM

Post #4 of 7 (1041 views)
Permalink
Re: HVR-1600 frontend initialization failed [In reply to]

Andy,


Thanks for the response. Is it media_tree or media_build that I need? The instructions at

http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers
and the message from Devin H. seem to suggest that it's media_build. Plus I'd prefer to add a
module to my current kernel instead of building a whole new one, if possible.


At any rate, when I follow the media_build instructions, the Kinect driver gives compilation errors.

/home/jetson/adm/v4l/media_build/v4l/kinect.c:38:19: error: 'D_ERR' undeclared here (not in a function)
/home/jetson/adm/v4l/media_build/v4l/kinect.c:38:27: error: 'D_PROBE' undeclared here (not in a function)
/home/jetson/adm/v4l/media_build/v4l/kinect.c:38:37: error: 'D_CONF' undeclared here (not in a function)
/home/jetson/adm/v4l/media_build/v4l/kinect.c:38:46: error: 'D_STREAM' undeclared here (not in a function)
/home/jetson/adm/v4l/media_build/v4l/kinect.c:38:57: error: 'D_FRAM' undeclared here (not in a function)
/home/jetson/adm/v4l/media_build/v4l/kinect.c:38:66: error: 'D_PACK' undeclared here (not in a function)
/home/jetson/adm/v4l/media_build/v4l/kinect.c:39:2: error: 'D_USBI' undeclared here (not in a
function)
/home/jetson/adm/v4l/media_build/v4l/kinect.c:39:11: error: 'D_USBO' undeclared here (not in a function)
/home/jetson/adm/v4l/media_build/v4l/kinect.c:39:20: error: 'D_V4L2' undeclared here (not in a function)


I tried installing the OpenNI software from the Fedora 14 repo (openni, openni-primesense, and

openni-devel) but it doesn't seem to supply the missing symbols. Perhaps the latest OpenNI Git
repo will supply the necessary bits, but short of that, I'd like to just omit the Kinect driver. I tried the
"Manually Intensive" approach so that I could get to "make menuconfig" but at the step

make tar DIR=<some dir with media -git tree>

I'm not sure what I'm supposed to supply in the DIR variable.



>________________________________
>Hi,
>
>You really do need the bleeding edge cx18 and tda8290 driver from the media_tree git repository. The changes will be in either kernel v2.6.39 or 2.6.40 (I can't remember which right now).
>
>The cx18 driver will report its version as 1.4.1 or greater.
>
>Regards,
>Andy
>
>


awalls at md

May 25, 2011, 2:32 AM

Post #5 of 7 (1003 views)
Permalink
Re: HVR-1600 frontend initialization failed [In reply to]

Greg Fruth <gf20613 [at] yahoo> wrote:

>Andy,
>
>
>Thanks for the response. Is it media_tree or media_build that I need?
>The instructions at
>
>http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers
>and the message from Devin H. seem to suggest that it's media_build. 
>Plus I'd prefer to add a
>module to my current kernel instead of building a whole new one, if
>possible.
>
>
>At any rate, when I follow the media_build instructions, the Kinect
>driver gives compilation errors.
>
>/home/jetson/adm/v4l/media_build/v4l/kinect.c:38:19: error: 'D_ERR'
>undeclared here (not in a function)
>/home/jetson/adm/v4l/media_build/v4l/kinect.c:38:27: error: 'D_PROBE'
>undeclared here (not in a function)
>/home/jetson/adm/v4l/media_build/v4l/kinect.c:38:37: error: 'D_CONF'
>undeclared here (not in a function)
>/home/jetson/adm/v4l/media_build/v4l/kinect.c:38:46: error: 'D_STREAM'
>undeclared here (not in a function)
>/home/jetson/adm/v4l/media_build/v4l/kinect.c:38:57: error: 'D_FRAM'
>undeclared here (not in a function)
>/home/jetson/adm/v4l/media_build/v4l/kinect.c:38:66: error: 'D_PACK'
>undeclared here (not in a function)
>/home/jetson/adm/v4l/media_build/v4l/kinect.c:39:2: error: 'D_USBI'
>undeclared here (not in a
> function)
>/home/jetson/adm/v4l/media_build/v4l/kinect.c:39:11: error: 'D_USBO'
>undeclared here (not in a function)
>/home/jetson/adm/v4l/media_build/v4l/kinect.c:39:20: error: 'D_V4L2'
>undeclared here (not in a function)
>
>
>I tried installing the OpenNI software from the Fedora 14 repo (openni,
>openni-primesense, and
>
>openni-devel) but it doesn't seem to supply the missing symbols. 
>Perhaps the latest OpenNI Git
>repo will supply the necessary bits, but short of that, I'd like to
>just omit the Kinect driver. I tried the
>"Manually Intensive" approach so that I could get to "make menuconfig"
>but at the step
>
>make tar DIR=<some dir with media -git tree>
>
>I'm not sure what I'm supposed to supply in the DIR variable.
>
>
>
>>________________________________
>>Hi,
>>
>>You really do need the bleeding edge cx18 and tda8290 driver from the
>media_tree git repository.  The changes will be in either kernel
>v2.6.39 or 2.6.40 (I can't remember which right now).
>>
>>The cx18 driver will report its version as 1.4.1 or greater.
>>
>>Regards,
>>Andy
>>
>>

Greg,

Yes media_tree is a whole kernel build; you likely don't want that.

It is my understanding that the media_build pulls down a media_tree and tries to build only the v4l-dvb modules for your kernel version. I have no firsthand experience.

Somewhere in the build area there should be a .config file that you can manually edit to inhibit the build of the kinect module.

This cx18 change is unfortunately not a one module fix. You'll at least need, IIRC, a new cx18, tda8290, tda18271, and s5h1411 modules. Since there have been various updates to infrastructure, you'll also need modules that those depend on: tuner, v4l-common and likely others. Dependencies tend to snowball. :(

Regards,
Andy

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


gf20613 at yahoo

May 25, 2011, 10:15 AM

Post #6 of 7 (979 views)
Permalink
Re: HVR-1600 frontend initialization failed [In reply to]

Yep, cascading dependencies are exactly why I wanted to skip the Kinect driver! :-)
I tried using the Fedora OpenNI packages but that was as much effort as I was willing
to put into it, seeing as I don't have a Kinect.

I'll give the media_build a try.

Thanks for your help!




>________________________________
>From: Andy Walls <awalls [at] md>
>To: Greg Fruth <gf20613 [at] yahoo>; User discussion about IVTV <ivtv-users [at] ivtvdriver>
>Sent: Wednesday, May 25, 2011 2:32 AM
>Subject: Re: [ivtv-users] HVR-1600 frontend initialization failed
>
>Yes media_tree is a whole kernel build; you likely don't want that.
>
>It is my understanding that the media_build pulls down a media_tree and tries to build only the v4l-dvb modules for your kernel version. I have no firsthand experience.
>
>Somewhere in the build area there should be a .config file that you can manually edit to inhibit the build of the kinect module.
>
>This cx18 change is unfortunately not a one module fix. You'll at least need, IIRC, a new cx18, tda8290, tda18271, and s5h1411 modules. Since there have been various updates to infrastructure, you'll also need modules that those depend on: tuner, v4l-common and likely others. Dependencies tend to snowball. :(
>
>
>


gf20613 at yahoo

May 26, 2011, 9:01 PM

Post #7 of 7 (976 views)
Permalink
Re: HVR-1600 frontend initialization failed [In reply to]

For the record, I got the drivers compiled and installed but so far I've only gotten them partially
working. The device sometimes works (in SD mode IIRC) using dd if=/dev/video0 but I'm still trying
to figure out what the symptoms are.

Anyway, FWIW here's what I had to do to get media_tree to build on stock Fedora 14 kernel
2.6.35.13-91.fc14.x86_64:

git clone git://linuxtv.org/media_build.git
cd media_build
./build.sh

build.sh will stop at the Kinect driver with compiler errors. Edit build.sh to comment out the following

lines, or build.sh will clobber any code edits you make below: (editing the .config file doesn't seem to
work)


#run git pull git://linuxtv.org/media_build.git master
#run make -C linux/ download
#run make -C linux/ untar

Assuming you don't need the Kinect driver, comment out or use #ifdef to disable the following line in
media_build/linux/drivers/media/video/gspca/kinect.c:

int gspca_debug = D_ERR | D_PROBE | D_CONF | D_STREAM | D_FRAM | D_PACK |
D_USBI | D_USBO | D_V4L2;


Assuming you don't need the Samsung S5P/EXYNOS4 SoC series MIPI-CSI driver, edit
media_build/linux/drivers/media/video/s5p-fimc/mipi-csis.c to comment out the line:

#include <plat/mipi_csis.h>


and use #ifdef to skip the contents of the functions s5pcsis_set_params, s5pcsis_probe, s5pcsis_suspend,
and s5pcsis_resume, as they seem to be using bits from that include that my system doesn't have. Then
build.sh will complete successfully.


The rest of the instructions worked as-is.



>>________________________________
>>From: Andy Walls <awalls [at] md>
>>To: Greg Fruth <gf20613 [at] yahoo>; User discussion about IVTV <ivtv-users [at] ivtvdriver>
>>Sent: Wednesday, May 25, 2011 2:32 AM
>>Subject: Re: [ivtv-users] HVR-1600 frontend initialization failed
>>
>>Yes media_tree is a whole kernel build; you likely don't want that.
>>
>>It is my understanding that the media_build pulls down a media_tree and tries to build only the v4l-dvb modules for your kernel version. I have no firsthand experience.
>>
>>Somewhere in the build area there should be a .config file that you can manually edit to inhibit the build of the kinect module.
>>
>>This cx18 change is unfortunately not a one module fix. You'll at least need, IIRC, a new cx18, tda8290, tda18271, and s5h1411 modules. Since there have been various updates to infrastructure, you'll also need modules that those depend on: tuner, v4l-common and likely others. Dependencies tend to snowball. :(

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users

ivtv users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.