Here is a port of 2ndboot to milestone2. It successfully boots new kernel, radio(as expected) is not working... but who uses smartphone as a phone anyway?
If you wish to try it:
1) extract attachment onto your sdcard
2) copy /sdcard/2ndboot_gb/hbootuser to /system/bin
3) chmod +x /system/bin/hbootuser
4) turn off lcd panel(otherwise the new kernel will not initialize display correctly)
5) in one console invoke adb shell cat /proc/kmsg (so that the processor does not sleep to deep... otherwise it can take time before it starts to boot )
5) from another console invoke adb shell /sdcard/2ndboot_gb/2ndboot_gb.sh... and cross your fingers(as it sometimes crashes)
Here is a source code:
hxxp://bitbucket.org/czechop/mils2_2ndboot
NOTE1: it is compiled against froyo kernel, so probably wont work with gb. I've tested it with froyo kernel(MILS2_U6_2.4.24) and tezet's CM10 system(btw really nice rom... and very handy that the same system image can work with both froyo and gb kernels ).
NOTE2: it takes quite a lot of time to boot(if it boots at all), so be patient
NOTE3: if you connect serial(ttl 3.3V) <=> usb converter to micro usb port you can grap early console output from the new kernel(speed 115200)
I'm about to test this over CM10 and GB kernel, will it work anyways?
Another question, if I boot this kernel, and then reboot, will I be back in Moto's kernel with radio?
Nice work, btw :good:
OK, I tried this 3 times, with no success, everytime the screen remained turned on but completely black, for about 10-15 seconds, then rebooted to Moto logo.
After the second try, my status bar and navigation buttons were gone, had to wipe dalvik cache to solve it.
Hope it helps you :good:
Lean946 said:
OK, I tried this 3 times, with no success, everytime the screen remained turned on but completely black, for about 10-15 seconds, then rebooted to Moto logo.
After the second try, my status bar and navigation buttons were gone, had to wipe dalvik cache to solve it.
Hope it helps you :good:
Click to expand...
Click to collapse
Did you turn off the screen before invoking the script? Without this the new kernel spends a lot of time tryinig to reinitialize it, and eventually watchdog will reboot the phone.
Have you got to the place where blue and green leds turn on?
czechop said:
Here is a port of 2ndboot to milestone2. It successfully boots new kernel, radio(as expected) is not working... but who uses smartphone as a phone anyway?
If you wish to try it:
1) extract attachment onto your sdcard
2) copy /sdcard/2ndboot_gb/hbootuser to /system/bin
3) chmod +x /system/bin/hbootuser
4) turn off lcd panel(otherwise the new kernel will not initialize display correctly)
5) in one console invoke adb shell cat /proc/kmsg (so that the processor does not sleep to deep... otherwise it can take time before it starts to boot )
5) from another console invoke adb shell /sdcard/2ndboot_gb/2ndboot_gb.sh... and cross your fingers(as it sometimes crashes)
NOTE1: it is compiled against froyo kernel, so probably wont work with gb. I've tested it with froyo kernel(MILS2_U6_2.4.24) and tezet's CM10 system(btw really nice rom... and very handy that the same system image can work with both froyo and gb kernels ).
NOTE2: it takes quite a lot of time to boot(if it boots at all), so be patient
NOTE3: it's my first post here, so... hello to everyone
Click to expand...
Click to collapse
Welcome to XDA and thanks for sharing this! Could you also please share the sources?
It would be cool to have working kexec, Droid 3 guys managed to have it working with radio. Maybe you could look at this and try to port it to our M2?
tezet said:
Welcome to XDA and thanks for sharing this! Could you also please share the sources?
It would be cool to have working kexec, Droid 3 guys managed to have it working with radio. Maybe you could look at this and try to port it to our M2?
Click to expand...
Click to collapse
Just added link to source code(should have done that straightaway)
As far as I know D3 has a different radio, so the chances are not so high it will work with M2... but probably it's worth to try anyway
Hey, nice work you have done! Maybe you should take a look at this repository: http://git.zerfleddert.de/cgi-bin/gitweb.cgi/ms2-kexec
From the same guy who made the MS2Debounce app, he tried some hacking with kexec but he failed, maybe you can find a way out in the code?
dangpzanco said:
Hey, nice work you have done! Maybe you should take a look at this repository: hxxp://git.zerfleddert.de/cgi-bin/gitweb.cgi/ms2-kexec
From the same guy who made the MS2Debounce app, he tried some hacking with kexec but he failed, maybe you can find a way out in the code?
Click to expand...
Click to collapse
Thanks
I've seen this repository. I've send the author PM with info regarding enabling console output(he gave up his work as without debugging info he was not able to progress), so I hope that he will get back to it
In the meantime I've tried 2ndboot to start mbm(milestone1 devs have tried it without success, but I hoped that maybe our mbm is better then the one milestone1 has), but mbm stucks at resetting BP Will try to dig this out(for some time)... and if this does not work(which is almost sure), will try(if my phone survive constant reboots) to look at possibility of passing usb context from the old kernel to the new one, so that to skip enumeration in the new kernel.
czechop said:
Thanks
I've seen this repository. I've send the author PM with info regarding enabling console output(he gave up his work as without debugging info he was not able to progress), so I hope that he will get back to it
In the meantime I've tried 2ndboot to start mbm(milestone1 devs have tried it without success, but I hoped that maybe our mbm is better then the one milestone1 has), but mbm stucks at resetting BP Will try to dig this out(for some time)... and if this does not work(which is almost sure), will try(if my phone survive constant reboots) to look at possibility of passing usb context from the old kernel to the new one, so that to skip enumeration in the new kernel.
Click to expand...
Click to collapse
Great to see someone (else) working on that and making some progress (even small ones is better than none).
Hope you'll reach something working someday.
czechop said:
Here is a port of 2ndboot to milestone2. It successfully boots new kernel, radio(as expected) is not working... but who uses smartphone as a phone anyway?
...
Click to expand...
Click to collapse
i have successfully test this on CM10 with GB kernel. one issue is the adb lost link after the new kernel launched, and un-recognized USB device found.
GREAT jobs! thanks
would you please post a kernel with swap support? it's a good reason for a custom kernel.
mimitech said:
i have successfully test this on CM10 with GB kernel. one issue is the adb lost link after the new kernel launched, and un-recognized USB device found.
GREAT jobs! thanks
would you please post a kernel with swap support? it's a good reason for a custom kernel.
Click to expand...
Click to collapse
Good to know that it works for someone else
Regarding adb, you lost link because micro-usb port is switched to serve as an UART to get console output. If you wish micro-usb to preserve its functionality, replace 2ndboot.ko with the one from the attachement, and in the 2ndboot.sh script add "emu_uart=0" parameter at the end of insmod command. Another option is to use adb over wifi.
Regarding swap support... I attach kernel version compiled with CONFIG_SWAP flag... this should I guess enable swap support(haven't tested that). Please let me know if it works
test progress
I have tested this. both the ADB over USB and swap work OK, thank you very much.
another minor issue is, after reboot into the new kernel, the CPU load is 100% high, all occurred in kernel. the process "khubd" has very high CPU time, and the dmesg show repeated messages:
"
<3>[ 2388.578765] hub 1-0:1.0: Cannot enable port 3. Maybe the USB cable is bad?
<3>[ 2388.584167] hub 1-0:1.0: unable to enumerate USB device on port 3
<4>[ 2388.588867] czecho: hub_port_reset: skipping reset of port 3
<4>[ 2388.593536] czecho: hub_port_reset: skipping reset of port 3
<4>[ 2388.598144] czecho: hub_port_reset: skipping reset of port 3
<4>[ 2388.602752] czecho: hub_port_reset: skipping reset of port 3
<4>[ 2388.607391] czecho: hub_port_reset: skipping reset of port 3
"
i have tried switch the 2ndboot.ko to original one, the issue still exists.
this issue should be related with OMPA3 usb hub? please help fix this, after then i guess this custom kernel should be very useful. thanks.
---------- Post added at 03:38 AM ---------- Previous post was at 03:28 AM ----------
post some more information for debug:
vmstat =>
procs memory system cpu
r b free mapped anon slab in cs flt us ni sy id wa ir
1 0 8600 120912 246264 13260 211 431 0 1 0 93 0 0 7
1 0 8600 120916 246264 13260 166 143 0 1 0 96 0 0 3
1 0 8600 120916 246264 13260 222 463 0 2 0 87 0 0 9
2 1 11204 120916 243632 13260 195 104 0 0 0 97 0 0 3
============================================
ps =>
R 0 289 2 0 0 0:0 09:55 00:34:00 [khubd]
============================================
in official kernel, there is a hub with 3 port:
<6>[ 7.889923] usbcore: registered new interface driver hub
<6>[ 8.063293] hub 1-0:1.0: USB hub found
<6>[ 8.063415] hub 1-0:1.0: 3 ports detected
czechop said:
Good to know that it works for someone else
Regarding adb, you lost link because micro-usb port is switched to serve as an UART to get console output. If you wish micro-usb to preserve its functionality, replace 2ndboot.ko with the one from the attachement, and in the 2ndboot.sh script add "emu_uart=0" parameter at the end of insmod command. Another option is to use adb over wifi.
Regarding swap support... I attach kernel version compiled with CONFIG_SWAP flag... this should I guess enable swap support(haven't tested that). Please let me know if it works
Click to expand...
Click to collapse
mimitech said:
I have tested this. both the ADB over USB and swap work OK, thank you very much.
another minor issue is, after reboot into the new kernel, the CPU load is 100% high, all occurred in kernel. the process "khubd" has very high CPU time, and the dmesg show repeated messages:
"
<3>[ 2388.578765] hub 1-0:1.0: Cannot enable port 3. Maybe the USB cable is bad?
<3>[ 2388.584167] hub 1-0:1.0: unable to enumerate USB device on port 3
<4>[ 2388.588867] czecho: hub_port_reset: skipping reset of port 3
<4>[ 2388.593536] czecho: hub_port_reset: skipping reset of port 3
<4>[ 2388.598144] czecho: hub_port_reset: skipping reset of port 3
<4>[ 2388.602752] czecho: hub_port_reset: skipping reset of port 3
<4>[ 2388.607391] czecho: hub_port_reset: skipping reset of port 3
"
i have tried switch the 2ndboot.ko to original one, the issue still exists.
this issue should be related with OMPA3 usb hub? please help fix this, after then i guess this custom kernel should be very useful. thanks.
---------- Post added at 03:38 AM ---------- Previous post was at 03:28 AM ----------
post some more information for debug:
vmstat =>
procs memory system cpu
r b free mapped anon slab in cs flt us ni sy id wa ir
1 0 8600 120912 246264 13260 211 431 0 1 0 93 0 0 7
1 0 8600 120916 246264 13260 166 143 0 1 0 96 0 0 3
1 0 8600 120916 246264 13260 222 463 0 2 0 87 0 0 9
2 1 11204 120916 243632 13260 195 104 0 0 0 97 0 0 3
============================================
ps =>
R 0 289 2 0 0 0:0 09:55 00:34:00 [khubd]
============================================
in official kernel, there is a hub with 3 port:
<6>[ 7.889923] usbcore: registered new interface driver hub
<6>[ 8.063293] hub 1-0:1.0: USB hub found
<6>[ 8.063415] hub 1-0:1.0: 3 ports detected
Click to expand...
Click to collapse
The CPU load is probably due to my recent modifications to disable usb reset in new kernel(so that to preserver link with BP)... which of course does not work as expected
Anyway, I guess I could prepare a "clean" kernel with swap support, but maybe it would be better if you do it yourself(so that in the future you could enable other features in the kernel)?
You would need(probably there is many other ways to do it):
1. ubuntu. I personally use 10.04 x64. In my system it cowork with windows xp(actually ubuntu is installed on the windows partition, so it could be easly deleted if space is required)
2. prepare a cross compiler(I use one made with crosstool-ng, but it took me realy loooong time to make it). I guess that the easiest option would be to use cross compiler from android ndk(it should work just fine). So that download ndk
3. find the path to the crosscompiler in extracted ndk(it would be something like android-ndk-r8b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin; should contain gcc and other tools) and add it to PATH
4. download motorola kernel source for milestone 2 from hxxp://sourceforge.net/projects/milestone.motorola/files/. I use version MILS2_U6_4.1-22(kernel is in file kernel_omap3.tgz)
5. extract kernel
6. cd to kernel root
7.edit configuration file(arch/arm/configs/mapphone_defconfig)... enable SWAP etc...
8. being in kernel root dir, invoke: make CROSS_COMPILE='prefix of your crosscompiler, e.g. arm-linux-androideabi-' ARCH=arm mapphone_defconfig
9. being in kernel root dir, invoke: make CROSS_COMPILE='prefix of your crosscompiler, e.g. arm-linux-androideabi-' ARCH=arm bzImage
10. if everything goes fine, your kernel should reside in arch/arm/boot/zImage... copy it over kern in 2ndboot
Let me know how do you feel about building your own custom kernel
Thanks for very detailed instruction. it should not be a problem for me, i have some experience with Linux kernel compiling, i need some time for environment setup and getting familiar with android SDK and cross-compiling tools.
thanks again. I'll let you know if any progress.
czechop said:
Let me know how do you feel about building your own custom kernel
Click to expand...
Click to collapse
I think you could have more luck with radio when starting new kernel from bootmenu, just like 2nd-init.
You may bind it to bootmenu's 2nd-boot option, however I suggest to use all init scripts from 2nd-init as a base, 2nd-boot is not mantained at all.
tezet said:
I think you could have more luck with radio when starting new kernel from bootmenu, just like 2nd-init.
You may bind it to bootmenu's 2nd-boot option, however I suggest to use all init scripts from 2nd-init as a base, 2nd-boot is not mantained at all.
Click to expand...
Click to collapse
Thanks for this tip
BTW, do you know if there is some way to restart then into 2nd-boot via bootmenu automatically(so that I don't need to choose 2nd-boot from the bootmenu list... this would speed booting up a little bit), but preserving 2nd-init as the default bootmenu option?
i have successfully compiled a kernel following your instruction, it's easy i think. but the kernel can't boot, about 10 second after i issue the "2ndboot_gb.sh", the red moto logo appeared, and the phone rebooted.
i use the stock config file, with one modification: 'config_swap=y'.
the kernel i compiled is larger than you provide, size is 3,130,008 bytes. the compiler is arm-linux-androideabi-4.4.3.
do you have any idea about this? maybe you can provide me a clean kernel with swap enabled to test? thanks
czechop said:
Let me know how do you feel about building your own custom kernel
Click to expand...
Click to collapse
---------- Post added at 08:23 AM ---------- Previous post was at 08:18 AM ----------
i post the kernel message before the new kernel reboot, please help me verify the process is ok. thakns
==================================================
<4>[ 221.475616] czecho: hboot_init
<4>[ 221.475708] dev[power.0], driver[power]
<4>[ 221.475799] dev[ram_console.0], driver[ram_console]
<4>[ 221.475982] dev[omap-panel], driver[omap-panel]
<4>[ 221.476074] dev[omapdss], driver[omapdss]
<4>[ 221.476165] dev[sfh7743], driver[sfh7743]
<4>[ 221.476562] dev[bu52014hfv], driver[bu52014hfv]
<4>[ 221.476654] dev[vib-gpio], driver[vib-gpio]
<4>[ 221.476745] dev[musb_hdrc], driver[musb_hdrc]
<4>[ 221.476928] dev[ehci-omap.0], driver[ehci-omap]
<4>[ 221.477020] dev[mapphone_bpwake], driver[mapphone_bpwake]
<4>[ 221.477172] dev[omap_hdq.0], driver[omap_hdq]
<4>[ 221.477264] dev[wl127x-rfkill.0], driver[wl127x-rfkill]
<4>[ 221.477691] dev[wl127x-test.0], driver[UNKNOWN]
<4>[ 221.477783] dev[mmci-omap-hs.0], driver[mmci-omap-hs]
<4>[ 221.477874] dev[mmci-omap-hs.1], driver[mmci-omap-hs]
<4>[ 221.478057] dev[TIWLAN_SDIO.2], driver[TIWLAN_SDIO]
<4>[ 221.478149] dev[omapvout], driver[omapvout]
<4>[ 221.478302] dev[omaplfb], driver[UNKNOWN]
<4>[ 221.478424] dev[usb_mass_storage], driver[usb_mass_storage]
<4>[ 221.478698] dev[rndis], driver[rndis]
<4>[ 221.478881] dev[android_usb], driver[android_usb]
<4>[ 221.478942] dev[sim.1], driver[sim]
<4>[ 221.479125] dev[omap3isp], driver[omap3isp]
<4>[ 221.479217] dev[omap2_mcspi.1], driver[omap2_mcspi]
<4>[ 221.479309] dev[omap2_mcspi.2], driver[omap2_mcspi]
<4>[ 221.479461] dev[omap2_mcspi.3], driver[omap2_mcspi]
<4>[ 221.479553] dev[omap2_mcspi.4], driver[omap2_mcspi]
<4>[ 221.479736] dev[omap-uart.1], driver[omap-uart]
<4>[ 221.479827] dev[omap-uart.2], driver[omap-uart]
<4>[ 221.479919] dev[omap-uart.3], driver[UNKNOWN]
<4>[ 221.480102] dev[omap-mcbsp.1], driver[omap-mcbsp]
<4>[ 221.480194] dev[omap-mcbsp.2], driver[omap-mcbsp]
<4>[ 221.480346] dev[omap-mcbsp.3], driver[omap-mcbsp]
<4>[ 221.480438] dev[omap-mcbsp.4], driver[omap-mcbsp]
<4>[ 221.480560] dev[omap-mcbsp.5], driver[omap-mcbsp]
<4>[ 221.480712] dev[i2c_omap.1], driver[i2c_omap]
<4>[ 221.480804] dev[i2c_omap.2], driver[i2c_omap]
<4>[ 221.480987] dev[i2c_omap.3], driver[i2c_omap]
<4>[ 221.481079] dev[omap_wdt], driver[omap_wdt]
<4>[ 221.481170] dev[omapfb], driver[omapfb]
<4>[ 221.484344] dev[cpcap_uc], driver[cpcap_uc]
<4>[ 221.484466] dev[cpcap_adc], driver[cpcap_adc]
<4>[ 221.484558] dev[cpcap_key], driver[cpcap_key]
<4>[ 221.484710] dev[cpcap_battery], driver[cpcap_battery]
<4>[ 221.484802] dev[cpcap_rtc], driver[cpcap_rtc]
<4>[ 221.484954] dev[cpcap_usb], driver[cpcap_usb]
<4>[ 221.485046] dev[cpcap_usb_det], driver[cpcap_usb_det]
<4>[ 221.485229] dev[cpcap_audio], driver[cpcap_audio]
<4>[ 221.485321] dev[cpcap_3mm5], driver[cpcap_3mm5]
<4>[ 221.485382] dev[bd7885], driver[bd7885]
<4>[ 221.485565] dev[leds-cpcap-kpb], driver[leds-cpcap-kpb]
<4>[ 221.485656] dev[leds-cpcap-gpio], driver[leds-cpcap-gpio]
<4>[ 221.485809] dev[leds-cpcap-rgb], driver[leds-cpcap-rgb]
<4>[ 221.485900] dev[flash-torch], driver[flash-torch]
<4>[ 221.485992] dev[wakeup_timer.0], driver[wakeup_timer]
<4>[ 221.486145] dev[omap-iommu.0], driver[omap-iommu]
<4>[ 221.486236] dev[C6410], driver[C6410]
<4>[ 221.486419] dev[adp5588-backlight], driver[UNKNOWN]
<4>[ 221.486511] dev[keyreset.0], driver[keyreset]
<4>[ 221.486572] dev[gpio-event.0], driver[gpio-event]
<4>[ 221.486755] dev[device_wifi.1], driver[device_wifi]
<4>[ 221.486846] dev[gpio-device.0], driver[gpio-device]
<4>[ 221.486999] dev[clock_32k], driver[clock_32k]
<4>[ 221.487091] dev[alarm], driver[alarm]
<4>[ 221.487182] dev[hp3a], driver[hp3a]
<4>[ 221.487365] dev[hplens-i2c], driver[UNKNOWN]
<4>[ 221.487426] dev[cpcap_usb_charger], driver[cpcap_usb_charger]
<4>[ 221.487609] dev[cpcap_usb_connected], driver[cpcap_usb_connected]
<4>[ 221.487701] dev[ondemand], driver[ondemand]
<4>[ 221.487854] dev[pvrsrvkm], driver[pvrsrvkm]
<4>[ 221.487945] dev[cpcap_usbled], driver[cpcap_usbled]
<4>[ 221.488037] hboot_init
<6>[ 221.488220] hbootctrl: Successfully registered dev
<6>[ 221.548248] hbootctrl: `open' stub called
<4>[ 221.549468] hbootctrl: ioctl. cmd[0], arg[-1097176624]
<4>[ 221.549652] hbootctrl: HBOOT_ALLOCATE_BUFFER. tag[0], type[0], attrs[0], size[9556], rest[0]
<4>[ 221.549743] hbootctrl: HBOOT_ALLOCATE_BUFFER. ret[0]
<4>[ 221.549926] hbootctrl: ioctl. cmd[4], arg[0]
<4>[ 221.550018] hbootctrl: HBOOT_SELECT_BUFFER. handle[0], ret[0]
<4>[ 221.551422] hbootctrl: ioctl. cmd[0], arg[-1097176624]
<4>[ 221.551513] hbootctrl: HBOOT_ALLOCATE_BUFFER. tag[1], type[1], attrs[1], size[3130008], rest[0]
<4>[ 221.597412] hbootctrl: HBOOT_ALLOCATE_BUFFER. ret[1]
<4>[ 221.597534] hbootctrl: ioctl. cmd[4], arg[1]
<4>[ 221.597686] hbootctrl: HBOOT_SELECT_BUFFER. handle[1], ret[0]
<4>[ 221.899444] hbootctrl: ioctl. cmd[0], arg[-1097176624]
<4>[ 221.899627] hbootctrl: HBOOT_ALLOCATE_BUFFER. tag[2], type[1], attrs[1], size[150558], rest[0]
<4>[ 221.899810] hbootctrl: HBOOT_ALLOCATE_BUFFER. ret[2]
<4>[ 221.899993] hbootctrl: ioctl. cmd[4], arg[2]
<4>[ 221.900085] hbootctrl: HBOOT_SELECT_BUFFER. handle[2], ret[0]
<4>[ 221.911102] hbootctrl: ioctl. cmd[0], arg[-1097176624]
<4>[ 221.911193] hbootctrl: HBOOT_ALLOCATE_BUFFER. tag[3], type[0], attrs[1], size[6220], rest[0]
<4>[ 222.208953] hbootctrl: HBOOT_ALLOCATE_BUFFER. ret[3]
<4>[ 222.209075] hbootctrl: ioctl. cmd[4], arg[3]
<4>[ 222.209228] hbootctrl: HBOOT_SELECT_BUFFER. handle[3], ret[0]
<4>[ 222.210693] hbootctrl: ioctl. cmd[0], arg[-1097176624]
<4>[ 222.210876] hbootctrl: HBOOT_ALLOCATE_BUFFER. tag[4], type[0], attrs[1], size[294], rest[0]
<4>[ 222.210968] hbootctrl: HBOOT_ALLOCATE_BUFFER. ret[4]
<4>[ 222.211120] hbootctrl: ioctl. cmd[4], arg[4]
<4>[ 222.211212] hbootctrl: HBOOT_SELECT_BUFFER. handle[4], ret[0]
<4>[ 222.212097] hbootctrl: ioctl. cmd[3], arg[0]
<4>[ 222.212188] hbootctrl: HBOOT_BOOT1. handle[0]
<4>[ 222.212432] hboot_boot
mimitech said:
i have successfully compiled a kernel following your instruction, it's easy i think. but the kernel can't boot, about 10 second after i issue the "2ndboot_gb.sh", the red moto logo appeared, and the phone rebooted.
i use the stock config file, with one modification: 'config_swap=y'.
the kernel i compiled is larger than you provide, size is 3,130,008 bytes. the compiler is arm-linux-androideabi-4.4.3.
do you have any idea about this? maybe you can provide me a clean kernel with swap enabled to test? thanks
---------- Post added at 08:23 AM ---------- Previous post was at 08:18 AM ----------
i post the kernel message before the new kernel reboot, please help me verify the process is ok. thakns
==================================================
<4>[ 221.475616] czecho: hboot_init
<4>[ 221.475708] dev[power.0], driver[power]
<4>[ 221.475799] dev[ram_console.0], driver[ram_console]
<4>[ 221.475982] dev[omap-panel], driver[omap-panel]
<4>[ 221.476074] dev[omapdss], driver[omapdss]
<4>[ 221.476165] dev[sfh7743], driver[sfh7743]
<4>[ 221.476562] dev[bu52014hfv], driver[bu52014hfv]
<4>[ 221.476654] dev[vib-gpio], driver[vib-gpio]
<4>[ 221.476745] dev[musb_hdrc], driver[musb_hdrc]
<4>[ 221.476928] dev[ehci-omap.0], driver[ehci-omap]
<4>[ 221.477020] dev[mapphone_bpwake], driver[mapphone_bpwake]
<4>[ 221.477172] dev[omap_hdq.0], driver[omap_hdq]
<4>[ 221.477264] dev[wl127x-rfkill.0], driver[wl127x-rfkill]
<4>[ 221.477691] dev[wl127x-test.0], driver[UNKNOWN]
<4>[ 221.477783] dev[mmci-omap-hs.0], driver[mmci-omap-hs]
<4>[ 221.477874] dev[mmci-omap-hs.1], driver[mmci-omap-hs]
<4>[ 221.478057] dev[TIWLAN_SDIO.2], driver[TIWLAN_SDIO]
<4>[ 221.478149] dev[omapvout], driver[omapvout]
<4>[ 221.478302] dev[omaplfb], driver[UNKNOWN]
<4>[ 221.478424] dev[usb_mass_storage], driver[usb_mass_storage]
<4>[ 221.478698] dev[rndis], driver[rndis]
<4>[ 221.478881] dev[android_usb], driver[android_usb]
<4>[ 221.478942] dev[sim.1], driver[sim]
<4>[ 221.479125] dev[omap3isp], driver[omap3isp]
<4>[ 221.479217] dev[omap2_mcspi.1], driver[omap2_mcspi]
<4>[ 221.479309] dev[omap2_mcspi.2], driver[omap2_mcspi]
<4>[ 221.479461] dev[omap2_mcspi.3], driver[omap2_mcspi]
<4>[ 221.479553] dev[omap2_mcspi.4], driver[omap2_mcspi]
<4>[ 221.479736] dev[omap-uart.1], driver[omap-uart]
<4>[ 221.479827] dev[omap-uart.2], driver[omap-uart]
<4>[ 221.479919] dev[omap-uart.3], driver[UNKNOWN]
<4>[ 221.480102] dev[omap-mcbsp.1], driver[omap-mcbsp]
<4>[ 221.480194] dev[omap-mcbsp.2], driver[omap-mcbsp]
<4>[ 221.480346] dev[omap-mcbsp.3], driver[omap-mcbsp]
<4>[ 221.480438] dev[omap-mcbsp.4], driver[omap-mcbsp]
<4>[ 221.480560] dev[omap-mcbsp.5], driver[omap-mcbsp]
<4>[ 221.480712] dev[i2c_omap.1], driver[i2c_omap]
<4>[ 221.480804] dev[i2c_omap.2], driver[i2c_omap]
<4>[ 221.480987] dev[i2c_omap.3], driver[i2c_omap]
<4>[ 221.481079] dev[omap_wdt], driver[omap_wdt]
<4>[ 221.481170] dev[omapfb], driver[omapfb]
<4>[ 221.484344] dev[cpcap_uc], driver[cpcap_uc]
<4>[ 221.484466] dev[cpcap_adc], driver[cpcap_adc]
<4>[ 221.484558] dev[cpcap_key], driver[cpcap_key]
<4>[ 221.484710] dev[cpcap_battery], driver[cpcap_battery]
<4>[ 221.484802] dev[cpcap_rtc], driver[cpcap_rtc]
<4>[ 221.484954] dev[cpcap_usb], driver[cpcap_usb]
<4>[ 221.485046] dev[cpcap_usb_det], driver[cpcap_usb_det]
<4>[ 221.485229] dev[cpcap_audio], driver[cpcap_audio]
<4>[ 221.485321] dev[cpcap_3mm5], driver[cpcap_3mm5]
<4>[ 221.485382] dev[bd7885], driver[bd7885]
<4>[ 221.485565] dev[leds-cpcap-kpb], driver[leds-cpcap-kpb]
<4>[ 221.485656] dev[leds-cpcap-gpio], driver[leds-cpcap-gpio]
<4>[ 221.485809] dev[leds-cpcap-rgb], driver[leds-cpcap-rgb]
<4>[ 221.485900] dev[flash-torch], driver[flash-torch]
<4>[ 221.485992] dev[wakeup_timer.0], driver[wakeup_timer]
<4>[ 221.486145] dev[omap-iommu.0], driver[omap-iommu]
<4>[ 221.486236] dev[C6410], driver[C6410]
<4>[ 221.486419] dev[adp5588-backlight], driver[UNKNOWN]
<4>[ 221.486511] dev[keyreset.0], driver[keyreset]
<4>[ 221.486572] dev[gpio-event.0], driver[gpio-event]
<4>[ 221.486755] dev[device_wifi.1], driver[device_wifi]
<4>[ 221.486846] dev[gpio-device.0], driver[gpio-device]
<4>[ 221.486999] dev[clock_32k], driver[clock_32k]
<4>[ 221.487091] dev[alarm], driver[alarm]
<4>[ 221.487182] dev[hp3a], driver[hp3a]
<4>[ 221.487365] dev[hplens-i2c], driver[UNKNOWN]
<4>[ 221.487426] dev[cpcap_usb_charger], driver[cpcap_usb_charger]
<4>[ 221.487609] dev[cpcap_usb_connected], driver[cpcap_usb_connected]
<4>[ 221.487701] dev[ondemand], driver[ondemand]
<4>[ 221.487854] dev[pvrsrvkm], driver[pvrsrvkm]
<4>[ 221.487945] dev[cpcap_usbled], driver[cpcap_usbled]
<4>[ 221.488037] hboot_init
<6>[ 221.488220] hbootctrl: Successfully registered dev
<6>[ 221.548248] hbootctrl: `open' stub called
<4>[ 221.549468] hbootctrl: ioctl. cmd[0], arg[-1097176624]
<4>[ 221.549652] hbootctrl: HBOOT_ALLOCATE_BUFFER. tag[0], type[0], attrs[0], size[9556], rest[0]
<4>[ 221.549743] hbootctrl: HBOOT_ALLOCATE_BUFFER. ret[0]
<4>[ 221.549926] hbootctrl: ioctl. cmd[4], arg[0]
<4>[ 221.550018] hbootctrl: HBOOT_SELECT_BUFFER. handle[0], ret[0]
<4>[ 221.551422] hbootctrl: ioctl. cmd[0], arg[-1097176624]
<4>[ 221.551513] hbootctrl: HBOOT_ALLOCATE_BUFFER. tag[1], type[1], attrs[1], size[3130008], rest[0]
<4>[ 221.597412] hbootctrl: HBOOT_ALLOCATE_BUFFER. ret[1]
<4>[ 221.597534] hbootctrl: ioctl. cmd[4], arg[1]
<4>[ 221.597686] hbootctrl: HBOOT_SELECT_BUFFER. handle[1], ret[0]
<4>[ 221.899444] hbootctrl: ioctl. cmd[0], arg[-1097176624]
<4>[ 221.899627] hbootctrl: HBOOT_ALLOCATE_BUFFER. tag[2], type[1], attrs[1], size[150558], rest[0]
<4>[ 221.899810] hbootctrl: HBOOT_ALLOCATE_BUFFER. ret[2]
<4>[ 221.899993] hbootctrl: ioctl. cmd[4], arg[2]
<4>[ 221.900085] hbootctrl: HBOOT_SELECT_BUFFER. handle[2], ret[0]
<4>[ 221.911102] hbootctrl: ioctl. cmd[0], arg[-1097176624]
<4>[ 221.911193] hbootctrl: HBOOT_ALLOCATE_BUFFER. tag[3], type[0], attrs[1], size[6220], rest[0]
<4>[ 222.208953] hbootctrl: HBOOT_ALLOCATE_BUFFER. ret[3]
<4>[ 222.209075] hbootctrl: ioctl. cmd[4], arg[3]
<4>[ 222.209228] hbootctrl: HBOOT_SELECT_BUFFER. handle[3], ret[0]
<4>[ 222.210693] hbootctrl: ioctl. cmd[0], arg[-1097176624]
<4>[ 222.210876] hbootctrl: HBOOT_ALLOCATE_BUFFER. tag[4], type[0], attrs[1], size[294], rest[0]
<4>[ 222.210968] hbootctrl: HBOOT_ALLOCATE_BUFFER. ret[4]
<4>[ 222.211120] hbootctrl: ioctl. cmd[4], arg[4]
<4>[ 222.211212] hbootctrl: HBOOT_SELECT_BUFFER. handle[4], ret[0]
<4>[ 222.212097] hbootctrl: ioctl. cmd[3], arg[0]
<4>[ 222.212188] hbootctrl: HBOOT_BOOT1. handle[0]
<4>[ 222.212432] hboot_boot
Click to expand...
Click to collapse
That was really quick.... I've spend almost a week configuring environment
The logs from the org kernel are ok. And the kernel is larger then mine probably due to a fact that I use slightly different compiler. But I guess that should not be a problem. Could you post your kernel? I would check if there is "uncompressing linux..." console output from the new kernel over micro-usb.
i have trouble with upload attachment in this forum. please download my kernel from here: "www . mimitech . net / zImage1" (please delete all space in it)
thanks
czechop said:
That was really quick.... I've spend almost a week configuring environment
The logs from the org kernel are ok. And the kernel is larger then mine probably due to a fact that I use slightly different compiler. But I guess that should not be a problem. Could you post your kernel? I would check if there is "uncompressing linux..." console output from the new kernel over micro-usb.
Click to expand...
Click to collapse
czechop said:
Thanks for this tip
BTW, do you know if there is some way to restart then into 2nd-boot via bootmenu automatically(so that I don't need to choose 2nd-boot from the bootmenu list... this would speed booting up a little bit), but preserving 2nd-init as the default bootmenu option?
Click to expand...
Click to collapse
No, there's no such feature. But simple modification of init scripts will do the job. You could just create file before restart and check it's presence in one of init scripts, e.g. 2nd-init.sh. Depending on file presence proceed with regular 2nd-init contents or run 2nd-boot.
That's the quickest I can think of.
Hi,
I bought a second hand i9505, which i used for several days with the standard Samsung stuff.
After a few day's i installed CM11, but after a day my wifi stopped working.
Then i started googling, found several other treads with the same problem, tried those solutions.
But at the this point none of them worked for me.
Things that i tried:
-Different modems
-Stock Samsung rom
-Factory reset
-Format /system , and reflash stock rom with Odin
-Pull the battery out for 30mins
-Reconnected the Wifi antenna
-Deleted the WPA_Supplicant file
-Disable the powersaving mode under *#0011#
Al of them did not work for me.
Is there anybody who has an idea?
Thanks in advance!
sven93 said:
Hi,
I bought a second hand i9505, which i used for several days with the standard Samsung stuff.
After a few day's i installed CM11, but after a day my wifi stopped working.
Then i started googling, found several other treads with the same problem, tried those solutions.
But at the this point none of them worked for me.
Things that i tried:
-Different modems
-Stock Samsung rom
-Factory reset
-Format /system , and reflash stock rom with Odin
-Pull the battery out for 30mins
-Reconnected the Wifi antenna
-Deleted the WPA_Supplicant file
-Disable the powersaving mode under *#0011#
Al of them did not work for me.
Is there anybody who has an idea?
Thanks in advance!
Click to expand...
Click to collapse
Hi,
Maybe is hardware related did you check if the WIFI Antenna Signal Flex Cable is well connected?
https://www.ifixit.com/Teardown/Samsung+Galaxy+S4+Teardown/13947
MAX 404 said:
Hi,
Maybe is hardware related did you check if the WIFI Antenna Signal Flex Cable is well connected?
Click to expand...
Click to collapse
Thanks, but i already tried this.
Reconnected both connections, and made sure both were aligned flat on the connector.
Unfortunately without any result.
sven93 said:
Thanks, but i already tried this.
Reconnected both connections, and made sure both were aligned flat on the connector.
Unfortunately without any result.
Click to expand...
Click to collapse
Maybe is the chip....can you scan , do you see wifi networks or did you try the option wifi direct , between your phone and another unit?
MAX 404 said:
Maybe is the chip....can you scan , do you see wifi networks or did you try the option wifi direct , between your phone and another unit?
Click to expand...
Click to collapse
Well, lets hope its not the chip.
I can't turn on the wifi, if i tap the wifi button (either in settings or at the notifications area) it goes green for 0.5 sec and goes to grey right after.
Haven't tried wifi-direct as i don't have any compatible devices.
Just tried to turn on the tether service, there is states "Error" when i try to turn it on.
Is there any logfile that i can use to determine the cause?
sven93 said:
Well, lets hope its not the chip.
I can't turn on the wifi, if i tap the wifi button (either in settings or at the notifications area) it goes green for 0.5 sec and goes to grey right after.
Haven't tried wifi-direct as i don't have any compatible devices.
Just tried to turn on the tether service, there is states "Error" when i try to turn it on.
Is there any logfile that i can use to determine the cause?
Click to expand...
Click to collapse
Not sure about the log file ...
Here i found a thread , it talks about a solution but they use a SPT box, for what i see the problem is efs related, do you have an EFS backup?
http://forum.gsmhosting.com/vbb/f45...nlock-default-efs-imei-solution-here-1788263/
Nope, unfortunately i didn't backup the EFS folder.
Flashed my S2 a thousand times, with backup, never happened anything. I flash my S4 1 time without,...
Compared the content with the S2, and for me is looks like everything needed is still there. (not an expert though)
Any other ideas?
sven93 said:
Nope, unfortunately i didn't backup the EFS folder.
Flashed my S2 a thousand times, with backup, never happened anything. I flash my S4 1 time without,...
Compared the content with the S2, and for me is looks like everything needed is still there. (not an expert though)
Any other ideas?
Click to expand...
Click to collapse
1. Dial *#1234# in Stock Rom and check if your Csc is correct.
2. Reflash 2 times the stock rom.
Joku1981 said:
1. Dial *#1234# in Stock Rom and check if your Csc is correct.
2. Reflash 2 times the stock rom.
Click to expand...
Click to collapse
CSC Seems to match.
Tried flashing it 3 times in a row with the same (stock) ROM, still nothing.
sven93 said:
Hi,
I bought a second hand i9505, which i used for several days with the standard Samsung stuff.
After a few day's i installed CM11, but after a day my wifi stopped working.
Then i started googling, found several other treads with the same problem, tried those solutions.
But at the this point none of them worked for me.
Things that i tried:
-Different modems
-Stock Samsung rom
-Factory reset
-Format /system , and reflash stock rom with Odin
-Pull the battery out for 30mins
-Reconnected the Wifi antenna
-Deleted the WPA_Supplicant file
-Disable the powersaving mode under *#0011#
Al of them did not work for me.
Is there anybody who has an idea?
Thanks in advance!
Click to expand...
Click to collapse
I have the same problem. Wifi won't turn on no matter what I do. I was on cm-11-20140627-NIGHTLY-jflte and then decided to upgrade to cm-11-20140908-NIGHTLY-jflte. With that upgrade I lost wifi. I tried every possible thing that I found on forums and nothing helped. I also tried to upgrade to latest stock. I was on old bootloader until then, now I have the KNOX sh...t.
I have a feeling that something is wrong with wifi firmware. Is there a way to somehow check or reflash wifi firmware only?
regards.
ajax505 said:
I have the same problem. Wifi won't turn on no matter what I do. I was on cm-11-20140627-NIGHTLY-jflte and then decided to upgrade to cm-11-20140908-NIGHTLY-jflte. With that upgrade I lost wifi. I tried every possible thing that I found on forums and nothing helped. I also tried to upgrade to latest stock. I was on old bootloader until then, now I have the KNOX sh...t.
I have a feeling that something is wrong with wifi firmware. Is there a way to somehow check or reflash wifi firmware only?
regards.
Click to expand...
Click to collapse
Sad to hear you have the same.
Pretty strange, i haven't used the S4 since Wednesday, but the phone was still turned on, ten minutes ago i wanted to check something, turns out wifi is working again, until i decided to reboot, now its doing the same as before...
It does indeed smells software/firmware related.
Just made a dumpfile of the logs (bugreport > /mnt/sdcard/dump.txt) , and saw some interesting stuff in the kernel log:
<4>[ 9.717163] failed to power up wifi chip, retry again (5 left) **
<4>[ 9.717163]
<4>[ 9.733306] ## wifi_remove
<4>[ 9.733612] wifi_set_power = 1
<4>[ 9.733612] WiFi: trying to acquire BT lock
<4>[ 9.733612] ####btlock acquired cookie: WiFi
<4>[ 9.733642] wifi_set_power: btlock acquired
<6>[ 9.733642] ------------------------------------------------
<6>[ 9.733642] ------------------------------------------------
<6>[ 9.733642] brcm_wlan_power Enter: power on
<3>[ 9.733642] brcm_wlan_power: WL_REG_ON failed to pull up
<4>[ 9.733734] wifi_probe: set_power failed. err=-5
<4>[ 9.733734] wifi_set_power = 0
<4>[ 9.733734] ####btlock released, cookie: WiFi
<6>[ 9.733734] ------------------------------------------------
<6>[ 9.733795] ------------------------------------------------
<6>[ 9.733825] brcm_wlan_power Enter: power off
<3>[ 9.733825] brcm_wlan_power: WL_REG_ON failed to pull down
Click to expand...
Click to collapse
Then after a bit:
<4>[ 11.727294]
<4>[ 11.727294] failed to power up wifi chip, retry again (4 left) **
<4>[ 11.727294]
<4>[ 11.743499] ## wifi_remove
<4>[ 11.743835] wifi_set_power = 1
<4>[ 11.743835] WiFi: trying to acquire BT lock
<4>[ 11.743835] ####btlock acquired cookie: WiFi
<4>[ 11.743835] wifi_set_power: btlock acquired
<6>[ 11.743835] ------------------------------------------------
<6>[ 11.743865] ------------------------------------------------
<6>[ 11.743865] brcm_wlan_power Enter: power on
<6>[ 11.743865] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 1
<6>[ 11.754608] [email protected]: Start PackageManagerService
<6>[ 11.775604] [SSP] Updated 73599 bytes / 139282 bytes
<4>[ 11.977172] wifi_set_carddetect = 1
<4>[ 11.977172] brcm_wifi_status:267 status 1
Click to expand...
Click to collapse
For people who want to view the log: https://dl.dropboxusercontent.com/u/15503253/dumpfile.txt
I also get those kind of messages in my system logs:
<4>[ 1837.921936] failed to power up wifi chip, retry again (1 left) **
<4>[ 1837.921966]
<4>[ 1837.941497] ## wifi_remove
<4>[ 1837.941497] wifi_set_power = 0
<4>[ 1837.941528] ####btlock released, cookie: WiFi
<6>[ 1837.941558] ------------------------------------------------
<6>[ 1837.941558] ------------------------------------------------
<6>[ 1837.941589] brcm_wlan_power Enter: power off
<6>[ 1837.941619] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 0
<4>[ 1838.182006] wifi_set_carddetect = 0
<4>[ 1838.182037] brcm_wifi_status:267 status 0
<6>[ 1838.182067] mmc1: Slot status change detected (1 -> 0)
<4>[ 1838.187591]
<4>[ 1838.187622] failed to power up wifi chip, max retry reached, exits **
Click to expand...
Click to collapse
I also get a lot of "mmc1: Data CRC error":
<3>[ 1826.574645] mmc1: Data CRC error
<3>[ 1826.577178] msmsdcc_data_err: opcode 0x00000035
<3>[ 1826.581542] msmsdcc_data_err: blksz 4, blocks 1
<6>[ 1826.586883] sps:BAM 0x12182000 enabled: ver:0x5, number of pipes:6dhd_detach(): thread:dhd_sysioc:392 terminated OK
<4>[ 1826.651245] dhd_detach(): thread:dhd_watchdog_thread:38f terminated OK
<4>[ 1826.651336] dhd_dpc_thread: Unexpected up_cnt 0
<4>[ 1826.651428] dhd_detach(): thread:dhd_dpc:390 terminated OK
<4>[ 1826.651733] dhd_detach(): thread:dhd_rxf:391 terminated OK
<6>[ 1826.670593] CFG80211-INFO2) wl_event_handler : was terminated
<4>[ 1826.670898] wl_destroy_event_handler(): thread:wl_event_handler:38e terminated OK
<4>[ 1826.682250] dhdsdio_disconnect : the lock is released.
<4>[ 1826.683807] ## wifi_remove
<4>[ 1826.683837] wifi_set_power = 0
<4>[ 1826.683868] ####ignore lock release, cookie mismatch: WiFi owner ˙˙˙˙
<6>[ 1826.683898] ------------------------------------------------
<6>[ 1826.683898] ------------------------------------------------
<6>[ 1826.683929] brcm_wlan_power Enter: power off
<6>[ 1826.683959] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 0
<4>[ 1826.920593] wifi_set_carddetect = 0
<4>[ 1826.920623] brcm_wifi_status:267 status 0
<6>[ 1826.920654] mmc1: Slot status change detected (1 -> 0)
<6>[ 1826.928405] mmc1: card 0001 removed
<6>[ 1828.083618] synaptics_rmi4_i2c 3-0020: [0][P] 0x01
<6>[ 1828.142578] synaptics_rmi4_i2c 3-0020: [0][R] 0x00 M[4] V[5c]
<4>[ 1828.178527] wifi_set_power = 1
<4>[ 1828.178558] WiFi: trying to acquire BT lock
<4>[ 1828.178558] ####btlock acquired cookie: WiFi
<4>[ 1828.178558] wifi_set_power: btlock acquired
<6>[ 1828.178558] ------------------------------------------------
<6>[ 1828.178588] ------------------------------------------------
<6>[ 1828.178588] brcm_wlan_power Enter: power on
<6>[ 1828.178588] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 1
<4>[ 1828.411895] wifi_set_carddetect = 1
<4>[ 1828.411926] brcm_wifi_status:267 status 1
<6>[ 1828.411956] mmc1: Slot status change detected (0 -> 1)
<3>[ 1828.473205] mmc1: msmsdcc_switch_io_voltage: MCIDATIN_3_0 is still not all zeros
<3>[ 1828.480651] mmc1: CMD7: Command CRC error
<3>[ 1828.484039] mmc1: SDCC PWR is ON
<3>[ 1828.487426] mmc1: SDCC clks are ON, MCLK rate=400000
<3>[ 1828.492217] mmc1: SDCC irq is enabled
<3>[ 1828.495849] ===== SDCC-CORE: Register Dumps @phys_base=0x12180000, @virt_base=0xe337a000 =====
<3>[ 1828.504608] Reg=0x00: 0x00000001, 0x01209300, 0x00000000, 0x00000447
<3>[ 1828.510955] Reg=0x10: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.517120] Reg=0x20: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.523620] Reg=0x30: 0x00000000, 0x004c0000, 0x00000000, 0x408001ff
<3>[ 1828.529785] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.536285] Reg=0x50: 0x06000018, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.542633] Reg=0x60: 0x67356400, 0x00000000, 0x00000018, 0x00000000
<3>[ 1828.548797] ===== SDCC-DML: Register Dumps @phys_base=0x12180800, @virt_base=0xe3534800 =====
<3>[ 1828.557495] Reg=0x00: 0x00000000, 0x00010001, 0x00000000, 0x00000000
<3>[ 1828.563629] Reg=0x10: 0x00000000, 0x00001000, 0x00001000, 0x00020001
<3>[ 1828.570159] Reg=0x20: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.576477] Reg=0x30: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.582641] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.589172] ===== SDCC-BAM: Register Dumps @phys_base=0x12182000, @virt_base=0xe33d8000 =====
<3>[ 1828.597503] Reg=0x00: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.604003] Reg=0x10: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.610351] Reg=0x20: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.616516] Reg=0x30: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.623016] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.629180] mmc1: MCI_TEST_INPUT = 0x0000003e
<3>[ 1828.633697] mmc1: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0, req_tout_ms=10000
<3>[ 1828.644012] mmc1: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<3>[ 1828.650817] mmc1: RPM: runtime_status=0, usage_count=2, is_suspended=0, disable_depth=0, runtime_error=0, request_pending=0, request=0
<4>[ 1828.663024] mmc1: Skipped tuning.
<3>[ 1828.686431] mmc1: error -110 whilst initialising SDIO card
<4>[ 1830.421936]
<4>[ 1830.421966] failed to power up wifi chip, retry again (4 left) **
Click to expand...
Click to collapse
As long as I know mmc0 is internal memory and mmc2 is external sd card. Can anyone explain what mmc1 device is?
Bump...