Re: [mythtv-users] The nvidia-settings tool and Myth (keeping overscan right)

2005-03-08 Thread Jason Blair
Put this in a place where it will be run each time you log in:

nvidia-settings --load-config-only &


On Tue, 8 Mar 2005 07:10:23 -0500, Pete Stagman <[EMAIL PROTECTED]> wrote:
> I have no problem keeping the settings. I know that nvidia-settings
> saves the settings when you exit it.
> 
> What I do is tweak my settings, close it, restart it and leave it
> running minimized. It always survives reboots for me that way. As long
> as I don't close it before shutdown.
> 
> --Pete
> 
> 
> On Tue, 8 Mar 2005 23:04:31 +1100, Phill Edwards <[EMAIL PROTECTED]> wrote:
> > > One of the few remaining issues for me is using all of my TV's screen
> > > real-estate.  If I use the 'nvidia-settings' tool, I can set up the
> > > overscan so that the image completely fills my TV.  Unfortunately, it
> > > doesn't last.  Especially if I use MythGame to launch an external
> > > application that resizes things (StepMania and TuxRacer for example).
> > > When I return to Myth the screen is no longer maximized.
> > >
> > > I've found that the only way to reliably get the screen maximized again
> > > is to quit Myth, fire up the nvidia-settings GUI, twiddle the size
> > > slider, then quit the GUI.  Even running 'nvidia-settings
> > > --load-config-only' doesn't do it.
> > > I know this isn't a Myth issue, it's poor design on nVidia's part, but
> > > how are other people dealing with nvidia-settings?  Does anybody have a
> > > way to re-maximize the display without leaving Myth, or at least without
> > > having to bring up the GUI?
> >
> > You could try putting this in the "Devices" section of your xord.conf
> > or equivalent:
> > Option "TVOverScan" "0.60"
> >
> > Obviously change 0.60 to suit your needs!
> >
> > Regards,
> > Phill
> >
> >
> > ___
> > mythtv-users mailing list
> > mythtv-users@mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
> >
> >
> 
> --
> Lirc, FC3, and an Irblaster?
> www.lircsetup.com
> 
> 
> ___
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> 
> 
>
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] PVR-250 and bttv card both think they are /dev/video0

2005-02-21 Thread Jason Blair
Ok...I this is fixed.  Jarod just released some updates that make sure
the drivers are loaded very early as udev starts.  It now creates the
video0 and video1 devices correctly.

[EMAIL PROTECTED] ~]# dmesg | grep bttv 
   
bttv: driver version 0.9.15 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
bttv0: Bt878 (rev 2) at :01:0a.0, irq: 5, latency: 32, mmio: 0xdc00
bttv0: detected: Hauppauge WinTV [card=10], PCI subsystem ID is 0070:13eb
bttv0: using: Hauppauge (bt878) [card=10,autodetected]
bttv0: gpio: en=, out= in=00fb [init]
bttv0: Hauppauge/Voodoo msp34xx: reset line init [5]
bttv0: Hauppauge eeprom: model=62471, tuner=Philips FM1236 (2), radio=yes
bttv0: using tuner=2
bttv0: i2c: checking for MSP34xx @ 0x80... not found
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
bttv0: i2c: checking for TDA9887 @ 0x86... not found
bttv0: registered device video1
bttv0: registered device vbi1
bttv0: registered device radio1
bttv0: PLL: 28636363 => 35468950 .. ok
bttv0: PLL can sleep, using XTAL (28636363).


