Talk:Using QEMU on Troubleshooting: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
 
Line 2: Line 2:


Which is it? There's been a little edit war between <tt>[Alt + Ctrl + 1]</tt>, <tt>[Alt + Ctrl + 3]</tt> and <tt>[Alt + Ctrl + 7]</tt>... does it depend on the build? or underlying OS? or just careless typos? flaky memory? Currently it has settled on 'a set of alternatives' (better than the wrong key combination) but is it really an alternative or one of them is wrong?--[[User:Xavi|Xavi]] 01:02, 11 January 2007 (EST)
Which is it? There's been a little edit war between <tt>[Alt + Ctrl + 1]</tt>, <tt>[Alt + Ctrl + 3]</tt> and <tt>[Alt + Ctrl + 7]</tt>... does it depend on the build? or underlying OS? or just careless typos? flaky memory? Currently it has settled on 'a set of alternatives' (better than the wrong key combination) but is it really an alternative or one of them is wrong?--[[User:Xavi|Xavi]] 01:02, 11 January 2007 (EST)

Actually virtual terminals are switched in Linux by <tt>[Alt + Ctrl + ''Function_key_with_number_of_virtual_terminal'']</tt> You can launch multiple X window sessions (:0, :1 ...) with different screen resolutions and/or color depths, and each X window takes next free virtual terminal to itself, but unofficially virtual terminal 7 is used most of the time for X window first invocation. <br>
Sugar interface does not seem to respond very fast for keypresses, especially if you are unable to use KQEMU (you have not Administrator rights for the computer you use). I have noticed that pushing also Shift down let's you invoke the other terminal screen. If not you must go to QEMU console and use sendkey command. It does not matter which terminal you choose as long as in the file /etc/inittab it is defined to wait for login it the runlevel you are using (runlevel is 1 for special maintanance and 3 for OLPC normal boot, I think. Most other Linuxes use 5 for XWindow login). <br>
The biggest problem seem to be that Sugar keys are not stable and maybe last command for Sugar's Memphis developer console is something with = -sign which in my Finnish keyboard is over 0 key and need Shift to produce and in US keyboard is somewhere else :-( <br>
--[[User:Tonyv|Tonyv]] 03:56, 1 February 2007 (EST)

Latest revision as of 08:56, 1 February 2007

Terminal mappings

Which is it? There's been a little edit war between [Alt + Ctrl + 1], [Alt + Ctrl + 3] and [Alt + Ctrl + 7]... does it depend on the build? or underlying OS? or just careless typos? flaky memory? Currently it has settled on 'a set of alternatives' (better than the wrong key combination) but is it really an alternative or one of them is wrong?--Xavi 01:02, 11 January 2007 (EST)

Actually virtual terminals are switched in Linux by [Alt + Ctrl + Function_key_with_number_of_virtual_terminal] You can launch multiple X window sessions (:0, :1 ...) with different screen resolutions and/or color depths, and each X window takes next free virtual terminal to itself, but unofficially virtual terminal 7 is used most of the time for X window first invocation.
Sugar interface does not seem to respond very fast for keypresses, especially if you are unable to use KQEMU (you have not Administrator rights for the computer you use). I have noticed that pushing also Shift down let's you invoke the other terminal screen. If not you must go to QEMU console and use sendkey command. It does not matter which terminal you choose as long as in the file /etc/inittab it is defined to wait for login it the runlevel you are using (runlevel is 1 for special maintanance and 3 for OLPC normal boot, I think. Most other Linuxes use 5 for XWindow login).
The biggest problem seem to be that Sugar keys are not stable and maybe last command for Sugar's Memphis developer console is something with = -sign which in my Finnish keyboard is over 0 key and need Shift to produce and in US keyboard is somewhere else :-(
--Tonyv 03:56, 1 February 2007 (EST)