AW: Problems with Sierra MC 8790 after kernel upgrade to 3.7.x

2013-02-14 Thread Harald Jung - ECOS Technology
Hi,

 

ups sorry... i've talked with Gerald and the modem never worked with 
modem-manager.

The last time it worked was with our own scripts before we switched to 
network-manager.

These scripts were based on AT init scripts and an pppd chat script.

 

 

Harald

 
 
-Ursprüngliche Nachricht-
An:networkmanager-list@gnome.org; 
Von:Marius Kotsbak 
Gesendet:Do 14.02.2013 13:31
Betreff:Re: Problems with Sierra MC 8790 after kernel upgrade to 3.7.x
Den 14. feb. 2013 12:51, skrev Harald Jung - ECOS Technology:
> Hi,
>
> after upgrading to kernel 3.7.X (3.7.7) the Sierra MC 8790 doesn't
> connect anymore, 3.6.11 was the last kernel the Sierre module worked with.
>

Does it work with 3.6.11 kernel now? What about 3.8 kernels?

--
Marius

___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list


AW: Problems with Sierra MC 8790 after kernel upgrade to 3.7.x

2013-02-14 Thread Harald Jung - ECOS Technology
It worked with the 3.6.11 but not with 3.7.6 and 3.7.7

But there where no tests with 3,8 yet.
 
-Ursprüngliche Nachricht-
An:networkmanager-list@gnome.org; 
Von:Marius Kotsbak 
Gesendet:Do 14.02.2013 13:31
Betreff:Re: Problems with Sierra MC 8790 after kernel upgrade to 3.7.x
Den 14. feb. 2013 12:51, skrev Harald Jung - ECOS Technology:
> Hi,
>
> after upgrading to kernel 3.7.X (3.7.7) the Sierra MC 8790 doesn't
> connect anymore, 3.6.11 was the last kernel the Sierre module worked with.
>

Does it work with 3.6.11 kernel now? What about 3.8 kernels?

--
Marius

___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list


Problems with Sierra MC 8790 after kernel upgrade to 3.7.x

2013-02-14 Thread Harald Jung - ECOS Technology
Hi,

 

after upgrading to kernel 3.7.X (3.7.7) the Sierra MC 8790 doesn't connect 
anymore, 3.6.11 was the last kernel the Sierre module worked with.

 

Feb 14 09:56:28 MClient020 modem-manager[2233]:   (ttyUSB0) closing 
serial port... 
Feb 14 09:56:28 MClient020 modem-manager[2233]:   (ttyUSB0) serial port 
closed 
Feb 14 09:56:28 MClient020 modem-manager[2233]:   (ttyUSB0) opening 
serial port... 
Feb 14 09:56:28 MClient020 modem-manager[2233]:   (ttyUSB1) closing 
serial port... 
Feb 14 09:56:28 MClient020 modem-manager[2233]:   (ttyUSB1) serial port 
closed 
Feb 14 09:56:28 MClient020 modem-manager[2233]:   (ttyUSB1) opening 
serial port... 
Feb 14 09:56:28 MClient020 modem-manager[2233]:   (ttyUSB1) closing 
serial port... 
Feb 14 09:56:28 MClient020 modem-manager[2233]:   (ttyUSB1) serial port 
closed 
Feb 14 09:56:30 MClient020 slapd_2.3[2577]: @(#) $OpenLDAP: slapd 2.3.40 (Jan 
23 2013 14:06:30) $ 
^I@gentoo4:/usr/bbsrc/bbbuild/dev-pkg/std/portage/net-nds/openldap-2.3.40/work/openldap-2.3.
Feb 14 09:56:32 MClient020 crond[2604]: crond: crond (busybox 1.20.2) started, 
log level 8
Feb 14 09:56:32 MClient020 sudo: root : TTY=unknown ; PWD=/ ; USER=ldap ; 
COMMAND=/bin/slapcat_2.3 -c -f /etc/openldap/slapd.conf_2.3
Feb 14 09:56:34 MClient020 modem-manager[2233]:   (ttyUSB0) closing 
serial port... 
Feb 14 09:56:34 MClient020 modem-manager[2233]:   (ttyUSB0) serial port 
closed 
Feb 14 09:56:35 MClient020 modem-manager[2233]:   Couldn't probe for 
capabilities, probably not a GSM or CDMA modem 
Feb 14 09:56:35 MClient020 modem-manager[2233]:   (ttyUSB2) closing 
serial port... 
Feb 14 09:56:35 MClient020 modem-manager[2233]:   (ttyUSB2) serial port 
closed 
Feb 14 09:56:35 MClient020 modem-manager[2233]:   (ttyUSB3) opening 
serial port... 
Feb 14 09:56:35 MClient020 modem-manager[2233]:   (ttyUSB3): port 
attributes not fully set 
Feb 14 09:56:35 MClient020 NetworkManager[2220]:  (ttyUSB3): failed to 
look up interface index
Feb 14 09:56:35 MClient020 NetworkManager[2220]:  (ttyUSB3): new GSM/UMTS 
device (driver: 'sierra' ifindex: 0)
Feb 14 09:56:35 MClient020 NetworkManager[2220]:  (ttyUSB3): exported as 
/org/freedesktop/NetworkManager/Devices/2
Feb 14 09:56:35 MClient020 NetworkManager[2220]:  (ttyUSB3): now managed
Feb 14 09:56:35 MClient020 NetworkManager[2220]:  (ttyUSB3): device state 
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 14 09:56:35 MClient020 NetworkManager[2220]:  (ttyUSB3): deactivating 
device (reason 'managed') [2]
Feb 14 09:56:35 MClient020 NetworkManager[2220]:  (ttyUSB3): device state 
change: unavailable -> disconnected (reason 'none') [20 30 0]
Feb 14 09:56:36 MClient020 modem-manager[2233]:   Modem 
/org/freedesktop/ModemManager/Modems/0: unlock no longer required

