Elive

It seems it happens with the new 2.6.29 kernel from elive repository

After to do a new clean install of a recent version of Elive, you have this problem ?

Does you reach the graphical system (entrance login) ?

After to do a new clean install of a recent version of Elive, you have this problem ?

I can't try, do not have a testing machine, both two ( desktop and netbook ) I do use are machines
I need to be stable and can't try to reinstall everything.

Does you reach the graphical system (entrance login) ?

Yes, yes, everything works except tty consolles. As I told, I installed 2.6.29 kernel from elive repository
on both, desktop and netbook and both has the tty problem.

looks like a problem of a stopped init script, maybe

Can you reboot any of these machines in order to do a test ?

Yes Thanatermesis, rebooted many times since I installed 2.6.29 kernel ( 2/3 weeks ago ),
no changes, everytime I don't have tty consolles, and as I can see from 'dmesg',
no errors related

Try to add the boot parameter noentrance before to boot the installed system, this should ignore entrance and continue booting, then you should have a tty on the first console and also all the tty's in the other consoles, if is not the case, the init process should be stopped somewhere between the entrance one (S30) and the last one (S99) of /etc/rc2.d/ , in order to know which one is... can you tell me the last line that appears on teh boot process where it is stopped ?

ok, booted with "noentrance", all consolles are correctly visible ( tty1,2,3,4,5,6 )

so only when you have entrance correctly working, there's no tty consoles ? you can't go to Ctrl + Alt + F2 for example ? this is very strange since it works without problems for me (with entrance)

If this is what really happens, add the line set -x in the start of the /etc/init.d/entrance script (second line, after #!/bin/bash), then try a new boot and when you reach entrance go to the TTY1 and tell me which is the last line printed that starts with a plus simbol (+), looks like entrance stops somewhere on that script that doesn't continue the boot

ok, Thanatermesis, problem solved.
Last lines are :

Becoming entranced: entrance+ cd /etc/pam.d
+ for i in gdm kdm wdm xdm
+ test -s gdm
+ for i in gdm kdm wdm xdm
+ test -s kdm
+ for i in gdm kdm wdm xdm
+ test -s wdm
+ for i in gdm kdm wdm xdm
+ test -s xdm
+ '[' -e /etc/X11/default-display-manager ']'
++ cat /etc/X11/default-display-manager
+ '[' /usr/sbin/entranced '!=' /usr/sbin/entranced ']'
+ set +e
+ pam_getenv -l PATH
++ pam_getenv -l PATH
+ export PATH=
+ PATH=
+ set -e
+ test -x /sbin/usplash
+ /usr/sbin/entranced
+ echo .
.
+ exit 0
Starting Net-Connectord
* Starting Acer AspireOne Fan Control [ ok ]
* Starting periodic command scheduler crond [ ok ]
Starting Esound server...
xscreensaver: 15:03:06: warning: $DISPLAY is not set: defaulting to ":0.0".
xscreensaver: 15:03:08: locking is disabled (running as nobody).
xscreensaver: 15:03:08: locking only works when xscreensaver is launched

       by a normal, non-privileged user (e.g., not "root".)
       See the manual for details.

It was xscreensaver that in some way locked consolles. I tried just to kill xscreensaver daemon and
consolles appeared ( all ).
I did put the startup of xscreensaver daemon in /etc/rc.local with just the line
/usr/bin/xscreensaver
and in some way it locked ttys. Now I delete from there and try to put it in ~/.elxstrt

ok, Thanatermesis, now everything ok, starting xscreensaver from .elxstrt
I have xscreensaver daemon running and tty consolles
great Thanatermesis

What is the init script (from /etc/rc2.d/ ) that has this xscreensaver thing ?

note: not problem solved, it is only solved for you, but it will affect to all other of Elive users, so please continue helping with this bug in order to be solved in elive for everybody, that's the idea of this website

What is the init script (from /etc/rc2.d/ ) that has this xscreensaver thing ?

no there was no /etc/rc2.d script with xscreensaver in it.
I, some week ago, to let xscreensaver starting at boot time, added the line
/usr/bin/xscreensaver
to /etc/rc.local, and it gaves me, at boot time end, the following messages:

xscreensaver: 15:03:06: warning: $DISPLAY is not set: defaulting to ":0.0".
xscreensaver: 15:03:08: locking is disabled (running as nobody).
xscreensaver: 15:03:08: locking only works when xscreensaver is launched
by a normal, non-privileged user (e.g., not "root".) See the manual for details.

I thought it was nothing particular. But when you told me to look at last boot lines
and I saw those messages I tried to kill xscreensaver, and consolles reappers correctly
So I think it was my fault to put xscreensaver startup in /etc/rc.local the cause of tty problem.

note: not problem solved, it is only solved for you, but it will affect to all other of Elive users,
> so please continue helping with this bug in order to be solved in elive for everybody, that's the idea of this website

I know exactly the purpose of a bug tracking system
If you think that the problem could depends from everything else, go haead with troubleshooting, I've no problem to continue
and give a complet solution for all

Ah ok, i understand now :)

Yes it is your fault

By the way, this won't start xscreensaver at boot at all, you need to run it FROM inside a graphical system running (no init scripts), please check the screensaver feature of your Elpanel, it allow you to start at boot :)

ok, will look elpanel :)