Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[linux-dvb] Re: Old NOVA-T (Philips) and 2.6 kernels
You're a genius. I just modprobed all the same modules as you are running
and it's happy. I was quite shocked when a big yellow Tellitubby appeared
on my screen. Now, MythTV working with dvb......
Thanks again.
> Tim Squires wrote:
>
>>Thanks for the replies.
>>
>>I've tried Peters suggestion but I don't think I'm getting far enough for
>>it to make a difference.
>>
>>The tda1004x module is compiled but is not loaded. Would you expect the
>>tda1004x to be loaded for the frontend?
>>
>>
>
> No.
>
>>When I expect it to appear, /var/log/messages shows
>>
>>DVB: registering frontend 0 (LSI L64781 DVB-T)...
>>
>>Would you be kind enough to snip your messages and tell me what I should
>>really expect to see?
>>
>>
>
> Ok here's mine.....
>
> Linux video capture interface: v1.00
> saa7146: register extension 'dvb'.
> saa7146: register extension 'budget dvb'.
> ACPI: PCI interrupt 0000:00:08.0[A] -> GSI 11 (level, low) -> IRQ 11
> saa7146: found saa7146 @ mem 22940000 (revision 1, irq 11)
> (0x13c2,0x1005).
> DVB: registering new adapter (TT-Budget/WinTV-NOVA-T PCI).
> adapter has MAC addr = 00:d0:5c:21:83:7f
> DVB: registering frontend 0 (LSI L64781 DVB-T)...
> saa7146: register extension 'budget_ci dvb'.
> budget_av: Unknown symbol tda10021_attach
> usbcore: registered new driver Technotrend/Hauppauge USB-Nova
> ttusb_dec: Unknown symbol ttusbdecfe_dvbs_attach
> ttusb_dec: Unknown symbol ttusbdecfe_dvbt_attach
> usbcore: registered new driver dvb_dibusb
> skystar2: Unknown symbol mt352_attach
> skystar2: Unknown symbol mt352_write
> cinergyT2: Unknown symbol remap_pfn_range
>
> Most of these modules are not actually used but the linux-dvb script
> seems to load everything possible, it's harmless. I should really strip
> it down to the essentials.
>
> Here's the output of lsmod too.....
>
> dvb_dibusb 14852 0
> dvb_ttusb_budget 28700 0
> budget_ci 13440 0
> budget 9096 0
> budget_core 9096 7 budget_ci,budget
> dvb_ttpci 84676 0
> ttpci_eeprom 2944 2 budget_core,dvb_ttpci
> saa7146_vv 45184 1 dvb_ttpci
> saa7146 16716 5
> budget_ci,budget,budget_core,dvb_ttpci,saa7146_vv
> stv0297 6416 0
> mt312 7556 0
> cx22702 5764 0
> cx24110 7428 0
> tda8083 6020 2 budget,dvb_ttpci
> l64781 7044 1 budget
> dib3000mb 14596 1 dvb_dibusb
> tda1004x 11780 2 dvb_ttusb_budget,budget_ci
> ves1820 5892 2 budget,dvb_ttpci
> stv0299 9604 3 budget_ci,budget,dvb_ttpci
> cx22700 6020 1 dvb_ttusb_budget
> sp8870 7180 1 dvb_ttpci
> ves1x93 6532 2 budget,dvb_ttpci
> dvb_core 80304 11
> dvb_dibusb,dvb_ttusb_budget,budget_ci,budget,budget_core,dvb_ttpci
> video_buf 17221 1 saa7146_vv
> v4l2_common 5057 1 saa7146_vv
> v4l1_compat 11461 1 saa7146_vv
> videodev 7105 1 saa7146_vv
>
> again alot of these are not required.
>
>>I have the firmware installed in /usr/lib/hotplug/firmware
>>
>># ls -l /usr/lib/hotplug/firmware
>>total 300
>>-rw-r--r-- 1 root root 303104 Dec 29 17:46 tda1004x.bin
>>
>>This was from the /software/OEM/PCI/App/ttlcdacc.dll file in
>>tt_budget_217g.zip from technotrend.de.
>>
>>If this is different from your firmware, please could you send on the one
>>that works?
>>
>>
>
> I don't think you need any firmware for the old Nova-T. I certainly
> never installed any .bin files for DVB.
>
> Peter
>
>>Thanks again,
>>Tim
>>
>>
>>
>>
>>>I am running a vanilla 2.6.9 kernel, compiled up using the .config from
>>>FC3-2.6.9-861 - think that's right. You have to add in the tda1004x
>>> module
>>>that they leave out because of the firmware.
>>>Let me know if you want my .config file.
>>>Paul
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: Tim Squires [mailto:nt650@cheekymail.net]
>>>>Sent: Tuesday, January 11, 2005 12:06 PM
>>>>To: linux-dvb@linuxtv.org
>>>>Subject: [linux-dvb] Old NOVA-T (Philips) and 2.6 kernels
>>>>
>>>>Hi All,
>>>>
>>>>Has anyone has success with the old NOVA-T PCI cards and FC3 or 2.6
>>>>kernels?
>>>>
>>>>Thanks,
>>>>Tim
>>>>
>>>>
>>>>Some details follow.
>>>>
>>>>
>>>>
>>>>I've spent weeks on this with not much joy. I've not seen a dvb picture
>>>>yet....
>>>>
>>>>Kernels
>>>>2.6.10 (with and without patches from bytesex.org)
>>>>2.6.9 (with and without patches from bytesex.org)
>>>>2.6.9-1.681_FC3
>>>>2.6.9-1.667
>>>>
>>>>I have an old Hauppauge WinTV bt787 card that works fine with MythTV.
>>>>
>>>>A few weeks ago I installed a Hauppauge NOVA-T PCI, one of the older
>>>>ones with the Philips chipset. My system is FC3.
>>>>
>>>>For the original MythTV setup I used the great guide on
>>>>http://wilsonet.com/mythtv/fcmyth.php
>>>>
>>>>For the additional dvb card the http://www.ethics-gradient.net/myth/
>>>>guide but have been stumped on using tzap and mplayer to test the
>>>>installation.
>>>>
>>>>tzap -r "BBC ONE" reports that is FE_HAS_LOCK
>>>>
>>>>and dvbstream with mplayer just sits there with no picture...
>>>>
>>>>dvbstream -o -ps -qam 16 -cr 3_4 600 601 | mplayer -
>>>>
>>>>as does streaming directly from device.
>>>>
>>>>mplayer /dev/dvb/adaptor0/dvr0
>>>>
>>>>/var/log/messages looks OK
>>>>
>>>>Jan 11 08:37:13 sam kernel: saa7146: register extension 'budget dvb'.
>>>>Jan 11 08:37:13 sam kernel: PCI: Enabling device 0000:00:10.0 (0004 ->
>>>>0006)
>>>>Jan 11 08:37:13 sam kernel: ACPI: PCI Interrupt Link [LNKD] enabled at
>>>>IRQ 11
>>>>Jan 11 08:37:13 sam kernel: ACPI: PCI interrupt 0000:00:10.0[A] -> GSI
>>>> 11
>>>>(level, low) -> IRQ 11
>>>>Jan 11 08:37:13 sam kernel: saa7146: found saa7146 @ mem f88e0000
>>>>(revision 1, irq 11) (0x13c2,0x1005).
>>>>Jan 11 08:37:13 sam kernel: DVB: registering new adapter
>>>>(TT-Budget/WinTV-NOVA-T PCI).
>>>>Jan 11 08:37:13 sam autofs: automount startup succeeded
>>>>Jan 11 08:37:13 sam kernel: adapter has MAC addr = 00:d0:5c:20:2c:c0
>>>>Jan 11 08:37:13 sam kernel: DVB: registering frontend 0 (LSI L64781
>>>>DVB-T)...
>>>>
>>>>
>>>>
>>>>--
>>>>This message has been scanned for viruses and
>>>>dangerous content by OpenProtect(http://www.openprotect.com), and is
>>>>believed to be clean.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>--
>>>This message has been scanned for viruses and
>>>dangerous content by OpenProtect(http://www.openprotect.com), and is
>>>believed to be clean.
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by OpenProtect(http://www.openprotect.com), and is
> believed to be clean.
>
>
--
This message has been scanned for viruses and
dangerous content by OpenProtect(http://www.openprotect.com), and is
believed to be clean.
Home |
Main Index |
Thread Index