Re: Help troubleshooting a wi(4) problem
This mail is only so those who come after me can find something to help them. I had a recommendation to downgrade to station firmware 1.7.4, so I did. wi0 at pci0 dev 20 function 0 "Intersil PRISM2.5" rev 0x01: irq 11 wi0: PRISM2.5 ISL3874A(Mini-PCI) (0x8013), Firmware 1.1.1 (primary), 1.7.4 (station), address 00:09:5b:11:cc:4e I've been running this for a week with some fairly heavy network loads, and no problems. I consider my problem resolved. Thanks for all who helped.
Re: Help troubleshooting a wi(4) problem
I've completed the firmware upgrade, finally. But when starting the network during boot I get errors. I'm not sure if I should worry about this yet. I've not tested to see if I can duplicate the previous error. $ cat /var/run/dmesg.boot |grep wi0 wi0 at pci0 dev 20 function 0 "Intersil PRISM2.5" rev 0x01: irq 11 wi0: PRISM2.5 ISL3874A(Mini-PCI) (0x8013), Firmware 1.1.1 (primary), 1.8.4 (station), address 00:09:5b:11:cc:4e wi0: init failed wi0: failed to allocate 1594 bytes on NIC wi0: tx buffer allocation failed wi0: failed to allocate 1594 bytes on NIC wi0: mgmt. buffer allocation failed wi0: wi_start: xmit failed The first 5 wi0: lines occur when the network is started. The 6th line occurs when httpd is started. Jason Murray wrote: $ cat /var/run/dmesg.boot | grep wi0 wi0 at pci0 dev 20 function 0 "Intersil PRISM2.5" rev 0x01: irq 11 wi0: PRISM2.5 ISL3874A(Mini-PCI) (0x8013), Firmware 1.0.7 (primary), 1.3.6 (station), address 00:09:5b:11:cc:4e I'm going to try a firmware upgrade ASAP. I found some references to using a the Linux bootable distro to use the hostap toolset (prism2_srec). Is this still the best way of doing it, short of moving the card to a windows box? If the problem is still there I'll re-plead for help. Chris Keuthe suggested a kernel upgrade. I'm running 3.9 release, with raidframe and autoconfig option. Is the patch you submitted later than that. Melameth, Daniel D. wrote: Melameth, Daniel D. wrote: Jason Murray wrote: Hello. I've been having a problem for the last year or so. This problem has occurred in 3.6 - 3.9. Let me try to explain it. I have a server with a wireless (802.11b) card in it and I have a laptop that is using that server as its gateway. Whenever the traffic over the wireless network increases (usually during an iTunes/iPod update/sync) I get the following types of messages: May 16 17:09:03 disillusion /bsd: wi0: wi_start: xmit failed May 16 17:09:18 disillusion /bsd: wi0: wi_mgmt_xmit: xmit failed And then the wireless network disappears. Does anyone have any ideas why this might be happening? Or any suggestions on how I can get more information about what is going on? You might want to try updating the firmware of the wi card--the output of 'cat /var/run/dmesg.boot | grep ral0' might help. I meant the output of 'cat /var/run/dmesg.boot | grep wi0' might help.
Re: Help troubleshooting a wi(4) problem
If you search the links from netgate.com you can find prism firmwares up to 1.8.0 or 1.8.4 which give you various interesting features and bugfixes Melameth, Daniel D. [EMAIL PROTECTED] wrote: > Jason Murray wrote: > > $ cat /var/run/dmesg.boot | grep wi0 > > wi0 at pci0 dev 20 function 0 "Intersil PRISM2.5" rev 0x01: irq 11 > > wi0: PRISM2.5 ISL3874A(Mini-PCI) (0x8013), Firmware 1.0.7 (primary), > > 1.3.6 (station), address 00:09:5b:11:cc:4e > > > > I'm going to try a firmware upgrade ASAP. I found some references to > > using a the Linux bootable distro to use the hostap toolset > > (prism2_srec). Is this still the best way of doing it, short of moving > > the card to a windows box? If the problem is still there I'll re-plead > > for help. > > > > Chris Keuthe suggested a kernel upgrade. I'm running 3.9 release, with > > raidframe and autoconfig option. Is the patch you submitted later than > > that. > > That's definitely old firmware. The last time I did this I used a > Windows box to move to 1.1.1/1.8.4. -- There is no certainty, there is only opportunity
Re: Help troubleshooting a wi(4) problem
Jason Murray wrote: > $ cat /var/run/dmesg.boot | grep wi0 > wi0 at pci0 dev 20 function 0 "Intersil PRISM2.5" rev 0x01: irq 11 > wi0: PRISM2.5 ISL3874A(Mini-PCI) (0x8013), Firmware 1.0.7 (primary), > 1.3.6 (station), address 00:09:5b:11:cc:4e > > I'm going to try a firmware upgrade ASAP. I found some references to > using a the Linux bootable distro to use the hostap toolset > (prism2_srec). Is this still the best way of doing it, short of moving > the card to a windows box? If the problem is still there I'll re-plead > for help. > > Chris Keuthe suggested a kernel upgrade. I'm running 3.9 release, with > raidframe and autoconfig option. Is the patch you submitted later than > that. That's definitely old firmware. The last time I did this I used a Windows box to move to 1.1.1/1.8.4.
Re: Help troubleshooting a wi(4) problem
$ cat /var/run/dmesg.boot | grep wi0 wi0 at pci0 dev 20 function 0 "Intersil PRISM2.5" rev 0x01: irq 11 wi0: PRISM2.5 ISL3874A(Mini-PCI) (0x8013), Firmware 1.0.7 (primary), 1.3.6 (station), address 00:09:5b:11:cc:4e I'm going to try a firmware upgrade ASAP. I found some references to using a the Linux bootable distro to use the hostap toolset (prism2_srec). Is this still the best way of doing it, short of moving the card to a windows box? If the problem is still there I'll re-plead for help. Chris Keuthe suggested a kernel upgrade. I'm running 3.9 release, with raidframe and autoconfig option. Is the patch you submitted later than that. Melameth, Daniel D. wrote: Melameth, Daniel D. wrote: Jason Murray wrote: Hello. I've been having a problem for the last year or so. This problem has occurred in 3.6 - 3.9. Let me try to explain it. I have a server with a wireless (802.11b) card in it and I have a laptop that is using that server as its gateway. Whenever the traffic over the wireless network increases (usually during an iTunes/iPod update/sync) I get the following types of messages: May 16 17:09:03 disillusion /bsd: wi0: wi_start: xmit failed May 16 17:09:18 disillusion /bsd: wi0: wi_mgmt_xmit: xmit failed And then the wireless network disappears. Does anyone have any ideas why this might be happening? Or any suggestions on how I can get more information about what is going on? You might want to try updating the firmware of the wi card--the output of 'cat /var/run/dmesg.boot | grep ral0' might help. I meant the output of 'cat /var/run/dmesg.boot | grep wi0' might help.
Re: Help troubleshooting a wi(4) problem
Melameth, Daniel D. wrote: > Jason Murray wrote: > > Hello. I've been having a problem for the last year or so. This > > problem has occurred in 3.6 - 3.9. > > > > Let me try to explain it. > > > > I have a server with a wireless (802.11b) card in it and I have a > > laptop that is using that server as its gateway. Whenever the > > traffic over the wireless network increases (usually during an > > iTunes/iPod update/sync) I get the following types of messages: > > > > May 16 17:09:03 disillusion /bsd: wi0: wi_start: xmit failed May 16 > > 17:09:18 disillusion /bsd: wi0: wi_mgmt_xmit: xmit failed > > > > And then the wireless network disappears. > > > > Does anyone have any ideas why this might be happening? Or any > > suggestions on how I can get more information about what is going > > on? > > You might want to try updating the firmware of the wi card--the > output of 'cat /var/run/dmesg.boot | grep ral0' might help. I meant the output of 'cat /var/run/dmesg.boot | grep wi0' might help.
Re: Help troubleshooting a wi(4) problem
Jason Murray wrote: > Hello. I've been having a problem for the last year or so. This > problem has occurred in 3.6 - 3.9. > > Let me try to explain it. > > I have a server with a wireless (802.11b) card in it and I have a > laptop that is using that server as its gateway. Whenever the traffic > over the wireless network increases (usually during an iTunes/iPod > update/sync) I get the following types of messages: > > May 16 17:09:03 disillusion /bsd: wi0: wi_start: xmit failed > May 16 17:09:18 disillusion /bsd: wi0: wi_mgmt_xmit: xmit failed > > And then the wireless network disappears. > > Does anyone have any ideas why this might be happening? Or any > suggestions on how I can get more information about what is going on? You might want to try updating the firmware of the wi card--the output of 'cat /var/run/dmesg.boot | grep ral0' might help.
