You are not logged in.
When I blacklist ndiswrapper in rc.conf (modules = (!ndiswrapper)) OR when blacklisting another module called b43
it always gives me a long error at boot, containing stuff like "call trace" it shows numbers blablabla and then "trace end" and it freezes there
I can't copy paste more information here sorry
Because I use an EXT4 partition, I needed to boot on the arch live cd and then mount the partition to be able to remove the bad line in rc.conf...
Now it works but why I can't blacklist something?
Sorry for my bad english
Offline
Any idea? why blacklisting a module gives me an error at boot? Should this module be removed in a different way?
Offline
To say the truth, I wanted to disable the default b43 driver for my wireless card. I prefer to use ndiswrapper, I get better transfer rates. Now it works using ndiswrapper, but I don't know if it gets in conlfict with the b43 driver, which is still there. Also this is an old pc, I don't know if a conflict could slow it down but it seems slower than before.
Offline
Ok I resolved that by typing
rmmod b43My mistake was to follow a ubuntu guide.. I was thinking that a module could be disabled at boot in rc.conf, but it seems that arch didn't like this.. I still don't know why
Offline