Skip to contentSkip to conversation

Remove Prism II support from Orinoco

DISCUSSION Jar 2 participants 2 messages Jun 13, 2006 – Jun 14, 2006

Subsystems (2)
lore
Share & tools
lore

Jar

author
#0 lore raw
Quoted 4 lines · Stephen Hemminger

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.

Signature · 1 line
Best Regards, Jar
#1 lore raw
Quoted 4 lines · Jar

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.

The hostap drivers are also much better behaved for rfmon than the orinoco drivers for prism2.

-m

Signature · 4 lines
Mike Kershaw/Dragorn <[email protected]>
GPG Fingerprint: 3546 89DF 3C9D ED80 3381  A661 D7B2 8822 738B BDB1

Bus Error at 008BE426 while reading byte from DEADBEEF in User data space