Could anyone advise me if there are any serious problems with this hardware and F18 ?
On Mar 14, 2013 10:58 PM, "dave peters" dpetlinux@gmail.com wrote:
Could anyone advise me if there are any serious problems with this
hardware and F18 ?
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Which hardware?
On Mar 15, 2013 7:41 AM, "Richard Vickery" richard.vickeryrv@gmail.com wrote:
On Mar 14, 2013 10:58 PM, "dave peters" dpetlinux@gmail.com wrote:
Could anyone advise me if there are any serious problems with this
hardware and F18 ?
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Which hardware?
Sorry. I suppose you meant the Dell xps 13; just trying to clarify in case one who knows doesn't reply... an attempt at being helpful.
On 03/14/2013 10:58 PM, dave peters wrote:
Could anyone advise me if there are any serious problems with this hardware and F18 ?
I received an XPS 13 yesterday!
So far, I haven't seen any problems from it. Intel's video is quite standard, and works as expected. WiFi is working. I've set up a few VMs under Linux KVM with virt-manager. Media keys all work properly, as does the OSD. The touchpad works as expected. I got around 6 hours of battery life from it yesterday under use that included periods of heavy activity (including the CPU, disk and WiFi access required to install multiple server VMs on an encrypted volume group). I haven't tried to use the DisplayPort output or BlueTooth, but the latter is at least correctly detected on boot.
On 03/15/2013 09:08 AM, Gordon Messmer wrote:
I haven't tried to use the DisplayPort output or BlueTooth, but the latter is at least correctly detected on boot.
I've learned that btusb needs to be removed on suspend. The following script will accomplish that.
/usr/lib/systemd/system-sleep/bluetooth.sh:
#!/bin/sh
case $1 in pre) echo "Removing module btusb..." rmmod btusb ;; post) echo "Re-loading module btusb..." modprobe btusb ;; esac