https://wiki.archlinux.org/api.php?action=feedcontributions&user=Dundee&feedformat=atomArchWiki - User contributions [en]2024-03-29T06:11:36ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=ASUS_Zenbook_UM425&diff=665609ASUS Zenbook UM4252021-04-30T10:06:56Z<p>Dundee: </p>
<hr />
<div>[[Category:ASUS]]<br />
[[ja:ASUS Zenbook UM425]]<br />
{{Laptop style|Hardware table needs some adjustments, page is missing a proper function keys table}}<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status'''<br />
|-<br />
| AMD CPU || {{G|Working}}<br />
|-<br />
| Radeon GPU || {{G|Working}}<br />
|-<br />
| HDMI || {{G|Working}}<br />
|-<br />
| Wireless || {{G|Working}}<br />
|-<br />
| Audio || {{G|Working}}<br />
|-<br />
| Touchpad || {{Y|Partially working}}<br />
|-<br />
| Camera || {{G|Working}}<br />
|-<br />
| Card Reader || {{G|Working}}<br />
|-<br />
| Bluetooth || {{G|Working}}<br />
|-<br />
| Function keys || {{G|Working}}<br />
|-<br />
| Battery charge threshold || {{G|Working}}<br />
|-<br />
| Suspend to RAM || {{R|Not working}}<br />
|}<br />
<br />
== Configuration ==<br />
<br />
=== Secure Boot (option) ===<br />
In order to boot any Linux operating system, navigate to BIOS (hold F2 during power-on), then hit {{ic|F7}} or click on ''Advanced Menu'', then the ''Security'' tab and set ''Secure Boot'' to {{ic|Off}}.<br />
<br />
If the aforementioned ''Secure Boot'' option is a menu rather than an on-or-off option, click on ''Secure Boot'', ''Key Management'', then ''Reset to Setup Mode'' and confirm in the dialog.<br />
<br />
=== Video ===<br />
See [[ATI|AMD Graphics]] and [[Hardware_video_acceleration|Hardware Acceleration]].<br />
<br />
=== Audio ===<br />
See [[PulseAudio]].<br />
<br />
=== Touchpad ===<br />
See [[Libinput]].<br />
<br />
The NumPad is working with [https://github.com/mohamed-badaoui/asus-touchpad-numpad-driver asus-touchpad-numpad-driver] implementation from GitHub. Be sure to install {{Pkg|python-libevdev}} and {{Pkg|i2c-tools}} before starting [[systemd]]'s service, otherwise this script won't work.<br />
<br />
=== Battery charge threshold ===<br />
<br />
Battery charge threshold is working. Laptop's battery stops charging at certain percentage when value in {{ic|/sys/class/power_supply/BATT/charge_control_end_threshold}} is set to either {{ic|60}}, {{ic|80}}, or {{ic|100}}. But some power managing services, such as [[KDE]]'s {{pkg|powerdevil}} may report wrong charging status when battery threshold is set bellow {{ic|100}}. This is problem is floating, user may see {{ic|"Charging complete"}}, {{ic|"Not charging"}} as well as {{ic|"Charging"}}.<br />
In order to automatically change the value at boot, user can create the [[systemd]] service: refer to [[Laptop/ASUS#Battery charge threshold]]<br />
<br />
== Troubleshooting ==<br />
<br />
<br />
=== Suspend ===<br />
<br />
Suspend to RAM (s2idle) is not working correctly. The system is often frozen when trying to wake-up.<br />
<br />
== Tips and tricks ==<br />
<br />
=== Power saving and performance ===<br />
As advertised by ASUS, both laptops are capable to last up to 20 hours on battery. In order to achieve this, see:<br />
<br />
* BIOS update - It is generally recommended to update BIOS, as it usually brings performance, power-saving and security features.<br />
<br />
* [[Power Saving]] - List of general recommendations to increase battery life.<br />
<br />
* [[Improving performance]] - List of general recommendations to increase performance.<br />
<br />
* [[SSD]] - Tips and tricks for Solid State Drives. Both laptops ship M.2 SSD by default.<br />
<br />
* [[Undervolting CPU]] - Decrease voltage for Intel CPU (reduce battery drain, reduce heat and therefore - reduce fan speed)<br />
<br />
=== Extract Windows 10 license key ===<br />
<br />
The laptop comes with Windows 10 preinstalled and the activation key is hardcoded into the firmware. If you replace Windows with Linux, then hardcoded activation key is useless. You might want to extract it and use somewhere else (e.g. virtualized Windows 10):<br />
# grep -aPo '[\w]{5}-[\w]{5}-[\w]{5}-[\w]{5}-[\w]{5}' /sys/firmware/acpi/tables/MSDM<br />
<br />
{{Note|Microsoft online support confirmed that the code is valid, but because you are unable to activate it (Windows fails to activate and asks for another code), they offered 2 options - replace activation code with another one for 40$ or contact OEM (ASUS) about this issue.<br />
ASUS confirmed, that in order to "use" this activation key, you need to bring this laptop to repair service so they can "restore" system using ASUS OEM Windows 10 image. They do not provide this image for download.}}</div>Dundeehttps://wiki.archlinux.org/index.php?title=Package_Maintainer_guidelines&diff=652502Package Maintainer guidelines2021-02-15T12:54:12Z<p>Dundee: fixed link to pkgstats</p>
<hr />
<div>[[Category:Package development]]<br />
[[es:AUR Trusted User Guidelines]]<br />
[[ja:AUR Trusted User ガイドライン]]<br />
[[pt:AUR Trusted User Guidelines]]<br />
[[zh-hans:AUR Trusted User Guidelines]]<br />
{{Related articles start}}<br />
{{Related|Arch User Repository}}<br />
{{Related articles end}}<br />
'''Trusted Users (TU)''' are members of the community charged with keeping the AUR in working order. They maintain popular packages ([https://mailman.archlinux.org/pipermail/aur-general/2010-September/010649.html communicating with and sending patches upstream as needed]), and vote in administrative matters. A TU is elected from active community members by current TUs in a democratic process. TUs are the only members who have a final say in the direction of the AUR.<br />
<br />
The TUs are governed using the [https://aur.archlinux.org/trusted-user/TUbylaws.html TU bylaws]<br />
<br />
== TODO list for new Trusted Users ==<br />
<br />
# Read this entire wiki article.<br />
# Read the [https://aur.archlinux.org/trusted-user/TUbylaws.html TU Bylaws].<br />
# Make sure your account details on the [[AUR]] are up-to-date.<br />
# Add yourself to the [[Trusted Users]] page.<br />
# Remind a [[ArchWiki:Access levels and roles#Access levels|bureaucrat]] to add your wiki account to the {{int:group-archtu}} group.<br />
# Subscribe to the public mailing list for Arch Linux development, [https://lists.archlinux.org/listinfo/arch-dev-public arch-dev-public].<br />
# Request subscription to the internal trusted user mailing list.<br />
# Remind a [https://bbs.archlinux.org/userlist.php?username=&show_group=1&sort_by=username&sort_dir=ASC&search=Submit BBS admin] to change your account on forums.<br />
# Ask some TU for the #archlinux-tu@freenode key and hang out with us in the channel. You do not have to do this, but it would be neat since this is where most dark secrets are spilled and where many new ideas are conceived.<br />
#* If you need a bouncer, ask heftig for a [[Matrix]] invite. <br />
#* Once in the channel, if you want an @archlinux/trusteduser/* cloak ask our [[Arch IRC channels#Freenode group contacts|group contacts]] to get you one.<br />
# Create a PGP key for [[package signing]] or use your existing PGP key. Make sure the key also contains an encryption subkey so you can receive encrypted verification tokens.<br />
# Send a signed email to Jelle van der Waa (jelle@vdwaa.nl):<br />
#* Attach one SSH public key. If you do not have one, use {{ic|ssh-keygen}} to generate one. Check the [[Using SSH Keys]] wiki page for more information about SSH keys.<br />
#* Ask him to whitelist you from arch-dev-public.<br />
#* Tell him if you want an @archlinux.org email.<br />
#* Preferred username and e-mail address which initial password should be sent to in order to access dev interface (archweb). If you already have an account, ask to be added to the Trusted Users group.<br />
#* Ask him to create an account on Arch Linux SSO for you and which username you want on that. He will also add you to the Trusted Users group on SSO. <br />
# Ask your sponsor:<br />
#* to give you TU status on the AUR.<br />
#* to open a new task in the "Keyring" project of the bug tracker following the instructions in [https://lists.archlinux.org/pipermail/arch-dev-public/2013-September/025456.html this message] in order to have your PGP key signed by three master key holders.<br />
# Install the {{pkg|devtools}} package.<br />
# [[AUR submission guidelines#Authentication|Configure your private ssh key]] for {{ic|repos.archlinux.org}}.<br />
# Ssh to yourname@repos.archlinux.org (once you have permissions).<br />
# If you are not upgraded to a Trusted User group on bug tracker in two days, report this as a bug to arch-dev-public.<br />
# Start contributing!<br />
<br />
== The TU and the AUR ==<br />
<br />
The TUs should also make an effort to check package submissions in the [[AUR]] for malicious code and good PKGBUILDing standards. In around 80% of cases the PKGBUILDs in the UNSUPPORTED are very simple and can be quickly checked for sanity and malicious code by the TU team.<br />
<br />
TUs should also check PKGBUILDs for minor mistakes, suggest corrections and improvements. The TU should endeavor to confirm that all pkgs follow the Arch Packaging Guidelines/Standards and in doing so share their skills with other package builders in an effort to raise the standard of package building across the distro.<br />
<br />
TUs are also in an excellent position to document recommended practices.<br />
<br />
=== Rewriting git history ===<br />
<br />
In some cases rewriting the history of an AUR repository is required, for example when a user inadvertently uses their real name in a published commit. This can be automated with {{man|1|git-filter-branch}}. <br />
<br />
To force push the new history, forward the {{ic|1=AUR_OVERWRITE=1}} environment variable to {{man|1|git-push}}. See [https://gitlab.archlinux.org/archlinux/aurweb/-/commit/c5302d3a33028f483cc2e01225226d4ae047dd4a] for details.<br />
<br />
{{Warning|It is recommended to create a backup of the repository before rewriting history.}}<br />
<br />
; Modify committer or author identity<br />
<br />
Use {{ic|git filter-branch --env-filter}} with the {{ic|GIT_AUTHOR_NAME}}, {{ic|GIT_AUTHOR_EMAIL}}, {{ic|GIT_COMMITTER_NAME}} and {{ic|GIT_COMMITTER_EMAIL}} [[environment variables]]. For example:<br />
<br />
{{bc|1=<br />
git filter-branch --env-filter '<br />
if test "$GIT_AUTHOR_EMAIL" = "lepetit@prince.com"; then<br />
GIT_AUTHOR_EMAIL=user@users.noreply.github.com<br />
fi<br />
if test "$GIT_AUTHOR_NAME" = "Antoine de Saint-Exupéry"; then<br />
GIT_AUTHOR_NAME=user<br />
fi'<br />
}}<br />
<br />
{{Note|{{man|1|git-log}} only displays the git ''author'' by default. Use {{ic|1=git log --pretty=fuller}} to display the ''author'' and ''committer''.}}<br />
<br />
== The TU and [community], Guidelines for Package Maintenance ==<br />
<br />
=== Rules for Packages Entering the [community] Repo ===<br />
<br />
* A package must not already exist in any of the Arch Linux repositories. You should take necessary precautions to ensure no other packager is in the process of promoting the same package. Double-check the AUR package comments, read the latest subject headings in [https://mailman.archlinux.org/mailman/listinfo/aur-general aur-general], search [https://bugs.archlinux.org/index.php?project=0&do=index&switch=1 all projects in the bugtracker], [[wikipedia:Grep|grep]] the [http://svnbook.red-bean.com/en/1.7/svn.ref.svn.c.log.html Subversion log], and send a quick message to the private TU [[IRC channel]].<br />
* [[AUR helpers#Pacman wrappers|Pacman wrappers]], as a special exception, will never be permitted. If wanting to otherwise add an [[AUR helper]], write an email to {{ic|arch-dev-public}} with the proposed addition, and respect any objections provided by team members.<br />
* Only "popular" packages may enter the repo, as defined by 1% usage from [https://pkgstats.archlinux.de/packages pkgstats] or 10 votes on the AUR.<br />
* Automatic exceptions to this rule are:<br />
** i18n packages<br />
** accessibility packages<br />
** drivers<br />
** dependencies of packages who satisfy the definition of popular, including makedeps and optdeps<br />
** packages that are part of a collection and are intended to be distributed together, provided a part of this collection satisfies the definition of popular<br />
* Any additions not covered by the above criteria must first be proposed on the aur-general mailing list, explaining the reason for the exemption (e.g. renamed package, new package). The agreement of three other TUs is required for the package to be accepted into [community]. Proposed additions from TUs with large numbers of "non-popular" packages are more likely to be rejected.<br />
* TUs are strongly encouraged to move packages they currently maintain from [community] if they have low usage. No enforcement will be made, although resigning TUs packages may be filtered before adoption can occur.<br />
* It is good practice to always bump the '''pkgrel''' by ''1'' (in other words, set it to ''n + 1'') when promoting a package from AUR. This is to facilitate automatic updates for those who already have the package installed, so that they may continue to receive updates from the official channel. Another positive effect of this is that users are not warned that their local copy is newer, as is the case if a packager does reset the '''pkgrel''' to ''1''.<br />
<br />
=== Accessing and Updating the Repository ===<br />
<br />
{{Merge|DeveloperWiki:HOWTO Be A Packager|Duplicate with some minor differences}}<br />
<br />
The [community] repository now uses '''devtools''' which is the same system used for uploading packages to [core] and [extra] to {{ic|repos.archlinux.org}}. Thus most of the instructions in [[DeveloperWiki:HOWTO Be A Packager|Packager Guide]] work without any change. Information which is specific for the [community] repository (like changed URLs) have been put here. The devtools require packagers to [[Makepkg#Packager_information|set the PACKAGER variable]] in {{ic|makepkg.conf}}.<br />
<br />
Initially you should do a '''non-recursive checkout''' of the [community] repository:<br />
<br />
<nowiki>$ svn checkout -N svn+ssh://svn-community@repos.archlinux.org/srv/repos/svn-community/svn svn-community</nowiki><br />
<br />
This creates a directory named "svn-community" which contains nothing but a ".svn" folder.<br />
<br />
For '''checking''' out, '''updating''' all packages or '''adding''' a package see the [[DeveloperWiki:HOWTO Be A Packager|Packager Guide]].<br />
<br />
To '''remove''' a package:<br />
<br />
$ ssh repos.archlinux.org /community/db-repo-remove community arch pkgname<br />
<br />
Here and in the following text, ''arch'' should be ''x86_64'' which is the only architecture supported by Arch Linux since [https://archlinux.org/news/the-end-of-i686-support/ i686 support has been deprecated].<br />
<br />
{{Note|If you are editing packages of the ''any'' architecture you can simply run the x86_64 scripts which will also work.}}<br />
<br />
When you are done with editing the PKGBUILD, etc., you should '''commit''' the changes ({{ic|svn commit}}).<br />
<br />
Build the package with the helper script {{ic|extra-x86_64-build}}. If you want to upload to testing you need to build with the testing script {{ic|testing-x86_64-build}} instead.<br />
<br />
Sign the package with {{ic|gpg --detach-sign *.pkg.tar.xz}}. If you are using a different PGP key for package signing you can add it to {{ic|~/.makepkg.conf}} with {{ic|1=GPGKEY=<identifier>}}.<br />
<br />
When you want to '''release''' a package, first copy the package along with its signatures to the ''staging/community'' directory on ''repos.archlinux.org'' using {{ic|scp}} and then '''tag''' the package by going to the ''pkgname/trunk'' directory and issuing {{ic|archrelease community-arch}}. This makes an svn copy of the trunk entries in a directory named ''community-x86_64'' indicating that this package is in the community repository for that architecture. Note that the staging directory is different from the staging repository and every package needs to be uploaded to the staging directory. This process can be automated with the {{ic|communitypkg}} script, see the summary below.<br />
<br />
'''Package update summary:'''<br />
<br />
* '''Update''' the package directory: {{ic|svn update some-package}}.<br />
* '''Change''' to the package trunk directory: {{ic|cd some-package/trunk}}.<br />
* '''Edit''' the PKGBUILD, make necessary changes, update hashes with {{ic|updpkgsums}}.<br />
* '''Build''' the package: {{ic|makechrootpkg}} or {{ic|extra-x86_64-build}}. It is '''mandatory''' to build in a [[DeveloperWiki:Building in a clean chroot|clean chroot]].<br />
* '''[[Namcap]]''' the PKGBUILD and the binary {{ic|pkg.tar.gz}}.<br />
* '''Commit''', '''Sign''', '''Copy''' and '''Tag''' the package using {{ic|communitypkg "commit message"}}. This automates the following:<br />
** '''Commit''' the changes to trunk: {{ic|svn commit}}.<br />
** '''Sign''' the package: {{ic|gpg --detach-sign *.pkg.tar.xz}}.<br />
** '''Copy''' the package and its signature to ''repos.archlinux.org'': {{ic|scp *.pkg.tar.xz *.pkg.tar.xz.sig repos.archlinux.org:staging/community/}}.<br />
** '''Tag''' the package: {{ic|archrelease community-x86_64}}.<br />
* '''Update''' the repository: {{ic|ssh repos.archlinux.org /community/db-update}}.<br />
<br />
Also see the ''Miscellaneous'' section in the [[DeveloperWiki:HOWTO Be A Packager|Packager Guide]] and [[SSH keys#ssh-agent]].<br />
<br />
=== Disowning packages ===<br />
<br />
If a TU cannot or does not want to maintain a package any longer, a notice should be posted to the AUR Mailing List, so another TU can<br />
maintain it. A package can still be disowned even if no other TU wants to maintain it, but the TUs should try not to drop many packages (they should not take on more than they have time for). If a package has become obsolete or is not used any longer, it can be removed completely as well.<br />
<br />
If a package has been removed completely, it can be uploaded once again (fresh) to UNSUPPORTED, where a regular user can maintain the package instead of the TU.<br />
<br />
=== Moving packages from unsupported to [community] ===<br />
<br />
Follow the normal procedures for adding a package to community, but remember to delete the corresponding package from unsupported!<br />
<br />
=== Moving packages from [community] to unsupported ===<br />
<br />
Remove the package using the instructions above and upload your source to the AUR.<br />
<br />
=== Moving packages from [community-testing] to [community] ===<br />
<br />
$ ssh repos.archlinux.org /community/db-move community-testing community <package><br />
<br />
=== Deleting packages from unsupported ===<br />
<br />
There is no point in removing dummy packages, because they will be re-created in an attempt to track dependencies. If someone uploads a<br />
real package then all dependents will point to the correct place.<br />
<br />
=== Remote build on PKGBUILD.com ===<br />
<br />
{{Warning|The following procedures defeats the Web Of Trust model: a user with root access to PKGBUILD.com could alter the package and/or the signature before it gets published.}}<br />
<br />
Trusted users and developers can connect to [http://pkgbuild.com/ PKGBUILD.com] via SSH to, among others, build packages using the devtools.<br />
This has numerous advantages over a local setup:<br />
<br />
* Builds are fast and network speed is high.<br />
* The environment needs setup only once.<br />
* Your local system need not be Arch Linux.<br />
<br />
The process is similar to that of a local setup with devtools. Your GnuPG private is required for signing but you do not want to upload it to soyuz for obvious security reasons. As such, you will need to forward the GnuPG agent socket from your local machine to the server: this will allow you to sign packages on soyuz without communicating your key. This also means that we need to disable the agent on the server before we can run anything.<br />
<br />
First, connect to soyuz and disable<br />
<br />
$ ssh soyuz.archlinux.org<br />
$ systemctl --user mask gpg-agent.service<br />
<br />
Make sure gpg-agent is not running ({{ic|systemctl --user stop gpg-agent.service}}). At this point, make sure that no sockets exist in the folder pointed by {{ic|gpgconf --list-dir socketdir}}. If they do, remove them or log out and in again.<br />
If you have a custom $GNUPGHOME (eg. to move it to {{ic|~/.config/gnupg}}), you will need to unset that, as it is not possible in gnupg to set the homedir without setting the socketdir.<br />
On soyuz, ''StreamLocalBindUnlink yes'' is set in ''sshd_config'', therefore removing the sockets manually on logout is not necessary.<br />
<br />
While the PGP private keys remain on your local machine, the public keys '''must''' be on soyuz. Export your public ring to soyuz, e.g. from you local machine<br />
<br />
$ scp ~/.gnupg/pubring.gpg soyuz.archlinux.org:~/.gnupg/pubring.gpg<br />
<br />
SSH is required to checkout and commit to the SVN repository. You can either set up a new SSH key pair on the server (it is highly discouraged to put your local private key on soyuz for security reasons) or reuse your local keys via socket forwarding. If you opt for the latter, make sure to disable ssh-agent on soyuz if you had enabled it previously (it is not running by default).<br />
<br />
Configure you build environment on soyuz:<br />
<br />
{{hc|1=~/.makepkg.conf|2=<br />
PACKAGER="John Doe <john@doe.example>"<br />
## Optional<br />
PKGDEST="/home/johndoe/packages"<br />
SRCDEST="/home/johndoe/sources"<br />
SRCPKGDEST="/home/johndoe/srcpackages"<br />
LOGDEST="/home/johndoe/logs"<br />
## If your PGP key is not the default, specify the right fingerprint:<br />
GPGKEY="ABCD1234..."<br />
}}<br />
<br />
{{Warning|Forwarding your gpg-agent socket to a remote machine makes it possible for anyone with root access to that system to use your unlocked GPG credentials. To circumvent this issue, we need to disable passphrase caching.}}<br />
<br />
Disable passphrase caching with the following settings:<br />
<br />
{{hc|gpg-agent.conf|<br />
default-cache-ttl 0<br />
max-cache-ttl 0<br />
}}<br />
<br />
Because we will want to keep our usual GPG agent running with its current settings, we are going to run another GPG agent dedicated to the task at hand. Create a {{ic|~/.gnupg-archlinux}} folder and symlink everything from {{ic|~/.gnupg}} there, except {{ic|~/.gnupg/gpg-agent.conf}}. Configure the new GPG agent:<br />
<br />
{{hc|~/.gnupg-archlinux|<br />
extra-socket /home/doe/.gnupg-archlinux/S.gpg-agent.extra<br />
default-cache-ttl 0<br />
max-cache-ttl 0<br />
pinentry-program /usr/bin/pinentry-gtk-2<br />
}}<br />
<br />
The {{ic|gpg-agent-extra.socket}} will be forwarded to PKGBUILD.com. <br />
<br />
Start the dedicated agent with<br />
<br />
$ gpg-agent --homedir ~/.gnupg-archlinux --daemon<br />
<br />
Connect with:<br />
<br />
$ ssh -R $REMOTE_SSH_AUTH_SOCK:$SSH_AUTH_SOCK -R /run/user/$REMOTE_UID/gnupg/S.gpg-agent:/home/doe/.gnupg-archlinux/S.gpg-agent.extra soyuz.archlinux.org<br />
<br />
or, if using GnuPG as your SSH agent:<br />
<br />
$ ssh -R /run/user/$REMOTE_UID/gnupg/S.gpg-agent.ssh:/run/user/$LOCAL_UID/gnupg/S.gpg-agent.ssh -R /run/user/$REMOTE_UID/gnupg/S.gpg-agent:/home/doe/.gnupg-archlinux/S.gpg-agent.extra soyuz.archlinux.org<br />
<br />
Replace ''$REMOTE_UID'' and ''$LOCAL_UID'' by your user identifier as returned by {{ic|id -u}} on soyuz and locally, respectively.<br />
If using ssh-agent, replace ''$REMOTE_SSH_AUTH_SOCK'' by the path to the SSH socket on the remote host (it can be anything).<br />
<br />
You can make the forwarding permanent for that host. For instance with gpg-agent.ssh:<br />
<br />
{{hc|~/.ssh/config|<br />
Host soyuz.archlinux.org<br />
RemoteForward /run/user/$REMOTE_UID/gnupg/S.gpg-agent /run/user/$LOCAL_UID/gnupg/S.gpg-agent.extra<br />
RemoteForward /run/user/$REMOTE_UID/gnupg/S.gpg-agent.ssh /run/user/$LOCAL_UID/gnupg/S.gpg-agent.ssh<br />
}}<br />
<br />
Again, replace ''$REMOTE_UID'' and ''$LOCAL_UID'' with their respective values.<br />
<br />
From then on, the procedure should be exactly the same as a local build:<br />
<br />
$ ssh soyuz.archlinux.org<br />
$ svn checkout -N svn+ssh://svn-community@repos.archlinux.org/srv/repos/svn-community/svn svn-community<br />
$ ...<br />
<br />
{{Note|pinentry-curses might not work with socket forwarding. If it fails for you, try using a different pinentry.}}<br />
<br />
== TODO list retiring a Trusted User ==<br />
<br />
When a TU resigns the following list has be followed, these steps do not apply when a TU resigns but is still a Developer.<br />
<br />
# All packages packaged by the retiree should be resigned (so rebuild). Packages packaged by the retiree can be found in Archweb https://archlinux.org/packages/?sort=&q=&packager=$packager&flagged= where packager is the username on Archweb.<br />
# The account of the retiree should be disabled on Archweb and added to the 'Retired Trusted users' group. The retiree should be removed from the 'Trusted Users' and the repository permissions should be reduced to none.<br />
# The shell access to our servers should be disabled. (notably repos.archlinux.org, pkgbuild.com)<br />
# The GPG key should be removed and a new archlinux-keyring package should be pushed to the repos. Create bug reports in the keyring project to remove the keys of the retired Trusted Users.<br />
# Remove the TU group from their AUR account.<br />
# A [[ArchWiki:Access levels and roles#Access levels|bureaucrat]] should remove their wiki account from the {{int:group-archtu}} group.<br />
# A [https://bbs.archlinux.org/userlist.php?username=&show_group=1&sort_by=username&sort_dir=ASC&search=Submit BBS admin] should change their account on forums.<br />
<br />
== See also ==<br />
<br />
* [[DeveloperWiki#Packaging Guidelines]]</div>Dundeehttps://wiki.archlinux.org/index.php?title=ASUS_Zenbook_UM425&diff=641174ASUS Zenbook UM4252020-11-10T08:37:47Z<p>Dundee: suspend update</p>
<hr />
<div>[[Category:ASUS]]<br />
[[ja:ASUS Zenbook UM425]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status'''<br />
|-<br />
| AMD CPU || {{G|Working}}<br />
|-<br />
| Radeon GPU || {{G|Working}}<br />
|-<br />
| HDMI || {{G|Working}}<br />
|-<br />
| Wireless || {{G|Working}}<br />
|-<br />
| Audio || {{G|Working}}<br />
|-<br />
| Touchpad || {{Y|Partially working}}<br />
|-<br />
| Camera || {{G|Working}}<br />
|-<br />
| Card Reader || {{G|Working}}<br />
|-<br />
| Bluetooth || {{G|Working}}<br />
|-<br />
| Function keys || {{G|Working}}<br />
|-<br />
| Battery charge threshold || {{R|Not working}}<br />
|-<br />
| Suspend to RAM || {{R|Not working}}<br />
|}<br />
<br />
<br />
== Configuration ==<br />
<br />
=== Secure Boot (option) ===<br />
In order to boot any Linux operating system, navigate to BIOS (hold F2 during power-on), then hit {{ic|F7}} or click on ''Advanced Menu'', then the ''Security'' tab and set ''Secure Boot'' to {{ic|Off}}.<br />
<br />
If the aforementioned ''Secure Boot'' option is a menu rather than an on-or-off option, click on ''Secure Boot'', ''Key Management'', then ''Reset to Setup Mode'' and confirm in the dialog.<br />
<br />
=== Video ===<br />
See [[ATI|AMD Graphics]] and [[Hardware_video_acceleration|Hardware Acceleration]].<br />
<br />
=== Audio ===<br />
See [[PulseAudio]].<br />
<br />
Microphone device is not yet detected.<br />
<br />
=== Touchpad ===<br />
See [[Libinput]].<br />
<br />
The NumPad is not working yet.<br />
<br />
== Troubleshooting ==<br />
<br />
<br />
=== Suspend ===<br />
<br />
Suspend to RAM (s2idle) is not working correctly. The system is often frozen when trying to wake-up.<br />
<br />
== Tips and tricks ==<br />
<br />
=== Power saving and performance ===<br />
As advertised by ASUS, both laptops are capable to last up to 20 hours on battery. In order to achieve this, see:<br />
<br />
* BIOS update - It is generally recommended to update BIOS, as it usually brings performance, power-saving and security features.<br />
<br />
* [[Power Saving]] - List of general recommendations to increase battery life.<br />
<br />
* [[Improving performance]] - List of general recommendations to increase performance.<br />
<br />
* [[SSD]] - Tips and tricks for Solid State Drives. Both laptops ship M.2 SSD by default.<br />
<br />
* [[Undervolting CPU]] - Decrease voltage for Intel CPU (reduce battery drain, reduce heat and therefore - reduce fan speed)<br />
<br />
=== Extract Windows 10 license key ===<br />
<br />
The laptop comes with Windows 10 preinstalled and the activation key is hardcoded into the firmware. If you replace Windows with Linux, then hardcoded activation key is useless. You might want to extract it and use somewhere else (e.g. virtualized Windows 10):<br />
# grep -aPo '[\w]{5}-[\w]{5}-[\w]{5}-[\w]{5}-[\w]{5}' /sys/firmware/acpi/tables/MSDM<br />
<br />
{{Note|Microsoft online support confirmed that the code is valid, but because you are unable to activate it (Windows fails to activate and asks for another code), they offered 2 options - replace activation code with another one for 40$ or contact OEM (ASUS) about this issue.<br />
ASUS confirmed, that in order to "use" this activation key, you need to bring this laptop to repair service so they can "restore" system using ASUS OEM Windows 10 image. They do not provide this image for download.}}</div>Dundeehttps://wiki.archlinux.org/index.php?title=ASUS_Zenbook_UM425&diff=639875ASUS Zenbook UM4252020-10-27T11:39:31Z<p>Dundee: audio is working now</p>
<hr />
<div>[[Category:ASUS]]<br />
[[ja:ASUS Zenbook UM425]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status'''<br />
|-<br />
| AMD CPU || {{G|Working}}<br />
|-<br />
| Radeon GPU || {{G|Working}}<br />
|-<br />
| HDMI || {{G|Working}}<br />
|-<br />
| Wireless || {{G|Working}}<br />
|-<br />
| Audio || {{G|Working}}<br />
|-<br />
| Touchpad || {{Y|Partially working}}<br />
|-<br />
| Camera || {{G|Working}}<br />
|-<br />
| Card Reader || {{G|Working}}<br />
|-<br />
| Bluetooth || {{G|Working}}<br />
|-<br />
| Function keys || {{G|Working}}<br />
|-<br />
| Battery charge threshold || {{R|Not working}}<br />
|}<br />
<br />
<br />
== Configuration ==<br />
<br />
=== Secure Boot (option) ===<br />
In order to boot any Linux operating system, navigate to BIOS (hold F2 during power-on), then hit {{ic|F7}} or click on ''Advanced Menu'', then the ''Security'' tab and set ''Secure Boot'' to {{ic|Off}}.<br />
<br />
If the aforementioned ''Secure Boot'' option is a menu rather than an on-or-off option, click on ''Secure Boot'', ''Key Management'', then ''Reset to Setup Mode'' and confirm in the dialog.<br />
<br />
=== Video ===<br />
See [[ATI|AMD Graphics]] and [[Hardware_video_acceleration|Hardware Acceleration]].<br />
<br />
=== Audio ===<br />
See [[PulseAudio]].<br />
<br />
Microphone device is not yet detected.<br />
<br />
=== Touchpad ===<br />
See [[Libinput]].<br />
<br />
The NumPad is not working yet.<br />
<br />
== Troubleshooting ==<br />
<br />
<br />
=== Suspend ===<br />
<br />
Suspend is not working correctly. The system is often frozen when trying to wake-up.<br />
<br />
== Tips and tricks ==<br />
<br />
=== Power saving and performance ===<br />
As advertised by ASUS, both laptops are capable to last up to 20 hours on battery. In order to achieve this, see:<br />
<br />
* BIOS update - It is generally recommended to update BIOS, as it usually brings performance, power-saving and security features.<br />
<br />
* [[Power Saving]] - List of general recommendations to increase battery life.<br />
<br />
* [[Improving performance]] - List of general recommendations to increase performance.<br />
<br />
* [[SSD]] - Tips and tricks for Solid State Drives. Both laptops ship M.2 SSD by default.<br />
<br />
* [[Undervolting CPU]] - Decrease voltage for Intel CPU (reduce battery drain, reduce heat and therefore - reduce fan speed)<br />
<br />
=== Extract Windows 10 license key ===<br />
<br />
The laptop comes with Windows 10 preinstalled and the activation key is hardcoded into the firmware. If you replace Windows with Linux, then hardcoded activation key is useless. You might want to extract it and use somewhere else (e.g. virtualized Windows 10):<br />
# grep -aPo '[\w]{5}-[\w]{5}-[\w]{5}-[\w]{5}-[\w]{5}' /sys/firmware/acpi/tables/MSDM<br />
<br />
{{Note|Microsoft online support confirmed that the code is valid, but because you are unable to activate it (Windows fails to activate and asks for another code), they offered 2 options - replace activation code with another one for 40$ or contact OEM (ASUS) about this issue.<br />
ASUS confirmed, that in order to "use" this activation key, you need to bring this laptop to repair service so they can "restore" system using ASUS OEM Windows 10 image. They do not provide this image for download.}}</div>Dundeehttps://wiki.archlinux.org/index.php?title=ASUS_Zenbook_UM425&diff=638903ASUS Zenbook UM4252020-10-16T09:13:25Z<p>Dundee: created</p>
<hr />
<div>[[Category:ASUS]]<br />
[[ja:ASUS Zenbook UM425]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status'''<br />
|-<br />
| AMD CPU || {{G|Working}}<br />
|-<br />
| Radeon GPU || {{G|Working}}<br />
|-<br />
| HDMI || {{G|Working}}<br />
|-<br />
| Wireless || {{G|Working}}<br />
|-<br />
| Audio || {{Y|Partially working}}<br />
|-<br />
| Touchpad || {{Y|Partially working}}<br />
|-<br />
| Camera || {{G|Working}}<br />
|-<br />
| Card Reader || {{G|Working}}<br />
|-<br />
| Bluetooth || {{G|Working}}<br />
|-<br />
| Function keys || {{G|Working}}<br />
|-<br />
| Battery charge threshold || {{R|Not working}}<br />
|}<br />
<br />
<br />
== Configuration ==<br />
<br />
=== Secure Boot (option) ===<br />
In order to boot any Linux operating system, navigate to BIOS (hold F2 during power-on), then hit {{ic|F7}} or click on ''Advanced Menu'', then the ''Security'' tab and set ''Secure Boot'' to {{ic|Off}}.<br />
<br />
If the aforementioned ''Secure Boot'' option is a menu rather than an on-or-off option, click on ''Secure Boot'', ''Key Management'', then ''Reset to Setup Mode'' and confirm in the dialog.<br />
<br />
=== Video ===<br />
See [[ATI|AMD Graphics]] and [[Hardware_video_acceleration|Hardware Acceleration]].<br />
<br />
=== Audio ===<br />
See [[PulseAudio]].<br />
<br />
Microphone device is not yet detected.<br />
<br />
=== Touchpad ===<br />
See [[Libinput]].<br />
<br />
The NumPad is not working yet.<br />
<br />
== Troubleshooting ==<br />
<br />
<br />
=== Suspend ===<br />
<br />
Suspend is not working correctly. The system is often frozen when trying to wake-up.<br />
<br />
== Tips and tricks ==<br />
<br />
=== Power saving and performance ===<br />
As advertised by ASUS, both laptops are capable to last up to 20 hours on battery. In order to achieve this, see:<br />
<br />
* BIOS update - It is generally recommended to update BIOS, as it usually brings performance, power-saving and security features.<br />
<br />
* [[Power Saving]] - List of general recommendations to increase battery life.<br />
<br />
* [[Improving performance]] - List of general recommendations to increase performance.<br />
<br />
* [[SSD]] - Tips and tricks for Solid State Drives. Both laptops ship M.2 SSD by default.<br />
<br />
* [[Undervolting CPU]] - Decrease voltage for Intel CPU (reduce battery drain, reduce heat and therefore - reduce fan speed)<br />
<br />
=== Extract Windows 10 license key ===<br />
<br />
The laptop comes with Windows 10 preinstalled and the activation key is hardcoded into the firmware. If you replace Windows with Linux, then hardcoded activation key is useless. You might want to extract it and use somewhere else (e.g. virtualized Windows 10):<br />
# grep -aPo '[\w]{5}-[\w]{5}-[\w]{5}-[\w]{5}-[\w]{5}' /sys/firmware/acpi/tables/MSDM<br />
<br />
{{Note|Microsoft online support confirmed that the code is valid, but because you are unable to activate it (Windows fails to activate and asks for another code), they offered 2 options - replace activation code with another one for 40$ or contact OEM (ASUS) about this issue.<br />
ASUS confirmed, that in order to "use" this activation key, you need to bring this laptop to repair service so they can "restore" system using ASUS OEM Windows 10 image. They do not provide this image for download.}}</div>Dundeehttps://wiki.archlinux.org/index.php?title=Intel_NUC&diff=481613Intel NUC2017-07-10T08:45:30Z<p>Dundee: </p>
<hr />
<div>[[Category:Mainboards and BIOS]]<br />
[[ja:Intel NUC]]<br />
[[wikipedia:Next_Unit_of_Computing|Next Unit of Computing (NUC)]] is a small-form-factor (SFF) PC designed by Intel and is based on soldered-on low-power Celeron, Pentium, i3, i5 and i7 CPUs. Its motherboard measures 4 × 4 inches (10.16 × 10.16 cm).<br />
<br />
The barebone kits consist of the board, in a plastic case with a fan, an external power supply and VESA mounting plate. Intel does offer for sale just the NUC motherboards, which have a built-in CPU, although (as of 2013) the price of a NUC motherboard is very close to the corresponding cased kit; third-party cases for the NUC boards are also available.<br />
<br />
== Installation ==<br />
<br />
Follow usual [[installation guide]] procedures.<br />
<br />
It is highly recommended to update the board BIOS prior to installation. See [https://www-ssl.intel.com/content/www/us/en/support/boards-and-kits/000005636.html official Intel BIOS update instructions] for details.<br />
<br />
{{Note|Prior to BIOS update, review the community response to the latest BIOS version compatability with the specific NUC model, as some versions are known to cause new regressions.}}<br />
<br />
=== NVMe ===<br />
<br />
Intel NUCs support NVMe drives connected to the PCIe M.2 connector. See [[Solid State Drives/NVMe]].<br />
<br />
{{Note|If the M.2 connector is not working, verify that it is enabled in BIOS.}}<br />
<br />
=== Graphics ===<br />
<br />
Most NUCs use integrated [[Intel graphics]]. See [[Hardware video acceleration]] to enjoy it on supported NUC models.<br />
<br />
==== Skylake ====<br />
<br />
Skylake support is stable on recent kernels, no further action should be required. See [[Intel graphics#Skylake support]] for more details.<br />
<br />
=== Wireless ===<br />
<br />
Most NUC wireless adapters should work out of the box. Make sure relevant firmware is loaded. See [[Wireless network configuration#iwlwifi]] for details.<br />
<br />
== Performance ==<br />
<br />
=== Boot ===<br />
<br />
Fastest boot times are achieved with [[UEFI]] boot and disabling legacy boot in the BIOS settings.<br />
<br />
=== 4K ===<br />
<br />
If you want to use 4K graphic output, open the BIOS settings and set ''Devices and Peripherals'' -> ''Video'' -> ''IGD Minimum Memory'' to 512 MB and ''IGD Aperture Size'' to 1024 MB.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Audio plug ===<br />
<br />
The [[PulseAudio#Switch on connect]] module is buggy and in some cases might cause pulseaudio to stop playing audio when disconnecting the plug, until pulse is restarted. In this case, comment out the module:<br />
<br />
{{hc|/etc/pulse/default.pa|<br />
#load-module module-switch-on-port-available<br />
}}<br />
<br />
=== TPM ===<br />
<br />
NUC devices have [[TPM]] capabilites that are currently blocked due to a few bugs in {{ic|tpm_crb}}[https://bugzilla.kernel.org/show_bug.cgi?id=98181][https://bugzilla.kernel.org/show_bug.cgi?id=111511]. 4.6 Kernel still has no solution for Haswell TPMs but a relevant patch is work in progress[https://lkml.org/lkml/2016/4/19/46].<br />
<br />
=== Poweroff ===<br />
<br />
After issuing a shutdown, the NUC might remain in some state which isn't completely shut down, as indicated by a remaining blue power LED. In this case it's neccesary to power off the unit by holding the power button for a few seconds.<br />
<br />
The workaround for this issue is to disable all wake-on-CIR (infrared sensor) options in the BIOS. In some cases it might be required to disable the CIR sensor completely to fix the issue.<br />
<br />
== Resources ==<br />
<br />
* [https://communities.intel.com/community/tech/nuc Official Intel NUC Support Community]</div>Dundeehttps://wiki.archlinux.org/index.php?title=Intel_NUC&diff=481612Intel NUC2017-07-10T08:44:41Z<p>Dundee: 4K</p>
<hr />
<div>[[Category:Mainboards and BIOS]]<br />
[[ja:Intel NUC]]<br />
[[wikipedia:Next_Unit_of_Computing|Next Unit of Computing (NUC)]] is a small-form-factor (SFF) PC designed by Intel and is based on soldered-on low-power Celeron, Pentium, i3, i5 and i7 CPUs. Its motherboard measures 4 × 4 inches (10.16 × 10.16 cm).<br />
<br />
The barebone kits consist of the board, in a plastic case with a fan, an external power supply and VESA mounting plate. Intel does offer for sale just the NUC motherboards, which have a built-in CPU, although (as of 2013) the price of a NUC motherboard is very close to the corresponding cased kit; third-party cases for the NUC boards are also available.<br />
<br />
== Installation ==<br />
<br />
Follow usual [[installation guide]] procedures.<br />
<br />
It is highly recommended to update the board BIOS prior to installation. See [https://www-ssl.intel.com/content/www/us/en/support/boards-and-kits/000005636.html official Intel BIOS update instructions] for details.<br />
<br />
{{Note|Prior to BIOS update, review the community response to the latest BIOS version compatability with the specific NUC model, as some versions are known to cause new regressions.}}<br />
<br />
=== NVMe ===<br />
<br />
Intel NUCs support NVMe drives connected to the PCIe M.2 connector. See [[Solid State Drives/NVMe]].<br />
<br />
{{Note|If the M.2 connector is not working, verify that it is enabled in BIOS.}}<br />
<br />
=== Graphics ===<br />
<br />
Most NUCs use integrated [[Intel graphics]]. See [[Hardware video acceleration]] to enjoy it on supported NUC models.<br />
<br />
==== Skylake ====<br />
<br />
Skylake support is stable on recent kernels, no further action should be required. See [[Intel graphics#Skylake support]] for more details.<br />
<br />
=== Wireless ===<br />
<br />
Most NUC wireless adapters should work out of the box. Make sure relevant firmware is loaded. See [[Wireless network configuration#iwlwifi]] for details.<br />
<br />
== Performance ==<br />
<br />
=== Boot ===<br />
<br />
Fastest boot times are achieved with [[UEFI]] boot and disabling legacy boot in the BIOS settings.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Audio plug ===<br />
<br />
The [[PulseAudio#Switch on connect]] module is buggy and in some cases might cause pulseaudio to stop playing audio when disconnecting the plug, until pulse is restarted. In this case, comment out the module:<br />
<br />
{{hc|/etc/pulse/default.pa|<br />
#load-module module-switch-on-port-available<br />
}}<br />
<br />
=== TPM ===<br />
<br />
NUC devices have [[TPM]] capabilites that are currently blocked due to a few bugs in {{ic|tpm_crb}}[https://bugzilla.kernel.org/show_bug.cgi?id=98181][https://bugzilla.kernel.org/show_bug.cgi?id=111511]. 4.6 Kernel still has no solution for Haswell TPMs but a relevant patch is work in progress[https://lkml.org/lkml/2016/4/19/46].<br />
<br />
=== Poweroff ===<br />
<br />
After issuing a shutdown, the NUC might remain in some state which isn't completely shut down, as indicated by a remaining blue power LED. In this case it's neccesary to power off the unit by holding the power button for a few seconds.<br />
<br />
The workaround for this issue is to disable all wake-on-CIR (infrared sensor) options in the BIOS. In some cases it might be required to disable the CIR sensor completely to fix the issue.<br />
<br />
=== 4K ===<br />
<br />
If you want to use 4K graphic output, open the BIOS settings and set ''Devices and Peripherals'' -> ''Video'' -> ''IGD Minimum Memory'' to 512 MB and ''IGD Aperture Size'' to 1024 MB.<br />
<br />
== Resources ==<br />
<br />
* [https://communities.intel.com/community/tech/nuc Official Intel NUC Support Community]</div>Dundeehttps://wiki.archlinux.org/index.php?title=Lm_sensors&diff=480742Lm sensors2017-06-30T11:19:05Z<p>Dundee: added gnome-shell-extension-system-monitor-git</p>
<hr />
<div>{{DISPLAYTITLE:lm_sensors}}<br />
[[Category:Status monitoring and notification]]<br />
[[Category:CPU]]<br />
[[cs:Lm-sensors]]<br />
[[de:Lm sensors]]<br />
[[es:Lm-sensors]]<br />
[[ja:Lm sensors]]<br />
[[ru:Lm-sensors]]<br />
[[uk:Lm-sensors]]<br />
[[zh-hans:Lm sensors]]<br />
{{Related articles start}}<br />
{{Related|Fan speed control}}<br />
{{Related|hddtemp}}<br />
{{Related|monitorix}}<br />
{{Related articles end}}<br />
[http://lm-sensors.org/ lm_sensors] (Linux monitoring sensors) is a free and open-source application that provides tools and drivers for monitoring temperatures, voltage, and fans. This document explains how to install, configure, and use lm_sensors.<br />
<br />
== Installation ==<br />
[[Install]] the {{Pkg|lm_sensors}} package.<br />
<br />
{{Note|More documentation is at the [https://github.com/groeck/lm-sensors/tree/master/doc GitHub repository]. In the future these may be installed, see {{Bug|48354}}.}}<br />
<br />
== Setup ==<br />
Use ''sensors-detect'' as root to detect and generate a list of kernel modules:<br />
{{Warning|Do not use anything other than the default options (by just hitting {{ic|Enter}}), unless you know exactly what you are doing. See [[#Laptop screen issues after running sensors-detect]].}}<br />
<br />
# sensors-detect<br />
<br />
It will ask to probe for various hardware. The "safe" answers are the defaults, so just hitting {{ic|Enter}} to all the questions will generally not cause any problems. This will create the {{ic|/etc/conf.d/lm_sensors}} configuration file which is used by {{ic|lm_sensors.service}} to automatically load kernel modules on boot.<br />
<br />
When the detection is finished, a summary of the probes is presented.<br />
<br />
Example:<br />
{{hc|# sensors-detect|<nowiki><br />
This program will help you determine which kernel modules you need<br />
to load to use lm_sensors most effectively. It is generally safe<br />
and recommended to accept the default answers to all questions,<br />
unless you know what you're doing.<br />
<br />
Some south bridges, CPUs or memory controllers contain embedded sensors.<br />
Do you want to scan for them? This is totally safe. (YES/no): <br />
Module cpuid loaded successfully.<br />
Silicon Integrated Systems SIS5595... No<br />
VIA VT82C686 Integrated Sensors... No<br />
VIA VT8231 Integrated Sensors... No<br />
AMD K8 thermal sensors... No<br />
AMD Family 10h thermal sensors... No<br />
<br />
...<br />
<br />
Now follows a summary of the probes I have just done.<br />
Just press ENTER to continue: <br />
<br />
Driver `coretemp':<br />
* Chip `Intel digital thermal sensor' (confidence: 9)<br />
<br />
Driver `lm90':<br />
* Bus `SMBus nForce2 adapter at 4d00'<br />
Busdriver `i2c_nforce2', I2C address 0x4c<br />
Chip `Winbond W83L771AWG/ASG' (confidence: 6)<br />
<br />
Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no): <br />
ln -s '/usr/lib/systemd/system/lm_sensors.service' '/etc/systemd/system/multi-user.target.wants/lm_sensors.service'<br />
Unloading i2c-dev... OK<br />
Unloading cpuid... OK<br />
</nowiki>}}<br />
<br />
{{Note|A systemd service is automatically enabled if users answer '''YES''' when asked about generating {{ic|/etc/conf.d/lm_sensors}}. Answering '''YES''' also automatically starts the service.}}<br />
<br />
== Running sensors ==<br />
Example running {{ic|sensors}}:<br />
{{hc|$ sensors|<nowiki><br />
coretemp-isa-0000<br />
Adapter: ISA adapter<br />
Core 0: +35.0°C (crit = +105.0°C)<br />
Core 1: +32.0°C (crit = +105.0°C)<br />
<br />
w83l771-i2c-0-4c<br />
Adapter: SMBus nForce2 adapter at 4d00<br />
temp1: +28.0°C (low = -40.0°C, high = +70.0°C)<br />
(crit = +85.0°C, hyst = +75.0°C)<br />
temp2: +37.4°C (low = -40.0°C, high = +70.0°C)<br />
(crit = +110.0°C, hyst = +100.0°C)<br />
</nowiki>}}<br />
<br />
=== Reading SPD values from memory modules (optional) ===<br />
<br />
To read the SPD timing values from memory modules, install the {{pkg|i2c-tools}} package. Once installed, load the {{ic|eeprom}} [[kernel module]].<br />
# modprobe eeprom<br />
<br />
Finally, view memory information with {{ic|decode-dimms}}.<br />
<br />
Here is partial output from one machine:<br />
{{hc|# decode-dimms|<nowiki><br />
Memory Serial Presence Detect Decoder<br />
By Philip Edelbrock, Christian Zuckschwerdt, Burkart Lingner,<br />
Jean Delvare, Trent Piepho and others<br />
<br />
<br />
Decoding EEPROM: /sys/bus/i2c/drivers/eeprom/0-0050<br />
Guessing DIMM is in bank 1<br />
<br />
---=== SPD EEPROM Information ===---<br />
EEPROM CRC of bytes 0-116 OK (0x583F)<br />
# of bytes written to SDRAM EEPROM 176<br />
Total number of bytes in EEPROM 512<br />
Fundamental Memory type DDR3 SDRAM<br />
Module Type UDIMM<br />
<br />
---=== Memory Characteristics ===---<br />
Fine time base 2.500 ps<br />
Medium time base 0.125 ns<br />
Maximum module speed 1066MHz (PC3-8533)<br />
Size 2048 MB<br />
Banks x Rows x Columns x Bits 8 x 14 x 10 x 64<br />
Ranks 2<br />
SDRAM Device Width 8 bits<br />
tCL-tRCD-tRP-tRAS 7-7-7-33<br />
Supported CAS Latencies (tCL) 8T, 7T, 6T, 5T<br />
<br />
---=== Timing Parameters ===---<br />
Minimum Write Recovery time (tWR) 15.000 ns<br />
Minimum Row Active to Row Active Delay (tRRD) 7.500 ns<br />
Minimum Active to Auto-Refresh Delay (tRC) 49.500 ns<br />
Minimum Recovery Delay (tRFC) 110.000 ns<br />
Minimum Write to Read CMD Delay (tWTR) 7.500 ns<br />
Minimum Read to Pre-charge CMD Delay (tRTP) 7.500 ns<br />
Minimum Four Activate Window Delay (tFAW) 30.000 ns<br />
<br />
---=== Optional Features ===---<br />
Operable voltages 1.5V<br />
RZQ/6 supported? Yes<br />
RZQ/7 supported? Yes<br />
DLL-Off Mode supported? No<br />
Operating temperature range 0-85C<br />
Refresh Rate in extended temp range 1X<br />
Auto Self-Refresh? Yes<br />
On-Die Thermal Sensor readout? No<br />
Partial Array Self-Refresh? No<br />
Thermal Sensor Accuracy Not implemented<br />
SDRAM Device Type Standard Monolithic<br />
<br />
---=== Physical Characteristics ===---<br />
Module Height (mm) 15<br />
Module Thickness (mm) 1 front, 1 back<br />
Module Width (mm) 133.5<br />
Module Reference Card B<br />
<br />
---=== Manufacturer Data ===---<br />
Module Manufacturer Invalid<br />
Manufacturing Location Code 0x02<br />
Part Number OCZ3G1600LV2G <br />
<br />
...<br />
</nowiki>}}<br />
<br />
== Using sensor data ==<br />
=== Graphical front-ends ===<br />
There are a variety of front-ends for sensors data.<br />
*[[conky]] - Conky is an advanced, highly configurable system monitor for X based on torsmo<br />
*{{Pkg|xsensors}} - X11 interface to lm_sensors<br />
*{{AUR|psensor}} - GTK+ application for monitoring hardware sensors, including temperatures and fan speeds. Monitors motherboard and CPU (using lm-sensors), Nvidia GPUs (using XNVCtrl), and harddisks (using [[hddtemp]] or libatasmart).<br />
For specific [[Desktop environments]]:<br />
*{{Pkg|sensors-applet}} - applet for the [[GNOME]] Panel to display readings from hardware sensors, including CPU temperature, fan speeds and voltage readings.<br />
*{{AUR|gnome-shell-extension-system-monitor-git}} - System monitor extension for [[GNOME]] Shell.<br />
*{{AUR|plasma5-applets-thermal-monitor-git}} - Is an example of the [[KDE#Widgets|widgets]] available for [[KDE]] desktop.<br />
*{{AUR|sensors-lxpanel-plugin}} -- A lm_sensors plugin for the [[LXDE]] panel. lxpanel also includes a simple 'Temperature Monitor' plugin.<br />
*{{Pkg|xfce4-sensors-plugin}} - A lm_sensors plugin for the [[Xfce]] panel<br />
<br />
=== sensord ===<br />
There is an optional daemon called sensord (included with the {{Pkg|lm_sensors}} package) which can log data to a round robin database (rrd) and later visualize graphically. See the sensord man page for details.<br />
<br />
==Tips and tricks==<br />
=== Adjusting values ===<br />
In some cases, the data displayed might be incorrect or users may wish to rename the output.<br />
Use cases include:<br />
* Incorrect temperature values due to a wrong offset (i.e. temps are reported 20 °C higher then actual).<br />
* Users wish to rename the output of some sensors.<br />
* The cores might be displayed in an incorrect order.<br />
<br />
All of the above (and more) can be adjusted by overriding the package provides settings in {{ic|/etc/sensors3.conf}} by creating {{ic|/etc/sensors.d/foo}} wherein any number of tweaks will override the default values. It is recommended to rename 'foo' to the motherboard brand and model but this naming nomenclature is optional.<br />
<br />
{{Note|Do not edit /etc/sensors3.conf directly since package updates will overwrite any changes thus losing them.}}<br />
<br />
==== Example 1. Adjusting temperature offsets ====<br />
This is a real example on a Zotac ION-ITX-A-U motherboard. The coretemp values are off by 20 °C (too high) and are adjusted down to Intel specs.<br />
<br />
{{hc|$ sensors|<nowiki><br />
coretemp-isa-0000<br />
Adapter: ISA adapter<br />
Core 0: +57.0°C (crit = +125.0°C)<br />
Core 1: +55.0°C (crit = +125.0°C)<br />
...<br />
</nowiki>}}<br />
<br />
Run {{ic|sensors}} with the {{ic|-u}} switch to see what options are available for each physical chip (raw mode):<br />
{{hc|$ sensors -u|<nowiki><br />
coretemp-isa-0000<br />
Adapter: ISA adapter<br />
Core 0:<br />
temp2_input: 57.000<br />
temp2_crit: 125.000<br />
temp2_crit_alarm: 0.000<br />
Core 1:<br />
temp3_input: 55.000<br />
temp3_crit: 125.000<br />
temp3_crit_alarm: 0.000<br />
...<br />
</nowiki>}}<br />
<br />
Create the following file overriding the default values:<br />
{{hc|/etc/sensors.d/Zotac-IONITX-A-U|<nowiki><br />
chip "coretemp-isa-0000"<br />
label temp2 "Core 0"<br />
compute temp2 @-20,@-20<br />
<br />
label temp3 "Core 1"<br />
compute temp3 @-20,@-20<br />
</nowiki>}}<br />
<br />
Now invoking {{ic|sensors}} shows the adjust values:<br />
{{hc|$ sensors|<nowiki><br />
coretemp-isa-0000<br />
Adapter: ISA adapter<br />
Core 0: +37.0°C (crit = +105.0°C)<br />
Core 1: +35.0°C (crit = +105.0°C)<br />
...<br />
</nowiki>}}<br />
<br />
==== Example 2. Renaming labels ====<br />
This is a real example on an Asus A7M266. The user wishes more verbose names for the temperature labels 'temp1' and 'temp2':<br />
{{hc|$ sensors|<nowiki><br />
as99127f-i2c-0-2d<br />
Adapter: SMBus Via Pro adapter at e800<br />
...<br />
temp1: +35.0°C (high = +0.0°C, hyst = -128.0°C)<br />
temp2: +47.5°C (high = +100.0°C, hyst = +75.0°C)<br />
...<br />
</nowiki>}}<br />
<br />
Create the following file to override the default values:<br />
{{hc|/etc/sensors.d/Asus_A7M266|<nowiki><br />
chip "as99127f-*"<br />
label temp1 "Mobo Temp"<br />
label temp2 "CPU0 Temp"<br />
</nowiki>}}<br />
<br />
Now invoking {{ic|sensors}} shows the adjust values:<br />
{{hc|$ sensors|<nowiki><br />
as99127f-i2c-0-2d<br />
Adapter: SMBus Via Pro adapter at e800<br />
...<br />
Mobo Temp: +35.0°C (high = +0.0°C, hyst = -128.0°C)<br />
CPU0 Temp: +47.5°C (high = +100.0°C, hyst = +75.0°C)<br />
...<br />
</nowiki>}}<br />
<br />
==== Example 3. Renumbering cores for multi-CPU systems ====<br />
This is a real example on an HP Z600 workstation with dual Xeons. The actual numbering of physical cores is incorrect: numbered 0, 1, 9, 10 which is repeated into the second CPU. Most users expect the core temperatures to report out in sequential order, i.e. 0,1,2,3,4,5,6,7.<br />
{{hc|$ sensors|<nowiki><br />
coretemp-isa-0000<br />
Adapter: ISA adapter<br />
Core 0: +65.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core 1: +65.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core 9: +66.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core 10: +66.0°C (high = +85.0°C, crit = +95.0°C)<br />
<br />
coretemp-isa-0004<br />
Adapter: ISA adapter<br />
Core 0: +54.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core 1: +56.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core 9: +60.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core 10: +61.0°C (high = +85.0°C, crit = +95.0°C)<br />
...<br />
</nowiki>}}<br />
<br />
Again, run {{ic|sensors}} with the {{ic|-u}} switch to see what options are available for each physical chip:<br />
<br />
{{hc|$ sensors -u coretemp-isa-0000|<nowiki><br />
coretemp-isa-0000<br />
Adapter: ISA adapter<br />
Core 0:<br />
temp2_input: 61.000<br />
temp2_max: 85.000<br />
temp2_crit: 95.000<br />
temp2_crit_alarm: 0.000<br />
Core 1:<br />
temp3_input: 61.000<br />
temp3_max: 85.000<br />
temp3_crit: 95.000<br />
temp3_crit_alarm: 0.000<br />
Core 9:<br />
temp11_input: 62.000<br />
temp11_max: 85.000<br />
temp11_crit: 95.000<br />
Core 10:<br />
temp12_input: 63.000<br />
temp12_max: 85.000<br />
temp12_crit: 95.000<br />
</nowiki>}}<br />
<br />
{{hc|$ sensors -u coretemp-isa-0004|<nowiki><br />
coretemp-isa-0004<br />
Adapter: ISA adapter<br />
Core 0:<br />
temp2_input: 53.000<br />
temp2_max: 85.000<br />
temp2_crit: 95.000<br />
temp2_crit_alarm: 0.000<br />
Core 1:<br />
temp3_input: 54.000<br />
temp3_max: 85.000<br />
temp3_crit: 95.000<br />
temp3_crit_alarm: 0.000<br />
Core 9:<br />
temp11_input: 59.000<br />
temp11_max: 85.000<br />
temp11_crit: 95.000<br />
Core 10:<br />
temp12_input: 59.000<br />
temp12_max: 85.000<br />
temp12_crit: 95.000<br />
...<br />
</nowiki>}}<br />
<br />
Create the following file overriding the default values:<br />
{{hc|/etc/sensors.d/HP_Z600|<nowiki><br />
chip "coretemp-isa-0000"<br />
label temp2 "Core 0"<br />
label temp3 "Core 1"<br />
label temp11 "Core 2"<br />
label temp12 "Core 3"<br />
<br />
chip "coretemp-isa-0004"<br />
label temp2 "Core 4"<br />
label temp3 "Core 5"<br />
label temp11 "Core 6"<br />
label temp12 "Core 7"</nowiki>}}<br />
<br />
Now invoking {{ic|sensors}} shows the adjust values:<br />
{{hc|$ sensors|<nowiki><br />
coretemp-isa-0000<br />
Adapter: ISA adapter<br />
Core0: +64.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core1: +63.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core2: +65.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core3: +66.0°C (high = +85.0°C, crit = +95.0°C)<br />
<br />
coretemp-isa-0004<br />
Adapter: ISA adapter<br />
Core4: +53.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core5: +54.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core6: +59.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core7: +60.0°C (high = +85.0°C, crit = +95.0°C)<br />
...<br />
</nowiki>}}<br />
<br />
=== Automatic lm_sensors deployment ===<br />
Users wishing to deploy lm_sensors on multiple machines can use either of the following:<br />
<br />
1. Accept defaults to questions:<br />
# sensors-detect --auto<br />
<br />
2. Override defaults and answer YES to all questions:<br />
# yes | sensors-detect<br />
<br />
== Troubleshooting ==<br />
<br />
=== K10Temp module ===<br />
<br />
Some K10 processors have issues with their temperature sensor. From the kernel documentation ({{ic|linux-&lt;version&gt;/Documentation/hwmon/k10temp}}):<br />
<br />
:''All these processors have a sensor, but on those for Socket F or AM2+, the sensor may return inconsistent values (erratum 319). The driver will refuse to load on these revisions unless users specify the {{ic|1=force=1}} module parameter.''<br />
<br />
:''Due to technical reasons, the driver can detect only the mainboard's socket type, not the processor's actual capabilities. Therefore, users of an AM3 processor on an AM2+ mainboard, can safely use the {{ic|1=force=1}} parameter.''<br />
<br />
On affected machines the module will report "unreliable CPU thermal sensor; monitoring disabled". Users which to force it can:<br />
<br />
# rmmod k10temp<br />
# modprobe k10temp force=1<br />
<br />
Confirm that the sensor is in fact valid and reliable. If it is, can edit {{ic|/etc/modprobe.d/k10temp.conf}} and add:<br />
<br />
options k10temp force=1<br />
<br />
This will allow the module to load at boot.<br />
<br />
=== Gigabyte GA-J1900N-D3V ===<br />
<br />
The motherboard use the ITE IT8620E chip (useful also to read voltages, mainboard temp, fan speed).<br />
As of October 2014, lm_sensors has no driver support for chip ITE IT8620E [https://hwmon.wiki.kernel.org/device_support_status_g_i] [http://comments.gmane.org/gmane.linux.drivers.sensors/35168].<br />
lm_sensors developers had a report that the chip is somewhat compatible with the IT8728F for the hardware monitoring part. However, as of August 2016, [https://www.kernel.org/doc/Documentation/hwmon/it87] lists the IT8620E as supported.<br />
<br />
You can load the module at runtime with modprobe:<br />
<br />
$ modprobe it87 force_id=0x8728<br />
<br />
Or you can [[Kernel modules|load the modules]] during boot process by creating the following two files:<br />
<br />
{{hc|/etc/modules-load.d/it87.conf|2=<br />
it87<br />
}}<br />
<br />
{{hc|/etc/modprobe.d/it87.conf|2=<br />
options it87 force_id=0x8603<br />
}}<br />
<br />
Once the module is loaded you can use the ''sensors'' tool to probe the chip.<br />
<br />
Now you can also use [[fancontrol]] to control the speedsteps of your case fan.<br />
<br />
=== Laptop screen issues after running sensors-detect ===<br />
This is caused by lm-sensors messing with the Vcom values of the screen while probing for sensors.<br />
It has been discussed and solved at the forums already: https://bbs.archlinux.org/viewtopic.php?id=193048<br />
However, make sure to read through the thread carefully before running any of the suggested commands.</div>Dundeehttps://wiki.archlinux.org/index.php?title=EnhanceIO&diff=306961EnhanceIO2014-03-25T12:54:49Z<p>Dundee: </p>
<hr />
<div>[[Category:File systems]]<br />
[https://github.com/stec-inc/EnhanceIO EnhanceIO] makes it possible to use an SSD as a caching device for any other type of block device storage (HDD, Network, you name it) with almost zero configuration. Based on [[Flashcache]] is it much simpler to set up. Unlike [[Bcache]] there is no need to convert file systems.<br />
<br />
{{Warning|As always be careful and read the documentation carefully before attempting to use EnhanceIO, do not confuse your HDD and SDD and make sure the SSD does not have any important data on it.}}<br />
<br />
==Installation==<br />
<br />
Install {{AUR|enhanceio-dkms-git}} from the [[AUR]].<br />
<br />
{{Note|Throughout the page, {{ic|/dev/sda}} will be used to indicate the slow drive and {{ic|/dev/sdb}} will be used to indicate the fast drive. Be sure to change these examples to match your setup.}}<br />
<br />
===Setting up the module and drives===<br />
<br />
The EnhanceIO command line interface (eio_cli) is used to manage your setup.<br />
Set up caching on your fast ssd for your slow hdd like so:<br />
# eio_cli create -d /dev/sda -s /dev/sdb -c my_first_enhanceio<br />
This will use the default options which are safe, if you want to enhance speed even further you might want to add {{ic|-m wb}} to enable WriteBack mode instead of WriteThrough. This might put data itegrity at risk though.<br />
<br />
The cache drive is persistent now, which means even after a reboot it will still be used. If you want to deactive it first set the cache into read-only mode to not lose any yet unwritten blocks<br />
# eio_cli edit -c my_first_enhanceio -m ro<br />
Then wait until<br />
$ grep nr_dirty /proc/enhanceio/enchanceio_test/stats<br />
returns 0. Now all the blocks have been written to your slow hdd and it's safe to delete the caching device:<br />
# eio_cli delete -c my_first_enhanceio<br />
<br />
===Getting information on caches===<br />
<br />
To get basic information on caches in use try<br />
# eio_cli info<br />
To get detailed information use<br />
$ cat /proc/enhanceio/my_first_enhanceio/stats<br />
<br />
{{Tip|After initiating EnhanceIO I felt that my system had become more sluggish, this seems to be due to building up the cache first. Use your system like you normally would and open up those applications you would want to start quickly, maybe give it another reboot and observe how things fly.}}</div>Dundeehttps://wiki.archlinux.org/index.php?title=Fprint&diff=168621Fprint2011-11-03T23:30:36Z<p>Dundee: /* Setup fingerprint-gui */</p>
<hr />
<div>[[Category:Input devices (English)]]<br />
{{i18n|fprint}}<br />
<br />
{{Out of date}}<br />
<br />
From [http://reactivated.net/fprint/wiki/Pam_fprint Pam fprint - fprint project]:<br />
<br />
:''pam_fprint is a simple PAM module which uses libfprint's fingerprint processing and verification functionality for authentication. In other words, instead of seeing a password prompt, you're asked to scan your fingerprint.''<br />
<br />
The idea is to use the built-in fingerprint reader in some notebooks for login using PAM. This article will also explain how to use regular password for backup login method (solely fingerprint scanner is not recommended due to numerous reasons).<br />
<br />
== Prerequisites ==<br />
<br />
First, make sure you have one of the supported finger scanners. You can check if your device is supported by checking [http://www.thinkwiki.org/wiki/Integrated_Fingerprint_Reader this] list of supported devices. To check which one you have, type<br />
# lsusb<br />
<br />
You need to install '''pam''' and '''libfprint'''.<br />
# pacman -S pam libfprint<br />
<br />
== Installation ==<br />
<br />
Once you made sure your reader is supported, you are good to go<br />
# pacman -S pam_fprint<br />
<br />
== Configuration ==<br />
<br />
=== Permissions ===<br />
<br />
By default, only root has access to the device. You can create a signature from sudo, but then you can only use it for root user. The following solution from the Ubuntu forums may work for some people.<br />
<br />
1. If the group plugdev doesn't exist, create it<br />
# groupadd plugdev<br />
<br />
2. Add yourself to the group<br />
# gpasswd -a USER plugdev<br />
<br />
3. Allow USB access<br />
# chgrp -R plugdev /dev/bus/usb/<br />
<br />
=== Login configuration ===<br />
<br />
Modify the auth section of /etc/pam.d/login to this<br />
auth required pam_env.so<br />
auth sufficient pam_fprint.so<br />
auth sufficient pam_unix.so try_first_pass likeauth nullok<br />
auth required pam_deny.so<br />
<br />
This tries to use fingerprint login first, and if if fails or if it finds no fingerprint signatures in the give user's home directory, it proceeds to password login.<br />
<br />
You can also modify other files in /etc/pam.d/ using the same method, for example /etc/pam.d/gdm for GNOME's fingerprint login or /etc/pam.d/polkit-1 for GNOME PolicyKit Authentication.<br />
<br />
=== Create fingeprint signature ===<br />
<br />
Now you should be able to run the program under a normal user. To see the usage, run<br />
$ pam_fprint_enroll --help<br />
Chose one of the fingers and run <br />
$ pam_fprint_enroll -f #<br />
You will be asked to scan the given finger 3 times. After that, the signature is created in your home directory.<br />
<br />
== Setup fingerprint-gui ==<br />
<br />
An alternate fingerprint reader gui.<br />
This works with libfprint-unstable which has support for the new Upeksonly readers, such as,<br />
the new Thinkpad W510 T510 T410 T420 Upeksonly reader with USB ID 147e:2016<br />
<br />
http://www.thinkwiki.org/wiki/Integrated_Fingerprint_Reader<br />
<br />
http://www.n-view.net/Appliance/fingerprint/<br />
<br />
Install fingerprint-gui from AUR<br />
$ yaourt -S fingerprint-gui<br />
<br />
Please make sure your user is a member of "plugdev" and "scanner" group if you use UPEK non-free library. You may also have to log out and back in for these changes to take effect.<br />
# gpasswd -a USER plugdev<br />
# gpasswd -a USER scanner<br />
<br />
fingerprint-polkit-agent conflicts with files in /etc/xdg/autostart that must<br />
be removed:<br />
"polkit-gnome-authentication-agent-1.desktop" and<br />
"polkit-kde-authentication-agent-1.desktop".<br />
<br />
Edit your PAM configuration<br />
(e.g., /etc/pam.d/{login,su,sudo,gdm}).<br />
<br />
Change the auth section to read<br />
<br />
auth required pam_env.so<br />
auth sufficient pam_fingerprint-gui.so<br />
auth sufficient pam_unix.so try_first_pass likeauth nullok<br />
auth required pam_deny.so<br />
<br />
Add this to your ~/.bashrc file if you get an error saying that it can't connect to X desktop.<br />
xhost + &><br />
<br />
Now run fingerprint-gui and register fingerprints for the current user. You will need to run fingerprint-gui and register fingerprints as all users you want to use the fingerprint reader, i.e. as root to use it for "su" login.</div>Dundeehttps://wiki.archlinux.org/index.php?title=Lenovo_ThinkPad_T420&diff=168620Lenovo ThinkPad T4202011-11-03T23:25:03Z<p>Dundee: /* Untested */</p>
<hr />
<div>{{Stub}}<br />
[[Category:Lenovo (English)]]<br />
This article covers the installation and configuration of Arch Linux on a Lenovo T420 laptop.<br />
<br />
== Installation ==<br />
This laptop supports [https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface UEFI] as well as the traditional BIOS.<br />
<br />
Because this laptop has newer hardware than is currently supported with the official iso, its recommended that you try the [http://releng.archlinux.org/isos testisos]. The 2011.06.10 works fine.<br />
<br />
{{Note|The 2011.06.10 testiso has not been tested with UEFI (or at least not shared with this wiki.)}} <br />
<br />
The rest of the installation process can be followed with the [[Official_Arch_Linux_Install_Guide | Official Install Guide]].<br />
<br />
== Hardware ==<br />
All hardware not listed below works out-of-the-box.<br />
<br />
=== Webcam ===<br />
The integrated [https://wiki.archlinux.org/index.php/Webcam_Setup webcam] uses the {{codeline|uvcvideo}} module which you must load yourself<br />
<br />
=== FingerPrint Reader ===<br />
FingerPrint reader works great with fprint and PAM (installation of fingerprint-gui recommended).<br />
<br />
https://wiki.archlinux.org/index.php/Fprint#Setup_fingerprint-gui<br />
<br />
=== Untested ===<br />
* Esata<br />
* Firewire<br />
<br />
== Laptop Settings ==<br />
=== ACPI ===<br />
[https://wiki.archlinux.org/index.php/ACPI_modules ACPI] is well supported here. No obvious troubleshoots.<br />
<br />
=== Tp_smapi ===<br />
Unfortunately, [https://wiki.archlinux.org/index.php/Tp_smapi tp_smapi] is not yet supported on the Thinkpad T420. However, if you are dual booting with Windows, you can still control the battery charging thresholds with Lenovo's Power Manager which communicates directly to the battery controller.<br />
<br />
=== CPU Frequency Scaling ===<br />
[https://wiki.archlinux.org/index.php/CPU_Frequency_Scaling CPU Frequency Scaling] is fully supported with all the available processor models with this laptop.<br />
<br />
=== Laptop Mode Tools ===<br />
No significant issues were found using [https://wiki.archlinux.org/index.php/Laptop_Mode_Tools Laptop mode tools].<br />
<br />
=== PM-Utils ===<br />
Suspending and hibernating with [https://wiki.archlinux.org/index.php/Pm-utils PM-Utils] works as intended.<br />
<br />
== Troubleshoots ==<br />
=== Media Keys ===<br />
Media keys that work out of the box:<br />
* Wireless On/Off<br />
* Backlight Brightness settings<br />
* Thinklight<br />
* Mute<br />
<br />
You must find a workaround and bind the keys yourself for the rest of them.<br />
<br />
=== Rebind Forward and Back keys ===<br />
Keys forward and back (next to cursor keys) can be easily remapped to PageDown/PageUp.<br />
<br />
Install xmodmap:<br />
pacman -S xorg-server-utils<br />
<br />
Create ~/.Xmodmap file with content:<br />
keysym XF86Back = Page_Up<br />
keysym XF86Forward = Page_Down<br />
<br />
Add this line to your ~/.xinitrc to make it work:<br />
xmodmap ~/.Xmodmap<br />
<br />
You can also remap AudioPrev (Fn + left) and AudioNext (Fn + right) to Home/End:<br />
keysym XF86AudioNext = End<br />
keysym XF86AudioPrev = Home<br />
<br />
{{Note|You have to logout for the changes to take effect.}}<br />
<br />
=== Shutdown on Battery ===<br />
One user has reported that he his T420 was rebooting on shutdown on battery power. This was fixed by disabling the module {{codeline|ehci_hcd}} by adding {{codeline|rmmod ehci_hcd}} to your {{codeline|/etc/rc.local.shutdown}}<br />
<br />
=== Hang on Reboot ===<br />
This is a problem on many laptops and can be fixed by adding {{codeline|rmmod e1000e}} to your {{codeline|/etc/rc.local.shutdown}}</div>Dundeehttps://wiki.archlinux.org/index.php?title=Lenovo_ThinkPad_T420&diff=168618Lenovo ThinkPad T4202011-11-03T23:20:17Z<p>Dundee: </p>
<hr />
<div>{{Stub}}<br />
[[Category:Lenovo (English)]]<br />
This article covers the installation and configuration of Arch Linux on a Lenovo T420 laptop.<br />
<br />
== Installation ==<br />
This laptop supports [https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface UEFI] as well as the traditional BIOS.<br />
<br />
Because this laptop has newer hardware than is currently supported with the official iso, its recommended that you try the [http://releng.archlinux.org/isos testisos]. The 2011.06.10 works fine.<br />
<br />
{{Note|The 2011.06.10 testiso has not been tested with UEFI (or at least not shared with this wiki.)}} <br />
<br />
The rest of the installation process can be followed with the [[Official_Arch_Linux_Install_Guide | Official Install Guide]].<br />
<br />
== Hardware ==<br />
All hardware not listed below works out-of-the-box.<br />
<br />
=== Webcam ===<br />
The integrated [https://wiki.archlinux.org/index.php/Webcam_Setup webcam] uses the {{codeline|uvcvideo}} module which you must load yourself<br />
<br />
=== FingerPrint Reader ===<br />
FingerPrint reader works great with fprint and PAM (installation of fingerprint-gui recommended).<br />
<br />
https://wiki.archlinux.org/index.php/Fprint#Setup_fingerprint-gui<br />
<br />
=== Untested ===<br />
* Bluetooth<br />
* Fingerprint Reader<br />
* Esata<br />
* Firewire<br />
<br />
== Laptop Settings ==<br />
=== ACPI ===<br />
[https://wiki.archlinux.org/index.php/ACPI_modules ACPI] is well supported here. No obvious troubleshoots.<br />
<br />
=== Tp_smapi ===<br />
Unfortunately, [https://wiki.archlinux.org/index.php/Tp_smapi tp_smapi] is not yet supported on the Thinkpad T420. However, if you are dual booting with Windows, you can still control the battery charging thresholds with Lenovo's Power Manager which communicates directly to the battery controller.<br />
<br />
=== CPU Frequency Scaling ===<br />
[https://wiki.archlinux.org/index.php/CPU_Frequency_Scaling CPU Frequency Scaling] is fully supported with all the available processor models with this laptop.<br />
<br />
=== Laptop Mode Tools ===<br />
No significant issues were found using [https://wiki.archlinux.org/index.php/Laptop_Mode_Tools Laptop mode tools].<br />
<br />
=== PM-Utils ===<br />
Suspending and hibernating with [https://wiki.archlinux.org/index.php/Pm-utils PM-Utils] works as intended.<br />
<br />
== Troubleshoots ==<br />
=== Media Keys ===<br />
Media keys that work out of the box:<br />
* Wireless On/Off<br />
* Backlight Brightness settings<br />
* Thinklight<br />
* Mute<br />
<br />
You must find a workaround and bind the keys yourself for the rest of them.<br />
<br />
=== Rebind Forward and Back keys ===<br />
Keys forward and back (next to cursor keys) can be easily remapped to PageDown/PageUp.<br />
<br />
Install xmodmap:<br />
pacman -S xorg-server-utils<br />
<br />
Create ~/.Xmodmap file with content:<br />
keysym XF86Back = Page_Up<br />
keysym XF86Forward = Page_Down<br />
<br />
Add this line to your ~/.xinitrc to make it work:<br />
xmodmap ~/.Xmodmap<br />
<br />
You can also remap AudioPrev (Fn + left) and AudioNext (Fn + right) to Home/End:<br />
keysym XF86AudioNext = End<br />
keysym XF86AudioPrev = Home<br />
<br />
{{Note|You have to logout for the changes to take effect.}}<br />
<br />
=== Shutdown on Battery ===<br />
One user has reported that he his T420 was rebooting on shutdown on battery power. This was fixed by disabling the module {{codeline|ehci_hcd}} by adding {{codeline|rmmod ehci_hcd}} to your {{codeline|/etc/rc.local.shutdown}}<br />
<br />
=== Hang on Reboot ===<br />
This is a problem on many laptops and can be fixed by adding {{codeline|rmmod e1000e}} to your {{codeline|/etc/rc.local.shutdown}}</div>Dundeehttps://wiki.archlinux.org/index.php?title=Lenovo_ThinkPad_T420&diff=168617Lenovo ThinkPad T4202011-11-03T23:19:59Z<p>Dundee: /* Webcam */</p>
<hr />
<div>{{Stub}}<br />
{{Note|This article is currently based off of one user's experience. It is possible that you may other troubleshoots not listed or mentioned.}}<br />
[[Category:Lenovo (English)]]<br />
This article covers the installation and configuration of Arch Linux on a Lenovo T420 laptop.<br />
<br />
== Installation ==<br />
This laptop supports [https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface UEFI] as well as the traditional BIOS.<br />
<br />
Because this laptop has newer hardware than is currently supported with the official iso, its recommended that you try the [http://releng.archlinux.org/isos testisos]. The 2011.06.10 works fine.<br />
<br />
{{Note|The 2011.06.10 testiso has not been tested with UEFI (or at least not shared with this wiki.)}} <br />
<br />
The rest of the installation process can be followed with the [[Official_Arch_Linux_Install_Guide | Official Install Guide]].<br />
<br />
== Hardware ==<br />
All hardware not listed below works out-of-the-box.<br />
<br />
=== Webcam ===<br />
The integrated [https://wiki.archlinux.org/index.php/Webcam_Setup webcam] uses the {{codeline|uvcvideo}} module which you must load yourself<br />
<br />
=== FingerPrint Reader ===<br />
FingerPrint reader works great with fprint and PAM (installation of fingerprint-gui recommended).<br />
<br />
https://wiki.archlinux.org/index.php/Fprint#Setup_fingerprint-gui<br />
<br />
=== Untested ===<br />
* Bluetooth<br />
* Fingerprint Reader<br />
* Esata<br />
* Firewire<br />
<br />
== Laptop Settings ==<br />
=== ACPI ===<br />
[https://wiki.archlinux.org/index.php/ACPI_modules ACPI] is well supported here. No obvious troubleshoots.<br />
<br />
=== Tp_smapi ===<br />
Unfortunately, [https://wiki.archlinux.org/index.php/Tp_smapi tp_smapi] is not yet supported on the Thinkpad T420. However, if you are dual booting with Windows, you can still control the battery charging thresholds with Lenovo's Power Manager which communicates directly to the battery controller.<br />
<br />
=== CPU Frequency Scaling ===<br />
[https://wiki.archlinux.org/index.php/CPU_Frequency_Scaling CPU Frequency Scaling] is fully supported with all the available processor models with this laptop.<br />
<br />
=== Laptop Mode Tools ===<br />
No significant issues were found using [https://wiki.archlinux.org/index.php/Laptop_Mode_Tools Laptop mode tools].<br />
<br />
=== PM-Utils ===<br />
Suspending and hibernating with [https://wiki.archlinux.org/index.php/Pm-utils PM-Utils] works as intended.<br />
<br />
== Troubleshoots ==<br />
=== Media Keys ===<br />
Media keys that work out of the box:<br />
* Wireless On/Off<br />
* Backlight Brightness settings<br />
* Thinklight<br />
* Mute<br />
<br />
You must find a workaround and bind the keys yourself for the rest of them.<br />
<br />
=== Rebind Forward and Back keys ===<br />
Keys forward and back (next to cursor keys) can be easily remapped to PageDown/PageUp.<br />
<br />
Install xmodmap:<br />
pacman -S xorg-server-utils<br />
<br />
Create ~/.Xmodmap file with content:<br />
keysym XF86Back = Page_Up<br />
keysym XF86Forward = Page_Down<br />
<br />
Add this line to your ~/.xinitrc to make it work:<br />
xmodmap ~/.Xmodmap<br />
<br />
You can also remap AudioPrev (Fn + left) and AudioNext (Fn + right) to Home/End:<br />
keysym XF86AudioNext = End<br />
keysym XF86AudioPrev = Home<br />
<br />
{{Note|You have to logout for the changes to take effect.}}<br />
<br />
=== Shutdown on Battery ===<br />
One user has reported that he his T420 was rebooting on shutdown on battery power. This was fixed by disabling the module {{codeline|ehci_hcd}} by adding {{codeline|rmmod ehci_hcd}} to your {{codeline|/etc/rc.local.shutdown}}<br />
<br />
=== Hang on Reboot ===<br />
This is a problem on many laptops and can be fixed by adding {{codeline|rmmod e1000e}} to your {{codeline|/etc/rc.local.shutdown}}</div>Dundeehttps://wiki.archlinux.org/index.php?title=Lenovo_ThinkPad_T420&diff=168613Lenovo ThinkPad T4202011-11-03T22:51:52Z<p>Dundee: /* Rebind Forward and Back keys */</p>
<hr />
<div>{{Stub}}<br />
{{Note|This article is currently based off of one user's experience. It is possible that you may other troubleshoots not listed or mentioned.}}<br />
[[Category:Lenovo (English)]]<br />
This article covers the installation and configuration of Arch Linux on a Lenovo T420 laptop.<br />
<br />
== Installation ==<br />
This laptop supports [https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface UEFI] as well as the traditional BIOS.<br />
<br />
Because this laptop has newer hardware than is currently supported with the official iso, its recommended that you try the [http://releng.archlinux.org/isos testisos]. The 2011.06.10 works fine.<br />
<br />
{{Note|The 2011.06.10 testiso has not been tested with UEFI (or at least not shared with this wiki.)}} <br />
<br />
The rest of the installation process can be followed with the [[Official_Arch_Linux_Install_Guide | Official Install Guide]].<br />
<br />
== Hardware ==<br />
All hardware not listed below works out-of-the-box.<br />
<br />
=== Webcam ===<br />
The integrated [https://wiki.archlinux.org/index.php/Webcam_Setup webcam] uses the {{codeline|uvcvideo}} module which you must load yourself<br />
<br />
=== Untested ===<br />
* Bluetooth<br />
* Fingerprint Reader<br />
* Esata<br />
* Firewire<br />
<br />
== Laptop Settings ==<br />
=== ACPI ===<br />
[https://wiki.archlinux.org/index.php/ACPI_modules ACPI] is well supported here. No obvious troubleshoots.<br />
<br />
=== Tp_smapi ===<br />
Unfortunately, [https://wiki.archlinux.org/index.php/Tp_smapi tp_smapi] is not yet supported on the Thinkpad T420. However, if you are dual booting with Windows, you can still control the battery charging thresholds with Lenovo's Power Manager which communicates directly to the battery controller.<br />
<br />
=== CPU Frequency Scaling ===<br />
[https://wiki.archlinux.org/index.php/CPU_Frequency_Scaling CPU Frequency Scaling] is fully supported with all the available processor models with this laptop.<br />
<br />
=== Laptop Mode Tools ===<br />
No significant issues were found using [https://wiki.archlinux.org/index.php/Laptop_Mode_Tools Laptop mode tools].<br />
<br />
=== PM-Utils ===<br />
Suspending and hibernating with [https://wiki.archlinux.org/index.php/Pm-utils PM-Utils] works as intended.<br />
<br />
== Troubleshoots ==<br />
=== Media Keys ===<br />
Media keys that work out of the box:<br />
* Wireless On/Off<br />
* Backlight Brightness settings<br />
* Thinklight<br />
* Mute<br />
<br />
You must find a workaround and bind the keys yourself for the rest of them.<br />
<br />
=== Rebind Forward and Back keys ===<br />
Keys forward and back (next to cursor keys) can be easily remapped to PageDown/PageUp.<br />
<br />
Install xmodmap:<br />
pacman -S xorg-server-utils<br />
<br />
Create ~/.Xmodmap file with content:<br />
keysym XF86Back = Page_Up<br />
keysym XF86Forward = Page_Down<br />
<br />
Add this line to your ~/.xinitrc to make it work:<br />
xmodmap ~/.Xmodmap<br />
<br />
You can also remap AudioPrev (Fn + left) and AudioNext (Fn + right) to Home/End:<br />
keysym XF86AudioNext = End<br />
keysym XF86AudioPrev = Home<br />
<br />
{{Note|You have to logout for the changes to take effect.}}<br />
<br />
=== Shutdown on Battery ===<br />
One user has reported that he his T420 was rebooting on shutdown on battery power. This was fixed by disabling the module {{codeline|ehci_hcd}} by adding {{codeline|rmmod ehci_hcd}} to your {{codeline|/etc/rc.local.shutdown}}<br />
<br />
=== Hang on Reboot ===<br />
This is a problem on many laptops and can be fixed by adding {{codeline|rmmod e1000e}} to your {{codeline|/etc/rc.local.shutdown}}</div>Dundeehttps://wiki.archlinux.org/index.php?title=Lenovo_ThinkPad_T420&diff=168467Lenovo ThinkPad T4202011-11-02T18:55:37Z<p>Dundee: </p>
<hr />
<div>{{Stub}}<br />
{{Note|This article is currently based off of one user's experience. It is possible that you may other troubleshoots not listed or mentioned.}}<br />
[[Category:Lenovo (English)]]<br />
This article covers the installation and configuration of Arch Linux on a Lenovo T420 laptop.<br />
<br />
== Installation ==<br />
This laptop supports [https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface UEFI] as well as the traditional BIOS.<br />
<br />
Because this laptop has newer hardware than is currently supported with the official iso, its recommended that you try the [http://releng.archlinux.org/isos testisos]. The 2011.06.10 works fine.<br />
<br />
{{Note|The 2011.06.10 testiso has not been tested with UEFI (or at least not shared with this wiki.)}} <br />
<br />
The rest of the installation process can be followed with the [[Official_Arch_Linux_Install_Guide | Official Install Guide]].<br />
<br />
== Hardware ==<br />
All hardware not listed below works out-of-the-box.<br />
<br />
=== Webcam ===<br />
The integrated [https://wiki.archlinux.org/index.php/Webcam_Setup webcam] uses the {{codeline|uvcvideo}} module which you must load yourself<br />
<br />
=== Untested ===<br />
* Bluetooth<br />
* Fingerprint Reader<br />
* Esata<br />
* Firewire<br />
<br />
== Laptop Settings ==<br />
=== ACPI ===<br />
[https://wiki.archlinux.org/index.php/ACPI_modules ACPI] is well supported here. No obvious troubleshoots.<br />
<br />
=== Tp_smapi ===<br />
Unfortunately, [https://wiki.archlinux.org/index.php/Tp_smapi tp_smapi] is not yet supported on the Thinkpad T420. However, if you are dual booting with Windows, you can still control the battery charging thresholds with Lenovo's Power Manager which communicates directly to the battery controller.<br />
<br />
=== CPU Frequency Scaling ===<br />
[https://wiki.archlinux.org/index.php/CPU_Frequency_Scaling CPU Frequency Scaling] is fully supported with all the available processor models with this laptop.<br />
<br />
=== Laptop Mode Tools ===<br />
No significant issues were found using [https://wiki.archlinux.org/index.php/Laptop_Mode_Tools Laptop mode tools].<br />
<br />
=== PM-Utils ===<br />
Suspending and hibernating with [https://wiki.archlinux.org/index.php/Pm-utils PM-Utils] works as intended.<br />
<br />
== Troubleshoots ==<br />
=== Media Keys ===<br />
Media keys that work out of the box:<br />
* Wireless On/Off<br />
* Backlight Brightness settings<br />
* Thinklight<br />
* Mute<br />
<br />
You must find a workaround and bind the keys yourself for the rest of them.<br />
<br />
=== Rebind Forward and Back keys ===<br />
Keys forward and back (next to cursor keys) can be easily remapped to PageDown/PageUp.<br />
<br />
Install xmodmap:<br />
pacman -S xorg-server-utils<br />
<br />
Create ~/.Xmodmap file with content:<br />
keysym XF86Back = Page_Up<br />
keysym XF86Forward = Page_Down<br />
<br />
Test if it works:<br />
xmodmap ~/.Xmodmap<br />
<br />
Add this command to ~/.xinitrc to make it permanent<br />
<br />
=== Shutdown on Battery ===<br />
One user has reported that he his T420 was rebooting on shutdown on battery power. This was fixed by disabling the module {{codeline|ehci_hcd}} by adding {{codeline|rmmod ehci_hcd}} to your {{codeline|/etc/rc.local.shutdown}}<br />
<br />
=== Hang on Reboot ===<br />
This is a problem on many laptops and can be fixed by adding {{codeline|rmmod e1000e}} to your {{codeline|/etc/rc.local.shutdown}}</div>Dundeehttps://wiki.archlinux.org/index.php?title=Benchmarking/Data_storage_devices&diff=168392Benchmarking/Data storage devices2011-11-01T22:08:57Z<p>Dundee: added Intel 310</p>
<hr />
<div>[[Category: Storage (English)]]<br />
{{Article summary start}}<br />
{{Article summary text|This article covers several Linux-native apps that benchmark I/O devices such as HDDs, SSDs, USB thumb drives, etc. There is also a "database" section specific to SSDs meant to capture user-entered benchmark results.}}<br />
{{Article summary heading|Related Articles}}<br />
{{Article summary wiki|Solid State Drives}}<br />
{{Article summary wiki|Benchmarking}}<br />
{{Article summary end}}<br />
<br />
==Introduction==<br />
Several I/O benchmark options exist under Linux.<br />
<br />
* Using hddparm with the -Tt switch, one can time sequential reads. This method is '''independent''' of partition alignment!<br />
* There is a graphical benchmark called palimpsest contained in the [http://www.archlinux.org/packages/?sort=&arch=&repo=&q=gnome-disk-utility&maintainer=&last_update=&flagged=&limit=50 gnome-disk-utility] package that will give min/max/ave reads along with ave access time and a nice graphical display. This method is '''independent''' of partition alignment!'''<br />
* The dd utility can be used to measure both reads and writes. This method is '''dependent''' on partition alignment! In other words, if you failed to properly align your partitions, this fact will be seen here since you're writing and reading to a mounted filesystem.<br />
* [http://wiki.archlinux.org/index.php/Benchmarking#Bonnie.2B.2B Bonnie++]<br />
<br />
== Using hdparm ==<br />
<br />
# hdparm -Tt /dev/sdX<br />
/dev/sdX:<br />
Timing cached reads: x MB in y seconds = z MB/sec<br />
Timing buffered disk reads: x MB in y seconds = z MB/sec<br />
<br />
{{Note|One should run the above command 4-5 times and manually average the results for an accurate evaluation of read speed per the hddparm man page.}}<br />
<br />
== Using palimpsest ==<br />
<br />
# sudo palimpsest<br />
<br />
Users will need to navigate through the GUI to the benchmark button.<br />
<br />
== Using dd ==<br />
<br />
{{Note|This method requires the command to be executed from a mounted partition on the device of interest!}}<br />
<br />
First, enter a directory on the SSD with at least 1.1 GB of free space (and one that obviously gives your user wrx permissions) and write a test file to measure write speeds and to give the device something to read:<br />
<br />
$ cd /path/to/SSD<br />
$ dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
1024+0 records in<br />
1024+0 records out<br />
w bytes (x GB) copied, y s, z MB/s<br />
<br />
Next, clear the buffer-cache to accurately measure read speeds directly from the device:<br />
<br />
# echo 3 > /proc/sys/vm/drop_caches<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
w bytes (x GB) copied, y s, z MB/s<br />
<br />
Now that the last file is in the buffer, repeat the command to see the speed of the buffer-cache:<br />
<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
w bytes (x GB) copied, y s, z GB/s<br />
<br />
{{Note|One should run the above command 4-5 times and manually average the results for an accurate evaluation of the buffer read speed.}}<br />
<br />
Finally, delete the temp file<br />
$ rm tempfile<br />
<br />
== Model Specific Data ==<br />
Please contribute to this section using the template below to post results obtained.<br />
<br />
See [http://www.anandtech.com/bench/SSD/65 here] for a nice database of benchmarks.<br />
<br />
=== Template ===<br />
*SSD:<br />
*Model Number:<br />
*Firmware Version:<br />
*Capacity: x GB<br />
*User:<br />
[*Filesystem: write something about your FS, optional]<br />
[*Notes: additional Notes, optional]<br />
<br />
# hdparm -Tt /dev/sdx<br />
<br />
Minimum Read Rate: x MB/s<br />
Maximum Read Rate: x MB/s<br />
Average Read Rate: x MS/s<br />
Average Access Time x ms<br />
<br />
$ dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
# echo 3 > /proc/sys/vm/drop_caches<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
<br />
=== Crucial ===<br />
==== Crucial C300 ====<br />
*SSD: Crucial C300 (SATA 3: 6Gb/s)<br />
*Model Number: CTFDDAC128MAG-1G1<br />
*Capacity: 128 GB<br />
*User: jac<br />
<br />
# hdparm -Tt /dev/sdb<br />
/dev/sda:<br />
Timing cached reads: 24112 MB in 2.00 seconds = 12072.84 MB/sec<br />
Timing buffered disk reads: 1056 MB in 3.00 seconds = 351.58 MB/sec<br />
<br />
Minimum Read Rate: 350.88 MB/s<br />
Maximum Read Rate: 351.58 MB/s<br />
Average Read Rate: 351.264 MB/s<br />
<br />
$ dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 7.77883 s, 138 MB/s<br />
<br />
# echo 3 > /proc/sys/vm/drop_caches<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 2.88752 s, 372 MB/s<br />
<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 0.164471 s, 6.5 GB/s<br />
<br />
==== Crucial M4 ====<br />
*SSD: Crucial M4 (SATA 3: 6Gb/s)<br />
*Model Number: M4-CT128M4SSD2 (Firmware: 0009)<br />
*Capacity: 128 GB<br />
*User: lynix<br />
*Filesystem: ext4 on LVM<br />
*Notes: connected to SATAII 3Gb/s port while benchmarking. firmware matters!<br />
<br />
# hdparm -Tt /dev/sde<br />
/dev/sde:<br />
Timing cached reads: 19094 MB in 2.00 seconds = 9559.40 MB/sec<br />
Timing buffered disk reads: 786 MB in 3.00 seconds = 261.63 MB/sec<br />
<br />
Minimum Read Rate: 271.7 MB/s<br />
Maximum Read Rate: 381.7 MB/s<br />
Average Read Rate: 279.0 MB/s<br />
<br />
Minimum Write Rate: 58.6 MB/s<br />
Maximum Write Rate: 258.9 MB/s<br />
Average Write Rate: 194.8 MB/s<br />
<br />
$ dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 5.57478 s, 193 MB/s<br />
<br />
# echo 3 > /proc/sys/vm/drop_caches<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 4.00688 s, 268 MB/s<br />
<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 0.157567 s, 6.8 GB/s<br />
<br />
=== Intel ===<br />
==== Intel 310 Soda Creek ====<br />
*SSD: Intel 310 Soda Creek<br />
*Model Number: SSDMAEMC040G2<br />
*Firmware Version: 2CV1023M<br />
*Capacity: 40 GB<br />
*User: dundee<br />
*Filesystem: ext4<br />
<br />
# hdparm -Tt /dev/sdb<br />
/dev/sdb:<br />
Timing cached reads: 6278 MB in 2.00 seconds = 3141.39 MB/sec<br />
Timing buffered disk reads: 784 MB in 3.00 seconds = 260.96 MB/sec<br />
<br />
Minimum Read Rate: 189.7 MB/s<br />
Maximum Read Rate: 281.1 MB/s<br />
Average Read Rate: 277.1 MS/s<br />
Minimum Write Rate: 30.3 MB/s<br />
Maximum Write Rate: 44.6 MB/s<br />
Average Write Rate: 43.8 MS/s<br />
<br />
Average Access Time 0.1 ms<br />
<br />
$ dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 24.3013 s, 44.2 MB/s<br />
<br />
# echo 3 > /proc/sys/vm/drop_caches<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 5.45325 s, 197 MB/s<br />
<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 0.255569 s, 4.2 GB/s<br />
<br />
==== Intel X18-M (G2) ====<br />
*SSD: Intel X18-M Generation 2<br />
*Model Number: SSDSA1M1602GN<br />
*Capacity: 160 GB<br />
*User: Cirk<br />
<br />
# hdparm -Tt /dev/sda<br />
Timing cached reads: 2826 MB in 2.00 seconds = 1414.39 MB/sec<br />
Timing buffered disk reads: 694 MB in 3.00 seconds = 231.14 MB/sec<br />
<br />
Minimum Read Rate: 216.1 MB/s<br />
Maximum Read Rate: 283.5 MB/s<br />
Average Read Rate: 271.2 MB/s<br />
Average Access Time 0.1 ms<br />
<br />
$ dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 10.4608 s, 103 MB/s<br />
<br />
# echo 3 > /proc/sys/vm/drop_caches<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 4.0866 s, 263 MB/s<br />
<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 0.403244 s, 2.7 GB/s<br />
<br />
==== Intel X25-M (G2) ====<br />
*SSD: Intel X25-M Generation 2<br />
*Model Number: SSDSA2MH080G2R5<br />
*Capacity: 80 GB<br />
*User: Graysky<br />
<br />
# hdparm -Tt /dev/sdb<br />
/dev/sdb:<br />
Timing cached reads: 15644 MB in 1.99 seconds = 7845.48 MB/sec<br />
Timing buffered disk reads: 788 MB in 3.00 seconds = 262.52 MB/sec<br />
<br />
Minimum Read Rate: 253.6 MB/s<br />
Maximum Read Rate: 286.1 MB/s<br />
Average Read Rate: 282.6 MB/s<br />
Average Access Time 0.1 ms<br />
<br />
$ dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 13.3236 s, 80.6 MB/s<br />
<br />
# echo 3 > /proc/sys/vm/drop_caches<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 4.00297 s, 268 MB/s<br />
<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 0.169713 s, 6.3 GB/s<br />
<br />
==== Intel X25-M (G2) ====<br />
*SSD: Intel X25-M Generation 2<br />
*Model Number: SSDSA2M160G2GC<br />
*Capacity: 160 GB<br />
*User: fackamato<br />
<br />
# hdparm -Tt /dev/sda<br />
Timing cached reads: 2890 MB in 2.00 seconds = 1445.86 MB/sec<br />
Timing buffered disk reads: 738 MB in 3.00 seconds = 245.69 MB/sec<br />
<br />
Minimum Read Rate: 244.3 MB/s<br />
Maximum Read Rate: 278.6 MB/s<br />
Average Read Rate: 273.3 MB/s<br />
Average Access Time 0.1 ms<br />
<br />
$ dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 10.8582 s, 98.9 MB/s<br />
<br />
# echo 3 > /proc/sys/vm/drop_caches<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 4.09679 s, 262 MB/s<br />
<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 0.363709 s, 3.0 GB/s<br />
<br />
==== Intel X25-M (G2) ====<br />
*SSD: Intel X25-M Generation 2<br />
*Model Number: SSDSA2M080G2C<br />
*Capacity: 80 GB<br />
*User: Cirk<br />
<br />
# hdparm -Tt /dev/sda<br />
Timing cached reads: 9384 MB in 2.00 seconds = 4694.29 MB/sec<br />
Timing buffered disk reads: 808 MB in 3.01 seconds = 268.64 MB/sec<br />
<br />
Minimum Read Rate: 229.9 MB/s<br />
Maximum Read Rate: 281.6 MB/s<br />
Average Read Rate: 272.4 MB/s<br />
Average Access Time 0.1 ms<br />
<br />
$ dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 15.1671 s, 70.8 MB/s<br />
<br />
# echo 3 > /proc/sys/vm/drop_caches<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 5.15237 s, 208 MB/s<br />
<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 0.256211 s, 4.2 GB/s<br />
<br />
==== Intel X25-M (G2) ====<br />
*SSD: Intel X25-M Generation 2<br />
*Model Number: SSDSA2MH120G2K5<br />
*Capacity: 120 GB<br />
*User: timo.hardebusch<br />
<br />
# hdparm -Tt /dev/sdb<br />
/dev/sdb:<br />
Timing cached reads: 4358 MB in 2.00 seconds = 2178.89 MB/sec<br />
Timing buffered disk reads: 752 MB in 3.01 seconds = 250.07 MB/sec<br />
<br />
Minimum Read Rate: 259.1 MB/s<br />
Maximum Read Rate: 283.3 MB/s<br />
Average Read Rate: 280.6 MB/s<br />
Average Access Time 0.1 ms<br />
<br />
$ dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 10.1452 s, 106 MB/s<br />
<br />
# echo 3 > /proc/sys/vm/drop_caches<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 4.05181 s, 265 MB/s<br />
<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 0.369308 s, 2.9 GB/s<br />
<br />
=== OCZ ===<br />
==== OCZ-VERTEX 60gb ====<br />
*SSD:OCZ-VERTEX<br />
*Model Number:Firmware 1.5<br />
*Capacity: 60 GB<br />
*User:Surfed<br />
<br />
# hdparm -Tt /dev/sda<br />
/dev/sda:<br />
Timing cached reads: 16306 MB in 2.00 seconds = 8162.55 MB/sec<br />
Timing buffered disk reads: 646 MB in 3.00 seconds = 215.09 MB/sec<br />
<br />
<br />
Minimum Read Rate: 226.7 MB/s<br />
Maximum Read Rate: 275.2 MB/s<br />
Average Read Rate: 256.9 MB/s<br />
Average Access Time 0.1 ms<br />
<br />
$ dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 7.5581 s, 142 MB/s<br />
<br />
# echo 3 > /proc/sys/vm/drop_caches<br />
<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 4.55881 s, 236 MB/s<br />
<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 0.205299 s, 5.2 GB/s<br />
<br />
==== OCZ-VERTEX3 120GO ====<br />
*SSD:OCZ-VERTEX3<br />
*Firmware Version:2.06<br />
*Capacity: 6Gb/s SATA III<br />
*User:[[User:Sputnick]]<br />
*Notes: tested on '''SATA II 3Gb/s Dell Optiplex 780 motherboard''' 0C27VV <br />
<br />
# hdparm -Tt /dev/sdc<br />
<br />
/dev/sdc:<br />
Timing cached reads: 13702 MB in 2.00 seconds = 6859.89 MB/sec<br />
Timing buffered disk reads: 644 MB in 3.00 seconds = 214.40 MB/sec<br />
<br />
<br />
$ dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
1024+0 enregistrements lus<br />
1024+0 enregistrements écrits<br />
1073741824 octets (1,1 GB) copiés, 4,37831 s, 245 MB/s<br />
<br />
# echo 3 > /proc/sys/vm/drop_caches<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 enregistrements lus<br />
1024+0 enregistrements écrits<br />
1073741824 octets (1,1 GB) copiés, 4,76932 s, 225 MB/s<br />
<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 enregistrements lus<br />
1024+0 enregistrements écrits<br />
1073741824 octets (1,1 GB) copiés, 0,234682 s, 4,6 GB/s<br />
<br />
==== OCZ-VERTEX-TURBO 30gb ====<br />
*SSD:OCZ-VERTEX-TURBO<br />
*Model Number:Firmware 1.5<br />
*Capacity: 30 GB<br />
*User:ScottKidder<br />
<br />
# hdparm -Tt /dev/sda<br />
/dev/sda:<br />
Timing cached reads: 6286 MB in 2.00 seconds = 3149.62 MB/sec<br />
Timing buffered disk reads: 630 MB in 3.01 seconds = 209.10 MB/sec<br />
<br />
Minimum Read Rate: 211.8 MB/s<br />
Maximum Read Rate: 254.1 MB/s<br />
Average Read Rate: 249.2 MB/s<br />
Average Access Time 0.1 ms<br />
<br />
$ dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 21.5437 s, 49.8 MB/s<br />
<br />
# echo 3 > /proc/sys/vm/drop_caches<br />
<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 9.34704 s, 115 MB/s<br />
<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 0.40667 s, 2.6 GB/s<br />
<br />
==== OCZ-VERTEX2 240GB ====<br />
*SSD: OCZ<br />
*Model Number: Vertex2<br />
*Capacity: 240GB<br />
*User: longint<br />
*Filesystem: btrfs compression=lzo,space_cache<br />
<br />
# hdparm -Tt /dev/sda<br />
/dev/sda:<br />
Timing cached reads: 10972 MB in 2.00 seconds = 5489.70 MB/sec<br />
Timing buffered disk reads: 648 MB in 3.00 seconds = 215.96 MB/sec<br />
<br />
# dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 1.26013 s, 852 MB/s<br />
<br />
# echo 3 > /proc/sys/vm/drop_caches<br />
<br />
# dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 4.45112 s, 241 MB/s<br />
<br />
# dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 0.320492 s, 3.4 GB/s<br />
<br />
==== OCZ-VERTEX3 120GB ====<br />
*SSD:OCZ-VERTEX3 SATA III<br />
*Firmware Version:2.13<br />
*Capacity: 120 GB<br />
*Filesystem: ext4 with discard and commit=60<br />
*[[User:muflone]]<br />
<br />
# hdparm -Tt /dev/sdc<br />
/dev/sdc:<br />
Timing cached reads: 23870 MB in 2.00 seconds = 11950.12 MB/sec<br />
Timing buffered disk reads: 866 MB in 3.00 seconds = 288.36 MB/sec<br />
<br />
$ dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 2.85159 s, 377 MB/s<br />
<br />
# echo 3 > /proc/sys/vm/drop_caches<br />
<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 3.6931 s, 291 MB/s<br />
<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 0.10383 s, 10.3 GB/s<br />
<br />
==== OCZ-AGILITY3 120GB ====<br />
*SSD:OCZ-AGILITY3 SATA III<br />
*Firmware Version:2.15<br />
*Capacity: 120 GB<br />
*Filesystem: ext4 with discard<br />
*[[User:bardo]]<br />
<br />
# hdparm -Tt /dev/sda<br />
/dev/sda:<br />
Timing cached reads: 27738 MB in 2.00 seconds = 13889.38 MB/sec<br />
Timing buffered disk reads: 1158 MB in 3.01 seconds = 385.08 MB/sec<br />
<br />
$ dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 2.41537 s, 445 MB/s<br />
<br />
# echo 3 > /proc/sys/vm/drop_caches<br />
<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 2.35961 s, 455 MB/s<br />
<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 0.130664 s, 8.2 GB/s<br />
<br />
=== Samsung ===<br />
==== SAMSUNG 128GB / SATAII ====<br />
*SSD: SAMSUNG 128GB / SATAII<br />
*Model Number: MMCQE28GFMUP-MVA<br />
*Capacity: 128 GB<br />
*User: Cirk<br />
<br />
# hdparm -Tt /dev/sda<br />
Timing cached reads: 2612 MB in 2.00 seconds = 1307.40 MB/sec<br />
Timing buffered disk reads: 294 MB in 3.01 seconds = 97.67 MB/sec<br />
<br />
Minimum Read Rate: 108.7 MB/s<br />
Maximum Read Rate: 114.5 MB/s<br />
Average Read Rate: 113.7 MB/s<br />
Average Access Time 0.2 ms<br />
<br />
$ dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 23.7352 s, 45.2 MB/s<br />
<br />
# echo 3 > /proc/sys/vm/drop_caches<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 10.7563 s, 99.8 MB/s<br />
<br />
$ dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 0.464824 s, 2.3 GB/s<br />
<br />
==== SAMSUNG 470 64GB ====<br />
*SSD: SAMSUNG 470 64GB<br />
*Model Number: MZ-5PA064/US<br />
*Firmware: AXM070Q1<br />
*Capacity: 64 GB<br />
*User: skylinux<br />
<br />
# hdparm -Tt /dev/sda<br />
Timing cached reads: 1736 MB in 2.00 seconds = 868.62 MB/sec<br />
Timing buffered disk reads: 516 MB in 3.00 seconds = 171.87 MB/sec<br />
<br />
Minimum Read Rate: 276.5 MB/s<br />
Maximum Read Rate: 278.8 MB/s<br />
Average Read Rate: 278.2 MB/s<br />
Average Access Time 0.2 ms<br />
<br />
# dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 5.69714 s, 188 MB/s<br />
<br />
# echo 3 > /proc/sys/vm/drop_caches<br />
# dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 5.25116 s, 204 MB/s<br />
<br />
# dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 1.05824 s, 1.0 GB/s<br />
<br />
=== Kingston ===<br />
==== Kingston SSDNow V+100 128 GB ====<br />
*SSD: Kingston SSDNow v+100 128 GB<br />
*Model Number: SVP100S2128G<br />
*Firmware: CJRA0202<br />
*Capacity: 128 GB<br />
*User: Tuxe<br />
<br />
# hdparm -Tt /dev/sda<br />
Timing cached reads: 11598 MB in 1.99 seconds = 5822.73 MB/sec<br />
Timing buffered disk reads: 598 MB in 3.01 seconds = 198.90 MB/sec<br />
<br />
Minimum Read Rate: 145.8 MB/s<br />
Maximum Read Rate: 259.2 MB/s<br />
Average Read Rate: 243.5 MB/s<br />
Average Access Time 0.1 ms<br />
<br />
# dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 9.74199 s, 110 MB/s<br />
<br />
# echo 3 > /proc/sys/vm/drop_caches <br />
# dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 4.62165 s, 232 MB/s<br />
<br />
# dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 0.330142 s, 3.3 GB/s<br />
<br />
==== Kingston SNV425-S2BD 128GB ====<br />
*SSD: Kingston SNV425-S2BD/128GB<br />
*Model Number: SNV425S2128GB<br />
*Firmware: C09112a6<br />
*Capacity: 128 GB<br />
*User: thof<br />
*Filesystem: ext4<br />
<br />
# hdparm -Tt /dev/sda<br />
Timing cached reads: 3480 MB in 2.00 seconds = 1741.72 MB/sec<br />
Timing buffered disk reads: 486 MB in 3.00 seconds = 161.82 MB/sec<br />
<br />
Minimum Read Rate: 235.0 MB/s<br />
Maximum Read Rate: 255.8 MB/s<br />
Average Read Rate: 250.2 MB/s<br />
Average Access Time 0.4 ms<br />
<br />
# dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 8.00357 s, 134 MB/s<br />
<br />
# echo 3 > /proc/sys/vm/drop_caches <br />
# dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 5.5384 s, 194 MB/s<br />
<br />
# dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 records in<br />
1024+0 records out<br />
1073741824 bytes (1.1 GB) copied, 0.415414 s, 2.6 GB/s<br />
<br />
= Encrypted Partitions =<br />
<br />
This section should show some data for encrypted partitions.<br />
<br />
== dm-crypt with AES ==<br />
<br />
I guess most people are using AES as encryption, if any.<br />
<br />
=== OCZ ===<br />
<br />
The OCZ Drives use compression on Data, so with uncompressible encrypted Data, speeds are expected to be way lower. Still, seek times should be as low as ever and the drive shouldn't get slower when it gets full, so there should be enough speed.<br />
<br />
==== OCZ-VERTEX2 180GB ====<br />
<br />
* SSD: OCZ <br />
* Model Number: Vertex2 <br />
* Capacity: 180Gb <br />
* User: crobe<br />
* Filesystem: ext4 on dm-crypt with AES, essiv, sha256<br />
<br />
# hdparm -Tt /dev/sda<br />
/dev/sda:<br />
Timing cached reads: 2842 MB in 2.00 seconds = 1422.61 MB/sec<br />
Timing buffered disk reads: 550 MB in 3.00 seconds = 183.26 MB/sec<br />
# dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc<br />
1024+0 Datensätze ein<br />
1024+0 Datensätze aus<br />
1073741824 Bytes (1,1 GB) kopiert, 16,9194 s, 63,5 MB/s<br />
# echo 3 > /proc/sys/vm/drop_caches<br />
# dd if=tempfile of=/dev/null bs=1M count=1024<br />
1024+0 Datensätze ein<br />
1024+0 Datensätze aus<br />
1073741824 Bytes (1,1 GB) kopiert, 14,5509 s, 73,8 MB/s<br />
<br />
Same values for bonnie++.<br />
<br />
== Truecrypt ==</div>Dundeehttps://wiki.archlinux.org/index.php?title=Codecs_and_containers_(%C4%8Ce%C5%A1tina)&diff=95120Codecs and containers (Čeština)2010-02-05T12:35:42Z<p>Dundee: </p>
<hr />
<div>[[Category:Audio/Video (Česky)]]<br />
{{i18n|Codecs}}<br />
<br />
== Kodeky Gstreamer ==<br />
Pokud shledáte, že nemůžete přehrávat běžné zvukové (jako třeba MP3) nebo video soubory, možná nemáte nainstalované správné kodeky pro jejich přehrávání. Multimediální přehrávěče používající backend '''gstreamer''' (jako třeba Totem) budou schopny přehrát většinu multimediálních souborů po instalaci těchto kodeků:<br />
<br />
# pacman -S gstreamer0.10-bad gstreamer0.10-ugly gstreamer0.10-ffmpeg gstreamer0.10-ugly-plugins<br />
<br />
V případě, že chcete nainstalovat '''všechny''' kodeky pro Gstreamer, můžete použít následující příkaz (za předpokladu, že máte nainstalován awk):<br />
<br />
# pacman -S `pacman -Ss gstreamer | grep -e '^extra/gstreamer0.10' | awk '{print $1}'`<br />
<br />
{{Note| Balík '''codecs''' je zastaralý a není nadále potřeba!}}<br />
<br />
== Užitečné multimediální přehrávače ==<br />
<br />
=== VLC ===<br />
Stále můžete shledat, že některé soubory (hlavně video soubory Windows) se v Totemu nepřehrají správně. '''VLC''' je víceúčelový multimediální přehrávač, jenž má mnoho vlastních kodeků a může ty záludné video soubory zvládnout, stejně jako DVD filmy s menu.<br />
<br />
# pacman -S vlc<br />
<br />
=== MPlayer ===<br />
Mplayer též přehraje mnoho souborů. Zjišťuji, že občas přehraje věci, které se nepřehrají ve VLC.<br />
<br />
# pacman -S mplayer<br />
<br />
Je zde také užitečný plugin, který integruje mplayer do webových prohlížečů. Nainstalujete ho pomocí:<br />
<br />
# pacman -S mplayer-plugin<br />
<br />
== Další zdroje ==<br />
<br />
=== codecs-all z archlinuxfr ===<br />
Repozitář archlinuxfr poskytuje balíček codecs-all, který se zdá kompletnější než běžný balíček codecs z oficiálních repozitářů Arch Linuxu.<br />
<br />
=== Přehrávání videí s posledními kodeky RealMedia (RV10...RV40) ===<br />
Přehrávání videí zakódovaných posledními kodeky RealMedia vám pravděpodobně selže, hlavně když přicházejí v exotických formátech jako kontejner Matroska kontejnery (to jest video soubory *.mkv).<br />
FFmpeg podporuje RV kodeky nativně, jelikož jsou tyto kodeky postupně reverse-engineerovány. Můžete zkusit nainstalovat ffmpegs-svn z AUR.<br />
<br />
Další možnost je jít na http://www.mplayerhq.hu/design7/dload.html. Někde vprostřed stránky můžete stáhnout balíčky s binárními kodeky. Zvolte vhodný pro svoji architekturu a stáhněte jej (v čase psaní tohoto článku verze 20071007 obsahuje cook.so, drvc.so a sipr.so). Rozbalte soubory a - jako root - je zkopírujte do /usr/lib/codecs. Pravděpodobně budete muset nechat přepsat stávající soubory.</div>Dundee