Nieuws:

We zijn er weer.

Na lange tijd van afwezigheid zijn we er weer  :laugh:
We hebben alle wachtwoorden gereset, je oude wachtwoord werkt niet meer.Je moet via het "wachtwoord vergeten"-linkje je wachtwoord resetten. Je krijgt hiervoor een mailtje op het adres dat je bij ons geregistreerd hebt.

De komende tijd zijn we nog druk bezig om de rest van de site op te bouwen, dus het kan zijn dat sommige onderdelen (tijdelijk) niet werken.

Welkom, Gast. Alsjeblieft inloggen of registreren.
Heb je de activerings-mail niet ontvangen?

Auteur Topic: ineens problemen met linksys wusb54GC (wireless usb)  (gelezen 1211 keer)

rokinrob

  • Gast
ineens problemen met linksys wusb54GC (wireless usb)
« Gepost op: 2008/08/07, 17:48:51 »
Ongeveer een half jaar geleden heb ik 2 wusb54GC sticks gekocht. Een voor mijn laptop en een voor mijn desktopcomputer. Beide draaien Ubuntu (sinds hardy er is draaien ze op hardy; schone install gedaan). En op beide werkten de sticks plug en play.

Sinds een week of 2 valt de verbinding op de laptop regelmatig helemaal weg en is niet meer te herstellen zonder opnieuw op te starten. Soms moet dit wel meerdere keren achter elkaar....
Op de desktop perfecte verbinding.
Heb de sticks van beide machines ook al even omgewisseld om uit te sluiten dat er een stick kapot is. Probleem bij de laptop blijft, desktop blijft probleemloos draaien.

Het gaat om een Asus A7D laptop.

Waar zou dit aan kunnen liggen?

Alvast bedankt voor jullie suggesties.

Groeten,
Rob

Offline Pjotr

  • Lid
    • http://sites.google.com/site/computertip
  • Steunpunt: Nee
ineens problemen met linksys wusb54GC (wireless usb)
« Reactie #1 Gepost op: 2008/08/07, 18:30:50 »
Het zou kunnen liggen aan de USB-poort op de flaptop (beschadigd?): probeer eens een andere USB-poort?

rokinrob

  • Gast
ineens problemen met linksys wusb54GC (wireless usb)
« Reactie #2 Gepost op: 2008/08/08, 18:54:02 »
Ik wil nog niet te vroeg juichen, maar het lijkt erop dat het gebruiken van een andere USB-poort de zaak heeft opgelost; vandaag nog geen problemen gehad en hij draait toch al weer een aantal uren.

Bedankt!

rokinrob

  • Gast
ineens problemen met linksys wusb54GC (wireless usb)
« Reactie #3 Gepost op: 2008/08/09, 12:03:51 »
En toch te vroeg gejuicht.

De verbinding op zich blijft nu goed, alleen na een paar minuten kom ik niet meer op internet, terwijl de verbinding er wel is (iets van 70% sterkte, dus prima).

Ik heb met copy en paste wat stukjes uit de logs gehaald, zie hieronder. Ik heb het idee dat daar wel iets instaat wat mis gaat, maar ik heb zelf te weinig kennis om er mee te doen.

Alle hulp is welkom...

Groeten,
Rob

/var/log/messages

Aug  9 11:27:36 harosabo-vehikel kernel: [  193.732641] ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug  9 11:27:36 harosabo-vehikel kernel: [  193.734046] ADDRCONF(NETDEV_UP): wlan1: link is not ready
Aug  9 11:27:44 harosabo-vehikel dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan1 for sub-path wlan1.dbus.get.reason
Aug  9 11:27:50 harosabo-vehikel kernel: [   94.915057] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Aug  9 11:27:56 harosabo-vehikel dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan1 for sub-path wlan1.dbus.get.host_name
Aug  9 11:27:56 harosabo-vehikel dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan1 for sub-path wlan1.dbus.get.nis_domain
Aug  9 11:27:56 harosabo-vehikel dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan1 for sub-path wlan1.dbus.get.nis_servers
Aug  9 11:27:56 harosabo-vehikel dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan1 for sub-path wlan1.dbus.get.interface_mtu

/var/log/syslog

