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 728] New: user can open various openmoko-keyboard at
same time ([EMAIL PROTECTED])
2. [Bug 729] New: in Call History Mode there is no time/date
info ([EMAIL PROTECTED])
3. [Bug 712] librsvg build fails
([EMAIL PROTECTED])
4. [Bug 730] New: Hang-up and title/"app switch" buttons are too
near ([EMAIL PROTECTED])
5. [Bug 720] libmokogsmd fails to compile, missing file
'common/linux_list.h' ([EMAIL PROTECTED])
6. [Bug 731] New: sending numbers with DTMF
([EMAIL PROTECTED])
7. [Bug 681] the gsmhandset.state file has the volume turned up
too high, causing feedback ([EMAIL PROTECTED])
8. [Bug 733] New: Ignore call button
([EMAIL PROTECTED])
9. [Bug 719] dfu-util should be able to initiate a nand-erase
([EMAIL PROTECTED])
10. [Bug 256] GSM Modem doesn't seem to work on some devices
([EMAIL PROTECTED])
11. [Bug 605] initscripts not compatible to busybox
([EMAIL PROTECTED])
12. [Bug 697] Don't generate security key pairs on every device
boot ([EMAIL PROTECTED])
13. [Bug 703] RTC readings corrupt in userland
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=728
Summary: user can open various openmoko-keyboard at same time
Product: OpenMoko
Version: 2007.2
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-keyboard
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
User can open various openmoko-keyboard at same time.
One idea: when one keyboard is open, the keyboard launch icon disappears from
"Launch Task Page".
------- 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=729
Summary: in Call History Mode there is no time/date info
Product: OpenMoko
Version: 2007.2
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: openmoko-dialer
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Would be nice to know the time/date info in the Call History Mode.
------- 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=712
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-08-20 19:00 -------
Please update your MokoMakefile.
MokoMakefile now uses oe.dev without an overlay and with it the new OM-2007.2
user interface. In oe.dev librsvg builds (just verified):
NOTE: package librsvg-2.16.1: completed
------- 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=730
Summary: Hang-up and title/"app switch" buttons are too near
Product: OpenMoko
Version: 2007.2
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-dialer
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
In Call Mode and Outgoing Call Mode, the hang-up and title-"app switch" buttons
are too near. If the user is talking and have no stylus, clicking in the menu
button to switch to another app is a bit risky.
I suggest to place the hang-up button as in the "Incoming Call Mode": at the
right. The "Speaker Phone" button can be placed at left without risk if the app
ask the user before turn-on the speaker.
------- 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=720
------- Additional Comments From [EMAIL PROTECTED] 2007-08-20 19:07 -------
Created an attachment (id=254)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=254&action=view)
local.conf
I am also seeing the same problem, I removed the parallel flags and get the
same result.
------- 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=731
Summary: sending numbers with DTMF
Product: OpenMoko
Version: 2007.2
Platform: PC
OS/Version: Linux
Status: NEW
Severity: wishlist
Priority: P2
Component: openmoko-contacts
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Would be nice if the user can send a "phone" number with DTMF if there is a
call.
This can be used to send passwords "hidden" as phone numbers in the contacts
app.
------- 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=681
------- Additional Comments From [EMAIL PROTECTED] 2007-08-20 19:14 -------
Please try the new gsmheadset.state (committed to oe.dev) and close the bug, if
that fixes your 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=733
Summary: Ignore call button
Product: OpenMoko
Version: 2007.2
Platform: PC
OS/Version: Linux
Status: NEW
Severity: wishlist
Priority: P2
Component: openmoko-dialer
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
An incoming call could be ignored, just pressing(touching?) a button when the
phone is ringing. The GSM call is active, but you can use the apps in phone
normaly.
Maybe an icon in the top panel area that allow you to pick up the call.
There is page in the wiki related:
http://wiki.openmoko.org/wiki/Wishlist:Ignore_Call_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=719
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |blocker
------- Additional Comments From [EMAIL PROTECTED] 2007-08-20 22:01 -------
Here another report that might be related to this issue from the device-owners
list (does not appear in
the web archives yet).
If this bug is already fixed by a newer uboot version, this should be made
public in the Wiki and by an
announcement on the lists...
Von: [EMAIL PROTECTED]
Betreff: Flashing Adventure (was Re: A few more First-Day issues)
Datum: 17. August 2007 12:17:14 MESZ
An: [EMAIL PROTECTED]
Hi List,
This thread is a good point to post my experiences in the first days of
Neo1973 ownership.
The issue that I had is about flashing the device. I initially flashed
(with dfu) the *-moko10-* kernel while the rootfs holds modules for
*-moko11-*. The device booted ok but of course there were no modules to
load.
So I flashed the *-moko11-* image to the nand partition reserved for the
kernel. And this is where the trouble started ...
Even though I flashed the *-moko11-* image and dfu reported no errors the
Neo still seemed to have the old *-moko10-* image in the nand. I flashed
the *-moko11-* image again, but no success. Now my idea was to
deliberately delete the nand with 'nand erase kernel' in u-boot.
Afterwards I flashed the *-moko11-* image once again with dfu.
Now when I switched on the Neo it stopped with a 'Bad magic number'
message an immediately powered down again (i.e. i guess the content of the
kernel partition got loaded in memory but could't get verified/executed or
similar). No reflashing of the kernel helped to get the Neo out of this
state, even though dfu reported successful flashing all the time (w. and
w/o executing a 'nand erase kernel' beforehand).
Well, I finally revived my Neo by putting the *-moko11-* image on the SD
card, and writing the image from there via memory into the nand as
described in
http://wiki.openmoko.org/wiki/U-boot#Commands_on_the_bootloader_prompt.
Trying to read the image into memory (ext2load mmc 0 0x32000000 uImage)
and then directly starting it from there (bootm 0x32000000) I got the
penguin and a blinking underscore curser. Doing the full procedure of
writing the kernel to nand after loading it into memory left me with a
bootable kernel again.
However, now the boot process stopped with a kernel panic because init
couldn't be started. So I guess now the rootfs was damaged/erased.
Reflashing it with the dfu tool resolved the problem and the Neo was
revived again.
Now I'm really curious what I did wrong and what the cause of my problems
was. Actually I have no clue and according to my understanding all steps I
took (1.) reflashing the kernel, 2.) loading a kernel into memory and
booting from memory) should have worked in the first place and what even
confuses me more was the need to reflash the rootfs, even though this
wasn't touched in the whole procedure (and yes, I always did a -a 3 in
dfu-util).
Hope to learn something from you guys,
Cheers,
Martin
--- Peter Rasmussen <[EMAIL PROTECTED]> wrote:
Then, when I will eventually be able to build a kernel, I am wondering:
is the only way to change to it, by loading it through the dfu-util, or
is it also possible by using a more "desktop like method", like building
a kernel, putting it in somewhere, eg. /boot, update /etc/lilo.conf, run
lilo and then reboot?
As someone already pointed out you can Boot from the SD card.
I doubt you'll get to the same process as you may be used to on a desktop
Linux
system, because on an embedded system it isn't simply a process of adding
a new
kernel image to the filesystem and pointing the bootloader at it. The
bootloader is configured to always boot the image that resides at a
specific
location in the nand flash. Now, while you _could_ add more kernel images
to
the nand flash, you would need to repartition the flash each time you
added
one. And that isn't as simple as doing it on a disc based system either.
One thing that may be worth exploring is modding u-boot to support Flash
from
SD card, I don't think it does this just yet, but most of the code needed
to do
it will be there, then your reflash proceedure would be to upload the
files to
the SD card, and reboot into the u-boot menu and choose the appropriate
option.
I think this is the closest to the familiar procedure as you are likely to
get.
I am hoping to eventually be able to run everything natively on the
Neo1973, just like on a desktop. Hey, it runs 266MHz so it should have
plenty horsepower to build its own kernel :-)
Yes, the Neo does have the horsepower, but I would advise against trying
this.
Compilation, especially large builds like Linux kernels, are very disc IO
intensive, and the one thing you should avoid on NAND flash based systems
is
disc IO intensive operations. They are slow and you will eventually wear
out
the NAND flash. Of course, you could try and configure it to use a RAM
drive as
a cache and scratchpad for all the temporary files.
------- 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=256
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
Version|GTA01Bv3 |GTA01Bv4
------- Additional Comments From [EMAIL PROTECTED] 2007-08-20 22:49 -------
I have a phase 1 hardware and I haven't succeeded in making the GSM modem work
either by following the instructions listed in the wiki
(http://wiki.openmoko.org/wiki/Manually_using_GSM) or here
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=256). Following
the instructions from bug 256, however, I have managed to get a list of carriers
using AT+COPS=? (by enabling flow control after doing a cu). Also I only get the
"connected" message and never get the "Interpreter Ready" message. Here is a
log:
[EMAIL PROTECTED]:~$ cu -l /dev/ttySAC0
Connected.
OK
ATE1
OK
AT+CFUN=1
OK
AT+CPIN="...."
ERROR
AT+COPS
OK
AT+COPS=?
+COPS: (2,"Cingular","Cingular","310410"),(1,"T-Mobile ","T-Mobile","31026")
ATDXXXXXXXXXX
NO CARRIER
ATD+1XXXXXXXXXX
NO CARRIER
ATH
OK
Is something wrong with GTA01Bv4 or my hardware has a faulty GSM modem ?
------- 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=605
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-08-21 00:26 -------
OM-2007.2 uses angstrom in oe HEAD which has this problem fixed (real ps
installed)
------- 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 ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=697
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Component|kernel |sysinit
Resolution| |INVALID
------- Additional Comments From [EMAIL PROTECTED] 2007-08-21 00:42 -------
I'm not sure what exactly you mean by that. What security key pairs?
If you mean the dropbear ssh keys they are only generated if they don't exist.
(See /etc/init.d/dropbear):
test -f $DROPBEAR_RSAKEY || dropbearkey -t rsa -f $DROPBEAR_RSAKEY
test -f $DROPBEAR_DSSKEY || dropbearkey -t dss -f $DROPBEAR_DSSKEY
I'm going to close this as invalid for now. If this is not your issue please
feel free to clarify and reopen. I also changed the component to sysinit.
------- 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=703
------- Additional Comments From [EMAIL PROTECTED] 2007-08-21 01:06 -------
[EMAIL PROTECTED]:~$ hwclock
Tue Aug 21 00:12:55 2007 0.000000 seconds
[EMAIL PROTECTED]:~$ hwclock
Tue Aug 21 00:12:59 2007 0.000000 seconds
[EMAIL PROTECTED]:~$ dmesg -c
<4>pcf50606_rtc_read_time: PCF_TIME: 21.07.07 00:12:55
<4>pcf50606_rtc_read_time: RTC_TIME: 21.7.107 0:12:55
<4>pcf50606_rtc_read_time: PCF_TIME: 21.07.07 00:12:59
<4>pcf50606_rtc_read_time: RTC_TIME: 21.7.107 0:12:59
Hmm, it works for me...
Using 2.6.22.1-moko10
------- 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
