DM04 USB DVB-S TUNER
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
dmesg message:
[ 1930.244086] usb 1-8: new high speed USB device using ehci_hcd and address 4 [ 1930.377256] usb 1-8: config 1 interface 0 altsetting 1 bulk endpoint 0x81 has invalid maxpacket 64 [ 1930.377270] usb 1-8: config 1 interface 0 altsetting 1 bulk endpoint 0x1 has invalid maxpacket 64 [ 1930.377280] usb 1-8: config 1 interface 0 altsetting 1 bulk endpoint 0x2 has invalid maxpacket 64 [ 1930.377291] usb 1-8: config 1 interface 0 altsetting 1 bulk endpoint
0x8A has invalid maxpacket 64
lsmod |grep dm04 message:
dvb_usb_lmedm04 19257 0 dvb_usb 18412 1 dvb_usb_lmedm04 dvb_core 87702 2 dvb_usb_lmedm04,dvb_usb rc_core 17755 2 dvb_usb_lmedm04,dvb_usb
please help me, thanks...
A message that is not in the archive (sent off-list or not yet received): 1307283393.22968.12.camel@localhost
05-06-2011 17:16, Malcolm Priestley yazmış:
Quoted 14 lines · Mehmet Altan Pire
Quoted 9 lines
Hi,
I have "DM04 USB DVBS TUNER", using ubuntu with v4l media-builddrivers/modulesbut device doesn't working (unknown device).lsusb message:
ID 3344:22f0under of the box:
DM04P2011050176Have you driver for windows to send me?
I need to verify what tuner is fitted to it.
Quoted 9 lines
The driver file is usually located in windows/system32/drivers
It is usually called something like US2A0D.sys
They may be fitting a new type of tuner that is not supported or it doesn't have the LME2510 chip.
tvboxspy
Yes, i have windows xp driver, name is "US2B0D.sys" I sending it, attached in this mail. Thanks.
A message that is not in the archive (sent off-list or not yet received): 1307306576.2064.13.camel@localhost
Quoted 23 lines · Malcolm Priestley
Quoted 6 lines · Mehmet Altan Pire
05-06-2011 17:16, Malcolm Priestley yazmış:
Quoted 5 lines · Mehmet Altan Pire
Quoted 4 lines
Hi,
I have "DM04 USB DVBS TUNER", using ubuntu with v4l media-builddrivers/modulesbut device doesn't working (unknown device).Quoted 8 lines
Quoted 6 lines
Quoted 5 lines
lsusb message:
ID 3344:22f0under of the box:
DM04P2011050176Yes, i have windows xp driver, name is "US2B0D.sys" I sending it, attached in this mail. Thanks.
Here is a modified
lmedm04.candlme2510b_fw.shusing the US2B0D.sysTested 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.
Quoted 7 lines
I assume you are using the lastest
media_buildto update driver then over writelmedm04.cfound in;
media_build/linux/drivers/media/dvb/dvb-usbIf 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
06-06-2011 00:47, Malcolm Priestley yazmış:
Quoted 34 lines · Malcolm Priestley
Quoted 21 lines · Mehmet Altan Pire
Quoted 6 lines
05-06-2011 17:16, Malcolm Priestley yazmış:
Quoted 5 lines · Mehmet Altan Pire
Quoted 4 lines
Hi,
I have "DM04 USB DVBS TUNER", using ubuntu with v4l media-builddrivers/modulesbut device doesn't working (unknown device).Quoted 7 lines
Quoted 5 lines
Quoted 5 lines
lsusb message:
ID 3344:22f0under of the box:
DM04P2011050176Yes, i have windows xp driver, name is "US2B0D.sys" I sending it, attached in this mail. Thanks.
Here is a modified
lmedm04.candlme2510b_fw.shusing the US2B0D.sysTested 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.
Quoted 7 lines
I assume you are using the lastest
media_buildto update driver then over writelmedm04.cfound in;
media_build/linux/drivers/media/dvb/dvb-usbIf 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.
Quoted 9 lines
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...
Quoted 29 lines · Mehmet Altan Pire
06-06-2011 00:47, Malcolm Priestley yazmış:
Quoted 11 lines · Malcolm Priestley
Quoted 10 lines · Mehmet Altan Pire
Quoted 9 lines
05-06-2011 17:16, Malcolm Priestley yazmış:
Quoted 8 lines · Mehmet Altan Pire
Quoted 7 lines
Hi,
I have "DM04 USB DVBS TUNER", using ubuntu with v4l media-builddrivers/modulesbut device doesn't working (unknown device).lsusb message:
ID 3344:22f0Quoted 6 lines
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
Quoted 2 lines
under of the box:
DM04P2011050176Yes, i have windows xp driver, name is "US2B0D.sys" I sending it, attached in this mail. Thanks.
Here is a modified
lmedm04.candlme2510b_fw.shusing the US2B0D.systo modify the interrupt return.
Quoted 3 lines
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 newlmedm04.candlme2510b_fw.shthan make, make install, and restart.
Quoted 3 lines
lsusb says:
Bus 001 Device 008: ID 3344:1120 (changes 22f0 to 1120) dmesg says:
Yes this should happen. The firmware will reboot with the correct id.
Quoted 5 lines
[ 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 - ResettingDevice
It found a LG tuner
remove the dvb-usb-lme2510c-lg.fw firmware file.
rename dvb-usb-lme2510c-s7395.fw to dvb-usb-lme2510c-lg.fw.
Quoted 12 lines
[ 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
Quoted 4 lines
count: 15).
My device different or chip is damaged? Label, box and driver cd title writes "DM04P". DM04 and DM04P different devices?
I think the id of the chip is faulty or default.
I will test the firmware with LG tuner later.
tvboxspy
Quoted 36 lines · Malcolm Priestley
Quoted 29 lines · Mehmet Altan Pire
06-06-2011 00:47, Malcolm Priestley yazmış:
Quoted 11 lines · Malcolm Priestley
Quoted 10 lines · Mehmet Altan Pire
Quoted 9 lines
05-06-2011 17:16, Malcolm Priestley yazmış:
Quoted 8 lines · Mehmet Altan Pire
Quoted 7 lines
Hi,
I have "DM04 USB DVBS TUNER", using ubuntu with v4l media-builddrivers/modulesbut device doesn't working (unknown device).lsusb message:
ID 3344:22f0Quoted 6 lines
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
Quoted 2 lines
under of the box:
DM04P2011050176Yes, i have windows xp driver, name is "US2B0D.sys" I sending it, attached in this mail. Thanks.
Here is a modified
lmedm04.candlme2510b_fw.shusing the US2B0D.systo modify the interrupt return.
Quoted 3 lines
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 newlmedm04.candlme2510b_fw.shthan make, make install, and restart.Quoted 3 lines
lsusb says:
Bus 001 Device 008: ID 3344:1120 (changes 22f0 to 1120) dmesg says:Yes this should happen. The firmware will reboot with the correct id.
Quoted 6 lines
Quoted 2 lines
My device different or chip is damaged? Label, box and driver cd title writes "DM04P". DM04 and DM04P different devices?
I think the id of the chip is faulty or default.
I will test the firmware with LG tuner later.
It is not the LG, s7395 or S0194 tuner.
So the id is intentional.
How does it identify itself in windows?
tvboxspy
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 51 lines · Mehmet Altan Pire
07-06-2011 22:34, Malcolm Priestley yazmış:
Quoted 37 lines · Malcolm Priestley
Quoted 30 lines · Mehmet Altan Pire
Quoted 26 lines
06-06-2011 00:47, Malcolm Priestley yazmış:
Quoted 11 lines · Malcolm Priestley
Quoted 10 lines · Mehmet Altan Pire
Quoted 9 lines
05-06-2011 17:16, Malcolm Priestley yazmış:
Quoted 8 lines · Mehmet Altan Pire
Quoted 7 lines
Hi,
I have "DM04 USB DVBS TUNER", using ubuntu with v4l media-builddrivers/modulesbut device doesn't working (unknown device).lsusb message:
ID 3344:22f0Quoted 6 lines
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
Quoted 2 lines
under of the box:
DM04P2011050176Yes, i have windows xp driver, name is "US2B0D.sys" I sending it, attached in this mail. Thanks.
Here is a modified
lmedm04.candlme2510b_fw.shusing the US2B0D.systo modify the interrupt return.
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 newlmedm04.candlme2510b_fw.shthan make, make install, and restart.Quoted 3 lines
lsusb says:
Bus 001 Device 008: ID 3344:1120 (changes 22f0 to 1120) dmesg says:Quoted 6 lines
Yes this should happen. The firmware will reboot with the correct id.
Quoted 2 lines
My device different or chip is damaged? Label, box and driver cd title writes "DM04P". DM04 and DM04P different devices?
I think the id of the chip is faulty or default.
I will test the firmware with LG tuner later.
Quoted 9 lines
It is not the LG, s7395 or S0194 tuner.
So the id is intentional.
How does it identify itself in windows?
tvboxspy
3. Tests
:WinXP Test:
Quoted 7 lines
I'm sure it worked on WinXP now. Tested with ProgDVB application. Signal, channel search and watching tv as succesfully.
My Device working without problems on WinXP and it's not damaged. When device running on stream, green led is active, if not running, green led is passive (red led is power led and it's always active). Driver Info:LME_PCTV_DVBS_RS2000"VID3344 PID22F0" 22f0 this number correct...
I need to find out what exactly the RS2000 tuner is. So currently the linux driver is not supported with your device.
tvboxspy
Quoted 60 lines · Malcolm Priestley
Quoted 51 lines · Mehmet Altan Pire
07-06-2011 22:34, Malcolm Priestley yazmış:
Quoted 37 lines · Malcolm Priestley
Quoted 30 lines · Mehmet Altan Pire
Quoted 26 lines
06-06-2011 00:47, Malcolm Priestley yazmış:
Quoted 11 lines · Malcolm Priestley
Quoted 10 lines · Mehmet Altan Pire
Quoted 9 lines
05-06-2011 17:16, Malcolm Priestley yazmış:
Quoted 8 lines · Mehmet Altan Pire
Quoted 7 lines
Hi,
I have "DM04 USB DVBS TUNER", using ubuntu with v4l media-builddrivers/modulesbut device doesn't working (unknown device).lsusb message:
ID 3344:22f0Quoted 6 lines
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
Quoted 2 lines
under of the box:
DM04P2011050176Yes, i have windows xp driver, name is "US2B0D.sys" I sending it, attached in this mail. Thanks.
Here is a modified
lmedm04.candlme2510b_fw.shusing the US2B0D.systo modify the interrupt return.
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 newlmedm04.candlme2510b_fw.shthan make, make install, and restart.Quoted 3 lines
lsusb says:
Bus 001 Device 008: ID 3344:1120 (changes 22f0 to 1120) dmesg says:Quoted 6 lines
Yes this should happen. The firmware will reboot with the correct id.
Quoted 2 lines
My device different or chip is damaged? Label, box and driver cd title writes "DM04P". DM04 and DM04P different devices?
I think the id of the chip is faulty or default.
I will test the firmware with LG tuner later.
Quoted 9 lines
It is not the LG, s7395 or S0194 tuner.
So the id is intentional.
How does it identify itself in windows?
tvboxspy
3. Tests
:WinXP Test:
Quoted 7 lines
I'm sure it worked on WinXP now. Tested with ProgDVB application. Signal, channel search and watching tv as succesfully.
My Device working without problems on WinXP and it's not damaged. When device running on stream, green led is active, if not running, green led is passive (red led is power led and it's always active). Driver Info:LME_PCTV_DVBS_RS2000"VID3344 PID22F0" 22f0 this number correct...
Quoted 2 lines
I need to find out what exactly the RS2000 tuner is. So currently the linux driver is not supported with your device.
A little update...
I now have one of these devices. The chip is actually a M8BRS2000 which is a combi frontend/tuner device.
The ID is confirmed as 3344:22f0, it appears to be patched by the Windows Driver as 3344:1120 devices try wrongly to use the RS2000 driver.
There is no Linux frontend driver for this device. I will start to write one shortly, so support could be several months away.
Regards
Malcolm
Quoted 69 lines · Malcolm Priestley
Quoted 60 lines · Malcolm Priestley
Quoted 51 lines · Mehmet Altan Pire
07-06-2011 22:34, Malcolm Priestley yazmış:
Quoted 37 lines · Malcolm Priestley
Quoted 30 lines · Mehmet Altan Pire
Quoted 26 lines
06-06-2011 00:47, Malcolm Priestley yazmış:
Quoted 11 lines · Malcolm Priestley
Quoted 10 lines · Mehmet Altan Pire
Quoted 9 lines
05-06-2011 17:16, Malcolm Priestley yazmış:
Quoted 8 lines · Mehmet Altan Pire
Quoted 7 lines
Hi,
I have "DM04 USB DVBS TUNER", using ubuntu with v4l media-builddrivers/modulesbut device doesn't working (unknown device).lsusb message:
ID 3344:22f0Quoted 6 lines
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
Quoted 2 lines
under of the box:
DM04P2011050176Yes, i have windows xp driver, name is "US2B0D.sys" I sending it, attached in this mail. Thanks.
Here is a modified
lmedm04.candlme2510b_fw.shusing the US2B0D.systo modify the interrupt return.
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 newlmedm04.candlme2510b_fw.shthan make, make install, and restart.Quoted 3 lines
lsusb says:
Bus 001 Device 008: ID 3344:1120 (changes 22f0 to 1120) dmesg says:Quoted 6 lines
Yes this should happen. The firmware will reboot with the correct id.
Quoted 2 lines
My device different or chip is damaged? Label, box and driver cd title writes "DM04P". DM04 and DM04P different devices?
I think the id of the chip is faulty or default.
I will test the firmware with LG tuner later.
Quoted 9 lines
It is not the LG, s7395 or S0194 tuner.
So the id is intentional.
How does it identify itself in windows?
tvboxspy
3. Tests
:WinXP Test:
Quoted 7 lines
I'm sure it worked on WinXP now. Tested with ProgDVB application. Signal, channel search and watching tv as succesfully.
My Device working without problems on WinXP and it's not damaged. When device running on stream, green led is active, if not running, green led is passive (red led is power led and it's always active). Driver Info:LME_PCTV_DVBS_RS2000"VID3344 PID22F0" 22f0 this number correct...Quoted 2 lines
I need to find out what exactly the RS2000 tuner is. So currently the linux driver is not supported with your device.
A little update...
I now have one of these devices. The chip is actually a M8BRS2000 which is a combi frontend/tuner device.
Quoted 7 lines
The ID is confirmed as 3344:22f0, it appears to be patched by the Windows Driver as 3344:1120 devices try wrongly to use the RS2000 driver.
There is no Linux frontend driver for this device. I will start to write one shortly, so support could be several months away.
I have written the M8BRS2000 frontend, which has been on test for the last two weeks.
Unfortunately, on Friday my device has partially failed, in that the m8brs2000 chip starts to fail with prolonged use.
It seems to be an heat issue as cooling the device restores normal operation. I will do some more tests in a lab this week for dry-joints.
Have you or anyone else noticed any similar problems running the device under Windows?
This means the device driver for Linux is back on Alpha and cannot be released.
Regards
Malcolm