stable-tracking test image

Lech Karol Pawłaszek ike at szluug.org
Sat Nov 15 02:11:10 CET 2008


Andy Green wrote:
[...]
> This is the current one:
[...]
> I was able to do iwlist eth0 scan successfully with that.

Hooray! It indeed works. WiFi seems stable however I'm not in the place
where it usually sucked so more testing is needed.

root at om-gta02:~# iwconfig eth0
eth0      AR6000 802.11g  ESSID:"szafir"
          Mode:Managed  Frequency:2.462 GHz  Access Point:
00:18:F8:B1:5D:0C
          Bit Rate=24 Mb/s   Tx-Power=15 dBm   Sensitivity=0/3
          Retry:on
          Encryption key:off
          Power Management:off
          Link Quality:195/94  Signal level:-156 dBm  Noise level:-96 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:5  Invalid misc:0   Missed beacon:0

However I never was able to connect to the AP after suspend. And the
phone hanged twice or three times while resuming (there was no WSOD,
only black screen with the cursor in the top left corner). I was able to
(re)connect to the phone via ssh, however most commands I issued just
hanged.

echo -n 1 > /sys/bus/spi/drivers/jbt6k74/spi2.0/reset

makes screen to flicker for a sec and does nothing else.

root at om-gta02:~# cat /sys/class/i2c-adapter/i2c-0/0-0073/glamo3362.0/regs

General

0000:  2020 3650 0002 01ff 0000 0000 0000 0000
0010:  000d 000b 00ee 000f 3000 1000 3000 3000
0020:  1000 0000 3000 1000 0000 0000 0000 0000
0030:  18b9 0000 2000 0101 0132 0000 0000 0000
0040:  05db 555b 0aba 955b 0003 0000 0000 0000
0050:  000f 111e ccc3 111e 000f 0001 020f 020f
0060:  080f 0f0f 0000 0000 0000 0000 0000 0000
0070:  0000 0000 0000

Host Bus

0200:  0e03 07ff 0000 0080 0344 0600 0000 0000
0210:  0000 0000 4000

Memory

0300:  0c74 afaf 0108 0010 0000 0000 0000 0000
0310:  0000 1002 6006 00ff 0001 0020 0000 0000
0320:  0000 0000 0000 0000 0000 0000 0000 0000
0330:  3210 5432 e100 01d6

LCD 1

1100:  0020 9020 0b40 01e0 0280 440c 0000 0000
1110:  6000 0009 0000 0000 03c0 0000 0200 0000
1120:  0000 0000 0008 0000 0010 0000 01f0 0000
1130:  0294 0000 0000 0000 0002 0000 0004 0000
1140:  0284 0000 0000 0000 0000 0000 0000 0000
1150:  c000 0012 0000 0000 0000 0000 0000 0000
1160:  0000 0000 0000 0000 0000 0000 0000 0000
1170:  0000 0000 0000 0000 0000 0000 0000 0000
1180:  8023 0023 2d00 0023 0000 0000 0000 0000
1190:  0000 0000 0000 0000 0000 0000 0000 0000
11A0:  0000 0000 0000 0000 0000 0000 0000 0000
11B0:  0000

LCD 2

1200:  0000 0000 0000 0000 0000 0000 0000 0000
1210:  0000 0000 0000 0000 0000 0000 0000 0000
1220:  0000 0000 0000 0000 0000 0000 0000 0000
1230:  0000 0000 0000 0000 0000 0000 0000 0000
1240:  0000 0000 0000 0000 0000 0000 0000 0000
1250:  0000 0000 0000 0000 0000 0000 0000 0000
1260:  0000 0000

MMC

1400:  00ef 6800 4db3 108a 0000 0000 0000 0000
1410:  003f 0009 8d00 8005 0004 4800 482e 0002
1420:  c300 0001 0000 0000 0000 0000 0000 0000
1430:  080e 0000 0000 0000 8000 007f 0001 0040

(TBH I don't know if I was supposed to paste this if I haven't got WSOD,
but hey... ;-) better safe than sorry)

> | Oh. It works if I press power button for a sec too. So I believe it's
> | not kernel's issue, but a software one and we can drop this topic here.
> |
> | Still have weird sound and GSM access issues... I'll investigate and
> | eventually report bugs later, however I suspect that these are software
> | related as well.
> 
> It's good to hear about any of this kind of thing if they're new with
> this kernel.

Sometimes I am not sure if it's new kernel, other distribution or 'opkg
update && opkg upgrade' which caused a regression/bug. ;-) too many options!

Kind regards,

-- 
Lech Karol Pawłaszek <ike>
"You will never see me fall from grace" [KoRn]



More information about the openmoko-kernel mailing list