I just wondering if there is such widget that I can put 'suspend to disk' and/or 'suspend to ram' onto my main panel like the logout button.I do not use 'Application Launcher' much but that is the only place I can find 'suspend to disk/ram' options/buttons.
View 7 RepliesAfter i click hibernate system begin to, but then it returns from suspend progress bar back to screensaver.
from dmesg:
Code:
[56908.741010] PM: Marking nosave pages: 000000000009f000 - 0000000000100000
[56908.741016] PM: Basic memory bitmaps created
[56909.338255] [drm] Requested: e: 20000 m: 0 p: 16
[56909.338259] [drm] Setting: e: 20000 m: 0 p: 16
[code]....
I just installed openSUSE 11.3 but cannot get hibernation (or suspend to disk) working. It does not go to hibernation but instead it just locks the screen. The relevant error in /var/log/pm-suspend.log looks like below.
According to /usr/lib/pm-utils/sleep.d/30s2disk-check '/dev/dm-1' must be the swap partition. What i don't understand is that why the error says swap partition is not active. There is no error for swap partition during boot time. Boot message says that swap partition is activated.
/usr/lib/pm-utils/sleep.d/06autofs hibernate hibernate:Shutting down automount ..done
success.
/usr/lib/pm-utils/sleep.d/30s2disk-check hibernate hibernate:INFO: checking for suspend-to-disk prerequisites...
ERROR: resume partition '/dev/dm-1' not active, can not suspend
[code]...
Below is fdisk -l information for the disk which has swap partition.
/dev/dm-0p1 1 2089 16779861 82 Linux swap / Solaris
Partition 1 does not start on physical sector boundary.
/dev/dm-0p2 2090 3395 10482431+ 83 Linux
[code].....
My system does not power off completely after I trigger the "suspend to disk" function. The monitor gets blank and the usb-mouse does not light anymore, but the power led is still on and the pc fans can be heared. Interestingly, neither pressing the power button nor the reset button starts the pc in this state. I have to unplug the electrical power and then press the power button. After that, the system resumes nicely from the hibernation state as it should. I know that the hardware itself is capable of powering off because it worked perfectly before with opensuse 10.2, and I didn't change any bios settings either. I tried the option acpi=force, but to no avail.
View 2 Replies View RelatedI've been struggling with suspend to disk (hibernate if you prefer) for a while, it works after a fresh boot and for several days' worth of overnight hibernation as I go about my work, but eventually it stops working - it gets to the splash screen but the bar only makes it a little way to the left before stopping, and then after a timeout the system just returns to the "session locked" screen - no real error messages.
I've done my best to try to find out what's causing it to break but I'm really struggling, the suspend process doesn't appear to write anything helpful to the dmesg log or the /var/log/pm-suspend.log - the only thing that I've seen at about the right point in time is cifsd, but I can't be sure that it's a problem with cifs as hibernate continues to work immediately after mounting windows shares with cifs.
System:
Phenom-II X3
4Gb ram
OpenSUSE 11.1
[code]....
I'm always struggling with desktop space. Widgets like Folder View and the ability to use the multiple virtual desktops are very helpful for me. I found an article about the KDE Shelf widget which I would love to have as another organizational tool but I can't seem to find it.I am a bit of a newbie with KDE and with Linux in general but I have found and added many widgets with no problem. I have been using computers for about 16 years and I'm pretty tech savvy (but unfortunately my skills have all been learned through Windows and some with Mac in college).
When I go to Add Widgets and type "shelf" in the search withing openSUSE KDE I get no results. I also checked on kde-look.org and an overall Google search but I'm not having any luck.
I am running an opensuse machine with 6 virtual desktops. I would like the 6th virtual desktops to share the common widget dashboard.
View 1 Replies View RelatedSo after installing 11.3 for some reason I cleared all the widgets off my desktop. When I add the folder view widget to the desktop again so I can see my desktop iconsthe widget doesn't show my icons unless I click on it and they drop down. Without clicking on it, the widget shows the desktop icon (similar to the "show desktop" icon)
View 5 Replies View RelatedI have been enjoying my newly installed openSuse installation for the past two weeks. I used it to run on a free computer I received so I didn't have to purchase that other operating system. It has come a long way since my last tinkering with linux/unix in college 12 years ago!I think that I noticed a problem with the calendar widget 1.0. When you change the month, the days don't update in the calendar.
View 5 Replies View RelatedI have installed ubuntu via the alternate installer, activating encrypted home directories, which in turn enabled to have encrypted swap partitions and disabled hibernation (suspend-to-disk). I understand the arguments for having an encrypted swapspace in these cases. However, I'd like to be nevertheless able to hibernate. Now that the system is already set up, I cannot change and completely encrypt my harddisk via LUKS+LVM as it is suggested in numerous places.Instead, I tried the following. I created two swap partitions (sda7 and sda: one being encrypted via cryptsetup, to be used as a 'real' swap (sda7). Another without encryption, which is not listed in /etc/fstab, so that it is not normally used by the system. I have then configured uswsusp in order to use sda8 as a resume partition:
[code]...
I have decided to encrypt the resume image - I don't care entering a password once every time I resume, it just shouldn't be at every boot. And this way, I can have hibernation without the uncomfortable solution of having my decrypted, open files on the disk as clear text. However, as sda8 is not 'mounted' when I want to suspend, I get the following error:
[code]...
When I try to suspend now, it works. The image seems to get correctly written to sda8. However, on reboot, the image does not seem to be detected and the system is not resuming. I end up with a fresh login screen. would be also to unmount sda8 upon resume, is this better done by entering a hook in /etc/pm/sleep.d or can I just continue in the wrapper script above by executing s2disk.unwrapped only by calling it (without 'exec'), and entering a swapoff line behind it?
I'm having some difficulties with the comic strip widget that I use to keep me updated on Dilbert. It started out in ok-ish size, a little small, but readable. Now the entire strip takes up 3x3 cm, totally unreadable. Is there anyway to fix that?
Here is a screeshot of it:
[URL]
I remember this was discussed some time ago but I cannot find the thread any more. I was just wondering if others are still seeing the same problem . I've had this all through 4.4.3 and now with 4.4.4. For some reason if only the logout or lock button is selected and placed on the far right of the panel then part of the button is chopped off. This only happens with the panel locked. If both buttons are selected then they display correctly. I also notice that when only one button is selected that it's size is slightly smaller than when both are selected. Also it only seems to be the logout/lock widget that has this problem.
View 1 Replies View RelatedI installed the pam_face_recognition package to try out but decided couldn't get it working properly so removed it via YAST. Now when I boot up I get a pop up dialogue saying the login greeter widget is missing and to check my configuration. Clicking OK on the pop up drops me to the console login.
View 4 Replies View RelatedAfter returning from suspend to disk, RF devices (wlan and bluetooth) are disabled. Running lspci indicates that no wireless network device is available, and no drivers are loaded. Furthermore, the LED on the front of the laptop remains off - this is always on when RF devices are available. There is an Fn-F1 function key to toggle wireless, but this does not function to either enable or disable.
Rebooting the system does not re-enable the RF devices, and there is no option in the BIOS. The only workaround I have at present is to boot into windows vista and use the Fn-F1 function key. This pops up a small hotkey utility with the option to disable/enable the wi-fi and bluetooth (independently). Upon confirming the dialog, the RF device light immediately illuminates. Rebooting into fedora and wireless devices are working once again.
I am running kernel 2.6.31.12-174.2.3.fc12.x86_64, with the latest compat-wireless drivers. I can provide much more debug information (dmidecode, acpidump, boot logs, lspci etc...), I am just unable to determine what is relevant
# rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
[code]....
i downloaded a widget named yet another netspeed monitor.it is not working.it says please see the following image
View 4 Replies View RelatedopenSUSE 11.3, 2.6.34.7-0.7-desktop, KDE 4.4.x, 3.0-P4, 2.5g mem. I replaced PATA-OEM optical drive with SATA-OEM works fine with all apps outside of and except with this widget. No problems until the swap. I have performed some updates and I have not put the PATA drive back in to see if the behavior changed because it was failing. It could be an update but the optical drive swap is my first suspect. This now. If I hover cursor over notifier widget icon "last plugged in device" will pop up with accurate last device until a click on the widget icon and selection of action for the recently plugged in device. Selected actions work fine ... once.
Then it no longer updates the new or retains the previous DVD/CD (or any USB external drive when connected) entry. Closing after viewing but with out selecting an action results in an empty list also. The menu remains empty there after and only removal of the widget and reinstall makes the devices appear again ... once. Then the behavior repeats if the widget is removed and reinstalled. I was wondering if this is likely to be a udev/rules.d problem related to the swap of the optical drives? The 70-persistant-cd.rules file shows two cd's after the swap:
[Code]...
If I delete or rename the 70-persistant-cd.rules file in udev/rules.d will it truly be recreated at boot and might it this fix the issue? Should I look elsewhere first at some var logs for errors? Reinstall 11.3 and let auto detect and config sort it out is also and option but I'd rather not, heh.
I've been playing with KDE's plasma desktop, getting things organization and such. For the most part, I really like it. I have one annoying problem. I'm not sure what it is called, but widgets have a component that slides out and allows you to configure, rotate, move, and close the widget. All is good, except I keep clicking the X and removing it. I have to open another folder view widget and configure it again. Argh! I know why I do it, in my head I'm thinking X closes this slider part (no it closes the widget!). The slider part is kind of sticky and sometimes I want it to close ASAP..., and that X is just staring at me :-) It is further complicated by the close on a Panel's settings. If I click the cashew on the TaskManager panel, a part slides out so I can configure the TaskManager panel, and to close it I can click the cashew again, or the little "x" in the red box. The panel isn't removed, just the part that slides out is closed. Unfortunately, "x" on the panel and "x" on a widget means two different things.
Has anyone run into a KDE configuration option to disable the close on a widget? I know if I lock all widgets the slider part is gone, and I do lock them. But, there are certain widgets that are too important and you just want to set them up, leave them alone, and adjust them as necessary.
Also, has anyone changed the defaults for widgets in the Add Widgets Dialog? If so, where is that done? I'd like the Folder View widget to always have specific icon settings, text settings, icon arrangement, so when I actually add the widget they are already set the way I need them for 90% of the cases.
If I suspend this toshiba satellite, and the battery is or gets low it will wake from suspend to tell me that it will need to suspend due to a critical low battery. Which is pretty dumb. I've experimented with this by plugging and unplugging the ac adapter.
View 1 Replies View Related3 questions i have about "pm-suspend-hybrid"
1. is it possible to schedule this command in the same manner as shutdown ? eg sudo shutdown -h 60
2. is it possible to schedule the laptop to come out of suspend ?
3. i have a usb sound card (xfi go). when waking from suspend, the internal sound card is selected. i have to manually select the external sound card & for whatever reason, also unmute it too
I created a thread about a problem a I had with my hard disk clicking whilst idle little while ago and I may now have stumbled upon a possible solution. The strange thing with the problem is that Ubuntu/Kubuntu didn't cause this problem but Opensuse 11.2 does.
I installed Fedora 13 to have a glimpse of what all the fuss was about and noticed that I had the same problem (hard disk clicking whilst idle ~ every 20 secs or so). Now there's a wiki on this subject and a few bug reports: [url]
Problem Description
Some ATA harddrives perform very frequent head unloads under Linux significantly shortening their lifespans. Root cause
The inactivity timer for head unload is configured too aggressively either via ATA APM (Advanced Power Management) feature or other non-standard means. Such aggressive settings are very fragile to changes in IO pattern and under Linux many such drives unload their heads only to re-load them shortly. Note that this relentless unloading/reloading cycle can also be triggered under Windows by installing programs which can alter the IO pattern (e.g. certain vaccine programs which runs in background).
Now two of the listed models with this problem are basically identical to my model (Dell Inspiron 1520) and basically share the same hardware: Dell Vostro 1500 and XPS 1520.
The workaround listed is to:
set APM to 254
Furthermore, there is a script: Storage-Fixup which can also be downloaded from opensuse software search. Indeed there is a report of this for a Vostro 1500: Gmane Loom
The report suggests looking at: Disk Power Management - openSUSE which lists a method to create a configuration file to management disk power management:
My question is whether I could download the storage-fixup rpm [url] has a description of it and it can be found: Software.openSUSE.org) and install it to (hopefully) solve the issue or should I follow the method given in: Disk Power Management - openSUSE
to set APM to 254:
Code:
My dual proc, dual core Opteron MSI Master2FAR motherboard failed, and I try to boot a disk, used on this board as boot disk, on an Intel based Gigabyte GA-965-DS3. Both systems are x86_64 architecture.
The OS is on both systems is openSUSE 11.1.
On booting the disk on the Gigabyte, the disk is seen correctly by the BIOS, but not by the OS, and there is no /dev/sdX; no /dev/disk/... either. I am taken to a login shell from the ramdisk.
When I just mount this disk on the Gigabyte (booted with the Gigabyte's original boot disk) everything seems fine. No suprise to me, since the disk was fine, and was unmounted gracefully and physically taken off the MSI before the board failed.
I think that the cause lies in the fact that the harddisk controller on the Gigabyte is different from the MSI, and the driver for that controller is not available at boot time.
I have two questions:
- is my assumption correct, or is something else going on?
- if I am right, is there a way to get this disk booting on the Gigabyte (or on another system, for that matter)?
You might want to ask why I want to boot this disk on the Gigabyte in the first place, since I can mount it and see all data on it. I have a reason for that, but telling that story would make this topic too long, and it's too off-topic. Most certainly I will get to that in another topic.
I just upgraded my AMD64 Phenom X3 on Asus M3A76-CM mobo from OpenSuSE 11.1 to OpenSuSE 11.2. The upgrade didn't go smooth, but it went through after some glitches. I posted this from the system running OpenSuSE 11.2. The problems I have encountered are the system crashed when I tried to Suspend to RAM and/or Disc. The display just showed the Penguin sideway with the bar went down to about 85%. BTW, why shows a Penguin sideway when the system is suspended to RAM/Disc? If one wants to show a Penguin sleeps, it should be standing and not laid sideway.
View 9 Replies View RelatedI have a 11.3/KDE4.5.2 desktop that I plan to use as a media server, connected to an HDTV/HDMI display and receiver(for audio).I frequently connect to it from another PC (also 11.3/KDE4.52) using any of the following:ssh for a CLI sessionvncXWindows application on a Windows machineI have suspend up and running (suspend to ram) but I am only able to initiate it from the local console.Is there a way to enable Suspend via any (or all) of the above remote connections?
View 4 Replies View RelatedThis isn't the biggest deal in the world, but I would like to know how to suspend to ram with qdbus in order to make a shortcut. I used to (11.3) do: qdbus org.kde.kded /modules/powerdevil suspend 2 and make the shortcut meta S. Now in 11.4 if I manually type it into terminal qdbus says it cannot find .suspend in /modules/powerdevil at org.kde.kded. Did something change in 11.4? I also tried accessing it from org.kde.Solid.PowerManagement to no avail.
View 3 Replies View RelatedI've upgraded 4 boxes (32- and 64-bit) from Suse 11.1 to 11.2 with no unresolvable issues. Now I'm stuck with my 5th box, a Dell Dimension 8400 desktop box (yes, an old brick, 32-bit). I can suspend to RAM ("suspend") and to disk ("hibernate") fine, but resume seems to fail. In Suse 11.1 I used kpowersave (GUI in the sys tray) to suspend to RAM. For some reason, it couldn't suspend to disk but that didn't bother me. kpowersave relies on the powersaved running.
Note I had upgraded my 11.1 installation to all shiny and new KDE 4.3 stuff, and while KDE 4.3 seems not to use powersaved (and thus kpowersave) all worked fine. Upgrading to 11.2 has removed kpowersave and powersaved. I don't mind switching to another way if only I could find documentation what's being used on KDE 4.3 (and/or Suse 11.2). All I find by googling is that the daemon used is powerdevil, and that I should use a GUI for suspending (this battery monitoring plasma app).
Well, if I do that on this box it simply does -- nothing. So I tried s2ram and a2disk directly:Running s2ram with the --force option works, but the box doesn't resume. Goes on, screen stays blank, mouse and keyboard don't work. s2disk complains about not being able to "stat the resume device file". I gave it the --resume_device /dev/sda6 option, and it hibernated fine. But it doesn't resume. Pressing the power on button just starts Suse anew (and recovers the file system journals, so I assume it thinks it has crashed before).
So I think I have 2 questions:
What the heck does Suse 11.2 use for suspend/hibernate and resume? Is there any how-to available to learn what I need to configure?
Why can't I resume from successful s2ram or s2disk operations? /var/log/pm-suspend-log or pm-powersave-log don't provide any clues.
I have a Toshiba Satellite A300, and a have tried 10.3 live cd.After the boot I can't use the hotkeys by FN key, and the CPU fan isn't run althought 100%cpu usage.After suspend and resume, CPU fan starts immediatly and hotkeys are worksMy question is, how can I find the command which runs after resume, what fix ACPI problems?
View 1 Replies View RelatedSuspend "appears" to be working for me but not quite:1) the screen says "done" (3 lines of text) appear2) the screen never shuts down, nor does the "done" messages disappear3) it returns from suspend by both keyboard activity and the power button4) the pc doesn't go silent, some fans or something still making sound 5) the pc power light blinks indicating suspensionActually the pc doesn't really suspend as not only do fans run but the optical drives open and appear to read (based on blinking lights)In 11.3 suspending seemed to actually suspend and hitting the power seemed to bring it out of sleep but the monitor never came back on (indicator light displayed off color) so the suspend functionality was useless
View 9 Replies View RelatedIs there anyone who can give a few pointers on how to go about controlling the Suspend/Wake process e.g. by using hooks. I know there are a few support pages on the site that refer to this but when it come to the details they are not as clear as they might be for someone new to Linux. (I assume that since 11.2 uses pm-utils the Powersave Project is not relevant to me, for example).Also any tips on restarting PCMCIA card services would be appreciated. Do I need to install pcmciautils?
View 4 Replies View RelatedFirstly, wol works fine from shutdown and hibernate; it's just suspend which doesn't work.
I've got 2 types of workstations, all running 11.1. They both have this kernel:
2.6.27.45-0.1-default #1 SMP 2010-02-22 16:49:47 +0100 x86_64 x86_64 x86_64 GNU/Linux
Type 1 is a dell optiplex 745, bios version 2.4.1. Here's the relevant bit from lspci:
03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5754 Gigabit Ethernet PCI Express (rev 02)
Kernel driver in use: tg3
Kernel modules: tg3
[Code]....
The fact that it's happening across two different machines makes me wonder if it is some OS setting I've missed, but then maybe neither card/driver supports it from suspend.
I'd really like to get them waking from suspend because training users to use suspend rather than hibernate would be a pain. Also, being able to configure such that it only wakes from suspend and not hibernate/shutdown, as implied in the bios, would allow me to wake machines up for backups etc only when the users are here, rather than on holiday/seconded to another department etc.
I'm running openSUSE 11.2 on a Thinkpad T61p with nvidia graphics. I'm running the proprietary nvidia driver.The battery ran very low and the computer suspended itself. After I woke it up, the desktop is completely black.After troubleshooting as much as I could, I did ctrl-alt-backspace, which brought me to a normal (non-black) login screen. However, as soon as I logged in, I was back to a completely black screen. But the system is operating.I rebooted the computer (warm reboot as well as cold restart) and each time the video is normal until I get to the desktop and all I get it black.Everything was normal until the pm suspend.Suspend has never worked exactly right, so I don't normally use it. But in this case, it used itself Next step: I logged in to console mode and looked at the logs. The only messages of interest seem to be in Xorg.0.log I found a couple error messages that might be of interest:
(II) LoadModule: "nouveau"
(WW) Warning, couldn't open module nouveau
(II) UnloadModule: "nouveau"
[code]....