Processed: Re: Bug#773467: efikamx: linux-image-3.2.0-4-mx5 is not upgraded to linux-image-armmp (and that one doesn't work)

[Debian Bug Tracking System]

reopen -1

Bug #773467 {Done: Holger Levsen <***@layer-acht.org>} [src:linux,upgrade-reports] efikamx: linux-image-3.2.0-4-mx5 is not upgraded to linux-image-armmp (and that one doesn't work)
Bug reopened
Ignoring request to alter fixed versions of bug #773467 to the same values previously set

reassign -1 release-notes

Bug #773467 [src:linux,upgrade-reports] efikamx: linux-image-3.2.0-4-mx5 is not upgraded to linux-image-armmp (and that one doesn't work)
Bug reassigned from package 'src:linux,upgrade-reports' to 'release-notes'.
No longer marked as found in versions linux,upgrade-reports/3.16.7-ckt2-1.
Ignoring request to alter fixed versions of bug #773467 to the same values previously set

retitle -1 "Efikamx plattform not supported in jessie anymore"

Bug #773467 [release-notes] efikamx: linux-image-3.2.0-4-mx5 is not upgraded to linux-image-armmp (and that one doesn't work)
Changed Bug title to '"Efikamx plattform not supported in jessie anymore"' from 'efikamx: linux-image-3.2.0-4-mx5 is not upgraded to linux-image-armmp (and that one doesn't work)'
--
773467: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773467
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems

[Ian Campbell]

Hi Ian,
thanks for the fast response!

But. I don't think any modern kernel supports the efika, it was removed
from the mainline kernel a while ago (summer 2012 it seems [0]) and was
therefore removed from the installer on that basis too[1]

thanks, I was looking for this information (as I saw in the jessie d-i beta1
release notes that support for efikamx was removed, but I couldn't really find
out why..) and then I saw this in the linux debian/changelog from 3.11.5-1
* [armhf] Remove mx5, omap and vexpress flavours. These are all supported
by the multiplatform flavour.
That sounded promising enough, so I gave upgrading a try...

Yeah, mx5 general still works (AFAIK), it's just the efika stuff which
has gone.

It didn't come back, will need to attach a serial console and see if I
see anything useful there...

I wonder if I should still bother...

With (AFAIK) no DTB file in existence it'd be something of a miracle if
it worked I'm afraid :-(

From what I gather this is not unexpected. I'm not sure why this
platform was removed upstream, [...]
Sorry, I expect none of this was what you wanted to hear :-(

Indeed, but thanks for explaining!
I'll guess I'll go with owning another brick then ;-)

I did look for non-mainline community/kernel support a while back, but
it might be worth having another look before putting it in the attic.

Ian.

[Joost van Baal-Ilić]

Hi,

Post by Ian Campbell

But. I don't think any modern kernel supports the efika, it was removed
from the mainline kernel a while ago (summer 2012 it seems [0]) and was
therefore removed from the installer on that basis too[1]

thanks, I was looking for this information (as I saw in the jessie d-i beta1
release notes that support for efikamx was removed, but I couldn't really find
out why..) and then I saw this in the linux debian/changelog from 3.11.5-1
* [armhf] Remove mx5, omap and vexpress flavours. These are all supported
by the multiplatform flavour.
That sounded promising enough, so I gave upgrading a try...

Yeah, mx5 general still works (AFAIK), it's just the efika stuff which
has gone.

Note to self: add information from https://www.debian.org/devel/debian-installer/
(e.g. https://www.debian.org/devel/debian-installer/News/2014/20141005 to release notes.)
That would fix this bug, and more.

Bye,

Joost

[Debian Bug Tracking System]

Your message dated Sun, 17 Feb 2019 21:34:52 +0100
with message-id <b7e34dd6-d425-a153-29b8-***@debian.org>
and subject line Re: Bug#773467: efikamx: linux-image-3.2.0-4-mx5 is not upgraded to linux-image-armmp (and that one doesn't work)
has caused the Debian Bug report #773467,
regarding "Efikamx plattform not supported in jessie anymore"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)