From owner-freebsd-x11@freebsd.org Sun Jan 7 21:40:13 2018 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 732EFE5F980; Sun, 7 Jan 2018 21:40:13 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5AD7D7A22F; Sun, 7 Jan 2018 21:40:13 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w07Le9HZ018602; Sun, 7 Jan 2018 13:40:09 -0800 (PST) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w07Le9xS018601; Sun, 7 Jan 2018 13:40:09 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201801072140.w07Le9xS018601@pdx.rh.CN85.dnsmgr.net> Subject: Re: Running FreeBSD on the Lenovo Thinkpad T470s (success) In-Reply-To: <813101D7-3A67-4C4E-8F3C-301B0AE7A550@grem.de> To: Michael Gmelin Date: Sun, 7 Jan 2018 13:40:09 -0800 (PST) CC: clutton , "freebsd-current@freebsd.org" , "freebsd-x11@freebsd.org" , "freebsd-mobile@freebsd.org" X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2018 21:40:13 -0000 > > > On 7. Jan 2018, at 21:32, Rodney W. Grimes wrote: > > >> > >> > >>>> On 7. Jan 2018, at 20:43, clutton wrote: > >>>> > >>>> On Sat, 2017-12-30 at 15:58 +0100, Michael Gmelin wrote: > >>>> Hi, > >>> > >>> Running carbon 5th gen I can't call my setup a success. Wireless iwm > >>> doesn't support even N and AC is not supported at all. The wifi is much > >>> slower then on my old machines. I'm going to replace the wifi card in > >>> mean time, any suggestions which one to buy? > >>> > >>> Graphics works perfectly. NVMe SSD with OPAL wouldn't allow machine to > >>> resume from sleep, sometimes it does after big timeout and writing > >>> errors to console, sometime it just reboots. > >>> > >>> Thinkpad Thunderbolt Dock Station, here is where things get > >>> interesting. If I boot machine connected to dock station, peripheral > >>> devices would work, external monitor, keyboard, and mouse. There's no > >>> other way I know to make it work. Once detached - it wouldn't see > >>> devices again. Booting and THEN attaching - the same, machine wouldn't > >>> see devices. > >>> > >>> Here is the device being seen (a lot of pcib*): > >>> pcib5@pci0:6:0:0: class=0x060400 card=0x11112222 chip=0x15d38086 > >>> rev=0x02 hdr=0x01 > >>> vendor = 'Intel Corporation' > >>> device = 'JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge > >>> 4C 2016]' > >>> class = bridge > >>> subclass = PCI-PCI > >>> > >>> > >>> For me the main concern is Thunderbolt thought, docking station is > >>> amazing thing. Any ideas and thought how to make it work would be > >>> highly appreciated. > >> > >> In my setup, plug/unplug events for display port don't work when docking (usually I'm not using a dock though). This means: Mouse, Keyboard can be plugged/unplugged as many time as I want at any point, while displays connected over display port only work when connected before starting X (and they don't disappear after disconnecting). Note that stopping X seems to fix this (so no reboot required), but I don't have the docking station myself (this is the Ultra Dock Pro or something - the one that connects at the bottom of the laptop). > >> > >> Also, in my setup wifi didn't work without adding iwm0 explicitly to cloned interfaces (which isn't something I wouldn't expect I have to do, but in this case I had to). > > > > Did you have a > > wlans_iwm0="wlan0" > > in /etc/rc.conf? > > I do not know or see why putting iwm0 in cloned would do much of anything > > for a wlan device. > > > > Also note that is wlans as in plural, not wlan_iwm0. A mistake I > > often make from finger memory. > > > > I have > > wlans_iwm0="wlan0" > ifconfig_wlan0="WPA DHCP country de" I use just simply: ifconfig_wlan0="WPA SYNCDHCP" I think without the SYNC you are not waiting for wpa to come up? I do not know of the /etc/rc.d/* stuff is prepared to deal with your "country de" either. > > in rc.conf. Without adding > > cloned_interfaces="iwm0" > > wlan0 never shows up in ifconfig and wpa_supplicant never starts (that's current r326912, setup like described in my blog post). > > I just double checked to confirm the behavior. Something is broken some place. > Best, > Michael -- Rod Grimes rgrimes@freebsd.org