Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.
Anybody can help?
i see many people have the same problem. There is an irq conflict between nvidia and ndiswrapper (can't be hardware, because both work fine under windows), so it has to be software.
thanks a lot for any input! here is the relevant part of my dmesg:
[17179589.584000] ACPI: AC Adapter [AC] (on-line)
[17179589.604000] ACPI: Battery Slot [BAT0] (battery present)
[17179589.688000] ACPI: Lid Switch [LID]
[17179589.688000] ACPI: Power Button (CM) [PBTN]
[17179589.688000] ACPI: Sleep Button (CM) [SBTN]
[17179589.772000] ibm_acpi: ec object not found
[17179589.808000] pcc_acpi: loading...
[17179589.892000] ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
[17179594.204000] ppdev: user-space parallel port driver
[17179594.832000] apm: BIOS not found.
[17179598.064000] NET: Registered protocol family 10
[17179598.064000] lo: Disabled Privacy Extensions
[17179598.064000] ADDRCONF(NETDEV_UP): eth0: link is not ready
[17179598.064000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[17179598.064000] IPv6 over IPv4 tunneling driver
[17179599.516000] Bluetooth: Core ver 2.8
[17179599.516000] NET: Registered protocol family 31
[17179599.516000] Bluetooth: HCI device and connection manager initialized
[17179599.516000] Bluetooth: HCI socket layer initialized
[17179599.584000] Bluetooth: L2CAP ver 2.8
[17179599.584000] Bluetooth: L2CAP socket layer initialized
[17179599.680000] Bluetooth: RFCOMM socket layer initialized
[17179599.680000] Bluetooth: RFCOMM TTY layer initialized
[17179599.680000] Bluetooth: RFCOMM ver 1.7
[17179636.992000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[17179644.104000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[17179644.708000] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[17179655.588000] wlan0: no IPv6 routers present
[17179666.392000] irq 177: nobody cared (try booting with the "irqpoll" option)
[17179666.392000] [<c014ea3a>] report_bad_irq+0x2a/0xa0
[17179666.392000] [<c0105ce9>] do_IRQ+0x19/0x30
[17179666.392000] [<c0103f26>] common_interrupt+0x1a/0x20
[17179666.392000] [<f8872f35>] acpi_processor_idle+0x21e/0x32d [processor]
[17179666.392000] [<c010111f>] cpu_idle+0x6f/0xc0
[17179666.392000] [<c03aca3f>] start_kernel+0x19f/0x200
[17179666.392000] [<c03ac3c0>] unknown_bootoption+0x0/0x1f0
[17179666.392000] [<f8c319a0>] (ndis_isr+0x0/0xd0 [ndiswrapper])
[17179666.392000] Disabling IRQ #177
Basically, everything works great for up to a few hours, when all of a sudden irq 177 gets disabled, and then no more wireless access. If you reboot, everything works great again, but only for a few minutes. You must then always reboot to get things working, and just for a few minutes. A total nuisance!
Thanks a lot again for any help.
You are supposed to give details (as mentioned in wiki - that was the point of suggesting you to read wiki). At the least, mention ndiswrapper version.
Since there is no way for me to test this setup, you try to find out what causes it; e.g., don't load module when system starts, but load it manually later (after / before loading nvidia driver) etc. Does it happen after nvidia is unloaded? Have you tried changing acpi settings, as documented in wiki? And so on.
ndiswrapper itself doesn't deal with hardware. So Windows driver and nvidia driver together are responsible for it.
I'm currently going through the wiki and compiling a bug report along those lines. An increase in coursework has been slowing me down.
Not giving all details is even more of a nuisance. (Hint: Read wiki, especially Troubleshooting and Bugs sections.)
That hint was not very helpful. What would you like to see specifically?
If you need more details, there is plenty of info available on the net from many people around the world with different distributions, with the same problem. See for instance, https://launchpad.net/bugs/57355
Of course, I'd be delighted to provide you with any additional info, as long as you specify what you would like to see.
thanks and regards,
I also have this problem, it occurs on Broadcom 4311 wireless cards found in some new dell inspirons and the compaq v3000z (which I have). This problem goes away if you don't use the nvidia proprietary driver, but I would really like to see a solution where both can coexist. I'm willing to use my machine as a test machine for possible patches/etc.
same here! I agree with you!