From: Mehmet Altan Pire <baybesteci@gmail.com>
To: Malcolm Priestley <tvboxspy@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: DM04 USB DVB-S TUNER
Date: Tue, 07 Jun 2011 02:28:14 +0300 [thread overview]
Message-ID: <4DED628E.9070502@gmail.com> (raw)
In-Reply-To: <1307310455.2547.9.camel@localhost>
06-06-2011 00:47, Malcolm Priestley yazmış:
> On Sun, 2011-06-05 at 21:42 +0100, Malcolm Priestley wrote:
>> On Sun, 2011-06-05 at 19:34 +0300, Mehmet Altan Pire wrote:
>>> 05-06-2011 17:16, Malcolm Priestley yazmış:
>>>> On Sun, 2011-06-05 at 03:35 +0300, Mehmet Altan Pire wrote:
>>>>> Hi,
>>>>> I have "DM04 USB DVBS TUNER", using ubuntu with v4l media-build
>>>>> drivers/modules but device doesn't working (unknown device).
>>>>>
>>>>> lsusb message:
>>>>> ID 3344:22f0
>>>>>
>>>>> under of the box:
>>>>> DM04P2011050176
>>> Yes, i have windows xp driver, name is "US2B0D.sys" I sending it,
>>> attached in this mail. Thanks.
>> Here is a modified lmedm04.c and lme2510b_fw.sh using the US2B0D.sys
>>
>> Tested here, it appears to work with the sharp7395 tuner.
>>
>> Are you sure it works under Windows? I can't find your ID in the
>> US2B0D.sys file. It may be a blank lme2510c chip.
>>
>> I assume you are using the lastest media_build to update driver then
>> over write lmedm04.c
>>
>> found in;
>> media_build/linux/drivers/media/dvb/dvb-usb
>>
>> If already build, just a make and sudo make install is required.
> I have done some further tests with this firmware and it does not return
> the correct signal lock data. By default the signal lock returns the
> last good lock and updated by interrupt. This just means when lock is
> lost the driver still returns lock.
>
> I will need to modify the interrupt return.
>
> However, it may be a different tuner.
>
> tvboxspy
>
>
>
>
Ok, i tested it. Device recognized on WinXP with original driver, but tv
application says "no lock".
I'm not sure it worked on WinXP but driver cd is original and
succesfully loaded and recognized.
Again tested on ubuntu with new lmedm04.c and lme2510b_fw.sh than make,
make install, and restart.
lsusb says:
Bus 001 Device 008: ID 3344:1120 (changes 22f0 to 1120)
dmesg says:
[ 1280.968068] usb 1-2: new high speed USB device using ehci_hcd and
address 7
[ 1281.101483] usb 1-2: config 1 interface 0 altsetting 1 bulk endpoint
0x81 has invalid maxpacket 64
[ 1281.101497] usb 1-2: config 1 interface 0 altsetting 1 bulk endpoint
0x1 has invalid maxpacket 64
[ 1281.101507] usb 1-2: config 1 interface 0 altsetting 1 bulk endpoint
0x2 has invalid maxpacket 64
[ 1281.101518] usb 1-2: config 1 interface 0 altsetting 1 bulk endpoint
0x8A has invalid maxpacket 64
[ 1281.102958] LME2510(C): Firmware Status: 6 (44)
[ 1281.107948] LME2510(C): FRM Loading dvb-usb-lme2510c-lg.fw file
[ 1281.107958] LME2510(C): FRM Starting Firmware Download
[ 1283.548064] LME2510(C): FRM Firmware Download Completed - Resetting
Device
[ 1283.548221] usb 1-2: USB disconnect, address 7
[ 1283.792067] usb 1-2: new high speed USB device using ehci_hcd and
address 8
[ 1283.928354] usb 1-2: config 1 interface 0 altsetting 1 bulk endpoint
0x81 has invalid maxpacket 64
[ 1283.928360] usb 1-2: config 1 interface 0 altsetting 1 bulk endpoint
0x1 has invalid maxpacket 64
[ 1283.928364] usb 1-2: config 1 interface 0 altsetting 1 bulk endpoint
0x2 has invalid maxpacket 64
[ 1283.929850] LME2510(C): Firmware Status: 6 (47)
[ 1283.929855] dvb-usb: found a 'DM04_LME2510C_DVB-S' in warm state.
[ 1283.954607] dvb-usb: will use the device's hardware PID filter (table
count: 15).
[ 1283.954866] DVB: registering new adapter (DM04_LME2510C_DVB-S)
[ 1284.461395] LME2510(C): DM04 Not Supported
[ 1284.461410] dvb-usb: no frontend was attached by 'DM04_LME2510C_DVB-S'
[ 1284.461441] Registered IR keymap rc-lme2510
[ 1284.461717] input: IR-receiver inside an USB DVB receiver as
/devices/pci0000:00/0000:00:0b.1/usb1/1-2/rc/rc2/input10
[ 1284.461913] rc2: IR-receiver inside an USB DVB receiver as
/devices/pci0000:00/0000:00:0b.1/usb1/1-2/rc/rc2
[ 1284.481096] dvb-usb: DM04_LME2510C_DVB-S successfully initialized and
connected.
[ 1284.481107] LME2510(C): DEV registering device driver
me-tv and gnome-dvb-setup says: There are no DVB devices available...
My device different or chip is damaged? Label, box and driver cd title
writes "DM04P". DM04 and DM04P different devices?
Thanks again...
next prev parent reply other threads:[~2011-06-06 23:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-05 0:35 DM04 USB DVB-S TUNER Mehmet Altan Pire
[not found] ` <1307283393.22968.12.camel@localhost>
2011-06-05 16:34 ` Mehmet Altan Pire
[not found] ` <1307306576.2064.13.camel@localhost>
2011-06-05 21:47 ` Malcolm Priestley
2011-06-06 23:28 ` Mehmet Altan Pire [this message]
2011-06-07 5:31 ` Malcolm Priestley
2011-06-07 19:34 ` Malcolm Priestley
[not found] ` <4DEF5A9F.8000200@gmail.com>
2011-06-08 15:20 ` Malcolm Priestley
2011-06-25 21:10 ` Malcolm Priestley
2011-09-04 19:33 ` Malcolm Priestley
-- strict thread matches above, loose matches on Subject: below --
2012-01-17 18:46 Dream HTPC
2012-01-17 20:24 ` Malcolm Priestley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DED628E.9070502@gmail.com \
--to=baybesteci@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=tvboxspy@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox