#21 2017-08-01 12:16:26

Temetka

Member

From: Sol System, Western Spiral Arm

Registered: 2015-10-14

Posts: 549

Re: Lenovo Laptops, T vs X?

There are detailed info about Powertop and tlp in threads here. In the end I opted for laptop-mode-tools with powertop.

@HoaS I'm not sure why, but that srobb.net link with multiboot just does not work for me.

Thanks for this. Using the tlp thread I was able to determine that my bluetooth was on. Which is something I've known and was looking for a way to turn it off, then I could write it to an autorun command (if needed) and kill it everytime the system is booted. Then a thought hit me. "Hey Mr. Smart Guy, go into your BIOS and disable it."

Done and done. No more battery drain for a device I never use. Next time I open the system to repaste the CPU and replace the palm rest (small crack) and keyboard (to get backlight as this one doesn't have it), I am going to physically remove the card. Then I won't have to worry about it drawing power and/or being a potential security risk.

---

The meaning of life is to just be alive. It is so plain and so obvious
    and so simple. And yet everybody rushes aroound in a great panic
             as if it were necessary to achieve something beyond themselves.
                                                                                                             - Alan Watts

Head_on_a_Stick

Member

From: London

Registered: 2015-09-29

Posts: 9,093

Website

Re: Lenovo Laptops, T vs X?

unless there some magic garbage collection for SSDs in blk-mq that I am unaware of

The multiqueue block layer removes a bottleneck in the Linux I/O system, it has nothing to do with garbage collection.

The advantages only really become noticeable with NVMe drives but the paradigm is clearly superior to the antediluvian schedulers used in a stock BunsenLabs system.

that srobb.net link with multiboot just does not work for me

Try allowing the expired certificate (if your browser will let you).

The method is simple really: just free up some blank space on your drive and then create an OpenBSD disklabel [1] there; accept the default options in the OpenBSD installer, it should ask to use the OpenBSD area of the disk rather than the whole drive.

If you are installing a UEFI system then you need a GUID partition table (GPT) and gdisk should be used to create the OpenBSD disklabel, the partition code needed is a600

For non-UEFI systems (msdos partition table), use the `fdisk` command (from the util-linux package) with a6 as the partition code.

Once the system is installed, add the custom stanza (see the FAQ for a non-UEFI entry and my linked daemonforums post for UEFI) to /etc/grub.d/40_custom and update the GRUB configuration to generate a menu entry.

[1] A "disklabel" is sort of like a Linux partition but it can be divided up into sub-partitions called "slices".

http://man.openbsd.org/disklabel.5

Last edited by Head_on_a_Stick (2017-08-01 20:38:56)

---

Para todos todo, para nosotros nada