linux-kernel - Re: Linux Support for Thunderbolt using Apple Monitor

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120503233858.GA13453@kroah.com>
Date:	Thu, 3 May 2012 16:38:58 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Francois Rigaut <frigaut@...il.com>
Cc:	Nico Schottelius <nico-linux-20120419@...ottelius.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Linux Support for Thunderbolt using Apple Monitor

On Fri, May 04, 2012 at 09:04:33AM +1000, Francois Rigaut wrote:
> Sorry for the lag, I live down under.
> 
> On Fri, May 4, 2012 at 1:35 AM, Greg KH <gregkh@...uxfoundation.org> wrote:
> 
>     On Thu, May 03, 2012 at 09:45:00PM +1000, Francois Rigaut wrote:
>     > After Greg pointed to the PCIE, I realized that modules related to PCIE
>     > hotpluging were not loaded in my config. I then did a whole bunch of test
>     > modprobing a couple of modules: pciehp (with and without pciehp_force and
>     /or
>     > pciehp_poll_mode) and acpiphp (not together obviously). No
>     change:connecting
>     > the thunderbolt does not lead to any kernel activity. No message
>     whatsoever in
>     > /var/log/everything.log.
>     > Checked /sys/bus/pci/slots, nothing appeared. No change in lspci. Added a
>     "echo
>     > 1 > /sys/bus/pci/rescan" for good measure to no avail.
> 
>     Does anything show up in there at all?
> 
> Greg, nope, nothing at all shows in either slots or everything.log after a
> hotplug. not a single line in the log file and no files in the /sys/bus/pci/
> slots directory.
>  
> 
> 
>     How about if you load the acpiphp module instead?  Some BIOSes use that
>     instead of pciehp.
> 
> I tried both with pciehp *and* acpiphp.

Odd, one of them should work.  If not, then that's why this isn't
working.

>     You need one of those drivers in order for this to work properly.
> 
>     Also, speaking of BIOS, make sure you have the latest updates, there
>     were a lot of initial problems with Thunderbolt hotplug issues that were
>     fixed in newer BIOS versions, so that will be required to be updated.
> 
> well that might be the problem. In fact, I'm booting EFI directly using the
> 3.3+ kernel direct efi boot feature. Might that be the problem? I though
> booting EFI on an EFI machine was supposed to give you better hardware
> recognition (I am on a macbook air trying to hotplug a thunderbolt display to
> the thunderbolt/displayport connector).
> Anyway, I will try with a more standard (fake) BIOS boot when I get to work.

That "shouldn't" make a difference, but it would be good to find out.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/