Re: Mystique SaTiX-S2 Sky V2 USB (DVBSKY S960 clone) - Linux driver.
Olli, what kernel version/v4l-dvb are you running? (I want to update the wiki) Steve, you can download Windows software from http://www.dvbsky.net/Support_win.html. It looks like the device should work with the driver+player. Bestunar doesn't sound like something to worry about. Seems to be a sub-brand of DVBsky or something. Since the device works for Olli and yours is misbehaving the same way on a different system (I understand you installed Ubuntu in VirtualBox on the Dell) it's probably time to try and run it on Windows native to verify the device itself isn't simply a DOA. Warning, Windows talk: If you're not allowed (or don't want) to install drivers/software on the host OS for the Dell laptop but you can use USB 2.0 in VirtualBox, you may be able to just install Windows in VirtualBox. You can just take Windows 7 installation media (don't enter any serial) or Windows 8.1 (with public trial key) or Windows 10 preview (public) and install that in VirtualBox. When it's expired (30 days for 7, instantly for 8.1) it'll just nag you, make the background black (actually an improvement) and maybe disables some advanced features, but all essential functions you need to troubleshoot the device will work. To get media: http://www.heidoc.net/joomla/technology-science/microsoft/70-windows-8-x-and-windows-10-iso-direct-download-links For Windows 10, just get the preview, completely legal. For Windows 8.1, use the MS media creation tool on the Dell laptop. As you don't have to download from any illegal source, don't activate and enter a trial serial this generally won't get you into trouble. (but when in doubt, ask your lawyer) For Windows 7 you may not be able to legally obtain a copy of the installation media. If you go down that route, check the hash against hashes as released by MS. If the device works on Windows, try to get the same system Olli has. (distro/kernel) If that doesn't work, it would be nice if you could provide a photograph of the inside of your device (but this could void your warranty) as perhaps it really is a new revision. If the system Olli uses works for you, we need to find the difference between the systems. Best regards, P. van Gaans. On 05/06/2015 06:43 PM, Steve wrote: Hi, thanks for your help so far... It's taken a few days - but I've now tried a variety of things without arriving at any resolution. Prior to posting, I had not downloaded any firmware. I placed the firmware from http://www.dvbsky.net/download/linux/dvbsky-firmware.tar.gz into /lib/firmware... I rebooted - the only difference I discovered is that, this time, my keyboard and mouse stopped working when the SaTiX device was plugged in. Investigating syslog (after a reboot) suggested the error messages (previously posted) remained. I downloaded and built the latest v4l-dvb sources. The upshot was that the device returned to failing as in my original post (i.e. without stopping my keyboard/mouse from working.) I tried several USB cables - no improvement. I hooked the SaTiX device up to a modern, Dell, Windows 8.1 laptop. Windows recognised the device as an S960, but was not able to (automatically) determine any drivers for it. (I have no windows software for this device.) I installed Ubuntu onto a VirtualBox instance, and configured it to use the SaTiX. At first, I thought I'd made progress as lsusb worked... however I quickly discovered an error message: dvb_usb_v2: this USB2.0 device cannot be run on a USB1.1 port (it lacks a hardware PID filter) Having installed the extension pack for VirtualBox (to support virtual USB 2.0) the SaTiX device behaved identically to on the original (Ubuntu native) PC - i.e. the same errors in dmesg and lsusb fails to work after the device has been attached. The only new information that I have are the device diagnostics from Windows - the device reports: Bestunar S960-- I was surprised not to see SaTiX here. Vendor ID : 0572 Product ID : 6831 Version : Revision : 20130511 The green light, on the front of the device, only comes on once Linux has recognised the device... Can anyone offer any other advice? Have I been sent a different Sky-S960 clone to the one I ordered? On 03/05/15 08:44, Olli Salonen wrote: Hi Steve, I've got the device in question and can confirm that it works ok. lsusb definitely should work ok - maybe there's indeed something wrong with your device. As suggested by P. van Gaans, maybe you can try your device on another computer or even on Windows and see if it works there. Cheers, -olli On 2 May 2015 at 03:32, P. van Gaans w3ird_n...@gmx.net wrote: On 05/01/2015 04:57 PM, Steve wrote: Hi, I'm trying a direct mail to you as you are associated with this page: http://linuxtv.org/wiki/index.php/DVB-S2_USB_Devices I have bought a Mystique SaTiX-S2 Sky V2 USB (DVBSKY S960 clone) - but it doesn't work
Re: Mystique SaTiX-S2 Sky V2 USB (DVBSKY S960 clone) - Linux driver.
On 05/01/2015 04:57 PM, Steve wrote: Hi, I'm trying a direct mail to you as you are associated with this page: http://linuxtv.org/wiki/index.php/DVB-S2_USB_Devices I have bought a Mystique SaTiX-S2 Sky V2 USB (DVBSKY S960 clone) - but it doesn't work with my 3.19 kernel, which I'd assumed it would from the above page. I've tried asking about the problem in various ways - first to AskUbuntu: http://askubuntu.com/questions/613406/absent-frontend0-with-usb-dvbsky-s960-s860-driver-bug ... and, more recently, on the Linux-Media mailing list. Without convincing myself that I've contacted the right person/people to give constructive feedback. By any chance can you offer me some advice about who it is best to approach? (Obviously I'd also be grateful if you can shed any light on this problem.) Steve Hi Steve, The page actually states Support in-kernel is expected in Linux kernel 3.18.. Devil's advocate, but it doesn't say it's actually there or guarantees it ever will. At the time it was written, 3.18 wasn't out yet. Looking at your dmesg output however it seems your kernel is aware of the device. (so the patch made it) As for me, I was offered a bargain for another device so I have no S960. Linux-media mailing list is the right place. (and here we are) A few quick suggestions: Did you really, really, really get the right firmware and are you absolutely positive it's in the right location and has the right filename? Does dmesg mention the firmware being loaded? Get/compile the latest v4l-dvb sources. (http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers) Maybe it's just a bug that has already been fixed. Try another program to access the device. But if even lsusb hangs, this is pretty much moot. Make sure the power supply/device is functioning properly. Try it on another OS to make sure it's not defective. Try another computer, preferably with another chipset. If your RAM is faulty or you have a funky USB-controller, you can experience strange problems. Good luck! Best regards, P. van Gaans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Advice on DVB-S/S2 card and CAM support
On 08/28/2014 04:44 PM, Kaya Saman wrote: On 08/28/2014 04:47 AM, P. van Gaans wrote: On 07/28/2014 01:44 AM, Kaya Saman wrote: Hi, I'm wondering what the best solution for getting satellite working on Linux is? Currently I have a satellite box with CAM module branded by the Satellite TV provider we are with. As I am now migrating everything including TV through my HTPC environment I would also like to link the satellite box up to the HTPC too to take advantage of the PVR and streaming capabilities. I run XBMC as my frontend so I was looking into TV Headend to take care of PVR side of things. My greatest issue though is what is the best solution for getting the satellite system into the HTPC? After some research my first idea was to use a satellite tuner card; models are available for Hauppauge and other vendors so really it was about which was going to offer best compatibility with Linux? (distro is Arch Linux with 3.15 kernel) The model of card I was looking was from DVB-Sky: http://www.dvbsky.net/Products_S950C.html something like that, which has CAM module slot and is DVB-S/S2 compatible and claims to have drivers supported by the Linuxtv project. Or alternately going for something like this: http://www.dvbsky.net/Products_T9580.html as it has a combined DVB-T tuner, then using a USB card reader for the CAM smart card. Has anyone used the cards above, what are the opinions relating to them? Also would they work with motorized dishes? Since I'm not sure if all CAM's are supported as apparently our satellite tv provider wanted to lock out other receivers so they force people to use their own product; my second idea was to perhaps use a capture card with RCA inputs. Something like this: http://www.c21video.com/viewcast/osprey-210.html perhaps or a Hauppauge HD-PVR mk I edition: which according to the wiki is supported. Looking forward to hearing advice. Thanks. Kaya -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Hi Kaya, Hi, many thanks for the response! RCA inputs is probably the last thing you want. Less quality, more of a pain to set up. Unfortunately I need the composite inputs due to a set-top box which is used to watch (non-English) sports with; and they are paid channels. The box is non-HD so only RCA (Phono) or SCART output. You may or may not be able to use that CAM - but even if it's supported, a CAM has downsides. It generally only supports one channel at a time - and surely not multiple channels from different frequencies (if you have more tuners). And it's more expensive, both the tuner (that needs a CI slot) and the CAM you need. Also, I'm not sure if tvheadend nowadays supports a CAM - it used not to, but support may have been added. The main downside of a phoenix-mode cardreader is that it's harder to set up, but if you can find a guide for your provider it's generally doable. It's cheaper, more flexible and allows for faster channel switching. I doubt the provider will have a guide as they claim to want to lock everybody into their own set-top box - the non-HD one described above. As for a tuner, I personally suggest going for a USB-tuner. You never know if you want to connect you tuner to a notebook or NAS or anything in the future, with USB you're more flexible. If you do go for PCI-e, Tevii appears to have some supported products that are also available. If you go for USB, support is somewhat problematic (problematic because many supported tuners are no longer available in stores), you'll have to see what's locally available. (perhaps also check second-hand) Be careful, some devices have various revisions. Always check http://linuxtv.org/wiki/index.php/Hardware_Device_Information I did go this route eventually (since writing my initial post) :-) currently - though this was supposed to be my last resort route. I grabbed a Hauppauge WinTV PVR-1900 EU version. According to these guides: http://www.linuxtv.org/wiki/index.php/Pvrusb2 http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-1950 http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-1900 It is supported. I will need to write a separate posting for it though as I'm a little stuck with it. The BER is quite high and also I can't switch to the 'composite' input most of the time though on rare occasion it does work? The PCI/ or PCI-E card is still an option for me as it will go into a rather large HTPC case which I can also use as a server for distributed TV around the network. Very recently, Antti reviewed a patch from nibble.max to support the DVBsky S960. (and presumably it's direct clones from Mystique) This is a pretty cheap tuner that can still be found in shops. It would appear that as soon as this patch gets merged, this device will be supported if you compile v4l-dvb yourself, and in time support will make
Re: Advice on DVB-S/S2 card and CAM support
On 07/28/2014 01:44 AM, Kaya Saman wrote: Hi, I'm wondering what the best solution for getting satellite working on Linux is? Currently I have a satellite box with CAM module branded by the Satellite TV provider we are with. As I am now migrating everything including TV through my HTPC environment I would also like to link the satellite box up to the HTPC too to take advantage of the PVR and streaming capabilities. I run XBMC as my frontend so I was looking into TV Headend to take care of PVR side of things. My greatest issue though is what is the best solution for getting the satellite system into the HTPC? After some research my first idea was to use a satellite tuner card; models are available for Hauppauge and other vendors so really it was about which was going to offer best compatibility with Linux? (distro is Arch Linux with 3.15 kernel) The model of card I was looking was from DVB-Sky: http://www.dvbsky.net/Products_S950C.html something like that, which has CAM module slot and is DVB-S/S2 compatible and claims to have drivers supported by the Linuxtv project. Or alternately going for something like this: http://www.dvbsky.net/Products_T9580.html as it has a combined DVB-T tuner, then using a USB card reader for the CAM smart card. Has anyone used the cards above, what are the opinions relating to them? Also would they work with motorized dishes? Since I'm not sure if all CAM's are supported as apparently our satellite tv provider wanted to lock out other receivers so they force people to use their own product; my second idea was to perhaps use a capture card with RCA inputs. Something like this: http://www.c21video.com/viewcast/osprey-210.html perhaps or a Hauppauge HD-PVR mk I edition: which according to the wiki is supported. Looking forward to hearing advice. Thanks. Kaya -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Hi Kaya, RCA inputs is probably the last thing you want. Less quality, more of a pain to set up. You may or may not be able to use that CAM - but even if it's supported, a CAM has downsides. It generally only supports one channel at a time - and surely not multiple channels from different frequencies (if you have more tuners). And it's more expensive, both the tuner (that needs a CI slot) and the CAM you need. Also, I'm not sure if tvheadend nowadays supports a CAM - it used not to, but support may have been added. The main downside of a phoenix-mode cardreader is that it's harder to set up, but if you can find a guide for your provider it's generally doable. It's cheaper, more flexible and allows for faster channel switching. As for a tuner, I personally suggest going for a USB-tuner. You never know if you want to connect you tuner to a notebook or NAS or anything in the future, with USB you're more flexible. If you do go for PCI-e, Tevii appears to have some supported products that are also available. If you go for USB, support is somewhat problematic (problematic because many supported tuners are no longer available in stores), you'll have to see what's locally available. (perhaps also check second-hand) Be careful, some devices have various revisions. Always check http://linuxtv.org/wiki/index.php/Hardware_Device_Information Very recently, Antti reviewed a patch from nibble.max to support the DVBsky S960. (and presumably it's direct clones from Mystique) This is a pretty cheap tuner that can still be found in shops. It would appear that as soon as this patch gets merged, this device will be supported if you compile v4l-dvb yourself, and in time support will make it into the kernel. In any case, you want something with in-kernel support - something that's only supported by s2-liplianin or vendor drivers (like many dvbsky and TBS products) will only break in the long term. Only exception to this is Sundtek, but I personally have mixed feelings about closed source userspace drivers. I wouldn't recommend them personally. Good luck, P. van Gaans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] em28xx: add MSI Digivox Trio support
On 05/27/2014 09:12 AM, Hans Verkuil wrote:
On 05/27/2014 02:04 AM, P. van Gaans wrote:
http://linuxtv.org/wiki/index.php/MSI_DigiVox_Trio
If you're having a deja-vu, yeah, it's still me. I'm still using this
device using my butt-ugly patch by adding:
{ USB_DEVICE(0xeb1a, 0x2885),/* MSI Digivox Trio */
.driver_info = EM2884_BOARD_TERRATEC_H5 },
to linux/drivers/media/usb/em28xx/em28xx-cards.c.
It's starting to bug me more and more that I can never update my kernel
(well not without hassle anyway). I've written this to the mailinglist
before, but with no response.
I just don't have the skill to write this in the neat way it needs to be
to be able to go upstream. Should I try to hire someone to do that? If
so, any suggestions? Just put an ad up on craigslist or something? Does
such a patch have a chance of going upstream? (as that's the whole point
- I want to update my kernel again)
It should be really straightforward given that no reverse engineering or
anything is needed. It's just what it states above - pretend the Digivox
is an H5 and it's done.
Anyone who can tune in on this, please share your thoughts.
I've made it into a proper patch, see below.
Can you reply with your 'Signed-off-by' line?
i.e.: Signed-off-by: John Doe john@foo.com
Since you're the author of the patch (I just formatted it), I need that to
get it upstream.
Regards,
Hans
diff --git a/drivers/media/usb/em28xx/em28xx-cards.c
b/drivers/media/usb/em28xx/em28xx-cards.c
index 15ad470..9da812b 100644
--- a/drivers/media/usb/em28xx/em28xx-cards.c
+++ b/drivers/media/usb/em28xx/em28xx-cards.c
@@ -2280,6 +2280,8 @@ struct usb_device_id em28xx_id_table[] = {
.driver_info = EM2820_BOARD_UNKNOWN },
{ USB_DEVICE(0xeb1a, 0x2875),
.driver_info = EM2820_BOARD_UNKNOWN },
+ { USB_DEVICE(0xeb1a, 0x2885), /* MSI Digivox Trio */
+ .driver_info = EM2884_BOARD_TERRATEC_H5 },
{ USB_DEVICE(0xeb1a, 0xe300),
.driver_info = EM2861_BOARD_KWORLD_PVRTV_300U },
{ USB_DEVICE(0xeb1a, 0xe303),
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Thank you!
Signed-off-by: P. van Gaans w3ird_n...@gmx.net
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
MSI Digivox Trio, should I try to hire someone to patch for this device?
http://linuxtv.org/wiki/index.php/MSI_DigiVox_Trio
If you're having a deja-vu, yeah, it's still me. I'm still using this
device using my butt-ugly patch by adding:
{ USB_DEVICE(0xeb1a, 0x2885),/* MSI Digivox Trio */
.driver_info = EM2884_BOARD_TERRATEC_H5 },
to linux/drivers/media/usb/em28xx/em28xx-cards.c.
It's starting to bug me more and more that I can never update my kernel
(well not without hassle anyway). I've written this to the mailinglist
before, but with no response.
I just don't have the skill to write this in the neat way it needs to be
to be able to go upstream. Should I try to hire someone to do that? If
so, any suggestions? Just put an ad up on craigslist or something? Does
such a patch have a chance of going upstream? (as that's the whole point
- I want to update my kernel again)
It should be really straightforward given that no reverse engineering or
anything is needed. It's just what it states above - pretend the Digivox
is an H5 and it's done.
Anyone who can tune in on this, please share your thoughts.
Best regards,
P. van Gaans
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Developers] I know how to make this Digivox work, could v4l-dvb be patched for it?
Device: http://linuxtv.org/wiki/index.php/MSI_DigiVox_Trio
In the making it work section I already described it: you just need to
threat this device exactly as if it's a Terratec H5.
Something as simple as adding:
{ USB_DEVICE(0xeb1a, 0x2885),/* MSI Digivox Trio */
.driver_info = EM2884_BOARD_TERRATEC_H5 },
to linux/drivers/media/usb/em28xx/em28xx-cards.c is sufficient. This is
probably a slightly ugly way to do it, but I've been using this solution
for half a year and haven't found any problems with it.
What needs to be done in order to get a change like this (or maybe one
that looks slighty more neat) into the official v4l-dvb?
Best regards,
P. van Gaans
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Terratec H5 (analog support)
On 10/24/2013 04:26 PM, Tobias Bengtsson wrote: Hi! I'm trying this question again. DVB-C works perfectly with the V4L-driver, but I'm a bit curious if the analog tuner is supposed to be supported? A video0 device gets created but starting tvheadend it complains about it missing a tuner and the device is skipped. Is this an issue with tvheadend or a constraint of the driver? Thanks in advance. Hi Tobias, To my knowledge, the driver does not support analog in any way. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: EM28xx - MSI Digivox Trio - almost working.
On 08/08/2013 02:37 AM, P. van Gaans wrote:
On 20-06-13 07:14, P. van Gaans wrote:
Hi all,
(device: http://linuxtv.org/wiki/index.php/MSI_DigiVox_Trio)
Thanks to the message from Philip Pemberton I was able to try loading
the em28xx driver myself using:
sudo modprobe em28xx card=NUMBER
echo eb1a 2885 | sudo tee /sys/bus/usb/drivers/em28xx/new_id
Here are the results for NUMBER:
Card=79 (Terratec Cinergy H5): works, less corruption than card=87, just
some blocks every few seconds. Attenuators didn't help.
Card=81 (Hauppauge WinTV HVR 930C): doesn't work, no /dev/dvb adapter
Card=82 (Terratec Cinergy HTC Stick): similar to card=87
Card=85 (PCTV QuatroStick (510e)): constantly producing i2c read errors,
doesn't work
Card=86 (PCTV QuatroStick nano (520e): same
Card=87 (Terratec Cinergy HTC USB XS): stick works and scans channels,
but reception is bugged with corruption. It's like having a DVB-T
antenna that's just not good enough, except this is DVB-C and my signal
is excellent. Attenuators didn't help.
Card=88 (C3 Tech Digital Duo HDTV/SDTV USB): doesn't work, no /dev/dvb
adapter
So with card=79 it's really close to working. What else can I do?
Best regareds,
P. van Gaans
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi all,
Success!
While I never succeeded in figuring out how the sniffing is supposed to
be done (how to get any output from those scripts anyway? how to load
the debug module in such away it actually works? run on native linux, or
a windows VM on linux, or snoop in windows en run the script on linux?
you get the picture) I just noticed a little notice on the DVB-C USB
wiki page:
If you are experiencing problems with USB devices, it may not be the
fault of the tuner. For example AMD 700 series chipsets (e.g. 780G) have
a problem with USB ports which results in tuners working or partially
working or not working at all.
I was actually not even testing on an AMD 700 series but on an AMD 600
series. And a somewhat older kernel, with latest v4l-dvb compiled.
So here's what I did: I took the Digivox Trio, plugged it in an Ivy
Bridgy computer with Lubuntu 13.04 (stock kernel, stock v4l-dvb, Lubuntu
appears to come with the firmware preloaded), load the em28xx driver as
if the Digivox were a Terratec H5 and watched 5 minutes or so, flawless.
I will continue to test and watch some longer programs, but right now it
appears it is safe to say the Digivox Trio can be supported by simply
treating as an H5.
Best regards,
P. van Gaans
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
It's been a while I've been using this setup and I haven't found any
obvious flaws.
I've added this to my own linux/drivers/media/usb/em28xx/em28xx-cards.c:
{ USB_DEVICE(0xeb1a, 0x2885), /* MSI Digivox Trio */
.driver_info = EM2884_BOARD_TERRATEC_H5 },
So it would load automatically. I've been using two of these with tvheadend.
So can this device be added? Any more info needed?
Best regards,
P. van Gaans
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
DVB-S2 USB device: DVBsky, Technotrend or Tevii?
Hi, I want to buy a DVB-S2 USB device. The following are available here (all Montage tuner/demod): Mystique SaTiX-S2 (DVBsky S860 clone) (M88TS2020/M88DS3000) Mystique SaTiX-S2 v2 (DVBsky S960 clone) (M88TS2022/M88DS3103) TechnoTrend Connect S2-4600 (M88TS2022/M88DS3103) TeVii S660 (M88TS2020/M88DS3000) Wiki links: http://linuxtv.org/wiki/index.php/DVBSKY_S860 http://linuxtv.org/wiki/index.php/DVBSKY_S960 http://linuxtv.org/wiki/index.php/TechnoTrend_TT-connect_S2-4600 http://linuxtv.org/wiki/index.php/TeVii_S660 Only the S660 is supported, but it has serious DiSEqC issues according to wiki, plus it's the most expensive, so it's not very attractive. Is there any hope/chance one of the others could be made to work with v4l-dvb? I've noticed liplian supports everything, but I don't think that's the most future-proof option. Best regards, P. van Gaans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
em28xx disabled when compiling on Debian wheezy?
Hi, I don't quite understand. When I follow instructions from http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers I seem to have different results. When I download/install the drivers on an Ubuntu 11.04 machine (it hasn't been updated in a while..) the em28xx driver is enabled in v4l/.config. When I try the same on a Debian stable (wheezy, kernel 3.2.0-4-amd64) install, the em28xx driver gets outcommented and not set in v4l/.config. If I enable it anyway, the driver won't load and produce errors like em28xx: Unknown symbol vb2_queue_init. Seemingly em28xx is disabled for a reason, but why? I would think Debian wheezy is in every way better (and newer) than Ubuntu 11.04. Am I missing some package? How can I fix it? Best regards, P. van Gaans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: EM28xx - MSI Digivox Trio - almost working.
On 20-06-13 07:14, P. van Gaans wrote: Hi all, (device: http://linuxtv.org/wiki/index.php/MSI_DigiVox_Trio) Thanks to the message from Philip Pemberton I was able to try loading the em28xx driver myself using: sudo modprobe em28xx card=NUMBER echo eb1a 2885 | sudo tee /sys/bus/usb/drivers/em28xx/new_id Here are the results for NUMBER: Card=79 (Terratec Cinergy H5): works, less corruption than card=87, just some blocks every few seconds. Attenuators didn't help. Card=81 (Hauppauge WinTV HVR 930C): doesn't work, no /dev/dvb adapter Card=82 (Terratec Cinergy HTC Stick): similar to card=87 Card=85 (PCTV QuatroStick (510e)): constantly producing i2c read errors, doesn't work Card=86 (PCTV QuatroStick nano (520e): same Card=87 (Terratec Cinergy HTC USB XS): stick works and scans channels, but reception is bugged with corruption. It's like having a DVB-T antenna that's just not good enough, except this is DVB-C and my signal is excellent. Attenuators didn't help. Card=88 (C3 Tech Digital Duo HDTV/SDTV USB): doesn't work, no /dev/dvb adapter So with card=79 it's really close to working. What else can I do? Best regareds, P. van Gaans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Hi all, Success! While I never succeeded in figuring out how the sniffing is supposed to be done (how to get any output from those scripts anyway? how to load the debug module in such away it actually works? run on native linux, or a windows VM on linux, or snoop in windows en run the script on linux? you get the picture) I just noticed a little notice on the DVB-C USB wiki page: If you are experiencing problems with USB devices, it may not be the fault of the tuner. For example AMD 700 series chipsets (e.g. 780G) have a problem with USB ports which results in tuners working or partially working or not working at all. I was actually not even testing on an AMD 700 series but on an AMD 600 series. And a somewhat older kernel, with latest v4l-dvb compiled. So here's what I did: I took the Digivox Trio, plugged it in an Ivy Bridgy computer with Lubuntu 13.04 (stock kernel, stock v4l-dvb, Lubuntu appears to come with the firmware preloaded), load the em28xx driver as if the Digivox were a Terratec H5 and watched 5 minutes or so, flawless. I will continue to test and watch some longer programs, but right now it appears it is safe to say the Digivox Trio can be supported by simply treating as an H5. Best regards, P. van Gaans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
A few wiki ideas (please comment!)
Hi, I have a few ideas for the wiki. They go a bit further than fixing a typo, so I'd first like to discuss the ideas before messing up wiki pages and doing lots of unwanted work. The first is to add a ==Users== section to each device, just above the external links section. For this I already made the following template to use (may need some tweaking, but it's a start): http://www.linuxtv.org/wiki/index.php/Template:Users_who_own_this_device The idea is primarily that whenever a patch is written for the device or another patch that might influence this device it's easier to find contact details for a few users who are willing to test the patch so they can be contacted directly. Most people don't read every message on the mailing list. --- The second idea is a bit more complicated and I'm not even sure the wiki is the right place to do it. While searching for support information for various devices, I noticed that I kept stumbling upon abandoned patches, mostly on the mailing list, for devices that are currently unsupported in v4l-dvb. If I really start to dig in, I'm afraid I'll find at least tens of them. Some of those devices are really attractive. That seems like a waste: we know how the device works, we actually have working code.. But for one reason or another, it's not getting pulled. Maybe the code needs a cleanup. Maybe somebody just forgot to file a pull request. Maybe the code wasn't signed off. AFAIK we currently have no overview of these patches. The idea is to make a wiki page (suggestions for a page title?) that lists the device, links to the available patch(es) or code and lists the reason why the patch hasn't been pulled yet. Best regards, P. van Gaans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Fwd: [PATCH 2/6 v2] dvbsky, dvb-s/s2 usb box
Trying to figure out if a Mystique SaTiX-S2 Sky V2 USB device (USB ID
0572:6831, looks like it is a DVBSKY S960 clone) would be supported
before I buy, I came along this message.
Looking at
http://git.linuxtv.org/media_tree.git/blob/HEAD:/drivers/media/usb/dvb-usb/dw2102.c
it seems as if this patch never made it, so these USB S2 boxes would be
unsupported.
Would it still be possible to include this patch?
Best regards,
P. van Gaans
Original Message
Subject: [PATCH 2/6 v2] dvbsky, dvb-s/s2 usb box
Date: Fri, 27 Apr 2012 15:06:29 +0800
From: nibble.max nibble@gmail.com
To: Mauro Carvalho Chehab mche...@redhat.com
CC: Antti Palosaari cr...@iki.fi, linux-media
linux-media@vger.kernel.org
Also fix some code sytle errors checked by checkpatch.pl.
---
drivers/media/dvb/dvb-usb/Kconfig |2 +
drivers/media/dvb/dvb-usb/dw2102.c | 337
2 files changed, 305 insertions(+), 34 deletions(-)
diff --git a/drivers/media/dvb/dvb-usb/Kconfig
b/drivers/media/dvb/dvb-usb/Kconfig
index be1db75..93c9381 100644
--- a/drivers/media/dvb/dvb-usb/Kconfig
+++ b/drivers/media/dvb/dvb-usb/Kconfig
@@ -279,6 +279,8 @@ config DVB_USB_DW2102
select DVB_STV0288 if !DVB_FE_CUSTOMISE
select DVB_STB6000 if !DVB_FE_CUSTOMISE
select DVB_CX24116 if !DVB_FE_CUSTOMISE
+ select DVB_M88TS202X if !DVB_FE_CUSTOMISE
+ select DVB_M88DS3103 if !DVB_FE_CUSTOMISE
select DVB_SI21XX if !DVB_FE_CUSTOMISE
select DVB_TDA10023 if !DVB_FE_CUSTOMISE
select DVB_MT312 if !DVB_FE_CUSTOMISE
diff --git a/drivers/media/dvb/dvb-usb/dw2102.c
b/drivers/media/dvb/dvb-usb/dw2102.c
index 451c5a7..1cf62fb 100644
--- a/drivers/media/dvb/dvb-usb/dw2102.c
+++ b/drivers/media/dvb/dvb-usb/dw2102.c
@@ -19,6 +19,8 @@
#include stb6000.h
#include eds1547.h
#include cx24116.h
+#include m88ts202x.h
+#include m88ds3103.h
#include tda1002x.h
#include mt312.h
#include zl10039.h
@@ -118,12 +120,12 @@ MODULE_PARM_DESC(demod, demod to probe (1=cx24116
2=stv0903+stv6110
DVB_DEFINE_MOD_OPT_ADAPTER_NR(adapter_nr);
static int dw210x_op_rw(struct usb_device *dev, u8 request, u16 value,
- u16 index, u8 * data, u16 len, int flags)
+ u16 index, u8 *data, u16 len, int flags)
{
int ret;
u8 *u8buf;
unsigned int pipe = (flags == DW210X_READ_MSG) ?
- usb_rcvctrlpipe(dev, 0) : usb_sndctrlpipe(dev,
0);
+ usb_rcvctrlpipe(dev, 0) : usb_sndctrlpipe(dev, 0);
u8 request_type = (flags == DW210X_READ_MSG) ? USB_DIR_IN : USB_DIR_OUT;
u8buf = kmalloc(len, GFP_KERNEL);
@@ -133,7 +135,8 @@ static int dw210x_op_rw(struct usb_device *dev, u8
request, u16 value,
if (flags == DW210X_WRITE_MSG)
memcpy(u8buf, data, len);
- ret = usb_control_msg(dev, pipe, request, request_type |
USB_TYPE_VENDOR,
+ ret = usb_control_msg(dev, pipe,
+ request, request_type | USB_TYPE_VENDOR,
value, index , u8buf, len, 2000);
if (flags == DW210X_READ_MSG)
@@ -179,7 +182,7 @@ static int dw2102_i2c_transfer(struct i2c_adapter
*adap, struct i2c_msg msg[],
break;
case 0x60:
if (msg[0].flags == 0) {
- /* write to tuner pll */
+ /* write to tuner pll */
buf6[0] = 0x2c;
buf6[1] = 5;
buf6[2] = 0xc0;
@@ -190,7 +193,7 @@ static int dw2102_i2c_transfer(struct i2c_adapter
*adap, struct i2c_msg msg[],
ret = dw210x_op_rw(d-udev, 0xb2, 0, 0,
buf6, 7, DW210X_WRITE_MSG);
} else {
- /* read from tuner */
+ /* read from tuner */
ret = dw210x_op_rw(d-udev, 0xb5, 0, 0,
buf6, 1, DW210X_READ_MSG);
msg[0].buf[0] = buf6[0];
@@ -273,7 +276,8 @@ static int dw2102_serit_i2c_transfer(struct
i2c_adapter *adap,
return num;
}
-static int dw2102_earda_i2c_transfer(struct i2c_adapter *adap, struct
i2c_msg msg[], int num)
+static int dw2102_earda_i2c_transfer(struct i2c_adapter *adap,
+ struct i2c_msg msg[], int num)
{
struct dvb_usb_device *d = i2c_get_adapdata(adap);
int ret = 0;
@@ -346,7 +350,8 @@ static int dw2102_earda_i2c_transfer(struct
i2c_adapter *adap, struct i2c_msg ms
return num;
}
-static int dw2104_i2c_transfer(struct i2c_adapter *adap, struct i2c_msg
msg[], int num)
+static int dw2104_i2c_transfer(struct i2c_adapter *adap,
+ struct i2c_msg msg[], int num)
{
struct
Re: EM28xx - MSI Digivox Trio - almost working.
On 20-06-13 09:40, Antti Palosaari wrote: On 06/20/2013 08:14 AM, P. van Gaans wrote: Hi all, (device: http://linuxtv.org/wiki/index.php/MSI_DigiVox_Trio) Thanks to the message from Philip Pemberton I was able to try loading the em28xx driver myself using: sudo modprobe em28xx card=NUMBER echo eb1a 2885 | sudo tee /sys/bus/usb/drivers/em28xx/new_id Here are the results for NUMBER: Card=79 (Terratec Cinergy H5): works, less corruption than card=87, just some blocks every few seconds. Attenuators didn't help. Card=81 (Hauppauge WinTV HVR 930C): doesn't work, no /dev/dvb adapter Card=82 (Terratec Cinergy HTC Stick): similar to card=87 Card=85 (PCTV QuatroStick (510e)): constantly producing i2c read errors, doesn't work Card=86 (PCTV QuatroStick nano (520e): same Card=87 (Terratec Cinergy HTC USB XS): stick works and scans channels, but reception is bugged with corruption. It's like having a DVB-T antenna that's just not good enough, except this is DVB-C and my signal is excellent. Attenuators didn't help. Card=88 (C3 Tech Digital Duo HDTV/SDTV USB): doesn't work, no /dev/dvb adapter So with card=79 it's really close to working. What else can I do? Take USB sniffs, generate code, copy paste that to the driver until it starts working. After it start working start reducing generated code. That way with trial and error you will find out problematic register(s) very quickly. There is suitable scripts to generate em28xx drx-k code from the sniffs, maybe in dvb-utils package. Mauro has done that script. I used it when I added PCTV 520e support (problem was bug in DRX-K GPIO code). regards Antti Hi Antti, Thanks for your answer. Do you mean I sniff on Windows or Linux? Would you happen to remember the name of the script you are referring to? Also in em28xx-new (https://bitbucket.org/mdonoughe/em28xx-new/overview) the device was supported. Wouldn't it be easier to try and find the differences between the Cinergy H5 and the Digivox in that code, or should I not even think of going there? Best regards, P. van Gaans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
EM28xx - MSI Digivox Trio - almost working.
Hi all, (device: http://linuxtv.org/wiki/index.php/MSI_DigiVox_Trio) Thanks to the message from Philip Pemberton I was able to try loading the em28xx driver myself using: sudo modprobe em28xx card=NUMBER echo eb1a 2885 | sudo tee /sys/bus/usb/drivers/em28xx/new_id Here are the results for NUMBER: Card=79 (Terratec Cinergy H5): works, less corruption than card=87, just some blocks every few seconds. Attenuators didn't help. Card=81 (Hauppauge WinTV HVR 930C): doesn't work, no /dev/dvb adapter Card=82 (Terratec Cinergy HTC Stick): similar to card=87 Card=85 (PCTV QuatroStick (510e)): constantly producing i2c read errors, doesn't work Card=86 (PCTV QuatroStick nano (520e): same Card=87 (Terratec Cinergy HTC USB XS): stick works and scans channels, but reception is bugged with corruption. It's like having a DVB-T antenna that's just not good enough, except this is DVB-C and my signal is excellent. Attenuators didn't help. Card=88 (C3 Tech Digital Duo HDTV/SDTV USB): doesn't work, no /dev/dvb adapter So with card=79 it's really close to working. What else can I do? Best regareds, P. van Gaans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: EM28xx - new device ID - Ion Video Forever USB capture dongle
On 26-05-13 11:23, Philip Pemberton wrote: Hi folks, This is my first post here (I think?) and I'm going to make it an informative one :) TL/DR: Can someone please add this to the device ID list for the em28xx module? Ion Video Forever - USB ID EB1A:5124, Card Type 9. Confirmed as working with Xawtv and VLC, video source PAL composite from a FLIR camera; S-video and audio untested as I have no suitable source to hand. Test platform: Ubuntu 13.04 Raring, kernel 3.8.0-21-generic #32-Ubuntu SMP x86_64 The longer version: I found this thing in a local Maplins under stock code A27KJ for the princely sum of £29.99 on special offer. According to the box, it's a Video Forever VHS-to-Digital Video Converter by ION (www.ionaudio.com). Strangely they don't list it on their website, so perhaps it's a special for Maplin? lsusb says: Bus 001 Device 084: ID eb1a:5124 eMPIA Technology, Inc. The CD-ROM in the packet is apparently a driver set for an ezcap device (Ezcap Video Grabber), the INF file suggests it's an EM2860 series chip. For a laugh, I did this: sudo modprobe em28xx card=9 echo eb1a 5124 | sudo tee /sys/bus/usb/drivers/em28xx/new_id Which has the effect of loading the EM28xx driver with cardtype forced to 9 (which seems to be a generic EM2860-based device ID), then adding the new device ID (temporarily) to the module. Dmesg after doing this: [377328.118295] usb 1-1.4.3.5: new high-speed USB device number 94 using ehci-pci [377328.217158] usb 1-1.4.3.5: New USB device found, idVendor=eb1a, idProduct=5124 [377328.217160] usb 1-1.4.3.5: New USB device strings: Mfr=0, Product=1, SerialNumber=2 [377328.217162] usb 1-1.4.3.5: Product: USB VIDBOX FW Audio [377328.217163] usb 1-1.4.3.5: SerialNumber: USB2.0 VIDBOX FW [377328.217448] em28xx: New device USB VIDBOX FW Audio @ 480 Mbps (eb1a:5124, interface 0, class 0) [377328.217450] em28xx: Video interface 0 found [377328.217451] em28xx: DVB interface 0 found [377328.217506] em28xx #0: chip ID is em2860 [377328.344000] em28xx #0: i2c eeprom 00: 1a eb 67 95 1a eb 24 51 50 00 20 03 8c 28 6a 22 [377328.344007] em28xx #0: i2c eeprom 10: 00 00 24 57 06 02 00 00 00 00 00 00 00 00 00 00 [377328.344012] em28xx #0: i2c eeprom 20: 02 00 01 00 f0 10 01 00 00 00 00 00 5b 00 00 00 [377328.344016] em28xx #0: i2c eeprom 30: 00 00 20 40 20 80 02 20 01 01 00 00 00 00 00 00 [377328.344020] em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 c4 00 00 [377328.344025] em28xx #0: i2c eeprom 50: 00 a2 00 87 81 00 00 00 00 00 00 00 00 00 00 00 [377328.344029] em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00 22 03 55 00 53 00 [377328.344033] em28xx #0: i2c eeprom 70: 42 00 32 00 2e 00 30 00 20 00 56 00 49 00 44 00 [377328.344038] em28xx #0: i2c eeprom 80: 42 00 4f 00 58 00 20 00 46 00 57 00 28 03 55 00 [377328.344042] em28xx #0: i2c eeprom 90: 53 00 42 00 20 00 56 00 49 00 44 00 42 00 4f 00 [377328.344047] em28xx #0: i2c eeprom a0: 58 00 20 00 46 00 57 00 20 00 41 00 75 00 64 00 [377328.344051] em28xx #0: i2c eeprom b0: 69 00 6f 00 00 00 00 00 00 00 00 00 00 00 00 00 [377328.344055] em28xx #0: i2c eeprom c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [377328.344060] em28xx #0: i2c eeprom d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [377328.344064] em28xx #0: i2c eeprom e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [377328.344068] em28xx #0: i2c eeprom f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [377328.344074] em28xx #0: EEPROM ID= 0x9567eb1a, EEPROM hash = 0x806f2156 [377328.344075] em28xx #0: EEPROM info: [377328.344076] em28xx #0: AC97 audio (5 sample rates) [377328.344076] em28xx #0: 500mA max power [377328.344078] em28xx #0: Table at 0x24, strings=0x288c, 0x226a, 0x [377328.344080] em28xx #0: Identified as Pinnacle Dazzle DVC 90/100/101/107 / Kaiser Baas Video to DVD maker / Kworld DVD Maker 2 / Plextor ConvertX PX-AV100U (card=9) [377328.706041] saa7115 4-0025: saa7113 found (1f7113d0e10) @ 0x4a (em28xx #0) [377329.472675] em28xx #0: Config register raw data: 0x50 [377329.496532] em28xx #0: AC97 vendor ID = 0x83847652 [377329.508515] em28xx #0: AC97 features = 0x6a90 [377329.508517] em28xx #0: Sigmatel audio processor detected(stac 9752) [377329.967933] em28xx #0: v4l2 driver version 0.1.3 [377330.990725] em28xx #0: V4L2 video device registered as video0 [377330.990727] em28xx #0: V4L2 VBI device registered as vbi0 Fire up Xawtv or VLC, select the device, enjoy. Thanks, Hi Philip, Very interesting post! I also have an unsupported em28xx device, a MSI Digivox Trio (http://linuxtv.org/wiki/index.php/MSI_DigiVox_Trio) which I suspect to be similar to a PCTV QuatroStick nano. If I use the device ID from my stick and card number from the QuatroStick to forceload the em28xx driver, would that be safe? Or would I risk destroying the USB stick? I don't know if it's actually the same, all I know is that it shares many (maybe all) components. Best regards,
MSI DigiVox Trio support?
Hi, I bought some MSI DigiVox trio. I made a page for it on the wiki: http://linuxtv.org/wiki/index.php/MSI_DigiVox_Trio So what I know is.. It shares several (if not all? maybe a clone?) components with the PCTV Quatrostick 520e. There was once some support (at least DVB-C) in em28xx-new. Is there anything I can do now? I can't really code, but can copypast. I could probably make a machine with this stick plugged in available through SSH. Any hope? Best regards, Pim -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Available and supported DVB-C USB device
I'm living in The Netherlands and am looking for a DVB-C USB device that's available, supported and (preferably) affordable. Devices that are available and affordable would appear to be the Delock DVB-C USB stick (which I can't find a whole lot about) and the MSI DigiVox mini Trio. According to a message on the mailinglist from 2010 by Matthias Larisch: I recently bought a DigiVox Trio by MSI. This card contains the following chips: nxp tda18271hdc2 (tuner) micronas drx 3926ka3 (demodulator, 3in1) em2884 atmlh946 64c (eeprom) micronas avf 4910ba1 so it is comparable to the Terratec Cinergy HTC USB XS HD and the TerraTec H5. Back in 2010 it didn't work, but I've noticed the EM2884 and Micronas DRX 3926K (maybe not the same?) and TDA18271HDC2 do work in the PCTV QuatroStick nano. (http://linuxtv.org/wiki/index.php/DVB-C_USB_Devices) So perhaps the MSI could also work? Or maybe someone has suggestions for a suitable device. Most of the devices on the wiki page are sadly either unavailable or very expensive. Best regards, Pim -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: S2-3200 switching-timeouts on 2.6.38
On 08/11/2011 01:49 AM, P. van Gaans wrote: On 03/21/2011 08:46 PM, Rico Tzschichholz wrote: Hello, I would like to know if there is any intention to include this patch soon? https://patchwork.kernel.org/patch/244201/ Currently using 2.6.38 results in switching-timeouts on my S2-3200 and this patch fixes this for good. So it would be nice to have it in 2.6.39. Thank you and best regards, Rico Tzschichholz Hello, I also have a Technotrend S2-3200. Bought it 4 years ago. Support for Linux seemed to be close at the time. I was a bit of a fool for thinking that. It's been on the shelf for most of the time. Anyway, I've applied that patch, and it turns the S2-3200 from being worth hardly more than a paperweight to a functional DVB-S card. I don't understand why this patch does not get included. Only DVB-S2 transponders don't consistently lock properly in kaffeine. I'll test what scan does tomorrow, see if it's a kaffeine-specific problem or not. But even just DVB-S working properly is a massive difference for this card. If it helps, I'll check the silicon version of my card tomorrow as well. Best regards, P. van Gaans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Hello, Here I am again. My card can be seen at http://tinypic.com/r/2hewzyu/7 Chip: C2L STB0899 VQ628NDY 220QQ VQ MLT 22 645 So far, scan-s2 won't compile: scan.c:51:2: error: #error scan-s2 requires Linux DVB driver API version 5.0! (I am doing something wrong undoubtedly) and I cannot find a way to make w_scan scan specific frequencies. It must be possible, but right now I can't figure it out. Scan doesn't support DVB-S2. Perhaps someone else who has an S2-3200 can test this, if not, I will eventually get to it I guess, but I'm not entirely sure when. Best regards, Pim -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: S2-3200 switching-timeouts on 2.6.38
On 03/21/2011 08:46 PM, Rico Tzschichholz wrote: Hello, I would like to know if there is any intention to include this patch soon? https://patchwork.kernel.org/patch/244201/ Currently using 2.6.38 results in switching-timeouts on my S2-3200 and this patch fixes this for good. So it would be nice to have it in 2.6.39. Thank you and best regards, Rico Tzschichholz Hello, I also have a Technotrend S2-3200. Bought it 4 years ago. Support for Linux seemed to be close at the time. I was a bit of a fool for thinking that. It's been on the shelf for most of the time. Anyway, I've applied that patch, and it turns the S2-3200 from being worth hardly more than a paperweight to a functional DVB-S card. I don't understand why this patch does not get included. Only DVB-S2 transponders don't consistently lock properly in kaffeine. I'll test what scan does tomorrow, see if it's a kaffeine-specific problem or not. But even just DVB-S working properly is a massive difference for this card. If it helps, I'll check the silicon version of my card tomorrow as well. Best regards, P. van Gaans -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
