[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#648678: module bcm5974 is not being loaded on mac book pro



On Mon, Nov 14, 2011 at 8:52 AM, David Roguin <nesdavid@gmail.com> wrote:
> On Mon, Nov 14, 2011 at 12:49 AM, Ben Hutchings <ben@decadent.org.uk> wrote:
>> On Sun, 2011-11-13 at 22:06 -0300, David Roguin wrote:
>>> Package: linux-image-3.1.0-1-amd64
>>> Status: install ok installed
>>> Priority: optional
>>> Section: kernel
>>> Installed-Size: 100967
>>> Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
>>> Architecture: amd64
>>> Source: linux-2.6
>>> Version: 3.1.0-1~experimental.1
>>> Provides: linux-image, linux-modules-3.1.0-1-amd64
>>> Depends: module-init-tools, linux-base (>= 3~), initramfs-tools (>=
>>> 0.99~) | linux-initramfs-tool
>>> Pre-Depends: debconf | debconf-2.0
>>> Recommends: firmware-linux-free (>= 3~)
>>> Suggests: linux-doc-3.1, grub-pc | extlinux | lilo (>= 22.8-8.2~)
>>> Breaks: initramfs-tools (<< 0.99~), lilo (<< 22.8-8.2~)
>>>
>>>
>>> The bcm5974 module is not being loaded on a mac book pro with Debian Wheezy.
>>> According to 'lsusb -t' usbhid module is handling the trackpad making
>>> the multitouch unusable.
>>
>> Please don't open a new bug report if you disagree with closing of
>> another.  We can always reopen that.
> Understood, but I've incorrected filled the previous bug against
> linux-3.0 when i meant linux-3.1
>
>> If I understand you correctly, usbhid can bind to the trackpad device
>> and should not.  Since usbhid is a class device (it works with most USB
>> 'human interface' devices, but not necessarily covering all their
>> features) we would need to add this device to a blacklist to prevent it
>> from doing that.  We will *not* fix this by making any driver built-in!
>
> I wasn't suggesting making the drivers built-in to fix the problem, I
> was just trying to note that building the custom kernel with those
> params made the trackpad work with multitouch capabilities.
> If I blacklist that module, should bcm5974 be loaded at start?
>
>> Please send the 'lsusb' output for this system, and the content of
>> '/sys/devices/virtual/dmi/id/product_name'.
>
> lsusb
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 001 Device 002: ID 0424:2513 Standard Microsystems Corp.
> Bus 001 Device 003: ID 05ac:8509 Apple, Inc.
> Bus 002 Device 002: ID 0424:2513 Standard Microsystems Corp.
> Bus 001 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub
> (part of BCM2046 Bluetooth)
> Bus 001 Device 005: ID 05ac:0252 Apple, Inc.
> Bus 002 Device 003: ID 05ac:8242 Apple, Inc. IR Receiver [built-in]
> Bus 001 Device 008: ID 05ac:821a Apple, Inc.
> Bus 002 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
> Bus 002 Device 005: ID 0458:003a KYE Systems Corp. (Mouse Systems)
> NetScroll+ Mini Traveler / Genius NetScroll 120
> Bus 002 Device 006: ID 04f2:0833 Chicony Electronics Co., Ltd
>
>
> cat '/sys/devices/virtual/dmi/id/product_name'
> MacBookPro8,1
>
> Cheers!
>
> --
> David
>

It's fixed on Version: 3.1.1-1
Thanks!


-- 
David



Reply to: