T-Sinus 154card

Gorden · 4 Feb. 2007

Guten Tag,
hab mir gestern mal SUSE Linux 10.1 draufgemacht mit KDE 3.5.1 Level a. Leider bekomme ich meine T-Sinus 154card nicht zum laufen. Wenn ich Ndiswrapper benutze und geb dann nediswrapper -l ein steht da invalid driver. So gibt es eine andere möglichkeit meine Karte doch noch zum laufen kriegen.
Meine Linux Kenntnise beschränken sich auf ein paar Monate Debian, also kein absoluter Anfänger.

Freecoffee · 4 Feb. 2007

Wie lautet die pciid? (/sbin/lspci)
Gleich die einmal ab mit http://ndiswrapper.sourceforge.net/mediawiki/index.php/List#T

Gorden · 4 Feb. 2007

00:00.0 Host bridge: VIA Technologies, Inc. P/KN266 Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP]
00:09.0 CardBus bridge: ENE Technology Inc CB1410 Cardbus Controller
00:0b.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
01:00.0 VGA compatible controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266]
02:00.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] (rev 01)

Das erscheint im Terminal wenn ich das eingebe!

Anonymous · 4 Feb. 2007

wären folgende Ausgaben:

Code:

/usr/sbin/hwinfo --wlan

find /lib/modules -name "*prism*"

find /lib/firmware -name "*isl*"

lsmod |grep prism

=> Ausgaben posten.

Greetz,

RM

Gorden · 4 Feb. 2007

Beim ersten:

Code:

14: PCI 200.0: 0282 WLAN controller
  [Created at pci.300]
  UDI: /org/freedesktop/Hal/devices/pci_1260_3890
  Unique ID: JNkJ.fsaVktW+224
  Parent ID: WL76.dMRXmYio445
  SysFS ID: /devices/pci0000:00/0000:00:09.0/0000:02:00.0
  SysFS BusID: 0000:02:00.0
  Hardware Class: network
  Model: "Accton ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow]"
  Hotplug: CardBus
  Socket: 0
  Vendor: pci 0x1260 "Intersil Corporation"
  Device: pci 0x3890 "ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow]"
  SubVendor: pci 0x1113 "Accton Technology Corporation"
  SubDevice: pci 0xb301
  Revision: 0x01
  Driver: "prism54"
  Device File: eth1
  Features: WLAN
  Memory Range: 0x22000000-0x22001fff (rw,non-prefetchable)
  IRQ: 11 (no events)
  Module Alias: "pci:v00001260d00003890sv00001113sd0000B301bc02sc80i00"
  Driver Info #0:
    Driver Status: prism54 is active
    Driver Activation Cmd: "modprobe prism54"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #3 (CardBus bridge)

Beim zweiten:

Code:

/lib/modules/2.6.16.27-0.6-default/kernel/drivers/net/wireless/prism54
/lib/modules/2.6.16.27-0.6-default/kernel/drivers/net/wireless/prism54/prism54.ko
/lib/modules/2.6.16.27-0.6-smp/kernel/drivers/net/wireless/prism54
/lib/modules/2.6.16.27-0.6-smp/kernel/drivers/net/wireless/prism54/prism54.ko
/lib/modules/2.6.16.27-0.6-xen/kernel/drivers/net/wireless/prism54
/lib/modules/2.6.16.27-0.6-xen/kernel/drivers/net/wireless/prism54/prism54.ko
/lib/modules/2.6.16.27-0.6-bigsmp/kernel/drivers/net/wireless/prism54
/lib/modules/2.6.16.27-0.6-bigsmp/kernel/drivers/net/wireless/prism54/prism54.ko

Beim dritten:
kommt sofort: heldch@linux-3rmp:~>

beim vierten:

Code:

prism54                64776  0
firmware_class         26112  2 prism54,pcmcia

Anonymous · 4 Feb. 2007

Laut der Ausgabe sollte die Karte mit dem Treiber prism54 laufen, der auch schon geladen ist.

Möglicherweise braucht die Karte aber eine Firmware.

OK, der Reihe nach:

0. Packe die Shellausgaben in CODE-Tags, dann sieht das übersichtlicher aus.

Auf "Edit" Deines letzten Postings klicken, die entsprechenden Ausgaben markieren und auf den Button "Code" klicken.

1. Die Firmware bekommst Du hier:

http://prism54.org/newdrivers.html

Du hast eine PCI-Karte, also Version 2.7.0.0 herunterladen und die arm-Datei in "isl3890" umbenennen und als _root_ in /lib/firmware kopieren.

2. Zwei Konsolen öffnen:

In der ersten:

Code:

su

Passwort

tail -f /var/log/messages

und laufen lassen.

In der zweiten:

Code:

su

Passwort

rmmod prism54

modprobe prism54

iwconfig

ifconfig

Ausgaben aus beiden Konsolen posten.

Greetz,

RM

Gorden · 5 Feb. 2007

Erste Konsole:

Code:

