My experiences has in the past been to stick with the Wheezy image, and just upgrade the kernel to 4.1.x. Perhaps 4.4.x, but I'm still on the fence with that one. Then . . .
remote_proc == *TI* kernel. uio_pruss == *bone* kernel. The rest is hit and / or miss trial by error. Now, with all the above said. I am currently working with one of the later Jessie images, and having backed out of systemd back into sysv for an init daemon. My reason for Jessie is that I needed a newer gcc ( 4.7 + I think ) to compile the newer versions of Nodejs. I'm currently using. . . william@beaglebone:~/dev$ node -v v4.2.6 william@beaglebone:~/dev$ npm -v 3.9.0 william@beaglebone:~/dev$ gcc --version gcc (Debian 4.9.2-10) 4.9.2 Copyright (C) 2014 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. But anyway, I'm not 100% sure I'll use a Jessie image, but I'm trying to making it work. Otherwise I'd have to fall all the way back to v0.10.x for Nodejs, at which point I'd fall back to Wheezy as well. I still Have a lot to test though, which I will not be able to completely test until I get a good portion of the software written for using nearly all the pins on the P8 / P9 headers . . . which will take a while as I have a lot I need to research javascript / Nodejs wise. Plus we're usually pretty busy here during the spring / summer. So "round-to-its" are fewer, and further in between. On Thu, May 19, 2016 at 11:46 AM, Super Twang <[email protected]> wrote: > > > On May 19, 2016, at 12:39 PM, William Hermans <[email protected]> wrote: > > No one can make this determination for you. As there is no "one size > fits all" image. > > @William > I understand. I’m not asking for that. I’m already doing a fair bit of > add and subtract, even starting from a console image, to come up with the > best image for my own application. I’m just looking for the gut-check of > folks who understand the various images and kernels better than I, to know > which ones might be the best starting point. (ie those that have issues > that might affect me, PRU/uio_pruss and others that I don’t know about). > > The process of trying all of the available console images, customizing > them and subjecting all of them to long-term stability tests, is a > painstaking, and long process that I am in the middle of. I have already > gleaned what I can from forums, etc. I know I’m not the only one going > through this process, so I’m just hoping that someone share a few tips to > help me reduce the search space. With no description of what each image > contains, reference of what issues popped up for users of them, and no > historical record of why new versions were rolled (presumably because some > problems were fixed, and the newer one is better), I don’t have a lot to > work with. Maybe this stuff exists somewhere, and I just don’t know > where? If so, point me to it and I’ll keep reading. > > Here’s what I’m working with: > > “Use an official image” - adds a bunch of stuff that is inappropriate for > an embedded device (graphical targets, node, cloud9, etc), I don’t know > enough about what I can safe remove to start from here. > > “Use the barefs” - really quite appealing, and I may get there someday, > but for now, I don’t have a non-virtualized-os linux dev machine. > > The best I’ve found so far: > > “Use a console image” > > Ok, so I’m using a console image: > > “Use the latest image” - exposes me to the potentially lurking issues of > the cutting edge. I am uncomfortable with that solution because the level > of risk is too high for me. > > My own reasoning is “Choose a long-term-support variant" (so it will have > the chance to settle into greater stability). > > BUT, I’ve been having a hard time solving stability problems with: > Jessie 8.4 console image of 4/7/2016 > Kernel: 4.4.9 -bone-rt-r10 kernel > > and know there was a period of uio_pruss issues somewhere in 3.8 - 4.1. > So, my thought was to back up to Wheezy. But, which console image should I > start with??? Was the latest one the best? > > I’m thankful for any input, even if it is to tell me I’m going about this > the wrong way. That said, one person telling me I’m doing it wrong is > probably not going to help, unless they can point me to a better way. If > not, then I’ll keep learning as best as I can, and asking for help when I’m > stuck. > > Best, > ST > > > -- > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/70D48203-53CF-4CF1-A901-700DA631B6A1%40gmail.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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORoLyBaU5O%3DL%3D_YdDi7fM6dbuRGcg6CadG-TRUoifeT3ow%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
