Forum Debian Users Gang

ilin · 2013-05-11 17:50:10

Mnie to zastanawia.

Kod:

b43-phy0: The hardware RF-kill button still turns the radio physically off. Press the button to turn it on.

Zainstalować rfkill za jego pomocą sprawdzić status karty i ewentualnie przełączyć.

LoLedman · 2013-05-13 08:10:22

Jackalex wywalilem haslo zostawiajac puste miejsce a linksys to jakas niezabiezpieczona siec kolo mnie. SSID nie jest ukryte.

yossarian · 2013-05-13 08:22:51

Zobacz czy nie masz zablokowanej karty.

Jacekalex · 2013-05-13 09:03:14

LoLedman napisał(-a):
Jackalex wywalilem haslo zostawiajac puste miejsce a linksys to jakas niezabiezpieczona siec kolo mnie. SSID nie jest ukryte.

Tylko w tym konfigu masz 2 wpisy, jeden ma ustawienia, ale odnosi się do świeżego powietrza, drugi to Linksys, w ogóle nie skonfigurowany.

Jak sieć ma ukryty ssid, to musisz w konfigu do danej sieci mieć bssid - mac routera, i włączoną opcję scan_ssid.
Nazwa sieci, ssid, bssid, dane logowania i protokół, to jest jeden integralny blok konfigu opisujący daną sieć.
Coś przekombinowałeś w wpa_gui.

yossarian · 2013-05-13 09:30:07

Jeśli to normalna sieć to wystarcza ssid i psk. Nie ma po co (na tym etapie) kombinować. Dmesg pluje coś o rfkill i to warto sprawdzić.

Ostatnio edytowany przez yossarian (2013-05-13 09:40:26)

Jacekalex · 2013-05-13 14:07:46

yossarian napisał(-a):
Jeśli to normalna sieć to wystarcza ssid i psk. Nie ma po co (na tym etapie) kombinować. Dmesg pluje coś o rfkill i to warto sprawdzić.

Pod warunkiem, że jakiś mądrala nie ma w sąsiednim budynku w routerze takiego samego ssid.
bssid jest o tyle bezpieczny, że unikalny.

LoLedman · 2013-05-13 18:01:41

ilin to wpis póżniejszy, wyłączyłem wlan0 żeby podłączyć eth0 bo chciałem logi wklejić

yossarian · 2013-05-13 19:32:57

Chyba w tym tkwi problem:

Kod:

[  111.296213] b43-phy0 ERROR: Fatal DMA error: 0x00000800, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
[  111.296225] b43-phy0 ERROR: This device does not support DMA on your system. Please use PIO instead.
[  111.296232] b43-phy0: Controller RESET (DMA error) ...
[  111.528257] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
[  116.961336] b43-phy0: Controller restarted
[  119.460097] No probe response from AP 00:24:a5:f4:1a:39 after 500ms, disconnecting.
[  129.928289] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
[  135.385719] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  136.288703] wlan0: direct probe to AP 00:24:a5:f4:1a:39 (try 1)
[  136.292401] wlan0: direct probe responded
[  136.292408] wlan0: authenticate with AP 00:24:a5:f4:1a:39 (try 1)
[  136.294742] wlan0: authenticated
[  136.294783] wlan0: associate with AP 00:24:a5:f4:1a:39 (try 1)
[  136.298206] wlan0: RX AssocResp from 00:24:a5:f4:1a:39 (capab=0x411 status=0 aid=4)
[  136.298214] wlan0: associated
[  136.300490] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  141.316068] No probe response from AP 00:24:a5:f4:1a:39 after 500ms, disconnecting.
[  142.333871] wlan0: direct probe to AP 00:1d:7e:aa:59:64 (try 1)
[  142.532069] wlan0: direct probe to AP 00:1d:7e:aa:59:64 (try 2)
[  142.732089] wlan0: direct probe to AP 00:1d:7e:aa:59:64 (try 3)
[  142.932072] wlan0: direct probe to AP 00:1d:7e:aa:59:64 timed out
[  146.788063] wlan0: no IPv6 routers present
[  148.228806] wlan0: direct probe to AP 00:24:a5:f4:1a:39 (try 1)
[  148.428074] wlan0: direct probe to AP 00:24:a5:f4:1a:39 (try 2)
[  148.628066] wlan0: direct probe to AP 00:24:a5:f4:1a:39 (try 3)
[  148.828102] wlan0: direct probe to AP 00:24:a5:f4:1a:39 timed out

