[SATLUG] Wireless Driver Installation
wg5o at sbcglobal.net
Wed Jul 16 16:38:41 CDT 2008
"Don't know if this is OBE or not, but I have put in some feedback/ideas
Actually, the post wasn't intended to be another request for help, but just a report on non-progress (after a lot of effort) for anyone interested. But, thank you for the comments and, since you offered, here is a response. I guess the sewing will have to wait.
"IIRC you need to have the kernel source (and headers?) installed, along with
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 know.
"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$ ./makedrv
The result was pretty long, but it ended like this:
/etc/network/rtl8185_linux_26.1010.0531.2006/rtl818x-0.1/r8180_core.c: In function ‘rtl8180_init’:
/etc/network/rtl8185_linux_26.1010.0531.2006/rtl818x-0.1/r8180_core.c:2953: error: ‘INIT_WORK’ undeclared (first use in this function)
/etc/network/rtl8185_linux_26.1010.0531.2006/rtl818x-0.1/r8180_core.c:3276: error: ‘SA_SHIRQ’ undeclared (first use in this function)
/etc/network/rtl8185_linux_26.1010.0531.2006/rtl818x-0.1/r8180_core.c:3276: warning: passing argument 2 of ‘request_irq’ from incompatible pointer type
/etc/network/rtl8185_linux_26.1010.0531.2006/rtl818x-0.1/r8180_core.c: In function ‘rtl8180_pci_probe’:
/etc/network/rtl8185_linux_26.1010.0531.2006/rtl818x-0.1/r8180_core.c:3960: error: implicit declaration of function ‘SET_MODULE_OWNER’
/etc/network/rtl8185_linux_26.1010.0531.2006/rtl818x-0.1/r8180_core.c:4031: error: ‘struct net_device’ has no member named ‘get_wireless_stats’
/etc/network/rtl8185_linux_26.1010.0531.2006/rtl818x-0.1/r8180_core.c: In function ‘rtl8180_pci_module_init’:
/etc/network/rtl8185_linux_26.1010.0531.2006/rtl818x-0.1/r8180_core.c:4156: error: implicit declaration of function ‘pci_module_init’
make: *** [/etc/network/rtl8185_linux_26.1010.0531.2006/rtl818x-0.1/r8180_core.o] 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
"2. `ndiswrapper -l` to list the loaded modules for ndiswrapper (if you
want to go this route rather than compiled driver)"
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).
"3. `lspci -knn` to list the PCI devices seen and the modules handling
The listing includes:
05:06.0 Ethernet controller : Marvell Technology Group Ltd. 88w8335 [Libertas] 802.11b/g Wireless [11ab:1faa] (rev 03)
"4. `lsmod` to list the loaded modules"
The long list includes:
Module Size Used by
ndiswrapper 243872 0
'"Doesn't/Didn't/Won't Work" are all diagnostically unuseful'
Sorry. It seems that, if you have a working driver, Ubuntu's Network Settings (System, Administration, Network) will show the network device. I had that to start with in 6.06, but haven't gotten that far with 8.04.
Thanks again for the attention.
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 Ethernet
>> 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 were
>> errors and I had no idea what to do.
> IIRC you need to have the kernel source (and headers?) installed, along with
> 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 present.
>> 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 is
> 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 vigor
> 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 on
> your journey to a working install.
> Andy Pickens
> "Sometimes the magic works, sometimes it doesn't."
More information about the SATLUG