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 #2254: No usb pressed/released event with
2.6.28/2.6.29 (Openmoko Public Trac)
2. Re: Openmoko Bug #2253: Very high, silent beep when screen in
horizontal mode (xrand -3) (Openmoko Public Trac)
3. Re: Openmoko Bug #2209: alsactl restore wakes up X
(Openmoko Public Trac)
4. Re: Openmoko Bug #2229: GSM was working fine for months,
suddenly will not register using any GSM stack (Openmoko Public Trac)
5. Re: Openmoko Bug #2209: alsactl restore wakes up X
(Openmoko Public Trac)
6. Re: Openmoko Bug #2209: alsactl restore wakes up X
(Openmoko Public Trac)
7. Re: Openmoko Bug #2209: alsactl restore wakes up X
(Openmoko Public Trac)
8. Openmoko Bug #2255: xf86-video-glamo/703acea13: xrandr -o 1;
xrandr -o 3 causes distortion (Openmoko Public Trac)
--- Begin Message ---
#2254: No usb pressed/released event with 2.6.28/2.6.29
---------------------+------------------------------------------------------
Reporter: Defiant | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone: FSO
Component: unknown | Version: unspecified
Severity: normal | Keywords: usb event4 2.6.28 pressed released
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
---------------------+------------------------------------------------------
Hello,
Hardware: Freerunner
Distribution: Debian (but kernel issue)
With the 2.6.24 kernel in Debian I always got an event when inserting or
removing the usb plug.
With the current 2.6.28 in debian I no longer get this event.
I also tried the andy-tracking-15ca3dafb2662db4 2.6.29 from 7.3.2009, no
change.
I tried with
hexdump /dev/input/event4
I guess this is a bug and not an intended change?
If you need additional information please let me know.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2254>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2253: Very high, silent beep when screen in horizontal mode (xrand -3)
---------------------+------------------------------------------------------
Reporter: rhk | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
---------------------+------------------------------------------------------
Comment(by rhk):
Ok, finally got -29 kernel installed from http://people.openmoko.org/andy
/uImage-moredrivers-GTA02_andy-tracking-d1a9cf85c8608601.bin with modules
from http://people.openmoko.org/andy/modules-GTA02_andy-tracking-
d1a9cf85c8608601.tar.gz
This Terminator is a tough one :)
Newer kernel changed it so that no matter if I try -o 3 or -o 1 it makes
the same very high beep and -o 0 and -0 2 stops it. It might be a little
quieter than with the old kernel or it's just my ears getting destroyed
slowly by the beep, making me insane :) No, it's really not THAT bad but I
really wouldn't like to hear it when speaking on the phone.
md5sum /dev/random - no effect
pressing around the screen/phone - no effect
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2253#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2209: alsactl restore wakes up X
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by joerg):
wakeup also happens without X running, e.g on FSO-console.
Traced down (one?) reason to be changing alsa control.66/67 'Capture Right
Mixer' (/Left)
reproduce:
FSO-console MS5, log in via ssh, start alsamixer, wait until screen goes
dark, tweak
'Capture Right Mixer' -> screen comes up again.
(this been tested on GSM-FW uSD image)
Note there's another bug in alsa implementation of control.66/7
Maybe this one a side effect
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2209#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2229: GSM was working fine for months, suddenly will not register using any GSM
stack
----------------------+-----------------------------------------------------
Reporter: danek2 | Owner: hardware
Type: defect | Status: new
Priority: normal | Milestone:
Component: hardware | Version: GTA02v5
Severity: normal | Keywords: calypso, gsm, registration
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
----------------------+-----------------------------------------------------
Comment(by danek2):
I recently saw a message on the support list giving instructions on how to
fix u-boot environment from the NOR u-boot console. I did this and can now
successfully boot from NAND u-boot for the first time in several months.
(See http://lists.openmoko.org/nabble.html#nabble-td2391517)
I was excited, as I was hoping that fixing the u-boot environment would
somehow make GSM start working again, even though booting from NAND had
stopped working a couple of months before GSM stopped working.
Unfortunately, after booting the phone, and reflashing a few times, I
still could not get GSM to register.
I am attaching a new log file taken from logread after the u-boot env fix.
It still seems to be doing the same thing.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2229#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2209: alsactl restore wakes up X
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by joerg):
btw as it is triggered by *change* of control.66, repeated restoring of
gsmhandset.state will produce the effect only on first action.
It's not alsactl that is triggering this, it's the _change_ of some mixer
controls.
Verified by repeated
"alsactl restore -f gsmhandset.state"
and an occasional
"alsactl restore -f mymodified-foo.state"
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2209#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2209: alsactl restore wakes up X
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
I think to wake up framebuffer, something is likely generating an input
event.
The two things floating around we generate input events for there are
headphone and HOLD.
I wonder if when we select the Capture action, we power MICBIAS, and we
see a HOLD event or by another path headphone event.
You can confirm it by hexdumping the appropriate /dev/input/event and then
doing the alsamixer.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2209#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2209: alsactl restore wakes up X
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by lindi):
Thanks,
{{{
fd = os.open("/dev/input/event4", os.O_NONBLOCK | os.O_RDONLY)
fcntl.ioctl(fd, 0x40044590, 1) # EVIOCGRAB
}}}
seems to be a temporary userland fix that prevents X and tty from seeing
this event. (They won't see AUX or POWER either obviously.)
When I switch from gsmhandset to stereoout I see keycode 119 release.
When I do the opposite I see keycode 119 press.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2209#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2255: xf86-video-glamo/703acea13: xrandr -o 1; xrandr -o 3 causes distortion
---------------------+------------------------------------------------------
Reporter: lindi | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
---------------------+------------------------------------------------------
[ I hope it is appropriate to use docs.openmoko.org for Xorg driver bugs
even though openmoko inc. is not shipping it yet. ]
Steps to reproduce:
1) xrandr -o 1
2) xrandr -o 3
Expected results:
2) http://iki.fi/lindi/openmoko/xf86-video-
glamo/xrandr-o3-distortion/03080002.jpg
Actual results:
2) http://iki.fi/lindi/openmoko/xf86-video-
glamo/xrandr-o3-distortion/03080001.jpg
More info:
1) If I do "xrandr -o 0; xrandr -o 3" I don't hit this problem.
2) kernel is from andy-tracking c1b03e4da
3) X is from debian experimental, xserver-xorg-core 2:1.5.99.902-1
4) xf86-video-glamo is 703acea13
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2255>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
