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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've decided not to incorporate any HDMI patches into the 4.14 Kernel since the only ones I found were for a newer branch, and we need a long term supported Kernel now (which 4.14 is scheduled to become).
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,601
Rep:
Front the ChangeLog:
Code:
Thu Jan 11 08:08:08 UTC 2018
The installation documentation has been renamed according to the SoC rather
than a branded product. This is because there are now more distinct branded
products using a particular SoC. U-Boot binaries have also been moved in to
new locations on the FTP site.
installdocs/INSTALL_AllWinner_A20.TXT: Added.
Renamed from '/INSTALL_BANANAPI.TXT'
installdocs/INSTALL_AllWinner_H3.TXT: Added.
Renamed from '/INSTALL_ORANGEPI.TXT'
installdocs/INSTALL_QEMU.TXT: Moved.
Moved from /
installdocs/INSTALL_RASPBERRYPI.TXT: Moved.
Moved from /
installdocs/INSTALL_Tegra20.TXT: Added.
Renamed from '/INSTALL_TRIMSLICE.TXT'
So, I'm having issues getting anything out of the serial console. I bought the exact same cable suggested in the install docs. However, I don't get any outpot. I can connect fine with screen, but never get anything. The hdmi screen works fine when using u-boot, so I know the board is working fine. The only cable that I didn't connect was the red one (serial cable). Is that cable supposed to be connected at all? My apologies ahead of time if I missed something. I've been working on this for several hours now and can't seem to figure it out.
So, I'm having issues getting anything out of the serial console. I bought the exact same cable suggested in the install docs. However, I don't get any outpot. I can connect fine with screen, but never get anything. The hdmi screen works fine when using u-boot, so I know the board is working fine. The only cable that I didn't connect was the red one (serial cable). Is that cable supposed to be connected at all? My apologies ahead of time if I missed something. I've been working on this for several hours now and can't seem to figure it out.
The TTL serial cable red wire is the 5v supply and it's not required. Try swapping the RX/TX (white/green) cables around.
Okay, was finally able to get slackwarearm-current installed. A few notes and one question.
Notes:
* cpufreq-info and lscpu does not show the complete cpu information. So, I'm not sure if operating at full speed.
* I noticed that my ethernet speed was set to 100 Mb instead of 1000Mb. Gotta make sure first my cable is okay and the switch.
* Gotta make sure to make sure to set the time before doing too much. I probably should have done this first before proceeding with the install.
As for my question, do I have to do anything with u-boot when updating the kernel?
* Gotta make sure to make sure to set the time before doing too much. I probably should have done this first before proceeding with the install.
As for my question, do I have to do anything with u-boot when updating the kernel?
I'd install a RTC, a DS3231 and not a DS1307. Then I'd stick a line in /etc/rc./rc.local like this:
Code:
#!/bin/sh
#
# /etc/rc.d/rc.local: Local system initialization script.
#
# Put any local startup commands in here. Also, if you have
# anything that needs to be run at shutdown time you can
# make an /etc/rc.d/rc.local_shutdown script and put those
# commands in there.
# Set system time from DS3231 RTC
/sbin/hwclock -s
If you don't have an RTC but you've got an Internet connection, you could try using this line in /etc/rc.d/rc.local instead:
Code:
/usr/sbin/ntpdate 0.pool.ntp.org
Then at least you don't have to remember to set the damned date/time every time you (re)boot.
Can't advise you on u-boot. I just compile it and hope it works. If it does then I leave it alone. lol
I'd install a RTC, a DS3231 and not a DS1307. Then I'd stick a line in /etc/rc./rc.local like this:
Code:
#!/bin/sh
#
# /etc/rc.d/rc.local: Local system initialization script.
#
# Put any local startup commands in here. Also, if you have
# anything that needs to be run at shutdown time you can
# make an /etc/rc.d/rc.local_shutdown script and put those
# commands in there.
# Set system time from DS3231 RTC
/sbin/hwclock -s
If you don't have an RTC but you've got an Internet connection, you could try using this line in /etc/rc.d/rc.local instead:
Code:
/usr/sbin/ntpdate 0.pool.ntp.org
Then at least you don't have to remember to set the damned date/time every time you (re)boot.
Can't advise you on u-boot. I just compile it and hope it works. If it does then I leave it alone. lol
I was thinking about the official kernel upgrades on -current. I don't want to brick my system after spending so much time getting this set up. lol I guess I can give it a try.
I'd install a RTC, a DS3231 and not a DS1307. Then I'd stick a line in /etc/rc./rc.local like this:
This is unnecessary as the Orange Pi has an RTC.
Code:
root@zippy:~/ac/source/x/xterm# dmesg | grep -i rtc
[ 1.527013] sun6i-rtc 1f00000.rtc: rtc core: registered rtc-sun6i as rtc0
[ 1.533825] sun6i-rtc 1f00000.rtc: RTC enabled
[ 1.572039] sun6i-rtc 1f00000.rtc: setting system clock to 2018-01-27 15:56:57 UTC (1517068617)
root@zippy:~/ac/source/x/xterm#
You don't need to do anything with u-boot once it's configured, and you've booted in to the new installation.
When you upgradepkg the kernel, that's all you need -- there's no "lilo" equivalent because u-boot has code to read ext file systems, so reads the DTB, Kernel and initrd from the file system directly.
root@zippy:~/ac/source/x/xterm# dmesg | grep -i rtc
[ 1.527013] sun6i-rtc 1f00000.rtc: rtc core: registered rtc-sun6i as rtc0
[ 1.533825] sun6i-rtc 1f00000.rtc: RTC enabled
[ 1.572039] sun6i-rtc 1f00000.rtc: setting system clock to 2018-01-27 15:56:57 UTC (1517068617)
root@zippy:~/ac/source/x/xterm#
You don't need to do anything with u-boot once it's configured, and you've booted in to the new installation.
When you upgradepkg the kernel, that's all you need -- there's no "lilo" equivalent because u-boot has code to read ext file systems, so reads the DTB, Kernel and initrd from the file system directly.
Thank you for the explanation. So, if I understand correctly, there can only be one kernel installed in the system. Correct? Same as the Raspberry?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
