Re: [linux-yocto] [yocto] Timestamp error between zImage & uname-a [ Yocto-2.6.1 + Qemux86 ]
It's picking up the minimal image instead of full-cmdline? Can you try: runqemu tmp/deploy/images/qemux86/ or runqemu qemux86 core-image-full-cmdline Thanks, Anuj On Fri, 2019-05-10 at 06:46 +, AshishKumar Mishra wrote: > HI Members , > Good Afternoon. > > I am trying to recompile the kernel after changing kernel-config > option and then recompile the kernel using below mentioned steps > 1) bitbake -c menuconfig virtual/kernel > 2) bitbake -c diffconfig virtual/kernel ( copy the config- > fragment to ~/Desktop) > 3) bitbake -C deploy linux-yocto ( to recompile kernel ) > 4) runqemu qemux86 > > The timestamp of files in tmp/deploy/images/qemux86/* is updated > properly but the time shown by command "uname -a" always shows > older time & is not showing recently compiled times. > > I checked the kernel config options in image , i can see the changes > i did > from menuconfig , but not sure / confused as to why the time shown > by "uname -a" is not getting updated. > > Basically i am trying to change some kernel-config & check if the > compiled > kernel is getting updated or not. > > Attached along are the snapshot for the error. > > Can members please let me know what am i doing wrong here or missing, > > Thanks > Ashish. > > > > > > > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [yocto] Timestamp error between zImage & uname-a [ Yocto-2.6.1 + Qemux86 ]
HI Anuj , I was building minimal image using $ bitbake core-image-minimal haven't tried full-cmdline. Not able to track why kernel "uname" has older timestamp rather than the one from build/deploy/image as seen by "ls -al Am i missing any command or sequence here -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [yocto] Timestamp error between zImage & uname-a [ Yocto-2.6.1 + Qemux86 ]
Yes . But this difference we expect in some minutes. But what i am observing is ( attached snapshot ) :- 1) First Compilation around ( 4:10) bitbake cleanall + bitbake core-image-minimal uname-a: Time shown is 4:24 timestamp of files in deploy/images/: Time shown is around 4:30 2) Second Compilation around ( 5:00) bitbake -c menuconfig virtual/kernel + bitbake -C deploy linux-yocto uname-a: Time shown is 4:24 timestamp of files in deploy/images/: Time shown is around 5:25 2) Second Compilation around ( 5:00) bitbake -c menuconfig virtual/kernel + bitbake -C deploy linux-yocto uname-a: Time shown is 4:24 timestamp of files in deploy/images/: Time shown is around 5:25 3) Third Compilation around ( 5:45) bitbake -c menuconfig virtual/kernel + bitbake -C deploy linux-yocto uname-a: Time shown is 4:24 timestamp of files in deploy/images/: Time shown is around 6:05 So , time shown by "uname -a" is retains older value even though i had compiled the linux multiple times . Currently , only way i am able to bypass this behavior is to do bitbake -c cleanall linux-yocto before every compilation. Thanks Ashish On Fri, May 10, 2019 at 10:23 PM Khem Raj wrote: > > > On 5/10/19 12:10 AM, AshishKumar Mishra wrote: > > HI Anuj , > > > > I was building minimal image using $ bitbake core-image-minimal haven't > > tried full-cmdline. > > > > Not able to track why kernel "uname" has older timestamp rather than > > the one from build/deploy/image > > as seen by "ls -al > > > > Am i missing any command or sequence here > > > > > > uname will show the time when it was built, which might be different > time then the one when it was copied over to deploy. > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [yocto] Timestamp error between zImage & uname-a [ Yocto-2.6.1 + Qemux86 ]
Hi Ashish, On Mon, May 13, 2019 at 5:57 AM AshishKumar Mishra < ashish.emailaddr...@gmail.com> wrote: > So , time shown by "uname -a" is retains older value even though > i had compiled the linux multiple times . > This is normal behaviour, even when building the kernel directly (eg. not using Yocto). It is a bit surprising at first, but it all comes down to dependencies in the Makefile for the kernel. The version string displayed by "uname -a" comes from init/version.c in the kernel source tree. Specifically the symbol UTS_VERSION, which is defined in include/generated/compile.h. This file is produced when you first build, and remains thereafter, unless you do "make clean" or equivalent. Currently , only way i am able to bypass this behavior is to do bitbake -c > cleanall linux-yocto > before every compilation. > You can delete the include/generated/compile.h file in your kernel build directory. Upon rebuild of kernel, the file will be re-created with the current date/time. Regards Ralph -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [yocto] Timestamp error between zImage & uname-a [ Yocto-2.6.1 + Qemux86 ]
Thanks Ralph for informative reply . Will check once again after deleting the file you suggested . Ashish On Mon, May 13, 2019, 7:05 PM Ralph Siemsen wrote: > Hi Ashish, > > On Mon, May 13, 2019 at 5:57 AM AshishKumar Mishra < > ashish.emailaddr...@gmail.com> wrote: > >> So , time shown by "uname -a" is retains older value even though >> i had compiled the linux multiple times . >> > > This is normal behaviour, even when building the kernel directly (eg. not > using Yocto). It is a bit surprising at first, but it all comes down to > dependencies in the Makefile for the kernel. > > The version string displayed by "uname -a" comes from init/version.c in > the kernel source tree. Specifically the symbol UTS_VERSION, which is > defined in include/generated/compile.h. This file is produced when you > first build, and remains thereafter, unless you do "make clean" or > equivalent. > > Currently , only way i am able to bypass this behavior is to do bitbake -c >> cleanall linux-yocto >> before every compilation. >> > > You can delete the include/generated/compile.h file in your kernel build > directory. Upon rebuild of kernel, the file will be re-created with the > current date/time. > > Regards > Ralph > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
