linux对什么芯片支持最好?

包含网卡/无线网的网络问题和ADSL/校园网/宽带拨号支持及代理/共享等网络使用问题
pengsir
帖子: 137
注册时间: 2015-07-24 8:29
系统: ubuntu

Re: linux对什么芯片支持最好?

#16

帖子 pengsir »

ls /lib
cpp libip4tc.so.0.1.0 modprobe.d
crda libip6tc.so.0 modules
discover libip6tc.so.0.1.0 modules-load.d
hdparm libipq.so.0 security
i386-linux-gnu libipq.so.0.0.0 startpar
ifupdown libiptc.so.0 systemd
init libiptc.so.0.0.0 terminfo
klibc-IpHGKKbZiB_yZ7GPagmQz2GwVAQ.so libxtables.so.10 udev
ld-linux.so.2 libxtables.so.10.0.0 x86_64-linux-gnu
libip4tc.so.0 lsb xtables


find / -name 'firmware'
/usr/src/linux-headers-3.16.0-4-amd64/include/config/firmware
/usr/src/linux-headers-3.16.0-4-amd64/include/config/prevent/firmware
/sys/class/firmware
/sys/firmware
/lib/modules/3.16.0-4-amd64/kernel/drivers/firmware

请问,解压后放置在什么地方?
头像
vickycq
帖子: 4507
注册时间: 2011-03-20 13:12
系统: Debian
来自: 山东省寿光县
联系:

Re: linux对什么芯片支持最好?

#17

帖子 vickycq »

标准的Ubuntu安装应该已经包含 linux-firmware 这个包。

你这张网卡需要的固件为 iwlwifi-5000-*.ucode

可以执行下面命令确认

代码: 全选

ls /lib/firmware | grep iwlwifi-5000
没输出表示没有。
若没有,从这里下载你对应版本的包 手动安装之 (sudo dpkg -i linux-firmware_*.deb)
http://packages.ubuntu.com/search?keywo ... ection=all

或者从
http://linuxwireless.org/attachments/en ... .11.tar.gz
http://linuxwireless.org/attachments/en ... 4.2.12.tgz
http://linuxwireless.org/attachments/en ... .5.1-1.tgz
下载三个版本的固件解压缩 将 iwlwifi-5000-*.ucode 拷贝到 /lib/firmware


优先选择第一种方法(安装deb),因为你貌似软件源配置有问题,先不去管它,先重点解决驱动问题。
Debian 中文论坛 - forums.debiancn.org
欢迎所有 Debian GNU/Linux 用户
pengsir
帖子: 137
注册时间: 2015-07-24 8:29
系统: ubuntu

Re: linux对什么芯片支持最好?

#18

帖子 pengsir »

是 debian哈,不是ubuntu.
头像
vickycq
帖子: 4507
注册时间: 2011-03-20 13:12
系统: Debian
来自: 山东省寿光县
联系:

Re: linux对什么芯片支持最好?

#19

帖子 vickycq »

pengsir 写了:今天货到了,附带光盘驱动,安装后win7下面成功搞定,请问ubuntu平台,如何使用?
pengsir 写了:是 debian哈,不是ubuntu.
你前面说了ubuntu的。说错了?
Debian 需要安装 firmware-iwlwifi。
先安装 firmware-iwlwifi 并重启试试。若还不行,需重复13楼的步骤,第二步去掉。

参考 https://wiki.debian.org/iwlwifi
Debian 中文论坛 - forums.debiancn.org
欢迎所有 Debian GNU/Linux 用户
pengsir
帖子: 137
注册时间: 2015-07-24 8:29
系统: ubuntu

Re: linux对什么芯片支持最好?

#20

帖子 pengsir »

