Siano SMS1140 DVB Receiver on Debian 5.0 (Lenny)

Siano SMS1140 DVB Receiver on Debian 5.0 (Lenny)

[jamenson]

Hi everyone.

I'm sorry if my question is a newbie question. I have a DVB receiver (Siano SMS1140).


<lsusb -v -d 187f:0201 >> lsusb.log> output:

Bus 002 Device 003: ID 187f:0201 Siano Mobile Silicon Nova B

Device Descriptor:

bLength 18

bDescriptorType 1

bcdUSB 2.00

bDeviceClass 0 (Defined at Interface level)

bDeviceSubClass 0

bDeviceProtocol 0

bMaxPacketSize0 64

idVendor 0x187f Siano Mobile Silicon

idProduct 0x0201 Nova B

bcdDevice 0.01

iManufacturer 1 Test EEPROM Manufacturer String

iProduct 2 Test EEPROM Product String

iSerial 0

bNumConfigurations 1

Configuration Descriptor:

bLength 9

bDescriptorType 2

wTotalLength 32

bNumInterfaces 1

bConfigurationValue 1

iConfiguration 0

bmAttributes 0x80

(Bus Powered)

MaxPower 100mA

Interface Descriptor:

bLength 9

bDescriptorType 4

bInterfaceNumber 0

bAlternateSetting 0

bNumEndpoints 2

bInterfaceClass 255 Vendor Specific Class

bInterfaceSubClass 255 Vendor Specific Subclass

bInterfaceProtocol 255 Vendor Specific Protocol

iInterface 0

Endpoint Descriptor:

bLength 7

bDescriptorType 5

bEndpointAddress 0x81 EP 1 IN

bmAttributes 2

Transfer Type Bulk

Synch Type None

Usage Type Data

wMaxPacketSize 0x0200 1x 512 bytes

bInterval 0

Endpoint Descriptor:

bLength 7

bDescriptorType 5

bEndpointAddress 0x02 EP 2 OUT

bmAttributes 2

Transfer Type Bulk

Synch Type None

Usage Type Data

wMaxPacketSize 0x0200 1x 512 bytes

bInterval 0

Device Qualifier (for other device speed):

bLength 10

bDescriptorType 6

bcdUSB 2.00

bDeviceClass 255 Vendor Specific Class

bDeviceSubClass 255 Vendor Specific Subclass

bDeviceProtocol 255 Vendor Specific Protocol

bMaxPacketSize0 64

bNumConfigurations 1

Device Status: 0x0000

(Bus Powered)

__________________________________________________________________________________________________________________

syslogd output:

Jan 21 01:30:34 comp01 acpid: client connected from 3409[0:0]

Jan 21 02:00:09 comp01 kernel: [ 7588.475485] usb 2-1.2: new high speed USB device using ehci_hcd and address 3

Jan 21 02:00:10 comp01 kernel: [ 7588.569182] usb 2-1.2: configuration #1 chosen from 1 choice

Jan 21 02:00:10 comp01 kernel: [ 7588.569182] usb 2-1.2: New USB device found, idVendor=187f, idProduct=0201

Jan 21 02:00:10 comp01 kernel: [ 7588.569182] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0

Jan 21 02:00:10 comp01 kernel: [ 7588.569182] usb 2-1.2: Product: Test EEPROM Product String

Jan 21 02:00:10 comp01 kernel: [ 7588.569182] usb 2-1.2: Manufacturer: Test EEPROM Manufacturer String

Jan 21 02:00:10 comp01 NetworkManager: <debug> [1295586010.065552] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_187f_201_noserial').

Jan 21 02:00:10 comp01 NetworkManager: <debug> [1295586010.113148] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_187f_201_noserial_if0').

Jan 21 02:00:10 comp01 NetworkManager: <debug> [1295586010.123770] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_187f_201_noserial_usbraw').

_________________________________________________________________________________________________________________________

dmesg output:



[ 343.193191] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0004

[ 343.193474] hub 2-1:1.0: port 2, status 0101, change 0001, 12 Mb/s

[ 343.297207] hub 2-1:1.0: debounce: port 2: total 100ms stable 100ms status 0x101

[ 343.308191] hub 2-1:1.0: port 2 not reset yet, waiting 10ms

[ 343.369999] usb 2-1.2: new high speed USB device using ehci_hcd and address 3

[ 343.380964] hub 2-1:1.0: port 2 not reset yet, waiting 10ms

[ 343.455532] usb 2-1.2: default language 0x0409

[ 343.456027] usb 2-1.2: udev 3, busnum 2, minor = 130

[ 343.456031] usb 2-1.2: New USB device found, idVendor=187f, idProduct=0201

[ 343.456035] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[ 343.456039] usb 2-1.2: Product: Test EEPROM Product String

[ 343.456042] usb 2-1.2: Manufacturer: Test EEPROM Manufacturer String

[ 343.456141] usb 2-1.2: usb_probe_device

[ 343.456146] usb 2-1.2: configuration #1 chosen from 1 choice

