Re: [linux-dvb] uk-Sudbury dvb-t tuning data file question.
Hi, Am Dienstag 05 Februar 2008 schrieb [EMAIL PROTECTED]: Hello, Apologies if this is the wrong list to ask. Perhaps you could answer a few questions for me? Sudbury, in England, is one of the sites with two DVB-T transmitters, Sudbury and SudburyB, main transmitter Tacolneston. On my Mythtv box I have found /usr/share/doc/dvb-utils/examples/scan/dvb-t/uk-SudburyB but there is no file for Sudbury. Now according to the www.ukfree.tv site Sudbury has six muxes, SudburyB has only one for ITV. I suspect I am missing something here, why is there only one frequency file for Sudbury and why is called SudburyB? I guess it's just wrongly named; will fix that. Should there be two files, as for Dover for example, uk-Sudbury with six muxes and uk_SudburyB with one? Geographically close transmitters should be in a single file; oh well, will fix that, too ... I assume MythTv does not use these files during tuning? Regards, Steve Goodey Christoph ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Help! I cant view video. BUT I can scan!!
Hello Jonas Andren. (Kom inte o säg att Anden är dansk) The Harware I have, I have said. Its the media-card, is this: http://www.linuxtv.org/wiki/index.php/Asus_My_Cinema-P7131_Hybrid (running on a amd64, mother-board m2a-vm.. Inköpt på KjellCo byggsats för 2 veckor sedan... I also said that the same Media-card did function (somewhat) on my old computer (a PII330MHz, though with terrible video result). And it works in Windows XP. So, the Media-card function. I downloadedinstalled linuxtv-dvb-apps-1.1.1.tar.bz2 http://www.linuxtv.org/downloads/linuxtv-dvb-apps-1.1.1.tar.bz2 (and all so called utils: dvbdate dvbtrafick scan and zap worked. BUT, nothing under the test) Your tips, with mplayer dvb://[EMAIL PROTECTED], produce: !-- code begin -- MPlayer 1.0rc2-4.2.3 (C) 2000-2007 MPlayer Team CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ (Family: 15, Model: 107, Ste CPUflags: MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 1 Compiled for x86 CPU with extensions: MMX MMX2 3DNow 3DNowEx SSE SSE2 mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Playing dvb://[EMAIL PROTECTED] The username option must be = 1: 0 Struct dvbin, field username parsing error: 0 dvb_tune Freq: 50600 dvb_streaming_read, attempt N. 6 failed with errno 0 when reading 1484 bytes dvb_streaming_read, attempt N. 5 failed with errno 0 when reading 1108 bytes dvb_streaming_read, attempt N. 4 failed with errno 0 when reading 1108 bytes dvb_streaming_read, attempt N. 3 failed with errno 0 when reading 1108 bytes dvb_streaming_read, attempt N. 2 failed with errno 0 when reading 1108 bytes dvb_streaming_read, attempt N. 1 failed with errno 0 when reading 1108 bytes dvb_streaming_read, attempt N. 6 failed with errno 0 when reading 2048 bytes dvb_streaming_read, attempt N. 5 failed with errno 0 when reading 2048 bytes TS file format detected. (and here its freeze, until I terminate it) MPlayer interrupted by signal 2 in module: demux_open !--/ code end -- I turned on some debug options on kernel-module saa7134 . Eew, the line modprobe saa7134 video_debug=1 ts_debug=1 i2c_debug=1 i2c_scan=1 If I use i2c_scan=1, I get these lines as: Feb 10 15:20:37 redeb kernel: saa7133[0]: i2c xfer: 79 ERROR: NO_DEVICE Feb 10 15:20:37 redeb kernel: saa7133[0]: i2c xfer: 7b ERROR: NO_DEVICE Feb 10 15:20:37 redeb kernel: saa7133[0]: i2c xfer: 7d ERROR: NO_DEVICE Feb 10 15:20:37 redeb kernel: saa7133[0]: i2c xfer: 7f ERROR: NO_DEVICE (there where many many more... And when I zap, I get lines as: Feb 10 15:21:56 redeb kernel: saa7133[0]/ts: buffer_activate [810027793a00]7saa7133[0]/ts: - [top] buf=810027793a00 next=810027793800 Feb 10 15:21:56 redeb kernel: saa7133[0]/ts: buffer_activate [810027793800]7saa7133[0]/ts: - [bottom] buf=810027793800 next=810027793600 Feb 10 15:21:56 redeb kernel: saa7133[0]/ts: buffer_activate [810027793600]7saa7133[0]/ts: - [top] buf=810027793600 next=810027793400 Feb 10 15:21:56 redeb kernel: saa7133[0]/ts: buffer_activate [810027793400]7saa7133[0]/ts: - [bottom] buf=810027793400 next=810027793200 Jonas Anden wrote: I haven't followed this thread from the beginning, but did you say what kind of DVB hardware you have? I know the Nova-TD stick is a bit picky. Too strong a signal will cause the behavior you describe on this device. On my Nova-TD, using a good antenna will yield no data stream (but a 100% signal), whereas if I use the little mobile antenna that came with the stick, I get a stream but mpeg artefacts in the picture (due to low signal). I would try attenuating the signal (or removing amplifiers) or a different antenna. I would also give it a shot (since you're using mplayer to test) to use mplayer to control the whole scenario (tune, stream-on, demux, decode and display). Try the following command: mplayer dvb://[EMAIL PROTECTED] Using the TV6 channel will avoid any obstacles by the channel name containing extended-ascii (Ö) and space ... TV6 should be an unencrypted channel and on the same MUX as TV4, even in the Öresund region ;) // J On Sat, 2008-02-09 at 01:28 +0100, Per Blomqvist wrote: The channel isn't encrypted. (I have tested with many public chanels, that I know isnt encrypted. Cant get any video out) Im Debian-tesing user, and this is a freshly installed system. On a amd64.. (as I mentioned, in previous email) Turns out /dev/dvb/adapter0/dvr0 isnt the only device that doesnt work. (framebuffer didnt work ether, /dev/fd0 are missing totaly, regardless of bootloader vga=791 options or so). I removed (by now mistake) older kernels when I distupgraded, cant nerrow down the error search, by testing other linux-kernels. (since I only have one, the 2.6.22-3-amd64) And snapshot.debian.net didnt record any older.. Only option left, to start compilling by myslef. (but to rough)
Re: [linux-dvb] MSI [EMAIL PROTECTED] A/D v1.1 mostly working
Hartmut Hackmann wrote: Hi, Russell Russell Kliese schrieb: Hartmut Hackmann wrote: Hi, all Russell Kliese schrieb: Nico Sabbi wrote: On Thursday 07 February 2008 14:39:44 Russell Kliese wrote: Analog TV worked without a problem (even with the older drivers). There is still a problem with the digital decoder. Sometimes it works fine (I can scan for channels and can run tzap to view a channel using mplayer). However, sometimes these commands don't work. I've noticed the following when running dmesg: [ 6318.055521] tda1004x: found firmware revision 20 -- ok I suspect that the card is failing to work because the firmware sometimes isn't being uploaded for some reason. Does anybody have any ideas why or what I could do to try and fix this? Hopefully this problem can be sorted out and another card can be added to the list of supported DVB-T cards. Yay! afaik the last fw for the 10046 demodulator is version 29, that you can extract from the lifeview drivers Thanks for pointing that out. I grabbed the version 29 firmware using get_dvb_firmware tda10046lifeview and copied this into the appropriate place. However, I'm still having the same sort of problem: [ 2095.281620] tda1004x: timeout waiting for DSP ready [ 2095.321600] tda1004x: found firmware revision 0 -- invalid [ 2095.321614] tda1004x: trying to boot from eeprom [ 2097.648360] tda1004x: timeout waiting for DSP ready [ 2097.688338] tda1004x: found firmware revision 0 -- invalid [ 2097.688346] tda1004x: waiting for firmware upload... [ 2110.173699] tda1004x: found firmware revision 29 -- ok [ 2121.531804] tda1004x: setting up plls for 48MHz sampling clock [ 2121.727550] tda1004x: found firmware revision 29 -- ok [ 2513.011736] tda1004x: setting up plls for 48MHz sampling clock [ 2513.199286] tda1004x: found firmware revision 33 -- invalid [ 2513.199294] tda1004x: trying to boot from eeprom [ 2513.567098] tda1004x: found firmware revision 33 -- invalid [ 2513.567110] tda1004x: waiting for firmware upload... [ 2526.044456] tda1004x: found firmware revision 33 -- invalid [ 2526.044469] tda1004x: firmware upload failed [ 2534.743826] tda1004x: setting up plls for 48MHz sampling clock [ 2534.885955] tda1004x: found firmware revision ff -- invalid [ 2534.885968] tda1004x: trying to boot from eeprom [ 2535.211575] tda1004x: found firmware revision 0 -- invalid [ 2535.211582] tda1004x: waiting for firmware upload... [ 2535.217254] tda1004x: Error during firmware upload [ 2535.224898] tda1004x: found firmware revision ff -- invalid [ 2535.224911] tda1004x: firmware upload failed Cheers, Russell This is not only a question of the firmware revision. Many cards have an eeprom with the firmware on the board. The TDA10046 automatically tries to boot from this. The eeprom address is controlled with a GPIO pin. IF this pin changes while the chip boots, it will crash and possibly not recover. This entrie mechanism is hard to control. The card specific configuration structures tda1004x_config in saa7134-dvb.c have a entry .gpio_config. Please change this to TDA10046_GP01_I or try card type 81. The symptoms I'm having of unreliable firmware loading sounds like it could indeed be caused by GPIO pins changing during operation of the card and affecting subsequent firmware loads. I tried setting .gpio_config to DA10046_GP01_I (the default for card=109), DA10046_GP00_I and DA10046_GP11_I. None of these solved the problem. I also tried card=81, but this didn't help either. Are there any other configuration options that could be affecting the reliable upload or loading of firmware? Cheers, Russell I had a look at the photo you published. There is only one eeprom on the card? it is in a 8 pin package. Can you please check its type? I inspected the card, and could only see one 8 pin device. The part number on the device is: ATMLH722 028 1 A7F5362E This looks like your board has no firmware eeprom. So the download doesn't succeed or the dsp crashes for some reason. In the log you sent, were there further messages? There weren't any subsequent messages in the log that were any different (there were more similar messages if I kept trying to use software that made use of the card). I'm happy spend a bit of time trying some things that might get this card working. Let me know if you have any ideas. Cheers, Russell ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Freecom DVB-T USB adapter not recognised
I have a Freecom DVB-T USB adapter, listed in lsusb as: [EMAIL PROTECTED]:~$ lsusb Bus 004 Device 003: ID 14aa:0161 AVerMedia (again) or CE it does not seem to be being recognised by the kernel when I plug it in. http://www.linuxtv.org/wiki/index.php/DVB-T_USB_Devices#Freecom_rev_4_DVB-T_USB_2.0_tuner suggests that the latest revision of this device isn't yet supported, but doesn't list the above device ID (14aa:0161). It does list 14aa:0160 as unsupported, though; how can I find out whether my device is the same? Also, what needs to happen for the device to be supported? Is it just a question of finding an appropriate firmware file and dropping it in /lib/firmware, or does the driver itself in the kernel need to be hacked on to make the device work? sil -- New Year's Day -- everything is in blossom! I feel about average. -- Kobayashi Issa ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Just wanted to say that I´m experiencing the same. Using latest rev (the one with patches merged) + unknown remote key patch. Ubuntu 7.10 Also having a lot of prebuffer timeout 10 times i the middle of shows. On Feb 7, 2008 5:51 PM, Jonas Anden [EMAIL PROTECTED] wrote: Do you have a way to automate this ? Ie to detect that a tuner is gone ? No, I have yet to find any log message that says things aren't OK. Mythbackend seems to just fail its recordings and not create the recording file, which is kind of annoying. In my point of view, it would be better if mythbackend would *crash*, since this would make the other backend (which uses analog tuners) take over the recording. It wouldn't be the same quality, but at least the show would be recorded... // J ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] CX88 Nova-S Not locking
Ok, so i been doing tones of test on my Nova-S i have taking a direct cable from the LNB and fed it into my Nova-S plus, removing any multiswitches and such I have alos swapped cards with a freind with the same card. Here are the results. Both cards lock on HIS computer with kernel 22 My cards will ONLY lock on my computer with kernel 18 Any kernel 22 or above gives me a Signal of 5100 to 5A00 only. My SZAP with His Card: [EMAIL PROTECTED] szap]# ./szap -a1 -lDBS ABCD reading channels from file '/root/.szap/channels.conf' zapping to 1244 'ABCD': sat 0, frequency = 12443 MHz V, symbolrate 2000, vpid = 0x, apid = 0x using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' status 01 | signal 6500 | snr 9a4c | ber | unc fffe | status 01 | signal 5f00 | snr 9be5 | ber | unc fffe | status 01 | signal 5f00 | snr 9f21 | ber | unc fffe | \ His lock with My Card --- [EMAIL PROTECTED] szap]# ./szap -a0 -lDBS ABC reading channels from file '/root/.szap/channels.conf' zapping to 8 'ABC: sat 0, frequency = 12238 MHz H, symbolrate 2000, vpid = 0x1522, apid = 0x1523 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' status 01 | signal ea00 | snr 0549 | ber | unc fffe | status 01 | signal f900 | snr ab34 | ber | unc fffe | status 1f | signal f900 | snr d986 | ber | unc fffe | FE_HAS_LOCK status 1f | signal f900 | snr daeb | ber | unc fffe | FE_HAS_LOCK status 1f | signal f900 | snr d90a | ber | unc fffe | FE_HAS_LOCK status 1f | signal f900 | snr d9df | ber 00047f61 | unc fffe | FE_HAS_LOCK What does this indicate?!?! any ideas at all??? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Help! I cant view video. BUT I can scan!!
Hi, Am Sonntag, den 10.02.2008, 15:28 +0100 schrieb Per Blomqvist: Hello Jonas Andren. (Kom inte o säg att Anden är dansk) The Harware I have, I have said. Its the media-card, is this: http://www.linuxtv.org/wiki/index.php/Asus_My_Cinema-P7131_Hybrid (running on a amd64, mother-board m2a-vm.. Inköpt på KjellCo byggsats för 2 veckor sedan... I also said that the same Media-card did function (somewhat) on my old computer (a PII330MHz, though with terrible video result). And it works in Windows XP. So, the Media-card function. I downloadedinstalled linuxtv-dvb-apps-1.1.1.tar.bz2 http://www.linuxtv.org/downloads/linuxtv-dvb-apps-1.1.1.tar.bz2 (and all so called utils: dvbdate dvbtrafick scan and zap worked. BUT, nothing under the test) you should prefer dvb-apps from mercurial, but that is not so important. First of all I would like to see relevant dmesg stuff for the card and tuner to see if it is still likely the same card, auto detected and eeprom content unchanged and all chips alive. If you enable i2c_scan=1 you look first for the devices found. Also we never saw, if your firmware upload is successful and if you use preferably revision 29 with such a card with Low Noise Amplifier. If not, download it from LifeView with the script in /Documentation/dvb and do a cold boot. (recent stuff is in a v4l-dvb mercurial snapshot) Antenna input for DVB-T is FM/RF input. Can you point to the initial tuning file you are using or to what you believe is a valid channels.conf file for you? It is always worth a try to set all to AUTO in the initial tuning file, except frequency to tune and bandwidth and then use scan to create a channels.conf. If still not, we install the recent v4l-dvb, remove all old modules and might try to debug from there. Cheers, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Freecom DVB-T USB adapter not recognised
Stuart Langridge. Try searching the archives for: RTL2831U kernel driver We have been trying to compile a new driver. No one has got it to work yet. _ Telly addicts unite! http://www.searchgamesbox.com/tvtown.shtml ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Error in scan.c - tune to transponder?
Running SuSe 10.1, kernel 2.6.24-default, dvbtools 1.1.1, Kaffeine 0.8.6
I have 8 DVB-S lnbs on 2 diseqc switches running into 2 PCI cards,
Skystar 2 and Geniatech 103G, both of which are supported in the kernel.
The dishes, lnbs and cards are fine, work well in Windows and with
standalone receivers Coolsat 6000 and Mercury II.
Kaffeine can scan and display channels from 6 of the 8 lnbs using the
diseqc switches. I am trying to find out why the other two dishes are
not tuned. So I started scan which returns the following on all adapter
/ diseqc combinations:
__tune_to_transponder:1483 ERROR Setting frontend parameters failed: 22
Invalid argument.
The relevant section of scan.c is
if (ioctl(frontend_fd, FE_SET_FRONTEND, p) == -1) {
errorn(Setting frontend parameters failed);
return -1;
}
Any suggestions?
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Freecom DVB-T USB adapter not recognised
On Sun, 2008-02-10 at 15:22 +, Stuart Langridge wrote: I have a Freecom DVB-T USB adapter, listed in lsusb as: [EMAIL PROTECTED]:~$ lsusb Bus 004 Device 003: ID 14aa:0161 AVerMedia (again) or CE it does not seem to be being recognised by the kernel when I plug it in. http://www.linuxtv.org/wiki/index.php/DVB-T_USB_Devices#Freecom_rev_4_DVB-T_USB_2.0_tuner suggests that the latest revision of this device isn't yet supported, but doesn't list the above device ID (14aa:0161). It does list 14aa:0160 as unsupported, though; how can I find out whether my device is the same? Also, what needs to happen for the device to be supported? Is it just a question of finding an appropriate firmware file and dropping it in /lib/firmware, or does the driver itself in the kernel need to be hacked on to make the device work? Help the guy ! Help the guy ! Who knows what could be said about this place on LugRadio otherwise! ;o) Nico wishes he could help more than by saying stupid things... ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Twinhan VisionPlus 2021 DVB-C tuning problems and a solution
Hi,
After some trial and error I managed to get tuning on a VP2021 DVB-C
card working. The card is detected correctly but running scan or czap
wouldn't tune to any channel.
The solution is just to ignore the checksum failure in dst_get_tuna. I
don't know exactly why it helps, though. Below you'll find all the
relevant information (I hope).
The patch is against changeset 7182:3a880d2669a6 from the 'tip' tag (or
branch?).
# the fix
diff -r 3a880d2669a6 linux/drivers/media/dvb/bt8xx/dst.c
--- a/linux/drivers/media/dvb/bt8xx/dst.c Sat Feb 09 09:59:00 2008 -0200
+++ b/linux/drivers/media/dvb/bt8xx/dst.c Mon Feb 11 02:16:48 2008 +0200
@@ -1364,7 +1364,6 @@ static int dst_get_tuna(struct dst_state
} else {
if (state-rx_tuna[9] != dst_check_sum(state-rx_tuna[2], 7)) {
dprintk(verbose, DST_INFO, 1, checksum failure? );
- return -EIO;
}
}
if (state-rx_tuna[2] == 0 state-rx_tuna[3] == 0)
# module parameters:
options bttv debug=10 i2c_hw=10 i2c_debug=10
options dst verbose=10
# dmesg from loading modules:
[ 2842.489922] Linux video capture interface: v2.00
[ 2842.498384] bttv: driver version 0.9.17 loaded
[ 2842.498391] bttv: using 8 buffers with 2080k (520 pages) each for capture
[ 2842.498934] bttv: Bt8xx card found (0).
[ 2842.498953] bttv0: Bt878 (rev 17) at :02:03.0, irq: 17, latency: 32,
mmio: 0xdeafe000
[ 2842.499333] bttv0: detected: Twinhan VisionPlus DVB [card=113], PCI
subsystem ID is 1822:0001
[ 2842.499342] bttv0: using: Twinhan DST + clones [card=113,autodetected]
[ 2842.499361] bttv0: gpio: en=, out= in=00f75bff [init]
[ 2842.45] bttv0: tuner absent
[ 2842.500115] bttv0: add subdevice dvb0
[ 2842.523182] bt878: AUDIO driver version 0.0.0 loaded
[ 2842.523415] bt878: Bt878 AUDIO function found (0).
[ 2842.523440] ACPI: PCI Interrupt :02:03.1[A] - GSI 19 (level, low) -
IRQ 17
[ 2842.523447] bt878_probe: card id=[0x11822],[ Twinhan VisionPlus DVB ] has
DVB functions.
[ 2842.523456] bt878(0): Bt878 (rev 17) at 02:03.1, irq: 17, latency: 32,
memory: 0xdeaff000
[ 2842.538284] DVB: registering new adapter (bttv0)
[ 2842.640229] dst(0) dst_comm_init: Initializing DST.
[ 2842.640239] dst(0) dst_gpio_outb: mask=[], enbb=[0001],
outhigh=[]
[ 2842.642229] dst(0) rdc_reset_state: Resetting state machine
[ 2842.642232] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[]
[ 2842.656869] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002]
[ 2842.771975] writing [ 00 06 00 00 00 00 00 fa ]
[ 2842.771991] bt-i2c: W aa 00 06 00 00 00 00 00 fa
[ 2842.773209] dst(0) dst_gpio_outb: mask=[], enbb=[],
outhigh=[]
[ 2842.774208] bt-i2c: R ab =ff
[ 2842.774512] dst(0) read_dst: reply is 0xff
[ 2842.774517] dst(0) dst_wait_dst_ready: dst wait ready after 0
[ 2842.774519] bt-i2c: R ab =00 =44 =43 =54 =2d =43 =49 =6c
[ 2842.775870] dst(0) read_dst: reply is 0x0
[ 2842.775872] 0x44 0x43 0x54 0x2d 0x43 0x49 0x6c
[ 2842.775879] dst(0) dst_gpio_outb: mask=[], enbb=[],
outhigh=[]
[ 2842.776876] dst(0) dst_get_device_id: Recognise [DCT-CI]
[ 2842.776880] dst(0) dst_type_print: DST type: cable
[ 2842.776881] DST type flags : 0x1000 VLF 0x8 firmware version = 1 0x10
firmware version = 2
[ 2842.776887] dst(0) dst_comm_init: Initializing DST.
[ 2842.776890] dst(0) dst_gpio_outb: mask=[], enbb=[0001],
outhigh=[]
[ 2842.778877] dst(0) rdc_reset_state: Resetting state machine
[ 2842.778880] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[]
[ 2842.791940] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002]
[ 2842.895771] writing [ 00 0a 00 00 00 00 00 f6 ]
[ 2842.895780] bt-i2c: W aa 00 0a 00 00 00 00 00 f6
[ 2842.896975] dst(0) dst_gpio_outb: mask=[], enbb=[],
outhigh=[]
[ 2842.901937] bt-i2c: R ab =ff
[ 2842.902238] dst(0) read_dst: reply is 0xff
[ 2846.102574] dst(0) dst_wait_dst_ready: dst wait NOT ready after 200
[ 2846.102584] dst(0) dst_get_mac: Unsupported Command
[ 2846.102587] dst(0) dst_probe: MAC: Unsupported command
[ 2846.102591] dst(0) dst_get_tuner_info: DST TYpe = MULTI FE
[ 2846.103319] dst(0) dst_comm_init: Initializing DST.
[ 2846.103325] dst(0) dst_gpio_outb: mask=[], enbb=[0001],
outhigh=[]
[ 2846.105636] dst(0) rdc_reset_state: Resetting state machine
[ 2846.105641] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[]
[ 2846.122530] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002]
[ 2846.226358] writing [ 00 13 00 00 00 00 00 ed ]
[ 2846.226557] bt-i2c: W aa 00 13 00 00 00 00 00 ed
[ 2846.227749] dst(0) dst_gpio_outb: mask=[], enbb=[],
outhigh=[]
[ 2846.232957] bt-i2c: R ab =ff
[ 2846.233193] dst(0) read_dst: reply is 0xff
[ 2849.429159] dst(0) dst_wait_dst_ready: dst wait NOT ready after 200
[ 2849.429168] dst(0) dst_get_tuner_info: Cmd=[0x13], Unsupported
[
Re: [linux-dvb] Help! I cant view video. BUT I can scan!!
Thanx! Now it works!! Watching some Danish (Dansk) channel, about Napoleon. Thanx again, for mocking me up.. It was the channel.conf, that was wrong The channel.conf -file that I used before, was 6 month old and from my previous computer. (Now dvbscan doesn't detect anything on that bandwidth. And that TV6 was on that.. If I run dvdscan against the closest mayor city (Malmö in my case, here in south Sweden), it only tunedin encrypted channels. BUT, against all of Denmark (file dk-All) I get a some.. Its strange though.. I CAN SEE TV6 unencrypted, but in Windows XP. But there with A program called PowerCinema is used (in XP OS). (tuning is a fuzz there also, I believe PowerCinema download channels and guides and what, from the internet. It would maybe be a point to retrieve its (channel) configure file. I have looked, but found none. Another question now, how is all these initial-tuning-data created?? redeb:~/.tzap# cat dk-All # Denmark, whole country # Created from http://www.digi-tv.dk/Indhold_og_tilbud/frekvenser.asp # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 48200 8MHz 2/3 NONE QAM64 8k 1/4 NONE T 50600 8MHz 2/3 NONE QAM64 8k 1/4 NONE T 53800 8MHz 2/3 NONE QAM64 8k 1/4 NONE T 55400 8MHz 2/3 NONE QAM64 8k 1/4 NONE T 60200 8MHz 2/3 NONE QAM64 8k 1/4 NONE T 65800 8MHz 2/3 NONE QAM64 8k 1/4 NONE T 68200 8MHz 2/3 NONE QAM64 8k 1/4 NONE T 69000 8MHz 2/3 NONE QAM64 8k 1/4 NONE T 71400 8MHz 2/3 NONE QAM64 8k 1/4 NONE T 73800 8MHz 2/3 NONE QAM64 8k 1/4 NONE T 77800 8MHz 2/3 NONE QAM64 8k 1/4 NONE T 82600 8MHz 2/3 NONE QAM64 8k 1/4 NONE T 83400 8MHz 2/3 NONE QAM64 8k 1/4 NONE redeb:~/.tzap# cat se-Malmo # Sweden - Malmö # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 48200 8MHz 3/4 NONE QAM64 8k 1/4 NONE T 50600 8MHz 3/4 NONE QAM64 8k 1/4 NONE T 61800 8MHz 2/3 NONE QAM64 8k 1/8 NONE T 81800 8MHz 3/4 NONE QAM64 8k 1/4 NONE T 85000 8MHz 3/4 NONE QAM64 8k 1/4 NONE Can I compose one, of these by myself (from other nearby citys), or how? hermann pitton wrote: Hi, Am Sonntag, den 10.02.2008, 15:28 +0100 schrieb Per Blomqvist: Hello Jonas Andren. (Kom inte o säg att Anden är dansk) The Harware I have, I have said. Its the media-card, is this: http://www.linuxtv.org/wiki/index.php/Asus_My_Cinema-P7131_Hybrid (running on a amd64, mother-board m2a-vm.. Inköpt på KjellCo byggsats för 2 veckor sedan... I also said that the same Media-card did function (somewhat) on my old computer (a PII330MHz, though with terrible video result). And it works in Windows XP. So, the Media-card function. I downloadedinstalled linuxtv-dvb-apps-1.1.1.tar.bz2 http://www.linuxtv.org/downloads/linuxtv-dvb-apps-1.1.1.tar.bz2 (and all so called utils: dvbdate dvbtrafick scan and zap worked. BUT, nothing under the test) you should prefer dvb-apps from mercurial, but that is not so important. There is a deb-package called mercurial. (I suspect it doesnt have anything, todo with this, no?) First of all I would like to see relevant dmesg stuff for the card and tuner to see if it is still likely the same card, auto detected and eeprom content unchanged and all chips alive. If you enable i2c_scan=1 you look first for the devices found. I used the linux-kernels-source. in its documents for this. Downloaded the firmware.. (I include dmesg output in the end of this email, anyway. The revision is 20, and not a LifeView fabrication.. Also we never saw, if your firmware upload is successful and if you use preferably revision 29 with such a card with Low Noise Amplifier. If not, download it from LifeView with the script in /Documentation/dvb and do a cold boot. (recent stuff is in a v4l-dvb mercurial snapshot) Antenna input for DVB-T is FM/RF input. Can you point to the initial tuning file you are using or to what you believe is a valid channels.conf file for you? It is always worth a try to set all to AUTO in the initial tuning file, except frequency to tune and bandwidth and then use scan to create a channels.conf. Yes, now my system is relatively fresh, again (I dont load any kernel-module with any extra options). If still not, we install the recent v4l-dvb, remove all old modules and might try to debug from there. Cheers, Hermann I also tried to compile the kernel (there was this option there VIDEO_ADV_DEBUG). But unfortunately I cut away so other stuff, soo the new kernel got panic at bootup. Another story.. It was the channel.conf that was wrong.. Thx again! (what a fuzz) dmesg_1.txt.gz Description: application/gzip ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
