# Using UART

**URL:** https://dietpi.com/forum/t/using-uart/2276
**Category:** Troubleshooting
**Created:** [20 May 2018 04:57 UTC](https://dietpi.com/forum/t/using-uart/2276 "2018-05-20T04:57:35Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)
#### Post date: [3 June 2018 15:29 UTC](https://dietpi.com/forum/t/using-uart/2276/3 "2018-06-03T15:29:51Z")

</div>

MrGlasspoole  
I never configured a serial console, UART or something like that, but you will get the important points here: [https://github.com/Fourdee/DietPi/issues/1759](https://github.com/Fourdee/DietPi/issues/1759)

- Enable serial console with **dietpi-config** should already do all steps for you, but to be sure:
- Verify that **/DietPi/config.txt** contains the line **enable\_uart=1**.
- Verify that **/DietPi/dietpi.txt** contains the line **CONFIG\_SERIAL\_CONSOLE\_ENABLE=1**.
- NEVER do **systemctl disable [getty@tty1.service](mailto:getty@tty1.service)** as TTY1 is always needed as fallback login console. You might be left without the possibility to login 😉.
- It seems cmdline does not need to contain anything about that, as UART entry in config.txt seems to replace it (as far as I understand dietpi-config code…). **console=serial0,115200** should be not present within the file, as we disable serial console by default (and remove the line by this).
- Disabling BT seems to be recommended. Jep just do it as well via dietpi-config.
- What you mean by /dev? Which entry in which file?

---

_[View the full topic](https://dietpi.com/forum/t/using-uart/2276)._