[ 343.456330] usb 2-1.2: adding 2-1.2:1.0 (config #1, interface 0)

[ 343.456456] drivers/usb/core/inode.c: creating file '003'

[ 343.578653] smsusb 2-1.2:1.0: usb_probe_interface

[ 343.578656] smsusb 2-1.2:1.0: usb_probe_interface - got id

[ 344.177738] smscore_set_device_mode: firmware download success: dvb_nova_12mhz_b0.inp

[ 344.178232] usbcore: registered new interface driver smsusb

_______________________________________________________________________________________________________________________

As you can see, driver is not registering the devices. So I did registration:

<ls -l /dev/bus/usb/002/003> output:

crw-rw-r-- 1 root root 189, 130 Fev 4 05:38 /dev/bus/usb/002/003

<cat /var/log/syslog | grep '04:30:40' | grep becomes> output:

Feb 4 04:30:40 comp01 udevd-event[2870]: udev_rules_get_name: rule applied, '2-1.2' becomes 'bus/usb/002/003'

Feb 4 04:30:40 comp01 udevd-event[2873]: udev_rules_get_name: rule applied, 'usbdev2.3' becomes 'bus/usb/002/003'

 

<ls -l /dev/dvb/adapter0/> output:

total 0

crwxrw-rw- 1 root root 189, 130 Fev 4 05:35 audio0

crwxrw-rw- 1 root root 189, 130 Fev 4 05:35 ca0

crwxrw-rw- 1 root root 189, 130 Fev 4 05:35 demux0

crwxrw-rw- 1 root root 189, 130 Fev 4 05:35 dvr0

crwxrw-rw- 1 root root 189, 130 Fev 4 05:35 frontend0

crwxrw-rw- 1 root root 189, 130 Fev 4 05:35 net0

crwxrw-rw- 1 root root 189, 130 Fev 4 05:35 osd0

crwxrw-rw- 1 root root 189, 130 Fev 4 05:35 video0


Unfortunatly <dvbtune -i> output is:

<transponder type="T" freq="0">

PAT - DMX_SET_FILTER:: Inappropriate ioctl for device

SDT - DMX_SET_FILTER:: Inappropriate ioctl for device

</transponder>

 

<scan -c> output is:

using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'

main:2287: FATAL: FE_GET_INFO failed: 1 Operation not permitted

 

<w_scan -c BR -a 0> output is:

w_scan version 20100316 (compiled for DVB API 5.1)

using settings for BRAZIL

Country identifier BR not defined. Using defaults.

frontend_type DVB-T, channellist 4

output format vdr-1.6

-_-_-_-_ Getting frontend capabilities-_-_-_-_

main:2937: FATAL: FE_GET_INFO failed: 25 Inappropriate ioctl for device

________________________________________________________________________________________________________________________

I'm using kernel 2.6.37 (downloaded from kernel.org) with Debian GNU/Linux 5.0 (Lenny).

What should I do to solve this?

Thank you.

Re: Siano SMS1140 DVB Receiver on Debian 5.0 (Lenny)

[Richard]

On Fri, Feb 11, 2011 at 12:39:30PM -0200, jamenson@bol.com.br wrote:


> As you can see, driver is not registering the devices. So I did registration:

just curious, how did you do that?

> 
> I'm using kernel 2.6.37 (downloaded from kernel.org) with Debian GNU/Linux 5.0 (Lenny).

try different kernel versions, also sms and other modules support debug options - those
are what I came across:

#options smsdvb debug=3
#options smsusb debug=3
#options dvb_frontend debug=1
#options dvb_frontend dvbdev_debug=1
#options smsmdtv debug=3
#options dvb_core debug=1
#options dvb_core dvbdev_debug=1

Richard

---
Name and OpenPGP keys available from pgp key servers

Re: Siano SMS1140 DVB Receiver on Debian 5.0 (Lenny)

[Mauro Carvalho Chehab]

Em 11-02-2011 12:39, jamenson@bol.com.br escreveu:
> Hi everyone.
> 
> I'm sorry if my question is a newbie question. I have a DVB receiver (Siano SMS1140).
<snip/>
> using settings for BRAZIL

I'm assuming that what you're trying to do is to use it for ISDB-T, right?

You may find some useful info (in Portuguese) at:
http://br-linux.org/2010/tv-digital-brasileira-no-linux-mais-drivers-experimentais-disponiveis/

The tree indicated there is outdated (it was a test tree I've created some time ago). The latest
drivers are available at the main devel tree. You may use the media_build tree to download and
compile with your kernel version:
	http://git.linuxtv.org/media_build.git

Also, AFAIK, vdr doesn't work with ISDB-T. The only application that I know for sure that works
with h.264/aac isdb-t decoding is vlc.

Cheers,
Mauro.

Re: Siano SMS1140 DVB Receiver on Debian 5.0 (Lenny)

[Mauro Carvalho Chehab]

Hi Jamenson,

Em 21-02-2011 16:51, Jamenson Ferreira Espindula de Almeida Melo escreveu:
> 
> Hi, Mauro! Thank you for your replying.
> 
> I have had some success. I just reconfigured the kernel 2.6.37 and recompiled it. I figured out two things.
> First: when I compiled the Siano driver as a module, smsmdtv.ko is loaded when I attach the receiver but no adapter directory, 
> no dvr, no demux and no frontend are created in /dev directory. Second: I compiled the Siano driver into the kernel and bingo:
> when I attach the receiver, frontend0, dvr0 and demux0 are created in /dev/dvb/adapter0 directory. No problem. Real problem is:
> scan, w_scan and dvbtune doesn't find any signal to scan, say "tunning failed". I figured out that receiver default mode is 
> setup to DVB-T (mode 4 in smscoreapi.c) and because of that dvb_nova_12mhz_b0.inp is required. Setting default mode to 6 in 
> smscoreapi.c makes isdbt_nova_12mhz_b0.inp be required instead and it does make me sense to be the correct driver considering ISDB-T
> standard in Brazil. Reading Siano's documentation I realized that ISDB-T standard only runs with SMS Host Library, that is a 
> proprietary subsystem of Siano Mobile Silicon and, actually, I am thinking receiver will only run if I use such a library.
> 
> Any more help?

Yes, you need to force it to mode 6, if you want to use it with ISDB-T.

It works fine with ISDB-T, provided that you use a good antenna. Here, I need
to use a "Sagna Baby" antenna, that gives me an additional gain of
18 dB, and put it on my window. Notice that sms1140 only works with 1seg/3seg.

Abraços,
Mauro