I'm sorry, I forgot to tell you in my last comment that I don't have those 
files:

/boot/dtbs/$(uname -r)/*.dtb 
/boot/vmlinuz-$(uname -r)

Maybe the tutorial I followed is not very up to date, It says nothing about 
those files so I don't know where to get them.

Thanks


El lunes, 20 de julio de 2015, 21:05:54 (UTC+2), RobertCNelson escribió:
>
> On Mon, Jul 20, 2015 at 1:51 PM, Pablo <[email protected] <javascript:>> 
> wrote: 
> > Hi, I have a BBB rev C. 
> > 
> > I installed the latest debian image (2015-03-01, Kernel: 3.8.13-bone70) 
> and 
> > flashed it to the eMMC. After that, I followed some instructions to 
> install 
> > a Preempt kernel. 
> > The guide I followed is this one: 
> > 
> http://dev.ardupilot.com/wiki/building-the-code/building-for-beaglebone-black-on-linux/
>  
> > 
> > Apparently, all went well. I only skipped a step where I had to make a 
> > backup of a zImage. And that's one problem, there's nothing in 
> /boot/uboot/, 
> > I can't find zImage... Is that normal? I thought that zImage was called 
> at 
> > boot time to load everything, so where does my BBB boot from? 
> > 
> > But the installation of Preempt looks fine. 
> > 
> > root@beaglebone:~# ls /lib/modules 
> > 3.8.13-bone70  3.8.13-rt9-00899-g6d55dce-dirty 
> > 
> > I have the rt folder, but 
> > 
> > root@beaglebone:~# uname -a 
> > Linux beaglebone 3.8.13-bone70 #1 SMP Fri Jan 23 02:15:42 UTC 2015 
> armv7l 
> > GNU/Linux 
> > 
> > i'm still running the old kernel version, how can I boot from the 
> Preempt 
> > kernel? 
>
> Make sure you set the uname_r variable in: 
>
> /boot/uEnv.txt 
>
> uname_r=3.8.13-rt9-00899-g6d55dce-dirty 
>
> Then make sure: 
>
> /boot/dtbs/$(uname -r)/*.dtb 
> /boot/vmlinuz-$(uname -r) 
>
> exist... 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
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