[Sugar-devel] [TRANSIENT ISSUE] 3G-Modem not being recognised

[Ajay Garg]

On Thu, Nov 22, 2012 at 5:04 AM, James Cameron <quozl at laptop.org> wrote:

> Thanks Ajay.
>
> Can you confirm this is on XO-1.75 with 13.1.0 os11?


Ahh yes. It is on XO-1.75 with 13.1.0 os11.

Sorry for not being clear previously :-\




 I think you
> mentioned XO-1.75 and 13.1.0 in a previous reply, but you might have
> changed the configuration since then.
>
> At step c, where the modem is not detected, I take it you mean that
> the Sugar frame icon does not appear.  I know you said your nm_test.py
> script does not list the device.
>
> I wanted to test your nm_test.py.  It seems reliable.  In the same
> test, I was unable to reproduce your problem.  My test is below.
>
> I suggest in your case obtaining kernel dmesg output for two
> scenarios:
>
> - the modem is inserted after Sugar has started,
>

Ok, so here are the steps ::


a)
Ensure that a pen-drive is inserted in one USB-slot; and the modem in
another.

b)
Reboot.

c)
The modem-icon does not appear in the frame.


The "/var/log/messages" at this stage are attached as "case_1_messages"
The "dmesg" messages  at this stage are attached as "case_1_dmesg".

======================


d)
Reboot.

e)
The modem-icon does not appear in the frame.

f)
Remove (unplug) the modem.

g)
Re-plug the modem.

h)
The modem-icon now appears in the frame.


The "/var/log/messages" at this stage are attached as "case_2_messages"
The "dmesg" messages  at this stage are attached as "case_2_dmesg".

=================


I proceeded further with an additional workflow.

i)
Unmount and remove the pen-drive.

j)
Reboot.

k)
The modem-icon appears in the frame.

l)
Insert the pen-drive (so that log-files can be copied on this external
storage).


The "/var/log/messages" at this stage are attached as "case_3_messages"
The "dmesg" messages  at this stage are attached as "case_3_dmesg".

===================


Please let me know if I could provide any other info.




>
> - the modem is inserted before power on.
>
> So that the kernel response to the USB device can be checked.
>
> --
>
> I tested with 13.1.0 os12 on XO-4, and 12.1.0 os21 on XO-1.75 with a
> Huawei E173 bound to service vendor Optus in Australia.
>
> The modem was inserted in the socket and the laptop switched on.  I
> waited for Sugar to be available.
>
> The modem does appear in the frame.  I used My Settings to configure
> APN, then selected Connect using the frame icon.
>
> The connection completes and Browse can be used, but the frame icon
> does not change from saying "Connecting" (SL #4255).
>
> At this point, and before connecting, your nm_test.py script reports
> device 0 with type 2, and device 1 with type 8.
>
> At Terminal prompt the command "nmcli dev" properly lists /dev/ttyUBS0
> as type gsm state connected.
>
> "nmcli con" properly lists the connection.
>
> "nmcli con down uuid <uuid>" properly terminates the connection, and
> the frame icon properly reports status of "Disconnected".
>
> When I remove the modem from the socket, your nm_test.py script
> properly reports removed device 1 type 8, and when re-run does not
> report device 1 any longer.
>
> (Unrelated, why can't I copy a URL from the Browse activity location
> bar?  I had gone to lists.laptop.org, to devel@ archives, to grab your
> nm_test.py attachment.)
>
> On Wed, Nov 21, 2012 at 04:16:39PM +0530, Ajay Garg wrote:
> > Hi all.
> >
> > I tested on os11, with all power-management disabled.
> >
> > 0.
> > Insert a pen-drive.
> >
> > a)
> > Inserted modem in another slot; the modem is detected.
> >
> > b)
> > Reboot.
> >
> > c)
> > Modem is NOT detected.
> >
> > d)
> > Remove modem.
> >
> > e)
> > Insert modem;  the modem is detected.
> >
> >
> > I tried the above steps 5 times; and the results were same.
> >
> >
> > Also, please find attached a sample  python script, which lists all the
> > detected network-devices.
> > When this script is run as "python nm_test.py" in step c), the
> modem-device is
> > not detected by this script as well; whereas in other cases, this script
> > detects the device.
> >
> >
> >
> >
> >
> >
> >
> >
> ===============================================================================
> > =
> >
> > Another sequence ::
> >
> >
> > 0.
> > Ensure that there is no pen-drive inserted in any of the USB slots.
> >
> > a)
> > Inserted modem; the modem is detected.
> >
> > b)
> > Reboot.
> >
> > c)
> > Modem is detected.
> >
> > d)
> > Remove modem.
> >
> > e)
> > Insert modem;  the modem is detected.
> >
> >
> > I tried the above steps 5 times; and the results were same.
> >
> >
> >
> ===============================================================================
> > ================
> >
> >
> > I will try the  same  steps with os12, once I am finished downloading it.
> >
> >
> >
> ===============================================================================
> > ================
> >
> >
> > I don't have a XO-1.5; so can't try on it :-\
> >
> >
> >
> >
> >
> >
> > On Wed, Nov 21, 2012 at 3:18 PM, Richard A. Smith <richard at laptop.org>
> wrote:
> >
> >     On 11/21/2012 01:07 AM, Jerry Vonau wrote:
> >
> >
> >
> >         Dropping the power to the usb bus is making the modem play
> peek-a-boo
> >         with the kernel: http://dev.laptop.org/ticket/10708.
> >         <http://dev.laptop.org/ticket/10708>
> >
> >
> >     And just to be clear its more than just a power dropping problem.
>  Both
> >     1.75 and XO-4 both have the ability to keep the USB bus powered
> during
> >     suspend (with an EC firmware change) but on resume the kernel resets
> the
> >     USB bus.  I don't know if the kernel has an option not to do that.
> >
> >
> >     --
> >     Richard A. Smith  <richard at laptop.org>
> >     One Laptop per Child
> >     _______________________________________________
> >     Devel mailing list
> >     Devel at lists.laptop.org
> >     http://lists.laptop.org/listinfo/devel
> >
> >
> >
> > Regards,
> > Ajay
> >
>
>
> > _______________________________________________
> > Devel mailing list
> > Devel at lists.laptop.org
> > http://lists.laptop.org/listinfo/devel
>
>
> --
> James Cameron
> http://quozl.linux.org.au/
>




Regards,

Ajay Garg
Dextrose Developer
Activity Central: http://activitycentral.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20121122/c2bb9abc/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: case_1_messages
Type: application/octet-stream
Size: 48125 bytes
Desc: not available
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20121122/c2bb9abc/attachment-0006.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: case_1_dmesg
Type: application/octet-stream
Size: 24778 bytes
Desc: not available
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20121122/c2bb9abc/attachment-0007.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: case_2_messages
Type: application/octet-stream
Size: 56805 bytes
Desc: not available
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20121122/c2bb9abc/attachment-0008.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: case_2_dmesg
Type: application/octet-stream
Size: 25332 bytes
Desc: not available
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20121122/c2bb9abc/attachment-0009.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: case_3_messages
Type: application/octet-stream
Size: 51179 bytes
Desc: not available
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20121122/c2bb9abc/attachment-0010.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: case_3_dmesg
Type: application/octet-stream
Size: 24719 bytes
Desc: not available
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20121122/c2bb9abc/attachment-0011.obj>