[oe] fso-console-image problems

[Mr Dash Four]

> You haven't specify target I guess..
> bitbake -c savedefconfig virtual/kernel
>   
Noted, thanks as always! I did try this but this time I am getting a 
make error from linux-leviathan_git recipe - "make savedefconfig" -> No 
rules to make target savedefconfig, so it is obviously not defined. 
Nevermind, I copied the file myself.

>> 1) how do I "activate" this keymap (provided it is the one I want);
>>     
>
> copy htcuniversal file to match MACHINE (so htcdream) and rebuild
> keymaps recipe, don't know if htcuniversal is using same layout..
>   
Noted, though what I did in the meantime is I logged in via ssh (see 
below :-) ), called nano, cut-and-paste job from my PC's htcuniversal 
keymap file, saved this as /etc/keymap-2.6.map (on the phone) and then 
executed /etc/init.d/keymap - the layout has changed somewhat but it is 
not what I need, so I am going to see if I could make the corrections I 
need so that this file matches the htcdream layout exactly.

There are quite a few "non-standard" keys (like "home", "back", two 
different "alt" keys, one "search" key etc) which I am hoping to capture 
with this layout config - will search google for the tool to use to see 
what scan codes they transmit (provided this is how the "keycode" works, 
that is).

What baffles me though is that I've had a very good layout on my 
shr-image (full GUI), but I can't see any keyboard map layouts there 
either - maybe the gui terminal I've been using there defines its own 
layouts in some different way?

>> 4) When I do all the changes, do I just do the versioning "magic" (bump 
>> up the keymaps PR) in order to trigger a re-make of the stuff I changed 
>> (great trick that!)?
>>     
>
> yes 
> 1) add file
> 2) bump PR,
> 3) rebuild
> 4) test it on device,
> 5) update it on device if it's not 100% correct and then sync keymap-2.6.map 
> with htcdream in OE
> 6) send patch to OE ML
>   
Noted, will do!

>> Hmm, I don't know what OE commit I have, but just checked my /etc/rcS.d 
>>     
>
> And I cannot run commands (git log even) in your checkout so I don't know it too :).
>   
It turns out that correcting this error (which is what I did do) fixes 
this as I am now able to use ssh and log in remotely. One other annoying 
thing - I don't seem to have "/var/log/messages" anywhere on this phone 
- everything is shown on the screen - is this something I could alter as 
well?

> Yes this is in initscripts-shr which are used only when you're building
> SHR and shr-images, if you're still playing with fso- or default
> console- iamges then IIRC normal initscript recipe is used and you have
> to apply similar fix there..
>   
I just did a grep on the entire recipes directory and apart from the 
shr-initscript recipe nothing else is there, so I altered that recipe 
(and bumped the version number to trigger a rebuild).