----- Original Message -----
From: "Camaleón"
inicio el ordenador y entra en kde despues de poner la contraseña. Una vez en el ( ya no aparecen rayas, es la 10.0) puedo mover el mouse. Pero cuando kle doy una orden ej entrar en yast/miscelanea/mensajes, entra pero a la minima orden mas se bloquea. solo me deja mover el mouse pero no hace caso. y tengo que apagarlo a lo bestia.
Si te deja utilizar el teclado, entra en una sesión sin entorno
gráfico (ctrl+alt+f1), entra como usuario y trabaja con el equipo para
ver si se queda bloqueado de la misma forma. Para acceder a yast desde
terminal ejecuta simplemente "yast", te mueves con el tabulador y las
flechas.
Otra posibilidad sería acceder al equipo desde la red vía ssh (te
sirve un equipo con windows -putty- u otro con suse) para ver si te
deja acceder de esta forma.
Los bloqueos de ese tipo suelen ser debidos a fallo de componentes
(fuente de alimentación, disco duro, memoria, placa base...). Este
tipo de errores no suele dejar rastro ni mensajes de error en el
registro, por eso es interesante la salida de dmesg.
Saludos,
--
Camaleón
Hola:
He hecho ctrl+alt+f10. Pero sale un mensaje enorme. ¿Se guarda en archivo y
con que nombre/directorio?
Por otro lado he bajado y usado la utilidad "Seatools de seagate" (lei el
otro dia que lo aconsejaban). Y me da errores. En las particiones NTFS. Las
particiones de Linux no las analiza.
Si tengo mal el disco duro. ¿Debo reinstalarlo todo y usar la erramienta
"Diskwizard de seagate"?
Adjunto debajo el contenido de "messages"
Gracias
Alejo
Jan 23 19:17:43 linux syslog-ng[4737]: syslog-ng version 1.6.8 starting
Jan 23 19:17:48 linux modprobe: FATAL: Error inserting asus_acpi
(/lib/modules/2.6.13-15-smp/kernel/drivers/acpi/asus_acpi.ko): No such
device
Jan 23 19:17:48 linux kernel: klogd 1.4.1, log source = /proc/kmsg started.
Jan 23 19:17:48 linux kernel: parport: PnPBIOS parport detected.
Jan 23 19:17:48 linux kernel: parport0: PC-style at 0x378, irq 7
[PCSPP,TRISTATE]
Jan 23 19:17:48 linux kernel: lp0: using parport0 (interrupt-driven).
Jan 23 19:17:48 linux kernel: usbcore: registered new driver usbfs
Jan 23 19:17:48 linux kernel: usbcore: registered new driver hub
Jan 23 19:17:48 linux kernel: Linux agpgart interface v0.101 (c) Dave Jones
Jan 23 19:17:48 linux kernel: agpgart: Detected SiS 655 chipset
Jan 23 19:17:48 linux kernel: agpgart: AGP aperture is 64M @ 0xf8000000
Jan 23 19:17:48 linux kernel: ohci_hcd: 2005 April 22 USB 1.1 'Open' Host
Controller (OHCI) Driver (PCI)
Jan 23 19:17:48 linux kernel: ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 20
(level, low) -> IRQ 177
Jan 23 19:17:48 linux kernel: ohci_hcd 0000:00:03.0: OHCI Host Controller
Jan 23 19:17:48 linux kernel: ohci_hcd 0000:00:03.0: new USB bus registered,
assigned bus number 1
Jan 23 19:17:48 linux kernel: ohci_hcd 0000:00:03.0: irq 177, io mem
0xfebfc000
Jan 23 19:17:48 linux kernel: hub 1-0:1.0: USB hub found
Jan 23 19:17:48 linux kernel: hub 1-0:1.0: 3 ports detected
Jan 23 19:17:48 linux modprobe: FATAL: Error inserting ibm_acpi
(/lib/modules/2.6.13-15-smp/kernel/drivers/acpi/ibm_acpi.ko): No such device
Jan 23 19:17:48 linux kernel: ACPI: PCI Interrupt 0000:00:03.1[B] -> GSI 21
(level, low) -> IRQ 185
Jan 23 19:17:48 linux kernel: ohci_hcd 0000:00:03.1: OHCI Host Controller
Jan 23 19:17:48 linux kernel: ohci_hcd 0000:00:03.1: new USB bus registered,
assigned bus number 2
Jan 23 19:17:48 linux kernel: ohci_hcd 0000:00:03.1: irq 185, io mem
0xfebfd000
Jan 23 19:17:48 linux kernel: hub 2-0:1.0: USB hub found
Jan 23 19:17:48 linux kernel: hub 2-0:1.0: 3 ports detected
Jan 23 19:17:48 linux kernel: ACPI: PCI Interrupt 0000:00:03.2[C] -> GSI 22
(level, low) -> IRQ 193
Jan 23 19:17:48 linux kernel: ohci_hcd 0000:00:03.2: OHCI Host Controller
Jan 23 19:17:48 linux kernel: ohci_hcd 0000:00:03.2: new USB bus registered,
assigned bus number 3
Jan 23 19:17:48 linux kernel: ohci_hcd 0000:00:03.2: irq 193, io mem
0xfebfe000
Jan 23 19:17:48 linux kernel: pci_hotplug: PCI Hot Plug PCI Core version:
0.5
Jan 23 19:17:48 linux syslog-ng[4737]: Changing permissions on special file
/dev/xconsole
Jan 23 19:17:48 linux syslog-ng[4737]: Changing permissions on special file
/dev/tty10
Jan 23 19:17:48 linux kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jan 23 19:17:48 linux kernel: hub 3-0:1.0: USB hub found
Jan 23 19:17:48 linux kernel: hub 3-0:1.0: 2 ports detected
Jan 23 19:17:48 linux kernel: shpchp: Standard Hot Plug PCI Controller
Driver version: 0.4
Jan 23 19:17:48 linux kernel: ACPI-0212: *** Warning: Device is not
power manageable
Jan 23 19:17:48 linux kernel: ACPI: PCI Interrupt 0000:00:03.3[D] -> GSI 23
(level, low) -> IRQ 201
Jan 23 19:17:48 linux kernel: ehci_hcd 0000:00:03.3: EHCI Host Controller
Jan 23 19:17:48 linux kernel: ehci_hcd 0000:00:03.3: new USB bus registered,
assigned bus number 4
Jan 23 19:17:48 linux kernel: ehci_hcd 0000:00:03.3: irq 201, io mem
0xfebff000
Jan 23 19:17:48 linux kernel: PCI: cache line size of 128 is not supported
by device 0000:00:03.3
Jan 23 19:17:48 linux kernel: ehci_hcd 0000:00:03.3: USB 2.0 initialized,
EHCI 1.00, driver 10 Dec 2004
Jan 23 19:17:48 linux kernel: hub 4-0:1.0: USB hub found
Jan 23 19:17:48 linux kernel: hub 4-0:1.0: 8 ports detected
Jan 23 19:17:48 linux kernel: sis900.c: v1.08.08 Jan. 22 2005
Jan 23 19:17:48 linux kernel: ACPI-0212: *** Warning: Device is not
power manageable
Jan 23 19:17:48 linux kernel: ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 19
(level, low) -> IRQ 209
Jan 23 19:17:48 linux kernel: 0000:00:04.0: Realtek RTL8201 PHY transceiver
found at address 1.
Jan 23 19:17:48 linux kernel: 0000:00:04.0: Using transceiver found at
address 1 as default
Jan 23 19:17:48 linux kernel: eth0: SiS 900 PCI Fast Ethernet at 0xe400, IRQ
209, 00:13:d4:a7:ec:f1.
Jan 23 19:17:48 linux kernel: usb 3-1: new full speed USB device using
ohci_hcd and address 2
Jan 23 19:17:48 linux kernel: hdb: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW
drive, 2048kB Cache, UDMA(33)
Jan 23 19:17:48 linux kernel: Uniform CD-ROM driver Revision: 3.20
Jan 23 19:17:48 linux kernel: ACPI: Power Button (FF) [PWRF]
Jan 23 19:17:48 linux kernel: ACPI: Power Button (CM) [PWRB]
Jan 23 19:17:48 linux kernel: ibm_acpi: ec object not found
Jan 23 19:17:48 linux modprobe: FATAL: Error inserting toshiba_acpi
(/lib/modules/2.6.13-15-smp/kernel/drivers/acpi/toshiba_acpi.ko): No such
device
Jan 23 19:17:48 linux kernel: pcc_acpi: module not supported by Novell,
setting U taint flag.
Jan 23 19:17:49 linux hal-subfs-mount[4941]: MOUNTPOINT:: /media/floppy
Jan 23 19:17:50 linux kernel: subfs 0.9
Jan 23 19:17:50 linux hal-subfs-mount[4941]: Collected mount options and
Called(0) /bin/mount -t subfs -o fs=floppyfss,sync,procuid,nosuid,nodev,exec
/dev/fd0 "/media/floppy"
Jan 23 19:17:50 linux kernel: end_request: I/O error, dev fd0, sector 0
Jan 23 19:17:50 linux kernel: end_request: I/O error, dev fd0, sector 0
Jan 23 19:17:50 linux kernel: end_request: I/O error, dev fd0, sector 0
Jan 23 19:17:50 linux kernel: end_request: I/O error, dev fd0, sector 0
Jan 23 19:17:50 linux submountd: mount failure, No such device or address
Jan 23 19:17:50 linux kernel: subfs: unsuccessful attempt to mount media
(256)
Jan 23 19:17:51 linux hal-subfs-mount[5367]: SYMLINKS::
disk/by-id/ata-HL-DT-ST_DVDRAM_GSA-4167B_BB2B211389DA
disk/by-path/pci-0000:00:02.5-ide-0:1 dvdram cdrom dvd cdrecorder
Jan 23 19:17:51 linux hal-subfs-mount[5367]: MOUNT_POINT:: /media/dvdram
Jan 23 19:17:51 linux hal-subfs-mount[5367]: MOUNTPOINT:: /media/dvdram
Jan 23 19:17:52 linux hal-subfs-mount[5367]: Collected mount options and
Called(0) /bin/mount -t subfs -o
fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 /dev/hdb
"/media/dvdram"
Jan 23 19:17:52 linux kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
Jan 23 19:17:52 linux udevd[2211]: get_netlink_msg: no ACTION in payload
found, skip event 'mount'
Jan 23 19:17:52 linux kernel: ISO 9660 Extensions: RRIP_1991A
Jan 23 19:17:54 linux kernel: bootsplash: status on console 0 changed to on
Jan 23 19:17:54 linux kernel: NET: Registered protocol family 10
Jan 23 19:17:54 linux kernel: Disabled Privacy Extensions on device
c03ba0a0(lo)
Jan 23 19:17:54 linux kernel: IPv6 over IPv4 tunneling driver
Jan 23 19:17:55 linux udevd[2211]: get_netlink_msg: no ACTION in payload
found, skip event 'umount'
Jan 23 19:18:00 linux kernel: SCSI subsystem initialized
Jan 23 19:18:00 linux kernel: st: Version 20050501, fixed bufsize 32768, s/g
segs 256
Jan 23 18:18:33 linux kernel: eth0: Media Link On 100mbps full-duplex
Jan 23 18:18:41 linux kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
Jan 23 18:18:41 linux udevd[2211]: get_netlink_msg: no ACTION in payload
found, skip event 'mount'
Jan 23 18:18:41 linux kernel: ISO 9660 Extensions: RRIP_1991A
Jan 23 18:18:41 linux kernel: eth0: no IPv6 routers present
Jan 23 19:23:39 linux udevd[2211]: get_netlink_msg: no ACTION in payload
found, skip event 'umount'
Jan 23 18:23:40 linux kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
Jan 23 19:23:40 linux udevd[2211]: get_netlink_msg: no ACTION in payload
found, skip event 'mount'
Jan 23 18:23:40 linux kernel: ISO 9660 Extensions: RRIP_1991A
Jan 23 19:23:40 linux udevd[2211]: get_netlink_msg: no ACTION in payload
found, skip event 'umount'
Jan 23 19:23:43 linux hal-subfs-mount[6276]: By hald-subfs-mount created
link /media/SU1000_002 got removed.
Jan 23 18:24:12 linux kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
Jan 23 19:24:12 linux udevd[2211]: get_netlink_msg: no ACTION in payload
found, skip event 'mount'
Jan 23 18:24:12 linux kernel: ISO 9660 Extensions: RRIP_1991A
Jan 23 19:24:57 linux shadow[6396]: group already exists - group=ntadmin,
by=0
Jan 23 19:26:39 linux udevd[2211]: get_netlink_msg: no ACTION in payload
found, skip event 'umount'
Jan 23 18:26:39 linux kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
Jan 23 19:26:39 linux udevd[2211]: get_netlink_msg: no ACTION in payload
found, skip event 'mount'
Jan 23 18:26:39 linux kernel: ISO 9660 Extensions: RRIP_1991A
Jan 23 19:26:39 linux udevd[2211]: get_netlink_msg: no ACTION in payload
found, skip event 'umount'
Jan 23 18:27:09 linux kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
Jan 23 19:27:09 linux udevd[2211]: get_netlink_msg: no ACTION in payload
found, skip event 'mount'
Jan 23 18:27:09 linux kernel: ISO 9660 Extensions: RRIP_1991A
Jan 23 19:28:03 linux udevd[2211]: get_netlink_msg: no ACTION in payload
found, skip event 'umount'
Jan 23 18:28:03 linux kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
Jan 23 19:28:03 linux udevd[2211]: get_netlink_msg: no ACTION in payload
found, skip event 'mount'
Jan 23 18:28:03 linux kernel: ISO 9660 Extensions: RRIP_1991A
Jan 23 19:28:03 linux udevd[2211]: get_netlink_msg: no ACTION in payload
found, skip event 'umount'
Jan 23 18:28:34 linux kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
Jan 23 19:28:34 linux udevd[2211]: get_netlink_msg: no ACTION in payload
found, skip event 'mount'
Jan 23 18:28:34 linux kernel: ISO 9660 Extensions: RRIP_1991A
Jan 23 19:28:36 linux udevd[2211]: get_netlink_msg: no ACTION in payload
found, skip event 'umount'
Jan 23 18:28:54 linux kernel: NET: Registered protocol family 17
Jan 23 19:30:07 linux su: (to root) root on none
Jan 23 18:30:10 linux kernel: ip6_tables: (C) 2000-2002 Netfilter core team
Jan 23 19:30:10 linux SuSEfirewall2: Warning: ip6tables does not support
state matching. Extended IPv6 support disabled.
Jan 23 18:30:10 linux kernel: ip_tables: (C) 2000-2002 Netfilter core team
Jan 23 18:30:10 linux kernel: ip_conntrack version 2.1 (8189 buckets, 65512
max) - 248 bytes per conntrack
Jan 23 19:30:10 linux SuSEfirewall2: batch committing...
Jan 23 19:30:11 linux SuSEfirewall2: Firewall rules set to CLOSE.
Jan 23 19:30:11 linux SuSEfirewall2: Warning: ip6tables does not support
state matching. Extended IPv6 support disabled.
Jan 23 19:30:11 linux SuSEfirewall2: Setting up rules from
/etc/sysconfig/SuSEfirewall2 ...
Jan 23 19:30:11 linux SuSEfirewall2: Warning: no interface active
Jan 23 19:30:11 linux SuSEfirewall2: batch committing...
Jan 23 19:30:11 linux SuSEfirewall2: Firewall rules successfully set
Jan 23 19:30:13 linux SuSEfirewall2: Warning: ip6tables does not support
state matching. Extended IPv6 support disabled.
Jan 23 19:30:13 linux SuSEfirewall2: batch committing...
Jan 23 19:30:13 linux SuSEfirewall2: Firewall rules set to CLOSE.
Jan 23 19:30:13 linux SuSEfirewall2: Warning: ip6tables does not support
state matching. Extended IPv6 support disabled.
Jan 23 19:30:13 linux SuSEfirewall2: Setting up rules from
/etc/sysconfig/SuSEfirewall2 ...
Jan 23 19:30:13 linux SuSEfirewall2: Warning: no interface active
Jan 23 19:30:13 linux SuSEfirewall2: batch committing...
Jan 23 19:30:13 linux SuSEfirewall2: Firewall rules successfully set
Jan 23 19:30:14 linux SuSEfirewall2: Warning: ip6tables does not support
state matching. Extended IPv6 support disabled.
Jan 23 19:30:14 linux SuSEfirewall2: batch committing...
Jan 23 19:30:14 linux SuSEfirewall2: Firewall rules set to CLOSE.
Jan 23 19:30:14 linux SuSEfirewall2: Warning: ip6tables does not support
state matching. Extended IPv6 support disabled.
Jan 23 19:30:14 linux SuSEfirewall2: Setting up rules from
/etc/sysconfig/SuSEfirewall2 ...
Jan 23 19:30:14 linux SuSEfirewall2: batch committing...
Jan 23 19:30:14 linux SuSEfirewall2: Firewall rules successfully set
Jan 23 18:30:15 linux kernel: eth0: Media Link On 100mbps full-duplex
Jan 23 19:30:18 linux logger: BEGIN OF YAST2 INTERNET TEST
Jan 23 18:30:23 linux kernel: eth0: no IPv6 routers present
Jan 23 18:30:52 linux kernel: BIOS EDD facility v0.16 2004-Jun-25, 1 devices
found
Jan 23 19:31:00 linux logger: END OF YAST2 INTERNET TEST
Jan 23 19:47:02 linux modprobe: FATAL: Error inserting asus_acpi
(/lib/modules/2.6.13-15-smp/kernel/drivers/acpi/asus_acpi.ko): No such
device
Jan 23 18:47:02 linux kernel: ibm_acpi: ec object not found
Jan 23 19:47:02 linux modprobe: FATAL: Error inserting ibm_acpi
(/lib/modules/2.6.13-15-smp/kernel/drivers/acpi/ibm_acpi.ko): No such device
Jan 23 19:47:02 linux modprobe: FATAL: Error inserting toshiba_acpi
(/lib/modules/2.6.13-15-smp/kernel/drivers/acpi/toshiba_acpi.ko): No such
device
Jan 23 18:47:02 linux kernel: pcc_acpi: module not supported by Novell,
setting U taint flag.
Jan 23 19:47:10 linux shadow[9673]: group already exists - group=haldaemon,
by=0
Jan 23 19:47:10 linux useradd[9674]: account already exists -
account=haldaemon, by=0
Jan 23 19:47:14 linux hal-subfs-mount[9720]: Device: /dev/fd0 already
mounted, exit now!
Jan 23 19:47:18 linux hal-subfs-mount[9723]: SYMLINKS::
disk/by-id/ata-HL-DT-ST_DVDRAM_GSA-4167B_BB2B211389DA
disk/by-path/pci-0000:00:02.5-ide-0:1 dvdram cdrom dvd cdrecorder
Jan 23 19:47:18 linux hal-subfs-mount[9723]: MOUNT_POINT:: /media/dvdram
Jan 23 19:47:18 linux hal-subfs-mount[9723]: MOUNTPOINT:: /media/dvdram
Jan 23 19:47:18 linux hal-subfs-mount[9723]: Collected mount options and
Called(0) /bin/mount -t subfs -o
fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 /dev/hdb
"/media/dvdram"
Jan 23 18:47:18 linux kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
Jan 23 19:47:18 linux udevd[2211]: get_netlink_msg: no ACTION in payload
found, skip event 'mount'
Jan 23 18:47:18 linux kernel: ISO 9660 Extensions: RRIP_1991A
Jan 23 19:47:21 linux udevd[2211]: get_netlink_msg: no ACTION in payload
found, skip event 'umount'
Jan 23 18:47:31 linux kernel: end_request: I/O error, dev fd0, sector 0
Jan 23 19:47:35 linux shadow[9807]: group already exists - group=ntadmin,
by=0
Jan 23 19:47:47 linux syslog-ng[4737]: SIGHUP received, restarting syslog-ng
Jan 23 18:47:47 linux kernel: Kernel logging (proc) stopped.
Jan 23 18:47:47 linux kernel: Kernel log daemon terminating.
Jan 23 19:47:49 linux-af syslog-ng[10020]: syslog-ng version 1.6.8 starting
Jan 23 19:47:54 linux-af kernel: klogd 1.4.1, log source = /proc/kmsg
started.
Jan 23 19:48:00 linux-af shadow[10123]: group already exists -
group=ntadmin, by=0
Jan 23 19:48:35 linux-af shadow[10250]: group already exists - group=sshd,
by=0
Jan 23 19:48:35 linux-af useradd[10251]: account already exists -
account=sshd, by=0
Jan 23 19:49:33 linux-af syslog-ng[10020]: SIGHUP received, restarting
syslog-ng
Jan 23 19:49:33 linux-af init: Re-reading inittab
Jan 23 19:49:35 linux-af syslog-ng[10020]: new configuration initialized
Jan 23 19:49:45 linux-af syslog-ng[10020]: Changing permissions on special
file /dev/xconsole
Jan 23 19:49:45 linux-af syslog-ng[10020]: Changing permissions on special
file /dev/tty10
Jan 23 19:49:45 linux-af ifstatus: Interface /NSC is not available
Jan 23 19:50:19 linux-af syslog-ng[10020]: SIGHUP received, restarting
syslog-ng
Jan 23 19:50:19 linux-af init: Re-reading inittab
Jan 23 19:50:21 linux-af syslog-ng[10020]: new configuration initialized
Jan 23 19:50:34 linux-af hp: unable to open /var/run/hpiod.port: No such
file or directory: prnt/hpijs/hplip_api.c 75
Jan 23 19:50:34 linux-af hp: unable to connect hpiod socket 50000:
Connection refused: prnt/hpijs/hplip_api.c 693
Jan 23 19:50:34 linux-af hp: unable to send ProbeDevices: Broken pipe
Jan 23 19:50:34 linux-af kernel: pnp: Device 00:07 disabled.
Jan 23 19:50:34 linux-af kernel: klogd 1.4.1, ---------- state
change ----------
Jan 23 19:50:34 linux-af kernel: pnp: Device 00:07 activated.
Jan 23 19:50:34 linux-af kernel: parport: PnPBIOS parport detected.
Jan 23 19:50:34 linux-af kernel: pnp: Device 00:07 disabled.
Jan 23 19:50:34 linux-af kernel: lp: driver loaded but no devices found
Jan 23 19:50:34 linux-af kernel: pnp: Device 00:07 activated.
Jan 23 19:50:34 linux-af kernel: parport: PnPBIOS parport detected.
Jan 23 19:50:34 linux-af kernel: pnp: Device 00:07 disabled.
Jan 23 19:50:34 linux-af kernel: lp: driver loaded but no devices found
Jan 23 19:50:53 linux-af syslog-ng[10020]: Changing permissions on special
file /dev/xconsole
Jan 23 19:50:53 linux-af syslog-ng[10020]: Changing permissions on special
file /dev/tty10
Jan 23 19:50:53 linux-af kernel: ACPI-0212: *** Warning: Device is not
power manageable
Jan 23 19:50:53 linux-af kernel: ACPI: PCI Interrupt 0000:00:02.7[C] -> GSI
18 (level, low) -> IRQ 217
Jan 23 19:50:53 linux-af kernel: intel8x0_measure_ac97_clock: measured 56505
usecs
Jan 23 19:50:53 linux-af kernel: intel8x0: clocking to 48000
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af y2base: resmgr: unable to connect to resmgrd: No
existe el fichero o el directorio
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:54 linux-af alsactl: resmgr: unable to connect to resmgrd: No
such file or directory
Jan 23 19:50:55 linux-af kernel: end_request: I/O error, dev fd0, sector 0
Jan 23 19:50:55 linux-af kernel: end_request: I/O error, dev fd0, sector 0
Jan 23 19:51:02 linux-af init: Entering runlevel: 5
Jan 23 19:51:02 linux-af kernel: bootsplash: status on console 0 changed to
on
Jan 23 19:51:02 linux-af kernel: Kernel logging (proc) stopped.
Jan 23 19:51:02 linux-af kernel: Kernel log daemon terminating.
Jan 23 19:51:03 linux-af syslog-ng[10020]: syslog-ng version 1.6.8 going
down
Jan 23 19:51:03 linux-af syslog-ng[13670]: syslog-ng version 1.6.8 starting
Jan 23 19:51:03 linux-af syslog-ng[13670]: Changing permissions on special
file /dev/xconsole
Jan 23 19:51:03 linux-af syslog-ng[13670]: Changing permissions on special
file /dev/tty10
Jan 23 19:51:03 linux-af mDNSResponder (Engineering Build) (Sep 9 2005
15:59:08) [13661]: starting
Jan 23 19:51:04 linux-af hp: unable to open /var/run/hpiod.port: No such
file or directory: prnt/hpijs/hplip_api.c 75
Jan 23 19:51:06 linux-af /usr/sbin/cron[13983]: (CRON) STARTUP (V5.0)
Jan 23 19:51:07 linux-af sshd[14004]: Server listening on :: port 22.
Jan 23 19:51:07 linux-af rcpowersaved: CPU frequency scaling is not
supported by your processor.
Jan 23 19:51:07 linux-af rcpowersaved: enter 'CPUFREQD_MODULE=off' in
/etc/sysconfig/powersave/cpufreq to avoid this warning.
Jan 23 19:51:07 linux-af rcpowersaved: Cannot load cpufreq governors - No
cpufreq driver available
Jan 23 19:51:07 linux-af [powersave]: ERROR (CPUFreq_Userspace:42) Could not
set userspace governor, seems as if the cpufreq_userspace module is not
loaded.
Jan 23 19:51:07 linux-af [powersave]: ERROR (read_line:43) Could not open
file for reading:
'/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies'
Jan 23 19:51:07 linux-af [powersave]: ERROR (read_line:43) Could not open
file for reading: '/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq'
Jan 23 19:51:07 linux-af [powersave]: ERROR (read_value:82) Could not read
value in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq: error:
No such file or directory!
Jan 23 19:51:07 linux-af [powersave]: ERROR (read_line:43) Could not open
file for reading: '/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq'
Jan 23 19:51:07 linux-af [powersave]: ERROR (read_value:82) Could not read
value in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: error:
No such file or directory!
Jan 23 19:51:07 linux-af [powersave]: WARNING (getMinMaxSpeeds:349)
Speedstepping not supported! Was the correct cpufreq module loaded?
Jan 23 19:51:07 linux-af [powersave]: WARNING (initFreqsViaTesting:377)
Could not read min and max speed
Jan 23 19:51:07 linux-af [powersave]: ERROR (PM_Interface:231) Cannot create
cpufreq objects
Jan 23 19:51:07 linux-af SuSEfirewall2: Warning: ip6tables does not support
state matching. Extended IPv6 support disabled.
Jan 23 19:51:07 linux-af SuSEfirewall2: Setting up rules from
/etc/sysconfig/SuSEfirewall2 ...
Jan 23 19:51:08 linux-af kernel: klogd 1.4.1, log source = /proc/kmsg
started.
Jan 23 19:51:08 linux-af kernel: IA-32 Microcode Update Driver: v1.14