Date: Wed, 04 Feb 2015 04:14:49 -0500 Subject: Documentation: implement theme, drastically improve readability --- (limited to 'docs/misc') diff --git a/docs/misc/index.html b/docs/misc/index.html index f4e7836..a4e0aba 100644 --- a/docs/misc/index.html +++ b/docs/misc/index.html @@ -13,74 +13,82 @@ -

Miscellaneous

- Or Back to main index. -

High Pitched Whining Noise on Idle (how to remove in Trisquel) -
- Powertop - how to use
- Powertop - Start automatically at boot time
-
High Pitched Whining Noise on Idle (how to remove in Parabola)
X60/T60: Serial port - how to use (for dock owners)
Using diff and patch
Get EDID: Find out the name (model) of your LCD panel

- -

High Pitched Whining Noise on Idle (how to remove in Trisquel)

Miscellaneous

+ Or Back to main index. +

High Pitched Whining Noise on Idle (how to remove in Trisquel) +
- Powertop - how to use
- Powertop - Start automatically at boot time
+
High Pitched Whining Noise on Idle (how to remove in Parabola)
X60/T60: Serial port - how to use (for dock owners)
Using diff and patch
Get EDID: Find out the name (model) of your LCD panel

- Tested in Trisquel 6 and 7. -

Powertop - how to use

High Pitched Whining Noise on Idle (how to remove in Trisquel)

Now you can use this command to kill that noise:
- $ sudo powertop --auto-tune

+ Tested in Trisquel 6 and 7. +

You can also run it without parameters and then go into 'Tunables' and set everything to 'Good'

Powertop - how to use

Note: On Trisquel 6, you will need to use a later powertop version from git. The one in the repositories is too old. See below:

Now you can use this command to kill that noise:
+ $ sudo powertop --auto-tune

Powertop - Start automatically at boot time (Trisquel 6)

You can also run it without parameters and then go into 'Tunables' and set everything to 'Good'

Included with libreboot is a script called 'powertop.trisquel6'. Run this and it will setup powertop to run with --auto-tune - at boot time. Load the file in your text editor to see how it does that.

Note: On Trisquel 6, you will need to use a later powertop version from git. The one in the repositories is too old. See below:

$ ./powertop.trisquel6

Powertop - Start automatically at boot time (Trisquel 6)

For Trisquel 7 users:

$ ./powertop.trisquel7

Included with libreboot is a script called 'powertop.trisquel6'. Run this and it will setup powertop to run with --auto-tune + at boot time. Load the file in your text editor to see how it does that.

$ ./powertop.trisquel6

For Trisquel 7 users:

$ ./powertop.trisquel7

High Pitched Whining Noise on Idle (how to remove in Parabola)

+ +

The following removes most of the noise. It reduces what is a high frequency whine - (that not everyone can hear) to a slight buzz (which most people can't hear or doesn't bother most people).

This is not perfect! The full solution is still not discovered but this is a step towards that. - Also, in some instances you will need to run 'sudo powertop --auto-tune' again. - This needs to be implemented properly in coreboot itself!

High Pitched Whining Noise on Idle (how to remove in Parabola)

On the X60 with coreboot or libreboot, there is a high pitched sound when idle. - So far we have use processor.max_cstate=2 or idle=halt in GRUB. - These consume power. Stop using them!

The following removes most of the noise. It reduces what is a high frequency whine + (that not everyone can hear) to a slight buzz (which most people can't hear or doesn't bother most people).

Be root
- $ su -

This is not perfect! The full solution is still not discovered but this is a step towards that. + Also, in some instances you will need to run 'sudo powertop --auto-tune' again. + This needs to be implemented properly in coreboot itself!

Installed powertop:
- # pacman -S powertop

On the X60 with coreboot or libreboot, there is a high pitched sound when idle. + So far we have use processor.max_cstate=2 or idle=halt in GRUB. + These consume power. Stop using them!

and added the following to /etc/systemd/system/powertop.service :

Be root
+ $ su -

+ +

Installed powertop:
+ # pacman -S powertop

+ +

and added the following to /etc/systemd/system/powertop.service :


 [Unit]
@@ -98,85 +106,93 @@ WantedBy=multi-user.target

Finally, as root do that:
- # systemctl enable powertop
- # systemctl start powertop

- -

The next time you boot the machine, the buzz will be gone.

- -

Finally, as root do that:
+ # systemctl enable powertop
+ # systemctl start powertop

+ +

The next time you boot the machine, the buzz will be gone.

+ +

X60/T60: Serial port - how to use (for dock owners)

+ For the Thinkpad X60 you can use the "UltraBase X6" dock (for the X60 Tablet it is called + X6 Tablet UltraBase). For the ThinkPad T60, + you can use the "Advanced Mini Dock". +

+ If you are using one of the ROM images with 'serial' in the name, then you have serial port enabled in libreboot + and you have memtest86+ included inside the ROM. Connect your null modem cable to the serial port on the dock + and connect the other end to a 2nd machine using your USB Serial adapter. +

+ On the 2nd machine, you can try this (using GNU Screen):
+ $ sudo screen /dev/ttyUSB0 115200 +

+ How to quit GNU Screen: Ctrl+A then release and press K, and then press Y. +

There are also others like Minicom but I like GNU Screen

+ By doing this before booting the X60/T60, you will see console output from libreboot. You will also see + GRUB displaying on the serial output, and you will be able to see MemTest86+ on the serial output aswell. + You can also configure your distro so that a terminal (TTY) is accessible from the serial console. +

+ The following guide is for Ubuntu, and can be followed for Trisquel 6.0 which is based on Ubuntu 12.04 + (should also work in Trisquel 7, based on Ubuntu 14.04) to enable a serial console using GeTTY:
+ https://help.ubuntu.com/community/SerialConsoleHowto +

+ Note: part of the tutorial above requires changing your grub.cfg. Just change the linux line to add instructions for enabling getty. + See ../gnulinux/grub_cbfs.html. +

+ +

Get EDID: Find out the name (model) of your LCD panel

+ Get the panel name with sudo get-edid | strings
+ Or look in /sys/class/drm/card0-LVDS-1/edid +

+ Alternatively you can use i2cdump. In Trisquel, this is in the package i2c-tools.
+ $ sudo modprobe i2c-dev
+ $ sudo i2cdump -y 5 0x50
+ $ sudo rmmod i2c-dev
+ You'll see the panel name in the output (from the EDID dump). +

+ If neither of these options work (or they are unavailable), physically removing the LCD panel is an option. + Usually, there will be information printed on the back. +

+ +

- -

X60/T60: Serial port - how to use (for dock owners)

- For the Thinkpad X60 you can use the "UltraBase X6" dock (for the X60 Tablet it is called - X6 Tablet UltraBase). For the ThinkPad T60, - you can use the "Advanced Mini Dock". -

- If you are using one of the ROM images with 'serial' in the name, then you have serial port enabled in libreboot - and you have memtest86+ included inside the ROM. Connect your null modem cable to the serial port on the dock - and connect the other end to a 2nd machine using your USB Serial adapter. -

- On the 2nd machine, you can try this (using GNU Screen):
- $ sudo screen /dev/ttyUSB0 115200 -

- How to quit GNU Screen: Ctrl+A then release and press K, and then press Y. + Copyright © 2014, 2015 Francis Rowe <info@gluglug.org.uk>
+ This document is released under the Creative Commons Attribution-ShareAlike 4.0 International Public License and all future versions. + A copy of the license can be found at ../license.txt.

There are also others like Minicom but I like GNU Screen

