Sempre i soliti problemi: Touchpad + mouse ps/2 help me plea

Loops · Messaggio da **Loops** » dom 29 mag 2005, 18:31

Dopo avere fatto un affarone, compaq armada 110 (700 mhz) a 50 euri. Ho
 installato la mia bella slack 10.1 e fino a qua tutto ok. Non contento
 del kernel 2.4 (che potete dire tutto ma a me nn piace) ho compilato
 prima il 2.6.10 dopo un errore che riporto dopo ho provato il 2.6.11 ma
 senza miglioramenti. Il mio problema è questo: 
 Il portatile ha il touchpad ma ha anche la porta ps/2 x mouse o
 tastiera, ovviamente io ho colegat un mouse ps/2 con rotellina. Dando
 un colpo di "dmesg" vengono fuori 2000 stringhe di questo tipo: 
 psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1 
 psmouse.c: TouchPad at isa0060/serio1/input0 - driver resynched. 
 Ora il touchpad funzion alla perfezione, il mouse ps/2 non va nemmeno
 ammazzato. Girando su internet non ho trovato nulla, sareste così
 gentili da darmi una mega mano??? Vi ringrazio Ciao Loops

Messaggio da **Bart** » dom 29 mag 2005, 18:49

Anche a me succede lo stesso, solo che a me non va nemmeno il touchpad(
 non è proprio touchpad ma è il pallino sulla tastiera). Potresti
 provare a ricompilare il kernel mettendo staticamente il supporto a
 ps/2. Io ancora non ho avuto voglia di farlo. 
 Prova con un mouse usb se va anche se credo proprio che non avrai problemi. 
 Ciao. 
 
 ps: IMHO devi censurare un pochino la tua firma.

jaco1279 · Messaggio da **jaco1279** » dom 29 mag 2005, 20:21

Ciao...intanto dovresti controllare le impostazioni del file
 /etc/X11/xorg.conf. Li hai tutte le impostazioni necessarie al
 funzionamento del server X. Dovresti vedere, alla fine della pagina, le
 impostazioni del mouse e del touchpad: ti allego il mio per farti
 capire come fare: 
 
 # Each InputDevice line specifies an InputDevice section name and 
 # optionally some options to specify the way the device is to be 
 # used. Those options include "CorePointer", "CoreKeyboard" and 
 # "SendCoreEvents". 
 
 InputDevice "Mouse1" "CorePointer" 
 InputDevice "touchpad" "AlwaysCore" 
 InputDevice "Keyboard1" "CoreKeyboard" 
 
 Devi settare quindi il touchpad come "AlwaysCore" ed il mouse come
 "CorePointer". Inoltre, nella sezione "Core Pointer´s InputDevice
 section" dovresti controllare l´impostazione del mouse...ti consiglio
 di dare una lettura al documento Slackware for dummies contenuto nella
 sezione Howto di questo sito...è davvero completo!!!! 
 
 Per quanto riguarda il kernel...potrebbe anche non essere necessaria la
 ricompilazione. Apri la tua con con make xconfig e controlla se il
 modulo del mouse è inkernelato o messo come modulo...se è come modulo
 basta richiamare il modulo. Nell 2.6.XX il file dei moduli dovrebbe
 essere modprobe.conf. Se non compare neanche come modulo devi per forza
 ricompilare!!! 
 
 Ciao 
 
 Angelo

Loops · Messaggio da **Loops** » dom 29 mag 2005, 20:41

nulla da fare!! psmouse è messo come modulo e me lo carica in
 automatico, ma ho sempre lo stesso errore. comunque se nn va dal kernel nn
 va nemmeno da X Aiutatemi x favoreeeeeeeeeeeeeeeee

jaco1279 · Messaggio da **jaco1279** » dom 29 mag 2005, 22:01

...mi posti il tuo /etc/X11/xorg.conf...inoltre potresti vedere cosa ti
 da il comando tail -f /var/log/message...magari posti anche quello...

Loops · Messaggio da **Loops** » lun 30 mag 2005, 1:21