Spróbuj tak:
Utwórz plik /etc/modprobe.d/b43-pio.conf o zawartości:

Kod:

options b43 pio=1

lub:

Kod:

options b43 pio=1 qos=0

i zobacz po restarcie.

Po każdej próbie pokaż dmesg.

Ostatnio edytowany przez yossarian (2013-05-13 19:49:45)

LoLedman · 2013-05-14 19:52:37

Dzięki! Działa piszę z lapka.

Kod:

 14 19:33:49 Debian kernel: [    6.739964] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
May 14 19:33:49 Debian kernel: [    6.752283]   alloc irq_desc for 29 on node -1
May 14 19:33:49 Debian kernel: [    6.752286]   alloc kstat_irqs on node -1
May 14 19:33:49 Debian kernel: [    6.752297] i915 0000:00:02.0: irq 29 for MSI/MSI-X
May 14 19:33:49 Debian kernel: [    6.752304] [drm] set up 63M of stolen space
May 14 19:33:49 Debian kernel: [    7.276576] phy0: Selected rate control algorithm 'minstrel'
May 14 19:33:49 Debian kernel: [    7.277242] Registered led device: b43-phy0::tx
May 14 19:33:49 Debian kernel: [    7.277258] Registered led device: b43-phy0::rx
May 14 19:33:49 Debian kernel: [    7.277273] Registered led device: b43-phy0::radio
May 14 19:33:49 Debian kernel: [    7.277338] Broadcom 43xx driver loaded [ Features: PMLS, Firmware-ID: FW13 ]
May 14 19:33:49 Debian kernel: [    7.436597] Console: switching to colour frame buffer device 180x56
May 14 19:33:49 Debian kernel: [    7.440108] fb0: inteldrmfb frame buffer device
May 14 19:33:49 Debian kernel: [    7.440110] registered panic notifier
May 14 19:33:49 Debian kernel: [    7.452298] acpi device:02: registered as cooling_device2
May 14 19:33:49 Debian kernel: [    7.460274] acpi device:03: registered as cooling_device3
May 14 19:33:49 Debian kernel: [    7.460691] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input9
May 14 19:33:49 Debian kernel: [    7.460748] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
May 14 19:33:49 Debian kernel: [    7.460784] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
May 14 19:33:49 Debian kernel: [    7.460839]   alloc irq_desc for 22 on node -1
May 14 19:33:49 Debian kernel: [    7.460842]   alloc kstat_irqs on node -1
May 14 19:33:49 Debian kernel: [    7.460851] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
May 14 19:33:49 Debian kernel: [    7.460898] HDA Intel 0000:00:1b.0: setting latency timer to 64
May 14 19:33:49 Debian kernel: [    7.580140] hda_codec: ALC268: BIOS auto-probing.
May 14 19:33:49 Debian kernel: [    7.580955] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input10
May 14 19:33:49 Debian kernel: [    8.742490] Adding 5901304k swap on /dev/sda5.  Priority:-1 extents:1 across:5901304k 
May 14 19:33:49 Debian kernel: [    8.896107] EXT3 FS on sda1, internal journal
May 14 19:33:49 Debian kernel: [    9.011118] loop: module loaded
May 14 19:33:49 Debian kernel: [   10.248266] b43 ssb0:0: firmware: requesting b43/ucode15.fw
May 14 19:33:49 Debian kernel: [   10.272846] b43 ssb0:0: firmware: requesting b43/lp0initvals15.fw
May 14 19:33:49 Debian kernel: [   10.276168] b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw
May 14 19:33:49 Debian kernel: [   10.425269] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
May 14 19:33:49 Debian kernel: [   10.713081] b43-phy0: Radio hardware status changed to DISABLED
May 14 19:33:49 Debian kernel: [   10.720262] b43-phy0: Radio turned on by software
May 14 19:33:49 Debian kernel: [   10.720264] b43-phy0: The hardware RF-kill button still turns the radio physically off. Press the button to turn it on.
May 14 19:33:49 Debian kernel: [   10.720921] ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 14 19:33:49 Debian kernel: [   10.978979]   alloc irq_desc for 30 on node -1
May 14 19:33:49 Debian kernel: [   10.978982]   alloc kstat_irqs on node -1
May 14 19:33:49 Debian kernel: [   10.978999] tg3 0000:09:00.0: irq 30 for MSI/MSI-X
May 14 19:33:49 Debian kernel: [   11.096840] ADDRCONF(NETDEV_UP): eth0: link is not ready
May 14 19:33:49 Debian kernel: [   12.386473] fuse init (API version 7.13)
May 14 19:33:50 Debian kernel: [   14.236412] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input11
May 14 19:33:52 Debian acpid: starting up with netlink and the input layer
May 14 19:33:52 Debian acpid: 42 rules loaded
May 14 19:33:52 Debian acpid: waiting for events: event logging is off
May 14 19:33:53 Debian acpid: client connected from 1296[0:0]
May 14 19:33:53 Debian acpid: 1 client rule loaded
May 14 19:33:53 Debian avahi-daemon[1334]: Found user 'avahi' (UID 105) and group 'avahi' (GID 108).
May 14 19:33:53 Debian avahi-daemon[1334]: Successfully dropped root privileges.
May 14 19:33:53 Debian avahi-daemon[1334]: avahi-daemon 0.6.27 starting up.
May 14 19:33:53 Debian avahi-daemon[1334]: Successfully called chroot().
May 14 19:33:53 Debian avahi-daemon[1334]: Successfully dropped remaining capabilities.
May 14 19:33:53 Debian avahi-daemon[1334]: No service file found in /etc/avahi/services.
May 14 19:33:53 Debian avahi-daemon[1334]: Network interface enumeration completed.
May 14 19:33:53 Debian avahi-daemon[1334]: Registering HINFO record with values 'X86_64'/'LINUX'.
May 14 19:33:53 Debian avahi-daemon[1334]: Server startup complete. Host name is Debian.local. Local service cookie is 3675122248.
May 14 19:33:53 Debian bluetoothd[1345]: Bluetooth deamon 4.66
May 14 19:33:53 Debian bluetoothd[1345]: Starting SDP server
May 14 19:33:53 Debian kernel: [   17.817512] Bluetooth: Core ver 2.15
May 14 19:33:53 Debian kernel: [   17.818079] NET: Registered protocol family 31
May 14 19:33:53 Debian kernel: [   17.818083] Bluetooth: HCI device and connection manager initialized
May 14 19:33:53 Debian kernel: [   17.818087] Bluetooth: HCI socket layer initialized
May 14 19:33:53 Debian kernel: [   17.847564] Bluetooth: L2CAP ver 2.14
May 14 19:33:53 Debian kernel: [   17.847568] Bluetooth: L2CAP socket layer initialized
May 14 19:33:53 Debian bluetoothd[1345]: Starting experimental netlink support
May 14 19:33:53 Debian bluetoothd[1345]: Failed to find Bluetooth netlink family
May 14 19:33:53 Debian bluetoothd[1345]: Failed to init netlink plugin
May 14 19:33:53 Debian kernel: [   17.892169] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
May 14 19:33:53 Debian kernel: [   17.892172] Bluetooth: BNEP filters: protocol multicast
May 14 19:33:53 Debian bluetoothd[1345]: bridge pan0 created
May 14 19:33:53 Debian kernel: [   17.899247] Bridge firewalling registered
May 14 19:33:53 Debian kernel: [   17.907081] Bluetooth: SCO (Voice Link) ver 0.6
May 14 19:33:53 Debian kernel: [   17.907084] Bluetooth: SCO socket layer initialized
May 14 19:33:53 Debian wpa_supplicant[1015]: Failed to initiate AP scan.
May 14 19:33:54 Debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
May 14 19:33:54 Debian kernel: [   18.572247] lp: driver loaded but no devices found
May 14 19:33:54 Debian kernel: [   18.613782] ppdev: user-space parallel port driver
May 14 19:33:55 Debian /usr/sbin/cron[1456]: (CRON) INFO (pidfile fd = 3)
May 14 19:33:55 Debian /usr/sbin/cron[1504]: (CRON) STARTUP (fork ok)
May 14 19:33:55 Debian /usr/sbin/cron[1504]: (CRON) INFO (Running @reboot jobs)
May 14 19:33:56 Debian udev-configure-printer: add /module/lp
May 14 19:33:56 Debian udev-configure-printer: Failed to get parent
May 14 19:33:57 Debian acpid: client connected from 1831[110:118]
May 14 19:33:57 Debian acpid: 1 client rule loaded
May 14 19:33:59 Debian wpa_supplicant[1015]: Failed to initiate AP scan.
May 14 19:34:04 Debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
May 14 19:34:05 Debian wpa_supplicant[1015]: Failed to initiate AP scan.
May 14 19:34:06 Debian polkitd[1953]: started daemon version 0.96 using authority implementation `local' version `0.96'
May 14 19:34:07 Debian gdm-simple-greeter[1948]: Gtk-WARNING: /scratch/build-area/gtk+2.0-2.20.1/gtk/gtkwidget.c:5628: widget not within a GtkWindow
May 14 19:34:11 Debian wpa_supplicant[1015]: Failed to initiate AP scan.
May 14 19:34:15 Debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
May 14 19:34:17 Debian wpa_supplicant[1015]: Failed to initiate AP scan.
May 14 19:34:20 Debian gdm-simple-greeter[1948]: WARNING: Failed to send buffer
May 14 19:34:23 Debian wpa_supplicant[1015]: Failed to initiate AP scan.
May 14 19:34:26 Debian gnome-session[2031]: WARNING: Could not launch application 'nm-applet.desktop': Unable to start application: Wykonanie procesu potomnego "nm-applet" (Nie ma takiego pliku ani katalogu) się nie powiodło
May 14 19:34:29 Debian wpa_supplicant[1015]: Failed to initiate AP scan.
May 14 19:34:30 Debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
May 14 19:34:35 Debian wpa_supplicant[1015]: Failed to initiate AP scan.
May 14 19:34:38 Debian AptDaemon: INFO: Initializing daemon
May 14 19:34:41 Debian wpa_supplicant[1015]: Failed to initiate AP scan.
May 14 19:34:45 Debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
May 14 19:34:47 Debian wpa_supplicant[1015]: Failed to initiate AP scan.
May 14 19:34:49 Debian dhclient: No DHCPOFFERS received.
May 14 19:34:49 Debian dhclient: No working leases in persistent database - sleeping.
May 14 19:34:49 Debian avahi-autoipd(eth0)[2181]: Found user 'avahi-autoipd' (UID 104) and group 'avahi-autoipd' (GID 107).
May 14 19:34:49 Debian avahi-autoipd(eth0)[2181]: Successfully called chroot().
May 14 19:34:49 Debian avahi-autoipd(eth0)[2181]: Successfully dropped root privileges.
May 14 19:34:49 Debian avahi-autoipd(eth0)[2181]: Starting with address 169.254.9.181
May 14 19:34:53 Debian wpa_supplicant[1015]: Failed to initiate AP scan.
May 14 19:34:55 Debian avahi-autoipd(eth0)[2181]: Callout BIND, address 169.254.9.181 on interface eth0
May 14 19:34:55 Debian avahi-daemon[1334]: Joining mDNS multicast group on interface eth0.IPv4 with address 169.254.9.181.
May 14 19:34:55 Debian avahi-daemon[1334]: New relevant interface eth0.IPv4 for mDNS.
May 14 19:34:55 Debian avahi-daemon[1334]: Registering new address record for 169.254.9.181 on eth0.IPv4.
May 14 19:34:59 Debian avahi-autoipd(eth0)[2181]: Successfully claimed IP address 169.254.9.181
May 14 19:34:59 Debian wpa_supplicant[1015]: Failed to initiate AP scan.
May 14 19:35:05 Debian wpa_supplicant[1015]: Failed to initiate AP scan.
May 14 19:35:07 Debian wpa_supplicant[1015]: CTRL-EVENT-TERMINATING - signal 15 received
May 14 19:35:17 Debian wpa_supplicant[2296]: Failed to initiate AP scan.
May 14 19:35:23 Debian wpa_supplicant[2296]: Failed to initiate AP scan.
May 14 19:35:29 Debian wpa_supplicant[2296]: Failed to initiate AP scan.
May 14 19:35:35 Debian wpa_supplicant[2296]: Failed to initiate AP scan.
May 14 19:35:41 Debian wpa_supplicant[2296]: Failed to initiate AP scan.
May 14 19:35:47 Debian wpa_supplicant[2296]: Failed to initiate AP scan.
May 14 19:35:53 Debian wpa_supplicant[2296]: Failed to initiate AP scan.
May 14 19:36:06 Debian wpa_supplicant[2296]: CTRL-EVENT-TERMINATING - signal 15 received
May 14 19:36:06 Debian wpa_supplicant[2383]: ctrl_iface exists and seems to be in use - cannot override it
May 14 19:36:06 Debian wpa_supplicant[2383]: Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
May 14 19:36:06 Debian wpa_supplicant[2383]: Failed to initialize control interface 'DIR=/var/run/wpa_supplicant GROUP=netdev'.#012You may have another wpa_supplicant process already running or the file was#012left by an unclean termination of wpa_supplicant in which case you will need#012to manually remove this file before starting wpa_supplicant again.
May 14 19:36:31 Debian kernel: [  175.926705] atkbd.c: Unknown key pressed (translated set 2, code 0xd5 on isa0060/serio0).
May 14 19:36:31 Debian kernel: [  175.926711] atkbd.c: Use 'setkeycodes e055 <keycode>' to make it known.
May 14 19:36:32 Debian kernel: [  176.215756] atkbd.c: Unknown key released (translated set 2, code 0xd5 on isa0060/serio0).
May 14 19:36:32 Debian kernel: [  176.215762] atkbd.c: Use 'setkeycodes e055 <keycode>' to make it known.
May 14 19:36:36 Debian kernel: [  180.836274] b43-phy0: Radio hardware status changed to ENABLED
May 14 19:37:02 Debian kernel: [  206.288281] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
May 14 19:37:07 Debian kernel: [  211.737603] ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 14 19:37:10 Debian wpa_supplicant[2461]: Trying to associate with 00:24:a5:f4:1a:39 (SSID='none' freq=2437 MHz)
May 14 19:37:10 Debian kernel: [  214.392659] wlan0: direct probe to AP 00:24:a5:f4:1a:39 (try 1)
May 14 19:37:10 Debian kernel: [  214.396155] wlan0: direct probe responded
May 14 19:37:10 Debian kernel: [  214.396161] wlan0: authenticate with AP 00:24:a5:f4:1a:39 (try 1)
May 14 19:37:10 Debian kernel: [  214.398506] wlan0: authenticated
May 14 19:37:10 Debian kernel: [  214.398551] wlan0: associate with AP 00:24:a5:f4:1a:39 (try 1)
May 14 19:37:10 Debian wpa_supplicant[2461]: Associated with 00:24:a5:f4:1a:39
May 14 19:37:10 Debian kernel: [  214.401708] wlan0: RX AssocResp from 00:24:a5:f4:1a:39 (capab=0x411 status=0 aid=5)
May 14 19:37:10 Debian kernel: [  214.401713] wlan0: associated
May 14 19:37:10 Debian kernel: [  214.403687] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
May 14 19:37:10 Debian kernel: [  214.494135] padlock: VIA PadLock not detected.
May 14 19:37:10 Debian wpa_supplicant[2461]: WPA: Key negotiation completed with 00:24:a5:f4:1a:39 [PTK=CCMP GTK=CCMP]
May 14 19:37:10 Debian wpa_supplicant[2461]: CTRL-EVENT-CONNECTED - Connection to 00:24:a5:f4:1a:39 completed (auth) [id=0 id_str=]
May 14 19:37:11 Debian avahi-daemon[1334]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::224:2bff:fe47:21cc.
May 14 19:37:11 Debian avahi-daemon[1334]: New relevant interface wlan0.IPv6 for mDNS.
May 14 19:37:11 Debian avahi-daemon[1334]: Registering new address record for fe80::224:2bff:fe47:21cc on wlan0.*.
May 14 19:37:20 Debian kernel: [  224.700048] wlan0: no IPv6 routers present
May 14 19:39:15 Debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
May 14 19:39:20 Debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
May 14 19:39:31 Debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
May 14 19:39:36 Debian kernel: [  360.312264] wlan0: deauthenticating from 00:24:a5:f4:1a:39 by local choice (reason=3)
May 14 19:39:36 Debian wpa_supplicant[2461]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
May 14 19:39:39 Debian wpa_supplicant[2461]: Trying to associate with 00:24:a5:f4:1a:39 (SSID='none' freq=2437 MHz)
May 14 19:39:39 Debian kernel: [  363.394412] wlan0: direct probe to AP 00:24:a5:f4:1a:39 (try 1)
May 14 19:39:39 Debian kernel: [  363.397862] wlan0: direct probe responded
May 14 19:39:39 Debian kernel: [  363.397869] wlan0: authenticate with AP 00:24:a5:f4:1a:39 (try 1)
May 14 19:39:39 Debian kernel: [  363.404301] wlan0: authenticated
May 14 19:39:39 Debian kernel: [  363.404353] wlan0: associate with AP 00:24:a5:f4:1a:39 (try 1)
May 14 19:39:39 Debian kernel: [  363.407445] wlan0: RX AssocResp from 00:24:a5:f4:1a:39 (capab=0x411 status=0 aid=5)
May 14 19:39:39 Debian kernel: [  363.407451] wlan0: associated
May 14 19:39:39 Debian wpa_supplicant[2461]: Associated with 00:24:a5:f4:1a:39
May 14 19:39:39 Debian wpa_supplicant[2461]: WPA: Key negotiation completed with 00:24:a5:f4:1a:39 [PTK=CCMP GTK=CCMP]
May 14 19:39:39 Debian wpa_supplicant[2461]: CTRL-EVENT-CONNECTED - Connection to 00:24:a5:f4:1a:39 completed (reauth) [id=0 id_str=]
May 14 19:39:39 Debian wpa_action: WPA_IFACE=wlan0 WPA_ACTION=CONNECTED
May 14 19:39:39 Debian wpa_action: WPA_ID=0 WPA_ID_STR= WPA_CTRL_DIR=/var/run/wpa_supplicant
May 14 19:39:39 Debian wpa_action: ifup wlan0=default
May 14 19:39:39 Debian dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1
May 14 19:39:39 Debian dhclient: Copyright 2004-2010 Internet Systems Consortium.
May 14 19:39:39 Debian dhclient: All rights reserved.
May 14 19:39:39 Debian dhclient: For info, please visit https://www.isc.org/software/dhcp/
May 14 19:39:39 Debian dhclient: 
May 14 19:39:39 Debian dhclient: Listening on LPF/wlan0/00:24:2b:47:21:cc
May 14 19:39:39 Debian dhclient: Sending on   LPF/wlan0/00:24:2b:47:21:cc
May 14 19:39:39 Debian dhclient: Sending on   Socket/fallback
May 14 19:39:39 Debian dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
May 14 19:39:39 Debian dhclient: DHCPOFFER from 192.168.1.1
May 14 19:39:39 Debian dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
May 14 19:39:39 Debian dhclient: DHCPACK from 192.168.1.1
May 14 19:39:39 Debian avahi-daemon[1334]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.162.
May 14 19:39:39 Debian avahi-daemon[1334]: New relevant interface wlan0.IPv4 for mDNS.
May 14 19:39:39 Debian avahi-daemon[1334]: Registering new address record for 192.168.1.162 on wlan0.IPv4.
May 14 19:39:39 Debian dhclient: bound to 192.168.1.162 -- renewal in 21486 seconds.
May 14 19:39:39 Debian wpa_action: creating sendsigs omission pidfile: /lib/init/rw/sendsigs.omit.d/wpasupplicant.wpa_supplicant.wlan0.pid
May 14 19:39:39 Debian wpa_action: bssid=00:24:a5:f4:1a:39
May 14 19:39:39 Debian wpa_action: ssid=none
May 14 19:39:39 Debian wpa_action: id=0
May 14 19:39:39 Debian wpa_action: pairwise_cipher=CCMP
May 14 19:39:39 Debian wpa_action: group_cipher=CCMP
May 14 19:39:39 Debian wpa_action: key_mgmt=WPA2-PSK
May 14 19:39:39 Debian wpa_action: wpa_state=COMPLETED
May 14 19:39:39 Debian wpa_action: ip_address=192.168.1.162
May 14 19:39:49 Debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
May 14 19:40:02 Debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
May 14 19:40:09 Debian wpa_supplicant[2461]: WPA: Group rekeying completed with 00:24:a5:f4:1a:39 [GTK=CCMP]
May 14 19:40:10 Debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
May 14 19:40:16 Debian dhclient: No DHCPOFFERS received.
May 14 19:40:16 Debian dhclient: No working leases in persistent database - sleeping.
May 14 19:40:38 Debian AptDaemon: INFO: Quiting due to inactivity
May 14 19:40:38 Debian AptDaemon: INFO: Shutdown was requested
May 14 19:43:34 Debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
May 14 19:43:42 Debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
May 14 19:43:56 Debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
May 14 19:44:08 Debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21
May 14 19:44:29 Debian dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
May 14 19:44:35 Debian dhclient: No DHCPOFFERS received.
May 14 19:44:35 Debian dhclient: No working leases in persistent database - sleeping.

