From:  siva kumar <[email protected]>
Reply-To:  <[email protected]>
Date:  Sunday, March 9, 2014 at 9:26 PM
To:  <[email protected]>
Subject:  [beagleboard] Re: booting error with BBB [Error:
unrecognized/unsupported machine ID (r1 = 0x00000e05).]

> buddy..
> thanks for your useful information..
> now i can able to boot the kernel from scratch !!!!..
> but as usual kernel panic error occurred ...this might be a problem with nfs
> configuration!!!!
> [    4.688893] IP-Config: Complete:
> [    4.692338]      device=eth0, hwaddr=90:59:af:5b:d4:88,
> ipaddr=192.168.1.61, mask=255.255.255.0, gw=192.168.1.100
> [    4.703098]      host=192.168.1.61, domain=, nis-domain=(none)
> [    4.709215]      bootserver=192.168.1.69, rootserver=192.168.1.69,
> rootpath=
> [    4.716420] ALSA device list:
> [    4.719726]   #0: TI BeagleBone Black
> [    4.860556] VFS: Mounted root (nfs filesystem) on device 0:12.
> [    4.867169] devtmpfs: mounted
> [    4.870723] Freeing init memory: 292K
> [    4.926371] Kernel panic - not syncing: No init found.  Try passing init=
> option to kernel. See Linux Documentation/init.txt for guidance.
> [    4.939425] [<c001367c>] (unwind_backtrace+0x0/0xe0) from [<c05e6d00>]
> (panic+0x84/0x1e0)
> [    4.947988] [<c05e6d00>] (panic+0x84/0x1e0) from [<c05e1a80>]
> (kernel_init+0xb8/0xe4)
> [    4.956185] [<c05e1a80>] (kernel_init+0xb8/0xe4) from [<c000d918>]
> (ret_from_fork+0x14/0x3c)
> [    4.965008] drm_kms_helper: panic occurred, switching back to text console
NFS doesn¹t like initrd, so you must build your kernel without initrd and
replace the initrd reference with a - (dash) in uEnv.txt so uenvcmd will
look like this
uenvcmd=run boot_ftd; run device_args; bootz 0x80200000 - 0x815f0000

Regards,
John
> 
> 
> 
> 
> On Sunday, 9 March 2014 07:25:56 UTC+5:30, t-szczyrba  wrote:
>> Looks like DT file loading before booting is missing.
>> For kernels >3.2 and BBB you should pre-load dtb with u-boot to boot
>> succesfully (or append dtb file to kernel image, but have to
>> CONFIG_ARM_APPENDED_DTB kernel compile option enabled).
>> 
>> There is also a possibility that dtb is loaded correctly, but the kernel is
>> too big and when decompresses overwrites dtb - it easy to check if the
>> situation happened in your case with nm tool- no symbol should be loaded
>> above c0f80000 for default u-boot config,
>> 
>> T.
> 
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to