Database Info

[Partial Solution] Wi-Fi unable to start.

"Wi-Fi unable to start" error appeared couple weeks ago.
I have tried everything - reflashing different images, radio, formatting ... etc.
Nothing helped.
In a desperate moment I tried something.
Here are the steps:
I made some progress and it seams that is pure software problem.
Currently I'm with G1/black Cyanogen 3.6.8.1, Recovery 1.4 and 8GB SD/class 4.
What I did is reformatting the SD card in 2 partitions 1st FAT32 and 2nd ext2 ~ 460MB.
Wiped before flashing cyanogen build and also I made sure that there is nothing on the ext2 partition.
When flashing finished I waited the phone to fully set up itself on the first boot ~5-7 min.
Then I tried the WiFi - it didn't start
The important and desperate thing I did was to go to su console in /system/lib/modules and tried to load wlan.ko manually (insmod wlan.ko) - it failed the 1st time.
Then I tried 2 times more and it loaded itself successfully (of course wifi connection is not established in that moment, because loading the module is just one step of the process).
I unloaded successfully (rmmod wlan) the module and tried to start WiFi again - gues what - It worked!
That is just partial solution of the problem, but shows that it is just a software problem.
I guess some timeouts appear and WiFi starting procedure is not so patient to wait for the module to start up and it's not retrying to unload and load again the module.
Good luck
Hope it will work on yours G1.
Cheers

this has been up on a google code bug report page for a while now. I had the same result when trying to start the module in the terminal
cyanogen's new 3.9.1 scary experimental build shows that he used a new wifi driver in the changelog but that hasn't helped me with this issue at all. I thought it might be a software conflict so I used a clean sd card, flashed my update.zip, and still had the same problem

I have tried Cyanogen 3.9.1 with the same result - it doesn't work for me.
I can't explain why it started to work again in 3.6.8.1
Anyway, try to copy all your important files (not system/applications created like thumbnails folder) to your PC, put the SD card to card reader connected to a PC and then do a full reformat to FAT32.
Partition the newly formatted SD card to FAT32 and EXT2 partitions.
Reformat partitions again, copy update.zip to your SD card.
Start up your G1 holding home button and do wipe ( I wiped 2-3 times just to be sure )
Do ext2 system repair from the repair menu.
Do not convert it to ext3.
Apply the update.zip and continue to the next steps I wrote above.
Hope that's info is useful for you.

Post the output of "dmesg" after you try to install the module. It will tell us whats going wrong. This is not normal at all and might be hardware related.

cssvb94 said:
but shows that it is just a software problem.
Click to expand...
Click to collapse
I don't see how you come to the conclusion that it is a software problem. Intermittence is typically a sign of a HARDWARE problem.

lbcoder said:
I don't see how you come to the conclusion that it is a software problem. Intermittence is typically a sign of a HARDWARE problem.
Click to expand...
Click to collapse
Simple, it works somethimes on some builds and it doesn't at all on others - same hardware, different software.
Anyway, I realy hope it's not hardware related ...

cyanogen said:
Post the output of "dmesg" after you try to install the module. It will tell us whats going wrong. This is not normal at all and might be hardware related.
Click to expand...
Click to collapse
Is that request for me or airmaxx?
I really don't want to reflash now when it's working.
In the moment when something goes wrong I'll post dmesg.
I've noticed "D/wlan_loader( 228): ConfigMge start rc = -1" couple times in dmesg output when it wasn't working and "D/wlan_loader( 228): ConfigMge start rc = 0" when it works.

after a clean install of cyanogen 3.9.1, i tried to start with in the gui, through settings menu. after it reported "unable to start wifi" this is my dmesg output....
Code:
<6>[ 695.675048] TIWLAN: Driver loading
<4>[ 695.679168] wifi_probe
<4>[ 695.681762] trout_wifi_power: 1
<4>[ 695.888366] trout_wifi_reset: 0
<4>[ 695.943084] trout_wifi_set_carddetect: 1
<7>[ 695.947265] mmc0: card_present 1
<6>[ 695.950744] mmc0: Slot status change detected (0 -> 1)
<3>[ 698.464202] mmc0: Command timeout
<4>[ 698.474548] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 698.484191] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
<6>[ 698.497955] mmc0: new SDIO card at address 0001
<6>[ 698.508758] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 698.517639] tiwlan0 (): not using net_device_ops yet
<6>[ 698.530426] TIWLAN: Driver initialized (rc 0)
<3>[ 698.535705] mmc0: Data CRC error
<3>[ 698.539276] msmsdcc_data_err: opcode 0x00000035
<3>[ 698.544128] msmsdcc_data_err: blksz 4, blocks 1
<3>[ 698.549621] SDIO_SyncWrite: failed (-84)
<3>[ 698.554016] mmc0: Data CRC error
<3>[ 698.557586] msmsdcc_data_err: opcode 0x00000035
<3>[ 698.562713] msmsdcc_data_err: blksz 4, blocks 1
<3>[ 698.567718] SDIO_SyncWrite: failed (-84)
<3>[ 701.399383] mmc0: Data timeout
<3>[ 701.403289] SDIO_SyncRead: failed (-110)
<4>[ 701.407623] TIWLAN: invalid chip id = 0x 0 0 0 0!
<6>[ 701.412933] TIWLAN: Driver loaded
<4>[ 701.820495] select 226 (app_process), adj 15, size 3301, to kill
<4>[ 701.826873] send sigkill to 226 (app_process), adj 15, size 3301
<3>[ 704.165802] mmc0: Data timeout
<3>[ 704.169311] SDIO_SyncRead: failed (-110)
<3>[ 704.174041] TIWLAN: TIWLAN: Failed to start config manager
<6>[ 710.698730] RPC_TIME_TOD_SET_APPS_BASES:
<6>[ 710.698760] tick = 38620607
<6>[ 710.698760] stamp = 48907518449025024
<4>[ 735.120178] select 480 (app_process), adj 15, size 4338, to kill
<4>[ 735.126464] send sigkill to 480 (app_process), adj 15, size 4338
something i remembered earlier was that long ago, many roms and flashes prior (when I was still chasing after Hero and Rosie) i saw a wpa supplicant file had been installed on my fat32 partition, no system folder or anything just on the root of the card. i remember thinking at the time how odd this was and manually deleting the file prior to my next flash.
My problem may have started shortly thereafter but honestly don't remember, just grasping for straws here

cssvb94 said:
Simple, it works somethimes on some builds and it doesn't at all on others - same hardware, different software.
Anyway, I realy hope it's not hardware related ...
Click to expand...
Click to collapse
Really? That's not what you said before...
cssvb94 said:
I have tried everything - reflashing different images, radio, formatting ... etc.
Nothing helped.
Click to expand...
Click to collapse
Clearly, it is NOT related to the software since you TRIED CHANGING the software and it didn't help, and the SAME SOFTWARE works fine for everybody else, which means that it MUST be either USER ERROR, or HARDWARE DEFECT.

lbcoder said:
Really? That's not what you said before...
Clearly, it is NOT related to the software since you TRIED CHANGING the software and it didn't help, and the SAME SOFTWARE works fine for everybody else, which means that it MUST be either USER ERROR, or HARDWARE DEFECT.
Click to expand...
Click to collapse
Listen, I'm not here to argue and I don't have anything against you.
Why you are so catchy about that simple details?
I'm trying to help and share what I've been through.
If you are offended of something I said then - sorry.
Don't be such arrogant, capital letters don't work on me. =)
----------------------------------------------------------------------
This is cut from my dmesg :
WiFi starting OK
--- cut ---
<6>[ 268.613555] TIWLAN: Driver loading
<4>[ 268.617797] wifi_probe
<4>[ 268.620758] trout_wifi_power: 1
<4>[ 268.830261] trout_wifi_reset: 0
<4>[ 268.884521] trout_wifi_set_carddetect: 1
<7>[ 268.888824] mmc0: card_present 1
<6>[ 268.892303] mmc0: Slot status change detected (0 -> 1)
<3>[ 271.400268] mmc0: Command timeout
<4>[ 271.410339] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 271.419982] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
<6>[ 271.436584] mmc0: new SDIO card at address 0001
<6>[ 271.446960] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 271.455352] tiwlan0 (): not using net_device_ops yet
<6>[ 271.464538] TIWLAN: Driver initialized (rc 0)
<4>[ 271.469909] TIWLAN: 1251 PG 1.2
<6>[ 271.473693] TIWLAN: Driver loaded
<3>[ 271.863403] mmc0: Data CRC error
<3>[ 271.866851] msmsdcc_data_err: opcode 0x00000035
<3>[ 271.871551] msmsdcc_data_err: blksz 512, blocks 1
<4>[ 271.877441] SDIO Write failure (-84)
<3>[ 271.883209] TIWLAN: TIWLAN: Failed to start config manager
--- cut ---
<6>[ 689.787445] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 689.795745] tiwlan0 (): not using net_device_ops yet
<6>[ 689.804901] TIWLAN: Driver initialized (rc 0)
<4>[ 689.810150] TIWLAN: 1251 PG 1.2
<6>[ 689.813690] TIWLAN: Driver loaded
<3>[ 690.153045] mmc0: Data CRC error
<3>[ 690.156463] msmsdcc_data_err: opcode 0x00000035
<3>[ 690.161163] msmsdcc_data_err: blksz 4, blocks 1
<4>[ 690.168182] SDIO Write failure (-84)
<3>[ 690.173889] TIWLAN: TIWLAN: Failed to start config manager
--- cut ---
Now new case: "Unable to stop Wi-Fi"
rmmod wlan throws back: "rmmod: delete_module 'wlan' failed (errno 11)"
lsmod returns: "wlan 566844 1 - Live 0xbf480000"

lbcoder, was there anything in my dmesg that confirmed it is indeed hardware, or anything useful at all in there?
after reading the reports on googlecode pages, i was leaning to hardware issue only because the problem is so rare and those people sent their g1's back in. I was really hoping this wasn't the case though.
I'd be happy with intermittent at this point, my wifi has not turned on in like 2 months my phone was purchased used (wifi worked fine at the time though) on craigslist so I can't return it to TMO

The CRC errors on mmc0 means that your sdcard is dying. It might seem unrelated but because how the way the G1 hardware works, this could be the problem. Yank your card and try it again.

