Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to login on an HLK-RM04 [RT5350] #71

Open
anantkamath opened this issue Dec 27, 2015 · 3 comments
Open

Unable to login on an HLK-RM04 [RT5350] #71

anantkamath opened this issue Dec 27, 2015 · 3 comments

Comments

@anantkamath
Copy link

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. 

)

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:

device      geom_uncompress
options     GEOM_UNCOMPRESS
options     MD_ROOT
makeoptions MFS_IMAGE=/home/anant/tftpboot/mfsroot-hlkrm04.img.ulzma
options     ROOTDEVNAME=\"ufs:md0.uncompress\"
device      md
device      if_bridge
device      pty
@anantkamath
Copy link
Author

Using mipsel_ap instead of mipsel in the cfg worked. (I could login normally at the prompt). Telneting into the device also works.

Does mipsel_ap mean that the device cannot act as a wifi client?

@erikarn
Copy link
Member

erikarn commented Jan 2, 2016

Hi,

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.

-a

On 2 January 2016 at 09:23, Anant Kamath notifications@github.com wrote:

Using mipsel_ap instead of mipsel in the cfg worked. (I could login
normally at the prompt).

Does mipsel_ap mean that the device cannot act as a wifi client?


Reply to this email directly or view it on GitHub
#71 (comment)
.

@anantkamath
Copy link
Author

Okay, thanks.
Makes sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants