Polskie Forum Użytkowników Debiana

Polski portal użytkowników dystrybucji Debian GNU/Linux, dyskusje, artykuły, nowości, blog, porady, pomoc.
https://593930.wb34atkl.asia/

[+] B4318 - po aktualizacji network managera nie widz

https://593930.wb34atkl.asia/viewtopic.php?t=12345

Strona 1 z 1

[+] B4318 - po aktualizacji network managera nie widzę sieci

: 03 marca 2009, 00:56
autor: olekj
Zaktualizowałem ostatnio network managera i od tego czasu karta BCM4318 przestała wykrywać mi sieci. Sterowniki są zainstalowane (b43-fwcutter).

Sytuacja w etc/network/interface:

Kod: Zaznacz cały

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
#allow-hotplug eth0
#iface eth0 inet dhcp
wlan0 No scan results

iwconfig:

Kod: Zaznacz cały

lo        no wireless extensions.

eth0      no wireless extensions.

wmaster0  no wireless extensions.

wlan0     IEEE 802.11  ESSID:""  
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated   
          Tx-Power=20 dBm   
          Retry min limit:7   RTS thr :o ff   Fragment thr=2352 B   
          Encryption key :o ff
          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
iwlist wlan0 scanning:

Kod: Zaznacz cały

wlan0     No scan results
lspci:

Kod: Zaznacz cały

02:03.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
Jeszcze na laptopie zawsze paliła mi się dioda że karta jest włączona - teraz się nie pali. Próba zapalenia od razu kończy się automatycznym zgaszeniem. W czym tkwi problem?

: 03 marca 2009, 10:07
autor: Utumno
sprobuj iwlist scan i wklej tutaj co sie pojawi w /var/log/syslog.

: 03 marca 2009, 15:09
autor: olekj
iwlist scan:

Kod: Zaznacz cały

lo        Interface doesn't support scanning.

eth0      Interface doesn't support scanning.

wmaster0  Interface doesn't support scanning.

