Skip to main content

huawei e1552 orange ubuntu debian

Orange Madagascar

This internet access provider had initially provided a USB Huawei E160. Then, then switched to the USB Huawei E1552 device.

The modem is composed by

  • A modem. (Why not?)
  • An USB mass storage, read-only, containing Windows drivers

Funny Windows

After I got the USB Huawei E1552, I wanted to to try it out on a spare Laptop running Microsoft Windows 7 32bits. I failed, because the driver provided on the USB stick is XP/Vista only, and known to be weird on Microsoft Windows 7 32bits.

On Linux

If the usb-modeswitch package is not installed, when plugging the modem, only the USB mass storage part is detected:

         usb 1-2: new high speed USB device using ehci_hcd and address 3 Initializing USB Mass Storage driver... scsi6 : usb-storage 1-2:1.0 scsi7 : usb-storage 1-2:1.1 usbcore: registered new interface driver usb-storage USB Mass Storage support registered. 

After installing usb-modeswitch and without any setup, when plugging the modem, the the USB mass storage part is detected and actived, then switched to the "GSM Modem" feature:

         usb_modeswitch: switching 12d1:1446 (HUAWEI Technology: HUAWEI Mobile) kernel: [10694.027147] usb 1-2: USB disconnect, address 3 kernel: [10700.190056] usb 1-2: new high speed USB device using ehci_hcd and address 4 kernel: [10700.361471] scsi10 : usb-storage 1-2:1.2 kernel: [10700.501603] usbcore: registered new interface driver usbserial kernel: [10700.501635] USB Serial support registered for generic kernel: [10700.502713] usbcore: registered new interface driver usbserial_generic kernel: [10700.502718] usbserial: USB Serial Driver core kernel: [10700.589257] USB Serial support registered for GSM modem (1-port) kernel: [10700.589427] option 1-2:1.0: GSM modem (1-port) converter detected kernel: [10700.592132] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB0 kernel: [10700.592185] option 1-2:1.1: GSM modem (1-port) converter detected kernel: [10700.592500] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB1 kernel: [10700.593596] usbcore: registered new interface driver option kernel: [10700.593603] option: v0.7.2:USB Driver for GSM modems usb_modeswitch: switched to 12d1:141b (HUAWEI Technology: HUAWEI Mobile) kernel: [10701.375029] scsi 10:0:0:0: Direct-Access     HUAWEI   MMC Storage      2.31 PQ: 0 ANSI: 2 kernel: [10701.381072] sd 10:0:0:0: Attached scsi generic sg2 type 0 kernel: [10701.389031] sd 10:0:0:0: [sdb] Attached SCSI removable disk 

Using "wvdial"

I use wvdial to connect to internet. This is the wvdial.conf part:

         [Dialer orange] Init0 = ATZ Modem Type = Analog Modem Baud = 921600 New PPPD = yes Modem = /dev/ttyUSB0 Phone = *99# Username = '' Password = '' Stupid Mode = 1 ISDN = 0 
Thanks to Elie Zedeck Randriamiandriray for the tips.

To connect, just run wvdial orange and you're done.

Using Gnome Network Manager

Use these settings:

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo&

emacs29 intelephense

Emacs 29 and PHP Intelephense I use to use Emacs and PHP Intelephense for PHP development. I recently upgraded to Emacs 29 and PHP Intelephense stopped working. I found a solution on Reddit Based on that, I rewrote my .emacs file to use eglot instead of lsp-mode, and this is the result. (use-package eglot :ensure t) (add-hook 'php-mode-hook 'eglot-ensure) (use-package php-mode :ensure t :mode ("\\.php\\'" . php-mode)) (add-to-list 'auto-mode-alist '("\\.php$" . php-mode)) (provide 'lang-php) (use-package company :ensure t :config (setq company-idle-delay 0.3) (global-company-mode 1) (global-set-key (kbd "M- ") 'company-complete)) (require 'eglot) (add-to-list 'eglot-server-programs '((php-mode :language-id "php") . ("intelephense" "--stdio" :initializationOptions (:licenseKey "98989898989898989898"

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: https://issues.jenkins-ci.org/browse/JENKINS-57495 Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM