Finally, I emerged madwifi-ng and the WLAN card works. Add if I do the cmd
manually:
# /etc/init.d/net.ath0 start
the interface can get IP address from dhcp normally. But when I add the net.
ath0 to the
runlevel default and reboot, it cannot obtain the IP information with
dhcpcd... That means
I have to run the network restart script every time the system boots... Can
you give me some
advices about this?

# cat /etc/conf.d/net

# This blank configuration will automatically use DHCP for any net.*
# scripts in /etc/init.d.  To create a more complete configuration,
# please review /etc/conf.d/net.example and save your configuration
# in /etc/conf.d/net (this file :]!).

# config_eth0=( "dhcp" )
# dhcp_eth0="nonis nontp"

modules=( "iwconfig" )
key_xxxxxx="[1] cccc-cccc-cccc-cccc-cccc-cccc-cc key [1] enc restricted"
preferred_aps=( "xxxxxx" )

config_ath0=( "dhcp" )
dhcp_ath0="nonis nontp"

Thank you very much.
Zhou

-----邮件原件-----
发件人: Kan-I Jyo [mailto:[EMAIL PROTECTED] 
发送时间: 2008年6月24日 17:15
收件人: [email protected]
主题: Re: [gentoo-user] Atheros 5xxx driver in kernel 2.6.24-gentoo-r5

2008/6/24 Zhou Rui <[EMAIL PROTECTED]>:
> Thanks for your help, but I'm still puzzled with the madwifi driver and
the
> build-in ath5k driver. Does it mean
> if I choose to install a madwifi driver I can still use my 2.6.24 kernel?

Though ath5k driver will eventually replace the madwifi driver
according to the development team,  surely you can use your current
2.6.24 kernel with madwifi-ng package in portage.

However, as Dirk has mentioned, the driver may or may not work with
your card. So you may have to give it a try.

> But the problem is I cannot find the "non-hamradio
> WLAN" option in current kernel either...

If the "How to install madwifi" gentoo wiki page is what you are
reffering to, it may be a little bit out of date. You can take a look
on madwifi.org's web page for an up-to-date requirements.

http://madwifi.org/wiki/Requirements


-- 
Sincerely,

Jyo
-- 
[email protected] mailing list

--
[email protected] mailing list

Reply via email to