On Tuesday, 13 February 2007 18:02, Larry Finger wrote: > Rafael J. Wysocki wrote: > > 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. > > PLEASE SEND OUTPUT FROM dmesg!!!!!!!!!!!!!!!!!!!!!
Okay, okay. The first one (dmesg.log.gz) is for the driver with bcm43xx_request_firmware(bcm) in bcm43xx_resume(). The other one is for the driver without it. BCM43xx_IRQWAIT_MAX_RETRIES was set to 100 in both cases. Greetings, Rafael
dmesg.log.gz
Description: GNU Zip compressed data
dmesg-2.log.gz
Description: GNU Zip compressed data
_______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
