2010/5/21 J.C. Roberts <list-...@designtools.org>:
> On Thu, 20 May 2010 23:17:25 +0200 patrick kristensen
> <kristensenpatri...@gmail.com> wrote:
>> 2010/5/17 J.C. Roberts <list-...@designtools.org>:
>> > On Fri, 14 May 2010 17:11:16 +0200 patrick kristensen
>> > <kristensenpatri...@gmail.com> wrote:
>> >> Hi
>> >>
>> >> I have 4.6-RELEASE on a lenovo x200s system with Ericsson F3507g
>> >> Mobile Broadband Module installed (mini-pci express wwan adapter).
>> >> On FreeBSD the device is detected by the cdce(4) driver which
>> >> creates an ue0 ethernet interface. On 4.6-RELEASE install this
>> >> does not happen.
>> >> The cdce(4) appeared in openBSD 4.1 and following the changelog
>> >> from 4.1 to -current, cdce(4) should be in generic.
>> >> Do I need to modload anything for cdce to load?
>> >
>> >
>> > It seems you forgot to post your dmesg and the output of `usbdevs
>> > -vd`
>> >
>> >
>> > --
>> > The OpenBSD Journal - http://www.undeadly.org
>> >
>>
>> I have upgraded to 4.7-release and later 4.7-current but cdce does
>> not load. The output from dmesg and usbdevs for -release and -current
>> is:
>>
>>
> ...
>> OpenBSD 4.7-current (GENERIC.MP) #229: Wed May 12 02:02:27 MDT 2010
>> t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> ...
>> umodem0 at uhub1 port 4 configuration 1 interface 1 "Ericsson Ericsson
>> F3507g Mobile Broadband Minicard Composite Device" rev 2.00/0.00 addr
>> 2
>> umodem0: data interface 2, has CM over data, has break
>> umodem0: status change notification available
>> ucom0 at umodem0
>> umodem1 at uhub1 port 4 configuration 1 interface 3 "Ericsson Ericsson
>> F3507g Mobile Broadband Minicard Composite Device" rev 2.00/0.00 addr
>> 2
>> umodem1: data interface 4, has CM over data, has break
>> umodem1: status change notification available
>> ucom1 at umodem1
>> umodem2 at uhub1 port 4 configuration 1 interface 9 "Ericsson Ericsson
>> F3507g Mobile Broadband Minicard Composite Device" rev 2.00/0.00 addr
>> 2
>> umodem2: data interface 12, has CM over data, has break
>> umodem2: no data interface
> ...
>>
>> usbdevs -vd (4.7-current)
> ...
>> Controller /dev/usb1:
>> addr 1: high speed, self powered, config 1, EHCI root hub(0x0000),
>> Intel(0x8086), rev 1.00
>> uhub1
>> port 1 powered
>> port 2 powered
>> port 3 powered
>> port 4 addr 2: high speed, power 20 mA, config 1, Ericsson F3507g
>> Mobile Broadband Minicard Composite Device(0x1900), Ericsson(0x0bdb),
>> rev 0.00, iSerialNumber 3541430209963360
>> umodem0
>> umodem1
>> umodem2
>> port 5 powered
>> port 6 powered
>
>
> Though I have and have read the mostly useless marketing material
> touting the features of the Erricsson F3507g, I haven't been able to
> find any real specs. It seems to be very similar feature-wise to the
> Qalcomm Gobi-1000 and Gobi-2000 (MDM1000 and MDM2000 chipsets), but I
> am yet to find any claim that the Erricson F3507g uses Qaulcom parts,
> or for that matter, uses Qualcomm logic cores. It doesn't matter all
> that much since the above tells me the device is most likely usable in
> OpenBSD as is.
>
> Two of the three umodem(4) have serial ports attached (ucom(4)) so all
> you need to do is configure ppp(8) or pppd(8) to talk to one of those
> serial ports (/dev/cuaU?). You should probably read the umsm(4) for
> more info and an example chat script.
>
> A lot of similar EVDO/HSPA devices are built in the same way in the
> sense of providing more than one serial port, but only one of them is
> usable with ppp/pppd. The other supposed serial port speaks a
> proprietary protocol and is used for "management" purposes. Typically,
> the proprietary protocol is either Qualcomm QMI or Qualcomm DM. Due to
> various "leaks" (read: google android), portions of the proprietary
> protocol have been figured out by the linux camp, but it's still a work
> in progress. Some details were posted here:
> http://blogs.gnome.org/dcbw/2010/04/
>
> jcr
>
> --
> The OpenBSD Journal - http://www.undeadly.org
>
Thanks for taking the time to answer and your fast replies.
In absence of cdce (using ue0 as ethernet interface (and minicom) to
connect to isp) i have tried several ppp and pppd configurations to
get a working internet connection on -release with no success.
The following is my ppp (# ppp -auto movistar) and pppd (# pppd call
movistar) attempts.
/etc/ppp/ppp.conf (appended to ppp.conf.sample)
movistar:
set device /dev/cuaU0
set speed 460800
set timeout 0
set dial "ABORT BUSY TIMEOUT 5 \
\"\" \
AT OK-AT-OK \
AT+CFUN=1 OK-AT-OK \
AT+CPIN? +CPIN:\\sREADY-AT+CPIN\\\"7291"\\\"-OK \
AT+CGDCONT=1,\\\"IP\\\",\\\"movistar.es\\\" OK \
"ATDT*99***1#"
set mtu maximum 750
resolv rewrite
set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0.
add default HISADDR
enable dns
# ./.
/var/log/ppp.log
May 22 17:57:51 x200s ppp[8742]: Phase: Using interface: tun0
May 22 17:57:51 x200s ppp[8742]: Phase: deflink: Created in closed state
May 22 17:57:51 x200s ppp[8742]: tun0: Command: default: set device
/dev/cuaU0
May 22 17:57:51 x200s ppp[8742]: tun0: Command: default: set speed 460800
May 22 17:57:51 x200s ppp[8742]: tun0: Command: default: set dial
ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 "" AT OK-AT-OK ATE1Q0 OK
\\dATDT\\T TIMEOUT 40 CONNECT
May 22 17:57:51 x200s ppp[8742]: tun0: Command: movistar: set device
/dev/cuaU0
May 22 17:57:51 x200s ppp[8742]: tun0: Command: movistar: set speed 460800
May 22 17:57:51 x200s ppp[8742]: tun0: Command: movistar: set timeout 0
May 22 17:57:51 x200s ppp[8742]: tun0: Command: movistar: set dial
ABORT BUSY TIMEOUT 5 "" AT OK-AT-OK
AT+CFUN=1 OK-AT-OK
AT+CPIN? +CPIN:\\sREADY-AT+CPIN\\"7291\\"-OK
AT+CGDCONT=1,\\"IP\\",\\"movistar.es\\" OK ATDT*99***1#
May 22 17:57:51 x200s ppp[8742]: tun0: Command: movistar: set mtu maximum 750
May 22 17:57:51 x200s ppp[8742]: tun0: Command: movistar: resolv rewrite
May 22 17:57:51 x200s ppp[8742]: tun0: IPCP: Primary nameserver set to
255.255.255.255
May 22 17:57:51 x200s ppp[8742]: tun0: Command: movistar: set ifaddr
10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0.
May 22 17:57:51 x200s ppp[8742]: tun0: Command: movistar: add default HISADDR
May 22 17:57:51 x200s ppp[8742]: tun0: Command: movistar: enable dns
May 22 17:57:51 x200s ppp[3315]: tun0: Phase: PPP Started (auto mode).
May 22 17:57:51 x200s ppp[3315]: tun0: Phase: bundle: Establish
May 22 17:57:51 x200s ppp[3315]: tun0: Phase: deflink: closed -> opening
May 22 17:57:51 x200s ppp[3315]: tun0: Phase: deflink: Connected!
May 22 17:57:51 x200s ppp[3315]: tun0: Phase: deflink: opening -> dial
May 22 17:57:51 x200s ppp[3315]: tun0: Chat: deflink: Dial attempt 1 of 1
May 22 17:57:51 x200s ppp[3315]: tun0: Chat: Send: AT\^M
May 22 17:57:51 x200s ppp[3315]: tun0: Chat: Expect(5): OK
May 22 17:57:51 x200s ppp[3315]: tun0: Chat: Received:
May 22 17:57:51 x200s last message repeated 2 times
May 22 17:57:51 x200s ppp[3315]: tun0: Chat: Received: \^M
May 22 17:57:51 x200s ppp[3315]: tun0: Chat: Received: \^M
May 22 17:57:51 x200s ppp[3315]: tun0: Chat: Received: AT\^M\^M
May 22 17:57:51 x200s ppp[3315]: tun0: Chat: Received: OK\^M
May 22 17:57:51 x200s ppp[3315]: tun0: Chat: Send: AT+CFUN=1\^M
May 22 17:57:51 x200s ppp[3315]: tun0: Chat: Expect(5): OK
May 22 17:57:51 x200s ppp[3315]: tun0: Chat: Received: AT+CFUN=1\^M\^M
May 22 17:57:51 x200s ppp[3315]: tun0: Chat: Received: OK\^M
May 22 17:57:51 x200s ppp[3315]: tun0: Chat: Send: AT+CPIN?\^M
May 22 17:57:51 x200s ppp[3315]: tun0: Chat: Expect(5): +CPIN: READY
May 22 17:57:51 x200s ppp[3315]: tun0: Chat: Received: AT+CPIN?\^M\^M
May 22 17:57:51 x200s ppp[3315]: tun0: Chat: Received: +CPIN: SIM PIN\^M
May 22 17:57:51 x200s ppp[3315]: tun0: Chat: Received: \^M
May 22 17:57:51 x200s ppp[3315]: tun0: Chat: Received: OK\^M
May 22 17:57:56 x200s ppp[3315]: tun0: Chat: Expect timeout
May 22 17:57:56 x200s ppp[3315]: tun0: Chat: Send: AT+CPIN"7291"\^M
May 22 17:57:56 x200s ppp[3315]: tun0: Phase: deflink: dial -> carrier
May 22 17:57:57 x200s ppp[3315]: tun0: Phase: deflink: carrier -> login
May 22 17:57:57 x200s ppp[3315]: tun0: Phase: deflink: login -> lcp
May 22 17:57:57 x200s ppp[3315]: tun0: LCP: FSM: Using "deflink" as a
transport
May 22 17:57:57 x200s ppp[3315]: tun0: LCP: deflink: State change
Initial --> Closed
May 22 17:57:57 x200s ppp[3315]: tun0: LCP: deflink: State change
Closed --> Stopped
May 22 17:57:58 x200s ppp[3315]: tun0: LCP: deflink: LayerStart
May 22 17:57:58 x200s ppp[3315]: tun0: LCP: deflink: SendConfigReq(1)
state = Stopped
May 22 17:57:58 x200s ppp[3315]: tun0: LCP: ACFCOMP[2]
May 22 17:57:58 x200s ppp[3315]: tun0: LCP: PROTOCOMP[2]
May 22 17:57:58 x200s ppp[3315]: tun0: LCP: ACCMAP[6] 0x00000000
May 22 17:57:58 x200s ppp[3315]: tun0: LCP: MRU[4] 1500
May 22 17:57:58 x200s ppp[3315]: tun0: LCP: MAGICNUM[6] 0x1081a7d5
May 22 17:57:58 x200s ppp[3315]: tun0: LCP: deflink: State change
Stopped --> Req-Sent
May 22 17:58:01 x200s ppp[3315]: tun0: LCP: deflink: SendConfigReq(1)
state = Req-Sent
May 22 17:58:01 x200s ppp[3315]: tun0: LCP: ACFCOMP[2]
May 22 17:58:01 x200s ppp[3315]: tun0: LCP: PROTOCOMP[2]
May 22 17:58:01 x200s ppp[3315]: tun0: LCP: ACCMAP[6] 0x00000000
May 22 17:58:01 x200s ppp[3315]: tun0: LCP: MRU[4] 1500
May 22 17:58:01 x200s ppp[3315]: tun0: LCP: MAGICNUM[6] 0x1081a7d5
May 22 17:58:04 x200s ppp[3315]: tun0: LCP: deflink: SendConfigReq(1)
state = Req-Sent
May 22 17:58:04 x200s ppp[3315]: tun0: LCP: ACFCOMP[2]
May 22 17:58:04 x200s ppp[3315]: tun0: LCP: PROTOCOMP[2]
May 22 17:58:04 x200s ppp[3315]: tun0: LCP: ACCMAP[6] 0x00000000
May 22 17:58:04 x200s ppp[3315]: tun0: LCP: MRU[4] 1500
May 22 17:58:04 x200s ppp[3315]: tun0: LCP: MAGICNUM[6] 0x1081a7d5
May 22 17:58:07 x200s ppp[3315]: tun0: LCP: deflink: SendConfigReq(1)
state = Req-Sent
May 22 17:58:07 x200s ppp[3315]: tun0: LCP: ACFCOMP[2]
May 22 17:58:07 x200s ppp[3315]: tun0: LCP: PROTOCOMP[2]
May 22 17:58:07 x200s ppp[3315]: tun0: LCP: ACCMAP[6] 0x00000000
May 22 17:58:07 x200s ppp[3315]: tun0: LCP: MRU[4] 1500
May 22 17:58:07 x200s ppp[3315]: tun0: LCP: MAGICNUM[6] 0x1081a7d5
May 22 17:58:10 x200s ppp[3315]: tun0: LCP: deflink: SendConfigReq(1)
state = Req-Sent
May 22 17:58:10 x200s ppp[3315]: tun0: LCP: ACFCOMP[2]
May 22 17:58:10 x200s ppp[3315]: tun0: LCP: PROTOCOMP[2]
May 22 17:58:10 x200s ppp[3315]: tun0: LCP: ACCMAP[6] 0x00000000
May 22 17:58:10 x200s ppp[3315]: tun0: LCP: MRU[4] 1500
May 22 17:58:10 x200s ppp[3315]: tun0: LCP: MAGICNUM[6] 0x1081a7d5
May 22 17:58:13 x200s ppp[3315]: tun0: LCP: deflink: LayerFinish
May 22 17:58:13 x200s ppp[3315]: tun0: LCP: deflink: State change
Req-Sent --> Stopped
May 22 17:58:13 x200s ppp[3315]: tun0: LCP: deflink: State change
Stopped --> Closed
May 22 17:58:13 x200s ppp[3315]: tun0: LCP: deflink: State change
Closed --> Initial
May 22 17:58:13 x200s ppp[3315]: tun0: Phase: deflink: Disconnected!
May 22 17:58:13 x200s ppp[3315]: tun0: Phase: deflink: lcp -> logout
May 22 17:58:13 x200s ppp[3315]: tun0: Phase: deflink: logout -> hangup
May 22 17:58:13 x200s ppp[3315]: tun0: Phase: deflink: Disconnected!
May 22 17:58:14 x200s ppp[3315]: tun0: Phase: deflink: Connect time:
23 secs: 288 octets in, 265 octets out
May 22 17:58:14 x200s ppp[3315]: tun0: Phase: deflink: 6 packets in, 5
packets out
May 22 17:58:14 x200s ppp[3315]: tun0: Phase: total 24 bytes/sec,
peak 46 bytes/sec on Sat May 22 17:58:02 2010
May 22 17:58:14 x200s ppp[3315]: tun0: Phase: deflink: hangup -> closed
May 22 17:58:14 x200s ppp[3315]: tun0: Phase: bundle: Dead
May 22 17:58:37 x200s ppp[3315]: tun0: Phase: Signal 15, terminate.
May 22 17:58:37 x200s ppp[3315]: tun0: Phase: PPP Terminated (normal).
And using pppd:
/etc/ppp/peers/chat/movistar.chat
TIMEOUT 120
ABORT "BUSY"
ABORT "NO CARRIER"
ABORT "ERROR"
ABORT "VOICE"
ABORT "NO DIALTONE"
OK AT+CPIN="7291"
OK AT+CFUN=1
OK AT+CGDCONT=1,"IP","movistar.es"
OK AT*ENAP=1,1
OK "ATD*99***1#"
CONNECT \c
/etc/ppp/peers/movistar
debug
cuaU0
460800
defaultroute
noauth
persist
noipdefault
connect '/usr/sbin/chat -v -f /etc/ppp/peers/chat/movistar.chat'
/var/log/chat
May 22 17:05:55 x200s chat[13931]: timeout set to 120 seconds
May 22 17:05:55 x200s chat[13931]: abort on (BUSY)
May 22 17:05:55 x200s chat[13931]: abort on (NO CARRIER)
May 22 17:05:55 x200s chat[13931]: abort on (ERROR)
May 22 17:05:55 x200s chat[13931]: abort on (VOICE)
May 22 17:05:55 x200s chat[13931]: abort on (NO DIALTONE)
May 22 17:05:55 x200s chat[13931]: expect (OK)
May 22 17:07:55 x200s chat[13931]: alarm
May 22 17:07:55 x200s chat[13931]: Failed
May 22 17:08:28 x200s chat[5761]: timeout set to 120 seconds
May 22 17:08:28 x200s chat[5761]: abort on (BUSY)
May 22 17:08:28 x200s chat[5761]: abort on (NO CARRIER)
May 22 17:08:28 x200s chat[5761]: abort on (ERROR)
May 22 17:08:28 x200s chat[5761]: abort on (VOICE)
May 22 17:08:28 x200s chat[5761]: abort on (NO DIALTONE)
May 22 17:08:28 x200s chat[5761]: expect (OK)
May 22 17:09:39 x200s chat[5761]: SIGTERM
In minicom(1) i get the following responses to the AT commands
AT+CPIN="7291"
OK
AT+CFUN=1
OK
*ESTKSMENU: movistar,0,3
6,Chat movistar
7,Correo movil
8,Copiagenda
*EMWI: 1,0
+PACSP0
(wwan antenna light turns on)
AT+CGDCONT=1,"IP","movistar.es"
OK
AT*ENAP=1,1
OK
(wwan antenna light starts blinking)
(At this stage with cdce i '# dhclient ue0' to get an ip adress)
My sources for creating the above configurations are
pppd(8)
ppp(8)
umsm(4)
http://old.nabble.com/umts-need-help-td22360780.html
http://projects.thiemo.net/moin.cgi/FreeBSD_on_ThinkPad_W500
http://www.thinkwiki.org/wiki/Ericsson_F3507g_Mobile_Broadband_Module
