* try a different USB drive,
I wore out a USB drive, just by downloading new versions of XO-1.0 software
to try. (Kingston, 2GB)
copy-nand complained. I forget the exact error message, but it was obvious
after I compared the bits on the USB drive against the bits on the disk.
Many thanks
Good to hear.
USB flash drives can be unreliable. There are so many things that can
go wrong.
On Thu, Jun 13, 2013 at 04:28:48PM +1100, David Leeming wrote:
Thanks again James.
The md5sum was OK so I reformatted the USB stick and tried again - and no
error. I have done this so many times
I'm a bit interested. I haven't been able to make any of mine fail,
and I've a collection of about twelve so far, accumulated over ten
years.
I've always found my problems to be either:
- invalid partitioning,
- unrepeatable corruption of the partition table or filesystem, or;
- physical wear
On Wed, Jun 12, 2013 at 8:08 PM, Juan Cubillo jcubi...@fundacionqt.org wrote:
Thank you for the info!
Yeah the ../docs/... was a typo... I was looking inside ../doc/
I also always wondered why the wiki instructions didn't used yum to install
the software... another mystery solved!
That is
Hi Mitch,
As mentioned, upstream now has APBC/APMU clock drivers, and I think there
are a couple of things in way that clock-dt.c interacts with the common
clock framework that upstream wouldn't approve of.
Here is my first attempt at a new approach, using the new upstream clock
drivers, and
daniel wrote:
Hi Mitch,
As mentioned, upstream now has APBC/APMU clock drivers, and I think there
are a couple of things in way that clock-dt.c interacts with the common
clock framework that upstream wouldn't approve of.
Here is my first attempt at a new approach, using the new
On Thu, Jun 13, 2013 at 11:56 AM, Paul Fox p...@laptop.org wrote:
does this imply a future flag day, at which time new firmware will be
incompatible with old kernels, and vice-versa?
Unfortunately even without the DT changes described here, old firmware
versions already will not be able to boot
It seems okay to me on first reading.
On 6/13/2013 7:53 AM, Daniel Drake wrote:
Hi Mitch,
As mentioned, upstream now has APBC/APMU clock drivers, and I think there
are a couple of things in way that clock-dt.c interacts with the common
clock framework that upstream wouldn't approve of.
Testing XSCE 3 on XO 1.5 2GB os855
http://wiki.laptop.org/go/User:Holt/XS_Community_Edition/0.3/Installing
I get as far as step 13, after the SD card (I am testing with an 8GB card)
successfully configures.
When I enter bootstrap-xo is replies
Not an XO please run 'xs-config'
Sorry just realised the XO is only installed with 11.3.1 (os855)
However, is it still possible to work around? It's not easy or cheap to
download the os file.
David
From: David Leeming [mailto:da...@leeming-consulting.com]
Sent: Friday, 14 June 2013 12:28 p.m.
To: 'server-devel'
Actually, it's not that much of a problem (a mere $50 or so). More of an issue
is my impatience, I was hoping to test it today - the download for the XO would
take about 10 hours on my connection. If there's no quick answer I'll download
it overnight.
David
-Original Message-
From:
11 matches
Mail list logo
