hai,
i tried to debug the boot process..
i went with some ideas to find the why such error comes..
[1] i tried to boot the kernel with init=/hello_world option.. i removed
all the rootfs files like /dev /usr /opt /bin /sbin folder and files
except hello_world option
----to make sure that my print is able to execute when
booting was done
but i got different reply from my kernel
error log1
=======
[ 5.800505] VFS: Mounted root (nfs filesystem) on device 0:12.
[ 5.807034] devtmpfs: error mounting -2
[ 5.811496] Freeing init memory: 288K
[* 5.818299] Failed to execute /hello_arm. Attempting defaults...*
[ 5.825859] Kernel panic - not syncing: No init found. Try passing
init= option to kernel. See Linux Documentation/init.txt for guidance.
also i'm not able to get the printed message !!!!
procedure i followed to boot the kernel from my board .i h'v done the
booting with sd card using uEnv.txt file...
On Monday, 17 March 2014 15:09:43 UTC+5:30, siva kumar wrote:
>
> when u saw my uEnv.txt file i used to boot the args without initrd
> address as you said
> *# uenvcmd=run boot_ftd; run device_args; bootz 0x80200000
> 0x81000000:${initrd_size} 0x815f0000*
> *uenvcmd=run boot_ftd; run device_args; bootz 0x80200000 - 0x815f0000*
>
> any ideas ...how to come back the kernel to boot up!!
>
>
> On Saturday, 15 March 2014 04:10:25 UTC+5:30, john3909 wrote:
>>
>>
>> From: William Hermans <yyr...@gmail.com>
>> Reply-To: <beagl...@googlegroups.com>
>> Date: Friday, March 14, 2014 at 2:27 PM
>> To: <beagl...@googlegroups.com>
>> Subject: Re: [beagleboard] Re: Kernel panic - not syncing: No init
>> found. Try passing init= option to kernel.
>>
>> NFS root as done on ARCH, Debian, and busybox will not work the same way
>> on ubuntu. Nor fedora or Angstrom for that matter. What you need to do is
>> find a how to for netbooting Ubuntu ( PC ) and adapt it.
>>
>> obviously going by the error messages above, this configuration does not
>> like your initial ramdisk ( initrd ) for some reason.
>>
>> NFS booting is not compatible with Initrd. Thus the kernel must be built
>> without Initrd configured and uenvcmd has a dash instead of an Initrd
>> memory load address.
>>
>> Regards,
>> John
>>
>>
>>
>>
>> On Fri, Mar 14, 2014 at 7:55 AM, siva kumar <boopathi...@gmail.com>wrote:
>>
>>> hello john,
>>> thanks for your help
>>> some how i understood the flow of kernel booting from nfs
>>> but still i got the same error report
>>> 6.876536] ALSA device list:
>>> [ 6.879838] #0: TI BeagleBone Black
>>> [ 6.889766] VFS: Mounted root (nfs filesystem) on device 0:12.
>>> [ 6.896385] devtmpfs: mounted
>>> [ 6.899975] Freeing init memory: 292K
>>> [ 6.907579]
>>> *[ 6.920985] Kernel panic - not syncing: No init found. Try passing
>>> init= option to kernel. See Linux Documentation/init.txt for guidance.*
>>> [ 6.934045] [<c001367c>] (unwind_backtrace+0x0/0xe0) from
>>> [<c05e6d00>] (panic+0x84/0x1e0)
>>> [ 6.942611] [<c05e6d00>] (panic+0x84/0x1e0) from [<c05e1a80>]
>>> (kernel_init+0xb8/0xe4)
>>> [ 6.950812] [<c05e1a80>] (kernel_init+0xb8/0xe4) from [<c000d918>]
>>> (ret_from_fork+0x14/0x3c)
>>> [ 6.959639] drm_kms_helper: panic occurred, switching back to text
>>> console
>>>
>>>
>>> this is my uEnv.txt file
>>> ================
>>>
>>> *kernel_file=zImage*
>>> *initrd_file=uInitrd*
>>> *initrd_high=0xffffffff*
>>> *fdt_high=0xffffffff*
>>>
>>> *serverip=192.168.1.69*
>>> *ipaddr=192.168.1.61*
>>> *gwaddr=192.168.1.100*
>>> *netmask=255.255.255.0*
>>>
>>> *#Video: Uncomment to override:*
>>> *#kms_force_mode=video=HDMI-A-1:1024x768@60*
>>>
>>> *##BeagleBone Cape Overrides*
>>> *##Note: On the BeagleBone Black, there is also an uEnv.txt in the eMMC,
>>> so if these changes do not seem to be makeing a difference...*
>>>
>>> *##BeagleBone Black:*
>>> *# Disable HDMI/eMMC*
>>> *# Note it is necessary to disable BOTH HDMI and HDMIN (no audio)
>>> "capes"*
>>> *# in order to use the HDMI pins for I/O*
>>>
>>> *#optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G*
>>>
>>> *# Default to leaving the HDMIN "cape" enabled, so HDMI works "out of
>>> the box"*
>>> *# Comment the line below and uncomment the optargs= line above to use
>>> an unmodified*
>>> *# BeBoPr or other board that uses the HDMI/LCD pins *
>>> *#siva optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONE-EMMC-2G
>>> capemgr.enable_partno=BB-BONE-AUDI-02*
>>>
>>> *console=ttyO0,115200n8*
>>>
>>> *mmcroot=/dev/mmcblk0p2 ro*
>>> *mmcrootfstype=ext4 rootwait fixrtc*
>>> *# ip_method=${ipaddr}:${serverip}:${gwaddr}:${netmask}::eth0:off*
>>>
>>> *ip_method=192.168.1.61:192.168.1.69:192.168.1.100:255.255.255.0::eth0:off*
>>> *nfsrootdev=/dev/nfs rw*
>>> *nfsroot=192.168.1.69:/home/cis-69/targetNFS ,vers=3*
>>> *nfsrootfstype=ext4 rootwait fixrtc *
>>> *nfsargs=setenv bootargs console=${console} ${optargs} ${kms_force_mode}
>>> root=${nfsrootdev} rootfstype=${nfsrootfstype} nfsroot=${nfsroot}
>>> init=/lib/modules/3.8.13/init mem=456M vram=50M ${expansion} *
>>> *#video=HDMI-A-1:1280x1024@60 ${expansion} *
>>>
>>> *loadkernel=tftp 0x80200000 ${kernel_file}*
>>> *loadinitrd=tftp 0x81000000 ${initrd_file}; setenv initrd_size
>>> ${filesize}*
>>> *loadfdt=tftp 0x815f0000 ${fdtfile}*
>>>
>>> *boot_classic=run loadkernel; run loadinitrd*
>>> *# boot_ftd=run loadkernel; run loadinitrd; run loadfdt*
>>> *boot_ftd=run loadkernel; run loadfdt*
>>>
>>> *device_args=run expansion_args; run nfsargs*
>>> *mmcargs=setenv bootargs console=${console} ${optargs} rootdelay=5
>>> ${kms_force_mode} root=${mmcroot} rootfstype=${mmcrootfstype} ${expansion}*
>>>
>>> *expansion_args=setenv expansion ip=${ip_method}*
>>> *#Classic Board File Boot:*
>>> *#uenvcmd=run boot_classic; run device_args; bootz 0x80200000
>>> 0x81000000:${initrd_size}*
>>> *#New Device Tree Boot:*
>>> *# uenvcmd=run boot_ftd; run device_args; bootz 0x80200000
>>> 0x81000000:${initrd_size} 0x815f0000*
>>> *uenvcmd=run boot_ftd; run device_args; bootz 0x80200000 - 0x815f0000*
>>>
>>>
>>> i tried this *init=/lib/modules/3.8.13/init option but no use of it *
>>>
>>> help me out fix this issue
>>>
>>>
>>>
>>>
>>>
>>> On Friday, 14 March 2014 11:20:15 UTC+5:30, john3909 wrote:
>>>>
>>>>
>>>> From: siva kumar <boopathi...@gmail.com>
>>>> Reply-To: <beagl...@googlegroups.com>
>>>>
>>>> Date: Thursday, March 13, 2014 at 9:58 PM
>>>> To: <beagl...@googlegroups.com>
>>>>
>>>> Subject: [beagleboard] Re: Kernel panic - not syncing: No init found.
>>>> Try passing init= option to kernel.
>>>>
>>>>
>>>> hai all,
>>>>
>>>> can anybody help me how to boot the rootfs using nfs ..still i stuck
>>>> with same issue..
>>>> currently i'm using ubuntu13.10 as a host pc to implement nfs booting.
>>>> i referred the following link to build the kernel
>>>> http://wiki.beyondlogic.org/index.php/BeagleBoneBlack_Building_Kernel
>>>> http://elinux.org/Building_BBB_Kernel
>>>>
>>>> I attached my uEnv.txt file I use for NFS. Make sure you change the IP
>>>> address and <userID> for nfsroot to match your host IP and userID. My
>>>> local
>>>> network uses an address 10.100.116.xxx. My BBB is 10.100.116.104 and my
>>>> host is 10.100.116.73.
>>>>
>>>> You need to install nfs-kernel-server on your Ubuntu host
>>>>
>>>> Add the following line to your /etc/exports file on your host
>>>>
>>>> /home/<userID>/targetNFS 10.100.116.0/255.255.255.0(rw,
>>>> insecure,async,no_wdelay,no_root_squash,no_subtree_check)
>>>>
>>>> Place your rootfs in /home/<userID>/targetNFS on your host
>>>>
>>>> sudo service nfs-kernel-server restart
>>>>
>>>> I think that is all, so NFS should work for you. I hope this helps.
>>>>
>>>> Regard,
>>>> John
>>>>
>>>>
>>>>
>>>> regards
>>>> siva
>>>>
>>>>
>>>>
>>>> On Wednesday, 12 March 2014 15:43:34 UTC+5:30, siva kumar wrote:
>>>>>
>>>>> hai ,
>>>>>
>>>>> i try to mount the rootfs using nfs for my beagle bone back..while
>>>>> booting the kernel i'm facing the following issue ..
>>>>>
>>>>> error log message :
>>>>> =============
>>>>>
>>>>> 5.745517] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>>>>> [ 5.758912] IP-Config: Complete:
>>>>> [ 5.762359] device=eth0, hwaddr=90:59:af:5b:d4:88,
>>>>> ipaddr=192.168.1.61, mask=255.255.255.0, gw=192.168.1.100
>>>>> [ 5.773113] host=192.168.1.61, domain=, nis-domain=(none)
>>>>> [ 5.779231] bootserver=192.168.1.69, rootserver=192.168.1.69,
>>>>> rootpath=
>>>>> [ 5.786438] ALSA device list:
>>>>> [ 5.789741] #0: TI BeagleBone Black
>>>>> *[ 5.799661] VFS: Mounted root (nfs filesystem) on device 0:12.*
>>>>> [ 5.808793] devtmpfs: mounted
>>>>> [ 5.812347] Freeing init memory: 292K
>>>>> *[ 5.822210] Kernel panic - not syncing: No init found. Try
>>>>> passing init= option to kernel. See Linux Documentation/init.txt for
>>>>> guidance.*
>>>>> [ 5.835271] [<c001367c>] (unwind_backtrace+0x0/0xe0) from
>>>>> [<c05e6d00>] (panic+0x84/0x1e0)
>>>>> [ 5.843839] [<c05e6d00>] (panic+0x84/0x1e0) from [<c05e1a80>]
>>>>> (kernel_init+0xb8/0xe4)
>>>>> [ 5.852039] [<c05e1a80>] (kernel_init+0xb8/0xe4) from [<c000d918>]
>>>>> (ret_from_fork+0x14/0x3c)
>>>>> [ 5.860868] drm_kms_helper: panic occurred, switching back to text
>>>>> console
>>>>>
>>>>>
>>>>>
>>>>> i used the following procedure to build the kernel
>>>>>
>>>>>
>>>>> U-Boot> setenv ipaddr 192.168.1.61
>>>>> U-Boot> setenv serverip 192.168.1.69
>>>>> U-Boot> tftpboot 0x80200000 uImage-BBB
>>>>> U-Boot> setenv bootargs console=ttyO0,115200n8 root=/dev/nfs rw
>>>>> nfsroot=192.168.1.69:/nfsroot ip=192.168.1.61:192.168.1.69:
>>>>> 192.168.1.100:255.255.255.0::eth0
>>>>> U-Boot> bootm 0x80200000
>>>>>
>>>>> i tried with vaious bootargs for nfs booting but no success !!!
>>>>>
>>>>> [1] setenv bootargs 'console=ttyO0,115200n8 noinitrd,3 root=/dev/nfs
>>>>> ip=192.168.1.61:192.168.1.69:192.168.1.100:255.255.255.0::eth0
>>>>> rootwait rw nolock,rsize=1024,wsize=1024,rootdelay=2
>>>>> nfsroot=192.168.1.69:/nfsroot '
>>>>>
>>>>> [2]setenv bootargs 'console=ttyO0,115200n8 noinitrd root=/dev/nfs
>>>>> nfsroot=192.168.1.69:/nfsroot rw ip=192.168.1.61:192.168.1.69:
>>>>> 192.168.1.100:255.255.255.0::eth0:'
>>>>> and so on..
>>>>>
>>>>> pls share your experience to get my kernel bootable...
>>>>>
>>>>> regards
>>>>> siva
>>>>>
>>>>>
>>>>> --
>>>> 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 beagleboard...@googlegroups.com.
>>>>
>>>> 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 beagleboard...@googlegroups.com.
>>> 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 beagleboard...@googlegroups.com.
>> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
