i reflashed u-boot and kernel, now i can boot, but the new kernel is
affected of this strange bug of no wifi anymore... do you have any idea
where i can find the old shr 2.6.28? thanks (i mainly use the fr as a
net-pocketPc).
d
On Mon, May 4, 2009 at 12:36 AM, Rask Ingemann Lambertsen
On Thu, Apr 30, 2009 at 04:26:30PM +0300, Timo Juhani Lindfors wrote:
Vasco Névoa vasco.ne...@sapo.pt writes:
Possible errors that lead to that situation:
- bad rootfs kernel parameters in u-boot environment; - check if you need
to change them;
This can't surely cause missing filesystem
i do not boot at all... but the message is
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(31,6)
but i flashed kernel and rootfs without errors...
d
On Thu, Apr 30, 2009 at 12:05 AM, Timo Juhani Lindfors timo.lindf...@iki.fi
wrote:
Davide Scaini dsca...@gmail.com
uhm...
...
...
I can't give you an answer 'cause I get a kernel panic... and i can't
connect to the fr... ;-)
d
On Thu, Apr 30, 2009 at 11:04 AM, Timo Juhani Lindfors timo.lindf...@iki.fi
wrote:
Davide Scaini dsca...@gmail.com writes:
i do not boot at all... but the message is
Kernel panic
Davide Scaini dsca...@gmail.com writes:
i do not boot at all... but the message is
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(31,6)
Your kernel lacks mtdblock support then?
(ls -l mtdblock6 shows 31, 6)
___
Openmoko
Possible errors that lead to that situation:
- bad rootfs kernel parameters in u-boot environment; - check if you need to
change them;
- missing kernel modules for the specific filesystem you have formatted;
- either mismatch between rootfs and kernel images, or just plain bad kernel
image;
-
2009/5/1 Vasco Névoa vasco.ne...@sapo.pt:
Possible errors that lead to that situation:
- bad rootfs kernel parameters in u-boot environment; - check if you need
to change them;
- missing kernel modules for the specific filesystem you have formatted;
- either mismatch between rootfs and kernel
Vasco Névoa vasco.ne...@sapo.pt writes:
Possible errors that lead to that situation:
- bad rootfs kernel parameters in u-boot environment; - check if you need to
change them;
This can't surely cause missing filesystem support?
- missing kernel modules for the specific filesystem you have
fu-util -a u-boot -d 1d50:5119 -R -D gta02v5_and_up-u-boot.bin
an example of my settings...
d
On Thu, Apr 30, 2009 at 3:26 PM, Timo Juhani Lindfors
timo.lindf...@iki.fiwrote:
Vasco Névoa vasco.ne...@sapo.pt writes:
Possible errors that lead to that situation:
- bad rootfs kernel parameters
usually means: kernel panic ;-)
d
On Wed, Apr 29, 2009 at 7:26 PM, rhn omcomali@porcupinefactory.orgwrote:
The battery died earlier today. I connected my FR to the wall charger. It
started upon connecting.
After a while, I noticed that the GUI is up, the red AUX LED is blinking
and the
blinking red == kernel panic
On Wed, Apr 29, 2009 at 7:26 PM, rhn omcomali@porcupinefactory.org wrote:
The battery died earlier today. I connected my FR to the wall charger. It
started upon connecting.
After a while, I noticed that the GUI is up, the red AUX LED is blinking
and the GUI
i tried now latest kernel
http://shr.bearstech.com/shr-unstable/images/om-gta02/uImage-2.6.29-oe10+gitr119801+b4136a36f31a65d0998a328465df9e8e2ba93166-r3.4-om-gta02.bin
and i get a kernel panic... nice!
d
On Wed, Apr 29, 2009 at 7:34 PM, Yorick Moko yorickm...@gmail.com wrote:
blinking red ==
Davide Scaini dsca...@gmail.com writes:
i tried now latest kernel
http://shr.bearstech.com/shr-unstable/images/om-gta02/uImage-2.6.29-oe10+gitr119801+b4136a36f31a65d0998a328465df9e8e2ba93166-r3.4-om-gta02.bin
and i get a kernel panic... nice!
If you chvt 1 can you see panic message?
13 matches
Mail list logo
