please respond to the list -
ptay1685 wrote:
Thanks.
Just my luck. First off I get a
Nebula usb DigiTV which never worked owing to an problem with ny
nforce2 usb controller (i found out when it was too late), and which
came with suspect WIndows software. So before I bought my two Leadtek
dongles I checked the DVB wikipedia to make sure I got a fully Linux
supported device. Now I have two new usb dongles neither of which work
with Linux. You can't bloody win can you? At least they come with great
WIndows software, which is more than you can say for the Nebula.
I can now use the Nebula with Linux
but the leadtek software under WIndows is so good, that now I simply
boot Windows to do my DVB stuff, and sometimes use Linux to author the
DVD's (DeVeDe).
I guess this situation will persist
until hardware vendors decide to support Linux. Unfortunately I will
probably be six feet under by then.
I would certainly be interested in a
fix for this situation but its hardly worth anyone putting in a lot of
effort for just one person or at most a handful of people. But if you
are able / willing to do something to remedy this problem I will
certainly be very grateful.
Or perhaps one day I will work up
the motivation to patch the code as you did - but i dare not hold my
breath waiting for that to happen!
1) the fix is simple and someone on the list will be able to push
through a simple patch, if all that is involved is added another
identifier to recognise your device.
2) we still need your lsusb -v to confirm this.
if you can do even a few minutes of effort to determine the required
information, you might be surprised to find others in your situation
and/or those capable of helping.
firstly: lsusb is located in the usbutils package so you may need to
install it, or you need to prefix the command with its location
i.e. /sbin/lsusb. Please try this first and post the result back to the
list. (with the -v option please)
secondly in reference to my patch below.
I never heard anything more from the list about it and I have no reason
to believe it was ever incorporated as a patch. I suspect this dongle
is a variant sold only in Australia (where you and I are from
obviously) and so the demand is relatively small - thus no one else was
interested. I posted more for people like yourself for whom my fix may
help.
The only thing this patch did is add an extra identifier so that the
dongle was recognized. Now that said, I suspect there is an even more
recent variant released in the last 2/3 months (right after I bought
mine :( ) which may have a different identifier again. So the result of
lsusb is even more important.
Unfortunately I got distracted after I got my dongle recognized and
haven't made it fully work yet (with MythTv) - but if you are
interested I might have another go at it.
I also note the large number of dibcom related posts in recent months
which will have a direct bearing on this dongle. So recent versions of
the dvb code are essential.
Cheers,
J
ptay1685 wrote:
How do I tell the usb-id? Tried to do a lsusb -v but the command is
unrecognised.
Note that the Leadtek device is not actually recognised by the kernel (shown
via dmesg).
The following is from a previous conversation on this mailing list and might
give you the info you need:
_______________________________________________________________________________
Hi,
How do I get a patch incorporated into the dvb kernel section ?
After recently purchasing a LeadTek WinFast DTV Dongle I rapidly
discovered it was the variant that was not recognized in the kernel
i.e. as previously reported at:
http://www.linuxtv.org/pipermail/linux-dvb/2007-December/022373.html
http://www.linuxtv.org/pipermail/linux-dvb/2008-January/023175.html
its device ids are: (lsusb)
ID 0413:6f01 Leadtek Research, Inc.
Rather than make the changes suggested by previous posters I set about
making a script and associated kernel patches to automatically do this.
My motivation was simple: I use a laptop with an ATI graphics card and
fedora 8. I find the best drivers for this card are currently from Livna
and are updated monthly (and changes are significant at the moment i.e.
see the phoronix forum). So I would need to do this repeatedly.
In my patch I add an identifier (USB_PID_WINFAST_DTV_DONGLE_STK7700P_B)
and modify the table appropriately
When I plug it in I now see in my messages log
kernel: usb 1-4: new high speed USB device using ehci_hcd and address 9
kernel: usb 1-4: configuration #1 chosen from 1 choice
kernel: dib0700: loaded with support for 2 different device-types
kernel: dvb-usb: found a 'Leadtek Winfast DTV Dongle B (STK7700P based)'
in cold state, will try to load a firmware
kernel: dvb-usb: downloading firmware from file 'dvb-usb-dib0700-01.fw'
kernel: dib0700: firmware started successfully.
kernel: dvb-usb: found a 'Leadtek Winfast DTV Dongle B (STK7700P based)'
in warm state.
kernel: dvb-usb: will pass the complete MPEG2 transport stream to the
software demuxer.
kernel: DVB: registering new adapter (Leadtek Winfast DTV Dongle B
(STK7700P based))
kernel: DVB: registering frontend 0 (DiBcom 7000PC)...
kernel: MT2060: successfully identified (IF1 = 1220)
kernel: dvb-usb: Leadtek Winfast DTV Dongle B (STK7700P based)
successfully initialized and connected.
kernel: usbcore: registered new interface driver dvb_usb_dib0700
My kernel patch ( other scripts to patch the Fedora 8 src rpm's
available on request)
----------------
--- a/drivers/media/dvb/dvb-usb/dib0700_devices.c 2008-02-13
10:05:13.000000000 +1100
+++ b/drivers/media/dvb/dvb-usb/dib0700_devices.c 2008-02-13
10:22:16.000000000 +1100
@@ -280,6 +280,7 @@ struct usb_device_id dib0700_usb_id_tabl
{ USB_DEVICE(USB_VID_LEADTEK,
USB_PID_WINFAST_DTV_DONGLE_STK7700P) },
{ USB_DEVICE(USB_VID_HAUPPAUGE,
USB_PID_HAUPPAUGE_NOVA_T_STICK_2) },
{ USB_DEVICE(USB_VID_AVERMEDIA,
USB_PID_AVERMEDIA_VOLAR_2) },
+ { USB_DEVICE(USB_VID_LEADTEK,
USB_PID_WINFAST_DTV_DONGLE_STK7700P_B) },
{ } /* Terminating entry */
};
MODULE_DEVICE_TABLE(usb, dib0700_usb_id_table);
@@ -321,7 +322,7 @@ struct dvb_usb_device_properties dib0700
},
},
- .num_device_descs = 6,
+ .num_device_descs = 7,
.devices = {
{ "DiBcom STK7700P reference design",
{ &dib0700_usb_id_table[0],
&dib0700_usb_id_table[1] },
@@ -346,6 +347,10 @@ struct dvb_usb_device_properties dib0700
{ "Leadtek Winfast DTV Dongle (STK7700P
based)",
{ &dib0700_usb_id_table[8], NULL },
{ NULL },
+ },
+ { "Leadtek Winfast DTV Dongle B (STK7700P
based)",
+ { &dib0700_usb_id_table[11], NULL },
+ { NULL },
}
}
}, { DIB0700_DEFAULT_DEVICE_PROPERTIES,
--- a/drivers/media/dvb/dvb-usb/dvb-usb-ids.h 2008-02-13
10:05:13.000000000 +1100
+++ b/drivers/media/dvb/dvb-usb/dvb-usb-ids.h 2008-02-13
10:18:00.000000000 +1100
@@ -148,6 +148,7 @@
#define USB_PID_WINFAST_DTV_DONGLE_COLD 0x6025
#define USB_PID_WINFAST_DTV_DONGLE_WARM 0x6026
#define USB_PID_WINFAST_DTV_DONGLE_STK7700P 0x6f00
+#define USB_PID_WINFAST_DTV_DONGLE_STK7700P_B 0x6f01
#define USB_PID_GENPIX_8PSK_COLD 0x0200
#define USB_PID_GENPIX_8PSK_WARM 0x0201
#define USB_PID_SIGMATEK_DVB_110 0x6610
_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
----- Original Message -----
From: "Antti Palosaari" <crope@xxxxxx>
To: "ptay1685" <ptay1685@xxxxxxxxxxxxxx>
Cc: <linux-dvb@xxxxxxxxxxx>
Sent: Monday, March 24, 2008 9:43 AM
Subject: Re: leadtek dtv dongle
ptay1685 wrote:
Any news about the new version of the dtv dongle? Still does not work
with the latest v4l sources. Anyone know whats happening?
Many thanks,
Phil T.
Can you say what is usb-id of your device? Also lsusb -v could be nice
to see.
regards
Antti
--
http://palosaari.fi/
_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
|
