When I install the distribution Mandrake 9.1 and only Mandrake 9.1
I cant login on my root account since the console xxxxxx@host33.linode.com
I have an anomaly on the level of the login cursor
This problem appears only with the MANDRAKE 9.1

Why not log in as root via your IP address?

-Chris

Yes I can always use this solution
But if the firewall is badly configured I did not access any more
with this solution

Thus I am obliged to use the mode console xxx@hot33.linode.com
That enables me to be connected with a firewall weakening

I just tested this with the Mandrake 9.1 small image, and it works fine for me.

[caker@home ~]# ssh linode2@hostXX.linode.com
linode2@hostXX.linode.com's password: 
[linode2@hostXX lish] Fri Oct 22 12:00:42 EDT 2004
[linode2@hostXX lish] Linode Shell (lish) Console starting...
[linode2@hostXX lish] 

Mandrake Linux release 9.1 (Bamboo) for i586
Kernel 2.4.27-linode34-1um on an i686 / tty0
li7-3 login: root
Password: 
[root@li7-3 root]# 

-Chris

You could always login with a regular user from the console, then su to root.

I'm actually having the same problem with Gentoo. I used to be able to login as root at the console, but it stopped working maybe less than a week ago. I wasn't too worried about it, but it is an interesting error.

I think he's having more of a terminal emulation problem...


Add ttyS0 (or tty0) to /etc/securetty, perhaps?

-Chris

this is result of my login :

Mandrake Linux release 9.1 (Bamboo) for i586
Kernel 2.4.27-linode34-1um on an i686 / tty0
Password: login: root


The word password crushes text "LOGIN" I cannot seize the
password completely because I have an automatic carriage return
before the end of seizure of the password

ttyS0 was there, but not tty0. It might of been removed in a recent etc-update, but I'm usually pretty good about watching changes there. Not sure it fixed it yet, I'll just wait til the next time I need to reboot to find out, unless you know if killing agetty will make it spawn a new process with updated settings (it would be agetty right?).

actually I bet etc-update did remove it, because they did recently push that file out I noticed.

No need to reboot -- just make the change and you should be able to log in as root on the console...

-Chris

Heh, it actually turned out to be vc/0, but yeah, that fixed it.

Ahh yes, good old devfs

-Chris