Mailing List Archive: MythTV: Users

X through PVR350 probs

1 2

View All

Index | Next | Previous | View Threaded

mythtv at biased

Dec 27, 2004, 4:02 AM

Post #1 of 27 (1756 views)
Permalink

X through PVR350 probs

Hello all,

Trying to get the PVR350 working via X, but the X server shows the
following error message:

(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Loading /usr/X11R6/lib/modules/linux/libfbdevhw.a
(II) Module fbdevhw: vendor="The XFree86 Project"
compiled for 4.3.0.1, module version = 0.0.2
ABI class: XFree86 Video Driver, version 0.6

*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.

Fatal server error:
Caught signal 11. Server aborting

Any ideas anyone?

Thanks very much for your help in advance

Cheers - Piers
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

john.p.harvey at btinternet

Dec 27, 2004, 4:21 AM

Post #2 of 27 (1750 views)
Permalink

RE: X through PVR350 probs [In reply to]

You need to use ivtvdev not fbdev. Fbdev is no longer supported with the 350
and ivtvdev provides better performance in any case.
Edit youre config file to refence ivtvdev.

John

> -----Original Message-----
> From: mythtv-users-bounces [at] mythtv [mailto:mythtv-users-
> bounces [at] mythtv] On Behalf Of Piers Kittel
> Sent: 27 December 2004 12:03
> To: Discussion about mythtv
> Subject: [mythtv-users] X through PVR350 probs
>
> Hello all,
>
> Trying to get the PVR350 working via X, but the X server shows the
> following error message:
>
> (II) Loading sub module "fbdevhw"
> (II) LoadModule: "fbdevhw"
> (II) Loading /usr/X11R6/lib/modules/linux/libfbdevhw.a
> (II) Module fbdevhw: vendor="The XFree86 Project"
> compiled for 4.3.0.1, module version = 0.0.2
> ABI class: XFree86 Video Driver, version 0.6
>
> *** If unresolved symbols were reported above, they might not
> *** be the reason for the server aborting.
>
> Fatal server error:
> Caught signal 11. Server aborting
>
> Any ideas anyone?
>
> Thanks very much for your help in advance
>
> Cheers - Piers
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mythtv at biased

Dec 27, 2004, 4:58 AM

Post #3 of 27 (1736 views)
Permalink

Re: X through PVR350 probs [In reply to]

Hello,

I get this:

(II) LoadModule: "ivtvdev"
(WW) Warning, couldn't open module ivtvdev
(II) UnloadModule: "ivtvdev"
(EE) Failed to load module "ivtvdev" (module does not exist, 0)

Cheers - Piers

John Harvey wrote:
> You need to use ivtvdev not fbdev. Fbdev is no longer supported with the 350
> and ivtvdev provides better performance in any case.
> Edit youre config file to refence ivtvdev.
>
> John
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

otter at kjoe

Dec 27, 2004, 5:20 AM

Post #4 of 27 (1743 views)
Permalink

Re: X through PVR350 probs [In reply to]

Piers,

On Monday, 27 December 2004, Piers Kittel wrote:
> I get this:
>
> (II) LoadModule: "ivtvdev"
> (WW) Warning, couldn't open module ivtvdev
> (II) UnloadModule: "ivtvdev"
> (EE) Failed to load module "ivtvdev" (module does not exist, 0)

Did you copy the module from your ivtv/utils directory to
/usr/X11R6/lib/modules/drivers/ (or where your X11 drivers are located)?

-- Niels

Attachments:

signature.asc (0.18 KB)

mythtv at biased

Dec 27, 2004, 5:41 AM

Post #5 of 27 (1730 views)
Permalink

Re: X through PVR350 probs [In reply to]

Have done now, and I get:

======================
(II) IVTVDEV: driver for framebuffer: ivtv
(II) Primary Device is: PCI 01:00:0

*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.

Fatal server error:
Caught signal 11. Server aborting
======================

Different driver, but similar result?

Just a note - Tho I notice that my PVR350 card is in the PCI:00:14:00
and is configured in the XF86Config-4 file but it says "Primary device
is: PCI 01:00:0" but then again it says that any time, no matter which
output I select (VGA via onbard, or TV)

Thanks very much for your help again

Cheers - Piers

Niels den Otter wrote:
> Piers,
>
> On Monday, 27 December 2004, Piers Kittel wrote:
>
>>I get this:
>>
>>(II) LoadModule: "ivtvdev"
>>(WW) Warning, couldn't open module ivtvdev
>>(II) UnloadModule: "ivtvdev"
>>(EE) Failed to load module "ivtvdev" (module does not exist, 0)
>
>
> Did you copy the module from your ivtv/utils directory to
> /usr/X11R6/lib/modules/drivers/ (or where your X11 drivers are located)?
>
>
> -- Niels
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

john.p.harvey at btinternet

Dec 27, 2004, 5:49 AM

Post #6 of 27 (1752 views)
Permalink

RE: X through PVR350 probs [In reply to]

Send me a copy of youre config file and the log file from start X.

It may be easier to start with the 0.7 driver I posted on the ivtv-dev
mailing list about a week ago.

John

> -----Original Message-----
> From: mythtv-users-bounces [at] mythtv [mailto:mythtv-users-
> bounces [at] mythtv] On Behalf Of Piers Kittel
> Sent: 27 December 2004 13:41
> To: Discussion about mythtv; otter [at] kjoe
> Subject: Re: [mythtv-users] X through PVR350 probs
>
> Have done now, and I get:
>
> ======================
> (II) IVTVDEV: driver for framebuffer: ivtv
> (II) Primary Device is: PCI 01:00:0
>
> *** If unresolved symbols were reported above, they might not
> *** be the reason for the server aborting.
>
> Fatal server error:
> Caught signal 11. Server aborting
> ======================
>
> Different driver, but similar result?
>
> Just a note - Tho I notice that my PVR350 card is in the PCI:00:14:00
> and is configured in the XF86Config-4 file but it says "Primary device
> is: PCI 01:00:0" but then again it says that any time, no matter which
> output I select (VGA via onbard, or TV)
>
> Thanks very much for your help again
>
> Cheers - Piers
>
> Niels den Otter wrote:
> > Piers,
> >
> > On Monday, 27 December 2004, Piers Kittel wrote:
> >
> >>I get this:
> >>
> >>(II) LoadModule: "ivtvdev"
> >>(WW) Warning, couldn't open module ivtvdev
> >>(II) UnloadModule: "ivtvdev"
> >>(EE) Failed to load module "ivtvdev" (module does not exist, 0)
> >
> >
> > Did you copy the module from your ivtv/utils directory to
> > /usr/X11R6/lib/modules/drivers/ (or where your X11 drivers are located)?
> >
> >
> > -- Niels
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mythtv at biased

Dec 27, 2004, 6:07 AM

Post #7 of 27 (1737 views)
Permalink

Re: X through PVR350 probs [In reply to]

Hello,

Copies of both files are available here:

http://www.biased.org/misc/XF86Config-4
http://www.biased.org/misc/XFree86.0.log

Thanks again

Cheers - Piers

John Harvey wrote:
> Send me a copy of youre config file and the log file from start X.
>
> It may be easier to start with the 0.7 driver I posted on the ivtv-dev
> mailing list about a week ago.
>
> John
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mythtv at biased

Dec 27, 2004, 6:16 AM

Post #8 of 27 (1737 views)
Permalink

Re: X through PVR350 probs [In reply to]

Installed your 0.7 driver, and here's the updated log:

http://www.biased.org/misc/XFree86.0.log-2
The config file is the same.

The main prob is:

(WW) ivtvdev: No matching Device section for instance (BusID PCI:0:20:0)
found

Obviously, this should be 0:14:0 not 0:20:0. I did try "BusID
"0:0x14:0" but no difference.

Thanks again for your help

Cheers - Piers

John Harvey wrote:
> Send me a copy of youre config file and the log file from start X.
>
> It may be easier to start with the 0.7 driver I posted on the ivtv-dev
> mailing list about a week ago.
>
> John
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mythtv at biased

Dec 27, 2004, 6:31 AM

Post #9 of 27 (1730 views)
Permalink

Re: X through PVR350 probs [In reply to]

Hello again,

Sorry for the flood of emails, but have fixed the config file and X
starts up fine, and I can see something like a login box on my TV but
it's all badly distorted, as the picture shows:

http://www.biased.org/misc/pc270089.jpg

Any ideas?

Thanks very much again for your help

Cheers - Piers

John Harvey wrote:
> Send me a copy of youre config file and the log file from start X.
>
> It may be easier to start with the 0.7 driver I posted on the ivtv-dev
> mailing list about a week ago.
>
> John
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

john.p.harvey at btinternet

Dec 27, 2004, 8:40 AM

Post #10 of 27 (1732 views)
Permalink

RE: X through PVR350 probs [In reply to]

No.
I see you've fixed it but just in case anyone follows this thread in the
future the 20 is correct. BusId's in config files need to be in decimal even
though X and lspci tend to print them in hex. Adding 0x in front completely
breaks the parser which stops when it hits a non decimal character.

John

> -----Original Message-----
> From: mythtv-users-bounces [at] mythtv [mailto:mythtv-users-
> bounces [at] mythtv] On Behalf Of Piers Kittel
> Sent: 27 December 2004 14:17
> To: Discussion about mythtv
> Subject: Re: [mythtv-users] X through PVR350 probs
>
> Installed your 0.7 driver, and here's the updated log:
>
> http://www.biased.org/misc/XFree86.0.log-2
> The config file is the same.
>
> The main prob is:
>
> (WW) ivtvdev: No matching Device section for instance (BusID PCI:0:20:0)
> found
>
> Obviously, this should be 0:14:0 not 0:20:0. I did try "BusID
> "0:0x14:0" but no difference.
>
> Thanks again for your help
>
> Cheers - Piers
>
> John Harvey wrote:
> > Send me a copy of youre config file and the log file from start X.
> >
> > It may be easier to start with the 0.7 driver I posted on the ivtv-dev
> > mailing list about a week ago.
> >
> > John
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

john.p.harvey at btinternet

Dec 27, 2004, 8:44 AM

Post #11 of 27 (1723 views)
Permalink

RE: X through PVR350 probs [In reply to]

I'm assuming that you are in PAL world?
If so I would guess that the driver isn't running properly in PAL.
Either add std=2 (I think) to ivtv options or if that doesn't work post a
link to your messages file and I'll take a look through it.

John

> -----Original Message-----
> From: mythtv-users-bounces [at] mythtv [mailto:mythtv-users-
> bounces [at] mythtv] On Behalf Of Piers Kittel
> Sent: 27 December 2004 14:31
> To: Discussion about mythtv
> Subject: Re: [mythtv-users] X through PVR350 probs
>
> Hello again,
>
> Sorry for the flood of emails, but have fixed the config file and X
> starts up fine, and I can see something like a login box on my TV but
> it's all badly distorted, as the picture shows:
>
> http://www.biased.org/misc/pc270089.jpg
>
> Any ideas?
>
> Thanks very much again for your help
>
> Cheers - Piers
>
> John Harvey wrote:
> > Send me a copy of youre config file and the log file from start X.
> >
> > It may be easier to start with the 0.7 driver I posted on the ivtv-dev
> > mailing list about a week ago.
> >
> > John
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mythtv at biased

Dec 27, 2004, 9:10 AM

Post #12 of 27 (1731 views)
Permalink

Re: X through PVR350 probs [In reply to]

Yeah I'm in the PAL world.

I assume when you mean the "messages file" you mean the output made by
ivtv when it starts up in dmesg?

Not sure if I've already told you, but when I start saa7127 with the
test image, it works fine but I suspect it's in NTSC as the image comes
up as black and white on my temporary TV isn't NTSC or S-Video
compatiable, but when connected to my main TV which is NTSC and S-Video
compatiable, the test image comes up in colour, but it's the same when I
select composite or S-Video on the TV (tho S-Video looks a bit checked).

Anyway when I start saa7127 without the test image on either TV, it
shows the same image as in the picture I included in the previous email.

Thanks yet again

Cheers - Piers

John Harvey wrote:
> I'm assuming that you are in PAL world?
> If so I would guess that the driver isn't running properly in PAL.
> Either add std=2 (I think) to ivtv options or if that doesn't work post a
> link to your messages file and I'll take a look through it.
>
> John
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mythtv at biased

Dec 27, 2004, 10:35 AM

Post #13 of 27 (1749 views)
Permalink

Re: X through PVR350 probs [In reply to]

Hello again,

Have added "std=2" onto the modules.conf file (already have an
ivtv_std=2 there though) and no difference.

Here's the messages from dmesg (full dmesg is at www.biased.org/misc/dmesg)

=================================
i2c-core.o: driver saa7127 registered.
i2c-core.o: driver saa7115 registered.
i2c-core.o: driver i2c msp3400 driver registered.
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.3.2 (a) loading
ivtv: Linux version: 2.4.28-pk-20041225-2
ivtv: In case of problems please include the debug info
ivtv: between the START INIT IVTV and END INIT IVTV lines when
ivtv: mailing the ivtv-devel mailinglist.
ivtv: Autodetected WinTV PVR 350 card
ivtv: Found an iTVC15 based chip
ivtv: Unreasonably low latency timer, setting to 64 (was 32)
ivtv: VIA PCI device: 0x3123 vendor: 0x1106
tuner: chip found @ 0xc2
tuner(bttv): type forced to 1 (Philips PAL_I (FI1246 and compatibles))
[insmod]
ivtv: i2c attach [client=Philips PAL_I (FI1246 and compa,ok]
i2c-core.o: client [Philips PAL_I (FI1246 and compa] registered to
adapter [ivtv i2c driver #0](pos. 0).
saa7127: detecting saa7127 client on address 0x88
saa7127: Selecting NTSC video Standard
saa7127: Selecting S-Video+Composite
saa7127: Turn WSS off
saa7127: Widescreen Mode 4:3 Full Format
saa7127: Selecting Normal Encoder Input
saa7127: Enable Video Output
ivtv: i2c attach [client=saa7127[0],ok]
i2c-core.o: client [saa7127[0]] registered to adapter [ivtv i2c driver
#0](pos. 1).
saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005)
saa7115: detecting saa7115 client on address 0x42
saa7115: writing init values
ivtv: i2c attach [client=saa7115[0],ok]
i2c-core.o: client [saa7115[0]] registered to adapter [ivtv i2c driver
#0](pos. 2).
saa7115: status: (1E) 0x48, (1F) 0xc0
msp34xx: ivtv version
msp34xx: init: chip=MSP3418W-A2, has NICAM support, simple (D) mode,
simpler (G) no-thread mode
msp34xx: $Id$ compiled on: Dec 27 2004 10:25:22
ivtv: i2c attach [client=MSP3418W-A2,ok]
i2c-core.o: client [MSP3418W-A2] registered to adapter [ivtv i2c driver
#0](pos. 3).
i2c-core.o: adapter ivtv i2c driver #0 registered as adapter 0.
i2c-core.o: driver tveeprom registered.
tveeprom: Hauppauge: model = 48135, rev = J324, serial# = 7244636
tveeprom: tuner = Philips FM1246 (idx = 24, type = 1)
tveeprom: tuner fmt = PAL(I) (eeprom = 0x10, v4l2 = 0x00000010)
tveeprom: audio_processor = CS5331 (type = 9)
ivtv: i2c attach [client=tveeprom[0],ok]
i2c-core.o: client [tveeprom[0]] registered to adapter [ivtv i2c driver
#0](pos. 4).
ivtv: Tuner Type 1, Tuner formats 0x00000010, Radio: yes, Model
0x00a93494, Revision 0x00000001
ivtv: Radio detected
ivtv: Encoder revision: 0x02040011
ivtv: Decoder revision: 0x02020023
ivtv: Configuring WinTV PVR 350 card with 10 streams
ivtv: Create DMA stream 0 using 256 16384 byte buffers 4194304 kbytes total
ivtv: Registered v4l2 device, streamtype 0 minor 0
ivtv: Create DMA stream 1
ivtv: Registered v4l2 device, streamtype 1 minor 32
ivtv: Create stream 2 using 40 52224 byte buffers 2097152 kbytes total
ivtv: Registered v4l2 device, streamtype 2 minor 224
ivtv: Create DMA stream 3 using 455 4608 byte buffers 2097152 kbytes total
ivtv: Registered v4l2 device, streamtype 3 minor 24
ivtv: Create stream 4
ivtv: Registered v4l2 device, streamtype 4 minor 64
ivtv: Create DMA stream 5 using 16 65536 byte buffers 1048576 kbytes total
ivtv: Registered v4l2 device, streamtype 5 minor 16
ivtv: Create stream 6 using 1024 2048 byte buffers 262144 kbytes total
ivtv: Registered v4l2 device, streamtype 6 minor 228
ivtv: Create stream 7
ivtv: Registered v4l2 device, streamtype 7 minor 232
ivtv: Create DMA stream 8 using 6 103680 byte buffers 622080 kbytes total
ivtv: Registered v4l2 device, streamtype 8 minor 48
ivtv: Create DMA stream 9 using 32 65536 byte buffers 2097152 kbytes total
ivtv: ivtv_enc_thread: pid = 1109, itv = 0xde9ab740
ivtv: ivtv_dec_thread: pid = 1111, itv = 0xde9ab740
ivtv: Setting Tuner 5
tuner: type already set (1)
saa7115: decoder set input (4)
saa7115: now setting Composite input
ivtv: Setting audio matrix to input 3, output 1
ivtv: Switching standard to PAL.
saa7115: decoder set norm PAL
saa7115: set audio: 0x01
saa7127: Setting Encoder Video Standard
saa7127: Set PAL Video Mode
saa7127: Selecting PAL video Standard
ivtv: Initialized WinTV PVR 350, card #0
ivtv: ==================== END INIT IVTV ====================
i2c-core.o: client [saa7115[0]] unregistered.
i2c-core.o: driver unregistered: saa7115
saa7127: video encoder driver unloaded
i2c-core.o: client [saa7127[0]] unregistered.
i2c-core.o: driver unregistered: saa7127
ivtv: i2c client addr: 0x21 not found!
ivtv: i2c client addr: 0x21 not found!
ivtv: Setting audio matrix to input 1, output 1
ivtv: i2c client addr: 0x21 not found!
saa7127: video encoder driver version V 0.3 loaded
i2c-core.o: driver saa7127 registered.
saa7127: detecting saa7127 client on address 0x88
saa7127: Selecting NTSC video Standard
saa7127: Selecting S-Video+Composite
saa7127: Turn WSS off
saa7127: Widescreen Mode 4:3 Full Format
saa7127: Selecting Normal Encoder Input
saa7127: Enable Video Output
ivtv: i2c attach [client=saa7127[0],ok]
i2c-core.o: client [saa7127[0]] registered to adapter [ivtv i2c driver
#0](pos. 1).
i2c-core.o: driver saa7115 registered.
saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005)
saa7115: detecting saa7115 client on address 0x42
saa7115: writing init values
ivtv: i2c attach [client=saa7115[0],ok]
i2c-core.o: client [saa7115[0]] registered to adapter [ivtv i2c driver
#0](pos. 2).
saa7115: status: (1E) 0x48, (1F) 0xc0
ivtv-osd: Framebuffer module loaded (attached to ivtv card id 0)
ivtv-osd: Framebuffer is at decoder-relative address 0x00510000 and has
1704960 bytes.
ivtv-osd: screen coords: [0 0] -> [720 576]
ivtv-osd: original global alpha = 208
ivtv-osd: current OSD state = 39
ivtv-osd: new global alpha = 208 (1 255 0)
ivtv-osd: framebuffer at 0xdd510000, mapped to 0xdf75e000, size 1620k
ivtv-osd: mode is 720x576x32, linelength=2880
Console: switching to colour frame buffer device 90x36
ivtv-osd: fb0: iTVC15 TV out frame buffer device
=================================

Here is what is in my modules.conf file relating to ivtv:

=================================
alias char-major-81 videodev
alias char-major-81-0 ivtv
alias /dev/v4l ivtv
options saa7127 enable_output=1 output_select=0 pal=1
options ivtv ivtv_debug=1 ivtv_pal=1 tuner=5 ivtv_std=2 std=2
options tuner pal=1
options tuner type=1
options msp3400 once=1 simple=1
add below ivtv msp3400 saa7115 saa7127 tuner
add above ivtv ivtv-fb
post-install ivtv /usr/local/bin/test_ioctl -d /dev/video0 -u 0xff
=================================

Thanks again

Cheers - Piers

John Harvey wrote:
> I'm assuming that you are in PAL world?
> If so I would guess that the driver isn't running properly in PAL.
> Either add std=2 (I think) to ivtv options or if that doesn't work post a
> link to your messages file and I'll take a look through it.
>
> John
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mythtv at biased

Dec 27, 2004, 12:48 PM

Post #14 of 27 (1748 views)
Permalink

Re: X through PVR350 probs [In reply to]

I have removed everything from the modules.conf that I added in and it
works fine - both input and output is fine and in colour - fantastic
thank you very much!

But... when I start MythTV, start displaying live TV, it's extremely
jerky when taking in input via composite and outputting via composite as
well (probably 2 fps max with tearing in the middle, coupled with
slightly poor image quality) and "top" shows 80% to 100% cpu load - any
ideas?

Also I note a large bit of the desktop is cut off by the TV on all sides
by quite a big margin - is this related?

Thanks very much for your help again

Cheers - Piers

John Harvey wrote:
> I would remove all the options in that case.
> I don't have any and my X starts up in PAL mode properly. So I would start
> with that.
> One of these old options may well be causing some bad side effect.
>
> For some reason the 7127 is selecting NTSC playback
>
>
>>saa7127: Selecting NTSC video Standard
>
>
> So that is your problem.
>
> John

john.p.harvey at btinternet

Dec 27, 2004, 12:54 PM

Post #15 of 27 (1733 views)
Permalink

RE: X through PVR350 probs [In reply to]

Sounds like you don't have the use 350 option set in the tv playback
options.

The frame buffer is 720 x 576 the tv displays something like 640 x 480 so
yes there is quite a lot missing. There are a few workarounds until I get
round to fixing something properly.

1) Use a window manager to set a virtual desktop
2) set the overscan options in myth

I use the 2nd with no window manager at the moment. It works ok.
The OSD display however for play/pause/channel change etc. currently ignores
the overscan settings which I might get round to looking at one day.

John

> -----Original Message-----
> From: Piers Kittel [mailto:mythtv [at] biased]
> Sent: 27 December 2004 20:48
> To: John Harvey; Discussion about mythtv
> Subject: Re: [mythtv-users] X through PVR350 probs
>
> I have removed everything from the modules.conf that I added in and it
> works fine - both input and output is fine and in colour - fantastic
> thank you very much!
>
> But... when I start MythTV, start displaying live TV, it's extremely
> jerky when taking in input via composite and outputting via composite as
> well (probably 2 fps max with tearing in the middle, coupled with
> slightly poor image quality) and "top" shows 80% to 100% cpu load - any
> ideas?
>
> Also I note a large bit of the desktop is cut off by the TV on all sides
> by quite a big margin - is this related?
>
> Thanks very much for your help again
>
> Cheers - Piers
>
> John Harvey wrote:
> > I would remove all the options in that case.
> > I don't have any and my X starts up in PAL mode properly. So I would
> start
> > with that.
> > One of these old options may well be causing some bad side effect.
> >
> > For some reason the 7127 is selecting NTSC playback
> >
> >
> >>saa7127: Selecting NTSC video Standard
> >
> >
> > So that is your problem.
> >
> > John

mythtv at biased

Dec 27, 2004, 1:48 PM

Post #16 of 27 (1749 views)
Permalink

Re: X through PVR350 probs [In reply to]

John,

> Sounds like you don't have the use 350 option set in the tv playback
> options.

Aha - fixed it now. Great - thanks!

One thing - I found that after several minutes of watching TV, it would
suddenly show a hue - blue one currently.

Plus moving the mouse would show black bars to be shown and it cannot be
removed unless I go back to the main menu and then go back to viewing
the TV and it'll be fine?

Thanks very much for your help again

Cheers - Piers

john.p.harvey at btinternet

Dec 27, 2004, 2:38 PM

Post #17 of 27 (1725 views)
Permalink

RE: X through PVR350 probs [In reply to]

Not sure about the black bars.
Moving the mouse shouldn't show anything while watching tv since the
mouse should be hidden while running myth.

I would try running without a window manager since it sounds like something
is making x draw to the screen for some reason.

John

> -----Original Message-----
> From: Piers Kittel [mailto:mythtv [at] biased]
> Sent: 27 December 2004 21:49
> To: John Harvey
> Cc: 'Discussion about mythtv'
> Subject: Re: [mythtv-users] X through PVR350 probs
>
> John,
>
> > Sounds like you don't have the use 350 option set in the tv playback
> > options.
>
> Aha - fixed it now. Great - thanks!
>
> One thing - I found that after several minutes of watching TV, it would
> suddenly show a hue - blue one currently.
>
> Plus moving the mouse would show black bars to be shown and it cannot be
> removed unless I go back to the main menu and then go back to viewing
> the TV and it'll be fine?
>
> Thanks very much for your help again
>
> Cheers - Piers

mythtv at biased

Dec 27, 2004, 2:47 PM

Post #18 of 27 (1747 views)
Permalink

Re: X through PVR350 probs [In reply to]

OK, how do I run it without using a windowmanager? It does sound like a
better idea anyway.

Any ideas about the blue tint?

Thanks again

Cheers - Piers

John Harvey wrote:
> Not sure about the black bars.
> Moving the mouse shouldn't show anything while watching tv since the
> mouse should be hidden while running myth.
>
> I would try running without a window manager since it sounds like something
> is making x draw to the screen for some reason.
>
> John

ijr at case

Dec 27, 2004, 5:17 PM

Post #19 of 27 (1745 views)
Permalink

Re: X through PVR350 probs [In reply to]

On Monday 27 December 2004 03:54 pm, John Harvey wrote:
> The OSD display however for play/pause/channel change etc. currently
> ignores the overscan settings which I might get round to looking at one
> day.

Separate setting in the playback options.

Isaac
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

sschaefer1 at woh

Dec 28, 2004, 10:08 AM

Post #20 of 27 (1705 views)
Permalink

Re: X through PVR350 probs [In reply to]

I run MythTV without a window manager by calling a seperate script for starting X on the PVR-350's tv out port (since I run a regular X session on my VGA card).
Notice that I "exec" mythfrontend rather than a window manager like Gnome or KDE

root [at] hos:~# cat startX
#!/bin/sh
xinit /root/startXrc -- /usr/X11R6/bin/Xorg :1 vt12 -layout "Hauppauge Layout"

root [at] hos:~# cat startXrc
#!/bin/sh
mythbackend --daemon --logfile /home/www/data/PVR/backend.log
exec mythfrontend

----- Original Message -----
From: Piers Kittel <mythtv [at] biased>
Date: Monday, December 27, 2004 5:47 pm
Subject: Re: [mythtv-users] X through PVR350 probs

> OK, how do I run it without using a windowmanager? It does sound
> like a
> better idea anyway.
>
> Any ideas about the blue tint?
>
> Thanks again
>
> Cheers - Piers
>
> John Harvey wrote:
> > Not sure about the black bars.
> > Moving the mouse shouldn't show anything while watching tv
> since the
> > mouse should be hidden while running myth.
> >
> > I would try running without a window manager since it sounds
> like something
> > is making x draw to the screen for some reason.
> >
> > John
>

mythtv at biased

Dec 28, 2004, 11:00 AM

Post #21 of 27 (1710 views)
Permalink

Re: X through PVR350 probs [In reply to]

Hello,

Thanks for that,

Just 2 probs:

1) How did you get both X sessions (PVR and VGA) to run at the same
time? I found while using your mehod, the VGA part would shut down, and
the image would come up on the TV, then when I exit MythTV, the monitor
would come back on exactly where I was before?

2) How do you get the PVR to run without keyboard/mouse as when I ran X
for the PVR, it wouldn't start without the keyboard and mouse?

Thanks very much for your help

Cheers - Piers

sschaefer1 [at] woh wrote:
> I run MythTV without a window manager by calling a seperate script for starting X on the PVR-350's tv out port (since I run a regular X session on my VGA card).
> Notice that I "exec" mythfrontend rather than a window manager like Gnome or KDE
>
> root [at] hos:~# cat startX
> #!/bin/sh
> xinit /root/startXrc -- /usr/X11R6/bin/Xorg :1 vt12 -layout "Hauppauge Layout"
>
> root [at] hos:~# cat startXrc
> #!/bin/sh
> mythbackend --daemon --logfile /home/www/data/PVR/backend.log
> exec mythfrontend
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

gaberubin at gmail

Dec 28, 2004, 12:12 PM

Post #22 of 27 (1744 views)
Permalink

Re: X through PVR350 probs [In reply to]

>
> 2) How do you get the PVR to run without keyboard/mouse as when I ran X
> for the PVR, it wouldn't start without the keyboard and mouse?

I hadf problems with not plugging a mouse in till I changed my mouse
section to this in my XF86.config file:

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/null"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection

I don't think I did anything special to my keyboard portion (I have
none plugged in), it looks like this:

Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

sschaefer1 at woh

Dec 28, 2004, 12:35 PM

Post #23 of 27 (1733 views)
Permalink

Re: X through PVR350 probs [In reply to]

Maybe I'm mistaken but your solution here only covers not having a keyboard/mouse correct?

The question as I understood it from Piers is how to have the frontend on the PVR-350 tv out and have a normal X session running.

I wrote it all down in a webpage, http://www.schaefer.dhcp.biz/pvr350tvout.htm

don't remember the specifics at the moment, basically you use the dummy drivers for the PVR350 session, so you have a keyboard/mouse left over for the normal X session, which you have to switch virtual consoles before you start the normal session.

----- Original Message -----
From: Gabe Rubin <gaberubin [at] gmail>
Date: Tuesday, December 28, 2004 3:12 pm
Subject: Re: [mythtv-users] X through PVR350 probs

> >
> > 2) How do you get the PVR to run without keyboard/mouse as when
> I ran X
> > for the PVR, it wouldn't start without the keyboard and mouse?
>
>
> I hadf problems with not plugging a mouse in till I changed my mouse
> section to this in my XF86.config file:
>
> Section "InputDevice"
> Identifier "Mouse0"
> Driver "mouse"
> Option "Protocol" "IMPS/2"
> Option "Device" "/dev/null"
> Option "ZAxisMapping" "4 5"
> Option "Emulate3Buttons" "no"
> EndSection
>
> I don't think I did anything special to my keyboard portion (I have
> none plugged in), it looks like this:
>
> Section "InputDevice"
> Identifier "Keyboard0"
> Driver "keyboard"
> Option "XkbRules" "xfree86"
> Option "XkbModel" "pc105"
> Option "XkbLayout" "us"
> EndSection
>

