Can't create bug ticket
daniel at digsoc.com
Mon Jan 26 14:25:04 CET 2009
(Never mind... I just don't know how to use Nabble...)
> I think I accidentally replied to you directly. I'm going to post
> again to the list, so please forgive if you get my e-mail twice.
> On Sun, Jan 25, 2009 at 11:19 PM, William Kenworthy (via Nabble)
> <ml-user+1677-643196188 at n2.nabble.com> wrote:
>> This is interesting - you have similar uart settings to mine!
>> Some things that might be useful:
>> minicom, set to 115200,8,n,1 hardware flow control
>> Stop X
>> stty -F /dev/ttySAC0 sane
>> stty -F /dev/ttySAC0
>> (the above is one line - sets the uart)
>> Once you are happy the uart is talking ok, try restarting X and see what
>> What I have been looking at so far is that my uart isnt being
>> initialised properly by some software (such as the mux)
>> And its already obvious to me that at least two variants of uart configs
>> exist (see bug #2215 for the one that works with the mux)
>> Hint: be nice if others could check and see what their uart shows if
>> they are having connection problems :)
>> On Sun, 2009-01-25 at 20:04 -0800, danek wrote:
>>> I don't have /dev/ttSAC0 ... I'm going to assume ttySAC0 is the same
>>> Below I have the output from 2007.2/2008.4, since it's the most recent
>>> I flashed (to try using GSM manually)
>>> If you think another distribution would give different output that would
>>> more useful for your purposes, let me know.
>>> My modem did work with FSO (I used milestone 3 briefly, and milestone 4
>>> a little bit longer) when it worked. I never got a chance to try SHR
>>> it was working. I never tried debugging my modem while it was working,
>>> don't know what parts of its behavior are normal and what parts are new.
>>> root at om-gta02:~# stty -a -F /dev/tty
>>> /dev/tty /dev/tty1 /dev/tty3 /dev/ttySAC0 /dev/ttySAC2
>>> /dev/tty0 /dev/tty2 /dev/tty4 /dev/ttySAC1
>>> root at om-gta02:~# stty -a -F /dev/ttySAC0
>>> speed 115200 baud; rows 24; columns 80;
>>> intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
>>> eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase =
>>> lnext = ^V; flush = ^O; min = 1; time = 0;
>>> -parenb -parodd cs8 -hupcl -cstopb cread clocal crtscts
>>> -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl
>>> -ixoff -iuclc -ixany -imaxbel
>>> -opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0
>>> -isig -icanon -iexten -echo echoe echok -echonl -noflsh -xcase -tostop
>>> echoctl echoke
>>> root at om-gta02:~# stty -g -F /dev/ttySAC0
>>> William Kenworthy wrote:
>>> > I would appreciate it if you could send me the results of:
>>> > stty -a -F /dev/ttSAC0
>>> > stty -g -F /dev/ttSAC0
>>> > Gives me some more data for my problem
>>> > Tks,
>>> > BillK
>> William Kenworthy <billk at ...>
>> Home in Perth!
>> support mailing list
>> support at ...
>> This email is a reply to your post @
>> You can reply by email or by visting the link above.
View this message in context: http://n2.nabble.com/Still-can%27t-register-GSM-tp1649863p2217846.html
Sent from the Openmoko Support mailing list archive at Nabble.com.
More information about the support