# Couldn't get boot messages on serial port with Raspberry 3 **URL:** \ **Category:** Embedded\ **Created:** [November 3, 2016, 12:14pm UTC](https://linux-tips.com/t/couldnt-get-boot-messages-on-serial-port-with-raspberry-3/424 "2016-11-03T12:14:11Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Debuser](https://linux-tips.com/letter_avatar_proxy/v4/letter/d/96bed5/32.png) [@Debuser](https://linux-tips.com/u/Debuser)\ **Post date:** [November 3, 2016, 12:14pm UTC](https://linux-tips.com/t/couldnt-get-boot-messages-on-serial-port-with-raspberry-3/424/1 "2016-11-03T12:14:12Z")
We’re using Raspberry Pi 2 with serial console attached with following kernel cmdline: ```auto console=ttyAMA0,115200 console=tty1 ``` It is working properly. But, same setting doesn’t work on Raspberry Pi 3 boards. TTY1 console works but we couldn’t see anything over serial console. Is it possible to make serial console working on boot with Raspberry 3? ---
**Author:** ![redsector](https://linux-tips.com/user_avatar/linux-tips.com/redsector/32/71_2.png) [@redsector](https://linux-tips.com/u/redsector)\ **Post date:** [November 3, 2016, 12:41pm UTC](https://linux-tips.com/t/couldnt-get-boot-messages-on-serial-port-with-raspberry-3/424/2 "2016-11-03T12:41:43Z")
This is a known issue with Raspberry 3. **UART0** pins (`ttyAMA0`) mapped for Bluetooth module and previously used pins mapped as **UART1**. It is possible to use UART1 but it is a software UART and baud rate affected by the cpu clock speed so it is not stable enough. If you decrease the cpu clock frequence, UART1 becomes more usable but probably you don’t want to limit your board’s cpu performance by this way. So, the best option is to disable bluetooth module completely and make UART0 working again with previoudly used pins like Raspberry Pi 2. If you need bluetooth, you can use external usb bluetooth modules. To disable bluetooth module, append following lines into `config.txt`: ```auto dtoverlay=pi3-disable-bt ``` You should see console messages working again.