- By doing this before booting the X60/T60, you will see console output from libreboot. You will also see - GRUB displaying on the serial output, and you will be able to see MemTest86+ on the serial output aswell. - You can also configure your distro so that a terminal (TTY) is accessible from the serial console. -

- The following guide is for Ubuntu, and can be followed for Trisquel 6.0 which is based on Ubuntu 12.04 - (should also work in Trisquel 7, based on Ubuntu 14.04) to enable a serial console using GeTTY:
- https://help.ubuntu.com/community/SerialConsoleHowto -

- Note: part of the tutorial above requires changing your grub.cfg. Just change the linux line to add instructions for enabling getty. - See ../gnulinux/grub_cbfs.html. -

- -

Get EDID: Find out the name (model) of your LCD panel

- Get the panel name with sudo get-edid | strings
- Or look in /sys/class/drm/card0-LVDS-1/edid + This document is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See ../license.txt for more information.

- Alternatively you can use i2cdump. In Trisquel, this is in the package i2c-tools.
- $ sudo modprobe i2c-dev
- $ sudo i2cdump -y 5 0x50
- $ sudo rmmod i2c-dev
- You'll see the panel name in the output (from the EDID dump). -

- If neither of these options work (or they are unavailable), physically removing the LCD panel is an option. - Usually, there will be information printed on the back. -

- -

- Copyright © 2014 Francis Rowe <info@gluglug.org.uk>
- This document is released under the Creative Commons Attribution-ShareAlike 4.0 International Public License and all future versions. - A copy of the license can be found at ../license.txt. -

- -

- This document is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See ../license.txt for more information. -

+ +

