Lately I upraded my Debian using aptitude update/aptitude upgrade - including installing a new kernel (3.0). Since this upgrade I have strange problem with networking. When I suspend my computer and resume it, I do not have connectivity with network:
$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.1 icmp_seq=1 Destination Host Unreachable
[code]....
I have installed squeeze on a HP notebook. I have one small problem though.It does not resume from suspend. If I shutdown -> suspend, or close the the lid, or shut downs (suspends) as expected, but whenower it backup up, the screen just stays black.Hibernate is working fine.
output of lspci (if needed)
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
[code]...
I have just joined the Debian community, for the past 2 years I have been using Linux Mint (ubuntu), I am now using Linux Mint Debian 64. I have a Lenovo A700 ideacentre with a Broadcom 4313 WiFi card. I manage to get the card working, now I have a new problem. If I suspend the machine the WiFi will not connect on resume. Is there a simple command I can use to getting the connection restarted, or better yet a work around so it will restart on its own?
View 14 Replies View RelatedI'm having problems with resume after suspend to RAM. The machine starts to wake up, but the screens (multi mon VGA and DVI setup) are black and the keyboard doesn't light up. After ~20 seconds there's some brief disk activity and then the computer reboots. 100% repeatable with affected kernel versions. My test method is simple, I boot the machine on the kernel's recovery option, log on as root and run "PM_DEBUG=1 pm-suspend". I haven't found anything in the logs after a failed resume.
Here's the situation:
I have a SSD disk. To get TRIM support I have to use kernel 2.6.33 or later, which means that the standard kernel in Squeeze is too old.I have Nvidia graphics, and there was a change in 2.6.34 that breaks older versions of xserver-xorg-video-nouveau (version 0.0.15, used in Squeeze), I can't use Debian Squeeze with a kernel newer than 2.6.33.x.My machine (XFX GeForce 9300 motherboard) won't resume from suspend to RAM if I use a kernel newer than 2.6.36. There are no BIOS updates available.
My options:
Install newer kernel from Squeeze backports (2.6.38.2 last time I tried). <--- Not doable b/c of resume problems. Upgrade to Wheezy, which uses kernel 3.0.x. <--- Not doable b/c of resume problems.Compile a vanilla kernel. So basically I'm forced to compile my own vanilla kernel, 2.6.33.x on Squeeze or 2.6.35.x on Wheezy. I won't be stuck with an unsupported kernel version in the near future, but so far I've failed miserably.
I know that the latest kernel version where everything works is 2.6.36.x (no longer maintained), 2.6.37.0 and later cause resume problems (I've tried 2.6.37, 38, 39 and 3.0.0, .0.1). I've tried doing a git bisect on the kernel, but didn't succeed, ended up on 2.6.36-rc5 which is weird considering that 2.6.36.4 works. There may be several suspend/resume bugs in different kernel versions that messed up the bisecting results.
I'm running Debian 8.1 KDE on a 2007 dv6 laptop. Model number is worn off. lol but the specs:
Intel i3 first gen m 330
4GB RAM
Intel (ironlake) graphics
First off, closing the lid to my laptop doesn't trigger suspend, or anything no matter what I set it to in power options.
I can suspend using "systemctl" or suspend from the "Leave" menu, but upon turning my computer back on, my touchpad and keyboard don't work.
Sometimes, my touchpad will start working after about 15 seconds, but the keyboard doesn't come back. I have to hard reset.
I have a feeling it's something to do with systemd, but I'm not super proficient in linux. Just an end user who is friendly with a terminal.
I am running Squeeze on an older Compaq EVO laptop with radeon graphics.
A few months ago, after an upgrade, suspend and hibernate stopped working. The suspend or hibernate worked fine, but the resume just hung with a black screen. I finally got around to looking into it and found a workaround.
The workaround is to disable Kernel Mode Setting for the radeon. This can be done by adding the boot parameter "radeon.modeset=0" or by editing /etc/modprobe.d/radeon-kms.conf so that it includes the line "options radeon modeset=0".
If you are interested in the details, you can search for problem reports related to radeon kernel mode setting.
I am having a problem with suspend in F15. While the computer enters and resumes from suspend extremely fast (basically instantaneous), the whole system seems sluggish and unresponsive afterwards. The mouse cursor is lagging and some key strokes are omitted when typing. The animations in Gnome 3 are also very non-fluid compared to how they were before suspend. The only way I have found to return to normal operation is to reboot the computer. I have tried 32 and 64-bit versions of Fedora 15 with the problem existing in both. I also tried the latest version of openSuse (Gnome 2.32) just to see if this problem persisted and I can confirm that it did. Perhaps this indicates a kernel-related problem that should be reported as a bug somewhere else?
lspci:
Code:
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11)
00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11) .....
The good news: 11.4 seems to have much better support for my radeon graphics driver which makes many of my workarounds for 11.3 unnecessary
The bad news: whereas previously for 11.2, 11.3 using traditional ifup meant that I could easily restore internet (either wlan0 or eth0) with ifdown/ifup now this seems to have no effect. I haven't investigated further yet since without internet on hibernate or suspend 11.4 is not my grub of choice at the moment
There seem to be quite a few glitches with the 'stable' release of 11.4 but this seems to be the main problem for me. (Minimizing the beta 4 Firefox windows closing them is another...)
For the sake of security, I want the screen to be locked after the system is resumed from suspend or hibernation. Now the only way I can do this is to check the options "Lock screen when screen saver is active." in the screensaver preference. But this method is annoying since I have to type the password to quit the screensaver. Is there other way to do this? Thanks.
By the way, I use CentOS 5.2 x86_64.
Leonard
2009-3-21
i dont know why my system dosnt resume from suspend sstate.i it goes in suspend state.it doesnt resume .i have to poweroff then restart it again.and when i get logged in it gives me Following Error: Resume problem: Your system did not appear to resume correctly from Suspend/Hibernate. This may be a driver problem or a hardware problem. Check the GNOME Power Manager Manual for common problems.
do you think it is because of batterry.i have a problem in my By Battery .IN DOS operating system.when i check my battery icon . A red Cross constantly blink on lower right side of the battery and it says (your Battery consider Replacing).i have notice one thing .And My battery timing hias become Decreased. Do you think this Resume problm is cause of battery problm.Or there is some problm in my Os software.
My system is hanging on screen suspension... And its not the usual hang on "sleep" or others similars, it will happen by only having the screen on stand-by ( eg xset +dpms)...
If I leave for a while the screen will shutdown as expected but computer will completely hang after an indefinite time, it will not respond to outside connections and the will be spinning faster than usual...
Only workaround is to have the screen power save option disabled, in my case, on the KDE settings...
I have tried the most common solution to have "nomodeset" as a kernel option to disable mode setting, but this doesn't seem to work...
Also tried to forcebly reproduce the issue with Code: Select allxset force dpms standby/suspend/off but nothing happens like that...
This issue also only appears with the fglrx driver, open-source works well.
I recently upgraded to Lucid (x86_64) on an HP dv2 laptop, and after doing so, the system will not resume after a suspend (with fglrx installed from the "official" repositories). After reading a lot about the problem, I have seen that updating to the latest ATI driver had fixed this issue for some, so I would like to try that.
I am following the guide at at cchtml.
First, I tried installing the Ubuntu-X team's drivers. However, after (successfully) adding their repository, an update does not fetch their packages:
Code:
It looks like both the xorg-edgers and ubuntu-x-swat repositories are being ignored? (If I'm reading that correctly.) If I open the window System->Administration->Software Sources, I can see that the ubuntu-x-swat repository is checked, so I'm confused why it's being ignored.
If I try to demand the fglrx-installer package, I get an error that it cannot find this package.
Code:
I have the same issues for xorg-edgers and ubuntu-x-swat.
Finally, if I try to build the official ATI v10.7 drivers myself, I get an error that Linux is an unrecognized architecture!
Code:
I have installed all preliminary packages suggested in the guide:
Code:
I really can't understand why I'm unable to build the package from ATI myself.
My computer have ATI X600 graphics card installed, and I installed CentOS5.3.
Every time I suspend my computer and then resume it, it seem the graphics card can't resume and the monitor says 'no signal', but the system still responses, I can use keyboard.
Is there any configuration I can't do to make it resume normally? I've searched a lot in Google but can't find out any one else run into the same problem.
Information about the card:
Quote:
To workaround the kio_smb madness, I set up shares to be mounted via /etc/fstab. It works flawlessly until I suspend my laptop. Coming back from suspend, samba mounts are not being re-mounted automatically. Since I'm new to opensuse, I wish to ask you:
Is there a polished way to make this happen, in opensuse approach?
Or shall I just go and toy with scripts in the init.d (or what is it in suse)?
As much as I could figure, I checked in yast, and smbfs service is signed as "Yes".
I have an issue with my Sony vaio fw31e not resuming from suspend. Reported this as a bug: [URL] The usual ways of suspending, from the kde 4 menu, from the power/battery widget or by lid closing always result in no resume. However, running pm-suspend from a root terminal suspends and resumes just fine. My question is, how does one delve into the way that the usual methods initiate suspend? Maybe if I could find out what each of these methods actually does, I may be able to see what is going wrong? I had been running squeeze on this lappy since July 2009 with no suspend issues until an update broke it sometime in January. The install is being fully upgraded every day at the moment.
View 11 Replies View RelatedI have a desktop system (P55-USB3 + Core i7 + Ubuntu 10.10) that fails to suspend/resume from memory. So I'm trying to diagnose the problem. The first obstacle was easy enough --- when I put the system to sleep to memory, the computer comes back alive right away. A look at /var/log/kern.log revealed that one USB device (usb10) failed to suspend, and from there I was able to pin it down to the USB3 controller in the BIOS. Disabled that and this problem disappeared.
Now, I'm stuck with the second obstacle. The computer successfully goes into the suspend mode, but it hangs during resume. The monitor doesn't get any video signal, and it fails to respond to ping (netconsole doesn't work either.) After a forced reboot (that involves unplugging the power cable), /var/log/kern.log doesn't contain any interesting entries. All the pm_test modes from freezer to core succeed (I followed [URL] I've also tried pm_trace (https://wiki.ubuntu.com/DebuggingKernelSuspend) but again kern.log nor dmesg contains anything after the suspend. Either the write didn't survive the forced power off, or the resume is failing even before that. The motherboard doesn't have a serial port nor firewire, so getting kernel logs through them is not a possibility, either.
I have a quite simple installation of Debian 8 Jessie XFCE and the resume from suspend is not working 9 out of 10 times. The system is single booted if that matters. I have found a few solutions to this problem but they were not suitable to my case as I don't have an Nvidia GPU but only Intel Onboard:
Code: Select all# lspci -v
00:00.0 Host bridge: Intel Corporation 82Q35 Express DRAM Controller (rev 02)
Subsystem: Hewlett-Packard Company Device 2818
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=0b <?>
Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device 2818
[CODE]..
When I try to resume, I can hear the system booting but I can't see anything on the screen and the keyboard is not working either (no light on Num Lock and Caps Lock). The only option is to press the power button for a few seconds to stop the machine and then push again to start booting again.
Up until a couple days ago, my computer had no problems suspending to ram. However, now when I suspend, and later hit a key on the keyboard (usually space) to resume, all I see is an illuminated black screen. I can't even open a tty via Ctrl+Alt+F1. I can however ssh into the machine.he only possibility I can think of is that I am no longer running kdm. I just use "startx" to star an openbox-session.
View 8 Replies View RelatedMy Acer Aspire 7552 laptop is running Debian Testing (just the main repos, no contrib or non-free). For some reason, it takes over five minutes to resume from suspend, and an absurd period to come back from hibernate (well over half an hour). Has anyone encountered this problem before, or have any tips on how to fix it? For the time being, I'm completely powering off every time I close my laptop because it's faster that way.
Output of lspci in case it helps:
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS880 Host Bridge
00:02.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (ext gfx port 0)
[code]...
Fixing my chronic suspend/resume problems turned out to be easier under systemd, but like everything else lacks documentation.
To suspend rather than power off when pressing the power button, I edited /etc/systemd/login.conf
uncommenting this line and changing it to suspend:
HandlePowerKey=suspend
and uncommenting the line
HandleLidSwitch=suspend
Some services were lost on resume. This problem seems common. To run a command on resume, I believe you have to make your own script, and create a systemd file to run it.
My script is /home/james/.bin/james-resume.service, which contains:
#! /bin/sh
/sbin/hdparm -B 255 /dev/sda
This must be executable. Ownership doesn't seem to matter.
To run it, I made a file in /etc/systemd/systen/suspend.target.wants
The file name must match the script name:
/etc/systemd/system/suspend.target.wants/james-resume.service
This contains:
[Unit]
Description=Run James jobs at resume
After=suspend.target
After=hibernate.target
After=hybrid-sleep.target
[Service]
ExecStart=/bin/bash /home/james/.bin/james-resume.service
[Install]
WantedBy=suspend.target
WantedBy=hibernate.target
WantedBy=hybrid-sleep.target
Ownership must be root.root. Apparently it doesn't need to be executable.
Then enable with:
sudo systemctl enable james-resume.service
and check with:
sudo systemctl status james-resume.service
If it says the service is loaded, it's OK -- inactive only means it's done running.
I'm running Debian Squeeze on a Dell Studio 1558 laptop, and I have my laptop set to suspend when my lid is closed. Resuming from suspend seems to work but the screen remains blank, forcing me to hard reboot every time. Upon reading this thread:
Tue Jun 21 23:07:12 AKDT 2011: performing suspend
Tue Jun 21 23:07:28 AKDT 2011: Awake.
Tue Jun 21 23:07:28 AKDT 2011: Running hooks for resume
[code]...
I am running Debian on an ARM module (BananaPi).5 minutes ago, i started upgrading the system, but fortunately the power cable moved and the system closed.Now i open it up again and i'm trying to re-upgrade the system but i'm always getting this message
# apt-get upgrade
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
Just upgraded (libudev0 and related) and system fails to mount other partitions, gives a lot of errors and drops to single mode.
View 14 Replies View RelatedA few days ago I upgraded my debian sid system, and since then systemd does a filesystem check on every boot which takes over two minutes, disobeying the existing settings I had. How can I set systemd to do a filesystem check only once every a set number of mounts, like I had set up before the upgrade?
View 5 Replies View RelatedI am on debian jessie. I ran "apt-get update && apt-get upgrade" and midway through the upgrade my computer suddenly rebooted.
I wasn't paying close attention to the upgrade process so I didnt see if there was any error messages right before the reboot. The laptop was plugged in, fully charged and I've never had issues with overheating.
When I boot now I get to a shell with a message that says:
Code: Select allWelcome to emergency mode. After logging in type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode.
If I try "systemctl default" there's a message that simply says "Hangup", nothing else happens.
Looking through "journalctl -xb" I see this:
Code: Select allFailed to insert module 'autofs4'
Failed to open /dev/autofs: No such file or directory
Failed to initialize automounter: No such file or directory
Failed to set up automount Arbitrary Executable File Formats File System Automount Point.
Failed to start Load Kernel Modules.
If I retry "apt-get upgrade" it says:
Code: Select alldpkg was interrupted, you must maually run dpkg --configure -a to correct the problem
If I run "dpkg --configure -a" stops at the package cups-browsed with message saying "Hangup"
Output of a few commands I saw in another forum thread:
$ lsmod
Code: Select allModule Size Used by
ext4 473802 1
crc16 12343 1 ext4
mbcache 17171 1 ext4
jbd2 82522 1 ext4
[Code] ....
Is this fixable without jumping through too many hoops or should I just reinstall the system? I need the computer for work so Im not gonna spend days trying to fix it without reinstalling.
I upgraded from lenny to squeeze on a notebook and I can no longer connect to the wireless network. The computer is an LG notebook and the network card is ralink rt2860. I am using Gnome and NetworkManager. The wireless key is WEP hex. It was working fine with lenny till before the upgrade. After the upgrade, the network card stopped working. So, I checked
$ lspci|grep Network
08:00.0 Network controller: RaLink RT2860
Then I reinstalled the driver with apt-get install firmware-ralink wireless-tools Then the network manager tray started working again and saw the network, but cannot connect. It was trying to connect but timed out and kept asking for the password. It is the correct password. I tried deleting the old connection and recreated a new one in the nm. But still does not work.
[Code]...
I don't know if these are related, but I have had occasional lockups, where no input has any effect and then it shuts down, and am usually unable to resume from suspend on closing the lid.
Here are the specifics. Thinkpad x120e, AMD e-350, ATI radion 6310 graphics, Intel 320 series SSD 80 GB, no bluetooth.
The ethernet and wireless cards, as given in lspci, are
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
04:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter (rev 01)
[Code].....
My laptop won't resume after it suspends. It works fine under win 7 so it's not the hardware. The light says it's on and it's pretty much a blank screen. I'm not sure whether it's operational but the screen is off. It has exactly the same resault a waiting for the blank screen except it won't go back on.
View 9 Replies View RelatedI've just upgraded from 9.10 to 10.04 via the upgrade manager. Prior to the upgrade I was able to suspend and hibernate without any problems. Now that I have upgraded to 10.04, I can suspend however when I resume I am back at the gdm login prompt, logging in again with a new session.Having just done another test whilst writing this, it actually appears that if I select suspend from the top right I am suspended and can resume my session. If I close the lid on my laptop (which is supposed to suspend) I am logged out and suspended.Also, Hibernate doesn't work as well - sometimes it never actually hibernates (just sits on a black screen) and sometimes it doesn't resume (it's never hibernated and resumed correctly since the upgrade)
View 9 Replies View RelatedI got this message when I tried to get in WifiSettings.
"The system network services are not compatible with this version"
What should I do?
