Bob Wessen wrote:

ok, making progress, got the latest version of hotplug, completely 
re-read and re-installed the firmware setup for ivtv 0.4.2 per the 
instructions on the wiki, then re-compiled and used the kernel (2.6.14) 
version of eeprom + tuner, and setting the following order for loading 
modules

tuner
tveeprom
ivtv
ivtv-fb

then everything loads and reports properly in dmesg and I can read from 
/dev/video0 and output to /dev/video16 as expected, although now I have 
a separate issue....

The video quality is very bad in using the ivtvdev (0.10.6) x fb 
driver.  It is pixelated and fuzzy, like I'm watching low bitrate 
streaming video with both myth and mplayer.  The performance in the past 
has been excellent (indistinguishable from normal TV).   CPU usage is 
below 5% (on a VIA C3, thats pretty good) while using the ivtvdev 
driver, the video is not choppy, just really bad quality, lots of blocks 
and artifacts showing up.  Both mplayer and myth display great using the 
vesa driver on x and the built in unichrome video card (although CPU 
usage is through the roof as would be expected without acceleration of 
any kind)

I've tried using the binary version of ivtvdev and compiled a version 
against xorg 6.8.2 with gcc 3.4.5, both act the same.

Anyone seen this or know how to correct it?

> Hans Verkuil wrote:
>   
>> On Sunday 15 January 2006 21:43, Bob Wessen wrote:
>>   
>>     
>>> Please excuse this reply to my own message, but I wanted to add that
>>> the just released 0.4.2 gives the exact same results.
>>>     
>>>       
>> ivtv is not seeing your card at all. Check with lspci to see if the card 
>> is detected properly. 
>>
>>      Hans
>>
>>   
>>     
> thanks for the reply, thats what I though at first too, since the first 
> line in the dmesg output is usually something about autodetecting the 
> card.  lspci gives:
>
> 00:14.0 Multimedia video controller: Internext Compression Inc
> iTVC15 MPEG-2 Encoder (rev 01)
>
> before and after running "modprobe ivtv"
>
> It however will *sometimes* not see the card after trying to load the 
> ivtv-fb module (which always fails with the error described below)  The 
> only way to get it back when it does go away is to pull the power and 
> card out, wait a minute, then plug it back in.
>
>   
>>> Bob Wessen wrote:
>>>     
>>>       
>>>> I have used the old ivtv 0.2 branch in the past on a VIA M10000
>>>> with a PVR350 using gentoo,  due to hardware failure it has been
>>>> out of action for 8 months.  I finally ditched the M10000 in favor
>>>> of a VIA SP13000. Now can't get seem to get ivtv to work again.  I
>>>> have tried both the gentoo 0.4.0 ebuild in the portage tree and
>>>> when that did not work tried the 0.4.1 release from ivtvdriver.org.
>>>>
>>>> I am using Gentoo 2.6.14-r5 sources.
>>>>
>>>> lspci gives
>>>> 00:14.0 Multimedia video controller: Internext Compression Inc
>>>> iTVC15 MPEG-2 Encoder (rev 01)
>>>>
>>>> The strange part is when I try to insert the ivtv module this
>>>> output comes up in dmesg,
>>>>
>>>> ivtv:  ==================== START INIT IVTV ====================
>>>> ivtv:  version 0.4.1 (tagged release) loading
>>>> ivtv:  Linux version: 2.6.14-gentoo-r5 preempt VIAC3-2 gcc-3.4
>>>> ivtv:  In case of problems please include the debug info between
>>>> ivtv:  the START INIT IVTV and END INIT IVTV lines, along with
>>>> ivtv:  any module options, when mailing the ivtv-users mailinglist.
>>>> ivtv:  ====================  END INIT IVTV  ====================
>>>>
>>>> but nothing else.  There used to be a whole lot more in the past,
>>>> and all other posts I have seen have much more going on.  After it
>>>> has been loaded, there are no errors and everything seems fine, but
>>>> there are no v4l devices setup and nothing works.
>>>>
>>>> When I try to load the ivtv-fb module it gives a message
>>>> ivtv-osd: ivtv_fb_card_id parameter is out of range (valid range:
>>>> 0--1)
>>>>
>>>> at that point the card sometimes hangs, I can't unload the ivtv-fb
>>>> driver and *sometimes* after this lspci will no longer report the
>>>> PVR350 as being there.
>>>>
>>>> Anyone seen this or have any throughts as to what I can try next? 
>>>> This was all working in the past...
>>>>
>>>> _______________________________________________
>>>> ivtv-users mailing list
>>>> [email protected]
>>>> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>>>>       
>>>>         
>>> _______________________________________________
>>> ivtv-users mailing list
>>> [email protected]
>>> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>>>     
>>>       
>> _______________________________________________
>> ivtv-users mailing list
>> [email protected]
>> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>>   
>>     
>
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>   


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

Reply via email to