wlan0     No scan results
var/log/syslog
Mar 3 14:36:55 host-81-190-236-5 acpid: starting up with proc fs
Mar 3 14:36:56 host-81-190-236-5 acpid: 81 rules loaded
Mar 3 14:36:56 host-81-190-236-5 acpid: waiting for events: event logging is off
Mar 3 14:36:56 host-81-190-236-5 avahi-daemon[2576]: Found user 'avahi' (UID 106) and group 'avahi' (GID 110).
Mar 3 14:36:56 host-81-190-236-5 avahi-daemon[2576]: Successfully dropped root privileges.
Mar 3 14:36:56 host-81-190-236-5 avahi-daemon[2576]: avahi-daemon 0.6.24 starting up.
Mar 3 14:36:56 host-81-190-236-5 avahi-daemon[2576]: Successfully called chroot().
Mar 3 14:36:56 host-81-190-236-5 avahi-daemon[2576]: Successfully dropped remaining capabilities.
Mar 3 14:36:56 host-81-190-236-5 avahi-daemon[2576]: No service file found in /etc/avahi/services.
Mar 3 14:36:56 host-81-190-236-5 kernel: [ 20.987939] NET: Registered protocol family 10
Mar 3 14:36:56 host-81-190-236-5 kernel: [ 20.988426] lo: Disabled Privacy Extensions
Mar 3 14:36:56 host-81-190-236-5 avahi-daemon[2576]: Network interface enumeration completed.
Mar 3 14:36:56 host-81-190-236-5 avahi-daemon[2576]: Registering HINFO record with values 'I686'/'LINUX'.
Mar 3 14:36:56 host-81-190-236-5 avahi-daemon[2576]: Server startup complete. Host name is host-81-190-236-5.local. Local service cookie is 1089736588.
Mar 3 14:36:57 host-81-190-236-5 kernel: [ 22.051029] lp0: using parport0 (interrupt-driven).
Mar 3 14:36:57 host-81-190-236-5 kernel: [ 22.089980] ppdev: user-space parallel port driver
Mar 3 14:37:00 host-81-190-236-5 atieventsd[3008]: ATI External Events Daemon started...
Mar 3 14:37:00 host-81-190-236-5 atieventsd[3008]: Event daemon control socket created
Mar 3 14:37:00 host-81-190-236-5 acpid: client connected from 3008[0:0]
Mar 3 14:37:00 host-81-190-236-5 acpid: 1 client rule loaded
Mar 3 14:37:00 host-81-190-236-5 atieventsd[3008]: acpid connection established
Mar 3 14:37:01 host-81-190-236-5 nmbd[3096]: [2009/03/03 14:37:01, 0] nmbd/asyncdns.c:start_async_dns(155)
Mar 3 14:37:01 host-81-190-236-5 nmbd[3096]: started asyncdns process 3097
Mar 3 14:37:01 host-81-190-236-5 nmbd[3096]: [2009/03/03 14:37:01, 0] nmbd/nmbd_subnetdb.c:create_subnets(206)
Mar 3 14:37:01 host-81-190-236-5 nmbd[3096]: create_subnets: No local IPv4 non-loopback interfaces !
Mar 3 14:37:01 host-81-190-236-5 nmbd[3096]: [2009/03/03 14:37:01, 0] nmbd/nmbd_subnetdb.c:create_subnets(207)
Mar 3 14:37:01 host-81-190-236-5 nmbd[3096]: create_subnets: Waiting for an interface to appear ...
Mar 3 14:37:03 host-81-190-236-5 acpid: client connected from 3154[107:114]
Mar 3 14:37:03 host-81-190-236-5 acpid: 1 client rule loaded
Mar 3 14:37:03 host-81-190-236-5 hcid[3175]: Bluetooth HCI daemon
Mar 3 14:37:03 host-81-190-236-5 hcid[3175]: Parsing /etc/bluetooth/main.conf failed: No such file or directory
Mar 3 14:37:03 host-81-190-236-5 hcid[3175]: Starting SDP server
Mar 3 14:37:03 host-81-190-236-5 kernel: [ 28.092741] Bluetooth: L2CAP ver 2.9
Mar 3 14:37:03 host-81-190-236-5 kernel: [ 28.092741] Bluetooth: L2CAP socket layer initialized
Mar 3 14:37:03 host-81-190-236-5 hcid[3175]: HCI dev 0 registered
Mar 3 14:37:03 host-81-190-236-5 hcid[3175]: HCI dev 0 up
Mar 3 14:37:03 host-81-190-236-5 hcid[3175]: Device hci0 has been added
Mar 3 14:37:03 host-81-190-236-5 kernel: [ 28.114254] Bluetooth: RFCOMM socket layer initialized
Mar 3 14:37:03 host-81-190-236-5 kernel: [ 28.114274] Bluetooth: RFCOMM TTY layer initialized
Mar 3 14:37:03 host-81-190-236-5 kernel: [ 28.114276] Bluetooth: RFCOMM ver 1.8
Mar 3 14:37:03 host-81-190-236-5 hcid[3175]: Starting security manager 0
Mar 3 14:37:03 host-81-190-236-5 hcid[3175]: Device hci0 has been activated
Mar 3 14:37:04 host-81-190-236-5 NetworkManager: <info> starting...
Mar 3 14:37:04 host-81-190-236-5 NetworkManager: <info> (eth0): new Ethernet device (driver: '8139too')
Mar 3 14:37:04 host-81-190-236-5 NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_18_f3_ca_a7_db
Mar 3 14:37:04 host-81-190-236-5 NetworkManager: <info> (wlan0): driver supports SSID scans (scan_capa 0x01).
Mar 3 14:37:04 host-81-190-236-5 NetworkManager: <info> (wlan0): new 802.11 WiFi device (driver: 'b43-pci-bridge')
Mar 3 14:37:04 host-81-190-236-5 NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_18_f3_73_b6_34
Mar 3 14:37:04 host-81-190-236-5 NetworkManager: <info> Trying to start the supplicant...
Mar 3 14:37:04 host-81-190-236-5 NetworkManager: <info> Trying to start the system settings daemon...
Mar 3 14:37:04 host-81-190-236-5 pcscd: pcscdaemon.c:505:main() pcsc-lite 1.5.2 daemon ready.
Mar 3 14:37:04 host-81-190-236-5 nm-system-settings: SCPlugin-Ifupdown: init!
Mar 3 14:37:04 host-81-190-236-5 nm-system-settings: SCPlugin-Ifupdown: update_system_hostname
Mar 3 14:37:04 host-81-190-236-5 nm-system-settings: SCPluginIfupdown: management mode: unmanaged
Mar 3 14:37:04 host-81-190-236-5 nm-system-settings: SCPlugin-Ifupdown: devices added (udi: /org/freedesktop/Hal/devices/net_00_18_f3_ca_a7_db, iface: eth0)
Mar 3 14:37:04 host-81-190-236-5 nm-system-settings: SCPlugin-Ifupdown: devices added (udi: /org/freedesktop/Hal/devices/net_00_18_f3_73_b6_34, iface: wlan0)
Mar 3 14:37:04 host-81-190-236-5 nm-system-settings: SCPlugin-Ifupdown: end _init.
Mar 3 14:37:04 host-81-190-236-5 nm-system-settings: Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list.
Mar 3 14:37:04 host-81-190-236-5 nm-system-settings: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Mar 3 14:37:04 host-81-190-236-5 nm-system-settings: SCPlugin-Ifupdown: (151707936) ... get_connections.
Mar 3 14:37:04 host-81-190-236-5 nm-system-settings: SCPlugin-Ifupdown: (151707936) connections count: 0
Mar 3 14:37:04 host-81-190-236-5 anacron[3230]: Anacron 2.3 started on 2009-03-03
Mar 3 14:37:05 host-81-190-236-5 anacron[3230]: Normal exit (0 jobs run)
Mar 3 14:37:05 host-81-190-236-5 NetworkManager: <info> (wlan0): supplicant manager state: down -> idle
Mar 3 14:37:05 host-81-190-236-5 nm-system-settings: Ifupdown: get unmanaged devices count: 0
Mar 3 14:37:05 host-81-190-236-5 /usr/sbin/cron[3257]: (CRON) INFO (pidfile fd = 3)
Mar 3 14:37:05 host-81-190-236-5 /usr/sbin/cron[3258]: (CRON) STARTUP (fork ok)
Mar 3 14:37:05 host-81-190-236-5 /usr/sbin/cron[3258]: (CRON) INFO (Running @reboot jobs)
Mar 3 14:37:06 host-81-190-236-5 acpid: client connected from 3316[0:0]
Mar 3 14:37:06 host-81-190-236-5 acpid: 1 client rule loaded
Mar 3 14:37:08 host-81-190-236-5 kernel: [ 32.254742] [fglrx] Maximum main memory to use for locked dma buffers: 804 MBytes.
Mar 3 14:37:08 host-81-190-236-5 kernel: [ 32.254779] [fglrx] vendor: 1002 device: 5a62 count: 1
Mar 3 14:37:08 host-81-190-236-5 kernel: [ 32.255107] [fglrx] ioport: bar 1, base 0x9800, size: 0x100
Mar 3 14:37:08 host-81-190-236-5 kernel: [ 32.255140] ACPI: PCI Interrupt 0000:01:05.0[A] -> GSI 17 (level, low) -> IRQ 17
Mar 3 14:37:08 host-81-190-236-5 kernel: [ 32.256256] [fglrx] Driver built-in PAT support is enabled successfully
Mar 3 14:37:08 host-81-190-236-5 kernel: [ 32.256292] [fglrx] module loaded - fglrx 8.58.2 [Feb 4 2009] with 1 minors
Mar 3 14:37:09 host-81-190-236-5 NetworkManager: <info> (eth0): device state change: 1 -> 2
Mar 3 14:37:09 host-81-190-236-5 NetworkManager: <info> (eth0): bringing up device.
Mar 3 14:37:09 host-81-190-236-5 kernel: [ 33.232361] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Mar 3 14:37:09 host-81-190-236-5 NetworkManager: <info> (eth0): preparing device.
Mar 3 14:37:09 host-81-190-236-5 NetworkManager: <info> (eth0): deactivating device (reason: 2).
Mar 3 14:37:09 host-81-190-236-5 NetworkManager: <info> (wlan0): device state change: 1 -> 2
Mar 3 14:37:09 host-81-190-236-5 NetworkManager: <info> (wlan0): bringing up device.
Mar 3 14:37:09 host-81-190-236-5 nm-system-settings: Adding default connection 'Auto eth0' for /org/freedesktop/Hal/devices/net_00_18_f3_ca_a7_db
Mar 3 14:37:09 host-81-190-236-5 kernel: [ 33.260434] input: b43-phy0 as /class/input/input9
Mar 3 14:37:09 host-81-190-236-5 kernel: [ 33.352066] firmware: requesting b43/ucode5.fw
Mar 3 14:37:09 host-81-190-236-5 kernel: [ 33.419486] firmware: requesting b43/pcm5.fw
Mar 3 14:37:09 host-81-190-236-5 kernel: [ 33.442451] firmware: requesting b43/b0g0initvals5.fw
Mar 3 14:37:09 host-81-190-236-5 kernel: [ 33.464315] firmware: requesting b43/b0g0bsinitvals5.fw
Mar 3 14:37:09 host-81-190-236-5 kernel: [ 33.588044] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
Mar 3 14:37:10 host-81-190-236-5 avahi-daemon[2576]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::218:f3ff:feca:a7db.
Mar 3 14:37:10 host-81-190-236-5 avahi-daemon[2576]: New relevant interface eth0.IPv6 for mDNS.
Mar 3 14:37:10 host-81-190-236-5 avahi-daemon[2576]: Registering new address record for fe80::218:f3ff:feca:a7db on eth0.*.
Mar 3 14:37:10 host-81-190-236-5 kernel: [ 34.650586] [fglrx] GART Table is not in FRAME_BUFFER range
Mar 3 14:37:10 host-81-190-236-5 kernel: [ 34.673179] [fglrx] Firegl kernel thread PID: 3395
Mar 3 14:37:10 host-81-190-236-5 kernel: [ 34.675132] [fglrx] Gart USWC size:378 M.
Mar 3 14:37:10 host-81-190-236-5 kernel: [ 34.675142] [fglrx] Gart cacheable size:60 M.
Mar 3 14:37:10 host-81-190-236-5 kernel: [ 34.675148] [fglrx] Reserved FB block: Shared offset:0, size:40000
Mar 3 14:37:10 host-81-190-236-5 kernel: [ 34.675151] [fglrx] Reserved FB block: Unshared offset:7ff5000, size:b000
Mar 3 14:37:10 host-81-190-236-5 kernel: [ 35.000385] Registered led device: b43-phy0::tx
Mar 3 14:37:10 host-81-190-236-5 kernel: [ 35.000409] Registered led device: b43-phy0::rx
Mar 3 14:37:10 host-81-190-236-5 kernel: [ 35.000427] Registered led device: b43-phy0::assoc
Mar 3 14:37:10 host-81-190-236-5 kernel: [ 35.000449] Registered led device: b43-phy0::radio
Mar 3 14:37:10 host-81-190-236-5 kernel: [ 35.000537] b43-phy0: Radio hardware status changed to DISABLED
Mar 3 14:37:10 host-81-190-236-5 kernel: [ 35.060655] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Mar 3 14:37:10 host-81-190-236-5 NetworkManager: <info> (wlan0): preparing device.
Mar 3 14:37:10 host-81-190-236-5 NetworkManager: <info> (wlan0): deactivating device (reason: 2).
Mar 3 14:37:10 host-81-190-236-5 NetworkManager: <info> (eth0): carrier now ON (device state 2)
Mar 3 14:37:10 host-81-190-236-5 NetworkManager: <info> (eth0): device state change: 2 -> 3
Mar 3 14:37:10 host-81-190-236-5 NetworkManager: <info> (wlan0): device state change: 2 -> 3
Mar 3 14:37:10 host-81-190-236-5 NetworkManager: <info> Activation (eth0) starting connection 'Auto eth0'
Mar 3 14:37:10 host-81-190-236-5 NetworkManager: <info> (eth0): device state change: 3 -> 4
Mar 3 14:37:10 host-81-190-236-5 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 3 14:37:10 host-81-190-236-5 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Mar 3 14:37:10 host-81-190-236-5 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Mar 3 14:37:10 host-81-190-236-5 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Mar 3 14:37:10 host-81-190-236-5 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Mar 3 14:37:10 host-81-190-236-5 NetworkManager: <info> (eth0): device state change: 4 -> 5
Mar 3 14:37:10 host-81-190-236-5 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Mar 3 14:37:10 host-81-190-236-5 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Mar 3 14:37:10 host-81-190-236-5 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Mar 3 14:37:10 host-81-190-236-5 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Mar 3 14:37:10 host-81-190-236-5 NetworkManager: <info> (eth0): device state change: 5 -> 7
Mar 3 14:37:10 host-81-190-236-5 NetworkManager: <info> Activation (eth0) Beginning DHCP transaction.
Mar 3 14:37:11 host-81-190-236-5 NetworkManager: <info> dhclient started with pid 3403
Mar 3 14:37:11 host-81-190-236-5 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Mar 3 14:37:11 host-81-190-236-5 dhclient: Internet Systems Consortium DHCP Client V3.1.1
Mar 3 14:37:11 host-81-190-236-5 dhclient: Copyright 2004-2008 Internet Systems Consortium.
Mar 3 14:37:11 host-81-190-236-5 dhclient: All rights reserved.
Mar 3 14:37:11 host-81-190-236-5 dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Mar 3 14:37:11 host-81-190-236-5 dhclient:
Mar 3 14:37:11 host-81-190-236-5 dhclient: wmaster0: unknown hardware address type 801
Mar 3 14:37:11 host-81-190-236-5 NetworkManager: <info> (wlan0): supplicant interface state: starting -> ready
Mar 3 14:37:11 host-81-190-236-5 NetworkManager: <info> DHCP: device eth0 state changed (null) -> preinit
Mar 3 14:37:11 host-81-190-236-5 dhclient: wmaster0: unknown hardware address type 801
Mar 3 14:37:11 host-81-190-236-5 dhclient: Listening on LPF/eth0/00:18:f3:ca:a7:db
Mar 3 14:37:11 host-81-190-236-5 dhclient: Sending on LPF/eth0/00:18:f3:ca:a7:db
Mar 3 14:37:11 host-81-190-236-5 dhclient: Sending on Socket/fallback
Mar 3 14:37:13 host-81-190-236-5 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
Mar 3 14:37:13 host-81-190-236-5 dhclient: DHCPOFFER from 192.168.1.1
Mar 3 14:37:13 host-81-190-236-5 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Mar 3 14:37:13 host-81-190-236-5 dhclient: DHCPACK from 192.168.1.1
Mar 3 14:37:13 host-81-190-236-5 NetworkManager: <info> DHCP: device eth0 state changed preinit -> bound
Mar 3 14:37:13 host-81-190-236-5 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
Mar 3 14:37:13 host-81-190-236-5 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) started...
Mar 3 14:37:13 host-81-190-236-5 NetworkManager: <info> address 192.168.1.116
Mar 3 14:37:13 host-81-190-236-5 NetworkManager: <info> prefix 24 (255.255.255.0)
Mar 3 14:37:13 host-81-190-236-5 NetworkManager: <info> gateway 192.168.1.1
Mar 3 14:37:13 host-81-190-236-5 NetworkManager: <info> nameserver '192.168.1.1'
Mar 3 14:37:13 host-81-190-236-5 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Mar 3 14:37:13 host-81-190-236-5 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) complete.
Mar 3 14:37:13 host-81-190-236-5 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Mar 3 14:37:13 host-81-190-236-5 avahi-daemon[2576]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.116.
Mar 3 14:37:13 host-81-190-236-5 avahi-daemon[2576]: New relevant interface eth0.IPv4 for mDNS.
Mar 3 14:37:13 host-81-190-236-5 avahi-daemon[2576]: Registering new address record for 192.168.1.116 on eth0.IPv4.
Mar 3 14:37:13 host-81-190-236-5 dhclient: bound to 192.168.1.116 -- renewal in 41540 seconds.
Mar 3 14:37:14 host-81-190-236-5 NetworkManager: <info> (eth0): writing resolv.conf to /sbin/resolvconf
Mar 3 14:37:15 host-81-190-236-5 NetworkManager: <info> (eth0): device state change: 7 -> 8
Mar 3 14:37:15 host-81-190-236-5 NetworkManager: <info> (eth0): writing resolv.conf to /sbin/resolvconf
Mar 3 14:37:15 host-81-190-236-5 NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.
Mar 3 14:37:15 host-81-190-236-5 NetworkManager: <info> Activation (eth0) successful, device activated.
Mar 3 14:37:15 host-81-190-236-5 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Mar 3 14:37:19 host-81-190-236-5 kernel: [ 43.584048] eth0: no IPv6 routers present
Mar 3 14:37:19 host-81-190-236-5 kdm_greet[3442]: Cannot open default user face