[EMAIL PROTECTED] ~]# dmesg | grep ivtv
ivtv: no version for "struct_module" found: kernel tainted.
ivtv:  START INIT IVTV 
ivtv: version 0.2.0 (rc3e) loading
ivtv: Linux version: 2.6.10-1.760_FC3 686 REGPARM 4KSTACKS gcc-3.4
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 250 card
ivtv: Found an iTVC16 based chip
ivtv: Unreasonably low latency timer, setting to 64 (was 32)
ivtv: XXX PCI device: 0x01e0 vendor: 0x10de
ivtv: i2c attach [client=tveeprom[0],ok]
ivtv: Tuner Type 8, Tuner formats 0x1000, Radio: yes, Model
0x00893496, Revision 0x
ivtv: NTSC tuner detected
ivtv: Radio detected
tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
ivtv: i2c attach [client=(tuner unset),ok]
saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005)
ivtv: i2c attach [client=saa7115[0],ok]
ivtv: i2c attach [client=MSP3448W-A2,ok]
ivtv: Encoder revision: 0x02040024
ivtv: Encoder Firmware is buggy, use version 0x02040011
ivtv: Configuring WinTV PVR 250 card with 5 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: Setting Tuner 8
tuner: type set to 8 (Temic NTSC (4036 FY5)) by ivtv i2c driver #0
ivtv: Setting audio matrix to input 3, output 1
ivtv: Switching standard to NTSC.
ivtv: Initialized WinTV PVR 250, card #0
ivtv:   END INIT IVTV  
ivtv: ivtv_enc_thread: pid = 2292, itv = 0xe097b020
ivtv: i2c attach [client=Hauppauge IR,ok]




On Mon, 21 Feb 2005 13:57:41 -0500, David George <[EMAIL PROTECTED]> wrote:
> On 2/21/2005 1:03 PM, Jason Blair wrote:
> 
> >Also, doesn't this line tell me that the ivtv card is /dev/video0?
> >
> >
> >
> >>ivtv: Initialized WinTV PVR 250, card #0
> >>
> >>
> Nope.  That just means that it is the first ivtv card.
> 
> >
> >If I pull out the bttv card the ivtv card works fine on /dev/video0.
> >I upgraded this machine to FC3 recently, before that with fc2 I had
> >both cards working with the ivtv as video0 and the bttv as video1.
> >
> >
> Interesting.  I am still on FC2.  There is no reason to go to FC3.  The
> only major difference I can think of that would affect this is the new
> UDEV in FC3.
> 
> --
> David
> ___
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] PVR-250 and bttv card both think they are /dev/video0

2005-02-21 Thread Jason Blair
Also, doesn't this line tell me that the ivtv card is /dev/video0?

> ivtv: Initialized WinTV PVR 250, card #0

If I pull out the bttv card the ivtv card works fine on /dev/video0. 
I upgraded this machine to FC3 recently, before that with fc2 I had
both cards working with the ivtv as video0 and the bttv as video1.


On Mon, 21 Feb 2005 12:30:20 -0500, Jason Blair <[EMAIL PROTECTED]> wrote:
> Yes, I have.  I tried changing my modprobe.conf so that the ivtv card
> was 81-1 and the bttv card was 81-0 but then when I try and setup
> mythtv so that the ivtv card is on /dev/video1 all I get is a black
> screen and a frozen machine.
> 
> 
> On Mon, 21 Feb 2005 11:31:52 -0500, David George <[EMAIL PROTECTED]> wrote:
> > On 2/20/2005 12:40 AM, Jason Blair wrote:
> >
> > >I'm having a issue with my dual tuner setup.  Both my ivtv and bttv
> > >card think they are /dev/video0.  Mythtv recognizes /dev/video0 as
> > >only having the inputs of my bttv card and not the pvr-250.  Trying to
> > >swap the cards in my modprobe.conf and setting up the ivtv card as
> > >81-1 and the bttv card as 81-0 doesn't work.
> > >
> > >
> > [snippage]
> >
> > >ivtv: Registered v4l2 device, streamtype 0 minor 1
> > >ivtv: Create DMA stream 1
> > >
> > >
> > This says that the ivtv card is really on /dev/video1.  Have you tried
> > setting MythTV to use /dev/video1 for the ivtv card?
> >
> > --
> > David
> >
> > ___
> > mythtv-users mailing list
> > mythtv-users@mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
>
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] PVR-250 and bttv card both think they are /dev/video0

