[SOLVED] applied last updates to bananapi pro, doesn't boot now
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My log of prior updates shows
/boot/uImage-armv7, /boot/uinitrd-armv7
The Banana Pi Hardware Model was migrated to the standard Kernel and initrd formats in 2015. Looks like you've had seamless upgrades working in a way I hadn't planned. Good going :-)
You just need to change the u-boot config and it'll boot. The installation documents provide the correct settings.
Here's what it should look like. This is the default settings from the installation documentation, so you may have /boot on a different storage device.
Copy whatever string yours has presently, substituting 'uImage' with 'zImage' and 'uinitrd' with 'initrd' and keep the rest of the string intact.
Then save the bootcmd_slk variable with the new settings (paste it into the u-boot console):
Again, this is the default so you need your own string after the setenv bootcmd_slk part.
That's the default and yours needs to look like that (but might not since you're using the older binary format with the u-boot header). However, U-Boot evaluates the strings once and stores the result, so you need to set it once again:.
If it doesn't, follow the installation instructions -you might need to change more of the u-boot configuration. That documentation has been fully baked for years now but I don't know what changed since you first installed it. You don't need to reinstall the OS though, just get the u-boot settings right.
Hopefully you have a recent enough U-Boot on there too, otherwise you'll have to upgrade that. If you can get it working by changing the config, there's no need to upgrade U-Boot itself.
The Banana Pi Hardware Model was migrated to the standard Kernel and initrd formats in 2015. Looks like you've had seamless upgrades working in a way I hadn't planned. Good going :-)
No, I'm not that clever, I followed INSTALL_AllWinner_A20.txt and tried to do what was said.
Please check out attachments, I think I have what you said to do.
This what I saw before rebooting
Quote:
-rw-r--r-- 1 root root 98176 May 13 22:29 /var/log/packages/kernel-firmware-20210503_ecdfcf8-noarch-1
-rw-r--r-- 1 root root 29376 May 13 22:30 /var/log/packages/kernel-headers-5.10.36-arm-1
-rw-r--r-- 1 root root 289835 May 13 22:33 /var/log/packages/kernel-modules-armv7-5.10.36_armv7-arm-1
-rw-r--r-- 1 root root 4856790 May 13 23:10 /var/log/packages/kernel-source-5.10.36-arm-1
-rw-r--r-- 1 root root 29303 May 13 23:11 /var/log/packages/kernel_armv7-5.10.36-arm-1
-rw-r--r-- 1 root root 4237419 May 11 11:24 /boot/System.map-armv7-5.10.36
-rw-r--r-- 1 root root 254530 May 11 10:36 /boot/config-armv7-5.10.36
-rw-r--r-- 1 root root 40203445 May 11 15:39 /boot/initrd-armv7-5.10.36
-rw-r--r-- 1 root root 5863768 May 11 11:25 /boot/zImage-armv7-5.10.36
like is my /boot/initrd-armv7-5.10.36 corrupt or something?
I have the OS installed on a 128G ssd, seems like I'm going to have to mount it somewhere to do what you said.
Nothing is corrupt - it's just that the new module loader only loads modules for known Hardware Models, and the Banana Pro doesn't identify as a 'Banana Pi', so it wasn't recognised.
You can check out Slackchat S02E12 for information about how it works.
I'm certain that the new version of the initrd will work because my Banana Pi surfaces the same model name within the U-Boot console as the Kernel /proc interface (as you'd expect!).
In fact you've just given me an idea. Thanks!
if [ -z "$platform_detected" ]; then
echo "WARNING: Unknown/unsupported $ARCH hardware platform."
and so on, can what's in /proc/device-tree/model be shown in above message?
Is "LeMaker Banana Pro" something you'll add to boot process to allow banana pro like mine to continue normal slackwarearm kernel updates?
I don't want to break it again and have to bug you some more.
Yes. The initrd I gave you to try supports it already, and the next version I'll release will display the Hardware Model regardless of whether it's supported, as that'll have informed me immediately as to what the problem was.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.