Jump to content


Photo

Cannot enable Wifi driver , not a network configuration issue

- - - - -

  • Please log in to reply
17 replies to this topic

#1
jthm23

jthm23

    Newbie

  • Members
  • Pip
  • 9 posts
  • Devices:Nexus One
Since I applied the froyo update from Paul's site wifi was working fine for 36 hours.
After a crash caused by copying files on my sdcard I rebooted the phone several times to recover it (another story).

Then wifi stopped working, by "stopped working" I mean the driver won't even load, giving me a warning in logcat, some timeouts in dhd_module_init and "Error" in the control panel.

It has nothing to do with my router configuration because I cannot even enable the wifi to scan for some ssid so it's not a "false alarm" issue...

I tried to flash Stock rom and radio, flash superboot FRF50, the last cyanogen, wipe a few thousand times between all of this but nothing seems to give life back to my wifi chip...

I can't stop thinking it is hardware related but why ??!! There was no shock, no fall, no EMP from a nuke in the vicinity, everything was smooth when I got back from work and bam !
Please, prove me its not hardware related I am ready to beg :rolleyes:

Is there some options to pass to the driver when I insmod to "reset" the chip in a healthy state ?
Can I somehow compile a debug build giving more informations on my hardware when it is crashing like **** ?
I don't know where to look anymore ...

Here are logs from various sources when I enable wifi in the settings (or insmod /system/lib/modules/bcm4239.ko) if it bothers I'll send them to pastebin :


From dmesg

<4>[ 9041.253845] wifi_set_power = 1
<4>[ 9041.253967] mahimahi_wifi_power: 1
<4>[ 9041.629699] wifi_set_carddetect = 1
<6>[ 9041.629821] mahimahi_wifi_set_carddetect: 1
<7>[ 9041.629943] mmc0: card_present 1
<6>[ 9041.630035] mmc0: Slot status change detected (0 -> 1)
<4>[ 9041.631988] 
<4>[ 9041.631988] Dongle Host Driver, version 4.218.223.0
<4>[ 9043.103698] save exit: isCheckpointed 1
<6>[ 9044.857452] batt:  99%, 4133 mV, 0 mA (0 avg), 30.8 C, 1345 mAh
<4>[ 9051.624053] dhd_module_init: sdio_register_driver timeout
<4>[ 9051.629364] wifi_set_carddetect = 0
<6>[ 9051.629730] mahimahi_wifi_set_carddetect: 0
<7>[ 9051.630065] mmc0: card_present 0
<6>[ 9051.630432] mmc0: Slot status change detected (1 -> 0)
<4>[ 9051.632110] wifi_set_power = 0
<4>[ 9051.632446] mahimahi_wifi_power: 0
From logcat
E/WifiService(   83): Failed to load Wi-Fi driver.
From insmod
# insmod bcm4329.ko
insmod: init_module 'bcm4329.ko' failed (Invalid argument)

  • 0

#2
stevenz

stevenz

    Diehard

  • MoDaCo Silver
  • PipPipPipPip
  • 473 posts
  • Gender:Male
  • Location:Wellington, New Zealand
  • Interests:Motorcycling
    Tinkering
  • Devices:OG Tab, Note, Touchpad, N7
  • Twitter:@KnightNZ
Should only be doing this if you're using a different kernel than the one the module is compiled against. Try flashing one of IntersectRaven's .34 kernels as they have the upgraded bcm4329.ko driver module included. Otherwise you can find this file by itself in the XDA dev forum and push that into /system/library/modules/ using adb. Unless you've got a hardware fault, but I doubt it. Does GPS/3G/Bluetooth all still work?

Don't reflash the radio if you can avoid it, it's unlikely to be the problem and can go wrong too easily.

  • 0
Motorcycling watchmaker.

#3
jthm23

jthm23

    Newbie

  • Members
  • Pip
  • 9 posts
  • Devices:Nexus One

... Try flashing one of IntersectRaven's .34 kernels as they have the upgraded bcm4329.ko driver module included...



I flashed the latest from InsectRaven and insmod the module from /system/lib/modules/2.6.34-CFS-intersectR/kernel/drivers/net/wireless/bcm4329/bcm4329.ko but it is the same thing, with the same errors. Tried the kernel from cyanogen too.

Unless you've got a hardware fault, but I doubt it. Does GPS/3G/Bluetooth all still work?

GPS/3G/Bluetooth are all working fine. You are right, if it was the chip who had fried, nothing would work or it would be working erraticaly.

Thanks for your advice

  • 0

#4
jthm23

jthm23

    Newbie

  • Members
  • Pip
  • 9 posts
  • Devices:Nexus One
Could this be related to msm_i2c errors found in the kernel logs here : http://pastebin.com/ehB7RtN7 ?
Maybe the bus is failing and prevents the driver from accessing the card.

  • 0

#5
McBaul

McBaul

    Newbie

  • Members
  • Pip
  • 15 posts
  • Devices:Google Nexus One
I've been troubled by this issue for almost 1 week..........
From logcat
CODEE/WifiService( 139): Failed to load Wi-Fi driver.
From insmod
CODE# insmod bcm4329.ko
insmod: init_module 'bcm4329.ko' failed (Invalid argument)

Still looking for solutions....

  • 0

#6
guruvan

guruvan

    Newbie

  • Members
  • Pip
  • 12 posts
  • Location:San Francisco
  • Devices:Nexus One
  • Twitter:@guruvan

I've been troubled by this issue for almost 1 week..........
From logcat
CODEE/WifiService( 139): Failed to load Wi-Fi driver.
From insmod
CODE# insmod bcm4329.ko
insmod: init_module 'bcm4329.ko' failed (Invalid argument)

Still looking for solutions....


The issue is that the module you're using was compiled for a different kernel than the one you're using. Find the correct module for the kernel you have, and push it to /system/lib/modules

  • 0

#7
McBaul

McBaul

    Newbie

  • Members
  • Pip
  • 15 posts
  • Devices:Google Nexus One

The issue is that the module you're using was compiled for a different kernel than the one you're using. Find the correct module for the kernel you have, and push it to /system/lib/modules


I'm using the cm5.0.7.1 which worked perfectly before. I also tried sevral orther ko files exported from many other version of cm rom and still not working.............

  • 0

#8
hmbvt

hmbvt

    Newbie

  • Members
  • Pip
  • 1 posts
  • Devices:dash
I thought I was the only one having is this problem... I hope we can find a fix soon...

  • 0

#9
jthm23

jthm23

    Newbie

  • Members
  • Pip
  • 9 posts
  • Devices:Nexus One
I thought I was an isolated case too...
FRF72 did not change a thing : always that sdio_register timeout when trying to insert the bcm4329 driver but I found that doing insmod a few dozen times may load the driver !!
Android shows me "Error" but by typing "rmmod bcm4329" and quicly enable wifi from the control panel it worked.
Unfortunately it did not survive a reboot but hey , it's some news ! And it really looks like faulty hardware now ... ;)

guruvan : I tried several different kernels and took care that the bcm module was compiled for that same kernel ... no luck ... Im beginning to think about witchcraft to get my wifi card back

McBaul : do you have the same msm_i2c related errors and/or dhd_module_init: sdio_register_driver timeout posted before ?

Edited by jthm23, 20 June 2010 - 10:41 PM.

  • 0

#10
stevenz

stevenz

    Diehard

  • MoDaCo Silver
  • PipPipPipPip
  • 473 posts
  • Gender:Male
  • Location:Wellington, New Zealand
  • Interests:Motorcycling
    Tinkering
  • Devices:OG Tab, Note, Touchpad, N7
  • Twitter:@KnightNZ

I thought I was an isolated case too...


Try a nandroid backup and a full wipe & flash the latest Cyanogen 5.0.8 and see what that does. He's got the latest wifi driver in it and a kernel to match. If you're not doing a wipe it could be holding a setting that's keeping the wifi turned off. You could try installing JuiceDefender and see what that does with the wireless.

Looks like a software issue though, so a full wipe & reflash should deal to it. Some WiFi drivers may have issues with the FroYo which won't help matters.

Edited by stevenz, 21 June 2010 - 07:06 AM.

  • 0
Motorcycling watchmaker.

#11
jthm23

jthm23

    Newbie

  • Members
  • Pip
  • 9 posts
  • Devices:Nexus One

Try a nandroid backup and a full wipe & flash the latest Cyanogen 5.0.8 and see what that does. He's got the latest wifi driver in it and a kernel to match. If you're not doing a wipe it could be holding a setting that's keeping the wifi turned off


