| View previous topic :: View next topic |
| Author |
Message |
pbarill
n00b
Joined: 08 Jul 2015
Posts: 14
|
 Posted: Sun Dec 08, 2019 4:08 am Post subject: [SOLVED]Raspberry Pi 4B: init exists but couldn't execute it |
 |
|
Not new to Gentoo, but new to Raspberry Pi. Got model 4B and trying to get it running. What I see on my screen is exactly this line shown there
or
| Code: | | [ 11.098491] ---[ end Kernel panic - not syncing: No working init found. ... |
In my case, the counter is much higher than that on the picture.
I followed the instructions on the wiki, and I used the latest stage3 tarball available (stage3-arm64-20191124.tar.bz2).
I have absolutely no clue what to do (I tried what was mentioned on that linked page above, to no avail).
Are the suggested cmdline.txt and config.txt advisable for the model 4B?
I tried replacing cmdline.txt from
| Code: | | root=/dev/mmcblk0p3 rootfstype=ext4 rootwait |
to
| Code: | | dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p3 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait |
No luck.
On closer inspection of the output on the screen, I see something that might be more insightful:
| Code: | [ 5.911627] request_module: modprobe binfmt-464c cannot be processed, kmod busy with 50 threads for more than 5 seconds now
[ 5.917284] Starting init: /sbin/init exists but couldn't execute it (error --8) |
Last edited by pbarill on Sun Dec 08, 2019 9:51 pm; edited 1 time in total |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 47055
Location: 56N 3W
|
| Posted: Sun Dec 08, 2019 11:25 am Post subject: |
|
|
pbarill,
That's a very old 32 bit kernel thats booted on your Pi.
Your image shows 4.1.13-v7+ which is a Pi foundation 32 bit kernel that well predates the Pi4.
As you have init from a 64 bit stage3-arm64-20191124.tar.bz2 ... in fact a whole 64 bit userland, nothing will work.
You need a 64 bit kernel and matching bits and pieces and some entries in /boot/config.txt
What does on the Pi show?
What is the content of /boot/config.txt
The Pi4 is a little different to the Pi3 so you need this wiki page for the Pi4.
It only lists the differences and makes references to the document you followed.
New News.
The Pi Foundation are distributing a 64 bit kernel now. Its called kernel8.img
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
pbarill
n00b
Joined: 08 Jul 2015
Posts: 14
|
| Posted: Sun Dec 08, 2019 9:50 pm Post subject: |
|
|
It works! It's alive!! Thanks NeddySeagoon.
| Code: | $ uname -a
Linux localhost 4.19.86-v8+ #2 SMP PREEMPT Sun Dec 8 11:28:14 EST 2019 aarch64 GNU/Linux |
I think I introduced a bit of confusion with that linked image out there. It was just to show the last line at the end (kernel panic). Otherwise I had stuff like:
| Code: | CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.19.83-v7l+ #1277
Hardware name: BCM2835
|
It seems it was just not getting kernel8.img.
What I did before:
* Used bcmrpi3_defconfig.
* Intuitively copied bcm2711-rpi-4-b.dtb instead of bcm2710-rpi-3-b.dtb.
What changed:
* Used instead bcm2711_defconfig (hey they could have used a clearer name, like rpi-4!)
* Your boot/config.txt bit, raspberry/tools, `discard` in fstab.
Questions:
1. Is the firmware update part of the firmware stuff that's grabbed from https://github.com/raspberrypi/firmware, or is that something else, something low-level equivalent in x86 parlance to a BIOS update? You mention it involves a 32 bit program. Humm.... How to deal with a 32 bit arm program on a pure 64 install? It's a brave new world...
2. I plan to build some packages on that machine (non-humongous ones that take little time on x86 and fit tmpfs). If I don't have active cooling, is it going to toast the board in no time? I see that the little heatsink becomes hot shortly after booting, and right now it's just in terminal mode! |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 47055
Location: 56N 3W
|
| Posted: Sun Dec 08, 2019 10:19 pm Post subject: |
|
|
pbarill,
I've used the Pi Firmware updater exactly twice and I have a raspbian SD card for when things don't work and I want to make sure I've not destroyed the Pi.
Thu first time I used the firmware updater, it did its thing but my HDD performance was disappointing.
It took 10 minutes to boot from SSD.
The second time I used it was to revert the change.
I believe Sakai has a 64 bit or statically linked 32 bit version of the firmware updater that runs in her 64 bit Pi image.
Either would work on 64 bit. I've not looked but I need to.
The firmware on the Pi 4 is bootcode.bin on the earlier Pis. It executes on the GPU to get everything ready.
Its not in the https://github.com/raspberrypi/firmware repo.
Try https://github.com/raspberrypi/rpi-eeprom instead.
See https://www.raspberrypi.org/documentation/hardware/raspberrypi/booteeprom.md too.
4.19.83-v7l+ is the 32 bit kernel for the Pi4.
There are two different versions of bcm2711-rpi-4-b.dtb. You need the one that was built in your kernel tree.
Your Pi4 will work with either but for a low value of work. They are named the same but contain different CPU descriptions.
You only get one core with the wrong bcm2711-rpi-4-b.dtb.
Check dmesg
| Code: | $ dmesg | grep Brought
[ 0.144655] smp: Brought up 1 node, 4 CPUs |
I need to look at bcm2711_defconfig. It used to have a few things I like missing.
You won't toast the Pi, it will do its own thermal throttling once the CPU gets to 80C. It will just be slow.
If it helps any I have an arm64 binhost.
There is also Sakakis github.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Sakaki
Guru
Joined: 21 May 2014
Posts: 409
|
| Posted: Tue Dec 10, 2019 9:56 am Post subject: |
|
|
| NeddySeagoon wrote: | I believe Sakai has a 64 bit or statically linked 32 bit version of the firmware updater that runs in her 64 bit Pi image.
Either would work on 64 bit. I've not looked but I need to. |
My bootable Gentoo image for the RPi3/4 runs an OpenRC service provided by this this package, to invoke the RPi statically-linked EEPROM updater on boot. The service and EEPROM image ebuilds are automatically updated once a week to track upstream.
You don't need to be using my particular Gentoo image to use the updater ebuild / service. For more details, please see this post.
_________________
Regards,
sakaki |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 47055
Location: 56N 3W
|
| Posted: Tue Dec 10, 2019 10:01 am Post subject: |
|
|
Sakaki,
Thank you.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
Gentoo on ARM
