Randy <abuse@127.0.0.1> writes:
>Unruh wrote:
>> Randy <abuse@127.0.0.1> writes:
>>
>>
>>>Ed wrote:
>>>
>>>> Is there ANY distribution or version of Linux that will recognize and
>>>>utilize the Linksys WPC54G wireless access card without going through
>>>>special hurdles, etc?
>>>>
>>>>
>>>> Ed
>>
>>
>>>No.
>>>FC3:
>>>ndiswrapper did work...until I used yum and updated then it stopped working
>>
>>
>> ndiswrapper must be taylored to the kernel you use. Yes, you have to remake
>> ndiswrapper for the kernel you have.
>Yes, but I didn't know this at the time and nobody told me anything when
>I asked.
>They were too busy flaming trolls.
>>
>>
>>>I am now thinking that I have to re-make it with new kernel for it to work.
>>>Mandrake:
>>>ndiswrapper came in a package... modprobe didn't find it, so it never
>>>got installed
>>
>>
>> ??
>> modprobe ndiswrapper
>unknown blah blah ndiswrapper
>point is this command DIDN'T WORK
>> Or put it into /etc/modprobe.conf
>> wlan0 ndiswrapper
>>
>>
>>>debian:
>>>...... It didn't work and I can't remember why now.
>>
>>
>>>None of them will play a DVD. I got the package I needed but after
>>
>>
>> ?? YOu have a category problem. Wireless cards do not play dvds. They are
>> for connecting to networks. DVD players are another thing (mplayer, xine,
>> ogle,...) Note that NO distribution comes with libdecss installed (that is
>> the decryptor software) since the opensource version is possibly illegal in
>> the USA and the closed source ones cost money, and they cannot afford to
>> pay for it and then give you the OS for free.
>> Download it.
>>
>"None of them..." = FC3, mandrake and debian. not the NIC. I'm not that
>stupid, but thanks anyway.
>If you *read* the message I did "download it" and it crashed the OS.
>>
>>>installing it
>>>system crashed and hung. Only thing I could do was shut off the computer.
>>>Boot whined and bitched and didn't start again.
>>>I reinstalled FC3 this time (I forgot I needed and update disk because
>>>install program
>>>didn't work)
>>>make ndiswrapper and then installed driver then I shut down and finished
>>>the next day.
>>>Or so I thought NOW it will not recognize ndiswrapper at all.
>>
>>
>> recognize it? What does "recognize it" mean.
>#make install
>blah blah blah
>#ndiswrapper
>Unknown command.
There are two separate things. ndiswrapper, the program whose purpose is to
install the Windows drivers, and ndiswrapper the module.
After you install the module, you must run
depmods
to set up the module dependencies so modprobe can use them.
ndiswrapper, the program is usually placed eitehr into /usr/sbin or
/usr/local/sbin
Look in both places. for example you may well not have /usr/local/sbin on
your path as root.
You can find out by looking in teh Makefile to find out where it is being
installed.
The module gets installed in /lib/modules/modules*/kernel/....
where the final part depends.
cd to that directory and then do
find . -name ndiswrapper\*
to see where it was installed. If it is not installed you need to put it
there somewhere.
Eg
/lib/modules/2.6.8.1-25mdk/kernel/3rdparty/ndiswrapper/ndiswrapper.ko
on my system.
Note that after it is put there you need to do
depmods
>>
>>
>>>I asked questions in the groups but they were too busy flaming trolls to
>>>help me.
>>
>>
>> If this is an example of how you asked that is not surprising.
>this is my anger after the fact. I'm not asking for help now, Im telling
>someone what happened to me.
>>
>>
>>>this is my experience with Linux. I am not impressed.
|
Similar Threads
Linear Mode
