[SATLUG] Wireless Driver Installation
j at jvpappas.net
Thu Jul 17 17:25:21 CDT 2008
On Wed, Jul 16, 2008 at 16:38, Andrew Pickens <wg5o at sbcglobal.net> wrote:
> "IIRC you need to have the kernel source (and headers?) installed, along
> module-assistant. AFAIK the kernel-dev package in Ubuntu ships with the
> config file present, so m-a (module assistant) can `make prepare` and
> whatnot. Once you have the kernel stuff in line, ..."
> I'm sorry, but my response to this one is, "Duhh..." I have no idea what to
> do about this one. It is Ubuntu 8.04, kernel 2.6.24-19, and that is all I
I don't have an ubuntu box running, but I think that if you install via
Synaptic the following packages (You may have to search for keywords as
kernel-devel & module-assistant
Those packages should get the functions you need in order properly compile.
> "1. The make command outputs for the driver (if you want to go this way
> rather than ndiswrapper)"
> The command I used was: /etc/network/rtl8185_linux_26.1010.0531.2006$
> The result was pretty long, but it ended like this:
> << SNIP >>
> make: ***
> Error 1
> make: ***
> [_module_/etc/network/rtl8185_linux_26.1010.0531.2006/rtl818x-0.1] Error 2
> make: Leaving directory `/usr/src/linux-headers-2.6.24-19-generic'
> make: *** [modules] Error 2
You should probably not be working in /etc/network, but rather in a proper
working directory (ie /home/andy/rtl8185_linux_26.1010.0531.2006/) Anyway,
installing kernel-devel and module-assistant will get us closer to proper
> "2. `ndiswrapper -l` to list the loaded modules for ndiswrapper
> This is appropriate to my current situation, since I have the Trendnet card
> installed. I get:
> andy at izzy:/etc$ ndiswrapper -l
> mrv8335 : driver installed
> device (11AB:1FAA) present
> net8185 : driver installed
> Where mrv8335 is the Trendnet driver. The result is exactly the same as
> returned by the built-in ndiswrapper (System, Administration, Windows
> Wireless Drivers).
Good. The GUI should use the underlying CLI commands. It is easier to
paste CLI output to this list than screen shots, so that is why I asked for
> "3. `lspci -knn` to list the PCI devices seen and the modules handling each
> The listing includes:
> 05:06.0 Ethernet controller : Marvell Technology Group Ltd. 88w8335
> [Libertas] 802.11b/g Wireless [11ab:1faa] (rev 03)
I assume the module listed for it is correct. If you trim output working on
the assumption that you know what we need, it is likely that we will miss
something. It is better to include the FULL output than to risk editing out
a seemingly unimportant detail that could ultimately end up assisting in the
resolution of your problem.
> "4. `lsmod` to list the loaded modules"
> The long list includes:
> Module Size Used by
> ndiswrapper 243872 0
See above discussion on selective editing of output, but regardless, we need
some more info. If things were correct, (AFAIK) the "Used By" listing
should be greater than zero, but we will press on, given that the device ID
on the lspci matches the device ID in ndiswrapper.
Since the device should be registered, we need the following:
1. `iwconfig` so that we can see if there is a wireless interface
availible to use
2. `ifconfig` so that we can see the ethernet interfaces on the system
Let's see where this gets us.
Thanks again for the attention.
When a frustrated person who appears to want to learn posts to this forum,
it is the responsibility for those that can help to do so, otherwise the
value of this forum decreases, and we would not want that. It is my
pleasure (and duty) to assist where I can. I agree that the state of linux
WiFi is unsat, but we can probably get this working, especially if it was
working in an earlier setup.
--- END NEW CONTENT ---
John Pappas wrote:
>> Don't know if this is OBE or not, but I have put in some feedback/ideas
>> On Fri, Jul 11, 2008 at 17:36, Andrew Pickens <wg5o at sbcglobal.net> wrote:
>>> So, here is the report. Some of you who attempted to help me may recall
>>> that I was trying to get WiFi working on Ubuntu 6.06 (Encore ENLWI-G3 PCI
>>> card), and we were out of ideas. So, as proposed, I hooked up an
>>> cable and up-graded to Ubuntu 8.04. That went well, but I was worse off,
>>> because I could never get the system to recognize the card, i.e. Network
>>> Settings doesn't see the card.
>>> I tired to use the down-loaded Linux driver, following the readme
>>> instructions, but I could never get it to compile successfully. There
>>> errors and I had no idea what to do.
>> IIRC you need to have the kernel source (and headers?) installed, along
>> module-assistant. AFAIK the kernel-dev package in Ubuntu ships with the
>> config file present, so m-a (module assistant) can `make prepare` and
>> whatnot. Once you have the kernel stuff in line, you can try running the
>> `make...` for the driver again. If you could send the errors, it makes it
>> MUCH easier to troubleshoot over email.
>>> Ubuntu 8.04 has ndiswrapper built in. I used it to load the Windows
>>> driver. That worked slick; said it was installed and hardware was
>>> But it didn't work.
>> "Doesn't/Didn't/Won't Work" are all diagnostically unuseful. More useful
>> would be the outputs of:
>> 1. The make command outputs for the driver (if you want to go this way
>> rather than ndiswrapper)
>> 2. `ndiswrapper -l` to list the loaded modules for ndiswrapper (if you
>> want to go this route rather than compiled driver)
>> 3. `lspci -knn` to list the PCI devices seen and the modules handling
>> each device
>> 4. `lsmod` to list the loaded modules
>> Those will get us much further along.
>> I installed my old Trendnet TWE-423PI card, and loaded its Windows driver.
>>> That didn't work either.
>> Again, see above discussion. I did not see it on TrendNet's Linux page (
>> http://www.trendnet.com/support/linux.htm) so it looks like NDIS wrapper
>> required for this one.
>> I give up. I'm going to switch to sewing.
>> Computers in general are hard, as the people who code/build them are not
>> perfect, and hence "challenges" are encountered. Even more difficult is
>> troubleshooting via email. Further, vendors that make drivers unavailible
>> (Binary/Proprietary/OSS, don't care) make Linux harder for some (ie this
>> occasion). All of this is further compounded with the complexity and
>> required to properly request assistance so that others who cannot
>> see/hear/telepath (verb for "use telepathy?") to garner the
>> errors/challenges/issues encountered.
>> In order to continue fostering adoption and general acceptance of Linux,
>> please understand I am trying to help you help us to help you ;) I am not
>> making any attempt to berate/demean/belittle you nor your efforts, but
>> rather guide the collection collection of information that will start us
>> your journey to a working install.
>> Andy Pickens
>> "Sometimes the magic works, sometimes it doesn't."
More information about the SATLUG