Re: cubox-i does not boot after upgrade to bullseye

2021-12-29 Thread Vagrant Cascadian
On 2021-12-29, Uwe Kleine-König wrote: > On 12/28/21 13:46, Rainer Dorsch wrote: >> Am Dienstag, 28. Dezember 2021, 11:47:37 CET schrieb Uwe Kleine-König: >>> I can recommend barebox here instead of U-Boot. i.MX is the probably >>> best supported platform for it and I would expect the cubox-i to be

Re: Solved: cubox-i does not boot after upgrade to bullseye

2021-12-29 Thread Vagrant Cascadian
On 2021-12-29, Rainer Dorsch wrote: > Am Mittwoch, 29. Dezember 2021, 19:33:20 CET schrieb Vagrant Cascadian: >> If you've used "saveenv" to save the u-boot environment variables, even >> if you upgrade u-boot, the environment will remain frozen in the state >> when you ran "saveenv". >> >> I stro

Re: cubox-i does not boot after upgrade to bullseye

2021-12-29 Thread Rainer Dorsch
Am Mittwoch, 29. Dezember 2021, 19:39:18 CET schrieb Vagrant Cascadian: > On 2021-12-29, Rainer Dorsch wrote: > > Am Montag, 27. Dezember 2021, 18:22:43 CET schrieb Vagrant Cascadian: > >> If you can insert the microSD into another Debian machine, you can get > >> the UUID by looking in /dev/di

Re: cubox-i does not boot after upgrade to bullseye

2021-12-29 Thread gene heskett
On Wednesday, December 29, 2021 1:39:18 PM EST Vagrant Cascadian wrote: > On 2021-12-29, Rainer Dorsch wrote: > > Am Montag, 27. Dezember 2021, 18:22:43 CET schrieb Vagrant Cascadian: > >> If you can insert the microSD into another Debian machine, you can > >> get > >> the UUID by looking in /d

Re: cubox-i does not boot after upgrade to bullseye

2021-12-29 Thread Vagrant Cascadian
On 2021-12-29, Rainer Dorsch wrote: > Am Montag, 27. Dezember 2021, 18:22:43 CET schrieb Vagrant Cascadian: >> If you can insert the microSD into another Debian machine, you can get >> the UUID by looking in /dev/disk/by-uuid/ to find the matching device >> or: >> >> lsblk --fs /dev/DEVICE

Re: Solved: cubox-i does not boot after upgrade to bullseye

2021-12-29 Thread Vagrant Cascadian
On 2021-12-29, Rainer Dorsch wrote: > The root cause of the new kernel not booting was that the memory addresses > for > kernel and initrd.img in the u-boot environment have probably changed during > this or a previous Debian release. > > A new installed bullseye system uses > > kernel_addr_r=0x

Re: cubox-i does not boot after upgrade to bullseye

2021-12-29 Thread Uwe Kleine-König
Hi Rainer, On 12/28/21 13:46, Rainer Dorsch wrote: Am Dienstag, 28. Dezember 2021, 11:47:37 CET schrieb Uwe Kleine-König: I can recommend barebox here instead of U-Boot. i.MX is the probably best supported platform for it and I would expect the cubox-i to be directly supported. Barebox can mou