Is that the same as symlinks? (never got that to work on my Rpi either).
If you use the command
That will show you if what you’re looking at is a
file (etc) or a
symlink to a file or directory
ls -l just list the files in the directory?
Im not sure I understand.
When I enter the terminal and write the command
ls -l this is what happens.
root@OpenHab2-C2:~# ls -l
-rw-r--r-- 1 root root 27059330 Nov 13 2018 grafana_5.3.4_armhf.deb
-rw-r--r-- 1 root root 196 Jan 8 18:09 update-velbus-jar-dev.sh
That shows that both of those are real files.
If they were symlinks, there would be an extra entry at the end showing where the symlink is pointing
ls -l /dev/tty*
ls -l /dev/serial/*
Or create a symlink and try
ls -l again
ln -s test test-symlink
ls -l tes*
You should see something like this
-rw-r--r-- 1 root root 0 May 13 07:47 test
lrwxrwxrwx 1 root root 4 May 13 07:47 test-symlink -> test
This made a bit more sense:
root@OpenHab2-C2:~# ls -l /dev/serial/*
lrwxrwxrwx 1 root root 13 Apr 7 10:19 usb-Silicon_Labs_CEL_EM357_Zigbee_USB_Stick__Long_Range_0101D166-if00-port0 -> ../../tt yUSB0
lrwxrwxrwx 1 root root 13 Feb 11 2016 usb-Velleman_Projects_VMB1USB_Velbus_USB_interface-if00 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 Feb 11 2016 platform-dwc2_b-usb-0:1.1:1.0 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 Apr 7 10:19 platform-dwc2_b-usb-0:1.2:1.0-port0 -> ../../ttyUSB0
You are trying a very 1st alfa build version of image for Odroid C4 (clearly noted as suitable for testing) and this (no proper reboot) problem is noted at the download pages. It is nearly impossible that v1.0 would work without issues.
We have a solution, but there is simply no time nor resources to integrate and test just like that. It takes time. I also manage to fry my test board and waiting for a replacement.
I know how that feels.
All I did was hook up a GPio pin incorrectly and it was “Goodnight Vienna” to the whole board.
Thank you for everything you are doing.
I’m really looking forward to trying a C4.
I am using an eMMC not SD card.
From the download pages:
Troubles with network. Sometimes it fails to initialise after reboot. All kernels are affected by this bug. apt update & apt upgrade leads to the broken system. Will be fixed soon. Workaround is to freeze system packages in armbian-config menu
- Reboot works properly on eMMC, while on SD card it doesn’t come back. Power cycle helps.
I will try another download and see if anything changes with rebooting.
Why? And you will rant ant complain if something will not work?
What about the important things like waiting, reading, helping? This is not a commercial service.
At this stage, there is no end user support since it is expensive and stressful like hell.
- Download Ubuntu Minimal 20-04 LTS image from here (non official image) and flash using etcher program. If this post is old, check for an official image first.
Only works on eMMC currently so don’t use sd. User:pass is odroid and odroid
Follow the steps at the link below. It /should setup your odroid C4 with samba shares and frontail just like you are used to with a pi. If it fails just post me a copy of the log file to look over. The script is not advanced and must be run on a clean image just flashed so if it fails it needs the image put back on to try again.
@igorp I didn’t mean to come across as ranting, just updating my experience for anyone else that’s interested.
I have been reading some on the Armbian forum but most issues are beyond my knowledge of Unix/Linux. I will continue to learn and help however I can but don’t hold your breath, neither I or my memory are getting any younger.
I would also like to thank you for the work thus far and if I can help let me know.
@matt1 Thanks for the links, will give it a try sometime today and post the results.
Update on installing OH with Debian headless image and using @matt1 script.
You will need to edit the sources list to include all deb-src lines, run apt-get update, then install sudo with apt-get install sudo -y. Next add sudo users with usermod -aG sudo yourusername then reboot.
After doing the above Matt1’s script worked perfect.
Thanks to all for your great work here. Looking forward to getting OH working on my C4.
@H102, could you clarify which image you used and where to download it?
I tried both of these:
- ubuntu-20.04-server-odroidc4-20200716.img.xz from http://ppa.linuxfactory.or.kr/images/raw/arm64/focal/
- https://www.armbian.com/odroid-c4/ v5.6.y
Matt’s script seems to run ok (each time on a clean image) and OH loads afterwards on http://openhabianpi:8080 (I can see the UI and can start setting up OH) but when I press Y at the end of the script to reboot the machine it seems to reboot ok and the blue heartbeart light start flashing after about 5 sec but I can’t connect any more via putty to the IP address and http://openhabianpi:8080 in my browser shows The connection has timed out.
Hardware is Odroid C4 + RTC shield + 32GB emmc
The only error I can see in the log is this one a few dozen times, but I don’t know if it matters because I can connect to http://openhabianpi:8080 on completion:
sudo: unable to resolve host openhabianpi: Name or service not known
This is the install log:
install.log (493.9 KB)
What should I try next?
Replace the ‘openhabianpi’ with the IP that your router shows the device is using. If you have a pi running on the network installed by openhabian then it will have already taken that hostname and that may be the cause of the issue. Frontail wont work if the hostname failed (easily fixed by editing a file) but the rest should work from memory.
http://192.168.171.22:8080/ gives a timeout error.
I deleted the Mac to IP assignment in the router and power cycled the machine and it does not show up in the DHCP table. To be sure I tried every possible IP the C4 could be assigned to in the browser and all gave a timeout.
There is no sign of traffic through wireshark and telnet cannot connect to the IP but the orange light on the RJ45 connector on the C4 is blinking.
It all works fine until I do the first reboot after the OH install.
Am I using the correct images to install from?
But what do you get if you plug a monitor & keyboard into the C4?
What do the commands
systemctl status openhab2
Sorry, I should have thought to mention that. With a newly loaded image the command line shows the machine booting when connected by hdmi. After running Matt’s script, the screen is black after rebooting or when the power is turned on. It flickers to dark grey about 3 seconds after power on and then is black again.
Connecting a keyboard gives the same result.
There is no login prompt or command line.
What options in the script are you using and have you tried turning a lot of them off to see if any of them causes the issue?