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. [Bug 1264] New: Two startup notification icons
([EMAIL PROTECTED])
2. [Bug 1265] New: IRQ storm from PMU chip
([EMAIL PROTECTED])
3. [Bug 1265] IRQ storm from PMU chip
([EMAIL PROTECTED])
4. [Bug 1266] New: Xserver lags at startup, "Please Wait" splash
does not display ([EMAIL PROTECTED])
5. [Bug 1267] New: Strong echo when calling a Neo from another
phone ([EMAIL PROTECTED])
6. [Bug 1268] New: Build fails because of glib & libogg
dependencies ([EMAIL PROTECTED])
7. [Bug 1265] IRQ storm from PMU chip
([EMAIL PROTECTED])
8. [Bug 1268] Build fails because of glib & libogg dependencies
([EMAIL PROTECTED])
9. [Bug 1172] cannot hear any sound from dialer in GTA02
([EMAIL PROTECTED])
10. [Bug 1269] New: No Audio ([EMAIL PROTECTED])
11. [Bug 1269] No Audio ([EMAIL PROTECTED])
12. [Bug 1214] Typo in Bluetooth Status change popup
([EMAIL PROTECTED])
13. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
14. [Bug 1250] No Wifi in Managed Mode
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1264
Summary: Two startup notification icons
Product: OpenMoko
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-panel
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
When an application is launched, two startup notification animations appear in
the panel.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1265
Summary: IRQ storm from PMU chip
Product: OpenMoko
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Approx every 5 boots of a GTA02 I get an irq storm which slows the machine to a
crawl and makes it next to useless. This is what turns up in dmesg.
pcf50633_irq: entering(irq=53, pcf=c7d06c00): scheduling work
pcf50633_work: INT1=0x00 INT2=0x00 INT3=0x40 INT4=0x00 INT5=0x00
ADCRDY
pcf50633_irq: entering(irq=53, pcf=c7d06c00): scheduling work
pcf50633_work: INT1=0x80 INT2=0x00 INT3=0x40 INT4=0x00 INT5=0x00
SECOND ADCRDY
pcf50633_irq: entering(irq=53, pcf=c7d06c00): scheduling work
pcf50633_work: INT1=0x00 INT2=0x00 INT3=0x40 INT4=0x00 INT5=0x00
ADCRDY
pcf50633_irq: entering(irq=53, pcf=c7d06c00): scheduling work
pcf50633_work: INT1=0x80 INT2=0x00 INT3=0x40 INT4=0x00 INT5=0x00
SECOND ADCRDY
pcf50633_irq: entering(irq=53, pcf=c7d06c00): scheduling work
pcf50633_work: INT1=0x80 INT2=0x00 INT3=0x40 INT4=0x00 INT5=0x00
SECOND ADCRDY
pcf50633_irq: entering(irq=53, pcf=c7d06c00): scheduling work
pcf50633_work: INT1=0x80 INT2=0x00 INT3=0x40 INT4=0x00 INT5=0x00
SECOND ADCRDY
pcf50633_irq: entering(irq=53, pcf=c7d06c00): scheduling work
pcf50633_work: INT1=0x00 INT2=0x00 INT3=0x40 INT4=0x00 INT5=0x00
ADCRDY
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1265
------- Additional Comments From [EMAIL PROTECTED] 2008-03-12 17:02 -------
I also get this (possibly on every boot), but it doesn't seem to be impacting on
performance.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1266
Summary: Xserver lags at startup, "Please Wait" splash does not
display
Product: OpenMoko
Version: current svn head
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Xfbdev (kdrive), Xglamo
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Using the daily snapshot image from buildhost for 12 March 2008 and the kernel
from 10 March 2008 (also from buildhost) the "Please Wait" splash screen fails
to display.
It is instead replaced with the gray stripe pattern seen when doing an X
--configure. This screen displays for several seconds before loading userspace
apps normally.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1267
Summary: Strong echo when calling a Neo from another phone
Product: Neo1973 Hardware
Version: unspecified
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Audio
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
This is a "well-known" issue but I couldn't find anything in Bugzilla for it.
When talking to a Neo, the person on the other end of the phone call will hear a
strong time-delayed echo of their voice. With the default settings it is bad
enough that it is difficult to hold a conversation, and it is even enough to
confuse IVR systems that use voice-recognition instead of DTMF tones.
It is possible to reduce (but not eliminate) the echo using the mixer, by
turning down the gain in the audio path from the microphone to the Calypso
input. However this also has the undesirable side-effect of reducing the volume
of the person who is speaking into the Neo. I am filing this under "hardware"
because I do not know if it will be possible to get acceptable performance using
only the mixer settings.
I have experienced this with a GTA01Bv4 and "-moko1" GSM firmware (one of the
first batch sold last summer), but it appears that this issue also affects
GTA02.
References:
http://lists.openmoko.org/pipermail/openmoko-kernel/2008-March/001477.html
http://lists.openmoko.org/pipermail/community/2008-January/012379.html
Note - a handy trick is to install 'xoscope' (which is in OE), a software
oscilloscope that measures the signal on the ADCs in the Wolfson codec. With a
few mixer tweaks it is possible to send a 1 kHz PCM tone out through the call
speaker, and measure the resulting microphone signal through the ADCs. It would
be even better to use a spectrum-analyzer program, but so far I have not been
able to compile one for the Neo.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1268
Summary: Build fails because of glib & libogg dependencies
Product: OpenMoko
Version: current svn head
Platform: Other
OS/Version: Linux
Status: NEW
Severity: blocker
Priority: P2
Component: OE bitbake recipes / build system
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
I started working with openmoko and openembedded a couple of days ago, building
it for a QTek blueangel PDA.
I checked out openembedded trunk version and performed a build from there. I had
the following errors:
| ERROR: Cannot satisfy the following dependencies for task-openmoko-pim:
| libogg0 (>= 1.1.3)
And a similar one for task-openmoko-ui asking for glib >= 2.15.6.
I added:
PREFERRED_VERSION_glib-2.0 = "2.15.6"
PREFERRED_VERSION_libogg = "1.1.3"
to conf/distro/include/preferred-om-2008-versions.inc and the image was
correctly built (but not yet tested on the target).
I need confirmation that this is actually a bug, I'm not yet confident with the
codebase to be sure that I didn't messed up or followed an incorrect build
processes (or even if this is an openembedded problem instead of an openmoko
one!).
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1265
------- Additional Comments From [EMAIL PROTECTED] 2008-03-12 18:44 -------
It is quite possible something is slowing the thing to a crawl, which would be
important to understand, but it shouldn't be this. The SECOND thing is an
interrupt from the PMU that happens once a second.
You can confirm this with cat /proc/interrupts.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1268
------- Additional Comments From [EMAIL PROTECTED] 2008-03-12 19:53 -------
This patch solved the problem for me.
#
# old_revision [be65002bdf2cc86e74c6837a77000ad7f649e754]
#
# patch "conf/distro/include/preferred-om-2008-versions.inc"
# from [45c4fabe80b7601dd86c45ad8f64a6773594d4e7]
# to [03aa6c652327fdca1d505eb10c4fdcc8147bbe24]
#
============================================================
--- conf/distro/include/preferred-om-2008-versions.inc
45c4fabe80b7601dd86c45ad8f64a6773594d4e7
+++ conf/distro/include/preferred-om-2008-versions.inc
03aa6c652327fdca1d505eb10c4fdcc8147bbe24
@@ -12,4 +12,5 @@ PREFERRED_VERSION_vte = "0.16.9"
PREFERRED_VERSION_pulseaudio = "0.9.9"
PREFERRED_VERSION_udev = "118"
PREFERRED_VERSION_vte = "0.16.9"
+PREFERRED_VERSION_glib-2.0 = "2.15.6"
+PREFERRED_VERSION_libogg = "1.1.3"
-
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1172
------- Additional Comments From [EMAIL PROTECTED] 2008-03-12 20:07 -------
Definate Heisenbug here and Im running out of ideas.
Booting a failing image will occasionally give working sound. I used objdump to
dissassemble the modules on working and non working images and found no
difference. Examined the driver code and can't see any obvious uninitialised
variables.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1269
Summary: No Audio
Product: Neo1973 Hardware
Version: GTA01Bv4
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Audio
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
The nightly builds hosted on buildhost, as of 29 Feb 2008, have no audio on
GTA01.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1269
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2008-03-12 23:42 -------
Fixed in OE.dev and will sync through to OM monotone tomorrow I hope.
A quick fix is to copy state files from OM SVN into /etc/
They are in trunk/src/target/audio/fic-gta01/
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1214
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2008-03-12 23:46 -------
Fixed in SVN rev 4197.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
[This e-mail has been automatically generated.]
You have one or more bugs assigned to you in the Bugzilla
bugsystem (http://bugzilla.openmoko.org/cgi-bin/bugzilla/) that require
attention.
All of these bugs are in the NEW state, and have not been touched
in 7 days or more. You need to take a look at them, and
decide on an initial action.
Generally, this means one of three things:
(1) You decide this bug is really quick to deal with (like, it's INVALID),
and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to someone
else. (Hint: if you don't know who to reassign it to, make sure that
the Component field seems reasonable, and then use the "Reassign bug to
owner of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
Just use the "Accept bug" command.
To get a list of all NEW bugs, you can use this URL (bookmark it if you like!):
http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?bug_status=NEW&[EMAIL
PROTECTED]
Or, you can use the general query page, at
http://bugzilla.openmoko.org/cgi-bin/bugzilla/query.cgi.
Appended below are the individual URLs to get to all of your NEW bugs that
haven't been touched for a week or more.
You will get this message once a day until you've dealt with these bugs!
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1012
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1081
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1107
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1127
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1133
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1136
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1158
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1162
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1189
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1193
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1197
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1199
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1200
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1201
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1206
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1212
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1215
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1216
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1217
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1218
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1250
------- Additional Comments From [EMAIL PROTECTED] 2008-03-13 11:46 -------
Mickey can you specify the brand and actual model number of the APs that work
and fail?
Also to be mega clear, "open" is a bit overloaded for Wifi, Open is an auth
mode but also "open" can mean no encryption informally. We mean "no
encryption" here I assume?
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
