i have a new BBB rev c from aidafruit and i downloaded the latest Debian from http://debian.beagleboard.org/images/BBB-eMMC-flasher-debian-7.5-2014-05-14-2gb.img.xz extracted it, and copied it to a16G MicroSD card i had laying around (using win32 disk imager)
i attempted the update with a 1A power cord / wall wart and no Ethernet cable attached.
i held the “boot” button and applied power, it looks like it is supposed to and then after a while it just shuts down.
after booting it back up i noticed that it had not updated.
so i tried it again with my brand new serial cable connected to it.i get this:
beaglebone login: [ 25.134741] libphy: PHY 4a101000.mdio:01 not found
[ 25.139945] net eth0: phy 4a101000.mdio:01 not found on slave 1
Sending SIGTERM to remaining processes…
Sending SIGKILL to remaining processes…
Unmounting file systems.
Unmounted /sys/fs/fuse/connections.
Unmounted /dev/mqueue.
Unmounted /sys/kernel/security.
Unmounted /sys/kernel/debug.
Disabling swaps.
Detaching loop devices.
Detaching DM devices.
[ 972.131075] (NULL device *): gadget not registered.
[ 972.145535] Power down.
[ 972.150454] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000
[ 972.150454]
[ 972.160175] [] (unwind_backtrace+0x1/0x9c) from [] (panic+0x59/0x158)
[ 972.168833] [] (panic+0x59/0x158) from [] (do_exit+0x5ff/0x68c)
[ 972.176944] [] (do_exit+0x5ff/0x68c) from [] (sys_reboot+0x105/0x15c)
[ 972.185604] [] (sys_reboot+0x105/0x15c) from [] (ret_fast_syscall+0x1/0x46)
[ 972.194795] drm_kms_helper: panic occurred, switching back to text console
any ideas what i did wrong / how to recover?
i have a new BBB rev c from aidafruit and i downloaded the latest Debian
from
http://debian.beagleboard.org/images/BBB-eMMC-flasher-debian-7.5-2014-05-14-2gb.img.xz
extracted it, and copied it to a16G MicroSD card i had laying around (using
win32 disk imager)
Well, that's the same image adafruit used.
i attempted the update with a 1A power cord / wall wart and no Ethernet
cable attached.
i held the "boot" button and applied power, it looks like it is supposed to
and then after a while it just shuts down.
after booting it back up i noticed that it had not updated.
Can you be more specific? What do you "notice" that would hint it
needs an update?
so i tried it again with my brand new serial cable connected to it.i get
this:
[ 972.145535] Power down.
972/60 = 16.2 minutes, so it "flashed" then shutdown...
[ 972.150454] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x00000000
[ 972.150454]
[ 972.160175] [<c00111f1>] (unwind_backtrace+0x1/0x9c) from [<c04c8955>]
(panic+0x59/0x158)
[ 972.168833] [<c04c8955>] (panic+0x59/0x158) from [<c00336ff>]
(do_exit+0x5ff/0x68c)
[ 972.176944] [<c00336ff>] (do_exit+0x5ff/0x68c) from [<c003dc5d>]
(sys_reboot+0x105/0x15c)
[ 972.185604] [<c003dc5d>] (sys_reboot+0x105/0x15c) from [<c000c841>]
(ret_fast_syscall+0x1/0x46)
[ 972.194795] drm_kms_helper: panic occurred, switching back to text
console
This error is known on v3.8..
Regards,
I'm apparently an idiot.
to elaborate, it's working fine now. i had misread the instructions and was
expecting the LEDs to stay full on when it finished flashing. when it
shutdown i had assumed the worst. so i tried it again with the serial cable
connected and saw the kernel panic and that just cemented the notion that i
somehow broke it.
thanks for entertaining a fools question.
--MikeW