Linksys AE3000
Dear Sirs,
I run an up-to-date ArchLinux system on a Toshiba Portege R600. I own a Linksys AE3000 (0x13b1:0x003b) usb wifi adapter, with driver downloaded from WikiDevi as per their AE3000 page, with the usual modifications. The driver compiles, installs and runs correctly, until I begin watching a Youtube video, when it causes a kernel panic. I can easily reproduce this crash at will, and thus I could submit a kernel panic picture.
I have seen that this behaviour is hardly discussed on Google, and, though not completely unknown, it seems to me to be under-reported. I am thus wondering whether this has been done already, or if you think might be useful to you (and to me, of course). Should it be of any interest to you, could you please point me to a page where a list of all required info for proper reporting is displayed?
Cheers,
Mario
Prof. Mario Vietri
Scuola Normale Superiore
56100 Pisa
Italia
Tel.: 39-050-509096 FAX: 39-050-509045 Cell: 39-333-7877992
Quoted 9 lines · Mario Vietri
Dear Sirs,
I run an up-to-date ArchLinux system on a Toshiba Portege R600. I own a Linksys AE3000 (0x13b1:0x003b) usb wifi adapter, with driver downloaded from WikiDevi as per their AE3000 page, with the usual modifications.
The driver compiles, installs and runs correctly, until I begin watching a Youtube video, when it causes a kernel panic. I can easily reproduce this crash at will, and thus I could submit a kernel panic picture.
Quoted 6 lines
I have seen that this behaviour is hardly discussed on Google, and, though not completely unknown, it seems to me to be under-reported. I am thus wondering whether this has been done already, or if you think might be useful to you (and to me, of course). Should it be of any interest to you, could you please point me to a page where a list of all required info for proper reporting is displayed?
The usual way to report a kernel panic would be to post that photograph.
That said, I'm not aware of anyone here that debugs vendor drivers, i.e. the ones that are not in the kernel. You will need to look at the cause of the panic, trace it back to the driver, and try to fix it yourself.
Because the chip in that device is an RT3573, perhaps the rt2x00 developers might help you, but most of us have other things to do.
Larry