Did you load ndiswrapper manually before typing lsmod? ndiswrapper seems
to be loaded. Also mrv8k, Marvell wireless driver is loaded, this is a
module included in the dapper packages of linux-image since January, but
there were later changes in a lot of packages that may interact with the
automatic detection of hardware that is responsible for loading the
module at boot. Maybe this is the module conflicting with your
ndiswrapper-setup.
You can test this by adding to /etc/modprobe.d/blacklist the following
line "blacklist mrv8k". After this, do a reboot. If this is the
conflicting driver, ndiswrapper should be loaded automatically. If this
resolves your problem, the linux-restricted-modules-package is maybe not
the package responsible for your broken ndiswrapper-setup.
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Did you load ndiswrapper manually before typing lsmod? ndiswrapper seems
to be loaded. Also mrv8k, Marvell wireless driver is loaded, this is a
module included in the dapper packages of linux-image since January, but
there were later changes in a lot of packages that may interact with the
automatic detection of hardware that is responsible for loading the
module at boot. Maybe this is the module conflicting with your
ndiswrapper-setup.
You can test this by adding to /etc/modprobe. d/blacklist the following d-modules- package is maybe not
line "blacklist mrv8k". After this, do a reboot. If this is the
conflicting driver, ndiswrapper should be loaded automatically. If this
resolves your problem, the linux-restricte
the package responsible for your broken ndiswrapper-setup.
_______ _______ _______ _______ _______ _______ _______ _______ ___ messenger. yahoo.de
Telefonate ohne weitere Kosten vom PC zum PC: http://