Anzeige:
Ergebnis 1 bis 10 von 10

Thema: FRITZ!WLAN USB STICK will nicht mehr

  1. #1
    Registrierter Benutzer
    Registriert seit
    Jan 2006
    Beiträge
    49

    FRITZ!WLAN USB STICK will nicht mehr

    Hallo,

    hab da ein masives Problem.
    Hab den FRITZ!WLAN USB STICK schon einmal ganz prima ma laufen gehabt.Es funktionierte alles super.
    In der Nacht System runter gefahren,am nächsten morgen gestartet und nix ging mehr.Hab daraufhin Platte platt gemacht und SUSE LINUX 10.0 neu installiert.
    Files gesaugt,installiert und probiert den WLAN Stick ans laufen zu bekommen.
    Erhalte wenn ich : rcnetwork restart eingebe folgende ausagbe:

    linux:/fritz/src # rcnetwork restart
    Shutting down network interfaces:
    eth0 device: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91)
    eth0 configuration: eth-id-00:03:0d:34:26:f1 done
    wlan0
    wlan0 No configuration found for wlan0
    Nevertheless the interface will be shut down.
    wlan0 configuration: done
    Shutting down service network . . . . . . . . . . . . . done.
    Hint: you may set mandatory devices in /etc/sysconfig/network/config
    Setting up network interfaces:
    lo
    lo IP address: 127.0.0.1/8 done
    eth0 device: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91)
    eth0 configuration: eth-id-00:03:0d:34:26:f1
    eth0 (DHCP) . . . . . IP/Netmask: 192.168.178.23 / 255.255.2done
    wlan0
    wlan0 No configuration found for wlan0 unused
    Setting up service network . . . . . . . . . . . . . . done.
    SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    SuSEfirewall2: Another SuSEfirewall2 with PID 9288 found, waiting ...
    SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    SuSEfirewall2: batch committing...
    SuSEfirewall2: Firewall rules successfully set
    linux:/fritz/src #

    Versteh das net denn wenn ich ihm sag : iwlist wlan0 scan kommt folgendes:

    wlan0 Scan completed :
    Cell 01 - Address: 00:01:E3:08:05 F
    ESSID:"Willi"
    Cell 02 - Address: 00:04:0E:62:F0:44
    ESSID:"Gigals Powernetz"

    linux:/fritz/src #

    Somit denk ich mal das er funzt der Stick den sonst könnte ich ja net scanen.
    Mit iwconfig ergibt sich auch folgendes:

    linux:/fritz/src # iwconfig
    lo no wireless extensions.

    sit0 no wireless extensions.

    eth0 no wireless extensions.

    wlan0 IEEE 802.11b/g ESSID:"Gigal´s Powernetz"
    Mode:Managed Channel:0
    Encryption keyff
    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:/fritz/src #


    Alles tut nur beim Netzwerk Neustart sagt er :
    wlan0: No configuration found
    Nun bin ich am Ende meiner Weisheit ( welche bezüglich Linux eher sehr bescheiden ist da ich blutiger Anfänger bin )und hoffe das mir hier irgendjemand helfen kann.

    Danke schon mal im voraus

    Greetz Cali37

  2. #2
    Registrierter Benutzer
    Registriert seit
    Jan 2006
    Beiträge
    49
    Kann den da gar keiner weiterhelfen?
    Hab nicht gerade Lust das ganze Spiel noch mal neu zu installieren.

  3. #3
    Registrierter Benutzer
    Registriert seit
    Jan 2006
    Beiträge
    49
    Hallo,

    hab bezüglich diesen Themas noch die /var/log/messages ausgelesen.
    Hoffe da hilft bei der Hilfe weiter.

    Hier der Auszug:

    an 25 22:46:52 linux kernel: fwlanusb: module not supported by Novell, setting U taint flag.
    Jan 25 22:46:52 linux kernel: fwlanusb: module license 'Proprietary' taints kernel.
    Jan 25 22:46:52 linux kernel: fwlanusb: AVM FRITZ!WLAN USB Stick driver, revision 0.09.00-BETA
    Jan 25 22:46:52 linux kernel: fwlanusb: (fwlanusb built on Jan 25 2006 at 22:46:34)
    Jan 25 22:46:52 linux kernel: fwlanusb: -- 32 bit driver --
    Jan 25 22:46:52 linux kernel: fwlanusb: Loading...
    Jan 25 22:46:52 linux kernel: fwlanusb: Driver 'fwlanusb' attached to fwlanusb-stack. (160)
    Jan 25 22:46:52 linux kernel: klogd 1.4.1, ---------- state change ----------
    Jan 25 22:46:52 linux kernel: usb 3-1: reset high speed USB device using ehci_hcd and address 2
    Jan 25 22:46:53 linux kernel: fwlanusb: Config manager successully created and started.
    Jan 25 22:46:53 linux kernel: usbcore: registered new driver fwlanusb
    Jan 25 22:46:53 linux kernel: fwlanusb: Loaded.
    Jan 25 22:47:03 linux ifup: No configuration found for wlan0
    Jan 25 22:48:40 linux dhcpcd[29586]: terminating on signal 15

    Und auch noch die antwort aus ifconfig

    linux:~ # ifconfig
    eth0 Link encap:Ethernet HWaddr 00:03:0D:34:26:F1
    inet addr:192.168.178.26 Bcast:192.168.178.255 Mask:255.255.255.0
    inet6 addr: fe80::203:dff:fe34:26f1/64 Scope:Link
    UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:5370 errors:0 dropped:0 overruns:0 frame:0
    TX packets:3512 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:6579672 (6.2 Mb) TX bytes:368160 (359.5 Kb)
    Interrupt:5 Base address:0xd800

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:504 errors:0 dropped:0 overruns:0 frame:0
    TX packets:504 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:38240 (37.3 Kb) TX bytes:38240 (37.3 Kb)

    linux:~ #

  4. #4
    Registrierter Benutzer
    Registriert seit
    Jan 2006
    Beiträge
    49
    Und gerade hab ich noch etaws entdeckt.
    Seht am besten selber:

    linux:~/fritz/src # ifconfig wlan0
    wlan0 Link encap:Ethernet HWaddr 00:04:0E:C2:17:71
    BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:82
    TX packets:0 errors:0 dropped:1363299651 overruns:0 carrier:1196312385
    collisions:41 txqueuelen:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

    linux:~/fritz/src #

  5. #5
    Registrierter Benutzer
    Registriert seit
    Jan 2006
    Beiträge
    49
    Hallo noch mal,

    da mir ,wie es scheint, mirt diesen Nagben keiner helfen kann, hab ich die ganze /var/log/messages nun kopiert und stell sie in der Hoffnung ein das mir nun doch noch jemand helfen kann.

    Hier Teil 1:

    Jan 25 22:33:49 linux kernel: klogd 1.4.1, log source = /proc/Jan 25 22:25:30 linux syslog-ng[14781]: syslog-ng version 1.6.8 starting
    Jan 25 22:25:30 linux modprobe: FATAL: Error inserting asus_acpi (/lib/modules/2.6.13-15-default/kernel/drivers/acpi/asus_acpi.ko): No such device
    Jan 25 22:25:30 linux modprobe: FATAL: Error inserting ibm_acpi (/lib/modules/2.6.13-15-default/kernel/drivers/acpi/ibm_acpi.ko): No such device
    Jan 25 22:25:30 linux modprobe: FATAL: Error inserting toshiba_acpi (/lib/modules/2.6.13-15-default/kernel/drivers/acpi/toshiba_acpi.ko): No such device
    Jan 25 22:25:35 linux kernel: klogd 1.4.1, log source = /proc/kmsg started.
    Jan 25 22:25:35 linux kernel: lp: driver loaded but no devices found
    Jan 25 22:25:35 linux kernel: Adding 1052216k swap on /dev/hda5. Priority:-1 extents:1
    Jan 25 22:25:35 linux kernel: usbcore: registered new driver usbfs
    Jan 25 22:25:35 linux kernel: usbcore: registered new driver hub
    Jan 25 22:25:35 linux kernel: ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
    Jan 25 22:25:35 linux syslog-ng[14781]: Changing permissions on special file /dev/xconsole
    Jan 25 22:25:35 linux syslog-ng[14781]: Changing permissions on special file /dev/tty10
    Jan 25 22:25:35 linux kernel: ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 4
    Jan 25 22:25:35 linux kernel: PCI: setting IRQ 4 as level-triggered
    Jan 25 22:25:35 linux kernel: ACPI: PCI Interrupt 0000:00:03.0[A] -> Link [LNKE] -> GSI 4 (level, low) -> IRQ 4
    Jan 25 22:25:35 linux kernel: ohci_hcd 0000:00:03.0: OHCI Host Controller
    Jan 25 22:25:35 linux kernel: ohci_hcd 0000:00:03.0: new USB bus registered, assigned bus number 1
    Jan 25 22:25:35 linux kernel: ohci_hcd 0000:00:03.0: irq 4, io mem 0xdfffd000
    Jan 25 22:25:35 linux kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    Jan 25 22:25:35 linux kernel: hub 1-0:1.0: USB hub found
    Jan 25 22:25:35 linux kernel: hub 1-0:1.0: 3 ports detected
    Jan 25 22:25:35 linux kernel: ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 3
    Jan 25 22:25:35 linux kernel: PCI: setting IRQ 3 as level-triggered
    Jan 25 22:25:35 linux kernel: ACPI: PCI Interrupt 0000:00:03.1[B] -> Link [LNKF] -> GSI 3 (level, low) -> IRQ 3
    Jan 25 22:25:35 linux kernel: ohci_hcd 0000:00:03.1: OHCI Host Controller
    Jan 25 22:25:36 linux kernel: ohci_hcd 0000:00:03.1: new USB bus registered, assigned bus number 2
    Jan 25 22:25:36 linux kernel: ohci_hcd 0000:00:03.1: irq 3, io mem 0xdfffe000
    Jan 25 22:25:36 linux kernel: shpchp: shpc_init : shpc_cap_offset == 0
    Jan 25 22:25:36 linux kernel: hub 2-0:1.0: USB hub found
    Jan 25 22:25:36 linux kernel: hub 2-0:1.0: 3 ports detected
    Jan 25 22:25:36 linux kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    Jan 25 22:25:36 linux kernel: usb 1-1: new full speed USB device using ohci_hcd and address 2
    Jan 25 22:25:36 linux kernel: sis900.c: v1.08.08 Jan. 22 2005
    Jan 25 22:25:36 linux kernel: ACPI-0212: *** Warning: Device is not power manageable
    Jan 25 22:25:36 linux kernel: ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5
    Jan 25 22:25:36 linux kernel: ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [LNKD] -> GSI 5 (level, low) -> IRQ 5
    Jan 25 22:25:36 linux kernel: 0000:00:04.0: Realtek RTL8201 PHY transceiver found at address 1.
    Jan 25 22:25:36 linux kernel: 0000:00:04.0: Using transceiver found at address 1 as default
    Jan 25 22:25:36 linux kernel: eth0: SiS 900 PCI Fast Ethernet at 0xd800, IRQ 5, 00:03:0d:34:26:f1.
    Jan 25 22:25:36 linux kernel: Linux agpgart interface v0.101 (c) Dave Jones
    Jan 25 22:25:36 linux kernel: agpgart: Detected AGP bridge 0
    Jan 25 22:25:36 linux kernel: agpgart: AGP aperture is 32M @ 0xe0000000
    Jan 25 22:25:36 linux kernel: ACPI-0212: *** Warning: Device is not power manageable
    Jan 25 22:25:36 linux kernel: ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 5
    Jan 25 22:25:36 linux kernel: ACPI: PCI Interrupt 0000:00:03.3[D] -> Link [LNKH] -> GSI 5 (level, low) -> IRQ 5
    Jan 25 22:25:36 linux kernel: ehci_hcd 0000:00:03.3: EHCI Host Controller
    Jan 25 22:25:36 linux kernel: ehci_hcd 0000:00:03.3: new USB bus registered, assigned bus number 3
    Jan 25 22:25:36 linux kernel: ehci_hcd 0000:00:03.3: irq 5, io mem 0xdffff000
    Jan 25 22:25:36 linux kernel: PCI: cache line size of 64 is not supported by device 0000:00:03.3
    Jan 25 22:25:36 linux kernel: ehci_hcd 0000:00:03.3: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
    Jan 25 22:25:36 linux kernel: hub 3-0:1.0: USB hub found
    Jan 25 22:25:36 linux kernel: hub 3-0:1.0: 6 ports detected
    Jan 25 22:25:36 linux kernel: i2c-sis96x version 1.0.0
    Jan 25 22:25:36 linux kernel: sis96x_smbus 0000:00:02.1: SiS96x SMBus base address: 0x0c00
    Jan 25 22:25:36 linux kernel: usb 3-1: new high speed USB device using ehci_hcd and address 2
    Jan 25 22:25:36 linux kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
    Jan 25 22:25:36 linux kernel: hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
    Jan 25 22:25:36 linux kernel: ide: failed opcode was: unknown
    Jan 25 22:25:36 linux kernel: usb 1-1: USB disconnect, address 2
    Jan 25 22:25:36 linux kernel: ACPI: PCI Interrupt 0000:00:09.0[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
    Jan 25 22:25:36 linux kernel: Yenta: CardBus bridge found at 0000:00:09.0 [1734:106c]
    Jan 25 22:25:36 linux kernel: Yenta O2: res at 0x94/0xD4: 00/ea
    Jan 25 22:25:36 linux kernel: Yenta O2: enabling read prefetch/write burst
    Jan 25 22:25:36 linux kernel: Yenta: ISA IRQ mask 0x0ac0, PCI irq 5
    Jan 25 22:25:36 linux kernel: Socket status: 30000006
    Jan 25 22:25:36 linux kernel: ACPI: PCI Interrupt 0000:00:09.1[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
    Jan 25 22:25:36 linux kernel: Yenta: CardBus bridge found at 0000:00:09.1 [1734:106c]
    Jan 25 22:25:36 linux kernel: Yenta: ISA IRQ mask 0x0ac0, PCI irq 5
    Jan 25 22:25:36 linux kernel: Socket status: 30000006
    Jan 25 22:25:36 linux kernel: ieee1394: Initialized config rom entry `ip1394'
    Jan 25 22:25:36 linux kernel: ohci1394: $Rev: 1299 $ Ben Collins <bcollins@debian.org>
    Jan 25 22:25:36 linux kernel: ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [LNKD] -> GSI 5 (level, low) -> IRQ 5
    Jan 25 22:25:36 linux kernel: ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[5] MMIO=[dfffb800-dfffbfff] Max Packet=[2048]
    Jan 25 22:25:36 linux kernel: usb 1-2: new low speed USB device using ohci_hcd and address 4
    Jan 25 22:25:36 linux kernel: usbcore: registered new driver hiddev
    Jan 25 22:25:36 linux kernel: input: USB HID v1.10 Mouse [062a:0000] on usb-0000:00:03.0-2
    Jan 25 22:25:36 linux kernel: usbcore: registered new driver usbhid
    Jan 25 22:25:36 linux kernel: drivers/usb/input/hid-core.c: v2.01:USB HID core driver
    Jan 25 22:25:36 linux kernel: bootsplash: status on console 0 changed to on
    Jan 25 22:25:36 linux kernel: ieee1394: Host added: ID:BUS[0-00:1023] GUID[00030d53255e4f7b]
    Jan 25 22:25:36 linux kernel: cs: IO port probe 0x3e0-0x4ff: excluding 0x480-0x48f 0x4d0-0x4d7
    Jan 25 22:25:36 linux kernel: cs: IO port probe 0x100-0x3af: clean.
    Jan 25 22:25:36 linux kernel: cs: IO port probe 0xc00-0xcff: clean.
    Jan 25 22:25:36 linux kernel: cs: IO port probe 0x820-0x8ff: excluding 0x828-0x837 0x840-0x84f 0x858-0x89f
    Jan 25 22:25:36 linux kernel: cs: IO port probe 0xa00-0xaff: clean.
    Jan 25 22:25:36 linux kernel: cs: IO port probe 0x3e0-0x4ff: excluding 0x480-0x48f 0x4d0-0x4d7
    Jan 25 22:25:36 linux kernel: cs: IO port probe 0x100-0x3af: clean.
    Jan 25 22:25:36 linux kernel: cs: IO port probe 0xc00-0xcff: clean.
    Jan 25 22:25:36 linux kernel: cs: IO port probe 0x820-0x8ff: excluding 0x828-0x837 0x840-0x84f 0x858-0x89f
    Jan 25 22:25:36 linux kernel: cs: IO port probe 0xa00-0xaff: clean.
    Jan 25 22:25:36 linux kernel: ACPI: AC Adapter [AC0] (on-line)
    Jan 25 22:25:36 linux kernel: ACPI: Battery Slot [BAT0] (battery present)
    Jan 25 22:25:36 linux kernel: ACPI: Power Button (FF) [PWRF]
    Jan 25 22:25:36 linux kernel: ACPI: Lid Switch [LID]
    Jan 25 22:25:36 linux kernel: ACPI: Sleep Button (CM) [SLPB]
    Jan 25 22:25:36 linux kernel: ACPI: Power Button (CM) [PWRB]
    Jan 25 22:25:36 linux kernel: ibm_acpi: ec object not found
    Jan 25 22:25:36 linux kernel: pcc_acpi: module not supported by Novell, setting U taint flag.
    Jan 25 22:25:36 linux kernel: bootsplash: status on console 0 changed to on
    Jan 25 22:25:36 linux kernel: NET: Registered protocol family 10
    Jan 25 22:25:36 linux kernel: Disabled Privacy Extensions on device c036b920(lo)
    Jan 25 22:25:36 linux kernel: IPv6 over IPv4 tunneling driver
    Jan 25 22:25:44 linux kernel: SCSI subsystem initialized
    Jan 25 22:25:44 linux kernel: st: Version 20050501, fixed bufsize 32768, s/g segs 256
    Jan 25 22:25:44 linux kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
    Jan 25 22:25:44 linux kernel: hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
    Jan 25 22:25:44 linux kernel: ide: failed opcode was: unknown
    Jan 25 21:27:06 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 25 21:27:14 linux kernel: eth0: no IPv6 routers present
    Jan 25 21:27:25 linux kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
    Jan 25 21:27:25 linux kernel: hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
    Jan 25 21:27:25 linux kernel: ide: failed opcode was: unknown
    Jan 25 21:27:25 linux kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
    Jan 25 21:27:25 linux kernel: hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
    Jan 25 21:27:25 linux kernel: ide: failed opcode was: unknown
    Jan 25 21:27:25 linux kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
    Jan 25 21:27:25 linux kernel: hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
    Jan 25 21:27:25 linux kernel: ide: failed opcode was: unknown
    Jan 25 21:27:41 linux kernel: NET: Registered protocol family 17
    Jan 25 21:28:25 linux kernel: ip6_tables: (C) 2000-2002 Netfilter core team
    Jan 25 22:28:25 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 21:28:25 linux kernel: ip_tables: (C) 2000-2002 Netfilter core team
    Jan 25 21:28:25 linux kernel: ip_conntrack version 2.1 (7166 buckets, 57328 max) - 248 bytes per conntrack
    Jan 25 22:28:25 linux SuSEfirewall2: batch committing...
    Jan 25 22:28:25 linux SuSEfirewall2: Firewall rules set to CLOSE.
    Jan 25 22:28:25 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:28:25 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 25 22:28:25 linux SuSEfirewall2: Warning: no interface active
    Jan 25 22:28:25 linux SuSEfirewall2: batch committing...
    Jan 25 22:28:25 linux SuSEfirewall2: Firewall rules successfully set
    Jan 25 22:28:27 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:28:27 linux SuSEfirewall2: batch committing...
    Jan 25 22:28:27 linux SuSEfirewall2: Firewall rules set to CLOSE.
    Jan 25 22:28:27 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:28:27 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 25 22:28:28 linux SuSEfirewall2: Warning: no interface active
    Jan 25 22:28:28 linux SuSEfirewall2: batch committing...
    Jan 25 22:28:28 linux SuSEfirewall2: Firewall rules successfully set
    Jan 25 21:28:28 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 25 22:28:28 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:28:28 linux SuSEfirewall2: batch committing...
    Jan 25 22:28:28 linux SuSEfirewall2: Firewall rules set to CLOSE.
    Jan 25 22:28:28 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:28:28 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 25 22:28:29 linux SuSEfirewall2: batch committing...
    Jan 25 22:28:29 linux SuSEfirewall2: Firewall rules successfully set
    Jan 25 22:28:33 linux logger: BEGIN OF YAST2 INTERNET TEST
    Jan 25 21:28:36 linux kernel: eth0: no IPv6 routers present
    Jan 25 21:28:38 linux kernel: BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
    Jan 25 22:28:42 linux logger: END OF YAST2 INTERNET TEST
    Jan 25 22:31:45 linux syslog-ng[14781]: SIGHUP received, restarting syslog-ng
    Jan 25 22:31:46 linux su: (to nobody) root on none
    Jan 25 22:31:46 linux syslog-ng[14781]: new configuration initialized
    Jan 25 22:31:46 linux su: (to nobody) root on none
    Jan 25 22:31:46 linux su: (to nobody) root on none
    Jan 25 22:32:05 linux su: (to nobody) root on none
    Jan 25 22:32:15 linux init: Re-reading inittab
    Jan 25 21:32:31 linux kernel: lp: driver loaded but no devices found
    Jan 25 21:32:31 linux kernel: klogd 1.4.1, ---------- state change ----------
    Jan 25 21:32:31 linux kernel: lp: driver loaded but no devices found
    Jan 25 22:32:32 linux hp: unable to open /var/run/hpiod.port: No such file or directory: prnt/hpijs/hplip_api.c 75
    Jan 25 22:32:32 linux hp: unable to connect hpiod socket 50000: Connection refused: prnt/hpijs/hplip_api.c 693
    Jan 25 22:32:32 linux hp: unable to send ProbeDevices: Broken pipe
    Jan 25 22:33:30 linux syslog-ng[14781]: Changing permissions on special file /dev/xconsole
    Jan 25 22:33:30 linux syslog-ng[14781]: Changing permissions on special file /dev/tty10
    Jan 25 21:33:30 linux kernel: ACPI-0212: *** Warning: Device is not power manageable
    Jan 25 21:33:30 linux kernel: ACPI: PCI Interrupt 0000:00:02.7[C] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
    Jan 25 21:33:30 linux kernel: intel8x0_measure_ac97_clock: measured 55518 usecs
    Jan 25 21:33:30 linux kernel: intel8x0: clocking to 48000
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 21:33:33 linux kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
    Jan 25 21:33:33 linux kernel: hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
    Jan 25 21:33:33 linux kernel: ide: failed opcode was: unknown
    Jan 25 22:33:42 linux init: Entering runlevel: 5
    Jan 25 21:33:43 linux kernel: bootsplash: status on console 0 changed to on
    Jan 25 21:33:43 linux kernel: Kernel logging (proc) stopped.
    Jan 25 21:33:43 linux kernel: Kernel log daemon terminating.
    Jan 25 22:33:44 linux syslog-ng[14781]: syslog-ng version 1.6.8 going down
    Jan 25 22:33:44 linux syslog-ng[25953]: syslog-ng version 1.6.8 starting
    Jan 25 22:33:44 linux syslog-ng[25953]: Changing permissions on special file /dev/xconsole
    Jan 25 22:33:44 linux syslog-ng[25953]: Changing permissions on special file /dev/tty10
    Jan 25 22:33:44 linux mDNSResponder: Unable to parse DNS server list. Unicast DNS-SD unavailable
    Jan 25 22:33:48 linux /usr/sbin/cron[26284]: (CRON) STARTUP (V5.0)kmsg started.
    Jan 25 22:33:49 linux kernel: IA-32 Microcode Update Driver: v1.14 <tigran@veritas.com>
    Jan 25 22:33:49 linux kernel: microcode: CPU0 not a capable Intel processor
    Jan 25 22:33:49 linux kernel: microcode: No new microcode data for CPU0
    Jan 25 22:33:49 linux kernel: IA-32 Microcode Update Driver v1.14 unregistered
    Jan 25 22:33:49 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 25 22:33:50 linux kernel: powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.50.3)
    Jan 25 22:33:50 linux kernel: powernow-k8: 0 : fid 0xc (2000 MHz), vid 0xa (1300 mV)
    Jan 25 22:33:50 linux kernel: powernow-k8: 1 : fid 0xa (1800 MHz), vid 0xc (1250 mV)
    Jan 25 22:33:50 linux kernel: powernow-k8: 2 : fid 0x8 (1600 MHz), vid 0xe (1200 mV)
    Jan 25 22:33:50 linux kernel: powernow-k8: 3 : fid 0x0 (800 MHz), vid 0x13 (1075 mV)
    Jan 25 22:33:50 linux kernel: cpu_init done, current fid 0xc, vid 0xa
    Jan 25 22:33:50 linux rcpowersaved: enter 'powernow_k8' into CPUFREQD_MODULE in /etc/sysconfig/powersave/cpufreq.
    Jan 25 22:33:50 linux rcpowersaved: this will speed up starting powersaved and avoid unnecessary warnings in syslog.
    Jan 25 22:33:53 linux sshd[26425]: Server listening on :: port 22.
    Jan 25 22:33:54 linux kernel: eth0: no IPv6 routers present
    Jan 25 22:33:55 linux hp: unable to open /var/run/hpiod.port: No such file or directory: prnt/hpijs/hplip_api.c 75
    Jan 25 22:33:56 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:33:56 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 25 22:33:57 linux SuSEfirewall2: batch committing...
    Jan 25 22:33:57 linux SuSEfirewall2: Firewall rules successfully set
    Jan 25 22:33:58 linux kernel: mtrr: 0xd0000000,0x8000000 overlaps existing 0xd0000000,0x1000000
    Jan 25 22:34:29 linux modprobe: FATAL: Error inserting sonypi (/lib/modules/2.6.13-15-default/kernel/drivers/char/sonypi.ko): No such device
    Jan 25 22:35:17 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:35:17 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 25 22:35:17 linux SuSEfirewall2: batch committing...
    Jan 25 22:35:17 linux SuSEfirewall2: Firewall rules successfully set
    Jan 25 22:35:19 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 25 22:35:27 linux kernel: eth0: no IPv6 routers present
    Jan 25 22:35:34 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:35:34 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 25 22:35:34 linux SuSEfirewall2: batch committing...
    Jan 25 22:35:34 linux SuSEfirewall2: Firewall rules successfully set
    Jan 25 22:35:35 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 25 22:35:44 linux kernel: eth0: no IPv6 routers present
    Jan 25 22:36:18 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 25 22:36:21 linux modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file
    Jan 25 22:36:21 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:36:22 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 25 22:36:22 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:36:22 linux SuSEfirewall2: Another SuSEfirewall2 with PID 28668 found, waiting ...
    Jan 25 22:36:22 linux SuSEfirewall2: batch committing...
    Jan 25 22:36:22 linux SuSEfirewall2: Firewall rules successfully set
    Jan 25 22:36:24 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 25 22:36:24 linux SuSEfirewall2: batch committing...
    Jan 25 22:36:24 linux SuSEfirewall2: Firewall rules successfully set
    Jan 25 22:36:24 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:36:24 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 25 22:36:25 linux SuSEfirewall2: batch committing...
    Jan 25 22:36:25 linux SuSEfirewall2: Firewall rules successfully set
    Jan 25 22:36:26 linux kernel: eth0: no IPv6 routers present
    Jan 25 22:36:26 linux dhcpcd[28619]: terminating on signal 15
    Jan 25 22:36:26 linux modify_resolvconf: restored /etc/resolv.conf.saved.by.dhcpcd.eth0 to /etc/resolv.conf
    Jan 25 22:36:30 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 25 22:36:32 linux kernel: martian source 255.255.255.255 from 192.168.178.1, on dev eth0
    Jan 25 22:36:32 linux kernel: ll header: ff:ff:ff:ff:ff:ff:00:04:0e:62:f0:43:08:00
    Jan 25 22:36:33 linux modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file
    Jan 25 22:36:33 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:36:33 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 25 22:36:33 linux SuSEfirewall2: batch committing...
    Jan 25 22:36:33 linux SuSEfirewall2: Firewall rules successfully set
    Jan 25 22:36:34 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.

  6. #6
    Registrierter Benutzer
    Registriert seit
    Jan 2006
    Beiträge
    49
    Nun Teil 2:

    Jan 25 22:36:34 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 25 22:36:34 linux SuSEfirewall2: batch committing...
    Jan 25 22:36:34 linux SuSEfirewall2: Firewall rules successfully set
    Jan 25 22:36:38 linux kernel: eth0: no IPv6 routers present
    Jan 25 22:36:50 linux gconfd (root-29863): starting (version 2.12.0), pid 29863 user 'root'
    Jan 25 22:36:50 linux gconfd (root-29863): Resolved address "xml:readonly:/etc/opt/gnome/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
    Jan 25 22:36:50 linux gconfd (root-29863): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1
    Jan 25 22:36:50 linux gconfd (root-29863): Resolved address "xml:readonly:/etc/opt/gnome/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
    Jan 25 22:44:15 linux syslog-ng[25953]: SIGHUP received, restarting syslog-ng
    Jan 25 22:44:16 linux syslog-ng[25953]: new configuration initialized
    Jan 25 22:44:50 linux syslog-ng[25953]: SIGHUP received, restarting syslog-ng
    Jan 25 22:44:52 linux syslog-ng[25953]: new configuration initialized
    Jan 25 22:45:39 linux su: (to nobody) root on none
    Jan 25 22:45:39 linux su: (to nobody) root on none
    Jan 25 22:45:41 linux su: (to nobody) root on none
    Jan 25 22:45:42 linux su: (to nobody) root on none
    Jan 25 22:45:50 linux gconfd (root-29863): GConf server is not in use, shutting down.
    Jan 25 22:45:50 linux gconfd (root-29863): Exiting
    Jan 25 22:45:56 linux su: (to nobody) root on none
    Jan 25 22:45:56 linux su: (to nobody) root on none
    Jan 25 22:45:56 linux su: (to nobody) root on none
    Jan 25 22:46:52 linux syslog-ng[25953]: Changing permissions on special file /dev/xconsole
    Jan 25 22:46:52 linux syslog-ng[25953]: Changing permissions on special file /dev/tty10
    Jan 25 22:46:52 linux kernel: fwlanusb: module not supported by Novell, setting U taint flag.
    Jan 25 22:46:52 linux kernel: fwlanusb: module license 'Proprietary' taints kernel.
    Jan 25 22:46:52 linux kernel: fwlanusb: AVM FRITZ!WLAN USB Stick driver, revision 0.09.00-BETA
    Jan 25 22:46:52 linux kernel: fwlanusb: (fwlanusb built on Jan 25 2006 at 22:46:34)
    Jan 25 22:46:52 linux kernel: fwlanusb: -- 32 bit driver --
    Jan 25 22:46:52 linux kernel: fwlanusb: Loading...
    Jan 25 22:46:52 linux kernel: fwlanusb: Driver 'fwlanusb' attached to fwlanusb-stack. (160)
    Jan 25 22:46:52 linux kernel: klogd 1.4.1, ---------- state change ----------
    Jan 25 22:46:52 linux kernel: usb 3-1: reset high speed USB device using ehci_hcd and address 2
    Jan 25 22:46:53 linux kernel: fwlanusb: Config manager successully created and started.
    Jan 25 22:46:53 linux kernel: usbcore: registered new driver fwlanusb
    Jan 25 22:46:53 linux kernel: fwlanusb: Loaded.
    Jan 25 22:47:03 linux ifup: No configuration found for wlan0
    Jan 25 22:48:40 linux dhcpcd[29586]: terminating on signal 15
    Jan 25 22:48:41 linux modify_resolvconf: restored /etc/resolv.conf.saved.by.dhcpcd.eth0 to /etc/resolv.conf
    Jan 25 22:48:43 linux ifdown: No configuration found for wlan0
    Jan 25 22:48:43 linux ifdown: Nevertheless the interface will be shut down.
    Jan 25 22:48:46 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 25 22:48:48 linux kernel: martian source 255.255.255.255 from 192.168.178.1, on dev eth0
    Jan 25 22:48:48 linux kernel: ll header: ff:ff:ff:ff:ff:ff:00:04:0e:62:f0:43:08:00
    Jan 25 22:48:49 linux modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file
    Jan 25 22:48:49 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:48:49 linux ifup: No configuration found for wlan0
    Jan 25 22:48:49 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 25 22:48:49 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:48:49 linux SuSEfirewall2: Another SuSEfirewall2 with PID 1806 found, waiting ...
    Jan 25 22:48:50 linux SuSEfirewall2: batch committing...
    Jan 25 22:48:50 linux SuSEfirewall2: Firewall rules successfully set
    Jan 25 22:48:52 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 25 22:48:52 linux SuSEfirewall2: batch committing...
    Jan 25 22:48:52 linux SuSEfirewall2: Firewall rules successfully set
    Jan 25 22:48:55 linux kernel: eth0: no IPv6 routers present
    Jan 25 22:50:21 linux kernel: usb 1-2: USB disconnect, address 4
    Jan 25 22:50:30 linux kernel: spurious 8259A interrupt: IRQ7.
    Jan 25 22:50:30 linux kernel: atkbd.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
    Jan 25 22:50:30 linux kernel: atkbd.c: Use 'setkeycodes 00 <keycode>' to make it known.
    Jan 25 22:50:30 linux kernel: psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
    Jan 25 22:50:30 linux kernel: psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
    Jan 25 22:50:30 linux kernel: psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
    Jan 25 22:50:30 linux kernel: psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
    Jan 25 22:50:30 linux kernel: psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
    Jan 25 22:50:30 linux kernel: psmouse.c: TouchPad at isa0060/serio2/input0 - driver resynched.
    Jan 25 22:54:48 linux kernel: wlan0: no IPv6 routers present
    Jan 25 22:55:38 linux dhcpcd[2163]: timed out waiting for a valid DHCP server response
    Jan 25 22:56:41 linux kernel: wlan0: no IPv6 routers present
    Jan 25 22:57:30 linux dhcpcd[2225]: timed out waiting for a valid DHCP server response
    Jan 25 22:58:05 linux dhcpcd[1753]: terminating on signal 15
    Jan 25 22:58:05 linux modify_resolvconf: restored /etc/resolv.conf.saved.by.dhcpcd.eth0 to /etc/resolv.conf
    Jan 25 22:58:07 linux ifdown: No configuration found for wlan0
    Jan 25 22:58:07 linux ifdown: Nevertheless the interface will be shut down.
    Jan 25 22:58:10 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 25 22:58:12 linux kernel: martian source 255.255.255.255 from 192.168.178.1, on dev eth0
    Jan 25 22:58:12 linux kernel: ll header: ff:ff:ff:ff:ff:ff:00:04:0e:62:f0:43:08:00
    Jan 25 22:58:12 linux modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file
    Jan 25 22:58:12 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:58:12 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 25 22:58:13 linux SuSEfirewall2: batch committing...
    Jan 25 22:58:13 linux SuSEfirewall2: Firewall rules successfully set
    Jan 25 22:58:13 linux ifup: No configuration found for wlan0
    Jan 25 22:58:13 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:58:13 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 25 22:58:14 linux SuSEfirewall2: batch committing...
    Jan 25 22:58:14 linux SuSEfirewall2: Firewall rules successfully set
    Jan 25 22:58:19 linux kernel: eth0: no IPv6 routers present
    Jan 25 22:59:02 linux kernel: wlan0: no IPv6 routers present
    Jan 25 22:59:51 linux dhcpcd[3038]: timed out waiting for a valid DHCP server response
    Jan 25 22:59:56 linux kernel: eth0: Media Link Off
    Jan 25 23:00:16 linux gconfd (root-3130): starting (version 2.12.0), pid 3130 user 'root'
    Jan 25 23:00:16 linux gconfd (root-3130): Resolved address "xml:readonly:/etc/opt/gnome/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
    Jan 25 23:00:16 linux gconfd (root-3130): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1
    Jan 25 23:00:16 linux gconfd (root-3130): Resolved address "xml:readonly:/etc/opt/gnome/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
    Jan 25 23:01:18 linux kernel: usb 1-2: new low speed USB device using ohci_hcd and address 5
    Jan 25 23:01:18 linux kernel: input: USB HID v1.10 Mouse [062a:0000] on usb-0000:00:03.0-2
    Jan 25 23:02:16 linux gconfd (root-3130): GConf server is not in use, shutting down.
    Jan 25 23:02:16 linux gconfd (root-3130): Exiting
    Jan 25 23:04:24 linux gconfd (root-3241): starting (version 2.12.0), pid 3241 user 'root'
    Jan 25 23:04:24 linux gconfd (root-3241): Resolved address "xml:readonly:/etc/opt/gnome/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
    Jan 25 23:04:24 linux gconfd (root-3241): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1
    Jan 25 23:04:24 linux gconfd (root-3241): Resolved address "xml:readonly:/etc/opt/gnome/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
    Jan 25 23:08:16 linux ifup: No configuration found for wlan0
    Jan 25 23:08:29 linux ifup: No configuration found for wlan0
    Jan 25 23:08:42 linux ifup: Interface dhcp is not available
    Jan 25 23:08:54 linux ifup: No configuration found for dhcp
    Jan 25 23:09:15 linux ifup: No configuration found for auto
    Jan 25 23:09:26 linux ifdown: Interface not available and no configuration found.
    Jan 25 23:11:21 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 25 23:21:16 linux ifup: No configuration found for wlan0
    Jan 25 23:21:54 linux kernel: fwlanusb: module not supported by Novell, setting U taint flag.
    Jan 25 23:22:03 linux kernel: fwlanusb: Removing...
    Jan 25 23:22:03 linux kernel: usbcore: deregistering driver fwlanusb
    Jan 25 23:22:03 linux kernel: fwlanusb: RX URB d9f30c00: status -108
    Jan 25 23:22:03 linux kernel: fwlanusb: Submitting read URB failed (-90)!
    Jan 25 23:22:03 linux kernel: fwlanusb: RX URB d9f30080: status -108
    Jan 25 23:22:03 linux kernel: fwlanusb: Submitting read URB failed (-90)!
    Jan 25 23:22:03 linux kernel: fwlanusb: RX URB d9f30580: status -108
    Jan 25 23:22:03 linux kernel: fwlanusb: Submitting read URB failed (-90)!
    Jan 25 23:22:03 linux kernel: fwlanusb: RX URB d9f30180: status -108
    Jan 25 23:22:03 linux kernel: fwlanusb: Submitting read URB failed (-90)!
    Jan 25 23:22:03 linux kernel: fwlanusb: RX URB d9f30e00: status -108
    Jan 25 23:22:03 linux kernel: fwlanusb: Submitting read URB failed (-90)!
    Jan 25 23:22:03 linux kernel: fwlanusb: RX URB d9f30d80: status -108
    Jan 25 23:22:03 linux kernel: fwlanusb: Submitting read URB failed (-90)!
    Jan 25 23:22:03 linux kernel: fwlanusb: RX URB d9f30d00: status -108
    Jan 25 23:22:03 linux kernel: fwlanusb: Submitting read URB failed (-90)!
    Jan 25 23:22:03 linux kernel: fwlanusb: RX URB d9f30c80: status -108
    Jan 25 23:22:03 linux kernel: fwlanusb: Submitting read URB failed (-90)!
    Jan 25 23:22:03 linux kernel: fwlanusb: Cmd URB status: -2
    Jan 25 23:22:03 linux kernel: fwlanusb: Driver 'fwlanusb' detached
    Jan 25 23:22:03 linux kernel: fwlanusb: Removed.
    Jan 25 23:22:05 linux ifdown: Interface not available and no configuration found.
    Jan 25 23:22:07 linux kernel: fwlanusb: module not supported by Novell, setting U taint flag.
    Jan 25 23:22:07 linux kernel: fwlanusb: AVM FRITZ!WLAN USB Stick driver, revision 0.09.00-BETA
    Jan 25 23:22:07 linux kernel: fwlanusb: (fwlanusb built on Jan 25 2006 at 22:46:34)
    Jan 25 23:22:07 linux kernel: fwlanusb: -- 32 bit driver --
    Jan 25 23:22:07 linux kernel: fwlanusb: Loading...
    Jan 25 23:22:07 linux kernel: fwlanusb: Driver 'fwlanusb' attached to fwlanusb-stack. (160)
    Jan 25 23:22:07 linux kernel: usb 3-1: reset high speed USB device using ehci_hcd and address 2
    Jan 25 23:22:07 linux kernel: usb 3-1: device firmware changed
    Jan 25 23:22:07 linux kernel: fwlanusb: Reset failed.
    Jan 25 23:22:07 linux kernel: fwlanusb: (Device may not work properly.)
    Jan 25 23:22:07 linux kernel: fwlanusb: usb_read_write_sync: usb_bulk/control_msg = -19
    Jan 25 23:22:07 linux kernel: fwlanusb: usb_read_write_sync: usb_bulk/control_msg = -19
    Jan 25 23:22:07 linux kernel: fwlanusb: usb_read_write_sync: usb_bulk/control_msg = -19
    Jan 25 23:22:07 linux kernel: fwlanusb: stack_init: Creating of config manager failed.
    Jan 25 23:22:07 linux kernel: fwlanusb: stack_init failed!
    Jan 25 23:22:07 linux kernel: fwlanusb: Driver 'fwlanusb' detached
    Jan 25 23:22:07 linux kernel: usbcore: registered new driver fwlanusb
    Jan 25 23:22:07 linux kernel: fwlanusb: Loaded.
    Jan 25 23:22:07 linux kernel: usb 3-1: USB disconnect, address 2
    Jan 25 23:22:07 linux kernel: usb 3-1: new high speed USB device using ehci_hcd and address 5
    Jan 25 23:22:07 linux kernel: fwlanusb: Driver 'fwlanusb' attached to fwlanusb-stack. (160)
    Jan 25 23:22:07 linux kernel: usb 3-1: reset high speed USB device using ehci_hcd and address 5
    Jan 25 23:22:08 linux kernel: fwlanusb: Config manager successully created and started.
    Jan 25 23:22:13 linux ifup: No configuration found for wlan0
    Jan 25 23:22:16 linux ifup: No configuration found for wlan0
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -71
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -71
    Jan 25 23:44:44 linux kernel: usb 3-1: USB disconnect, address 5
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53300: status -108
    Jan 25 23:44:44 linux kernel: fwlanusb: Submitting read URB failed (-19)!
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53280: status -108
    Jan 25 23:44:44 linux kernel: fwlanusb: Submitting read URB failed (-19)!
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53e00: status -108
    Jan 25 23:44:44 linux kernel: fwlanusb: Submitting read URB failed (-19)!
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB f1c53500: status -108
    Jan 25 23:44:44 linux kernel: fwlanusb: Submitting read URB failed (-19)!
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2c00: status -108
    Jan 25 23:44:44 linux kernel: fwlanusb: Submitting read URB failed (-19)!
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2980: status -108
    Jan 25 23:44:44 linux kernel: fwlanusb: Submitting read URB failed (-19)!
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB e59d2d00: status -108
    Jan 25 23:44:44 linux kernel: fwlanusb: Submitting read URB failed (-19)!
    Jan 25 23:44:44 linux kernel: fwlanusb: RX URB cb489700: status -108
    Jan 25 23:44:44 linux kernel: fwlanusb: Submitting read URB failed (-19)!
    Jan 25 23:44:44 linux kernel: fwlanusb: Submitting cmd URB failed (-19)!
    Jan 25 23:44:44 linux kernel: fwlanusb: Driver 'fwlanusb' detached
    Jan 25 23:44:45 linux ifdown: Interface not available and no configuration found.
    Jan 25 23:44:45 linux kernel: atkbd.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
    Jan 25 23:44:45 linux kernel: atkbd.c: Use 'setkeycodes 00 <keycode>' to make it known.
    Jan 25 23:44:45 linux kernel: psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
    Jan 25 23:44:45 linux kernel: psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
    Jan 25 23:44:45 linux kernel: psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
    Jan 25 23:44:45 linux kernel: psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
    Jan 25 23:44:45 linux kernel: psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1
    Jan 25 23:44:45 linux kernel: psmouse.c: TouchPad at isa0060/serio2/input0 - driver resynched.
    Jan 25 23:44:52 linux syslog-ng[25953]: STATS: dropped 0
    Jan 25 23:50:40 linux kernel: usb 3-1: new high speed USB device using ehci_hcd and address 6
    Jan 25 23:50:41 linux kernel: fwlanusb: Driver 'fwlanusb' attached to fwlanusb-stack. (160)
    Jan 25 23:50:41 linux kernel: usb 3-1: reset high speed USB device using ehci_hcd and address 6
    Jan 25 23:50:41 linux kernel: fwlanusb: Config manager successully created and started.
    Jan 25 23:50:46 linux ifup: No configuration found for wlan0
    Jan 25 23:51:15 linux dhcpcd[2731]: terminating on signal 15
    Jan 25 23:51:15 linux modify_resolvconf: restored /etc/resolv.conf.saved.by.dhcpcd.eth0 to /etc/resolv.conf
    Jan 25 23:51:16 linux ifdown: No configuration found for wlan0
    Jan 25 23:51:16 linux ifdown: Nevertheless the interface will be shut down.
    Jan 25 23:51:19 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 25 23:51:21 linux kernel: martian source 255.255.255.255 from 192.168.178.1, on dev eth0
    Jan 25 23:51:21 linux kernel: ll header: ff:ff:ff:ff:ff:ff:00:04:0e:62:f0:43:08:00
    Jan 25 23:51:21 linux modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file
    Jan 25 23:51:22 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 23:51:22 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 25 23:51:22 linux SuSEfirewall2: batch committing...
    Jan 25 23:51:22 linux SuSEfirewall2: Firewall rules successfully set
    Jan 25 23:51:22 linux ifup: No configuration found for wlan0
    Jan 25 23:51:23 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.

  7. #7
    Registrierter Benutzer
    Registriert seit
    Jan 2006
    Beiträge
    49
    Hier Teil 3

    Jan 25 23:51:23 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 25 23:51:23 linux SuSEfirewall2: batch committing...
    Jan 25 23:51:23 linux SuSEfirewall2: Firewall rules successfully set
    Jan 25 23:51:28 linux kernel: eth0: no IPv6 routers present
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -71
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -71
    Jan 26 00:00:12 linux kernel: usb 3-1: USB disconnect, address 6
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc300: status -108
    Jan 26 00:00:12 linux kernel: fwlanusb: Submitting read URB failed (-19)!
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcc00: status -108
    Jan 26 00:00:12 linux kernel: fwlanusb: Submitting read URB failed (-19)!
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bce80: status -108
    Jan 26 00:00:12 linux kernel: fwlanusb: Submitting read URB failed (-19)!
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcb80: status -108
    Jan 26 00:00:12 linux kernel: fwlanusb: Submitting read URB failed (-19)!
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd80: status -108
    Jan 26 00:00:12 linux kernel: fwlanusb: Submitting read URB failed (-19)!
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc380: status -108
    Jan 26 00:00:12 linux kernel: fwlanusb: Submitting read URB failed (-19)!
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bcd00: status -108
    Jan 26 00:00:12 linux kernel: fwlanusb: Submitting read URB failed (-19)!
    Jan 26 00:00:12 linux kernel: fwlanusb: RX URB cf0bc880: status -108
    Jan 26 00:00:12 linux kernel: fwlanusb: Submitting read URB failed (-19)!
    Jan 26 00:00:12 linux kernel: fwlanusb: Submitting cmd URB failed (-19)!
    Jan 26 00:00:12 linux kernel: fwlanusb: Driver 'fwlanusb' detached
    Jan 26 00:00:13 linux ifdown: Interface not available and no configuration found.
    Jan 26 00:00:36 linux kernel: usb 3-1: new high speed USB device using ehci_hcd and address 7
    Jan 26 00:00:36 linux kernel: fwlanusb: Driver 'fwlanusb' attached to fwlanusb-stack. (160)
    Jan 26 00:00:36 linux kernel: usb 3-1: reset high speed USB device using ehci_hcd and address 7
    Jan 26 00:00:37 linux kernel: fwlanusb: Config manager successully created and started.
    Jan 26 00:00:42 linux ifup: No configuration found for wlan0
    Jan 26 00:02:01 linux dhcpcd[4975]: terminating on signal 15
    Jan 26 00:02:01 linux modify_resolvconf: restored /etc/resolv.conf.saved.by.dhcpcd.eth0 to /etc/resolv.conf
    Jan 26 00:02:03 linux ifdown: No configuration found for wlan0
    Jan 26 00:02:03 linux ifdown: Nevertheless the interface will be shut down.
    Jan 26 00:02:06 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 26 00:02:08 linux kernel: martian source 255.255.255.255 from 192.168.178.1, on dev eth0
    Jan 26 00:02:08 linux kernel: ll header: ff:ff:ff:ff:ff:ff:00:04:0e:62:f0:43:08:00
    Jan 26 00:02:08 linux modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file
    Jan 26 00:02:08 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.

  8. #8
    Registrierter Benutzer
    Registriert seit
    Jan 2006
    Beiträge
    49
    Und nun der Rest vom Schützenfest:


    Jan 26 00:02:08 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:02:09 linux SuSEfirewall2: batch committing...
    Jan 26 00:02:09 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:02:09 linux ifup: No configuration found for wlan0
    Jan 26 00:02:09 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:02:09 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:02:10 linux SuSEfirewall2: batch committing...
    Jan 26 00:02:10 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:02:14 linux kernel: eth0: no IPv6 routers present
    Jan 26 00:02:43 linux dhcpcd[6156]: terminating on signal 15
    Jan 26 00:02:43 linux modify_resolvconf: restored /etc/resolv.conf.saved.by.dhcpcd.eth0 to /etc/resolv.conf
    Jan 26 00:02:44 linux ifdown: No configuration found for wlan0
    Jan 26 00:02:44 linux ifdown: Nevertheless the interface will be shut down.
    Jan 26 00:02:48 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 26 00:02:50 linux kernel: martian source 255.255.255.255 from 192.168.178.1, on dev eth0
    Jan 26 00:02:50 linux kernel: ll header: ff:ff:ff:ff:ff:ff:00:04:0e:62:f0:43:08:00
    Jan 26 00:02:50 linux modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file
    Jan 26 00:02:50 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:02:50 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:02:50 linux SuSEfirewall2: batch committing...
    Jan 26 00:02:50 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:02:51 linux ifup: No configuration found for wlan0
    Jan 26 00:02:51 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:02:51 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:02:51 linux SuSEfirewall2: batch committing...
    Jan 26 00:02:51 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:02:57 linux kernel: eth0: no IPv6 routers present
    Jan 26 00:03:17 linux dhcpcd[6924]: terminating on signal 15
    Jan 26 00:03:17 linux modify_resolvconf: restored /etc/resolv.conf.saved.by.dhcpcd.eth0 to /etc/resolv.conf
    Jan 26 00:03:18 linux ifdown: No configuration found for wlan0
    Jan 26 00:03:18 linux ifdown: Nevertheless the interface will be shut down.
    Jan 26 00:03:21 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 26 00:03:23 linux kernel: martian source 255.255.255.255 from 192.168.178.1, on dev eth0
    Jan 26 00:03:23 linux kernel: ll header: ff:ff:ff:ff:ff:ff:00:04:0e:62:f0:43:08:00
    Jan 26 00:03:24 linux modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file
    Jan 26 00:03:24 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:03:24 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:03:24 linux SuSEfirewall2: batch committing...
    Jan 26 00:03:24 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:03:25 linux ifup: No configuration found for wlan0
    Jan 26 00:03:25 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:03:25 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:03:25 linux SuSEfirewall2: batch committing...
    Jan 26 00:03:25 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:03:30 linux kernel: eth0: no IPv6 routers present
    Jan 26 00:31:11 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:31:11 linux SuSEfirewall2: batch committing...
    Jan 26 00:31:11 linux SuSEfirewall2: Firewall rules unloaded.
    Jan 26 00:31:11 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:31:12 linux SuSEfirewall2: batch committing...
    Jan 26 00:31:12 linux SuSEfirewall2: Firewall rules set to CLOSE.
    Jan 26 00:31:12 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:31:12 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:31:12 linux SuSEfirewall2: batch committing...
    Jan 26 00:31:12 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:31:13 linux ifstatus: No configuration found for wlan0
    Jan 26 00:31:13 linux ifstatus: No configuration found for wlan0
    Jan 26 00:31:14 linux dhcpcd[7701]: terminating on signal 15
    Jan 26 00:31:14 linux modify_resolvconf: restored /etc/resolv.conf.saved.by.dhcpcd.eth0 to /etc/resolv.conf
    Jan 26 00:31:17 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 26 00:31:19 linux kernel: martian source 255.255.255.255 from 192.168.178.1, on dev eth0
    Jan 26 00:31:19 linux kernel: ll header: ff:ff:ff:ff:ff:ff:00:04:0e:62:f0:43:08:00
    Jan 26 00:31:20 linux modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file
    Jan 26 00:31:20 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:31:20 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:31:20 linux SuSEfirewall2: batch committing...
    Jan 26 00:31:20 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:31:20 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:31:21 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:31:21 linux SuSEfirewall2: batch committing...
    Jan 26 00:31:21 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:31:25 linux kernel: eth0: no IPv6 routers present
    Jan 26 00:31:31 linux dhcpcd[9503]: terminating on signal 15
    Jan 26 00:31:31 linux modify_resolvconf: restored /etc/resolv.conf.saved.by.dhcpcd.eth0 to /etc/resolv.conf
    Jan 26 00:31:32 linux ifdown: No configuration found for wlan0
    Jan 26 00:31:32 linux ifdown: Nevertheless the interface will be shut down.
    Jan 26 00:31:35 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 26 00:31:38 linux kernel: martian source 255.255.255.255 from 192.168.178.1, on dev eth0
    Jan 26 00:31:38 linux kernel: ll header: ff:ff:ff:ff:ff:ff:00:04:0e:62:f0:43:08:00
    Jan 26 00:31:38 linux modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file
    Jan 26 00:31:38 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:31:38 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:31:38 linux SuSEfirewall2: batch committing...
    Jan 26 00:31:38 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:31:39 linux ifup: No configuration found for wlan0
    Jan 26 00:31:39 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:31:39 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:31:39 linux SuSEfirewall2: batch committing...
    Jan 26 00:31:39 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:31:44 linux kernel: eth0: no IPv6 routers present
    Jan 26 00:33:57 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:33:57 linux SuSEfirewall2: batch committing...
    Jan 26 00:33:57 linux SuSEfirewall2: Firewall rules unloaded.
    Jan 26 00:33:57 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:33:57 linux SuSEfirewall2: batch committing...
    Jan 26 00:33:57 linux SuSEfirewall2: Firewall rules set to CLOSE.
    Jan 26 00:33:57 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:33:57 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:33:58 linux SuSEfirewall2: batch committing...
    Jan 26 00:33:58 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:33:58 linux ifstatus: No configuration found for wlan0
    Jan 26 00:33:58 linux ifstatus: No configuration found for wlan0
    Jan 26 00:34:00 linux dhcpcd[10428]: terminating on signal 15
    Jan 26 00:34:00 linux modify_resolvconf: restored /etc/resolv.conf.saved.by.dhcpcd.eth0 to /etc/resolv.conf
    Jan 26 00:34:03 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 26 00:34:05 linux kernel: martian source 255.255.255.255 from 192.168.178.1, on dev eth0
    Jan 26 00:34:05 linux kernel: ll header: ff:ff:ff:ff:ff:ff:00:04:0e:62:f0:43:08:00
    Jan 26 00:34:05 linux modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file
    Jan 26 00:34:06 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:34:06 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:34:06 linux SuSEfirewall2: batch committing...
    Jan 26 00:34:06 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:34:06 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:34:06 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:34:07 linux SuSEfirewall2: batch committing...
    Jan 26 00:34:07 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:34:12 linux kernel: eth0: no IPv6 routers present
    Jan 26 00:34:13 linux dhcpcd[11684]: terminating on signal 15
    Jan 26 00:34:13 linux modify_resolvconf: restored /etc/resolv.conf.saved.by.dhcpcd.eth0 to /etc/resolv.conf
    Jan 26 00:34:15 linux ifdown: No configuration found for wlan0
    Jan 26 00:34:15 linux ifdown: Nevertheless the interface will be shut down.
    Jan 26 00:34:18 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 26 00:34:20 linux kernel: martian source 255.255.255.255 from 192.168.178.1, on dev eth0
    Jan 26 00:34:20 linux kernel: ll header: ff:ff:ff:ff:ff:ff:00:04:0e:62:f0:43:08:00
    Jan 26 00:34:20 linux modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file
    Jan 26 00:34:20 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:34:20 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:34:21 linux SuSEfirewall2: batch committing...
    Jan 26 00:34:21 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:34:21 linux ifup: No configuration found for wlan0
    Jan 26 00:34:21 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:34:21 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:34:22 linux SuSEfirewall2: batch committing...
    Jan 26 00:34:22 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:34:26 linux kernel: eth0: no IPv6 routers present
    Jan 26 00:36:23 linux dhcpcd[12610]: terminating on signal 15
    Jan 26 00:36:23 linux modify_resolvconf: restored /etc/resolv.conf.saved.by.dhcpcd.eth0 to /etc/resolv.conf
    Jan 26 00:36:25 linux ifdown: No configuration found for wlan0
    Jan 26 00:36:25 linux ifdown: Nevertheless the interface will be shut down.
    Jan 26 00:36:28 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 26 00:36:30 linux kernel: martian source 255.255.255.255 from 192.168.178.1, on dev eth0
    Jan 26 00:36:30 linux kernel: ll header: ff:ff:ff:ff:ff:ff:00:04:0e:62:f0:43:08:00
    Jan 26 00:36:30 linux modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file
    Jan 26 00:36:30 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:36:30 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:36:30 linux SuSEfirewall2: batch committing...
    Jan 26 00:36:31 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:36:31 linux ifup: No configuration found for wlan0
    Jan 26 00:36:31 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:36:31 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:36:32 linux SuSEfirewall2: batch committing...
    Jan 26 00:36:32 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:36:36 linux kernel: eth0: no IPv6 routers present
    Jan 26 00:36:51 linux dhcpcd[13417]: terminating on signal 15
    Jan 26 00:36:51 linux modify_resolvconf: restored /etc/resolv.conf.saved.by.dhcpcd.eth0 to /etc/resolv.conf
    Jan 26 00:36:52 linux ifdown: No configuration found for wlan0
    Jan 26 00:36:52 linux ifdown: Nevertheless the interface will be shut down.
    Jan 26 00:36:56 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 26 00:36:58 linux kernel: martian source 255.255.255.255 from 192.168.178.1, on dev eth0
    Jan 26 00:36:58 linux kernel: ll header: ff:ff:ff:ff:ff:ff:00:04:0e:62:f0:43:08:00
    Jan 26 00:36:58 linux modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file
    Jan 26 00:36:58 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:36:58 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:36:58 linux SuSEfirewall2: batch committing...
    Jan 26 00:36:58 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:36:59 linux ifup: No configuration found for wlan0
    Jan 26 00:36:59 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:36:59 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:36:59 linux SuSEfirewall2: batch committing...
    Jan 26 00:36:59 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:37:04 linux kernel: eth0: no IPv6 routers present
    Jan 26 00:40:47 linux dhcpcd[14189]: terminating on signal 15
    Jan 26 00:40:47 linux modify_resolvconf: restored /etc/resolv.conf.saved.by.dhcpcd.eth0 to /etc/resolv.conf
    Jan 26 00:40:48 linux ifdown: No configuration found for wlan0
    Jan 26 00:40:48 linux ifdown: Nevertheless the interface will be shut down.
    Jan 26 00:40:52 linux kernel: eth0: Media Link On 100mbps full-duplex
    Jan 26 00:40:54 linux kernel: martian source 255.255.255.255 from 192.168.178.1, on dev eth0
    Jan 26 00:40:54 linux kernel: ll header: ff:ff:ff:ff:ff:ff:00:04:0e:62:f0:43:08:00
    Jan 26 00:40:54 linux modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file
    Jan 26 00:40:54 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:40:54 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:40:54 linux SuSEfirewall2: batch committing...
    Jan 26 00:40:54 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:40:55 linux ifup: No configuration found for wlan0
    Jan 26 00:40:55 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 26 00:40:55 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 26 00:40:55 linux SuSEfirewall2: batch committing...
    Jan 26 00:40:55 linux SuSEfirewall2: Firewall rules successfully set
    Jan 26 00:41:00 linux kernel: eth0: no IPv6 routers present
    Jan 26 00:41:47 linux kernel: fwlanusb: module not supported by Novell, setting U taint flag.
    Jan 26 00:41:54 linux kernel: fwlanusb: Removing...
    Jan 26 00:41:54 linux kernel: usbcore: deregistering driver fwlanusb
    Jan 26 00:41:54 linux kernel: fwlanusb: RX URB f2600880: status -108
    Jan 26 00:41:54 linux kernel: fwlanusb: Submitting read URB failed (-90)!
    Jan 26 00:41:54 linux kernel: fwlanusb: RX URB f2600080: status -108
    Jan 26 00:41:54 linux kernel: fwlanusb: Submitting read URB failed (-90)!
    Jan 26 00:41:54 linux kernel: fwlanusb: RX URB c83a5080: status -108
    Jan 26 00:41:54 linux kernel: fwlanusb: Submitting read URB failed (-90)!
    Jan 26 00:41:54 linux kernel: fwlanusb: RX URB c83a5900: status -108
    Jan 26 00:41:54 linux kernel: fwlanusb: Submitting read URB failed (-90)!
    Jan 26 00:41:54 linux kernel: fwlanusb: RX URB c83a5880: status -108
    Jan 26 00:41:54 linux kernel: fwlanusb: Submitting read URB failed (-90)!
    Jan 26 00:41:54 linux kernel: fwlanusb: RX URB f2600780: status -108
    Jan 26 00:41:54 linux kernel: fwlanusb: Submitting read URB failed (-90)!
    Jan 26 00:41:54 linux kernel: fwlanusb: RX URB f2600800: status -108
    Jan 26 00:41:54 linux kernel: fwlanusb: Submitting read URB failed (-90)!
    Jan 26 00:41:54 linux kernel: fwlanusb: RX URB f2600700: status -108
    Jan 26 00:41:54 linux kernel: fwlanusb: Submitting read URB failed (-90)!
    Jan 26 00:41:54 linux kernel: fwlanusb: Cmd URB status: -2
    Jan 26 00:41:54 linux kernel: fwlanusb: Driver 'fwlanusb' detached
    Jan 26 00:41:54 linux kernel: fwlanusb: Removed.
    Jan 26 00:41:55 linux ifdown: Interface not available and no configuration found.
    Jan 26 00:41:59 linux kernel: fwlanusb: module not supported by Novell, setting U taint flag.
    Jan 26 00:41:59 linux kernel: fwlanusb: AVM FRITZ!WLAN USB Stick driver, revision 0.09.00-BETA
    Jan 26 00:41:59 linux kernel: fwlanusb: (fwlanusb built on Jan 25 2006 at 22:46:34)
    Jan 26 00:41:59 linux kernel: fwlanusb: -- 32 bit driver --
    Jan 26 00:41:59 linux kernel: fwlanusb: Loading...
    Jan 26 00:41:59 linux kernel: fwlanusb: Driver 'fwlanusb' attached to fwlanusb-stack. (160)
    Jan 26 00:41:59 linux kernel: usb 3-1: reset high speed USB device using ehci_hcd and address 7
    Jan 26 00:41:59 linux kernel: usb 3-1: device firmware changed
    Jan 26 00:41:59 linux kernel: fwlanusb: Reset failed.
    Jan 26 00:41:59 linux kernel: fwlanusb: (Device may not work properly.)
    Jan 26 00:41:59 linux kernel: fwlanusb: usb_read_write_sync: usb_bulk/control_msg = -19
    Jan 26 00:41:59 linux kernel: fwlanusb: usb_read_write_sync: usb_bulk/control_msg = -19
    Jan 26 00:41:59 linux kernel: fwlanusb: usb_read_write_sync: usb_bulk/control_msg = -19
    Jan 26 00:41:59 linux kernel: fwlanusb: stack_init: Creating of config manager failed.
    Jan 26 00:41:59 linux kernel: fwlanusb: stack_init failed!
    Jan 26 00:41:59 linux kernel: fwlanusb: Driver 'fwlanusb' detached
    Jan 26 00:41:59 linux kernel: usbcore: registered new driver fwlanusb
    Jan 26 00:41:59 linux kernel: fwlanusb: Loaded.
    Jan 26 00:41:59 linux kernel: usb 3-1: USB disconnect, address 7
    Jan 26 00:41:59 linux kernel: usb 3-1: new high speed USB device using ehci_hcd and address 8
    Jan 26 00:41:59 linux kernel: fwlanusb: Driver 'fwlanusb' attached to fwlanusb-stack. (160)
    Jan 26 00:41:59 linux kernel: usb 3-1: reset high speed USB device using ehci_hcd and address 8
    Jan 26 00:42:00 linux kernel: fwlanusb: Config manager successully created and started.
    Jan 26 00:42:05 linux ifup: No configuration found for wlan0
    Jan 26 00:43:04 linux ifup: No configuration found for wlan0
    Jan 26 00:44:52 linux syslog-ng[25953]: STATS: dropped 0


    So,nun hoff ich doch,denn die Hoffnung stirbt zuletzt.

    Greetz Cali37

  9. #9
    Moderator Avatar von DaGrrr
    Registriert seit
    Jul 2002
    Ort
    Berlin
    Beiträge
    1.892
    Das ist nen Scherz oder?

    Bitte editiere deine Postings und setze die Ausgaben in code Tags... also so:
    Code:
    Hier alles einfügen.
    Grüße
    DaGrrr
    PC: Kubuntu 11.04
    Router: Soekris net4801 mit OpenBSD 4.8
    Server: OpenBSD 4.7
    Private Linux Page

  10. #10
    Registrierter Benutzer
    Registriert seit
    Jan 2006
    Beiträge
    49

    Ne ist kein scherz

    Hallo,

    sorry,bin noch neu aber lernfähig.
    Wußte das mit dem Code einfügen net.
    Werde es aber ab jetzt tun.

    PHP-Code:
    Jan 25 22:25:30 linux syslog-ng[14781]: syslog-ng version 1.6.8 starting
    Jan 25 22
    :25:30 linux modprobeFATALError inserting asus_acpi (/lib/modules/2.6.13-15-default/kernel/drivers/acpi/asus_acpi.ko): No such device
    Jan 25 22
    :25:30 linux modprobeFATALError inserting ibm_acpi (/lib/modules/2.6.13-15-default/kernel/drivers/acpi/ibm_acpi.ko): No such device
    Jan 25 22
    :25:30 linux modprobeFATALError inserting toshiba_acpi (/lib/modules/2.6.13-15-default/kernel/drivers/acpi/toshiba_acpi.ko): No such device
    Jan 25 22
    :25:35 linux kernelklogd 1.4.1log source = /proc/kmsg started.
    Jan 25 22:25:35 linux kernellpdriver loaded but no devices found
    Jan 25 22
    :25:35 linux kernelAdding 1052216k swap on /dev/hda5.  Priority:-1 extents:1
    Jan 25 22
    :25:35 linux kernelusbcoreregistered new driver usbfs
    Jan 25 22
    :25:35 linux kernelusbcoreregistered new driver hub
    Jan 25 22
    :25:35 linux kernelohci_hcd2005 April 22 USB 1.1 'Open' Host Controller (OHCIDriver (PCI)
    Jan 25 22:25:35 linux syslog-ng[14781]: Changing permissions on special file /dev/xconsole
    Jan 25 22
    :25:35 linux syslog-ng[14781]: Changing permissions on special file /dev/tty10
    Jan 25 22
    :25:35 linux kernelACPIPCI Interrupt Link [LNKEenabled at IRQ 4
    Jan 25 22
    :25:35 linux kernelPCIsetting IRQ 4 as level-triggered
    Jan 25 22
    :25:35 linux kernelACPIPCI Interrupt 0000:00:03.0[A] -> Link [LNKE] -> GSI 4 (levellow) -> IRQ 4
    Jan 25 22
    :25:35 linux kernelohci_hcd 0000:00:03.0OHCI Host Controller
    Jan 25 22
    :25:35 linux kernelohci_hcd 0000:00:03.0: new USB bus registeredassigned bus number 1
    Jan 25 22
    :25:35 linux kernelohci_hcd 0000:00:03.0irq 4io mem 0xdfffd000
    Jan 25 22
    :25:35 linux kernelpci_hotplugPCI Hot Plug PCI Core version0.5
    Jan 25 22
    :25:35 linux kernelhub 1-0:1.0USB hub found
    Jan 25 22
    :25:35 linux kernelhub 1-0:1.03 ports detected
    Jan 25 22
    :25:35 linux kernelACPIPCI Interrupt Link [LNKFenabled at IRQ 3
    Jan 25 22
    :25:35 linux kernelPCIsetting IRQ 3 as level-triggered
    Jan 25 22
    :25:35 linux kernelACPIPCI Interrupt 0000:00:03.1[B] -> Link [LNKF] -> GSI 3 (levellow) -> IRQ 3
    Jan 25 22
    :25:35 linux kernelohci_hcd 0000:00:03.1OHCI Host Controller
    Jan 25 22
    :25:36 linux kernelohci_hcd 0000:00:03.1: new USB bus registeredassigned bus number 2
    Jan 25 22
    :25:36 linux kernelohci_hcd 0000:00:03.1irq 3io mem 0xdfffe000
    Jan 25 22
    :25:36 linux kernelshpchpshpc_init shpc_cap_offset == 0
    Jan 25 22
    :25:36 linux kernelhub 2-0:1.0USB hub found
    Jan 25 22
    :25:36 linux kernelhub 2-0:1.03 ports detected
    Jan 25 22
    :25:36 linux kernelshpchpStandard Hot Plug PCI Controller Driver version0.4
    Jan 25 22
    :25:36 linux kernelusb 1-1: new full speed USB device using ohci_hcd and address 2
    Jan 25 22
    :25:36 linux kernelsis900.cv1.08.08 Jan22 2005
    Jan 25 22
    :25:36 linux kernel:     ACPI-0212: *** WarningDevice is not power manageable
    Jan 25 22
    :25:36 linux kernelACPIPCI Interrupt Link [LNKDenabled at IRQ 5
    Jan 25 22
    :25:36 linux kernelACPIPCI Interrupt 0000:00:04.0[A] -> Link [LNKD] -> GSI 5 (levellow) -> IRQ 5
    Jan 25 22
    :25:36 linux kernel0000:00:04.0Realtek RTL8201 PHY transceiver found at address 1.
    Jan 25 22
    :25:36 linux kernel0000:00:04.0Using transceiver found at address 1 as default
    Jan 25 22:25:36 linux kerneleth0SiS 900 PCI Fast Ethernet at 0xd800IRQ 500:03:0d:34:26:f1.
    Jan 25 22:25:36 linux kernelLinux agpgart interface v0.101 (cDave Jones
    Jan 25 22
    :25:36 linux kernelagpgartDetected AGP bridge 0
    Jan 25 22
    :25:36 linux kernelagpgartAGP aperture is 32M 0xe0000000
    Jan 25 22
    :25:36 linux kernel:     ACPI-0212: *** WarningDevice is not power manageable
    Jan 25 22
    :25:36 linux kernelACPIPCI Interrupt Link [LNKHenabled at IRQ 5
    Jan 25 22
    :25:36 linux kernelACPIPCI Interrupt 0000:00:03.3[D] -> Link [LNKH] -> GSI 5 (levellow) -> IRQ 5
    Jan 25 22
    :25:36 linux kernelehci_hcd 0000:00:03.3EHCI Host Controller
    Jan 25 22
    :25:36 linux kernelehci_hcd 0000:00:03.3: new USB bus registeredassigned bus number 3
    Jan 25 22
    :25:36 linux kernelehci_hcd 0000:00:03.3irq 5io mem 0xdffff000
    Jan 25 22
    :25:36 linux kernelPCIcache line size of 64 is not supported by device 0000:00:03.3
    Jan 25 22
    :25:36 linux kernelehci_hcd 0000:00:03.3USB 2.0 initializedEHCI 1.00driver 10 Dec 2004
    Jan 25 22
    :25:36 linux kernelhub 3-0:1.0USB hub found
    Jan 25 22
    :25:36 linux kernelhub 3-0:1.06 ports detected
    Jan 25 22
    :25:36 linux kerneli2c-sis96x version 1.0.0
    Jan 25 22
    :25:36 linux kernelsis96x_smbus 0000:00:02.1SiS96x SMBus base address0x0c00
    Jan 25 22
    :25:36 linux kernelusb 3-1: new high speed USB device using ehci_hcd and address 2
    Jan 25 22
    :25:36 linux kernelhdcpacket command errorstatus=0x51 DriveReady SeekComplete Error }
    Jan 25 22:25:36 linux kernelhdcpacket command errorerror=0x54 AbortedCommand LastFailedSense=0x05 }
    Jan 25 22:25:36 linux kernelidefailed opcode wasunknown
    Jan 25 22
    :25:36 linux kernelusb 1-1USB disconnectaddress 2
    Jan 25 22
    :25:36 linux kernelACPIPCI Interrupt 0000:00:09.0[A] -> Link [LNKB] -> GSI 5 (levellow) -> IRQ 5
    Jan 25 22
    :25:36 linux kernelYentaCardBus bridge found at 0000:00:09.0 [1734:106c]
    Jan 25 22:25:36 linux kernelYenta O2res at 0x94/0xD400/ea
    Jan 25 22
    :25:36 linux kernelYenta O2enabling read prefetch/write burst
    Jan 25 22
    :25:36 linux kernelYentaISA IRQ mask 0x0ac0PCI irq 5
    Jan 25 22
    :25:36 linux kernelSocket status30000006
    Jan 25 22
    :25:36 linux kernelACPIPCI Interrupt 0000:00:09.1[A] -> Link [LNKB] -> GSI 5 (levellow) -> IRQ 5
    Jan 25 22
    :25:36 linux kernelYentaCardBus bridge found at 0000:00:09.1 [1734:106c]
    Jan 25 22:25:36 linux kernelYentaISA IRQ mask 0x0ac0PCI irq 5
    Jan 25 22
    :25:36 linux kernelSocket status30000006
    Jan 25 22
    :25:36 linux kernelieee1394Initialized config rom entry `ip1394'
    Jan 25 22:25:36 linux kernel: ohci1394: 
    $Rev: 1299 $ Ben Collins <bcollins@debian.org>
    Jan 25 22:25:36 linux kernel: ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [LNKD] -> GSI 5 (level, low) -> IRQ 5
    Jan 25 22:25:36 linux kernel: ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[5]  MMIO=[dfffb800-dfffbfff]  Max Packet=[2048]
    Jan 25 22:25:36 linux kernel: usb 1-2: new low speed USB device using ohci_hcd and address 4
    Jan 25 22:25:36 linux kernel: usbcore: registered new driver hiddev
    Jan 25 22:25:36 linux kernel: input: USB HID v1.10 Mouse [062a:0000] on usb-0000:00:03.0-2
    Jan 25 22:25:36 linux kernel: usbcore: registered new driver usbhid
    Jan 25 22:25:36 linux kernel: drivers/usb/input/hid-core.c: v2.01:USB HID core driver
    Jan 25 22:25:36 linux kernel: bootsplash: status on console 0 changed to on
    Jan 25 22:25:36 linux kernel: ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00030d53255e4f7b]
    Jan 25 22:25:36 linux kernel: cs: IO port probe 0x3e0-0x4ff: excluding 0x480-0x48f 0x4d0-0x4d7
    Jan 25 22:25:36 linux kernel: cs: IO port probe 0x100-0x3af: clean.
    Jan 25 22:25:36 linux kernel: cs: IO port probe 0xc00-0xcff: clean.
    Jan 25 22:25:36 linux kernel: cs: IO port probe 0x820-0x8ff: excluding 0x828-0x837 0x840-0x84f 0x858-0x89f
    Jan 25 22:25:36 linux kernel: cs: IO port probe 0xa00-0xaff: clean.
    Jan 25 22:25:36 linux kernel: cs: IO port probe 0x3e0-0x4ff: excluding 0x480-0x48f 0x4d0-0x4d7
    Jan 25 22:25:36 linux kernel: cs: IO port probe 0x100-0x3af: clean.
    Jan 25 22:25:36 linux kernel: cs: IO port probe 0xc00-0xcff: clean.
    Jan 25 22:25:36 linux kernel: cs: IO port probe 0x820-0x8ff: excluding 0x828-0x837 0x840-0x84f 0x858-0x89f
    Jan 25 22:25:36 linux kernel: cs: IO port probe 0xa00-0xaff: clean.
    Jan 25 22:25:36 linux kernel: ACPI: AC Adapter [AC0] (on-line)
    Jan 25 22:25:36 linux kernel: ACPI: Battery Slot [BAT0] (battery present)
    Jan 25 22:25:36 linux kernel: ACPI: Power Button (FF) [PWRF]
    Jan 25 22:25:36 linux kernel: ACPI: Lid Switch [LID]
    Jan 25 22:25:36 linux kernel: ACPI: Sleep Button (CM) [SLPB]
    Jan 25 22:25:36 linux kernel: ACPI: Power Button (CM) [PWRB]
    Jan 25 22:25:36 linux kernel: ibm_acpi: ec object not found
    Jan 25 22:25:36 linux kernel: pcc_acpi: module not supported by Novell, setting U taint flag.
    Jan 25 22:25:36 linux kernel: bootsplash: status on console 0 changed to on
    Jan 25 22:25:36 linux kernel: NET: Registered protocol family 10
    Jan 25 22:25:36 linux kernel: Disabled Privacy Extensions on device c036b920(lo)
    Jan 25 22:25:36 linux kernel: IPv6 over IPv4 tunneling driver
    Jan 25 22:25:44 linux kernel: SCSI subsystem initialized
    Jan 25 22:25:44 linux kernel: st: Version 20050501, fixed bufsize 32768, s/g segs 256
    Jan 25 22:25:44 linux kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
    Jan 25 22:25:44 linux kernel: hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
    Jan 25 22:25:44 linux kernel: ide: failed opcode was: unknown
    Jan 25 21:27:06 linux kernel: eth0: Media Link On 100mbps full-duplex 
    Jan 25 21:27:14 linux kernel: eth0: no IPv6 routers present
    Jan 25 21:27:25 linux kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
    Jan 25 21:27:25 linux kernel: hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
    Jan 25 21:27:25 linux kernel: ide: failed opcode was: unknown
    Jan 25 21:27:25 linux kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
    Jan 25 21:27:25 linux kernel: hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
    Jan 25 21:27:25 linux kernel: ide: failed opcode was: unknown
    Jan 25 21:27:25 linux kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
    Jan 25 21:27:25 linux kernel: hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
    Jan 25 21:27:25 linux kernel: ide: failed opcode was: unknown
    Jan 25 21:27:41 linux kernel: NET: Registered protocol family 17
    Jan 25 21:28:25 linux kernel: ip6_tables: (C) 2000-2002 Netfilter core team
    Jan 25 22:28:25 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 21:28:25 linux kernel: ip_tables: (C) 2000-2002 Netfilter core team
    Jan 25 21:28:25 linux kernel: ip_conntrack version 2.1 (7166 buckets, 57328 max) - 248 bytes per conntrack
    Jan 25 22:28:25 linux SuSEfirewall2: batch committing...
    Jan 25 22:28:25 linux SuSEfirewall2: Firewall rules set to CLOSE.
    Jan 25 22:28:25 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:28:25 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 25 22:28:25 linux SuSEfirewall2: Warning: no interface active
    Jan 25 22:28:25 linux SuSEfirewall2: batch committing...
    Jan 25 22:28:25 linux SuSEfirewall2: Firewall rules successfully set
    Jan 25 22:28:27 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:28:27 linux SuSEfirewall2: batch committing...
    Jan 25 22:28:27 linux SuSEfirewall2: Firewall rules set to CLOSE.
    Jan 25 22:28:27 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:28:27 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 25 22:28:28 linux SuSEfirewall2: Warning: no interface active
    Jan 25 22:28:28 linux SuSEfirewall2: batch committing...
    Jan 25 22:28:28 linux SuSEfirewall2: Firewall rules successfully set
    Jan 25 21:28:28 linux kernel: eth0: Media Link On 100mbps full-duplex 
    Jan 25 22:28:28 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:28:28 linux SuSEfirewall2: batch committing...
    Jan 25 22:28:28 linux SuSEfirewall2: Firewall rules set to CLOSE.
    Jan 25 22:28:28 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
    Jan 25 22:28:28 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Jan 25 22:28:29 linux SuSEfirewall2: batch committing...
    Jan 25 22:28:29 linux SuSEfirewall2: Firewall rules successfully set
    Jan 25 22:28:33 linux logger: BEGIN OF YAST2 INTERNET TEST
    Jan 25 21:28:36 linux kernel: eth0: no IPv6 routers present
    Jan 25 21:28:38 linux kernel: BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
    Jan 25 22:28:42 linux logger: END OF YAST2 INTERNET TEST
    Jan 25 22:31:45 linux syslog-ng[14781]: SIGHUP received, restarting syslog-ng
    Jan 25 22:31:46 linux su: (to nobody) root on none
    Jan 25 22:31:46 linux syslog-ng[14781]: new configuration initialized
    Jan 25 22:31:46 linux su: (to nobody) root on none
    Jan 25 22:31:46 linux su: (to nobody) root on none
    Jan 25 22:32:05 linux su: (to nobody) root on none
    Jan 25 22:32:15 linux init: Re-reading inittab
    Jan 25 21:32:31 linux kernel: lp: driver loaded but no devices found
    Jan 25 21:32:31 linux kernel: klogd 1.4.1, ---------- state change ---------- 
    Jan 25 21:32:31 linux kernel: lp: driver loaded but no devices found
    Jan 25 22:32:32 linux hp: unable to open /var/run/hpiod.port: No such file or directory: prnt/hpijs/hplip_api.c 75
    Jan 25 22:32:32 linux hp: unable to connect hpiod socket 50000: Connection refused: prnt/hpijs/hplip_api.c 693
    Jan 25 22:32:32 linux hp: unable to send ProbeDevices: Broken pipe
    Jan 25 22:33:30 linux syslog-ng[14781]: Changing permissions on special file /dev/xconsole
    Jan 25 22:33:30 linux syslog-ng[14781]: Changing permissions on special file /dev/tty10
    Jan 25 21:33:30 linux kernel:     ACPI-0212: *** Warning: Device is not power manageable
    Jan 25 21:33:30 linux kernel: ACPI: PCI Interrupt 0000:00:02.7[C] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
    Jan 25 21:33:30 linux kernel: intel8x0_measure_ac97_clock: measured 55518 usecs
    Jan 25 21:33:30 linux kernel: intel8x0: clocking to 48000
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 liny2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux y2base: resmgr: unable to connect to resmgrd: Datei oder Verzeichnis nicht gefunden
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 22:33:32 linux alsactl: resmgr: unable to connect to resmgrd: No such file or directory
    Jan 25 21:33:33 linux kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
    Jan 25 21:33:33 linux kernel: hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
    Jan 25 21:33:33 linux kernel: ide: failed opcode was: unknown
    Jan 25 22:33:42 linux init: Entering runlevel: 5
    Jan 25 21:33:43 linux kernel: bootsplash: status on console 0 changed to on
    Jan 25 21:33:43 linux kernel: Kernel logging (proc) stopped.
    Jan 25 21:33:43 linux kernel: Kernel log daemon terminating.
    Jan 25 22:33:44 linux syslog-ng[14781]: syslog-ng version 1.6.8 going down
    Jan 25 22:33:44 linux syslog-ng[25953]: syslog-ng version 1.6.8 starting
    Jan 25 22:33:44 linux syslog-ng[25953]: Changing permissions on special file /dev/xconsole
    Jan 25 22:33:44 linux syslog-ng[25953]: Changing permissions on special file /dev/tty10 

Ähnliche Themen

  1. Wie wird mein MP3-Player von Linux erkannt?
    Von 123Linux im Forum Mobiles Linux, Notebook, PDA
    Antworten: 30
    Letzter Beitrag: 25.06.05, 17:55
  2. USB Kartenleser/Hub: usb-storage Devicescan Problem
    Von Skipper im Forum stationäre Hardware
    Antworten: 1
    Letzter Beitrag: 22.05.05, 14:53
  3. Der (nicht willige) USB-Hub
    Von netswipe im Forum stationäre Hardware
    Antworten: 2
    Letzter Beitrag: 06.04.05, 11:20
  4. Suse 9.2 und Siemens Gigaset USB Adapter 54
    Von thesmarty im Forum Mobiles Linux, Notebook, PDA
    Antworten: 0
    Letzter Beitrag: 09.12.04, 22:31
  5. Erkennung von USB
    Von gast44 im Forum System installieren und konfigurieren
    Antworten: 22
    Letzter Beitrag: 01.08.04, 16:08

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •