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
Related
Got my tablet 2 weeks ago.
I went from stock ROM->Vegan 5.1.1 (2 weeks ago)->Vegan Ginger edition 7.0.0 (yesterday)
so far so good.
However, when i tried to update to the latest kernel (see below)
"ViewSonic Gtab/Malata Zpad (Gingerbread):
boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-042411.zip
Download: boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-042411.zip"
I get "wifi error" upon startup. Wifi is not recognized, nor can i add my wifi manually.
Tried going back and forth between base ROM/kernel from this forum "VEGAn-TAB GingerEdition STABLE RC1" and the latest kernel (with the usual clear data/cache/davlik cache post-install). Base kernel has wifi no probs, but any later kernel and i get wifi errors
Tried to cycle airport mode, but nothing happens - just goes into disabling wifi networks and stays grayed out
Also tried to clear cache "before" flashing kernel, as suggested by member TEK112 in the same thread. Any help will be appreciated. thanks!
xda-novice said:
Got my tablet 2 weeks ago.
I went from stock ROM->Vegan 5.1.1 (2 weeks ago)->Vegan Ginger edition 7.0.0 (yesterday)
so far so good.
However, when i tried to update to the latest kernel (see below)
"ViewSonic Gtab/Malata Zpad (Gingerbread):
boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-042411.zip
Download: boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-042411.zip"
I get "wifi error" upon startup. Wifi is not recognized, nor can i add my wifi manually.
Tried going back and forth between base ROM/kernel from this forum "VEGAn-TAB GingerEdition STABLE RC1" and the latest kernel (with the usual clear data/cache/davlik cache post-install). Base kernel has wifi no probs, but any later kernel and i get wifi errors
Tried to cycle airport mode, but nothing happens - just goes into disabling wifi networks and stays grayed out
Also tried to clear cache "before" flashing kernel, as suggested by member TEK112 in the same thread. Any help will be appreciated. thanks!
Click to expand...
Click to collapse
Usually wifi not working means you flashed the wrong kernel, but it sure looks like you got the right (gb) one. You sure you're on gingerbread?
schettj said:
Usually wifi not working means you flashed the wrong kernel, but it sure looks like you got the right (gb) one. You sure you're on gingerbread?
Click to expand...
Click to collapse
hmm...wonder what's wrong then ?
I'm positive about Ginger edition though - Followed instructions from this forum - "http://forum.xda-developers.com/showthread.php?t=1031250"
Downloaded and installed "VEGAn-GE-7.0.0-RC1-Harmony-signed.zip" from http://vegantab.gojimi.com/downloads/
Home screen confirms Vegan-Tab GingerEdition - do not have the tablet with me at the moment, but can post "About Tablet" info later.
Sounds more like you forgot to take the lib-2632.39_gb.tar.gz from pershoot's webpage or failed to take the correct version of the lib. That lib tarball contains the bcm4329.ko (wifi driver kernel module). You have to untar the lib and adb push the bcm4329.ko driver to /system/lib/modules/, reboot after pushing the module over.
Try that and see if you have any better luck bringing up wifi with a newer pershoot kernel.
terrypchan said:
Sounds more like you forgot to take the lib-2632.39_gb.tar.gz from pershoot's webpage or failed to take the correct version of the lib. That lib tarball contains the bcm4329.ko (wifi driver kernel module). You have to untar the lib and adb push the bcm4329.ko driver to /system/lib/modules/, reboot after pushing the module over.
Try that and see if you have any better luck bringing up wifi with a newer pershoot kernel.
Click to expand...
Click to collapse
Thanks terrypchan...never played around with adb before, and couldn't get it to work last night, but will definitely give it a shot and post my results.
However, in previous version, when I had Vegan 5.1.1, and upgraded the kernel, i didn't have to go through the adb push of bcm4329.ko install. Even with the upgrade kernel for gingerbread7.0 (the noted issue here), there is base bcm4329.ko driver is already sitting under /system/lib/hw/wlan folder, so the adb push of this module under lib/modules will override the base ?
terrypchan said:
Sounds more like you forgot to take the lib-2632.39_gb.tar.gz from pershoot's webpage or failed to take the correct version of the lib. That lib tarball contains the bcm4329.ko (wifi driver kernel module). You have to untar the lib and adb push the bcm4329.ko driver to /system/lib/modules/, reboot after pushing the module over.
Try that and see if you have any better luck bringing up wifi with a newer pershoot kernel.
Click to expand...
Click to collapse
I've never needed to do that.
I'm wondering if he's stuck in airplane mode now that I've re-read his first post.
This is from the old version, but suggests that getting a widget that can toggle flight mode may fix it:
http://forum.xda-developers.com/showthread.php?t=951822&page=59
FYI - no need to use flight mode on a tablet, just turn off all the radios.
terrypchan said:
Sounds more like you forgot to take the lib-2632.39_gb.tar.gz from pershoot's webpage or failed to take the correct version of the lib. That lib tarball contains the bcm4329.ko (wifi driver kernel module). You have to untar the lib and adb push the bcm4329.ko driver to /system/lib/modules/, reboot after pushing the module over.
Try that and see if you have any better luck bringing up wifi with a newer pershoot kernel.
Click to expand...
Click to collapse
Can you tell me how to do that??
I am having exct same issue on Samsung Wave..
It seems I cant start Wifi on my mobilephone Evo 3D GSM
I followed 2 Tutorial, one to boot an boot.img and other to flash with some file bcm4329.
Non of it suceed.
After installing completly new rom, it happens again. LeeDroid
sniperkiki said:
It seems I cant start Wifi on my mobilephone Evo 3D GSM
I followed 2 Tutorial, one to boot an boot.img and other to flash with some file bcm4329.
Non of it suceed.
After installing completly new rom, it happens again. LeeDroid
Click to expand...
Click to collapse
The tutorials sound to be on the right track.
Essentially, the bcm4329.ko file is the wifi module (drivers) for Wifi. This module file, bcm4320.ko, stored in /system/lib/modules/ must match the currently flashed kernel. If the wifi module and kernel do not match, you will receive this Wifi error.
Whenever a kernel developer compiles a new kernel, they must also compile the Wifi module, bcm4329.ko. The bcm4329.ko module file must be loaded into /system/lib/modules on the phone along with the custom kernel being flashed to the boot partition. If either of these files mismatch, Wifi will throw the error.
I walked through a lot of the logic in a separate thread troubleshooting this issue: WiFi - Error
Hope that helps!
My phone will reboot when I press the power button moments after I turn the screen off.
I have tried SetCPU multiple settings, and governors, but nothing seems to work.
I have also tried flashing multiple kernels, even stock!
I have reinstalled this ROM several times and the same result every time, I have tried Xperia ROM as well as the Titan rom, same result. Do I have a faulty phone?
Current ROM: Nocturnal Adrenaline 1.0.2
Current Kernel: [email protected] #9
Thanks.
Try cheking your init.d folder to see if you have any startup scripts or scripts in general interfering with the kernel. I recall reading that chads kernels are already pretweaked and in some cases Rom developers may add scripts to tweak memory,app loading, etc. Well in some cases these may interfere with chads kernels, not saying that this is your issue just saying it might be that is if you haven't already ruled it out. Also if your s-off you can always ruu back to stock to see if the issue still remains..By the way what software ver are you on ?? And have you ran the latest updates??
#Root_Hack-Mod*Always\
laie1472 said:
Try cheking your init.d folder to see if you have any startup scripts or scripts in general interfering with the kernel. I recall reading that chads kernels are already pretweaked and in some cases Rom developers may add scripts to tweak memory,app loading, etc. Well in some cases these may interfere with chads kernels, not saying that this is your issue just saying it might be that is if you haven't already ruled it out. Also if your s-off you can always ruu back to stock to see if the issue still remains..By the way what software ver are you on ?? And have you ran the latest updates??
#Root_Hack-Mod*Always\
Click to expand...
Click to collapse
Thanks for your response.
I don't think the init.d folder would be an issue because:
1. Chad's kernel came preloaded in the ROM
2. I haven't put any start up scripts
Software version: 2.08.651.3 Nocturnal'd
Baseband Bersion: 0.97.10.0808
Android: 2.3.4
Latest updates? I didn't run sofware updates since forever
zanekills said:
Thanks for your response.
I don't think the init.d folder would be an issue because:
1. Chad's kernel came preloaded in the ROM
2. I haven't put any start up scripts
Software version: 2.08.651.3 Nocturnal'd
Baseband Bersion: 0.97.10.0808
Android: 2.3.4
Latest updates? I didn't run sofware updates since forever
Click to expand...
Click to collapse
Have you checked the folder ?? Also you should try system timer for overclocking with chads kernels Imo and from what I've read it works a lot better. Also as fat as the updates you can hit the dev section to find freezas aio zip with the latest updates and read what they are for to see if you want to update or not.
Here's the thread
http://forum.xda-developers.com/showthread.php?t=1443592
Towards the end of it frezza and haux both posted aio's so you have a choice.
I flashed freezas without any issues at all. I strongly urge to read a lot of that thread and heed all of the warnings as well.
#Root_Hack-Mod*Always\
Hello,
I own a 64GB P7510. It is rooted and currently it has a version of CM9 ICS installed. I have tried several versions of ICS and Stock Honeycomb as well as Tasks GalaxyTask 14.
I use Splashtop HD mostly on the tab and have noticed that it randomly freezes the tablet and crashes the device. The only way to recover it to hold the power button down and wait for the device to restart.
In Stock ROM and GalaxyTask 14 it seems to work fine. In ICS or when installing Pershoots kernel the crashes occur. The crashes are totally random and can happen when splashtop has been left along for a minute, ten minutes or not at all.
I assume this has something to do with the kernel as I experience the same problem with GalaxyTask 14 but only when I install the pershoots kernel. It also happens in all ICS versions I have tried.
Current config: Android 4.0.4, Kernel [email protected] #1 SMP PREEMPT Sat June 23 22:18:30 EDT 2012, Cyanogenmod version: 9-20120703-NIGHTLY-p4wifi, Build date: Mon Jul 2 22:00:33 PDT 2012, Build number: cm_p4wifi-userdebug 4.0.4 IMM76L eng.jenkins.20120702.220017 test-keys
Splashtop version: (Streamer) 2.0.0.4 (also tested in older streamer but same results), (Client) Splashtop 1.9.9.5 SW r21787
This make using Splashtop unusable as it randomly crashes. When I spoke to Splashtop support they said they had never heard of a problem like it.
I have looked all over the web and done extensive searches of XDA to try to find out what the problem could be, but to no avail. I also hope I have put this question in the correct forum.
The problem takes place in (and I have tested):
GalaxyTask 14 (only with pershoots kernel)
AOKP ICS
CM9 ICS
It works fine in:
GalaxyTask 14 without pershoots kernel
Stock HC ROM
Even if there is no solution, is there a way I could troubleshoot the problem.
Any help would be appreciated.
Many thanks,
Graham.
Just bumping. Has no one at all experienced this problem at all?
I reloaded Honeycomb this week and there were no problems at all, then reloaded ICS and it still crashes. I can't be on my own surely?
Graham.
on ICS (you can use 0710 experimental i posted this morning on droidbasement),
as soon as it crashes, head straight to recovery and pull /proc/last_kmsg and send it to me.
i'll see what i can do.
I will flash this now and let you know. My tab crashes quite a bit on the 07.04 CM9 nightly, and am thinking about going back to HC
Sent from my GT-P7510 using xda premium
it should not be crashing. you may have a bad app or an unstable OC doing harm. at any rate, load up 7/10 experimental, do not OC or install any other app but splashtop. if it crashes, pull the log.
pershoot said:
it should not be crashing. you may have a bad app or an unstable OC doing harm. at any rate, load up 7/10 experimental, do not OC or install any other app but splashtop. if it crashes, pull the log.
Click to expand...
Click to collapse
in fact, this is what you should do:
pull your data off /data/media, odin back to 3.2 (the whole tab will be wiped), odin CWM (found in the 7/10 experimental folder), boot CWM, wipe, flash 7/10 experimental, latest gapps, and boot in. dont restore any apps and dont OC. install only the splashtop app. observe and pull log if it crashes as i outlined above.
the added bonus from the above will ensure you don't have any more crashes from extraneous unknown factors.
When I said my Tab was crashing, I meant in general and not due to splashtop. I don't even use splashtop. I thought maybe your experimental build and giving you that one file could help troubleshoot crashing in general. Sorry about that.
Sent from my GT-P7510 using xda premium
Thanks Pershoots. I am not sure what is going on. I will have a look and send it to you. It may be next week before I get a chance.
Many thanks,
Graham.
pershoot said:
on ICS (you can use 0710 experimental i posted this morning on droidbasement),
as soon as it crashes, head straight to recovery and pull /proc/last_kmsg and send it to me.
i'll see what i can do.
Click to expand...
Click to collapse
hi pershots.
i rebooted into recovery after the last crash but i dont see where to pull that from. i am using cwm recovery. also when you talk of your 0710 experimental do you mean a newer version of the kernel?
many thanks,
graham.
medialinx said:
hi pershots.
i rebooted into recovery after the last crash but i dont see where to pull that from. i am using cwm recovery. also when you talk of your 0710 experimental do you mean a newer version of the kernel?
many thanks,
graham.
Click to expand...
Click to collapse
you need to be on 07/11 experimental rom (from droidbasement) or 07/12 nightly from get.cm.
please odin back to 3.2 (the whole tab will be wiped; make sure you back up any data you may have in /data/media), odin CWM (you can find this at droidbasement), boot it, wipe, flash either of those roms and flash latest gapps. enter in, do not restore any apps. install only splashtop and run it.
now observe.
if you get a crash, head straight to recovery and do this:
adb pull /proc/last_kmsg .
then send that to me.
I am experiencing the same problem. On stock HC 3.2 splashtop worked fine but my HDMI cable out didn't work so I flashed RS_Supremacy_AOKP v0.2 pershoots kernel 2.6.36.4-cynogenmod+, my HDMI cable worked great after that the rom is awesome I love it but only just recently noticed that splashtop now is almost useless it always freezes within 5-10mins of use and I then need to hold power button down to restart tablet. I'll be watching this thread with great interest as I don't really want to change my rom I really like this one.
Sent from my GT-P7100 using XDA Premium HD app
Ichigo66 said:
I am experiencing the same problem. On stock HC 3.2 splashtop worked fine but my HDMI cable out didn't work so I flashed RS_Supremacy_AOKP v0.2 pershoots kernel 2.6.36.4-cynogenmod+, my HDMI cable worked great after that the rom is awesome I love it but only just recently noticed that splashtop now is almost useless it always freezes within 5-10mins of use and I then need to hold power button down to restart tablet. I'll be watching this thread with great interest as I don't really want to change my rom I really like this one.
Sent from my GT-P7100 using XDA Premium HD app
Click to expand...
Click to collapse
it will not get fixed until i see logs.
Ok I'm still a bit of a noob when it comes to these things but i'll give it a try and see if I can get a log for u fingers crossed X
Sent from my GT-I9300T using xda app-developers app
pershoot said:
you need to be on 07/11 experimental rom (from droidbasement) or 07/12 nightly from get.cm.
please odin back to 3.2 (the whole tab will be wiped; make sure you back up any data you may have in /data/media), odin CWM (you can find this at droidbasement), boot it, wipe, flash either of those roms and flash latest gapps. enter in, do not restore any apps. install only splashtop and run it.
now observe.
if you get a crash, head straight to recovery and do this:
adb pull /proc/last_kmsg .
then send that to me.
Click to expand...
Click to collapse
Here you go Pershoots. I hope this is what you are looking for. I am not really up on using ADB. I could not get it to do a pull from CWM recovery or Odin recovery so I rebooted and ran USB Debug then finally got the computer to see the device. Anyhow, here is what I pulled. If I did this wrong if you could please explain or point me to somewhere to see the steps needed to ADB from recovery as I could not find anything on Google about ADB recovery galaxy tab 10.1.
Thank you for looking at this for me.
Here you go...
[ 12.526464] [DBG] upload cause : UPLOAD_CAUSE_INIT
[ 12.526479] (kernel_sec_set_upload_cause) : upload_cause set 0
[ 12.526464] [DBG] upload cause : UPLOAD_CAUSE_INIT
[ 12.526479] (kernel_sec_set_upload_cause) : upload_cause set 0
[ 13.162166] i2c i2c-11: sendbytes: NAK bailout.
[ 13.276914] mxt_config_settings
[ 13.852817] Failed to add route HPOUTL->Headset Jack
[ 13.886165] Tegra protected aperture disabled because nvmap is using system memory
[ 14.706771] init: cannot open '/initlogo.rle'
[ 14.712062] init: Unable to open persistent property directory /data/property errno: 2
[ 14.721883] android_usb: already disabled
[ 84.203676] SysRq : Emergency Remount R/O
[ 84.208259] Restarting Linux version 2.6.36.4-cyanogenmod+ ([email protected]) (gcc version 4.5.1 (Sourcery G++ Lite 2010.09-51) ) #1 SMP PREEMPT Sat Mar 17 18:04:36 EDT 2012
[ 84.208268]
[ 84.266040] VFS: Close: file count is 0
[ 84.884148] Restarting system.
No errors detected
You're running a really old kernel/build.
I'll be posting new test builds soon. U can retest against them.
pershoot said:
You're running a really old kernel/build.
I'll be posting new test builds soon. U can retest against them.
Click to expand...
Click to collapse
Thanks pershoots.
From looking at that output would you have any idea what is going wrong?
Graham.
medialinx said:
Thanks pershoots.
From looking at that output would you have any idea what is going wrong?
Graham.
Click to expand...
Click to collapse
not really. altho, there was a blurb about protected memory which ive since enabled in the video driver (been enabled for a while).
crash
The crash is happening in aDownloader and Splashtop... now in JB. It happens very randomly...
I have re-flashed it, re-odined it, re-stocked it many times(tried all sorts of different roms), but I get this issue always when I have pershoot kernel, and unfortunately there isn't much alternative choice on ICS / JB. It looks like this kernel issue is here since the beginning and basically I am unable to download torrents (or stream HD via splashtop) without restarting it a couple of times.
It's really strange that more people are not experiencing this issue...
Try the experimental I posted for cm9 or 10 (07/28).
Post logs if it crashes.
Hi pershoots.
I have been running jellybean with your kernel 26/7 for the last week and had only a couple of crashes. Maybe it is an ics issue as i have reflashed ics this week too and it crashed under it.
Graham.
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.