Author Topic: Starting help for rusty Mythtv user ...  (Read 8890 times)

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Starting help for rusty Mythtv user ...
« on: April 24, 2005, 08:49:29 pm »
Hi,

I have mythtv server at home that ran 0.15 version. Right now I'm trying to set up newer system with Pluto & Mythtv and would like to get mythtv functionality at least to PVR working state...

I'd kindly ask for some quick guidance, since I guess my mythtv skills are a bit rusty..

- how do you deal with setting up recordings ? I've installed mythweb additionaly, but don't know if I must set it up...

- can recordings or live TV be watched on MD ?

- can TV guide be handled through GUI interfaces ?

- any other tips for mythtv under Pluto ?


Regards,

Rob.

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
MythTV in pluto.
« Reply #1 on: April 25, 2005, 11:33:48 am »
Hi Rob,

 In Pluto you should be able to do the same things you are able to do when using the mythfronted as a standalone application. This means you can schedule recording and  handle tv guide, etc from the mythfrontend application. The guide and schedule recording (albeit simpler) are also accessible from the pluto interfaces (the tablet and the phone).

 The MD will play any movie which is stored in the /home/public/data/videos/ folder ( and subfolders ) and is playable by xine. This means that anything which can be transcoded to a xine acceptable format and stored there will be  played.

  There is currently no script to automatically transcode a recorded show from myth format to something that xine can play ( you can still watch the show from the mythfrontend interface thou ).

Sincerely,
  ToMiC
[/list]

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Starting help for rusty Mythtv user ...
« Reply #2 on: April 27, 2005, 01:00:21 am »
Hi,

I'm having some problems setting up mythtv. I have pvr 350 card and this in logs:

Code: newbielink:javascript:void(0); [nonactive]