# dmesg | grep iwl
[ 5.832451] iwlwifi 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 5.832493] iwlwifi 0000:02:00.0: irq 45 for MSI/MSI-X
[ 6.688231] iwlwifi 0000:02:00.0: firmware: direct-loading firmware iwlwifi-5000-5.ucode
[ 6.688291] iwlwifi 0000:02:00.0: loaded firmware version 8.83.5.1 build 33692 op_mode iwldvm
[ 6.886417] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUG disabled
[ 6.886419] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[ 6.886419] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
[ 6.886421] iwlwifi 0000:02:00.0: Detected Intel(R) WiFi Link 5100 AGN, REV=0x54
[ 6.886462] iwlwifi 0000:02:00.0: L1 Disabled - LTR Disabled
[ 6.987861] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'

# cat /var/log/syslog | grep iwl
Nov 2 19:44:21 hws kernel: [ 7.291929] iwlwifi 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
Nov 2 19:44:21 hws kernel: [ 7.291981] iwlwifi 0000:02:00.0: irq 46 for MSI/MSI-X
Nov 2 19:44:21 hws kernel: [ 7.322560] iwlwifi 0000:02:00.0: firmware: direct-loading firmware iwlwifi-5000-5.ucode
Nov 2 19:44:21 hws kernel: [ 7.322606] iwlwifi 0000:02:00.0: loaded firmware version 8.83.5.1 build 33692 op_mode iwldvm
Nov 2 19:44:21 hws kernel: [ 7.937405] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUG disabled
Nov 2 19:44:21 hws kernel: [ 7.937408] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
Nov 2 19:44:21 hws kernel: [ 7.937410] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
Nov 2 19:44:21 hws kernel: [ 7.937412] iwlwifi 0000:02:00.0: Detected Intel(R) WiFi Link 5100 AGN, REV=0x54
Nov 2 19:44:21 hws kernel: [ 7.937455] iwlwifi 0000:02:00.0: L1 Disabled - LTR Disabled
Nov 2 19:44:21 hws kernel: [ 8.005360] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
Nov 2 19:51:39 hws rc.local[538]: modprobe: FATAL: Module iwlwifi is in use.
Nov 2 19:51:39 hws kernel: [ 5.832451] iwlwifi 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
Nov 2 19:51:39 hws kernel: [ 5.832493] iwlwifi 0000:02:00.0: irq 45 for MSI/MSI-X
Nov 2 19:51:39 hws kernel: [ 6.688231] iwlwifi 0000:02:00.0: firmware: direct-loading firmware iwlwifi-5000-5.ucode
Nov 2 19:51:39 hws kernel: [ 6.688291] iwlwifi 0000:02:00.0: loaded firmware version 8.83.5.1 build 33692 op_mode iwldvm
Nov 2 19:51:39 hws kernel: [ 6.886417] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUG disabled
Nov 2 19:51:39 hws kernel: [ 6.886419] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
Nov 2 19:51:39 hws kernel: [ 6.886419] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
Nov 2 19:51:39 hws kernel: [ 6.886421] iwlwifi 0000:02:00.0: Detected Intel(R) WiFi Link 5100 AGN, REV=0x54
Nov 2 19:51:39 hws kernel: [ 6.886462] iwlwifi 0000:02:00.0: L1 Disabled - LTR Disabled
Nov 2 19:51:39 hws kernel: [ 6.987861] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
pengsir
帖子: 137
注册时间: 2015-07-24 8:29
系统: ubuntu

Re: linux对什么芯片支持最好?

#21

帖子 pengsir »

apt-get install firmware-iwlwifi
重启后。
iw dev wlan0 scan

TSF: 44377007236 usec (0d, 12:19:37)
freq: 2452
beacon interval: 100 TUs
capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
signal: -59.00 dBm
last seen: 0 ms ago
Information elements from Probe Response frame:
SSID: MyCharterWiFi99-2G
Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
DS Parameter set: channel 9
RSN: * Version: 1
* Group cipher: CCMP
* Pairwise ciphers: CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
ERP: <no flags>
Extended supported rates: 24.0 36.0 48.0 54.0
WMM: * Parameter version 1
* u-APSD
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
HT capabilities:
Capabilities: 0x11cc
HT20
SM Power Save disabled
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT RX MCS rate indexes supported: 0-15
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 9
* secondary channel offset: no secondary
* Wi-Fi Protected Setup State: 2 (Configured)
* Response Type: 3 (AP)
* UUID: 00000000-0000-1000-0000-04a151ba6a99
* Manufacturer: Netgear
* Model: WNDR3800
* Model Number: V1
* Serial Number: none
* Primary Device Type: 6-0050f204-1
* Device name: WNDR3800CH(Wireless AP)
* Config methods: Ethernet, Label,

