Ok, before you all send me to the many posts that already exist on this topic, please believe me when I tell you that I've read a goodly number of them and I am still having problems.

I am using a 2.7GHz Celeron based E-machine with a 200G HD running KnoppMyth R4V4. The TV card is a PVR-350. Currently the system is configured to display on the monitor and that works great, no problems.

I would like to move the system to the lliving room and hook it up to the big TV their using the PVR-350 TV-OUT connector. I've determined that the frame buffer device is fb0, I've found the bus address, which is 02:0a.0, and I've made the changes as instructed in all the various posts to the supplied XF86Config-4 file. I started with the PVR350-OUT example.

I've also verified that I can use dd to pipe the input to /dev/video and everything seems to work fine, the TV output is nice and clear.

I copied the modified XF86Config-4 file into place and tried rebooting and my results are less than thrilling. There is a brief flash of a green screen on the target TV then a black screen with what appears to be a blinking block cursor.

I've scoured the various message and log files and the only thing I can find that looks relevant is the following message:

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 0xf9510000
ivtv-fb: framebuffer at 0xf9510000, mapped to 0xd2acd000, size 2818k
ivtv-fb: mode is 720x480x32, linelength=2880
Console: switching to colour frame buffer device 90x30
fb0: iTVC15 TV out frame buffer device

I'm talking about the line with the warning. I put in the other lines for context.

The following is a more complete listing of all the messages that seem relevant:

ivtv: version 0.1.9 (release) loading
ivtv: SGarray_size = 340, DSGarray_size = 16
ivtv: Found an iTVC15 based chip
PCI: Found IRQ 11 for device 02:0a.0
tuner: chip found @ 0xc2
i2c-core.o: client [(tuner unset)] registered to adapter [ivtv i2c driver #0](pos. 0).
tuner: type forced to -1 (<NULL>) [insmod]
tuner: type set to 2 (Philips NTSC (FI1236,FM1236 and compatibles))
saa7127: Configuring encoder...<7>i2c-core.o: client [saa7127[0]] registered to adapter [ivtv i2c driver #0](pos. 1).
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) 0x89, (1F) 0xb1
i2c-core.o: client [saa7115[0]] registered to adapter [ivtv i2c driver #0](pos. 2).
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. 3).
i2c-core.o: adapter ivtv i2c driver #0 registered as adapter 0.
ivtv: Encoder revision: 0x02040011
ivtv: Decoder revision: 0x02020023
ivtv: Registered v4l2 device, minor 0
ivtv: Registered v4l2 device, minor 32
ivtv: Registered v4l2 device, minor 224
ivtv: Registered v4l2 device, minor 16
ivtv: loaded
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 0xf9510000
ivtv-fb: framebuffer at 0xf9510000, mapped to 0xd2acd000, size 2818k
ivtv-fb: mode is 720x480x32, linelength=2880
Console: switching to colour frame buffer device 90x30
fb0: iTVC15 TV out frame buffer device
lirc_dev: IR Remote Control driver registered, at major 61
bttv: driver version 0.9.12 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: driver version 0.9.15 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
i2c-core.o: driver i2c ir driver registered.
lirc_i2c: chip found @ 0x18 (Hauppauge IR)
i2c-core.o: client [Hauppauge IR] registered to adapter [ivtv i2c driver #0](pos. 4).
lirc_dev: lirc_register_plugin:sample_rate: 10
saa7115[0]: decoder set norm NTSC
saa7115[0] set audio: 0x02
saa7115[0]: decoder set input (0)
saa7115[0]: now setting Composite input
saa7115[0]: decoder set size
Setting full NTSC width
Setting full NTSC height
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
saa7115[0]: decoder set input (4)
saa7115[0]: now setting Composite input
saa7115[0]: decoder set norm NTSC
saa7115[0] set audio: 0x02
saa7115[0]: decoder set picture bright=128 contrast=63 saturation=64 hue=0
saa7115[0]: decoder set picture bright=128 contrast=63 saturation=63 hue=0
saa7115[0]: decoder set picture bright=127 contrast=63 saturation=63 hue=0
saa7115[0]: decoder set picture bright=127 contrast=63 saturation=63 hue=0

I'm hoping one of you can come up with some suggestions as to what I can look at to find out where this problem is.

One more possibly imporant detail. In the stuff I read it said that once I had things configured correctly I should be able to change the TV Playback settings so that the output is to the PVR-350 using /dev/video16 and I'd see the playback on the TV rather than on the monitor. Doing this just gives me a blank screen on both devices until I use the Esc key or the Back key on the remote.

Thank you ahead of time for your patient help.

Ray

_________________
-- All that is gold does not glitter -- J.R.R. Tolkien

Ok I'll preface this with I'm not good with the pvr350's I helped one person get it partially working till we scraped it cause of the divx playback problems that had no solution at the time.

but you may want to look at /var/log/XFree86.0.log to see if there are any errors there that might give you a clue.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

That was just the help I needed actually. What I found, when I looked in the XFree86.0.log was that I had not changed the name of the Mouse device from "Mouse0" to "PS/2 Mouse", so the file was aborting with an error. Once that was fixed I was able to use startx to start up X and got X on the TV screen!

Thanks!

_________________
-- All that is gold does not glitter -- J.R.R. Tolkien

Well, I thought everything was all done. After I started X up using startx and was able to successfully watch TV on the TV, I tried rebooting to make sure everything still worked the same way. This time, to my dismay, the menus show up, but if I try to watch TV, all I get is a blank screen. I'm perplexed again!

_________________
-- All that is gold does not glitter -- J.R.R. Tolkien

Blank or black screen? If the latter, you may now have to fix the famous "obsolete" problem. Look in the logs for "remapping obsolete fb" or something like this...

check
http://www.mysettopbox.tv/phpBB2/viewto ... t=obsolete

Laurent

I don't think that's it. I can't find the indicated message in the dmesg and I don't have a device /dev/fbautodetect.

The wierd thing is that at one point I did have the front end working and playback on the TV. It was when I'd first fixed the XF86Config-4 file and used startx to bring X up. When I tried watching TV it worked. When I rebooted, though, the playback stopped working.

_________________
-- All that is gold does not glitter -- J.R.R. Tolkien

when you used startx to bring up the display were you logged in as root? if so then it may be a permissions issue somewhere. you could always do a ctrl+alt+F1 then as root do /etc/init.d/gdm stop at that point you can test and see if startx will make it work again, and you could test both from root and from mythtv users and see if it's a permissions issue. to get back to go back to the way it works on boot you would do /etc/init.d/gdm start (once you've killed X from the startx command.)

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

Also, the card and the ivtv drivers are a bit funky sometimes... I've had situations where I had to reboot 3,4,5 times before something would "take". Maybe your card is in a weird state, and just not coming back.
Try loading and unloading the modules, cold restart a few times... before you rip the whole thing apart.

X works ok, it's the playback of video that is not working correctly. I was super user when I started X, but I don't think that would have influenced the mythTV application which should have been controlling playback of the video.

_________________
-- All that is gold does not glitter -- J.R.R. Tolkien