Hello, e.waelde wrote:
> installing debian from scratch on neo freerunner, 4GB microSD: > > 1. stage "install" fails with > ... > P: Configuring helper cdebootstrap-helper-apt > E: Internal error: install > > continue using workaround from > http://lists.linuxtogo.org/pipermail/smartphones-userland/2009-July/001785.html I can confirm that one. No idea what might be wrong. The missing dependency is even reverse-depending to dpkg (try killing install-info from your laptop). So I don't get why the manual install of cdebootstrap (without the --includes) and the subsequent install of the other packages from within the chroot is just working fine. > 2. stage "apt" fails with > W: GPG error: http://pkg-fso.alioth.debian.org unstable Release:\ > The following signatures were invalid: KEYEXPIRED 1249744278 > and > WARNING: The following packages cannot be authenticated! > pkg-fso-keyring > E: There are problems and -y was used without --force-yes > > see below for more details > > workaround: add > APT_OPTIONS=" --yes --force-yes" > to environment calling ./install.sh > The installation completes successfully. Joachim has updated the key. > REBOOT > boots straight into X, zhone starts :-) > pin entry and connection to gsm ok. > > 3. openmoko-panel-plugin / trayer > is missing the icons for "battery" and "usb" confirmed. but you can add them easily via the config (menu entry) of the openmoko-panel-plugin. > 4. AUX Button: > does not "toggle" it creates new matchbox-keyboard processes instead > ... (the icon in trayer does correctly create and kill one). confirmed. the icond in the trayer sadly does not kill the one that was started by AUX. > 5. Screenlock > screenlock does engage correctly after screen blanking. The screen > is black and touches are not accepted. > Pressing AUX shortly will show the screen again, however, it will > not accept any input.I found out, that pressing POWER will remove > the lock (can see the icon change) but send the neo to suspend :-/. > Waking up from suspend works, and touch screen events are accepted > again. confirmed. I thought this was hilarious. The refusal of the input is indicated by the lock-icon that shows the key in red, so it is not an error per se. While I was just trying to outwit the system, i.e. being real quick to do from the black screenlock an "ACT-POWER-ACT" sequence as quickly as I could, I got a kernel panic (screen left intact. > 6. POWER Button > Pressing POWER shortly will show the button menu not if you just came back from a time-induced suspend with AUX and then press POWER with the intend to revoke the screenlock. Then the input-lock is taken away (the red color of the key of the lock-icon goes back to white) and fractions of a second later the power-induced suspend is invoked. Hence my idea to stop that suspension with AUX again, which led to the panic. > but send the neo to > suspend again. When coming back (via another short press) I can > correctly move through the buttons (active button will be > highlighted) and select an action with POW. Confirmed for short-POWER-press-induced suspends. > I suspect that the suspend action is handled separately from > whatever processes the AUX and POWER button presses. Any hints where > to look? ? but I'll test whatever you come up with :o) My hunch is the config of the openmoko-panel-plugin. Cheers, Steffen _______________________________________________ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