Apr 27 00:00:09 dcerouter kernel: ivtv: ==================== START INIT IVTV ====================
Apr 27 00:00:09 dcerouter kernel: ivtv: version 0.2.0 (rc3f) loading
Apr 27 00:00:09 dcerouter kernel: ivtv: Linux version: 2.6.10-1-686 preempt 686 gcc-3.3
Apr 27 00:00:09 dcerouter kernel: ivtv: In case of problems please include the debug info
Apr 27 00:00:09 dcerouter kernel: ivtv: between the START INIT IVTV and END INIT IVTV lines when
Apr 27 00:00:09 dcerouter kernel: ivtv: mailing the ivtv-devel mailinglist.
Apr 27 00:00:09 dcerouter kernel: ivtv: Autodetected WinTV PVR 350 card
Apr 27 00:00:09 dcerouter kernel: ivtv: Found an iTVC15 based chip
Apr 27 00:00:09 dcerouter kernel: ACPI: PCI interrupt 0000:02:0a.0[A] -> GSI 22 (level, low) -> IRQ 209
Apr 27 00:00:09 dcerouter kernel: ivtv: XXX PCI device: 0x2570 vendor: 0x8086
Apr 27 00:00:10 dcerouter kernel: tveeprom: Hauppauge: model = 48134, rev = J342, serial# = 6564762
Apr 27 00:00:10 dcerouter kernel: tveeprom: tuner = Temic 4009FR5 (idx = 42, type = 20)
Apr 27 00:00:10 dcerouter kernel: tveeprom: tuner fmt = PAL(B/G) (eeprom = 0x04, v4l2 = 0x00000007)
Apr 27 00:00:10 dcerouter kernel: tveeprom: audio_processor = CS5331 (type = 9)
Apr 27 00:00:10 dcerouter kernel: ivtv: i2c attach [client=tveeprom[4],ok]
Apr 27 00:00:10 dcerouter kernel: ivtv: Tuner Type 20, Tuner formats 0x00000007, Radio: yes, Model 0x00a93512, Revision 0x00000001
Apr 27 00:00:10 dcerouter kernel: ivtv: PAL tuner detected
Apr 27 00:00:10 dcerouter kernel: ivtv: Radio detected
Apr 27 00:00:10 dcerouter kernel: tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
Apr 27 00:00:10 dcerouter kernel: ivtv: i2c attach [client=(tuner unset),ok]
Apr 27 00:00:10 dcerouter kernel: saa7115: starting probe for adapter bt878 #0 [sw] (0x10005)
Apr 27 00:00:10 dcerouter kernel: saa7115: starting probe for adapter bt878 #1 [sw] (0x10005)
Apr 27 00:00:10 dcerouter kernel: saa7115: starting probe for adapter bt878 #2 [sw] (0x10005)
Apr 27 00:00:10 dcerouter kernel: saa7115: starting probe for adapter bt878 #3 [sw] (0x10005)
Apr 27 00:00:10 dcerouter kernel: saa7115: starting probe for adapter SMBus I801 adapter at 0400 (0x0)
Apr 27 00:00:10 dcerouter kernel: saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005)
Apr 27 00:00:10 dcerouter kernel: saa7115: detecting saa7115 client on address 0x42
Apr 27 00:00:10 dcerouter kernel: saa7115: writing init values
Apr 27 00:00:10 dcerouter kernel: ivtv: i2c attach [client=saa7115[0],ok]
Apr 27 00:00:10 dcerouter kernel: saa7115: status: (1E) 0x48, (1F) 0xc0
Apr 27 00:00:11 dcerouter kernel: saa7127: video encoder driver version V 0.3 loaded
Apr 27 00:00:11 dcerouter kernel: saa7127: Selecting NTSC video Standard
Apr 27 00:00:11 dcerouter kernel: saa7127: Selecting S-Video+Composite
Apr 27 00:00:11 dcerouter kernel: saa7127: Turn WSS off
Apr 27 00:00:11 dcerouter kernel: saa7127: Widescreen Mode 4:3 Full Format
Apr 27 00:00:11 dcerouter kernel: saa7127: Selecting Normal Encoder Input
Apr 27 00:00:11 dcerouter kernel: saa7127: Enable Video Output
Apr 27 00:00:11 dcerouter kernel: saa7127: Selecting NTSC video Standard
Apr 27 00:00:11 dcerouter kernel: saa7127: Selecting S-Video+Composite
Apr 27 00:00:11 dcerouter kernel: saa7127: Turn WSS off
Apr 27 00:00:11 dcerouter kernel: saa7127: Widescreen Mode 4:3 Full Format
Apr 27 00:00:11 dcerouter kernel: saa7127: Selecting Normal Encoder Input
Apr 27 00:00:11 dcerouter kernel: saa7127: Enable Video Output
Apr 27 00:00:11 dcerouter kernel: ivtv: i2c attach [client=saa7127[1],ok]
Apr 27 00:00:11 dcerouter kernel: msp34xx: ivtv version
Apr 27 00:00:11 dcerouter kernel: msp34xx: init: chip=MSP3418W-A2, has NICAM support, simple (D) mode, simpler (G) no-thread mode
Apr 27 00:00:11 dcerouter kernel: msp34xx: $Id$ compiled on: Apr 14 2005 14:09:47
Apr 27 00:00:11 dcerouter kernel: ivtv: i2c attach [client=MSP3418W-A2,ok]
Apr 27 00:00:12 dcerouter kernel: ivtv: Encoder revision: 0x02040011
Apr 27 00:00:12 dcerouter kernel: ivtv: Decoder revision: 0x02020023
Apr 27 00:00:12 dcerouter kernel: ivtv: Configuring WinTV PVR 350 card with 9 streams
Apr 27 00:00:12 dcerouter kernel: ivtv: Create DMA stream 0 using 256 16384 byte buffers  4194304 kbytes total
Apr 27 00:00:12 dcerouter kernel: ivtv: Registered v4l2 device, streamtype 0 minor 4
Apr 27 00:00:12 dcerouter kernel: ivtv: Create DMA stream 1
Apr 27 00:00:12 dcerouter kernel: ivtv: Registered v4l2 device, streamtype 1 minor 32
Apr 27 00:00:12 dcerouter kernel: ivtv: Create stream 2 using 40 52224 byte buffers  2097152 kbytes total
Apr 27 00:00:12 dcerouter kernel: modprobe: page allocation failure. order:4, mode:0xd0
Apr 27 00:00:12 dcerouter kernel:  [__alloc_pages+450/880] __alloc_pages+0x1c2/0x370
Apr 27 00:00:12 dcerouter kernel:  [__get_free_pages+37/64] __get_free_pages+0x25/0x40
Apr 27 00:00:12 dcerouter kernel:  [kmem_getpages+34/192] kmem_getpages+0x22/0xc0
Apr 27 00:00:12 dcerouter kernel:  [cache_grow+185/384] cache_grow+0xb9/0x180
Apr 27 00:00:12 dcerouter kernel:  [cache_alloc_refill+371/544] cache_alloc_refill+0x173/0x220
Apr 27 00:00:12 dcerouter kernel:  [__kmalloc+116/128] __kmalloc+0x74/0x80
Apr 27 00:00:12 dcerouter kernel:  [pg0+550075245/1069863936] ivtv_init_buffer+0x3d/0x1d0 [ivtv]
Apr 27 00:00:12 dcerouter kernel:  [pg0+550075706/1069863936] ivtv_init_queue_nolock+0x3a/0x80 [ivtv]
Apr 27 00:00:12 dcerouter kernel:  [pg0+550075863/1069863936] ivtv_init_queues_nolock+0x57/0x90 [ivtv]
Apr 27 00:00:12 dcerouter kernel:  [pg0+550100201/1069863936] ivtv_stream_init+0x389/0x4e0 [ivtv]
Apr 27 00:00:12 dcerouter kernel:  [pg0+550100929/1069863936] ivtv_streams_setup+0x181/0x3a0 [ivtv]
Apr 27 00:00:12 dcerouter kernel:  [pg0+550085117/1069863936] ivtv_probe+0x24d/0x960 [ivtv]
Apr 27 00:00:12 dcerouter kernel:  [pci_device_probe_static+82/112] pci_device_probe_static+0x52/0x70
Apr 27 00:00:12 dcerouter kernel:  [__pci_device_probe+60/80] __pci_device_probe+0x3c/0x50
Apr 27 00:00:12 dcerouter kernel:  [pci_device_probe+44/80] pci_device_probe+0x2c/0x50
Apr 27 00:00:12 dcerouter kernel:  [driver_probe_device+47/128] driver_probe_device+0x2f/0x80
Apr 27 00:00:12 dcerouter kernel:  [driver_attach+92/160] driver_attach+0x5c/0xa0
Apr 27 00:00:12 dcerouter kernel:  [bus_add_driver+157/208] bus_add_driver+0x9d/0xd0
Apr 27 00:00:12 dcerouter kernel:  [driver_register+47/64] driver_register+0x2f/0x40
Apr 27 00:00:12 dcerouter kernel:  [pci_register_driver+100/144] pci_register_driver+0x64/0x90
Apr 27 00:00:12 dcerouter kernel:  [pg0+550088172/1069863936] module_start+0xcc/0x1f0 [ivtv]
Apr 27 00:00:12 dcerouter kernel:  [sys_init_module+355/528] sys_init_module+0x163/0x210
Apr 27 00:00:12 dcerouter kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
Apr 27 00:00:13 dcerouter kernel: ivtv: Registered v4l2 device, streamtype 2 minor 228
Apr 27 00:00:13 dcerouter kernel: ivtv: Create DMA stream 3 using 455 4608 byte buffers  2097152 kbytes total
Apr 27 00:00:13 dcerouter kernel: modprobe: page allocation failure. order:5, mode:0xd0
Apr 27 00:00:13 dcerouter kernel:  [__alloc_pages+450/880] __alloc_pages+0x1c2/0x370
Apr 27 00:00:13 dcerouter kernel:  [__get_free_pages+37/64] __get_free_pages+0x25/0x40
Apr 27 00:00:13 dcerouter kernel:  [kmem_getpages+34/192] kmem_getpages+0x22/0xc0
Apr 27 00:00:13 dcerouter kernel:  [cache_grow+185/384] cache_grow+0xb9/0x180
Apr 27 00:00:13 dcerouter kernel:  [cache_alloc_refill+371/544] cache_alloc_refill+0x173/0x220
Apr 27 00:00:13 dcerouter kernel:  [__kmalloc+116/128] __kmalloc+0x74/0x80
Apr 27 00:00:13 dcerouter kernel:  [pg0+550099834/1069863936] ivtv_stream_init+0x21a/0x4e0 [ivtv]
Apr 27 00:00:13 dcerouter kernel:  [pg0+550100983/1069863936] ivtv_streams_setup+0x1b7/0x3a0 [ivtv]
Apr 27 00:00:13 dcerouter kernel:  [pg0+550085117/1069863936] ivtv_probe+0x24d/0x960 [ivtv]
Apr 27 00:00:13 dcerouter kernel:  [pci_device_probe_static+82/112] pci_device_probe_static+0x52/0x70
Apr 27 00:00:13 dcerouter kernel:  [__pci_device_probe+60/80] __pci_device_probe+0x3c/0x50
Apr 27 00:00:13 dcerouter kernel:  [pci_device_probe+44/80] pci_device_probe+0x2c/0x50
Apr 27 00:00:13 dcerouter kernel:  [driver_probe_device+47/128] driver_probe_device+0x2f/0x80
Apr 27 00:00:13 dcerouter kernel:  [driver_attach+92/160] driver_attach+0x5c/0xa0
Apr 27 00:00:13 dcerouter kernel:  [bus_add_driver+157/208] bus_add_driver+0x9d/0xd0
Apr 27 00:00:13 dcerouter kernel:  [driver_register+47/64] driver_register+0x2f/0x40
Apr 27 00:00:13 dcerouter kernel:  [pci_register_driver+100/144] pci_register_driver+0x64/0x90
Apr 27 00:00:13 dcerouter kernel:  [pg0+550088172/1069863936] module_start+0xcc/0x1f0 [ivtv]
Apr 27 00:00:13 dcerouter kernel:  [sys_init_module+355/528] sys_init_module+0x163/0x210
Apr 27 00:00:13 dcerouter kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
Apr 27 00:00:13 dcerouter kernel: ivtv: Create stream 4
Apr 27 00:00:13 dcerouter kernel: ivtv: Registered v4l2 device, streamtype 4 minor 64
Apr 27 00:00:13 dcerouter kernel: ivtv: Create DMA stream 5 using 16 65536 byte buffers  1048576 kbytes total
Apr 27 00:00:13 dcerouter kernel: modprobe: page allocation failure. order:4, mode:0xd0
Apr 27 00:00:13 dcerouter kernel:  [__alloc_pages+450/880] __alloc_pages+0x1c2/0x370
Apr 27 00:00:13 dcerouter kernel:  [__get_free_pages+37/64] __get_free_pages+0x25/0x40
Apr 27 00:00:13 dcerouter kernel:  [kmem_getpages+34/192] kmem_getpages+0x22/0xc0
Apr 27 00:00:13 dcerouter kernel:  [cache_grow+185/384] cache_grow+0xb9/0x180
Apr 27 00:00:13 dcerouter kernel:  [cache_alloc_refill+371/544] cache_alloc_refill+0x173/0x220
Apr 27 00:00:13 dcerouter kernel:  [__kmalloc+116/128] __kmalloc+0x74/0x80
Apr 27 00:00:13 dcerouter kernel:  [pg0+550075245/1069863936] ivtv_init_buffer+0x3d/0x1d0 [ivtv]
Apr 27 00:00:13 dcerouter kernel:  [pg0+550075706/1069863936] ivtv_init_queue_nolock+0x3a/0x80 [ivtv]
Apr 27 00:00:13 dcerouter kernel:  [pg0+550075863/1069863936] ivtv_init_queues_nolock+0x57/0x90 [ivtv]
Apr 27 00:00:13 dcerouter kernel:  [pg0+550100201/1069863936] ivtv_stream_init+0x389/0x4e0 [ivtv]
Apr 27 00:00:13 dcerouter kernel:  [pg0+550101102/1069863936] ivtv_streams_setup+0x22e/0x3a0 [ivtv]
Apr 27 00:00:13 dcerouter kernel:  [pg0+550085117/1069863936] ivtv_probe+0x24d/0x960 [ivtv]
Apr 27 00:00:13 dcerouter kernel:  [pci_device_probe_static+82/112] pci_device_probe_static+0x52/0x70
Apr 27 00:00:13 dcerouter kernel:  [__pci_device_probe+60/80] __pci_device_probe+0x3c/0x50
Apr 27 00:00:13 dcerouter kernel:  [pci_device_probe+44/80] pci_device_probe+0x2c/0x50
Apr 27 00:00:13 dcerouter kernel:  [driver_probe_device+47/128] driver_probe_device+0x2f/0x80
Apr 27 00:00:13 dcerouter kernel:  [driver_attach+92/160] driver_attach+0x5c/0xa0
Apr 27 00:00:13 dcerouter kernel:  [bus_add_driver+157/208] bus_add_driver+0x9d/0xd0
Apr 27 00:00:13 dcerouter kernel:  [driver_register+47/64] driver_register+0x2f/0x40
Apr 27 00:00:13 dcerouter kernel:  [pci_register_driver+100/144] pci_register_driver+0x64/0x90
Apr 27 00:00:13 dcerouter kernel:  [pg0+550088172/1069863936] module_start+0xcc/0x1f0 [ivtv]
Apr 27 00:00:13 dcerouter kernel:  [sys_init_module+355/528] sys_init_module+0x163/0x210
Apr 27 00:00:13 dcerouter kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
Apr 27 00:00:13 dcerouter kernel: ivtv: Registered v4l2 device, streamtype 5 minor 16
Apr 27 00:00:13 dcerouter kernel: ivtv: Create stream 6 using 1024 2048 byte buffers  262144 kbytes total
Apr 27 00:00:13 dcerouter kernel: ivtv: Registered v4l2 device, streamtype 6 minor 229
Apr 27 00:00:13 dcerouter kernel: ivtv: Create stream 7
Apr 27 00:00:13 dcerouter kernel: ivtv: Registered v4l2 device, streamtype 7 minor 232
Apr 27 00:00:13 dcerouter kernel: ivtv: Create DMA stream 8
Apr 27 00:00:13 dcerouter kernel: ivtv: Registered v4l2 device, streamtype 8 minor 48
Apr 27 00:00:13 dcerouter kernel: ivtv-iTVC15_16_mpg2_encoder_card: probe of 0000:02:0a.0 failed with error -12
Apr 27 00:00:13 dcerouter kernel: ivtv: ====================  END INIT IVTV  ====================