Feb 14 09:56:36 MClient020 modem-manager[2233]:   (ttyUSB3) closing 
serial port... 
Feb 14 09:56:36 MClient020 modem-manager[2233]:   (ttyUSB3) serial port 
closed 
Feb 14 09:56:48 MClient020 NetworkManager[2220]:  Activation (ttyUSB3) 
starting connection 'Mobilfunk'
Feb 14 09:56:48 MClient020 NetworkManager[2220]:  (ttyUSB3): device state 
change: disconnected -> prepare (reason 'none') [30 40 0]
Feb 14 09:56:48 MClient020 NetworkManager[2220]:  Activation (ttyUSB3) 
Stage 1 of 5 (Device Prepare) scheduled...
Feb 14 09:56:48 MClient020 NetworkManager[2220]:  Activation (ttyUSB3) 
Stage 1 of 5 (Device Prepare) started...
Feb 14 09:56:48 MClient020 NetworkManager[2220]:  Activation (ttyUSB3) 
Stage 1 of 5 (Device Prepare) complete.
Feb 14 09:56:48 MClient020 modem-manager[2233]:   (ttyUSB3) opening 
serial port... 
Feb 14 09:56:48 MClient020 modem-manager[2233]:   (ttyUSB3): port 
attributes not fully set 
Feb 14 09:56:48 MClient020 modem-manager[2233]:   Modem 
/org/freedesktop/ModemManager/Modems/0: state changed (disabled -> enabling) 
Feb 14 09:56:48 MClient020 modem-manager[2233]:   (ttyUSB4) opening 
serial port... 
Feb 14 09:56:48 MClient020 modem-manager[2233]:   (ttyUSB4): port 
attributes not fully set 
Feb 14 09:56:48 MClient020 modem-manager[2233]:   (ttyUSB3): using PDU 
mode for SMS 
Feb 14 09:56:49 MClient020 modem-manager[2233]:   Modem 
/org/freedesktop/ModemManager/Modems/0: state changed (enabling -> enabled) 
Feb 14 09:56:49 MClient020 NetworkManager[2220]:  WWAN now enabled by 
management service
Feb 14 09:56:49 MClient020 modem-manager[2233]:   Modem 
/org/freedesktop/ModemManager/Modems/0: state changed (enabled -> registered) 
Feb 14 09:56:49 MClient020 modem-manager[2233]:   Modem 
/org/freedesktop/ModemManager/Modems/0: state changed (registered -> 
connecting) 
Feb 14 09:56:49 MClient020 modem-manager[2233]:   Modem 
/org/freedesktop/ModemManager/Modems/0: state changed (connecting -> 
registered) 
Feb 14 09:56:49 MClient020 NetworkManager[2220]:  GSM connection failed: 
(32) No cause information available
Feb 14 09:56:49 MClient020 NetworkManager[2220]:  (ttyUSB3): device state 
change: prepare -> failed (reason 'modem-no-carrier') [40 120 25]
Feb 14 09:56:

Problems with Sierra LTE MC7710 Device

2013-01-23 Thread Harald Jung - ECOS Technology
Hi,

 

we have problems with a Sierra MC7710, it isn't even recognized by the kernel.

The device should be included in the current kernel 3.6.11/3.7.2 and I think it 
is caused by an usb issue.

 

When I take a look at the usb device, I see that there are only 2 subdevices:

 

T:  Bus=01 Lev=02 Prnt=02 Port=04 Cnt=03 Dev#=  7 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  2
P:  Vendor=1199 ProdID=68a2 Rev=00.06
S:  Manufacturer=Sierra Wireless, Incorporated
S:  Product=MC7710
C:  #Ifs= 2 Cfg#= 2 Atr=e0 MxPwr=0mA
/bin/usb-devices: line 79: printf: 0c: invalid number
I:  If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=(none)
/bin/usb-devices: line 79: printf: 0d: invalid number
I:  If#= 0 Alt= 0 #EPs= 0 Cls=0a(data ) Sub=00 Prot=02 Driver=(none)

 

But it should look like this (found it in the net):

 

T: Bus=01 Lev=02 Prnt=02 Port=04 Cnt=03 Dev#= 5 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1199 ProdID=68a2 Rev=00.06
S: Manufacturer=Sierra Wireless, Incorporated
S: Product=MC7710
C: #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
/usr/bin/usb-devices: line 79: printf: 08: invalid octal number
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)

 

dmesg output:

 

usb 1-1.5: new high-speed USB device number 7 using ehci_hcd
usb 1-1.5: config 1 has an invalid interface number: 8 but max is 3
usb 1-1.5: config 1 has no interface number 1
usb 1-1.5: config 2 has an invalid interface number: 12 but max is 1
usb 1-1.5: config 2 has an invalid interface number: 13 but max is 1
usb 1-1.5: config 2 has an invalid interface number: 13 but max is 1
usb 1-1.5: config 2 has no interface number 0
usb 1-1.5: config 2 has no interface number 1

 

As far as I understand are there 4 subdevices, as it should be normally.

 

00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB xHCI Host Controller (rev 04)

 

Maybe someone has seen something like this and knows a solution.

 

best regards 

Harald
 
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list