Hi,
i think my message got lost, could you please check again?
no there was no device node created named like /dev/hso0, but the sysfs
interface was created.
Inside the sysfs path i don't see the "file" "dev", which should contain the
device node information. So udev has no idea how to create t
Hi,
no there was no device node created named like /dev/hso0, but the sysfs
interface was created.
Inside the sysfs path i don't see the "file" "dev", which should contain the
device node information. So udev has no idea how to create this device node.
Dan: What does ls -l /dev/hso0 show for you
On Sat, 2011-06-04 at 09:25 +0200, Harald Jung wrote:
> Hi,
>
>
> (sorry i forgot to shorten my message)
>
>
> the created network interface:
>
> hso0 Link encap:UNSPEC HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>
> POINTOPOINT NOARP MULTICAST MTU:1486 Metric:1
>
> RX packets:
Hi,
(sorry i forgot to shorten my message)
the created network interface:
hso0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
POINTOPOINT NOARP MULTICAST MTU:1486 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX pack
On Fri, 2011-06-03 at 15:24 +0200, Harald Jung wrote:
> Hi,
>
>
> i've done some tests again with the device, without beeing able to get
> the problem.
Can you stop NetworkManager, killall -TERM ModemManager, then run
ModemManager like so?
modem-manager --debug
when the modem is plugged in, do
Hi,
i've done some tests again with the device, without beeing able to get the
problem.
Device Info:
T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1
P: Vendor=0af0 ProdID=6971 Rev= 0.00
S: Manufacturer=Option N.V.
Hi,
i've done some tests again with the device, without beeing able to get the
problem.
Now I've got some more verbose logs:
Jun 3 15:12:58 ThinClient NetworkManager[24019]: Activation (ttyHS0)
Stage 1 of 5 (Device Prepare) complete.
Jun 3 15:12:58 ThinClient modem-manager[2227]: [mm-gener
On Tue, 2011-05-24 at 18:28 +0200, Harald Jung wrote:
> Hi,
>
>
> i think i was wrong with that speculation, the problem is not in the
> modem-manager AT command stuff. But in the way network-manager gets
> its ip configuration.
>
> Networkmanager isn't able to query the ip-settigs from the hso
Hi,
i think i was wrong with that speculation, the problem is not in the modem-
manager AT command stuff. But in the way network-manager gets its ip
configuration.
Networkmanager isn't able to query the ip-settigs from the hso network
interface.
best regards
Harald
Am Dienstag, 24. Mai 2011,
Hi Harald,
> > > May 20 14:41:21 ThinClient modem-manager[3764]:
>
> > > [mm-at-serial-port.c:298] debug_log(): (ttyHS0): --> 'AT
>
> > > +CPMS="ME","ME","ME"'
>
> >
>
> I have removed the CPMS setting from the source code, I don't need any
> sms support and the AT command caused the modem d
Hi,
Am Freitag, 20. Mai 2011, 15:27:33 schrieb Aleksander Morgado:
> On Fri, 2011-05-20 at 14:59 +0200, Harald Jung wrote:
> > May 20 14:41:21 ThinClient modem-manager[3764]:
> > [mm-at-serial-port.c:298] debug_log(): (ttyHS0): --> 'AT
> > +CPMS="ME","ME","ME"'
>
I have removed the CPMS setting
On Fri, 2011-05-20 at 14:59 +0200, Harald Jung wrote:
>
> May 20 14:41:21 ThinClient modem-manager[3764]:
> [mm-at-serial-port.c:298] debug_log(): (ttyHS0): --> 'AT
> +CPMS="ME","ME","ME"'
It seems the first command not replied properly is the above CPMS
setting, which is the SMS-storage relat
Hi,
we are using the modem-manager and networkmanager from the current git.
The last checkout was from May the 9th.
It seems that there are communication problems via the AT commands.
This is the USB Device we are try to get work with NetworkManager:
T: Bus=02 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#
13 matches
Mail list logo
