Re: HHL 2.0 login problem

2 messages, 2 authors, 2001-07-31 · open the first message on its own page

Re: HHL 2.0 login problem

From: James F Dougherty <hidden>
Date: 2001-07-31 09:01:35

INIT: version 2.78 booting
eth0: Setting full-duplex based on MII#0 link partner capability of 45e1.
INIT: Entering runlevel: 2

Linux 2.0 (linux-2.4.2_hhl20)





mousse login: root
PAM_unix[14]: (login) session opened for user root by (uid=0)

Linux 2.0 (MontaVista HLL2.0)

MOUSSE/MPC8240



login[14]: unable to change tty `/dev/console' for user `root'

Unable to change tty /dev/console: Illegal seek


Linux 2.0 (linux-2.4.2_hhl20)



mousse login:


Content-MD5: rWhRYjSxD0fPNTrP1f0TsA==

Anyone know what is wrong here? Perhaps my dev tree is not
configured correctly, or there is some missing file?



VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 84k init 4k openfirmware
modrs_close: bad serial port count; tty->count is 1, state->count is 2
probe: modprobe: Can't open dependencies file
/lib/modules/2.4.2_hhl20/modules.dep (No such file or directory)
INIT: version 2.78 booting
eth0: Setting full-duplex based on MII#0 link partner capability of 45e1.
INIT: Entering runlevel: 2

mousse login: root

PAM_unix[14]: (login) session opened for user root by (uid=0)
login[14]: unable to change tty `/dev/console' for user `root'
Unable to change tty /dev/console: Illegal seek

mousse login:
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: HHL 2.0 login problem

From: Andrew Dixon <hidden>
Date: 2001-07-31 13:30:06

Hi James,
James F Dougherty wrote:
INIT: version 2.78 booting
eth0: Setting full-duplex based on MII#0 link partner capability of 45e1.
INIT: Entering runlevel: 2

Linux 2.0 (linux-2.4.2_hhl20)

mousse login: root
PAM_unix[14]: (login) session opened for user root by (uid=0)

Linux 2.0 (MontaVista HLL2.0)

MOUSSE/MPC8240

login[14]: unable to change tty `/dev/console' for user `root'

Unable to change tty /dev/console: Illegal seek
What do /dev/console and /dev/tty[0-7] look like (ls -l)?

Look in /usr/src/linux/Documentation/devices.txt for a description of
these devices (be sure to read the section TERMINAL DEVICES).

You should also checkout /etc/inittab.  The last few lines in there
spawn gettys to handle the terminal connection.

hth,
Andy

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help