Ken Ko and other developers. I have the same problem in such environment. - android-4.0.3_r1 - omap-tuna-3.0-mr0 - Galaxy Nexus (maguro)
When I used pre-built kernel image that is located in '/devices/samsung/tuna/kernel', it works well. In order to use my own kernel image instead of pre-built kernel image, it doesn't work and the same error message occurs like that. <3>[ 292.940032] drivers/misc/inv_mpu/mldl_cfg.c| inv_mpu_get_slave_config|1792 returning 4 <6>[ 294.745819] PVR_K:(Error): BridgedDispatchKM: Initialisation failed. Driver unusable. [4811, drivers/gpu/pvr/bridged_pvr_bridge.c] <3>[ 294.762664] init: untracked pid 1738 exited <3>[ 294.762817] init: untracked pid 1742 exited I don't know what is the main reason of failure. Please let me know the reason and the possible solution for this problem. Thank you in advances. Derick SJ Woo. 2012년 1월 23일 월요일 오전 9시 47분 53초 UTC+9, Ken Ko 님의 말: > > Preetam, > > That is what I meant in the first post, when the driver wouldn't > load--presumably because the kernel version strings didn't match up. > My mistake was with using the wrong branch: android-omap-tuna-3.0-mr0 > rather than android-omap-tuna-3.0. > > Now a `fastboot boot out/target/product/toro/boot.img` gives me my > computer's hostname in the kernel version string in the About Phone > page. > > Sidenote: does anyone know what the -mr0 signifies in the branch naming > scheme? > > Thanks, > Ken Ko > > On Fri, Jan 20, 2012 at 12:41 AM, preetam m.n <preeta...@gmail.com> wrote: > > Looks like your kernel image, and your file system image has a mismatch. > > confirm that what ever kernel and filesystem are compatible. > > > > Regards, > > Preetam > > > > > > On Fri, Jan 20, 2012 at 11:54 AM, Kenneth Ko <ko.harm...@gmail.com> > wrote: > >> > >> After looking around the Makefile a bit more, I tried the following > >> with no avail: > >> > >> make clobber > >> make -j3 TARGET_PREBUILT_KERNEL=/opt/omap/arch/arm/boot/zImage > >> fastboot boot out/target/product/toro/boot.img > >> > >> Is there a crucial step that I'm missing? > >> > >> Thanks, > >> Ken > >> > >> On Mon, Jan 16, 2012 at 10:29 AM, Ken Ko <ko.harm...@gmail.com> wrote: > >> > Hi, > >> > > >> > I'm having issues with loading my kernel. The error below leads me to > >> > believe that I'm not building the proprietary imgtec/samsung drivers > >> > against my modified kernel. > >> > > >> > <3>[ 292.940032] drivers/misc/inv_mpu/mldl_cfg.c| > >> > inv_mpu_get_slave_config|1792 returning 4 > >> > <6>[ 294.745819] PVR_K:(Error): BridgedDispatchKM: Initialisation > >> > failed. Driver unusable. [4811, drivers/gpu/pvr/bridged_pvr_bridge.c] > >> > <3>[ 294.762664] init: untracked pid 1738 exited > >> > <3>[ 294.762817] init: untracked pid 1742 exited > >> > > >> > For reference, I'm building with the android-omap-tuna-3.0-mr0 branch. > >> > I believe that it's built properly because I have a arch/arm/boot/ > >> > zImage. > >> > Next, I copied over the zImage to device/samsung/tuna/kernel and built > >> > an aosp toro rom. > >> > When that finished, I did a `fastboot boot boot.img`. > >> > Now I'm stuck at the initial Google screen but my device is up and > >> > running, as far as I can tell, when I go in through `adb shell`. > >> > > >> > At this point, I had 4.0.2 from Verizon's OTA update but then I > >> > decided to install a 4.0.3 AOSP-based image from one of the many > >> > distributions online, because I thought the kernel I just built may be > >> > for 4.0.3 only. Tried my own boot.img once more, but there is no > >> > change. > >> > > >> > To sanity check myself, I flashed one of the many 4.0.3 kernels > >> > distributed with the same `fastboot boot boot.img` and everything > >> > appeared to be working and functional. > >> > > >> > I've tried using `split_bootimg.pl boot.img` on the working boot.img > I > >> > downloaded, `mkbootimg --kernel boot.img-kernel --ramdisk boot.img- > >> > ramdisk.gz -o boot.img` followed by a `fastboot boot boot.img` but > >> > that gives me the same result as before--stuck at the Google screen > >> > while the actual system is up and running. > >> > > >> > At this point, I'm not sure what to do so I'm reaching out for advice. > >> > > >> > Thanks, > >> > Ken > >> > > >> > -- > >> > unsubscribe: android-kernel+unsubscr...@googlegroups.com > >> > website: http://groups.google.com/group/android-kernel > >> > >> -- > >> unsubscribe: android-kernel+unsubscr...@googlegroups.com > >> website: http://groups.google.com/group/android-kernel > > > > > > > > > > -- > > "The great pleasure in life is doing what people say you cannot do" > > > > -- > > unsubscribe: android-kernel+unsubscr...@googlegroups.com > > website: http://groups.google.com/group/android-kernel > > -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
