search

mmonaco / PKGBUILDs

Arch Linux PKGBUILDs
2 stars 2 forks source link

Error with synaptic-led #1

Open sailerboy opened 11 years ago

sailerboy commented 11 years ago

Hi. When I install this package, it compiles just fine into the package, but on install, it gives me this error:

depmod: tools/depmod.c:980: mod_free: Assertion `mod->kmod == ((void *)0)' failed. /tmp/alpm_z5eKAW/.INSTALL: line 1: 9275 Aborted depmod error: command failed to execute correctly

mmonaco commented 11 years ago

Hmm, I can't recreate this. What kernel version are you compiling against? Have you upgraded your kernel recently and not rebooted? What version of kmod do you have?

sailerboy commented 11 years ago

[sailerboy@ALEXHP ~]$ uname -a Linux ALEXHP 3.6.6-1-ARCH #1 SMP PREEMPT Mon Nov 5 11:57:22 CET 2012 x86_64 GNU/Linux [sailerboy@ALEXHP ~]$ kmod -V kmod version 11

I've rebooted many times. It still doesn't work. I'm using the latest updates from Arch.

mmonaco commented 11 years ago

What happens if you just run

$ sudo depmod
sailerboy commented 11 years ago

If the package isn't installed, no output. If the package is installed, I get the following:

depmod: tools/depmod.c:980: mod_free: Assertion `mod->kmod == ((void *)0)' failed.
mmonaco commented 11 years ago

kmod 11-2 in testing will fix your problem. It is ok to download the pkg manually and install it with pacman -U (it doesn't require anything else in testing)

sailerboy commented 11 years ago

Well, that solves my error, but the LED doesn't work (that is, doesn't show up in /sys/class/leds), even though the package was installed cleanly. I guess my laptop doesn't support the LEDs then :(

At least the double-tap to disable touchpad works fine.

mmonaco commented 11 years ago

The patch is hard-coded to a specific model. There's a line in the patch that has 0xe4, you can try replacing that with the product ID of your touchpad.

sailerboy commented 11 years ago

I'm terribly sorry, but in searching, there's about 10-20 different possible IDs. How do I find the proper ID?

mmonaco commented 11 years ago

I updated the package on the AUR last night, have you tried it?

sailerboy commented 11 years ago

Yes, no dice.

mmonaco commented 11 years ago

There has to be a better way, but you can try adding a debug line to that patch:

printk(KERN_WARNING, "SYNAPTICS: my id is %x\n", SYN_CAP_PRODUCT_ID(priv->ext_cap));

Then, you should be able to see that line in the output of dmesg

mmonaco commented 11 years ago

Nevermind, I add some debugging lines directly to the package to help in the future, try rebuilding and show me the output of dmesg | grep "synaptics: led"

sailerboy commented 11 years ago

No output for synaptics: led

[sailerboy@ALEXHP ~]$ dmesg | grep "synaptics: led"
[sailerboy@ALEXHP ~]$ dmesg | grep "synaptics"
[   15.288081] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xd00123/0x840300/0x26c00, board id: 2054, fw id: 1096083
sailerboy commented 11 years ago

I forgot to mention, I'm using anrxc's patch from https://bbs.archlinux.org/viewtopic.php?id=142108

Would that cause an issue?

mmonaco commented 11 years ago

Which patch?

Also, I tried to change the way I defaulted the LED support to on and I don't think it worked. You can try the PKGBUILD from github (I didn't push a fix to the AUR yet)

sailerboy commented 11 years ago

This one: https://bbs.archlinux.org/viewtopic.php?pid=1111201#p1111201

I will try it and update.

sailerboy commented 11 years ago

No dice. There's a folder in /sys/class for it, but setting brightness to 255 has no effect.

mmonaco commented 11 years ago

Does dmesg have any log about a Synaptics LED?

sailerboy commented 11 years ago

Oh yes, sorry. 

[root@ALEXHP psmouse::synaptics]# dmesg | grep synaptics
[   14.338799] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xd00123/0x840300/0x26c00, board id: 2054, fw id: 1096083
[   14.338806] synaptics: support LED control
[   14.338869] Registered led device: psmouse::synaptics
mmonaco commented 11 years ago

I (yet again) messed up the patch and had a typo in the printk's.

If you install the latest version from the AUR (v7) the driver should setup the LED on /sys. Can you confirm this, and post the output of dmesg | grep -i synaptics

If you have the LED, but the double-tap portion doesn't work, then we need to look at it from the Xorg side.

Even if the double-tap doesn't work, you can try manually disabling with synclient and see if the light comes on.

sailerboy commented 11 years ago

Double Tap works fine, but the LED doesn't light up, even if i manually trigger it by echoing 255 to brightness.

[   12.871521] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xd00123/0x840300/0x26c00, board id: 2054, fw id: 1096083
[   12.871525] synaptics: led: checking for led
[   12.871527] synaptics: led: your product ID is 84
[   12.871529] synaptics: led: looks like you have one
[   12.871530] synaptics: support LED control
[   12.871581] Registered led device: psmouse::synaptics
[   12.935926] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input4
mmonaco commented 11 years ago

Have you forced synpara.has_led = 1? I just updated the Xorg driver on the AUR with a debugging statement to check the result of access(). It may be that the kernel driver doesn't actually support your model...

sailerboy commented 11 years ago

Yes, I did force has_led to 1. After installing the new package, double-tap doesn't work any more. I'm not able to find any messages in dmesg other than the one that I have already posted.