Aug  9 11:27:57 harosabo-vehikel NetworkManager:  Clearing nscd hosts cache.
Aug  9 11:27:57 harosabo-vehikel NetworkManager:  nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory))  
Aug  9 11:27:57 harosabo-vehikel NetworkManager:  Activation (wlan1) successful, device activated.
Aug  9 11:27:57 harosabo-vehikel NetworkManager:  Activation (wlan1) Finish handler scheduled.
Aug  9 11:27:57 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 5 of 5 (IP Configure Commit) complete.
Aug  9 11:27:59 harosabo-vehikel avahi-daemon[5199]: Registering new address record for fe80::21d:7eff:fe11:707c on wlan1.*.
Aug  9 11:27:59 harosabo-vehikel ntpdate[6238]: adjust time server 91.189.94.4 offset 0.481293 sec
Aug  9 11:28:04 harosabo-vehikel dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
Aug  9 11:28:08 harosabo-vehikel kernel: [  242.462432] wlan1: no IPv6 routers present
Aug  9 11:28:16 harosabo-vehikel dhclient: No DHCPOFFERS received.
Aug  9 11:28:16 harosabo-vehikel avahi-autoipd(eth0)[6271]: Found user 'avahi-autoipd' (UID 105) and group 'avahi-autoipd' (GID 113).
Aug  9 11:28:16 harosabo-vehikel avahi-autoipd(eth0)[6271]: Successfully called chroot().
Aug  9 11:28:16 harosabo-vehikel avahi-autoipd(eth0)[6271]: Successfully dropped root privileges.
Aug  9 11:28:16 harosabo-vehikel avahi-autoipd(eth0)[6271]: Starting with address 169.254.10.177
Aug  9 11:28:22 harosabo-vehikel avahi-autoipd(eth0)[6271]: Callout BIND, address 169.254.10.177 on interface eth0
Aug  9 11:28:23 harosabo-vehikel avahi-daemon[5199]: Joining mDNS multicast group on interface eth0.IPv4 with address 169.254.10.177.
Aug  9 11:28:23 harosabo-vehikel avahi-daemon[5199]: New relevant interface eth0.IPv4 for mDNS.
Aug  9 11:28:23 harosabo-vehikel avahi-daemon[5199]: Registering new address record for 169.254.10.177 on eth0.IPv4.
Aug  9 11:28:26 harosabo-vehikel avahi-autoipd(eth0)[6271]: Successfully claimed IP address 169.254.10.177

/var/log/debug

Aug  9 11:27:50 harosabo-vehikel kernel: [   94.909678] wlan1: Initial auth_alg=0
Aug  9 11:27:50 harosabo-vehikel kernel: [   94.909685] wlan1: authenticate with AP 00:90:d0:f7:f9:3d
Aug  9 11:27:50 harosabo-vehikel kernel: [   94.911315] wlan1: RX authentication from 00:90:d0:f7:f9:3d (alg=0 transaction=2 status=0)
Aug  9 11:27:50 harosabo-vehikel kernel: [   94.911318] wlan1: authenticated
Aug  9 11:27:50 harosabo-vehikel kernel: [   94.911321] wlan1: associate with AP 00:90:d0:f7:f9:3d
Aug  9 11:27:50 harosabo-vehikel kernel: [   94.913935] wlan1: RX AssocResp from 00:90:d0:f7:f9:3d (capab=0x411 status=0 aid=1)
Aug  9 11:27:50 harosabo-vehikel kernel: [   94.913939] wlan1: associated
Aug  9 11:27:50 harosabo-vehikel kernel: [   94.913943] wlan1: CTS protection enabled (BSSID=00:90:d0:f7:f9:3d)
Aug  9 11:27:50 harosabo-vehikel kernel: [   94.913976] wlan1: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0
Aug  9 11:27:50 harosabo-vehikel kernel: [   94.913980] wlan1: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0
Aug  9 11:27:50 harosabo-vehikel kernel: [   94.913982] wlan1: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30
Aug  9 11:27:50 harosabo-vehikel kernel: [   94.913985] wlan1: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15
Aug  9 11:28:08 harosabo-vehikel kernel: [  242.462432] wlan1: no IPv6 routers present
Aug  9 11:38:57 harosabo-vehikel kernel: [  991.963341] APIC error on CPU0: 00(40)