2005-02-21 Thread Jason Blair
Yes, I have.  I tried changing my modprobe.conf so that the ivtv card
was 81-1 and the bttv card was 81-0 but then when I try and setup
mythtv so that the ivtv card is on /dev/video1 all I get is a black
screen and a frozen machine.


On Mon, 21 Feb 2005 11:31:52 -0500, David George <[EMAIL PROTECTED]> wrote:
> On 2/20/2005 12:40 AM, Jason Blair wrote:
> 
> >I'm having a issue with my dual tuner setup.  Both my ivtv and bttv
> >card think they are /dev/video0.  Mythtv recognizes /dev/video0 as
> >only having the inputs of my bttv card and not the pvr-250.  Trying to
> >swap the cards in my modprobe.conf and setting up the ivtv card as
> >81-1 and the bttv card as 81-0 doesn't work.
> >
> >
> [snippage]
> 
> >ivtv: Registered v4l2 device, streamtype 0 minor 1
> >ivtv: Create DMA stream 1
> >
> >
> This says that the ivtv card is really on /dev/video1.  Have you tried
> setting MythTV to use /dev/video1 for the ivtv card?
> 
> --
> David
> 
> ___
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Re: PVR-250 and bttv card both think they are /dev/video0

2005-02-21 Thread Jason Blair
Thank you.  I've actually looked over that page before in my search to
figure out what's going wrong.  I will have to sit down and try and
understand it more.  I had been following Jarod's guide and he covers
ivtv and bttv cards in the same system, but doesn't mention much more
than adding the proper line to modules.conf which is supposed to make
the bttv card come up as /dev/video1. I guess I have some homework to
do know to understand udev a bit more.


On Mon, 21 Feb 2005 08:10:34 +0100, Alberto Hernando
<[EMAIL PROTECTED]> wrote:
> El Lunes, 21 de Febrero de 2005 03:40, Jason Blair escribió:
> > Anyone have any ideas?
> 
> Check this link. It explains how to use udev and write rules, so that you will
> know where each device is. It also gives a method to know what hardware is
> every /dev file.
> 
> http://www.reactivated.net/udevrules.php
> 
>  Alberto
>
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


[mythtv-users] Re: PVR-250 and bttv card both think they are /dev/video0

2005-02-20 Thread Jason Blair
Anyone have any ideas? 


