Hello, I'm trying to port the franco kernel, but, it (given that the hardware is the same) should at least boot to the splash (you can flash OG kernels on the N4). Anyways, the kernel messages keep erroring with "[ 18.169082] msmfb_overlay_set: ioctl failed, rc=-34"
What I can't figure out is what msmfb error is. If I understand correctly, it is the adreno framebuffer having a write error.
It's initializing and the kernel boots correctly, but, I can't figure out what the issue with the framebuffer is...(The screen just shows a bunch of lines)
Here's the full log: http://pastebin.com/Gfs5ks8B
alastair53 said:
Hello, I'm trying to port the franco kernel, but, it (given that the hardware is the same) should at least boot to the splash (you can flash OG kernels on the N4). Anyways, the kernel messages keep erroring with "[ 18.169082] msmfb_overlay_set: ioctl failed, rc=-34"
What I can't figure out is what msmfb error is. If I understand correctly, it is the adreno framebuffer having a write error.
It's initializing and the kernel boots correctly, but, I can't figure out what the issue with the framebuffer is...(The screen just shows a bunch of lines)
Here's the full log: http://pastebin.com/Gfs5ks8B
Click to expand...
Click to collapse
I am having the same issue (different kernel, CM11). Did you found a fix?
ssrij said:
I am having the same issue (different kernel, CM11). Did you found a fix?
Click to expand...
Click to collapse
alastair53 said:
Hello, I'm trying to port the franco kernel, but, it (given that the hardware is the same) should at least boot to the splash (you can flash OG kernels on the N4). Anyways, the kernel messages keep erroring with "[ 18.169082] msmfb_overlay_set: ioctl failed, rc=-34"
What I can't figure out is what msmfb error is. If I understand correctly, it is the adreno framebuffer having a write error.
It's initializing and the kernel boots correctly, but, I can't figure out what the issue with the framebuffer is...(The screen just shows a bunch of lines)
Here's the full log: http://pastebin.com/Gfs5ks8B
Click to expand...
Click to collapse
hope you find a solution. What features will it have? It would be nice to have a kernel like Neighborhood but updated and for cm11.
Related
Google just moved out the 2.6.32 kernel from the experimental git repo to the msm repo. This means that google thinks they are stable now.
There are currently two 32 branches:
android-msm-2.6.32-nexusonec
http://android.git.kernel.org/?p=kernel/msm.git;a=shortlog;h=refs/heads/android-msm-2.6.32-nexusonec
android-msm-2.6.32
http://android.git.kernel.org/?p=kernel/msm.git;a=shortlog;h=refs/heads/android-msm-2.6.32
I've compiled both and I'm finding the nexusonec branch more stable than the 32 branch. The 32 branch causes issues with the gallery and camera app not recognizing the sd card. Everything seems to work fine in the nexusonec branch (sdcard, wifi, BT, camera, etc). Speed is definitely faster than 29.
For those who are interesting in flashing the 32 zimage, they can d/l it here:
http://drop.io/xdp6104#
Right now the kernel is just a stock config, meaning no tethering or anything else. Only change I've made from stock is to use the deadline I/O scheduler. I'm sure cyanogen will add those other goodies when he releases a new version.
Very nice: cant wait for a Enomther rom with this new Kernel
nice....
ive compiled a nice cyanogen kernel 2.6.32 already
just need to get the wifi module compiled correctly and we are gtg!
Does this mean that they've fixed some of the power saving regressions people were seeing with 2.6.32 before?
Installed on my Nexus with enomther 1.61: works nicely
Tot mem 395448K, Free 265916K
Does this still have the charging issue that blocks the battery to charge when it goes under 90%...???
eug89 said:
Does this still have the charging issue that blocks the battery to charge when it goes under 90%...???
Click to expand...
Click to collapse
86% now and charging..
eug89 said:
Does this still have the charging issue that blocks the battery to charge when it goes under 90%...???
Click to expand...
Click to collapse
It wasn't an issue per-se it was a 'feature'
The problem was caused by downgrading to older kernels after using 2.6.32. Certain hardware states that were set by the new kernel telling the battery not to charge weren't being un-set by the new kernel, and the older kernel didn't even know about them. They patched the newer kernel pretty quickly after getting feedback so that it removes the hardware state when shutting down, I believe. So, yes, it's 'fixed'
FettsVett said:
It wasn't an issue per-se it was a 'feature'
The problem was caused by downgrading to older kernels after using 2.6.32. Certain hardware states that were set by the new kernel telling the battery not to charge weren't being un-set by the new kernel, and the older kernel didn't even know about them. They patched the newer kernel pretty quickly after getting feedback so that it removes the hardware state when shutting down, I believe. So, yes, it's 'fixed'
Click to expand...
Click to collapse
Thanks, i called it issue because i didn't know how to call it but i knew that it was meant to be a sort of new feature of the 2..6.32 kernel and I wanted to write above 90% and not under 90%... did a bit of a mess
woahhh its way faster
thanks dwang
will do some thorough testing and post back soon.
edit: Hmmm having some trouble with fastboot... unable to push wifi via adb?
anyone else encountering this?
Are you trying to push the ko module on fastboot mode?
This kernel is FAST and SNAPPY! HIGHLY RECOMMENDED!
boqonx said:
Are you trying to push the ko module on fastboot mode?
This kernel is FAST and SNAPPY! HIGHLY RECOMMENDED!
Click to expand...
Click to collapse
yeah. iirc thats where you do it right?
Let the OS run, then push through adb. Can't do it when it's on recovery either because the /system/lib is not mounted. Wifi should work even without a restart.
yep just did that
i think i was just confused on where to use adb
it still works so all good. this kernel is zippy.
Damn right This thing flies now! Scrolling through messages is MUCH smoother. Seen a lot of tearing when scrolling on CM's kernel.
I released my undervolted version of CM's in the other thread. He changed the scheduler from anticipatory to deadline as well.
Will try! Had any reports on instabilities yet?
Dwang: great job on the deadline scheduler suggestion. It really does make the whole experience smoother.
Can someone write the exact adb command to push it?
Code:
adb remount
adb push ./bcm4329.ko /system/lib/modules
himmatwala said:
Can someone write the exact adb command to push it?
Click to expand...
Click to collapse
Just compiled AOSP master. It boots OK - however it looks like the screen driver and the radio are not working. I get excessive screen flicker and radio doesn't work at all.
Any ideas? Do I need to pull the proprietary drivers from the phone itself like we used to have to if using cyanogen's passion vendor overlay?
riddelln said:
Just compiled AOSP master. It boots OK - however it looks like the screen driver and the radio are not working. I get excessive screen flicker and radio doesn't work at all.
Any ideas? Do I need to pull the proprietary drivers from the phone itself like we used to have to if using cyanogen's passion vendor overlay?
Click to expand...
Click to collapse
I would suggest checking out Cyanogen's IRC. There are a number of people in there who could help you with this.
You need to run the extract-files script or the unzip-files scripts in devices/htc/passion before you can build. the product should be "full_passion"
After that step there are some things still not working such as camera and playing videos. Logcat says that the permissions in /dev are not correct and they cannot access the /dev/vdec and audio as well. I havnt got past that part yet using either 2.6.32 or 2.6.34 kernels.
Hey everyone was hoping someone can tell me what files inside the kernel make wifi function specifically in an ICS Kernel ?
Thanks.
crisvillani said:
Hey everyone was hoping someone can tell me what files inside the kernel make wifi function specifically in an ICS Kernel ?
Thanks.
Click to expand...
Click to collapse
For EVO 3D devices, the WiFi module is located at /system/lib/modules/bcm4329.ko and should always be the same location across all Android versions on the EVO 3D.
The kernel and modules are compiled separately from the Android OS. As such, the kernel and modules must always matched and should therefore always be installed together.
If that wasnt enough detail, please ask more specificially what aspect you're interested in. Hope that helps!
hey man thanks for the help, so basically what im trying to do is I flashed a Sense ICS kernel overtop AOSP ICS rom, it booted up fine and actually fixed a couple issues but the problem is wifi doesnt start, in logcat it says "failed to start driver" ,
I tried swapping the bcm4329.ko from the AOSP Kernel into the rom but it didn't work There must be something more, hope thats a bit clearer
Thanks
This is what it says in logcat :
Code:
E/WifiStateMachine< 252>: Failed to load driver!
E/WifiStateMachine< 252>: DriverFailedState
Dmesg
When trying to turn wifi on dmesg spits this out :
Code:
<3>[ 455.505561] bcm4329: version magic '2.6.35.14-cayniarb_miui.us_stock_ics-010612+ SMP preempt mod_unload ARMv7 ' should be 2.6.35.14-MDJ-SENSE-ICS-V1-g910203-dirty SMP mod_unload ARMv7 '
Im no expert, but if it was as simple as copy and pasting a wifi module from another kernel into a new ICS kernel I think everyone would have perfectly working wifi in the ICS kernels by now
joeykrim said:
For EVO 3D devices, the WiFi module is located at /system/lib/modules/bcm4329.ko and should always be the same location across all Android versions on the EVO 3D.
The kernel and modules are compiled separately from the Android OS. As such, the kernel and modules must always matched and should therefore always be installed together.
If that wasnt enough detail, please ask more specificially what aspect you're interested in. Hope that helps!
Click to expand...
Click to collapse
Was Wondering the same, Thanxx...
you issue is you are trying to load an miui kernel to an ASOP ROM. the drivers are not the same, and your system is looking for a particular driver and finding one that is not compatible, hence your dmsg error details...
its a little difficult to explain... but basically you are not using the right kernel
crisvillani said:
hey man thanks for the help, so basically what im trying to do is I flashed a Sense ICS kernel overtop AOSP ICS rom, it booted up fine and actually fixed a couple issues but the problem is wifi doesnt start, in logcat it says "failed to start driver" ,
I tried swapping the bcm4329.ko from the AOSP Kernel into the rom but it didn't work There must be something more, hope thats a bit clearer
Thanks
This is what it says in logcat :
Code:
E/WifiStateMachine< 252>: Failed to load driver!
E/WifiStateMachine< 252>: DriverFailedState
Click to expand...
Click to collapse
To start off, I'll give you an A+ for researching the issue on your device .. but a poor grade for researching the issue on this forum.
I've answered this question quite a few times on this EVO 3D Q&A board. I think I've got the details down pretty well. I'm going to quote from a previous post. Feel free to ask if you have any questions or something isn't clear!
http://forum.xda-developers.com/showpost.php?p=18793336&postcount=2
The WiFi error is caused by a mismatch between the WiFi module and the currently loaded kernel. The WiFi module is stored in /system/lib/modules/bcm4329.ko . The kernel is stored in the boot partition.
When booted into the custom recovery through the traditional methods, reboot recovery, bootloader -> recovery, etc., HTC unlock method does not unlock *kernel* write access but does unlock *system* write access.
The result is the kernel module for WiFi is loaded but the kernel itself is not loaded. This creates a mismatch between a WiFi module loaded from the ROM and the matching kernel not being loaded as HTC does not allow it to be loaded from the traditional recovery boot method.
The main issue around kernel write access is due to the HTC unlock method only allowing kernel write access in two modes:
1) Booted in normal Android mode. My application, Flash Image GUI, will flash any kernel .zip file with the HTC unlock method because it runs in normal android mode. HTC unlocks write access to the boot partition, where the kernel is stored, in normal Android mode. Flash Image GUI also properly loads the respective WiFi modules essentially eliminating this WiFi mismatch error.
2) Fastboot booted into the custom recovery using the following command: fastboot boot c:\android\cwm-recovery.img. HTC unlock method allows kernel write access while using fastboot boot of a custom recovery.
Hope that helps!
Edit: If you're curious and want to do some reading on previous WiFi error issues with the EVO 3D on this Q&A board where I replied, here are some similar posts:
http://forum.xda-developers.com/showthread.php?p=17681402
http://forum.xda-developers.com/showthread.php?p=16990247
http://forum.xda-developers.com/showthread.php?p=18624865
http://forum.xda-developers.com/showthread.php?t=1265467
http://forum.xda-developers.com/showthread.php?p=18807723
Click to expand...
Click to collapse
crisvillani said:
When trying to turn wifi on dmesg spits this out :
Code:
<3>[ 455.505561] bcm4329: version magic '2.6.35.14-cayniarb_miui.us_stock_ics-010612+ SMP preempt mod_unload ARMv7 ' should be 2.6.35.14-MDJ-SENSE-ICS-V1-g910203-dirty SMP mod_unload ARMv7 '
Click to expand...
Click to collapse
To further the point, this error in dmesg shows the exact mismatch between the WiFi module which can't load because it doesn't match the compile version of the kernel. Appears the kernel is using 2.6.35-14-MDJ-Sense-ICS-V1 kernel but the wifi module is from cayniarb_miui.us_stock_ics .. or the message is flip flopped, but the concept is the same.
WiFi module version does not match kernel version. They must match as they are compiled together at the same time.
Hope that helps!
^what joe said. lol
Sent from EVO 3D using XDA premium
So I'm getting right to the point. Upon every try of kernel installation I eather get kernel panic on boot, or it pops up at the finish of "optimazing android" screen. Tried every wipe, every installation sequence - nothing. I'm currently on Paranoid Android RC2 by adamz667, still no success installing kernel (but the rom works perfectly by itself). I've searched every message on that thread, but no one is having a problem like mine. So.. I ask your help
Model Number - P760
Android Version - 4.3.1
Baseband version - LGP760AT-00-V20h-EUR-XXX-JUL-12-2013
Kernel Version - 3.0.31-ASAP+
[email protected] #2
ParanoidAndroid version - 3.99-RC2
Without any logs we can't tell you what's wrong.
Here is the screen:
You have similar problem as some users of my experiencedkernel. I'm trying to fix it.
I pressume this is some hardware problem? Why is it that just some of us have this problem?
And yeah, I had the same window when I had MIUI installed and tried to install your experiencedkernel.
evalduuk said:
I pressume this is some hardware problem? Why is it that just some of us have this problem?
And yeah, I had the same window when I had MIUI installed and tried to install your experiencedkernel.
Click to expand...
Click to collapse
I've this problem with some kernel, I think should be a low or high voltage of some frequencies at boot.
Hello friends. So I am officially stumped. I have an issue with my kernel bootlooping. The interesting thing is, eventually it boots. After about 5-10 minutes of bootloop, it just boots. Weird right?
See, I merged a lot of code with my kernel and I'm not sure what is causing the bootloop. Here is my source: https://github.com/Snepsts/kernel_e980
It started on the add intelli-plug commit (which also includes intelli-thermal) it is probably important to mention disabling intelli-plug and thermal (and only one of each) all have the same outcome. I have also tried wiping the board back to its original state. I'm assuming its one of the core changes or nr_running changes. But I cannot find any way to get a log of the issue as it is not in a stable state during bootloop to give me logs from adb. I also cannot compile intelli-plug without the changes I made. And I really want to have it. I have looked for code I may be missing but cannot find any. I have made many different test kernels and taken the ramdisk and config from the latest official cm build for my device. Does anybody have any ideas? If you need anymore info please let me know. Thanks for any help in advance.
Sent from my LG-E980 running Carbon KitKat & E980 Kernel+