sschaefer1 at woh

Dec 28, 2004, 1:38 PM

Post #24 of 27 (1726 views)
Permalink

Re: X through PVR350 probs [In reply to]

I don't think I explained it well enough.. but keep in mind that when you start an X session that will lock up a virtual console, so before you can start a second X session you will need to switch to a different virtual console. Also, a X server will register itself as a particular :X display... so you will need to specify (probably with the PVR 350's session to use maybe :1) the display.

I haven't had time to finish that page of mine, which the stuff I mention here is what is missing. I've thought to check out the VNC server / Xvnc to see how it works, it doesn't lock up a virtual terminal, but it does behave as a display device (even thought it is a virtual display).

----- Original Message -----
From: sschaefer1 [at] woh
Date: Tuesday, December 28, 2004 3:35 pm
Subject: Re: [mythtv-users] X through PVR350 probs

> Maybe I'm mistaken but your solution here only covers not having a
> keyboard/mouse correct?
>
> The question as I understood it from Piers is how to have the
> frontend on the PVR-350 tv out and have a normal X session running.
>
> I wrote it all down in a webpage,
> http://www.schaefer.dhcp.biz/pvr350tvout.htm
> don't remember the specifics at the moment, basically you use the
> dummy drivers for the PVR350 session, so you have a keyboard/mouse
> left over for the normal X session, which you have to switch
> virtual consoles before you start the normal session.
>
> ----- Original Message -----
> From: Gabe Rubin <gaberubin [at] gmail>
> Date: Tuesday, December 28, 2004 3:12 pm
> Subject: Re: [mythtv-users] X through PVR350 probs
>
> > >
> > > 2) How do you get the PVR to run without keyboard/mouse as
> when
> > I ran X
> > > for the PVR, it wouldn't start without the keyboard and mouse?
> >
> >
> > I hadf problems with not plugging a mouse in till I changed my mouse
> > section to this in my XF86.config file:
> >
> > Section "InputDevice"
> > Identifier "Mouse0"
> > Driver "mouse"
> > Option "Protocol" "IMPS/2"
> > Option "Device" "/dev/null"
> > Option "ZAxisMapping" "4 5"
> > Option "Emulate3Buttons" "no"
> > EndSection
> >
> > I don't think I did anything special to my keyboard portion (I have
> > none plugged in), it looks like this:
> >
> > Section "InputDevice"
> > Identifier "Keyboard0"
> > Driver "keyboard"
> > Option "XkbRules" "xfree86"
> > Option "XkbModel" "pc105"
> > Option "XkbLayout" "us"
> > EndSection
> >
>
>

mythtv at biased

Dec 28, 2004, 1:59 PM

Post #25 of 27 (1719 views)
Permalink

Re: X through PVR350 probs [In reply to]

Hello again,

Very good guide, but my prob is that when I start up with no window
manager at all, I then do an "startX" (following your guide) and then
switch to a different virtual console (both times via SSH tho) and do an
"startx" - the original display vanishes and the other display loads up
the desktop. When I exit the windowmanager on the monitor, the original
windowmanager (i.e. MythTV) pops back up. Trying to do it the other way
round has the same result but vice versa.

Cheers - Piers

sschaefer1 [at] woh wrote:
> I don't think I explained it well enough.. but keep in mind that when you start an X session that will lock up a virtual console, so before you can start a second X session you will need to switch to a different virtual console. Also, a X server will register itself as a particular :X display... so you will need to specify (probably with the PVR 350's session to use maybe :1) the display.
>
> I haven't had time to finish that page of mine, which the stuff I mention here is what is missing. I've thought to check out the VNC server / Xvnc to see how it works, it doesn't lock up a virtual terminal, but it does behave as a display device (even thought it is a virtual display).
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

1 2

View All

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads