Suse: bcm4318 treiber sind druff, was jetzt? (gmod)

gmod
Gast

« am: 28.05.07, 16:36:38 »

hallo,
1. habe die firmware drauf.es gab dabei keine fehlermeldungen.
2. mit yast2 karte konfiguriert.
3. router angepingt, ging aber nicht!

iwconfig:
eth1 IEEE 802.11b/g ESSID:off/any Nickname:"Broadcom 4318"
Mode:Managed Frequency=2.484 GHz Access Point: Invalid
Bit Rate=1 Mb/s Tx-Power=15 dBm
RTS thr:off Fragment thr:off
Encryption key:3030-3030-3030-3030-3030-3030-3030-3030 Security mode:restricted
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

ifconfig:
eth0 Protokoll:Ethernet Hardware Adresse 00:0C:6E:1F:43:85
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 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:177 Basisadresse:0xc000

eth1 Protokoll:Ethernet Hardware Adresse 00:17:31:1F:7D:18
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:5 overruns:0 frame:0
TX packets:7448 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 b) TX bytes:314272 (306.9 Kb)
Interrupt:5 Basisadresse:0xc000

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

bitte helft mir!

Moderator informieren

gmod
Gast

Re: Suse: bcm4318 treiber sind druff, was jetzt?

« Antwort #1 am: 28.05.07, 17:06:32 »

knetworkmanager bricht bei 28% ab!

Moderator informieren

gmod
Gast

Re: Suse: bcm4318 treiber sind druff, was jetzt?

« Antwort #2 am: 28.05.07, 17:22:18 »

noch ein paar weitere angaben:

route:
Kernel IP Routentabelle
Ziel Router Genmask Flags Metric Ref Use Iface
loopback * 255.0.0.0 U 0 0 0 lo

sudo grep -i firmware /var/log/messages
May 28 13:28:18 .... sudo: root : TTY=pts/1 ; PWD=/lib/firmware/bcm4318 ; USER=root ; COMMAND=/usr/bin/bcm43xx-fwcutter -w /lib/firmware/bcm4318/wl_apst.o
May 28 13:29:01 .... sudo: root : TTY=pts/1 ; PWD=/lib/firmware/bcm4318 ; USER=root ; COMMAND=/usr/bin/bcm43xx-fwcutter -w
May 28 13:29:45 .... sudo: root : TTY=pts/1 ; PWD=/lib/firmware/bcm4318 ; USER=root ; COMMAND=/usr/bin/bcm43xx-fwcutter -w
May 28 13:30:07 .... sudo: root : TTY=pts/1 ; PWD=/lib/firmware/bcm4318 ; USER=root ; COMMAND=/usr/bin/bcm43xx-fwcutter -w
May 28 13:30:54 .... sudo: root : TTY=pts/1 ; PWD=/lib/firmware/bcm4318 ; USER=root ; COMMAND=/usr/bin/bcm43xx-fwcutter -w
May 28 13:31:14 .... sudo: root : TTY=pts/1 ; PWD=/lib/firmware/bcm4318 ; USER=root ; COMMAND=/usr/bin/bcm43xx-fwcutter -w
May 28 13:31:46 .... sudo: root : TTY=pts/1 ; PWD=/lib/firmware/bcm4318 ; USER=root ; COMMAND=/usr/bin/bcm43xx-fwcutter -i
May 28 13:38:07 .... sudo: root : TTY=pts/1 ; PWD=/lib/firmware/bcm4318 ; USER=root ; COMMAND=/usr/bin/bcm43xx-fwcutter -w
May 28 13:38:38 .... sudo: root : TTY=pts/1 ; PWD=/lib/firmware/bcm4318 ; USER=root ; COMMAND=/usr/bin/bcm43xx-fwcutter -w
May 28 13:44:54 .... sudo: root : TTY=pts/1 ; PWD=/lib/firmware/bcm4318 ; USER=root ; COMMAND=/usr/bin/bcm43xx-fwcutter -w
May 28 13:45:27 .... sudo: root : TTY=pts/1 ; PWD=/lib/firmware/bcm4318 ; USER=root ; COMMAND=/usr/bin/bcm43xx-fwcutter
May 28 13:45:47 .... sudo: root : TTY=pts/1 ; PWD=/lib/firmware/bcm4318 ; USER=root ; COMMAND=/usr/bin/bcm43xx-fwcutter -w
May 28 14:21:39 .... sudo: root : TTY=pts/1 ; PWD=/lib/firmware ; USER=root ; COMMAND=/usr/bin/bcm43xx-fwcutter -w
May 28 16:59:58 .... sudo: gmod : TTY=pts/1 ; PWD=/home/gmod ; USER=root ; COMMAND=/usr/bin/grep -i firmware /var/log/messages
May 28 17:18:50 .... sudo: root : TTY=pts/1 ; PWD=/home/gmod ; USER=root ; COMMAND=/usr/bin/grep -i firmware /var/log/messages