Don’t worry about that. I see it like a way to learn more about Linux 
1 Like
@Rosika,
Could you please do these first tests?
Open a terminal window
with umts working write these commands:
sudo grep 001/015 /sys/bus/usb/devices/*/ueventThis is to obtain your USB port form what you gave me:
Bus 001 Device 015: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem
The result will be somethig like this:
/sys/bus/usb/devices/yyy-xxx/ueventwith umts working:
write the following command:
sudo echo 'yyy-xxx' > /sys/bus/usb/drivers/usb/unbindcheck if umts stops working. If it stops working, write this command:
sudo echo 'yyy-xxx' > /sys/bus/usb/drivers/usb/bindThis is an attempt to just restart the USB port where UMTS is connected
Give the feedback please and indicate the yyy–xxx numbers too
1 Like
Hi again and tnx,
first of all:
lsusb | grep Huawei
Bus 001 Device 017: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem
So the device number changed. Therefore:
lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
|__ Port 4: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 2: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 3: Dev 6, If 0, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 4: Dev 8, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 2: Dev 10, If 0, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 3: Dev 12, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 3: Dev 12, If 2, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 3: Dev 12, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 3: Dev 12, If 3, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 1: Dev 9, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 4: Dev 14, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 4: Dev 14, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 2: Dev 11, If 0, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 3: Dev 13, If 0, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 4: Dev 15, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 3: Dev 17, If 4, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 3: Dev 17, If 2, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 3: Dev 17, If 0, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 3: Dev 17, If 3, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 3: Dev 17, If 1, Class=Vendor Specific Class, Driver=option, 480M
The respective usb-port is 1-1.2.4.4.3 .
I used the command “echo ‘1-1.2.4.4.3’ | sudo tee /sys/bus/usb/drivers/usb/unbind” which I already used in the past. It should have the same effect as the one provided by you.
And indeed umts stopped working.
With “echo ‘1-1.2.4.4.3’ | sudo tee /sys/bus/usb/drivers/usb/bind” I got it working again. So everything behaves as expected.
Greetings
Rosika 
1 Like
Great.
Know only needs to put the code to run automatically after re(boot)
Late I’ll try to do it
1 Like
Hi @Rosika,
Sorry for the late answer but I’m tryed to create a solution with systemd but without success
Could you please try these codes?
You will program a cron job to run your code every time your computer (re)boots
Open a terminal and type the follow code:
sudo crontab -eIf it is your first time you use crontab you need to choose the editor. Choose 1 ( nano)
Now, at the bottom of the test, write this:
@reboot /etc/cron.d/umts.shPress ctrl+o and Enter to save and ctrl+x to exit nano
With you terminal still open, we will now create your file with undind and bind commands:
sudo nano /etc/cron.d/umts.shand write your commands:
#!/bin/sh
echo '1-1.2.4.4.3' | sudo tee /sys/bus/usb/drivers/usb/unbind
echo '1-1.2.4.4.3' | sudo tee /sys/bus/usb/drivers/usb/bindor my version:
#!/bin/sh
echo '1-1.2.4.4.3' > /sys/bus/usb/drivers/usb/unbind
echo '1-1.2.4.4.3' > /sys/bus/usb/drivers/usb/bindSave the file ctrl+o and Enter
Exit nano ctrl+x
Turn your file executable:
chmod +x /etc/cron.d/umts.shTurn off and on your PC and check if if works
Reboot your PC and check if it works
please give the feedback
Regards,
Jorge
2 Likes
@Tech_JA:
Hi Jorge,
thank you so much for your help.
I looked through your post and it makes sense.
Yet before I put it into action there´s something I want to be clear of:
The main problem is that in most cases when I (re)boot lsusb doesn´t list the umts-stick at all. So the entries
Port 3: Dev 17, If 4, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 3: Dev 17, If 2, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 3: Dev 17, If 0, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 3: Dev 17, If 3, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 3: Dev 17, If 1, Class=Vendor Specific Class, Driver=option, 480M
don´t exist at all and
wouldn´t make any sense. Or do I get this wrong?
Because in the past I already tried
echo '1-1.2.4.4.3' | sudo tee /sys/bus/usb/drivers/usb/unbind
and I got an error or at least it didn´t have any effect at all.
I´m not sure about this but I think the main problem here is that the system doesn´t recognize at boot that the umts-stick is connected. It´s only when I physically disconnect and then connect it again that it does.
Greetings.
Rosika
1 Like
yes, you’re right.
this code only resets the device
We could try reset the controller again to check if it see the device…
1 Like
could you try tho reset the second hub?
#!/bin/sh
echo '1-1.2.4' > /sys/bus/usb/drivers/usb/unbind
sleep 4
echo '1-1.2.4' > /sys/bus/usb/drivers/usb/bind
1 Like
Hi Jorge,
thanks again for yor help.
#!/bin/sh
echo ‘1-1.2.4’ > /sys/bus/usb/drivers/usb/unbind
sleep 4
echo ‘1-1.2.4’ > /sys/bus/usb/drivers/usb/bind
But I´d rather not do that. That might prove counter-productive.
If I unbind ‘1-1.2.4’ I would get rid of access to my keyboard amongst other things. 
I´d say it´s best to leave things as they´re right now.
Even if that means I have to live with some quirks I still have the “solution” of switching off/on my hub and getting the system to recognize the umts-modem that way.
I know that this is an issue to some others as well. And for what it´s worth I´ve still learnt quite a few things with your help.
Thank you again for taking out quite a lot of time trying to solve my issue.
Greetings.
Rosika
1 Like
That’s OK, no problem 
1 Like
@Tech_JA:
Hi Jorge,
I just wanted to thank you for your help.
And, as I already said, I´ve learnt some things during the process.
The crontab-topic is particularly interesting.
And that´s what I like very much in this forum: you can always broaden yor knowledge of Linux.
I´d be glad if I can count on your help in the future as well, if the occasion arises. 
So thanks again and have a good time.
Greetings.
Rosika
2 Likes
@Rosika,
You can count on me at any time
I don’t know much about Linux, I’m still leaning as I go
Just a note:
unbind a bind your hub you don’t lose your keyboard and other peripherals connecting to hub
I’m tried to find a solution, searching in several sites, forums and even on Huawei’s site ( drivers, firmware…) but didn’t find anything.
I don’t know what else I can do to help you
2 Likes
Thanks a lot. That´s really kind of you.
As far as Linux-learning is concerned it´s the same with me. Although I´ve been using
Lubuntu for quite a while now it seems that there´s still so much to learn.
But it´s awfully interesting I must say.
Well, that´s more than I could hope for.
If I unexpectedly come up with a solution I´ll let you know here. In the meantime I´ll use my hub.
Thanks again and have a nice day.
Rosika
2 Likes