Kernel .config for K-R42

[Gfunk]

I am trying to build a custom kernel for the K-R42 for use with some dvb modules. Currently I am using the rk3188_hotdog_defconfig with the kernel source found here http://github.com/thesawolf/android_kernel_rockchip_rk3188 and the modules that I successfully built insert fine with an init.d insmod script but when trying to use the modules I am receiving "usb in operation" errors. I would be grateful if one of you kernel devs could provide me with a defconfig/.config for the K-R42 so I can compile a zkernel.img/kernel.img and flash it myself with all the modules built specifically for the kernel being flashed.

I have successfully built kernel modules for my nexus 10 using cyanogenmod sources for dvb use with zero issues but building them individually does not seem to work for the k-r42/rk3188 kernel source. The usb devices initializes but does not work for some reason....

[leolas]

the user wasser is the one working on it. I think he compiled some kernels for r-k42 with all working. I tried it, but without ther device is a pain to try it.

[Gfunk]

the user wasser is the one working on it. I think he compiled some kernels for r-k42 with all working. I tried it, but without ther device is a pain to try it.

Thanks for the reply leolas. I sent wasser a PM a few days ago, still waiting for a response...

[leolas]

Thanks for the reply leolas. I sent wasser a PM a few days ago, still waiting for a response...

I ask him about share his .config and sources so we can adapt phjanderson kernel sources for this device too, but no response too, I supose he is busy the last days

[Gfunk]

Okayyyy so I flashed 1.2.2 (lewy hfw with wasser kernel) and low and behold wasser kept a copy of the config.gz in the /proc directory so I copied cp config.gz to /mnt/sdcard then extracted the .gz for the the kernel .config

Here it is for anyone else interested in building custom kernels:

[leolas]

Okayyyy so I flashed 1.2.2 (lewy hfw with wasser kernel) and low and behold wasser kept a copy of the config.gz in the /proc directory so I copied cp config.gz to /mnt/sdcard then extracted the .gz for the the kernel .config

Here it is for anyone else interested in building custom kernels:

Good, the waser let us a copy of the config. Thanks to him. Now we dont know the sources used to compile, but it is a first step. Thanks.

[lewy20041]

yap.
he is very nice person

[Gfunk]

Well I built my own kernel on my ubuntu machine and flashed the img and eveything seems to work just fine but I am still getting an initialization "usb in" error for my dvb module. This leads me to believe there could be either a module conflict or usb 2.0 port issue. All my custom modules insert fine with my custom kernel but when I connect my dvb-usb device I start to see "usb in operation failed" so the device will not work correctly. I am leaning more in the direction that I may need a powered usb hub perhaps. I use the same device with my nexus 10 with zero issues so THIS makes me think there is a module conflict. I guess I have some work cut out for myself tracking down the issue.

Wasser if you stumble upon this thread please post your github source you use for k-r42 kernel. Much appreciation for all your hard work

[wasser]

Good, the waser let us a copy of the config. Thanks to him. Now we dont know the sources used to compile, but it is a first step. Thanks.

i'm working on merging, don't worry

[wasser]

Well I built my own kernel on my ubuntu machine and flashed the img and eveything seems to work just fine but I am still getting an initialization "usb in" error for my dvb module. This leads me to believe there could be either a module conflict or usb 2.0 port issue. All my custom modules insert fine with my custom kernel but when I connect my dvb-usb device I start to see "usb in operation failed" so the device will not work correctly. I am leaning more in the direction that I may need a powered usb hub perhaps. I use the same device with my nexus 10 with zero issues so THIS makes me think there is a module conflict. I guess I have some work cut out for myself tracking down the issue.

Wasser if you stumble upon this thread please post your github source you use for k-r42 kernel. Much appreciation for all your hard work

i use the thesawolf's git repo

[walter]

i use the thesawolf's git repo

I'm using wasser's config from the earlier post for my K-R42 and built the kernel from thesawolf's git repo. I added a few other drivers that I needed and everything appears to be working, with one (major) problem - the unit now randomly reboots after running for a few minutes. I think I saw wasser mention that he posted another kernel that fixes this issue, but I can't seem to find the post right now.

Does anyone know what option might be in the kernel config / source tree that is causing the reboot issue? I did not experience any reboot issues with other firmware or the stock firmware.

I also found two 1080p monitors that I can not get 1080p to work on. I believe thesawolf's git repo has the 1080p fbmon.c edid fix in place, but it appears that the edid info is still not read correctly on all displays (ELO 42", Planar 23"). If anyone has any info on that I would appreciate it. It may be more of a kernel issue.

[Gfunk]

Are the reboots happening when you have a USB device active (with custom kernel module loaded) or when nothing, no USB device, is connected?

[walter]

Are the reboots happening when you have a USB device active (with custom kernel module loaded) or when nothing, no USB device, is connected?

The custom module(s) I'm using are mostly touchscreen drivers backported from kernel 3.3.x to enable Android to work with older single-touch screens like my eGalax touch panel and the ELO 2700 controller that came in the new ELO 4201L display (3.0.36 HID driver doesn't work, but the usbtouchscreen module reports the correct events so Android will use them as an input device). When it's up and running, all of the touch drivers appear to work great. A 42" Android touchscreen is interesting to play with

I'm running it now with NO usb devices, but have previously confirmed that it will reboot with only a USB mouse attached. It typically reboots after about 4 or 5 minutes and doesn't appear to be getting hot.

Is there any chance the stock ROM on the K-R42 is tied to the kernel in some way (watchdog?) and causing this issue? I wanted to tackle changing one part at a time, so at this point I'm running a completely stock rom with my kernel built on wasser's config and thesawolf's branch. Maybe that has something to do with the problem I'm seeing.

[walter]

The custom module(s) I'm using are mostly touchscreen drivers backported from kernel 3.3.x to enable Android to work with older single-touch screens like my eGalax touch panel and the ELO 2700 controller that came in the new ELO 4201L display (3.0.36 HID driver doesn't work, but the usbtouchscreen module reports the correct events so Android will use them as an input device). When it's up and running, all of the touch drivers appear to work great. A 42" Android touchscreen is interesting to play with

I'm running it now with NO usb devices, but have previously confirmed that it will reboot with only a USB mouse attached. It typically reboots after about 4 or 5 minutes and doesn't appear to be getting hot.

Is there any chance the stock ROM on the K-R42 is tied to the kernel in some way (watchdog?) and causing this issue? I wanted to tackle changing one part at a time, so at this point I'm running a completely stock rom with my kernel built on wasser's config and thesawolf's branch. Maybe that has something to do with the problem I'm seeing.

Yes, it still reboots with no usb devices attached.

[walter]

Yes, it still reboots with no usb devices attached.

Edit - Dumped the stock ROM - Flashed K-R42 HFW Rom, flashed my kernel. No more reboots! I guess it was something in the stock rom, intentional or not, I'm not sure.

Thanks for the config & kernel source guys! Fun times.