Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. Re: Openmoko Bug #1902: Wifi can't connect at all
(Openmoko Public Trac)
2. Re: Openmoko Bug #1927: Login problem (Openmoko Public Trac)
3. Re: Openmoko Bug #1890: gdb problems (single stepping and
debug symbol table) (Openmoko Public Trac)
4. Re: Openmoko Bug #1923: Create contacts3 as a copy of
2007.2's contacts2 (Openmoko Public Trac)
5. Re: Openmoko Bug #1913: port 2007.2 gsm-panel apps to use
ophoned instead. (Openmoko Public Trac)
6. Re: Openmoko Bug #1884: [suspend/resume] if press power
batton right after suspend, the device won't wake up
(Openmoko Public Trac)
7. Openmoko Bug #1928: Settings don't change the suspend time
(Openmoko Public Trac)
8. Re: Openmoko Bug #1884: [suspend/resume] if press power
batton right after suspend, the device won't wake up
(Openmoko Public Trac)
9. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
--- Begin Message ---
#1902: Wifi can't connect at all
--------------------------------------------------------------------------+-
Reporter: hiciu |
Owner: hardware
Type: defect |
Status: new
Priority: normal |
Milestone:
Component: hardware |
Version: GTA02v6
Severity: normal |
Resolution:
Keywords: wireless wifi wlan set essid failed invalid argument 8B1A |
Blockedby:
Reproducible: always |
Blocking:
--------------------------------------------------------------------------+-
Comment(by hiciu):
("Bug Filing Policy" says to write tickets in this way)
Kernel: http://buildhost.openmoko.org/daily/freerunner/200808/20080829
/uImage-om-gta02-latest.bin (and other kernels too)
How to reproduce:
{{{
iwconfig eth0 essid my_ssid
}}}
Results:
{{{
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device eth0 ; Invalid argument.
}}}
Expected:
Wifi connect's to accesspoint.
Reproducible:
Always.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1902#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1927: Login problem
------------------------+---------------------------------------------------
Reporter: dareus | Owner: openmoko-devel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution: invalid
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Changes (by zecke):
* status: new => closed
* resolution: => invalid
Comment:
Please use the https://admin-trac.openmoko.org/trac to file admin issues.
AFAIK we can not migrate bugs from one trac to another so I'm closing this
as invalid and encourage you to file a bug over there. *please*
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1927#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1890: gdb problems (single stepping and debug symbol table)
-------------------------+--------------------------------------------------
Reporter: h.koenig | Owner: openmoko-devel
Type: defect | Status: in_testing
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
-------------------------+--------------------------------------------------
Changes (by zecke):
* status: new => in_testing
Comment:
Om2008.9 will have gdb6.8 and the Om2008.8 updates should have it too... I
added gdb 6.8 but didn't make it default for reasons I don't remember.
So it should pop up somewhere soon.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1890#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1923: Create contacts3 as a copy of 2007.2's contacts2
--------------------------------+-------------------------------------------
Reporter: aleix | Owner: openmoko-kernel
Type: task | Status: new
Priority: normal | Milestone: SHR
Component: System Software | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
--------------------------------+-------------------------------------------
Comment(by aleix):
Replying to [comment:1 zecke]:
> Duplicate of #1921?
#1921 is for messages3 and this one is for contacts3.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1923#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1913: port 2007.2 gsm-panel apps to use ophoned instead.
--------------------------------+-------------------------------------------
Reporter: aleix | Owner: openmoko-kernel
Type: task | Status: new
Priority: normal | Milestone: SHR
Component: System Software | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
--------------------------------+-------------------------------------------
Comment(by aleix):
Should be tested regarding the signal strength updates.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1913#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1884: [suspend/resume] if press power batton right after suspend, the device
won't wake up
--------------------------------+-------------------------------------------
Reporter: wendy_hung | Owner: andy
Type: defect | Status: new
Priority: high | Milestone: Om2008.9
Component: System Software | Version: Om2008.8
Severity: critical | Resolution:
Keywords: | Blockedby:
Reproducible: sometimes | Blocking:
--------------------------------+-------------------------------------------
Comment(by Treviño):
Tried. Nothing changed... :( To resume:
* Powerbutton doesn't wakeup
* Incoming call/sms doesn't wakeup
* Usb cable inserting doesn't wakeup
* Headset jack inserting/removing doesn't wakeup
Simply, doesn't wakeup :|. I just hope that all these battery remotion
won't damage it...
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1884#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1928: Settings don't change the suspend time
----------------------+-----------------------------------------------------
Reporter: wilk | Owner: marek
Type: defect | Status: new
Priority: normal | Milestone: Om2008.9
Component: Settings | Version:
Severity: blocker | Keywords:
Blockedby: | Reproducible: always
Blocking: |
----------------------+-----------------------------------------------------
After today's (30/08) update from
http://downloads.openmoko.org/repository/Om2008.8/, my freerunner doesn't
suspend by itself, whatever the setting configured. I can however manually
make it suspend (POW button) and wake up (POW button or a call).
I suspect that it's the Settings menu that doesn't change the apm
parameters since other users reported that their Freerunner goes into
suspend mode, but they can't change the time to suspend. I guess I'm just
lucky that mine was configured for "no suspend" when I did the upgrade.
I'm running raster's image upgraded through official repos. I attach the
output of opkg list_installed.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1928>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1884: [suspend/resume] if press power batton right after suspend, the device
won't wake up
--------------------------------+-------------------------------------------
Reporter: wendy_hung | Owner: andy
Type: defect | Status: new
Priority: high | Milestone: Om2008.9
Component: System Software | Version: Om2008.8
Severity: critical | Resolution:
Keywords: | Blockedby:
Reproducible: sometimes | Blocking:
--------------------------------+-------------------------------------------
Comment(by hbernard):
Mhh, since the update of today (I think I didn't reboot at the time of my
last comment), I can't reproduce exactly the same.
What I'm able to reproduce :
* powerbutton to put in suspend
* powerbutton right after (during the darkening effect of suspend)
* wait some seconds
* powerbutton resume, but the display fade to dark soon after ang go back
to suspend
* (I can repeat the above line several times)
* It seems when I wait some more seconds (10 or 20), it resumes OK
I also tested the wake from jack, which is working OK
Not sure it helps... Trevino, are you using an up2date 2008.08 ?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1884#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1841: white screen of death (WSOD) after resume
----------------------------+-----------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: GTA02v5
Severity: critical | Resolution:
Keywords: wsod,resume | Blockedby:
Reproducible: always | Blocking:
----------------------------+-----------------------------------------------
Comment(by pbondo):
Hello again
Should I start to feel worried that I bought a rather expensive brick ?
If Andy is correct in his assumption that the sticky WSOD is caused by a
reset of the glamo chip, then the obvious thing would be to look into the
specs of this chip.
However according to the hardware page the specs are only available under
NDA: http://wiki.openmoko.org/wiki/Neo_FreeRunner_GTA02_Hardware
This will in effect reduce the resource pool to internal OpenMoko
developers.
According to the svn log: svn log
https://svn.openmoko.org/trunk/src/target/kernel/patches/smedia-
glamo.patch
this was handled by Harald Welte until he left last year and since then it
appears that no one has touched it.
How do we proceed from here ? Will someone from OpenMoko step up and look
into it, or should I simply return the phone as a DOA hardware ? It
obviously has a hardware error, but it should be solvable by software.
As it stands the device is useless as a phone.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:8>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