Is anything wrong in this log (modprobe: page allocation failure doesn't look pretty to me)?

Does this make PVR card /dev/video4 for mythtv-setup ?

Is Composite0 default input showing on PVR 350 ?


I just cannot get mythtv-setup to finish its job properly...

Thanks in advance,

regards,

Rob.

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Starting help for rusty Mythtv user ...
« Reply #3 on: April 27, 2005, 09:33:59 am »
Hi,

Does this happend all the time ? Even after clean reboot ? Do you have any other cards inside the system ?

We had this at some point when loading the modules by hand but usually the drivers loaded properly on a reboot.

Sincerely,
   ToMiC

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Starting help for rusty Mythtv user ...
« Reply #4 on: April 27, 2005, 04:58:44 pm »
Quote from: "mihai.t"
Hi,

Does this happend all the time ? Even after clean reboot ? Do you have any other cards inside the system ?

We had this at some point when loading the modules by hand but usually the drivers loaded properly on a reboot.

Sincerely,
   ToMiC


I've read somewhere to put this

vm.min_free_kbytes=16384

in /etc/sysctl.conf and it helped. I guess it has to do with amount of free memory...

Now it looks more clean:


Code: newbielink:javascript:void(0); [nonactive]


Apr 27 10:01:35 dcerouter kernel: ivtv: ==================== START INIT IVTV ====================
Apr 27 10:01:36 dcerouter kernel: ivtv: version 0.2.0 (rc3f) loading
Apr 27 10:01:36 dcerouter kernel: ivtv: Linux version: 2.6.10-1-686 preempt 686 gcc-3.3
Apr 27 10:01:36 dcerouter kernel: ivtv: In case of problems please include the debug info
Apr 27 10:01:36 dcerouter kernel: ivtv: between the START INIT IVTV and END INIT IVTV lines when
Apr 27 10:01:36 dcerouter kernel: ivtv: mailing the ivtv-devel mailinglist.
Apr 27 10:01:36 dcerouter kernel: ivtv: Autodetected WinTV PVR 350 card
Apr 27 10:01:36 dcerouter kernel: ivtv: Found an iTVC15 based chip
Apr 27 10:01:36 dcerouter kernel: ivtv: XXX PCI device: 0x2570 vendor: 0x8086
Apr 27 10:01:36 dcerouter kernel: ivtv: i2c attach [client=tveeprom[4],ok]
Apr 27 10:01:36 dcerouter kernel: ivtv: Tuner Type 20, Tuner formats 0x00000007, Radio: yes, Model 0x00a93512, Revision 0x00000001
Apr 27 10:01:36 dcerouter kernel: ivtv: PAL tuner detected
Apr 27 10:01:36 dcerouter kernel: ivtv: Radio detected
Apr 27 10:01:36 dcerouter kernel: tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
Apr 27 10:01:36 dcerouter kernel: ivtv: i2c attach [client=(tuner unset),ok]
Apr 27 10:01:36 dcerouter kernel: saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005)
Apr 27 10:01:36 dcerouter kernel: ivtv: i2c attach [client=saa7115[0],ok]
Apr 27 10:01:37 dcerouter kernel: ivtv: i2c attach [client=saa7127[1],ok]
Apr 27 10:01:37 dcerouter kernel: msp34xx: ivtv version
Apr 27 10:01:37 dcerouter kernel: ivtv: i2c attach [client=MSP3418W-A2,ok]
Apr 27 10:01:38 dcerouter kernel: ivtv: Encoder revision: 0x02040011
Apr 27 10:01:38 dcerouter kernel: ivtv: Decoder revision: 0x02020023
Apr 27 10:01:38 dcerouter kernel: ivtv: Configuring WinTV PVR 350 card with 9 streams
Apr 27 10:01:38 dcerouter kernel: ivtv: Create DMA stream 0 using 256 16384 byte buffers  4194304 kbytes total
Apr 27 10:01:38 dcerouter kernel: ivtv: Registered v4l2 device, streamtype 0 minor 4
Apr 27 10:01:38 dcerouter kernel: ivtv: Create DMA stream 1
Apr 27 10:01:38 dcerouter kernel: ivtv: Registered v4l2 device, streamtype 1 minor 32
Apr 27 10:01:38 dcerouter kernel: ivtv: Create stream 2 using 40 52224 byte buffers  2097152 kbytes total
Apr 27 10:01:38 dcerouter kernel: ivtv: Registered v4l2 device, streamtype 2 minor 228
Apr 27 10:01:38 dcerouter kernel: ivtv: Create DMA stream 3 using 455 4608 byte buffers  2097152 kbytes total
Apr 27 10:01:38 dcerouter kernel: ivtv: Registered v4l2 device, streamtype 3 minor 24
Apr 27 10:01:38 dcerouter kernel: ivtv: Create stream 4
Apr 27 10:01:38 dcerouter kernel: ivtv: Registered v4l2 device, streamtype 4 minor 64
Apr 27 10:01:38 dcerouter kernel: ivtv: Create DMA stream 5 using 16 65536 byte buffers  1048576 kbytes total
Apr 27 10:01:38 dcerouter kernel: ivtv: Registered v4l2 device, streamtype 5 minor 16
Apr 27 10:01:38 dcerouter kernel: ivtv: Create stream 6 using 1024 2048 byte buffers  262144 kbytes total
Apr 27 10:01:38 dcerouter kernel: ivtv: Registered v4l2 device, streamtype 6 minor 229
Apr 27 10:01:38 dcerouter kernel: ivtv: Create stream 7
Apr 27 10:01:38 dcerouter kernel: ivtv: Registered v4l2 device, streamtype 7 minor 232
Apr 27 10:01:38 dcerouter kernel: ivtv: Create DMA stream 8
Apr 27 10:01:38 dcerouter kernel: ivtv: Registered v4l2 device, streamtype 8 minor 48
Apr 27 10:01:38 dcerouter kernel: ivtv: Setting Tuner 20
Apr 27 10:01:38 dcerouter kernel: tuner: type set to 20 (Temic PAL_BG (4009 FR5) or PAL_I (4069 FR5)) by ivtv i2c driver #0
Apr 27 10:01:38 dcerouter kernel: ivtv: Setting audio matrix to input 3, output 1
Apr 27 10:01:38 dcerouter kernel: ivtv: Switching standard to PAL.
Apr 27 10:01:38 dcerouter kernel: ivtv: ivtv_enc_thread: pid = 27937, itv = 0xe1071560
Apr 27 10:01:38 dcerouter kernel: ivtv: ivtv_dec_thread: pid = 27938, itv = 0xe1071560
Apr 27 10:01:38 dcerouter kernel: ivtv: Initialized WinTV PVR 350, card #0
Apr 27 10:01:38 dcerouter kernel: ivtv: ====================  END INIT IVTV  ====================
d


