[nflug] MythTV issues

Joshua Ronne Altemoos joshua at wolfnix.net
Thu Mar 9 09:33:13 EST 2006


I belive this is the most updated kernal and I can not make the meetings
because of bussing and There is no way I could bring the comptuer. Thanks
anyways.

Josh

> Joshua Ronne Altemoos wrote:
>> Well the card is made by EVGA and has nvidida chipsets and a philips
>> tuner
>> in it. I am running 2.6.12-10
>>
>>
>>> Joshua Ronne Altemoos wrote:
>>>
>>>> Well i did tha howto, but It did not change anything...
>>>>
>>>> joshua at purgatory:~$ lspci
>>>> 0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365
>>>> [KT133/KM133] (rev 03)
>>>> 0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365
>>>> [KT133/KM133 AGP]
>>>> 0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super
>>>> South] (rev 40)
>>>> 0000:00:07.1 IDE interface: VIA Technologies, Inc.
>>>> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
>>>> 0000:00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
>>>> 1.1 Controller (rev 1a)
>>>> 0000:00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
>>>> 1.1 Controller (rev 1a)
>>>> 0000:00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super
>>>> ACPI] (rev 40)
>>>> 0000:00:07.5 Multimedia audio controller: VIA Technologies, Inc.
>>>> VT82C686 AC97 Audio Controller (rev 50)
>>>> 0000:00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
>>>> RTL-8139/8139C/8139C+ (rev 10)
>>>> 0000:00:0c.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro
>>>> 100] (rev 08)
>>>> 0000:01:00.0 VGA compatible controller: nVidia Corporation NV18
>>>> [GeForce4 MX 440 AGP 8x] (rev c1)
>>>> joshua at purgatory:~$
>>>>
>>>> joshua at purgatory:~$ lspci -vvvv
>>>> 0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365
>>>> [KT133/KM133] (rev 03)
>>>>        Subsystem: Giga-byte Technology: Unknown device 0000
>>>>        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
>>>> ParErr- Stepping- SERR- FastB2B-
>>>>        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>>>>
>>>>> TAbort- <TAbort- <MAbort+ >SERR- <PERR-
>>>>>
>>>>        Latency: 8
>>>>        Region 0: Memory at e0000000 (32-bit, prefetchable) [size=64M]
>>>>        Capabilities: <available only to root>
>>>>
>>>> 0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365
>>>> [KT133/KM133 AGP] (prog-if 00 [Normal decode])
>>>>        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
>>>> ParErr- Stepping- SERR- FastB2B-
>>>>        Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium
>>>>
>>>>> TAbort- <TAbort- <MAbort+ >SERR- <PERR-
>>>>>
>>>>        Latency: 0
>>>>        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
>>>>        I/O behind bridge: 00009000-00009fff
>>>>        Memory behind bridge: dda00000-dfafffff
>>>>        Prefetchable memory behind bridge: cd800000-dd8fffff
>>>>        BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
>>>>        Capabilities: <available only to root>
>>>>
>>>> 0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super
>>>> South] (rev 40)
>>>>        Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge
>>>>        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
>>>> ParErr- Stepping+ SERR- FastB2B-
>>>>        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>>>>
>>>>> TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>>>>
>>>>        Latency: 0
>>>>        Capabilities: <available only to root>
>>>>
>>>> 0000:00:07.1 IDE interface: VIA Technologies, Inc.
>>>> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
>>>> (prog-if 8a [Master SecP PriP])
>>>>        Subsystem: VIA Technologies, Inc.
>>>> VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE
>>>>        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
>>>> ParErr- Stepping- SERR- FastB2B-
>>>>        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>>>>
>>>>> TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>>>>
>>>>        Latency: 32
>>>>        Region 4: I/O ports at ffa0 [size=16]
>>>>        Capabilities: <available only to root>
>>>>
>>>> 0000:00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
>>>> 1.1 Controller (rev 1a) (prog-if 00 [UHCI])
>>>>        Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
>>>>        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
>>>> ParErr- Stepping- SERR+ FastB2B-
>>>>        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>>>>
>>>>> TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>>>>
>>>>        Latency: 64, Cache Line Size: 0x08 (32 bytes)
>>>>        Interrupt: pin D routed to IRQ 11
>>>>        Region 4: I/O ports at cc00 [size=32]
>>>>        Capabilities: <available only to root>
>>>>
>>>> 0000:00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
>>>> 1.1 Controller (rev 1a) (prog-if 00 [UHCI])
>>>>        Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
>>>>        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
>>>> ParErr- Stepping- SERR+ FastB2B-
>>>>        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>>>>
>>>>> TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>>>>
>>>>        Latency: 64, Cache Line Size: 0x08 (32 bytes)
>>>>        Interrupt: pin D routed to IRQ 11
>>>>        Region 4: I/O ports at d000 [size=32]
>>>>        Capabilities: <available only to root>
>>>>
>>>> 0000:00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super
>>>> ACPI] (rev 40)
>>>>        Subsystem: Giga-byte Technology: Unknown device 0000
>>>>        Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
>>>> ParErr- Stepping- SERR- FastB2B-
>>>>        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>>>>
>>>>> TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>>>>
>>>>        Interrupt: pin ? routed to IRQ 9
>>>>        Capabilities: <available only to root>
>>>>
>>>> 0000:00:07.5 Multimedia audio controller: VIA Technologies, Inc.
>>>> VT82C686 AC97 Audio Controller (rev 50)
>>>>        Subsystem: Giga-byte Technology: Unknown device a002
>>>>        Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
>>>> ParErr- Stepping- SERR- FastB2B-
>>>>        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>>>>
>>>>> TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>>>>
>>>>        Interrupt: pin C routed to IRQ 10
>>>>        Region 0: I/O ports at dc00 [size=256]
>>>>        Region 1: I/O ports at d800 [size=4]
>>>>        Region 2: I/O ports at d400 [size=4]
>>>>        Capabilities: <available only to root>
>>>>
>>>> 0000:00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
>>>> RTL-8139/8139C/8139C+ (rev 10)
>>>>        Subsystem: Addtron Technology Co, Inc.: Unknown device 1360
>>>>        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
>>>> ParErr- Stepping- SERR- FastB2B-
>>>>        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>>>>
>>>>> TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>>>>
>>>>        Latency: 64 (8000ns min, 16000ns max)
>>>>        Interrupt: pin A routed to IRQ 18
>>>>        Region 0: I/O ports at c800 [size=256]
>>>>        Region 1: Memory at dfffff00 (32-bit, non-prefetchable)
>>>> [size=256]
>>>>        Capabilities: <available only to root>
>>>>
>>>> 0000:00:0c.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro
>>>> 100] (rev 08)
>>>>        Subsystem: Intel Corp. EtherExpress PRO/100+ Management Adapter
>>>>        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
>>>> ParErr- Stepping- SERR- FastB2B-
>>>>        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>>>>
>>>>> TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>>>>
>>>>        Latency: 64 (2000ns min, 14000ns max), Cache Line Size: 0x08
>>>> (32 bytes)
>>>>        Interrupt: pin A routed to IRQ 16
>>>>        Region 0: Memory at dfffe000 (32-bit, non-prefetchable)
>>>> [size=4K]
>>>>        Region 1: I/O ports at c400 [size=64]
>>>>        Region 2: Memory at dfe00000 (32-bit, non-prefetchable)
>>>> [size=1M]
>>>>        Expansion ROM at dfd00000 [disabled] [size=1M]
>>>>        Capabilities: <available only to root>
>>>>
>>>> 0000:01:00.0 VGA compatible controller: nVidia Corporation NV18
>>>> [GeForce4 MX 440 AGP 8x] (rev c1) (prog-if 00 [VGA])
>>>>        Subsystem: Unknown device 3842:3088
>>>>        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
>>>> ParErr- Stepping- SERR- FastB2B-
>>>>        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium
>>>>
>>>>> TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>>>>
>>>>        Latency: 248 (1250ns min, 250ns max)
>>>>        Interrupt: pin A routed to IRQ 16
>>>>        Region 0: Memory at de000000 (32-bit, non-prefetchable)
>>>> [size=16M]
>>>>        Region 1: Memory at d0000000 (32-bit, prefetchable) [size=128M]
>>>>        Expansion ROM at dfae0000 [disabled] [size=128K]
>>>>        Capabilities: <available only to root>
>>>>
>>>> joshua at purgatory:~$
>>>>
>>>> Joshua Ronne Altemoos wrote:
>>>>
>>>>
>>>>> They have a nice ubuntu howto :)
>>>>> http://ivtvdriver.org/index.php/Howto:Ubuntu
>>>>>
>>>>> Cyber Source wrote:
>>>>>
>>>>>
>>>>>> Joshua Ronne Altemoos wrote:
>>>>>>
>>>>>>
>>>>>>> I don't know I just did what I was asked. I looked at rivatv and it
>>>>>>> says the driver for my tuner is under development so I will have to
>>>>>>> check back there again, but as CyberSource said, If lspci did not
>>>>>>> show the tuner?
>>>>>>>
>>>>>>> ~Josh
>>>>>>>
>>>>>>> Mark T. Valites wrote:
>>>>>>>
>>>>>>>
>>>>>>>> On Wed, 8 Mar 2006, Joshua Ronne Altemoos wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>> I can play ppracer, but I can not watch TV in xawtv. I sent the
>>>>>>>>> lspci and
>>>>>>>>> my /etc/modules eariler.
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> The firsst result in a google/linux search for "EVGA geforce4 MX
>>>>>>>> 440 phillips" turns up:
>>>>>>>>
>>>>>>>> http://rivatv.sourceforge.net/status.html
>>>>>>>>
>>>>>>>> Your modules.conf doesn't list the rivatv module - this is most
>>>>>>>> likely what you need. I'm not sure if it's part of ubuntu (it's
>>>>>>>> not found by apt in Debian here).
>>>>>>>>
>>>>>>>> Having tuxracer or any other opengl app working well doesn't
>>>>>>>> really have anything to do with the tuner. You'll want to get the
>>>>>>>> tuner working first with xawtv before throwing mythtv into the
>>>>>>>> mix.
>>>>>>>> _______________________________________________
>>>>>>>> nflug mailing list
>>>>>>>> nflug at nflug.org
>>>>>>>> http://www.nflug.org/mailman/listinfo/nflug
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> nflug mailing list
>>>>>>> nflug at nflug.org
>>>>>>> http://www.nflug.org/mailman/listinfo/nflug
>>>>>>>
>>>>>>>
>>>>>> Ok, see the part where it said "Subsystem: Unknown device
>>>>>> 3842:3088", a quick google on this found this--->
>>>>>> http://www.spinics.net/lists/vfl/msg07108.html . That mentions the
>>>>>> saa* stuff, I seem to recall that this is covered by the ivtv
>>>>>> modules. Check out http://ivtvdriver.org/index.php/Main_Page
>>>>>> _______________________________________________
>>>>>> nflug mailing list
>>>>>> nflug at nflug.org
>>>>>> http://www.nflug.org/mailman/listinfo/nflug
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> nflug mailing list
>>>>> nflug at nflug.org
>>>>> http://www.nflug.org/mailman/listinfo/nflug
>>>>>
>>>> _______________________________________________
>>>> nflug mailing list
>>>> nflug at nflug.org
>>>> http://www.nflug.org/mailman/listinfo/nflug
>>>>
>>>>
>>> I had to do some real diggin on Nvidia's site to find that thing and
>>> finally found it under their legacy stuff. The "cinema" line does not
>>> appear to be well noted or advertised and I don't believe it's made
>>> anymore but I could be wrong. I found some info here
>>> http://www.nvidia.com/page/personalcinema.html .
>>> I found only 2 links when I googled the vendor and product ID's from
>>> your lspci output, not much help there. I would shoot an email off to
>>> nvidia's support and ask them for some info. Also, what kernel are you
>>> running?
>>> _______________________________________________
>>> nflug mailing list
>>> nflug at nflug.org
>>> http://www.nflug.org/mailman/listinfo/nflug
>>>
>>>
>>
>>
>> _______________________________________________
>> nflug mailing list
>> nflug at nflug.org
>> http://www.nflug.org/mailman/listinfo/nflug
>>
>>
> I would try a newer kernel and then see if it gets recognized better.
> You might want to bring this to our first meeting in a long time if we
> have one on the 19th. Are we on for the 19th at ITT??? at 1:00
> _______________________________________________
> nflug mailing list
> nflug at nflug.org
> http://www.nflug.org/mailman/listinfo/nflug
>


_______________________________________________
nflug mailing list
nflug at nflug.org
http://www.nflug.org/mailman/listinfo/nflug



More information about the nflug mailing list