Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: georgp24 on October 16, 2013, 12:13:17 PM
-
I booted Core Linux and Tiny Core Linux with the "text" boot code and tried to switch to a second session with CTRL-ALT-F2. This did not work. How do I enable VT-switching?
Georg
-
See FAQ http://tinycorelinux.net/faq.html#bootcodes
bootcode multivt
-
Thank you Robert, multivt enables CTRL-ALT-F2. I will now test if I can use "ioctl" calls to do the vt-switch from a program.
-
With shell scripts you could use "chvt".
-
In the "old" days the way to change VT was to use ALT Fn (n=1,2,...).
I am using multivt and can see the is being read by TCL (dCore 5.14.03.09) using showbootcodes. I can also get a new VT from the shell using the chvt command.
What I _do_not_ get is changing the combination ALT-Fn to work. Any hint?
Thanks!
LDS
Note: my /etc/inittab has respawn for ttys 1 to 3 and askfirst for ttys 4 to 6.
-
If you are running X you need CTL ALT Fn.
You hijacked a thread in the wrong forum.
Please post dcore questions in a dcore forum.
-
Thanks for chiming in Gerald.
The FAQ at http://distro.ibiblio.org/tinycorelinux/faq.html#bootcodes (http://distro.ibiblio.org/tinycorelinux/faq.html#bootcodes) explains that the base boot flag disable extensions at bootitme. It might be semantics, but the name of this forum is also Tiny Core Base Q&A. I am also running without X extensions, thus I expected ALT-FN for changing VTs, which as I said work as expected with chvt from the CLI. And anyone running X and using CTRL ALT Fn would be in my same position, needing to ALT-Fn to change to another VT (with ALT F7 probably bringing him/her back to X).
I still think the issue, being related to a bootcode is independent of the the two methods to extend the base system defined as the kernel + and (some) initrd in the FAQ. Reading further, multivt just provides the suitable inittab that bb will use at boot time, and will do the same on both Core and dCore initrds.
I might be wrong and people using initrd=core.gz
do get a different behaviour/inittab than the one I described, but the doc says different and that is the reason why I am asking.
Cheers,
LDS :)
-
I can also get a new VT from the shell using the chvt command.
No you don't, 'chvt' just switches tty, regardless to what's there or not, to get a new VT you would use 'openvt'.
-
Thanks for clarifying the difference between openvt and chvt tinypoodle. I never thought/knew about that. probably because I never had an inittab with askfirst, and if understand you correctly with respawn both openvt and chvt would do the same.
Anyway, my original question is still: what can be the reason for ALT-Fn not working when syslinux booting from a flash pendrive with just the kernel and the initrd (dCore.gz) and multivt as a boot flag? I did compiled a custom kernel, but just include/exclude some pata drivers.
Am I missing something?
TiA,
LDS
Sent from my ...who cares?
-
Try it with the stock kernel. If that works, it is your custom kernel that is the problem.
-
if understand you correctly with respawn both openvt and chvt would do the same.
I never implied any such, and only ever tried to use openvt with target unused tty.