I've setup in mythtv-setup device to /dev/video4, but something is obviously wrong...

I get this:

Code: newbielink:javascript:void(0); [nonactive]
MythTV_Backend_Proxy, v.2.0.0.16
Visit www.plutohome.com for source code and license information

10 04/27/05 16:38:19.569 Device: 6618 starting.  Connecting to: localhost
10 04/27/05 16:38:19.572 DCE Router asked us to wait--it's busy at the moment
10 04/27/05 16:38:24.573 DCE Router asked us to wait--it's busy at the moment
10 04/27/05 16:38:29.574 DCE Router asked us to wait--it's busy at the moment
10 04/27/05 16:38:34.576 DCE Router asked us to wait--it's busy at the moment
10 04/27/05 16:38:39.578 DCE Router asked us to wait--it's busy at the moment


log is full of those messages. And then mythfrontend says that cannot connect to mythbackend, and asks if it's running? All this despite if I run mythbackend by hand ....

I wonder what does mythbackend proxy, and how is myhtbackend started under pluto? Also what settings are good for myhtfrontend...

Thanks in advance,

regards,

Rob.

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Starting help for rusty Mythtv user ...
« Reply #5 on: April 27, 2005, 05:07:40 pm »
I think there are 3 issues:

1. Why are you using video4 ?
2. the cannot connect to router are generated because you don't have the DCERouter program started or it takes a veeery long time to start ?
  This also can happend if you configured the mythtv database access from the mythtv-setup. if so then please remove the /.mythtv/ folder.

