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 79] suspend/resume to RAM support
([EMAIL PROTECTED])
2. [Bug 1250] No Wifi in Managed Mode
([EMAIL PROTECTED])
3. [Bug 79] suspend/resume to RAM support
([EMAIL PROTECTED])
4. [Bug 1349] New: Multitap keypad disappears on password fields
([EMAIL PROTECTED])
5. [Bug 79] suspend/resume to RAM support
([EMAIL PROTECTED])
6. [Bug 1350] New: bt module does not enumerate
([EMAIL PROTECTED])
7. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
8. [Bug 1024] gsm modem oscillating between registrated /
not-registrated ([EMAIL PROTECTED])
9. [Bug 1309] gprs dialin responses "ERROR"
([EMAIL PROTECTED])
10. [Bug 1024] gsm modem oscillating between registrated /
not-registrated ([EMAIL PROTECTED])
11. [Bug 79] suspend/resume to RAM support
([EMAIL PROTECTED])
12. [Bug 79] suspend/resume to RAM support
([EMAIL PROTECTED])
13. [Bug 1024] gsm modem oscillating between registrated /
not-registrated ([EMAIL PROTECTED])
14. [Bug 1349] Multitap keypad disappears on password fields
([EMAIL PROTECTED])
15. [Bug 1349] Multitap keypad disappears on password fields
([EMAIL PROTECTED])
16. [Bug 1350] bt module does not enumerate
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=79
------- Additional Comments From [EMAIL PROTECTED] 2008-04-16 13:59 -------
i just did this via ssh:
/etc/init.d/xserver-nodm stop
apm -s; fbset vga
*press key*
and voila ... screen is back! :D
------- 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=1250
------- Additional Comments From [EMAIL PROTECTED] 2008-04-16 18:19 -------
Mickey, I would once again need a sniffing dump of your failing association.
Also, could you let me know if your AP is running in 11g mode only ?
------- 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=79
------- Additional Comments From [EMAIL PROTECTED] 2008-04-16 21:04 -------
Created an attachment (id=595)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=595&action=view)
fix resume of fbdev
I played a bit with the fbdev resume. With this patch the neo doesn't get this
white screen on resume from console and from X.
------- 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=1349
Summary: Multitap keypad disappears on password fields
Product: OpenMoko
Version: current svn head
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: libgtkinput
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Multitap kepad disappears when in a password field. There is no way to get it
back.
------- 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=79
------- Additional Comments From [EMAIL PROTECTED] 2008-04-16 22:09 -------
Thanks guys you have done some great work here. I believe I captured all of
these patches into the andy/stable/andy-tracking now.
On the GSM wakeup thing, have a look through your .config and make sure about
CONFIG_S3C_LOWLEVEL_UART_PORT=x
Where x should somehow be 0 or 2 depending on if you are GTA01 or not. It
says where late suspend messages should go... maybe it makes sense to try to
disable CONFIG_S3C2410_PM_DEBUG and see if it helps with the suspend issue
too.
------- 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=1350
Summary: bt module does not enumerate
Product: OpenMoko
Version: current svn head
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
on 2.6.24+git20080416-r0
echo 1 > /sys/bus/platform/drivers/neo1973-pm-bt/neo1973-pm-bt.0/power_on
does not get the bt module enumerated on usb
dmesg shows that it allegedly set 900 into ldo4 -> 0.9V ?
echo 3200 >
/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/voltage_ldo4
echo 1 > /sys/bus/platform/drivers/neo1973-pm-bt/neo1973-pm-bt.0/reset
echo 0 > /sys/bus/platform/drivers/neo1973-pm-bt/neo1973-pm-bt.0/reset
gets bt enumerated on usb
-> some bug in the sysfs logic for neo1973-pm-bt?
------- 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 ---
[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
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1276
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1292
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1024
------- Additional Comments From [EMAIL PROTECTED] 2008-04-17 05:04 -------
Status update:
[EMAIL PROTECTED] finish the analysis of the trace, they didn't see something
abnormal in
protocol layer.They think the problem could be in L1 layer or our hw. TI will do
more testing with neo device, and compared to their EVB.
------- 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=1309
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
------- 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=1024
------- Additional Comments From [EMAIL PROTECTED] 2008-04-17 05:15 -------
[EMAIL PROTECTED] also said, the cell reselection is OK and only "searching for
network" is
abnormal.
------- 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=79
------- Additional Comments From [EMAIL PROTECTED] 2008-04-17 07:26 -------
Created an attachment (id=596)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=596&action=view)
Updated kernel config file for the GTA01 to resolve GSM resume problem
Some of the low-level debug stuff for the S3C2410 gets in the way of the GSM
device on the serial port during resume from suspend. Disabling selected
low-level debug items prevents this.
The operative config item is the disabling of CONFIG_DEBUG_LL; this has the
side effect of removing the CONFIG_S3C2410_PM_DEBUG config item due to
dependency.
Signed-off-by: Mike Westerhof <[EMAIL PROTECTED]>
------- 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=79
------- Additional Comments From [EMAIL PROTECTED] 2008-04-17 07:33 -------
The final kernel config change for the GTA01 brings the device to the same point
that the GTA02 was at some days ago -- suspend/resume seems to work, however
since there is no gsmd support yet for suspend, anything will wake the device
from suspend.
One of my devices (T-Mobile SIM) will suspend, but will not resume on an SMS
message. It will resume, however, on an incoming call -- but the device is so
slow coming out of the deep standby state that you usually cannot answer the
call before it is missed.
The other device (Cingular/AT&T SIM) will suspend and immediately resume. Once
in a long while it will actually stay suspended for a few minutes before some
activity on the GSM device wakes it back up.
So, at this point, the major issues with the GTA01 kernel are addressed. We
still need feedback from the community, but while that is happening, the next
items to work on include determining what else is supposed to wake the device,
and testing those wake events, as well as testing other general GTA01 functions
for recovery over suspend/resume (gllin, bluetooth, usb networking).
------- 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=1024
------- Additional Comments From [EMAIL PROTECTED] 2008-04-17 08:26 -------
Thanks for the update.
Yes, I would expect the device to frequently reselect based on cell tower signal
strength. Automatically dropping registration every couple of seconds is what
worries me.
------- 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=1349
------- Additional Comments From [EMAIL PROTECTED] 2008-04-17 08:29 -------
Created an attachment (id=597)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=597&action=view)
Normal field
------- 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=1349
------- Additional Comments From [EMAIL PROTECTED] 2008-04-17 08:30 -------
Created an attachment (id=598)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=598&action=view)
Password field
------- 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=1350
------- Additional Comments From [EMAIL PROTECTED] 2008-04-17 09:33 -------
Heh I recognize this issue, it has a surprising reason. You can make this
happen if the first time after boot you do
echo 1>/sys...
and not
echo 1 >/sys...
It's not actually a kernel issue if I understood it.
------- 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
