Re: [SOLVED] Prism 2.5 MiniPCI Wireless Unstable
My Thinkpad T30 "Intel" wireless now works perfectly after switching to the hostap_pci driver and updating the primary and station firmware (pk010101.hex and sf010804.hex respectively) on the MiniPCI card using the WinUpdate program (I dual boot Win2K) as described in the below link. I re-ran my rsync test and it completed without error at a smooth 550Kbps from two floors up. Thanks, Mike hostap_pci: Registered netdevice wifi0 wifi0: NIC: id=0x8013 v1.0.0 wifi0: PRI: id=0x15 v1.1.1 wifi0: STA: id=0x1f v1.8.4 wifi0: Intersil Prism2.5 PCI: mem=0xf800, irq=11 On Tue, 12 Jul 2005 01:46:52 +0300 Jar <[EMAIL PROTECTED]> wrote: > Michael B Allen wrote: > > hostap_pci: 0.3.9 - 2005-06-10 (Jouni Malinen <[EMAIL PROTECTED]>) > > ACPI: PCI interrupt :02:02.0[A] -> GSI 11 (level, low) -> IRQ 11 > > hostap_pci: Registered netdevice wifi0 > > wifi0: NIC: id=0x8013 v1.0.0 > > wifi0: PRI: id=0x15 v1.1.0 > > wifi0: STA: id=0x1f v1.4.9 > > wifi0: Intersil Prism2.5 PCI: mem=0xf800, irq=11 > > Maybe you should try to update the firmwares, that is all you can do at > this point. For me the 1.1.1/1.7.4 combination has been worked like a > charm, also when used in heavy load. I belive the driver itself is > stable (the PCI prism2.5 card never timed out for me). So there has to > be hardware/firmware problem somewhere. > > PRI: id=0x15 v1.1.0 --> v1.1.1 > STA: id=0x1f v1.4.9 --> v1.7.4 > > The Flashing HOWTO: http://linux.junsun.net/intersil-prism/ > The firmware collection: http://www.red-bean.com/~proski/firmware/ > > You can try the RAM (volatile) firmawares first and if it helps you can > flash the non volatile versions (Flash) if you want. Newer flash primary > firmware alone, but primary and station firmwares simultaneously. The > filenames (if I remember correctly) are: > > ak010104.hex (RAM PRI:1.1.4) > rf010704.hex (RAM STA:1.7.4) > > pk010101.hex (Flash PRI:1.1.1) > sf010704.hex (Flash STA:1.7.4) > > There is also newer verisons available: > > The latest firmwares in the collection are: > > RAM Flash > Prism 2 PCMCIA 1.7.1 1.7.1 > Prism 2.5/3 PCI/PCMCIA 1.8.4 (NEW!) 1.8.4 > Prism 3 USB1.8.3 1.8.4 > > -- > Best Regards, Jar > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Prism 2.5 MiniPCI Wireless Unstable
On Mon, 11 Jul 2005 17:08:38 +0300 (EEST) "Jar" <[EMAIL PROTECTED]> wrote: > > > FYI: > > > > Please use more suitable driver for 802.11b Prism cards. This kind of > > driver is > > hostap_pci (for PCI cards). It can be downloaded from > > http://hostap.epitest.fi/ > > > > This driver really works for Prism2/2.5/3 cards! > > Sorry about this spam, I didn't read your mail in LKML properly. You already > have > used hostap in the past :) > > Still I think the hostap_pci is the best driver for Prism2/2.5/3 cards. I > have one > Prism2.5 PCI card in daily & heavy use as access point. The card becomes 100% > stable > after I updated it's primary and station firmawares (PRI 1.0.0 --> 1.1.1, STA > 1.4.9-->1.7.4). There have been a lot of development after 2.4 days in hostap > driver. I use the latest and greatest 0.3.9 version :) Better. With the hostap_pci driver, after 2 and a half tries, I managed to get the backup to complete. But I still get lots of errors along the way: Jul 11 16:29:42 quark kernel: NETDEV WATCHDOG: wifi0: transmit timed out Jul 11 16:29:42 quark kernel: wifi0 Tx timed out! Resetting card Jul 11 16:29:43 quark kernel: hostap_pci: wifi0: resetting card Jul 11 16:30:13 quark last message repeated 2 times Jul 11 16:30:28 quark kernel: NETDEV WATCHDOG: wifi0: transmit timed out Jul 11 16:30:28 quark kernel: wifi0 Tx timed out! Resetting card Jul 11 16:30:29 quark kernel: hostap_pci: wifi0: resetting card Jul 11 16:31:03 quark last message repeated 2 times Jul 11 16:31:18 quark kernel: NETDEV WATCHDOG: wifi0: transmit timed out Jul 11 16:31:18 quark kernel: wifi0 Tx timed out! Resetting card Jul 11 16:31:19 quark kernel: hostap_pci: wifi0: resetting card ... With the hostap_pci driver, the first time I tried to run the backup (rsync over ssh from workstation next to AP to T30 w/ prism card) my machine locked up after about 15 minutes. After rebooting, running fsck, and moving close to the AP I stopped X and tried to run it on virtual consoles. After about 15 minutes it stopped but the machine didn't lockup. It was totally idle w/ no network traffic. Running lsof | grep rsync tool about 20 seconds to respond. After stopping the interface and reloading the hostap_pci modules I was able to get network back. Interestingly rsync suddenly resumed where it left off and eventually completed (resetting the card all the way). Something about this rsync backup really tickles the system. Is this a known problem? Is it known to be the driver, firmware, or what? Could it be my access point (Linksys 802.11b 4 port switch BEFW11S4 v.2)? Thanks for your help. Personally I think I'm ok - now that I've sync'd up the backup should only take a minute or two now. But I'm willing to explore this if someone wants me to try some debugging. > See.. > > hostap_pci: 0.3.9 - 2005-06-10 (Jouni Malinen <[EMAIL PROTECTED]>) > PCI: Found IRQ 9 for device :00:09.0 > hostap_pci: Registered netdevice wifi1 > wifi1: Original COR value: 0x0 > prism2_hw_init: initialized in 195 ms > wifi1: NIC: id=0x8013 v1.0.0 > wifi1: PRI: id=0x15 v1.1.1 > wifi1: STA: id=0x1f v1.7.4 > wifi1: Intersil Prism2.5 PCI: mem=0xe780, irq=9 > wifi1: registered netdevice wlan1 > wifi1: Deauthenticate all stations > wifi1: prism2_send_mgmt - device is not UP - cannot send frame > wlan1: Enabling ALC hostap_pci: 0.3.9 - 2005-06-10 (Jouni Malinen <[EMAIL PROTECTED]>) ACPI: PCI interrupt :02:02.0[A] -> GSI 11 (level, low) -> IRQ 11 hostap_pci: Registered netdevice wifi0 wifi0: NIC: id=0x8013 v1.0.0 wifi0: PRI: id=0x15 v1.1.0 wifi0: STA: id=0x1f v1.4.9 wifi0: Intersil Prism2.5 PCI: mem=0xf800, irq=11 Mike - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Prism 2.5 MiniPCI Wireless Unstable
On Mon, 11 Jul 2005 17:08:38 +0300 (EEST) Jar [EMAIL PROTECTED] wrote: FYI: Please use more suitable driver for 802.11b Prism cards. This kind of driver is hostap_pci (for PCI cards). It can be downloaded from http://hostap.epitest.fi/ This driver really works for Prism2/2.5/3 cards! Sorry about this spam, I didn't read your mail in LKML properly. You already have used hostap in the past :) Still I think the hostap_pci is the best driver for Prism2/2.5/3 cards. I have one Prism2.5 PCI card in daily heavy use as access point. The card becomes 100% stable after I updated it's primary and station firmawares (PRI 1.0.0 -- 1.1.1, STA 1.4.9--1.7.4). There have been a lot of development after 2.4 days in hostap driver. I use the latest and greatest 0.3.9 version :) Better. With the hostap_pci driver, after 2 and a half tries, I managed to get the backup to complete. But I still get lots of errors along the way: Jul 11 16:29:42 quark kernel: NETDEV WATCHDOG: wifi0: transmit timed out Jul 11 16:29:42 quark kernel: wifi0 Tx timed out! Resetting card Jul 11 16:29:43 quark kernel: hostap_pci: wifi0: resetting card Jul 11 16:30:13 quark last message repeated 2 times Jul 11 16:30:28 quark kernel: NETDEV WATCHDOG: wifi0: transmit timed out Jul 11 16:30:28 quark kernel: wifi0 Tx timed out! Resetting card Jul 11 16:30:29 quark kernel: hostap_pci: wifi0: resetting card Jul 11 16:31:03 quark last message repeated 2 times Jul 11 16:31:18 quark kernel: NETDEV WATCHDOG: wifi0: transmit timed out Jul 11 16:31:18 quark kernel: wifi0 Tx timed out! Resetting card Jul 11 16:31:19 quark kernel: hostap_pci: wifi0: resetting card ... With the hostap_pci driver, the first time I tried to run the backup (rsync over ssh from workstation next to AP to T30 w/ prism card) my machine locked up after about 15 minutes. After rebooting, running fsck, and moving close to the AP I stopped X and tried to run it on virtual consoles. After about 15 minutes it stopped but the machine didn't lockup. It was totally idle w/ no network traffic. Running lsof | grep rsync tool about 20 seconds to respond. After stopping the interface and reloading the hostap_pci modules I was able to get network back. Interestingly rsync suddenly resumed where it left off and eventually completed (resetting the card all the way). Something about this rsync backup really tickles the system. Is this a known problem? Is it known to be the driver, firmware, or what? Could it be my access point (Linksys 802.11b 4 port switch BEFW11S4 v.2)? Thanks for your help. Personally I think I'm ok - now that I've sync'd up the backup should only take a minute or two now. But I'm willing to explore this if someone wants me to try some debugging. See.. hostap_pci: 0.3.9 - 2005-06-10 (Jouni Malinen [EMAIL PROTECTED]) PCI: Found IRQ 9 for device :00:09.0 hostap_pci: Registered netdevice wifi1 wifi1: Original COR value: 0x0 prism2_hw_init: initialized in 195 ms wifi1: NIC: id=0x8013 v1.0.0 wifi1: PRI: id=0x15 v1.1.1 wifi1: STA: id=0x1f v1.7.4 wifi1: Intersil Prism2.5 PCI: mem=0xe780, irq=9 wifi1: registered netdevice wlan1 wifi1: Deauthenticate all stations wifi1: prism2_send_mgmt - device is not UP - cannot send frame wlan1: Enabling ALC hostap_pci: 0.3.9 - 2005-06-10 (Jouni Malinen [EMAIL PROTECTED]) ACPI: PCI interrupt :02:02.0[A] - GSI 11 (level, low) - IRQ 11 hostap_pci: Registered netdevice wifi0 wifi0: NIC: id=0x8013 v1.0.0 wifi0: PRI: id=0x15 v1.1.0 wifi0: STA: id=0x1f v1.4.9 wifi0: Intersil Prism2.5 PCI: mem=0xf800, irq=11 Mike - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [SOLVED] Prism 2.5 MiniPCI Wireless Unstable
My Thinkpad T30 Intel wireless now works perfectly after switching to the hostap_pci driver and updating the primary and station firmware (pk010101.hex and sf010804.hex respectively) on the MiniPCI card using the WinUpdate program (I dual boot Win2K) as described in the below link. I re-ran my rsync test and it completed without error at a smooth 550Kbps from two floors up. Thanks, Mike hostap_pci: Registered netdevice wifi0 wifi0: NIC: id=0x8013 v1.0.0 wifi0: PRI: id=0x15 v1.1.1 wifi0: STA: id=0x1f v1.8.4 wifi0: Intersil Prism2.5 PCI: mem=0xf800, irq=11 On Tue, 12 Jul 2005 01:46:52 +0300 Jar [EMAIL PROTECTED] wrote: Michael B Allen wrote: hostap_pci: 0.3.9 - 2005-06-10 (Jouni Malinen [EMAIL PROTECTED]) ACPI: PCI interrupt :02:02.0[A] - GSI 11 (level, low) - IRQ 11 hostap_pci: Registered netdevice wifi0 wifi0: NIC: id=0x8013 v1.0.0 wifi0: PRI: id=0x15 v1.1.0 wifi0: STA: id=0x1f v1.4.9 wifi0: Intersil Prism2.5 PCI: mem=0xf800, irq=11 Maybe you should try to update the firmwares, that is all you can do at this point. For me the 1.1.1/1.7.4 combination has been worked like a charm, also when used in heavy load. I belive the driver itself is stable (the PCI prism2.5 card never timed out for me). So there has to be hardware/firmware problem somewhere. PRI: id=0x15 v1.1.0 -- v1.1.1 STA: id=0x1f v1.4.9 -- v1.7.4 The Flashing HOWTO: http://linux.junsun.net/intersil-prism/ The firmware collection: http://www.red-bean.com/~proski/firmware/ You can try the RAM (volatile) firmawares first and if it helps you can flash the non volatile versions (Flash) if you want. Newer flash primary firmware alone, but primary and station firmwares simultaneously. The filenames (if I remember correctly) are: ak010104.hex (RAM PRI:1.1.4) rf010704.hex (RAM STA:1.7.4) pk010101.hex (Flash PRI:1.1.1) sf010704.hex (Flash STA:1.7.4) There is also newer verisons available: The latest firmwares in the collection are: RAM Flash Prism 2 PCMCIA 1.7.1 1.7.1 Prism 2.5/3 PCI/PCMCIA 1.8.4 (NEW!) 1.8.4 Prism 3 USB1.8.3 1.8.4 -- Best Regards, Jar - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Prism 2.5 MiniPCI Wireless Unstable
My wireless is a little fragile. I have a Thinkpad T30 with a MiniPCI card: 02:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01) Subsystem: Intel Corp. Wireless 802.11b MiniPCI Adapter Flags: bus master, medium devsel, latency 64, IRQ 11 Memory at f800 (32-bit, prefetchable) [size=4K] Capabilities: [dc] Power Management version 2 If I run rsync it's guaranteed to get the kernel in a bad way. CPU goes to 100% doing what looks like an endless loop error handling. If I unload and load the orinoco, orinoco_pci, and hermes modules it restores normal behavior. But anything can trigger the problem. I just tried to print to a network printer and it triggered the problem. The first of many log messages follows: Jul 11 00:03:07 quark kernel: eth1: Error -110 transmitting packet Jul 11 00:03:07 quark kernel: eth1: Error -110 writing Tx descriptor to BAP Jul 11 00:03:08 quark last message repeated 99 times Jul 11 00:03:08 quark kernel: hermes @ MEM 0xe0856000: Timeout waiting for command completion. Jul 11 00:03:08 quark kernel: eth1: Error -110 writing Tx descriptor to BAP Jul 11 00:03:09 quark last message repeated 610 times Jul 11 00:03:09 quark kernel: hermes @ MEM 0xe0856000: Error -16 issuing command. Jul 11 00:03:09 quark kernel: eth1: Error -5 writing packet to BAP Jul 11 00:03:09 quark kernel: hermes @ MEM 0xe0856000: Error -16 issuing command. Jul 11 00:03:09 quark kernel: eth1: Error -16 transmitting packet Jul 11 00:03:09 quark kernel: hermes @ MEM 0xe0856000: Error -16 issuing command. Jul 11 00:03:09 quark kernel: eth1: Error -16 transmitting packet Jul 11 00:03:09 quark kernel: hermes @ MEM 0xe0856000: Error -16 issuing command. Jul 11 00:03:09 quark kernel: eth1: Error -16 transmitting packet I tried changing irqs around a while back but I can't see any difference. Is there anything I can do about this? I had problems with 2.4 using the hostap driver too but it was stable enough to run my rsync backup. I'm systems programmer and I'm willing to patch & debug. Thanks, Mike Linux quark.foo.net 2.6.11-1.35_FC3 #1 Mon Jun 13 00:52:08 EDT 2005 i686 i686 i386 GNU/Linux autofs426181 1 pcmcia 26465 4 dm_mod 59221 0 video 15813 0 ibm_acpi 15997 0 button 6609 0 battery 9285 0 ac 4805 0 md5 4161 1 ipv6 259201 8 yenta_socket 21065 2 rsrc_nonstatic 10433 1 yenta_socket pcmcia_core47993 3 pcmcia,yenta_socket,rsrc_nonstatic uhci_hcd 33497 0 hw_random 6101 0 i2c_i8018653 0 i2c_core 21953 1 i2c_i801 snd_intel8x0m 18565 0 snd_intel8x0 34049 0 snd_ac97_codec 71097 2 snd_intel8x0m,snd_intel8x0 snd_pcm_oss51953 0 snd_mixer_oss 18241 1 snd_pcm_oss snd_pcm99657 4 snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_timer 33093 1 snd_pcm snd56741 7 snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 10785 1 snd snd_page_alloc 9669 3 snd_intel8x0m,snd_intel8x0,snd_pcm orinoco_pci 8269 0 orinoco53837 1 orinoco_pci hermes 8513 2 orinoco_pci,orinoco e100 46401 0 mii 4929 1 e100 floppy 64753 0 ext3 131145 1 jbd82905 1 ext3 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Prism 2.5 MiniPCI Wireless Unstable
My wireless is a little fragile. I have a Thinkpad T30 with a MiniPCI card: 02:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01) Subsystem: Intel Corp. Wireless 802.11b MiniPCI Adapter Flags: bus master, medium devsel, latency 64, IRQ 11 Memory at f800 (32-bit, prefetchable) [size=4K] Capabilities: [dc] Power Management version 2 If I run rsync it's guaranteed to get the kernel in a bad way. CPU goes to 100% doing what looks like an endless loop error handling. If I unload and load the orinoco, orinoco_pci, and hermes modules it restores normal behavior. But anything can trigger the problem. I just tried to print to a network printer and it triggered the problem. The first of many log messages follows: Jul 11 00:03:07 quark kernel: eth1: Error -110 transmitting packet Jul 11 00:03:07 quark kernel: eth1: Error -110 writing Tx descriptor to BAP Jul 11 00:03:08 quark last message repeated 99 times Jul 11 00:03:08 quark kernel: hermes @ MEM 0xe0856000: Timeout waiting for command completion. Jul 11 00:03:08 quark kernel: eth1: Error -110 writing Tx descriptor to BAP Jul 11 00:03:09 quark last message repeated 610 times Jul 11 00:03:09 quark kernel: hermes @ MEM 0xe0856000: Error -16 issuing command. Jul 11 00:03:09 quark kernel: eth1: Error -5 writing packet to BAP Jul 11 00:03:09 quark kernel: hermes @ MEM 0xe0856000: Error -16 issuing command. Jul 11 00:03:09 quark kernel: eth1: Error -16 transmitting packet Jul 11 00:03:09 quark kernel: hermes @ MEM 0xe0856000: Error -16 issuing command. Jul 11 00:03:09 quark kernel: eth1: Error -16 transmitting packet Jul 11 00:03:09 quark kernel: hermes @ MEM 0xe0856000: Error -16 issuing command. Jul 11 00:03:09 quark kernel: eth1: Error -16 transmitting packet I tried changing irqs around a while back but I can't see any difference. Is there anything I can do about this? I had problems with 2.4 using the hostap driver too but it was stable enough to run my rsync backup. I'm systems programmer and I'm willing to patch debug. Thanks, Mike Linux quark.foo.net 2.6.11-1.35_FC3 #1 Mon Jun 13 00:52:08 EDT 2005 i686 i686 i386 GNU/Linux autofs426181 1 pcmcia 26465 4 dm_mod 59221 0 video 15813 0 ibm_acpi 15997 0 button 6609 0 battery 9285 0 ac 4805 0 md5 4161 1 ipv6 259201 8 yenta_socket 21065 2 rsrc_nonstatic 10433 1 yenta_socket pcmcia_core47993 3 pcmcia,yenta_socket,rsrc_nonstatic uhci_hcd 33497 0 hw_random 6101 0 i2c_i8018653 0 i2c_core 21953 1 i2c_i801 snd_intel8x0m 18565 0 snd_intel8x0 34049 0 snd_ac97_codec 71097 2 snd_intel8x0m,snd_intel8x0 snd_pcm_oss51953 0 snd_mixer_oss 18241 1 snd_pcm_oss snd_pcm99657 4 snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_timer 33093 1 snd_pcm snd56741 7 snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 10785 1 snd snd_page_alloc 9669 3 snd_intel8x0m,snd_intel8x0,snd_pcm orinoco_pci 8269 0 orinoco53837 1 orinoco_pci hermes 8513 2 orinoco_pci,orinoco e100 46401 0 mii 4929 1 e100 floppy 64753 0 ext3 131145 1 jbd82905 1 ext3 - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