Thanks but been there done that a few thousand times .... with full wipe, and always checking if bcm4329 is the good one for the loaded kernel... Actually if it was the problem I would not even post a question here, it is something else.

I tried stock, cm , enomther and MCR with various kernel various hboot and various radio. Apart from loading 20 times the module until the motherboard accepts to open the sdio bus nothing seems to be efficient.

  • 0

#12
McBaul

McBaul

    Newbie

  • Members
  • Pip
  • 15 posts
  • Devices:Google Nexus One

I thought I was an isolated case too...
FRF72 did not change a thing : always that sdio_register timeout when trying to insert the bcm4329 driver but I found that doing insmod a few dozen times may load the driver !!
Android shows me "Error" but by typing "rmmod bcm4329" and quicly enable wifi from the control panel it worked.
Unfortunately it did not survive a reboot but hey , it's some news ! And it really looks like faulty hardware now ... ;)

guruvan : I tried several different kernels and took care that the bcm module was compiled for that same kernel ... no luck ... Im beginning to think about witchcraft to get my wifi card back

McBaul : do you have the same msm_i2c related errors and/or dhd_module_init: sdio_register_driver timeout posted before ?


Sorry, I didn't notice that.

  • 0

#13
McBaul

McBaul

    Newbie

  • Members
  • Pip
  • 15 posts
  • Devices:Google Nexus One

Thanks but been there done that a few thousand times .... with full wipe, and always checking if bcm4329 is the good one for the loaded kernel... Actually if it was the problem I would not even post a question here, it is something else.

I tried stock, cm , enomther and MCR with various kernel various hboot and various radio. Apart from loading 20 times the module until the motherboard accepts to open the sdio bus nothing seems to be efficient.


I tried too. If fresh rom didn't solve this problem, maybe this is a HW problem........
Waiting for further solutions...

  • 0

#14
msemaan

msemaan

    Newbie

  • Members
  • Pip
  • 1 posts
  • Devices:nexus one
hello ,
anybody got a solution for this problem, i am having the same problem myself

sdio_register_driver timeout

i got this problem since i upgraded to cm6 , but not instantly, i used it a while , then after sometime the problem began to happen

i managed to open my wifi once since then , but i cant figure out how to enable it again ,even if it is hard could someone point it out?

  • 0

#15
bekit

bekit

    Newbie

  • Members
  • Pip
  • 1 posts
This issue is appearing on the new ViewSonix G Tablet as well. >75% of the time the wifi errors out with these errors. Every once in a while, on a reboot, the wifi will start properly. Has anyone found any answers to this? I'm really concerned that it is hardware related.

-Brint

  • 0

#16
pol88

pol88

    Newbie

  • Members
  • Pip
  • 2 posts
  • Devices:Nexus One
I know it's been a while since last reply.. Exact same problem here (Failed to load wi-fi driver - sdio_register_driver timeout).. Is there a solution for this issue?

Nexus One
Cyanogenmod7 RC1 (but also tried with several other roms, including stock, both rooted and not)

  • 0

#17
windozer

windozer

    Newbie

  • Members
  • Pip
  • 1 posts

I know it's been a while since last reply.. Exact same problem here (Failed to load wi-fi driver - sdio_register_driver timeout).. Is there a solution for this issue?

Nexus One
Cyanogenmod7 RC1 (but also tried with several other roms, including stock, both rooted and not)

Im using the modaco 03/Mar r26 ROM now.
My wifi stopped working after i put intersectraven's cm7 kernel. i have yet to try his wififast version. : ) anyway my wifi is working now after flashing wildmonk's CM kernel http://wildmonks.who.../2.6.35/022311/

Edited by windozer, 06 March 2011 - 07:14 AM.

  • 0

#18
pol88

pol88

    Newbie

  • Members
  • Pip
  • 2 posts
  • Devices:Nexus One

Im using the modaco 03/Mar r26 ROM now.
My wifi stopped working after i put intersectraven's cm7 kernel. i have yet to try his wififast version. : ) anyway my wifi is working now after flashing wildmonk's CM kernel http://wildmonks.who.../2.6.35/022311/


Thank you very much for the reply :D excuse my ignorance but, which kernel should i download? the directory you linked has several files.. i'm new to this whole custom stuff :(

  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users