linux@xxxxxxxxxxxxxxxx said: > rmmod / modprobe not working isn't a good sign. After a modprobe there is a > pretty comprehensive reconfigure. When you say you currently have to power > cycle, have you also tried a reboot I'll make another go at rmmod/modprobe at the next event to make sure. linux@xxxxxxxxxxxxxxxx said: > and have a look in there under ieee80211/phy0/rt2500pci for first. Probable > the most useful thing there is the queue counters which should let you see if > the card is > a) trying to transmit anything > b) receiving anything Done that. I currently have: chipset:rt chip: 0201 chipset:rf chip: 0003 chipset:revision:00000004 chipset: chipset:csr length: 93 chipset:eeprom length: 256 chipset:bbp length: 64 chipset:rf length: 5 dev_flags:0x00000a2f driver:driver: rt2500pci driver:version: 2.2.3 driver:compiled: Feb 21 2009 15:31:04 Binary file queue/dump matches queue/queue:qid count limit length index done crypto queue/queue:14 0 24 6612 12 0 0 queue/queue:0 22 24 0 22 22 0 queue/queue:1 707 24 0 11 11 0 queue/queue:16 0 1 0 0 0 0 queue/queue:17 0 8 0 0 0 0 register/bbp_offset:0 register/bbp_value:0x12 register/csr_offset:0 register/csr_value:0x00000004 register/eeprom_offset:0 register/eeprom_value:0x2560 register/rf_offset:0 register/rf_value:0x00000000 What should I look out for wrt the queue counters? > Would be good to know if the legacy driver has the same issue - if it does > that might point to a hardware fault. Is that still maintained and working with new kernels? I recall needing to have different a different config setup for with the legacy driver (other name, and whatnot), so it's been a while. This is a "once is a week" bug, so it's hard to say for sure when it's working correctly. If you really want me to, I could try the legay one for a couple of weeks... /Anders -- 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
