I'm sure that over-clocking can cause this problem, however when they appeared and
tested the was with a clean install and nothing attached on the XO (not even a mouse). BTW
me XO-1 is over-clocked for 2 years now and is going through several reboots and OSs every
day under my observation. This was a first.
Also going through os67 and then back to os11 the problem does not appear anymore (but
still no neighborhood in os11).
Maybe 2 years of overclocking, several re-flashes multiple OSs, crashes, and
experimenting, start getting the best of it :-)
--- On Fri, 3/19/10, Mikus Grinbergs <mikus(a)bga.com> wrote:
From: Mikus Grinbergs <mikus(a)bga.com>
Subject: Re: unsupported nodetype e009
To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
Cc: "James Cameron" <quozl(a)laptop.org>, fedora-olpc-list(a)redhat.com
Date: Friday, March 19, 2010, 8:27 AM
A friend of mine has a G1G1 XO-1 that
he got Dec 2007. I help him to
install reasonably-up-to-date software - his system
currently has q2e43e
and os11. [BTW, he normally does not power off his
XO, but leaves it
sit forever with the lid closed and AC plugged in - with
papers stacked
on top. I've seen his system be warm to the touch.]
It is quite rare that I observe his XO being booted -- but
I do not
recall ever seeing the "unsupported nodetype e009"
message. For the fun
of it, I added the four lines at the beginning of his
olpc.fth that
caused the XO to be overclocked (to now 462 Mhz) -- and now
I *did* see
several of those messages while booting his XO.
[Neither those
messages, nor the overclocking, appeared to affect the
operation of the
XO. (My reason for applying a mild overclock was that
Timidity was
running the default-speed XO at more than 85% average CPU
utilization -
I wanted to create some "head room" by speeding up the
CPU).]
IIRC, Yioryos has his XO-1 overclocked. As the
above-described
experience shows, it is likely that the "unsupported
nodetype e009"
message is being brought on by the use of overclocking.
mikus