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 1380] GSM modem sleeps on virtual channels in MUX
([EMAIL PROTECTED])
2. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
3. [Bug 1391] New: setting WEP key through iwconfig does not
work ([EMAIL PROTECTED])
4. [Bug 1391] setting WEP key through iwconfig does not work
([EMAIL PROTECTED])
5. [Bug 1391] setting WEP key through iwconfig does not work
([EMAIL PROTECTED])
6. [Bug 1391] setting WEP key through iwconfig does not work
([EMAIL PROTECTED])
7. [Bug 1391] setting WEP key through iwconfig does not work
([EMAIL PROTECTED])
8. [Bug 1391] setting WEP key through iwconfig does not work
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1380
------- Additional Comments From [EMAIL PROTECTED] 2008-05-12 21:03 -------
Multiple automated tests now confirm that the enter the sleep individually per
virtual channel, however once the first channel has been woken up
(either by receiving an unsolicited response or a command that is terminated
with \r\n [which will receive no response]), all virtual channels wake up.
Until we have a proper fix, I will work around this by using a dedicated
KeepAlive channel that keeps the modem alive (sic!) :(
I would consider one of the following solutions as a proper fix from the side of
the modem, with c) being the most wanted solution, a) or b) being acceptable and
d) being the very last resort.
a) stop sleeping on virtual channels and receive act on PSC wakeup, or
b) stop sleeping on virtual channels and send PSC sleep command, or
c) a) + b)
d) continue sleeping on virtual channels, but accept a special AT wakeup command
that does not send 'OK' if the modem is already woken up.
------- 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=1391
Summary: setting WEP key through iwconfig does not work
Product: OpenMoko
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
It is currently not possible to set a WEP key using iwconfig:
[EMAIL PROTECTED]:~# iwconfig eth0 key "supersecret"
Error for wireless request "Set Encode" (8B2A) :
invalid argument "supersecret".
[EMAIL PROTECTED]:~# iwconfig eth0 enc "supersecret"
Error for wireless request "Set Encode" (8B2A) :
invalid argument "supersecret".
This was tested with the following kernel package on GTA02:
[EMAIL PROTECTED]:~# opkg status kernel-image-2.6.24
Package: kernel-image-2.6.24
Version: 1:2.6.24+git20080511-r
------- 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=1391
------- Additional Comments From [EMAIL PROTECTED] 2008-05-13 10:57 -------
Anything in dmesg about it?
------- 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=1391
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
------- Additional Comments From [EMAIL PROTECTED] 2008-05-13 11:06 -------
I try this on a belkin AP temporarily configure for WEP, the following works
iwconfig eth0 key e14a790fa60e1b9697abeb7368
iwconfig eth0 essid <AP SID>
BTW WEP is very insecure...
------- 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=1391
------- Additional Comments From [EMAIL PROTECTED] 2008-05-13 11:16 -------
Isnt is supposed to be
iwconfig eth0 key s:supersecret
------- 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=1391
------- Additional Comments From [EMAIL PROTECTED] 2008-05-13 11:18 -------
Ah interesting, iwconfig eth0 key s:XXXXX works before iwconfig eth0 essid, but
not afterwards. This is clearly a bug.
------- 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=1391
------- Additional Comments From [EMAIL PROTECTED] 2008-05-13 11:47 -------
Created an attachment (id=612)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=612&action=view)
Fix to allow keys to be set after ESSID
Try the following patch. It works for me.
------- 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
