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. Openmoko Bug #1999: python-etk-git patches patched upstream
(Openmoko Public Trac)
2. Re: Openmoko Bug #1862: stop boot (Openmoko Public Trac)
3. Re: Openmoko Bug #1998: "Unable to mount root fs on
unknown-block(179, 2)" after hard shutdown (Openmoko Public Trac)
4. Re: Openmoko Bug #1780: cannot add number in
openmoko-contacts2 (Openmoko Public Trac)
5. Re: Openmoko Bug #1904: om2008.8 wifi don't get always an
ipv4 ip (Openmoko Public Trac)
--- Begin Message ---
#1999: python-etk-git patches patched upstream
---------------------+------------------------------------------------------
Reporter: ptitjes | Owner: julian_chu
Type: defect | Status: new
Priority: normal | Milestone:
Component: Distro | Version:
Severity: normal | Keywords:
Blockedby: | Reproducible: always
Blocking: |
---------------------+------------------------------------------------------
Patches for the python-etk-git package already have been patched upstream.
This makes its build fail.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1999>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1862: stop boot
--------------------------------+-------------------------------------------
Reporter: therippo | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: Om2008.9
Component: System Software | Version: GTA02v6
Severity: critical | Resolution:
Keywords: boot freeze | Blockedby:
Reproducible: | Blocking:
--------------------------------+-------------------------------------------
Comment(by therippo):
Apologies for late response.
Contacted dealer who suggests to charge OM when turned on, cuz instead
would not be loaded....
By suggestion fully updated the unit using http://www.qtopia.net/ which in
general much better, but remain very high my concerns about proper charge
of battery, lasting of the unit, because, without placing any phone calls,
just having casually sent or received a couple of SMS per test, bluetooth
disabled, WIFI disabled, the OM lasts, at best, 6-6:30 hours just in
standby.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1862#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1998: "Unable to mount root fs on unknown-block(179,2)" after hard shutdown
------------------------+---------------------------------------------------
Reporter: denver | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone: Om2008.8
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Comment(by andy):
/*
* Check feature flags regardless of the revision level, since we
* previously didn't change the revision level when setting the
flags,
* so there is a chance incompat flags are set on a rev 0
filesystem.
*/
features = EXT2_HAS_INCOMPAT_FEATURE(sb,
~EXT2_FEATURE_INCOMPAT_SUPP);
if (features) {
printk("EXT2-fs: %s: couldn't mount because of "
"unsupported optional features (%x).\n",
sb->s_id, le32_to_cpu(features));
goto failed_mount;
}
#define EXT2_FEATURE_INCOMPAT_SUPP (EXT2_FEATURE_INCOMPAT_FILETYPE| \
EXT2_FEATURE_INCOMPAT_META_BG)
Don't really know what it means, but I never saw it myself and Google is
pretty quiet about it, usually a sign it is the outcome of somthing funny.
Note the desktop box is doing a mount from userspace, so it's quite
possible it can try multiple times or take corrective action if it sees
insanity: we are having one go entirely from kernel so we might be a
little more fragile.
Check we are not somehow mixing up rootfstype= between ext2 and ext3, on
kernel commandline or in /etc/fstab in the root filesystem for example.
Another angle, IIRC Debian for example has initscript to remount the
rootfs rw, it is happy to have ro rootfs initially. I noticed in the ext2
code there are different rules for what it doesn't like if you mount ro.
So you might mask this behaviour if you add "ro" to your kernel
commandline to get the rootfs mounted read only initially.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1998#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1780: cannot add number in openmoko-contacts2
------------------------+---------------------------------------------------
Reporter: el | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Comment(by trs80):
I figured out a workaround - click Add Phone Number, then click somewhere
else. Go back to the phone number, enter it, but don't click away, instead
press the dropdown to the left.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1780#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1904: om2008.8 wifi don't get always an ipv4 ip
------------------------+---------------------------------------------------
Reporter: dolfje | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Comment(by andy):
If you can stick another box with WLAN in Monitor mode and observe
proceedings with the packetloss, it could be interesting. A random guess
can be problem with WEP decrypt on your key anyway on some packets? If
possible try changing your WEP key (on AP too) and see if that affects
anything.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1904#comment:10>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