On Sun, 20 Feb 2005 00:40:17 -0500, Jason Blair <[EMAIL PROTECTED]> wrote:
> I'm having a issue with my dual tuner setup.  Both my ivtv and bttv
> card think they are /dev/video0.  Mythtv recognizes /dev/video0 as
> only having the inputs of my bttv card and not the pvr-250.  Trying to
> swap the cards in my modprobe.conf and setting up the ivtv card as
> 81-1 and the bttv card as 81-0 doesn't work.
> 
> Can anyone offer any insight on how to fix this?  If you need more
> info please let me know.
> 
>  Thanks!
> 
> [EMAIL PROTECTED] ~]# ll /dev/video*
> lrwxrwxrwx  1 root   root  6 Feb 19 19:27 /dev/video -> video0
> crw---  1 mythtv root 81,  0 Feb 19 19:27 /dev/video0
> crw---  1 mythtv root 81,  1 Feb 20 00:27 /dev/video1
> crw---  1 mythtv root 81, 24 Feb 20 00:27 /dev/video24
> crw---  1 mythtv root 81, 32 Feb 20 00:27 /dev/video32
> crw---  1 mythtv root 81,  0 Feb 19 19:27 /dev/video4linux
> 
> [EMAIL PROTECTED] ~]# dmesg | grep bttv
> bttv: driver version 0.9.15 loaded
> bttv: using 8 buffers with 2080k (520 pages) each for capture
> bttv: Bt8xx card found (0).
> bttv0: Bt878 (rev 2) at :01:0a.0, irq: 5, latency: 32, mmio: 0xdc00
> bttv0: detected: Hauppauge WinTV [card=10], PCI subsystem ID is 0070:13eb
> bttv0: using: Hauppauge (bt878) [card=10,autodetected]
> bttv0: gpio: en=, out= in=00fb [init]
> bttv0: Hauppauge/Voodoo msp34xx: reset line init [5]
> bttv0: Hauppauge eeprom: model=62471, tuner=Philips FM1236 (2), radio=yes
> bttv0: using tuner=2
> bttv0: i2c: checking for MSP34xx @ 0x80... not found
> bttv0: i2c: checking for TDA9875 @ 0xb0... not found
> bttv0: i2c: checking for TDA7432 @ 0x8a... not found
> bttv0: i2c: checking for TDA9887 @ 0x86... not found
> bttv0: registered device video0
> bttv0: registered device vbi0
> bttv0: registered device radio0
> bttv0: PLL: 28636363 => 35468950 .. ok
> 
> [EMAIL PROTECTED] ~]# dmesg |grep ivtv
> ivtv:  START INIT IVTV 
> ivtv: version 0.2.0 (rc3e) loading
> ivtv: Linux version: 2.6.10-1.760_FC3 686 REGPARM 4KSTACKS gcc-3.4
> 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 250 card
> ivtv: Found an iTVC16 based chip
> ivtv: Unreasonably low latency timer, setting to 64 (was 32)
> ivtv: XXX PCI device: 0x01e0 vendor: 0x10de
> tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
> ivtv: i2c attach [client=(tuner unset),ok]
> ivtv: i2c attach [client=tveeprom[1],ok]
> ivtv: Tuner Type 8, Tuner formats 0x1000, Radio: yes, Model
> 0x00893496, Revision 0x
> ivtv: NTSC tuner detected
> ivtv: Radio detected
> saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005)
> ivtv: i2c attach [client=saa7115[0],ok]
> ivtv: i2c attach [client=MSP3448W-A2,ok]
> ivtv: Encoder revision: 0x02040024
> ivtv: Encoder Firmware is buggy, use version 0x02040011
> ivtv: Configuring WinTV PVR 250 card with 5 streams
> ivtv: Create DMA stream 0 using 256 16384 byte buffers  4194304 kbytes total
> ivtv: Registered v4l2 device, streamtype 0 minor 1
> 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 225
> 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 65
> ivtv: Setting Tuner 8
> tuner: type set to 8 (Temic NTSC (4036 FY5)) by ivtv i2c driver #0
> ivtv: Setting audio matrix to input 3, output 1
> ivtv: Switching standard to NTSC.
> ivtv: Initialized WinTV PVR 250, card #0
> ivtv:   END INIT IVTV  
> ivtv: ivtv_enc_thread: pid = 4673, itv = 0xe0d18020
> ivtv: i2c attach [client=Hauppauge IR,ok]
> 
> [EMAIL PROTECTED] ~]# /sbin/lspci -v
> 01:08.0 Multimedia video controller: Internext Compression Inc iTVC16
> (CX23416) MPEG-2 Encoder (rev 01)
> Subsystem: Hauppauge computer works Inc. WinTV PVR 250
> Flags: bus master, medium devsel, latency 64, IRQ 11
> Memory at d800 (32-bit, prefetchable) [size=64M]
> Capabilities: [44] Power Management version 2
> 
> 01:0a.0 Multimedia video controller: Brooktree Corporation Bt878 Video
> Capture (rev 02)
> Subsystem: Hauppauge computer works Inc. WinTV Series
> Flags: bus master, medium devsel, latency 32, IRQ 5
> Memory at dc00 (

[mythtv-users] PVR-250 and bttv card both think they are /dev/video0

2005-02-19 Thread Jason Blair
I'm having a issue with my dual tuner setup.  Both my ivtv and bttv
card think they are /dev/video0.  Mythtv recognizes /dev/video0 as
only having the inputs of my bttv card and not the pvr-250.  Trying to
swap the cards in my modprobe.conf and setting up the ivtv card as
81-1 and the bttv card as 81-0 doesn't work.

Can anyone offer any insight on how to fix this?  If you need more
info please let me know.

 Thanks!


[EMAIL PROTECTED] ~]# ll /dev/video*
lrwxrwxrwx  1 root   root  6 Feb 19 19:27 /dev/video -> video0
crw---  1 mythtv root 81,  0 Feb 19 19:27 /dev/video0
crw---  1 mythtv root 81,  1 Feb 20 00:27 /dev/video1
crw---  1 mythtv root 81, 24 Feb 20 00:27 /dev/video24
crw---  1 mythtv root 81, 32 Feb 20 00:27 /dev/video32
crw---  1 mythtv root 81,  0 Feb 19 19:27 /dev/video4linux


