Re: [linux-dvb] VP 1041: Is anybody able to tune to DVBS2 or DSS?
Just to clarify, the diseqc switches mentioned do not work reliably with any of the D-Sat cards in my PC (one Skystar HD2 DVB-S/DVB-S2, three Skystar 2 (DVB-S only)), the VP-1041 driver is not the issue - it was best to remove the switch as they can be troublesome, in my case they tend to block tuning to either horizontal or vertical transponders (apparently randomly over time). All three switches work fine with a Technomate TM1000 receiver, incidentally. If of any help, these are the commands I am using to tune successfully and reliably to DVB-S2 transponders on Astra 2D (28East). I am using the current mantis tree with a Skystar HD2 card, using the replacement szap.c from the VP1041 wiki. Entry in channels.conf: DVBS2:11798:h:1:29500:513:641:2:2018 szap command line and output: [EMAIL PROTECTED]:~/linuxtv-dvb-apps-1.1.1/util/szap# ./szap -r -p -a 5 -l UNIVERSAL -t 2 DVBS2 reading channels from file '/root/.szap/channels.conf' zapping to 11 'DVBS2': sat 1, frequency = 11798 MHz H, symbolrate 2950, vpid = 0x0201, apid = 0x0281 sid = 0x0002 Querying info .. Delivery system=DVB-S2 using '/dev/dvb/adapter5/frontend0' and '/dev/dvb/adapter5/demux0' -- Using 'STB0899 DVB-S2' DVB-S2 do_tune: API version=3, delivery system = 2 do_tune: Frequency = 1198000, Srate = 2950 do_tune: Frequency = 1198000, Srate = 2950 couldn't find pmt-pid for sid 0002 status 1a | signal 05aa | snr 0030 | ber | unc fffe | FE_HAS_LOCK status 1a | signal 05aa | snr 002f | ber | unc fffe | FE_HAS_LOCK status 1a | signal 05aa | snr 002f | ber 00516155 | unc fffe | FE_HAS_LOCK status 1a | signal 05aa | snr 002e | ber 00145855 | unc fffe | FE_HAS_LOCK status 1a | signal 05aa | snr 002f | ber | unc fffe | FE_HAS_LOCK status 1a | signal 05aa | snr 002f | ber | unc fffe | FE_HAS_LOCK status 1a | signal 05aa | snr 002e | ber | unc fffe | FE_HAS_LOCK status 1a | signal 05aa | snr 002f | ber | unc fffe | FE_HAS_LOCK [EMAIL PROTECTED]:~/linuxtv-dvb-apps-1.1.1/util/szap# In a different shell, output of scan while the card is tuned using szap above: [EMAIL PROTECTED]:# scan -c -a 5 using '/dev/dvb/adapter5/frontend0' and '/dev/dvb/adapter5/demux0' 0x 0x0ef9: pmt_pid 0x0102 BSkyB -- Sky Screen 1HD (running, scrambled) 0x 0x0f23: pmt_pid 0x0103 BSkyB -- Channel 4 HD (running, scrambled) 0x 0x1034: pmt_pid 0x BSkyB -- Anytime (???, scrambled) dumping lists (4 services) Sky Screen 1HD (0x0ef9) 86:V 0514 A 0642 (NAR) TT 2305 AC3 0662 Channel 4 HD (0x0f23) 86:V 0513 AC3 0661 [0f38] (0x0f38) 00: Anytime (0x1034) 04: Done. [EMAIL PROTECTED]:# HTH, Tim. On 8 Mar 2008, at 22:00, Simeon Simeonov wrote: Just for the record: in my case eliminating the diseqc did not make a difference. - Original Message From: Manu Abraham [EMAIL PROTECTED] To: Tim Hewett [EMAIL PROTECTED] Cc: Simeon Simeonov [EMAIL PROTECTED]; linux-dvb@linuxtv.org Sent: Saturday, March 8, 2008 11:50:33 AM Subject: Re: [linux-dvb] VP 1041: Is anybody able to tune to DVBS2 or DSS? Tim Hewett wrote: Simeon, It doesn't matter re: the diseqc commands, with no switch present will be nothing listening, assuming there is nothing else connected such as a rotor. The SEC equipment should work fine AFAICS. The bad aspect of the tests were that no one really came up with any real logs that could really reproduced a driver bug or a hardware bug. Nevertheless, there had been an interesting post on the VDR mailing list. http://www.linuxtv.org/pipermail/vdr/2008-March/016068.html Regards, Manu Tim. On 8 Mar 2008, at 01:27, Simeon Simeonov wrote: Thanks for the answer Tim! That's a good point - I do have a switch. I will try bypassing it but do you still send the diseqc commands or I have to get rid of them? Simeon - Original Message From: Tim Hewett [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Tim Hewett [EMAIL PROTECTED]; linux-dvb@linuxtv.org Sent: Friday, March 7, 2008 5:18:43 PM Subject: VP 1041: Is anybody able to tune to DVBS2 or DSS? Yes, I have the Skystar HD2 tuning to DVB-S2 transponders using the replacement szap.c mentioned on the wiki page, then listing the channels using 'scan -c -a n' to prove proper reception, all using the current mantis tree. No hacks were needed, it works out of the box every time now that the mantis tree has been updated to support the HD2 card (same one as the VP-1041). If you are using a Diseqc switch then get rid of it for now, mine was causing lots of unreliability. I tried three different types of Diseqc switch, all were the same. Got rid of them then it all started working. Tim. Hi, I am curious to find out if anybody is able to use Twinhan/ Azurware VP-1041
Re: [linux-dvb] VP 1041: Is anybody able to tune to DVBS2 or DSS?
Simeon, It doesn't matter re: the diseqc commands, with no switch present will be nothing listening, assuming there is nothing else connected such as a rotor. Tim. On 8 Mar 2008, at 01:27, Simeon Simeonov wrote: Thanks for the answer Tim! That's a good point - I do have a switch. I will try bypassing it but do you still send the diseqc commands or I have to get rid of them? Simeon - Original Message From: Tim Hewett [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Tim Hewett [EMAIL PROTECTED]; linux-dvb@linuxtv.org Sent: Friday, March 7, 2008 5:18:43 PM Subject: VP 1041: Is anybody able to tune to DVBS2 or DSS? Yes, I have the Skystar HD2 tuning to DVB-S2 transponders using the replacement szap.c mentioned on the wiki page, then listing the channels using 'scan -c -a n' to prove proper reception, all using the current mantis tree. No hacks were needed, it works out of the box every time now that the mantis tree has been updated to support the HD2 card (same one as the VP-1041). If you are using a Diseqc switch then get rid of it for now, mine was causing lots of unreliability. I tried three different types of Diseqc switch, all were the same. Got rid of them then it all started working. Tim. Hi, I am curious to find out if anybody is able to use Twinhan/ Azurware VP-1041 with the mantis drivers to tune to standards other than DVBS - DVBS2 and DSS? Thanks, Simeon Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] VP 1041: Is anybody able to tune to DVBS2 or DSS?
Yes, I have the Skystar HD2 tuning to DVB-S2 transponders using the replacement szap.c mentioned on the wiki page, then listing the channels using 'scan -c -a n' to prove proper reception, all using the current mantis tree. No hacks were needed, it works out of the box every time now that the mantis tree has been updated to support the HD2 card (same one as the VP-1041). If you are using a Diseqc switch then get rid of it for now, mine was causing lots of unreliability. I tried three different types of Diseqc switch, all were the same. Got rid of them then it all started working. Tim. Hi, I am curious to find out if anybody is able to use Twinhan/ Azurware VP-1041 with the mantis drivers to tune to standards other than DVBS - DVBS2 and DSS? Thanks, Simeon ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)
Manu, The Diseqc switch has been removed and now all polarities tune, and DVB-S2 works as well. Thanks! Tim. On 24 Feb 2008, at 00:38, Manu Abraham wrote: Tim Hewett wrote: Manu, Thanks, it now tunes to horizontal transponders though not vertical ones. I think others have been having similar symptoms with the mantis/multiproto trees. Can someone replicate this behaviour: not tuning to vertical transponders ? Do you have any switches or a rotor in the SEC chain ? It won't tune to any DVB-S2 transponder, but that has not changed since previously. Hmm .. Are you really sure ? Messages in dmesg for successful tuning: [ 402.455361] dvb_frontend_ioctl: DVBFE_GET_INFO [ 402.455366] stb0899_get_info: Querying DVB-S info [ 402.556373] newfec_to_oldfec: Unsupported FEC 9 [ 402.556377] dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 [ 402.556998] mantis start feed dma [ 402.557255] stb0899_search: set DVB-S params [ 402.567810] stb6100_set_bandwidth: Bandwidth=5161 [ 402.569927] stb6100_get_bandwidth: Bandwidth=5200 [ 402.581331] stb6100_get_bandwidth: Bandwidth=5200 [ 402.613394] stb6100_set_frequency: Frequency=1023000 [ 402.615510] stb6100_get_frequency: Frequency=1022994 [ 402.621496] stb6100_get_bandwidth: Bandwidth=5200 [ 404.541047] _stb0899_read_reg: Read error, Reg=[0xf525], Status=-121 [ 404.541749] mantis stop feed and dma I will need the stb0899 and stb6100 modules to be loaded with verbose=5 parameter, for understanding what's happening. Regards, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)
I have three diseqc switches, all different models, they all behave in this way. The PC also has three Skystar 2 (non HD) card and they all have trouble with these switches. I had hoped that because the Skystar HD2 has its own power supply separate from the PCI bus, that might help, but no. My Technomate TM1000 receiver has no problems with any of the switches. Different subject: I want to modify dvbstream to be able to tune the SkyStar HD2, is there any information on the changes to the API? I have tried to follow the changes made to szap.c, but so far without any success in terms of getting dvbstream to tune. Tim. On 24 Feb 2008, at 16:27, Manu Abraham wrote: Tim Hewett wrote: Manu, The Diseqc switch has been removed and now all polarities tune, and DVB-S2 works as well. Bad diseqc switch ? Regards, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)
] mantis_ack_wait (0): Slave RACK Fail ! [ 320.987088] stb6100_get_frequency: Frequency=487856768 [ 323.992976] mantis_ack_wait (0): Slave RACK Fail ! [ 323.993157] stb6100_get_bandwidth: Bandwidth=-32512 HTH, Tim. On 23 Feb 2008, at 22:22, Manu Abraham wrote: Tim Hewett wrote: Gernot, I have now tried the mantis tree. It also needed the MANTIS_VP_1041_DVB_S2 #define to be changed to 0x0001 for this card, but after doing that it was recognised: Applied the ID's to the mantis tree alongwith some other fixes/ optimizations. Please do test the updated mantis tree. Regards, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)
] stb6100_set_bandwidth: Bandwidth=5161 [ 430.849576] stb6100_get_bandwidth: Bandwidth=5200 [ 430.861267] stb6100_get_bandwidth: Bandwidth=5200 [ 430.894753] stb6100_set_frequency: Frequency=1068000 [ 430.897148] stb6100_get_frequency: Frequency=1068002 [ 430.902855] stb6100_get_bandwidth: Bandwidth=5200 [ 431.133659] mantis stop feed and dma HTH, Tim. On 23 Feb 2008, at 23:43, Manu Abraham wrote: Tim Hewett wrote: Manu, I tried the changes, the card is now recognised at boot time without needing any manual changes to the code. However it now no longer tunes: Sigh! missed out something while i carried forward something. I have applied the fix to the tree just now. Please try again. Regards, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)
Manu, On 24 Feb 2008, at 00:38, Manu Abraham wrote: Do you have any switches or a rotor in the SEC chain ? I have a Diseqc 1.0 switch on this card. I just retested using Technisat's Windows software and the vertical transponders still don't work, same for DVB-S2 transponders. Strange, they worked perfectly every time previously, e.g. BBCHD on 10847/v on Astra 2D. But not today. For now, my system is the problem. Definitely still no tuning to DVB-S2 transponders under Linux, horizontal or vertical. Horizontal ones work ok with Technisat's Windows software. Tim. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Technisat Skystar HD2 success
The Technisat Skystar HD2 card (Azurewave AD SP400 clone) has now been used successfully with the current mantis tree. It is necessary to use szap to set DVB-S2 mode first, even if the transponder you want is DVB-S (discovered by chance). If this isn't done then it does not lock on to the frequency. So you do the following: szap -r -p -l UNIVERSAL -t 2 -a card channel CTRL-C that after it has settled, then: szap -r -p -l UNIVERSAL -t 0 -a card channel Then (leaving the above line running) you can do: cat /dev/dvb/adaptorn/dvr0 file.mpg and it then records error-free video. As mentioned previously you need to change linux/drivers/media/dvb/ mantis/mantis_vp1041.h before building the drivers. Change the line: #define MANTIS_VP_1041_DVB_S2 0x0031 to #define MANTIS_VP_1041_DVB_S2 0x0001 This will let the driver detect the card properly on bootup due to its different subsystem IDs, otherwise the frontend isn't registered. HTH, Tim. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)
I'm trying to get a new Technisat Skystar HD2 working. It looks like it is a Twinhan VP-1041/Azurewave AD SP400 rebadge. The card hardware and satellite feed has been confirmed to work ok under Windows using Technisat's software. I am using the current multiproto DVB drivers, downloaded today. These were patched, built and installed successfully as described for the Azurewave AD SP400 in the linuxdvb wiki, but the card was not recognised on bootup even though it was allocated a DVB adaptor number. This appeared in dmesg: [ 57.359723] found a UNKNOWN PCI UNKNOWN device on (01:06.0), [ 57.359802] Mantis Rev 1 [1ae4:0001], irq: 16, latency: 32 [ 57.359858] memory: 0xe510, mmio: 0xc20fc000 [ 57.363015] MAC Address=[00:08:c9:e0:26:92] [ 57.363133] mantis_alloc_buffers (0): DMA=0x1b7a cpu=0x81001b7a size=65536 [ 57.363242] mantis_alloc_buffers (0): RISC=0x1ae24000 cpu=0x81001ae24000 size=1000 [ 57.363348] DVB: registering new adapter (Mantis dvb adapter) This is the output of lspci -vvn: 01:06.0 0480: 1822:4e35 (rev 01) Subsystem: 1ae4:0001 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 (2000ns min, 63750ns max) Interrupt: pin A routed to IRQ 16 Region 0: Memory at e510 (32-bit, prefetchable) [size=4K] This is the output of lsusb -vv: 01:06.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] (rev 01) Subsystem: Unknown device 1ae4:0001 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 (2000ns min, 63750ns max) Interrupt: pin A routed to IRQ 16 Region 0: Memory at e510 (32-bit, prefetchable) [size=4K] Note that subsystem IDs 1ae4:0001 are different to those listed in the wiki for the Azurewave (1822:0031). I changed #define MANTIS_VP_1041_DVB_S2 in linux/drivers/media/dvb/ mantis/mantis_vp1041.h from 0x0031 to 0x0001, which changed the dmesg output on reboot to this: [ 59.546375] found a VP-1041 PCI DVB-S/DVB-S2 device on (01:06.0), [ 59.546456] Mantis Rev 1 [1ae4:0001], irq: 16, latency: 32 [ 59.546512] memory: 0xe510, mmio: 0xc20fc000 [ 59.549609] MAC Address=[00:08:c9:e0:26:92] [ 59.549719] mantis_alloc_buffers (0): DMA=0x1b7b cpu=0x81001b7b size=65536 [ 59.549827] mantis_alloc_buffers (0): RISC=0x1af43000 cpu=0x81001af43000 size=1000 [ 59.549933] DVB: registering new adapter (Mantis dvb adapter) [ 60.137583] stb0899_attach: Attaching STB0899 [ 60.137665] mantis_frontend_init (0): found STB0899 DVB-S/DVB-S2 frontend @0x68 [ 60.152161] stb6100_attach: Attaching STB6100 [ 60.168021] DVB: registering frontend 3 (STB0899 Multistandard)... So that change seemed to cause the card to be recognised. Then I tried the replacement scan and szap as suggested by the Azurewave wiki, but the card will not tune. So it appears to be almost working, but I'm not sure what tests to try or changes to make to see if it will work.___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)
Gernot, I have now tried the mantis tree. It also needed the MANTIS_VP_1041_DVB_S2 #define to be changed to 0x0001 for this card, but after doing that it was recognised: [ 56.586237] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16 [ 56.586330] ACPI: PCI Interrupt :01:06.0[A] - Link [APC1] - GSI 16 (level, low) - IRQ 16 [ 56.586556] irq: 16, latency: 32 [ 56.586557] memory: 0xe510, mmio: 0xc20f8000 [ 56.586708] found a VP-1041 PCI DSS/DVB-S/DVB-S2 device on (01:06.0), [ 56.586791] Mantis Rev 1 [1ae4:0001], irq: 16, latency: 32 [ 56.586847] memory: 0xe510, mmio: 0xc20f8000 [ 56.589867] MAC Address=[00:08:c9:e0:26:92] [ 56.589972] mantis_alloc_buffers (0): DMA=0x1aa1 cpu=0x81001aa1 size=65536 [ 56.590081] mantis_alloc_buffers (0): RISC=0x1b7f cpu=0x81001b7f size=1000 [ 56.590187] DVB: registering new adapter (Mantis dvb adapter) [ 57.106676] stb0899_write_regs [0xf1b6]: 02 [ 57.107730] stb0899_write_regs [0xf1c2]: 00 [ 57.108781] stb0899_write_regs [0xf1c3]: 00 [ 57.110884] _stb0899_read_reg: Reg=[0xf000], data=82 [ 57.110964] stb0899_get_dev_id: ID reg=[0x82] [ 57.111040] stb0899_get_dev_id: Device ID=[8], Release=[2] [ 57.117425] _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x0400], Offset=[0xf334], Data=[0x444d4431] [ 57.123732] _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x0400], Offset=[0xf33c], Data=[0x0001] [ 57.123735] stb0899_get_dev_id: Demodulator Core ID=[DMD1], Version=[1] [ 57.130121] _stb0899_read_s2reg Device=[0xfafc], Base address=[0x0800], Offset=[0xfa2c], Data=[0x46454331] [ 57.136428] _stb0899_read_s2reg Device=[0xfafc], Base address=[0x0800], Offset=[0xfa34], Data=[0x0001] [ 57.136430] stb0899_get_dev_id: FEC Core ID=[FEC1], Version=[1] [ 57.136509] stb0899_attach: Attaching STB0899 [ 57.136586] mantis_frontend_init (0): found STB0899 DVB-S/DVB-S2 frontend @0x68 [ 57.136690] stb6100_attach: Attaching STB6100 [ 57.137118] DVB: registering frontend 1 (STB0899 Multistandard)... However it still doesn't tune. e.g.: [EMAIL PROTECTED]:~/linuxtv-dvb-apps-1.1.1/util/szap# ./szap -r -p -l UNIVERSAL -t 0 -a 1 BBC1West reading channels from file '/root/.szap/channels.conf' zapping to 1 'BBC1West': sat 0, frequency = 10818 MHz V, symbolrate 2200, vpid = 0x0901, apid = 0x0904 sid = 0x0002 Querying info .. Delivery system=DVB-S using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' -- Using 'STB0899 DVB-S' DVB-S do_tune: API version=3, delivery system = 0 do_tune: Frequency = 1068000, Srate = 2200 do_tune: Frequency = 1068000, Srate = 2200 Whereas this is the result when using an ordinary Skystar 2 card (which works fine): [EMAIL PROTECTED]:~/linuxtv-dvb-apps-1.1.1/util/szap# ./szap -r -p -l UNIVERSAL -t 0 -a 0 BBC1West reading channels from file '/root/.szap/channels.conf' zapping to 1 'BBC1West': sat 0, frequency = 10818 MHz V, symbolrate 2200, vpid = 0x0901, apid = 0x0904 sid = 0x0002 Querying info .. Delivery system=DVB-S using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' -- Using 'ST STV0299 DVB-S' DVB-S do_tune: API version=3, delivery system = 0 do_tune: Frequency = 1068000, Srate = 2200 do_tune: Frequency = 1068000, Srate = 2200 couldn't find pmt-pid for sid 0002 status 1f | signal cac8 | snr cb6d | ber 61d0 | unc | FE_HAS_LOCK status 1f | signal c9f0 | snr d15e | ber | unc | FE_HAS_LOCK status 1f | signal ca1d | snr d176 | ber | unc | FE_HAS_LOCK Using szap on the Skystar HD2 caused lots of logs to dmesg: [ 97.691029] stb0899_search: set DVB-S params [ 97.691112] stb0899_search: delivery system=1 [ 97.691188] stb0899_search: Frequency=1068000, Srate=2200 [ 97.691269] stb0899_search: Parameters IN RANGE [ 97.692611] _stb0899_read_reg: Reg=[0xf1c2], data=20 [ 97.694085] _stb0899_read_reg: Reg=[0xf1c3], data=00 [ 97.694166] stb0899_set_delsys: Delivery System -- DVB-S [ 97.695848] _stb0899_read_reg: Reg=[0xf533], data=01 [ 97.695929] stb0899_write_regs [0xf533]: 09 [ 97.697420] stb0899_write_regs [0xf548]: b1 [ 97.698913] stb0899_write_regs [0xf549]: 40 [ 97.700410] stb0899_write_regs [0xf54a]: 42 [ 97.701778] stb0899_write_regs [0xf54b]: 12 [ 97.704225] _stb0899_read_reg: Reg=[0xff11], data=00 [ 97.704308] stb0899_write_regs [0xff11]: 80 [ 97.705797] stb0899_write_regs [0xf1c2]: 78 07 [ 97.707631] stb0899_set_mclk: state-config=882654a0 [ 97.707713] stb0899_set_mclk: mdiv=21 [ 97.707788] stb0899_write_regs [0xf1b3]: 15 [ 97.710338] _stb0899_read_reg: Reg=[0xf1b3], data=15 [ 97.710427] stb0899_get_mclk: div=21, mclk=9900 [ 97.710505] stb0899_set_mclk: MasterCLOCK=9900 [ 97.710582] stb0899_search: DVB-S delivery system [ 97.712051] _stb0899_read_reg:
Re: [linux-dvb] How to force adaptor order when using 2 DVB cards?
I have adapted dvbstream to allow an adaptor's string ident (e.g. ST
STV0299 DVB-S for a Technisat SkyStar 2 DVB-S PCI card, i.e. the
string which appears in dmesg when the DVB frontend is added) to be
passed as the argument to '-c' instead of just the adaptor number. e.g.:
dvbstream -n 4400 -o -f 10847 -p v -s 22000 -c ST STV0299 DVB-S -D 1
0 258 2327 2328 2329
I have three SkyStar 2 cards, a Wideview USB, AF9005 USB and AF9015
USB all in one PC, so they often are assigned to different card
numbers on boot up. Using the ident string allows the device's actual
adaptor number to be searched for each time.
The change also allows individual cards to be addressed if you have
more than one of the same type, by adding the number to the end of the
string delimited by ':', e.g. ST STV0299 DVB-S:1 means the second
SkyStar card, even if it is at card number 4 with the first being at
card number 1 (with other devices in between). I need this because
each card has a different LNB configuration, e.g. one has a diseqc
switch. Fortunately the ordering of the PCI cards stays the same
relative to each other, even if they aren't always assigned the same
adaptor number.
The code is a total hack but if it helps then I can publish it,
perhaps it could even migrate into MythTV etc.
There are various other hacks I've added to dvbstream, e.g. to avoid
the consequences of constantly changing PID assignments (as happens
sometimes for the BBC and ITV in the UK) you can specify a channel
name, e.g. BBC 2 England and have dvbstream discover the PIDs in the
same way as 'scan -c'.
HTH,
Tim.
Yep, it's horrible. This is what I did, the adapters 0,1,2 are still
there but MythTV is configured to used 4,5 and 6.
# My own DVB hell
# Twinhan DVB-S Card
#
KERNEL==dvb[0-9].frontend0, ATTR{dev}==212:3,
symlink+=dvb/adapter4/frontend0, GROUP=video
KERNEL==dvb[0-9].demux0, ATTR{dev}==212:4,
symlink+=dvb/adapter4/demux0, GROUP=video
KERNEL==dvb[0-9].net0, ATTR{dev}==212:7,
symlink+=dvb/adapter4/net0, GROUP=video
KERNEL==dvb[0-9].dvr0, ATTR{dev}==212:5,
symlink+=dvb/adapter4/dvr0, GROUP=video
#
# Nova-T Stick 1
#
KERNEL==dvb[0-9].frontend0, ATTRS{serial}==4030489593,
symlink+=dvb/adapter5/frontend0, GROUP=video
KERNEL==dvb[0-9].demux0, ATTRS{serial}==4030489593,
symlink+=dvb/adapter5/demux0, GROUP=video
KERNEL==dvb[0-9].net0, ATTRS{serial}==4030489593,
symlink+=dvb/adapter5/net0, GROUP=video
KERNEL==dvb[0-9].dvr0, ATTRS{serial}==4030489593,
symlink+=dvb/adapter5/dvr0, GROUP=video
#
# Nova-T Stick 2
#
KERNEL==dvb[0-9].frontend0, ATTRS{serial}==4027844315,
symlink+=dvb/adapter6/frontend0, GROUP=video
KERNEL==dvb[0-9].demux0, ATTRS{serial}==4027844315,
symlink+=dvb/adapter6/demux0, GROUP=video
KERNEL==dvb[0-9].net0, ATTRS{serial}==4027844315,
symlink+=dvb/adapter6/net0, GROUP=video
KERNEL==dvb[0-9].dvr0, ATTRS{serial}==4027844315,
symlink+=dvb/adapter6/dvr0, GROUP=video
I'm not sure if gmail has split the lines above but each actual line
should start with KERNEL.
Sim
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Equinux TubeStick (AF9015) working fine with Antti and Manu's driver
The Equinux TubeStick (USB2 DVB-T device for MacOS X) work great with the AF9015 patched drivers. I had to alter the second part of the USB ID from 0x9016 to 0x9015 to make it be recognised, but after that it is just fine. Thanks! It is also able to record an entire multiplex, e.g. using the pseudo PID of 8192 with dvbstream. BTW the driver logs the device as AF9013 when it is detected, is that right? One request: to have a way to shut the device down when the host no longer needs it, e.g. when halting. The LED remains lit after power down and it stays quite warm, I guess the hardware is still active. This used to be a problem with the Mac software (called TheTube) but recent updates have fixed it so that the device powers down when the application is quit. It would be great to be able to add a line to the halt scripts to have it powered down at that time, or maybe even power the device down automatically when no application has it open any more. Thanks again, Tim. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Re: how to record entire TS?
Hello, I know that if you use dvbstream to record then it provides a wildcard PID of 8192 for recording a whole transponder or multiplex. Works fine for me when using Technisat Sky Star 2 and Twinhan VP-1025 PCI D-Sat cards, but it doesn't work with a Freecom Wideview USB2 DTT receiver for some reason. HTH, Tim. Hi, I have looked at the azap.c code and I see how it creates PES filters to select specific video and audio PIDs. Then, when azap is used with -r, packets with those PIDs are available on the dvr device file. However, how would I go about making the entire transport stream (including PSI packets) available for recording? I assume there is a way to send the whole thing to the dvr device file, anyone know how? Thanks. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Equinux TubeStick support - WideView device?
Is there a way to have the Equinux TubeStick work with the DVB drivers? It is a USB2 DVB-T device for the Mac, but the OS X software is very basic - no ability to schedule recordings for example. I suspect it is a WideView-based device since the same software recognises other WideView ones like the Terratec and Freecom, but the TubeStick isn't recognised by the linuxtv drivers. Are there any tests I can do to help get it working? Here is the output of dmesg when the device is connected: [ 9329.979120] usb 2-1: new high speed USB device using ehci_hcd and address 4 [ 9330.117276] usb 2-1: configuration #1 chosen from 1 choice This is the output of lsusb -v for the device: Bus 002 Device 004: ID 15a4:9015 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x15a4 idProduct 0x9015 bcdDevice2.00 iManufacturer 0 iProduct0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 46 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 4 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x85 EP 5 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 1 Device Status: 0x (Bus Powered) Tim. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Adjusting drivers for slow CPUs - buffer overruns suspected
I am wondering if there are ways to adjust the DVB drivers to suit a slow CPU. The background is that I have two Technisat SkyStar2 DVB-S cards in a PIII 550MHz PC. If I try to record an entire transport stream the recording suffers from drops and gaps, something which doesn't happen when recording one video and audio PID, presumably because their five hardware PID filters are doing the hard work. Before upgrading to the 2.6 kernel (ages ago) the same PC would happily record an entire transport stream concurrently on each card without any data loss, so it doesn't seem as if the PC is fundamentally running out of steam. Something changed in the DVB drivers for the 2.6 kernel which started causing problems it seems. Now I've added a Twinhan VP-1025, which has no hardware filters at all apparently, I'm getting data drops whether I record an entire transport stream or just one audio and video PID, I guess because the filtering is done in the CPU. So I'm wondering if there are tweaks which I can make to the DVB drivers, maybe to increase buffer sizes, or some other adjustment, to try to stop these drops happening. Any ideas? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Glitches in audio and video when recording from BTTV Twinhan VP-1025
I have a Twinhan VP-1025 PCI card (BTTV). It tunes fine and records ok except that every few minutes the recording has glitches which disrupt the audio and video at irregular intervals. The Twinhan card works fine using Twinhan's windows software and the same feed as when used from Linux, so it seems to be a pure Linux issue. The drivers load and detect the card without any errors. I've tried running the latest drivers (extracted using Mercuurial and rebuilt and re-tested just before sending this message) with kernel 2.6.20, but the problem still happens. Can anyone help? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Driver loading race condition
I have a Twinhan VP-1025 DVB-S card (bt878) and a Terratec DTT (dtt200u) USB2 device. It is a lottery as to which gets adapter 0 and adapter 1 at boot time. Is there a way to delay one driver's startup or module load so that the assignment of adapter numbers is the same each time the host is booted, or is there some other way to make this happen? (probably a common question but can't find anything in the archives/ FAQ/wiki, sorry) Thanks. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
re: [linux-dvb] Please see if you can help: Twinhan VP 1025 DVB-S PCI Card
(original post: http://www.linuxtv.org/pipermail/linux-dvb/2006- August/012188.html) Dave, I had the exact same problem. First the card would be recognised but wouldn't appear in /dev/dvb (solved by following/adapting instructions here: http://ubuntuforums.org/showthread.php?p=1777028), then once it did have device nodes it wouldn't tune. This was solved by coldstarting, booting into Windows and using Twinhan's software to tune the card. It was then warm booted into Kubuntu Dapper and the card now worked. Previously dvbsnoop -s feinfo showed this: Basic capabilities: Name: DST DVB-S Frontend-type: QPSK (DVB-S) Frequency (min): 950.000 MHz Frequency (max): 2150.000 MHz Frequency stepsiz: 1.000 MHz Frequency tolerance: 29500 Symbol rate (min): 1.00 MSym/s Symbol rate (max): 45.00 MSym/s Symbol rate tolerance: 0 ppm Notifier delay: 0 ms Frontend capabilities: auto inversion FEC AUTO QPSK Current parameters: Frequency: 0.000 MHz Inversion: AUTO Symbol rate: 22.00 MSym/s FEC: FEC AUTO then after the trick using Twinhan's Windows software it showed this: Basic capabilities: Name: DST DVB-S Frontend-type: QPSK (DVB-S) Frequency (min): 950.000 MHz Frequency (max): 2150.000 MHz Frequency stepsiz: 1.000 MHz Frequency tolerance: 29500 Symbol rate (min): 1.00 MSym/s Symbol rate (max): 45.00 MSym/s Symbol rate tolerance: 0 ppm Notifier delay: 0 ms Frontend capabilities: auto inversion FEC AUTO QPSK Current parameters: Frequency: 1053.000 MHz Inversion: OFF Symbol rate: 22.00 MSym/s FEC: FEC AUTO Then it worked fine - note the frequency no longer is 0.000 MHz, however it does return to 0 after a cold boot but the card still works fine. So it looks like the card needs to be used from Windows first, the only problem I have left now is a race condition between the Twinhan and a Terratec USB DVB-T receiver as to which gets to be device 0 - it changes between each boot. HTH, Tim. Hi list, I've been struggling with this for awhile now and I'm in need of some insight. The problem seems to be that the front end is unable to tune to or monitor a signal. Here is some background info: Card: Twinhan 1025 VisionPlus PCI DVB-S Kernel/Dist: 2.6.17.8, Debian testing. I just used hg to download the latest v4l-dvb and dvb-apps from Mercurial and everything compiled and installed fine. The drivers all modprobe fine. I modpobe in this order: dvb-core bttv dvb-bt8xx dst Is there anything I'm missing there? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Can't build dvb-kernel under 2.4
Hi,
For several weeks I've been updating my dvb-kernel CVS tree and
trying to build it, but each time the build fails. My original checkout
of
it near the start of January built fine but I'd like to get some of the
updates to see if it fixes some things.
The kernel is 2.4.21-0.13mdk on Mandrake 9.1, the log is from an
attempt to build a dvb-kernel tree checked out from scratch today.
Regards,
Tim.
[EMAIL PROTECTED] root]# cd dvb-kernel/build-2.4
[EMAIL PROTECTED] build-2.4]# make clean ./getlinks make
find . -type l -exec rm {} \;
rm -f *~ .version
rm -f *.o *.d .*.o.flags *.o.flags *.o.cmd
rm -f TAGS
rm -f fdump av7110_firm.h dsp_dec2000t.h dsp_dec2540t.h dsp_dec3000s.h
dvb-ttpci-info.txt
getting links from kernel-cvs driver
find . -type l -exec rm {} \;
rm -f *~ .version
rm -f *.o *.d .*.o.flags *.o.flags *.o.cmd
rm -f TAGS
rm -f fdump av7110_firm.h dsp_dec2000t.h dsp_dec2540t.h dsp_dec3000s.h
dvb-ttpci-info.txt
create symbolic link `include/linux/videodev.h' to
`/lib/modules/2.4.21-0.13mdk/build/include/linux/videodev.h'
create symbolic link `include/linux/videodev2.h' to
`/lib/modules/2.4.21-0.13mdk/build/include/linux/videodev2.h'
create symbolic link `include/media/saa7146.h' to
`../../../linux/include/media/saa7146.h'
create symbolic link `include/media/saa7146_vv.h' to
`../../../linux/include/media/saa7146_vv.h'
create symbolic link `av7110.c' to
`../linux/drivers/media/dvb/ttpci/av7110.c'
create symbolic link `av7110.h' to
`../linux/drivers/media/dvb/ttpci/av7110.h'
create symbolic link `av7110_av.c' to
`../linux/drivers/media/dvb/ttpci/av7110_av.c'
create symbolic link `av7110_av.h' to
`../linux/drivers/media/dvb/ttpci/av7110_av.h'
create symbolic link `av7110_ca.c' to
`../linux/drivers/media/dvb/ttpci/av7110_ca.c'
create symbolic link `av7110_ca.h' to
`../linux/drivers/media/dvb/ttpci/av7110_ca.h'
create symbolic link `av7110_hw.c' to
`../linux/drivers/media/dvb/ttpci/av7110_hw.c'
create symbolic link `av7110_hw.h' to
`../linux/drivers/media/dvb/ttpci/av7110_hw.h'
create symbolic link `av7110_ipack.c' to
`../linux/drivers/media/dvb/ttpci/av7110_ipack.c'
create symbolic link `av7110_ipack.h' to
`../linux/drivers/media/dvb/ttpci/av7110_ipack.h'
create symbolic link `av7110_ir.c' to
`../linux/drivers/media/dvb/ttpci/av7110_ir.c'
create symbolic link `av7110_v4l.c' to
`../linux/drivers/media/dvb/ttpci/av7110_v4l.c'
create symbolic link `budget-av.c' to
`../linux/drivers/media/dvb/ttpci/budget-av.c'
create symbolic link `budget-ci.c' to
`../linux/drivers/media/dvb/ttpci/budget-ci.c'
create symbolic link `budget-core.c' to
`../linux/drivers/media/dvb/ttpci/budget-core.c'
create symbolic link `budget-patch.c' to
`../linux/drivers/media/dvb/ttpci/budget-patch.c'
create symbolic link `budget.c' to
`../linux/drivers/media/dvb/ttpci/budget.c'
create symbolic link `budget.h' to
`../linux/drivers/media/dvb/ttpci/budget.h'
create symbolic link `fdump.c' to
`../linux/drivers/media/dvb/ttpci/fdump.c'
create symbolic link `ttpci-eeprom.c' to
`../linux/drivers/media/dvb/ttpci/ttpci-eeprom.c'
create symbolic link `ttpci-eeprom.h' to
`../linux/drivers/media/dvb/ttpci/ttpci-eeprom.h'
create symbolic link `dvb-ttusb-budget.c' to
`../linux/drivers/media/dvb/ttusb-budget/dvb-ttusb-budget.c'
create symbolic link `dvb-ttusb-dspbootcode.h' to
`../linux/drivers/media/dvb/ttusb-budget/dvb-ttusb-dspbootcode.h'
create symbolic link `ttusb_dec.c' to
`../linux/drivers/media/dvb/ttusb-dec/ttusb_dec.c'
create symbolic link `bt878.c' to
`../linux/drivers/media/dvb/bt8xx/bt878.c'
create symbolic link `bt878.h' to
`../linux/drivers/media/dvb/bt8xx/bt878.h'
create symbolic link `dvb-bt8xx.c' to
`../linux/drivers/media/dvb/bt8xx/dvb-bt8xx.c'
create symbolic link `dvb-bt8xx.h' to
`../linux/drivers/media/dvb/bt8xx/dvb-bt8xx.h'
create symbolic link `skystar2.c' to
`../linux/drivers/media/dvb/b2c2/skystar2.c'
create symbolic link `demux.h' to
`../linux/drivers/media/dvb/dvb-core/demux.h'
create symbolic link `dmxdev.c' to
`../linux/drivers/media/dvb/dvb-core/dmxdev.c'
create symbolic link `dmxdev.h' to
`../linux/drivers/media/dvb/dvb-core/dmxdev.h'
create symbolic link `dvb_compat.c' to
`../linux/drivers/media/dvb/dvb-core/dvb_compat.c'
create symbolic link `dvb_compat.h' to
`../linux/drivers/media/dvb/dvb-core/dvb_compat.h'
create symbolic link `dvb_demux.c' to
`../linux/drivers/media/dvb/dvb-core/dvb_demux.c'
create symbolic link `dvb_demux.h' to
`../linux/drivers/media/dvb/dvb-core/dvb_demux.h'
create symbolic link `dvb_filter.c' to
`../linux/drivers/media/dvb/dvb-core/dvb_filter.c'
create symbolic link `dvb_filter.h' to
`../linux/drivers/media/dvb/dvb-core/dvb_filter.h'
create symbolic link `dvb_frontend.c' to
`../linux/drivers/media/dvb/dvb-core/dvb_frontend.c'
create symbolic link `dvb_frontend.h' to
`../linux/drivers/media/dvb/dvb-core/dvb_frontend.h'
create symbolic link `dvb_functions.c' to
`../linux/drivers/media/dvb/dvb-core/dvb_functions.c'
create symbolic link
[linux-dvb] Re: Can't build dvb-kernel under 2.4
Michael, Thanks for your help, it works now. Regards, Tim. On 3 Feb 2004, at 16:36, Michael Hunold wrote: Hello Tim, For several weeks I've been updating my dvb-kernel CVS tree and trying to build it, but each time the build fails. My original checkout of it near the start of January built fine but I'd like to get some of the updates to see if it fixes some things. ../linux/include -I . -DCONFIG_DVB_AV7110_OSD -nostdinc -iwithprefix include -DKBUILD_BASENAME=v4l2_common -DEXPORT_SYMTAB -c v4l2-common.c v4l2-common.c:135: warning: `struct v4l2_prio_state' declared inside parameter list v4l2-common.c:135: warning: its scope is only this definition or declaration, which is probably not what you want v4l2-common.c: In function `v4l2_prio_init': v4l2-common.c:137: dereferencing pointer to incomplete type v4l2-common.c:137: dereferencing pointer to incomplete type v4l2-common.c:137: dereferencing pointer to incomplete type v4l2-common.c:137: dereferencing pointer to incomplete type v4l2-common.c:137: dereferencing pointer to incomplete type v4l2-common.c:137: dereferencing pointer to incomplete type v4l2-common.c: At top level: You have an old videodev2.h lying around somewhere, probably in /usr/src/linux/include/ Delete it or replace it with the copy from the build-2.4 directory. Regards, Tim. CU Michael. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: Hauppauge DEC2000-t
Alex,
On 1 Jan 2004, at 23:46, Alex Woods wrote:
Now I've got the SkyStar2 card recognised by the dvb-kernel drivers
and also the Hauppauge DEC2000-t (USB device) seems to be registered
as shown by dmesg, I only get one device showing in /dev/dvb.
Shouldn't
there be two, since both the SkyStar2 PCI and Hauppauge USB devices
have been detected? I'd love to be able to record from more than one
source at a time.
Make sure you have built the firmware into the driver. See
linux/Documentation/dvb/ttusb-dec.txt in dvb-kernel for details
I have just followed these instructions and there is a build error
(see attached shell log below). I have spaced out the individual
commands to make it more readable, so you can see the DEC2000
firmware being extracted and placed in the right directory prior to
building dvb-kernel.
Do you know what is wrong to cause the fdump error?
Cheers,
Alex
regards,
Tim.
[EMAIL PROTECTED] root]# unzip -j /mnt/pvr/dec215a.exe
Software/Oem/STB/App/Boot/STB_PC_T.bin
Archive: /mnt/pvr/dec215a.exe
warning [/mnt/pvr/dec215a.exe]: 30038 extra bytes at beginning or
within zipfile
(attempting to process anyway)
inflating: STB_PC_T.bin
[EMAIL PROTECTED] build-2.4]#
[EMAIL PROTECTED] root]# unzip -j /mnt/pvr/dec215a.exe
Software/Oem/STB/App/Boot/STB_PC_S.bin
Archive: /mnt/pvr/dec215a.exe
warning [/mnt/pvr/dec215a.exe]: 30038 extra bytes at beginning or
within zipfile
(attempting to process anyway)
inflating: STB_PC_S.bin
[EMAIL PROTECTED] build-2.4]#
[EMAIL PROTECTED] root]# mv STB_PC_T.bin /etc/dvb/dec2000t.bin
bin /etc/dvb/[EMAIL PROTECTED] root]# mv STB_PC_S.bin
/etc/dvb/dec3000s.bin
[EMAIL PROTECTED] root]# cd dvb-kernel/bui
build-2.4 build-template
[EMAIL PROTECTED] build-2.4]#
[EMAIL PROTECTED] root]# cd dvb-kernel/build-2.4/
[EMAIL PROTECTED] build-2.4]# make clean ./getlinks make
find . -type l -exec rm {} \;
rm -f *~ .version
rm -f *.o *.d .*.o.flags *.o.flags *.o.cmd
rm -f TAGS
rm -f fdump av7110_firm.h dsp_dec2000t.h dsp_dec3000s.h
dvb-ttpci-info.txt
getting links from kernel-cvs driver
find . -type l -exec rm {} \;
rm -f *~ .version
rm -f *.o *.d .*.o.flags *.o.flags *.o.cmd
rm -f TAGS
rm -f fdump av7110_firm.h dsp_dec2000t.h dsp_dec3000s.h
dvb-ttpci-info.txt
create symbolic link `include/media/saa7146.h' to
`../../../linux/include/media/saa7146.h'
create symbolic link `include/media/saa7146_vv.h' to
`../../../linux/include/media/saa7146_vv.h'
create symbolic link `av7110.c' to
`../linux/drivers/media/dvb/ttpci/av7110.c'
create symbolic link `av7110.h' to
`../linux/drivers/media/dvb/ttpci/av7110.h'
create symbolic link `av7110_ipack.c' to
`../linux/drivers/media/dvb/ttpci/av7110_ipack.c'
create symbolic link `av7110_ipack.h' to
`../linux/drivers/media/dvb/ttpci/av7110_ipack.h'
create symbolic link `av7110_ir.c' to
`../linux/drivers/media/dvb/ttpci/av7110_ir.c'
create symbolic link `budget-av.c' to
`../linux/drivers/media/dvb/ttpci/budget-av.c'
create symbolic link `budget-ci.c' to
`../linux/drivers/media/dvb/ttpci/budget-ci.c'
create symbolic link `budget-core.c' to
`../linux/drivers/media/dvb/ttpci/budget-core.c'
create symbolic link `budget-patch.c' to
`../linux/drivers/media/dvb/ttpci/budget-patch.c'
create symbolic link `budget.c' to
`../linux/drivers/media/dvb/ttpci/budget.c'
create symbolic link `budget.h' to
`../linux/drivers/media/dvb/ttpci/budget.h'
create symbolic link `fdump.c' to
`../linux/drivers/media/dvb/ttpci/fdump.c'
create symbolic link `ttpci-eeprom.c' to
`../linux/drivers/media/dvb/ttpci/ttpci-eeprom.c'
create symbolic link `ttpci-eeprom.h' to
`../linux/drivers/media/dvb/ttpci/ttpci-eeprom.h'
create symbolic link `dvb-ttusb-budget.c' to
`../linux/drivers/media/dvb/ttusb-budget/dvb-ttusb-budget.c'
create symbolic link `dvb-ttusb-dspbootcode.h' to
`../linux/drivers/media/dvb/ttusb-budget/dvb-ttusb-dspbootcode.h'
create symbolic link `ttusb_dec.c' to
`../linux/drivers/media/dvb/ttusb-dec/ttusb_dec.c'
create symbolic link `bt878.c' to
`../linux/drivers/media/dvb/bt8xx/bt878.c'
create symbolic link `bt878.h' to
`../linux/drivers/media/dvb/bt8xx/bt878.h'
create symbolic link `dvb-bt8xx.c' to
`../linux/drivers/media/dvb/bt8xx/dvb-bt8xx.c'
create symbolic link `dvb-bt8xx.h' to
`../linux/drivers/media/dvb/bt8xx/dvb-bt8xx.h'
create symbolic link `skystar2.c' to
`../linux/drivers/media/dvb/b2c2/skystar2.c'
create symbolic link `demux.h' to
`../linux/drivers/media/dvb/dvb-core/demux.h'
create symbolic link `dmxdev.c' to
`../linux/drivers/media/dvb/dvb-core/dmxdev.c'
create symbolic link `dmxdev.h' to
`../linux/drivers/media/dvb/dvb-core/dmxdev.h'
create symbolic link `dvb_compat.c' to
`../linux/drivers/media/dvb/dvb-core/dvb_compat.c'
create symbolic link `dvb_compat.h' to
`../linux/drivers/media/dvb/dvb-core/dvb_compat.h'
create symbolic link `dvb_demux.c' to
`../linux/drivers/media/dvb/dvb-core/dvb_demux.c'
create symbolic link `dvb_demux.h' to
`../linux/drivers/media/dvb/dvb-core/dvb_demux.h'
create
[linux-dvb] Re: Hauppauge DEC2000-t
Alex,
The build looks like it ended badly, but for a different reason since
updating from the latest in CVS. The dec2000t.bin file is still where
it should be, in /etc/dvb, but it still seems to be complaining about
the lack of a firmware files. I don't associate av7110 with the
DEC2000, is this perhaps a different problem in the latest CVS tree?
Tim.
..
gcc -I/root/dvb-kernel/build-2.4/include -D__KERNEL__
-I/usr/src/linux-2.4.21-0.13mdk/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe
-mpreferred-stack-boundary=2 -march=i586 -DMODULE -DMODVERSIONS
-include /usr/src/linux-2.4.21-0.13mdk/include/linux/modversions.h -MD
-I ../linux/include -I . -DCONFIG_DVB_AV7110_OSD -nostdinc -iwithprefix
include -DKBUILD_BASENAME=ttpci_eeprom -DEXPORT_SYMTAB -c
ttpci-eeprom.c
( \
echo 'Warning: no firmware file for the av7110 driver found.' \
echo ' the driver will *not* be build.' \
echo ' Have a look at README for details!' \
) dvb-ttpci-info.txt;
make[2]: Leaving directory `/root/dvb-kernel/build-2.4'
make[1]: Leaving directory `/usr/src/linux-2.4.21-0.13mdk'
[EMAIL PROTECTED] build-2.4]# ls
On 2 Jan 2004, at 14:38, Alex Woods wrote:
I have just followed these instructions and there is a build error
(see attached shell log below). I have spaced out the individual
commands to make it more readable, so you can see the DEC2000
firmware being extracted and placed in the right directory prior to
building dvb-kernel.
Do you know what is wrong to cause the fdump error?
gcc -I/root/dvb-kernel/build-2.4/include -o fdump fdump.c
usage: ./fdump ucode.bin array_name output_name
make[2]: *** [dsp_dec2000t.h] Error 255
make[2]: Leaving directory `/root/dvb-kernel/build-2.4'
make[1]: *** [_mod_/root/dvb-kernel/build-2.4] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.21-0.13mdk'
make: *** [build] Error 2
[EMAIL PROTECTED] build-2.4]#
Yes, there have been some changes to the fdump utility recently and it
looks
like the Makefile hadn't been updated for the DEC2000. If you update
your
dvb-kernel checkout ('cvs -q up' from inside dvb-kernel), you should
get a
fixed Makefile.
Cheers,
Alex
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as
subject.
[linux-dvb] Hauppauge DEC2000-t
Hi, Now I've got the SkyStar2 card recognised by the dvb-kernel drivers and also the Hauppauge DEC2000-t (USB device) seems to be registered as shown by dmesg, I only get one device showing in /dev/dvb. Shouldn't there be two, since both the SkyStar2 PCI and Hauppauge USB devices have been detected? I'd love to be able to record from more than one source at a time. Also, at present I have to install the drivers each time the host is booted. Is there a way to have them loaded automatically? I have tried doing make install but the drivers still don't load when the host boots. One other question: does the driver support simultaneously recording two channels which are on the same satellite transponder with one SkyStar2 card? Or would I need to have a second one? Regards, Tim. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Linux DVB driver install howto
Hi, I'm a one-time Unix geek who last built a kernel under Sunos 4.1.3 10 years ago and coming from MacOS X I need a helping hand. The linuxtv-dvb-1.0.1 driver readme says that you must have the source for the kernel, I am running Mandrake 9.1, where can I get this? Is there an installation procedure for dummies or do you have to be a Linux expert to get DVB working? Is there and easy install procedure or does the driver need to be statically linked into the kernel. I've never built a Linux kernel you see, even for installing drivers for my other peripherals. Any direction as to how to get this driver installed, or where to go to find out how to, would be gratefully received. BTW the card I have is a SkyStar 2, and the PC is a 500MHz PIII, will the PC be up to the job? Regards, Tim. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: Linux DVB driver install howto
Hi, In addition to my previous post I should add that simply following the instructions in the INSTALL file gave these results: [EMAIL PROTECTED] linuxtv-dvb-1.0.1]# make cat: CVS/Root: No such file or directory (cd driver; make) make[1]: Entering directory `/root/linuxtv-dvb-1.0.1/driver' Makefile:102: /lib/modules/2.4.21-0.13mdk/build/Rules.make: No such file or directory make[1]: *** No rule to make target `/lib/modules/2.4.21-0.13mdk/build/Rules.make'. Stop. make[1]: Leaving directory `/root/linuxtv-dvb-1.0.1/driver' make: *** [dvb] Error 2 [EMAIL PROTECTED] linuxtv-dvb-1.0.1]# Regards, Tim. Hi, I'm a one-time Unix geek who last built a kernel under Sunos 4.1.3 10 years ago and coming from MacOS X I need a helping hand. The linuxtv-dvb-1.0.1 driver readme says that you must have the source for the kernel, I am running Mandrake 9.1, where can I get this? Is there an installation procedure for dummies or do you have to be a Linux expert to get DVB working? Is there and easy install procedure or does the driver need to be statically linked into the kernel. I've never built a Linux kernel you see, even for installing drivers for my other peripherals. Any direction as to how to get this driver installed, or where to go to find out how to, would be gratefully received. BTW the card I have is a SkyStar 2, and the PC is a 500MHz PIII, will the PC be up to the job? Regards, Tim. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: Linux DVB driver install howto
Paul and Guido, Thanks for you help, I found the kernel sources on the magazine DVD that Mandrake 9.1 was installed from (saves a 35MB V.90 download...). I got the drivers built ok but when I try to install it with make insmod I get an error. Looking at the output of dmesg it seems that it has detected the SkyStar 2 card fine but then bombs for some reason. It looks like it is very nearly working, any hints as to how to complete it would be gladly received. Tim. -- make insmod output: [EMAIL PROTECTED] driver]# make insmod /lib/modules/2.4.21-0.13mdk/build/scripts/pathdown.sh: line 4: TOPDIR: parameter null or not set DIR=`pwd`; (cd /lib/modules/2.4.21-0.13mdk/build; make SUBDIRS=$DIR modules) make[1]: Entering directory `/usr/src/linux-2.4.21-0.13mdk' make -C /root/linuxtv-dvb-1.0.1/driver CFLAGS=-D__KERNEL__ -I/usr/src/linux-2.4.21-0.13mdk/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i586 -DMODULE -DMODVERSIONS -include /usr/src/linux-2.4.21-0.13mdk/include/linux/modversions.h MAKING_MODULES=1 modules make[2]: Entering directory `/root/linuxtv-dvb-1.0.1/driver' ld -m elf_i386 -r -o dvb-core.o dmxdev.o dvb_demux.o dvb_net.o dvb_i2c.o dvb_filter.o dvb_frontend.o dvbdev.o compat.o dvb_ksyms.o make -C av7110 modules make[3]: Entering directory `/root/linuxtv-dvb-1.0.1/driver/av7110' ld -m elf_i386 -r -o dvb-ttpci.o saa7146_core.o saa7146_v4l.o av7110.o av7110_ir.o ttpci_eeprom.o make[3]: Leaving directory `/root/linuxtv-dvb-1.0.1/driver/av7110' make -C b2c2 modules make[3]: Entering directory `/root/linuxtv-dvb-1.0.1/driver/b2c2' make[3]: Nothing to be done for `modules'. make[3]: Leaving directory `/root/linuxtv-dvb-1.0.1/driver/b2c2' make -C frontends modules make[3]: Entering directory `/root/linuxtv-dvb-1.0.1/driver/frontends' make[3]: Nothing to be done for `modules'. make[3]: Leaving directory `/root/linuxtv-dvb-1.0.1/driver/frontends' make[2]: Leaving directory `/root/linuxtv-dvb-1.0.1/driver' make[1]: Leaving directory `/usr/src/linux-2.4.21-0.13mdk' sync ( \ insmod videodev;\ \ insmod dvb-core.o dvb_shutdown_timeout=0; \ make -C frontends insmod; \ make -C av7110 insmod; make -C b2c2 insmod; \ ) Using /lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/videodev.o.gz make[1]: Entering directory `/root/linuxtv-dvb-1.0.1/driver/frontends' insmod alps_bsrv2.o; insmod alps_tdmb7.o; insmod alps_tdlb7.o; insmod grundig_29504-401.o; insmod grundig_29504-491.o; insmod stv0299.o; insmod ves1820.o; insmod tda1004x.o; insmod mt312.o; make[1]: Leaving directory `/root/linuxtv-dvb-1.0.1/driver/frontends' make[1]: Entering directory `/root/linuxtv-dvb-1.0.1/driver/av7110' insmod input; \ insmod evdev; \ insmod dvb-ttpci.o; Using /lib/modules/2.4.21-0.13mdk/kernel/drivers/input/input.o.gz Using /lib/modules/2.4.21-0.13mdk/kernel/drivers/input/evdev.o.gz dvb-ttpci.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg make[1]: *** [insmod] Error 1 make[1]: Leaving directory `/root/linuxtv-dvb-1.0.1/driver/av7110' make[1]: Entering directory `/root/linuxtv-dvb-1.0.1/driver/b2c2' insmod skystar2.o; make[1]: Leaving directory `/root/linuxtv-dvb-1.0.1/driver/b2c2' sync [EMAIL PROTECTED] driver]# -- dmesg output: Linux video capture interface: v1.00 Technisat SkyStar2 driver loading PCI: Found IRQ 5 for device 00:0b.0 skystar2.c: FlexCopII(rev.130) chip found skystar2.c: MAC address = 00:d0:d7:01:16:8f:00:00 skystar2.c: key = b2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 DVB: registering new adapter (PCI device 13d0:2103 (Techsan Electronics Co Ltd)). mt312_read: ret == -121 -- scan -c output: [EMAIL PROTECTED] scan]# ./scan -c using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' main:1768: FATAL: failed to open '/dev/dvb/adapter0/frontend0': 2 No such file or directory [EMAIL PROTECTED] scan]# ls /dev/dvb/adapter0/ demux0 dvr0net0 [EMAIL PROTECTED] scan]# On 31 Dec 2003, at 10:43, Paul Woodward wrote: Hi Tim, I'm a mandrake user as well. I believe there was insufficient room on the CD to include the kernel source. I got mine from ftp://mirror.ac.uk/pub/Mandrake_Linux The source for your kernel may be in the Mandrake-devel or Mandrake folders depending if you have upgraded the kernel. Just download the kernel-source rpm with the correct version and install it. Then (from memory) I believe you have to modify the DVB driver
