public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] NDISWRAPPER
Date: Tue, 18 Jul 2006 13:23:43 -0700	[thread overview]
Message-ID: <5bdc1c8b0607181323ib507a9bp4afff9a5b4a684c9@mail.gmail.com> (raw)
In-Reply-To: <17CD9CE4C0FA574A8B29EF02D49B385D0F564E@srvexch-01.mcaschool.local>

On 7/18/06, Timothy A. Holmes <tholmes@mcaschool.net> wrote:
> Hi folks:
>
> I rebuilt my kernel the other day and my wireless nick suddenly stopped
> operating, I re-emerged NDISWRAPPER and followed the howto on the forum
> to re-install it
>
> Every time I do Modprobe ndiswrapper I get a fatal error saying that the
> module is not found
>
> I need to know were to go from here
>
> Thanks
>
> TIM
>

Hi Tim,
   I had this same problem the other day. In the end I think (I THINK)
that what I did to get it working was:

1) Compile, install and reboot into the new kernel 2.6.17-rt5 in my case
2) re-emerge ndiswrapper
3) Reinstall the Windows driver (ndiswrapper -i *.INF)
4) Check that the driver and hardware were present. (ndiswrapper -l)

IIRC at that point I could modprobe it again. I was confused as to why
I had to do all of that but it seemed to work for me.

HTH,
Mark
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-07-18 20:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-18 19:31 [gentoo-user] NDISWRAPPER Timothy A. Holmes
2006-07-18 20:07 ` Richard Fish
2006-07-18 20:23 ` Mark Knecht [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-18 20:43 Timothy A. Holmes
2007-04-20 17:48 [gentoo-user] ndiswrapper Matthew Daubenspeck
2007-04-20 22:30 ` Mick
     [not found]   ` <20070421160700.GM12275@sinclair>
2007-04-22 12:55     ` Mick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5bdc1c8b0607181323ib507a9bp4afff9a5b4a684c9@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox