RE: oops in current -git
- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Latency: 32 (2000ns min, 14000ns max), Cache Line Size 08 Interrupt: pin A routed to IRQ 169 Region 0: Memory at dfeff000 (32-bit, non-prefetchable) [size=4K] Region 1: I/O ports at ac00 [size=64] Capabilities: [dc] Power Management version 2 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=2 PME- 02:0a.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01) Subsystem: 3Com Corporation: Unknown device 0001 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Interrupt: pin A routed to IRQ 185 Region 0: Memory at dfbff000 (32-bit, prefetchable) [size=4K] Capabilities: [dc] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 02:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) Subsystem: Allied Telesyn International AT-2500TX/ACPI Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Latency: 32 (8000ns min, 16000ns max) Interrupt: pin A routed to IRQ 177 Region 0: I/O ports at a800 [size=256] Region 1: Memory at dfefef00 (32-bit, non-prefetchable) [size=256] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- -- Best Regards, Jar - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Remove Prism II support from Orinoco
Stephen Hemminger wrote: >use blacklist in module config to block one. >Just put in /etc/modprobe.conf >blacklist orinoco Unfortunately this is not work at least it is not work with FC4. I can blacklist eepro100 and 8139cp. blacklist eepro100 blacklist 8139cp but I can't blacklist orinoco_pci blacklist orinoco_pci It always loads itself with or without blacklist. That's why I have to do 'rm -f orinoco*.* && depmod -a' when the new kernel arrives. Seems that users are directed to use unsecure orinoco (wep) driver rather than secure hostap (wpa/wpa2,tkip,aes) driver for their prism2 hardware. -- Best Regards, Jar - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 1/5] new pcmcia IDs for hostap - ASUS WL-110
Pavel Roskin wrote: >I strongly believe that every driver should list all devices it can >support. In case of multiple drivers supporting one device, the choice >should be done in userspace. Just from end user's standpoint: I am totally bored with this "model". Every time new kernel comes I first delete all orinoco drivers, because I can't even blacklist them. I don't want to use them, I have a better driver -->hostap. When I try to do the following in the /etc/modprobe.d/blacklist-custom : # a) Do NOT load orinoco_pci/plx when we are using hostap driver # b) Do NOT load eepro100, 8139cp blacklist orinoco_pci blacklist orinoco_plx blacklist eepro100 blacklist 8139cp The eepro100 and 8139cp get blacklisted just fine but not the orinoco_pci, it always want to load itself. Because of this and the lack of WPA support in orinoco drivers the prism2 id:s should be removed from the orinoco drivers. To achieve security you have to run vpn over wireless when you use orinoco drivers. How the orinoco driver can be as _good_ as the hostap driver for the prism2 cards? I think hostap is a lot better. -- Best Regards, Jar - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
