[ath9k-devel] ath9k vs nvidia(proprietary)

[Dmitri Seletski <drjoms@gmail.com>]

Hello Jason.
I will probably get a slap from developers, which i do and do not deserve...
Anyway, i was using gnome on linux for as long as i remember.
And every time i have loaded nvidia drivers, i was loading gnome too.
(hence, my assumption of hardware issue)
Now for several days i am running xfce, pinging local computers over
Acess Point  in G mode for hours without one packet being dropped.
Nvidia drivers are loaded, SLI is enabled, all 3 devices are actually
IRQ 16...
I could never guess, it looks like it was not hardware problem after all.

So irqpoll option was unnecessary for me...

I still have issue with connecting using N mode...
It silently fails, even by manually assigning channel.

Jason Tackaberry wrote:
> On Mon, 2009-04-06 at 22:17 +0100, Dmitri Seletski wrote:
>   
>>> It should not be a problem.  You can try some workarounds, such as the
>>> "irqpoll" option on the kernel command line.
>>>       
>> [...]
>>    
>> Well, how can i help? I am not coder... I dont speak C ;)
>>     
>
> Dmitri, I'd be very curious to hear if booting with the irqpoll option
> helps your problem.
>
> The other day I was playing with a D-Link DWA-652 and whenever I started
> doing bulk transfers dmesg would show "received PCI FATAL interrupt" and
> the wireless connection would go dead.
>
> I noticed in /proc/interrupts that both ath9k and nvidia were using IRQ
> 16.  However, as the nvidia binary driver is more important to me than
> the wireless card, and I didn't have very long to decide if I wanted to
> keep it, I decided to return the DWA-652.
>
> Thanks,
> Jason.
>
>