Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.rc > #334182 > unrolled thread
| Started by | Diederik de Haas <didi.debian@cknow.org> |
|---|---|
| First post | 2022-12-29 14:40 +0100 |
| Last post | 2022-12-29 14:40 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.debian.bugs.rc
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#1016963: Help with testing u-boot! Diederik de Haas <didi.debian@cknow.org> - 2022-12-29 14:40 +0100
| From | Diederik de Haas <didi.debian@cknow.org> |
|---|---|
| Date | 2022-12-29 14:40 +0100 |
| Subject | Bug#1016963: Help with testing u-boot! |
| Message-ID | <FI1ix-e6R2-5@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
On Thursday, 29 December 2022 04:33:51 CET Rick Thomas wrote: > Rebooting while watching the serial console output says "U-Boot SPL > 2016.05-rc2+dfsg0~20160423~1-1 (Apr 24 2016 - 04:24:21)" So the firmware > does not correspond to what aptitude says. <hmmm...> The main difference with your other Cubox-i output is the 'SPL' part. I have no clue about Cubox-i, but on Rockchip/Pine64 devices you (often) can boot from SPI, eMMC and SDcard and its preference is also in that order. So if you have u-boot on SPI (flash), then it'll use that (if it also preferences SPI above others). Which likely means that you could also completely remove the u-boot packages and that has no effect on your ability to boot the device. If you want to try newer u-boot versions, then you need to find out how to either update u-boot in SPI or how to clear the contents of SPI, so it would 'fall back' on u-boot found somewhere else, like SDcard. HTH
Back to top | Article view | linux.debian.bugs.rc
csiph-web