LoLedman · 2013-05-18 20:17:44

Jeszcze takie offtopowe pytanie, jeżeli zaktualizuje do Wheezy lub Jessie będę w stanie skonfigurować to tak jak jest tutaj opisane?

Jacekalex · 2013-05-19 02:20:16

Skonfigurować możesz.
Ale czy wszystko na 100% będzie chodziło tak, jak oczekujesz, gwarancji nie ma żadnej, chociaż w Wheezym będzie można ogarnąć sprawę, to w końcu stabilne wydanie, natomiast w Jessie może być rożnie.
Jessie to w końcu kilka tygodni temu był Sid, i conieco humorków i temperamentu z Sida pewnie w nim jeszcze zostało. :D

LoLedman · 2013-05-20 18:42:37

Dobra :D apt-get dist-upgrade i mamy Wheezy, wszystko działa jak powinno :D. Powie mi może ktoś jak oznaczyć temat jako rozwiązany?

yossarian · 2013-05-20 18:47:49

LoLedman napisał(-a):
Jeszcze takie offtopowe pytanie, jeżeli zaktualizuje do Wheezy lub Jessie będę w stanie skonfigurować to tak jak jest tutaj opisane?

To był/jest jakiś błąd w sterowniku.
Generalnie powinno działać bez tego pliku i kiedyś przy którejś aktualizacji pewnie będzie już niepotrzebny.