3. the config in the mythtv databsae is changed so that the communication between the frontend and the backed is thru one of our programs (MythTV_Backedn_Proxy) we need this so that pluto can know what channel a certain frontend is tuned to.

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Starting help for rusty Mythtv user ...
« Reply #6 on: April 27, 2005, 06:57:34 pm »
Hi,

I have further info. There seems to be problem with logging to mythtv database and this problem blocks whole pluto system on booting (DCERouter busy messages to all devices)...

Aaron helped me and just removed mythtv plugin with

mv MythTV_PlugIn.so MythTV_PlugIn.so.bak

so pluto now starts fine but without mythtv...

Problems began when I fixed problem with loading ivtv, so from then ivtv is loading properly and mythtv plugin gets activated...

I suspect that parts of mythtv subsystem could be setup right, so don't now why this happens...

Anyone with similar experience ?  Anyone with fully working mythtv-pluto setup ?

Thanks in advance,

regards,

Rob.

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Starting help for rusty Mythtv user ...
« Reply #7 on: April 27, 2005, 06:58:22 pm »
Sorry, forgot log output:
Code: newbielink:javascript:void(0); [nonactive]
2005-04-27 18:32:47.620 Unable to connect to database!
2005-04-27 18:32:47.620 Driver error was [1/1045]:
QMYSQL3: Unable to connect
Database error was:
Access denied for user: 'mythtv@dcerouter' (Using password: YES)

