OpenRC hangs on boot after recompiling AArch64

[dr_wulsen]

Hi there,

after getting the experimental aarch-stage3, setting up my raspberry and having it boot nicely multiple times,
I've started to re-emerge @system with CFLAGS="-march=armv8-a+crc -mtune=cortex-a53 -ftree-vectorize -pipe -fomit-frame-pointer -O2" which at some point finishes without reporting problems.
However, the next boot does not happen, as it hangs at the end of /etc/init.d/devfs.

I've set the verbosity mode on and have modified the devfs init script to give an einfo "Finished" as last command before the script exits;
this happens. But after that....nothing happens.
Now if I delete the symlink to devfs in the runlevels folder, OpenRC will run /etc/init.d/dmesg instead at the next boot (modified as well to give an exit info when finished).
This happens, the exit info is given and then....nothing.

It seems that my OpenRC simply executes the first script it was told to, but after that can't continue calling other scripts.


Parallel startup of services (RC_PARALLEL) is disabled. My kernel is the default RPI3 config and was not touched in the process of upgrading @system.
So I'd exclude my kernel from the list of suspects.

However, after emerge @system completes, some message (unfortunately don't remember) appeared that tput (or something like that) failed....
Tput would be part of ncurses, would that affect the OpenRC boot process?

Is there any hope, or should I just start over with my raspberry PI?

Any help is appreciated!
_________________
There's no stupid questions, only stupid answers.

[khayyam]

[NeddySeagoon]

dr_wulsen,

Please post your cmdline.txt and config.txt from the Pi /boot.

Do you use u-boot to boot or the up to date bootcode.bin firmware?

Your kernel is in three pieces.
The Image file, the modules and the device tree binary.
Here be dragons.

There are two different bcm2710-rpi-3-b.dtb files. One is 32 bit, the other is 64 bit.
You need the right one.

If emerge @system gave you a new /etc/inittab your console may be on the serial port now but then you get nothing on the console after inittab is read.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[dr_wulsen]

First, thank you all for your support and really quick replies. I love linux and especially gentoo for the system itself, but even more for the community and people who help out. You are the good people in this world.

@khayyam: thank you for this information, I have injected a tput from another system but the issue remains the same, so i reverted back to original. At least einfo, ewarn, etc. works, so i guess the issue is not there....

@neddy: I'm on the UTD bootcode.bin, kernel8.img and the proper device tree, as well as the modules my kernel compilation gave me.This has been running and working well, remaining untouched by the emerge causing the issues. Anyway, I will replace those files in question with a new kernel build to avoid the firespitting worms lurking there.

I will post the requested files as soon as i can.... we are moving to a new apartment now, so there's no inet or even computer at the moment.
However, I believe that the inittab might lead me in the right direction...though, i can't even ping that rpi and assume it doesn't boot still.

For the next few days - thank you all for your guidance and I'll be back
_________________
There's no stupid questions, only stupid answers.

[NeddySeagoon]

dr_wulsen,

If its been fine and you have not changed the kernel or the dtb, it has to be something later in the boot process.
The dragons in the kernel are down to the 32 and 64 bit dtb files having the same name but different content.

With the default config, your Pi only runs at 600MHz, as you get the powersave CPU governor.
You can double that when you need to by switching to ondemand.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.