On Tuesday, 13 February 2007 00:24, Michael Buesch wrote: > On Tuesday 13 February 2007 00:08, Rafael J. Wysocki wrote: > > On Monday, 12 February 2007 23:20, Larry Finger wrote: > > > Rafael J. Wysocki wrote: > > > > On Monday, 12 February 2007 02:18, Larry Finger wrote: > > > >> Rafael J. Wysocki wrote: > > > >>> It doesn't help in my case. The behavior is similar to that without the patch, > > > >>> but also with the patch it loses the association entirely. > > > >> Thanks for trying. > > > >> > > > >> Do you have this patch installed? If you do, please try increasing the 100 to 200. > > > > > > > > Hm, but it wouldn't help to get the microcode to respond after the resume ... > > > > > > Yes it would. That count is how long the system waits for the firmware to respond. > > > > > > > I'm still thinking the problem is with the firmware. Where exactly is it > > > > stored? > > > > > > In the memory of the microprocessor on the card. > > > > > > Please do what I asked. > > > > With or without the previous patch? > > Both, please. It doesn't help in either case. I get albercik:~ # ifconfig eth1 down albercik:~ # ifconfig eth1 up SIOCSIFFLAGS: No such device in both cases. I think the problem is that the firmware is not present and requesting it doesn't work for some reason. Greetings, Rafael - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
