Now Debian6 suspend and rstart is all ok!
Auto start a program with login is ok.
How to auto start a program with debian suspended and restart ?
Maybe with gdm3 or NIC....?
How can I catch a event to auto start my program?
With what functions i can write my program in /etc/init.d with c++ to start every time the computer starts ? (like in windows with RegOpenKey,RegSetValueEx..............) ?
View 4 Replies View RelatedInstalled Debian 8.2 a while back, and I've been having issues with getting the machine to suspend correctly. If I try to put it to sleep when logged in to my regular user account the screen just goes black and then the computer hangs. However if I put it to sleep as root everything works fine. I do this by running this command (as root):
Code: Select allsystemctl suspend
What can I do about this? Worked fine on Debian wheezy..
Btw, just found this in the dmesg log. Connected perhaps..?
Code: Select all[ 6.863018] ACPI Warning: SystemIO range 0x00000000000018e0-0x00000000000018ff conflicts with OpRegion 0x00000000000018e0-0x00000000000018ef (\_SB_.PCI0.SBUS.SMBI) (20140424/utaddress-258)
[ 6.863028] ACPI:
If an ACPI driver is available for this device, you should use it instead of the native driver
Suspend worked before I completely reinstalled Testing from scratch. Now it seems to suspend OK, but when it tries to wake up it fails. Details here: [URL]
View 6 Replies View RelatedI 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've been running 6.0.2 amd64 stable since release day and recently have noticed my suspend and hibernate do not work. Normally I have transmission running and have set it to not enter sleep mode while torrents are active. However today I have not had transmission and was wanting to see if the sleep mode options would kick in. So I have set my display to "sleep when inactive for" 5 mins (this works perfect)
I have set "put computer to sleep when inactive for" 10 mins (this does not work at all)
When I try to manually test suspend my display flashes black for a few seconds but remains backlit, then asks me to log back in
When I manually go into hibernate mode my display turns off, pops back on for a second and in a terminal says something about a usb device (something failed but it happens so fast I cannot read it)
I tried to set up an automatic program restart on Debian Lenny for fail2ban and asterisk. Google helped me to find some HowTos. However, all what I tried so far doesn't work. The latest version: According some instructions the following commands have been written in a file called auto_start_stop:
Code: #! /bin/sh
-> saved in the folder /etc/init.d and
-> its properties changed with a right-click to 075.
-> The links have been created with update-rc.d auto_start_stop defaults
Why this doesn't work and how I could correct it?
Trying to load ubuntu 11.04 and error message comes up cannot find autorun program. how do i get the program on my computer so i can download the upgraded version of ubuntu I have tried rebooting and many many other things. it loaded just fine on my desktop right over my pc linux os.
View 1 Replies View RelatedSo I have this laptop with a busted battery, I'm trying to get it into some kind of headless server, media topbox hybrid.
First thing I want to do is being able to leave it shut (powered on) in the corner without having to interact with it directly.
I've setup ssh and vnc so to login remotely and do task, transfer files and etc.
However there is a little issue with the laptop lid down upon turning it on, it immediately goes into suspend when getting to the display manager, which is 'lightdm'.
I suppose this is the default setting for Xorg and as such my custom configs for KDE only kick in after I login.
Question is: I never seen configuration for default power management stuff being done in Xorg, is there some way to disable automatic suspension on lid down?
Another question is: After the KDE kicks in does it always replace power options? I have setup a xorg.conf file specifying dpms options but these don't seem to remain.
System is a Dell E7440, with Jessie, I recently upgraded to kernel 4.2.5 due to issues with wireless that are supposed to be fixed. (The same issue exists with jessie stock kernel 3.16 and BPO tough)
When I close the lid it often does not work and I get this in dmesg
Code: Select all[ 567.104335] pci_bus 0000:01: Allocating resources
[ 567.104349] pci_bus 0000:02: Allocating resources
[ 567.104415] pci_bus 0000:03: Allocating resources
[ 567.104428] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[ 567.105515] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[ 567.105540] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[ 567.105585] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[Code] ....
I suppose the i915 stuff is something I can ignore, However
Code: Select all[ 570.768020] acpi device:40: Cannot transition to power state D3hot for parent in (unknown)
seems to be the issue.. I don't even know what device:40 is.
in ls -l it shows as
Code: Select all lrwxrwxrwx 1 root root 0 Nov 2 12:28 device:40 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C6:00/device:40
and
Code: Select all# cat /sys/bus/acpi/devices/device:40/path
\_SB_.PCI0.SDHC.WI01
The awkward thing is tough, software suspend by running "systemctl suspend" works perfectly and always.
Code: Select all [ 872.054627] PM: Syncing filesystems ... done.
[ 872.091506] PM: Preparing system for sleep (mem)
[ 872.092045] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 872.093377] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 872.094563] PM: Suspending system (mem)
[ 872.094595] Suspending console(s) (use no_console_suspend to debug)
[Code] ....
So despite the mysterious issue with acpi device 40, how is real lid close different from "systemctl suspend"? And can I simply workaround the issue by making such a suspend when the lid closes?
Just curious if this is possible. What I want to do is setup a rsync job to backup my laptop to my personal file server(same LAN), but I want it do do this at 3AM while I'm sleeping. However I always close my laptop lid when I'm done using it which puts the laptop into suspend mode since that's how I configured my power options in gnome. Since I don't want to leave my laptop powered up all the time, I was wondering if it is possible to have a cron job scheduled that will wake the laptop up(out of suspend mode) and run my script/backup job, all without opening the lid of the laptop, and then put it back into suspend mode when it's done. Is this possible, and is it as easy as scheduling a cron job or is there some other scripting/configuration/trickery that I need to do to accomplish this?
Also, my laptop's BIOS has the option to power on at a scheduled time if needed, but I'm not sure if that would work with it being suspended(hibernation is not an option since my entire HD is encrypted with LUKS and I would have to be present to enter the password to boot the system.).
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've tried editing .xinitrc to contain ck-launch-session and dbus-launch to no avail. Console kit is installed. I'm using Sid without a login manager, and xfce's suspend and hibernate work fine on my Wheezy computer. Xfce4-session and consolekit are installed. Is this a problem with permissions?
View 3 Replies View RelatedI have installed the latest virtualbox 4.1 on my desktop and laptop. It hosed suspend and hibernate.
The laptop is A Dell D630 with Intel Core2 Duo CPU, the desktop is an AMD based ASUS M3N78-VM mobo with Athlon II x2 250 CPU. Debian Testing 32-bit (same results with the 2.6.39 and the 3.0 kernels). Both have nvidia cards though - the desktop an integrated 8200, the laptop a NVS 135M. But suspend/hibernate was working before with the 4.0 series virtualbox.
The workaround is to clear the vboxpci vboxnetadp vboxnetflt vboxdrv modules from the memory before suspend/hibernate. I added the
service vboxdrv stop
rmmod vboxpci vboxnetadp vboxnetflt vboxdrv
lines to my sleep script (i dont use power managers, just the acpi powerbutton/lid scripts modified). Everything is ok now.
I'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.
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'm trying to lower consumption of my server/HTPC. After wakeup from pm-suspend server/HTPC is ready to use in 1 or 2 seconds .For example if I suspend it while watching movie in KODI, after resume movie starts playing instantly. But some services (SSH and SAMBA) are not running. I thought it was network problem so I change configuration to static (not DHCP). SAMBA and SSH starts like 15 seconds after wakeup.
View 0 Replies View RelatedI have Debian Squeeze x64 on ThinkPad T61p with standard 2.6.32-5-amd64 kernel. thinkpad_acpi loaded as module, suspend to RAM works fine from menu in KDE as well as by closing the lid, however machine doesn't appear to react on pressing Fn+F4 which should put it to sleep as well. I've read through thinkpad_acpi documentation and asked Google but so far can't find the solution. Can anyone, point me in correct direction?
View 6 Replies View RelatedLately 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]....
My system is a three days old Linux version 2.6.32-5-amd64 (Debian 2.6.32-35) with an Intel(R) Core(TM) i7 CPU 60 @ 2.80GHz. It does start, goes through the grub and then spits out strange messages and just freezes before the KDE can be started. I have to restart again, until it really boots everything. This is happening in a random pattern.
I activated bootlog, but as far as I can see, the log only tracks, if the system is really booting. So I also have the dmesg copied into pastebin. These are the only two logs I know, now.
The code of the boot log goes here-
Wed Aug 17 10:24:19 2011: Setting parameters of disc: (none).
Wed Aug 17 10:24:19 2011: Setting preliminary keymap...done.
Wed Aug 17 10:24:19 2011: Activating swap...done.
[Code].....
I decided to upgrade my Asus Eee 900 from Lenny to Squeeze, to fix some issues that I was having. I did a fresh install using the beta1 netinstall cd image, and now my system is mostly working as I'd like it. Overall it seems quite good, and it even boots much faster than it did with Lenny.
I've encountered a problem, though. The suspend key doesn't work. I installed the package 'hibernate', and now the system can suspend via a command (which seems to work properly, although I haven't tested it extensively). I've noticed that the squeeze system doesn't have a command that my other Lenny systems do, 's2ram'. And I've noticed also that a package, uswsusp, which seems to be related to this kind of thing, can't be installed because it's not in the repositories: Package uswsusp is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'uswsusp' has no installation candidate
My hibernation was working out_off_the_box but now it has strange issue. This is debian testing with kernel 2.6.38.4 "hibarnation-disk" hibernate successfully ,with an error though ( seen from hibernate-disk -v2 --dry-run) hibernate-disk:Warning: Tuxonice binary signature file not found Anyhow , after executing the hibernation , on the next boot, the system boots from scratch and not from the resume image. During boot a message is displayed though Invalidating stale software suspend images I have done some google search but none of the solution work so far, including reinstalling the package itself.
View 6 Replies View RelatedI just installed Ubuntu on my brand new system that I built. I put in my cd for my HD 5770 video card, and an icon shows up on my screen XFX_VGA_V9.8C text under it.
However when I try to access it in anyway, I try to open with autorun prompt, I get a message "This medium contains software intended to be automatically started. would you like to run it?"
I click on run and get "Error autorunning software, cannot find the autorun program."
Is there anyway that I can run this disk. It's important for setup. I cant copy the disk to the desktop, I get errors.
Some problems keep bothering me and dont let me use my debian sqeeze with joy.Im in network with no DHCP on. When installing i didnt configure my eth network card.After each restart i need to configure manually my eth because it loses it.
View 7 Replies View RelatedI'm using Debian 8 and I have ipset v6.23 and iptables v1.4.21. I put a rule with ipset in rules.v4 file and then I restart the iptables with netfilter-persistent service. When I reboot the iptables list is empty. But if in the file I don't put a rule with ipset, after reboot the iptables list is correct.
View 4 Replies View RelatedI wanted to ask how to restart the Debian Server. It should start daily, at 2-3 o'clock in the morning. Don't know how to program the server.
View 4 Replies View RelatedI 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 have problems to get it work. i have tried to use pm-utils, but it does nothing.
What is need is to kill application, when pc is going into suspend to ram and run that application again on wake. It's a graphical application.
I've after latest jessie update a problem with service samba restart. If I use "service samba restart", there is a timeout (after long time) and error.
Output of "systemctl status samba.service":
Code:
Select all● samba.service - LSB: ensure Samba daemons are started (nmbd and smbd)
Loaded: loaded (/etc/init.d/samba)
Active: failed (Result: timeout) since Mo 2014-10-20 02:16:57 CEST; 7s ago
Process: 6205 ExecStart=/etc/init.d/samba start (code=killed, signal=TERM)
Okt 20 02:16:57 server systemd[1]: samba.service start operation timed out. Terminating.
Okt 20 02:16:57 server systemd[1]: Failed to start LSB: ensure Samba daemons are started (nmbd and smbd).
[Code] ....
Whats going wrong. "service samba restart" should bring no error message if the service is not running previously.