: 03 marca 2009, 18:57
autor: Utumno
1) Jaka wersja n-m?
2) Jaka wersja kernela (do n-m 0.7 trzeba mieć >= 2.6.27!)?
3) Co to znaczy ,,nie widzę sieci''. Zdefiniuj to precyzyjniej.

: 04 marca 2009, 12:03
autor: kmir
Witam. Zaktualizowałem system - w tym NetworkManagera do wersji 0.7. Wifi przestało mi działać (urządzenie nie jest gotowe). Jak mogę downgradować nm do wersji 0.6?

: 04 marca 2009, 12:33
autor: pavbaranov
Sprawdź, czy nie masz w cache APTa, jeśli tak - to po prostu zainstaluj ręcznie przed dpkg.

: 04 marca 2009, 12:38
autor: kmir
Jak to sprawdzić (przepraszam za podstawowe pytania?

Edit:
Nie ma w cache. Co mogę jeszcze zrobić?

: 04 marca 2009, 15:43
autor: wieszti
Mnie też po aktualizacji Network Managera do 0.7 przestało działać wifi. Poradziłem sobie ustawiając wifi na sztywno w /etc/network/interfaces. Może spróbuj zamienić menadżera na wicd.

: 04 marca 2009, 16:27
autor: kmir
Dziękuję! Wicd śmiga świetnie.

: 04 marca 2009, 20:51
autor: wieszti
Cieszę się że mogłem pomóc. Polecam się na przyszłość :)
Strefa czasowa UTC+01:00
Strona 1 z 1

Technologię dostarcza phpBB® Forum Software © phpBB Limited

Polski pakiet językowy dostarcza phpBB.pl