Does not recognize Mygica T119 in SOLO2 with BH 3.0.3

C

CoPtOs®

Vu+ Newbie
Good morning forum !!!!.

As I indicated in the title, I have a problem with the usb migyca.

The case is that in the first installation that made with the BH 3.0.3 image, It was recognized and even installed the DVT channels and these were seen.

The case is that, by mistake, I went back to searching for the DVT channels and instead of setting the DVT in DVT-T, set it to DVT-C, and of course, stop watching the channels.

The case is that I reloaded the image BH 3.0.3, by flashing, and tried again to recognize the usb tdt (a new Migyca t119) and nothing, do not recognize it.

The case that in telnet, I put the following command:
dmesg

And as a result he gives me;
Usb 1-2: usb 3 "not enabled" or something similar....

I do not know what else to do, I do not know how to enable the port. I am considering uploading the official VUPLUS image and re trying to upload the BH. I am worried that the USB port has loaded it into the vuplus, or, for some reason, I have disabled it (it happens in the two rear USB ports of SOLO2).

Any advice or help ??

Thanks!!!!
 
M

Mick12334

Moderator
Perhaps the problem is with your Mygica T119, why not connect it to your PC and use the tools, from the Mygica support site to load the software, or drivers, and see if it then works.
The fact that it was working, before you changed the settings, suggests that it does work with the Solo2, and Blackhole, but you might need to update the Blackhole drivers.
First try doing a reset, on your Mygica T119, using your PC, and read the online manual, from the Mygica site:
Code: 
http://www.mygica.com/html/Support/
 
C

CoPtOs®

Vu+ Newbie
Nothing, I'm still the same. I reset via PC and nothing. The drivers are siano and apparently installed, but still can not be installed automatically. Any additional help? Thank you

root@vusolo2:~# opkg list-installed | grep smsdvb
media-tree-module-smsdvb - 0.0+git20140924-r0.11
root@vusolo2:~# lsusb
Bus 002 Device 003: ID 187f:0202
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0002
Bus 003 Device 001: ID 1d6b:0002
Bus 004 Device 001: ID 1d6b:0002
Bus 005 Device 001: ID 1d6b:0001
Bus 006 Device 001: ID 1d6b:0001
Bus 007 Device 001: ID 1d6b:0001
Bus 008 Device 001: ID 1d6b:0001
 
C

CoPtOs®

Vu+ Newbie
Thank you for your support;

I am trying to access rc.sh using FILEZILLA and NOTEPAD to enter the file to add what you tell me, but it does not read correctly what appears in the rc.sh file. Could you help me a little more in detail how to perform this operation?

Thank you very much in advance
 
C

CoPtOs®

Vu+ Newbie
Sorry, I'm already with notepad:

Now inside the file and at the end of everything, I put the three lines and then restart enigma2?

Thank you
 
S

superglud

BH Lover
CoPtOs® said:
Sorry, I'm already with notepad:

Now inside the file and at the end of everything, I put the three lines and then restart enigma2?

Thank you
Click to expand...

Or even more easy .. use DCC1.50 (Dreambox Control Center v1.50)

and remember always copy(backup) the org file before modify'ing anything

New DCC-E2-1.50

run DCC and setup and connect to box
press the "ftp"-button and navigate to the file and right-click and choose "Edit"

best regards
 
C

CoPtOs®

Vu+ Newbie
Hi:

Thank you for you support;

After performing the steps and launching DMESG, I receive this:

usb 2-1: new high-speed USB device number 2 using ehci-brcm
usb 2-1: Direct firmware load failed with error -2
usb 2-1: Falling back to user helper
smscore_load_firmware_from_file: line: 1168: failed to open firmware file "dvb_nova_12mhz_b0.inp"
smscore_set_device_mode: line: 1417: return error code -2.
smsusb_init_device: line: 436: smscore_start_device(...) failed
smsusb_onresponse: line: 143: error, urb status -2, 0 bytes
smsusb_onresponse: line: 143: error, urb status -2, 0 bytes
smsusb_onresponse: line: 143: error, urb status -2, 0 bytes
smsusb_onresponse: line: 143: error, urb status -2, 0 bytes
smsusb_onresponse: line: 143: error, urb status -2, 0 bytes
smsusb_onresponse: line: 143: error, urb status -2, 0 bytes
smsusb_onresponse: line: 143: error, urb status -2, 0 bytes
smsusb_onresponse: line: 143: error, urb status -2, 0 bytes
smsusb_onresponse: line: 143: error, urb status -2, 0 bytes
smsusb_onresponse: line: 143: error, urb status -2, 0 bytes
WARNING: You are using an experimental version of the media stack.
As the driver is backported to an older kernel, it doesn't offer
enough quality for its usage in production.
Use it with care.
Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
b2d1467ad0461049c0de8f82f514447b0b8f016b tryfix v4l2_ctrl_check duplicate symbol #2
64955823cf3bd80743f1f3a5f7d50bd599d8affc tryfix v4l2_ctrl_check duplicate symbol - modify header
e8812dab0d410e2694451a73b421df6fd82b3b07 Merge branch 'bh-master_20140924_bh_dvb_usb_v2' of git.blackhole-commun
ity.net:repos/bh/vuplus_kernel into bh-master_20140924_bh_dvb_usb_v2
smsusb: probe of 2-1:1.0 failed with error -2
usbcore: registered new interface driver smsusb
 
You must log in or register to reply here.
Top