Re: [opensuse-arm] Updating RPi 2B image to kernel 4.0.1 leaves non-bootable system

2015-05-19 Thread Alexander Graf

On 05/19/2015 04:58 PM, Freek de Kruijf wrote:

Op dinsdag 19 mei 2015 16:51:03 schreef Andreas Färber:

Am 18.05.2015 um 00:51 schrieb Freek de Kruijf:

I had a running image on my RPi 2B and saw kernel 4.0.1 being available.
Using zypper I updated the kernel, but after that the system was no
longer bootable.

The newest image still has a 3.19 kernel.

Are you maybe accidentally installing a kernel-default from Factory
(which I think does not yet support RPi2) over the kernel-rpi2 or so
from the Contrib project?

Yes, this 4.0.1 kernel is in the armv7l Factory repository, the repository
that is defined in the image, next to the Contrib repository.


Ah, that explains it. The raspberry pi 2 requires a special downstream 
kernel today still, hence the name kernel-rpi2. The kernel you 
installed is probably kernel-default which is an upstream kernel and 
doesn't support the RPi2 properly yet FWIW.



Alex

--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org



Re: [opensuse-arm] Updating RPi 2B image to kernel 4.0.1 leaves non-bootable system

2015-05-19 Thread Freek de Kruijf
Op dinsdag 19 mei 2015 16:51:03 schreef Andreas Färber:
 Am 18.05.2015 um 00:51 schrieb Freek de Kruijf:
  I had a running image on my RPi 2B and saw kernel 4.0.1 being available.
  Using zypper I updated the kernel, but after that the system was no
  longer bootable.
  
  The newest image still has a 3.19 kernel.
 
 Are you maybe accidentally installing a kernel-default from Factory
 (which I think does not yet support RPi2) over the kernel-rpi2 or so
 from the Contrib project?

Yes, this 4.0.1 kernel is in the armv7l Factory repository, the repository 
that is defined in the image, next to the Contrib repository.

-- 
fr.gr.

member openSUSE
Freek de Kruijf

--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org



Re: [opensuse-arm] Updating RPi 2B image to kernel 4.0.1 leaves non-bootable system

2015-05-19 Thread Freek de Kruijf
Op dinsdag 19 mei 2015 18:07:19 schreef Alexander Graf:
 On 05/19/2015 06:02 PM, Freek de Kruijf wrote:
  So maybe this kernel should not be available in the repo?
 
 It's part of the official Factory:ARM repository, because all upstream
 (non-contrib) boards use it.

So this kernel conflicts with kernel-rpi2 or vice versa.
Is it possible to keep Contrib synchronized with the same kernel version in 
Factory:ARM?

-- 
fr.gr.

member openSUSE
Freek de Kruijf

-- 
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org



Re: [opensuse-arm] Updating RPi 2B image to kernel 4.0.1 leaves non-bootable system

2015-05-19 Thread Alexander Graf

On 05/19/2015 06:36 PM, Freek de Kruijf wrote:

Op dinsdag 19 mei 2015 18:07:19 schreef Alexander Graf:

On 05/19/2015 06:02 PM, Freek de Kruijf wrote:

So maybe this kernel should not be available in the repo?

It's part of the official Factory:ARM repository, because all upstream
(non-contrib) boards use it.

So this kernel conflicts with kernel-rpi2 or vice versa.
Is it possible to keep Contrib synchronized with the same kernel version in
Factory:ARM?


Nope :). The usual way this goes is that the downstream kernel slowly 
gets merged upstream and then eventually we can take kernel-default 
instead. During the transitioning phase where there is a downstream 
kernel, we have contribs.



Alex

--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org



Re: [opensuse-arm] Updating RPi 2B image to kernel 4.0.1 leaves non-bootable system

2015-05-19 Thread Freek de Kruijf
Op dinsdag 19 mei 2015 17:02:24 schreef Alexander Graf:
 On 05/19/2015 04:58 PM, Freek de Kruijf wrote:
  Op dinsdag 19 mei 2015 16:51:03 schreef Andreas Färber:
  Am 18.05.2015 um 00:51 schrieb Freek de Kruijf:
  I had a running image on my RPi 2B and saw kernel 4.0.1 being available.
  Using zypper I updated the kernel, but after that the system was no
  longer bootable.
  
  The newest image still has a 3.19 kernel.
  
  Are you maybe accidentally installing a kernel-default from Factory
  (which I think does not yet support RPi2) over the kernel-rpi2 or so
  from the Contrib project?
  
  Yes, this 4.0.1 kernel is in the armv7l Factory repository, the repository
  that is defined in the image, next to the Contrib repository.
 
 Ah, that explains it. The raspberry pi 2 requires a special downstream
 kernel today still, hence the name kernel-rpi2. The kernel you
 installed is probably kernel-default which is an upstream kernel and
 doesn't support the RPi2 properly yet FWIW.

So maybe this kernel should not be available in the repo?

-- 
fr.gr.

member openSUSE
Freek de Kruijf

P.S. No need to send it to my address directly, I am on the mailing list.

--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org



Re: [opensuse-arm] Updating RPi 2B image to kernel 4.0.1 leaves non-bootable system

2015-05-19 Thread Alexander Graf

On 05/19/2015 06:02 PM, Freek de Kruijf wrote:

Op dinsdag 19 mei 2015 17:02:24 schreef Alexander Graf:

On 05/19/2015 04:58 PM, Freek de Kruijf wrote:

Op dinsdag 19 mei 2015 16:51:03 schreef Andreas Färber:

Am 18.05.2015 um 00:51 schrieb Freek de Kruijf:

I had a running image on my RPi 2B and saw kernel 4.0.1 being available.
Using zypper I updated the kernel, but after that the system was no
longer bootable.

The newest image still has a 3.19 kernel.

Are you maybe accidentally installing a kernel-default from Factory
(which I think does not yet support RPi2) over the kernel-rpi2 or so
from the Contrib project?

Yes, this 4.0.1 kernel is in the armv7l Factory repository, the repository
that is defined in the image, next to the Contrib repository.

Ah, that explains it. The raspberry pi 2 requires a special downstream
kernel today still, hence the name kernel-rpi2. The kernel you
installed is probably kernel-default which is an upstream kernel and
doesn't support the RPi2 properly yet FWIW.

So maybe this kernel should not be available in the repo?


It's part of the official Factory:ARM repository, because all upstream 
(non-contrib) boards use it.



Alex

--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org



[opensuse-arm] Updating RPi 2B image to kernel 4.0.1 leaves non-bootable system

2015-05-17 Thread Freek de Kruijf
I had a running image on my RPi 2B and saw kernel 4.0.1 being available. Using 
zypper I updated the kernel, but after that the system was no longer bootable.

The newest image still has a 3.19 kernel.

-- 
fr.gr.

member openSUSE
Freek de Kruijf

-- 
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org