Installed Xorg-7.7 and now touchpad stopped to respond. What should I do?

[Dinir]

My netbook originally uses 1366x768 resolution, and can't use 915resolution since it's using nVidia chipset.

So I tried installing Xorg-7.7.tcz as onBoot, and as I couldn't make change with it (console says 'Only console user can...' message), I rebooted the computer.

Now, after booting touchpad doesn't respond. I don't know if the touchpad is the only thing not working. I have to make hard power off.

I need to get my touchpad back...

[Juanito]

What version and architecture of tinycore are you using?

What make of touchpad do you have?

Did you download Xorg-7.7 using the apps gui or did you do it manually?

[Dinir]

I connected a USB mouse into it, now I know that
- touchpad 'buttons' work.
- sudo Xorg outputs this:
(EE)
Fatal server error:
(EE) Server is already active for display 0
        If this server is no longer running, remove /tmp/.X0-lock
        and start again.
(EE)
(EE)
Please consult the The X.org Foundation support
         at http://wiki.x.org
 for help.
(EE)
- if I remove the .X0-lock Terminal says I have to restart X server first to do anything with Xorg.
- I changed resolution to 800x600 before reboot, so now when I move mouse whole screen scrolls up and down.
- But I can't access Xvesa again. It instantly shutdown as I clicked it on wbar.

What version and architecture of tinycore are you using?

What make of touchpad do you have?

Did you download Xorg-7.7 using the apps gui or did you do it manually?

uname -r says '3.16.6-tinycore'.
I am using Asus EeePC 1201N, I don't think what I should answer about the touchpad...
I downloaded it using the apps gui. I set it to loaded onBoot using the apps gui.

[Juanito]

It's hard to help if you don't know what touchpad you have...

You can try to load the xf86-input-synaptics extension and Xorg-7.7 and then look at /var/log/Xorg.0.log for any error messages.

Note that from the console prompt you start Xorg or Xvesa with "startx" and not with "sudo Xorg".

[Dinir]

I runned cat Xorg.0.log | grep -n 'WW' and cat Xorg.0.log | grep -n 'EE'. and this is the result.

Code: [Select]

15: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
27:[    36.195] (WW) The directory "/usr/local/lib/X11/fonts/OTF/" does not exist.
29:[    36.195] (WW) The directory "/usr/local/lib/X11/fonts/100dpi/" does not exist.
46:[    36.211] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
60:[    36.229] (WW) Warning, couldn't open module nouveau
63:[    36.229] (EE) Failed to load module "nouveau" (module does not exist, 0)
65:[    36.230] (WW) Warning, couldn't open module nv
68:[    36.230] (EE) Failed to load module "nv" (module does not exist, 0)
92:[    36.248] (EE) open /dev/dri/card0: No such file or directory
93:[    36.248] (WW) Falling back to old probe method for modesetting
94:[    36.248] (EE) open /dev/dri/card0: No such file or directory
101:[    36.274] (EE) open /dev/fb0: No such device
102:[    36.274] (WW) Falling back to old probe method for fbdev
109:[    36.302] (EE) open /dev/fb0: No such device
110:[    36.302] (EE) Screen 0 deleted because of no matching config section.
112:[    36.302] (EE) Screen 0 deleted because of no matching config section.
1206:[    37.759] (WW) VESA(0): Unable to estimate virtual size
1215:[    37.759] (WW) VESA(0): No valid modes left. Trying less strict filter...
1219:[    37.759] (WW) VESA(0): Unable to estimate virtual size
1271:[    38.632] (EE) AIGLX: reverting to software rendering
1272:[    38.632] (EE) AIGLX error: dlopen of /usr/local/lib/dri/swrast_dri.so failed (/usr/local/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
1273:[    38.632] (EE) GLX: could not load software renderer
1468:[    40.741] (EE) AIGLX: reverting to software rendering
1469:[    40.741] (EE) AIGLX error: dlopen of /usr/local/lib/dri/swrast_dri.so failed (/usr/local/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
1470:[    40.741] (EE) GLX: could not load software renderer
I thought I should use Xorg on console as I saw a post saying I could use something like Xorg & xrandr -s 800x600.

[Dinir]

But since I don't have any idea about what my touchpad is, probably I could not try using Xorg to change resolution.

Removed Xorg and got my touchpad back.

[Juanito]

Could you post all of Xorg.0.log please?

[Dinir]

Of course I'll do. Now even I removed Xorg touchpad has gone again... I should ask help for sure.

It is 1660 lines though...
http://pastebin.com/9zcF8G7R

[Juanito]

The xorg log says it found your synaptics touchpad and loaded the driver, so I'm surprised it doesn't work...

[Dinir]

So there will be no way I can get help then... :,(

Thank you for listening to my problem.

[gerald_clark]

Does your keypad have a lock button?  Perhaps you turned it off.

[dentonlt]

Xorg recognizes my Chromebook touchpad as a Synaptics, but that driver doesn't actually work - I have to build/use the Cyapa module. Compare your dmesg output w/ and w/o Xorg - that might help identify what's different.

It's possible the touchpad button/sensor mapping is mixed up. Perhaps dig around with xinput?

HTH

Sent from my HTC_0P6B6 using Tapatalk

[JaguarDown]

Does your keypad have a lock button?  Perhaps you turned it off.

Thanks! I have an older Acer Aspire One with a synpatics touch pad and I was in the same exact situation. I installed Xorg 7.7 which seemed to break my touchpad. The log said it was fine. After reading this post by gerald_clark, I looked on my keyboard and found a function key that probably locked it, and sure enough my touchpad came back to life! The only problem is that it only has very basic function, you can't tap click, you have to use the actual buttons. Not sure why, I even have xf86 synaptics input extension. That may have been what "helped the keypad unlock" because I thought I tried the unlocking solution before without success, but this time I loaded the extension first. Thanks for the help!