Re: [ivtv-devel] ivtv: Write on read-only interface/ dd Invalid Argument

[Bryan M. <br...@te...>]

Argh.  I feel like a dolt.  dd doesn't work when the ivtv-fb module is 
loaded.  I removed that, and it's working now and damn does it look 
great!  Nice work guys!  :)

Thanks for dealing with my questions.  Hopefully this will help somebody 
else browsing the list archive in the future!
Bryan

Bryan Murphy wrote:

> Well, no luck here.  I removed all my other PCI cards and tried every 
> PCI slot.  Same behavior for all PCI slots, except one where the 
> machine won't boot.  I grabbed another video card from my desktop and 
> tried the system with that and experienced the same problem.
> Unfortunately, my desktop is refusing to boot to windows (unrelated to 
> the PVR-350) so I can't test the card on that machine at the moment, 
> however it was working fine in the windows environment only a couple 
> days ago so I have no reason to believe that the PVR card has gone bad.
> I'll play around with the saa7121 driver a bit tonight, add some 
> debugging code, and see what I can come up with.  At the very least I 
> hope to narrow it down to the line of code that causes the white lines 
> appear.
>
> Bryan
>
> Bryan Murphy wrote:
>
>> Nope, I've tried that as well.  If I do a cold boot with test_image=0 
>> and/or no test_image parameter I get audio and no video as well.   
>> The only difference in these scenarios are that instead of the test 
>> pattern I get a screen of black and white lines offset like the 
>> following pattern:
>>
>> --- -------
>> ---- ------
>> ------ ----
>> -------- --
>>
>> Not that that really helps anything, but I wanted to try out my 
>> rather lacking ASCII art skills. ;)
>>
>> I've attached my whole dmesg output this time.  Nothing catches my 
>> eye, but something is surely going wrong somewhere.  I'm going to try 
>> monkeying around with my PCI slots and IRQ settings to see if 
>> something else might be conflicting with it and see if that helps any.
>>
>> Bryan
>>
>> (dmesg output after quoted email)
>>
>> kevin thayer wrote:
>>
>>> you're not loading saa7127 with test_image=1 are you?
>>>
>>> you shouldn't do that. If the audio is coming out of
>>> the PVR card, then it's decoding, and the problem is
>>> with the saa7127 driver
>>>
>>> -tmk
>>>
>>> --- Bryan Murphy <br...@te...> wrote:
>>>  
>>>
>>>> I'm closer.  I fixed my problem yesterday with the
>>>> screwy TV out image (though I don't know what it was).  Today I'm 
>>>> using
>>>> Jens 29B driver but I am still having one problem.
>>>>
>>>> Basically, I did the same as Nick below:
>>>>
>>>> modprobe i2c-core
>>>> modprobe i2c-algo-bit
>>>> modprobe videodev
>>>> modprobe tuner type=2
>>>> modprobe saa7115
>>>> modprobe ivtv
>>>> modprobe saa7127 enable_output=1 output_select=0
>>>> test_image=1   
>>>
>>>
>>
>>
>> dmesg output:
>>
>> i2c-core.o: i2c core module
>> i2c-algo-bit.o: i2c bit algorithm module
>> Linux video capture interface: v1.00
>> i2c-core.o: driver i2c TV tuner driver registered.
>> i2c-core.o: driver saa7115 registered.
>> ivtv: SGarray_size = 340, DSGarray_size = 16
>> ivtv: Found an iTVC15 based chip
>> tuner: chip found @ 0xc2
>> tuner(bttv): type forced to 2 (Philips NTSC (FI1236,FM1236 and 
>> compatibles)) [insmod]
>> i2c-core.o: client [Philips NTSC (FI1236,FM1236 and] registered to 
>> adapter [ivtv i2c driver #0](pos. 0).
>> saa7114.c: starting probe for adapter ivtv i2c driver #0 (0x10005)
>> saa7114.c: detecting saa7114 client on address 0x42
>> saa7115.c: writing init values
>> status: (1E) 0x48, (1F) 0xc0
>> i2c-core.o: client [saa7115[0]] registered to adapter [ivtv i2c 
>> driver #0](pos. 1).
>> i2c-core.o: adapter ivtv i2c driver #0 registered as adapter 0.
>> ivtv: Encoder revision: 0x02040011
>> ivtv: Decoder revision: 0x02020023
>> ivtv: i2c client addr: 64 not found!
>> ivtv: Registered v4l2 device, minor 0
>> ivtv: Registered v4l2 device, minor 32
>> ivtv: Registered v4l2 device, minor 224
>> ivtv: Registered v4l2 device, minor 16
>> i2c-core.o: driver i2c msp3400 driver registered.
>> msp34xx: init: chip=MSP3448W-A2, has NICAM support
>> msp3410: daemon started
>> i2c-core.o: client [MSP3448W-A2] registered to adapter [ivtv i2c 
>> driver #0](pos. 2).
>> [saa7127.c: INFO]: SAA7127 video encoder driver loaded
>> i2c-core.o: driver saa7127 registered.
>> saa7127: Configuring encoder...i2c-core.o: client [saa7127[0]] 
>> registered to adapter [ivtv i2c driver #0](pos. 3).
>> ivtv-fb: Framebuffer module loaded (attached to ivtv card id 0)
>> ivtv-fb: screen coords: [0 0] -> [720 480]
>> ivtv-fb: original global alpha = 208
>> ivtv-fb: new global alpha = 208
>> ivtv-fb: current OSD state = 35
>> ivtv-fb: warning: cannot reserve video memory at 0xd9510000
>> ivtv-fb: framebuffer at 0xd9510000, mapped to 0xe2bb3000, size 2818k
>> ivtv-fb: mode is 720x480x32, linelength=2880
>> Console: switching consoles 1-0 to frame buffer device
>> fb0: iTVC15 TV out frame buffer device
>>
>
>