El Thursday, 25 de September de 2008 15:44:45 [EMAIL PROTECTED] va escriure:
That sounds very likely what I did. I will check the fstab entry on the sd
card, but I'm almost certain it was mtdblock0.
On the minus side this means I will definitely need a debug board, but at
least it is highly
2008/9/26 The Rasterman Carsten Haitzler [EMAIL PROTECTED]:
perhaps doing what it suggests might help? :) note - chances are whatever you
have is likely behind the curve and possibly is segving as a result of
inconsistent packages (eg svnrev of illume != svnrev of efl/e-wm). most
likely.
i
On Fri, 26 Sep 2008 21:24:35 +1200 Robin Paulson [EMAIL PROTECTED]
babbled:
2008/9/26 The Rasterman Carsten Haitzler [EMAIL PROTECTED]:
perhaps doing what it suggests might help? :) note - chances are whatever
you have is likely behind the curve and possibly is segving as a result of
2008/9/26 The Rasterman Carsten Haitzler [EMAIL PROTECTED]:
illume as well? hmm. ok definitely behind the curve - i'm building 36262's
right - i'm using what opkg provides. not sure what else to do
currently. backtraces would be good! i dont use asu anymore. (fso stuff thouhg
i've now been
2008/9/26 Boris Wong [EMAIL PROTECTED]
Boris here.
I have re-flashed the bios and tried different kernels and
rootfs' (including om2008.8, om2008.9, qtopia). None of which
work.
What could be the problem? If it is a hardware defect, I may be
too late
I am using gta02v5_and_up-u-boot.bin (from September 12, 2008).
Right now I am using U-Boot 1.3.2-moko12 to boot (by bios, I meant the
u-boot). I have not modified the partition tables, but I do not know how
to access all of them.
I have used
Om2008.8-gta02-20080903.uImage.bin