premetto che
 sto cercando di sistemare il problema passando a un mouse seriale (che
 porca pupazzola mi sta dando problemi pure lui) comunque sotto posto
 l´xorg,conf 
 [ Questo Messaggio è stato Modificato da: Loops il 30-05-2005 01:24 ]

Loops · Messaggio da **Loops** » lun 30 mag 2005, 1:21

Ecco xorg.conf 
 
 <TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD>Quote:<HR></TD></TR><TR><TD><BLOCKQUOTE>
 # File generated by xorgconfig. 
 
 # 
 # Copyright 2004 The X.Org Foundation 
 # 
 # Permission is hereby granted, free of charge, to any person obtaining a 
 # copy of this software and associated documentation files (the "Software"), 
 # to deal in the Software without restriction, including without limitation 
 # the rights to use, copy, modify, merge, publish, distribute, sublicense, 
 # and/or sell copies of the Software, and to permit persons to whom the 
 # Software is furnished to do so, subject to the following conditions: 
 # 
 # The above copyright notice and this permission notice shall be included in 
 # all copies or substantial portions of the Software. 
 # 
 # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
 # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
 # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL 
 # The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, 
 # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF 
 # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 
 # SOFTWARE. 
 # 
 # Except as contained in this notice, the name of The X.Org Foundation shall 
 # not be used in advertising or otherwise to promote the sale, use or other 
 # dealings in this Software without prior written authorization from 
 # The X.Org Foundation. 
 # 
 
 # ********************************************************************** 
 # Refer to the xorg.conf(5x) man page for details about the format of 
 # this file. 
 # ********************************************************************** 
 
 # ********************************************************************** 
 # Module section -- this section is used to specify 
 # which dynamically loadable modules to load. 
 # ********************************************************************** 
 # 
 Section "Module" 
 
 # This loads the DBE extension module. 
 
 Load "dbe" # Double buffer extension 
 
 # This loads the miscellaneous extensions module, and disables 
 # initialisation of the XFree86-DGA extension within that module. 
 SubSection "extmod" 
 Option "omit xfree86-dga" # don´t initialise the DGA extension 
 EndSubSection 
 
 # This loads the font modules 
 Load "type1" 
 # Load "speedo" 
 Load "freetype" 
 # Load "xtt" 
 
 # This loads the GLX module 
 Load "glx" 
 # This loads the DRI module 
 # Load "dri" 
 EndSection 
 
 # ********************************************************************** 
 # Files section. This allows default font and rgb paths to be set 
 # ********************************************************************** 
 
 Section "Files" 
 
 # The location of the RGB database. Note, this is the name of the 
 # file minus the extension (like ".txt" or ".db"). There is normally 
 # no need to change the default. 
 
 RgbPath "/usr/X11R6/lib/X11/rgb" 
 
 # Multiple FontPath entries are allowed (which are concatenated together), 
 # as well as specifying multiple comma-separated entries in one FontPath 
 # command (or a combination of both methods) 
 # 
 # 
 
 FontPath "/usr/X11R6/lib/X11/fonts/misc/" 
 FontPath "/usr/X11R6/lib/X11/fonts/TTF/" 
 FontPath "/usr/X11R6/lib/X11/fonts/Type1/" 
 FontPath "/usr/X11R6/lib/X11/fonts/CID/" 
 FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" 
 FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" 
 FontPath "/usr/X11R6/lib/X11/fonts/local/" 
 FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" 
 FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/" 
 
 # The module search path. The default path is shown here. 
 
 # ModulePath "/usr/X11R6/lib/modules" 
 
 EndSection 
 
 # ********************************************************************** 
 # Server flags section. 
 # ********************************************************************** 
 
 Section "ServerFlags" 
 
 # Uncomment this to cause a core dump at the spot where a signal is 
 # received. This may leave the console in an unusable state, but may 
 # provide a better stack trace in the core dump to aid in debugging 
 
 # Option "NoTrapSignals" 
 
 # Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence 
 # (where n is 1 through 12). This allows clients to receive these key 
 # events. 
 
 # Option "DontVTSwitch" 
 
 # Uncomment this to disable the <Crtl><Alt><BS> server abort sequence 
 # This allows clients to receive this key event. 
 
 # Option "DontZap" 
 
 # Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching 
 # sequences. This allows clients to receive these key events. 
 
 # Option "Dont Zoom" 
 
 # Uncomment this to disable tuning with the xvidtune client. With 
 # it the client can still run and fetch card and monitor attributes, 
 # but it will not be allowed to change them. If it tries it will 
 # receive a protocol error. 
 
 # Option "DisableVidModeExtension" 
 
 # Uncomment this to enable the use of a non-local xvidtune client. 
 
 # Option "AllowNonLocalXvidtune" 
 
 # Uncomment this to disable dynamically modifying the input device 
 # (mouse and keyboard) settings. 
 
 # Option "DisableModInDev" 
 
 # Uncomment this to enable the use of a non-local client to 
 # change the keyboard or mouse settings (currently only xset). 
 
 # Option "AllowNonLocalModInDev" 
 #Avvia X anche se il mouse PS/2 non e´ collegato 
 
 Option "AllowMouseOpenFail" 
 
 EndSection 
 
 # ********************************************************************** 
 # Input devices 
 # ********************************************************************** 
 
 # ********************************************************************** 
 # Core keyboard´s InputDevice section 
 # ********************************************************************** 
 
 Section "InputDevice" 
 
 Identifier "Keyboard1" 
 Driver "kbd" 
 
 # For most OSs the protocol can be omitted (it defaults to "Standard"). 
 # When using XQUEUE (only for SVR3 and SVR4, but not Solaris), 
 # uncomment the following line. 
 
 # Option "Protocol" "Xqueue" 
 
 Option "AutoRepeat" "500 30" 
 
 # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) 
 # Option "Xleds" "1 2 3" 
 
 # Option "LeftAlt" "Meta" 
 # Option "RightAlt" "ModeShift" 
 
 # To customise the XKB settings to suit your keyboard, modify the 
 # lines below (which are the defaults). For example, for a non-U.S. 
 # keyboard, you will probably want to use: 
 # Option "XkbModel" "pc102" 
 # If you have a US Microsoft Natural keyboard, you can use: 
 # Option "XkbModel" "microsoft" 
 # 
 # Then to change the language, change the Layout setting. 
 # For example, a german layout can be obtained with: 
 # Option "XkbLayout" "de" 
 # or: 
 # Option "XkbLayout" "de" 
 # Option "XkbVariant" "nodeadkeys" 
 # 
 # If you´d like to switch the positions of your capslock and 
 # control keys, use: 
 # Option "XkbOptions" "ctrl:swapcaps" 
 
 # These are the default XKB settings for Xorg 
 # Option "XkbRules" "xorg" 
 # Option "XkbModel" "pc101" 
 # Option "XkbLayout" "us" 
 # Option "XkbVariant" "" 
 # Option "XkbOptions" "" 
 
 # Option "XkbDisable" 
 
 Option "XkbRules" "xorg" 
 Option "XkbModel" "pc104" 
 Option "XkbLayout" "it" 
 
 EndSection 
 
 
 # ********************************************************************** 
 # Core Pointer´s InputDevice section 
 # ********************************************************************** 
 #Touchpad 
 Section "InputDevice" 
 Identifier "Mouse0" 
 Driver "mouse" 
 Option "Protocol" "PS/2" 
 Option "Device" "/dev/mouse" 
 EndSection 
 
 #Mouse PS/2 
 Section "InputDevice" 
 Identifier "Mouse1" 
 Driver "mouse" 
 Option "Protocol" "IMPS/2" 
 Option "Device" "/dev/psaux" 
 Option "ZAxisMapping" "4 5" 
 Option "Emulate3Buttons" "no" 
 EndSection 
 
 
 
 
 # ********************************************************************** 
 # Monitor section 
 # ********************************************************************** 
 
 # Any number of monitor sections may be present 
 
 Section "Monitor" 
 
 Identifier "My Monitor" 
 
 # HorizSync is in kHz unless units are specified. 
 # HorizSync may be a comma separated list of discrete values, or a 
 # comma separated list of ranges of values. 
 # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR´S 
 # USER MANUAL FOR THE CORRECT NUMBERS. 
 
 HorizSync 31.5 - 57.0 
 
 # HorizSync 30-64 # multisync 
 # HorizSync 31.5, 35.2 # multiple fixed sync frequencies 
 # HorizSync 15-25, 30-50 # multiple ranges of sync frequencies 
 
 # VertRefresh is in Hz unless units are specified. 
 # VertRefresh may be a comma separated list of discrete values, or a 
 # comma separated list of ranges of values. 
 # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR´S 
 # USER MANUAL FOR THE CORRECT NUMBERS. 
 
 VertRefresh 50-90 
 
 EndSection 
 
 
 # ********************************************************************** 
 # Graphics device section 
 # ********************************************************************** 
 
 # Any number of graphics device sections may be present 
 
 # Standard VGA Device: 
 
 Section "Device" 
 Identifier "Standard VGA" 
 VendorName "Unknown" 
 BoardName "Unknown" 
 
 # The chipset line is optional in most cases. It can be used to override 
 # the driver´s chipset detection, and should not normally be specified. 
 
 # Chipset "generic" 
 
 # The Driver line must be present. When using run-time loadable driver 
 # modules, this line instructs the server to load the specified driver 
 # module. Even when not using loadable driver modules, this line 
 # indicates which driver should interpret the information in this section. 
 
 Driver "vga" 
 # The BusID line is used to specify which of possibly multiple devices 
 # this section is intended for. When this line isn´t present, a device 
 # section can only match up with the primary video device. For PCI 
 # devices a line like the following could be used. This line should not 
 # normally be included unless there is more than one video device 
 # intalled. 
 
 # BusID "PCI:0:10:0" 
 
 # VideoRam 256 
 
 # Clocks 25.2 28.3 
 
 EndSection 
 
 # Device configured by xorgconfig: 
 
 Section "Device" 
 Identifier "Trident CyberBlade (generic)" 
 Driver "trident" 
 #VideoRam 65536 
 # Insert Clocks lines here if appropriate 
 EndSection 
 
 
 # ********************************************************************** 
 # Screen sections 
 # ********************************************************************** 
 
 # Any number of screen sections may be present. Each describes 
 # the configuration of a single screen. A single specific screen section 
 # may be specified from the X server command line with the "-screen" 
 # option. 
 Section "Screen" 
 Identifier "Screen 1" 
 Device "Trident CyberBlade (generic)" 
 Monitor "My Monitor" 
 DefaultDepth 24 
 
 Subsection "Display" 
 Depth 8 
 Modes "1280x1024" "1024x768" "800x600" "640x480" 
 ViewPort 0 0 
 EndSubsection 
 Subsection "Display" 
 Depth 16 
 Modes "1280x1024" "1024x768" "800x600" "640x480" 
 ViewPort 0 0 
 EndSubsection 
 Subsection "Display" 
 Depth 24 
 Modes "1280x1024" "1024x768" "800x600" "640x480" 
 ViewPort 0 0 
 EndSubsection 
 EndSection 
 
 # ********************************************************************** 
 # ServerLayout sections. 
 # ********************************************************************** 
 
 # Any number of ServerLayout sections may be present. Each describes 
 # the way multiple screens are organised. A specific ServerLayout 
 # section may be specified from the X server command line with the 
 # "-layout" option. In the absence of this, the first section is used. 
 # When now ServerLayout section is present, the first Screen section 
 # is used alone. 
 
 Section "ServerLayout" 
 
 # The Identifier line must be present 
 Identifier "Simple Layout" 
 
 # Each Screen line specifies a Screen section name, and optionally 
 # the relative position of other screens. The four names after 
 # primary screen name are the screens to the top, bottom, left and right 
 # of the primary screen. In this example, screen 2 is located to the 
 # right of screen 1. 
 
 Screen "Screen 1" 
 
 # Each InputDevice line specifies an InputDevice section name and 
 # optionally some options to specify the way the device is to be 
 # used. Those options include "CorePointer", "CoreKeyboard" and 
 # "SendCoreEvents". 
 
 InputDevice "Mouse0" "AlwaysCore" 
 InputDevice "Mouse1" "CorePointer" 
 InputDevice "Keyboard1" "CoreKeyboard" 
 
 EndSection 
 
 # Section "DRI" 
 # Mode 0666 
 # EndSection 
 
 
 </BLOCKQUOTE></TD></TR><TR><TD><HR></TD></TR></TABLE>

