You are not logged in.
Since this is my first posting: I LOVE ARCH !!!!! No other distro installed that smoothely on my old laptop (Medion MD41700).
But:
I have to use ndiswrapper with my WLAN-card, which works fine. The problem is that I have blacklisted the prism54 module (I have to because it conflicts with the driver from ndiswrapper) in my /etc/rc.conf
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=(prism54)
#
# Modules to load at boot-up (in this order)
# - prefix a module with a ! to blacklist it
#
MODULES=(8139cp 8139too mii !prism54 ndiswrapper slhc ac97_bus snd-mixer-oss snd-pcm-oss snd-page-alloc snd-pcm snd-timer snd snd-ac97-codec snd-atiixp-modem snd-atiixp soundcore)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
but the module is still there after restart and I have to 'rmmod prism54'.
What have I done wrong ? *confused*
Any solutions ?
Thanks
Theo
Last edited by Theomachos (2007-08-13 19:21:07)
There is one thing even more vital to science than intelligent methods; and that is, the sincere desire to find out the truth, whatever it may be.
Charles S. Peirce
Offline
Try removing !prism54 from the MODULES= line.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Doesn't work
Prism54 is still there.
There is one thing even more vital to science than intelligent methods; and that is, the sincere desire to find out the truth, whatever it may be.
Charles S. Peirce
Offline
Perhaps driver is being loaded very early in the boot process. You could try removing autodetect from /etc/mkinitcpio.conf and re-installing the kernel. Just ensure that the modules needed for booting are listed in mkinitcpio.conf. In any case if things go wrong you could always boot with the fallback kernel.
Here is the link to the wiki http://wiki.archlinux.org/index.php/Mkinitcpio
---for there is nothing either good or bad, but only thinking makes it so....
Hamlet, W Shakespeare
Offline
Thank you !
Just added /etc/modprobe.conf (with a "blacklist prism54") to the files-section of mkinitcpio.conf -> WORKS
There is one thing even more vital to science than intelligent methods; and that is, the sincere desire to find out the truth, whatever it may be.
Charles S. Peirce
Offline