Not sure if it is related. Let me know if I should file another bug.
I have the bcm5974-dkms module installed but it doesn't work at bootup.
I find that I have to rmmod bcm5974; modprobe bcm5974 to get it to work.
This is on lucid with the mactel PPA
--
[Jaunty] MacBook 5.1 touchpad not fully
It seems like there's a lot of noise on this bug; for what it's worth,
I'm only really interested in one of the things mentioned in #38
https://bugs.launchpad.net/linux/+bug/337935/comments/38, Can't click
and hold with thumb while dragging with another finger.. I have a
MacBook 5,3; on Karmic I
Doesn't work out of the box for me on current Karmic Beta, as Jim Rorie
claims. It used to work on Intrepid with some additional packages from
the Mactel Support PPA, but I deliberately dropped all PPA packages
after updating to Karmic, and even moved the fdi file I had created on
Intrepid. So my
The package in the PPA is really a kernel module. It could be that the
version of that driver that we have in the kernel is a bit dated.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New = Confirmed
** Changed in: linux
Unfortunately the bcm5974-dkms PPA module is delivered as full text
source, not as a patch against some underlying kernel source. So when
comparing that file to the one in the current kernel, and as I don't
know the common ancestor, I don't know which modifications were
introduced in the kernel
Stupid me: it's the Gnome settings which disabled taps and stuff like
that. I just found out that with my fdi file in place, taps worked all
right in the gdm login screen, but failed once the session was started.
I found the corresponding settings in System / Settings / Mouse /
Touchpad.
So I
So I take back my complaints: things work, only the Mactel guides
talking about fdi files need adjusting, as settings are now per-user
and
not per-system. If you can manage to log in without those settings,
that
is.
Martin,
Could you be more specific about the per user/per session
Martin:
doesn't that touchpad have physical buttons?
If it doesn't have buttons then the gnome-settings-daemon should enable
tap-to-click by default (only in this case)
** Tags removed: xorg-needs-kernel-fix
** Changed in: linux (Ubuntu)
Status: Confirmed = Invalid
--
[Jaunty] MacBook
I'll try. The current docs describe how you should place a file in
/etc/hal/fdi/policy/ in order to enable tapping and two-finger scrolling
and such stuff. While this is still true for the initial settings of the
X server, once a user logs in, gnome-settings-daemon overwrites these
initial
Ok, If I understand this correctly, you are saying that the hal
configuration file is only used for X. Gnome is controlled through
gnome-settings-demon and most of the settings are changed through gconf
or menu. You are not sure about KDE. Synclient controls extended
values. I assume these
Jim Rorie wrote:
Ok, If I understand this correctly, you are saying that the hal
configuration file is only used for X. Gnome is controlled through
gnome-settings-demon and most of the settings are changed through gconf
or menu. You are not sure about KDE.
Correct.
Synclient controls
On a 13 Macbook Pro 5.5 I followed all the steps and nothing worked for
me. :(
Making a .fdi file found on the Karmic Wiki:
https://help.ubuntu.com/community/MacBookPro5-5/Karmic?highlight=%28%28MacBookPro5-5|Karmic%29%29
Blacklisting usbhid then in /etc/modules then loading bcm5974 and then
Tapping and two finger scroll/context menu appear to be working as of
Karmic Alpha 6. Both features are accessible in default install and
controllable under preferences. Two things of note:
1) Hal policy file values for FingerLow and FingerHigh appear to be
ignored. My touchpad will track my
** Summary changed:
- [Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
+ [Jaunty] MacBook 5.1 touchpad not fully supported
--
[Jaunty] MacBook 5.1 touchpad not fully supported
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member
I think the bug has been fixed in the update. At least I cannot reproduce it
anymore.
See the changelog here:
https://launchpad.net/~mactel-support/+archive/ppa/+sourcepub/612058/+listing-archive-extra
So maybe someone wants to close this bug?
--
[Jaunty] MacBook 5.1 touchpad not fully
acron, those are community-made packages. This fix is still an issue for
Ubuntu.
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Johannes,
thanks. That (meaning depmod update-initramfs) did the trick for me as well
:-).
Cheers, Nikos
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member of Ubuntu
Bugs,
Ricky,
thanks, good point ;-) I updated the wiki with the info.
I wasn't sure if some kind of privileges would be needed to edit the wiki but
there weren't...
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug
1. I would like to confirm the existence this bug in the final version of
jaunty.
2. Eric's walkaround didn't work for me until I run:
sudo depmod -ae
sudo update-initramfs -u
Could someone update the wiki with that?
Btw the MacBook5-1/Jaunty-Page is not linked from here
acron,
if you see things that should be added to a wiki page, go for it. That
is the idea of wiki pages.
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member of Ubuntu
Bugs,
I just reinstalled Ubuntu 9.04 Beta on my MacBookPro (4,1) and found out
that right click is working (without mactel-support or any patches) if
you put *three* fingers on the touchpad and the click anywhere... Can
anyone confirm that for another model?
--
[Jaunty] MacBook 5.1 touchpad not fully
yes. It was that way for me since I have been using Jaunty.
3 finger tap should also work.
2-fingers is middle click I think.
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a
This bug affects also MacBook Pro 5,1.
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Apparently, OS X does have the ability to do a right-click by two-
finger-clicking feature (enabled together with two-finger-tapping).
Doing the same will require some state tracking. Something to look into
next. Still, the patch should improve the current experience as long as
two-finger tapping
I would say that this patch and associated feature request be put into
another bug report since this bug is really about getting the fdi file
to work at all, not modifying the touchpad driver to add/remove
functionality.
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
I removed the patch and the package here as I created a new bug report with an
improved version of the patch that does not break two-finger-clicking and makes
the behavior similar to OS X:
https://bugs.edge.launchpad.net/mactel-support/+bug/356317
** Attachment removed: Make click-and-drag
@P. Dunbar: OK, the problem was actually that my .fdi file was not
taking effect! So SHMConfig was defaulted to false and all my settings
had no effect. I grabbed the .fdi file off the wiki and started fresh,
and got it working better. The sensitivity is great now.
--
[Jaunty] MacBook 5.1
Here is a patch for bcm5974-dkms to make click-and-drag work with
Macbook 5,1. When clicking with two fingers touching the trackpad, it
simply ignores the finger that is doing the clicking (the one that is
relatively lower on the touchpad), just like OS X does. It does *not*
disable the bottom
** Attachment added: deb package for testing
http://launchpadlibrarian.net/24852553/bcm5974-dkms_1.1.4_all_test.deb
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member of
** Attachment added: Synaptics bcm5974 policy
http://launchpadlibrarian.net/24852563/x11-synaptics-bcm5974.fdi
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member of Ubuntu
I don't seem to have a big sensitivity problem. I am currenlty using the .fdi
file I have on the wiki (not sure if its the same I uploaded here at this
point).
My big issue with the touchpad is the dragging as you mentioned as well. In
Mac OSX I primarily will drag with holding my thumb
I got the trackpad on my MacBook Pro 5,1 *mostly* working by doing:
(On a fresh install of Jaunty Beta)
1. Install all the mactel PPA packages.
2. Blacklist usbhid
3. Put bcm5974, usbhid in modprobe's modules file to force bcm5974 to load
first.
4. Put the file posted above by P. Dunbar on
Workaround disables the keyboard in Jaunty Beta, both internal and
external USB keyboards. Removal of the policy file restores normal
keyboard functioning.
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug
Sorry, macbook pro 5,1
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Use the attached .fdi file.
I was messing with this last night and some of the .fdi files I used on the
wiki above or this wiki https://help.ubuntu.com/community/MacBookPro4-1/Jaunty
caused me the same behavior.
I was just ready to update this wiki:
This affects *also* MacBookPro (4,1)! Thanks for the workaround.
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Great! I thought this might affect the MacBookPro4,1 as well. It is
probably likely that it affects the MacBook(Pro)5.x models as well since
they use the same touchpad driver.
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You
It seems at this point that the kernel is where this would have to be fixed.
which means if you want a fully working touchpad on your mac you'd might want
to use intrepid cause I doubt kernel modifications will come any time soon for
this.
--
[Jaunty] MacBook 5.1 touchpad not fully supported
Mm, this line says the trackpad is added as a raw input device:
[ 10.121135] apple 0003:05AC:0236.0002: input,hidraw2: USB HID v1.11
Keyboard [Apple, Inc. Apple Internal Keyboard / Trackpad] on
usb-:00:04.0-6/input0
-- Is there a way to blacklist usbhid so it does not claim the device,
to
It seems to me like blacklisting usbhid is a poor workaround... wouldn't
that prevent you from using external mice, etc. in the usual way (ie,
plug it in and it works)?
Would it be possible for mactel support to continue to provide a patched
usbhid kernel module (as I assume the case had been
I can confirm blacklisting usbhid worked for me. I simply made a
blacklist entry for usbhid and then in /etc/modules I loaded bcm5974 and
then usbhid.
That way usbhid still gets loaded, but after bcm5974
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
Good idea Eric. I think that is easier than maintaining a package.
usbhid code is at bitmath.org git repo though...
http://bitmath.org/code/usbhid-dkms/
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug
Ricky Campbell wrote:
Good idea Eric. I think that is easier than maintaining a package.
I'm glad you found a workaround, since this problem got tougher with the
new 2.6.28 kernel.
usbhid code is at bitmath.org git repo though...
http://bitmath.org/code/usbhid-dkms/
The possibility to
I can confirm that Eric's workaround worked for me too.
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Great. Can someone edit the wiki page here appropriately so that can be closed
against Mactel-Support?
https://help.ubuntu.com/community/MacBook5-1/Jaunty#Trackpad
** Changed in: mactel-support
Status: New = Triaged
** Also affects: linux
Importance: Undecided
Status: New
**
The wiki has been updates appropriately.
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
On a fresh install of Jaunty a6 hal starts in runlevel 2, and
x11-common starts in runlevel 5, so the hal/X11 trick is probably not a
valid workaround.
Should this be entered as a bug or question for the Jaunty kernel?
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
P. Dunbar wrote:
I've installed the bcm5974-dkms for jaunty from the mactel ppa and still
can not get any .fdi profiles to do anything.
The conjecture is that the built-in HID module is stealing the mouse
interface. To confirm, please reboot and attach the full output of dmesg.
Henrik
--
I think someone in the forum mentioned that hal was not loading before
xorg or something which cause xorg to not see the hardware properly. I
can't seem to find the post now. He editted the number of the script so
that it would load in the right order.
--
[Jaunty] MacBook 5.1 touchpad not fully
Here is my dmesg output on a clean boot.
** Attachment added: dmesg output
http://launchpadlibrarian.net/24189298/dmesg.out
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a
P. Dunbar wrote:
Here is my dmesg output on a clean boot.
** Attachment added: dmesg output
http://launchpadlibrarian.net/24189298/dmesg.out
Mm, this line says the trackpad is added as a raw input device:
[ 10.121135] apple 0003:05AC:0236.0002: input,hidraw2: USB HID v1.11
Keyboard
confirmed. bcm5974 is not in /proc/bus/input/devices
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I've installed the bcm5974-dkms for jaunty from the mactel ppa and still
can not get any .fdi profiles to do anything.
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member of
I'm also experiencing this issue. Opening up xev the trackpad doesn't
produce any events on anything other than left click (I don't know if it
should be expected to if the problem is simply that the FDI is not being
utilized).
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of
Ed K wrote:
I'm also experiencing this issue. Opening up xev the trackpad doesn't
produce any events on anything other than left click (I don't know if it
should be expected to if the problem is simply that the FDI is not being
utilized).
The jaunty kernel does not include the necessary
XOrg-Driver-Synaptics is not the correct package name for -synaptics.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Sourcepackagename: xorg = xserver-xorg-input-synaptics
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You
Still no luck with this, despite several kernel and Xorg updates.
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: xorg-driver-synaptics
Status: New = Invalid
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
any reason this was decided invalid against synaptics?
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Can I provide any more information to help?
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Could this be related to this bug:
https://bugs.edge.launchpad.net/ubuntu/+source/xfree86-driver-synaptics/+bug/336523
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member of
Quite possibly. Some differences:
* `grep bcm5974 /proc/bus/input/devices` returns nothing (I'm attaching the
file). This could be rather important--this device should show up here, no? I
do have that module loaded, as confirmed by the lsmod attached above.
* xserver-xorg-input-synaptics is
This a different bug. In my bug, the touchpad would not work at all
because synaptics did not install by default. This bug still seems to
affect me even after fixing the other bug. The issue here is that the
fdi policy file seems to be completely ignored. I haven't looked too
deeply into my
** Attachment added: lsmod output
http://launchpadlibrarian.net/23441283/lsmod.txt
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: Synaptics policy
http://launchpadlibrarian.net/23441199/11-x11-synaptics.fdi
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: lspci output
http://launchpadlibrarian.net/23441288/lspci.txt
** Also affects: mactel-support
Importance: Undecided
Status: New
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this
** Description changed:
Binary package hint: xorg
The touchpad for MacBook 5.1 is not supported completely in Jaunty
(Ubuntu 9.04) as of Alpha 5 release. The pointer can move, and a
physical left-click works, but that's it. I can not get tapping to
respond as I could using the Mactel
** Also affects: xorg-driver-synaptics
Importance: Undecided
Status: New
** Also affects: hal
Importance: Undecided
Status: New
** Changed in: mactel-support
Importance: Undecided = Medium
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
Please attach the output of `lspci -vvnn`, and attach your
/var/log/Xorg.0.log file from after reproducing this issue. If you've
made any customizations to your /etc/X11/xorg.conf please attach that as
well.
** Changed in: xorg (Ubuntu)
Status: New = Incomplete
--
[Jaunty] MacBook 5.1
Sure thing.
** Attachment added: lspci output (verbose)
http://launchpadlibrarian.net/23451471/lspci_verbose.txt
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launchpad.net/bugs/337935
You received this bug notification because you are a member of
Here I attach my current Xorg file, which uses the nVIDIA restricted
driver. The conditions remain with this xorg.conf.
** Attachment added: current Xorg file
http://launchpadlibrarian.net/23451502/xorg.conf
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
My original xorg.conf file from the out of the box install was
completely empty, apparently. As such I can't actually attach it here in
Launchpad. Suffice to say, I experienced the touchpad issue using the
empty xorg.conf file, even when supplying the fdi file for the hal
policy.
--
[Jaunty]
72 matches
Mail list logo
