how-to block ads
|
| | | | FAQ Revisions | Editors: yock  , No_Strings , Zuhaib , adsldude , FastEddie
Last modified on 2008-01-24 14:55:55
| |
|
|
2.3 GUI·What is GUI?
·How do I get the scroll wheel on my mouse to work?
·How can I enable the Side Buttons on an Intellimouse Explorer?
·How do I get Anti-Aliased Fonts in Mozilla?
·How Do I get LM_SENSORS working with gkrellm?
·Nvidia Drivers and How To Enable AGP FW and SBA
·How do i start X apps as root while logged in as a normal user?
·Can I use Mac OS X Aqua on my x86 machine?
·How do I get sound working on my Thinkpad 600 series Laptop?
| | | GUI stands for Graphical User Interface
 show feedback form
 close
by howe81 | | | For X Server:
XFree 3.3.2 (and later)
XFree 3.3.2, natively supports a lot of mouse wheel devices. Its support is quite complete and customizable, it even supports the 4th button (side thumb button) on some mice, such as the logitech MouseMan+. Upgrading to at least XFree 3.3.2 is thus the recommended solution.
Normally, all that is needed is to declare a bindtag in your XF86Config, add the following line in the Pointer section:
ZAxisMapping 4 5
We map the wheel to buttons instead of using it as an axis, as buttons is the only way to support it via just changing resources without recompiling or patching applications and toolkits
If you have a 4-button mouse, if you want to use the 4th button, I recommend rebinding the button4 to button6 to be able to use the resources in this page directly, rather than using 5 and 6 for the wheel. Alas, X only supports 5 buttons officially (thus you cannot use button 6 in Xt and Motif applications) so, depending on the application you may not use anymore the side button. And as the X server seems more unstable this way, I don't recommend you use the side button at all.
Just use "Protocol IMPS/2" and "ZAxisMapping 4 5" as above or "Protocol ExplorerPS/2" and "ZAxisMapping 4 5" if you have an IntelliMouse Explorer. If you want to have a 6th button, you can re-map the side button to button6 by this command:
xmodmap -e "pointer = 1 2 3 6 4 5"
or
add the lines (for IntelliMouse Explorer):in the file ~/.Xmodmap.
Note that this command may prompt you interactively to press and release buttons to perform its initialization process, so I use the following code in my X startup script:
## rebind mouse buttons
echo '#!/bin/sh
xmodmap -e "pointer = 1 2 3 6 4 5"' >/tmp/x$$
chmod a+x /tmp/x$$
xterm -bg pink2 -fg blue4 -fn 9x15 -name "Pointer Remap" -e /tmp/x$$
rm -f /tmp/x$$
In your XF86Config file, you should then use one of these protocols:
Section "Pointer"
Protocol "imps/2" # for ps/2 wheel mouse
Protocol "intellimouse" # for serial wheel mouse
Protocol "MouseManPlusPS/2"
... see the Xfree docs
WARNING! These patches or servers do not work if Emulate3Buttons is defined in the X Config file.
For Xterm:
Wheel will scroll the saved output lines. Add to your ~/.Xresources the following lines:
!# Scrolling on wheel mouse: half a page normally, line per line with shift
XTerm.vt100.translations: #override\n\
Shift,:scroll-back(1,line)\n\
Shift,:scroll-forw(1,line)\n\
Ctrl,:scroll-back(1,page)\n\
Ctrl,:scroll-forw(1,page)\n\
,:scroll-back(1,halfpage)\n\
,:scroll-forw(1,halfpage)\n\
!# In the scrollbar we map buttons 5 & 4 to 1 and 2 otherwise, core dump
!# This will move proportionally to cursor position but we dont know how to
!# program the same exact behavior as in the text widget.
XTerm.vt100.Scrollbar.translations: #override\n\
: StartScroll(Forward)\n\
: StartScroll(Backward)\n\
After you have done all this, restart X server and have fun with your, now working, scroll wheel.
show feedback form
close
by DeadlySniper edited by howe81
last modified: 2002-07-22 20:20:24 | | | You will need a small program called IMWheel, that can help you.
Step 1 Edit /etc/X11/XF86Config
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ExplorerPS/2"
Option "Device" "/dev/usbmouse"
Option "Buttons" "7"
Option "ZAxisMapping" "6 7"
Step 2 Add the following line to ~/.xinitrc. Make sure to put it before whatever line loads your window manager.
exec xmodmap -e "pointer = 1 2 3 6 7 4 5" &
That will set the scroll whell to use buttons 6 and 7. 4 and 5 are the side buttons.
Step 3 Install imwheel. Installing is your standard fair. Untar the file, cd into the new directory
./configure
make
make install
If you allow for all the defaults this will load the executable to /usr/local/bin. The config file is in /etc/X11 by default
Step 4 Now to got used to those buttons performing forward and back.
Copy /etc/X11/imwheelrc that to imwheelrc.bak.
(It has a lot of things that I just could not get to work.)
edit /etc/X11/imwheelrc with your favorite text editor to read
".*"
None, Up, Alt_L|Left
None, Down, Alt_L|Right
Step 5 Edit ~/.xinitrc and add the line before your window manager is loaded but after the xmodmap entry.
exec imwheel -k -b "67" &
Step 6 Restart X to get the changes loaded.
Using this method will let the X server control the wheel while imwheel controls the side buttons. After installing imwheel man imwheel for more information on setting up the side buttons.
show feedback form
close
by elboricua edited by bmn
last modified: 2005-11-15 01:10:36 | | | Getting Anti-Aliased fonts in Mozilla.
Prequisites:
I'm not 100% sure if all of these are required for this to work. But I'll list them anyways, sides most distros include them by default.
1. Gdkxft
2. Microsoft's True Type Fonts
Getting bored with XFS
Mostly because I was reading another Font de-uglification HOW-TO I got rid of XFS. Click here for information on doing this. It is important that the font paths in your configuration file from XFS now be listed in your XF86Config.
Anti-Aliased Fonts
I personally had just wanted to use Microsoft fonts with Mozilla. But somehow they ended up getting anti-aliased too. The key to my success is a file called unix.js where most of your mozilla options are stored. I suggest opening this file. It is located in different places dependant upon what Mozilla version you installed and your distro. So to find where your unix.js file is located as root:
code:
updatedb
locate unix.js
The next step is to open the file in a text editor. I personally used nano, but pico or vim should be fine. Anyways scroll down into the file until you find the part talking about Truetype. If you don't want to read further this is what mine looks like, and as long as you have the same font paths it should work fine to replace your section with this:
code:
// TrueType
pref("font.FreeType2.enable", true);
pref("font.freetype2.shared-library", "libfreetype.so.6");
// if libfreetype was built without hinting compiled in
// it is best to leave hinting off
pref("font.FreeType2.autohinted", true);
pref("font.FreeType2.unhinted", false);
// below a certian pixel size anti-aliased fonts produce poor results
pref("font.antialias.min", 10);
pref("font.embedded_bitmaps.max", 1000000);
pref("font.scale.tt_bitmap.dark_text.min", 64);
pref("font.scale.tt_bitmap.dark_text.gain", "0.8");
// sample prefs for TrueType font dirs
pref("font.directory.truetype.1", "/usr/X11R6/lib/X11/fonts/truetype");
However I'll give the more detailed instructions here. First you must enable TrueType by changing the line:
code:
pref("font.FreeType2.enable", false);
change the word false to true. The next part is what gives you the anti-aliasing effect of the text.
code:
// if libfreetype was built without hinting compiled in
// it is best to leave hinting off
pref("font.FreeType2.autohinted", false);
pref("font.FreeType2.unhinted", true);
It is important that libfreetype was built with hinting compiled in. I'm not quite sure how to do that, but I remember reading Gentoo compiled this by default so I had no worries. Anyways all you have to do is swap the word false with true, and in the line below true with false. The final thing you have to do is specify the paths to where your true type fonts are kept.
code:
pref("font.directory.truetype.1", "/usr/X11R6/lib/X11/fonts/truetype");
you can continue on with as many directories as you like changing the 1 to the next number up. After that save the file. Restart Mozilla, and then go into your preferences. Choose the TrueType fonts and they should be anti-aliased.
show feedback form
close
by Techie2000 edited by howe81
last modified: 2002-07-16 02:30:30 | | | 1. The first step in getting lm_sensors to work is to enable i2c devices in your kernel. Once you enable i2c devices you need to be sure to add i2c-dev and i2c-proc support. I like to install these as modules and then add them to my module loader.
Now that you have the i2c-dev and i2c-proc in your kernel you need to download and install lm_sensors. You can get lm_sensors HERE
3. Once lm_sensors is installed you will need to run sensors-detect as root. This will determine what modules you need.
4. It may fail on the last step of writing to /etc/sysconfig/sensors. Don't worry about that error. Just add the modules it mentions to the file that autoloads your modules. Refer to the documentation from your distro on what this file is named.
5. modprobe the drivers that sensor detect tells you it needs to run.
6. After the modules are loaded, from the command line run sensors -s
7. Now type sensors
8. If step 7 gives you info about the motherboard you are in business.
9. To get sensor to display in gkrellm you need to configure the labels. Right click on gkrellm and go to configuration. Under builtins select sensors. What sensor does what depends on your board. Just try temporary labels and make a best guess as to what it is monitoring. Then you can just go back and change the label. Just make sure that whatever label you use does not have a space in it.
NOTE: If for any reason you recompile the kernel you will need to recompile lm_sensors.
show feedback form
close
by elboricua edited by howe81
last modified: 2002-10-13 06:57:13 | | | I found that by default the nvidia drivers do not enable AGP FastWrites or Side Band Addressing. Here is a quick and easy way to turn it on.
NOTE To enable fastwrite you must have a motherboard that supports it, and have it turned on in the BIOS. Most AMD boards have fastwrite capability. I am not sure about Pentium based boards.
*(This tip requires a reboot. Unloading and reloading the driver just gets you an unstable system:/)*
First check to see if the FastWrites and SBA is enabled or disabled.
$ cat /proc/driver/nvidia/agp/status
Status: Enabled
Driver: AGPGART
AGP Rate: 4x
Fast Writes: Enabled
SBA: Enabled
THis may say disabled. My system has FW and SBA turned on.
Now before enabling fastwrites and sba make sure that your video card supports it. The Geforce 2 GTS cards and Geforce Ti cards support it. I am not sure if the MX cards do.
$ cat /proc/driver/nvidia/agp/card
Fast Writes: Supported
SBA: Supported
AGP Rates: 4x 2x 1x
Registers: 0x1f000217:0x1f000314
If your card supports FW and SBA then just do the following:
For Gentoo edit /etc/modules.d/nvidia
For Most other Distro's edit /etc/modules.conf
Add the following:
alias char-major-195 NVdriver
options NVdriver NVreg_EnableAGPSBA=1 NVreg_EnableAGPFW=1
NOTE: As of the 4191 drivers, the kernel module/driver is now called nvidia instead of NVdriver so please change the above to suit the drivers you are using.
Reboot. To make sure that the Fastwrite and SBA are enabled just
$ cat /proc/driver/nvidia/agp/status
Status: Enabled
Driver: AGPGART
AGP Rate: 4x
Fast Writes: Enabled
SBA: Enabled
Again and make sure that Fast Writes and SBA are enabled.
show feedback form
close
by elboricua edited by howe81
last modified: 2003-01-29 20:25:54 | | | Place the following in root's .bashrc
# allow root to run programs when another
# user is in X
if [ ! "$USER" = "root" ]; then
export XAUTHORITY=/home/$USER/.Xauthority
fi
Note: this assumes that root's shell is /bin/bash
show feedback form
close
by freerock edited by howe81
last modified: 2002-11-28 01:22:31 | | | Aqua is a proprietary GUI developed by Apple and there is currently no way to get Aqua on an x86 based computer. However there are Aqua/OS X themes available for many desktop environments and window managers for Linux. A good place to check out is KDE Look.org
show feedback form
close
by Techie2000 edited by howe81
last modified: 2003-03-06 03:41:29 | | | I have gotten this to work on a thinkpad 600e 2645 5au. I can get sound working on my laptop but only with OSS. I cannot get ALSA to work at all. However OSS sounds and works fine. I use OSS with ESD for sound on my laptop. Here is how:
1. I downloaded this ISO Image that loads dos and has thinkpad configuration options for dos. ps2.exe is the name of the program on the iso. I disabled the onboard modem. I could not get it to work anyway, and got the exact configuration, irg, dma, io etc about the cs4232 sound card. Alternatively you could download and install the Thinkpad Configuration Tools. This is a linux tools that does basically the same thing. It is up to you to choose which to use.
2. It does not matter which kernel you use 2.4.x or 2.6.x Just make sure that you have cs4232 compiled as a module. If you compile the driver into the kernel you will only get clicks and static from the speakers.
3. I did not set the modules to load in /etc/rc.d/rc.modles or /etc/modules.conf. For some odd reason I get the same weird popping sounds as you do with the driver compiled in. I am not sure why. I found a script on the Linux on Laptops website and I use that to start sound. I created the script and then call it from local.start or rc.local depending on your distribution.
Here is the script
#!/bin/sh
#
# sound - start sound subsystem modules
#
# 2002-12-30,jtk
case $1 in
start)
echo "Starting sound subsystem..."
# /sbin/modprobe isa-pnp
/sbin/modprobe ad1848
/sbin/modprobe uart401
/sbin/modprobe cs4232 io=0x530 irq=5 dma=1 dma2=0 mpuio=0x330 mpuirq=9
;;
stop)
echo "Stopping sound subsystem..."
rmmod cs4232
rmmod uart401
rmmod ad1848
# rmmod isa-pnp
;;
*)
echo "Usage: $0 {start|stop}"
exit 1
;;
esac
exit 0
I hope that this helps out anyone with a Thinkpad 600 series.
show feedback form
close
by elboricua edited by howe81
last modified: 2004-02-07 04:25:49 |
|
