LXQt suspend not working [solved]

[francois]

You really have an irreverent style. Don't you? 8)

[brokenman]

Here it is officially. Moderators and ONLY moderators should mark threads as FAA. That is what we requested them to do. That is the work flow we have chosen. If users begin marking their own threads FAA when they feel like it we will remove the ability to edit threads. Enough said.

[Ed_P]

You really have an irreverent style. Don't you? 8)

I would refer to it as being honest and direct. Though I have been criticized for being blunt at times. I try to add humor, like the beer cans comment.

Here it is officially. Moderators and ONLY moderators should mark threads as FAA. That is what we requested them to do. That is the work flow we have chosen.

Ok but there needs to be a way for non-mods to flag a thread for admin review. Maybe AAP (Admin Attention Please) would do.

If users begin marking their own threads FAA when they feel like it we will remove the ability to edit threads. Enough said.

Ok but then you will have to have fanthom change his sig line because users won't be able to add {Solved} to their threads either. Regardless users can still PM and Email admins to get their attention when needed.

[brokenman]

Ok but there needs to be a way for non-mods to flag a thread for admin review.

No there doesn't. This is why we have moderators. We are handing the forum to the community which means experienced users will answer questions. If the problem can not be resolved then moderators will mark it as FAA and we will pick it up. This is the system we have chosen in order to better utilize time. Sorry if this is not convenient for you but it is the best we can do right now.

[Ed_P]

How does one convert a new 3.19 tar.xz kernel to a 000-kernel.xzm format? Is there a Porteus command for doing that?

[brokenman]

No. It is a kernel source file. You need to compile the kernel, and then update the 000-kernel.xzm module with the new drivers. This is only for advanced linux users. There is documentation on the website.

http://www.porteus.org/tutorials/20-dev ... ernel.html

[Ed_P]

This is only for advanced linux users.

hmmmm Yeah, I don't think I qualify as an "advanced linux user". I barely qualify as a beginner linux user.

There is documentation on the website.

http://www.porteus.org/tutorials/20-dev ... ernel.html

An impressive link, very detailed. And scary:

"WARNING: after upgrading, all kernel dependent Porteus modules like VirtualBox or proprietary GPU drivers will need to be recompiled against the new kernel version too."

Sounds like an all day job.

Is it reasonable to assume the next kernel change for Porteus will be in December when 3.2 is released? I noticed on the kernel.org site no reference to the 3.17.x kernel Porteus 3.1 is using.

[fanthom]

Is it reasonable to assume the next kernel change for Porteus will be in December when 3.2 is released?
could be earlier but cant say that for sure. i see no point for another Porteus release (4th one) based on Slackware-14.1. lets wait till new slack is out, check what it brings (KDE5 maybe?) and then create Porteus based on it.

[Ed_P]

Porteus release (4th one) based on Slackware-14.1.

I not sure I understand. (nothing new) Slackware 14.1 according to this link: http://www.slackware.com/announce/14.1.php uses the 3.10.17 kernel. Porteus 3.1 is using the 3.17.x kernel so it didn't come from Slackware 14.1, again according to my understanding of what I have read. Could there be a kernel update to Porteus without doing a whole new release? A 000-kernel_alldesktops-15mmdd.xzm module that includes kernel 3.18? Or 3.19? Or a mini Porteus 3.1.1 update release like 3.0.1 was?

[fanthom]

Could there be a kernel update to Porteus without doing a whole new release?
rather not:
a) updates system supports pushing items to /porteus/base and not /boot/syslinux folder (because we cant know for sure from which location kernel was loaded and updating 000 only breaks the system)
b) we have no guarantee that new kernel resolves your problem
c) i'm not going to prepare new kernels when single user has an issue

solution:
if older kernel works for you - just stick to it.

[Ed_P]

Ok.

Thanks fanthom.

c) i'm not going to prepare new kernels when single user has an issue.

Understood. And rather surprised no one else has encounter this.