couldn't open db
Would you like to configure the database connection now? [yes]  13      04/27/05 18:33:12.575           TCPIP: Accepting incoming connection on socket 75, po
rt 3450, from IP 127.0.0.1. <-1253016656>
start const 0x8c501d8
stop const 0x8c501d8
2


Regards,

Rob.

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Starting help for rusty Mythtv user ...
« Reply #8 on: April 27, 2005, 11:56:43 pm »
Quote from: "mihai.t"
I think there are 3 issues:

1. Why are you using video4 ?
2. the cannot connect to router are generated because you don't have the DCERouter program started or it takes a veeery long time to start ?
  This also can happend if you configured the mythtv database access from the mythtv-setup. if so then please remove the /.mythtv/ folder.

3. the config in the mythtv databsae is changed so that the communication between the frontend and the backed is thru one of our programs (MythTV_Backedn_Proxy) we need this so that pluto can know what channel a certain frontend is tuned to.

1. Cause other devices are already taken with video capture card...
2. With Aaron help we spotted problem. Mythtv was blocking whole boot process cause couldn't connect to database...

3. What should I do on my installation to get this settings right ?

Thanks in advance,

regards,

Rob.

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Starting help for rusty Mythtv user ...
« Reply #9 on: April 28, 2005, 11:11:26 am »
Hi,

