Tiny Core Linux
dCore Import Debian Packages to Mountable SCE extensions => dCore X86 => Topic started by: nitram on January 31, 2016, 10:10:26 PM
-
Unable to switch from Xorg to TTY, running dCore-jessie:2016.01.31.21.53, the latest release candidate.
Minimal boot to rule out other issues, rebuilt SCEs using newly modified -z option, also tested with restored SCE backups before new purge system. Attempting to switch to TTY just get a black screen, blinking underscore cursor top left corner. When switching back to Xorg briefly see text but not able to read. Able to switch back/forth, just don't get a TTY prompt or anything functional.
Tried with/out minimal sceboot.lst:
graphics-3.16.6-tinycore
xorg-intel
Xprogs
fluxbox
This hardware and intel 810 always gives Xorg errors but in TC6 no problem switching back and forth, same hardware also using Fluxbox. In dCore when attempting to switch back/forth get this in Xorg.0.log, thanks.
[ 903.827] (II) intel(0): Setting dot clock to 108.0 MHz [ 0x10 0x2 0x20 ] [ 18 4 2 ]
[ 903.827] (II) intel(0): chose watermark 0x22210000: (tab.freq 108.0)
-
Hi nitram
When you got the blinking cursor, did you try hitting enter to see if you get a prompt?
-
Hi Rich, thanks.
Already tried hitting Enter, Escape, spacebar amongst others.
Retrieved inittab, rcS and tc-config from TC6 to compare to dCore...new territory for me.
-
Although minor variations between these files to my untrained eye nothing significant. Obviously there are differences between TC and dCore but using the text bootcode in TC6 boots to TTY. The following codes in dCore boot direct into Fluxbox, despite removing 'desktop=fluxbox' and adding 'text'. In dCore the only way i can boot direct into text is to use 'base' and i believe 'text', just different, may not be relevant, then TTY works fine.
Booted me into Fluxbox:
tc@box:~$ version
dCore-jessie:2016.01.31.21.53
tc@box:~$ showbootcodes
BOOT_IMAGE=/dCore/boot/vmlinuz-jessie nozswap showapps tce=sdb4 text
So still can't get to TTY from Xorg session, suggestions appeciated, thanks.
-
I nitram. Read the boot codes on the faq
-
Hi jls.
tinycore text Textmode
http://tinycorelinux.net/faq.html#bootcodes
As explained, 'text' bootcode doesn't boot my dCore into text mode unless i also add 'base', but then boot without anything loaded. Doesn't appear to work this way in TC6. Regardless the main issue is unable to switch from Xorg to TTY during a graphic session. Anything else to look at?
-
Same issue switching to flwm_topside.
The multivt bootcode provided additional TTYs and got a login prompt, some progress BUT shouldn't default boot without this bootcode provide one TTY in addition to Xorg? At least that's how it works in TC6...
This may be due to my purged extensions, using mutlivt then Ctrl-Alt F1-F4 keys provided additional TTYS, logging in as 'tc' started another graphic session. Never saw that before, had four seperate graphic sessions running and was able to switch between them using Ctrl-Alt-F1-F4. As mentioned, may be due to broken purged extensions. Regardless the intial problem of not being able to switch from Xorg to TTY with default extensions (sce-import -z) did not work. Now stuck, can't think of anything else to try ATM. Can anyone test and reproduce any of this? Thanks.
-
The "text" boot code of dCore fixed. I have not tested with the multivt boot code, but at least if you use the text boot code it will boot to text even with Xorg and a WM installed, and with the desktop= specified.
In the latest RC.
Tested and I can switch to different tty that produces a text login prompt when X is running whether the "text" boot code is used or not.
-
Those who are using the 'mutivt' boot code and wish to switch to a tty during an X session, please test and confirm, thanks.
-
Hi
multivt works.
Thanx
-
Sorry notice no change, boots into Fluxbox despite 'text' bootcode. Using minimal boot, all SCEs listed below built using sce-import -z option. After booting to Fluxbox, toggling Ctrl-Alt-F1/F2 doesn't properly switch to TTY, thanks.
tc@box:~$ version
dCore-jessie:2016.02.03.23.56
tc@box:~$ showbootcodes
BOOT_IMAGE=/dCore/boot/vmlinuz-jessie nozswap text showapps tce=sdb4 desktop=fluxbox
tc@box:~$ cat /etc/sysconfig/tcedir/sceboot.lst
graphics-3.16.6-tinycore
xorg-intel
Xprogs
fluxbox
-
Ok, will test.
-
Using boot codes "multivt text" boots into text, even with desktop=icewm.
CTRL-Alt-F* switches to a new terminal login prompt.
cat /etc/sysconfit/tcedir/sceboot.lst:
pysolfc
200-multimedia-wily
wodim
minidlna
trans
flash11
-
If you just use 'text' bootcode, not 'multivt text', should this not boot into text mode?
Not sure if this would make a difference but are you able to test with a dcore-jessie install?
-
Just rebooted and 'multivt text' still booted into Fluxbox. IIRC previously only able to boot into TTY if i remove the tce=* and/or desktop=* bootcodes:
tc@box:~$ showbootcodes
BOOT_IMAGE=/dCore/boot/vmlinuz-jessie multivt text nozswap showapps tce=sdb4 desktop=fluxbox
tc@box:~$ version
dCore-jessie:2016.02.03.23.56
If someone could test on dcore-jessie it would certainly be appreciated. This is an odd problem as the 'text' bootcode works perfect on same hardware running Tiny Core 6. Oh well, can't expect my old beast to run perfect anymore :)
Jason did your successful text boot have a tce=* bootcode with a bootlist that loaded xorg?
-
With dCore-jessie, all works here, boot "multivt text" and boots to text and I can switch from an X desktop to login terminals with the vt switching.
One thing, are you backing up your ~/.profile or have persistent home? That file is where conditions are checked to startx on login or not.
-
Thanks for the tip. No wonder, my local .profile never got the *fix*. Copied /etc/skel/.profile to /home/tc and now 'text' bootcode works as expected, thanks. Also tested 'multivt' and it provides multiple TTYs. And of course booting with 'text multivt' boots into text, can startx then later switch to numerous TTYs.
Just one more clarification. Without using any 'text' or 'multivt' bootcode (regular boot), are you able to boot into graphics then Ctrl-Alt-F2 to TTY?
On my dCore this doesn't work, requiring 'multivt'. On my TC6, it provides a single TTY so i never need to bother with 'multivt'. I tried playing with /etc/inittab but was unable to 'unlock' an extra TTY without 'multivt'.
-
I remember Robert would mention when making RCs or releases something like "changes that might affect your backup file", that is /home and /opt in particular, I will try to do the same.
Are you saying that multivt capability is available in Core without the multivt boot code and with one tty? Or are you able to unock them after boot? dCore and Core share the exact /etc/inittab. Since without multivt multiple vts are not supposed to work, so it is more of a curiosity.
-
I remember Robert would mention when making RCs or releases something like "changes that might affect your backup file", that is /home and /opt in particular, I will try to do the same.
Thanks, probably would have saved me a couple hours of frustration. I'm not so advanced, so it's not automatic to me which files were changed to fix bugs.
Are you saying that multivt capability is available in Core without the multivt boot code and with one tty? Or are you able to unock them after boot? dCore and Core share the exact /etc/inittab. Since without multivt multiple vts are not supposed to work, so it is more of a curiosity.
Yes that's what i'm saying, TC6 and dCore don't behave the same way. I don't mess with my .profile or inittab so AFAIK this is default TC6 behaviour. Booting TC6 without multivt bootcode, Fluxbox starts then pressing Ctrl-Alt-F1 gets me to TTY. Toggling Ctrl-Alt-F2 gets me back to Fluxbox...no multivt required. Not sure why dCore doesn't behave the same way, it's kinda handy to have around. Most users don't require 6 TTYs, but the one is nice for graphic escape. Maybe another TC user could confirm this behaviour. I have another TC6 install on a netbook but it's not available ATM.
My TC6 boot (same hardware) that provides one TTY in addition to Xorg/Fluxbox:
tc@box:~$ version
6.4.1rc1
tc@box:~$ showbootcodes
BOOT_IMAGE=/tinycore/boot/vmlinuz nozswap showapps tce=sdb3
-
This is the first time in a long time if any I made changes to a file that will wind up in the home directory. Believe me, I understand the concept of hours of frustration. And though dCore is Tinycore, there are differences in package behavior. I will boot with Core6 and try to see what you are talking about.
In the past, it was recommended that "base norestore" was used when testing, but I am not going to ask that. I will simply give notice if anything in /etc/skel , ie /home, is changed.
-
What I see in core6 with no multivt boot code is if I press CTRL-ALT-F1 then I see a black screen with no prompt, and pressing CTRL-ALT-F2 brings back the desktop. In dCore what I see without the multivt boot code is if you press CTRL-ALT-F2 or F3 or whatever you get a black screen with no prompt, and CTRL-ALT-F1 brings it back.
-
Hi Jason W
This is the first time in a long time if any I made changes to a file that will wind up in the home directory.
Not to quibble, but this doesn't seem to be that long ago:
http://forum.tinycorelinux.net/index.php/topic,19303.msg118922.html#msg118922
-
Just comparing on my other TC6 install, this one boots Xvesa with JWM, the other Xorg with Fluxbox. On this install i am also able to Ctrl-Alt-F1 to get to a TTY, actually need to press Enter key to clear Xorg gibberish then get prompt. Ctrl-Alt-F2 returns to graphics. Pretty sure none of these systems were tweaked in this regard.
When i run tty from Ctrl-Alt-F1 TTY i get /dev/tty1. Learned the command su openvt , which opens yet another virtual terminal on-the-fly. So now Ctrl-Alt-F3 changes to a new TTY and when i run tty get /dev/tty3. So my guess is Xvesa is running in TTY2? My limited understanding can only, therefore, conclude that my TC6 installs boot by default (no multi boot code) with two vt.
Anywho...just wanted to report findings. Yes i understand there will definitely be differences between TC and dCore, even in base functionality. Just interesting. Also nice to learn the new openvt command for myself. The text boot issue is resolved, multivt works well, now i know how to easily add another vt on the go, thanks.
[edit] now unable to repeat openvt , will need to keep playing around.
[edit2] appears to work well, opens new vt as tc: sudo openvt su tc
http://forum.tinycorelinux.net/index.php?topic=12506.0
-
Rich - I guess I would have been more accurate to say I have only made changes to home dir files once over a period of a long time, rather than it has been a long time. lol I forgot that patch to .profile was applied in Dec, seemed like longer. Usually time flies, but evidently not in this case.