No more WiFi
"Unable to stop" or "Unable to start" after reboot.
Tried with different SD card - no CRC errors and still no WiFi

for me the wifi turned on but it cant connect with a router... just write obtain ip address.. and after.. no connection
this is my log
<6>[ 175.583831] ept #2 out max:512 head:ffc0c100 bit:2
<6>[ 175.584289] ept #0 in max:64 head:ffc0c040 bit:16
<6>[ 175.585083] ept #1 in max:512 head:ffc0c0c0 bit:17
<6>[ 175.585510] ept #2 in max:512 head:ffc0c140 bit:18
<6>[ 175.586059] usb: notify offline
<6>[ 175.594207] usb: suspend
<6>[ 175.813262] usb: reset
<6>[ 175.815673] usb: portchange USB_SPEED_HIGH
<6>[ 175.967803] usb: reset
<6>[ 175.970092] usb: portchange USB_SPEED_HIGH
<6>[ 176.164825] usb_mass_storage usb_mass_storage: config #1
<6>[ 187.209259] request_suspend_state: wakeup (3->0) at 180968491210 (2009-07-
29 16:16:01.570098877 UTC)
<6>[ 188.333618] TIWLAN: Driver loading
<4>[ 188.334503] wifi_probe
<4>[ 188.334777] trout_wifi_power: 1
<4>[ 188.536346] trout_wifi_reset: 0
<4>[ 188.586914] trout_wifi_set_carddetect: 1
<7>[ 188.587432] mmc0: card_present 1
<6>[ 188.587738] mmc0: Slot status change detected (0 -> 1)
<3>[ 191.095031] mmc0: Command timeout
<4>[ 191.102386] mmc0: card claims to support voltages below the defined range.
These will be ignored.
<4>[ 191.103210] mmc0: SDIO card claims to support the incompletely defined 'lo
w voltage range'. This will be ignored.
<6>[ 191.112518] mmc0: new SDIO card at address 0001
<6>[ 191.118377] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 191.123901] TIWLAN: Driver initialized (rc 0)
<4>[ 191.125244] TIWLAN: 1251 PG 1.2
<6>[ 191.125701] TIWLAN: Driver loaded
<6>[ 192.657897] snd_set_volume 256 0 5
<6>[ 192.747344] snd_set_volume 256 0 5
<3>[ 198.871185] init: sys_prop: permission denied uid:1000 name:ro.config.noc
heckin
<6>[ 244.551879] TIWLAN: Driver unloading
<4>[ 244.553070] sdio_reset_comm():
<7>[ 244.631011] TIWLAN: Releasing SDIO resources
<7>[ 244.632324] TIWLAN: SDIO resources released
<4>[ 244.634918] wifi_remove
<4>[ 244.635406] trout_wifi_set_carddetect: 0
<7>[ 244.636199] mmc0: card_present 0
<6>[ 244.636627] mmc0: Slot status change detected (1 -> 0)
<6>[ 244.639465] mmc0: card 0002 removed
<4>[ 244.643585] trout_wifi_reset: 1
<4>[ 244.699401] trout_wifi_power: 0
<6>[ 244.905883] TIWLAN: Driver unloaded
<6>[ 246.548492] TIWLAN: Driver loading
<4>[ 246.549377] wifi_probe
<4>[ 246.549652] trout_wifi_power: 1
<4>[ 246.754119] trout_wifi_reset: 0
<4>[ 246.805236] trout_wifi_set_carddetect: 1
<7>[ 246.805786] mmc0: card_present 1
<6>[ 246.806060] mmc0: Slot status change detected (0 -> 1)
<3>[ 249.310638] mmc0: Command timeout
<4>[ 249.318481] mmc0: card claims to support voltages below the defined range.
These will be ignored.
<4>[ 249.319335] mmc0: SDIO card claims to support the incompletely defined 'lo
w voltage range'. This will be ignored.
<6>[ 249.326782] mmc0: new SDIO card at address 0001
<6>[ 249.332794] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 249.338226] TIWLAN: Driver initialized (rc 0)
<4>[ 249.339141] TIWLAN: 1251 PG 1.2
<6>[ 249.339599] TIWLAN: Driver loaded
<6>[ 994.061614] request_suspend_state: sleep (0->3) at 987820816650 (2009-07-2
9 16:29:28.422424317 UTC)
<4>[ 994.083801] deinit sharp panel
<4>[ 994.762908] save exit: isCheckpointed 1
<4>[ 994.765380] save exit: isCheckpointed 1

If you want help, get your details straight! If you contradict yourself all over the place, then nobody can possibly know what is going on and you won't get anywhere.
cssvb94 said:
Listen, I'm not here to argue and I don't have anything against you.
Why you are so catchy about that simple details?
Click to expand...
Click to collapse

You mention having tried flashing different software...
Have you tried flashing IMAGES (fastboot) or just update scripts (i.e. update.zip)?
If you haven't tried already, I suggest flashing the stock *engineering* bootloader 0.95.3000, ADP1-CRC1 images from www.htc.com -- the one that's labeled as "system image" (not the one labeled "recovery image", which is just an update.zip), and radio v2_22_19_26I (also from htc.com), write everything to the phone using fastboot, pull the battery, wait 10 minutes, and see what happens. IF it is a software problem, then this will *definitely* fix it. If it is a HARDWARE problem, then this will *definitely NOT* fix it. If the wifi starts working right after you write these things, *do not* conclude that it was a software problem since it could simply have gone intermittent-on. Keep the software like that and run it for at least a week to make sure the problem doesn't come back before making your conclusions.

Went back to stock 1.0 RC29 with original SPL, radio and bootloader and started from scratch.
Also formated SD card - only one partition FAT32.
Now I'm with ADP1.5 JF and WiFi is working most of the time.
So angry lbcoder what's your great verdict now? SOFTWARE or HARDWARE?

lbcoder said:
You mention having tried flashing different software...
Have you tried flashing IMAGES (fastboot) or just update scripts (i.e. update.zip)?
If you haven't tried already, I suggest flashing the stock *engineering* bootloader 0.95.3000, ADP1-CRC1 images from www.htc.com -- the one that's labeled as "system image" (not the one labeled "recovery image", which is just an update.zip), and radio v2_22_19_26I (also from htc.com), write everything to the phone using fastboot, pull the battery, wait 10 minutes, and see what happens. IF it is a software problem, then this will *definitely* fix it. If it is a HARDWARE problem, then this will *definitely NOT* fix it. If the wifi starts working right after you write these things, *do not* conclude that it was a software problem since it could simply have gone intermittent-on. Keep the software like that and run it for at least a week to make sure the problem doesn't come back before making your conclusions.
Click to expand...
Click to collapse
which is the commands for push the radio and the the adp1-crc1 image via fastboot?
i can t find ADP1-CRC1 images can you give me a url please?

success!!!!!!
the problem was the radio... i flashed 2 times the radio and now work!!!!!
thanks guyssss i love you aahahah

rock187 said:
the problem was the radio... i flashed 2 times the radio and now work!!!!!
thanks guyssss i love you aahahah
Click to expand...
Click to collapse
Great =)
Would you please post full step-by-step what you did.
10x in advance
It didn't work for me. I'm going to return my G1 back to the store I bought it, it's still under warranty.

[Q] Can I just confirm my phone is stuffed?

History:
Desire S rooted using "revolutionary-0.4pre4" but otherwise no changes (rooted many months ago).
Crashed during update of Apps (I pressed update all and it crashed it after a few minutes). Had to pull the battery out to reset. Crashed again after about 2 minutes so I pulled the battery again and now won't load past the HTC loading screen.
I assume something fried as I pulled the battery.
I have tried updating the ROM without success - just to confirm I am doing it properly I put the file onto the phone's normal SD card (eg "RunnymedeS-Saga-v6.zip"), start recovery mode, wipe data and cache and load from zip file.
It either finishes loading or says there is a problem with the zip file (I've tried 5 or so ROM files). on the times it managed to finish it resets and just gets stuck on the HTC load screen (like before).
In Recovery mode I have:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 10 2011,14:58:38
Is the phone stuffed or is there anything else I can try?

col320ce said:
History:
Desire S rooted using "revolutionary-0.4pre4" but otherwise no changes (rooted many months ago).
Crashed during update of Apps (I pressed update all and it crashed it after a few minutes). Had to pull the battery out to reset. Crashed again after about 2 minutes so I pulled the battery again and now won't load past the HTC loading screen.
I assume something fried as I pulled the battery.
I have tried updating the ROM without success - just to confirm I am doing it properly I put the file onto the phone's normal SD card (eg "RunnymedeS-Saga-v6.zip"), start recovery mode, wipe data and cache and load from zip file.
It either finishes loading or says there is a problem with the zip file (I've tried 5 or so ROM files). on the times it managed to finish it resets and just gets stuck on the HTC load screen (like before).
In Recovery mode I have:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 10 2011,14:58:38
Is the phone stuffed or is there anything else I can try?
Click to expand...
Click to collapse
Ate you still able to boot into recovery?? Try full wiping your phone
Sent my thoughts to your head with XDA App

i'm no expert, but i'm pretty sure there is still bunch of options for you...
search trough forum, even try to install stock roms (ruu)
chin up!

I have tried a full wipe but will try a .RUU file.
I can get into recovery and move about...

Just tried installing from .RUU file using FASTBOOT USB and RUU from computer. And it won't get past the first screen - "Rebooting to bootloader.........."
After all I have done it still tells me I have Software version 1.47.832.1 installed.

col320ce said:
History:
Desire S rooted using "revolutionary-0.4pre4" but otherwise no changes (rooted many months ago).
Crashed during update of Apps (I pressed update all and it crashed it after a few minutes). Had to pull the battery out to reset. Crashed again after about 2 minutes so I pulled the battery again and now won't load past the HTC loading screen.
I assume something fried as I pulled the battery.
I have tried updating the ROM without success - just to confirm I am doing it properly I put the file onto the phone's normal SD card (eg "RunnymedeS-Saga-v6.zip"), start recovery mode, wipe data and cache and load from zip file.
It either finishes loading or says there is a problem with the zip file (I've tried 5 or so ROM files). on the times it managed to finish it resets and just gets stuck on the HTC load screen (like before).
In Recovery mode I have:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 10 2011,14:58:38
Is the phone stuffed or is there anything else I can try?
Click to expand...
Click to collapse
Can you enter the custom recovery at all?
If so, do the following and post your result so first we can rule out an eMMC problem.
Set up adb (link in my sig) connect your device to the PC, enter recovery, open cmd (command prompt) on the PC and type:
adb shell
dmesg | grep mmc0
Source : Amidabuddha's excellent guide here : http://forum.xda-developers.com/showthread.php?t=1284196

I can enter recovery and I am on the screen with "HBOOT USB PLUG" when plugged into the PC.
I have set up the abd link but it cmd says "error: device not found"
I assume I have not installed adb correctly or am not in the correct part of the command prompt. Do I need to go to C:/android-tools/ then type adb shell or does it not matter?
When I type
adb shell
dmesg | grep mmc0
I assume I hit return after the first line?
How do I type the vertical line in the second line?
I have HTC Sync Installed
I have the folder at c drive root - c:\android-tools\
I have put a copy of the content of the folder into windows\sytem32
I can't see the phone in "my computer" when it is attached by USB.
???

Just got it to work
C:\Documents and Settings\Person>adb shell
~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 8.471618] mmc0: No card detect facilities available
<6>[ 8.472259] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 8.472412] mmc0: Platform slot type: MMC
<6>[ 8.472625] mmc0: 4 bit data mode disabled
<6>[ 8.472747] mmc0: 8 bit data mode enabled
<6>[ 8.472991] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 8.473114] mmc0: Slot eject status = 0
<6>[ 8.473236] mmc0: Power save feature enable = 1
<6>[ 8.473480] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c1fa000
<6>[ 8.473602] mmc0: DM cmd busaddr 0x0c1fa000, cmdptr busaddr 0x0c1fa300
<6>[ 8.626892] mmc0: new high speed MMC card at address 0001
<6>[ 8.628082] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
<3>[ 9.837493] mmc0: Failed to get card ready i = 122109
<6>[ 9.837585] mmc0: reinit card
<4>[ 9.837707] mmc0: Starting deferred resume
<6>[ 11.879486] mmc0: Deferred resume failed
<3>[ 11.881774] mmc0: DMA channel flushed (0x80000004)
<6>[ 11.882141] mmc0: Controller has been reset
<6>[ 11.882324] mmc0: Worked around bug 1535304
<3>[ 11.883758] mmc0: DMA channel flushed (0x80000004)
<6>[ 11.884094] mmc0: Controller has been reset
<6>[ 11.884368] mmc0: Worked around bug 1535304
<6>[ 11.890960] mmc0: reinit card
<4>[ 11.891052] mmc0: Starting deferred resume
<6>[ 13.931549] mmc0: Deferred resume failed
~ #
I don't think this is a good sign.
thanks

