CentOS 5.2 - Suspend/resume on Dell Latitude D620

Issues related to hardware problems

CentOS 5.2 - Suspend/resume on Dell Latitude D620

Postby marek158 » 2008/09/22 13:02:13

Hello,

I was trying to suspend my laptop using gnome-power-manager (similar results when using KDE's KLaptop). It seems that the machine has suspended OK, but on resume I got only a broken display (an unable to switch into console) so I had to hard reboot. This is the relevant part of /var/log/messages:

Code: Select all
Sep 22 14:10:36 latituded620 gnome-power-manager: (marek) Suspending computer because user clicked suspend from tray menu
Sep 22 14:10:36 latituded620 NetworkManager: <information>      Going to sleep.
Sep 22 14:10:36 latituded620 avahi-daemon[10067]: Interface eth0.IPv6 no longer relevant for mDNS.
Sep 22 14:10:36 latituded620 avahi-daemon[10067]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::215:c5ff:
fe59:e9fd.
Sep 22 14:10:36 latituded620 avahi-daemon[10067]: Interface eth0.IPv4 no longer relevant for mDNS.
Sep 22 14:10:36 latituded620 avahi-daemon[10067]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.0.94.6.
Sep 22 14:10:36 latituded620 avahi-daemon[10067]: Withdrawing address record for fe80::215:c5ff:fe59:e9fd on eth0.
Sep 22 14:10:36 latituded620 avahi-daemon[10067]: Withdrawing address record for 10.0.94.6 on eth0.
Sep 22 14:10:36 latituded620 dhclient: DHCPRELEASE on eth0 to 10.0.2.12 port 67
Sep 22 14:10:36 latituded620 dhclient: send_packet: Network is unreachable
Sep 22 14:10:36 latituded620 dhclient: send_packet: please consult README file regarding broadcast address.
Sep 22 14:10:38 latituded620 kernel: ACPI: PCI interrupt for device 0000:03:00.0 disabled
Sep 22 14:10:39 latituded620 kernel: Disabling non-boot CPUs ...
Sep 22 14:10:39 latituded620 kernel: Breaking affinity for irq 1
Sep 22 14:10:39 latituded620 kernel: Breaking affinity for irq 14
Sep 22 14:10:39 latituded620 kernel: Breaking affinity for irq 74
Sep 22 14:10:39 latituded620 kernel: CPU 1 is now offline
Sep 22 14:10:39 latituded620 kernel: SMP alternatives: switching to UP code
Sep 22 14:10:55 latituded620 kernel: CPU1 is down
Sep 22 14:10:55 latituded620 kernel: Stopping tasks: =============================================================================
===================================|
Sep 22 14:10:55 latituded620 kernel:  usbdev2.4_ep81: PM: suspend 0->2, parent 2-2.3.2:1.0 already 1
Sep 22 14:10:55 latituded620 kernel:  usbdev2.4_ep82: PM: suspend 0->2, parent 2-2.3.2:1.0 already 1
Sep 22 14:10:55 latituded620 kernel:  usbdev2.4_ep03: PM: suspend 0->2, parent 2-2.3.2:1.0 already 1
Sep 22 14:10:55 latituded620 kernel: pnp: Device 00:0c disabled.
Sep 22 14:10:55 latituded620 kernel: ACPI: PCI interrupt for device 0000:05:01.0 disabled
Sep 22 14:10:55 latituded620 kernel: NVRM: RmPowerManagement: 4
Sep 22 14:10:55 latituded620 kernel: ACPI: PCI interrupt for device 0000:00:1f.2 disabled
Sep 22 14:10:55 latituded620 kernel: ACPI: PCI interrupt for device 0000:00:1d.7 disabled
Sep 22 14:10:55 latituded620 kernel: ACPI: PCI interrupt for device 0000:00:1d.3 disabled
Sep 22 14:10:55 latituded620 kernel: ACPI: PCI interrupt for device 0000:00:1d.2 disabled
Sep 22 14:10:55 latituded620 kernel: ACPI: PCI interrupt for device 0000:00:1d.1 disabled
Sep 22 14:10:56 latituded620 kernel: ACPI: PCI interrupt for device 0000:00:1d.0 disabled
Sep 22 14:10:57 latituded620 kernel: ACPI: PCI interrupt for device 0000:00:1b.0 disabled
Sep 22 14:10:57 latituded620 kernel: Intel machine check architecture supported.
Sep 22 14:10:57 latituded620 kernel: Intel machine check reporting enabled on CPU#0.
Sep 22 14:10:57 latituded620 kernel: PCI: Enabling device 0000:00:1b.0 (0100 -> 0102)
Sep 22 14:10:57 latituded620 kernel: ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 21 (level, low) -> IRQ 177
Sep 22 14:10:57 latituded620 kernel: ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 20 (level, low) -> IRQ 201
Sep 22 14:10:57 latituded620 kernel: usb usb2: root hub lost power or was reset
Sep 22 14:10:57 latituded620 kernel: PCI: Enabling device 0000:00:1d.1 (0000 -> 0001)
Sep 22 14:10:57 latituded620 kernel: ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 21 (level, low) -> IRQ 177
Sep 22 14:10:57 latituded620 kernel: usb usb3: root hub lost power or was reset
Sep 22 14:10:57 latituded620 kernel: PCI: Enabling device 0000:00:1d.2 (0000 -> 0001)
Sep 22 14:10:57 latituded620 kernel: ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 22 (level, low) -> IRQ 209
Sep 22 14:10:57 latituded620 kernel: usb usb4: root hub lost power or was reset
Sep 22 14:10:57 latituded620 kernel: PCI: Enabling device 0000:00:1d.3 (0000 -> 0001)
Sep 22 14:10:57 latituded620 kernel: ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 23 (level, low) -> IRQ 217
Sep 22 14:10:57 latituded620 kernel: usb usb5: root hub lost power or was reset
Sep 22 14:10:57 latituded620 kernel: ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 20 (level, low) -> IRQ 201
Sep 22 14:10:57 latituded620 kernel: usb usb1: root hub lost power or was reset
Sep 22 14:10:57 latituded620 kernel: ehci_hcd 0000:00:1d.7: debug port 1
Sep 22 14:10:57 latituded620 kernel: ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
Sep 22 14:10:57 latituded620 kernel: ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 17 (level, low) -> IRQ 185
Sep 22 14:10:57 latituded620 kernel: NVRM: RmPowerManagement: 5
Sep 22 14:10:57 latituded620 kernel: ACPI: PCI Interrupt 0000:05:01.0[A] -> GSI 18 (level, low) -> IRQ 193
Sep 22 14:10:57 latituded620 kernel: Yenta O2: res at 0x94/0xD4: 00/ea
Sep 22 14:10:57 latituded620 kernel: Yenta O2: enabling read prefetch/write burst
Sep 22 14:10:57 latituded620 kernel: ata1.00: configured for UDMA/100
Sep 22 14:10:57 latituded620 kernel: SCSI device sda: 78140160 512-byte hdwr sectors (40008 MB)
Sep 22 14:10:57 latituded620 kernel: sda: Write Protect is off
Sep 22 14:10:57 latituded620 kernel: SCSI device sda: drive cache: write back
Sep 22 14:10:57 latituded620 kernel: pnp: Device 00:04 does not support activation.
Sep 22 14:10:57 latituded620 kernel: pnp: Device 00:05 does not support activation.
Sep 22 14:10:57 latituded620 kernel: pnp: Device 00:0c activated.
Sep 22 14:10:57 latituded620 kernel:  usbdev2.4_ep03: PM: resume from 0, parent 2-2.3.2:1.0 still 1
Sep 22 14:10:57 latituded620 kernel:  usbdev2.4_ep82: PM: resume from 0, parent 2-2.3.2:1.0 still 1
Sep 22 14:10:57 latituded620 kernel:  usbdev2.4_ep81: PM: resume from 0, parent 2-2.3.2:1.0 still 1
Sep 22 14:10:57 latituded620 kernel: Restarting tasks... done
Sep 22 14:10:57 latituded620 kernel: Enabling non-boot CPUs ...
Sep 22 14:10:57 latituded620 kernel: usb 2-2: USB disconnect, address 2
Sep 22 14:10:57 latituded620 kernel: usb 2-2.3: USB disconnect, address 3
Sep 22 14:10:57 latituded620 kernel: usb 2-2.3.2: USB disconnect, address 4
Sep 22 14:10:57 latituded620 kernel: SMP alternatives: switching to SMP code
Sep 22 14:10:57 latituded620 kernel: Booting processor 1/1 eip 3000
Sep 22 14:10:57 latituded620 kernel: CPU 1 irqstacks, hard=c074d000 soft=c072d000
Sep 22 14:10:57 latituded620 kernel: Initializing CPU#1
Sep 22 14:10:57 latituded620 kernel: Calibrating delay using timer specific routine.. 3328.99 BogoMIPS (lpj=1664495)
Sep 22 14:10:57 latituded620 kernel: monitor/mwait feature present.
Sep 22 14:10:57 latituded620 kernel: CPU: L1 I cache: 32K, L1 D cache: 32K
Sep 22 14:10:57 latituded620 kernel: CPU: L2 cache: 2048K
Sep 22 14:10:57 latituded620 kernel: CPU: Physical Processor ID: 0
Sep 22 14:10:57 latituded620 kernel: CPU: Processor Core ID: 1
Sep 22 14:10:57 latituded620 kernel: Intel machine check architecture supported.
Sep 22 14:10:57 latituded620 kernel: Intel machine check reporting enabled on CPU#1.
Sep 22 14:10:57 latituded620 kernel: CPU1: Intel Genuine Intel(R) CPU           T2300  @ 1.66GHz stepping 08
Sep 22 14:10:57 latituded620 kernel: CPU1 is up
Sep 22 14:10:57 latituded620 kernel: usb 4-2: USB disconnect, address 2
Sep 22 14:10:58 latituded620 kernel: usb 2-2: new full speed USB device using uhci_hcd and address 5
Sep 22 14:10:58 latituded620 kernel: usb 2-2: configuration #1 chosen from 1 choice
Sep 22 14:10:58 latituded620 kernel: hub 2-2:1.0: USB hub found
Sep 22 14:10:58 latituded620 kernel: hub 2-2:1.0: 4 ports detected
Sep 22 14:10:58 latituded620 kernel: usb 4-2: new low speed USB device using uhci_hcd and address 3
Sep 22 14:10:59 latituded620 kernel: usb 4-2: configuration #1 chosen from 1 choice
Sep 22 14:10:59 latituded620 kernel: input: Logitech USB-PS/2 Optical Mouse as /class/input/input8
Sep 22 14:10:59 latituded620 kernel: input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.2-2
Sep 22 14:10:59 latituded620 kernel: usb 2-2.3: new full speed USB device using uhci_hcd and address 6
Sep 22 14:10:59 latituded620 kernel: usb 2-2.3: configuration #1 chosen from 1 choice
Sep 22 14:10:59 latituded620 kernel: hub 2-2.3:1.0: USB hub found
Sep 22 14:10:59 latituded620 kernel: hub 2-2.3:1.0: 3 ports detected
Sep 22 14:10:59 latituded620 kernel: usb 2-2.3.2: new full speed USB device using uhci_hcd and address 7
Sep 22 14:10:59 latituded620 kernel: usb 2-2.3.2: configuration #1 chosen from 1 choice
Sep 22 14:11:01 latituded620 kernel: ieee80211: 802.11 data/management/control stack, git-1.1.13
Sep 22 14:11:01 latituded620 kernel: ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
Sep 22 14:11:01 latituded620 kernel: ipw3945: Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.2.1dm
Sep 22 14:11:01 latituded620 kernel: ipw3945: Copyright(c) 2003-2006 Intel Corporation
Sep 22 14:11:01 latituded620 kernel: PCI: Enabling device 0000:03:00.0 (0100 -> 0102)
Sep 22 14:11:01 latituded620 kernel: ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 185
Sep 22 14:11:01 latituded620 kernel: ipw3945: Detected Intel PRO/Wireless 3945ABG Network Connection
Sep 22 14:11:01 latituded620 NetworkManager: <information>      Waking up from sleep.
Sep 22 14:11:01 latituded620 NetworkManager: <information>      Deactivating device eth0.
Sep 22 14:11:01 latituded620 NetworkManager: <information>      eth0: Device is fully-supported using driver 'tg3'.
Sep 22 14:11:01 latituded620 gnome-power-manager: (marek) Resuming computer
Sep 22 14:11:01 latituded620 NetworkManager: <information>      nm_device_init(): waiting for device's worker thread to start
Sep 22 14:11:01 latituded620 NetworkManager: <information>      nm_device_init(): device's worker thread started, continuing.
Sep 22 14:11:01 latituded620 NetworkManager: <information>      Now managing wired Ethernet (802.3) device 'eth0'.
Sep 22 14:11:01 latituded620 NetworkManager: <information>      Deactivating device eth0.
Sep 22 14:11:01 latituded620 kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 22 14:11:02 latituded620 kernel: ipw3945: Radio Frequency Kill Switch is On:
Sep 22 14:11:02 latituded620 kernel: Kill switch must be turned off for wireless networking to work.
Sep 22 14:11:03 latituded620 kernel: tg3: eth0: Link is up at 10 Mbps, half duplex.
Sep 22 14:11:03 latituded620 kernel: tg3: eth0: Flow control is off for TX and off for RX.
Sep 22 14:11:03 latituded620 kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sep 22 14:11:03 latituded620 NetworkManager: <information>      Will activate wired connection 'eth0' because it now has a link.
Sep 22 14:11:03 latituded620 NetworkManager: <information>      SWITCH: no current connection, found better connection 'eth0'.
Sep 22 14:11:03 latituded620 NetworkManager: <information>      Will activate connection 'eth0'.
Sep 22 14:11:03 latituded620 NetworkManager: <information>      Device eth0 activation scheduled...
Sep 22 14:11:03 latituded620 NetworkManager: <information>      Activation (eth0) started...
Sep 22 14:11:03 latituded620 NetworkManager: <information>      Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Sep 22 14:11:03 latituded620 NetworkManager: <information>      Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Sep 22 14:11:03 latituded620 NetworkManager: <information>      Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Sep 22 14:11:03 latituded620 NetworkManager: <information>      Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Sep 22 14:11:03 latituded620 NetworkManager: <information>      Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Sep 22 14:11:03 latituded620 NetworkManager: <information>      Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Sep 22 14:11:03 latituded620 NetworkManager: <information>      Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Sep 22 14:11:03 latituded620 NetworkManager: <information>      Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Sep 22 14:11:03 latituded620 NetworkManager: <information>      Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Sep 22 14:11:04 latituded620 NetworkManager: <information>      Activation (eth0) Beginning DHCP transaction.
Sep 22 14:11:04 latituded620 NetworkManager: <information>      Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Sep 22 14:11:04 latituded620 NetworkManager: <information>      DHCP daemon state is now 12 (successfully started) for interface e
th0
Sep 22 14:11:04 latituded620 NetworkManager: <information>      DHCP daemon state is now 1 (starting) for interface eth0
Sep 22 14:11:04 latituded620 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Sep 22 14:11:04 latituded620 dhclient: DHCPOFFER from 10.0.94.254
Sep 22 14:11:04 latituded620 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Sep 22 14:11:04 latituded620 dhclient: DHCPACK from 10.0.94.254
Sep 22 14:11:04 latituded620 NetworkManager: <information>      DHCP daemon state is now 2 (bound) for interface eth0
Sep 22 14:11:04 latituded620 NetworkManager: <information>      Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
Sep 22 14:11:04 latituded620 NetworkManager: <information>      Activation (eth0) Stage 4 of 5 (IP Configure Get) started...
Sep 22 14:11:04 latituded620 dhclient: bound to 10.0.94.6 -- renewal in 262231 seconds.
Sep 22 14:11:04 latituded620 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus
.get.host_name
Sep 22 14:11:04 latituded620 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus
.get.nis_domain
Sep 22 14:11:04 latituded620 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus
.get.nis_servers
Sep 22 14:11:04 latituded620 NetworkManager: <information>      Retrieved the following IP4 configuration from the DHCP daemon:
Sep 22 14:11:04 latituded620 NetworkManager: <information>        address 10.0.94.6
Sep 22 14:11:04 latituded620 NetworkManager: <information>        netmask 255.255.255.0
Sep 22 14:11:04 latituded620 NetworkManager: <information>        broadcast 10.0.94.255
Sep 22 14:11:04 latituded620 NetworkManager: <information>        gateway 10.0.94.254
Sep 22 14:11:04 latituded620 NetworkManager: <information>        nameserver 10.0.2.32
Sep 22 14:11:04 latituded620 NetworkManager: <information>        nameserver 10.0.2.33
Sep 22 14:11:04 latituded620 NetworkManager: <information>        nameserver 10.0.2.43
Sep 22 14:11:04 latituded620 NetworkManager: <information>      Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Sep 22 14:11:04 latituded620 NetworkManager: <information>      Activation (eth0) Stage 4 of 5 (IP Configure Get) complete.
Sep 22 14:11:04 latituded620 NetworkManager: <information>      Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Sep 22 14:11:04 latituded620 avahi-daemon[10067]: New relevant interface eth0.IPv4 for mDNS.
Sep 22 14:11:04 latituded620 avahi-daemon[10067]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.0.94.6.
Sep 22 14:11:04 latituded620 avahi-daemon[10067]: Registering new address record for 10.0.94.6 on eth0.
Sep 22 14:11:05 latituded620 NetworkManager: <information>      Activation (eth0) successful, device activated.
Sep 22 14:11:05 latituded620 NetworkManager: <information>      Activation (eth0) Finish handler scheduled.
Sep 22 14:11:05 latituded620 NetworkManager: <information>      Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Sep 22 14:11:06 latituded620 avahi-daemon[10067]: New relevant interface eth0.IPv6 for mDNS.
Sep 22 14:11:06 latituded620 avahi-daemon[10067]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::215:c5ff:
fe59:e9fd.
Sep 22 14:11:06 latituded620 avahi-daemon[10067]: Registering new address record for fe80::215:c5ff:fe59:e9fd on eth0.
Sep 22 14:11:10 latituded620 kernel: NVRM: os_map_kernel_space: can't map 0xf0100000, invalid context!
Sep 22 14:11:10 latituded620 kernel: NVRM: Xid (0001:00): 8, Channel 00000020
Sep 22 14:11:26 latituded620 last message repeated 2 times
Sep 22 14:11:30 latituded620 kernel: NVRM: Xid (0001:00): 16, Head 00000000 Count 00004e9d


Some suspicious messages I saw there:
Code: Select all
 
Sep 22 14:10:57 latituded620 kernel: pnp: Device 00:04 does not support activation.
Sep 22 14:10:57 latituded620 kernel: pnp: Device 00:05 does not support activation.
Sep 22 14:10:57 latituded620 kernel: pnp: Device 00:0c activated.


Code: Select all
Sep 22 14:11:06 latituded620 avahi-daemon[10067]: Registering new address record for fe80::215:c5ff:fe59:e9fd on eth0.
Sep 22 14:11:10 latituded620 kernel: NVRM: os_map_kernel_space: can't map 0xf0100000, invalid context!
Sep 22 14:11:10 latituded620 kernel: NVRM: Xid (0001:00): 8, Channel 00000020
Sep 22 14:11:26 latituded620 last message repeated 2 times
Sep 22 14:11:30 latituded620 kernel: NVRM: Xid (0001:00): 16, Head 00000000 Count 00004e9d


More info:
Code: Select all
$ uname -r
2.6.18-92.1.10.el5

# lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express PCI Express Root Port (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 01)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
01:00.0 VGA compatible controller: nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300] (rev a1)
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
04:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express (rev 02)
05:01.0 CardBus bridge: O2 Micro, Inc. OZ601/6912/711E0 CardBus/SmartCardBus Controller (rev 40)

# grep kernel /boot/grub/menu.lst
kernel /vmlinuz-2.6.18-92.1.10.el5 ro root=LABEL=/ pci=assign-busses pci=routeirq


The result of resume is the same if I remove the two "pci" options in grub's menu.lst.


All suggestions will be appreciated.
m
marek158
 
Posts: 114
Joined: 2008/08/12 11:32:43

Re: CentOS 5.2 - Suspend/resume on Dell Latitude D620

Postby thenga » 2008/10/30 20:58:20

it seems that no one knows about how to solve the black screen problem when waking up after a suspend. !
thenga
 
Posts: 15
Joined: 2008/10/12 13:39:58

Re: CentOS 5.2 - Suspend/resume on Dell Latitude D620

Postby thenga » 2008/10/31 06:04:42

Oops...replied too quickly..

it works for me now. i386, nvidia 8600 GTS home assembled system.

I do not know how it started working though. Did not do anything special except ran pm-suspend once.
Now the display come back properly.
thenga
 
Posts: 15
Joined: 2008/10/12 13:39:58


Return to CentOS 5 - Hardware Support

Who is online

Users browsing this forum: No registered users and 1 guest