Lenovo W540 so far

[Adrian Chadd]

Hi!

Would you be willing to write up a wiki page for this?

http://wiki.freebsd.org/Laptops

That way we have a lit of what laptops are known to work and what the
limitations are.

It'd also be nice to add those lines to a wiki page somewhere so we
don't forget the magic.

Thanks!


-a



On 15 June 2014 07:01, Eric McCorkle <eric at metricspace.net> wrote:
> Hello all,
>
> I recently purchased a Lenovo W540 mobile workstation.  Most of the hardware
> works, though there are a few issues.  Here is a breakdown of my setup, what
> works, and what doesn't.
>
>
> Basic Installation:  I set up a GPT/ZFS-only scheme.  The laptop comes
> pre-configured for booting UEFI-only, but it supports a legacy BIOS boot
> mode.  Setting up ZFS went smoothly with little trouble.
>
> The laptop also came with a 16 GB flash drive, which I used as a swap
> device.  It could also be used as an L2ARC for ZFS.
>
> I also ran into some build errors when trying to build world, that seemed to
> be caused by a version mismatch between the clang-tblgen binary in the 10
> installer and the .tbl files in head.
>
>
> ACPI: Suspend/resume works without incident, both in terminal mode and in X.
> The following error messages get printed:
>
> pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.PEG_:
> AE_BAD_PARAMETER
> pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP1:
> AE_BAD_PARAMETER
> pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP2:
> AE_BAD_PARAMETER
> pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP3:
> AE_BAD_PARAMETER
> pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP5:
> AE_BAD_PARAMETER
>
> This doesn't seem to affect anything, though.
>
> A similar error occurs when trying to use the nvidia driver.  However, these
> errors do seem to prevent the driver from working:
>
> ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch -
> Found [Buffer], APCI requires [Package] (20130823/nsarguments-97)
> (the same message gets repeated about 10 times)
>
>
> Xorg: As previously mentioned, the nvidia driver is non-functional.  The nv
> driver does not seem to support the on-board card (Quadro K1100). The vesa
> driver works though.
>
> I'm using enlightenment 17.  I haven't done anything fancy with it yet,
> though.
>
>
> USB: USB 1.0 and 2.0 seem to work.  USB 3.0 has problems.
>
> The messages for xhci are:
>
> xhci0: <Intel Lynx Point USB 3.0 Controller> mem 0xb2a20000-b2a2ffff irq 16
> at device 3.0 on pci0
> xhci0: 32 byte context size
> xhci0: Port routing mask set to 0xffffffff
> ...
> xhci0: Port routing mask set to 0x00000000
> usb_alloc_device: device init 2 failed (USB_ERR_IOERROR, ignored)
>
>
> A bit of looking around seemed to reveal that there's known issues with the
> Lynx Point controller.  I don't know much about the USB system, so not sure
> what to do here.
>
>
> Mouse: Trackpad and trackpoint work, though Synaptics does not seem to be
> supported (at the kernel driver level).  If I'm not mistaken, the touchpad
> is a multitouch touchpad, so maybe I will look into why it's not supported.
>
> The touchpad is a bit sensitive, though, and an accidental palm touch can
> register as a click.
>
> Sound: Sound card gets detected, seems to work, though I haven't done
> anything serious with it yet.  Also experimenting a bit with setting up rc
> scripts to start audio servers like Jack and Pulseaudio and run them as
> system-wide processes
>
>
> Network: Ethernet works fine, Intel 7260AC chipset is not supported for
> wireless :(
>
>
> Questions/suggestions/advice are welcome.
>
> Eric
> _______________________________________________
> freebsd-mobile at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
> To unsubscribe, send any mail to "freebsd-mobile-unsubscribe at freebsd.org"