znoxx Posted May 19, 2022 Posted May 19, 2022 I have several OpiOne Plus boards. They differ by the date of manufacture (let's say 1st batch and 2nd batch) 1st batch: Works with kernel 5.10.x but does not boot kernel 5.15.x. Red light is on, power meter shows very little consumption, ethernet does not go up. Switching to last available 5.10.x kernel resolves the situation. 2nd batch: Successfully work with both 5.10.x and work with 5.15.x. Green light is on, power meter shows adequate consumption, board works. I'm pretty sure, that no more "new" opi one plus will appear at Xunlong shop and this issue won't be fixed in visible future. But well.. How I can "freeze" kernel update and I guess, uboot update also ? Just to prevent accidental updating of boards from "1st batch" ? Thanks in advance for the answer. 0 Quote
znoxx Posted May 19, 2022 Author Posted May 19, 2022 Well, sorry. Answer is: via armbian-config Anyway, is it known issue ? 0 Quote
Werner Posted May 20, 2022 Posted May 20, 2022 14 hours ago, znoxx said: Anyway, is it known issue ? I think there was a discussion about OPi1+ a few weeks ago but cannot remember if it was forums or Discord. Anyways the conclusion was I could boot 5.15 image with my board and other could not while having the same board with same revision. No solution. 0 Quote
nnb1972 Posted May 22, 2022 Posted May 22, 2022 (edited) 19.05.2022 в 23:00, znoxx сказал: They differ by the date of manufacture (let's say 1st batch and 2nd batch) Please write the date for 1st and 2nd batch. Werner! Please write the date of manufacture your OPi1+. Edited May 22, 2022 by nnb1972 0 Quote
Werner Posted May 22, 2022 Posted May 22, 2022 53 minutes ago, nnb1972 said: Please write the date for 1st and 2nd batch. Werner! Please write the date of manufacture your OPi1+. There is no date on the PCB rather than the v2.1 However there is a sticker on the back that reads 2018060800201173 I assume at least 2018 is year of production. 0 Quote
nnb1972 Posted May 23, 2022 Posted May 23, 2022 My OPi1+ v2.1 2020122800100146 doesn't boot with 5.15.x. It doesn't boot any kernel which use RSB instead of I2C for AXP805. 0 Quote
znoxx Posted May 25, 2022 Author Posted May 25, 2022 One i can check was bought in 2019. This is "old", which does not boot "new" kernel. 0 Quote
grn Posted June 1, 2022 Posted June 1, 2022 My Opi1+ sticker states: 2019042800100097 It doesn't boot any kernel which use RSB instead of I2C for AXP805. Kind regards 0 Quote
gleam2003 Posted July 3, 2022 Posted July 3, 2022 (edited) I patch the kernel 5.18 with the attached patch and it boot fine. The kernel patch switch to i2c like orangepi 3 lts. Probably it can work with 5.15 but not tested kernel-sunxi64-edge.patch u-boot-sunxi64-edge.patch Edited July 3, 2022 by gleam2003 0 Quote
Werner Posted July 4, 2022 Posted July 4, 2022 8 hours ago, gleam2003 said: I patch the kernel 5.18 with the attached patch and it boot fine. The kernel patch switch to i2c like orangepi 3 lts. Probably it can work with 5.15 but not tested kernel-sunxi64-edge.patch 624 B · 0 downloads u-boot-sunxi64-edge.patch 769 B · 1 download Would you mind providing a PR with these changes? 0 Quote
gleam2003 Posted July 4, 2022 Posted July 4, 2022 3 hours ago, Werner said: Would you mind providing a PR with these changes? Yes, i would first test if it work ok with 5.15. 5.10 work fine without change 0 Quote
gleam2003 Posted July 6, 2022 Posted July 6, 2022 (edited) I'm working on it, sorry for delay. The patch work ok on 5.15. The uboot patch isn't needed. Today I will submit the patch Edited July 6, 2022 by gleam2003 0 Quote
gleam2003 Posted July 7, 2022 Posted July 7, 2022 On 7/4/2022 at 7:30 AM, Werner said: Would you mind providing a PR with these changes? PR make https://github.com/armbian/build/pull/3964 2 Quote
grn Posted July 11, 2022 Posted July 11, 2022 Good work. I compiled Armbian 22.08 Jammy, kernel 5.15.53 and it works like a charm. I know it has nothing to do with the patch but there is some odd behaviour when I set console=serial in /boot/armbianEnv.txt boot progress hangs at Starting kernel ... Setting it back to console=both the boot progress works fine. I just want to point it out in case someone runs into this when they set their armbianEnv.txt for debugging output the way it is advised. verbosity=7 and console=both works just fine. can somebody confirm that behaviour with newer Armbian release? Kind regards 0 Quote
znoxx Posted December 1, 2022 Author Posted December 1, 2022 May be it will be helpful for someone I have spare board, which previously was running under 5.10.?? (may be 65 ?). I have especially saved this Armbian build, since it worked with "strange boards". Today I flashed latest Jammy diet with 5.15.80 and... no reaction. USB doctor shows 0.05 to 0.08 spikes and nothing. Tried to use again image with 5.10.65. Same reaction. Tried image from "orangepi.org" with 5.4.x or whatever. Same, but red light immediately on. Found one of boards running 5.10.34, copied microSD and it booted! After this I've downloaded 5.10.34 Armbian Focal -- https://mirror.yandex.ru/mirrors/armbian/archive/orangepioneplus/archive/Armbian_21.05.1_Orangepioneplus_focal_current_5.10.34.img.xz and it booted OK. Upgraded to 5.10.74 -- still ok. Then again flashed Jammy diet -- and it works now. No idea, how to explain what happened, but thanks for bringing board "up" again... 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.