Re: [linux-dvb] Please finaly include hvr4000 (was hvr4000-news)
Thank to the tremendous work of Steven Stoth and Darron Broad and certainly lots of other, HVR-4000 is now perfectly supported with only the need of a small patch to be found under http://dev.kewl.org/hvr4000/v4l-dvb-hg-2007-12-06-FIX.diff The same is true for the DVB-S-only version of this card, called Hauppauge NOVA-S2-HD PCI or HVR-4000lite . I've used this card for several days now - without any issues or instabilities so far. Very nice work, many thanks to all people involved. Regards, Holger ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Pinnacle PCTV Sat HDTV Pro USB (452e) packet loss
Although this device is not yet officially supported, I've been trying to get it working following success reported by others in an earlier thread. I've followed the instructions in the DVB wiki entry for this device, and have succeeded in tuning the device using the patched version of szap, and recording a transport stream (using cat /dev/dvb/adapter0/dvr0 recording.ts). However, the transport stream shows up discontinuity errors which manifest as glitches in the playback. From the stats produced by TS Reader the rate of loss is typically around 1 packet in 700, though it varies from run to run. I realise the simplest explanation for this would be a poor quality signal. However, the device performs flawlessly under Windows XP in exactly the same hardware configuration (same computer, dish, and sat feed) when tuned to the same channels. This seems to rule out signal quality as a cause unless the linux driver does not configure the device's error correction properly. Is there any possibility this could be the case ? I've also tried running the linux configuration on two different computers - an AMD X2 4600 with Asus M2NPV-VM mobo, and a Via EPIA5000 system (with a PCI 5-port USB2.0 card). The same problem occurs on both systems. I'm using kernel version 2.6.18-2. I also have two DVB-T USB adapters which work with the same software configuration with no packet loss. The channels I've tried are BBC 1 London and BBC HD. Obviously, the data rate is much higher on the HD channel. I've cross-checked with the XP configuration to make sure that the frequencies, polarity, etc. are correct in the channels.conf file. Note that during the BBC HD trial from Crystal Palace I was able to record this channel from a DVB-T adapter without packet loss even on the EPIA5000 (533 MHz Via Eden processor). I'm unable to determine at what point in the processing chain the packets are being lost. I temporarily inserted some checks for continuity errors on a specific pid in the 'dvb_dmxdev_ts_callback' function in dmxdev.c. This showed packets had already gone missing at this point in the driver. I don't know my way around the code well enough to be able to pursue it further. In particular, I can't tell whether the packets are being discarded somewhere in the driver, or within the device itself. The only kind of errors which I detect are continuity errors. Does the device filter out all packets in error or does it pass them through to the driver with the appropriate error flags set in the packet header ? Has anybody succeeded in getting an error free transport stream from this device ? If not, are there any ideas about where the problem might be ? Thanks, John ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] How to Scan C-BAND Signal
Hi all, I am using WinTv-Nexus-S card, with ku-band feed connected to it. I am using linux-dvb-apps scan utility to scan the channels. With ku-band signal i used the following command to scan the channels. #scan Hotbird-13.0E This is working fine without any issues. Now i started using C-Band signal. when i try the same command, it says tunning failed. I tested the signal in the feed by connecting it to a TV. It shows the following channels. Gyandarshan, Eklavya, UGC-CEC etc... So Please help me to fix this problem. Thanks for ur help in advance. Regards, Thiru. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle PCTV Sat HDTV Pro USB (452e) packet loss
i also noticed glitches on some channels, but not all. Using szap2 (or the patched version of VDR 1.5) on Astra 19.2E Das Erste:11836:hC34M2S0Z0:S19.2E:27500:101:102=deu,103=2ch;106=dd:104:0:28106:1:1101:0 works perfect and didn't show a single error in several hours of recording, while ORF2E:12692:hC56M2S0Z0:S19.2E:22000:170:171=deu:505:0:13014:1:1117:0 rarely gives any complete picture at all - usually vdr-softdevice crashes after some seconds... this pointed me to a possible dependency on the symbol rate, but i didn't investigate it further. as I'm currently waiting for a new LNC to be delivered, i cannot run any meaningful test at this moment (but hopefully next week). regards Daniel On Thu, 2007-12-13 at 13:20 +0100, [EMAIL PROTECTED] wrote: Although this device is not yet officially supported, I've been trying to get it working following success reported by others in an earlier thread. I've followed the instructions in the DVB wiki entry for this device, and have succeeded in tuning the device using the patched version of szap, and recording a transport stream (using cat /dev/dvb/adapter0/dvr0 recording.ts). However, the transport stream shows up discontinuity errors which manifest as glitches in the playback. From the stats produced by TS Reader the rate of loss is typically around 1 packet in 700, though it varies from run to run. I realise the simplest explanation for this would be a poor quality signal. However, the device performs flawlessly under Windows XP in exactly the same hardware configuration (same computer, dish, and sat feed) when tuned to the same channels. This seems to rule out signal quality as a cause unless the linux driver does not configure the device's error correction properly. Is there any possibility this could be the case ? I've also tried running the linux configuration on two different computers - an AMD X2 4600 with Asus M2NPV-VM mobo, and a Via EPIA5000 system (with a PCI 5-port USB2.0 card). The same problem occurs on both systems. I'm using kernel version 2.6.18-2. I also have two DVB-T USB adapters which work with the same software configuration with no packet loss. The channels I've tried are BBC 1 London and BBC HD. Obviously, the data rate is much higher on the HD channel. I've cross-checked with the XP configuration to make sure that the frequencies, polarity, etc. are correct in the channels.conf file. Note that during the BBC HD trial from Crystal Palace I was able to record this channel from a DVB-T adapter without packet loss even on the EPIA5000 (533 MHz Via Eden processor). I'm unable to determine at what point in the processing chain the packets are being lost. I temporarily inserted some checks for continuity errors on a specific pid in the 'dvb_dmxdev_ts_callback' function in dmxdev.c. This showed packets had already gone missing at this point in the driver. I don't know my way around the code well enough to be able to pursue it further. In particular, I can't tell whether the packets are being discarded somewhere in the driver, or within the device itself. The only kind of errors which I detect are continuity errors. Does the device filter out all packets in error or does it pass them through to the driver with the appropriate error flags set in the packet header ? Has anybody succeeded in getting an error free transport stream from this device ? If not, are there any ideas about where the problem might be ? Thanks, John ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] m920x device: Genius TVGo DVB-T02Q
hi,
Looks like it is almost working :)
Román wrote:
.stream = {
.type = USB_ISOC,
.count = 6,
.endpoint = 0x81,
.u = {
.isoc = {
.framesperurb = 1,
.framesize = 564,
.interval = 150,
}
}
},
Be aware that lsusb -v (without ehci_usb) lists 1023 as the maximum
packet size, as opposed to 564 (the value with ehci_usb loaded), but
changing that parameter didn't make any difference. Also note the
value in .interval: I only got some success with values between 100
and 200, approximately. I'm not an expert but they seem very strange
values to me. Didn't have any success at all with ehci_usb loaded.
There is not many drivers using isoc currently, only au6610 and ttusb2.
When I did au6610 it was was also hard to guess those values. I don't
know whats the correct way to find values, but here is method I used
(au6610.c):
.framesperurb = 40,
from usbsnoop.log
NumberOfPackets = 0028
.framesize = 942,
from lsusb
wMaxPacketSize 0x03ae 1x 942 bytes
or from usbsnoop.log
IsoPacket[1].Offset = 942
.interval = 1.25, /* 125 us */
Interface[0]: Pipes[1] : Interval = 0x0001
Interface[0]: Pipes[1] : PipeType = 0x0001
(UsbdPipeTypeIsochronous)
I don't remember where I found 125 us, maybe looking times from
usbsnoop.log. Anyhow, looks like it is wrong but still works just fine
because 1.25 is rounded to 1 due to integer.
I hope this helps :)
regards
Antti
--
http://palosaari.fi/
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Additional tuning status values req'd for tda10048
The TDA10048 (channel decoder) has some status registers that are helpful for fast scanning and accurate tuning. AUTO_OFFSET/OFFSET_F and FREQERR_R/TIMERR_R - for offset detection and tuning sampling clock correction How would features such as these fit into the existing frontend API ? I could imagine a FE_CAN_OFFSET_AUTO, FE_CAN_FREQ_CORRECT and FE_CAN_SAMP_CLOCK_CORRECT, in fe_caps, and an FE_HAS_OFFSET in fe_status, but can't see how you could read or set any of the other values without extending ioctls. Regards, MikeW ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Additional tuning status values req'd for tda10048
MikeW mw_phil at x.xx.xx writes: The TDA10048 (channel decoder) has some status registers that are helpful for fast scanning and accurate tuning. AUTO_OFFSET/OFFSET_F and FREQERR_R/TIMERR_R - for offset detection and tuning sampling clock correction How would features such as these fit into the existing frontend API ? I could imagine a FE_CAN_OFFSET_AUTO, FE_CAN_FREQ_CORRECT and FE_CAN_SAMP_CLOCK_CORRECT, in fe_caps, and an FE_HAS_OFFSET in fe_status, but can't see how you could read or set any of the other values without extending ioctls. Regards, MikeW I guess they could be additional dvb_frontend_parameters: __u32 channel_offset, freq_offset, samp_clk_error; MikeW gmane_padding ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem with Hauppauge Nova-TD
Nicolas Will wrote: On Wed, 2007-12-12 at 22:49 +0100, Luca wrote: I have this DVB-T USB device: http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-TD-Stick It seem supported by difference sources: http://cateee.net/lkddb/web-lkddb/DVB_USB_DIB0700.html (PCI ID 2040:9580). I tried to find the correct firmware, I loaded/unloaded drivers for all the day (dib0700 is the correct one, right?), but nothing happens: dmesg reports: ... Dec 12 22:02:25 sirius kernel: dib0700: loaded with support for 2 different device-types Dec 12 22:02:25 sirius kernel: usbcore: registered new interface driver dvb_usb_dib0700 ... The firmware name is dvb-usb-dib0700-01.fw and it's located to /lib/firmware/`uname -r`/... I'm not sure I have the correct firmware (I tried to get it from Windows driver installation and from web, but I didn't found anything intersting). I would strongly suggest that you follow the instructions there: http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#Making_it_work Make sure you follow the instructions in the note (get the 1.10 firmware). And then compile a v4l-dvb tree. Tell us what it does for you, but I think it should mostly sort you out. If it does, the -TD stick wiki page would need content. http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-TD-Stick Nico Thank you for response... My dmesg is happy: ... dib0700: loaded with support for 5 different device-types dvb-usb: found a 'Hauppauge Nova-TD Stick/Elgato Eye-TV Diversity' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Hauppauge Nova-TD Stick/Elgato Eye-TV Diversity) DVB: registering frontend 0 (DiBcom 7000PC)... MT2266: successfully identified dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Hauppauge Nova-TD Stick/Elgato Eye-TV Diversity) DVB: registering frontend 1 (DiBcom 7000PC)... MT2266: successfully identified input: IR-receiver inside an USB DVB receiver as /class/input/input11 dvb-usb: schedule remote query interval to 150 msecs. dvb-usb: Hauppauge Nova-TD Stick/Elgato Eye-TV Diversity successfully initialized and connected. usbcore: registered new interface driver dvb_usb_dib0700 I have 2 adapters now in /dev/dvb. But (there's always a but!)... I tried to find out my channels.conf: At first, I've used the it-Varese, because I live there, but scan give me the following output: scan /usr/share/doc/dvb-utils/examples/scan/dvb-t/it-Varese scanning /usr/share/doc/dvb-utils/examples/scan/dvb-t/it-Varese using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 22650 1 2 1 3 1 0 0 initial transponder 70600 0 2 1 3 1 0 0 initial transponder 60200 0 2 1 3 1 0 0 initial transponder 51400 0 2 1 3 1 0 0 initial transponder 61000 0 2 1 3 1 0 0 tune to: 22650:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 tune to: 70600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 tune to: 60200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 60200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 51400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 51400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 61000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 61000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! dumping lists (0 services) Done. Since no channel was found, I've used w_scan binary, maybe my zone is not served as specified in it-Varese: ./w_scan w_scan version 20071209 Info: using DVB adapter auto detection. Found DVB-T frontend. Using adapter /dev/dvb/adapter0/frontend0 -_-_-_-_ Getting frontend capabilities-_-_-_-_ frontend DiBcom 7000PC supports INVERSION_AUTO QAM_AUTO TRANSMISSION_MODE_AUTO GUARD_INTERVAL_AUTO HIERARCHY_AUTO FEC_AUTO -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ ... 226500: 474000: signal ok (I999B8C999D999M999T999G999Y999) 482000: ... 618000: 626000: signal ok
Re: [linux-dvb] Problem with Hauppauge Nova-TD
On Thu, 2007-12-13 at 20:23 +0100, Luca wrote: Nicolas Will wrote: On Wed, 2007-12-12 at 22:49 +0100, Luca wrote: I have this DVB-T USB device: http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-TD-Stick It seem supported by difference sources: http://cateee.net/lkddb/web-lkddb/DVB_USB_DIB0700.html (PCI ID 2040:9580). I tried to find the correct firmware, I loaded/unloaded drivers for all the day (dib0700 is the correct one, right?), but nothing happens: dmesg reports: ... Dec 12 22:02:25 sirius kernel: dib0700: loaded with support for 2 different device-types Dec 12 22:02:25 sirius kernel: usbcore: registered new interface driver dvb_usb_dib0700 ... The firmware name is dvb-usb-dib0700-01.fw and it's located to /lib/firmware/`uname -r`/... I'm not sure I have the correct firmware (I tried to get it from Windows driver installation and from web, but I didn't found anything intersting). I would strongly suggest that you follow the instructions there: http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#Making_it_work Make sure you follow the instructions in the note (get the 1.10 firmware). And then compile a v4l-dvb tree. Tell us what it does for you, but I think it should mostly sort you out. If it does, the -TD stick wiki page would need content. http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-TD-Stick Nico Thank you for response... My dmesg is happy: ... dib0700: loaded with support for 5 different device-types dvb-usb: found a 'Hauppauge Nova-TD Stick/Elgato Eye-TV Diversity' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Hauppauge Nova-TD Stick/Elgato Eye-TV Diversity) DVB: registering frontend 0 (DiBcom 7000PC)... MT2266: successfully identified dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Hauppauge Nova-TD Stick/Elgato Eye-TV Diversity) DVB: registering frontend 1 (DiBcom 7000PC)... MT2266: successfully identified input: IR-receiver inside an USB DVB receiver as /class/input/input11 dvb-usb: schedule remote query interval to 150 msecs. dvb-usb: Hauppauge Nova-TD Stick/Elgato Eye-TV Diversity successfully initialized and connected. usbcore: registered new interface driver dvb_usb_dib0700 I have 2 adapters now in /dev/dvb. Great. This is good. I'll try to do something about the wiki page soon, then. And god of you to come back on-list, it was not my intention to keep the exchange private. But (there's always a but!)... I tried to find out my channels.conf: [MAJOR SNIP] What am I doing wrong? Anyone could help me? I'm starting to think here I'm not receiving any signal... I'm crap at scan, zap, tzap, etc... as well as in using mplayer for DVB-T. My only tests of DVB-T equipment outside of MythTV were with Kaffeine, which can do a full scan out of thin air. http://www.andresmartinezsoto.net/blog/wp-content/uploads/2007/10/skaffeine.png Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] New scan config es-Euskaltel
Hello everybody, I made a new scan config for Euskaltel(1) cable company (Basque Country-Spain). Sorry for my bad english ;) and thanks to developers of LinuxTV. Regards, Pilaf. (1) http://en.wikipedia.org/wiki/Euskaltel es-Euskaltel Description: Binary data ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Datasheet zl10353
Hi, The datasheet for the zl10353 is freely available on the Intel support site. Intel now call it a CE6353, the datasheet is D55752.pdf. It seems to include everything, pin allocation etc. Can this be used to improve our zl10353 driver ? Rob ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem with Hauppauge Nova-TD
Well... the device seem working properly after I put the firmware in /lib/firmware... maybe before I was using the wrong one... mah! Now dib0700 module say me that loads the firmware at ... (really two different firmwares, 1.10 and 03-pre). I don't know if it can work with both antennas... I'm playing with them, because I think it's an antenna problems... Kaffein is awesome! But sadly I cannot find any channel... sigh... Still trying here. Thank! I will let you know... ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan VP1041 and 64-bit FC6 troubles
I can confirm that Gernot's patch http://pansy.at/gernot/twinhan-vp1041-3.diff.gz is working for me for the Twinhan VP-1041 (aka Azurewave AD-SP 400, and it looks like the Technisat SkyStar HD2 too.) Kernel 2.6.22 (ubuntu gutsy). Scan found 1198 FTA TV and radio channels on Hotbird. Finds DVB-S and DVB-S2 channels ok. Tuning with szap -i -r working fine (still have the hanging problem with szap -r but interactive mode is ok). DVB-S: Tuning between channels in 2-7 seconds. Playing fine with mplayer. Reception seems solid. DVB-S2: was able to tune and lock several DVB-S2 HD channels on Astra 19degE (though not always first time). Dumped out a few files from ASTRA HD+ (FTA) -- when played with mplayer I hear the audio but see no video. Don't know if the files are actually ok yet. Many thanks Gernot. Hans Gernot, thanks, I have tried your second patch from http://pansy.at/gernot/twinhan-vp1041-2.diff.gz and could successfully see one dvb-s channel on my Twinhan VP-1041, but when I use szap -r to view the channel it hangs in a way that I can't kill (it becomes a process in state D, i.e. uninterruptible sleep). So I can't change channels and have to reboot. I didn't try dvb-s2 yet. Here is what I did -- perhaps you can see something wrong: a)kernel 2.6.20 stock ubuntu feisty, amd-64bit b)used your patch to patch multiproto commit 0f3e5ce65e32 c)there was one file missing from your patch (cu1216_regs.h) so I copied it from the driver on twinhan's website v1.4.2 d)compiled patched multiproto and installed successfully e)obtained scan from http://jusst.de/manu/scan.tar.bz2 and slotted in the util/scan directory of hg http://linuxtv.org/hg/dvb-apps/. I fixed up the .h includes to come from the earlier multiproto compilation. f)obtained szap.c from http://abraham.manu.googlepages.com/szap.c and compiled it in util/szap according to http://www.linuxtv.org/pipermail/linux-dvb/2007-October/021474.html (messy -- is there a dvb-apps for multiproto tree somewhere?) scan seems to work fine to create a channels.conf. Then to view a channel I did: szap -r -a 0 -l UNIVERSAL -t 0 -c channels.conf channelname and then mplayer - /dev/dvb/adapter0/dvr0 szap tunes and locks and I get video and audio from mplayer but after that I cannot kill it (with ctrl-c or kill) to change to another channel. Any idea what's wrong? What's the best way to view channels? Are you merging your code into multiproto? Regards, Hans hy, i have updated my patch. now it's also based on the current mantis tree on jusst.de (much improved i2c code, so intialization tunning is much faster) http://pansy.at/gernot/twinhan-vp1041-2.diff.gz gernot On Monday 12 November 2007 13:54:27 Gernot Pansy wrote: hy, pherhaps you like to try this patch against the current multiproto branch on http://jusst.de/hg/multiproto/. http://pansy.at/gernot/twinhan-vp1041.diff.gz it's working much better for me. also it compiles with recent kernels. gernot p.s.: if you want to test it mythtv, youd could try this hack against current svn: http://pansy.at/gernot/mythtv-multiproto-hack.diff.gz On Saturday 06 October 2007 19:16:57 Simeon Simeonov wrote: Hello everyone, I have hard time getting the VP1041 (Azureware AD-SP 400) to work properly with 64-bit FC6. I used the drivers from Twinhan web site. First compiled them with the stock kernel-2.6.18-1.2798, then I tried with the latest 2.6.22 -2 FC6 kernel. The drivers compile OK. They also load just fine, the frontend is created and all of the nodes in /dev/dvb* are created just fine. The problem is when I try to use the interface - as soon as I try to open the frontend I get kernel Oops. It looks like stb0899 module is not happy about something. I've seen that some people are using the card - how did you guys get it to work? Could it be the 64-bit that is giving me problems? Thanks. Simeon -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Kaffeine multiproto patch?
Has anyone written (or started working on) a patch for Kaffeine so that its dvb functions work with multiproto? Thanks, Hans -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
