# No login through Xem ports

**URL:** https://forums.digi.com/t/no-login-through-xem-ports/7781
**Category:** USB Devices
**Created:** [June 12, 2007, 10:04pm UTC](https://forums.digi.com/t/no-login-through-xem-ports/7781 "2007-06-12T22:04:46Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![KenJ](https://avatars.discourse-cdn.com/v4/letter/k/9fc29f/32.png) [@KenJ](https://forums.digi.com/u/KenJ)
#### Post date: [June 12, 2007, 10:04pm UTC](https://forums.digi.com/t/no-login-through-xem-ports/7781/1 "2007-06-12T22:04:46Z")

</div>

We are unable to get a simple ansi session running under RHEL ES4 using the devices configured with the dgap 1.3-6 drivers using agetty.

Diagnostic testing of the PORTS16em works fine in loopback. I can access the test terminal with dinc and have a dialog going but it seems agetty is not invoking the login.

All other logins work through telnet and the system’s serial ports. I am attaching the inittab we are working with.

Any ideas?

thanks in advance,

---

<div class="post-metadata">

### Author: ![michaelt](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.digi.com/michaelt/32/92_2.png) [@michaelt](https://forums.digi.com/u/michaelt)
#### Post date: [June 12, 2007, 10:36pm UTC](https://forums.digi.com/t/no-login-through-xem-ports/7781/2 "2007-06-12T22:36:20Z")

</div>

I don’t see any problem with your inittab syntax for that terminal. It looks very similar to what we have listed in our example:

[http://www.digi.com/support/kbase/kbaseresultdetl.jsp?id=194](http://www.digi.com/support/kbase/kbaseresultdetl.jsp?id=194)

So being that your agetty entry looks sound and you can send data out the serial port with dinc, did you “init q” or “telinit q” after editing the inittab or reboot the server so the inittab changes take effect?