after several hours I've finally gotten slackware running! But the only thing I don't understand is how to configure the touchpad. In Ubuntu you can do it in the GUI, but I have no idea how to do it via Slackware.
I mostly want it to disable tap to click when I type, and enable horizontal and vertical scrolling. I've tried using synclient but that doesn't seem to work, and in any case I think that is only supposed to be a temporary fix anyway.
how to update packages I've installed? I installed wicd to use wireless for my laptop, but according to their website, it's best that I update it to the newest version because of some bug.
I have a new HP ENVY 14 laptop with OpenSuSE 11.3 installed, running the Gnome desktop. The laptop has a Synaptics TouchPad. By default, many of the touchpad settings are turned off, e.g. single tap to click. I'm trying to set them in /etc/X11/xorg.conf.d/20-synaptics.conf code...
I've verified that the settings I'm trying to set work when I set them using synclient, e.g. synclient TapButton1=1 enables tap to click.
I'm brand new to Linux and OpenSuSE so I'm not even sure this is the preferred way to set up my touchpad. I'd appreciate any help diagnosing this problem.
for some reason I got taping on touchpad is disabled after some software upgrade or something.I can enable it with synclient TapButton1=1, etc.. but have got to do it every time I reboot. Also, I don't have Xorg.conf file. Is there any way I can configure taping to work permanently ?
I have acer aspire one netbook with synatics ps2 touchpad. It works fine, but I'd like to emulate left button by just pressing somewhere in the touch area (same as it works in windows or ubunntu). I think this is called tapping. How can I configure that? I have been in touchpad settings and management, but I have not found any checkbox helpful. In OS 11.3 I need to press left button next to the touchpad.
I have an Acer Aspire 5740 with a synaptics touchpad. I have tried using the ksynaptics program as well as the touchpad settings under System Settings >> Computer Administration. My touchpad works, but it is driving me crazy with how sensitive the tap to click feature is. I want to disable it altogether so I can actually work on my computer. When I go to the touchpad section in System Settings >> Computer Administration >> Keyboard & Mouse, the tab says "Warning: Touchpad configuration is not supported on this system. The synaptics driver is either not loaded or too old. Refer to doumentation for information about the required driver version."
Just installed Slackware 13.1 and I'm trying to disable tap to click on my touchpad. When I run "synclient MaxTapTime=0" it turns off. But the next time I restart X, the settings won't hold. I tried putting Option "MaxTapTime" "0" in xorg.conf, but it didn't work. This is my mouse portion from xorg.conf generated from the nvidia driver from slackbuilds.
Alright, so I finally decided to test Slackware Current on my laptop. After this upgrade my touchpad does not work in X, but it does work in the terminal. The mouse section of my xorg.conf is:
If I cat /dev/psaux I get output when i move my touchpad around. I also ran cat on /dev/mouse and I also get output from that when i move my touchpad around. I also tried Protocol "Auto" instead of PS/2, and IMPS/2 to no avail. Also, to begin with I was using the synaptics driver, and i moved it back to the generic mouse driver, and still nothing.
I login as root every time (its a closed system) and I am running it on a laptop. I want to disable the touch pad after typing for 4 seconds.I have tried adding this command:syndaemon -i 4 -dto rc.4, rc.local, rc.httpd, http.mysqld
Just recently discovered that for a non-root user the touchpad on my Acer laptop ( Aspire 5720z fyi ) isn't working in X ( KDE or XFCE ). It does work in in tty (at login) and for root it works in both environments.
I'm running 13.1 x64 on it, with the normal security patches via slackpkg. Didn't notice before since I normally use a mouse (and thus I do like the touchpad being disabled so I don't 'tap' away the cursur while typing).
With the recent holidays (with family visits and all) I took the laptop on my lap,.and voila: no trackpad movement.. I did some searching allready, but this problem seems to be solved since a while, and isn't supposed to be in 13.1
FROM RELEASE NOTES Piter Punk for udev and slackpkg work, updating the shadow password system, writing the initial patch for polkit to use a shadow authentication backend so we could consider using KDE 4.4.3, and making tap-to-click work with Synaptics touchpads out-of-the-box,)
[URL]
/etc/modprobe.d/psmouse(.conf) allready has this commented line: #options psmouse proto=imps
After compiling the 2.6.36.2 kernel and re-installing the Nvidia proprietary drivers, my touchpad has started to act strange; the cursor seems to glide a lot faster, yet more erratic and when I try to hover over an icon the cursor wont stay still, furthermore I lost the ability to 'click' on anything using just touchpad.
I have checked dmesg and Xorg.log for any clues, as well as removed everything with the exception of the card and device section from my xorg.conf. The issue has nothing to do with compiling the new kernel, as it was working perfect until I installed the Nvidia driver.
After upgrading to -current (using slackpkg), my touchpad scrolling won't work.I remember that this had solved my problem previous time and in fact, after upgrade I have changed nothing (since this file already existed there). When I check the /usr/share/hal/fdi/ policy/ 10osvendor/ directory, I see that no "11-x11-synaptics.fdi" file was present. I just copied the file from /etc/hal/fdi/policy into this directory, but this did not help. Can somebody guide me through this?
What happens is on first boot, my Synaptics touchpad is not being recognised by the Kernel, so I have to boot a second time when it will start working.I have followed and tried loads of advice from different threads, including the copying and editing of the 11-x11-synaptics.fdi file under etc/hal/policy. Also the psmouse proto=any trick. The rmmod and further modprobe of psmouse. Restarting both HALD and UDEV both later and earlier in the boot procedure . The results of all of which is the same. The touchpad only works on second and subsequent warm boots.Below is the output of cat /proc/bus/input/devices for cold and warm bootCold boot
I am running Ubuntu 10.04 Lucid Lynx LTS. My laptop is an HP Pavilion TX1210AU (TX1000 series). After disabling the touchpad using the toggle button and reenabling it again, it stopped working. I tried restarting my laptop and the mouse worked again only up to the Login Screen. After logging in to my account, the mouse froze again. I tried making a new account and tried logging into it (I'm using it now) and it's now fixed. Does Ubuntu change any user settings everytime the touchpad toggle (on/off) button is switched? Maybe I could just reenable it myself.
Now i have 64 bit computer i installed Slackware 23 64 bit on it. i followed Alien Bob's multi lib how to and installed needed libraries one by one. everything is fine expect wine configure script can not find some libraries needed: libgsm, libmpg123, libopenal, libxcomposite.
I have already installed 32 bit compatibility packages and used /etc/profile.d/32bit.sh as recommended in Alien Bob's howto. configure -- does not really list anything for pointing for libraries.
When i want to configure my touchpad on my dell inspiron 1525 with debian lenny then i got this message: gsynaptics couldnt initialize you have to set 'shmconfig' 'true' in xorg.conf or xf86config to use gsynaptics My touchpad is an alps and not a synaptics so far i can see. My xorg.conf is this: [URL]
i tried following the readme file included in the driver of the usb network adapter but seems its not exact.
any ideas on how i can configure it manually? KDE does not detect any wifi device. .(of course since no driver is installed yet).
i used my desktop (win***)with DSL connection and installed the driver of the usb net adapter.. made it as the access point. . so my laptop detects the desktop as wifi spot.
I'm trying to find a VNC server for Slackware 13.1. I was searching around a little and I found that there are quite many. The most popular for slackware were tightVNC, x11vnc. I think in Slackware 13.1 is by default installed the libvnc but I can't find documentation on how to configure it.
what is the configuration file responsible for the X system !!! i did not have /etc/X11/xorg.conf file and the X server was pretty good and i can open it through "startx" command.i created xorg.config by "xorgsetup" program but i could not feel any change. i wanna reconfigure my display driver to be sure it's functioning at maximum performance.
Has anyone noticed this bug in KDE 4.5? It started for me with the official 4.5.1 packages in -current, and is now continuing with Alien Bob's 4.5.2 packages. I don't think it happened with previous 4.5.0 builds I was using.
1) Right-click title bar, select "Configure Window Behavior" 2) the "Desktop Effects" option is selected by default, but displays the "Window Decorations" screen instead. 3) Clicking on another option on the left will show appropriate screen. 4) Finally clicking on "Desktop Effects" will show the proper screen to configure effects.
[URL]. [In the screenshot above, you can see "Desktop Effects" pre-selected, but displaying the wrong screen.]. Bug still shows up with a brand new user account with fresh .kde. My searching for other bug reports has turned up nothing, so I'm wondering if this is unique to slackware for whatever reason. I'm running slackware64-current, up to date, with NVIDIA binary drivers.
Does anybody know how to configure a lenovo t60 to use internet?I installed Slackware fresh and I chose not to configure the network when it prompted me during installation. Now I have cable so I ran netconfig and picked DHCP and entered "darkswamp", "darkswamp.org", and I left the last one blank.I can't research how to configure my internet because I don't have internet. I can only come to library to figure it out.
I m trying to find an answer for this matter. I have download the SNMP version which I am concerned due to the following problems. I am trying to configure the SNMPD.conf and I cannod find any tutorial on the internet.
I downloaded the following product.
Linux version :
Linux version 2.6.18 (root@srv03) (gcc version 3.3.6) #1 SMP Sat Sep 23 19:32:53 BRT 2006
SNMP
net-snmp-5.4.2.1-i486-1_slack12.0.tgz
when I run the command snmpd I have the following problems
root@srv03:~# snmpd snmpd: /lib/libc.so.6: version `GLIBC_2.4' not found (required by snmpd)
I dont know how to configure the SNMPD.conf there is anyway
I am on a slackware13.0 machine, that I just finished upgrading to 13.1 with slackpkg.(did slackpkg update;slackpkg upgrade-all; slackpkg install-new. I did not restart the machine). Now im attempting to run the mrtg slackbuild but I get the following during the configure stage:Quote:
I've recently updated my Slackware 13.1 system to the Slackware current. Although I have created my "initrd" image without specifying the "-u" option to "mkinitrd" it still starts up "udev".
That is causing me some difficulty because I am using "dmraid" to detect my RAID arrays. I had created my own device names such as "/dev/sdr2" for my root partition. With 13.1 I had no problem, since "udev" was not started by the "initrd" unless the "-u" option was provided. The current version seems to start up "udev" even without that option.
Is there a way to disable "udev" in the "initrd", or is there a way to specify custom "udev" rules for an "initrd"? I tried placing a "10-local.rules" file in the "etc/udev/rules.d" directory of the "initrd-tree" but that file had no effect on the device names generated by "udev" during the "initrd".
Here is my script that creates the "initrd".
Code:
ROOTDEVNAME="/dev/sdr2"# Name of root device LINUXVER="2.6.35.7-smp"# Linux modules version CLIBVER="2.12.1"# C library version ROOTDIR="/boot/initrd-tree"# Location of root filesystm
[code]....
It will be helpful for me to understand "udev" issues related to an "initrd" because I will eventually try to use "mdadm" instead of "dmraid". So far I have only been able to get my system to boot from the RAID array using "dmraid" and I often run into new problems when I update Linux. Still, Slackware has proven to have the best support for booting from my RAID array because of the user community, documentation and flexibility.
