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 #2160: bluetooth is powered up on resume and
bootup (Openmoko Public Trac)
2. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
3. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
4. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
5. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
6. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
7. Openmoko Bug #2161: [wifi] wpa_supplicant PEM decoding error
(Openmoko Public Trac)
8. Re: Openmoko Bug #2161: [wifi] wpa_supplicant PEM decoding
error (Openmoko Public Trac)
--- Begin Message ---
#2160: bluetooth is powered up on resume and bootup
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: highest | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
Comment(by andy):
Well, it's better you use andy-tracking with the new Regulator PSU stuff
on it, but this is actually broken there right now as well. If nobody
beats me to it I will solve it in the next few days.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2160#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1841: white screen of death (WSOD) after resume
-----------------------+----------------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: GTA02v5
Severity: critical | Keywords: wsod,resume
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------+----------------------------------------------------
Comment(by joerg):
could we please fix this ever incrementing integer, like e.g. by moving
the "++" out of the "if" down to the "then" branch?
Didn't check new version, old one was hard enough for me to read.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:106>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1841: white screen of death (WSOD) after resume
-----------------------+----------------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: GTA02v5
Severity: critical | Keywords: wsod,resume
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------+----------------------------------------------------
Comment(by andy):
If you had checked it, you'd've seen there was nothing to complain about.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:107>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1841: white screen of death (WSOD) after resume
-----------------------+----------------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: GTA02v5
Severity: critical | Keywords: wsod,resume
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------+----------------------------------------------------
Comment(by nelg):
Hi Andy,
I would like to give your kernel a try to see if it fixed my WSOD. I've
looked on http://people.openmoko.org/andy/, but am unsure if I should be
using qi or u-boot, and which version, as you have a few on your page. I
have a GTA02v6.
Which boot loader and kernel would you suggest?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:108>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1841: white screen of death (WSOD) after resume
-----------------------+----------------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: GTA02v5
Severity: critical | Keywords: wsod,resume
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------+----------------------------------------------------
Comment(by andy):
Right this second this kernel
http://people.openmoko.org/andy/uImage-moredrivers-GTA02_andy-
tracking_49cff03d0e867b06.bin
and you can either try U-Boot if you adjust the environment to pull >
2MByte kernel, or you can give Qi a try, it would be the one qi-
s3c2442-master-*.udfu DFU'd into the U-Boot partition (you can always
replace it with U-Boot image http://people.openmoko.org/andy/u-boot-
gta02v5v6-stable_650149a53dbdd48b.udfu to go back).
If you go the Qi route, it tries first to boot from the first three
partitions of SD Card, looking at any ext2 / 3 partition on there for
/boot/uImage-GTA02.bin... if it finds it, it will try to boot it and use
that partition as the rootfs.
If none of the first three SD partitions have the kernel file, it will
boot from the NAND kernel partition as usual.
I added a README in the web dir to help future travellers as well.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:109>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1841: white screen of death (WSOD) after resume
-----------------------+----------------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: GTA02v5
Severity: critical | Keywords: wsod,resume
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------+----------------------------------------------------
Comment(by nicolas.dufresne):
Replying to [comment:106 joerg]:
> Didn't check new version, old one was hard enough for me to read.
This is the exact reason there is a second patch ;) Actually I remember
someone at the OLS last year telling that if you are not satisfied of a
patch, you should not release it because it might go upstream "as-is".
Well, sometimes you have to do this mistake to really learn.
Note also that the first version was breaking other things (like
resolution switching including rotation).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:110>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2161: [wifi] wpa_supplicant PEM decoding error
---------------------+------------------------------------------------------
Reporter: ksnieck | Owner: julian_chu
Type: defect | Status: new
Priority: normal | Milestone:
Component: Distro | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
---------------------+------------------------------------------------------
I have wpa_supplicant setup exactly the same as on a working system to
connect to a WPA2 enterprise AP that uses certificates for authentication.
I get the following relevant error bits from -ddd
Failed to read client cert/key in PEM format: Base64 decoding error.
Failed to read client cert/key in DER format: ASN1 parser: Error in DER
parsing.
TLS: Failed to set TLS connection parameters
EAP-TLS: Failed to initialize SSL.
I found the base64 command to be missing from the default software install
and think that might be the problem. (the certs are in PEM format)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2161>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2161: [wifi] wpa_supplicant PEM decoding error
---------------------+------------------------------------------------------
Reporter: ksnieck | Owner: julian_chu
Type: defect | Status: new
Priority: normal | Milestone:
Component: Distro | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
---------------------+------------------------------------------------------
Comment(by ksnieck):
I can also reproduce this error on my laptop (which usually successfully
connects) by temporarily moving /usr/bin/base64 so it cannot find it. It
seems then that including /usr/bin/base64 would fix this.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2161#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