[EMAIL PROTECTED] ~]# dmesg | grep bttv
bttv: driver version 0.9.15 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
bttv0: Bt878 (rev 2) at :01:0a.0, irq: 5, latency: 32, mmio: 0xdc00
bttv0: detected: Hauppauge WinTV [card=10], PCI subsystem ID is 0070:13eb
bttv0: using: Hauppauge (bt878) [card=10,autodetected]
bttv0: gpio: en=, out= in=00fb [init]
bttv0: Hauppauge/Voodoo msp34xx: reset line init [5]
bttv0: Hauppauge eeprom: model=62471, tuner=Philips FM1236 (2), radio=yes
bttv0: using tuner=2
bttv0: i2c: checking for MSP34xx @ 0x80... not found
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
bttv0: i2c: checking for TDA9887 @ 0x86... not found
bttv0: registered device video0
bttv0: registered device vbi0
bttv0: registered device radio0
bttv0: PLL: 28636363 => 35468950 .. ok


[EMAIL PROTECTED] ~]# dmesg |grep ivtv
ivtv:  START INIT IVTV 
ivtv: version 0.2.0 (rc3e) loading
ivtv: Linux version: 2.6.10-1.760_FC3 686 REGPARM 4KSTACKS gcc-3.4
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 250 card
ivtv: Found an iTVC16 based chip
ivtv: Unreasonably low latency timer, setting to 64 (was 32)
ivtv: XXX PCI device: 0x01e0 vendor: 0x10de
tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
ivtv: i2c attach [client=(tuner unset),ok]
ivtv: i2c attach [client=tveeprom[1],ok]
ivtv: Tuner Type 8, Tuner formats 0x1000, Radio: yes, Model
0x00893496, Revision 0x
ivtv: NTSC tuner detected
ivtv: Radio detected
saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005)
ivtv: i2c attach [client=saa7115[0],ok]
ivtv: i2c attach [client=MSP3448W-A2,ok]
ivtv: Encoder revision: 0x02040024
ivtv: Encoder Firmware is buggy, use version 0x02040011
ivtv: Configuring WinTV PVR 250 card with 5 streams
ivtv: Create DMA stream 0 using 256 16384 byte buffers  4194304 kbytes total
ivtv: Registered v4l2 device, streamtype 0 minor 1
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 225
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 65
ivtv: Setting Tuner 8
tuner: type set to 8 (Temic NTSC (4036 FY5)) by ivtv i2c driver #0
ivtv: Setting audio matrix to input 3, output 1
ivtv: Switching standard to NTSC.
ivtv: Initialized WinTV PVR 250, card #0
ivtv:   END INIT IVTV  
ivtv: ivtv_enc_thread: pid = 4673, itv = 0xe0d18020
ivtv: i2c attach [client=Hauppauge IR,ok]


[EMAIL PROTECTED] ~]# /sbin/lspci -v
01:08.0 Multimedia video controller: Internext Compression Inc iTVC16
(CX23416) MPEG-2 Encoder (rev 01)
Subsystem: Hauppauge computer works Inc. WinTV PVR 250
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at d800 (32-bit, prefetchable) [size=64M]
Capabilities: [44] Power Management version 2

