benedict, just don't confuse people! I work with 3.2 kernel from RCN and the Debian rootfs from him either. Everything works out of the box.
2013/12/9 <benedict290...@gmail.com> > Hi, > > You may want to have a read here > RoberCNelson<http://eewiki.net/display/linuxonarm/BeagleBone+Black> , > also here linux-dev <http://buildroot.uclibc.org/> for a git repository > covering many kernel branches (probably mentioned in the first link) > I am not sure if you can just take a Debian root files system and replace > the Kernel with the 3.2 one and any modules you have compiled. Most of the > Debian images are build for the 3.8 kernel or later it seems. > > I am actually using a BuildRoot <http://buildroot.uclibc.org/> based > environment, as I only needed a very basic environment, in which to run my > code (Qt using frame buffer). > > > > On Monday, 9 December 2013 11:29:12 UTC, Ali wrote: >> >> Hello, >> >> I am trying to go through the same process and bolt the 3.2 kernel into a >> Debian or Ubuntu root file system. >> >> I got some problems so far regarding the partition type. >> Can you please show me the steps you used to get this work? >> >> Thanks in advance :) >> >> On Wednesday, October 30, 2013 8:09:57 PM UTC+2, >> bko...@scanimetrics.comwrote: >>> >>> Hello all, >>> >>> Over the last few days I've been trying to get the 3.2 Linux Kernel >>> (AM335x-PSP_04.06.00.11) that comes with TI's 06.00.00.00 SDK to work on >>> the Beagle Bone Black with a Debian root file system. I compiled the kernel >>> from their source code myself along with a few extra modules that I need. >>> The end goal is to port a data logging application to the Beagle Bone >>> Black. The reason to use TI's kernel is that it is the only kernel that I >>> am aware of that supports power management functionality on the Beagle Bone >>> Black. The reason to use Debian is because the data logging application >>> currently runs on a Debian system; pre-built packages and experience with >>> Debian ought to make the port easier. >>> >>> I have managed to successfully bolt the 3.2 kernel into a Debian root >>> file system that runs off the emmc. Everything seems to work fine except >>> that the board reboots itself at random intervals (typically at least once >>> every 4 hours). At the time of the reboots I am not running any application >>> and am just letting Linux idle. >>> >>> The reboots are not accompanied by any suspicious messages in syslog or >>> dmesg (I also have an FTDI cable hooked up to capture messages from the >>> console and still see nothing). >>> >>> I am powering the board via the barrel connector and have tried multiple >>> power supplies but see no improvement. To further rule out power supply >>> issues, I have also tried the 3.8 kernel with the exact same root file >>> system with the same boot loader and have found that the reboots simply >>> disappear. >>> >>> At this point I am very stuck and am open to any ideas and will be very >>> thankful for any insights. >>> >>> I fear that in order to get up and running with a Kernel that supports >>> power management I may have to use TI's Arago distribution and compile all >>> needed packages from source which, although I've never done something like >>> that before, seems like it would take a whole lot of time and effort. >>> >>> Thanks! >>> >>> >>> -- > 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 beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- LinkedIn - http://www.linkedin.com/in/maximpodbereznyy Company - http://www.linkedin.com/company/mentorel Facebook - https://www.facebook.com/mentorel.company -- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
