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 1363] New: Qemu on the internet
([EMAIL PROTECTED])
2. [Bug 1270] matchbox keyboard maps differently with USB
plugged in ([EMAIL PROTECTED])
3. [Bug 1270] matchbox keyboard maps differently with USB
plugged in ([EMAIL PROTECTED])
4. [Bug 1364] New: GTA01 SD card unrecognized on boot following
kernel flash ([EMAIL PROTECTED])
5. [Bug 1364] GTA01 SD card unrecognized on boot following
kernel flash ([EMAIL PROTECTED])
6. [Bug 1365] New: No way to manually suspend GTA01
([EMAIL PROTECTED])
7. [Bug 1366] New: GSM is unresponsive after resume on GTA01
([EMAIL PROTECTED])
8. [Bug 1363] Qemu on the internet
([EMAIL PROTECTED])
9. [Bug 1366] GSM is unresponsive after resume on GTA01
([EMAIL PROTECTED])
10. [Bug 79] suspend/resume to RAM support
([EMAIL PROTECTED])
11. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
12. [Bug 1360] "make" failed in package
linux-openmoko-2.6.24+git20080420
([EMAIL PROTECTED])
13. [Bug 1365] No way to manually suspend GTA01
([EMAIL PROTECTED])
14. [Bug 1359] Unable to unload the GTA01 audio module
snd_soc_neo1973_wm8753 ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1363
Summary: Qemu on the internet
Product: OpenMoko
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: qemu-neo1973
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
On the site (
http://wiki.openmoko.org/wiki/Qemu#Setting_up_Internet_connection_for_your_qemu_neo:
) stands an excellent manual for getting internet on the emulator qemu. But I
can't go past the command:
route add default gw 192.168.68.1
The emulated neo gives the following error:
route: SIOCADDRT: No such process
I've checked with the ifconfig and I've noticed that the loopback is the only
network 'connection'. (usb0 is down because we used the command ifdown usb0).
Normally I would expect another network device, so the route command shouldn't
give errors.
How can I still get internet on the neo (without having to setup the emulated
usb connection, because I and many others don't like messing in my kernel)
Nikos
------- 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=1270
------- Additional Comments From [EMAIL PROTECTED] 2008-04-21 18:36 -------
I have a bluetooth keyboard that I connected with while the neo was connected to
the usb, and I get the same (mis)behavior: typing "7 8 9 0" yields "{ [ ] } \"
(regardless of shift or caps-lock state).
------- 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=1270
------- Additional Comments From [EMAIL PROTECTED] 2008-04-21 18:39 -------
er, of course I meant 'typing "7 8 9 0 -"'
------- 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=1364
Summary: GTA01 SD card unrecognized on boot following kernel
flash
Product: OpenMoko
Version: 2007.2
Platform: Neo1973
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: u-boot
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Immediately following a GTA01 kernel flash (via USB from dfu-util on the host),
u-boot returns to the boot menu. Any attempt to boot from there without
powering down first results in the SD card being unrecognized. There is an
error message to that effect right before the kernel details are printed out (it
disappears quickly, so I don't have the exact verbiage), and eventually there's
a kernel panic as the rootfs fails to be mounted.
My rootfs is located on an SD card partition.
If the GTA01 is powered down after flashing, it will boot successfully
thereafter. It has not failed to do so yet.
This on a version of u-boot I built on April 2, 2008 -- the u-boot menu screen
shows ver. 1.3.2-rc2.
------- 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=1364
------- Additional Comments From [EMAIL PROTECTED] 2008-04-21 18:42 -------
I should add that I don't have a debug board, so I'm wary of trying new u-boot
versions unnecessarily, and hence I have not tried the very latest.
------- 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=1365
Summary: No way to manually suspend GTA01
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: neod
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
There is no way to manually suspend a GTA01 (at least that I know of) for a
"regular user" on the default image. This is important since a phone in a purse
or pocket is activated by keys or pocketbooks. Without a manual selection
option, it is quite possible that normal use will never be able to activate
suspend.
------- 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=1366
Summary: GSM is unresponsive after resume on GTA01
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]
When resuming from suspend, GSM is unresponsive. Wake-on-call, for instance,
wakes the device to the finger-lock screen but doesn't begin ringing. Sending an
SMS message to the device after resume does nothing. Panel applets show the
device is registered on the network but is still unresponsive.
------- 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=1363
------- Additional Comments From [EMAIL PROTECTED] 2008-04-22 01:26 -------
I believe this chapter (Setting up Internet Connection..) assumes that you've
already set up a normal network connection between the Neo1973 and the PC, and
it only covers setting up a NAT routing to the internet over that (pre-existing)
connection. (I haven't tried these instructions)
------- 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=1366
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
BugsThisDependsOn| |79
Severity|normal |major
------- Additional Comments From [EMAIL PROTECTED] 2008-04-22 02:58 -------
Very likely, there are multiple issues happening here.
First, as described in comment 34
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=79#c34) of bug
#79, you must have removed "console=ttySAC0,115200" from the bootargs in your
u-boot environment, otherwise spurious resume messages will be spewed into the
GSM during resume, which annoys it rather much and confused both it and gsmd.
Next, there is a problem in the GSM, UART, and suspend/resume logic that results
in an occasional buffer-overrun shortly after resume. The symptoms are that the
GSM "holds it in" while the Neo resumes, then when the serial driver initializes
the UART, it dumps whatever it has over the serial connection. This data
transmission is always ok, even if it is larger than the FIFO. The problem is
the next one -- usually sent some 200ms later, the next transmission overruns
the FIFO. It is not known if the problem is the GSM ignoring the desperate
attempts by the UART to flow control when the FIFO hits 14 characters, or if the
problem is that flow control never happens for some reason. In any case, this
transmission is truncated at 16 characters (the size of the FIFO), which usually
causes gsmd to become confused (the GSM is fine; it's waiting for the Neo to
talk to it; the problem is clearly gsmd that is out-to-lunch here). At some
point, gsmd calls the modem dead (it isn't), and exits. The application
(dialer? phonekit?) that's on the other end talking to gsmd reports an I/O
error, and it too goes off to the loony bin. At this point, you have a Neo that
is awake -- and you have no indication why, and the GUI looks like it's still
registered. But nothing is happening underneath, and a reboot is your only
recovery choice.
There may be other failure modes, but that's what I've been working on lately.
A custom kernel that seems to crash less often, and has much debugging support,
is available. Additional data-points may help solve this.
------- 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
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
OtherBugsDependingO| |1366
nThis| |
------- 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=1360
------- Additional Comments From [EMAIL PROTECTED] 2008-04-22 05:22 -------
I have exactly the same problem...
------- 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=1365
------- Additional Comments From [EMAIL PROTECTED] 2008-04-22 08:05 -------
Created an attachment (id=601)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=601&action=view)
basic patch for neod to manually suspend and disabled wifi
This is a beginning of a patch for neod. This patch invites a funtion to
determine the hardware version (yes, i think this could be done better) and
depending on this, disables the wifi button, and modify the gps button.
------- 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=1359
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2008-04-22 08:07 -------
patch is splited in openmoko's git tree...
------- 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
