You are not logged in.
this is an old but sweet acer aspire one.
the inbuilt modem:
# lsusb -v | grep -iA22 '0af0:7211'
Bus 004 Device 002: ID 0af0:7211 Option
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x0af0 Option
idProduct 0x7211
bcdDevice 0.00
iManufacturer 1 Option N.V.
iProduct 2 Globetrotter HSUPA Modem
iSerial 4 Serial Number
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 95
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
and
$ ip link
3: hso0: <POINTOPOINT,MULTICAST,NOARP> mtu 1486 qdisc noop state DOWN mode DEFAULT group default qlen 10
link/none
here on my minimalist arch install i was trying with netctl's mobile_ppp presets but got nowhere. equally with wvdial.
(with normal dongles, i have been using wvdial, pppd and netctl succesfully.)
but from these tries, it seems that the device shows up as /dev/ttyHS*, and /dev/ttyHS1 actually reacts to AT sequences.
anyways, none resulted in a working connection.
with these options i can connect with sakis3g:
sakis3g --sudo connect OTHER='USBMODEM' USBMODEM='0af0:7211' USBINTERFACE='2' APN='internet' APN_USER='0' APN_PASS='0'
after that, "ip link" shows another interface:
6: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 3
link/ppp
but i would really like to use netctl, if at all possible.
or at least something simpler than networkmanager, or something more reliable than sakis3g.
but i have no clue how to tell netctl to communicate with the modem & actually create a working connection.
any input appreciated.
Last edited by ondoho (2015-05-24 17:20:58)
Offline
my respect to the sakis3g creators, but it's messy, and it resists attempts at integrating it into systemd.
upon connection, sakis3g calls the device "GTM380".
trying to connect with this profile:
Description='Example PPP mobile connection'
Interface=ttyHS2
# i tried this with ttyHS0 - ttyHS3
Connection=mobile_ppp
TimeoutUp=30
# Use default route provided by the peer (default: true)
#DefaultRoute=true
# Use DNS provided by the peer (default: true)
#UsePeerDNS=true
# The user and password are not always required
User='0'
Password='0'
# The access point name you are connecting to
AccessPointName=internet
# If your device has a PIN code, set it here. Defaults to 'None'
Pin=None
# Mode can be one of 3Gpref, 3Gonly, GPRSpref, GPRSonly, None
# These only work for Huawei USB modems; all other devices should use None
#Mode=3Gpref
netctl is communicating with the modem, but everytime, after executing a few chat AT commands (terminology?), I get "Connect script failed".
i tried to adjust the profile in many ways, to no avail.
it seems i just need the right "chatscript" or however it's called.
there seems to be almost no info on this device on the internet, let alone for linux.
Last edited by ondoho (2015-05-04 02:58:51)
Offline
i found another tool, hsoconnect.
afaiu, it's a python gui wrapper for hsolinkcontrol.
hsolink, which includes the command line tool, is in [community], which suggests that it is still usable/useful/not out of date.
but the python gui is sluggish and too resource-hungry on this weak netbook. it has to keep running while connected. it also gets confused after suspend.
i thought i might just use hsolinkcontrol, but unfortunately the gui utility does not explain how it uses hsolinkcontrol...
But it has a nice debug output and i was hoping i could maybe build my own chatscript from it, so i can use pppd or hsolinkcontrol or wvdial for connecting?
here's an example output of a succesful connection (i xxx'd out some ip-addresses and personal-looking numbers).
i would really appreciate your input.
i have tried too many things to put down in this thread; it seems i can communicate with the modem (even tried minicom), but not create an internet connection.
Last edited by ondoho (2015-05-04 03:01:01)
Offline
I have a similar problem with a usb 3G modem, works with Sakis3G but not with NetworkManager, it try to connect and modem light says it's connected but NM isn't connected. ModemManager says unknown error.
Offline
Worked with wvdial, i did a
# wvdialconf
and added this to /etc/wvdial.conf
Init3 = at+cgdcont=1,"IP","apn","",0,0
where apn is your apn.
Offline
the problem already starts with not being able to run
# wvdialconf
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
Modem Port Scan<*1>: S1 S2 S3
Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?
Please read the FAQ at http://alumnit.ca/wiki/?WvDial
however, i'm fairly sure it is at /dev/ttyHS0-3, so i tried a fairly standard /etc/wvdial.conf, with your added Init3, played around with it - to no avail.
i should add that i have been unsing wvdial with normal 3g dongles for years... but this one is not normal.
i'm able to communicate with the modem with
# comgt -d /dev/ttyHS1
SIM ready
Waiting for registration..(120 sec max)
Registered on Home network: "DNA",2
Signal Quality: 16,99
and
# comgt -d /dev/ttyHS1 info
##### Wireless WAN Modem Configuration #####
Product text:
====
Manufacturer: Option N.V.
Model: GTM380
Revision: 2.12.0Hd (Date: May 27 2008, Time: 11:19:10)
OK
====
Manufacturer: Option N.V.
IMEI and Serial Number: 357564011701640,PE2989G00L
Manufacturer's Revision:
2.12.0Hd (Date: May 27 2008, Time: 11:19:1
Hardware Revision: 2.0
Network Locked: 0
Customisation: DEPRICATED
Band settings: Europe 900/1800MHz (4)
APN: 1,"IP","internetinternet.saunalahtiinternetinternet.saunalahtiinternetinternet.saunalahtiinternet","",0,0
##### END #####
and according to this i should be able to connect with pppd or wvdial after initializing the modem.
i tried with wvdial (with and without initializing) but all i get is
--> WvDial: Internet dialer version 1.61
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: AT+CGDCONT=1,"IP","internet","",0,0
AT+CGDCONT=1,"IP","internet","",0,0
OK
--> Modem initialized.
--> Sending: ATDT*99#
--> Waiting for carrier.
--> Timed out while dialing. Trying again.
...
(which does seem like a partial success until now).
the biggest pita is that the modem seems to lock up totally after any unsuccesful attempt and i don't know any other solution but to put the laptop to hibernate & wake it up again...
so, does anyone know the secret ingredient?
Offline
solved at last.
the hso kernel module source package contains a shell script to connect (hso_connect.sh).
the README says "far from failsafe" - so far i see no problems, but i will not mark this thread solved just yet.
the script is easy to hack.
in its core it only uses chat, ifconfig and route.
here's the hso module source (v. 1.9.):
http://www.pharscape.org/forum/index.ph … 0;attach=8
Last edited by ondoho (2015-05-23 09:40:31)
Offline
^ that script works well enough.
however, all methods mentioned above use something called "slow aquisition" - it means it takes about 30s to get an internet connection up.
i tried again with network-manager, and this time i succeeded. it's faster, and also integration with sleep & hibernate is better. i've documented the process here.
Offline