The settings are usually correct from the installation. MythTV installation will create the proper config file in /etc/mythtv/mysql.txt file. If you change/put other settings in the mythtv-setup software this will generate a /.mythtv or a ~root/.mythtv folder with a mysql.txt file in it (usually the settings are wrong in there becase the default pass is generated randomly).

To fix you settings you need to remove both of the /.mythv/mysql.txt file and ~root/.mythtv/mysql.txt files and restart DCERouter.

Sincerely,
   ToMiC

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Starting help for rusty Mythtv user ...
« Reply #10 on: April 28, 2005, 12:34:04 pm »
Quote from: "mihai.t"
Hi,

The settings are usually correct from the installation. MythTV installation will create the proper config file in /etc/mythtv/mysql.txt file. If you change/put other settings in the mythtv-setup software this will generate a /.mythtv or a ~root/.mythtv folder with a mysql.txt file in it (usually the settings are wrong in there becase the default pass is generated randomly).

To fix you settings you need to remove both of the /.mythv/mysql.txt file and ~root/.mythtv/mysql.txt files and restart DCERouter.

Sincerely,
   ToMiC


Hi,

thanks for info. I just wonder where or what settings are default for pluto? I need them to get mythweb working... Till Orbiters GUI for TV guide gets better, I'd like to use mythweb to schedule recordings and manage mythtv....

Thanks in advance,

regards,
Rob.

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Starting help for rusty Mythtv user ...
« Reply #11 on: April 28, 2005, 01:19:43 pm »
Hi,

The database access defaults are in the /etc/mythtv/mysql.txt file
For the rest (backend/frontend ip/ports and so on .. ) they are updated at every reboot. I hope you don't need to change those.

Sincerely,
   ToMiC