Forum Debian Users Gang

Ogłoszenie

#51 2013-05-11 17:50:10

ilin - Palacz

Re: BCM4312 LP-PHY Sieci WPA2

Kod:

#52 2013-05-13 08:10:22

LoLedman - Użytkownik

Re: BCM4312 LP-PHY Sieci WPA2

#53 2013-05-13 08:22:51

yossarian - Szczawiożerca

Re: BCM4312 LP-PHY Sieci WPA2

#54 2013-05-13 09:03:14

Jacekalex - Podobno człowiek...;)

Re: BCM4312 LP-PHY Sieci WPA2

LoLedman napisał(-a):

#55 2013-05-13 09:30:07

yossarian - Szczawiożerca

Re: BCM4312 LP-PHY Sieci WPA2

#56 2013-05-13 14:07:46

Jacekalex - Podobno człowiek...;)

Re: BCM4312 LP-PHY Sieci WPA2

yossarian napisał(-a):

#57 2013-05-13 18:01:41

LoLedman - Użytkownik

Re: BCM4312 LP-PHY Sieci WPA2

#58 2013-05-13 19:32:57

yossarian - Szczawiożerca

Re: BCM4312 LP-PHY Sieci WPA2

Kod:

Kod:

Kod:

#59 2013-05-14 19:52:37

LoLedman - Użytkownik

Re: BCM4312 LP-PHY Sieci WPA2

Kod:

#60 2013-05-18 20:17:44

LoLedman - Użytkownik

Re: BCM4312 LP-PHY Sieci WPA2

#61 2013-05-19 02:20:16

Jacekalex - Podobno człowiek...;)

Re: BCM4312 LP-PHY Sieci WPA2

#62 2013-05-20 18:42:37

LoLedman - Użytkownik

Re: BCM4312 LP-PHY Sieci WPA2

#63 2013-05-20 18:47:49

yossarian - Szczawiożerca

Re: BCM4312 LP-PHY Sieci WPA2

LoLedman napisał(-a):

Stopka forum