Re: 4.5.0-0.bpo.2-armmp does not boot on cubox-i

[Rainer Dorsch <ml@bokomoko.de>]

Hi again,

On Saturday 04 June 2016 12:43:00 Rainer Dorsch wrote:
> Hi Karsten,
> 
> thanks for the detailed response, that is exactly, what I was looking for.
> 
> On Saturday 04 June 2016 11:46:28 K. Merker wrote:
> > On Thu, Jun 02, 2016 at 09:30:35PM +0200, Rainer Dorsch wrote:
> > > after the upgrade to kernel 4.5.0-0.bpo.2-armmp, my cubox-i does not
> > > boot anymore. Can anybody tell if I can easlily boot the previous
> > > kernel when I enter u-boot (I used 4.5.0-0.bpo.1-armmp)?
> > 
> > Hello,
> > 
> > you can use the u-boot environment variable "fk_kvers" to
> > override the default kernel version of the boot script.
> > 
> > To do that, stop the autoboot process by pressing a key when
> > u-boot says so and enter the following commands at the u-boot
> > 
> > prompt:
> >    setenv fk_kvers 4.5.0-0.bpo.1-armmp
> >    run bootcmd
> 
> Hmm....I tried that, but that did not have any effect on the booting kernel:
> 

I realized that the boot.scr evaluates the variable. But at least in jessie it 
is called kvers (not fk_kvers). With 4.5.0-0.bpo.1-armmp I was able to boot 
normally.

Should I open a bug report against the kernel?

Thanks
Rainer

-- 
Rainer Dorsch
http://bokomoko.de/