01:0a.0 Multimedia video controller: Brooktree Corporation Bt878 Video
Capture (rev 02)
Subsystem: Hauppauge computer works Inc. WinTV Series
Flags: bus master, medium devsel, latency 32, IRQ 5
Memory at dc00 (32-bit, prefetchable) [size=4K]

01:0a.1 Multimedia controller: Brooktree Corporation Bt878 Audio
Capture (rev 02)
Subsystem: Hauppauge computer works Inc. WinTV Series
Flags: bus master, medium devsel, latency 32, IRQ 5
Memory at dc001000 (32-bit, prefetchable) [size=4K]
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Shuttle SB75S, SB65G2, or SB61G2V3

2005-02-03 Thread Jason Blair
I have a shuttle but don't use it for myth.  I need a system that has
room for 2 tv tuners so I can record one thing and watch another.  As
far as the sound issue goeshow hot is the system running and what
setting is the fan on in the bios.  My system is near quiet except for
when things start to get too hot and then the fan ramps up.


On Thu, 3 Feb 2005 09:09:40 -0700, Brandon Beattie
<[EMAIL PROTECTED]> wrote:
> On Wed, Feb 02, 2005 at 08:12:45PM -0600, Robert Denier wrote:
> > John Hannan wrote:
> 
> How about AC3/SPdif/TOSLINK audio output?  Does this work?  I want to
> make sure I won't have to add a PCI card to get DD/DTS audio streams to
> an external receiver.
> 
> --Brandon
> 
> 
> ___
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> 
> 
>
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Can't apt-get ivtv

2005-01-17 Thread Jason Blair
opps...looks like you might have to leave the _FC3 off those commands.

sorry.


On Mon, 17 Jan 2005 22:38:12 -0500, Jason Blair <[EMAIL PROTECTED]> wrote:
> cd /var/cache/apt/archives
> rpm -Uvh video4linux-kmdl-2.6.10-1.741_FC3*.rpm
> rpm -Uvh ivtv-kmdl-2.6.10-1.741_FC3*.rpm
> 
> That worked for me tonight.  I can't saw it's the 'right' thing to do,
> but it is what I did to get past that point.
> 
> Hope that helps!
> 
> 
> On Mon, 17 Jan 2005 21:17:47 -0600, Drew Zerdecki <[EMAIL PROTECTED]> wrote:
> > I have been screwing around with kernels after having installed myth.
> > Now after removing and reinstalling mythtv packages, I ran into the
> > following while apt-getting ivtv...  I'd appreciate any help.
> >
> > Thanks...
> >
> > Drew
> >
> > [EMAIL PROTECTED] modules]# apt-get install ivtv
> > Reading Package Lists... Done
> > Building Dependency Tree... Done
> > The following extra packages will be installed:
> >   ivtv-kmdl-2.6.10-1.741_FC3 perl-Video-ivtv 
> > video4linux-kmdl-2.6.10-1.741_FC3
> > The following NEW packages will be installed:
> >   ivtv ivtv-kmdl-2.6.10-1.741_FC3 perl-Video-ivtv
> >   video4linux-kmdl-2.6.10-1.741_FC3
> > 0 upgraded, 4 newly installed, 0 removed and 24 not upgraded.
> > Need to get 0B/297kB of archives.
> > After unpacking 764kB of additional disk space will be used.
> > Do you want to continue? [Y/n] y
> > Committing changes...
> > Preparing...### 
> > [100%]
> > file 
> > /lib/modules/2.6.10-1.741_FC3/updates/drivers/media/video/tveeprom.ko
> > conflicts between attempted installs of
> > ivtv-kmdl-2.6.10-1.741_FC3-0.1.10-48.4_pre2_ck100zz.rhfc3.at and
> > video4linux-kmdl-2.6.10-1.741_FC3-20050113_172233-54.rhfc3.at
> > E: Error while running transaction
> > [EMAIL PROTECTED] modules]#
> >
> > 
> > ___
> > mythtv-users mailing list
> > mythtv-users@mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
> >
> >
>
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Can't apt-get ivtv

