Re: [beagleboard] RobertCNelson Tree
On 07/26/14 11:26, William Hermans wrote: /It's not weak, It's empty. But, my focus was using a easier/ /cross-compiler rather than building my own./ /I will get crosstool-ng when I have more time to test before I publish./ You have a problem with the Linaro toolchain ? That is what is used for uboot and the kernel . . . I'm not saying to be snide or sarcastic, really, but anyone can play that nonsense game: You have a problem with a crosstool-ng tool chain? And to the next statement: which uboot and kernel? *The* uboot and kernel? Not mine: http://ttylinux.net/dloadBBN.html The Linux-targeted cross tool chain has an associated glibc and kernel interface; I build versions of those of my own preference to suit my ttylinux distribution. That is why I build my cross tool chain from sources with crosstool-ng. With this approach I have commonality to make ttylinux for mac-g4, beaglebone, i486, i686, x8_64 of the same versions of glibc and Linux kernel, each built with a crosstool-ng produced cross tool chain constructed with the proper glibc and kernel interfaces. https://github.com/djerome/crosslinux The world does not revolve around what you happen to use. Just most of it. :) -- 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.
Re: [beagleboard] RobertCNelson Tree
On 07/26/14 15:10, Lucas Tanure wrote: Jerome, Sorry I didn't understand what you want, or complain about that page. Feel free to edit and add what you think is important. I can only write about things I know, and understand. That tip about Linaro toolchain was very good thanks, I will take a look. The wiki is for anyone, from anyone. So add your way, so people can know of. Whoa, I really don't mean to sound cross about anything. For that page, my critique is: from the terseness of the crosstool-ng part it lacks usefulness and I'm willing to help. My first name is Douglas, not Jerome. Willian, I feel the same way, I just want to build my kernel, boot and use. I'm not a expert, I'm a newbie, so I need first a easier and faster way to get where I want. For me, what I know about crosstool-ng is that you can choose many variables and build a perfect compiler for you, using uLibc, gLibc what ever you need. And I don't see yet why In that case perhaps crosstool-ng may be the way to go. . What I'm missing in this case ? What crosstool-ng is so much better than a preconfigured gcc from ubuntu servers ? For what it's worth, from someone who uses crosstool-ng but not a pre-built cross tool chain, I don't think it's fair to say crosstool-ng is so much better in an open ended way. When you build code for a Linux system the tool chain supplies the glibc interface (header files and library files) which has the Linux kernel system call interface; if you want some particular version of those, then building your own cross-tool chain with those versions can be so much better than using a pre-built cross tool chain. If you use a pre-built cross tool chain, what versions of glibc and Linuc kernel is your cross-built code targeted to? I am being glibc-centric here, I know. Cheers. -- 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.
Re: [beagleboard] minimal kernel v3.8
Hi, I know I'm some days late with this but you can also take a look at ttylinux kernel for beaglebone. The kernel is small but larger than his; it is in the ttylinux-beagle_bone-2014.10.tar.bz2 file: http://ttylinux.net/dloadBBN.html On 07/18/14 07:26, Maxim Podbereznyy wrote: Thank you Jeronimo! I will check the folders of modules 18 Июл 2014 г. 18:23 пользователь Jerônimo Lopes lopesjeron...@gmail.com mailto:lopesjeron...@gmail.com написал: Hi Maxim, I'm no expert in kernel build, just sharing my own experience. 2014-07-18 4:52 GMT-03:00 Maxim Podbereznyy lisar...@gmail.com mailto:lisar...@gmail.com: Hi! I need to compile a minimal kernel v3.8 for BBB. With instructions from RCN the kernel builds with the final size of 5.5M for zImage and 32M for modules. I need to reduce this size but yet don't want to lose any capes support. I'm currently using buildroot, and (almost) default beaglebone configuration. The result is a kernel image has 3.5 Mb, and about 0.5 Mb for modules. So it's possible. But, no cape manager support. Can any body suggest how to reduce it? Looking into defconfig drives me crazy because it seems that anything could be enabled was enabled statically or dynamically. I'd say, try to check the biggest folders at modules, and start checking if you really need that module(s) on your system. For example, I just check some tests that I've made with RCN kernel (using default configuration), the result is about 103 Mb of modules. 14Mb of those, are at the 'fs', in this case I won't use anything but ext2/4, so disable it. And so on. First check the big villains. -- LinkedIn - http://www.linkedin.com/in/maximpodbereznyy Company - http://www.linkedin.com/company/mentorel Facebook - https://www.facebook.com/mentorel.company -- 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 mailto:beagleboard+unsubscr...@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 mailto:beagleboard+unsubscr...@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 mailto:beagleboard+unsubscr...@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.
[beagleboard] Bug in github.com/beagleboard/kernel/tree/3.8
Robert, are you (one of the folks) maintaining the github repo for BeagleBone kernel patches? If not, who do I send this too? This patch in the 3.8 branch doesn't seem to work; it just makes a bug or two: https://github.com/beagleboard/kernel/blob/3.8/patches/build/0002-headers_install-Fix-build-failures-on-deep-directory.patch Lines 37, 38 of that patch change from giving file names using command line arguments to giving them in standard input, but the perl program doesn't read standard input and it doesn't handle the files. The perl script is scripts/headers_install.pl Attached is an instrumented copy of the perl script; you can diff it to see what it does. Try this script on the last change before that patch was applied, 2013-03-22 commit 41dbd166a6394be45389e25459cd127854615366 and after 2013-03-25 commit 20e92cc2b03d5934b142785bf4ae96f1335d77cd Try make ARCH=arm headers_install and then look in linux-3.8/usr/include/asm; you will notice the missing files. -- 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. headers_install.pl Description: Perl program
[beagleboard] BeagleBone CT-NG Tool Chain
Hello, I am trying to build a cross tool chain for the BeagleBone (white), rev A3. The problem I have is the kernel header files; the kernel is from https://github.com/beagleboard/kernel/tree/3.8 and no kernel later than the 2013-03-22 from that tree can properly export its header files. Is anyone using crosstool-ng to make a cross tool chain for making the latest BeagleBone 3.8.4 kernel+modules? I've look at using https://rcn-ee.net/deb/wheezy-armhf/v3.8.13-bone43/linux-headers-3.8.13-bone43_1.0wheezy_armhf.deb but I've not found a way to use that to successfully build a crosstool-ng tool chain. -- 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.
Re: [beagleboard] Re: Kernel panic - not syncing: No init found. Try passing init= option to kernel.
On 03/19/14 23:53, siva kumar wrote: hai, yes u r right , i try to mount my file system using nfs, i also cross checked my rootfs that shows that /bin/bash file not available .. i dont know how that was missed ..!!! when i look out my targetNFS directory (which is my actual nfs mount folder) the following dir's available *bin dev home media proc sbin sys usr* *boot etc lib mntruntmp var* inside /bin i'm not able to find any executable like *bash.* *but all the files are compiled for arm arch . * *i ran * *targetNFS/bin#file ** * ash:symbolic link to `busybox busybox:ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.16, stripped cat:symbolic link to `busybox' chattr: symbolic link to `busybox' chgrp: symbolic link to `busybox' chmod: symbolic link to `busybox' chown: symbolic link to `busybox' * and so on .. . . . regards siva I suggest you set init to /bin/ash and see if you get a shell when you boot. Also *look* for init in the file system; it probably is /sbin/init, but verify you know where it is and after you see the init=/bin/ash work then try your verified init pathname. -- 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.
Re: [beagleboard] Re: Kernel panic - not syncing: No init found. Try passing init= option to kernel.
Control yourself. Stop doing random things. Put the directories back into the file system. Change to using init=/bin/bash and see if you get a shell prompt when you boot. On 03/17/14 06:05, siva kumar wrote: 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... -- 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.
Re: [beagleboard] Re: Kernel panic - not syncing: No init found. Try passing init= option to kernel.
I build linux Linux systems that run on their inital RAM disk
and I can NFS boot them, so I don't think the kernel haveing
initrd capability does anything wrong.
Maybe I missed something in the thread, but why are
you using /lib/modules/3.8.13/init ??
When I see this
Kernel panic - not syncing: No init found. Try
passing init= option to kernel.
message it is because the /sbin/init program the kernel
tries to run is missing a dynamic dependency. This sort
of thing happens when you build a whole (small) system
from scratch.
Try using init=/bin/bash just to see if it runs. If so,
it isn't an NFS root problem per se, is is a problem
with the program you are using for init.
On 03/14/14 15:40, John Syn wrote:
From: William Hermans yyrk...@gmail.com mailto:yyrk...@gmail.com
Reply-To: beagleboard@googlegroups.com
mailto:beagleboard@googlegroups.com
Date: Friday, March 14, 2014 at 2:27 PM
To: beagleboard@googlegroups.com mailto:beagleboard@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
boopathisivaku...@gmail.com mailto:boopathisivaku...@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=0x*
*fdt_high=0x*
*
*
*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 0x8020 ${kernel_file}*
