From: "Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>
To: Hulin Thibaud <hulin.thibaud@wanadoo.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Fwd: ndiswrapper]
Date: Mon, 21 Aug 2006 14:45:40 -0600 [thread overview]
Message-ID: <44EA1B74.3000702@wolfmountaingroup.com> (raw)
In-Reply-To: <44EA1335.9000004@wanadoo.fr>
Hulin Thibaud wrote:
> That's not the kernel of my distrib (Ubuntu Dapper). That's my own
> kernel compiled with the option -binary. So, I installed manually the
> .deb from kernel.org to sources, image, and headers. Maybe there is a
> problem of links, to headers by example ?
Looks that way. First thing it to get a stable kernel tree you can
build and boot from without ndiswrapper. Next is check their makefiles
for ndiswrapper.
I have never attempted to build it on Ubuntu, just Suse and RedHat so
there may be issues with this.
Jeff
>
>
>
> Jeff V. Merkey a écrit :
>
>> Hulin Thibaud wrote:
>>
>>> I rebuilt ndiswrapper 1.19 version. When I type make, I have these
>>> errors :
>>>
>>> /usr/src/kernel-headers-2.6.17.060815.dell/Ach/i386/Makefile:383
>>> /usr/src/kernel-headers-2.6.17.060815.dell/Ach/i386/Makefile.cpu :
>>> No file or folder of this type
>>> Not rules to built the target
>>>
>>> (I traduce from french)
>>>
>>> Jeff V. Merkey a écrit :
>>>
>>>> Hulin Thibaud wrote:
>>>>
>>>>> Hi !
>>>>> I wanted to write at the kernel-net list, but that don't works.
>>>>> I updated my kernel and compiled it to 2.6.17, but now, ndiswrapper
>>>>> don't recognize my dongle Thomson XG-1500A.
>>>>> What can I do ?
>>>>> Thanks you very much,
>>>>> Thibaud.
>>>>>
>>>>>
>>>>> -
>>>>> To unsubscribe from this list: send the line "unsubscribe
>>>>> linux-kernel" in
>>>>> the body of a message to majordomo@vger.kernel.org
>>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>>> Please read the FAQ at http://www.tux.org/lkml/
>>>>>
>>>> Use the .19 ndiswrapper and try rebuilding.
>>>> Jeff
>>>>
>>>>
>>>
>>>
>> Sounds like the kernel includes and sources are not fully installed.
>> Don't rely on stock kernels for any of the distros, go the the
>> provider and get the kernel andall the header sources.
>>
>> Jeff
>>
>>
>
>
prev parent reply other threads:[~2006-08-21 20:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 15:27 [Fwd: ndiswrapper] Hulin Thibaud
2006-08-21 16:21 ` Jeff V. Merkey
2006-08-21 16:06 ` Hulin Thibaud
2006-08-21 17:00 ` Jeff V. Merkey
2006-08-21 20:10 ` Hulin Thibaud
2006-08-21 20:45 ` Jeff V. Merkey [this message]
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=44EA1B74.3000702@wolfmountaingroup.com \
--to=jmerkey@wolfmountaingroup.com \
--cc=hulin.thibaud@wanadoo.fr \
--cc=linux-kernel@vger.kernel.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