linux-3rmp:/home/heldch # tail -f /var/log/m
Feb  4 23:57:38 linux-3rmp kernel: eth1: mgm
Feb  4 23:57:38 linux-3rmp kernel: eth1: mgt                  err=-12
Feb  4 23:57:38 linux-3rmp kernel: eth1: mgm
Feb  4 23:57:38 linux-3rmp kernel: eth1: mgt                  err=-12
Feb  4 23:57:38 linux-3rmp kernel: eth1: mgm
Feb  4 23:57:39 linux-3rmp kernel: eth1: mgt
Feb  4 23:57:39 linux-3rmp kernel: eth1: mgt
Feb  4 23:57:39 linux-3rmp kernel: eth1: int
Feb  4 23:57:39 linux-3rmp kernel: prism54:                   RQ line too busy :(
Feb  4 23:58:45 linux-3rmp su: (to root) hel
Feb  4 23:59:23 linux-3rmp su: (to root) heldch on /dev/pts/4
Feb  4 23:59:32 linux-3rmp kernel: eth1: removing device
Feb  4 23:59:32 linux-3rmp kernel: Unloaded prism54 driver
Feb  4 23:59:32 linux-3rmp ifdown: Network interface is managed from NetworkManager
Feb  4 23:59:32 linux-3rmp ifdown: NetworkManager cannot be advised to take down an interface.
Feb  4 23:59:32 linux-3rmp ifdown: Set up another interface instead.
Feb  4 23:59:38 linux-3rmp kernel: Loaded prism54 driver, version 1.2
Feb  4 23:59:38 linux-3rmp kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
Feb  4 23:59:39 linux-3rmp kernel: eth1: resetting device...
Feb  4 23:59:39 linux-3rmp kernel: eth1: uploading firmware...
Feb  4 23:59:39 linux-3rmp kernel: prism54: request_firmware() failed for 'isl3890'
Feb  4 23:59:39 linux-3rmp kernel: eth1: could not upload firmware ('isl3890')
Feb  4 23:59:39 linux-3rmp kernel: eth1: islpci_reset: failure
Feb  4 23:59:49 linux-3rmp kernel: eth1: resetting device...
Feb  4 23:59:49 linux-3rmp kernel: eth1: uploading firmware...
Feb  4 23:59:49 linux-3rmp kernel: prism54: request_firmware() failed for 'isl3890'
Feb  4 23:59:49 linux-3rmp kernel: eth1: could not upload firmware ('isl3890')
Feb  4 23:59:49 linux-3rmp kernel: eth1: islpci_reset: failure

Zweite Konsole:

Code:

linux-3rmp:/home/heldch # rmmod prism54
linux-3rmp:/home/heldch # modprobe prism54
linux-3rmp:/home/heldch # iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

irda0     no wireless extensions.

sit0      no wireless extensions.

eth1      NOT READY!  ESSID:off/any
          Mode:Managed  Channel:0  Access Point: Not-Associated
          Tx-Power=31 dBm   Sensitivity=0/200
          Retry min limit:0   RTS thr=0 B   Fragment thr=0 B
          Encryption key: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

Anonymous · 5 Feb. 2007

Code:

Feb  4 23:59:39 linux-3rmp kernel: prism54: request_firmware() failed for 'isl3890'

Siehe Punkt 1.

Code:

ls -ls /lib/firmware

?

Dann fehlt auch noch die Ausgabe von

Code:

su

Passwort

ifconfig

Greetz,

RM

Gorden · 5 Feb. 2007

Code:

insgesamt 1002
  4 -rw-r--r-- 1 root root    137 2006-04-23 04:24 3CCFEM556.cis
  4 -rw-r--r-- 1 root root    134 2006-04-23 04:24 3CXEM556.cis
112 -rw-r--r-- 1 root root 114688 2006-04-23 05:04 BCM2033-FW.bin
  4 -rw-r--r-- 1 root root   3245 2006-04-23 05:04 BCM2033-MD.hex
412 -rw-r--r-- 1 root root 418352 2006-04-23 05:04 bfubase.frm
  4 -rw-r--r-- 1 root root    109 2006-04-23 04:24 COMpad2.cis
  4 -rw-r--r-- 1 root root     76 2006-04-23 04:24 COMpad4.cis
 96 -rw-r--r-- 1 root root  97652 2006-05-02 09:00 digiface_firmware.bin
 96 -rw-r--r-- 1 root root  97652 2006-05-02 09:00 digiface_firmware_rev11.bin
  4 -rw-r--r-- 1 root root    136 2006-04-23 04:24 DP83903.cis
  1 drwxr-xr-x 2 root root   1032 2007-02-03 14:50 ea
  4 -rw-r--r-- 1 root root     53 2006-04-23 04:24 E-CARD.cis
  1 drwxr-xr-x 2 root root   1080 2007-02-03 15:06 isdn
 32 -rw-r--r-- 1 root root  29024 2007-02-04 23:39 isl3890.arm
  4 -rw-r--r-- 1 root root    253 2006-04-23 04:24 LA-PCM.cis
  0 drwxr-xr-x 2 root root    144 2007-02-03 14:50 mixart
  4 -rw-r--r-- 1 root root    107 2006-04-23 04:24 MT5634ZLX.cis
 96 -rw-r--r-- 1 root root  97652 2006-05-02 09:00 multiface_firmware.bin
 96 -rw-r--r-- 1 root root  97652 2006-05-02 09:00 multiface_firmware_rev11.bin
  4 -rw-r--r-- 1 root root     54 2006-04-23 04:24 NE2K.cis
  4 -rw-r--r-- 1 root root    210 2006-04-23 04:24 PCMLM28.cis
  0 drwxr-xr-x 2 root root    208 2007-02-03 14:50 pcxhr
  4 -rw-r--r-- 1 root root     68 2006-04-23 04:24 PE-200.cis
  4 -rw-r--r-- 1 root root     74 2006-04-23 04:24 PE520.cis
  4 -rw-r--r-- 1 root root     86 2006-04-23 04:24 RS-COM-2P.cis
  4 -rw-r--r-- 1 root root     85 2006-04-23 04:24 tamarack.cis
  0 drwxr-xr-x 2 root root    464 2007-02-03 14:50 vx

ifconfig

Code:

eth0      Protokoll:Ethernet  Hardware Adresse 00:40:D0:46:87:4B
          inet Adresse:192.168.2.35  Bcast:192.168.2.255  Maske:255.255.255.0
          inet6 Adresse: fe80::240:d0ff:fe46:874b/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:108167 errors:0 dropped:0 overruns:0 frame:0
          TX packets:112697 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 Sendewarteschlangenlänge:1000
          RX bytes:47398040 (45.2 Mb)  TX bytes:45684959 (43.5 Mb)
          Interrupt:10 Basisadresse:0xe300

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:322 errors:0 dropped:0 overruns:0 frame:0
          TX packets:322 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 Sendewarteschlangenlänge:0
          RX bytes:21202 (20.7 Kb)  TX bytes:21202 (20.7 Kb)

Anonymous · 5 Feb. 2007

Code:

 32 -rw-r--r-- 1 root root  29024 2007-02-04 23:39 isl3890.arm

Mache mal das .arm am Ende weg.

Danach auf ein Neues (die 2 Konsolen).

Greetz,

RM

Gorden · 5 Feb. 2007

Konsole1:

Code:

linux-3rmp:/home/heldch # tail -f /var/log/messages
Feb  5 00:35:00 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:35:00 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff02000c err=-12
Feb  5 00:35:00 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:35:00 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff020003 err=-12
Feb  5 00:35:00 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:35:00 linux-3rmp kernel: eth1: mgt_update_addr: failure
Feb  5 00:35:00 linux-3rmp kernel: eth1: mgt_commit: failure
Feb  5 00:35:00 linux-3rmp kernel: eth1: interface reset failure
Feb  5 00:35:00 linux-3rmp kernel: prism54: Your card/socket may be faulty, or IRQ line too busy :(
Feb  5 00:35:28 linux-3rmp su: (to root) heldch on /dev/pts/4
Feb  5 00:35:52 linux-3rmp su: (to root) heldch on /dev/pts/5
Feb  5 00:36:04 linux-3rmp kernel: eth1: removing device
Feb  5 00:36:04 linux-3rmp kernel: Unloaded prism54 driver
Feb  5 00:36:04 linux-3rmp ifdown: Network interface is managed from NetworkManager
Feb  5 00:36:04 linux-3rmp ifdown: NetworkManager cannot be advised to take down an interface.
Feb  5 00:36:04 linux-3rmp ifdown: Set up another interface instead.
Feb  5 00:36:11 linux-3rmp kernel: Loaded prism54 driver, version 1.2
Feb  5 00:36:11 linux-3rmp kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
Feb  5 00:36:11 linux-3rmp kernel: eth1: resetting device...
Feb  5 00:36:11 linux-3rmp kernel: eth1: uploading firmware...
Feb  5 00:36:11 linux-3rmp kernel: eth1: firmware version: 2.7.0.0
Feb  5 00:36:11 linux-3rmp kernel: eth1: firmware upload complete
Feb  5 00:36:11 linux-3rmp kernel: eth1: timeout waiting for mgmt response 250, triggering device
Feb  5 00:36:11 linux-3rmp kernel: eth1: timeout waiting for mgmt response 225, triggering device
Feb  5 00:36:11 linux-3rmp kernel: eth1: timeout waiting for mgmt response 200, triggering device
Feb  5 00:36:11 linux-3rmp kernel: eth1: timeout waiting for mgmt response 175, triggering device
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 150, triggering device
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 125, triggering device
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 100, triggering device
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 75, triggering device
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 50, triggering device
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 25, triggering device
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response
Feb  5 00:36:12 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff020008 err=-110
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 250, triggering device
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 225, triggering device
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 200, triggering device
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 175, triggering device
Feb  5 00:36:13 linux-3rmp kernel: eth1: timeout waiting for mgmt response 150, triggering device
Feb  5 00:36:13 linux-3rmp kernel: eth1: timeout waiting for mgmt response 125, triggering device
Feb  5 00:36:13 linux-3rmp kernel: eth1: timeout waiting for mgmt response 100, triggering device
Feb  5 00:36:13 linux-3rmp kernel: eth1: timeout waiting for mgmt response 75, triggering device
Feb  5 00:36:13 linux-3rmp kernel: eth1: timeout waiting for mgmt response 50, triggering device
Feb  5 00:36:13 linux-3rmp kernel: eth1: timeout waiting for mgmt response 25, triggering device
Feb  5 00:36:13 linux-3rmp kernel: eth1: timeout waiting for mgmt response
Feb  5 00:36:13 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff020003 err=-110
Feb  5 00:36:13 linux-3rmp kernel: eth1: timeout waiting for mgmt response 250, triggering device
Feb  5 00:36:13 linux-3rmp kernel: eth1: timeout waiting for mgmt response 225, triggering device
Feb  5 00:36:13 linux-3rmp kernel: eth1: timeout waiting for mgmt response 200, triggering device
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 175, triggering device
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 150, triggering device
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 125, triggering device
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 100, triggering device
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 75, triggering device
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 50, triggering device
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 25, triggering device
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response
Feb  5 00:36:14 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=10000000 err=-110
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 250, triggering device
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 225, triggering device
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 200, triggering device
Feb  5 00:36:15 linux-3rmp kernel: eth1: timeout waiting for mgmt response 175, triggering device
Feb  5 00:36:15 linux-3rmp kernel: eth1: timeout waiting for mgmt response 150, triggering device
Feb  5 00:36:15 linux-3rmp kernel: eth1: timeout waiting for mgmt response 125, triggering device
Feb  5 00:36:15 linux-3rmp kernel: eth1: timeout waiting for mgmt response 100, triggering device
Feb  5 00:36:15 linux-3rmp kernel: eth1: timeout waiting for mgmt response 75, triggering device
Feb  5 00:36:15 linux-3rmp kernel: eth1: timeout waiting for mgmt response 50, triggering device
Feb  5 00:36:15 linux-3rmp kernel: eth1: timeout waiting for mgmt response 25, triggering device
Feb  5 00:36:15 linux-3rmp kernel: eth1: timeout waiting for mgmt response
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=17000007 err=-110
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=19000001 err=-12
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=10000002 err=-12
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=19000004 err=-12
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000000 err=-12
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000001 err=-12
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000002 err=-12
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000004 err=-12
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000005 err=-12
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000006 err=-12
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000007 err=-12
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000003 err=-12
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=150007e0 err=-12
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff02000c err=-12
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff020003 err=-12
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_update_addr: failure
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit: failure
Feb  5 00:36:16 linux-3rmp kernel: eth1: interface reset failure
Feb  5 00:36:16 linux-3rmp kernel: prism54: Your card/socket may be faulty, or IRQ line too busy :(
Feb  5 00:36:25 linux-3rmp kernel: eth1: resetting device...
Feb  5 00:36:25 linux-3rmp kernel: eth1: uploading firmware...
Feb  5 00:36:25 linux-3rmp kernel: eth1: firmware version: 2.7.0.0
Feb  5 00:36:25 linux-3rmp kernel: eth1: firmware upload complete
Feb  5 00:36:26 linux-3rmp kernel: eth1: timeout waiting for mgmt response 250, triggering device
Feb  5 00:36:26 linux-3rmp kernel: eth1: timeout waiting for mgmt response 225, triggering device
Feb  5 00:36:26 linux-3rmp kernel: eth1: timeout waiting for mgmt response 200, triggering device
Feb  5 00:36:26 linux-3rmp kernel: eth1: timeout waiting for mgmt response 175, triggering device
Feb  5 00:36:26 linux-3rmp kernel: eth1: timeout waiting for mgmt response 150, triggering device
Feb  5 00:36:26 linux-3rmp kernel: eth1: timeout waiting for mgmt response 125, triggering device
Feb  5 00:36:26 linux-3rmp kernel: eth1: timeout waiting for mgmt response 100, triggering device
Feb  5 00:36:26 linux-3rmp kernel: eth1: timeout waiting for mgmt response 75, triggering device
Feb  5 00:36:26 linux-3rmp kernel: eth1: timeout waiting for mgmt response 50, triggering device
Feb  5 00:36:27 linux-3rmp kernel: eth1: timeout waiting for mgmt response 25, triggering device
Feb  5 00:36:27 linux-3rmp kernel: eth1: timeout waiting for mgmt response
Feb  5 00:36:27 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff020008 err=-110
Feb  5 00:36:27 linux-3rmp kernel: eth1: timeout waiting for mgmt response 250, triggering device
Feb  5 00:36:27 linux-3rmp kernel: eth1: timeout waiting for mgmt response 225, triggering device
Feb  5 00:36:27 linux-3rmp kernel: eth1: timeout waiting for mgmt response 200, triggering device
Feb  5 00:36:27 linux-3rmp kernel: eth1: timeout waiting for mgmt response 175, triggering device
Feb  5 00:36:27 linux-3rmp kernel: eth1: timeout waiting for mgmt response 150, triggering device
Feb  5 00:36:27 linux-3rmp kernel: eth1: timeout waiting for mgmt response 125, triggering device
Feb  5 00:36:27 linux-3rmp kernel: eth1: timeout waiting for mgmt response 100, triggering device
Feb  5 00:36:27 linux-3rmp kernel: eth1: timeout waiting for mgmt response 75, triggering device
Feb  5 00:36:27 linux-3rmp kernel: eth1: timeout waiting for mgmt response 50, triggering device
Feb  5 00:36:28 linux-3rmp kernel: eth1: timeout waiting for mgmt response 25, triggering device
Feb  5 00:36:28 linux-3rmp kernel: eth1: timeout waiting for mgmt response
Feb  5 00:36:28 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff020003 err=-110
Feb  5 00:36:28 linux-3rmp kernel: eth1: timeout waiting for mgmt response 250, triggering device
Feb  5 00:36:28 linux-3rmp kernel: eth1: timeout waiting for mgmt response 225, triggering device
Feb  5 00:36:28 linux-3rmp kernel: eth1: timeout waiting for mgmt response 200, triggering device
Feb  5 00:36:28 linux-3rmp kernel: eth1: timeout waiting for mgmt response 175, triggering device
Feb  5 00:36:28 linux-3rmp kernel: eth1: timeout waiting for mgmt response 150, triggering device
Feb  5 00:36:28 linux-3rmp kernel: eth1: timeout waiting for mgmt response 125, triggering device
Feb  5 00:36:28 linux-3rmp kernel: eth1: timeout waiting for mgmt response 100, triggering device
Feb  5 00:36:28 linux-3rmp kernel: eth1: timeout waiting for mgmt response 75, triggering device
Feb  5 00:36:28 linux-3rmp kernel: eth1: timeout waiting for mgmt response 50, triggering device
Feb  5 00:36:29 linux-3rmp kernel: eth1: timeout waiting for mgmt response 25, triggering device
Feb  5 00:36:29 linux-3rmp kernel: eth1: timeout waiting for mgmt response
Feb  5 00:36:29 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=10000000 err=-110
Feb  5 00:36:29 linux-3rmp kernel: eth1: timeout waiting for mgmt response 250, triggering device
Feb  5 00:36:29 linux-3rmp kernel: eth1: timeout waiting for mgmt response 225, triggering device
Feb  5 00:36:29 linux-3rmp kernel: eth1: timeout waiting for mgmt response 200, triggering device
Feb  5 00:36:29 linux-3rmp kernel: eth1: timeout waiting for mgmt response 175, triggering device
Feb  5 00:36:29 linux-3rmp kernel: eth1: timeout waiting for mgmt response 150, triggering device
Feb  5 00:36:29 linux-3rmp kernel: eth1: timeout waiting for mgmt response 125, triggering device
Feb  5 00:36:29 linux-3rmp kernel: eth1: timeout waiting for mgmt response 100, triggering device
Feb  5 00:36:29 linux-3rmp kernel: eth1: timeout waiting for mgmt response 75, triggering device
Feb  5 00:36:29 linux-3rmp kernel: eth1: timeout waiting for mgmt response 50, triggering device
Feb  5 00:36:30 linux-3rmp kernel: eth1: timeout waiting for mgmt response 25, triggering device
Feb  5 00:36:30 linux-3rmp kernel: eth1: timeout waiting for mgmt response
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=17000007 err=-110
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=19000001 err=-12
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=10000002 err=-12
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=19000004 err=-12
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000000 err=-12
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000001 err=-12
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000002 err=-12
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000004 err=-12
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000005 err=-12
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000006 err=-12
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000007 err=-12
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000003 err=-12
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=150007e0 err=-12
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff02000c err=-12
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff020003 err=-12
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgt_update_addr: failure
Feb  5 00:36:30 linux-3rmp kernel: eth1: mgt_commit: failure
Feb  5 00:36:30 linux-3rmp kernel: eth1: interface reset failure
Feb  5 00:36:30 linux-3rmp kernel: prism54: Your card/socket may be faulty, or IRQ line too busy :(
Feb  5 00:36:40 linux-3rmp rename_netiface: all zero mac address for eth1
Feb  5 00:36:40 linux-3rmp ifup: Network interface is managed from NetworkManager
Feb  5 00:36:40 linux-3rmp ifup: NetworkManager will be advised to set up eth1
Feb  5 00:36:40 linux-3rmp ifup: but it cannot be assured from here.
Feb  5 00:36:40 linux-3rmp kernel: eth1: resetting device...
Feb  5 00:36:40 linux-3rmp kernel: eth1: uploading firmware...
Feb  5 00:36:40 linux-3rmp kernel: eth1: firmware version: 2.7.0.0
Feb  5 00:36:40 linux-3rmp kernel: eth1: firmware upload complete
Feb  5 00:36:40 linux-3rmp kernel: eth1: timeout waiting for mgmt response 250, triggering device
Feb  5 00:36:40 linux-3rmp kernel: eth1: timeout waiting for mgmt response 225, triggering device
Feb  5 00:36:41 linux-3rmp kernel: eth1: timeout waiting for mgmt response 200, triggering device
Feb  5 00:36:41 linux-3rmp kernel: eth1: timeout waiting for mgmt response 175, triggering device
Feb  5 00:36:41 linux-3rmp kernel: eth1: timeout waiting for mgmt response 150, triggering device
Feb  5 00:36:41 linux-3rmp kernel: eth1: timeout waiting for mgmt response 125, triggering device
Feb  5 00:36:41 linux-3rmp kernel: eth1: timeout waiting for mgmt response 100, triggering device
Feb  5 00:36:41 linux-3rmp kernel: eth1: timeout waiting for mgmt response 75, triggering device
Feb  5 00:36:41 linux-3rmp kernel: eth1: timeout waiting for mgmt response 50, triggering device
Feb  5 00:36:41 linux-3rmp kernel: eth1: timeout waiting for mgmt response 25, triggering device
Feb  5 00:36:41 linux-3rmp kernel: eth1: timeout waiting for mgmt response
Feb  5 00:36:41 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff020008 err=-110
Feb  5 00:36:41 linux-3rmp kernel: eth1: timeout waiting for mgmt response 250, triggering device
Feb  5 00:36:41 linux-3rmp kernel: eth1: timeout waiting for mgmt response 225, triggering device
Feb  5 00:36:42 linux-3rmp kernel: eth1: timeout waiting for mgmt response 200, triggering device
Feb  5 00:36:42 linux-3rmp kernel: eth1: timeout waiting for mgmt response 175, triggering device
Feb  5 00:36:42 linux-3rmp kernel: eth1: timeout waiting for mgmt response 150, triggering device
Feb  5 00:36:42 linux-3rmp kernel: eth1: timeout waiting for mgmt response 125, triggering device
Feb  5 00:36:42 linux-3rmp kernel: eth1: timeout waiting for mgmt response 100, triggering device
Feb  5 00:36:42 linux-3rmp kernel: eth1: timeout waiting for mgmt response 75, triggering device
Feb  5 00:36:42 linux-3rmp kernel: eth1: timeout waiting for mgmt response 50, triggering device
Feb  5 00:36:42 linux-3rmp kernel: eth1: timeout waiting for mgmt response 25, triggering device
Feb  5 00:36:42 linux-3rmp kernel: eth1: timeout waiting for mgmt response
Feb  5 00:36:42 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff020003 err=-110
Feb  5 00:36:42 linux-3rmp kernel: eth1: timeout waiting for mgmt response 250, triggering device
Feb  5 00:36:42 linux-3rmp kernel: eth1: timeout waiting for mgmt response 225, triggering device
Feb  5 00:36:43 linux-3rmp kernel: eth1: timeout waiting for mgmt response 200, triggering device
Feb  5 00:36:43 linux-3rmp kernel: eth1: timeout waiting for mgmt response 175, triggering device
Feb  5 00:36:43 linux-3rmp kernel: eth1: timeout waiting for mgmt response 150, triggering device
Feb  5 00:36:43 linux-3rmp kernel: eth1: timeout waiting for mgmt response 125, triggering device
Feb  5 00:36:43 linux-3rmp kernel: eth1: timeout waiting for mgmt response 100, triggering device
Feb  5 00:36:43 linux-3rmp kernel: eth1: timeout waiting for mgmt response 75, triggering device
Feb  5 00:36:43 linux-3rmp kernel: eth1: timeout waiting for mgmt response 50, triggering device
Feb  5 00:36:43 linux-3rmp kernel: eth1: timeout waiting for mgmt response 25, triggering device
Feb  5 00:36:43 linux-3rmp kernel: eth1: timeout waiting for mgmt response
Feb  5 00:36:43 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=10000000 err=-110
Feb  5 00:36:43 linux-3rmp kernel: eth1: timeout waiting for mgmt response 250, triggering device
Feb  5 00:36:43 linux-3rmp kernel: eth1: timeout waiting for mgmt response 225, triggering device
Feb  5 00:36:44 linux-3rmp kernel: eth1: timeout waiting for mgmt response 200, triggering device
Feb  5 00:36:44 linux-3rmp kernel: eth1: timeout waiting for mgmt response 175, triggering device
Feb  5 00:36:44 linux-3rmp kernel: eth1: timeout waiting for mgmt response 150, triggering device
Feb  5 00:36:44 linux-3rmp kernel: eth1: timeout waiting for mgmt response 125, triggering device
Feb  5 00:36:44 linux-3rmp kernel: eth1: timeout waiting for mgmt response 100, triggering device
Feb  5 00:36:44 linux-3rmp kernel: eth1: timeout waiting for mgmt response 75, triggering device
Feb  5 00:36:44 linux-3rmp kernel: eth1: timeout waiting for mgmt response 50, triggering device
Feb  5 00:36:44 linux-3rmp kernel: eth1: timeout waiting for mgmt response 25, triggering device
Feb  5 00:36:44 linux-3rmp kernel: eth1: timeout waiting for mgmt response
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=17000007 err=-110
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=19000001 err=-12
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=10000002 err=-12
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=19000004 err=-12
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000000 err=-12
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000001 err=-12
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000002 err=-12
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000004 err=-12
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000005 err=-12
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000006 err=-12
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000007 err=-12
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000003 err=-12
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=150007e0 err=-12
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff02000c err=-12
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:44 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff020003 err=-12
Feb  5 00:36:45 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:45 linux-3rmp kernel: eth1: mgt_update_addr: failure
Feb  5 00:36:45 linux-3rmp kernel: eth1: mgt_commit: failure
Feb  5 00:36:45 linux-3rmp kernel: eth1: interface reset failure
Feb  5 00:36:45 linux-3rmp kernel: prism54: Your card/socket may be faulty, or IRQ line too busy :(
Feb  5 00:36:48 linux-3rmp kernel: eth1: resetting device...
Feb  5 00:36:48 linux-3rmp kernel: eth1: uploading firmware...
Feb  5 00:36:48 linux-3rmp kernel: eth1: firmware version: 2.7.0.0
Feb  5 00:36:48 linux-3rmp kernel: eth1: firmware upload complete
Feb  5 00:36:48 linux-3rmp kernel: eth1: timeout waiting for mgmt response 250, triggering device
Feb  5 00:36:48 linux-3rmp kernel: eth1: timeout waiting for mgmt response 225, triggering device
Feb  5 00:36:48 linux-3rmp kernel: eth1: timeout waiting for mgmt response 200, triggering device
Feb  5 00:36:48 linux-3rmp kernel: eth1: timeout waiting for mgmt response 175, triggering device
Feb  5 00:36:48 linux-3rmp kernel: eth1: timeout waiting for mgmt response 150, triggering device
Feb  5 00:36:48 linux-3rmp kernel: eth1: timeout waiting for mgmt response 125, triggering device
Feb  5 00:36:48 linux-3rmp kernel: eth1: timeout waiting for mgmt response 100, triggering device
Feb  5 00:36:49 linux-3rmp kernel: eth1: timeout waiting for mgmt response 75, triggering device
Feb  5 00:36:49 linux-3rmp kernel: eth1: timeout waiting for mgmt response 50, triggering device
Feb  5 00:36:49 linux-3rmp kernel: eth1: timeout waiting for mgmt response 25, triggering device
Feb  5 00:36:49 linux-3rmp kernel: eth1: timeout waiting for mgmt response
Feb  5 00:36:49 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff020008 err=-110
Feb  5 00:36:49 linux-3rmp kernel: eth1: timeout waiting for mgmt response 250, triggering device
Feb  5 00:36:49 linux-3rmp kernel: eth1: timeout waiting for mgmt response 225, triggering device
Feb  5 00:36:49 linux-3rmp kernel: eth1: timeout waiting for mgmt response 200, triggering device
Feb  5 00:36:49 linux-3rmp kernel: eth1: timeout waiting for mgmt response 175, triggering device
Feb  5 00:36:49 linux-3rmp kernel: eth1: timeout waiting for mgmt response 150, triggering device
Feb  5 00:36:49 linux-3rmp kernel: eth1: timeout waiting for mgmt response 125, triggering device
Feb  5 00:36:49 linux-3rmp kernel: eth1: timeout waiting for mgmt response 100, triggering device
Feb  5 00:36:50 linux-3rmp kernel: eth1: timeout waiting for mgmt response 75, triggering device
Feb  5 00:36:50 linux-3rmp kernel: eth1: timeout waiting for mgmt response 50, triggering device
Feb  5 00:36:50 linux-3rmp kernel: eth1: timeout waiting for mgmt response 25, triggering device
Feb  5 00:36:50 linux-3rmp kernel: eth1: timeout waiting for mgmt response
Feb  5 00:36:50 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff020003 err=-110
Feb  5 00:36:50 linux-3rmp kernel: eth1: timeout waiting for mgmt response 250, triggering device
Feb  5 00:36:50 linux-3rmp kernel: eth1: timeout waiting for mgmt response 225, triggering device
Feb  5 00:36:50 linux-3rmp kernel: eth1: timeout waiting for mgmt response 200, triggering device
Feb  5 00:36:50 linux-3rmp kernel: eth1: timeout waiting for mgmt response 175, triggering device
Feb  5 00:36:50 linux-3rmp kernel: eth1: timeout waiting for mgmt response 150, triggering device
Feb  5 00:36:50 linux-3rmp kernel: eth1: timeout waiting for mgmt response 125, triggering device
Feb  5 00:36:50 linux-3rmp kernel: eth1: timeout waiting for mgmt response 100, triggering device
Feb  5 00:36:51 linux-3rmp kernel: eth1: timeout waiting for mgmt response 75, triggering device
Feb  5 00:36:51 linux-3rmp kernel: eth1: timeout waiting for mgmt response 50, triggering device
Feb  5 00:36:51 linux-3rmp kernel: eth1: timeout waiting for mgmt response 25, triggering device
Feb  5 00:36:51 linux-3rmp kernel: eth1: timeout waiting for mgmt response
Feb  5 00:36:51 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=10000000 err=-110
Feb  5 00:36:51 linux-3rmp kernel: eth1: timeout waiting for mgmt response 250, triggering device
Feb  5 00:36:51 linux-3rmp kernel: eth1: timeout waiting for mgmt response 225, triggering device
Feb  5 00:36:51 linux-3rmp kernel: eth1: timeout waiting for mgmt response 200, triggering device
Feb  5 00:36:51 linux-3rmp kernel: eth1: timeout waiting for mgmt response 175, triggering device
Feb  5 00:36:51 linux-3rmp kernel: eth1: timeout waiting for mgmt response 150, triggering device
Feb  5 00:36:52 linux-3rmp kernel: eth1: timeout waiting for mgmt response 125, triggering device
Feb  5 00:36:52 linux-3rmp kernel: eth1: timeout waiting for mgmt response 100, triggering device
Feb  5 00:36:52 linux-3rmp kernel: eth1: timeout waiting for mgmt response 75, triggering device
Feb  5 00:36:52 linux-3rmp kernel: eth1: timeout waiting for mgmt response 50, triggering device
Feb  5 00:36:52 linux-3rmp kernel: eth1: timeout waiting for mgmt response 25, triggering device
Feb  5 00:36:52 linux-3rmp kernel: eth1: timeout waiting for mgmt response
Feb  5 00:36:52 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=17000007 err=-110
Feb  5 00:36:52 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:52 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=19000001 err=-12
Feb  5 00:36:52 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:52 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=10000002 err=-12
Feb  5 00:36:52 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:52 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=19000004 err=-12
Feb  5 00:36:52 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:52 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000000 err=-12
Feb  5 00:36:52 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:52 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000001 err=-12
Feb  5 00:36:52 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:52 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000002 err=-12
Feb  5 00:36:52 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:52 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000004 err=-12
Feb  5 00:36:52 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:52 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000005 err=-12
Feb  5 00:36:52 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:52 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000006 err=-12
Feb  5 00:36:53 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:54 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000007 err=-12
Feb  5 00:36:54 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:54 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000003 err=-12
Feb  5 00:36:54 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:54 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=150007e0 err=-12
Feb  5 00:36:54 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:54 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff02000c err=-12
Feb  5 00:36:54 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:54 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff020003 err=-12
Feb  5 00:36:54 linux-3rmp kernel: eth1: mgmt tx queue is still full
Feb  5 00:36:54 linux-3rmp kernel: eth1: mgt_update_addr: failure
Feb  5 00:36:54 linux-3rmp kernel: eth1: mgt_commit: failure
Feb  5 00:36:54 linux-3rmp kernel: eth1: interface reset failure
Feb  5 00:36:54 linux-3rmp kernel: prism54: Your card/socket may be faulty, or IRQ line too busy :(

Konsole2:

Code:

linux-3rmp:/home/heldch # rmmod prism54
linux-3rmp:/home/heldch # modprobe prism54
linux-3rmp:/home/heldch # iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

irda0     no wireless extensions.

sit0      no wireless extensions.

eth1      NOT READY!  ESSID:off/any
          Mode:Managed  Channel:0  Access Point: Not-Associated
          Tx-Power=31 dBm   Sensitivity=0/200
          Retry min limit:0   RTS thr=0 B   Fragment thr=0 B
          Encryption key: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

linux-3rmp:/home/heldch # ifconfig
eth0      Protokoll:Ethernet  Hardware Adresse 00:40:D0:46:87:4B
          inet Adresse:192.168.2.35  Bcast:192.168.2.255  Maske:255.255.255.0
          inet6 Adresse: fe80::240:d0ff:fe46:874b/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:151233 errors:0 dropped:0 overruns:0 frame:0
          TX packets:162121 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 Sendewarteschlangenlänge:1000
          RX bytes:66301539 (63.2 Mb)  TX bytes:87547954 (83.4 Mb)
          Interrupt:10 Basisadresse:0xe300

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:322 errors:0 dropped:0 overruns:0 frame:0
          TX packets:322 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 Sendewarteschlangenlänge:0
          RX bytes:21202 (20.7 Kb)  TX bytes:21202 (20.7 Kb)

Anonymous · 5 Feb. 2007

Was schonmal gut aussieht:

Code:

Feb  5 00:36:40 linux-3rmp kernel: eth1: resetting device... 
Feb  5 00:36:40 linux-3rmp kernel: eth1: uploading firmware... 
Feb  5 00:36:40 linux-3rmp kernel: eth1: firmware version: 2.7.0.0 
Feb  5 00:36:40 linux-3rmp kernel: eth1: firmware upload complete

Die Firmware wird geladen und die Karte wird auch versucht zu aktivieren.

Das hier sieht weniger gut aus:

Code:

Feb  5 00:36:11 linux-3rmp kernel: eth1: timeout waiting for mgmt response 250, triggering device 
Feb  5 00:36:11 linux-3rmp kernel: eth1: timeout waiting for mgmt response 225, triggering device 
Feb  5 00:36:11 linux-3rmp kernel: eth1: timeout waiting for mgmt response 200, triggering device 
Feb  5 00:36:11 linux-3rmp kernel: eth1: timeout waiting for mgmt response 175, triggering device 
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 150, triggering device 
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 125, triggering device 
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 100, triggering device 
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 75, triggering device 
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 50, triggering device 
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 25, triggering device 
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 
Feb  5 00:36:12 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff020008 err=-110 
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 250, triggering device 
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 225, triggering device 
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 200, triggering device 
Feb  5 00:36:12 linux-3rmp kernel: eth1: timeout waiting for mgmt response 175, triggering device 
Feb  5 00:36:13 linux-3rmp kernel: eth1: timeout waiting for mgmt response 150, triggering device 
Feb  5 00:36:13 linux-3rmp kernel: eth1: timeout waiting for mgmt response 125, triggering device 
Feb  5 00:36:13 linux-3rmp kernel: eth1: timeout waiting for mgmt response 100, triggering device 
Feb  5 00:36:13 linux-3rmp kernel: eth1: timeout waiting for mgmt response 75, triggering device 
Feb  5 00:36:13 linux-3rmp kernel: eth1: timeout waiting for mgmt response 50, triggering device 
Feb  5 00:36:13 linux-3rmp kernel: eth1: timeout waiting for mgmt response 25, triggering device 
Feb  5 00:36:13 linux-3rmp kernel: eth1: timeout waiting for mgmt response 
Feb  5 00:36:13 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff020003 err=-110 
Feb  5 00:36:13 linux-3rmp kernel: eth1: timeout waiting for mgmt response 250, triggering device 
Feb  5 00:36:13 linux-3rmp kernel: eth1: timeout waiting for mgmt response 225, triggering device 
Feb  5 00:36:13 linux-3rmp kernel: eth1: timeout waiting for mgmt response 200, triggering device 
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 175, triggering device 
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 150, triggering device 
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 125, triggering device 
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 100, triggering device 
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 75, triggering device 
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 50, triggering device 
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 25, triggering device 
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 
Feb  5 00:36:14 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=10000000 err=-110 
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 250, triggering device 
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 225, triggering device 
Feb  5 00:36:14 linux-3rmp kernel: eth1: timeout waiting for mgmt response 200, triggering device 
Feb  5 00:36:15 linux-3rmp kernel: eth1: timeout waiting for mgmt response 175, triggering device 
Feb  5 00:36:15 linux-3rmp kernel: eth1: timeout waiting for mgmt response 150, triggering device 
Feb  5 00:36:15 linux-3rmp kernel: eth1: timeout waiting for mgmt response 125, triggering device 
Feb  5 00:36:15 linux-3rmp kernel: eth1: timeout waiting for mgmt response 100, triggering device 
Feb  5 00:36:15 linux-3rmp kernel: eth1: timeout waiting for mgmt response 75, triggering device 
Feb  5 00:36:15 linux-3rmp kernel: eth1: timeout waiting for mgmt response 50, triggering device 
Feb  5 00:36:15 linux-3rmp kernel: eth1: timeout waiting for mgmt response 25, triggering device 
Feb  5 00:36:15 linux-3rmp kernel: eth1: timeout waiting for mgmt response 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=17000007 err=-110 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=19000001 err=-12 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=10000002 err=-12 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=19000004 err=-12 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000000 err=-12 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000001 err=-12 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000002 err=-12 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000004 err=-12 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000005 err=-12 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000006 err=-12 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000007 err=-12 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=12000003 err=-12 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=150007e0 err=-12 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff02000c err=-12 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit_list: failure. oid=ff020003 err=-12 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgmt tx queue is still full 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_update_addr: failure 
Feb  5 00:36:15 linux-3rmp kernel: eth1: mgt_commit: failure 
Feb  5 00:36:16 linux-3rmp kernel: eth1: interface reset failure 
Feb  5 00:36:16 linux-3rmp kernel: prism54: Your card/socket may be faulty, or IRQ line too busy :(

Und daraus folgend:

Code:

eth1      NOT READY!  ESSID:off/any

AFAIK kann aber der NetworkManager (den Du offensichtlich verwendest) nur ein Interface zur gleichen Zeit aktiv halten, was auch diese Meldung andeutet.

Code:

Feb  5 00:36:04 linux-3rmp ifdown: Network interface is managed from NetworkManager 
Feb  5 00:36:04 linux-3rmp ifdown: NetworkManager cannot be advised to take down an interface. 
Feb  5 00:36:04 linux-3rmp ifdown: Set up another interface instead.

Kannst Du die Karte nun über Yast einrichten? Wird sie erkannt? (Wahrscheinlich als "nicht konfiguriert")

Wenn nicht, kannst Du ein neues Drahtloses Interface (Hinzufügen => Drahtlos) einrichten und ihm als Modul prism54 zuordnen.

Egal wie, vor dem Versuch, das Interface einzurichten, muß das Modul 'prism54' unbedingt als root geladen werden

Code:

su

Passwort

modprobe prism54

Welche Verschlüsselung soll verwendet werden?

WPA/WEP/Keine?

Greetz,

RM

Gorden · 5 Feb. 2007

Im Networkmanager war die Karte nicht aufgelistet. Hab wie Du es gesagt hast eine neue angelegt und als Modulname prism54. Doch es geschieht nichts, die Kontrollämpchen der Karte bleiben weiterhin dunkel grün und es passiert gar nichts.
Eine Verschlüsselung benutze ich nicht!

Anonymous · 5 Feb. 2007

OK, eigentlich müsste alles von Treiberseite her stimmen, die Firmware wird zwar jetzt geladen, aber das Device funktioniert trotzdem nicht richtig:

Doch es geschieht nichts, die Kontrollämpchen der Karte bleiben weiterhin dunkel grün und es passiert gar nichts.

Was ein weiteres Zeichen dafür ist.

Ich finde auch im Internet widersprüchliche Aussagen zu dieser Karte, allerdings geht nicht immer eindeutig hervor, ob es um eine PCI/PCMCIA-Karte oder die USB-Karte selben Namens geht.

Nun gibt es mehrere Möglichkeiten, wobei es immer noch die Notlösung "ndiswrapper" und Windowstreiber gibt, obwohl SuSE einen Intersil-Chip erkennt und prism54 als Treiber vorschlägt.

Here's the Deal.

Wir probieren zunächst aus, ob es mit den nativen Treibern geht, das dürfte schnell erledigt sein, denn außer dem Verwenden anderer Firmware-Dateien fällt mir dazu auch nichts mehr ein.

Wenn das nicht klappt, dann werde ich Dir bei der Einrichtung über ndiswrapper helfen.

Verschiedene Firmwaredateien findest Du auf der selben Seite wie die Version 2.7.0.0, allerdings sind laut Aussage der HP die älteren 2er Versionen eigentlich für die USB-Karte gedacht.
Du kannst sie trotzdem mal ausprobieren, mehr als "Karte will immer noch nicht" kann nicht passieren.

Die Prozedur ist denkbar einfach (wie der die beiden Konsolen verwenden).

1. Altes Firmwarefile umbenennen, ich würde -der Übersicht halber- einfach die Versionsnummer anhängen, also aus isl3890 wird isl3890.2.7.7.0.

2. Neues Firmwarefile als isl3890 in /lib/firmware kopieren.

3. In der Konsole, wo man die Kommandos absetzt, einfach Modul laden und entladen und dabei die zweite Konsole sowie die LEDs beobachten.

Code:

su

Passwort

rmmod prism54

modprobe prism54

iwconfig

Sollten die LEDs auf einmal angehen und die vielen Meldungen in der 2. Konsole verschwinden, sowie iwconfig etwas anderes als "NOT READY" anzeigen, dann hast Du einen Treffer gelandet.

Hier sind ein paar Firmwarefiles zur Auswahl.

http://prism54.org/firmware/

Probiere die alle durch, vor allem auch die 1er Versionen, ist ja schnell passiert.

Wenn da nichts Positives passiert, sollte man sich mit ndiswrapper anfreunden.

Greetz,

RM

Gorden · 5 Feb. 2007

Hat bei allen nicht geklappt und Ndiswrapper hab ich ja auch schon versucht oder ist der HowKnow falsch?

Freecoffee · 5 Feb. 2007

Keine Ahnung, was ein HowKnow ist. "Nicht geklappt" solltest du aber in jedem Fall weiter ausführen.

Anonymous · 5 Feb. 2007

Programme haben Namen und Versionen.

Shelleingaben haben auch Ausgaben zur Folge.

Poste diese.

Code:

rpm -qa|grep ndiswrapper

Welcher Windowstreiber? Dateiname und ggf. Downloadlink, wo Du den her hast.

Was wurde beim Versuche den Treiber zu installieren ausgespuckt?

Ausgabe _IM WORTLAUT_ aus der Konsole 1:1 zitieren!

Greetz,

RM

Gorden · 5 Feb. 2007

Version ist:

Code:

ndiswrapper-kmp-smp-1.10_2.6.16.21_0.13-19.3
ndiswrapper-kmp-bigsmp-1.10_2.6.16.21_0.13-19.3
ndiswrapper-1.10-19
ndiswrapper-kmp-default-1.10_2.6.16.21_0.13-19.3
ndiswrapper-kmp-xen-1.10_2.6.16.21_0.13-19.3

Treiber ist original von T-Com

Und das spuckt Ndiswrapper aus:

Code:

linux-3rmp:/home/heldch # ndiswrapper -i /home/heldch/Desktop/TS154ICB.inf
ts154icb is already installed. Use -e to remove it
linux-3rmp:/home/heldch # modprobe ndiswrapper
linux-3rmp:/home/heldch # ndiswrapper -l
Installed drivers:
inffile invalid driver!
ts154icb        invalid driver!
ts154icb2       invalid driver!
ts154icb3       invalid driver!

Anonymous · 5 Feb. 2007

Schmeiss mal die ganzen verborkten Installationsversuche raus.

Code:

su

Passwort

rm -rf /etc/ndiswrapper/*

Welche Dateien befinden sich in dem Ordner, wo auch die inf-Datei liegt?

FYI:

Code:

Sinus 154 card utility/Driver # ls
Driver.2K  Driver.98  Driver.ME  TS154IC1.sys  TS154ICB.cat  TS154ICB.inf  TS154ICB.sys

Sinus 154 card utility/Driver # ndiswrapper -i TS154ICB.inf
installing ts154icb ...
Sinus 154 card utility/Driver # ndiswrapper -l
ts154icb : driver installed

Works for me [tm]

Greetz,

RM

Gorden · 5 Feb. 2007

Ist immernoch so:

Code:

linux-3rmp:/home/heldch # ndiswrapper -i /home/heldch/Desktop/TS154ICB.inf
Installing ts154icb
linux-3rmp:/home/heldch # ndiswrapper -l
Installed drivers:
ts154icb        invalid driver!

T-Sinus 154card

Newbie

Guru

Newbie

Anonymous

Gast

Newbie

Anonymous

Gast

Newbie

Anonymous

Gast

Newbie

Anonymous

Gast

Newbie

Anonymous

Gast

Newbie

Anonymous

Gast

Newbie

Guru

Anonymous

Gast

Newbie

Anonymous

Gast

Newbie