Puppy 2.16 install problem(s)

Please post any bugs you have found
Message
Author
User avatar
edoc
Posts: 4729
Joined: Sun 07 Aug 2005, 20:16
Location: Southeast Georgia, USA
Contact:

#61 Post by edoc »

edoc wrote:
GuestToo wrote:if you have a frugal install, copy the missing seamonkey-bin file from /initrd/pup_ro2/usr/lib/mozilla/ to /usr/lib/mozilla/

if you have a full install, boot the Puppy cd maybe using the pfix=ram option, mount the partition, and copy the missing seamonkey-bin file from /usr/lib/mozilla/ to the mounted partition

there may be other missing files
Thanks, did the copy, will reboot.

Any idea why this would have happened?
You weren't kidding that there were other missing files! :-)

I copied the entirety of /initrd/pup_ro2/usr/lib/mozilla/ TO /usr/lib/mozilla/
and Seamonkey seems to now be OK.

The HTML icon now returns the usual - open this under your browser
message, kind of a wasted icon.

gxine is still unresponsive.

How do I fix that, please?

And also, any idea what may have hiccupped to cause these significant
gaps in the upgrade process from 2.14 to 2.16?
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603

GuestToo
Puppy Master
Posts: 4083
Joined: Wed 04 May 2005, 18:11

#62 Post by GuestToo »

it depends what the problem with gxine is ... if it's missing or corrupted files, the files need to be replaced ... there may be missing or corrupted library files or configuration files

depending on the circumstances, an upgrade may not work properly

in your case, it sounds like you are having hardware problems, or maybe the cd did not burn properly, or maybe the iso file did not download properly

if the iso does not download properly, you would have a corrupted iso file, which would not be a Puppy iso at all ... it would be some sort of corrupted thing that might do anything to your system

i usually download isos with wget, which usually works well ... i always check the iso file's md5sum to be sure it is perfect ... i usually run Puppy as a frugal install, so i don't burn a cd, i just mount the iso file and copy the 4 files from it ... so to upgrade Puppy i might do something like this:

wget -c http://distro.ibiblio.org/pub/linux/dis ... so.md5.txt
wget -c http://distro.ibiblio.org/pub/linux/dis ... rivers.iso
md5sum -c puppy-2.16-seamonkey-fulldrivers.iso.md5.txt
mount -o loop puppy-2.16-seamonkey-fulldrivers.iso /mnt/data
cp /mnt/data/vmlinuz /mnt/home/
cp /mnt/data/initrd.gz /mnt/home/
cp /mnt/data/pup_216.sfs /mnt/home/
cp /mnt/data/zdrv_216.sfs /mnt/home/

it's a good idea to backup the pup_save file first ... which is very easy, just copy the file somewhere ... i have never had a pup_save file larger than 256 megs

GuestToo
Puppy Master
Posts: 4083
Joined: Wed 04 May 2005, 18:11

#63 Post by GuestToo »

if you use a pup_save file (you seem to) you can look in /initrd/pup_rw ... corrupted and damaged and deleted files should be visible in there

