prism54 card driver

**Jada32** · 01-03-2011

I have tried to blacklist or remove the prism54 driver which does not support WPA. I can see that p54pci is included in the linux kernel (2.6.33.7), but I cannot figure out how to change the driver. Everytime I plug it in, the hardware tab in PC linux control center shows the module as prism54.

Could someone help?

**reed9** · 01-03-2011

How have you tried to remove or blacklist prism54?

**Jada32** · 01-04-2011

Hi Reed,

Glad to hear from you again. I bought a new hard drive and put the PCLinuxOS on it. I have even thought of buying a new card, but it seems that whatever the card people have trouble with them so I am sticking with the old card for now. I read through tons of forums and messages trying to figure this out. I believe that I got into the terminal as root and typed "blacklist prism54." What I am wondering is, if I have messed up a bunch of files and could I start over? Thanks for the help.

**reed9** · 01-04-2011

No, if what you did was just write "blacklist prism54" in a terminal, you haven't messed anything up. (Though you should have gotten a command not found error.)

To remove a loaded module, do

Code:

su -
modprobe -r prism54
exit

What you can do is unload that module and load p54pci

Code:

su -
modprobe -r prism54
modprobe p54pci
exit

To prevent the module from loading at boot, you have to append a line reading blacklist prism54 to the file /etc/modprobe.d/blacklist.conf. You can do this with any text editor (though you need to open it with root privileges.) Or from the terminal

Code:

su -
echo "blacklist prism54" >> /etc/modprobe.d/blacklist.conf
exit

Note the two >>. It's very important. If you use just one, it will overwrite the file rather than add to the file.

**Jada32** · 01-05-2011

I don't know much about all the linux commands but I tried. Here is a copy of my terminal:

Code:

[jan@localhost /]$ su -
Password: 
[root@localhost ~]# modprobe -r prism54
[root@localhost ~]# modprobe p54pci
[root@localhost ~]# echo "blacklist prism54" >> /etc/modprobe.d/blacklist.conf
[root@localhost ~]# exit
logout
[jan@localhost /]$

I checked the hardware profile in PC Control center and it still lists the prism54 as the module: (last line)
Misc
Module: ‎prism54

**Jada32** · 01-05-2011

why do you put the commands on different lines? Is is important to type "exit?" What does the "su -" mean?

**reed9** · 01-05-2011

Can you post the output of

Code:

lsmod

The su - is to log you in as root. As far as I know, PCLinuxOS does't use susudo - Wikipedia, the free encyclopediado by default. The hyphen in that ensures the environment changes to root's. In many distros, system commands are not on a normal user's $PATH, so by doing this I know the command will run without having to worry about directing you to enter /usr/sbin/lspci or /sbin/lspci or whatnot. The exit logs you out of root and back to your user account.

The commands are on different lines in part for readability, in part for syntax. You can run a command as root as so

Code:

su -c 'amazing linux command'

But you could not do

Code:

su - 'amazing linux command'

That would try to log you in to the user account amazing linux command which presumably doesn't exist.

**Jada32** · 01-05-2011

Code:

[root@localhost /]# lsmod
Module                  Size  Used by
af_packet              14122  2 
prism54                42912  0 
snd_usb_audio          64903  0 
snd_hwdep               4802  1 snd_usb_audio
snd_usb_lib            13866  1 snd_usb_audio
ipv6                  222857  8 
binfmt_misc             5590  1 
loop                   10919  0 
dm_mod                 55938  0 
cpufreq_ondemand        7009  0 
cpufreq_conservative     8144  0 
cpufreq_powersave        698  0 
freq_table              3091  1 cpufreq_ondemand
speedstep_lib           3177  0 
ohci1394               22696  0 
sbp2                   16049  0 
ieee1394               69727  2 ohci1394,sbp2
fuse                   49640  2 
snd_cs46xx             67646  4 
gameport                8272  2 snd_cs46xx
thinkpad_acpi          56386  1 
snd_rawmidi            16323  2 snd_usb_lib,snd_cs46xx
rfkill                 13919  1 thinkpad_acpi
snd_ac97_codec         89701  1 snd_cs46xx
ac97_bus                 946  1 snd_ac97_codec
snd_seq_dummy           1266  0 
snd_seq_oss            22774  0 
snd_seq_midi_event      5464  1 snd_seq_oss
snd_seq                40753  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device          5214  4 snd_rawmidi,snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss            29040  0 
snd_pcm                58856  4 snd_usb_audio,snd_cs46xx,snd_ac97_codec,snd_pcm_oss
snd_timer              15794  2 snd_seq,snd_pcm
pcmcia                 26801  0 
snd_mixer_oss          11096  2 snd_pcm_oss
snd                    46351  22 snd_usb_audio,snd_hwdep,snd_usb_lib,snd_cs46xx,thinkpad_acpi,snd_rawmidi,snd_ac97_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
ppdev                   4676  0 
nsc_ircc               11363  0 
led_class               2692  1 thinkpad_acpi
yenta_socket           17237  3 
parport_pc             26665  0 
soundcore               5680  2 snd
i2c_piix4               7524  0 
shpchp                 23804  0 
irda                   91727  1 nsc_ircc
sr_mod                 11640  0 
video                  17141  0 
rsrc_nonstatic          7981  1 yenta_socket
battery                 8252  0 
ac                      2650  0 
nvram                   5352  1 thinkpad_acpi
output                  1735  1 video
pcspkr                  1382  0 
rtc_cmos                6929  0 
crc_ccitt               1311  1 irda
floppy                 44968  0 
parport                28094  2 ppdev,parport_pc
pcmcia_core            28857  3 pcmcia,yenta_socket,rsrc_nonstatic
pci_hotplug            22676  1 shpchp
snd_page_alloc          6506  2 snd_cs46xx,snd_pcm
sg                     21491  0 
e100                   24772  0 
i2c_core               18110  1 i2c_piix4
uhci_hcd               16806  0 
cdrom                  28716  1 sr_mod
evdev                   6341  12 
processor              29811  1 
thermal                10903  0 
button                  4713  0 
mii                     3885  1 e100
usbcore               124336  4 snd_usb_audio,snd_usb_lib,uhci_hcd
ata_generic             2315  0 
ide_pci_generic         2306  0 
pata_acpi               2303  0 
piix                    4019  0 
ide_gd_mod             19349  0 
ide_core               85822  3 ide_pci_generic,piix,ide_gd_mod
ahci                   29234  0 
ata_piix               18324  3 
libata                145448  4 ata_generic,pata_acpi,ahci,ata_piix
sd_mod                 27633  4 
scsi_mod              132396  5 sbp2,sr_mod,sg,libata,sd_mod
crc_t10dif              1195  1 sd_mod
ext4                  266257  2 
jbd2                   64781  1 ext4
crc16                   1303  1 ext4

**Jada32** · 01-05-2011

I noticed that I also have a folder called "modprobe.preload.d" also in /etc. What is this for?

**reed9** · 01-05-2011

It's another location to specify modules to load at boot.

When you did

Code:

modprobe -r prism54

Did it give any errors?

Just to be clear, you've added the blacklist line to /etc/modprobe.d/blacklist.conf, right? And on reboot, prism54 is still loading?

I believe that if another module loads prism54 or if it has an alias, blacklisting like that will not work. We can get around it though. Add this line to /etc/modprobe.d/blacklist.conf

Code:

install prism54 /bin/true

Thread Tools

Display

prism54 card driver

Posting Permissions