diff --git a/docs/misc/patch.html b/docs/misc/patch.html index 3d926ac..681fdfb 100644 --- a/docs/misc/patch.html +++ b/docs/misc/patch.html @@ -6,7 +6,7 @@ @@ -17,147 +17,170 @@ <body> - <header> + <div class="section"> <h1 id="pagetop">Diff and patch</h1> - <aside>This is just a quick guide for reference, use 'man' to know more.</aside> - </header> - - - <a href="index.html">back to index</a> - - -<hr/> - - <h1> - Apply a patch - </h1> - - - To apply a patch to a single file, do that in it's directory: - $ patch < foo.patch - - - - Assuming that the patch is distributed in unified format identifying - the file the patch should be applied to, the above will work. Otherwise: - $ patch foo.txt < bar.patch - - - - You can apply a patch to an entire directory, but note the "p level". - What this means is that inside patch files will be the files that you - intend to patch, identified by path names that might be different - when the files ane located on your own computer instead of on the computer - where the patch was created. 'p' level instructs the 'patch' utility to - ignore parts of the path name to identify the files correctly. Usually a - p level of 1 will work, so you would use: - $ patch -p1 < baz.patch - - - - Change to the top level directory before running this. If a patch level - of 1 cannot identify the files to patch, then inspect the patch file for file names. - For example: - /home/user/do/not/panic/yet.c - - - - and you are working in a directory that contains panic/yet.c, use: - $ patch -p5 < baz.patch - - - - You usually count one up for each path separator (forward slash) - removed from the beginning of the path, until you are left with a path - that exists in the current working directory. The count is the p level. - - - - Removing a patch using the -R flag - $ patch -p5 -R < baz.patch - - - <a href="#pagetop">Back to top of page.</a> - -<hr/> - - <h1> - Create a patch with diff - </h1> - - - Diff can create a patch for a single file: - $ diff -u original.c new.c > original.patch - - - - For diff'ing a source tree: - $ cp -R original new - - - - Do whatever you want in new/ and then diff it: - $ diff -rupN original/ new/ > original.patch - - - <a href="#pagetop">Back to top of page.</a> - -<hr/> - - <h1> - git diff - </h1> - - - git is something special. - - - - Just make whatever changes you want to a git clone and then: - $ git diff > patch.git - - - - Note the git revision that you did this with: - $ git log - - - <a href="#pagetop">Back to top of page.</a> - -<hr/> - - <h1> - git apply - </h1> - - it really is. - - - Now to apply that patch in the future, just git clone it again and do - with the git revision you found from above: - $ git reset --hard REVISIONNUMBER - - - - Now put patch.git in the git clone directory and do: - $ git apply patch.git - - - <a href="#pagetop">Back to top of page.</a> - -<hr/> - - - Copyright © 2014 Francis Rowe <info@gluglug.org.uk> - This document is released under the Creative Commons Attribution-ShareAlike 4.0 International Public License and all future versions. - A copy of the license can be found at <a href="../license.txt">../license.txt</a>. - - - - This document is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See <a href="../license.txt">../license.txt</a> for more information. - + This is just a quick guide for reference, use 'man' to know more. + + <a href="index.html">Back to index</a> + + </div> + + <div class="section"> + + <h1> + Apply a patch + </h1> + + + To apply a patch to a single file, do that in it's directory: + $ patch < foo.patch + + + + Assuming that the patch is distributed in unified format identifying + the file the patch should be applied to, the above will work. Otherwise: + $ patch foo.txt < bar.patch + + + + You can apply a patch to an entire directory, but note the "p level". + What this means is that inside patch files will be the files that you + intend to patch, identified by path names that might be different + when the files ane located on your own computer instead of on the computer + where the patch was created. 'p' level instructs the 'patch' utility to + ignore parts of the path name to identify the files correctly. Usually a + p level of 1 will work, so you would use: + $ patch -p1 < baz.patch + + + + Change to the top level directory before running this. If a patch level + of 1 cannot identify the files to patch, then inspect the patch file for file names. + For example: + /home/user/do/not/panic/yet.c + + + + and you are working in a directory that contains panic/yet.c, use: + $ patch -p5 < baz.patch + + + + You usually count one up for each path separator (forward slash) + removed from the beginning of the path, until you are left with a path + that exists in the current working directory. The count is the p level. + + + + Removing a patch using the -R flag + $ patch -p5 -R < baz.patch + + + <a href="#pagetop">Back to top of page.</a> + + </div> + + <div class="section"> + + <h1> + Create a patch with diff + </h1> + + + Diff can create a patch for a single file: + $ diff -u original.c new.c > original.patch + + + + For diff'ing a source tree: + $ cp -R original new + + + + Do whatever you want in new/ and then diff it: + $ diff -rupN original/ new/ > original.patch + + + <a href="#pagetop">Back to top of page.</a> + + </div> + + <div class="section"> + + <h1> + git diff + </h1> + + + git is something special. + + + Note: this won't show new files created. + + + + Just make whatever changes you want to a git clone and then: + $ git diff > patch.git + + + + Note the git revision that you did this with: + $ git log + + + + Alternatively (better yet), commit your changes and then use: + $ git format-patch -N + Replace N with the number of commits that you want to show. + + + <a href="#pagetop">Back to top of page.</a> + + </div> + + <div class="section"> + + <h1> + git apply + </h1> + + it really is. + + + Now to apply that patch in the future, just git clone it again and do + with the git revision you found from above: + $ git reset --hard REVISIONNUMBER + + + + Now put patch.git in the git clone directory and do: + $ git apply patch.git + + + + If you use a patch from git format-patch, then use git am patch.git instead of git apply patch.git. git-am + will re-create the commits aswell, instead of just applying the patch. + + + <a href="#pagetop">Back to top of page.</a> + + </div> + + <div class="section"> + + + Copyright © 2014, 2015 Francis Rowe <info@gluglug.org.uk> + This document is released under the Creative Commons Attribution-ShareAlike 4.0 International Public License and all future versions. + A copy of the license can be found at <a href="../license.txt">../license.txt</a>. + + + + This document is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See <a href="../license.txt">../license.txt</a> for more information. + + + </div> </body> </html> -- cgit v0.9.1