On 12/07/2012 10:13 AM, Peter Robinson wrote: > On Fri, Dec 7, 2012 at 2:08 PM, Jon Masters <jcm@xxxxxxxxxx> wrote: >> On 12/07/2012 03:31 AM, Peter Robinson wrote: >>> On Fri, Dec 7, 2012 at 12:31 AM, Jon Masters <jcm@xxxxxxxxxx> wrote: >>>> On 12/06/2012 06:37 PM, Peter Robinson wrote: >>>>> On Thu, Dec 6, 2012 at 10:47 PM, Richard W.M. Jones <rjones@xxxxxxxxxx> wrote: >>>>>> On Thu, Dec 06, 2012 at 05:39:17PM -0500, Jon Masters wrote: >>>>>>> On 12/06/2012 05:29 PM, Richard W.M. Jones wrote: >>>>>>>> On Wed, Dec 05, 2012 at 11:19:51PM -0500, Jon Masters wrote: >>>>>>>>> https://fedoraproject.org/wiki/Architectures/ARM/Samsung_Chromebook_2012 >>>>>>>>> >>>>>>>>> Do not follow any of these instructions unless: >>>>>>>>> >>>>>>>>> 1). You know what you are doing. >>>>>>>>> 2). You understand that you may cause damage to your Chrombook. In >>>>>>>>> particular, you may permanently damage the audio (speaker) hardware >>>>>>>>> until we have UCM working properly in ALSA. This is at your risk. >>>>>>>>> >>>>>>>>> PLEASE do not remove the giant obnoxiously offensive warning from that >>>>>>>>> wiki page that I intentionally added to scare people off in the interim. >>>>>>>> >>>>>>>> Heh :-) >>>>>>>> >>>>>>>> I followed Dan Berrange's instructions and successfully got Fedora 17 >>>>>>>> onto my Chromebook. >>>>>>>> >>>>>>>> However it crashes (pretty reliably actually) when I do a 'yum update'. >>>>>>>> Somewhere in the middle. >>>>>>>> >>>>>>>> I haven't entirely ruled out general hardware crappiness. In >>>>>>>> particular, the SD card might be bad (although it works OK on my main >>>>>>>> laptop). Aside from that has anyone seen anything like this? >>>>>>> >>>>>>> I've seen one crash so far which happened when I left it running >>>>>>> overnight. Haven't had chance to track down why. Generally though, I've >>>>>>> not have the unreliably you mention. Upgrades work ok. If that's >>>>>>> reproducible, can you provide some more info, debug output, even a >>>>>>> YouTube video of the process for us to see what's happening? >>>>>> >>>>>> I think first of all I'm going to replace the SD card with another >>>>>> one. Never trust them even (in this case) when it's a brand name card >>>>>> bought from a reputable retailer. >>>>> >>>>> Arnd mentioned the Samsung ones as they're basically built to the >>>>> standards of eMMC cards. I've actually got a couple and they've been >>>>> very good. >>>>> >>>>> Also I've seen that on occasion. I usually do a "yum clean all; rpm >>>>> --rebuilddb" and it sometimes helps. >>>> >>>> Also, if you're upgrading for some reason from F17 to F18 you'll need to >>>> destroy and rebuild the rpm metadata in some cases. I've had to whack >>>> the __db files manually and rebuild, etc. >>> >>> All F17 -> F18 upgrades need to rebuild the rpmdb because of the move >>> from db4 to db5. It is in fact documented in the yum upgrade guide for >>> F18 here https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_17_-.3E_Fedora_18 >> >> Ah, I guess I did it every time then :) Well, David, you should know >> that one too then. I'll add it to the wiki and clean that up too. > > Personally I think most people would be better off just generating a > new image from a F18 one rather than messing around "yum upgrade" the > install. The standard upstream docs should work for those that do > except for the linker symlink bit. I agree wholeheartedly. _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