jaco1279 · Messaggio da **jaco1279** » lun 30 mag 2005, 15:51

...beh...sembra andare bene...non so...a questo punto penso sia proprio il caso di dare un´occhiata al kernel...

Loops · Messaggio da **Loops** » lun 30 mag 2005, 17:27

questo è l´output del tail 
 <TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD>Quote:<HR></TD></TR><TR><TD><BLOCKQUOTE> 
 May 30 17:25:11 CyberSmokers udev[4208]: removing device node ´/dev/vcc/a7´ 
 May 30 17:26:24 CyberSmokers udev[4231]: configured rule in
 ´/etc/udev/rules.d/udev.rules´ at line 99 applied, added symlink ´%k´ 
 May 30 17:26:24 CyberSmokers udev[4231]: configured rule in
 ´/etc/udev/rules.d/udev.rules´ at line 99 applied, ´vcs7´ becomes
 ´vcc/%n´ 
 May 30 17:26:24 CyberSmokers udev[4231]: creating device node ´/dev/vcc/7´ 
 May 30 17:26:24 CyberSmokers udev[4238]: configured rule in
 ´/etc/udev/rules.d/udev.rules´ at line 101 applied, added symlink ´%k´ 
 May 30 17:26:24 CyberSmokers udev[4238]: configured rule in
 ´/etc/udev/rules.d/udev.rules´ at line 101 applied, ´vcsa7´ becomes
 ´vcc/a%n´ 
 May 30 17:26:24 CyberSmokers udev[4238]: creating device node ´/dev/vcc/a7´ 
 May 30 17:26:31 CyberSmokers kernel: psmouse.c: TouchPad at isa0060/serio1/input0 - driver resynched. 
 May 30 17:26:38 CyberSmokers last message repeated 35 times 
 May 30 17:31:28 CyberSmokers kernel: psmouse.c: TouchPad at isa0060/serio1/input0 - driver resynched. 
 </BLOCKQUOTE></TD></TR><TR><TD><HR></TD></TR></TABLE> 
 
 <IMG SRC="http://utenti.lycos.it/morphinamount/Lo ... hansen.gif">
 [ Questo Messaggio è stato Modificato da: Loops il 30-05-2005 17:29 ]

