• Willkommen im Linux Club - dem deutschsprachigen Supportforum für GNU/Linux. Registriere dich kostenlos, um alle Inhalte zu sehen und Fragen zu stellen.

WLAN mit Medion MD 40100

susehase

Newbie
Ich habe einen Medion MD 40100-Laptop. Ich hatte mein WLAN bereits einmal mit SuSe 10.2 und der Anleitung unter http://linuxwiki.de/LinuxHardware/NoteBooks/Medion MD 40100 eingerichtet und es hat auch funktioniert. Da ich eine neue Festplatte eingebaut habe und alles neu unter 10.3 installiert habe, hab ichs wieder ausprobiert, aber leider klappt es nicht mehr. Zwar funktioniert das mit der LED etc. alles, aber irgendwie spinnt die Konfiguration der Netzwerkkarte. Wenn ich
Code:
iwconfig eth1
eingebe, kommt meistens:
Code:
eth1      no wireless extensions.
. Woran könnte das liegen? Wenn ich
Code:
dmesg
eingebe, kommt zum Schluss folgendes:
Code:
eth1: resetting device...
eth1: uploading firmware...
eth1: firmware version: 1.0.4.3
eth1: firmware upload complete
eth1: interface reset complete
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
audit(1205071160.827:3): audit_pid=3116 old=0 by auid=4294967295
NET: Registered protocol family 17
IA-32 Microcode Update Driver: v1.14a <tigran@aivazian.fsnet.co.uk>
ip6_tables: (C) 2000-2006 Netfilter Core Team
ip_tables: (C) 2000-2006 Netfilter Core Team
JBD: barrier-based sync failed on dm-0 - disabling barriers
bootsplash: status on console 0 changed to on
eth0: no IPv6 routers present
NET: Registered protocol family 4
NET: Registered protocol family 3
NET: Registered protocol family 5
eth1: timeout waiting for mgmt response 250, triggering device
eth1: timeout waiting for mgmt response 225, triggering device
eth1: timeout waiting for mgmt response 200, triggering device
eth1: timeout waiting for mgmt response 175, triggering device
eth1: timeout waiting for mgmt response 150, triggering device
eth1: timeout waiting for mgmt response 125, triggering device
eth1: timeout waiting for mgmt response 100, triggering device
eth1: timeout waiting for mgmt response 75, triggering device
eth1: timeout waiting for mgmt response 50, triggering device
eth1: timeout waiting for mgmt response 25, triggering device
eth1: timeout waiting for mgmt response
eth1: timeout waiting for mgmt response 250, triggering device
eth1: timeout waiting for mgmt response 225, triggering device
eth1: timeout waiting for mgmt response 200, triggering device
eth1: timeout waiting for mgmt response 175, triggering device
eth1: timeout waiting for mgmt response 150, triggering device
eth1: timeout waiting for mgmt response 125, triggering device
eth1: timeout waiting for mgmt response 100, triggering device
eth1: timeout waiting for mgmt response 75, triggering device
eth1: timeout waiting for mgmt response 50, triggering device
eth1: timeout waiting for mgmt response 25, triggering device
eth1: timeout waiting for mgmt response
eth1: timeout waiting for mgmt response 250, triggering device
eth1: timeout waiting for mgmt response 225, triggering device
eth1: timeout waiting for mgmt response 200, triggering device
eth1: timeout waiting for mgmt response 175, triggering device
eth1: timeout waiting for mgmt response 150, triggering device
eth1: timeout waiting for mgmt response 125, triggering device
eth1: timeout waiting for mgmt response 100, triggering device
eth1: timeout waiting for mgmt response 75, triggering device
eth1: timeout waiting for mgmt response 50, triggering device
eth1: timeout waiting for mgmt response 25, triggering device
eth1: timeout waiting for mgmt response
eth1: timeout waiting for mgmt response 250, triggering device
eth1: timeout waiting for mgmt response 225, triggering device
eth1: timeout waiting for mgmt response 200, triggering device
eth1: timeout waiting for mgmt response 175, triggering device
eth1: timeout waiting for mgmt response 150, triggering device
eth1: timeout waiting for mgmt response 125, triggering device
eth1: timeout waiting for mgmt response 100, triggering device
eth1: timeout waiting for mgmt response 75, triggering device
eth1: timeout waiting for mgmt response 50, triggering device
eth1: timeout waiting for mgmt response 25, triggering device
eth1: timeout waiting for mgmt response
eth1: mgmt tx queue is still full
eth1: mgmt tx queue is still full
...........(geht immer so weiter)

[/code]
 

whois

Ultimate Guru
Hi

Bitte mal folgendes Ergebnis als root aus der Konsole ins Forum stellen.

Code:
hwinfo  --wlan
Code:
ifconfig

cu
 
OP
S

susehase

Newbie
Das kam raus:

Code:
hwinfo  --wlan
20: PCI 306.0: 0282 WLAN controller
  [Created at pci.301]
  UDI: /org/freedesktop/Hal/devices/pci_1260_3890
  Unique ID: JNkJ.Z7e7L9Q6ex5
  Parent ID: 6NW+.c7JTK_YUBi2
  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:03:06.0
  SysFS BusID: 0000:03:06.0
  Hardware Class: network
  Model: "Z-Com XG-600 and clones Wireless Adapter"
  Vendor: pci 0x1260 "Intersil Corporation"
  Device: pci 0x3890 "ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow]"
  SubVendor: pci 0x17cf "Z-Com, Inc."
  SubDevice: pci 0x0014 "XG-600 and clones Wireless Adapter"
  Revision: 0x01
  Driver: "prism54"
  Driver Modules: "prism54"
  Device File: eth1
  Features: WLAN
  Memory Range: 0xd2004000-0xd2005fff (rw,non-prefetchable)
  IRQ: 19 (no events)
  HW Address: 02:10:91:23:78:ba
  Link detected: yes
  Module Alias: "pci:v00001260d00003890sv000017CFsd00000014bc02sc80i00"
  Driver Info #0:
    Driver Status: p54pci is active
    Driver Activation Cmd: "modprobe p54pci"
  Driver Info #1:
    Driver Status: prism54 is active
    Driver Activation Cmd: "modprobe prism54"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #8 (PCI bridge)
und
Code:
ifconfig
eth0      Protokoll:Ethernet  Hardware Adresse 00:0A:E4:02:96:95
          inet Adresse:192.168.2.101  Bcast:255.255.255.255  Maske:255.255.255.0
          inet6 Adresse: fe80::20a:e4ff:fe02:9695/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:163029 errors:0 dropped:0 overruns:0 frame:0
          TX packets:155649 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 Sendewarteschlangenlänge:1000
          RX bytes:203251198 (193.8 Mb)  TX bytes:12518052 (11.9 Mb)
          Interrupt:21 Basisadresse:0xc800

eth1      Protokoll:Ethernet  Hardware Adresse 02:10:91:23:78:BA
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 Sendewarteschlangenlänge:1000
          RX bytes:0 (0.0 b)  TX bytes:168 (168.0 b)
          Interrupt:19 Basisadresse:0x4000

lo        Protokoll:Lokale Schleife
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:768 errors:0 dropped:0 overruns:0 frame:0
          TX packets:768 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 Sendewarteschlangenlänge:0
          RX bytes:46304 (45.2 Kb)  TX bytes:46304 (45.2 Kb)
 
Oben