col320ce said:
I can enter recovery and I am on the screen with "HBOOT USB PLUG" when plugged into the PC.
???
Click to expand...
Click to collapse
There is a difference between being in the bootloader and Recovery.xCan you boot into recovery?

col320ce said:
<3>[ 9.837493] mmc0: Failed to get card ready i = 122109
<6>[ 9.837585] mmc0: reinit card
<4>[ 9.837707] mmc0: Starting deferred resume
<6>[ 11.879486] mmc0: Deferred resume failed
<3>[ 11.881774] mmc0: DMA channel flushed (0x80000004)
<6>[ 11.882141] mmc0: Controller has been reset
<6>[ 11.882324] mmc0: Worked around bug 1535304
<3>[ 11.883758] mmc0: DMA channel flushed (0x80000004)
<6>[ 11.884094] mmc0: Controller has been reset
<6>[ 11.884368] mmc0: Worked around bug 1535304
<6>[ 11.890960] mmc0: reinit card
<4>[ 11.891052] mmc0: Starting deferred resume
<6>[ 13.931549] mmc0: Deferred resume failed
~ #
Click to expand...
Click to collapse
Sorry man.
col320ce said:
I assume something fried as I pulled the battery.
Click to expand...
Click to collapse
Another proof that this is a dangerous action on Desire S

col320ce said:
Just got it to work
C:\Documents and Settings\Person>adb shell
~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 8.471618] mmc0: No card detect facilities available
<6>[ 8.472259] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 8.472412] mmc0: Platform slot type: MMC
<6>[ 8.472625] mmc0: 4 bit data mode disabled
<6>[ 8.472747] mmc0: 8 bit data mode enabled
<6>[ 8.472991] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 8.473114] mmc0: Slot eject status = 0
<6>[ 8.473236] mmc0: Power save feature enable = 1
<6>[ 8.473480] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c1fa000
<6>[ 8.473602] mmc0: DM cmd busaddr 0x0c1fa000, cmdptr busaddr 0x0c1fa300
<6>[ 8.626892] mmc0: new high speed MMC card at address 0001
<6>[ 8.628082] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
<3>[ 9.837493] mmc0: Failed to get card ready i = 122109
<6>[ 9.837585] mmc0: reinit card
<4>[ 9.837707] mmc0: Starting deferred resume
<6>[ 11.879486] mmc0: Deferred resume failed
<3>[ 11.881774] mmc0: DMA channel flushed (0x80000004)
<6>[ 11.882141] mmc0: Controller has been reset
<6>[ 11.882324] mmc0: Worked around bug 1535304
<3>[ 11.883758] mmc0: DMA channel flushed (0x80000004)
<6>[ 11.884094] mmc0: Controller has been reset
<6>[ 11.884368] mmc0: Worked around bug 1535304
<6>[ 11.890960] mmc0: reinit card
<4>[ 11.891052] mmc0: Starting deferred resume
<6>[ 13.931549] mmc0: Deferred resume failed
~ #
I don't think this is a good sign.
thanks
Click to expand...
Click to collapse
Ouch!
eMMC most likely dead. I'm real sorry man... wish there was anything further i could suggest....
You'll have to take it to the Service Centre, and hope for the best.
I still don't understand, that after all the warnings against pulling battery, why do so many users do it? It baffles me. Honest to God, i still have to figure that behavior out... It's like wanting to brick your phone.

I usaly leave debugging on all the time. If it hangs 3 button combo or clear catches with adb and then restart it. Never pull battery out, if you don't have access to PC then leave it and do it later, better do it without risk. And you got faulty emmc before becouse it hanged on app upgrade. Sorry mate
Sent from my HTC Desire S using xda premium

Is pulling the battery the only way to brick the m4g2de emmc chip or can it just happen on its own?

incrediblealex said:
Is pulling the battery the only way to brick the m4g2de emmc chip or can it just happen on its own?
Click to expand...
Click to collapse
Here is a post about what can brick it. Many things can fry it. But still Never pull out battery
Sent from my HTC Desire S using xda premium

I can enter bootloader but the computer can't find the phone unless I go into the RECOVERY (revolutionary CWM v4.0.1.4). I assume the text printout is still valid?
In bootloader (after vol down and on) I attach the USB and the screen says (amongst other things) HBOOT USB PLUG (from HBOOT).
C:\>adb shell
error: device not found
Unless anyone thinks the phone is not stuffed, can I brick it further to stop the HTC repair man seeing that it is S-OFF? I have tried to remove revolutionary and S-OFF but can't get anything to work.

Not sure If you can brick it further since your emmc is where you write all of the files

[MOD] 1.8GHz+ overclock module for AT&T/Rogers HTC One X/ (One XL)/One S!

