* Thierry Moreau (thierry.moreau@connotech.com) wrote:
On 19/04/18 06:54 PM, Victor Martinez wrote:
* Thierry Moreau (thierry.moreau@connotech.com) wrote:
On 19/04/18 04:22 PM, Victor Martinez wrote:
* Fredrik Rinnestam (fredrik@rinnestam.se) wrote:
On 2018-04-19 13:59, Thierry Moreau wrote:
From the Archlinux partition I removed every /<dir> except /boot. Then untarred the generic 64b release -- thanks -- to this device.
The Odroid C2 boots with this. I was able to log root/root, and then shutdown -h now. But there is no display (I did observe success by the keyboard capslock LED going live, and then dead). Lack of display shouldn't be too difficult to troubleshoot.
You should have left /lib/modules in place too
Good catch Fredrik! Hope it helps Thierry.
Yes, good advice. My kernel installation notes indeed referred to /lib/{modules,firmware}.
I understand the the version inside those directories should be right.
It did not change the blank display (blank screen hdmi output signal, not "no hdmi signal").
Is there any specific option for the bootloader?
Hey Thierry, I waa reviewing the second mail and you are login in with archlinux credentials (root/root) because in CRUX-ARM the first time you login to the system with root account it ask to set a password. I don't understand this very well.
I am quite ignorant on this part (u-boot customization for hardware and kernel image).
Have you taken a look to boot.ini options? May be you have there video resolution options to fit your needs.
My guess is that the u-boot is able to achieve its purpose since a bash interpreter (could it be a busybox shell?) is able to obey a "shutdown -h now" command.
We've find this behaviour on a old device (wm8505) with a prebuilt kernel. We needed to overlay the rc script and adapt to its needs, but any other device is working as expected.
My further guess is that some configuration is missing in the startup steps from /sbin/init. If this was on the top of my priority, I would investigate these startup steps in the ArchLinux root filesystem (look at Odroid C2 in https://archlinuxarm.org/about/downloads ) to find something specific to the hdmi output configuration (fbdev? dvi?). From such hints, an equivalent configuration of some Crux startup file(s) should fix the issue.
I'll try to take a look this afternoon, but I have other feonts between hands (iptables, llvm, cland and chromium... and the new 3.4 devwlopment) and without a device for testing it's hard to help.
- Thierry
Regards, --- Victor Martinez Learning bit by bit | http://vjml.es