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. Re: Openmoko Bug #2043: GTA02 WiFi signal reception too weak
(Openmoko Public Trac)
2. Openmoko Bug #2044: om-locations - map licensing
(Openmoko Public Trac)
3. Re: Openmoko Bug #2043: GTA02 WiFi signal reception too weak
(Openmoko Public Trac)
4. Openmoko Bug #2045: [Om2008.9] Wifi associating is very
unreliable (Openmoko Public Trac)
5. Re: Openmoko Bug #2044: om-locations - map licensing
(Openmoko Public Trac)
6. Re: Openmoko Bug #2045: [Om2008.9] Wifi associating is very
unreliable (Openmoko Public Trac)
7. Re: Openmoko Bug #1884: [suspend/resume] if press power
batton right after suspend, the device won't wake up
(Openmoko Public Trac)
--- Begin Message ---
#2043: GTA02 WiFi signal reception too weak
------------------------+---------------------------------------------------
Reporter: vnevoa | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Comment(by andy):
Not really excusing the behaviour, but two ideas:
Signal quality reported for AR6000 driver is probably bogus.
The firmware can choose to hide results from the iwlist eth0 scan.
iwl4965 does this, sometimes to the point it gets confused and hides
everything, but will connect by ap mac. So it may not represent what it
really sees there either.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2043#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2044: om-locations - map licensing
---------------------+------------------------------------------------------
Reporter: drlizau | Owner: openmoko-devel
Type: task | Status: new
Priority: normal | Milestone: Om2008.9
Component: unknown | Version:
Severity: normal | Keywords:
Blockedby: | Reproducible:
Blocking: |
---------------------+------------------------------------------------------
The maps from OpenStreetMap used in om-locations require attribution
according to the CC-by-SA licence.
The wiki page indicates that the maps come from OSM. There does need to be
indication with the downloaded maps that they are from OSM.
May I suggest that in the package information which is read prior to
download through assassin this information is included
for example
om-maps-london
Openmoko Software 20080430-r0
Download size 17156KB
Map of London, for use with Locations application.
Data from OpenStreetMap.org, licenced CC-by-SA.
reference:
http://wiki.openstreetmap.org/index.php/Common_licence_interpretations#I_want_to_use_OSM_data_with_my_GPS_routing.2Fmapping.2Fother_application.__Do_I_have_licence_the_application_under_the_OSM_licence.3F
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2044>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2043: GTA02 WiFi signal reception too weak
------------------------+---------------------------------------------------
Reporter: vnevoa | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Comment(by vnevoa):
We should check if those reports are bogus or not. Is there a way to check
these values?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2043#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2045: [Om2008.9] Wifi associating is very unreliable
-----------------------------+----------------------------------------------
Reporter: Matthias | Owner: openmoko-kernel
Type: defect | Status: new
Priority: highest | Milestone:
Component: System Software | Version:
Severity: major | Keywords:
Blockedby: | Reproducible: sometimes
Blocking: |
-----------------------------+----------------------------------------------
I'm using the Wifi-method described in
http://wiki.openmoko.org/wiki/Neo_FreeRunner_Wifi#Using_WPA_and_.2Fetc.2Fnetwork.2Finterfaces
i.e. having a working config file /etc/wpa_supplicant/wpa_supplicant.conf
for all my known access points (which is just a copy of that I'm using
daily and stable in my two FreeBSD based laptops); and I'm trying to bring
up the eth0 with
# ifup eth0
this works very unreliable; in (let's say) 8 of 10 cases it can't
associate to the AP, even not after fresh re-boots and independently if
the AP at my home works with WEP or in my office with WPA;
I'm attaching:
relevant part of /etc/network/interfaces
iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
pre-up iwconfig eth0 essid off
up route del default gw 192.168.0.200
down route add default gw 192.168.0.200
iface eth1 inet dhcp
relevant part of /etc/wpa_supplicant/wpa_supplicant.conf
network={
priority=99
ssid="santaclara"
key_mgmt=WPA-PSK
psk="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
}
output of 'iwlist eth0 scan'
eth0 Scan completed :
Cell 01 - Address: 00:04:E2:A1:76:0B
ESSID:"santaclara"
Mode:Master
Frequency:2.442 GHz (Channel 7)
Quality=19/94 Signal level=-76 dBm Noise level=-95
dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
output of 'ifup eth0':
[EMAIL PROTECTED]:~# ifup eth0
WPA: Configuring Interface
wpa_supplicant: using default driver type: wpa-driver wext
wpa_supplicant: /usr/sbin/wpa_supplicant -B -P
/var/run/wpa_supplicant.eth0.pid -i eth0 -D wext -c /etc/wpa_supplicant
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
wpa_supplicant: ctrl_interface socket located at
/var/run/wpa_supplicant/eth0
udhcpc (v1.9.1) started
run-parts: /etc/udhcpc.d/00avahi-autoipd exited with return code 1
Sending discover...
Sending discover...
Sending discover...
No lease, failing
and a full debug log of a session:
[EMAIL PROTECTED]:~# /usr/sbin/wpa_supplicant -d -P
/var/run/wpa_supplicant.eth0.pid -i eth0 -D wext -c
/etc/wpa_supplicant/wpa_supplicant.conf -C /var/run/wpa_supplicant >
wpadebug.txt
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2045>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2044: om-locations - map licensing
------------------------+---------------------------------------------------
Reporter: drlizau | Owner: julian_chu
Type: task | Status: new
Priority: highest | Milestone:
Component: Distro | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Changes (by zecke):
* cc: olv, tick (added)
* owner: openmoko-devel => julian_chu
* priority: normal => highest
* component: unknown => Distro
* milestone: Om2008.9 =>
Comment:
I will move this to "Distro" as this is where the package comes from. We
should have CC-by-SA in the LICENSE field. The question is where the
attribution needs to happen? Is it good enough to put attribution into the
package description or should the application using the data attribute
openstreetmap?
I will try to discuss with the engineers involved. Sorry about not
honoring the license, we should do better.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2044#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2045: [Om2008.9] Wifi associating is very unreliable
--------------------------------+-------------------------------------------
Reporter: Matthias | Owner: openmoko-kernel
Type: defect | Status: new
Priority: highest | Milestone:
Component: System Software | Version:
Severity: major | Resolution:
Keywords: | Blockedby:
Reproducible: sometimes | Blocking:
--------------------------------+-------------------------------------------
Comment(by Matthias):
I've re-booted the FR and without any kind of changes in software now I
have one working case:
[EMAIL PROTECTED]:~# ifdown eth0
WPA: Terminating
wpa_supplicant: terminating wpa_supplicant daemon via pidfile
/var/run/wpa_supplicant.eth0.pid
stopped /usr/sbin/wpa_supplicant (pid 1516)
[EMAIL PROTECTED]:~# ifup eth0
WPA: Configuring Interface
wpa_supplicant: using default driver type: wpa-driver wext
wpa_supplicant: /usr/sbin/wpa_supplicant -B -P
/var/run/wpa_supplicant.eth0.pid -i eth0 -D wext -c
/etc/wpa_supplicant/wpa_supplicant.conf -C /var/run/wpa_supplicant
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
wpa_supplicant: ctrl_interface socket located at
/var/run/wpa_supplicant/eth0
udhcpc (v1.9.1) started
run-parts: /etc/udhcpc.d/00avahi-autoipd exited with return code 1
Sending discover...
Sending select for 10.0.1.217...
Lease of 10.0.1.217 obtained, lease time 7200
run-parts: /etc/udhcpc.d/00avahi-autoipd exited with return code 1
adding dns 10.0.1.201
adding dns 192.87.44.17
adding dns 192.168.52.230
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2045#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1884: [suspend/resume] if press power batton right after suspend, the device
won't wake up
--------------------------------+-------------------------------------------
Reporter: wendy_hung | Owner: andy
Type: defect | Status: new
Priority: high | Milestone: Om2008.10
Component: System Software | Version: Om2008.8
Severity: critical | Resolution:
Keywords: | Blockedby:
Reproducible: sometimes | Blocking:
--------------------------------+-------------------------------------------
Comment(by matt_hsu):
Problem statement:
This issue is result from the INT is trapped in the PMU when system is
getting into suspend. During the time of getting into suspend, there's a
window that the I2C device is suspended. This interrupt from PCF50633
can't be READ & CLEAR in this moment. So you could not wake the system
anymore.
In my opinion, there are three approaches which could resolve this
issue.
1. Like HXD8, add an alternative INT pin to S3C2442. This this pin
as a wakeup source.
2. Extend the debounce time of ONKEY. But this will change the
behavior of users.
3. Use bitbang to R&C the INT register of PMU in the last
moment(this sounds crazy).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1884#comment:12>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