家里的wifi可以被扫描出来。

iw wlan0 connect MyCharterWiFi99-2G 2452
这个命令没有报错。
但是,用火狐浏览器无法连接到任何url.
头像
vickycq
帖子: 4507
注册时间: 2011-03-20 13:12
系统: Debian
来自: 山东省寿光县
联系:

Re: linux对什么芯片支持最好?

#22

帖子 vickycq »

家里的wifi可以被扫描出来。
iw wlan0 connect MyCharterWiFi99-2G 2452
这个命令没有报错。
但是,用火狐浏览器无法连接到任何url.
没有安装/使用 NetworkManager?

断开无线连接,打开终端执行

代码: 全选

sudo tail -f /var/log/syslog
连接无线,将上面终端中刷出的信息 全部复制贴上来。

保持无线连接,在终端中执行

代码: 全选

sudo lshw -C network
sudo ifconfig -a
sudo iwconfig
sudo nmcli dev show
sudo cat /etc/resolv.conf
sudo route -nv
ping -c 3 127.0.0.1
ping -c 3 <网关地址,即无线路由器地址>
ping -c 3 114.114.114.114
ping -c 3 www.taobao.com
把结果全部复制贴上来
Debian 中文论坛 - forums.debiancn.org
欢迎所有 Debian GNU/Linux 用户
pengsir
帖子: 137
注册时间: 2015-07-24 8:29
系统: ubuntu

Re: linux对什么芯片支持最好?

#23

帖子 pengsir »

root@hws:/home/debian8# tail -f /var/log/syslog
Nov 3 09:30:34 hws kernel: [ 1871.198119] ata6.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 25 pio 16392 in
Nov 3 09:30:34 hws kernel: [ 1871.198119] res 51/04:00:00:14:eb/00:00:00:14:eb/20 Emask 0x1 (device error)
Nov 3 09:30:34 hws kernel: [ 1871.198123] ata6.00: status: { DRDY ERR }
Nov 3 09:30:37 hws kernel: [ 1873.283737] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov 3 09:30:37 hws kernel: [ 1873.283744] ata6.00: irq_stat 0x40000001
Nov 3 09:30:37 hws kernel: [ 1873.283752] sr 5:0:0:0: CDB:
Nov 3 09:30:37 hws kernel: [ 1873.283754] Get event status notification: 4a 01 00 00 10 00 00 00 08 00
Nov 3 09:30:37 hws kernel: [ 1873.283772] ata6.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 26 pio 16392 in
Nov 3 09:30:37 hws kernel: [ 1873.283772] res 51/04:00:00:14:eb/00:00:00:14:eb/20 Emask 0x1 (device error)
Nov 3 09:30:37 hws kernel: [ 1873.283776] ata6.00: status: { DRDY ERR }
Nov 3 09:30:39 hws kernel: [ 1875.540694] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov 3 09:30:39 hws kernel: [ 1875.540703] ata6.00: irq_stat 0x40000001
Nov 3 09:30:39 hws kernel: [ 1875.540712] sr 5:0:0:0: CDB:
Nov 3 09:30:39 hws kernel: [ 1875.540716] Get event status notification: 4a 01 00 00 10 00 00 00 08 00
Nov 3 09:30:39 hws kernel: [ 1875.540736] ata6.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 27 pio 16392 in
Nov 3 09:30:39 hws kernel: [ 1875.540736] res 51/04:00:00:14:eb/00:00:00:14:eb/20 Emask 0x1 (device error)
Nov 3 09:30:39 hws kernel: [ 1875.540742] ata6.00: status: { DRDY ERR }
Nov 3 09:30:39 hws ntpd_intres[1614]: host name not found: 1.debian.pool.ntp.org
Nov 3 09:30:41 hws kernel: [ 1877.848640] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov 3 09:30:41 hws kernel: [ 1877.848648] ata6.00: irq_stat 0x40000001
Nov 3 09:30:41 hws kernel: [ 1877.848656] sr 5:0:0:0: CDB:
Nov 3 09:30:41 hws kernel: [ 1877.848660] Get event status notification: 4a 01 00 00 10 00 00 00 08 00
Nov 3 09:30:41 hws kernel: [ 1877.848678] ata6.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 28 pio 16392 in
Nov 3 09:30:41 hws kernel: [ 1877.848678] res 51/04:00:00:14:eb/00:00:00:14:eb/20 Emask 0x1 (device error)
Nov 3 09:30:41 hws kernel: [ 1877.848683] ata6.00: status: { DRDY ERR }
Nov 3 09:30:43 hws kernel: [ 1879.902824] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov 3 09:30:43 hws kernel: [ 1879.902832] ata6.00: irq_stat 0x40000001
Nov 3 09:30:43 hws kernel: [ 1879.902840] sr 5:0:0:0: CDB:
Nov 3 09:30:43 hws kernel: [ 1879.902843] Get event status notification: 4a 01 00 00 10 00 00 00 08 00
Nov 3 09:30:43 hws kernel: [ 1879.902862] ata6.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 29 pio 16392 in
Nov 3 09:30:43 hws kernel: [ 1879.902862] res 51/04:00:00:14:eb/00:00:00:14:eb/20 Emask 0x1 (device error)
Nov 3 09:30:43 hws kernel: [ 1879.902867] ata6.00: status: { DRDY ERR }
Nov 3 09:30:45 hws kernel: [ 1881.937626] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov 3 09:30:45 hws kernel: [ 1881.937635] ata6.00: irq_stat 0x40000001
Nov 3 09:30:45 hws kernel: [ 1881.937644] sr 5:0:0:0: CDB:
Nov 3 09:30:45 hws kernel: [ 1881.937647] Get event status notification: 4a 01 00 00 10 00 00 00 08 00
Nov 3 09:30:45 hws kernel: [ 1881.937668] ata6.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 30 pio 16392 in
Nov 3 09:30:45 hws kernel: [ 1881.937668] res 51/04:00:00:14:eb/00:00:00:14:eb/20 Emask 0x1 (device error)
Nov 3 09:30:45 hws kernel: [ 1881.937673] ata6.00: status: { DRDY ERR }
Nov 3 09:30:47 hws kernel: [ 1883.984879] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov 3 09:30:47 hws kernel: [ 1883.984888] ata6.00: irq_stat 0x40000001
Nov 3 09:30:47 hws kernel: [ 1883.984896] sr 5:0:0:0: CDB:
Nov 3 09:30:47 hws kernel: [ 1883.984899] Get event status notification: 4a 01 00 00 10 00 00 00 08 00
Nov 3 09:30:47 hws kernel: [ 1883.984920] ata6.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio 16392 in
Nov 3 09:30:47 hws kernel: [ 1883.984920] res 51/04:00:00:14:eb/00:00:00:14:eb/20 Emask 0x1 (device error)
Nov 3 09:30:47 hws kernel: [ 1883.984926] ata6.00: status: { DRDY ERR }
Nov 3 09:30:49 hws kernel: [ 1886.033884] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov 3 09:30:49 hws kernel: [ 1886.033893] ata6.00: irq_stat 0x40000001
Nov 3 09:30:49 hws kernel: [ 1886.033901] sr 5:0:0:0: CDB:
Nov 3 09:30:49 hws kernel: [ 1886.033904] Get event status notification: 4a 01 00 00 10 00 00 00 08 00
Nov 3 09:30:49 hws kernel: [ 1886.033925] ata6.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 1 pio 16392 in
Nov 3 09:30:49 hws kernel: [ 1886.033925] res 51/04:00:00:14:eb/00:00:00:14:eb/20 Emask 0x1 (device error)
Nov 3 09:30:49 hws kernel: [ 1886.033930] ata6.00: status: { DRDY ERR }
Nov 3 09:30:51 hws kernel: [ 1888.079531] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov 3 09:30:51 hws kernel: [ 1888.079540] ata6.00: irq_stat 0x40000001
Nov 3 09:30:51 hws kernel: [ 1888.079548] sr 5:0:0:0: CDB:
Nov 3 09:30:51 hws kernel: [ 1888.079551] Get event status notification: 4a 01 00 00 10 00 00 00 08 00
Nov 3 09:30:51 hws kernel: [ 1888.079571] ata6.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 2 pio 16392 in
Nov 3 09:30:51 hws kernel: [ 1888.079571] res 51/04:00:00:14:eb/00:00:00:14:eb/20 Emask 0x1 (device error)
Nov 3 09:30:51 hws kernel: [ 1888.079577] ata6.00: status: { DRDY ERR }
Nov 3 09:30:53 hws kernel: [ 1890.127874] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov 3 09:30:53 hws kernel: [ 1890.127883] ata6.00: irq_stat 0x40000001
Nov 3 09:30:53 hws kernel: [ 1890.127892] sr 5:0:0:0: CDB:
Nov 3 09:30:53 hws kernel: [ 1890.127895] Get event status notification: 4a 01 00 00 10 00 00 00 08 00
Nov 3 09:30:53 hws kernel: [ 1890.127915] ata6.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 3 pio 16392 in
Nov 3 09:30:53 hws kernel: [ 1890.127915] res 51/04:00:00:14:eb/00:00:00:14:eb/20 Emask 0x1 (device error)
Nov 3 09:30:53 hws kernel: [ 1890.127920] ata6.00: status: { DRDY ERR }
Nov 3 09:30:55 hws kernel: [ 1892.180355] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov 3 09:30:55 hws kernel: [ 1892.180363] ata6.00: irq_stat 0x40000001
Nov 3 09:30:55 hws kernel: [ 1892.180370] sr 5:0:0:0: CDB:
Nov 3 09:30:55 hws kernel: [ 1892.180373] Get event status notification: 4a 01 00 00 10 00 00 00 08 00
Nov 3 09:30:55 hws kernel: [ 1892.180391] ata6.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 4 pio 16392 in
Nov 3 09:30:55 hws kernel: [ 1892.180391] res 51/04:00:00:14:eb/00:00:00:14:eb/20 Emask 0x1 (device error)
Nov 3 09:30:55 hws kernel: [ 1892.180396] ata6.00: status: { DRDY ERR }
Nov 3 09:30:57 hws kernel: [ 1894.227457] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov 3 09:30:57 hws kernel: [ 1894.227465] ata6.00: irq_stat 0x40000001
Nov 3 09:30:57 hws kernel: [ 1894.227473] sr 5:0:0:0: CDB:
Nov 3 09:30:57 hws kernel: [ 1894.227476] Get event status notification: 4a 01 00 00 10 00 00 00 08 00
Nov 3 09:30:57 hws kernel: [ 1894.227494] ata6.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 5 pio 16392 in
Nov 3 09:30:57 hws kernel: [ 1894.227494] res 51/04:00:00:14:eb/00:00:00:14:eb/20 Emask 0x1 (device error)
Nov 3 09:30:57 hws kernel: [ 1894.227499] ata6.00: status: { DRDY ERR }
Nov 3 09:30:59 hws ntpd_intres[1614]: host name not found: 2.debian.pool.ntp.org
Nov 3 09:31:00 hws kernel: [ 1896.278368] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov 3 09:31:00 hws kernel: [ 1896.278375] ata6.00: irq_stat 0x40000001
Nov 3 09:31:00 hws kernel: [ 1896.278382] sr 5:0:0:0: CDB:
Nov 3 09:31:00 hws kernel: [ 1896.278385] Get event status notification: 4a 01 00 00 10 00 00 00 08 00
Nov 3 09:31:00 hws kernel: [ 1896.278401] ata6.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 6 pio 16392 in
Nov 3 09:31:00 hws kernel: [ 1896.278401] res 51/04:00:00:14:eb/00:00:00:14:eb/20 Emask 0x1 (device error)
Nov 3 09:31:00 hws kernel: [ 1896.278405] ata6.00: status: { DRDY ERR }
Nov 3 09:31:02 hws kernel: [ 1898.366232] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov 3 09:31:02 hws kernel: [ 1898.366240] ata6.00: irq_stat 0x40000001
Nov 3 09:31:02 hws kernel: [ 1898.366248] sr 5:0:0:0: CDB:
Nov 3 09:31:02 hws kernel: [ 1898.366251] Get event status notification: 4a 01 00 00 10 00 00 00 08 00
Nov 3 09:31:02 hws kernel: [ 1898.366270] ata6.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 7 pio 16392 in
Nov 3 09:31:02 hws kernel: [ 1898.366270] res 51/04:00:00:14:eb/00:00:00:14:eb/20 Emask 0x1 (device error)
Nov 3 09:31:02 hws kernel: [ 1898.366275] ata6.00: status: { DRDY ERR }
Nov 3 09:31:04 hws kernel: [ 1900.647082] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov 3 09:31:04 hws kernel: [ 1900.647091] ata6.00: irq_stat 0x40000001
Nov 3 09:31:04 hws kernel: [ 1900.647100] sr 5:0:0:0: CDB:
Nov 3 09:31:04 hws kernel: [ 1900.647103] Get event status notification: 4a 01 00 00 10 00 00 00 08 00
Nov 3 09:31:04 hws kernel: [ 1900.647123] ata6.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 8 pio 16392 in
Nov 3 09:31:04 hws kernel: [ 1900.647123] res 51/04:00:00:14:eb/00:00:00:14:eb/20 Emask 0x1 (device error)
Nov 3 09:31:04 hws kernel: [ 1900.647129] ata6.00: status: { DRDY ERR }
Nov 3 09:31:06 hws kernel: [ 1902.958350] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov 3 09:31:06 hws kernel: [ 1902.958358] ata6.00: irq_stat 0x40000001
Nov 3 09:31:06 hws kernel: [ 1902.958367] sr 5:0:0:0: CDB:
Nov 3 09:31:06 hws kernel: [ 1902.958370] Get event status notification: 4a 01 00 00 10 00 00 00 08 00
Nov 3 09:31:06 hws kernel: [ 1902.958391] ata6.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 9 pio 16392 in
Nov 3 09:31:06 hws kernel: [ 1902.958391] res 51/04:00:00:14:eb/00:00:00:14:eb/20 Emask 0x1 (device error)
Nov 3 09:31:06 hws kernel: [ 1902.958396] ata6.00: status: { DRDY ERR }
Nov 3 09:31:08 hws kernel: [ 1905.033610] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov 3 09:31:08 hws kernel: [ 1905.033618] ata6.00: irq_stat 0x40000001
Nov 3 09:31:08 hws kernel: [ 1905.033625] sr 5:0:0:0: CDB:
Nov 3 09:31:08 hws kernel: [ 1905.033628] Get event status notification: 4a 01 00 00 10 00 00 00 08 00
Nov 3 09:31:08 hws kernel: [ 1905.033647] ata6.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 10 pio 16392 in
Nov 3 09:31:08 hws kernel: [ 1905.033647] res 51/04:00:00:14:eb/00:00:00:14:eb/20 Emask 0x1 (device error)
Nov 3 09:31:08 hws kernel: [ 1905.033652] ata6.00: status: { DRDY ERR }
^C
root@hws:/home/debian8# lshw -C network
*-network
description: Wireless interface
product: WiFi Link 5100
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: wlan0
version: 00
serial: 00:21:5d:26:c1:10
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=3.16.0-4-amd64 firmware=8.83.5.1 build 33692 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn
resources: irq:46 memory:f7d00000-f7d01fff
*-network
description: Ethernet interface
product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:03:00.0
logical name: eth0
version: 0c
serial: e0:3f:49:57:4b:d1
size: 10Mbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half ip=192.168.1.100 latency=0 link=no multicast=yes port=MII speed=10Mbit/s
resources: irq:42 ioport:e000(size=256) memory:f7c00000-f7c00fff memory:f0000000-f0003fff
root@hws:/home/debian8# ifconfig -a
eth0 Link encap:Ethernet HWaddr e0:3f:49:57:4b:d1
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:366 errors:0 dropped:0 overruns:0 frame:0
TX packets:366 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:34300 (33.4 KiB) TX bytes:34300 (33.4 KiB)

wlan0 Link encap:Ethernet HWaddr 00:21:5d:26:c1:10
inet6 addr: fe80::221:5dff:fe26:c110/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:51 errors:0 dropped:0 overruns:0 frame:0
TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:10965 (10.7 KiB) TX bytes:3645 (3.5 KiB)

root@hws:/home/debian8# iwconfig
eth0 no wireless extensions.

wlan0 IEEE 802.11abgn ESSID:"MyCharterWiFi99-2G"
Mode:Managed Frequency:2.447 GHz Access Point: 04:A1:51:BA:6A:99
Bit Rate=1 Mb/s Tx-Power=15 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=47/70 Signal level=-63 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:19 Missed beacon:0

lo no wireless extensions.

root@hws:/home/debian8# nmcli dev show
nmcli: error while loading shared libraries: libnm-util.so.2: cannot open shared object file: No such file or directory
root@hws:/home/debian8# cat /etc/resolv.conf
nameserver 192.168.1.1
root@hws:/home/debian8# route -nv
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
root@hws:/home/debian8# ping -c 3 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.031 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.035 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.026 ms

--- 127.0.0.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.026/0.030/0.035/0.007 ms
root@hws:/home/debian8# ping -c 3 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.100 icmp_seq=1 Destination Host Unreachable
From 192.168.1.100 icmp_seq=2 Destination Host Unreachable
From 192.168.1.100 icmp_seq=3 Destination Host Unreachable

--- 192.168.1.1 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2016ms
pipe 3
root@hws:/home/debian8# ping -c 3 114.114.114.114
PING 114.114.114.114 (114.114.114.114) 56(84) bytes of data.
From 192.168.1.100 icmp_seq=1 Destination Host Unreachable
From 192.168.1.100 icmp_seq=2 Destination Host Unreachable
From 192.168.1.100 icmp_seq=3 Destination Host Unreachable

--- 114.114.114.114 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2014ms
pipe 3
pengsir
帖子: 137
注册时间: 2015-07-24 8:29
系统: ubuntu

Re: linux对什么芯片支持最好?

#24

帖子 pengsir »

我的B电脑安装了pci接口的wifi接收器,A电脑的网址 192.168.1.100 ,A电脑连接的无线路由器,这个无线路由器的地址是 192.168.1.1
B电脑上执行

ping -c 3 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.100 icmp_seq=1 Destination Host Unreachable
From 192.168.1.100 icmp_seq=2 Destination Host Unreachable
From 192.168.1.100 icmp_seq=3 Destination Host Unreachable

192.168.1.100连接了192.168.1.1 ,为何B电脑无法连接上它?
pengsir
帖子: 137
注册时间: 2015-07-24 8:29
系统: ubuntu

Re: linux对什么芯片支持最好?

#25

帖子 pengsir »

胜利在望了!
1。驱动顺利安装了
2。可以scan到ssid ,表明可以接收信号了
3。链接的命令无报错
iw wlan0 connect -w MyCharterWiFi99-2G
4。最可能的问题就是网络的设置了

我问了老外,
http://superuser.com/questions/995404/h ... 406#995406
按照他的做,还是有问题,请高手看看,如何写这种情况下的配置。
谢谢
pengsir
帖子: 137
注册时间: 2015-07-24 8:29
系统: ubuntu

Re: linux对什么芯片支持最好?

#26

帖子 pengsir »

问题解决了,最后是网络配置的问题。
请看

http://superuser.com/questions/995404/h ... 406#995406
回复