我是新手,想尝试用 Mythbuntu 替换即将报废的 Tivo,但遇到了一些基本问题。经过一个周末的学习,我学到了一点东西,但总是遇到死胡同,我不知道该如何克服。
uname -a
Linux Shade 3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
初始行为:无线网络不会显示在“网络管理器”中?(是这个名字吗?我看到 GUI 右上角有一个图标(运行 XFCE 后显示),我单击该图标,插入以太网电缆后它会发生变化)。
lspci -nn
05:00.0 Network controller [0280]: Ralink corp. RT2800 802.11n PCI [1814:0601]
使用http://wireless.kernel.org/en/users/Documentation/FAQ主要是为了作为指南,我首先安装最新、最好的 compat-wireless for rt2x00 驱动程序。
当前行为:重新启动时,我在网络管理器中看到 SSID,然后尝试连接到我的网络,一个受 WPA2 保护的网络。系统提示我输入密码并输入。网络管理器图标旋转了大约一分钟,然后再次提示我输入密码。我知道我的密码正确,我从另一台 Windows 机器上删除并重试了我的密码信息,它按输入的方式工作。最后我点击了取消,SSID 全部从网络管理器中消失。
iwlist wlan0 scan
wlan0 No scan results
检查,嗯,不确定,dmesg
命令是我经常输入的东西,所以我把它添加到我的运行纸笔记中。看起来它是错误或通知或某种日志。左边的数字一直在变化,可能是经过的时间或其他什么。
dmesg | tail
[ 3321.935084] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0.
[ 3381.899236] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0.
[ 3441.855438] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0.
[ 3501.819676] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0.
[ 3561.779743] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0.
[ 3621.738350] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0.
[ 3681.697177] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0.
[ 3741.655319] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0.
[ 3801.613986] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0.
[ 3861.572981] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0.
Checked for "blocks", not really sure what this means, but I'm running on a newly built desktop
rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
也尝试使用 iw,但它没有返回任何内容。
sudo iw dev wlan0 scan
再次运行后,dmesg
我看到了相同类型的错误消息,每行前面的数字不同。我确信我搞砸了 wpa_supplicant:
sudo wpa_supplicant -Dwext -iwlan0 -ctest.conf
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
Failed to initialize control interface '/var/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.
我test.conf
看起来像是从 wpa_supplicant 网站的示例修改而来,因为我没有“wheel”组,所以我认为使用 sudo 组就没问题
# allow frontend (e.g., wpa_cli) to be used by all users in 'wheel' group
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=sudo
#
# home network; allow all valid ciphers
network={
ssid="Feroz"
scan_ssid=1
key_mgmt=WPA-PSK
psk="******"
}
我不太确定接下来该怎么做,因为据说 rt2x00 是受支持的,所以不知道发生了什么。我并不反对使用 ndis 来使用 Windows 驱动程序,但驱动程序被锁在 InstallShield 后面,我无法从安装文件中提取它们。
任何帮助都将不胜感激,这样我就不用再花 XX 个小时敲打石头了。