i inserted a live usb and hit esc in bios and selected UEFI:sandisk and during the install process formatted /boot as EFI

everything else was same installation

hope this helps people...

]]>https://bbs.archlinux.org/profile.php?id=763352013-10-30T00:53:26Zhttps://bbs.archlinux.org/viewtopic.php?pid=1343173#p1343173FIXED! It was what I suspected: fn-keys doesnt work in Arch. I found an old thread where some guy tried booting into fedora live, activating his touchpad, then rebooting into arch again, and it worked for him.

I tried exactly that, downloaded the latest fedora live cd, burned it, rebooted, pressed fn+f5 (which is the touchpadbutton on this laptop), it got the touchpad working in fedora, then just hardkilled the laptop by holding down the powerbutton, start it up in arch again, and it simply works!

I will do some research on how fedora handles fn-toshiba-keys and try to implement it into arch!

1. I found out there exists a c++-library to talk to the synapticsdriver, called libsynaptics. I created a small app to get some debugging information from synaptics, but either libsynaptics is broken or the current synaptics-driver in arch is(or libsynaptics, I dont really know). Anyway I uploaded the program here: http://haikarainen.dotgeek.org/syndbg.tar.gz

syndbg / syndbg-clean.sh should be perfectly runnable for most arch users, but I've included the source, few helperscripts and a readme.

syndbg is the executable, syndbg-clean.sh is a small script that tries to only display syndbg:s output and filter out libsynaptics.

Basically what it does is use libsynaptics functions to retrieve information (like if it finds hardware, driver, versions etc). I get some weird results(from libsynaptics), and I'd truly appreciate if someone else with a touchpad tested this and gave me their output, and if their touchpad is working.

Well, your kernel sees the device and allocates an event stream for it. When you look at the stream, however, there are no data. I think that is the root of problem. It makes sense as you had stated it comes up in a disabled state. I'll look at this some more this evening (UTC -7)

Thanks a lot! Older version of synaptics wouldnt even load (tried to insmod a freshly compiled 1.5 from xfree86), so files turned out invalid :S

]]>https://bbs.archlinux.org/profile.php?id=634952012-09-07T16:16:06Zhttps://bbs.archlinux.org/viewtopic.php?pid=1158186#p1158186Well, your kernel sees the device and allocates an event stream for it. When you look at the stream, however, there are no data. I think that is the root of problem. It makes sense as you had stated it comes up in a disabled state. I'll look at this some more this evening (UTC -7)]]>https://bbs.archlinux.org/profile.php?id=272892012-09-07T14:55:01Zhttps://bbs.archlinux.org/viewtopic.php?pid=1158149#p1158149Just tried the lts-kernel. No change regarding the synaptics. Will try to find another version of xf86-input-synaptics.]]>https://bbs.archlinux.org/profile.php?id=634952012-09-07T14:48:59Zhttps://bbs.archlinux.org/viewtopic.php?pid=1158143#p1158143ewaller wrote:

Lets try a little experiment.

First, figure out which event number belongs to the touch pad....On my system it is currently mapped to event11. Note that this sometimes changes at boot time.

From a console, with the X system not running, try a sudo od -x /dev/input/event11but change the event number to match your mapping.

Try the touch pad and see if you see a stream of stuff.

Report back.

/sys/class/input/event9/device/name:SynPS/2 Synaptics TouchPad

od -x /dev/input/event9

returns absolutely nothing. I tried the same with cat while in an xserver, still nothing. Also tried it with both sudo as well as root, since I also have some problems running X-programs with sudo (no display or protocol set). kdesu works like a charm though.

EDIT: To think of it, synclient wont work with sudo neither, think this might be related?

I think we have the same issue https://bbs.archlinux.org/viewtopic.php?id=148115I tried booting into a live CD with linux mint on it to see if it had anything to do with the pad on/off key not working. The key didn't work there either. Have you tried booting into another dist?

Im not 100% positive that it is the exact same issue, I dont get the "bad data" error I have tried linux mint on this laptop a few months ago (probably before the current kernel release), it did work. Debian also with no problems.

On my system it is currently mapped to event11. Note that this sometimes changes at boot time.

From a console, with the X system not running, try a sudo od -x /dev/input/event11but change the event number to match your mapping.

Try the touch pad and see if you see a stream of stuff.

Report back.

]]>https://bbs.archlinux.org/profile.php?id=272892012-09-07T04:29:46Zhttps://bbs.archlinux.org/viewtopic.php?pid=1157972#p1157972I think we have the same issue https://bbs.archlinux.org/viewtopic.php?id=148115I tried booting into a live CD with linux mint on it to see if it had anything to do with the pad on/off key not working. The key didn't work there either. Have you tried booting into another dist?]]>https://bbs.archlinux.org/profile.php?id=201242012-09-06T23:23:16Zhttps://bbs.archlinux.org/viewtopic.php?pid=1157912#p1157912EDIT: FIXED: https://bbs.archlinux.org/viewtopic.php … 1#p1158481

Fresh install of Arch and KDE, my synaptics touchpad seems to be identified, xf86-input-synaptics is installed, synclient works, synaptiks identifies my touchpad etc. But it doesnt respond at all to input.