Strona 1 z 1

Bardzo kiepska praca karty USB TP-Link TL-WN822N

: 28 listopada 2014, 02:47
autor: Malice
Witam,
korzystam z w/w karty usb. Mam system na dual boocie - win7 i debian sid. Karta działa prawidłowo na win, natomiast na Debianie występuje problem - na początku śmiga(aczkolwiek wolniej niż na windzie), po czym po pewnym czasie przestaje praktycznie zupełnie(ale jest podłączona - coś ze sterownikiem).

background:
instalowałem kilka różnych systemów - CrunchBang Linux(remix debiana wheezy), xubuntu, gNewSense. Niestety - za każdym razem jest problem ze sterownikami sieciowymi. Mam dwa urządzenia do wifi - wbudowane i na USB. Oba nie działają poprawnie...

insight note: korzystałem z tej samej karty na lapku(teraz jestem na stacjonarce), i wiem, że na Ubuntu były jakieś problemy z driverem - podobno sam usypiał się(oszczędzanie energii → https://github.com/pvaret/rtl8192cu-fix ... /README.md ). Nie wiem jednak, jak skorzystać z tego fixa, bo nie mam w repo linux-headers*.

Spece:
Karta sieciowa jak w temacie. Wersja 3 - więc chip realteka.

Różne pliki:
&quot pisze: Linux Haskell-linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-2 (2014-11-06) x86_64 GNU/Linux
&quot pisze: amd64
&quot pisze: 00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
Subsystem: Hewlett-Packard Company Device 2a9c
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11)
Kernel driver in use: pcieport
00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11)
Subsystem: Device 003c:009c
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11)
Subsystem: Device 003c:009c
00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11)
Subsystem: Device 003c:009c
00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11)
Subsystem: Device 003c:009c
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11)
Subsystem: Device 003c:009c
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and Protocol Registers (rev 11)
Subsystem: Device 003c:009c
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
Subsystem: Hewlett-Packard Company Device 2a9c
Kernel driver in use: mei_me
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
Subsystem: Hewlett-Packard Company Device 2a9c
Kernel driver in use: ehci-pci
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
Subsystem: Hewlett-Packard Company Device 2a9c
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
Kernel driver in use: pcieport
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 06)
Kernel driver in use: pcieport
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 06)
Kernel driver in use: pcieport
00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 06)
Kernel driver in use: pcieport
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
Subsystem: Hewlett-Packard Company Device 2a9c
Kernel driver in use: ehci-pci
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation 5 Series Chipset LPC Interface Controller (rev 06)
Subsystem: Hewlett-Packard Company Device 2a9c
Kernel driver in use: lpc_ich
00:1f.2 RAID bus controller: Intel Corporation 82801 SATA Controller [RAID mode] (rev 06)
Subsystem: Hewlett-Packard Company Device 2a9c
Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
Subsystem: Hewlett-Packard Company Device 2a9c
Kernel driver in use: i801_smbus
01:00.0 VGA compatible controller: NVIDIA Corporation GT200 [GeForce GTX 260] (rev a1)
Subsystem: NVIDIA Corporation Device 0753
Kernel driver in use: nouveau
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)
Subsystem: Hewlett-Packard Company Device 2a9c
Kernel driver in use: r8169
03:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6315 Series Firewire Controller
Subsystem: Hewlett-Packard Company Device 2a9c
Kernel driver in use: firewire_ohci
04:00.0 Multimedia video controller: Conexant Systems, Inc. CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb (rev 04)
Subsystem: Avermedia Technologies Inc Device e139
Kernel driver in use: cx23885
05:00.0 Network controller: Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe
Subsystem: Lite-On Communications Inc Device 6632
Kernel driver in use: rt2800pci
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-Core Registers (rev 04)
Subsystem: Intel Corporation Device 8086
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 04)
Subsystem: Intel Corporation Device 8086
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 04)
Subsystem: Intel Corporation Device 8086
Kernel driver in use: i7core_edac
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 04)
Subsystem: Intel Corporation Device 8086
ff:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller (rev 04)
Subsystem: Intel Corporation Device 8086
ff:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Target Address Decoder (rev 04)
Subsystem: Intel Corporation Device 8086
ff:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Test Registers (rev 04)
Subsystem: Intel Corporation Device 8086
ff:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Control Registers (rev 04)
Subsystem: Intel Corporation Device 8086
ff:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Address Registers (rev 04)
Subsystem: Intel Corporation Device 8086
ff:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Rank Registers (rev 04)
Subsystem: Intel Corporation Device 8086
ff:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Thermal Control Registers (rev 04)
Subsystem: Intel Corporation Device 8086
ff:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Control Registers (rev 04)
Subsystem: Intel Corporation Device 8086
ff:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Address Registers (rev 04)
Subsystem: Intel Corporation Device 8086
ff:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Rank Registers (rev 04)
Subsystem: Intel Corporation Device 8086
ff:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Thermal Control Registers (rev 04)
Subsystem: Intel Corporation Device 8086
&quot pisze: 00:00.0 0600: 8086:d131 (rev 11)
00:03.0 0604: 8086:d138 (rev 11)
00:08.0 0880: 8086:d155 (rev 11)
00:08.1 0880: 8086:d156 (rev 11)
00:08.2 0880: 8086:d157 (rev 11)
00:08.3 0880: 8086:d158 (rev 11)
00:10.0 0880: 8086:d150 (rev 11)
00:10.1 0880: 8086:d151 (rev 11)
00:16.0 0780: 8086:3b64 (rev 06)
00:1a.0 0c03: 8086:3b3c (rev 06)
00:1b.0 0403: 8086:3b56 (rev 06)
00:1c.0 0604: 8086:3b42 (rev 06)
00:1c.2 0604: 8086:3b46 (rev 06)
00:1c.3 0604: 8086:3b48 (rev 06)
00:1c.5 0604: 8086:3b4c (rev 06)
00:1d.0 0c03: 8086:3b34 (rev 06)
00:1e.0 0604: 8086:244e (rev a6)
00:1f.0 0601: 8086:3b08 (rev 06)
00:1f.2 0104: 8086:2822 (rev 06)
00:1f.3 0c05: 8086:3b30 (rev 06)
01:00.0 0300: 10de:05ea (rev a1)
02:00.0 0200: 10ec:8168 (rev 03)
03:00.0 0c00: 1106:3403
04:00.0 0400: 14f1:8880 (rev 04)
05:00.0 0280: 1814:3090
ff:00.0 0600: 8086:2c51 (rev 04)
ff:00.1 0600: 8086:2c81 (rev 04)
ff:02.0 0600: 8086:2c90 (rev 04)
ff:02.1 0600: 8086:2c91 (rev 04)
ff:03.0 0600: 8086:2c98 (rev 04)
ff:03.1 0600: 8086:2c99 (rev 04)
ff:03.4 0600: 8086:2c9c (rev 04)
ff:04.0 0600: 8086:2ca0 (rev 04)
ff:04.1 0600: 8086:2ca1 (rev 04)
ff:04.2 0600: 8086:2ca2 (rev 04)
ff:04.3 0600: 8086:2ca3 (rev 04)
ff:05.0 0600: 8086:2ca8 (rev 04)
ff:05.1 0600: 8086:2ca9 (rev 04)
ff:05.2 0600: 8086:2caa (rev 04)
ff:05.3 0600: 8086:2cab (rev 04)
&quot pisze: Bus 002 Device 006: ID 0bda:0151 Realtek Semiconductor Corp. Mass Storage Device (Multicard Reader)
Bus 002 Device 005: ID 04b4:0101 Cypress Semiconductor Corp. Keyboard/Hub
Bus 002 Device 004: ID 1038:1361 Ideazon, Inc.
Bus 002 Device 003: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
&quot pisze: eth0 Link encap:Ethernet HWaddr 40:61:86:f2:9a:f5
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:1900 errors:0 dropped:0 overruns:0 frame:0
TX packets:1900 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:231654 (226.2 KiB) TX bytes:231654 (226.2 KiB)

wlan0 Link encap:Ethernet HWaddr 70:f1:a1:93:9f:fd
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)

wlan1 Link encap:Ethernet HWaddr e8:de:27:10:f3:e0
inet addr:192.168.1.103 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::eade:27ff:fe10:f3e0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2533 errors:0 dropped:0 overruns:0 frame:0
TX packets:2775 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3449358 (3.2 MiB) TX bytes:315085 (307.7 KiB)
&quot pisze: wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

wlan1 IEEE 802.11bgn ESSID:"linksys"
Mode:Managed Frequency:2.437 GHz Access Point: 00:25:9C:D3:2E:39
Bit Rate=7.2 Mb/s Tx-Power=20 dBm
Retry short limit:7 RTS thr=2347 B Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=42/70 Signal level=-68 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:1 Missed beacon:0
&quot pisze: # Generated by NetworkManager
search piatkowo.inotel.pl
nameserver 192.168.1.1
nameserver 62.21.99.94
nameserver 62.21.99.95
&quot pisze: # This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback
$ apt-cache policy firmware-realtek
firmware-realtek:
Installed: 0.43
Candidate: 0.43
Version table:
*** 0.43 0
500 http://ftp.pl.debian.org/debian/ unstable/non-free amd64 Packages
100 /var/lib/dpkg/status
Od siebie jeszcze tylko dodam, że łączę się do sieci która jest zabezpieczona kluczem WPA2 Personal.
Mam nadzieję, że rozwiązanie będzie w miarę proste i cross-platformowe(bo niedługo z chęcią bym się z Gentoo zmierzył), gdyż ciężko mi korzystać z Linuksa bez internetu...
Z góry dziękuję.

: 28 listopada 2014, 10:25
autor: navigator

: 28 listopada 2014, 14:40
autor: Malice
Dzięki za odpowiedź.
Ten drugi temat czytałem - nic nie pomogło, a gość sam zresztą w temacie napisał, że poddał się i zwrócił cacko do amazonu. Ja niestety możliwości takiej nie mam, a wolałbym, żeby to działało - tym bardziej, że na innym kompie, o dziwo, chodziło wszystko okej...
Z kolei pierwszy działa dla innych wersji mojego urządzenia - tych na firmware Atheros - a ja mam Realtek...

: 29 listopada 2014, 20:09
autor: Malice
Ktoś ma inne pomysły?
Czy gdybym ściągnął dkms, to mógłbym zrobić jakoś pakiet, który zastąpiłby linux-headers-generic? Wiem, że deb* ma własny(linux-headers-wersja), więc może zrobiłbym ten pakiet jako kopię tego debianowego i skompilowałbym w ten sposób? Boję się jedynie, że zrobienie tego rozwaliłoby mi system.