... has linux-restricted-modules been installed? On Fri, 21 Jul 2006 14:24:41 +1200 Nick Rout <[EMAIL PROTECTED]> wrote:
> > On Fri, 21 Jul 2006 12:44:06 +1200 > Nick Rout wrote: > > > > So where to from here? Do I need to do a modprobe because the correct > > > module isn't in the kernel? How would I know - how do I check? Or is > > > it time to move on to installing the madwifi drivers I have downloaded? > > > > Some further reading seems to suggest that in pcmcia devices will in > > fact show up on the pci bus (at least according to lspci anyway) so it > > may be entirely proper that the card shows in lspci. > > > > normally there is a base module and then modules for the various > > interfaces, like > > > > ath > > ath_pci > > ath_cs > > > > But I dunno where you get the ath_cs module from in this case. > > > OK Nick's wrong again. madwifi does not follow that pattern, from the > README: > > "There is only one driver included here; it supports PCI, miniPCI > and Cardbus devices - USB devices are currently not supported by > this driver! ... > ... > Using the driver > ================ > The driver should support any Atheros-based Cardbus or PCI device. > This version of the driver is managed and controlled by the usual > Linux tools (ifconfig, iwconfig, iwpriv) plus the wlanconfig ... > > First, run "modprobe ath_pci" or the equivalent using "insmod". When > the driver is successfully loaded it creates two devices, named > "wifi0" and "ath0"...." > > can you tell me what the following produces? > > cd /lib/modules > find|grep ath_pci > > This will find the full path to the module. Then use dpkg -S to find > which package it belongs to: > > dpkg -S /lib/modules/blah/blah/ath_pci.ko > > > > -- > Nick Rout <[EMAIL PROTECTED]> > >
