FedoraForum.org - Fedora Support Forums and Community
Results 1 to 6 of 6
  1. #1
    Join Date
    Sep 2017
    Location
    United Kingdom
    Posts
    3

    USB C not working on new laptop, Fedora 26

    Hi, I just installed Fedora 26 on my new laptop. Everything works except the USB C port, which appears not to register at all. (The USB C device I am trying works fine on another computer).

    How can I check if this is some setup or driver issue that I just need to re-set? Or how can I verify it is definitely a hardware error?

    The laptop is a PC Specialist lafite iii, built to custom spec and supposed to be fully tested, so I don't think I should immediately assume this is a hardware error. Though of course it might be.
    https://www.pcspecialist.co.uk/notebooks/lafiteIII/

    Thanks in advance.

  2. #2
    Join Date
    Apr 2016
    Location
    Kota Tinggi, Johor, Malaysia
    Age
    21
    Posts
    163

    Re: USB C not working on new laptop, Fedora 26

    $ dmesg

    is a nice place to start with...

    $ journalctl -f

    when you try testing plugging and unplugging usb c...
    Laptop Specs
    https://forums.fedoraforum.org/showpost.php?p=1760122&postcount=528

  3. #3
    Join Date
    Sep 2017
    Location
    United Kingdom
    Posts
    3

    Re: USB C not working on new laptop, Fedora 26

    Thanks so much.

    Output of dmesg (not altered by plugging and unplugging the usb c)
    https://www.dropbox.com/s/5o58j264jqau09a/help.txt?dl=0

    Output of journalctl -f
    (I plug in the usb c at about 17:03 and unplug it at 17:08. This firefox window in which I am typing now seems to be misbehaving... might my usb c device be wlp59s0?)

    Code:
    Sep 09 17:03:01 lumen sudo[30380]: pam_unix(sudo:session): session closed for user root
    Sep 09 17:03:01 lumen audit[30380]: USER_END pid=30380 uid=0 auid=1000 ses=13 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
    Sep 09 17:03:01 lumen audit[30380]: CRED_DISP pid=30380 uid=0 auid=1000 ses=13 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_env,pam_fprintd acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
    Sep 09 17:03:14 lumen org.gnome.Shell.desktop[15600]: Window manager warning: last_user_time (121089367) is greater than comparison timestamp (121089366).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
    Sep 09 17:03:14 lumen org.gnome.Shell.desktop[15600]: Window manager warning: 0x2c00003 (.bashrc - ) appears to be one of the offending windows with a timestamp of 121089367.  Working around...
    Sep 09 17:03:14 lumen systemd[1]: Starting dnf makecache...
    Sep 09 17:03:15 lumen dnf[30468]: Metadata cache refreshed recently.
    Sep 09 17:03:15 lumen systemd[1]: Started dnf makecache.
    Sep 09 17:03:15 lumen audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-makecache comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
    Sep 09 17:03:15 lumen audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-makecache comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
    Sep 09 17:04:28 lumen org.gnome.Shell.desktop[15600]: Window manager warning: last_user_time (121163023) is greater than comparison timestamp (121162999).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
    Sep 09 17:04:28 lumen org.gnome.Shell.desktop[15600]: Window manager warning: 0x2400010 (USB C not ) appears to be one of the offending windows with a timestamp of 121163023.  Working around...
    Sep 09 17:04:28 lumen org.gnome.Shell.desktop[15600]: Window manager warning: last_user_time (121163357) is greater than comparison timestamp (121163338).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
    Sep 09 17:04:28 lumen org.gnome.Shell.desktop[15600]: Window manager warning: 0x2400010 (USB C not ) appears to be one of the offending windows with a timestamp of 121163357.  Working around...
    Sep 09 17:04:28 lumen org.gnome.Shell.desktop[15600]: Window manager warning: last_user_time (121163387) is greater than comparison timestamp (121163368).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
    Sep 09 17:04:28 lumen org.gnome.Shell.desktop[15600]: Window manager warning: 0x2400010 (USB C not ) appears to be one of the offending windows with a timestamp of 121163387.  Working around...
    Sep 09 17:04:29 lumen org.gnome.Shell.desktop[15600]: Window manager warning: last_user_time (121163507) is greater than comparison timestamp (121163495).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
    Sep 09 17:04:29 lumen org.gnome.Shell.desktop[15600]: Window manager warning: 0x2400010 (USB C not ) appears to be one of the offending windows with a timestamp of 121163507.  Working around...
    Sep 09 17:04:29 lumen org.gnome.Shell.desktop[15600]: Window manager warning: last_user_time (121163537) is greater than comparison timestamp (121163526).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
    Sep 09 17:04:29 lumen org.gnome.Shell.desktop[15600]: Window manager warning: 0x2400010 (USB C not ) appears to be one of the offending windows with a timestamp of 121163537.  Working around...
    Sep 09 17:04:29 lumen org.gnome.Shell.desktop[15600]: Window manager warning: last_user_time (121163567) is greater than comparison timestamp (121163557).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
    Sep 09 17:04:29 lumen org.gnome.Shell.desktop[15600]: Window manager warning: 0x2400010 (USB C not ) appears to be one of the offending windows with a timestamp of 121163567.  Working around...
    Sep 09 17:04:29 lumen org.gnome.Shell.desktop[15600]: Window manager warning: last_user_time (121163627) is greater than comparison timestamp (121163617).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
    Sep 09 17:04:29 lumen org.gnome.Shell.desktop[15600]: Window manager warning: 0x2400010 (USB C not ) appears to be one of the offending windows with a timestamp of 121163627.  Working around...
    Sep 09 17:04:29 lumen org.gnome.Shell.desktop[15600]: Window manager warning: last_user_time (121163657) is greater than comparison timestamp (121163647).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
    Sep 09 17:04:29 lumen org.gnome.Shell.desktop[15600]: Window manager warning: 0x2400010 (USB C not ) appears to be one of the offending windows with a timestamp of 121163657.  Working around...
    Sep 09 17:04:38 lumen org.gnome.Shell.desktop[15600]: Window manager warning: last_user_time (121173095) is greater than comparison timestamp (121173073).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
    Sep 09 17:04:38 lumen org.gnome.Shell.desktop[15600]: Window manager warning: 0x2400010 (USB C not ) appears to be one of the offending windows with a timestamp of 121173095.  Working around...
    Sep 09 17:04:53 lumen NetworkManager[1278]: <info>  [1504973093.6072] device (wlp59s0): set-hw-addr: set MAC address to 2A:B8:55:73:3B:96 (scanning)
    Sep 09 17:04:53 lumen kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
    Sep 09 17:04:53 lumen NetworkManager[1278]: <info>  [1504973093.6392] device (wlp59s0): supplicant interface state: scanning -> disabled
    Sep 09 17:04:53 lumen NetworkManager[1278]: <info>  [1504973093.6409] device (wlp59s0): supplicant interface state: disabled -> inactive
    Sep 09 17:04:53 lumen wpa_supplicant[1384]: wlp59s0: Reject scan trigger since one is already pending
    Sep 09 17:05:45 lumen kernel: psmouse serio2: TouchPad at isa0060/serio2/input0 lost synchronization, throwing 4 bytes away.
    Sep 09 17:07:00 lumen NetworkManager[1278]: <info>  [1504973220.8393] device (wlp59s0): supplicant interface state: inactive -> scanning
    
    Sep 09 17:08:32 lumen kernel: psmouse serio2: TouchPad at isa0060/serio2/input0 lost synchronization, throwing 4 bytes away.
    Sep 09 17:08:45 lumen org.gnome.Shell.desktop[15600]: Window manager warning: last_user_time (121419629) is greater than comparison timestamp (121419617).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
    Sep 09 17:08:45 lumen org.gnome.Shell.desktop[15600]: Window manager warning: 0x2400010 (USB C not ) appears to be one of the offending windows with a timestamp of 121419629.  Working around...
    Sep 09 17:09:18 lumen kernel: psmouse serio2: TouchPad at isa0060/serio2/input0 lost synchronization, throwing 4 bytes away.
    Sep 09 17:09:33 lumen kernel: psmouse serio2: TouchPad at isa0060/serio2/input0 lost synchronization, throwing 5 bytes away.

  4. #4
    Join Date
    Apr 2016
    Location
    Kota Tinggi, Johor, Malaysia
    Age
    21
    Posts
    163

    Re: USB C not working on new laptop, Fedora 26

    not exactly, wlp59s0 is probably your wifi, could be what affecting your firefox...

    well I am no expert in debugging info, I can try guide you huhu /.\ but I dont have usb c hardware...
    looking through dmesg feels like dont reveal much and journalctl looks irrelevant, even though there's usb c there...
    maybe Fedora is not detecting any usb c...

    journalctl alone w/o option is probably not a good idea, it combines all the logs,
    we need to filter it, kernel related is what we looking for

    try testing plug and unplug with,
    Code:
    $ journalctl -f -k
    (Fedora doesn't have /var/log/kern.log if you Google for solutions, mostly ubuntu, opensuse related)
    https://askubuntu.com/questions/7141...ctors-on-15-10
    https://bugzilla.opensuse.org/show_bug.cgi?id=973138

    before and after plugging,
    Code:
    $ lsusb
    Last edited by TruboXL; 10th September 2017 at 06:12 AM. Reason: formatting
    Laptop Specs
    https://forums.fedoraforum.org/showpost.php?p=1760122&postcount=528

  5. #5
    Join Date
    Sep 2017
    Location
    United Kingdom
    Posts
    3

    Re: USB C not working on new laptop, Fedora 26

    Thanks for all your help. Someone else suggested I simply see whether the usb c device, which draws power, was getting any power in the boot or BIOS menus. It isn't. However, it does get power (ie the little light comes on) if it is plugged into the usb 2 ports, or if it is plugged into the usb c port of the other laptop which has a working usb c port and happens to have the same usb driver.

    We are concluding hardware / BIOS problem, this can't be Fedora's fault. We cannot find anything about the usb in the BIOS. So back to the shop it goes.

    Anyway, yes, thanks.

  6. #6
    Join Date
    Dec 2013
    Location
    United Kingdom
    Posts
    5,240

    Re: USB C not working on new laptop, Fedora 26

    have you tried the following command to see if USB C is supported by the kernel
    Code:
    lspci -d ::0c03 -k
    I'd be tempted to try an F27 nightly before giving up on the hardware. you can get a live bootable ISO from here. reason being, it will have the new 4.13 branch kernels as opposed to 4.12 branch.

Similar Threads

  1. laptop tuchpad is not working well with fedora
    By randyorton in forum Hardware & Laptops
    Replies: 7
    Last Post: 18th October 2011, 04:09 AM
  2. Bluetooth is not working on Fedora 10 cambridge Laptop
    By dipanchandra in forum Hardware & Laptops
    Replies: 10
    Last Post: 14th October 2010, 04:28 PM
  3. Fedora 12 Laptop Touchpad Stopped Working
    By ole_ersoy in forum Hardware & Laptops
    Replies: 2
    Last Post: 6th March 2010, 08:53 PM
  4. Laptop function keys not working with Fedora 8
    By exsencon in forum Hardware & Laptops
    Replies: 19
    Last Post: 25th February 2008, 12:50 PM
  5. ASUS A1 laptop + Fedora 4 = non stop working fan
    By linuxben in forum Hardware & Laptops
    Replies: 0
    Last Post: 12th August 2005, 12:48 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •