Wlan Problem
Markus Schüttler
mschuettler at gmail.com
Do Okt 27 21:01:55 UTC 2011
Hi,
ich habe ein Wlan Problem seit einem update. Ich gebe erstmal
folgende Daten aus:
~$ lsmod | grep ip
ipw2100 66395 0
libipw 39896 1 ipw2100
lib80211 5046 1 libipw
multipath 6009 0
~$ dmesg | grep ip
[ 0.008009] Calibrating delay loop (skipped), value calculated using timer frequency.. 2790.89 BogoMIPS (lpj=5581788)
[ 0.181642] cpufreq-nforce2: No nForce2 chipset.
[ 0.224474] io scheduler anticipatory registered
[ 0.338885] i8042.c: Detected active multiplexing controller, rev 1.1.
[ 0.343557] device-mapper: multipath: version 1.1.0 loaded
[ 0.343561] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 1.256264] md: multipath personality registered for level -4
[ 1.418573] 8139cp 0000:02:01.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip, use 8139too
[ 43.057924] agpgart-intel 0000:00:00.0: Intel 855PM Chipset
[ 43.173475] type=1505 audit(1319744283.321:4): operation="profile_load" pid=542 name="/usr/lib/connman/scripts/dhclient-script"
[ 43.270724] found SMC SuperIO Chip (devid=0x7a rev=00 base=0x002e): LPC47N227
[ 43.400419] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2
[ 43.400425] ipw2100: Copyright(c) 2003-2006 Intel Corporation
[ 43.540682] [drm] radeon: 1 quad pipes, 1 Z pipes initialized.
[ 43.628188] ipw2100 0000:02:02.0: power state changed by ACPI to D0
[ 43.628201] ipw2100 0000:02:02.0: power state changed by ACPI to D0
[ 43.628214] ipw2100 0000:02:02.0: PCI INT A -> Link[LNKC] -> GSI 10 (level, low) -> IRQ 10
[ 43.628233] ipw2100 0000:02:02.0: power state changed by ACPI to D0
[ 43.628243] ipw2100 0000:02:02.0: power state changed by ACPI to D0
[ 43.628953] ipw2100: Detected Intel PRO/Wireless 2100 Network Connection
[ 43.628982] ipw2100 0000:02:02.0: firmware: requesting ipw2100-1.3.fw
[ 112.713175] type=1505 audit(1319744352.861:8): operation="profile_replace" pid=955 name="/usr/lib/connman/scripts/dhclient-script"
[ 3820.492429] ipw2100: Fatal interrupt. Scheduling firmware restart.
~$ lspci -nnk | grep -i net -A2
02:01.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10)
Kernel driver in use: 8139too
Kernel modules: 8139too, 8139cp
02:02.0 Network controller [0280]: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter [8086:1043] (rev 04)
Kernel driver in use: ipw2100
Kernel modules: ipw2100
~$ cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
lp
psmouse
sbp2
sr_mod
ipw2100
~$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 unassociated ESSID:off/any Nickname:"ipw2100"
Mode:Managed Channel=0 Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:16 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Wenn ich das richtig verstehe, wird die Wlan-Karte erkannt und auch geladen.
Sie findet aber nicht den Access-Point. Jetzt habe ich noch eine ziemlich
chaotische interfaces:
~$ cat /etc/network/interfaces
Beim Bootvorgang automatisch starten
#iface eth0 inet static
# address 192.168.1.12
# netmask 255.255.255.0
# gateway 192.168.1.1
## LAN interface (dynamisch)
auto eth0
# Beim Bootvorgang automatisch starten
iface eth0 inet dhcp
## LAN interface 2
# auto eth1
# iface eth1 inet dhcp
## LAN interface 3
#auto eth2
#iface eth2 inet dhcp
## LAN interface 4
#auto ath0
#iface ath0 inet dhcp
## WLAN interface (dynamisch)
auto wlan0
# Beim Bootvorgang automatisch starten
iface wlan0 inet dhcp
## WLAN interface (statisch)
#auto wlan0
# Beim Bootvorgang automatisch starten
#iface wlan0 inet static
# address 192.168.1.11
# netmask 255.255.255.0
# gateway 192.168.1.1
#
# wireless yes
# wireless_mode managed
# wireless_key 3450738743abefcd7932103356
# wireless_essid bolsena
Wo könnte der Fehler liegen. eth0 (LAN) funktioniert einwandfrei.
Gruss Markus
Mehr Informationen über die Mailingliste ubuntu-de