there may be hidden .wh. whiteout files in pup_rw that are causing some files in pup_ro2 to be invisible and therefore "deleted" ... if there are .whw. files that should not be there, they could be deleted and the files in pup_ro2 (the pup_216.sfs file0 should be available again ... i have a script that deletes all .wh. whiteout files

find /initrd/pup_rw -noleaf -name '.wh.*' > /tmp/wh.txt
cat /tmp/wh.txt | while read J
do
echo rm -f \"$J\"
[ -r "$J" ] && rm -f "$J"
done
sync
sync

you need to reboot immediately after deleting files in pup_rw (unionfs does not like it)

basslord1124
Posts: 73
Joined: Tue 12 Dec 2006, 03:11

#64 Post by basslord1124 »

I downloaded 2.16 today to try it out and didn't make it very far. It made it through the first few steps in the boot process on the CD and then it crashes telling me it can't find my CD or something to that effect. I don't remember the exact error but that's basically what it said. CD is good and checksum worked out fine. So for right now, I am halting on 2.16 and just gonna stick with 2.15.

And my 2 cents...
While I absolutely enjoy Puppy Linux, I just have not been impressed with the last 2 versions. While I can get 2.15 to work, it was not without a little bit of headache to make it work. I think the most trouble-free versions I have experienced so far is Puppy 2.13 and 2.14.
[url=http://groups.myspace.com/puppylinux]The Official Myspace Puppy Linux Group[/url]

User avatar
edoc
Posts: 4729
Joined: Sun 07 Aug 2005, 20:16
Location: Southeast Georgia, USA
Contact:

#65 Post by edoc »

basslord1124 wrote:I downloaded 2.16 today to try it out and didn't make it very far. It made it through the first few steps in the boot process on the CD and then it crashes telling me it can't find my CD or something to that effect. I don't remember the exact error but that's basically what it said. CD is good and checksum worked out fine. So for right now, I am halting on 2.16 and just gonna stick with 2.15.

And my 2 cents...
While I absolutely enjoy Puppy Linux, I just have not been impressed with the last 2 versions. While I can get 2.15 to work, it was not without a little bit of headache to make it work. I think the most trouble-free versions I have experienced so far is Puppy 2.13 and 2.14.
I am guessing that the differences are partially hardware-specific because the
newer versions are accessing new hardware and are running more sophisticated
apps.

I have used most of the MS-like Linux distros with all of their code-bloat and
saw the same sort of occasional upgrade anomalies. The good thing about
Puppy is that the code is efficient and easier for the team to troubleshoot.
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603

basslord1124
Posts: 73
Joined: Tue 12 Dec 2006, 03:11

#66 Post by basslord1124 »

edoc wrote:
I am guessing that the differences are partially hardware-specific because the
newer versions are accessing new hardware and are running more sophisticated
apps.

I have used most of the MS-like Linux distros with all of their code-bloat and
saw the same sort of occasional upgrade anomalies. The good thing about
Puppy is that the code is efficient and easier for the team to troubleshoot.
I figure that newer hardware support might've been part of the reason, although I hope this doesn't mean that the quality of the support on old hardware is deteriorating. It almost seems it with the last 2 versions for me....of course maybe it's me, but then again, if I put a slightly newer version of Puppy on a machine that was already running Puppy, I expect to not really have any troubles. Now if I switched hardware around that'd be different. That is actually one of the main reasons I went with Puppy was b/c I had some old machines that I wanted to sort of revive with a nice lightweight Linux distro. I never was all that crazy for DSL, then when I found Puppy I was just amazed at how well it performed.

Manually entering a soundcard config isn't that big of a deal, but telling me it can't find my CD drive when it was reading from it 30 seconds earlier kinda is in my book. Never was able to get the system fully booted. Of course I never did try it in my old desktop, so not too sure if I will get the same result. The CD error was with my laptop. I dunno....I love Puppy Linux and it is one of the main distros I recommend to people looking for something lightweight...but these past 2 versions of the distro just have not liked me for some reason.
[url=http://groups.myspace.com/puppylinux]The Official Myspace Puppy Linux Group[/url]

basslord1124
Posts: 73
Joined: Tue 12 Dec 2006, 03:11

update.....

#67 Post by basslord1124 »

Well, my desktop didn't mind it at least and installed without a hitch. So now the issue is with my laptop....
[url=http://groups.myspace.com/puppylinux]The Official Myspace Puppy Linux Group[/url]

basslord1124
Posts: 73
Joined: Tue 12 Dec 2006, 03:11

update part 2....

#68 Post by basslord1124 »

Well I managed to get it going on my laptop....sorry for the previous response, my patience was a little thin that day. I ended up using the ide=nodma option at boot time before I was able to get anywhere with the installation. I have never had to do that before in previous versions of puppy.

The only thing I have noticed now which this is a minor issue, is that my touchpad on my laptop partially works...I can move the mouse pointer around but when I touch it to highlight something nothing happens. I have to use the buttons to highlight or select anything.
[url=http://groups.myspace.com/puppylinux]The Official Myspace Puppy Linux Group[/url]

User avatar
edoc
Posts: 4729
Joined: Sun 07 Aug 2005, 20:16
Location: Southeast Georgia, USA
Contact:

Re: update part 2....

#69 Post by edoc »

basslord1124 wrote:Well I managed to get it going on my laptop....sorry for the previous response, my patience was a little thin that day. I ended up using the ide=nodma option at boot time before I was able to get anywhere with the installation. I have never had to do that before in previous versions of puppy.

The only thing I have noticed now which this is a minor issue, is that my touchpad on my laptop partially works...I can move the mouse pointer around but when I touch it to highlight something nothing happens. I have to use the buttons to highlight or select anything.
My 2.16 on my laptop was handling my USB mouse fine until I forgot it at home and had to use the pad.

Came home and powered up and now it refuses to recognize the USB mouse.

Very odd ... but then my 2.16 install hiccupped so I really need to do a reinstall from a clean CD.
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603

User avatar
edoc
Posts: 4729
Joined: Sun 07 Aug 2005, 20:16
Location: Southeast Georgia, USA
Contact:

#70 Post by edoc »

GuestToo wrote: i usually download isos with wget, which usually works well ... i always check the iso file's md5sum to be sure it is perfect ... i usually run Puppy as a frugal install, so i don't burn a cd, i just mount the iso file and copy the 4 files from it ... so to upgrade Puppy i might do something like this:

mount -o loop puppy-2.16-seamonkey-fulldrivers.iso /mnt/data
Just had a moment to try this and I receive two errors.

What are these errors telling me, please?

sh-3.00# mount -o loop puppy-2.16.1-seamonkey-fulldrivers.iso /mnt/data
mount: ioctl: LOOP_SET_FD: Invalid argument
mount: Could not setup loop device
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603

User avatar
edoc
Posts: 4729
Joined: Sun 07 Aug 2005, 20:16
Location: Southeast Georgia, USA
Contact:

#71 Post by edoc »

edoc wrote:
GuestToo wrote: i usually download isos with wget, which usually works well ... i always check the iso file's md5sum to be sure it is perfect ... i usually run Puppy as a frugal install, so i don't burn a cd, i just mount the iso file and copy the 4 files from it ... so to upgrade Puppy i might do something like this:

mount -o loop puppy-2.16-seamonkey-fulldrivers.iso /mnt/data
Just had a moment to try this and I receive two errors.

What are these errors telling me, please?

sh-3.00# mount -o loop puppy-2.16.1-seamonkey-fulldrivers.iso /mnt/data
mount: ioctl: LOOP_SET_FD: Invalid argument
mount: Could not setup loop device
Was going to try burning a CD but am out of blanks!

Sigh.

Waiting on y'all to tell me how to boot the iso ...
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603

GuestToo
Puppy Master
Posts: 4083
Joined: Wed 04 May 2005, 18:11

#72 Post by GuestToo »

i'm not sure what the error is referring to

if the iso file name or mount point name is not correct, the error would be something like this:

mount: puppy-2.16.1-seamonkey-fulldrivers.iso: No such file or directory
mount: Could not setup loop device

if there were no free loop devices, the error would be something like:

mount: Could not find a spare loop device

if the iso file is corrupted, it might look like this:

mount: Mounting puppy-2.16.1-seamonkey-fulldrivers.iso on /mnt/data failed: Invalid argument

the closest error message to your error message would be for a corrupted iso file ... i would check the md5sum of the iso file ... type:

md5sum puppy-2.16-seamonkey-fulldrivers.iso

and see if it is the same as the md5sum in the md5sum.txt file

User avatar
edoc
Posts: 4729
Joined: Sun 07 Aug 2005, 20:16
Location: Southeast Georgia, USA
Contact:

#73 Post by edoc »

GuestToo wrote: the closest error message to your error message would be for a corrupted iso file ... i would check the md5sum of the iso file ... type:

md5sum puppy-2.16-seamonkey-fulldrivers.iso

and see if it is the same as the md5sum in the md5sum.txt file
I had checked that but just checked it again, it is good.

I thought I'd try a couple of other things to see if any useful info could be
generated:

sh-3.00# mount -o loop puppy-2.16.1-seamonkey-fulldrivers.iso /mnt/data
mount: ioctl: LOOP_SET_FD: Invalid argument
mount: Could not setup loop device
sh-3.00# mount -o loop
/dev/root on /initrd type ext2 (rw)
/dev/hda1 on /initrd/pup_rw type ext2 (rw)
tmpfs on /initrd/mnt/tmpfs type tmpfs (rw)
/dev/loop0 on /initrd/pup_ro2 type squashfs (ro,noatime)
unionfs on / type unionfs (rw,dirs=/initrd/pup_rw=rw:/initrd/pup_ro2=ro,debug=4294967295,delete=whiteout)
none on /proc type proc (rw)
none on /dev/pts type devpts (rw)
none on /sys type sysfs (rw)
none on /proc/bus/usb type usbfs (rw)
sh-3.00# mount -o loop puppy-2.16.1-seamonkey-fulldrivers.iso /mnt/data
mount: ioctl: LOOP_SET_FD: Invalid argument
mount: Could not setup loop device
sh-3.00#


Guess I will have to buy some CD's today and try that method again
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603

kirk
Posts: 1553
Joined: Fri 11 Nov 2005, 19:04
Location: florida

#74 Post by kirk »

Edoc, make sure that the file your trying to mount on the loopback device is not in Puppy's normal file system (/root or anywhere in your pup_save file). If it is copy it to a harddrive partition (/mnt/home) and try it there.

User avatar
alienjeff
Posts: 2265
Joined: Sat 08 Jul 2006, 20:19
Location: Winsted, CT - USA

Re: update part 2....

#75 Post by alienjeff »

basslord1124 wrote:The only thing I have noticed now which this is a minor issue, is that my touchpad on my laptop partially works...I can move the mouse pointer around but when I touch it to highlight something nothing happens. I have to use the buttons to highlight or select anything.
That's a design "feature." Seems as though some folks don't have the patience to teach themselves to keep their cotton-picking thumbs off the touchpad when they're typing. So Barry disabled "tap." Sad, eh?

-aj
[size=84][i]hangout:[/i] ##b0rked on irc.freenode.net
[i]diversion:[/i] [url]http://alienjeff.net[/url] - visit The Fringe
[i]quote:[/i] "The foundation of authority is based upon the consent of the people." - Thomas Hooker[/size]

PaulBx1
Posts: 2312
Joined: Sat 17 Jun 2006, 03:11
Location: Wyoming, USA

#76 Post by PaulBx1 »

Depends on your point of view. I hate "tap", as I'm always inadvertently tapping something I don't want. Maybe because I never got tired of the mouse, and don't use the touchpad much.

Best would be to have it configurable, of course. Maybe it is, I don't know.

John Doe
Posts: 1681
Joined: Mon 01 Aug 2005, 04:46
Location: Michigan, US

#77 Post by John Doe »


kirk
Posts: 1553
Joined: Fri 11 Nov 2005, 19:04
Location: florida

#78 Post by kirk »

That's a design "feature." Seems as though some folks don't have the patience to teach themselves to keep their cotton-picking thumbs off the touchpad when they're typing. So Barry disabled "tap." Sad, eh?
Nope, that's my doing in Dougals reworked xorgwizard. Before, the touchpad was treated as a ps/2 mouse and on many touchpads the slightest touch would cause a click. Also, none of the other touchpad features where availble.

Edit /etc/X11/xorg.conf-synaptic. If you want to enable touch pad tapping (touching the pad to click the mouse) change "MaxTapTime" to 130 found in xorg.conf. You can adjust this number as needed. You must restart X for the changes to take effect! Here's the readme:
Synaptics TouchPad driver for XOrg/XFree86
------------------------------------------

Introduction
------------

This is a driver for the Synaptics TouchPad for XOrg/XFree86 4.x. A
Synaptics touchpad by default operates in compatibility mode by
emulating a standard mouse. However, by using a dedicated driver, more
advanced features of the touchpad becomes available, such as:

- Movement with adjustable, non-linear acceleration and speed.
- Button events through short touching of the touchpad.
- Double-Button events through double short touching of the touchpad.
- Dragging through short touching and holding down the finger on the
touchpad.
- Middle and right button events on the upper and lower corner of
the touchpad.
- Vertical scrolling (button four and five events) through moving
the finger on the right side of the touchpad.
- The up/down button sends button four/five events.
- Horizontal scrolling (button six and seven events) through moving
the finger on the lower side of the touchpad.
- The multi-buttons send button four/five events, and six/seven
events for horizontal scrolling.
- Adjustable finger detection.
- Multifinger taps: two finger for middle button and three finger
for right button events. (Needs hardware support. Not all models
implement this feature.)
- Run-time configuration using shared memory. This means you can
change parameter settings without restarting the X server.

Note that depending on the touchpad firmware, some of these features
might be available even without using the synaptics driver. Note also
that some functions are not available on all touchpad models, because
they need support from the touchpad hardware/firmware. (Multifinger
taps for example.)


Installation
------------

See the INSTALL file for detailed installation instructions.


Compatibility
-------------

The driver has been reported to work on a number of different laptop
computers. See the COMPATIBILITY file for the list. If your computer
is not listed, please let me (petero2@telia.com) know if the driver
works on your computer.


Parameters
----------

See the synaptics(5) manual page for a description of the available
driver parameters.


FAQ
---

* Is this free software?

Yes, the source code is released under the GNU General Public
License.

* When will the driver be included in the XOrg distribution?

This is unlikely to happen because of copyright issues. Although
the GPL license is compatible with the license used by the XOrg X
server, the XOrg project doesn't want to include GPL code in their
source code, because it would effectively make the whole XOrg
project GPL. The synaptics license can't be changed unless all
copyright holders agree to change the license, but previous
attempts to find all copyright holders for the synaptics source
code have failed.

So unfortunately, the best we can currently hope for is that the
synaptics driver is included as a separate package by the major
distributions.

* How do I use this driver with Linux kernel 2.6.x?

You need to have the "evdev" driver loaded or compiled into the
kernel (CONFIG_INPUT_EVDEV). Set the "Protocol" parameter in the X
configuration file to "auto-dev". Also, if you set the "Device"
parameter to "/dev/psaux", the same X configuration file should
work for a 2.4.x kernel.

When configuring the kernel, enable PS/2 mouse support
(CONFIG_MOUSE_PS2).

* It still doesn't work with a 2.6 kernel.

Some distributions come with an incomplete /dev directory. The
driver needs the /dev/input/eventX device nodes. Try to create
them manually if they don't exist already. (Look at
/proc/bus/input/devices to figure out how many nodes you need.)

# mknod /dev/input/event0 c 13 64
# mknod /dev/input/event1 c 13 65
# mknod /dev/input/event2 c 13 66
...

* How can I configure tap-to-click behavior?

If you set MaxTapTime=0 in the X config file then the touchpad
will not use tapping at all, i.e. touching/tapping will not be
taken as a mouse click.

If, instead, you set MaxTapMove=0 in the X config file, then the
touchpad will not use tapping for a single finger tap (left mouse
button click) but will for the two and three finger tap (middle
and right button click).

* Why did tap-to-click stop working after I upgraded from an old version?

Time is now measured in milliseconds instead of "number of
packets". In practice, this means that if you are upgrading from
an old version, you need to change MaxTapTime and
EmulateMidButtonTime to make "tap to click" work. Good values are
180 and 75 respectively.

* Gnome scrollbars scroll too much when using tap-to-click. Why?

The ClickTime parameter is probably too big. Try setting it to
100. Gnome scrollbars use auto repeat, ie if you press the left
mouse button and keep it pressed, the scroll bar will move until
you release the button. This will lead to problems if the tap time
is longer than the delay before auto repeat starts.

* Vertical and horizontal scrolling events are mixed up. How come?

Probably because some X startup/login script uses xmodmap to remap
the mouse buttons. Correct settings for the touchpad are:

xmodmap -e 'pointer = 1 2 3 4 5 6 7'

You can check the current settings by running:

xmodmap -pp

* Horizontal scrolling doesn't work in some programs. Is it a driver
bug?

No, probably not. Support for horizontal scroll events must be
handled by the application programs. Not all programs do that
yet. Ask the authors of the application in question to implement
support for horizontal scroll events.

You can use the "xev" program to check if the synaptics driver
generates the horizontal scroll events.

* Can the driver be used together with gpm?

No, not reliably, if you are using a 2.4.x kernel. The gpm driver
and the X driver both try to read data from the touchpad, and if
they try to read at the same time, both drivers see incomplete
data and don't know how to interpret it.

If you are running a 2.6.x kernel though, there should be no
conflict, because the kernel driver will make sure both user space
drivers receive all events from the touchpad.

* How do I compile the driver?

Beginning with version 0.11.8, it should be possible to compile
the driver by simply running "make". This will compile a driver
for XFree86 4.2.x, which will also work for 4.3.x versions of
XFree86.

If you have an older version of XFree86, you will need an
installed X source tree. On an RPM based distribution, you can
build a suitable source tree by installing the XFree86 source RPM
and compile it. For example, in RedHat 9, use the following
commands:

# rpm -vU XFree86-4.3.0-2.src.rpm
# cd /usr/src/redhat/SPECS
# rpmbuild -bb XFree86.spec

Then change the TOP variable in the Makefile to match the version
of XFree86 you are using. In the example above, set

TOP = /usr/src/redhat/BUILD/XFree86-4.3.0/xc

* Can I use this driver with an ALPS Glidepoint device?

Yes, see the README.alps file for more information.

* The driver says "reset failed" and the touchpad doesn't work. What
can I do?

This problem has been reported for some Compaq models. It's
currently not known why it happens, but removing the reset command
from the driver appears to make it work. If you use a 2.4 linux
kernel, replace the contents of the ps2_synaptics_reset() function
in ps2comm.c with a "return TRUE;" statement. If you use a 2.6
linux kernel, remove the while loop in synaptics_query_hardware()
in the file drivers/input/mouse/synaptics.c in the linux kernel
source code.


Authors
-------

Many people have contributed to this driver. Look at the top of
synaptics.c and ps2comm.c for details.

The current maintainer is Peter Osterlund <petero2@telia.com>.



Installation of the Synaptics Touchpad Driver for XOrg/XFree 4.x
================================================================

Author: Stefan Gmeiner <riddlebox@freesurf.ch>

Requirements
------------

1. You need X include files. On RPM based systems, they are usually
included in the XFree86-devel package. On Debian systems, you need
to install the packages x-dev, libx11-dev and libxext-dev.

2. For use with kernel 2.6.x you need to enable synaptics touchpad
support when configuring the kernel (CONFIG_MOUSE_PS2). You also
need support for the evdev interface (CONFIG_INPUT_EVDEV). If you
compile evdev as a module, make sure it is loaded before starting
the X server, as it will not be auto-loaded.

3. If you use XFree86 version 4.0 or 4.1, you will need the XFree86
source code to compile the driver. See the "How do I compile the
driver?" section in the FAQ in the README file for details.

4. Using with kernel 2.4.x for x < 10 needs a kernel patch
(pc_keyb.c.diff.2.4.3).

Installing
----------

1. Type "make" to build the driver "synaptics_drv.o".

2. Copy the driver module "synaptics_drv.o" into the XFree module
path. This path is usually "/usr/X11R6/lib/modules/input/", and
running "make install" as root will do this for you. Note though
that some distributions have a different module path. For example,
in Gentoo 1.4 (with XFree86 4.3.0), the correct path is
"/usr/X11R6/lib/modules/drivers".

3. Add the driver to the XFree configuration file (usually called
/etc/X11/XF86Config-4 or /etc/X11/XF86Config)

Section "Module"
...
Load "synaptics"
...
EndSection


4. Add/Replace in the InputDevice section for the touchpad the
following lines:

Section "InputDevice"
Identifier "Synaptics Mouse"
Driver "synaptics"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "LeftEdge" "1700"
Option "RightEdge" "5300"
Option "TopEdge" "1700"
Option "BottomEdge" "4200"
Option "FingerLow" "25"
Option "FingerHigh" "30"
Option "MaxTapTime" "180"
Option "MaxTapMove" "220"
Option "VertScrollDelta" "100"
Option "MinSpeed" "0.09"
Option "MaxSpeed" "0.18"
Option "AccelFactor" "0.0015"
Option "SHMConfig" "on"
# Option "Repeater" "/dev/ps2mouse"
EndSection

Change the Identifier to the same name as in the ServerLayout section.
The Option "Repeater" is at the moment for testing.

5. Add the "CorePointer" option to the InputDevice line at the
ServerLayout section:

Section "ServerLayout"
...
InputDevice "Synaptics Mouse" "CorePointer"
...

Note! You can not have more than one core pointer, so if you want
to use an external mouse too, you have to set all mouse input
devices except one to "AlwaysCore" instead of "CorePointer". For
example:

Section "ServerLayout"
...
InputDevice "Mouse0" "CorePointer"
InputDevice "Synaptics Mouse" "AlwaysCore"
...
Section "InputDevice"
...
Identifier "Mouse0"
Option "Device" "/dev/input/mice"
...

This also applies if you are using a 2.6 linux kernel and the
touchpad contains a "pass through" device. Usually a pass through
device is a touch stick located in the middle of the keyboard, but
it can also be a separate set of buttons located next to the
touchpad. If you want the pass through device to be enabled in X,
the second InputDevice is needed. If there is a line in
/proc/bus/input/devices that begins with "P: Phys=synaptics-pt" it
means that the kernel has found a pass through device.

6. Start/Restart the X Server. If the touchpad doesn't work:
a) Check the XFree log file. This file is usually called
/var/log/XFree86.0.log.
b) Try to start the X server with 'startx -- -logverbose 8' for
more output.

7. If you want to be able to change driver parameters without
restarting the X server, enable the "SHMConfig" option in the XFree
configuration file. You can then use the "synclient" program to
query and modify driver parameters on the fly.
Note! This is not secure if you are in an untrusted multiuser
environment. All local users can change the parameters at any
time.

If you can't get the driver working, check the trouble-shooting.txt
file for common problems. If that doesn't help, mail the log files and
the configuration file to petero2@telia.com. If you use a 2.6.x linux
kernel, also mail the output from dmesg and the output from
"cat /proc/bus/input/devices".

User avatar
edoc
Posts: 4729
Joined: Sun 07 Aug 2005, 20:16
Location: Southeast Georgia, USA
Contact:

ISO burn warning & touchpad tap

#79 Post by edoc »

Second item first ...

The prior discussion in this wide-ranging thread suggested that the
"tap" feature of a laptop touchpad has been disabled - this is not
correct in all cases - mine works fine.

First item -- for which I need a solution ...

When I run the isoburn app in 2.4 I am greeted with the following pop-
up warning:

"cdrecord: WARNING: Drive returns wrong startsec (0) using -150"

Should I be concerned or is this another of those to-be-ignored errors
that will eventually be eliminated or captured and discarded and not
displayed?
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603

User avatar
edoc
Posts: 4729
Joined: Sun 07 Aug 2005, 20:16
Location: Southeast Georgia, USA
Contact:

Re: ISO burn warning & touchpad tap

#80 Post by edoc »

edoc wrote: First item -- for which I need a solution ...

When I run the isoburn app in 2.4 I am greeted with the following pop-
up warning:

"cdrecord: WARNING: Drive returns wrong startsec (0) using -150"

Should I be concerned or is this another of those to-be-ignored errors
that will eventually be eliminated or captured and discarded and not
displayed?
I ignored the warning and used the CD to copy the four Frugal Install files.
No further errors or warnings observed.

I see no difference between my prior incomplete 2.6 install and the current
2.6.1 install -- most troublesome is the continued failure to activate my USB
mouse - -- it had been working prior to 2.6 and even afterwards but I booted
my laptop once without the USB mouse attached and now it never works.

Very odd ...
without
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603

Post Reply