Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Edit /etc/inittab and modify the section below to enable a serial line:
Editing that alone (and running "init q") doesn't give me a /dev/ttyAMA0, /dev/ttyS0, or /dev/serial0 device.
Don't I need to do something in /boot/config.txt ?
Editing that alone (and running "init q") doesn't give me a /dev/ttyAMA0, /dev/ttyS0, or /dev/serial0 device.
Don't I need to do something in /boot/config.txt ?
In your /boot/config.txt file:
Code:
enable_uart=1
After ensuring that is enabled, reboot. Now what is the output of this command?
Code:
root@slackware:~# ls -l /dev/ttyAMA*
For me it's:
Code:
root@iana:~# ls -l /dev/ttyAMA*
crw-rw---- 1 root dialout 204, 74 Jan 6 03:32 /dev/ttyAMA10
I would advise you, given that you're experiencing so many issues by installing Slackware AArch64 with the SARPi installer, to use the official Slackware installer software and follow the instructions on https://docs.slackware.com/slackware...4_bcm2711_rpi4 to ensure complete success. Even though this is intended for the RPi4 it works just as well on a RPi3.
SARPi does work as intended (in most cases) but sometimes requires a little more effort, and knowledge/experience of troubleshooting the Raspberry Pi with regards to configuration settings and such. If all you want to do is get Slackware AArch64 up and running as quickly and easily as possible then the official means and methods is by far the best option. SARPi is a community driven effort for playing around and for when there are no other official options available (e.g. for the Raspberry Pi (1) & 2, etc.).
[EDIT] You will probably also need to disable BlueTooth in your /boot/config.txt file in order to get a serial line working:
Code:
dtoverlay=disable-bt
Last edited by Exaga; 01-06-2024 at 01:57 AM.
Reason: typos & edit
In Slackware, Serial console support is preconfigured upon setup. Across all Raspberry Pi models, the system utilises /dev/ttyS1 for serial communication. The serial configuration is described at the foot of the Install guide.
Code:
root@mutley:~# slk-hwm-discover
Raspberry Pi 4 Model B Rev 1.4
root@mutley:~# grep -A1 serial /etc/inittab
# Local serial lines:
s0:12345:respawn:/sbin/agetty --keep-baud 115200,38400,9600 ttyS1 vt100
root@mutley:~#
Here's Slackware's RPi4 undergoing testing of Linux 6.6:
Code:
Welcome to Linux 6.6.9-armv8 aarch64 (ttyS1)
mutley login:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.