Luca Capello
Wed, 18 Mar 2009 18:05:40 -0700
Hi Sebastian! Please always separate different issues, it is easier to follow them :-)
On Fri, 13 Mar 2009 21:07:00 +0100, Sebastian Reichel wrote: > On Fri, Mar 13, 2009 at 11:53:46AM +0100, Luca Capello wrote: >> FYI, I anyway uploaded the 2.6.29 kernel package to the pkg-fso >> repository, because it should fix some nasty bugs and various people >> asked for it. Please do not advise for it, it should be tested before >> going into the public (the pkg-fso repository still provides the 2.6.28 >> kernel package). > > ah finally it's there :D I tested it with my full-upgraded > freerunner: First of all: before any new test, please kill the openmoko-panel-plugin instance running, since it takes 50% of the resources, probably because of the battery problem below. Another option is to completely disable the battery plugin, then everything is fine, at least on my case: ===== debian-gta02:~# grep -A 2 main .panel-pluginrc [main] iconpath = /usr/share/pixmaps/openmoko-panel-plugin plugins = buttons, usb, gsm, wifi, gps, keyboard, brightness, bluetooth, screenlock debian-gta02:~# ===== > 1. apm reports crap > r...@freerunner ~ # apm > cOff-line, battery status critical > r...@freerunner ~ # cat /proc/apm > 1.13 1.2 0x02 0x00 0x02 0x02 -1% -1 min Same here, it seems that the battery driver is not properly working. This should be reported to smartphones-kernel@, at least. > 2. Framework didn't enable orange led, so framework doesn't know > power status Without o-p-p, the PWR-LED of my FR is now blue: the USB is plugged in and I guess frameworkd reads the value above as 100%. > 3. framework can't access GSM > r...@freerunner ~ # tail -n 2 /var/log/frameworkd.log > 2009.03.13 20:53:22 ogsmd.modem.abstract ERROR could not open > channel CALL, retrying in 2 seconds > 2009.03.13 20:53:30 ogsmd.modem.abstract ERROR could not open > channel MISC, retrying in 2 seconds I can call, at least I hear the other end ringing. > 4. Display has been turned of by framework, but not reenabled > after touching the screen. Touchscreen input device works, > though. And I could use the mouse in X, when the Display > was enabled. Display works as expected here and gets re-enabled when touching the screen. > 5. Power Button doesn't suspend the phone. Seems it's not > recognized by the framework. It works fine here, again I guess o-p-p is the cause in your case. BTW, when resuming, Zhone updates the time as well: I consider this a bonus point since I guess it means that the system is aware of the suspension cycle. > 6. I don't get the matchbox-keyboard either when pressing the > AUX button This is because o-p-p takes most of the CPU power, i.e. it does not respond anymore. It is o-p-p that enables matchbox-keyboard when pressing the AUX button. > 7. I can't enable wifi via framework I have never used WiFi through frameworkd, but I can use it via plain CLI tools. And then I, for the first time, installed a web browser for my Debian on the FR :-D > => Looks like frameworks can't access any hardware. I'm not aware of > the internal framework structure. But I perhaps The GSM problem > blocks the remaining parts? I would say that everything seems to be frameworkd's fault, but the real problem is... > => Power Management is not working This is the main (and unique) problem, yes. To resume: with 2.6.29 I can call (sorry, given the time now I cannot test any call reception), Zhone GPS gets a 2D fix in 45.8 seconds (I live at the 7th floor, just in case) and WiFi works with WPA2-PSK (no wicd, plain i?config and wpa_supplicant). Thx, bye, Gismo / Luca
pgpTDa1FtlyRh.pgp
Description: PGP signature
_______________________________________________ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland