You are not logged in.
Can you help me please?
I´m new user of Q4OS (old user of Windows XP). Can you explain it step by step?
Q4OS OS has been installed correctly.
The problem comes when the OS enters in hibernation in few minutes. I press space key and return to the OS correctly, and in a minute again goes into hibernation. And again, again, ...
Thanks! Regards.
Offline
Do you have tdepowersave installed?
Where is it exactly?
If you installed Q4OS with a minimal install it may be missing versus a full desktop profile install.
I chose the classic installation. I have it properly installed?
I actually had the same issue with my older laptop but once I installed the full desktop profile which included the tdepowersaver the issue went away when I rebooted.
Do you have to configure?
Thanks!
Offline
Can you help me please?
Install 'tdepowersave-trinity' package using Synaptic package manager or from terminal:
$ sudo apt-get install tdepowersave-trinity
Offline
The minimal install may be part of the problems I am having with my laptop. I tried selecting the other two choices but it reported that I didn't have the hardware for them, so I defaulted to minimal. I have ordered a usb nic and a usb sound card, when I get them I will try again. It isn't that much trouble to do a full install and delete what is there.
Offline
The minimal install may be part of the problems I am having with my laptop. I tried selecting the other two choices but it reported that I didn't have the hardware for them, so I defaulted to minimal.
We would recommend to install the 'Basic' profile. It's very solid desktop base, eats less space from disk and keeps your computer very light, even though it brings all the necessary desktop libraries, codecs and packages. So you have option to install desktop applications by your choice.
'Desktop' profile adds end user applications like web browser, office suite and others. If the Basic profile will not suite your wishes, you will be able whenever install Desktop profile over.
Offline
Right crosscourt!
I'm still waiting for the usb nic and sound cards, but when I get them I'll do a new install with the full desktop profile. With a 40 Gig hard drive a few megs ain't gonna make much difference!
Offline
I, too, am having a problem with Hibernate (Suspend to Disk). I have a laptop with 8GB ram, and a /Swap partition with about 8.5 GB allocated. I have TDEPowersave installed, but it shows the Suspend to Disk entry grayed out. The Suspend to RAM works OK, and Freeze sort of works (very hard to get the laptop to exit from Freeze, must press various keys multiple times, quickly). But Suspend to Disk is not available, nor is it shown on the Start menu's Log Out... menu.
Any suggestions as to how to troubleshoot this problem? Multiple internet searches have left me a couple of hours in the hole, with no solution that works.
Thanks in advance.
aboutblank
December 16, 2015
Offline
Agree, you could report it at TDE https://bugs.trinitydesktop.org/buglist … search=ALL
Offline
Regarding my hibernation problem, I did note that I am getting an error message on each boot that states:
"A start job is running for dev-disk-by\x2dpartuuid-3ac2a839\x2d08.device ( xx seconds / 1 min 30 sec)"
where 'xx' is a counter that increments until it reaches 1 min 30 seconds, then time out, and the boot continues. I wonder if that is somehow the cause of the lack of the Hibernation option?! Perhaps a disk related problem on one of the three Linux partitions (root, home, or swap) is telling the system not to allow Hibernation?
So, I am not certain that I should submit a bug report just yet, if I have a disk problem.
I tried setting up a fsck disk check to be run on reboot using the command:
"/sbin/shutdown - r -F now"
in a root Konsole window, but got the following error message:
"Code should not be reached 'Unhandled option' at ../src/systemctl/systemctl.c:6316, function shutdown_parse_argv(). Aborting.
Aborted"
Any insights as to the cause of this error message, or how else to proceed, would be appreciated! Thanks!
aboutblank
December 17, 2015
Last edited by aboutblank (2015-12-18 03:34)
Offline
fsck is run by default every time you start or restart Q4OS, at least on my systems....
... i have both new and old hardware all running with hibernation options.Q4OS team will hopefully have a suggestion for you.
Thanks for the reply! I'll give it a couple of days, and submit a bug report if necessary.
aboutblank
December 17, 2015
Offline
A start job is running for dev-disk-by\x2dpartuuid-3ac2a839\x2d08.device ( xx seconds / 1 min 30 sec)
Looks more like a hardware related issue. If you want to get an assistance, run command in terminal:
$ sudo journalctl --no-pager --all | gzip > jrctl.log.gz
and attach 'jrctl.log.gz' file here to analyze. We will be able to check your ACPI hardware and systemd/hibernation capabilities too.
As crosscourt noted, fsck is ran by default every time you start Q4OS, but it's forced only if ext4/filesystem journal file has been disrupted. If you want to pass forced complete data integrity check on the next boot, you have to create emtpy '/forcefsck' file:
$ sudo touch /forcefsck
The other way is to boot from live media, make sure the drive is unmounted and run:
$ sudo fsck -f /dev/sdnx
where sdnx is the drive, for example sda1.
Offline
I have had this problem when changing partitions on hdd, If the partition is set to be automounted in fstab but cannot be found. What I do is check the available partitions with
sudo blkid
This will list all partitions
and then
cat /etc/fstab
to see which partitions are mounted at boot time.
If there is a partition in fstab that is not in the output from blkid it will need to be removed. You can just put a hash at the beginning of the line to comment it out.
Hope this helps
Dai
Offline
Thanks for the suggestions, I will sort through them and report back.
My hardware summary is as follows: Dell Inspiron Laptop Model 3520 with 500GB hard drive and 8GB RAM.
I have attached a text file to this message with a much more detailed summary of my hardware.
Thanks for all your help!
aboutblank
December 18, 2015
Offline
I have had this problem when changing partitions on hdd, If the partition is set to be automounted in fstab but cannot be found. What I do is check the available partitions with
sudo blkid
This will list all partitions
and thencat /etc/fstab
to see which partitions are mounted at boot time.
If there is a partition in fstab that is not in the output from blkid it will need to be removed. You can just put a hash at the beginning of the line to comment it out.
Hope this helpsDai
Thanks for the tip. I tried those commands, and got this output, which raises a couple of questions:
root@q4oslaptop:~# blkid
/dev/sda1: LABEL="System Reserved" UUID="A862F2AB62F27CFE" TYPE="ntfs" PARTUUID="3ac2a839-01"
/dev/sda2: LABEL="DRIVE_C" UUID="01D11393987E7680" TYPE="ntfs" PARTUUID="3ac2a839-02"
/dev/sda5: LABEL="DRIVE_D" UUID="01D1139399170D00" TYPE="ntfs" PARTUUID="3ac2a839-05"
/dev/sda6: UUID="0f621593-d2ef-4de0-8756-c2b5fab2037a" TYPE="ext4" PTTYPE="dos" PARTUUID="3ac2a839-06"
/dev/sda7: UUID="c2b75797-ee3b-4939-aa97-3ca57cd779a5" TYPE="ext4" PARTUUID="3ac2a839-07"
/dev/sda8: UUID="646eda77-677f-42f6-b9dc-57123c18ee10" TYPE="swap" PARTUUID="3ac2a839-08"
/dev/sdb1: SEC_TYPE="msdos" LABEL="512MBSDCARD" UUID="FC30-3DA9" TYPE="vfat" PARTUUID="7405f335-01"
root@alq4oslaptop:~# cat /etc/fstab
# UNCONFIGURED FSTAB FOR BASE SYSTEM
proc /proc proc defaults 0 0
# /dev/sda6
UUID=0f621593-d2ef-4de0-8756-c2b5fab2037a / ext4 rw,errors=remount-ro 0 1
# /dev/sda7
UUID=c2b75797-ee3b-4939-aa97-3ca57cd779a5 /home ext4 rw,errors=remount-ro 0 0
# /dev/sda8
PARTUUID=3ac2a839-08 swap swap sw 0 0
First thing I noticed, sda6 has PTTYPE="dos" in it's description, but sda7 doesn't. Both are ext4 partitions, so I don't know where that "dos" is coming from, and wonder if it is part of my problem with lack of Hibernation?!
Second, I noticed that PARTUUID=3ac2a839-08 identifies my swap partition, sda8. The message I get on the 'start job' that slows down the boot for 90 seconds before it times out does not contain the full descriptor, lacking the '-08' at the end, i.e.:
"A start job is running for dev-disk-by\x2dpartuuid-3ac2a839\x2d08.device ( xx seconds / 1 min 30 sec)"
So, I wonder if this is an error that is causing the delay, and whether it's responsible for the lack of Hibernation. (Presumably, if the OS thinks that the swap partition is somehow corrupted, perhaps it automatically won't use it, and won't enable 'Suspend to Disk' because of it?!) (I see that in the FSTAB table, the swap partition is identified only by the 'PARTUUID', but that PARTUUID's in the output for blkid above it all contain "3ac2a839", so maybe that's a red herring, only identifying the disk as opposed to the partition?)
Third, I wonder what the "1" indicates at the end of the FSTAB output for sda6, i.e. "rw,errors=remount-ro 0 1", instead of
"rw,errors=remount-ro 0 0", as for sda7?!
Thanks for anyhelp with the above!
aboutblank
December 18, 2015
Last edited by aboutblank (2015-12-19 00:59)
Offline
You could try putting the full UUID label as the identifier in fstab, I don't know if this will solve the problem but it would make your fstab more uniform and rule that out as a problem.
And the 1at the end of the fstab entry is to tell fsck that it is the main partition for checking so it is ok to leave that as it is.
Last edited by Dai_trying (2015-12-19 01:06)
Offline
Thanks, Dai_trying, I'll give that a shot!
aboutblank
December 18, 2015
Offline
Well, I'm happy to report some progress! I took Dai_trying's advice, and replaced PARTUUID with the full UUID for sda8 (swap partition) in fstab, and rebooted. Lo and behold, no longer a 90 second time-out, very snappy boot-up time, and now the 'Suspend to Disk' option is available in both the 'start' menu and the TDEPowersaver applet in the tray! That's the good news.
The bad news is that Suspend to Disk doesn't work. When I click on it (in either the 'start' menu or in TDEPowersaver), the screen flashes and goes blank, then the power goes off, all within about 2 seconds. There is apparently no write to disk, as upon reboot, it goes into the full boot through the Windows boot process (I don't use grub in the Master Boot Record - could that be the problem??!). When I select the Q4OS boot option from the menu, it shows that it is cleaning up 'inode' problems, four of them the first time, and eight of them the second time I tried it.
So, I'm still experiencing problems. Anything obvious I'm missing? Or, should I take q4osteam's advice, above, and run
journalctl --no-pager --all | gzip > jrctl.log.gz
and submit the gz file for analysis?
Thanks!
aboutblank
December 18, 2015
Offline
Here's the file jrctl.log.gz from
journalctl --no-pager --all | gzip > jrctl.log.gz
attached to this message.
aboutblank
December 18, 2015
Offline
One more thing I would try is changing the type on your sda6 partition to ext4, all mine are of the expected type so it's a definite maybe.
Dai
Offline
One more thing I would try is changing the type on your sda6 partition to ext4, all mine are of the expected type so it's a definite maybe.
Dai
Thanks, Dai. I played around with your suggestion, changing the type to ext4 and mode (?) to rw (instead of sw), but the menu entry for 'Suspend to Disk' was gone again. I changed the 'rw' back to 'sw', but same result. Changed the type back from ext4 to 'swap', and it came back, but clicking on it produced same result, screen went blank, then came back on, then power off. On resume, same four 'orphaned inodes' when going through full reboot.
aboutblank
December 18, 2015
Offline
sorry my bad, the PTTYPE is shown in blkid listing not in fstab...
Did you allow the installation process to format sda6 when you installed? I ask this as my partitions do not have this set and was wondering if something failed to run properly...
Dai
Offline
Did you allow the installation process to format sda6 when you installed?
I created the three Linux partitions (root, home, swap) with a Windows tool called Minitool Partition Wizard 9.1. I selected ext4 as the format type, and that's what's reported by Minitool and by GParted. I'm not certain if Minitool actually formatted the partitions (as opposed to only labeling them as ext4), but I think it did, and when I installed Q4OS, I used the Q4OS installation process to mark the Linux partitions so that they would be formatted. The process of formatting never seems to take very long when preparing ext4 partitions (unlike formatting a disk under Windows), so I'm not sure exactly what takes place when an installation routine indicates it is formatting a partition.
The installation seems to work fine (except for Suspend to Disk), so I rather think that the format method is not affecting it. Perhaps the format is different for the swap partition, enough to prevent hibernation, or other use of it?
aboutblank
December 19, 2015
Offline
it doesn't look like the swap is wrong now, although I would check it by typing "free" in a console the results would look something similar to this :-
total used free shared buffers cached
Mem: 4108668 1098868 3009800 87316 50904 776828
-/+ buffers/cache: 271136 3837532
Swap: 4194300 0 4194300
The last line tells me my swap is on and approx 4gb in size and the 0 means none is currently used.
Dai
Offline
Thanks, Dai. Here's my 'free' output:
total used free shared buffers cached
Mem: 8057944 1732080 6325864 115144 68128 1202624
-/+ buffers/cache: 461328 7596616
Swap: 9083900 0 9083900
Looks OK to me.
aboutblank
December 19, 2015
Offline
Yea, looks ok to me. I don't think i can help any further really, maybe support@q4os.org can help.
Dai
Offline