upgraded to jessie, resume from suspend broken on desktop
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
upgraded to jessie, resume from suspend broken on desktop
Yesterday I upgraded a desktop from wheezy to jessie (32-bit/386 installation).
sources.list:
Code:
deb http://http.us.debian.org/debian/ jessie contrib non-free main
deb http://security.debian.org/ jessie/updates main contrib non-free
deb http://http.us.debian.org/debian/ jessie-updates contrib non-free main
deb ftp://ftp.deb-multimedia.org jessie main non-free
I used apt-get -d dist-upgrade and then completed the process with apt-get dist-upgrade.
After I resume from suspend now, I can hear the desktop waking up, but the monitor never comes back on.
I tried "blindly" switching to a terminal (ctrl-alt-f4) and pressing ctrl-alt-del but the system didn't reboot. I did a cold shut-down. I replicated the problem by suspending from the lightdm log in screen (after logging out of xfce) and got the same results.
In the earlier days of 3.1x, my Ivy Bridge chip/set had issues with suspend/resume that later went away. Until then, I'd have to blindly shut down (I'd switch to a VT, CTRL+DEL+ALT didn't work; I'd blindly log in, blindly issue a halt command).
If all else fails, give us some output from lspci to work with, so we know a little more about your hardware. A quick search just gave me an Amazon and eBay link, a few tech support requests, yet no real info on the hardware other than CPU speed.
Linux gateway 3.16-3-686-pae #1 SMP Debian 3.16.5-1 (2014-10-10) i686 GNU/Linux
I don't see there's a newer kernel available. I booted the 486 kernel but that didn't make any difference.
This is on my mom's computer and pretty soon won't be around to work on it anymore. I did figure out a workaround. I switch to a terminal, log in as root, type in pm-suspend. Suspend works, resume works. I can switch back to the GUI by Ctrl-Alt-F7.
I've also found a way that I can test the suspend without doing a cold shut down if resume fails. I switch to a terminal, log in as root, enter "sleep 60s ; reboot". When I resume and get nothing, the system will reboot automatically.
Hope that helps someone.
Anyway, thanks for your response. Here's my lscpi output, and cpuinfo at the bottom:
Code:
root@gateway:~# lspci -v
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
Subsystem: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface
Flags: bus master, fast devsel, latency 0
Memory at f8000000 (32-bit, prefetchable) [size=64M]
Capabilities: [e4] Vendor Specific Information: Len=06 <?>
Capabilities: [a0] AGP version 3.0
Kernel driver in use: agpgart-intel
00:01.0 PCI bridge: Intel Corporation 82865G/PE/P AGP Bridge (rev 02) (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, fast devsel, latency 32
Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
Memory behind bridge: fca00000-feafffff
Prefetchable memory behind bridge: e4800000-f47fffff
00:06.0 System peripheral: Intel Corporation 82865G/PE/P Processor to I/O Memory Interface (rev 02)
Flags: fast devsel
Memory at fecf0000 (32-bit, non-prefetchable) [size=4K]
00:1d.0 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02) (prog-if 00 [UHCI])
Subsystem: Gateway, Inc. Device 2019
Flags: bus master, medium devsel, latency 0, IRQ 16
I/O ports at c800 [size=32]
Kernel driver in use: uhci_hcd
00:1d.1 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02) (prog-if 00 [UHCI])
Subsystem: Gateway, Inc. Device 2019
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at cc00 [size=32]
Kernel driver in use: uhci_hcd
00:1d.2 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02) (prog-if 00 [UHCI])
Subsystem: Gateway, Inc. Device 2019
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at d000 [size=32]
Kernel driver in use: uhci_hcd
00:1d.3 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02) (prog-if 00 [UHCI])
Subsystem: Gateway, Inc. Device 2019
Flags: bus master, medium devsel, latency 0, IRQ 16
I/O ports at d400 [size=32]
Kernel driver in use: uhci_hcd
00:1d.7 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) (prog-if 20 [EHCI])
Subsystem: Gateway, Inc. Device 2019
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at febff400 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Kernel driver in use: ehci-pci
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
I/O behind bridge: 0000b000-0000bfff
Memory behind bridge: fc900000-fc9fffff
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02)
Flags: bus master, medium devsel, latency 0
Kernel driver in use: lpc_ich
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02) (prog-if 8a [Master SecP PriP])
Subsystem: Gateway, Inc. Device 2019
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at 01f0 [size=8]
I/O ports at 03f4
I/O ports at 0170 [size=8]
I/O ports at 0374
I/O ports at ffa0 [size=16]
Memory at 80000000 (32-bit, non-prefetchable) [size=1K]
Kernel driver in use: ata_piix
00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller (rev 02) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: Gateway, Inc. Device 2019
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 18
I/O ports at ec00 [size=8]
I/O ports at e800 [size=4]
I/O ports at e400 [size=8]
I/O ports at e000 [size=4]
I/O ports at dc00 [size=16]
Kernel driver in use: ata_piix
00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02)
Subsystem: Gateway, Inc. Device 2019
Flags: medium devsel, IRQ 17
I/O ports at d800 [size=32]
Kernel driver in use: i801_smbus
00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
Subsystem: Gateway, Inc. Device 2019
Flags: bus master, medium devsel, latency 0, IRQ 17
Memory at febffc00 (32-bit, non-prefetchable) [size=512]
Memory at febff800 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2
Kernel driver in use: snd_intel8x0
01:01.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
Subsystem: Creative Labs Device 1006
Flags: bus master, medium devsel, latency 32, IRQ 22
I/O ports at b400 [size=64]
Capabilities: [dc] Power Management version 2
Kernel driver in use: snd_emu10k1
01:01.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04) (prog-if 10 [OHCI])
Subsystem: Creative Labs SB Audigy FireWire Port
Flags: bus master, medium devsel, latency 32, IRQ 21
Memory at fc9fd800 (32-bit, non-prefetchable) [size=2K]
Memory at fc9f8000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [44] Power Management version 2
Kernel driver in use: firewire_ohci
01:02.0 Modem: Broadcom Corporation BCM4212 v.90 56k modem (prog-if 00 [Generic])
Subsystem: Broadcom Corporation Device 0002
Flags: bus master, fast devsel, latency 32, IRQ 17
Memory at fc9fe000 (32-bit, non-prefetchable) [size=4K]
I/O ports at b800 [size=16]
Capabilities: [40] Power Management version 2
Kernel driver in use: serial
01:08.0 Ethernet controller: Intel Corporation 82562EZ 10/100 Ethernet Controller (rev 02)
Subsystem: Gateway, Inc. Device 2019
Flags: bus master, medium devsel, latency 32, IRQ 20
Memory at fc9ff000 (32-bit, non-prefetchable) [size=4K]
I/O ports at bc00 [size=64]
Capabilities: [dc] Power Management version 2
Kernel driver in use: e100
02:00.0 VGA compatible controller: NVIDIA Corporation NV34 [GeForce FX 5200] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Gateway, Inc. Device 3019
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 11
Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Memory at e8000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at feae0000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Capabilities: [44] AGP version 3.0
Code:
root@gateway:~# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Pentium(R) 4 CPU 2.60GHz
stepping : 9
microcode : 0x11
cpu MHz : 2593.355
cache size : 512 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fdiv_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe pebs bts cid xtpr
bogomips : 5186.71
clflush size : 64
cache_alignment : 128
address sizes : 36 bits physical, 32 bits virtual
power management:
Ok, I see mention of an nVidia chip... are you using the proprietary drivers, or the nVidia binary blob?
Try adding nomodeset to the kernel boot line when you turn on the computer. If GRUB is your bootloader: highlight the entry you normally use to boot, press TAB. Add nomodeset somewhere on that line, and press F10 to continue booting. See if this improves the situation. If so, add nomodeset so it's used at every boot (I typically do this by running dpkg-reconfigure grub-pc to let DPKG manage this so it's always added in case another package tries to add its own changes).
If not, you may need to install the binary drivers from nVidia.com, it may be a power management issue with the card and open source drivers.
Right after I upgraded to jessie, the video froze when gdm started loading. I blacklisted the nouveau kernel module and that fixed that problem.
I did try appending nomodeset to the kernel command line (via grub) as you suggested, but that didn't make any difference.
As for what X is using, apparently the nouveau driver, and then VESA mode is being set automatically. So as you can imagine, even without the resume problem, I notice the graphics are frequently sluggish during general use.
Code:
root@gateway:~# cat /var/log/Xorg.0.log | grep nouveau
[ 24.798] (==) Matched nouveau as autoconfigured driver 0
[ 24.798] (II) LoadModule: "nouveau"
[ 24.799] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[ 24.834] (II) Module nouveau: vendor="X.Org Foundation"
root@gateway:~# cat /var/log/Xorg.0.log | grep -i vesa
[ 24.798] (==) Matched vesa as autoconfigured driver 4
[ 24.932] (II) LoadModule: "vesa"
[ 24.933] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 24.939] (II) Module vesa: vendor="X.Org Foundation"
[ 24.941] (II) VESA: driver for VESA chipsets: vesa
[ 25.049] (II) VESA(0): initializing int10
[ 25.070] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[ 25.154] (II) VESA(0): VESA BIOS detected
[ 25.154] (II) VESA(0): VESA VBE Version 3.0
[ 25.154] (II) VESA(0): VESA VBE Total Mem: 131072 kB
[ 25.155] (II) VESA(0): VESA VBE OEM: NVIDIA
[ 25.155] (II) VESA(0): VESA VBE OEM Software Rev: 4.52
[ 25.155] (II) VESA(0): VESA VBE OEM Vendor: NVIDIA Corporation
[ 25.155] (II) VESA(0): VESA VBE OEM Product: NV34 Board - p118dtnz
[ 25.155] (II) VESA(0): VESA VBE OEM Product Rev: Chip Rev
I installed the nvidia-support and nvidia-kernel packages, which as I recall installed the 304xx legacy driver. I then ran the nvidia xconfig but received a message (in the log) that I couldn't use the 304xx driver. X failed to start at all until I removed the newly create xorg.conf file.
As I understand it, the 173xx legacy driver is required for the chipset she's using (GeForce FX 5200), but the 173xx was removed from jessie because it fails to build against the xorg-server packages.
For Wheezy and earlier releases there's a 173xx series nvidia driver that can be installed for the FX5200 card
The 173xx nvidia driver has been removed from sid & Jessie because the highest Xorg version it supports is the 1.15 version (sid & Jessie are using Xorg 1.16).
So nouveau is the only option for sid & Jessie (unless you want to use the vesa or fbdev driver)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.