Hi, Please go through chapter 4 of sprue66 (DM6446) or sprue73 (DM355) as these contains the instructions for setting up your build machine & building the kernel in more detail than I am prepared to write. Also, if you want help from the list you need to be more specific than saying 'it do not work'. We need to see the output of the build (for kernel build issues) and u-boot environment + log of console output for booting related issues. We may be good here but we are not psychic.. Regards Phil Q Phil Quiney, Senior Software Engineer Trinity Convergence Cambridge Business Park Cowley Road Cambridge CB4 0WZ, UK T: +44(0)1223-435536 F: +44(0)1223-435560 www.trinityconvergence.com <http://www.trinityconvergence.com/>
________________________________ From: Ondrej Pindroch [mailto:[EMAIL PROTECTED] Sent: 03 July 2008 08:21 To: Phil Quiney Subject: RE: Bad kernel bootargs, or bad whole kernel Thak you for your answer. However I am realy new in LINUX could you pleas write me a more detailed instruction how to build kernel and modules. Or where to find all modules needed for DVEVM. I have tried to build kernel according to instruction from TI spruf88A.pdf. And it do not work. Thanks Ondrej Pindroch SoftHard Technology ltd. -----Original Message----- From: "Phil Quiney" <[EMAIL PROTECTED]> To: "Ondrej Pindroch" <[EMAIL PROTECTED]>, "davinci-linux-open-source" <davinci-linux-open-source@linux.davincidsp.com> Date: Fri, 27 Jun 2008 13:20:34 +0100 Subject: RE: Bad kernel bootargs, or bad whole kernel Hi I assume you have rebuilt the kernel? You need to do the following steps.... build kernel (make uImage) build modules (make modules) Now you need to install the modules.....a command like this will do mkdir /tmp/my_modules make INSTALL_MOD_PATH=/tmp/my_modules modules_install As root cd /tmp/my_modules chown -R 0.0 lib tar -czf modules.tgz lib Copy the modules.tgz onto the target and untar in / Now you will have a kernel & modules that are consistent - these should load OK. You can make the link between kernel & modules more explicit by adding some text to the line in the 'localversion' file. This currently contains the '_mvl401' part of the kernel name you see if you do a 'uname -a' on the target. You can add your own text... this has the advantage that you do not overwrite existing kernel modules on the target and can easily confirm that you are running the modified kernel. Regards Phil Q Phil Quiney, Senior Software Engineer Trinity Convergence Cambridge Business Park Cowley Road Cambridge CB4 0WZ, UK T: +44(0)1223-435536 F: +44(0)1223-435560 www.trinityconvergence.com <http://www.trinityconvergence.com/>
_______________________________________________ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
