Running Beagle Black with latest Debian release. I am trying to compile a couple of programs against kernel source and I am having a problem.
I used the bb-get-rcn-kernel-source.sh script to download the kernel headers, source and apply patches. The kernel is linux-3.8.13-bone43 which matches uname -r = 3.8.13-bone43.
This all goes well. I am compiling dahdi 2.9.1.1 and asterisk. Patches are applied successfully to dahdi before compile and the asterisk is custom. For this reason neither package can be download as a binary package they must be compiled from source. The compilations and installs go fine except in the case of dahdi it put the modules in /lib/modules/3.8.13 and not 3.8.13-bone43. where the rest of the kernel modules are. Dahdi does not work unless I move the modules to /lib/modules/3.8.13-bone43.and then do a depmod -a 3.8.13-bone43.
OK so far so good. Asterisk compiles and installs fine. When I run it crashes usually within about a half hour. Up until it crashes the application seems to work. All tests I have done show no messages and memory checks show nothing strange before the crash. The crash is immediate. It just stops working and heartbeat LED stops. I have been pulling my hair out as to what this is. This package does work. I have it working on the RPi and a Debian PC.
My questions is this, does using the bb-get-rcn-kernel-source.sh script accurately prepare the source and headers to match the current system? If so why does the dahdi compile insist on putting the modules in 3.8.13 leaving the -bone43 off? Could this be a potential problem indicating I am not matching the running kernel in my compiles? I am trying to look at all possibilities.
Perhaps I should compile the kernel from the source I have downloaded, install it and then recompile against that.
Is there a written procedure for installing a compiled Debian kernel on the BBB?
Running Beagle Black with latest Debian release. I am trying to compile a
couple of programs against kernel source and I am having a problem.
I used the bb-get-rcn-kernel-source.sh script to download the kernel
headers, source and apply patches. The kernel is linux-3.8.13-bone43 which
matches uname -r = 3.8.13-bone43.
This all goes well. I am compiling dahdi 2.9.1.1 and asterisk. Patches are
applied successfully to dahdi before compile and the asterisk is custom. For
this reason neither package can be download as a binary package they must be
compiled from source. The compilations and installs go fine except in the
case of dahdi it put the modules in /lib/modules/3.8.13 and not
3.8.13-bone43. where the rest of the kernel modules are. Dahdi does not work
unless I move the modules to /lib/modules/3.8.13-bone43.and then do a depmod
-a 3.8.13-bone43.
OK so far so good. Asterisk compiles and installs fine. When I run it
crashes usually within about a half hour. Up until it crashes the
application seems to work. All tests I have done show no messages and memory
checks show nothing strange before the crash. The crash is immediate. It
just stops working and heartbeat LED stops. I have been pulling my hair out
as to what this is. This package does work. I have it working on the RPi and
a Debian PC.
Lets see, serial console dead, no ethernet, led's stop... That sounds
similar to the gtk2 lockup bug.
I'm waiting for a reply from the ti hardware guys..
My questions is this, does using the bb-get-rcn-kernel-source.sh script
accurately prepare the source and headers to match the current system? If so
why does the dahdi compile insist on putting the modules in 3.8.13 leaving
the -bone43 off? Could this be a potential problem indicating I am not
matching the running kernel in my compiles? I am trying to look at all
possibilities.
add: LOCALVERSION=-bone43 to the make call, it's not set in the
Makefile so it won't get picked up automatically.
Perhaps I should compile the kernel from the source I have downloaded,
install it and then recompile against that.
Is there a written procedure for installing a compiled Debian kernel on the
BBB?
Well I am using the BBB headless so I suspect the gtk2 lockup bug would not be an issue???
So I guess you are saying I can be assured the kernels are the same (source and running kernel) and it would be a waste of time to try compiling the source kernel, installing it, and try again?