jaco1279 · Messaggio da **jaco1279** » lun 30 mag 2005, 18:35

...potresti provare, anzichè utilizzare udev...usa hotplug. In pratica dovresti togliere l´eseguibilità al file /etc/rc.d/rc.udev col comando chmod -x rc.udev. Dopodicchè lancia il comando /etc/rc.d/rc.hotplug restart. Rifai tail -f /var/log/messages...prova anche a togliere e mettere il mouse e vedi cosa ti dice...se riesce a creare il driver vuol dire che il kernel riesce a vederlo quindi resta un problema del server X. Puoi anche utilizzare il comando mouseconfig. In pratica è un tool che ti permette di riconfigurare il mouse...vedi un po´!!!

Loops · Messaggio da **Loops** » mer 1 giu 2005, 20:53

Nulla da fare ho provato in tutti i modi pure a cancellare rc.udev
 cancellare tutti i dev dalla dir dev e riavviare ma nulla. Vabbè magari
 stasera mi ucciderò

comunque se nn riuscissi + a far nulla comprerò un
 mouse usb grazie a tutti x il supporto ciao 
 
 
 PS: se avete ancora idee potete continuare a postarle tnxxx

Loops · Messaggio da **Loops** » lun 6 giu 2005, 14:57

Ho risolto, alla carlona ma ho risolto, vi spiego come ho fatto.

Ho ricompilato il kernel 2.4.29 ed è tutto ok
L'unico problema che ho adesso è che se stacco il mouse ps/ il touchpad scatticchia e clicca continuamente, ma visto che uso il laptop sempre al tavolo il problema è risolto. Vi saluto grazie di tutto ciao