2005-01-17 Thread Jason Blair
cd /var/cache/apt/archives
rpm -Uvh video4linux-kmdl-2.6.10-1.741_FC3*.rpm
rpm -Uvh ivtv-kmdl-2.6.10-1.741_FC3*.rpm

That worked for me tonight.  I can't saw it's the 'right' thing to do,
but it is what I did to get past that point.

Hope that helps!



On Mon, 17 Jan 2005 21:17:47 -0600, Drew Zerdecki <[EMAIL PROTECTED]> wrote:
> I have been screwing around with kernels after having installed myth.
> Now after removing and reinstalling mythtv packages, I ran into the
> following while apt-getting ivtv...  I'd appreciate any help.
> 
> Thanks...
> 
> Drew
> 
> [EMAIL PROTECTED] modules]# apt-get install ivtv
> Reading Package Lists... Done
> Building Dependency Tree... Done
> The following extra packages will be installed:
>   ivtv-kmdl-2.6.10-1.741_FC3 perl-Video-ivtv video4linux-kmdl-2.6.10-1.741_FC3
> The following NEW packages will be installed:
>   ivtv ivtv-kmdl-2.6.10-1.741_FC3 perl-Video-ivtv
>   video4linux-kmdl-2.6.10-1.741_FC3
> 0 upgraded, 4 newly installed, 0 removed and 24 not upgraded.
> Need to get 0B/297kB of archives.
> After unpacking 764kB of additional disk space will be used.
> Do you want to continue? [Y/n] y
> Committing changes...
> Preparing...### [100%]
> file 
> /lib/modules/2.6.10-1.741_FC3/updates/drivers/media/video/tveeprom.ko
> conflicts between attempted installs of
> ivtv-kmdl-2.6.10-1.741_FC3-0.1.10-48.4_pre2_ck100zz.rhfc3.at and
> video4linux-kmdl-2.6.10-1.741_FC3-20050113_172233-54.rhfc3.at
> E: Error while running transaction
> [EMAIL PROTECTED] modules]#
> 
> 
> ___
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> 
> 
>
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] ivtv-kmdl, PVR-250, FC3, Jarod's guide and no capture

2005-01-17 Thread Jason Blair
I think have run into the same situation described below.  Anyone have
any idea what the problem could be?

Thanks!
Jason


