linaro-image-tools should make it clear that it only works on Lucid and above

Bug #627607 reported by Torez Smith
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro Image Tools
Won't Fix
Low
Unassigned

Bug Description

If run linaro-image-tools tool on Karmic and generate sd image, you are not able to boot that image on a beagle board XM. ( Although you are able to boot it on an IGEP board )

On XM booting does not begin, it halts before seeing the X-loader line

Revision history for this message
Loïc Minier (lool) wrote :

Could you attach the output of fdisk -l on a working and on a failing MMC?

Thanks,

Loïc Minier (lool)
Changed in linaro-image-tools:
assignee: nobody → Torez Smith (lnxtorez)
importance: Undecided → Low
Revision history for this message
Torez Smith (lnxtorez) wrote :

I actually suggest we close this bug because not certain the efforts will be fruitful

While creating and testing a new hwpack, ran into other problems with the linaro-media-create tool where things do not work too well on Karmic. It appears each day there are more and more Maverick dependencies on the Linaro tools so to have them supported in Karmic may not be a good idea.

Revision history for this message
Peter Maydell (pmaydell) wrote :

I think the combination of this bug and https://bugs.launchpad.net/linaro-image-tools/+bug/638966 are a bit awkward because it means that if your machine runs karmic you can't run the script directly, and you can't write the image to a file under a maverick chroot and then dd to sdcard in karmic either (without editing linaro-media-create, which is what I do in practice). So I think if we decide we don't care about this bug it would be good to fix 638966.

Also if we do decide not to support karmic we should at least make the script bomb out with a "run under lucid or better" message rather than silently writing a duff image...

Revision history for this message
Torez Smith (lnxtorez) wrote :

Peter, I've seen many problems with running the script under karmic. If we fix and/or address one, we further down the road find another. Over the weekend I finally bit the bullet and moved my system forward from karmic up to lucid and that appears to have solved quite a bit of the issues I'm seeing.

While talking to a few other folks, I understand karmic is not a very well supported release, and based on my experience, I can vouch for a few problems. With that in mind, I will agree and suggest we add logic to the tool that say we support lucid or higher with this tool

Revision history for this message
Alexander Sack (asac) wrote :

seems to be triaged: we should add info that we need lucid or higher.

Changed in linaro-image-tools:
status: New → Triaged
summary: - linaro-image-tools does not work on Karmic
+ linaro-image-tools should make it clear that it only works on Lucid and
+ above
Loïc Minier (lool)
Changed in linaro-image-tools:
assignee: Torez Smith (lnxtorez) → nobody
Revision history for this message
Loïc Minier (lool) wrote :

I don't think we will fix this bug; LP #638966 was fixed which makes it possible to use a chroot to run linaro-image-tools.

We could defensively look at the environment to check whether commands etc. are recent enough, but it's just a lot of work and I don't think this will happen in the light of karmic support timeframe ending in a month or so, so closing this bug.

(Please reopen if there are other use cases)

Changed in linaro-image-tools:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.