[mythtv-users] /sbin/modprobe ivtv -- not working
Dean Blackburn
deano at deano.com
Mon Dec 22 02:59:39 EST 2003
I'll just through in another voice: absolutely the same symptoms here,
but running on fedora core 1. I've tried with both the 21288 and the
earlier 21226(?) version, and still no luck.
-deano
>>I have gotten to this place 4 times after complete re-installs. :^(
>>
>> I have a WINTV PVR 350 card on a P4PE ASUS MB w/ a 2.4ghz and 1 GIG
>> of RAM.
>>
>> I followed Jarod's Guide..
>>
>>When I do a /sbin/modprobe ivtv, I get this:
>>
>>[root at myth root]# /sbin/modprobe ivtv
>>Warning: ignoring debug=1, no such parameter in this module
>>/lib/modules/2.4.20-24_31.rh9.at/updates/drivers/media/video/ivtv.o:
>>
>>
>init_module: No such device
>
>
>>Hint: insmod errors can be caused by incorrect module parameters,
>>
>>
>including invalid IO or IRQ parameters.
>
>
>> You may find more information in syslog or the output from dmesg
>>/lib/modules/2.4.20-24_31.rh9.at/updates/drivers/media/video/ivtv.o:
>>
>>
>insmod /lib/modules/2.4.20-24_31.rh9.at/updates/drivers/media/video/ivtv.o
>failed
>
>
>>/lib/modules/2.4.20-24_31.rh9.at/updates/drivers/media/video/ivtv.o:
>>
>>
>insmod ivtv failed
>
>
>>The relevant output of /var/log/messages is:
>>
>>Dec 20 18:11:52 myth kernel: i2c-core.o: i2c core module version 2.8.0
>>
>>
>(20030714)
>
>
>>Dec 20 18:11:52 myth kernel: ivtv: SGarray_size = 340, DSGarray_size = 16
>>Dec 20 18:11:52 myth kernel: ivtv: Found an iTVC15 based chip
>>Dec 20 18:11:52 myth kernel: PCI: Found IRQ 7 for device 02:0c.0
>>Dec 20 18:11:52 myth kernel: PCI: Sharing IRQ 7 with 02:05.0
>>Dec 20 18:11:52 myth kernel: tuner: probing ivtv i2c driver #0 i2c adapter
>>
>>
>[id=0x10005]
>
>
>>Dec 20 18:11:52 myth kernel: tuner: chip found @ 0xc2
>>Dec 20 18:11:52 myth kernel: tuner(bttv): type forced to 2 (Philips NTSC
>>
>>
>(FI1236,FM1236 and compatibles)) [insmod]
>
>
>>Dec 20 18:11:52 myth kernel: saa7114.c: starting probe for adapter ivtv
>>
>>
>i2c driver #0 (0x10005)
>
>
>>Dec 20 18:11:52 myth kernel: saa7114.c: detecting saa7114 client on
>>
>>
>address 0x42
>
>
>>Dec 20 18:11:52 myth kernel: saa7115.c: writing init values
>>Dec 20 18:11:54 myth kernel: status: (1E) 0x48, (1F) 0xc0
>>Dec 20 18:11:54 myth kernel: msp34xx: init: chip=MSP3448W-A2, has NICAM
>>
>>
>support
>
>
>>Dec 20 18:11:54 myth kernel: msp3410: daemon started
>>Dec 20 18:11:56 myth kernel: ivtv: Encoder revision: 0x02040011
>>Dec 20 18:11:56 myth kernel: ivtv: Device or minor 0 not accepted
>>Dec 20 18:11:56 myth kernel: ivtv: Device or minor 1 not accepted
>>Dec 20 18:11:56 myth kernel: ivtv: Registered v4l2 device, minor 2
>>Dec 20 18:11:56 myth kernel: ivtv: Device or minor 32 not accepted
>>Dec 20 18:11:56 myth kernel: ivtv: Couldn't register v4l2 device!
>>Dec 20 18:11:56 myth kernel: ivtv: Problem starting v4l2
>>Dec 20 18:11:56 myth kernel: ivtv: Error -19 on init
>>Dec 20 18:11:56 myth kernel: ivtv: Error detecting PCI card
>>
>>
>>It's almost as if the WinTV PVR 350 is not recognized on the system at
>>all. This is borne out by the output of /proc/interrupts:
>>
>>[root at myth root]# cat /proc/interrupts
>> CPU0
>> 0: 239439 XT-PIC timer
>> 1: 1783 XT-PIC keyboard
>> 2: 0 XT-PIC cascade
>> 5: 198505 XT-PIC nvidia
>> 7: 73873 XT-PIC eth0
>> 8: 1 XT-PIC rtc
>> 9: 0 XT-PIC Intel ICH4
>> 12: 137372 XT-PIC PS/2 Mouse
>> 14: 13783 XT-PIC ide0
>> 15: 7442 XT-PIC ide1
>>NMI: 0
>>ERR: 0
>>
>>
>>I have swapped the PVR card to different PCI slots with no change.
>>
>>The only thing I can think of that is different from Jarod's Guide is
>>the kernel.
>>
>>"Install his latest kernel and kernel-source packages (as of this
>>
>>
>writing), like so:
>
>
>># apt-get install kernel#2.4.20-20_29.rh9.at
>>
>>
>kernel-source#2.4.20-20_29.rh9.at"
>
>
>>The latest kernel according to the link provided was ...20-24_31,
>>which is what I installed.
>>
>>And the .exe on the Hauptpauge web site is now pvr250_17_21288.exe
>>instead of pvr250_17_21226.exe, so I installed the 88.exe one.
>>
>>I have tried to find the older kernel version mentioned in the Guide,
>>but it is obsolete and UTL.
>>
>>I have read up on the GOSSAMER forums as well, but didn't find any
>>help there. Some clues that did not pan out.
>>
>>Any assistance would be most appreciated.
>>
>>
>>
>>--
>>Best regards,
>> Myth mailto:mythtv at pln.cc
>>
>>
>>
>>
>
>
>----------------------------------------------------------------------------
>----
>
>
>_______________________________________________
>mythtv-users mailing list
>mythtv-users at mythtv.org
>http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>_______________________________________________
>mythtv-users mailing list
>mythtv-users at mythtv.org
>http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>
More information about the mythtv-users
mailing list