from comment 12 do not use: opkg upgrade
perhaps a write up on the home page?
ie what is the proposed upgrade process?
is there a way to prevent opkg uprade? its a reflex action...
Well, given that I saw people doing this a couple of times already I probably will add something like that.
The way to prevent opkg upgrade is just avoid running it To be honest I don't really understand why would you want to run it in the first place - in no place in the docs or community forums there's a recommendation of doing anything like that
The upgrade process for specific packages (there's no process for the whole system) is just "opkg install packagename", sometimes with "--force-overwrite" if opkg wouldn't want to do that. For the kernel the process is a bit more complicated and I've described it in the blog post: http://alextgalileo.altervista.org/blog/install-kernel-from-repo-onto-edison-official-image/
I think "opkg upgrade" is recommended somewhere in the context of adding only mraa/UPM repo (intelgalactic).
Ah, okay, yes, that would explain that, thanks.
In the meanwhile I've added a line with a warning to the repo configuration instructions
I now understand that opkg upgrade is a bad idea, but I have already done opkg upgrade. Is there a fix? I cannot access the "edison drive" as the OTG port seems to be rendered useless...what exactly is the "easy workaround" mentioned in the main thread?
Not sure what easy workaround you're referring to (my search doesn't yield anything), but in general I'd suggest you either to uninstall some packages/delete some files manually or reflash using the newly released Phone Flash Tool Lite - that should be easy enough (and easier than using flashall.bat, which is what I'd recemmended before 2.1 release).
Just FYI, I ran into this same issue after following the Getting Started with the Intel® IoT Devkit and Intel® XDK IoT Edition guide:
Note: If you get an error message saying "can not find mraa", connect to your board using an ssh session and run the following:
- echo "src maa-upm http://iotdk.intel.com/repos/1.1/intelgalactic" > /etc/opkg/intel-iotdk.conf
- opkg update
- opkg upgrade
What I have found, is even with the new images, the boot segment is not extended to it's full size. So I follow the steps of AlexT http://alextgalileo.altervista.org/blog/install-kernel-from-repo-onto-edison-official-image/
Up through the steps of rebooting after copying the stuff back in. For the most part I found this keeps me from this error if I do the opkg upgrade.
Actually the steps I normally follow after flashing a new image is in my posting: Wish there was a Wiki and/or Sticky Posts and/or FAQ and/or ...
Not sure if doing the steps after your image is in the state you mentioned will fix it or not, but may be worth a try.
Yeah, that guide doesn't take into account that user might have other repositories in the opkg config and that running "upgrade" like that might cause problems.
That should rather IMHO be "opkg upgrade libmraa upm", because these are the packages over there they're talking about.
This is still a problem and using opkg-upgrade is in fact recommended in an official guide here: IoT - Upgrading Intel® IoT Developer Kit libraries – Intel® Edison or Intel® Galileo board | Intel® Developer Zone. That guide suggests "From time to time, you should check if there is a new version of the libraries available," which is def. not a warning against it. When I did with a fresh install of Yocto (using the ./flashall.sh method) - I got the error that started this thread.
That's because that guide assumes the opkg config contains only Intel-supported repo