One XL/AT&T/Rogers One X/One S 1.8GHz overclock module
Please let me know about the module's compatibility with your phone. It has been reported to work on the latest AT&T version kernel, and I have a Rogers device myself.
Hey guys! I've created a kernel module that overclocks the MSM8960 Qualcomm Krait to over 1.8GHz. It also allows you to specify a custom voltage and frequency instead of 1.8GHz. This method works on ANY MSM8960-based rooted HTC One X, even on locked bootloader devices. This allows AT&T users to overclock, and others to overclock without necessarily needing to unlock the bootloader. This overclock makes the already tremendously fast MSM8960 about 20% faster.
Note that this mod is ONLY for the Qualcomm MSM8960-based Krait HTC One X and HTC One XL. This includes the AT&T HTC One X, Rogers HTC One X, and any phone branded as the HTC One XL. It has also been confirmed to work on the One S (see this thread: http://forum.xda-developers.com/showthread.php?t=1670904) and MIGHT work on the EVO 4G LTE.
The module is loaded using this command: insmod /data/local/krait_oc.ko pll_l_val=67 vdd_uv=1300000
The pll_l_val parameter determines how high the overclock is. Multiply this number by 27 to get the final clock speed in MHz. For example, 67*27 is 1809000, which is what the module defaults to.
The vdd_uv parameter determines the voltage used at the overclocked speed, in microvolts. The default for 1.5GHz is 1200000, and I was able to get a stable overclock at 1300000 at 1.8GHz. Raise the vdd_uv parameter if the overclock is unstable. The current maximum for this field is 1300000, so don't go higher than this. If your system crashes or is unstable at this frequency/voltage, lower the pll_l_val one by one until you reach stability. You can run rmmod krait_oc and then insmod krait_oc.ko with different parameters without having to reboot.
You'll also need a custom, tweaked thermald.conf. This thermald.conf raises thermal tolerances slightly (I've found that they're a little too strict, even at stock clocks and voltages). I've included this in the package, and instructions for installing it are below.
Video, demonstrating the overclock on a Rogers HTC One X:
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Source code is included in the package. If anyone has an HTC One S, this method will work on that, too. Please post below a dump of /system/lib/modules and I should be able to add support for any MSM8960-based HTC device with just that.
Instructions
First, determine which kernel module to use. Do an adb shell cat /proc/version and choose a ko file that matches your version number (these instructions assume you've renamed it to krait_oc.ko). 21/05/2012: If you don't see your kernel version here, try loading the module anyway. If it fails to load, please post a file from /system/lib/modules (any file) here and I will add support.
Install the overclock (only once):
1. Push the kernel module to your device:
Code:
adb push krait_oc.ko /data/local
2. Install the new thermald.conf, making sure to back up the old one, and reboot. The thermald.conf is included in the download. If you want to target a frequency other than 1809000 KHz, you should edit the thermald.conf and replace "1809000" to whatever frequency you want to target.
Code:
adb push thermald.conf /data/local
adb shell
su
mount -o rw,remount /system
cp /system/etc/thermald.conf /system/etc/thermald.conf.bak
rm -r /system/etc/thermald.conf
cp /data/local/thermald.conf /system/etc
reboot
Load the overclock (every time you reboot):
1. Load the kernel module (replace pll_l_val and vdd_uv with your desired voltages and L value as explained above. It defaults to 67 and 1300000 if you don't give it any parameters):
Code:
adb shell
su
insmod /data/local/krait_oc.ko pll_l_val=67 vdd_uv=1300000
2. Bring core 1 temporarily offline so it gets updated with the new max frequency:
Code:
echo 0 > /sys/devices/system/cpu/cpu1/online
3. You'll now have an additional CPU frequency! SetCPU can configure your maximum frequency up to this speed. You can also choose to keep running at 1.5GHz at any time - this method doesn't eliminate any available frequencies. Set the max at 1.8GHz to verify it's stable here.
4. Restart thermald by running "ps". Look for "thermald" in the list, and find thermald's pid (it's usually a number in the low hundreds, higher up in the list). Run "kill [thermald's PID]" in adb shell. The kernel does not currently have kernel-level temperature throttling turned on, so thermald is important for now.
Remove the overclock by restoring your backup of thermald.conf:
Code:
adb shell
su
mount -o rw,remount /system
rm -r /system/etc/thermald.conf
cp /system/etc/thermald.conf.bak /system/etc/thermald.conf
rm -r /system/etc/thermald.conf.bak
reboot
Rebooting clears any kernel modules that are loaded, so you're now clean. You can then delete anything left over in /data/local, but it doesn't matter.
If the module loads but the overclock doesn't seem to have any effect, even after putting max and min at 1.8GHz, your device might use a different SoC bin than the "nominal," and the kernel module is looking at the wrong place. Please reboot your device and post an adb shell dmesg right after the reboot so I can look at it.
Download current pack of modules:
http://www.setcpu.com/files/krait_oc_v2.zip (current)
http://www.setcpu.com/files/krait_oc.zip (old)
Finally, it'd be great if we as a community tried to work harder to encourage HTC to hurry up and 1. Release kernel source on time, all the time and 2. NOT cave into carrier pressure and stick to their written bootloader policy! S-OFF would be nice, too.

Thanks for sharing! Hard!

can we not use both cores with your mod?
ignore my ignorance it comes online fine

Sorry for being a noob but I don't understand how to do step 4 for restarting the thermald?
As it currently stands the OC works but as soon as I restart the phone, the overclock goes away.

Doesn't it say that you have to re-load the Overclock everytime your reboot ? (Post #1)

My bad, I thought those steps meant that the overlock will load everytime the phone reboots.

Confirmation
Hey, just wanted to confirm that this overclock is working for RUU_Evita_UL_Cingular_US_1.82.502.3 (version 3.0.8-01150-g31e8587) on the AT&T HTC One X. Also, thanks so much for the mod!

Zarboz said:
can we not use both cores with your mod?
ignore my ignorance it comes online fine
Click to expand...
Click to collapse
Yeah, you just have to bring core 1 temporarily offline. The overclock fully works with both cores.
jojojohnson7410 said:
Hey, just wanted to confirm that this overclock is working for RUU_Evita_UL_Cingular_US_1.82.502.3 (version 3.0.8-01150-g31e8587) on the AT&T HTC One X. Also, thanks so much for the mod!
Click to expand...
Click to collapse
Thanks for confirming this! I wasn't sure because I compiled it so that it works on my Rogers ROM, and some symbol versions might have differed. Guess not. Modversions is turned on in this kernel (yay), so there's no need to compile a different module for every kernel version.
gtung99 said:
My bad, I thought those steps meant that the overlock will load everytime the phone reboots.
Click to expand...
Click to collapse
Nope, but a script to do it automatically upon every reboot should be very trivial to write. I might leave that to the ROM devs though.
gtung99 said:
Sorry for being a noob but I don't understand how to do step 4 for restarting the thermald?
Click to expand...
Click to collapse
"adb shell ps" gives a list of the running processes on the system in rows. Find thermald's row (if you are on Linux or Mac OS X you can just do an "adb shell ps | grep thermald" to find the row quickly), and make a note of the first number - this is the PID. Now do "adb shell", "su", and then "kill [thermald's PID]". thermald will now be restarted automatically and will be aware of the overclocked speed. I want to find a way to enable kernel-level temperature throttling so we can disable thermald, as it's not very good.

"If the module loads but the overclock doesn't seem to have any effect, even after putting max and min at 1.8GHz, your device might use a different SoC bin than the "nominal," and the kernel module is looking at the wrong place. Please reboot your device and post an adb shell dmesg right after the reboot so I can look at it.
"
Looks like this is happening to me. Here is my dmesg:
<6>[ 35.453074] [FD92][PID=530][wake_unlock][sys]
<6>[ 35.453197] [FD93][PID=530][state][sys]
<6>[ 35.453288] [FD94][PID=437][SettingsProvider.apk][system]
<6>[ 35.453349] [FD95][PID=437][SettingsProvider.apk][system]
<6>[ 35.453471] [FD96][PID=524][][pipe:]
<6>[ 35.453532] [FD97][PID=524][][pipe:]
<6>[ 35.453654] [FD98][PID=524][[eventpoll]][anon_inode:]
<6>[ 35.453715] [FD99][PID=530][[eventpoll]][anon_inode:]
<6>[ 35.453776] [FD100][PID=530][inotify][anon_inode:]
<6>[ 35.453898] [FD101][PID=530][][pipe:]
<6>[ 35.453960] [FD102][PID=530][][pipe:]
<6>[ 35.454082] [FD103][PID=530][][pipe:]
<6>[ 35.454143] [FD104][PID=530][][pipe:]
<6>[ 35.454204] [FD105][PID=530][[eventpoll]][anon_inode:]
<6>[ 35.454326] [FD106][PID=531][][pipe:]
<6>[ 35.454387] [FD107][PID=531][][pipe:]
<6>[ 35.454448] [FD108][PID=531][[eventpoll]][anon_inode:]
<6>[ 35.454570] [FD109][PID=534][][pipe:]
<6>[ 35.454631] [FD110][PID=533][ashmem][dev]
<6>[ 35.454692] [FD111][PID=533][ashmem][dev]
<6>[ 35.454814] [FD112][PID=534][][pipe:]
<6>[ 35.454906] [FD113][PID=534][[eventpoll]][anon_inode:]
<6>[ 35.454967] [FD114][PID=531][ashmem][dev]
<6>[ 35.455028] [FD115][PID=561][][pipe:]
<6>[ 35.455089] [FD116][PID=536][event6][dev]
<6>[ 35.455211] [FD117][PID=437][][socket:]
<6>[ 35.455302] [FD118][PID=537][][pipe:]
<6>[ 35.455363] [FD119][PID=537][][pipe:]
<6>[ 35.455424] [FD120][PID=537][[eventpoll]][anon_inode:]
<6>[ 35.455486] [FD121][PID=538][][pipe:]
<6>[ 35.455547] [FD122][PID=538][][pipe:]
<6>[ 35.455669] [FD123][PID=538][[eventpoll]][anon_inode:]
<6>[ 35.455730] [FD124][PID=539][][pipe:]
<6>[ 35.455821] [FD125][PID=539][][pipe:]
<6>[ 35.455943] [FD126][PID=539][[eventpoll]][anon_inode:]
<6>[ 35.456004] [FD127][PID=543][][pipe:]
<6>[ 35.456065] [FD128][PID=543][][pipe:]
<6>[ 35.456188] [FD129][PID=543][[eventpoll]][anon_inode:]
<6>[ 35.456249] [FD130][PID=564][][pipe:]
<6>[ 35.456371] [FD131][PID=533][ashmem][dev]
<6>[ 35.456432] [FD132][PID=564][][pipe:]
<6>[ 35.456493] [FD133][PID=565][][pipe:]
<6>[ 35.456615] [FD134][PID=536][event3][dev]
<6>[ 35.456706] [FD135][PID=536][event2][dev]
<6>[ 35.456767] [FD136][PID=533][ashmem][dev]
<6>[ 35.456889] [FD137][PID=564][[eventpoll]][anon_inode:]
<6>[ 35.456951] [FD138][PID=536][event1][dev]
<6>[ 35.457012] [FD139][PID=536][event0][dev]
<6>[ 35.457164] [FD140][PID=536][event8][dev]
<6>[ 35.457225] [FD141][PID=536][event7][dev]
<6>[ 35.457286] [FD142][PID=561][][pipe:]
<6>[ 35.457408] [FD143][PID=561][[eventpoll]][anon_inode:]
<6>[ 35.457469] [FD144][PID=560][][socket:]
<6>[ 35.457591] [FD145][PID=562][][pipe:]
<6>[ 35.457652] [FD146][PID=562][][pipe:]
<6>[ 35.457714] [FD147][PID=562][[eventpoll]][anon_inode:]
<6>[ 35.457836] [FD148][PID=563][][pipe:]
<6>[ 35.457897] [FD149][PID=563][][pipe:]
<6>[ 35.457988] [FD150][PID=563][[eventpoll]][anon_inode:]
<6>[ 35.458110] [FD151][PID=565][][pipe:]
<6>[ 35.458171] [FD152][PID=565][[eventpoll]][anon_inode:]
<6>[ 35.458293] [FD153][PID=437][Infinite.apk][system]
<6>[ 35.458354] [FD154][PID=566][][pipe:]
<6>[ 35.458415] [FD155][PID=566][][pipe:]
<6>[ 35.458538] [FD156][PID=566][[eventpoll]][anon_inode:]
<6>[ 35.458599] [FD157][PID=567][][pipe:]
<6>[ 35.458660] [FD158][PID=567][][pipe:]
<6>[ 35.458782] [FD159][PID=567][[eventpoll]][anon_inode:]
<6>[ 35.458843] [FD160][PID=568][][pipe:]
<6>[ 35.458904] [FD161][PID=568][][pipe:]
<6>[ 35.459026] [FD162][PID=568][[eventpoll]][anon_inode:]
<6>[ 35.459117] [FD163][PID=569][][pipe:]
<6>[ 35.459240] [FD164][PID=569][][pipe:]
<6>[ 35.459301] [FD165][PID=569][[eventpoll]][anon_inode:]
<6>[ 35.459362] [FD166][PID=570][][pipe:]
<6>[ 35.459484] [FD167][PID=570][][pipe:]
<6>[ 35.459575] [FD168][PID=570][[eventpoll]][anon_inode:]
<6>[ 35.459636] [FD169][PID=573][][pipe:]
<6>[ 35.459758] [FD170][PID=573][][pipe:]
<6>[ 35.459819] [FD171][PID=573][[eventpoll]][anon_inode:]
<6>[ 35.459942] [FD172][PID=579][][pipe:]
<6>[ 35.460003] [FD173][PID=577][][pipe:]
<6>[ 35.460064] [FD174][PID=577][][pipe:]
<6>[ 35.460125] [FD175][PID=577][[eventpoll]][anon_inode:]
<6>[ 35.460247] [FD176][PID=575][][socket:]
<6>[ 35.460308] [FD177][PID=579][][pipe:]
<6>[ 35.460430] [FD178][PID=579][[eventpoll]][anon_inode:]
<6>[ 35.460491] [FD179][PID=580][][pipe:]
<6>[ 35.460582] [FD180][PID=580][][pipe:]
<6>[ 35.460674] [FD181][PID=580][[eventpoll]][anon_inode:]
<6>[ 35.460766] [FD182][PID=437][userbehavior.db][data]
<6>[ 35.460857] [FD183][PID=437][ashmem][dev]
<6>[ 35.460949] [FD184][PID=607][][socket:]
<6>[ 35.461010] [FD185][PID=607][][socket:]
<6>[ 35.461132] [FD186][PID=607][][socket:]
<6>[ 35.461193] [FD187][PID=607][][socket:]
<6>[ 35.461254] [FD188][PID=608][][pipe:]
<6>[ 35.461376] [FD189][PID=608][][pipe:]
<6>[ 35.461437] [FD190][PID=608][[eventpoll]][anon_inode:]
<6>[ 35.461498] [FD191][PID=543][][socket:]
<6>[ 35.461620] [FD192][PID=543][][socket:]
<6>[ 35.461681] [FD193][PID=610][][pipe:]
<6>[ 35.461742] [FD194][PID=610][][pipe:]
<6>[ 35.461864] [FD195][PID=610][[eventpoll]][anon_inode:]
<6>[ 35.461925] [FD196][PID=611][][pipe:]
<6>[ 35.462017] [FD197][PID=611][][pipe:]
<6>[ 35.462108] [FD198][PID=611][[eventpoll]][anon_inode:]
<6>[ 35.462200] [FD199][PID=613][][pipe:]
<6>[ 35.462322] [FD200][PID=617][ashmem][dev]
<6>[ 35.462383] [FD201][PID=613][][pipe:]
<6>[ 35.462444] [FD202][PID=613][[eventpoll]][anon_inode:]
<6>[ 35.462566] [FD203][PID=437][lightsensor][dev]
<6>[ 35.462627] [FD204][PID=614][][pipe:]
<6>[ 35.462688] [FD205][PID=614][][pipe:]
<6>[ 35.462810] [FD206][PID=614][][pipe:]
<6>[ 35.462871] [FD207][PID=614][][pipe:]
<6>[ 35.462933] [FD208][PID=614][[eventpoll]][anon_inode:]
<6>[ 35.463055] [FD209][PID=531][ashmem][dev]
<6>[ 35.463116] [FD210][PID=531][ashmem][dev]
<6>[ 35.463177] [FD211][PID=531][][pipe:]
<6>[ 35.463299] [FD212][PID=531][][pipe:]
<6>[ 35.463390] [FD213][PID=531][][pipe:]
<6>[ 35.463451] [FD214][PID=531][][pipe:]
<6>[ 35.463573] [FD215][PID=531][HtcLockScreen.apk][system]
<6>[ 35.463634] [FD216][PID=531][HtcLockScreen.apk][system]
<6>[ 35.463757] [FD217][PID=531][HtcLockScreen.apk][system]
<6>[ 35.463818] [FD218][PID=615][][pipe:]
<6>[ 35.463879] [FD219][PID=615][][pipe:]
<6>[ 35.464001] [FD220][PID=615][[eventpoll]][anon_inode:]
<6>[ 35.464062] [FD221][PID=616][][pipe:]
<6>[ 35.464184] [FD222][PID=616][][pipe:]
<6>[ 35.464245] [FD223][PID=616][[eventpoll]][anon_inode:]
<6>[ 35.464306] [FD224][PID=437][GoogleBackupTransport.apk][system]
<6>[ 35.464459] [FD225][PID=437][][socket:]
<6>[ 35.464520] [FD226][PID=701][ashmem][dev]
<6>[ 35.464642] [FD227][PID=617][ashmem][dev]
<6>[ 35.464703] [FD228][PID=531][ion_share_fd][anon_inode:]
<6>[ 35.464764] [FD229][PID=531][genlock][anon_inode:]
<6>[ 35.464886] [FD230][PID=531][ion][dev]
<6>[ 35.464947] [FD231][PID=531][genlock][dev]
<6>[ 35.465008] [FD232][PID=617][ashmem][dev]
<6>[ 35.465130] [FD233][PID=885][][pipe:]
<6>[ 35.465191] [FD234][PID=429][][pipe:]
<6>[ 35.465283] [FD235][PID=429][][pipe:]
<6>[ 35.465374] [FD236][PID=617][ashmem][dev]
<6>[ 35.465466] [FD237][PID=806][][pipe:]
<6>[ 35.465527] [FD238][PID=806][][pipe:]
<6>[ 35.465649] [FD239][PID=885][][pipe:]
<6>[ 35.465710] [FD240][PID=885][[eventpoll]][anon_inode:]
<6>[ 35.465832] [FD241][PID=617][ashmem][dev]
<6>[ 35.465893] [FD242][PID=418][][pipe:]
<6>[ 35.465954] [FD243][PID=418][][pipe:]
<6>[ 35.466076] [FD244][PID=531][ion_share_fd][anon_inode:]
<6>[ 35.466137] [FD245][PID=531][genlock][anon_inode:]
<6>[ 35.466229] [FD246][PID=531][genlock][dev]
<6>[ 35.466351] [FD247][PID=418][Browser.apk][system]
<6>[ 35.466412] [FD248][PID=429][][pipe:]
<6>[ 35.466534] [FD249][PID=429][][pipe:]
<6>[ 35.466595] [FD250][PID=418][Calendar.apk][system]
<6>[ 35.466656] [FD251][PID=429][][pipe:]
<6>[ 35.466778] [FD252][PID=701][][pipe:]
<6>[ 35.466870] [FD253][PID=701][][pipe:]
<6>[ 35.466931] [FD254][PID=701][[eventpoll]][anon_inode:]
<6>[ 35.467053] [FD255][PID=701][][socket:]
<6>[ 35.467144] [FD256][PID=705][][pipe:]
<6>[ 35.467205] [FD257][PID=705][][pipe:]
<6>[ 35.467327] [FD258][PID=705][[eventpoll]][anon_inode:]
<6>[ 35.467419] [FD259][PID=701][][socket:]
<6>[ 35.467480] [FD260][PID=706][][pipe:]
<6>[ 35.467602] [FD261][PID=706][][pipe:]
<6>[ 35.467663] [FD262][PID=706][[eventpoll]][anon_inode:]
<6>[ 35.467785] [FD263][PID=704][][pipe:]
<6>[ 35.467846] [FD264][PID=704][][pipe:]
<6>[ 35.467907] [FD265][PID=704][[eventpoll]][anon_inode:]
<6>[ 35.468029] [FD266][PID=701][][pipe:]
<6>[ 35.468090] [FD267][PID=701][][pipe:]
<6>[ 35.468151] [FD268][PID=701][diag][dev]
<6>[ 35.468274] [FD269][PID=437][settings.db-wal][data]
<6>[ 35.468335] [FD270][PID=437][databases][data]
<6>[ 35.468426] [FD271][PID=784][][pipe:]
<6>[ 35.468518] [FD272][PID=437][htcCheckin.db][data]
<6>[ 35.468609] [FD273][PID=784][][pipe:]
<6>[ 35.468670] [FD274][PID=784][[eventpoll]][anon_inode:]
<6>[ 35.468792] [FD275][PID=429][][pipe:]
<6>[ 35.468853] [FD276][PID=418][HtcContacts+CRC_VIE_EVA_ENR_PRO_S40.apk][syst
em]
<6>[ 35.468976] [FD277][PID=437][GoogleBackupTransport.apk][system]
<6>[ 35.469037] [FD278][PID=437][GoogleBackupTransport.apk][system]
<6>[ 35.469159] [FD279][PID=418][HtcMusic.apk][system]
<6>[ 35.469220] [FD280][PID=418][HtcNotes.apk][system]
<6>[ 35.469342] [FD281][PID=418][Mail.apk][system]
<6>[ 35.469403] [FD282][PID=418][Message+CRC_1.apk][system]
<6>[ 35.469525] [FD283][PID=418][Music2.apk][system]
<6>[ 35.469586] [FD284][PID=418][PDF_Viewer_F_A.apk][system]
<6>[ 35.469647] [FD285][PID=418][PureC_ApplicationsProvider.apk][system]
<6>[ 35.469769] [FD286][PID=418][Settings.apk][system]
<6>[ 35.469830] [FD287][PID=418][Twitter.apk][system]
<6>[ 35.469952] [FD288][PID=418][VoiceSearch.apk][system]
<6>[ 35.470044] [FD289][PID=418][Watch.apk][system]
<6>[ 35.470135] [FD290][PID=418][YouTube.apk][system]
<6>[ 35.470227] [FD291][PID=418][com.android.vending-1.apk][data]
<6>[ 35.470349] [FD292][PID=418][com.google.android.apps.maps-1.apk][data]
<6>[ 35.470410] [FD293][PID=418][com.google.android.gm-1.apk][data]
<6>[ 35.470532] [FD294][PID=418][com.google.android.videos-1.apk][data]
<6>[ 35.470593] [FD295][PID=418][com.google.android.apps.books-1.apk][data]
<6>[ 35.470715] [FD296][PID=418][com.yellowpages.android.ypmobile-1.apk][data]
<6>[ 35.470837] [FD297][PID=418][com.twitter.android-1.apk][data]
<6>[ 35.470898] [FD298][PID=418][com.quoord.tapatalkxda.activity-1.apk][data]
<6>[ 35.471020] [FD299][PID=418][net.zedge.android-1.apk][data]
<6>[ 35.471081] [FD300][PID=418][com.handcent.nextsms-1.apk][data]
<6>[ 35.530352] [FD] 301 files print end
<6>[ 36.954768] genlock: genlock_release_lock: Releasing a handle that still h
olds lock (2)
<6>[ 36.955012] mdp4_overlay_pipe_free: pipe=c0c81828 ndx=2 stage 4 mixer 0
<6>[ 36.955898] genlock: genlock_release_lock: Releasing a handle that still h
olds lock (2)
<4>[ 36.963467] mdp4_overlay_update_layers: unstaging pipe ndx=2
<4>[ 36.963558] mdp4_overlay_update_layers: mask=0000F000 new layermixer_cfg=0
0000132
<6>[ 37.272943] msm_etb msm_etb.0: etb disabled
<6>[ 37.273035] msm_tpiu msm_tpiu.0: tpiu disabled
<6>[ 37.276148] msm_etb msm_etb.0: etb enabled
<6>[ 37.276239] msm_funnel msm_funnel.0: funnel port mask 0x3 enabled
<4>[ 37.276545] ------------[ cut here ]------------
<4>[ 37.276636] WARNING: at /home/aa/Project/Evita_ATT_WWE_ICS_CRC_Stable_2549
31/kernel/arch/arm/mach-msm/qdss-ptm.c:250 ptm_trace_enable+0x3b8/0x450()
<4>[ 37.276758] timeout while clearing prog bit
<4>[ 37.276880] Modules linked in: prima_wlan(P)
<4>[ 37.277094] [<c010c744>] (unwind_backtrace+0x0/0x12c) from [<c0179aec>] (w
arn_slowpath_common+0x4c/0x64)
<4>[ 37.277247] [<c0179aec>] (warn_slowpath_common+0x4c/0x64) from [<c0179b84>
] (warn_slowpath_fmt+0x2c/0x3c)
<4>[ 37.277674] [<c0179b84>] (warn_slowpath_fmt+0x2c/0x3c) from [<c011ba54>] (
ptm_trace_enable+0x3b8/0x450)
<4>[ 37.277826] [<c011ba54>] (ptm_trace_enable+0x3b8/0x450) from [<c011bdb8>]
(ptm_write+0x180/0x418)
<4>[ 37.277887] [<c011bdb8>] (ptm_write+0x180/0x418) from [<c021dbb4>] (vfs_wr
ite+0xac/0x134)
<4>[ 37.278040] [<c021dbb4>] (vfs_write+0xac/0x134) from [<c021dce8>] (sys_wri
te+0x3c/0x68)
<4>[ 37.278162] [<c021dce8>] (sys_write+0x3c/0x68) from [<c0105e60>] (ret_fast
_syscall+0x0/0x30)
<4>[ 37.278284] ---[ end trace 3e69383386a66a84 ]---
<4>[ 37.278528] ------------[ cut here ]------------
<4>[ 37.278620] WARNING: at /home/aa/Project/Evita_ATT_WWE_ICS_CRC_Stable_2549
31/kernel/arch/arm/mach-msm/qdss-ptm.c:250 ptm_trace_enable+0x3b8/0x450()
<4>[ 37.278773] timeout while clearing prog bit
<4>[ 37.278834] Modules linked in: prima_wlan(P)
<4>[ 37.279047] [<c010c744>] (unwind_backtrace+0x0/0x12c) from [<c0179aec>] (w
arn_slowpath_common+0x4c/0x64)
<4>[ 37.279261] [<c0179aec>] (warn_slowpath_common+0x4c/0x64) from [<c0179b84>
] (warn_slowpath_fmt+0x2c/0x3c)
<4>[ 37.279383] [<c0179b84>] (warn_slowpath_fmt+0x2c/0x3c) from [<c011ba54>] (
ptm_trace_enable+0x3b8/0x450)
<4>[ 37.279505] [<c011ba54>] (ptm_trace_enable+0x3b8/0x450) from [<c011bdb8>]
(ptm_write+0x180/0x418)
<4>[ 37.279627] [<c011bdb8>] (ptm_write+0x180/0x418) from [<c021dbb4>] (vfs_wr
ite+0xac/0x134)
<4>[ 37.279719] [<c021dbb4>] (vfs_write+0xac/0x134) from [<c021dce8>] (sys_wri
te+0x3c/0x68)
<4>[ 37.279841] [<c021dce8>] (sys_write+0x3c/0x68) from [<c0105e60>] (ret_fast
_syscall+0x0/0x30)
<4>[ 37.279963] ---[ end trace 3e69383386a66a85 ]---
<6>[ 37.280054] msm_ptm msm_ptm.0: tracing enabled
<6>[ 37.291255] msm_etb msm_etb.0: etb dumped
<6>[ 37.291316] msm_etb msm_etb.0: etb disabled
<6>[ 37.295406] msm_funnel msm_funnel.0: funnel port mask 0x3 disabled
<6>[ 37.298489] msm_ptm msm_ptm.0: tracing disabled
<6>[ 37.341614] [PM] CPU1: msm_pm_power_collapse: change clock rate (old rate
= 0)
<6>[ 37.343293] mdp4_overlay_req2pipe: pipe=c0c81828 ndx=2 num=1 zorder=4 mixe
r 0 format = 9
<3>[ 37.707187] l2cap_sock_connect: failed -115
<6>[ 38.011353] [WLAN] Set country code: US
<6>[ 38.071356] mdp4_overlay_pipe_free: pipe=c0c81a40 ndx=3 stage 2 mixer 0
<6>[ 38.071600] mdp4_overlay_pipe_free: pipe=c0c81c58 ndx=4 stage 3 mixer 0
<6>[ 38.071753] mdp4_overlay_pipe_free: pipe=c0c81828 ndx=2 stage 4 mixer 0
<4>[ 38.072028] mdp4_overlay_update_layers: unstaging pipe ndx=3
<4>[ 38.072028] mdp4_overlay_update_layers: unstaging pipe ndx=4
<4>[ 38.072028] mdp4_overlay_update_layers: unstaging pipe ndx=2
<4>[ 38.072058] mdp4_overlay_update_layers: mask=0000F0FF new layermixer_cfg=0
0000100
<6>[ 38.873920] mdp4_overlay_req2pipe: pipe=c0c81a40 ndx=3 num=2 zorder=2 mixe
r 0 format = 9
<6>[ 38.885609] mdp4_overlay_req2pipe: pipe=c0c81c58 ndx=4 num=3 zorder=3 mixe
r 0 format = 9
<6>[ 38.888600] mdp4_overlay_req2pipe: pipe=c0c81828 ndx=2 num=1 zorder=4 mixe
r 0 format = 9
<3>[ 39.689516] qtaguid: iface_stat: stat_update() rmnet0 not found
<3>[ 39.693148] qtaguid: iface_stat: stat_update() rmnet0 not found
<6>[ 41.600793] call alarm, type 2, func alarm_triggered+0x0/0xa0, 41568000000
(s 41568000000)
<7>[ 42.714695] wlan0: no IPv6 routers present
<6>[ 43.281794] call alarm, type 2, func alarm_triggered+0x0/0xa0, 43249000000
(s 43249000000)
<3>[ 43.849412] l2cap_sock_connect: failed -115
<3>[ 49.018159] l2cap_sock_connect: failed -115
<6>[ 49.228933] call alarm, type 3, func alarm_triggered+0x0/0xa0, 0 (s 0)
[email protected]:/ $
---------- Post added at 06:47 PM ---------- Previous post was at 06:46 PM ----------
BTW.....Thanks for all the hard work

Didn't work on my Rogers XL unfortunately. I noticed my directory structure is a little different than in the instructions. Your adb instructions say:
Code:
echo 0 > /sys/devices/system/cpu/cpu1/cpufreq/online
Following that path with a file explorer I discovered my device has no cpufreq directory. The file "online" is in the cpu1 folder itself.
SetCPU shows 1809 MHz as selectable but does not show any changes in clock speed when selected as both min and max. Can't see any difference in speed.
Dmesg log is attached. Help would be appreciated! Thanks!

Oh ya, love this guy. Had this same type of thing for the 3d. Thanks op.
Sent from my SPH-D710 using Xparent ICS Blue Tapatalk 2

MatinatorX said:
Didn't work on my Rogers XL unfortunately. I noticed my directory structure is a little different than in the instructions. Your adb instructions say:
Code:
echo 0 > /sys/devices/system/cpu/cpu1/cpufreq/online
Following that path with a file explorer I discovered my device has no cpufreq directory. The file "online" is in the cpu1 folder itself.
SetCPU shows 1809 MHz as selectable but does not show any changes in clock speed when selected as both min and max. Can't see any difference in speed.
Dmesg log is attached. Help would be appreciated! Thanks!
Click to expand...
Click to collapse
Yeah, I made a mistake in regards to the directory structure. My mistake - I edited the post to reflect the correct directory that online is in.
Your attached log seems to be taken too late in the boot up process. You have to take it immediately after boot up or else it won't catch the crucial line solidus175 too. The line should look similar to:
[ACPU] select_freq_plan: ACPU PVS: Nominal
Where Nominal can be Nominal, Fast, or Slow.
EDIT: You know what, I can just change all three tables. That shouldn't hurt anything. Will release an updated version of the module.

coolbho3000 said:
Yeah, I made a mistake in regards to the directory structure. My mistake - I edited the post to reflect the correct directory that online is in.
Your attached log seems to be taken too late in the boot up process. You have to take it immediately after boot up or else it won't catch the crucial line solidus175 too. The line should look similar to:
[ACPU] select_freq_plan: ACPU PVS: Nominal
Where Nominal can be Nominal, Fast, or Slow.
EDIT: You know what, I can just change all three tables. That shouldn't hurt anything. Will release an updated version of the module.
Click to expand...
Click to collapse
Cool....Will wait for update. THANKS!

solidus175 said:
Cool....Will wait for update. THANKS!
Click to expand...
Click to collapse
Released a new version of the kernel in the topic post: http://www.setcpu.com/files/krait_oc_v2.zip. Let me know how it works out. If it doesn't, this version now has more debug logging, so a dmesg log right after you load the module is very helpful.

coolbho3000 said:
Released a new version of the kernel in the topic post: http://www.setcpu.com/files/krait_oc_v2.zip. Let me know how it works out. If it doesn't, this version now has more debug logging, so a dmesg log right after you load the module is very helpful.
Click to expand...
Click to collapse
Worked like a charm! Many THANKS!

Worked awesome! Thank you very much. I created a script for ScriptManager with a homescreen shortcut to make things easier each boot. Overclocking does indeed feel significant, noticing a healthy boost in N64oid.
Edit: After about a half hour of gaming my XL is pretty toasty. Hoping the casing doesn't take on a different hue

Is there anyway to have the module load automatically when the device boots? Like a modules.conf
Sent from my HTC One X using XDA

MatinatorX said:
Worked awesome! Thank you very much. I created a script for ScriptManager with a homescreen shortcut to make things easier each boot. Overclocking does indeed feel significant, noticing a healthy boost in N64oid.
Edit: After about a half hour of gaming my XL is pretty toasty. Hoping the casing doesn't take on a different hue
Click to expand...
Click to collapse
What was the temp?
Sent from my HTC One X using XDA

blacklistedcard said:
Is there anyway to have the module load automatically when the device boots? Like a modules.conf
Click to expand...
Click to collapse
You can write a script and set it to run on boot with scriptmanager.
I'll do another test when I get home from work to verify the temperature. Not enough battery left right now.

Do u have to use the perflock disabler because setcpu shows 1.8 but CPU spy only shows up to 1.5.
Sent from my HTC One X using Xparent ICS Blue Tapatalk 2

[Q] Random restarts

My sensation keeps restarting randomly.
I've tried:
- Reflashing firmware 3.33, 3.32
- Other roms: Miui v4, cm10, cm9, Darksense, ARDHD, stock, gingerbread cm7.
- New battery
- Battery card trick
Sometimes it turns off completely and I can't turn it back on without pulling the battery out and putting it back in.

Moon2 said:
My sensation keeps restarting randomly.
I've tried:
- Reflashing firmware 3.33, 3.32
- Other roms: Miui v4, cm10, cm9, Darksense, ARDHD, stock, gingerbread cm7.
- New battery
- Battery card trick
Sometimes it turns off completely and I can't turn it back on without pulling the battery out and putting it back in.
Click to expand...
Click to collapse
I need more information, so I ask you do these things.
OK. First:
Code:
adb shell
dmesg > /sdcard/DMESG.txt
Attach the DMESG.txt file from your SDCard.
Code:
adb logcat > Logcat.txt
Wait for phone to randomly restart (sorry) and attach the logcat file.
Secondly:
Current HBOOT version? Kernel if flashing manually?

DennisBold said:
I need more information, so I ask you do these things.
OK. First:
Code:
adb shell
dmesg > /sdcard/DMESG.txt
Attach the DMESG.txt file from your SDCard.
Code:
adb logcat > Logcat.txt
Wait for phone to randomly restart (sorry) and attach the logcat file.
Secondly:
Current HBOOT version? Kernel if flashing manually?
Click to expand...
Click to collapse
I'd previously logged the logcat twice before it restarted and also have a last_kmsg of when it happened. It doesn't seem to reboot when I'm in recovery.
HBoot: 1.29.0000, S-off
Kernel: Stock, faux, sebastian (happens on all of them)

I'm having the same problem with my sensation with alternative battery!!! Please help!!!

It just happened again and I've got another logcat, I'll try and do the dmesg now.
I've tried letting the phone sleep without wifi/3g, taking sd card out, formatting it.

Moon2 said:
I'd previously logged the logcat twice before it restarted and also have a last_kmsg of when it happened. It doesn't seem to reboot when I'm in recovery.
HBoot: 1.29.0000, S-off
Kernel: Stock, faux, sebastian (happens on all of them)
Click to expand...
Click to collapse
I thought the pyramid had Adreno 220?
Code:
D/libEGL ( 1113): loaded /system/lib/egl/libGLESv2_adreno200.so
What ROM do you currently have installed?

DennisBold said:
I thought the pyramid had Adreno 220?
Code:
D/libEGL ( 1113): loaded /system/lib/egl/libGLESv2_adreno200.so
What ROM do you currently have installed?
Click to expand...
Click to collapse
Miui v4
I've seen that library used on different phones with adreno on them, I don't think the 200 has a bearing on the type found on the phone.

Moon2 said:
Miui v4
Click to expand...
Click to collapse
Is your GPS enabled, and does this happen when your GPS is disabled?
Moon2 said:
Miui v4
I've seen that library used on different phones with adreno on them, I don't think the 200 has a bearing on the type found on the phone.
Click to expand...
Click to collapse
Never really looked at that, well, the only thing I can connect it with is GPS.

DennisBold said:
Is your GPS enabled, and does this happen when your GPS is disabled?
Click to expand...
Click to collapse
I've tried it with wifi, 3g, bluetooth, gps, auto-sync all turned off and it still happens.

Moon2 said:
I've tried it with wifi, 3g, bluetooth, gps, auto-sync all turned off and it still happens.
Click to expand...
Click to collapse
(From First Logcat)
Code:
D/GpsLocationProvider( 241): [handleMessage] message :7
D/GpsLocationProvider( 241): [handleMessage] UPDATE_LOCATION
D/GpsLocationProvider( 241): handleUpdateLocation
D/lib_locapi( 241): loc_eng_inject_location, accuracy = 48.0
(Second Logcat)
Code:
D/GpsLocationProvider( 242): [handleMessage] message :7
D/GpsLocationProvider( 242): [handleMessage] UPDATE_LOCATION
D/GpsLocationProvider( 242): handleUpdateLocation
D/lib_locapi( 242): loc_eng_inject_location, accuracy = 52.0
Logcat ends a minute not long after that.
On a side note, do you have AdFree installed?

DennisBold said:
(From First Logcat)
Code:
D/GpsLocationProvider( 241): [handleMessage] message :7
D/GpsLocationProvider( 241): [handleMessage] UPDATE_LOCATION
D/GpsLocationProvider( 241): handleUpdateLocation
D/lib_locapi( 241): loc_eng_inject_location, accuracy = 48.0
(Second Logcat)
Code:
D/GpsLocationProvider( 242): [handleMessage] message :7
D/GpsLocationProvider( 242): [handleMessage] UPDATE_LOCATION
D/GpsLocationProvider( 242): handleUpdateLocation
D/lib_locapi( 242): loc_eng_inject_location, accuracy = 52.0
Logcat ends a minute not long after that.
On a side note, do you have AdFree installed?
Click to expand...
Click to collapse
No, I've tried all of the roms with & without adding any apps.

Moon2 said:
No, I've tried all of the roms with & without adding any apps.
Click to expand...
Click to collapse
There's not exactly any errors other than this on dmesg.
Code:
<3>[ 475.735900] init: cannot execve('/system/bin/DxDrmServerIpc'): Permission denied
That isn't really a problem. Neither are these:
Code:
E/MobileDataStateTracker( 242): Error mapping networkType 23 to apnType.
Code:
D/MobileDataStateTracker( 242): internet: mMobileDataState=DISCONNECTED mTeardownRequested=false got [AnyDataCSC] : type=internet state=DISCONNECTED reason=dataDetached apn=null roaming=false unavailable=true NetworkType=0 NetworkTypeName=UNKNOWN entitleError=0 apnCarrier=null

I've just installed cm9 and run the logcat to just before it rebooted.

Moon2 said:
I've just installed cm9 and run the logcat to just before it rebooted.
Click to expand...
Click to collapse
Run Fix Permissions in recovery.
Also, send me another DMESG. Not during/while the phone is crashing.

DennisBold said:
Run Fix Permissions in recovery.
Also, send me another DMESG. Not during/while the phone is crashing.
Click to expand...
Click to collapse
It seems to reboot more frequently on a non-sense rom like cm9/10 than sense based roms like Miui or arhd and I don't think its rebooted or shutdown yet if it's been plugged in to charger/computer.

Moon2 said:
It seems to reboot more frequently on a non-sense rom like cm9/10 than sense based roms like Miui or arhd and I don't think its rebooted or shutdown yet if it's been plugged in to charger/computer.
Click to expand...
Click to collapse
Thanks.
Can you try:
Code:
adb shell
dmesg | grep mmc
And copy and paste the results?
You should see:
Code:
[email protected]:/ # dmesg | grep mmc
dmesg | grep mmc
[email protected]:/ #
---------- Post added at 08:04 PM ---------- Previous post was at 07:33 PM ----------
Could you run?
Code:
cat /sys/class/block/mmcblk0/device/name

Code:
[email protected]:/ $ dmesg | grep mmc
dmesg | grep mmc
1|[email protected]:/ $ cat /sys/class/block/mmcblk0/device/name
cat /sys/class/block/mmcblk0/device/name
MLL00M

Moon2 said:
Code:
[email protected]:/ $ dmesg | grep mmc
dmesg | grep mmc
1|[email protected]:/ $ cat /sys/class/block/mmcblk0/device/name
cat /sys/class/block/mmcblk0/device/name
MLL00M
Click to expand...
Click to collapse
Flash an RUU (preferably Gingerbread) and see if it makes any difference?
Run this from stock and see if you still have errors
Code:
adb shell
dmesg | grep mmc
logcat | grep mmc

DennisBold said:
Flash an RUU (preferably Gingerbread) and see if it makes any difference?
Run this from stock and see if you still have errors
Code:
adb shell
dmesg | grep mmc
logcat | grep mmc
Click to expand...
Click to collapse
Code:
dmesg | grep mmc
Code:
<5>[ 0.000000] Kernel command line: poweron_status=1 board_pyramid.disable_ua
rt3=0 diag.enabled=0 board_pyramid.debug_uart=0 userdata_sel=0 androidboot.emmc=
true androidboot.pagesize=2048 androidboot.baseband=10.14.9035.01_M androidboo
t.cid=11111111 androidboot.batt_poweron=good_battery androidboot.carrier=ALL and
roidboot.mid=PG5813000 androidboot.keycaps=qwerty androidboot.dq=FAIL androidboo
t.mode=normal androidboot.serialno=SH191V463715 androidboot.bootloader=1.17.1111
zygote_oneshot=off msm_watchdog.enable=1 console=ttyHSL0 androidboot.hardware=p
yramid no_console_suspend=1
<6>[ 0.335052] pyramid: pyramid_init_mmc
<6>[ 0.907806] Create /proc/emmc OK.
<3>[ 2.389921] mmc0: No card detect facilities available
<6>[ 2.390287] mmc0: Qualcomm MSM SDCC at 0x0000000012400000 irq 136,0 dma 18
<6>[ 2.390379] mmc0: Platform slot type: MMC
<6>[ 2.390562] mmc0: 8 bit data mode enabled
<6>[ 2.390654] mmc0: 4 bit data mode disabled
<6>[ 2.390745] mmc0: polling status mode disabled
<6>[ 2.390928] mmc0: MMC clock 400000 -> 48000000 Hz, PCLK 0 Hz
<6>[ 2.391020] mmc0: Slot eject status = 0
<6>[ 2.391203] mmc0: Power save feature enable = 1
<6>[ 2.391294] mmc0: DM non-cached buffer at ff007000, dma_addr 0x5751b000
<6>[ 2.391386] mmc0: DM cmd busaddr 0x5751b000, cmdptr busaddr 0x5751b300
<6>[ 2.391966] mmc1: Qualcomm MSM SDCC at 0x0000000012180000 irq 134,654 dma
20
<6>[ 2.392149] mmc1: Platform slot type: SD
<6>[ 2.392240] mmc1: 8 bit data mode disabled
<6>[ 2.392332] mmc1: 4 bit data mode enabled
<6>[ 2.392515] mmc1: polling status mode disabled
<6>[ 2.392607] mmc1: MMC clock 144000 -> 48000000 Hz, PCLK 0 Hz
<6>[ 2.392790] mmc1: Slot eject status = 0
<6>[ 2.392881] mmc1: Power save feature enable = 1
<6>[ 2.392973] mmc1: DM non-cached buffer at ff008000, dma_addr 0x5751c000
<6>[ 2.393156] mmc1: DM cmd busaddr 0x5751c000, cmdptr busaddr 0x5751c300
<6>[ 2.393644] mmc2: Qualcomm MSM SDCC at 0x00000000121c0000 irq 133,0 dma 21
<6>[ 2.393736] mmc2: Platform slot type: N/A
<6>[ 2.393919] mmc2: 8 bit data mode disabled
<6>[ 2.394010] mmc2: 4 bit data mode enabled
<6>[ 2.394102] mmc2: polling status mode disabled
<6>[ 2.394285] mmc2: MMC clock 400000 -> 48000000 Hz, PCLK 0 Hz
<6>[ 2.394377] mmc2: Slot eject status = 1
<6>[ 2.394468] mmc2: Power save feature enable = 1
<6>[ 2.394651] mmc2: DM non-cached buffer at ff009000, dma_addr 0x5751d000
<6>[ 2.394743] mmc2: DM cmd busaddr 0x5751d000, cmdptr busaddr 0x5751d300
<6>[ 2.513761] mmc0: new high speed MMC card at address 0001
<6>[ 2.526975] mmcblk0: mmc0:0001 MLL00M 2.25 GiB
<6>[ 2.527555] mmcblk0: p1 p2 p3 p4 < p5 p6
<6>[ 2.568296] EXT4-fs (mmcblk0p22): INFO: recovery required on readonly file
system
<6>[ 2.568662] EXT4-fs (mmcblk0p22): write access will be enabled during reco
very
<4>[ 2.666654] mmc1: high speed mode max_dtr = 50000000
<4>[ 2.667081] mmc1: host does not support reading read-only switch. assuming
write-enable.
<6>[ 2.667264] mmc1: new high speed SD card at address 1234
<6>[ 2.667753] mmcblk1: mmc1:1234 SA02G 1.83 GiB
<6>[ 2.668149] mmcblk1: p1
<6>[ 2.697813] EXT4-fs (mmcblk0p22): recovery complete
<6>[ 2.705625] EXT4-fs (mmcblk0p22): mounted filesystem with ordered data mod
e. Opts: (null)
<7>[ 3.291562] EXT4-fs (mmcblk0p23): ext4_orphan_cleanup: deleting unreferenc
ed inode 22945
<7>[ 3.292050] EXT4-fs (mmcblk0p23): ext4_orphan_cleanup: deleting unreferenc
ed inode 22946
<6>[ 3.292416] EXT4-fs (mmcblk0p23): 2 orphan inodes deleted
<6>[ 3.292691] EXT4-fs (mmcblk0p23): recovery complete
<6>[ 3.334836] EXT4-fs (mmcblk0p23): mounted filesystem with ordered data mod
e. Opts: nodelalloc
<6>[ 3.389493] EXT4-fs (mmcblk0p24): recovery complete
<6>[ 3.397031] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mod
e. Opts: nodelalloc
<6>[ 3.516964] EXT4-fs (mmcblk0p27): recovery complete
<6>[ 3.521115] EXT4-fs (mmcblk0p27): mounted filesystem with writeback data m
ode. Opts: nodelalloc
<6>[ 20.862468] mmc2: Slot status change detected (0 -> 1)
<7>[ 20.915202] mmc2: queuing CIS tuple 0x91 length 3
<6>[ 20.915446] mmc2: new high speed SDIO card at address 0001
Code:
logcat | grep mmc
I've left it running for a few mins but nothings showing up.

Its still not showing anything, but I'm attaching a logcat on stock gb upto the point it restarted.

porting kernel + drivers

Hi folks,
I'm hoping someone can help me get my head around loading drivers in android.
I'm very familiar with Linux, so I understand drivers compiled into the kernel vs loading modular drivers. I also understand module versions in that they should match the installed kernel.
I have a cyanogenmod ROM that was built for a device similar to mine except that the wifi/bt drivers do not work. I have a ROM where these DO work.
I have extracted the boot.img from each ROM and I'm trying to combine the kernel that works with the cyanogenmod boot.img to get a working device. But the drivers have me a bit stumped.
On the device that works, here is what I see during boot in dmesg:
Code:
<6>[ 2.273829] Bluetooth: HCI UART driver ver 2.2
<6>[ 2.278272] Bluetooth: HCI H4 protocol initialized
<6>[ 2.283084] Bluetooth: HCI BCSP protocol initialized
<6>[ 2.288045] Bluetooth: HCILL protocol initialized
<7>[ 2.292983] [wifi]: Select sdio wifi: bcm40183 !!
<7>[ 2.297878] [mmc_pm]: SDIO card gpio init is OK !!
<7>[ 2.302753] [mmc]: sunximmc_init
<7>[ 2.306208] [mmc]: sunxi mmc controller using config : 0xb
<7>[ 2.311762] [mmc]: sunxi-mmc.0: pdev->name: sunxi-mmc, pdev->id: 0
<7>[ 2.318190] [mmc]: mmc 0 power off !!
<7>[ 2.321978] [mmc]: mmc0 Probe: base:0xe8916000 irq:32 dma:0 pdes:0xe704c000, ret 0.
<7>[ 2.329650] [mmc]: sunxi-mmc.1: pdev->name: sunxi-mmc, pdev->id: 1
<7>[ 2.336069] [mmc]: mmc 1 power off !!
<7>[ 2.339801] [mmc]: mmc1 Probe: base:0xe8918000 irq:33 dma:0 pdes:0xe7050000, ret 0.
<7>[ 2.347496] [mmc]: sunxi-mmc.3: pdev->name: sunxi-mmc, pdev->id: 3
<7>[ 2.353876] [mmc]: mmc 3 power off !!
<7>[ 2.357601] [mmc]: mmc3 Probe: base:0xe891a000 irq:35 dma:0 pdes:0xe7054000, ret 0.
This is below the line that says
Code:
<7>[ 2.081010] insmod_device_driver
So I'm assuming this is a module that is being loaded. I have however compared the init.sun4i.rc on both and made sure I'm loading the same drivers. I'm also loading the kernel from the working ROM.
This is what I see in the broken setup:
Code:
<6>[ 2.261673] Bluetooth: HCI UART driver ver 2.2
<6>[ 2.266116] Bluetooth: HCI H4 protocol initialized
<6>[ 2.270928] Bluetooth: HCI BCSP protocol initialized
<6>[ 2.275891] Bluetooth: HCILL protocol initialized
<7>[ 2.280811] [mmc_pm]: no sdio card used in configuration
<7>[ 2.286118] [mmc]: sunximmc_init
<7>[ 2.289602] [mmc]: sunxi mmc controller using config : 0xb
<7>[ 2.295210] [mmc]: sunxi-mmc.0: pdev->name: sunxi-mmc, pdev->id: 0
<7>[ 2.301688] [mmc]: mmc 0 power off !!
<7>[ 2.305451] [mmc]: mmc0 Probe: base:0xe8916000 irq:32 dma:0 pdes:0xe704c000, ret 0.
<7>[ 2.313150] [mmc]: sunxi-mmc.1: pdev->name: sunxi-mmc, pdev->id: 1
<7>[ 2.319533] [mmc]: mmc 1 power off !!
<7>[ 2.323293] [mmc]: mmc1 Probe: base:0xe8918000 irq:33 dma:0 pdes:0xe7050000, ret 0.
<7>[ 2.330984] [mmc]: sunxi-mmc.3: pdev->name: sunxi-mmc, pdev->id: 3
<7>[ 2.337351] [mmc]: mmc 3 power off !!
<7>[ 2.341106] [mmc]: mmc3 Probe: base:0xe891a000 irq:35 dma:0 pdes:0xe7054000, ret 0.
So this seems to be complaining about no SD card being available - is this a correct assumption?
I also assume this is a card used for storage, and wifi/bt using the SDIO standard.
Would the wifi driver be being loaded from the SD card? If so, where? It may just be something else I need to add to the zip file for the new ROM.
When I compare dmesg between the two, I don't see anything obvious that loads differently, so it's got me stumped as to what's happening.
Can anyone shed some light on how the working ROM might be loading the bcm40183 driver?

in my android tablet I noticed how the /system folder is actually stored in nandd partition, and refered to by the main nand partition via a symlink. Since /system/vendor/modules (where my bcm40183 module is stored) is a symlink path to a location on a nand partition, I assume the OS reaches that location using a mmc device (maybe because it is flash memory after all). So your problem isn't about a missing SD card, but about a missing nand partition...or a broken link. Apparently, from one android version to the next, the number of partitions varies. On mine, there are 9 partitions!
Since you know about modules and versions, do you know how I could get that bcm40183 module working in linux? I can't find a kernel with that module on offer and I dont know how to add modules on already compiled kernels. I'd love to be able to insmod this bcm40183 version 3.0.8 in my sunxi-3.4 kernel...