On Sun, 16 Jan 2005 18:57:50 -0600, Michael S. Ritterbusch
<[EMAIL PROTECTED]> wrote:
> 
> I'm having a similar issue with ivtv (specifically ivtv-kmdl-$KVER).
> However, the issue I'm having appears to be a conflict with another
> module, which I'm not sure is something that can be unloaded/removed.
> 
> Like George, I have everything else working great except for this. (the
> critical component of course).
> 
> When doing: apt-get install ivtv-kmdl-$KVER  ($KVER = 2.6.10-1.741_FC3),
> here is what the error message is:
> 
> ## Console CLIP
> 
> # apt-get install ivtv-kmdl-$KVER
> Reading Package Lists... Done
> Building Dependency Tree... Done
> The following extra packages will be installed:
>   video4linux-kmdl-2.6.10-1.741_FC3
> The following NEW packages will be installed:
>   ivtv-kmdl-2.6.10-1.741_FC3 video4linux-kmdl-2.6.10-1.741_FC3
> 0 upgraded, 2 newly installed, 0 removed and 0 not upgraded.
> Need to get 0B/169kB of archives.
> After unpacking 434kB of additional disk space will be used.
> Do you want to continue? [Y/n] Y
> Committing changes...
> Preparing...###
> [100%]
> file
> /lib/modules/2.6.10-1.741_FC3/updates/drivers/media/video/tveeprom.ko
> conflicts between attempted installs of
> ivtv-kmdl-2.6.10-1.741_FC3-0.1.10-48.4_pre2_ck100zz.rhfc3.at and
> video4linux-kmdl-2.6.10-1.741_FC3-20050113_172233-54.rhfc3.at
> E: Error while running transaction
> ## END CLIP 
> 
> This is the only thing standing between me and MythTV bliss... Any
> suggestions that don't require me to start over would be greatly
> appreciated!
> 
> Other Details:
> Fedora Core 3
> Intel 865 Video
> Hauppauge PVR-250
> 
> Thanks in advance for any feedback.
> 
> Best,
> Mike
> 
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of George Lopez
> Sent: Sunday, January 16, 2005 4:14 AM
> To: Discussion about mythtv
> Subject: [mythtv-users] ivtv, PVR-250, FC3,Jarod's guide and no capture
> - newbie
> 
> I have a critical issue with mythtv.  I cannot capture
> because I am not able to get ivtv to load.  Not sure
> if this is a Jarod's guide issue, ivtv issue, or user
> issue.  I have gotten everything up and running except
> I cannot capture anything b/c I cannot get ivtv to
> load.  I have done everything I could think of and
> find on the mail lists.  I am so close, yet all I have
> is a hunk of metal until I get this issue resolved.
> Modprobe.conf lines are there:
> # nvidia kernel module
> alias char-major-195 nvidia-1_0-6629
> # ivtv modules setup
> alias char-major-81 videodev
> alias char-major-81-0 ivtv
> 
> [EMAIL PROTECTED] mythtv]# uname -r
> 2.6.9-1.681_FC3
> [EMAIL PROTECTED] mythtv]# /sbin/lspci -v
> +++
> 02:0a.0 Multimedia video controller: Internext
> Compression Inc iTVC16 (CX23416)
> MPEG-2 Encoder (rev 01)
> Subsystem: Hauppauge computer works Inc. WinTV
> PVR 250
> Flags: bus master, medium devsel, latency 64,
> IRQ 9
> Memory at e800 (32-bit, prefetchable)
> [size=64M]
> Capabilities: [44] Power Management version 2
> +
> [EMAIL PROTECTED] mythtv]# apt-get install ivtv-firmware
> Reading Package Lists... Done
> Building Dependency Tree... Done
> ivtv-firmware is already the newest version.
> 0 upgraded, 0 newly installed, 0 removed and 20 not
> upgraded.
> [EMAIL PROTECTED] mythtv]# apt-get install
> ivtv-kmdl-$KVER
> Reading Package Lists... Done
> Building Dependency Tree... Done
> ivtv-kmdl-2.6.9-1.681_FC3 is already the newest
> version.
> 0 upgraded, 0 newly installed, 0 removed and 20 not
> upgraded.
> [EMAIL PROTECTED] mythtv]# apt-get install ivtv
> Reading Package Lists... Done
> Building Dependency Tree... Done
> The following extra packages will be installed:
>   ivtv-kmdl-2.6.10-1.741_FC3 kernel#2.6.10-1.741_FC3
> The following packages will be upgraded
>   ivtv
> The following NEW packages will be installed:
>   ivtv-kmdl-2.6.10-1.741_FC3 kernel#2.6.10-1.741_FC3
> 1 upgraded, 2 newly installed, 0 removed and 19 not
> upgraded.
> Need to get 17.0MB of archives.
> After unpacking 45.4MB of additional disk space will
> be used.
> Do you want to continue? [Y/n] y
> Get:1 http://ayo.freshrpms.net
> fedora/linux/3/i386/updates kernel#2.6.10-1.741_FC3
> 2.6.10-1.741_FC3 [16.8MB]
> Get:2 http://apt.atrpms.net
> fedora/3/en/i386/at-testing ivtv-kmdl-2.6.10-1.741_FC3
> 1:0.2.0-61_rc3d.rhfc3.at [109kB]
> Get:3 http://apt.atrpms.net
> fedora/3/en/i386/at-testing ivtv
> 1:0.2.0-61_rc3d.rhfc3.at [101kB]
> Fetched 17.0MB in 16m48s (16.8kB/s)
> Committing changes...
> Preparing...
> ### [100%]
>1:kernel
> ### [ 33%]
> 
> 2