Heh, perfect example of why one need to update the APT cache . . . william@beaglebone:~$ *sudo apt-get update* william@beaglebone:~$ *apt-cache search linux-image-4 |grep bone-rt* linux-image-4.0.8-bone-rt-r8 - Linux kernel, version 4.0.8-bone-rt-r8 linux-image-4.1.10-bone-rt-r16 - Linux kernel, version 4.1.10-bone-rt-r16 linux-image-4.1.11-bone-rt-r16 - Linux kernel, version 4.1.11-bone-rt-r16 linux-image-4.1.12-bone-rt-r16 - Linux kernel, version 4.1.12-bone-rt-r16 linux-image-4.1.13-bone-rt-r16 - Linux kernel, version 4.1.13-bone-rt-r16 linux-image-4.1.13-bone-rt-r17 - Linux kernel, version 4.1.13-bone-rt-r17 linux-image-4.1.14-bone-rt-r17 - Linux kernel, version 4.1.14-bone-rt-r17 linux-image-4.1.15-bone-rt-r17 - Linux kernel, version 4.1.15-bone-rt-r17 linux-image-4.1.15-bone-rt-r18 - Linux kernel, version 4.1.15-bone-rt-r18 linux-image-4.1.16-bone-rt-r18 - Linux kernel, version 4.1.16-bone-rt-r18 linux-image-4.1.17-bone-rt-r18 - Linux kernel, version 4.1.17-bone-rt-r18 linux-image-4.1.17-bone-rt-r19 - Linux kernel, version 4.1.17-bone-rt-r19 linux-image-4.1.18-bone-rt-r19 - Linux kernel, version 4.1.18-bone-rt-r19 linux-image-4.1.3-bone-rt-r15 - Linux kernel, version 4.1.3-bone-rt-r15 linux-image-4.1.5-bone-rt-r15 - Linux kernel, version 4.1.5-bone-rt-r15 linux-image-4.1.7-bone-rt-r16 - Linux kernel, version 4.1.7-bone-rt-r16 linux-image-4.1.8-bone-rt-r16 - Linux kernel, version 4.1.8-bone-rt-r16 linux-image-4.1.9-bone-rt-r16 - Linux kernel, version 4.1.9-bone-rt-r16 linux-image-4.4.0-bone-rt-r1 - Linux kernel, version 4.4.0-bone-rt-r1 linux-image-4.4.0-bone-rt-r2 - Linux kernel, version 4.4.0-bone-rt-r2 linux-image-4.4.0-bone-rt-r3 - Linux kernel, version 4.4.0-bone-rt-r3 linux-image-4.4.0-rc8-bone-rt-r1 - Linux kernel, version 4.4.0-rc8-bone-rt-r1 linux-image-4.4.1-bone-rt-r4 - Linux kernel, version 4.4.1-bone-rt-r4 linux-image-4.4.1-bone-rt-r5 - Linux kernel, version 4.4.1-bone-rt-r5 *linux-image-4.4.2-bone-rt-r5 - Linux kernel, version 4.4.2-bone-rt-r5*
On Thu, Feb 25, 2016 at 8:04 PM, William Hermans <[email protected]> wrote: > *I started from the Jessie BBB image that had the 4.1.15-ti-rt-r43 kernel. >> Now I have the 4.4.2-bone-rt-r5 kernel that I compiled and installed >> myself, am I maybe missing some udev rules?* >> > > If I were you, I would . . . > > $ *apt-cache search linux-image-4 |grep bone-rt* > linux-image-4.0.6-bone-rt-r5 - Linux kernel, version 4.0.6-bone-rt-r5 > linux-image-4.0.6-bone-rt-r6 - Linux kernel, version 4.0.6-bone-rt-r6 > linux-image-4.0.7-bone-rt-r7 - Linux kernel, version 4.0.7-bone-rt-r7 > linux-image-4.0.8-bone-rt-r8 - Linux kernel, version 4.0.8-bone-rt-r8 > linux-image-4.1.10-bone-rt-r16 - Linux kernel, version 4.1.10-bone-rt-r16 > linux-image-4.1.11-bone-rt-r16 - Linux kernel, version 4.1.11-bone-rt-r16 > linux-image-4.1.12-bone-rt-r16 - Linux kernel, version 4.1.12-bone-rt-r16 > linux-image-4.1.13-bone-rt-r16 - Linux kernel, version 4.1.13-bone-rt-r16 > linux-image-4.1.13-bone-rt-r17 - Linux kernel, version 4.1.13-bone-rt-r17 > linux-image-4.1.14-bone-rt-r17 - Linux kernel, version 4.1.14-bone-rt-r17 > linux-image-4.1.15-bone-rt-r17 - Linux kernel, version 4.1.15-bone-rt-r17 > linux-image-4.1.3-bone-rt-r15 - Linux kernel, version 4.1.3-bone-rt-r15 > linux-image-4.1.5-bone-rt-r15 - Linux kernel, version 4.1.5-bone-rt-r15 > linux-image-4.1.7-bone-rt-r16 - Linux kernel, version 4.1.7-bone-rt-r16 > linux-image-4.1.8-bone-rt-r16 - Linux kernel, version 4.1.8-bone-rt-r16 > linux-image-4.1.9-bone-rt-r16 - Linux kernel, version 4.1.9-bone-rt-r16 > > Then pick the last one which would be: linux-image-4.1.9-bone-rt-r16 Here > is the problem. There are a couple kernel config options that must be > enabled / disabled in order for prussdrv to work properly. Passed that it > is entirely possible that 4.4* may break prussdrv *somehow*, and > unintentionally. Because no one who uses prussdrv has tested this kernel > yet. > > Later, once you confirm that linux-image-4.1.9-bone-rt-r16 works. You can > always compare configs between the two to double check what you've missed. > > On Thu, Feb 25, 2016 at 7:40 PM, lajos kamocsay <[email protected]> > wrote: > >> I used the info from a post you made in this thread: >> >> >> https://groups.google.com/forum/m/#!category-topic/beagleboard/software/tdt1TTix7aE >> >> It's your 3rd post from the top, sorry, couldn't figure out how to link >> to it. >> >> I started from the Jessie BBB image that had the 4.1.15-ti-rt-r43 kernel. >> Now I have the 4.4.2-bone-rt-r5 kernel that I compiled and installed >> myself, am I maybe missing some udev rules? >> >> >> On Thu, Feb 25, 2016 at 4:57 PM, William Hermans <[email protected]> >> wrote: >> >>> *As I understand prus are supported with the *bone* kernels. Any ideas >>>> why they don't work? Maybe in conflict with something?* >>>> >>> >>> First, which device tree file are you using for the PRU's, and have you >>> loaded it ? >>> >>> On Thu, Feb 25, 2016 at 2:46 PM, lajos <[email protected]> wrote: >>> >>>> Hello- >>>> >>>> I have a BBB rev c with the Debian Jessie image on an SD card. I >>>> compiled the 4.4.2 bone rt kernel with RFKILL disabled, otherwise default >>>> settings built with github.com/RobertCNelson/bb-kernel. (Thanks for >>>> the great kernel builder!!!) >>>> >>>> uname -a >>>> Linux beagle 4.4.2-bone-rt-r5 #1 PREEMPT RT Thu Feb 25 11:36:52 EST >>>> 2016 armv7l GNU/Linux >>>> >>>> When I boot up the system I have several (8) systemd-udevd processes >>>> using up all the cpu, but they are killed after a while with this message >>>> in syslog: >>>> >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [636] >>>> /devices/platform/ocp/4a300000.pruss/uio/uio0 timeout; kill it >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2259 >>>> '/devices/platform/ocp/4a300000.pruss/uio/uio0' killed >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [684] >>>> /devices/platform/ocp/4a300000.pruss/uio/uio1 timeout; kill it >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2260 >>>> '/devices/platform/ocp/4a300000.pruss/uio/uio1' killed >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [685] >>>> /devices/platform/ocp/4a300000.pruss/uio/uio2 timeout; kill it >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2261 >>>> '/devices/platform/ocp/4a300000.pruss/uio/uio2' killed >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [686] >>>> /devices/platform/ocp/4a300000.pruss/uio/uio3 timeout; kill it >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2262 >>>> '/devices/platform/ocp/4a300000.pruss/uio/uio3' killed >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [832] >>>> /devices/platform/ocp/4a300000.pruss/uio/uio4 timeout; kill it >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2263 >>>> '/devices/platform/ocp/4a300000.pruss/uio/uio4' killed >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [834] >>>> /devices/platform/ocp/4a300000.pruss/uio/uio5 timeout; kill it >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2264 >>>> '/devices/platform/ocp/4a300000.pruss/uio/uio5' killed >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [850] >>>> /devices/platform/ocp/4a300000.pruss/uio/uio6 timeout; kill it >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2265 >>>> '/devices/platform/ocp/4a300000.pruss/uio/uio6' killed >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [856] >>>> /devices/platform/ocp/4a300000.pruss/uio/uio7 timeout; kill it >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2266 >>>> '/devices/platform/ocp/4a300000.pruss/uio/uio7' killed >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [636] terminated by >>>> signal 9 (Killed) >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [684] terminated by >>>> signal 9 (Killed) >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [685] terminated by >>>> signal 9 (Killed) >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [686] terminated by >>>> signal 9 (Killed) >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [832] terminated by >>>> signal 9 (Killed) >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [834] terminated by >>>> signal 9 (Killed) >>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [850] terminated by >>>> signal 9 (Killed) >>>> >>>> As I understand prus are supported with the *bone* kernels. Any ideas >>>> why they don't work? Maybe in conflict with something? >>>> >>>> I have HDMI Audio/Video and eMMC turned off in uEnv.txt: >>>> >>>> uname_r=4.4.2-bone-rt-r5 >>>> dtb=am335x-boneblack-overlay.dtb >>>> cmdline=coherent_pool=1M quiet cape_universal=enable >>>> >>>> And this is my lsmod: >>>> >>>> Module Size Used by >>>> c_can_platform 6560 0 >>>> c_can 9531 1 c_can_platform >>>> uio_pruss 4928 0 >>>> can_dev 11689 1 c_can >>>> spidev 7481 0 >>>> tieqep 8758 0 >>>> pwm_tiecap 3652 0 >>>> pwm_tiehrpwm 4706 0 >>>> usb_f_acm 7193 1 >>>> u_serial 10716 3 usb_f_acm >>>> usb_f_rndis 22093 1 >>>> g_multi 5441 0 >>>> usb_f_mass_storage 41731 2 g_multi >>>> u_ether 11887 2 usb_f_rndis,g_multi >>>> libcomposite 43393 4 >>>> usb_f_acm,usb_f_rndis,g_multi,usb_f_mass_storage >>>> ccm 6710 3 >>>> arc4 2019 2 >>>> rtl8192cu 52442 0 >>>> rtl_usb 9579 1 rtl8192cu >>>> rtl8192c_common 37747 1 rtl8192cu >>>> rtlwifi 56114 3 rtl_usb,rtl8192c_common,rtl8192cu >>>> mac80211 490892 3 rtl_usb,rtlwifi,rtl8192cu >>>> cfg80211 419275 2 mac80211,rtlwifi >>>> joydev 8336 0 >>>> omap_aes 13637 0 >>>> omap_sham 21619 0 >>>> omap_rng 4359 0 >>>> rng_core 7099 1 omap_rng >>>> evdev 10516 1 >>>> spi_omap2_mcspi 11118 0 >>>> uio_pdrv_genirq 3661 0 >>>> uio 8760 2 uio_pruss,uio_pdrv_genirq >>>> leds_gpio 3420 0 >>>> >>>> >>>> Any help would be appreciated! >>>> >>>> Thanks- >>>> Lajos >>>> >>>> >>>> -- >>>> 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. >>>> >>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "BeagleBoard" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/beagleboard/3iJ-J-x0-Ko/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> 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 [email protected]. >> 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