/var/log/daemon.log

Aug  9 11:27:09 harosabo-vehikel NetworkManager:  Activation (eth0) Beginning DHCP transaction.
Aug  9 11:27:09 harosabo-vehikel NetworkManager:  Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Aug  9 11:27:09 harosabo-vehikel NetworkManager:  DHCP daemon state is now 12 (successfully started) for interface eth0
Aug  9 11:27:09 harosabo-vehikel NetworkManager:  SWITCH: terminating current connection 'eth0' because it's no longer valid.
Aug  9 11:27:09 harosabo-vehikel NetworkManager:  Deactivating device eth0.
Aug  9 11:27:09 harosabo-vehikel NetworkManager:  Activation (eth0): cancelling...
Aug  9 11:27:09 harosabo-vehikel NetworkManager:  Activation (eth0) cancellation handler scheduled...
Aug  9 11:27:09 harosabo-vehikel NetworkManager:  Activation (eth0): waiting for device to cancel activation.
Aug  9 11:27:09 harosabo-vehikel dhclient: wmaster0: unknown hardware address type 801
Aug  9 11:27:09 harosabo-vehikel last message repeated 2 times
Aug  9 11:27:10 harosabo-vehikel NetworkManager:  Activation (eth0) cancellation handled.
Aug  9 11:27:10 harosabo-vehikel NetworkManager:  Activation (eth0): cancelled.
Aug  9 11:27:10 harosabo-vehikel NetworkManager: nm_device_is_802_3_ethernet: assertion `dev != NULL' failed
Aug  9 11:27:10 harosabo-vehikel NetworkManager: nm_device_is_802_11_wireless: assertion `dev != NULL' failed
Aug  9 11:27:11 harosabo-vehikel dhclient: wmaster0: unknown hardware address type 801
Aug  9 11:27:15 harosabo-vehikel dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Aug  9 11:27:19 harosabo-vehikel dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Aug  9 11:27:24 harosabo-vehikel dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
Aug  9 11:27:26 harosabo-vehikel gdmgreeter[5902]: WARNING: Theme broken: must have pam-message label!
Aug  9 11:27:36 harosabo-vehikel dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
Aug  9 11:27:42 harosabo-vehikel hcid[5577]: Default passkey agent (:1.20, /org/bluez/passkey) registered
Aug  9 11:27:42 harosabo-vehikel hcid[5577]: Default authorization agent (:1.20, /org/bluez/auth) registered
Aug  9 11:27:44 harosabo-vehikel NetworkManager:  Updating allowed wireless network lists.
Aug  9 11:27:44 harosabo-vehikel NetworkManager:  SWITCH: no current connection, found better connection 'wlan1'.
Aug  9 11:27:44 harosabo-vehikel NetworkManager:  Will activate connection 'wlan1/harosabo'.
Aug  9 11:27:44 harosabo-vehikel NetworkManager:  Device wlan1 activation scheduled...
Aug  9 11:27:44 harosabo-vehikel NetworkManager:  Activation (wlan1) started...
Aug  9 11:27:44 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 1 of 5 (Device Prepare) scheduled...
Aug  9 11:27:44 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 1 of 5 (Device Prepare) started...
Aug  9 11:27:44 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 2 of 5 (Device Configure) scheduled...
Aug  9 11:27:44 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 1 of 5 (Device Prepare) complete.
Aug  9 11:27:44 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 2 of 5 (Device Configure) starting...
Aug  9 11:27:44 harosabo-vehikel NetworkManager:  Activation (wlan1/wireless): access point 'harosabo' is encrypted, but NO valid key exists.  New key needed.
Aug  9 11:27:44 harosabo-vehikel NetworkManager:  Activation (wlan1) New wireless user key requested for network 'harosabo'.
Aug  9 11:27:44 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 2 of 5 (Device Configure) complete.
Aug  9 11:27:44 harosabo-vehikel NetworkManager:  Activation (wlan1) New wireless user key for network 'harosabo' received.
Aug  9 11:27:44 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 1 of 5 (Device Prepare) scheduled...
Aug  9 11:27:44 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 1 of 5 (Device Prepare) started...
Aug  9 11:27:44 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 2 of 5 (Device Configure) scheduled...
Aug  9 11:27:44 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 1 of 5 (Device Prepare) complete.
Aug  9 11:27:44 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 2 of 5 (Device Configure) starting...
Aug  9 11:27:44 harosabo-vehikel NetworkManager:  Activation (wlan1/wireless): access point 'harosabo' is encrypted, and a key exists.  No new key needed.
Aug  9 11:27:46 harosabo-vehikel NetworkManager:  retry to connect to global supplicant socket (try=1)
Aug  9 11:27:46 harosabo-vehikel NetworkManager:  retry to connect to global supplicant socket (try=2)
Aug  9 11:27:46 harosabo-vehikel NetworkManager:  retry to connect to global supplicant socket (try=3)
Aug  9 11:27:46 harosabo-vehikel NetworkManager:  retry to connect to global supplicant socket (try=4)
Aug  9 11:27:47 harosabo-vehikel dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
Aug  9 11:27:47 harosabo-vehikel NetworkManager:  retry to connect to global supplicant socket (try=5)
Aug  9 11:27:47 harosabo-vehikel NetworkManager:  retry to connect to global supplicant socket (try=6)
Aug  9 11:27:48 harosabo-vehikel NetworkManager:  SUP: sending command 'INTERFACE_ADD wlan1^I^Iwext^I/var/run/wpa_supplicant0^I'
Aug  9 11:27:48 harosabo-vehikel NetworkManager:  SUP: response was 'OK'
Aug  9 11:27:49 harosabo-vehikel NetworkManager:  SUP: sending command 'AP_SCAN 1'
Aug  9 11:27:49 harosabo-vehikel NetworkManager:  SUP: response was 'OK'
Aug  9 11:27:49 harosabo-vehikel NetworkManager:  SUP: sending command 'ADD_NETWORK'
Aug  9 11:27:49 harosabo-vehikel NetworkManager:  SUP: response was '0'
Aug  9 11:27:49 harosabo-vehikel NetworkManager:  SUP: sending command 'SET_NETWORK 0 ssid 6861726f7361626f'
Aug  9 11:27:49 harosabo-vehikel NetworkManager:  SUP: response was 'OK'
Aug  9 11:27:49 harosabo-vehikel NetworkManager:  SUP: sending command 'SET_NETWORK 0 proto WPA'
Aug  9 11:27:49 harosabo-vehikel NetworkManager:  SUP: response was 'OK'
Aug  9 11:27:49 harosabo-vehikel NetworkManager:  SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'
Aug  9 11:27:49 harosabo-vehikel NetworkManager:  SUP: response was 'OK'
Aug  9 11:27:49 harosabo-vehikel NetworkManager:  SUP: sending command 'SET_NETWORK 0 psk '
Aug  9 11:27:49 harosabo-vehikel NetworkManager:  SUP: response was 'OK'
Aug  9 11:27:49 harosabo-vehikel NetworkManager:  SUP: sending command 'ENABLE_NETWORK 0'
Aug  9 11:27:49 harosabo-vehikel NetworkManager:  SUP: response was 'OK'
Aug  9 11:27:49 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 2 of 5 (Device Configure) complete.
Aug  9 11:27:50 harosabo-vehikel NetworkManager:  Old device 'wlan1' activating, won't change.
Aug  9 11:27:51 harosabo-vehikel NetworkManager:  Supplicant state changed: 1
Aug  9 11:27:51 harosabo-vehikel NetworkManager:  Activation (wlan1/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to access point 'harosabo'.
Aug  9 11:27:51 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 3 of 5 (IP Configure Start) scheduled.
Aug  9 11:27:51 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 3 of 5 (IP Configure Start) started...
Aug  9 11:27:52 harosabo-vehikel avahi-daemon[5199]: Registering new address record for fe80::21d:7eff:fe11:707c on wlan1.*.
Aug  9 11:27:52 harosabo-vehikel NetworkManager:  Activation (wlan1) Beginning DHCP transaction.
Aug  9 11:27:52 harosabo-vehikel dhclient: wmaster0: unknown hardware address type 801
Aug  9 11:27:52 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 3 of 5 (IP Configure Start) complete.
Aug  9 11:27:52 harosabo-vehikel NetworkManager:  DHCP daemon state is now 12 (successfully started) for interface wlan1
Aug  9 11:27:53 harosabo-vehikel NetworkManager:  DHCP daemon state is now 1 (starting) for interface wlan1
Aug  9 11:27:53 harosabo-vehikel dhclient: wmaster0: unknown hardware address type 801
Aug  9 11:27:55 harosabo-vehikel NetworkManager:  Old device 'wlan1' activating, won't change.
Aug  9 11:27:56 harosabo-vehikel dhclient: DHCPREQUEST of 192.168.1.65 on wlan1 to 255.255.255.255 port 67
Aug  9 11:27:56 harosabo-vehikel dhclient: DHCPACK of 192.168.1.65 from 192.168.1.254
Aug  9 11:27:56 harosabo-vehikel avahi-daemon[5199]: Joining mDNS multicast group on interface wlan1.IPv4 with address 192.168.1.65.
Aug  9 11:27:56 harosabo-vehikel avahi-daemon[5199]: New relevant interface wlan1.IPv4 for mDNS.
Aug  9 11:27:56 harosabo-vehikel avahi-daemon[5199]: Registering new address record for 192.168.1.65 on wlan1.IPv4.
Aug  9 11:27:56 harosabo-vehikel NetworkManager:  DHCP daemon state is now 4 (reboot) for interface wlan1
Aug  9 11:27:56 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 4 of 5 (IP Configure Get) scheduled...
Aug  9 11:27:56 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 4 of 5 (IP Configure Get) started...
Aug  9 11:27:56 harosabo-vehikel NetworkManager:  Retrieved the following IP4 configuration from the DHCP daemon:
Aug  9 11:27:56 harosabo-vehikel NetworkManager:    address 192.168.1.65
Aug  9 11:27:56 harosabo-vehikel NetworkManager:    netmask 255.255.255.0
Aug  9 11:27:56 harosabo-vehikel NetworkManager:    broadcast 192.168.1.255
Aug  9 11:27:56 harosabo-vehikel NetworkManager:    gateway 192.168.1.254
Aug  9 11:27:56 harosabo-vehikel NetworkManager:    nameserver 192.168.1.254
Aug  9 11:27:56 harosabo-vehikel NetworkManager:    domain name 'lan'
Aug  9 11:27:56 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 5 of 5 (IP Configure Commit) scheduled...
Aug  9 11:27:56 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 4 of 5 (IP Configure Get) complete.
Aug  9 11:27:56 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 5 of 5 (IP Configure Commit) started...
Aug  9 11:27:56 harosabo-vehikel dhclient: bound to 192.168.1.65 -- renewal in 40316 seconds.
Aug  9 11:27:56 harosabo-vehikel avahi-daemon[5199]: Withdrawing address record for 192.168.1.65 on wlan1.
Aug  9 11:27:56 harosabo-vehikel avahi-daemon[5199]: Leaving mDNS multicast group on interface wlan1.IPv4 with address 192.168.1.65.
Aug  9 11:27:56 harosabo-vehikel avahi-daemon[5199]: Interface wlan1.IPv4 no longer relevant for mDNS.
Aug  9 11:27:56 harosabo-vehikel avahi-daemon[5199]: Withdrawing address record for fe80::21d:7eff:fe11:707c on wlan1.
Aug  9 11:27:56 harosabo-vehikel avahi-daemon[5199]: Received packet from invalid interface.
Aug  9 11:27:56 harosabo-vehikel avahi-daemon[5199]: Joining mDNS multicast group on interface wlan1.IPv4 with address 192.168.1.65.
Aug  9 11:27:56 harosabo-vehikel avahi-daemon[5199]: New relevant interface wlan1.IPv4 for mDNS.
Aug  9 11:27:56 harosabo-vehikel avahi-daemon[5199]: Registering new address record for 192.168.1.65 on wlan1.IPv4.
Aug  9 11:27:57 harosabo-vehikel NetworkManager:  Clearing nscd hosts cache.
Aug  9 11:27:57 harosabo-vehikel NetworkManager:  nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory))  
Aug  9 11:27:57 harosabo-vehikel NetworkManager:  Activation (wlan1) successful, device activated.
Aug  9 11:27:57 harosabo-vehikel NetworkManager:  Activation (wlan1) Finish handler scheduled.
Aug  9 11:27:57 harosabo-vehikel NetworkManager:  Activation (wlan1) Stage 5 of 5 (IP Configure Commit) complete.
Aug  9 11:27:59 harosabo-vehikel avahi-daemon[5199]: Registering new address record for fe80::21d:7eff:fe11:707c on wlan1.*.
Aug  9 11:27:59 harosabo-vehikel ntpdate[6238]: adjust time server 91.189.94.4 offset 0.481293 sec
Aug  9 11:28:04 harosabo-vehikel dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
Aug  9 11:28:16 harosabo-vehikel dhclient: No DHCPOFFERS received.
Aug  9 11:28:16 harosabo-vehikel avahi-autoipd(eth0)[6271]: Found user 'avahi-autoipd' (UID 105) and group 'avahi-autoipd' (GID 113).
Aug  9 11:28:16 harosabo-vehikel avahi-autoipd(eth0)[6271]: Successfully called chroot().
Aug  9 11:28:16 harosabo-vehikel avahi-autoipd(eth0)[6271]: Successfully dropped root privileges.
Aug  9 11:28:16 harosabo-vehikel avahi-autoipd(eth0)[6271]: Starting with address 169.254.10.177
Aug  9 11:28:22 harosabo-vehikel avahi-autoipd(eth0)[6271]: Callout BIND, address 169.254.10.177 on interface eth0
Aug  9 11:28:23 harosabo-vehikel avahi-daemon[5199]: Joining mDNS multicast group on interface eth0.IPv4 with address 169.254.10.177.
Aug  9 11:28:23 harosabo-vehikel avahi-daemon[5199]: New relevant interface eth0.IPv4 for mDNS.
Aug  9 11:28:23 harosabo-vehikel avahi-daemon[5199]: Registering new address record for 169.254.10.177 on eth0.IPv4.
Aug  9 11:28:26 harosabo-vehikel avahi-autoipd(eth0)[6271]: Successfully claimed IP address 169.254.10.177
Aug  9 11:45:05 harosabo-vehikel NetworkManager: [1218275105.288557] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_457_151_000000000001F3').
Aug  9 11:45:05 harosabo-vehikel NetworkManager: [1218275105.996449] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_457_151_000000000001F3_if0').
Aug  9 11:45:11 harosabo-vehikel NetworkManager: [1218275111.207694] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_457_151_000000000001F3_if0_scsi_host').
Aug  9 11:45:11 harosabo-vehikel NetworkManager: [1218275111.223007] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_457_151_000000000001F3_if0_scsi_host_scsi_device_lun0').
Aug  9 11:45:11 harosabo-vehikel NetworkManager: [1218275111.291572] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_457_151_000000000001F3_if0_scsi_host_scsi_device_lun0_scsi_generic').
Aug  9 11:45:11 harosabo-vehikel NetworkManager: [1218275111.530402] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/storage_serial_TinyDisk_2005_09_15_000000000001F3_0_0').
Aug  9 11:45:12 harosabo-vehikel NetworkManager: [1218275112.240724] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/volume_uuid_6699_27E5').


rokinrob

  • Gast
ineens problemen met linksys wusb54GC (wireless usb)
« Reactie #5 Gepost op: 2008/08/10, 21:41:24 »
Ik heb voor een zeer onelegante oplossing gekozen.
Ik heb Hardy gewoon opnieuw geinstalleerd en alles loopt weer als een zonnetje; inclusief draadloos internet.

Voelt wel een beetje als een nederlaag, maar de rest van het gezin is wel weer heel blij...

Offline Pjotr

  • Lid
    • http://sites.google.com/site/computertip
  • Steunpunt: Nee
ineens problemen met linksys wusb54GC (wireless usb)
« Reactie #6 Gepost op: 2008/08/10, 21:58:06 »
Citaat van: rokinrob
Ik heb voor een zeer onelegante oplossing gekozen.
Ik heb Hardy gewoon opnieuw geinstalleerd en alles loopt weer als een zonnetje; inclusief draadloos internet.

Voelt wel een beetje als een nederlaag, maar de rest van het gezin is wel weer heel blij...
Och welnee, dat heb ik zo vaak gedaan, in het begin van mijn Linuxavontuur, twee jaar geleden....  :-)