Hi Steve,
* Steve [EMAIL PROTECTED], Saturday, April 2, 2005, 6:21:18 PM:
I realised that the madwifi-driver package is masked and that this
indicates that I may experience problems, but I suspect I'm more
problems than others - considering that loads of people appear to have
the madwifi
I realised that the madwifi-driver package is masked and that this
indicates that I may experience problems, but I suspect I'm more
problems than others - considering that loads of people appear to have
the madwifi drivers working with other distributions. I've hunted on the
web for
Steve ([EMAIL PROTECTED]) scribbled:
Can anyone tell me if they've got the madwifi-drivers working under
Gentoo (with a 2.6 kernel)? If so - where do our approaches differ? What
kernel options are actually required? Do I really need all the modules
I've got in my autoloading (I don't care
On Saturday 02 April 2005 08:21, Steve wrote:
Noting that the first error is generated by the wlan module, following a
session with Google I suspected that my kernel needed wireless network
support... I used menuconfig and made these selections:
--
[*] Wan interfaces support
Comtrol
Grant wrote:
The only module you need to autoload is ath_pci. The kernel option
you must be missing is:
That is a surprise - I used the same card under FreeBSD and that
definitely also needed ATH_HAL - but I bow to your greater experience
with Gentoo... I'm guessing from the output from
Jason Cooper wrote:
Bad move. Exposing a single port to the internet is more than enough. I
also only expose a few ports (including ssh) to the net. My logs are
full of knucklehead script kiddies trying to get in through ssh. At a
minimum, disallow root login, and listen on a port other than 22.
Jason Cooper wrote:
The relevant portion of my '/etc/modules.autoload.d/kernel-2.6':
wlan
ath_hal
ath_pci
everything else autoloads from these three.
By any chance can you point me at documentation which explains what
facilities are presented by ath_hal and wlan (as a previous post
suggests
Steve ([EMAIL PROTECTED]) scribbled:
Jason Cooper wrote:
Bad move. Exposing a single port to the internet is more than enough. I
also only expose a few ports (including ssh) to the net. My logs are
full of knucklehead script kiddies trying to get in through ssh. At a
minimum, disallow
By any chance can you point me at documentation which explains what
facilities are presented by ath_hal and wlan (as a previous post
suggests these two aren't strictly necessary.) Is it possible that
ath_hal and wlan are loaded anyway as dependencies of ath_pci?
I think that's exactly what
Steve ([EMAIL PROTECTED]) scribbled:
While they didn't used to be (I'd misread WAN as Wireless LAN - Doah!)
but they are now... However I still get a (now single) error ath_pci:
Unknown symbol ieee80211_ioctl - about which I'm as unclear as I was
about the dozens of unknown symbols I saw
Jason Cooper ([EMAIL PROTECTED]) scribbled:
'/lib/modules/`uname-r`/' and then run depmaod -ae again just in case.
That should've been 'depmod -ae', sorry.
Cooper.
--
gentoo-user@gentoo.org mailing list
Grant wrote:
By any chance can you point me at documentation which explains what
facilities are presented by ath_hal and wlan (as a previous post
suggests these two aren't strictly necessary.) Is it possible that
ath_hal and wlan are loaded anyway as dependencies of ath_pci?
I think that's
Grant ([EMAIL PROTECTED]) scribbled:
By any chance can you point me at documentation which explains what
facilities are presented by ath_hal and wlan (as a previous post
suggests these two aren't strictly necessary.) Is it possible that
ath_hal and wlan are loaded anyway as dependencies
Jason Cooper wrote:
aha? In you kernel .config, what is CONFIG_KMOD set to? If set, it
allows the kernel to autoload modules as needed, for example, when they
are dependencies of ath_pci.ko ... If unset, and wlan.ko isn't listed
first in /etc/modules.autoload.d/kernel-2.6, this could be the
By any chance can you point me at documentation which explains what
facilities are presented by ath_hal and wlan (as a previous post
suggests these two aren't strictly necessary.) Is it possible that
ath_hal and wlan are loaded anyway as dependencies of ath_pci?
I think that's exactly
Steve ([EMAIL PROTECTED]) scribbled:
Jason Cooper wrote:
aha? In you kernel .config, what is CONFIG_KMOD set to? If set, it
allows the kernel to autoload modules as needed, for example, when they
are dependencies of ath_pci.ko ... If unset, and wlan.ko isn't listed
first in
Jason Cooper wrote:
Steve ([EMAIL PROTECTED]) scribbled:
While they didn't used to be (I'd misread WAN as Wireless LAN - Doah!)
but they are now... However I still get a (now single) error ath_pci:
Unknown symbol ieee80211_ioctl - about which I'm as unclear as I was
about the dozens of
Steve ([EMAIL PROTECTED]) scribbled:
Jason Cooper wrote:
Steve ([EMAIL PROTECTED]) scribbled:
While they didn't used to be (I'd misread WAN as Wireless LAN - Doah!)
but they are now... However I still get a (now single) error ath_pci:
Unknown symbol ieee80211_ioctl - about which I'm as
Jason Cooper wrote:
try:
# find /lib/modules/`uname -r`/ -name wlan.ko -print
'locate' is only accurate as of the last time you updated its database.
OK - I was just being lazy - which happened not to matter because I knew
my locate database was up-to-date.
[ I'd included the grep line for
19 matches
Mail list logo
