https://wiki.archlinux.org/api.php?action=feedcontributions&user=Rocktorrentz&feedformat=atomArchWiki - User contributions [en]2024-03-28T23:05:05ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Jumper_EZBOOK_3_PRO&diff=545824Jumper EZBOOK 3 PRO2018-10-03T21:01:17Z<p>Rocktorrentz: /* Problems */ add note about root cause of reversed brightness.</p>
<hr />
<div>[[Category:Laptops]]<br />
<br />
Jumper EZBOOK 3 PRO is a chinese manufactured notebook equipped with a 13.3 inch FHD IPS display, Intel Apollo Lake N3450 processor, 6GB DDR3 RAM, 64GB eMMC Storage, 802.11b/g/n/ac dual band wireless Internet ( Intel Corporation Wireless 3165).<br />
<br />
== Hardware support ==<br />
The notebook can run the x86_64 version of Archlinux, almost everything works out of the box with the stock Archlinux Kernel.<br />
<br />
Install {{Pkg|xf86-input-synaptics}} for better trackpad suppport.<br />
<br />
Wifi, speakers, webcam, battery/power management works out of the box.<br />
<br />
The installation can be done as usual for an x86_64 uefi system.<br />
<br />
<br />
== Problems ==<br />
<br />
* The HDMI port works but it doesn't support audio output, it seems to be a common problem with intel devices and Linux right now.<br />
* Do not change the operating system setting in the BIOS from Windows to Linux. This causes the built in keyboard to become unresponsive during boot-time (although USB keyboards still work) and reverses the backlight controls.</div>Rocktorrentzhttps://wiki.archlinux.org/index.php?title=Jumper_EZBOOK_3_PRO&diff=545821Jumper EZBOOK 3 PRO2018-10-03T20:43:01Z<p>Rocktorrentz: /* Problems */ add note about reversed brightness.</p>
<hr />
<div>[[Category:Laptops]]<br />
<br />
Jumper EZBOOK 3 PRO is a chinese manufactured notebook equipped with a 13.3 inch FHD IPS display, Intel Apollo Lake N3450 processor, 6GB DDR3 RAM, 64GB eMMC Storage, 802.11b/g/n/ac dual band wireless Internet ( Intel Corporation Wireless 3165).<br />
<br />
== Hardware support ==<br />
The notebook can run the x86_64 version of Archlinux, almost everything works out of the box with the stock Archlinux Kernel.<br />
<br />
Install {{Pkg|xf86-input-synaptics}} for better trackpad suppport.<br />
<br />
Wifi, speakers, webcam, battery/power management works out of the box.<br />
<br />
The installation can be done as usual for an x86_64 uefi system.<br />
<br />
<br />
== Problems ==<br />
<br />
The HDMI port works but it doesn't support audio output, it seems to be a common problem with intel devices and Linux right now.<br />
<br />
<br />
The display brightness controls may inverted, which seems to be quite common with Intel Graphics. This problem may be solved by adding {{ic|i915.invert_brightness&#61;1}} to the list of [[kernel parameters]] as mentioned on the [[Backlight]] page.</div>Rocktorrentzhttps://wiki.archlinux.org/index.php?title=X10&diff=137222X102011-04-13T17:53:49Z<p>Rocktorrentz: Added a link to relevant information on the boxee-source page</p>
<hr />
<div>[[Category:Other hardware (English)]]<br />
[[Category:HOWTOs (English)]]<br />
X10 is a radio remote compatible with [[lirc]]<br />
<br />
== Install lirc ==<br />
<br />
# pacman -S lirc lirc-utils<br />
<br />
The package lirc provides the right kernel module.<br />
<br />
==Blacklist not working module==<br />
<br />
For some reason udev loads the wrong kernel module for this radio remote, so you need to blacklist it. this is done in /etc/rc.conf<br />
<br />
Erros in dmesg with the wrong module:<br />
ati_remote 1-1.1:1.0: Unknown input from channel 0x00: data 72,9d<br />
ati_remote: Weird data, len=5 20 fa 5b 65 b6 20 ...<br />
ati_remote: Weird data, len=5 20 fa db 5d b6 00 ...<br />
<br />
To blacklist:<br />
MODULES=(... !ati_remote)<br />
<br />
You need to unload the wrong kernel module manually if you attached the receiver before blacklisting the module.<br />
<br />
Add the daemon to the daemons array to start it at boot:<br />
DAEMONS="(... lircd)"<br />
<br />
== Create /etc/lircd.conf ==<br />
This maps the keys from your remote to strings you can use for programs like mplayer.<br />
<br />
It can automatically generated or copied from one of the provided examples in /usr/share/lirc/remotes. More details are available at [[Lirc#Making_a_configuration_file]].<br />
<br />
Here is one for a Medion X10 Remote:<br />
<pre><br />
# Please make this file available to others<br />
# by sending it to <lirc@bartelmus.de><br />
#<br />
# this config file was automatically generated<br />
# using lirc-0.8.2(default) on Sun Aug 12 02:13:30 2007<br />
#<br />
# contributed by Ben Adler @ gmx dot net<br />
#<br />
# brand: Medion / X10 (part of http://www.medion.de/md8824/)<br />
# remote control: RF Vista Remote Control (OR24V)<br />
# P/N: 2003 5335<br />
# devices being controlled by this remote: USB RF remote receiver (CM20E), P/N 2003 1776<br />
<br />
begin remote<br />
<br />
name Medion_X10<br />
bits 16<br />
eps 30<br />
aeps 100<br />
<br />
one 0 0<br />
zero 0 0<br />
pre_data_bits 8<br />
pre_data 0x14<br />
post_data_bits 16<br />
post_data 0x0<br />
gap 227978<br />
toggle_bit_mask 0x80800000<br />
<br />
begin codes<br />
red 0x87B2<br />
yellow 0x0934<br />
blue 0x8AB5<br />
green 0x0833<br />
power 0xD702<br />
text 0xEB16<br />
tvrecord 0x6D98<br />
disc 0xD904<br />
table 0x86B1<br />
tvplay 0xF11C<br />
back 0x75A0<br />
info 0x042F<br />
volume_up 0x5E89<br />
volume_down 0xDD08<br />
mute 0x5580<br />
channel_up 0xE00B<br />
channel_down 0x618C<br />
cursor_up 0xEF1A<br />
cursor_down 0x77A2<br />
cursor_left 0xF21D<br />
cursor_right 0x749F<br />
ok 0xF31E<br />
start 0x709B<br />
track_previous 0xF621<br />
track_next 0x78A3<br />
record 0xFC27<br />
pause 0x7EA9<br />
stop 0xFD28<br />
seek_backward 0x79A4<br />
play 0xFA25<br />
seek_forward 0x7BA6<br />
1 0xE20D<br />
2 0x638E<br />
3 0xE40F<br />
4 0x6590<br />
5 0xE611<br />
6 0x6792<br />
7 0xE813<br />
8 0x6994<br />
9 0xEA15<br />
0 0x6C97<br />
asterisk 0x0C37<br />
hash 0x8DB8<br />
clear 0x0530<br />
enter 0x8BB6<br />
end codes<br />
<br />
end remote<br />
</pre><br />
<br />
== Edit /etc/conf.d/lircd.conf ==<br />
<br />
Recent versions of lirc drop support for the lirc_atiusb kernel module and so it is now necessary to use the atilibusb driver.<br />
<br />
Simply add "atilibusb" to the LIRC_DRIVER field so that the file looks like this:<br />
# Parameters for lirc daemon<br />
#<br />
<br />
LIRC_DEVICE="/dev/lirc0"<br />
LIRC_DRIVER="atilibusb"<br />
LIRC_EXTRAOPTS=""<br />
LIRC_CONFIGFILE=""<br />
<br />
<br />
== Starting lircd ==<br />
# /etc/rc.d/lircd start<br />
<br />
== Example mplayer config ==<br />
<br />
You need to remove --disable-lirc from mplayers PKGBUILD and recompile it, as it is disabled by default (04.02.09)<br />
<br />
You can check if lirc support is compiled in with "mplayer -v someplayablefile.xyz", look for "Setting up LIRC support.<br />
<br />
~/.lircrc is the default mplayer filename for the lirc config, see man mplayer to change this.<br />
<br />
Change in ~/.lircrc:<br />
<pre><br />
begin<br />
button = VOLUME_UP #VOLUME_UP is the string defined in /etc/lircd.conf<br />
prog = mplayer <br />
config = volume 1 #this is mplayers internal command, see "mplayer -input cmdlist" for more<br />
end<br />
<br />
begin<br />
button = VOLUME_DOWN<br />
prog = mplayer<br />
config = volume -1<br />
end<br />
<br />
begin<br />
button = RIGHT<br />
prog = mplayer<br />
config = seek +1<br />
end<br />
<br />
begin<br />
button = LEFT<br />
prog = mplayer<br />
config = seek -1<br />
end<br />
<br />
begin<br />
button = UP<br />
prog = mplayer<br />
config = seek +50<br />
end<br />
<br />
begin<br />
button = DOWN<br />
prog = mplayer<br />
config = seek -50<br />
end<br />
<br />
begin<br />
button = PLAY<br />
prog = mplayer<br />
config = pause<br />
end<br />
<br />
begin<br />
button = PAUSE<br />
prog = mplayer<br />
config = pause <br />
end<br />
#show elapse/total time in the upper left corner<br />
#Source: http://prasinos.eu/articles/mplayer-lirc-elapsed-time<br />
begin<br />
button = GUIDE<br />
prog = mplayer<br />
config = osd_show_property_text "${time_pos} / ${length}"<br />
end<br />
</pre><br />
<br />
==Boxee (and XBMC)==<br />
Information about how to get the X10 remote control working in Boxee and XBMC is available: [[Boxee-source#LIRC_Remote_Controls]]</div>Rocktorrentzhttps://wiki.archlinux.org/index.php?title=Boxee-source&diff=137219Boxee-source2011-04-13T17:52:05Z<p>Rocktorrentz: Added a bit of info about LIRC</p>
<hr />
<div>[[Category: Audio/Video (English)]]<br />
== About This Page ==<br />
This is the official wiki for the boxee-source aur package; it should contain reasonably up to date information on its status and on workarounds to get things running in specific environments. Please feel free to add useful information in this regard to this page, and if you do, remember to credit yourself in the contributors section below.<br />
<br />
== About boxee-source ==<br />
The Boxee media center @ http://www.boxee.tv/ is both open source and by far the most advanced and featureful mediaplayer available for linux. Unfortunately, the sourcecode does not compile properly against archlinux or 64bit, and even worse, there is no functioning 'make install' to easily seperate the unused chunks of xbmc and sourcecode from the actual package. To remedy this, a small group of us have been working hard to maintain our own patchset and installation script (built against the official ubuntu releases' file structure) that allows the latest boxee to compile in archlinux on both 32 and 64bit.<br />
<br />
<br />
== Repository == <br />
If you want to skip compiling from source, you can add this repo :<br />
<nowiki><br />
[studioidefix]<br />
Server = http://studioidefix.googlecode.com/hg/repo/x86_64<br />
</nowiki><br />
or for 32bit users :<br />
<nowiki><br />
[studioidefix]<br />
Server = http://studioidefix.googlecode.com/hg/repo/i686<br />
</nowiki><br />
<br />
== Staff ==<br />
=== Active Project Maintainers ===<br />
*Prurigro (prurigro at gmail dot com) - Contributor/Maintainer, Patches, PKGBUILD & 32bit Testing<br />
*Anish (anish.7 at gmail dot com) - Patches, PKGBUILD & 32bit Testing<br />
<br />
=== Former Maintainers ===<br />
*Paulingham (paul.ingham at beefeatingmonkeys dot com) - 64bit Patches, 64bit PKGBUILD & 64bit Testing<br />
<br />
=== Contributors/External Help ===<br />
*sdnick484<br />
*jaydonoghue<br />
*jpf<br />
*vrtladept<br />
*adamruss<br />
<br />
== Workarounds ==<br />
=== Issues Compiling ===<br />
==== NVIDIA (binary) ====<br />
<strike>If you are using the nvidia binary driver, then compiling boxee-source will give you the following error: "configure: error: cannot compute sizeof (size_t)". To get around this error, you must compile the package as root: <br />
* 'makepkg' -> 'sudo makepkg -asroot'<br />
* 'yaourt' -> 'sudo yaourt -S boxee-source'</strike><br />
<br />
As of pacman 3.3, this should no longer be required<br />
<br />
=== Issues Running ===<br />
==== ATI ====<br />
An up to date xorg/ati installation reportedly breaks boxee, and the only known fix right now is to downgrade libgl and ati-dri to 7.4.4.<br />
<br />
For those using up to date ATI Catalyst drivers and having video playback issues, changing the render method in your <i>.boxee/UserData/guisetting.xml</i> file may help. <br />
<br />
In the <b><videoplayer></b> section, change the value of <b><rendermethod></b> to <i>1</i> or <i>2</i>.<br />
<br />
== Quick Start Guide ==<br />
<br />
This assumes i686 architecture. If you're using 64bit, I can't help you.<br />
<br />
1. install yaourt, it's much easier. Follow the guide HERE: http://wiki.archlinux.org/index.php/Yaourt<br />
<br />
2. yaourt -S boxee-source OR if you have nvidia binary it MUST be sudo yaourt -S boxee-source. Maybe it'll even install all the dependencies for you! That'd be nice, wouldn't it?<br />
<br />
3. To save you what may have been hours looking in vain for the command to start the fracking program, it is <br />
<br />
/opt/boxee/run-boxee-desktop<br />
<br />
4. Also, if you receive errors related to the following files, you can fix it with symbolic links, whatever they might be:<br />
<br />
sudo ln -s /usr/lib/libgssapi.so.2 /usr/lib/libgssapi_krb5.so.2<br />
<br />
and<br />
<br />
sudo ln -s /usr/lib/libnspr4.so /usr/lib/libnspr4.so.0d <br />
<br />
5. If you get a segmentation fault, uh...<br />
<br />
You could try removing the libgl driver? I replaced mine with nvidia and didn't get this error anymore. But possibly the error was unrelated to libgl. Maybe I wrote a crappy xorg. Or something.<br />
<br />
6. Consult the boxee source page on the AUR if you have further problems. Maybe you need to download some extra libraries or something? Who knows?<br />
<br />
7. Please, someone, make this guide better!<br />
<br />
<br />
== Boxee Beta ==<br />
The current AUR files provide a 100% working beta for 32 & 64 bit machines.<br />
<br />
<strike>There are a couple of issues with updating the PKGBUILD to beta as of now<br />
<br />
1. There is no source release, only a .deb is available.<br />
<br />
2. This one's the showstopper, downloads need a signin and a unique download url give out to those who signed up for early access (as of 25th Dec 2009).<br />
<br />
3. There are some dependency issues with libtiff<br />
<br />
WIP to get it running on Arch. There's a 64 bit version available as well, so it might work just as well on 64bit too.</strike><br />
<br />
== Known Issues ==<br />
=== 64bit flash support (hulu/monty python etc) ===<br />
The flash player provided with boxee is released only in binary format. After a great deal of work and waiting, boxee-source finally supports flash content in 32bit, however; to support 64bit we need to wait for the boxee team to release 64bit binaries, and sadly there hasn't been much talk in this direction.<br />
<br />
However, it is possible to install a 32-bit chroot Arch environment as per the [[Arch64_FAQ]], make sure to enter the environment you set up using linux32 chroot /opt/arch32, and install the appropriate binaries (xorg, nvidia drivers if necessary, yaourt, and Firefox and flash for Hulu) build a 32-bit Boxee-source in the chroot, and run from the 64-bit command line using schroot -p -- /opt/boxee/run-boxee-desktop. Seems to work great on my amd64 box. I've successfully watched video content in 32-bit Boxee using this method.<br />
<br />
If anyone can figure out how to get lirc working with this setup, that would be wonderful.<br />
<br />
== IRC ==<br />
A small warning to all that the room is empty more often than not, but when its not you can find us @ #boxee-source on irc.freenode.net<br />
<br />
==Debugging==<br />
Basic boxee debugging can be done by editing or creating ~/.boxee/UserData/advancedsettings.xml<br />
<br />
to include the following code:<br />
<nowiki><br />
<advancedsettings><br />
<loglevel>0</loglevel><br />
</advancedsettings><br />
</nowiki><br />
<br />
after starting boxee, your log will be located at<br />
<br />
Linux:<br />
/tmp/<username>-boxee.log<br />
<br />
Please be kind and use pastebin.com/pastie.org for the debug log, don't paste it in the comments.<br />
<br />
==LIRC Remote Controls==<br />
As described in this [http://forums.boxee.tv/showthread.php?t=1036 Boxee Forum Post], it is possible to get LIRC remote controls working in Boxee. You simply need to create a ~/.boxee/UserData/Lircmap.xml file. This translates LIRC button presses to XBMC key-presses. The syntax is described in more detail on the [http://wiki.xbmc.org/index.php?title=Lirc_and_Lircmap.xml XBMC Wiki].<br />
<br />
Here is an example for a Medion X10 RF remote: <br />
<pre><br />
<!-- This file contains the mapping of LIRC keys to XBMC keys used in Keymap.xml --><br />
<br />
<lircmap><br />
<remote device="Medion_X10"><br />
<pause>pause</pause><br />
<stop>stop</stop><br />
<forward>seek_forward</forward><br />
<reverse>seek_backward</reverse><br />
<left>cursor_left</left><br />
<right>cursor_right</right><br />
<up>cursor_up</up><br />
<down>cursor_down</down><br />
<select>ok</select><br />
<pageplus>channel_up</pageplus><br />
<pageminus>channel_down</pageminus><br />
<back>back</back><br />
<menu>table</menu><br />
<title>play</title><br />
<info>info</info><br />
<skipplus>track_next</skipplus><br />
<skipminus>track_previous</skipminus><br />
<display>text</display><br />
<start>start</start><br />
<record>record</record><br />
<volumeplus>volume_up</volumeplus><br />
<volumeminus>volume_down</volumeminus><br />
<mute>mute</mute><br />
<myvideo>red</myvideo><br />
<mymusic>yellow</mymusic><br />
<mypictures>green</mypictures><br />
<mytv>blue</mytv><br />
<one>1</one><br />
<two>2</two><br />
<three>3</three><br />
<four>4</four><br />
<five>5</five><br />
<six>6</six><br />
<seven>7</seven><br />
<eight>8</eight><br />
<nine>9</nine><br />
<zero>0</zero><br />
</remote><br />
</lircmap><br />
</pre></div>Rocktorrentzhttps://wiki.archlinux.org/index.php?title=X10&diff=137217X102011-04-13T17:43:12Z<p>Rocktorrentz: Changes to reflect breakage of lirc_atiusb</p>
<hr />
<div>[[Category:Other hardware (English)]]<br />
[[Category:HOWTOs (English)]]<br />
X10 is a radio remote compatible with [[lirc]]<br />
<br />
== Install lirc ==<br />
<br />
# pacman -S lirc lirc-utils<br />
<br />
The package lirc provides the right kernel module.<br />
<br />
==Blacklist not working module==<br />
<br />
For some reason udev loads the wrong kernel module for this radio remote, so you need to blacklist it. this is done in /etc/rc.conf<br />
<br />
Erros in dmesg with the wrong module:<br />
ati_remote 1-1.1:1.0: Unknown input from channel 0x00: data 72,9d<br />
ati_remote: Weird data, len=5 20 fa 5b 65 b6 20 ...<br />
ati_remote: Weird data, len=5 20 fa db 5d b6 00 ...<br />
<br />
To blacklist:<br />
MODULES=(... !ati_remote)<br />
<br />
You need to unload the wrong kernel module manually if you attached the receiver before blacklisting the module.<br />
<br />
Add the daemon to the daemons array to start it at boot:<br />
DAEMONS="(... lircd)"<br />
<br />
== Create /etc/lircd.conf ==<br />
This maps the keys from your remote to strings you can use for programs like mplayer.<br />
<br />
It can automatically generated or copied from one of the provided examples in /usr/share/lirc/remotes. More details are available at [[Lirc#Making_a_configuration_file]].<br />
<br />
Here is one for a Medion X10 Remote:<br />
<pre><br />
# Please make this file available to others<br />
# by sending it to <lirc@bartelmus.de><br />
#<br />
# this config file was automatically generated<br />
# using lirc-0.8.2(default) on Sun Aug 12 02:13:30 2007<br />
#<br />
# contributed by Ben Adler @ gmx dot net<br />
#<br />
# brand: Medion / X10 (part of http://www.medion.de/md8824/)<br />
# remote control: RF Vista Remote Control (OR24V)<br />
# P/N: 2003 5335<br />
# devices being controlled by this remote: USB RF remote receiver (CM20E), P/N 2003 1776<br />
<br />
begin remote<br />
<br />
name Medion_X10<br />
bits 16<br />
eps 30<br />
aeps 100<br />
<br />
one 0 0<br />
zero 0 0<br />
pre_data_bits 8<br />
pre_data 0x14<br />
post_data_bits 16<br />
post_data 0x0<br />
gap 227978<br />
toggle_bit_mask 0x80800000<br />
<br />
begin codes<br />
red 0x87B2<br />
yellow 0x0934<br />
blue 0x8AB5<br />
green 0x0833<br />
power 0xD702<br />
text 0xEB16<br />
tvrecord 0x6D98<br />
disc 0xD904<br />
table 0x86B1<br />
tvplay 0xF11C<br />
back 0x75A0<br />
info 0x042F<br />
volume_up 0x5E89<br />
volume_down 0xDD08<br />
mute 0x5580<br />
channel_up 0xE00B<br />
channel_down 0x618C<br />
cursor_up 0xEF1A<br />
cursor_down 0x77A2<br />
cursor_left 0xF21D<br />
cursor_right 0x749F<br />
ok 0xF31E<br />
start 0x709B<br />
track_previous 0xF621<br />
track_next 0x78A3<br />
record 0xFC27<br />
pause 0x7EA9<br />
stop 0xFD28<br />
seek_backward 0x79A4<br />
play 0xFA25<br />
seek_forward 0x7BA6<br />
1 0xE20D<br />
2 0x638E<br />
3 0xE40F<br />
4 0x6590<br />
5 0xE611<br />
6 0x6792<br />
7 0xE813<br />
8 0x6994<br />
9 0xEA15<br />
0 0x6C97<br />
asterisk 0x0C37<br />
hash 0x8DB8<br />
clear 0x0530<br />
enter 0x8BB6<br />
end codes<br />
<br />
end remote<br />
</pre><br />
<br />
== Edit /etc/conf.d/lircd.conf ==<br />
<br />
Recent versions of lirc drop support for the lirc_atiusb kernel module and so it is now necessary to use the atilibusb driver.<br />
<br />
Simply add "atilibusb" to the LIRC_DRIVER field so that the file looks like this:<br />
# Parameters for lirc daemon<br />
#<br />
<br />
LIRC_DEVICE="/dev/lirc0"<br />
LIRC_DRIVER="atilibusb"<br />
LIRC_EXTRAOPTS=""<br />
LIRC_CONFIGFILE=""<br />
<br />
<br />
== Starting lircd ==<br />
# /etc/rc.d/lircd start<br />
<br />
== Example mplayer config ==<br />
<br />
You need to remove --disable-lirc from mplayers PKGBUILD and recompile it, as it is disabled by default (04.02.09)<br />
<br />
You can check if lirc support is compiled in with "mplayer -v someplayablefile.xyz", look for "Setting up LIRC support.<br />
<br />
~/.lircrc is the default mplayer filename for the lirc config, see man mplayer to change this.<br />
<br />
Change in ~/.lircrc:<br />
<pre><br />
begin<br />
button = VOLUME_UP #VOLUME_UP is the string defined in /etc/lircd.conf<br />
prog = mplayer <br />
config = volume 1 #this is mplayers internal command, see "mplayer -input cmdlist" for more<br />
end<br />
<br />
begin<br />
button = VOLUME_DOWN<br />
prog = mplayer<br />
config = volume -1<br />
end<br />
<br />
begin<br />
button = RIGHT<br />
prog = mplayer<br />
config = seek +1<br />
end<br />
<br />
begin<br />
button = LEFT<br />
prog = mplayer<br />
config = seek -1<br />
end<br />
<br />
begin<br />
button = UP<br />
prog = mplayer<br />
config = seek +50<br />
end<br />
<br />
begin<br />
button = DOWN<br />
prog = mplayer<br />
config = seek -50<br />
end<br />
<br />
begin<br />
button = PLAY<br />
prog = mplayer<br />
config = pause<br />
end<br />
<br />
begin<br />
button = PAUSE<br />
prog = mplayer<br />
config = pause <br />
end<br />
#show elapse/total time in the upper left corner<br />
#Source: http://prasinos.eu/articles/mplayer-lirc-elapsed-time<br />
begin<br />
button = GUIDE<br />
prog = mplayer<br />
config = osd_show_property_text "${time_pos} / ${length}"<br />
end<br />
</pre></div>Rocktorrentzhttps://wiki.archlinux.org/index.php?title=IceWM&diff=95717IceWM2010-02-09T19:56:38Z<p>Rocktorrentz: Updates and Corrections</p>
<hr />
<div>[[Category:Desktop environments (English)]]<br />
{{stub}}<br />
<br />
== What is IceWM? ==<br />
In Unix computing, IceWM is a window manager for the X Window System graphical infrastructure, written by Marko Maček. It was coded from scratch in C++ and is released under the terms of the GNU Lesser General Public License. It is relatively lightweight in terms of memory and CPU usage, and comes with themes that allow it to imitate the UI of Windows 95, OS/2, Motif, and other graphical user interfaces. (Source: [http://en.wikipedia.org/wiki/Icewm Wikipedia])<br />
<br />
== Installation ==<br />
IceWM is available in [extra] and therefore easily installable:<br />
<pre><br />
# pacman -S icewm<br />
</pre><br />
<br />
Alternatively, the latest version from the testing branch ({{Package AUR|icewm-testing}}) and CVS version ({{Package AUR|icewm-cvs}}) are available from the [[AUR]]. These versions add new features such as RandR support.<br />
<br />
== Configuration ==<br />
Although IceWM configuration is originally text-based, there are GUI-based tools available, notably icewm-utils in [community]. However these tools are relatively old and most users prefer to simply edit the text configuration files.<br />
<br />
To change your icewm configuration from the default, simply copy the default configuration files from <tt>/usr/share/icewm/</tt> to <tt>~/.icewm/</tt>, for example: <br />
<br />
{{Note | Do this as a regular user, not as root.}}<br />
<br />
$ mkdir ~/.icewm/<br />
$ cp -R /usr/share/icewm/* ~/.icewm/<br />
<br />
{{Filename|preferences}} is the core configuration file for IceWM.<br />
{{Filename|menu}} controls the contents of the IceWM application menu.<br />
{{Filename|keys}} allows the user to customize keyboard shortcuts.<br />
<br />
=== Menu ===<br />
MenuMaker (available in [Community]) is a Python script that automatically populates your applications menu based on what is installed in your system. Although this may result in a menu filled with many unwanted applcations, it may still be preferable to manually editing the menu configuration file. When running MenuMaker, use the -f flag to overwrite an existing menu file:<br />
<pre><br />
# mmaker -f icewm<br />
</pre> <br />
<br />
=== Themes ===<br />
Although some themes are included by default, there is a much larger and better selection in the verified [http://aur.archlinux.org/packages.php?do_Details=1&ID=5719&O=0&L=0&C=0&K=icewm&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd icewm-themes] package in the repository. Although many have a spartan, 'old Windows' feel, some (ElbergBlue, liquid, etc.) have a more modern look.<br />
<br />
You can also visit [http://www.box-look.org/index.php?xcontentmode=7311 box-look.org] for more themes.<br />
<br />
== File Managers ==<br />
It should be noted that IceWM is a window manager only and therefore does not include a file manager. [[PCManFM]] and Rox Filer enable desktop icons, but iDesk can also be used to achieve this functionality.<br />
<br />
== Related Articles ==<br />
* [[Starting different desktop environments HOWTO]]<br />
<br />
== External Resources ==<br />
* [http://www.icewm.org/ Official IceWM website]<br />
* [http://en.gentoo-wiki.com/wiki/IceWM/ IceWM - Gentoo Linux Wiki]<br />
* [http://www.osnews.com/story.php/7774/IceWM--The-Cool-Window-Manager/ IceWM - The Cool Window Manager] - Detailed introduction on OSNews<br />
* [http://polishlinux.org/apps/window-managers/icewm-a-desktop-for-windows-emmigrants/ IceWM - A desktop for Windows emigrants] - Overview and tutorial from polishlinux.org</div>Rocktorrentzhttps://wiki.archlinux.org/index.php?title=Folding@home&diff=53456Folding@home2008-11-14T14:57:25Z<p>Rocktorrentz: /* Multiple Folding@Home Installs */</p>
<hr />
<div>[[Category:Daemons and system services (English)]]<br />
<br />
= What is Folding@Home =<br />
From the [http://aur.archlinux.org/packages.php?do_Details=1&ID=11852&O=0&L=&C=&K=folding&SB=&SO=&PP=&do_MyPackages=&do_Orphans=&SeB= AUR package page] "Folding@Home is a distributed computing project which studies protein folding, misfolding, aggregation, and related diseases."<br />
<br />
Please see the [http://folding.stanford.edu/ Folding@Home site] for a fuller description.<br />
<br />
= Installing Folding@Home =<br />
<br />
Folding@Home is no longer in the community repository due to licensing issues. However, it is still possible to build it from [[AUR]]. If you are familiar with PKGBUILDS and AUR then build it and skip to configuration.<br />
<br />
<br />
== Automatic Install ==<br />
<br />
<br />
If you are using [[Aurbuild]], it's as simple as:<br />
<br />
sudo aurbuild -s foldingathome<br />
<br />
If you are using [http://archlinux.fr/yaourt-en yaourt] , it's as simple as:<br />
<br />
sudo yaourt -S --aur foldingathome<br />
<br />
== Manual Install ==<br />
<br />
To install manually, first download everything under the [http://aur.archlinux.org/packages/foldingathome/foldingathome/ files section] of the [http://aur.archlinux.org/packages.php?do_Details=1&ID=11852&O=0&L=&C=&K=folding&SB=&SO=&PP=&do_MyPackages=&do_Orphans=&SeB= Folding@Home AUR page] to a folder. Open a console and cd to the directory you downloaded to. Now it's just a matter of running<br />
<br />
makepkg<br />
<br />
and if there are no errors you will be left with a package called foldingathome-version-number.pkg.tar.gz.<br />
<br />
Run <br />
sudo pacman -U foldingathome-version-number.pkg.tar.gz<br />
being sure to replace version-number first ;)<br />
<br />
If all went well, Folding@Home should now be installed.<br />
<br />
<br />
<br />
<br />
= Configuration =<br />
<br />
Firstly, you will want to open your /etc/conf.d/foldingathome config file, with your editor of choice.<br />
<br />
sudo nano /etc/conf.d/foldingathome<br />
<br />
The config is self explanatory, if you wish to have Folding@Home run as a user other than root (handy on single user systems, probably more secure on multi-user systems), or in a different group, then change these values.<br />
<br />
Now run the Folding@Home process for the first time with<br />
<br />
sudo /etc/rc.d/foldingathome start<br />
<br />
give it a few seconds and then run <br />
<br />
sudo /etc/rc.d/foldingathome stop<br />
<br />
You will find under your /opt/fah/ directory, either new files or a new folder, if you set the user variable in /etc/conf.d/foldingathome. You will find a file called client.cfg, either in the /opt/fah dir or the /opt/fah/FAH_USER folder.<br />
<br />
sudo nano /opt/fah/client.cfg<br />
or<br />
nano /opt/fah/FAH_USER/client.cfg # Replace FAH_USER first<br />
<br />
<br />
The most important settings here are:<br />
<br />
<br />
*username, username associated to the work-units you return (not related to the FAH_USER variable in /etc/conf.d/foldingathome).<br />
<br />
*team, the team number you wish to contribute points to (earned for work units returned), you will of course want to fill in 45032, the arch-linux team number ;)<br />
<br />
*bigpackets, defines whether you will accept memory intensive work loads. If you have no problem with Folding@Home using up more of your RAM, then set this to yes (at least 512MB of RAM recommended).<br />
<br />
*machineid, covered in the Multi-Core section.<br />
<br />
<br />
After editing that, run <br />
<br />
sudo /etc/rc.d/foldingathome start<br />
<br />
again, to start Folding@Home up.<br />
<br />
<br />
Assuming it all ran correctly, you'll want to put it in /etc/rc.conf to run on startup, so<br />
<br />
sudo nano /etc/rc.conf<br />
<br />
and add @foldingathome to your DAEMONS variable (the @ causes it to start in the background, so as not to slow startup, see [[Daemons]]).<br />
<br>Remember, this is @foldingathome-smp for the SMP client!<br />
<br />
<br />
Folding@Home is now installed and running!<br />
<br />
<br />
= Multi-Core Cpu's and Folding@Home =<br />
<br />
== A Quick Note On Hyperthreading ==<br />
If you have a single-core hyperthreading CPU, you may be tempted to follow the multi-core instructions. It's highly recommenced that you '''''don't''''' do this as the Folding@Home team prefers fewer results quickly, than more results slowly. There's also a time-limit on work-units, so if it runs slower, your work-units may not be returned in time, and so distributed to another user. If you have one core, run one folding process.<br />
<br />
== Multiple Folding@Home Installs ==<br />
=== Setting up Multiple Folding@Home installs ===<br />
It's very simple to set up an extra install, although after each (rare) upgrade of the Folding@Home package, you will have to perform some maintenance, unless you wish to build separate packages with custom PKGBUILDS / scripts (beyond the scope of this tutorial). This method ''should'' also scale to however many cores/processors you have.<br />
<br />
First, stop Folding@Home if it's running<br />
<br />
sudo /etc/rc.d/foldingathome stop<br />
<br />
next<br />
<br />
sudo cp -r /opt/fah /opt/fah2<br />
<br />
If you wish to call it something different, then by all means do. This tutorial will assume you're using /opt/fah2 for your second install and that you have the FAH_USER directory.<br />
<br />
Now<br />
<br />
rm -rf /opt/fah2/FAH_USER/work /opt/fah2/FAH_USER/queue.dat<br />
<br />
<br />
if they exist, this way the new process won't start working on the same work-unit as the original thread.<br />
<br />
You now have to open up the config for the new process<br />
<br />
nano /opt/fah2/FAH_USER/client.cfg<br />
<br />
and change the '''machineid''' to a number different to the one in /opt/fah/client.cfg.<br />
<br />
If you're using the bigpackets option in client.cfg, you should only have it set to yes for '''one''' of your Folding@Home processes as it can overwhelm your system unless you have plenty of free RAM (1GB at least).<br />
<br />
=== Editing Init Scripts ===<br />
Now comes the fun part. A second init script needs to be created and a little editing needs to be done, but this way you can turn each process on and off as wanted and it's simpler than one script managing both.<br />
<br />
<br />
First, some initial editing has to be done to the current script and saved under another name<br />
<br />
sudo nano /etc/rc.d/foldingathome<br />
<br />
<br />
After <br />
<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
. /etc/conf.d/foldingathome<br />
<br />
Add<br />
<br />
FAH_VER=504<br />
<br />
<br />
This is to cut down on later maintenance.<br />
<br />
<br />
Next, change <br />
<br />
PID=`pidof -o %PPID /opt/fah/FAH504-Linux.exe`<br />
<br />
to<br />
<br />
PID=`pgrep -f /opt/fah/FAH${FAH_VER}-Linux.exe -u $FAH_USER`<br />
<br />
The reason for this is that pidof detects the first and second Folding@Home process as the same and so stopping one init script will kill both processes. On the other hand, pgrep will find the process' associated filename/location. The "-u $FAH_USER" part is tacked on as a precaution, in case you are doing something strange with Folding@Home threads and users. You'll also notice the FAH_VER has slipped in there.<br />
<br />
There should be two more instances of /opt/fah/FAH504-Linux.exe, change them to <br />
<br />
/opt/fah/FAH${FAH_VER}-Linux.exe<br />
<br />
<br />
Next, find the lines <br />
add_daemon foldingathome<br />
rm_daemon foldingathome <br />
<br />
and change them to something like<br />
add_daemon foldingathome1<br />
rm_daemon foldingathome1 <br />
<br />
<br />
You can also change the<br />
<br />
stat_busy "Starting Folding@Home"<br />
<br />
stat_busy "Stopping Folding@Home"<br />
<br />
lines to have some extra description such as "on Core 1" if you need to.<br />
<br />
<br />
Now save the file as /etc/rc.d/foldingathome1 , this is to prevent it being over-written by a package upgrade.<br />
<br />
<br />
Make a copy of the script<br />
<br />
sudo cp /etc/rc.d/foldingathome1 /etc/rc.d/foldingathome2<br />
<br />
Now you have to find and replace instances of /opt/fah with /opt/fah2 in this script, double checking you aren't getting any false positives (there shouldn't be any, but scripts change). Make sure you get the one in the PID variable, otherwise the whole pgrep bit was a bit pointless ;)<br />
<br />
Also, find the lines <br />
add_daemon foldingathome1<br />
rm_daemon foldingathome1<br />
<br />
again, and change them to something like <br />
add_daemon foldingathome2<br />
rm_daemon foldingathome2 <br />
<br />
Now, save this script and open up /etc/rc.conf and add @foldingathome1 and @foldingathome2 to the DAEMONS variable. Start up the two processes<br />
<br />
sudo /etc/rc.d/foldingathome1 start<br />
sudo /etc/rc.d/foldingathome2 start<br />
<br />
and if all goes well, you've got 2 Folding@Home processes running!<br />
<br />
=== Maintenance ===<br />
<br />
When upgrading the Folding@Home package, it's recommended you stop both Folding@Home init-scripts first<br />
<br />
sudo /etc/rc.d/foldingathome1 stop<br />
sudo /etc/rc.d/foldingathome2 stop<br />
<br />
On upgrading, /opt/fah/FAH504-Linux.exe will be replaced with a new version, this needs to be copied into your /opt/fah2 directory and the old executable deleted. <br />
<br />
You then just have to change the FAH_VER variable in ''both scripts'' to reflect the new version number. You can then restart both scripts with<br />
<br />
sudo /etc/rc.d/foldingathome1 start<br />
sudo /etc/rc.d/foldingathome2 start<br />
<br />
It may also be worth checking that there have been no other significant changes to the updated original script.<br />
<br />
=== Alternative: Single Init Script ===<br />
<br />
I couldn't get the above method to work with the current (6.02) version of the client. I found an old script on the forums and modified it slightly which works just fine on my system.<br />
<br />
#!/bin/bash<br />
#/etc/rc.d/foldingathome<br />
#<br />
# Starts the Folding@Home client in the background<br />
<br />
. /etc/rc.d/functions<br />
<br />
case "$1" in<br />
start)<br />
stat_busy "Starting Folding@Home"<br />
cd /opt/fah/<br />
/opt/fah/fah6 > /opt/fah/myfah.log &<br />
cd /opt/fah2/<br />
/opt/fah2/fah6 > /opt/fah2/myfah.log &<br />
stat_done<br />
;;<br />
stop)<br />
stat_busy "Stopping Folding@Home"<br />
killall fah6<br />
stat_done<br />
;;<br />
restart)<br />
stop<br />
start<br />
;;<br />
*)<br />
echo $"Usage: $0 {start|stop|restart}"<br />
RETVAL=1<br />
<br />
esac<br />
exit 0<br />
<br />
Just make sure you don't forget to follow the first section under "Setting up Multiple Folding@Home installs".<br />
<br />
== Folding@Home SMP Support ==<br />
<br />
=== About ===<br />
There is now a Folding@Home client available for 64-bit multi-processor or multi-core computers (aka SMP). The creators of Folding@Home suggest the SMP client runs best on quad core machines but many people run it on dual cores with no trouble. This client is definitely NOT recommended for single-core CPUs with Hyperthreading. So, if your machine meets the requirements (Arch 64-bit, true multi-core/processor) you may want to give the SMP client a try instead of running two of the standard client!<br />
<br />
<br />
Setup is identical to that of the standard client EXCEPT for the following:<br />
<br />
* the name of the package in the [http://aur.archlinux.org/packages.php?do_Details=1&ID=11964&O=0&L=&C=&K=folding&SB=&SO=&PP=&do_MyPackages=&do_Orphans=&SeB= AUR is foldingathome-smp]<br />
* lib32-glibc is required to install and run the client (this is reflected as a dependency in the PKGBUILD)<br />
* the package installs to /opt/fah-smp<br />
* the configuration script in /etc/conf.d is foldingathome-smp<br />
* the daemon that should be added to /etc/rc.conf is foldingathome-smp<br />
<br />
<br />
=== Migrating ===<br />
<br />
When migrating from the standard FAH client/s to SMP, you may wish to finish off the work units currently running but without the FAH client downloading new ones. This is possible through the init-scripts as long as you make sure to check the status of the current work-unit before shutting down / rebooting. <br />
<br />
This may seem a bit over the top and whether you do it depends on how committed you are to returning all work-units sent to your box. At the worst, your work-unit will be distributed to someone else after the cut-off date.<br />
<br />
<br />
To do this, stop the folding client/s <br />
sudo /etc/rc.d/foldingathome1 stop<br />
sudo /etc/rc.d/foldingathome2 stop<br />
<br />
open up your /etc/rc.d/foldingathome file/s and change<br />
<br />
su $FAH_USER -c "/opt/fah/FAH504-Linux.exe -verbosity 9 > /opt/fah/$FAH_USER/myfah.log" &<br />
<br />
to<br />
<br />
su $FAH_USER -c "/opt/fah/FAH504-Linux.exe -oneunit -verbosity 9 > /opt/fah/$FAH_USER/myfah.log" &<br />
<br />
<br />
<br />
This will force the FAH client to only finish its current work-unit and upload it without downloading a new one. The problem arises in that if you reboot (or restart the init-scripts) after it's finished and sent back the work-unit, it will download a new one to finish and send back. You will just have to monitor the status of the work-unit before you restart, and if it's at 100% and the end of /opt/fah/FAH_USER/FAHlog.txt says the work-unit has been returned, you can remove that script from the DAEMONS= line in /etc/rc.conf. <br />
<br />
<br />
If you know how, you can probably find a way of stopping it from doing this, maybe with a check in the init-script which stops it running when the work-unit file is no longer in the /opt/fah/FAH_USER/work directory. <br />
<br />
<br />
If you're currently on i686 arch, you will also need to migrate to X86_64 arc, and it would be a good idea to read the [[Arch64_FAQ]]<br />
<br />
=== Troubleshooting ===<br />
<br />
==== Can't find ./mpiexec ====<br />
<br />
If you are using the $FAH_USER variable, you will find on starting the smp client that it can't find ./mpiexec , this is because it's in the /opt/fah-smp/ directory and not your local one. Copy it to /opt/fah-smp/$FAH_USER and it should run fine.<br />
<br />
<br />
==== SMP client not doing any work / stalling ( NNODES=4 ) ====<br />
<br />
( This is adapted from the [http://folding.stanford.edu/English/FAQ-SMP folding@home SMP FAQ] )<br />
<br />
If you run <br />
sudo /etc/rc.d/foldingathome-smp start<br />
<br />
from the console, you will get some output. If this output stalls with a<br />
NNODES=4 <br />
line and top/htop shows the smp-client running but with no CPU usage, you will need to check your local network settings. Check that your /etc/hosts file is set up with 127.0.0.1 linked to the hostname you set up in /etc/rc.conf.<br />
<br />
= Monitoring Work-Unit Progress =<br />
There are several ways of monitoring the progress of your FAH client/s, both on the command line and by GUI. <br />
<br />
In AUR there is silent blades [http://aur.archlinux.org/packages.php?do_Details=1&ID=7788&O=0&L=&C=&K=folding&SB=&SO=&PP=&do_MyPackages=&do_Orphans=&SeB= fahmon], which provides a GUI with the ability to watch multiple clients and get info on the work-unit itself. Fahmon has a dedicated site at [http://www.fahmon.net/ http://www.fahmon.net/]<br />
<br />
On the CLI, you can add a command to your .bashrc , .zshrc or .whateverrc :<br />
<br />
fahstat() {<br />
echo<br />
echo `date`<br />
echo<br />
cat /opt/fah/FAH_USER/unitinfo.txt #(replacing FAH_USER first)<br />
}<br />
<br />
Or for multiple clients :<br />
<br />
fahstat() {<br />
echo<br />
echo `date`<br />
echo<br />
echo "Core 1:";cat /opt/fah/FAH_USER/unitinfo.txt #(replace FAH_USER first)<br />
echo<br />
echo "Core 2:";cat /opt/fah2/FAH_USER/unitinfo.txt #(replace FAH_USER first)<br />
}<br />
<br />
Also, replacing cat with tail -n1 will give just the percentage of work unit complete.<br />
<br />
<br />
= More Resources =<br />
[http://folding.stanford.edu/ Folding@Home Site] <br />
<br />
[http://folding.stanford.edu/English/FAQ Folding@Home FAQ] <br />
<br />
[http://folding.stanford.edu/English/FAQ-Configure Folding@Home Configuration FAQ]<br />
<br />
<br />
<br />
[http://aur.archlinux.org/packages.php?do_Details=1&ID=11964&O=0&L=&C=&K=foldingathome&SB=&SO=&PP=&do_MyPackages=&do_Orphans=&SeB= Folding@Home SMP Client on AUR] <br />
<br />
[http://folding.stanford.edu/English/FAQ-SMP Folding@Home SMP Client FAQ]<br />
<br />
<br />
<br />
[http://vspx27.stanford.edu/cgi-bin/main.py?qtype=teampage&teamnum=45032 Arch Folding@Home team page]<br />
<br />
[http://folding.extremeoverclocking.com/team_summary.php?s=&t=45032 Extended Arch team statistics on extremeoverclocking.com]</div>Rocktorrentz