**** BEGIN LOGGING AT Wed Aug 03 02:59:57 2011 Aug 03 09:47:05 so, what's the best way to upgrade an Angstrom installation from 2008 to the 2011.3 ? just edit /etc/opkg/*.conf and replace 2008 with 2011.3? Aug 03 09:47:34 eranm: in theory that should work; I wonder if it has ever been tested though Aug 03 09:48:24 are there repos named 2011.3? or did we establish the other day that 2011.3 was a reference to the 2011.3 branch of OE rather than an angstrom version? Aug 03 09:49:48 Tried that yesterday, my hx4700 choked because it didn't have enough memory to complete all the upgrades. Aug 03 09:50:04 Under http://www.angstrom-distribution.org/feeds/ there's unstable (which is where the package explorer points to) and 2011.03 Aug 03 09:51:24 ah right Aug 03 09:51:41 The question is what to pick, basically. Aug 03 09:52:21 Alternatively, where can I find this information. Aug 03 09:52:37 I don't think there is a good place for this Aug 03 09:52:47 frankly we don't do well on this kind of thing :( Aug 03 09:54:05 if I were you I'd wait a little bit; there should be some improvements for hx4700 coming soon Aug 03 09:54:19 I'd be happy to help testing them Aug 03 09:56:05 By the way, if I do 'opkg upgrade' *without* changing the conf files, this is what I get: Aug 03 09:56:09 Upgrading opkg on root from 0.1.6+svnr209-r2.1 to 0.1.8+svnr609-r5.6... Aug 03 09:56:18 and ultimately: Aug 03 09:56:20 * ERROR: Package opkg (parent opkg) is not available from any configured src. Aug 03 09:56:57 First question is, how does opkg 'know' there's a new version? second, where does this version should be coming from? Aug 03 09:59:13 well, on the face of it that error makes no sense at all Aug 03 10:00:04 (by the way, this is taken from the unstable feed, not from 2011.03) Aug 03 10:03:07 ok, I've changed the conf files to point to unstable, verified all feeds exist and told it to upgrade. Let's see what happens. Aug 03 10:04:57 ok Aug 03 10:05:08 googling suggests checking for duplicate entries for opkg in /usr/lib/ipkg/status Aug 03 10:05:15 er, /usr/lib/opkg/status I mean Aug 03 10:07:58 thanks, bluelightning. I'll have another look after the attempted upgrade Aug 03 11:06:21 So, opkg segfaulted in the middle of the upgrade and now basic things like 'ps' are missing. Does that mean my system is borked? Aug 03 11:08:12 ouch. if you can still run opkg you can probably just install the appropriate package though (procps?) Aug 03 11:08:27 presumably ls works? Aug 03 11:08:45 nope, all of these binaries are not found Aug 03 11:09:25 I still have opkg but things like sed and bzip2 are not working ,so I can't even tell it to configure unconfigured packages. Aug 03 11:29:23 hmm, maybe busybox got nuked Aug 03 11:30:35 in which case your system may be hosed :/ Aug 03 11:38:45 aye, makes sense Aug 03 11:39:14 * eranm learned long ago that 'echo *' is a reasonable ls replacement, when the times are tough Aug 03 11:39:56 bluelightning, were you the original creator of the online image builder? Aug 03 11:40:33 eranm: no... I submitted some patches once to support opie, but that's pretty much the extent of my involvement Aug 03 11:43:05 My goal is to get a hx4700 with a recent wpa_supplicant on it. For that to happen, I need Angstrom 'unstable' (at least) on the hx4700. I building a stable image and upgrading proves tough, I wonder what it takes to get the image builder to build from unstable. **** BEGIN LOGGING AT Wed Aug 03 14:05:28 2011 Aug 03 18:10:50 How do I disable the Angstrom splash screen on boot, so I can see what's going on? Aug 03 18:11:08 nm, it's in the faq :) Aug 03 20:59:13 Hello Aug 03 21:01:16 I've been able to upgrade the Angstrom version on my hx4700 to the unstable version, but on boot it does not go past rcS (I see rcS.d/S99finihs.sh called but nothing past it). Any clues on why init behaves like this? **** ENDING LOGGING AT Thu Aug 04 02:59:57 2011