You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I created a kernel using this cfg: #70, and used a mfsroot image created using build_mfsroot and build_fsimage.
I get the same problem as #9, but after adding login.conf to /etc instead of just /c/etc,
it boots but after init finishes, at the serial login prompt, no username seems to be valid. (I tried root, user)
Configuring /etc/ttys to autologin using al.57600 instead of 3wire, like this:
ttyu1 "/usr/libexec/getty al.57600" vt100 on secure
also fails. (It results in an infinite failed login loop with this message:
Dec 26 18:53:20 init: getty repeating too quickly on port /dev/ttyu1, sleeping.
No. mipsel_ap is the AP build. It is what build_mfsroot / build_tinymfsroot
use. The ap build disables a bunch of things (eg kerberos) to reduce the
image / dependency size.
The build_ scripts include only the pieces needed and nothing more. Those
scripts assume no kerberos was built, etc.
I created a kernel using this cfg: #70, and used a mfsroot image created using build_mfsroot and build_fsimage.
I get the same problem as #9, but after adding login.conf to /etc instead of just /c/etc,
it boots but after init finishes, at the serial login prompt, no username seems to be valid. (I tried root, user)
Configuring /etc/ttys to autologin using al.57600 instead of 3wire, like this:
also fails. (It results in an infinite failed login loop with this message:
)
Boot message: http://pastebin.com/qYcBR0bq
Telnetd too rejects the credentials (login: user, blank password; login: root, blank password; login: root, password:root ; all these combinations fail)
These are the additions to the RT5350 kernconf:
The text was updated successfully, but these errors were encountered: