Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: ASUS: keyboard issue

  1. #1

    Default ASUS: keyboard issue

    Hi guys,

    I bought ASUS VivoBook Pro 15 with Intel Core i5-7300HQ processor, NVIDIA GeForce GTX 1050 + Intel HD Graphics 630 graphic cards and Intel HM175 chipset. For years I use openSUSE with KDE but knowing the problem with hanging I decided to install the system with GNOME. Everything works correctly besides some keyboard functions. Firstly I noticed that combination of Fn + F1-F9 doesn't work. I can't change either brightness of keyboard nor display, although I can do this using graphical sliders. Secondly I can mute/decrease/increase volume using combinations of Fn + F10-12 and sliders too. I read a lot of topics but any method didn't solve my problem (for example I edited /etc/default/grub file to change grub2 configuration).

    I decided to leave this issue away, but I started to configure my new notebook and I installed geany. And there is another problem with some key combinations. For example I can't use Ctrl+Scroll to zoom in/out a text content. It works on my old notebook with KDE. Moreover, it works on the new machine with Firefox or Terminator (alternative to terminal). So I suppose that the issue is related to ACPI, but is hard to fix.

    My questions are: how to fix this? If I see a lot of topics which report the keyboard issue with notebooks, why there is no update to improve the openSUSE code?

  2. #2
    Join Date
    Oct 2014
    Location
    Italy
    Posts
    1,674

    Default Re: ASUS: keyboard issue

    Hi, I had similar problems with ASUS notebooks with Leap 42.x and I solved them by adding "acpi_osi= " (including the trailing blank and excluding quotes) to the GRUB boot line.
    But I noticed that a fresh LEAP 15 install does no more need that trick, everything working as expected (till now, at least ).
    So the openSUSE code was indeed improved, maybe not to a point to include your HW or BIOS.
    Main: Leap 15 Gnome on i7 4720HQ + Geforce GTX960M
    Test: Leap 42.3 (& others) on Core2Duo + GM965

  3. #3
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,670
    Blog Entries
    15

    Default Re: ASUS: keyboard issue

    Hi
    I had the same issue a while back along with the acpi_osi trick on a HP system (acpi_osi=\"!Windows 2012\"), a bug report and hwinfo and dmidecode output attached resulted in a fix...

    @OP, since it's a new system, suggest a bug report with attached hwinfo and dmidecode output should enable a fix to be propagated....

    openSUSE:Submitting bug reports - openSUSE
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  4. #4
    Join Date
    Oct 2008
    Location
    Glasgow, Scotland
    Posts
    1,131

    Default Re: ASUS: keyboard issue

    Quote Originally Posted by Benek View Post
    Hi guys,

    I bought ASUS VivoBook Pro 15 ...
    It is worth checking that you have the latest BIOS firmware (version 315)
    Code:
     # hwinfo --bios
    http://dlcdnet.asus.com/pub/ASUS/nb/...580VDAS315.zip
    ~Thank you for sharing an interesting problem.
    --
    slàinte mhath,
    rayH

  5. #5

    Default Re: ASUS: keyboard issue

    I tried both options and they didn't help. I also installed KDE and Ctrl+Scroll has an effect on zoom in geany, but Fn + key combinations behave as on GNOME. I came back to Gnome.

    Code:
    hwinfo --bios
    
    01: None 00.0: 10105 BIOS                                       
      [Created at bios.186]
      Unique ID: rdCR.lZF+r4EgHp4
      Hardware Class: bios
      BIOS Keyboard LED Status:
        Scroll Lock: off
        Num Lock: off
        Caps Lock: off
      Config Status: cfg=no, avail=yes, need=no, active=unknown
    What kind of information from hwinfo or dmidecode do you need? Unfortunately, I never did a BIOS update and I read that it could make irreversible changes on a machine. I can still return the notebook to the store within one week.

  6. #6
    Join Date
    Oct 2014
    Location
    Italy
    Posts
    1,674

    Default Re: ASUS: keyboard issue

    Quote Originally Posted by Benek View Post
    What kind of information from hwinfo or dmidecode do you need?
    The BIOS version should show something like:
    Code:
    # hwinfo --bios
    01: None 00.0: 10105 BIOS                                       
      [Created at bios.186]
      Unique ID: rdCR.lZF+r4EgHp4
      Hardware Class: bios
      BIOS Keyboard LED Status:
        Scroll Lock: off
        Num Lock: off
        Caps Lock: off
      SMBIOS Version: 2.7
      BIOS Info: #0
        Vendor: "American Megatrends Inc."
        Version: "N551JW.209"
        Date: "03/04/2016"
    You may also test that the kernel modules wmi, asus_wmi and asus_nb_wmi are loaded:
    Code:
    # lsmod |grep wmi
    If not so, you might try to load them manually and see what happens.
    Main: Leap 15 Gnome on i7 4720HQ + Geforce GTX960M
    Test: Leap 42.3 (& others) on Core2Duo + GM965

  7. #7
    Join Date
    Oct 2008
    Location
    Glasgow, Scotland
    Posts
    1,131

    Default Re: ASUS: keyboard issue

    Quote Originally Posted by Benek View Post
    What kind of information from hwinfo
    On my laptop (a Lenovo) “hw-nco --boot” produces 456 lines of output, including:
    Code:
    BIOS Info: #0
        Vendor: "LENOVO"
        Version: "A6CN58WW"
        Date: "08/06/2015"
    I do not understand why you do not have something similar.

    You should be able to boot into the BIOS and read the version number from the status page.
    ~Thank you for sharing an interesting problem.
    --
    slàinte mhath,
    rayH

  8. #8

    Default Re: ASUS: keyboard issue

    Sorry guys, my fault. I triggered hwinfo as normal user, not root.
    Code:
      SMBIOS Version: 3.0
      BIOS Info: #0
        Vendor: "American Megatrends Inc."
        Version: "X580VD.308"
        Date: "10/20/2017"
    Code:
    asus_nb_wmi            28672  0
    asus_wmi               32768  1 asus_nb_wmi
    sparse_keymap          16384  1 asus_wmi
    rfkill                 28672  9 asus_wmi,bluetooth,cfg80211
    mxm_wmi                16384  1 nouveau
    video                  45056  3 asus_wmi,nouveau,i915
    wmi                    16384  3 asus_wmi,mxm_wmi,nouveau

  9. #9
    Join Date
    Oct 2008
    Location
    Glasgow, Scotland
    Posts
    1,131

    Default Re: ASUS: keyboard issue

    Quote Originally Posted by Benek View Post
    Code:
      BIOS Info: #0
        Vendor: "American Megatrends Inc."
        Version: "X580VD.308"
        Date: "10/20/2017"
    So you have version 308 and Asus have published version 315 on 2018/04/16, unfortunately without a meaningful change log.
    ~Thank you for sharing an interesting problem.
    --
    slàinte mhath,
    rayH

  10. #10
    Join Date
    Oct 2014
    Location
    Italy
    Posts
    1,674

    Default Re: ASUS: keyboard issue

    Let me recap my understanding.
    1- The keyboard layout is the same as the one that works for me currently, it seems a "standard ASUS" layout, no fancy keys;
    2- all needed wmi modules are loaded;
    3- your BIOS is not up to date, but mine is 1 yr older and works out of the box with Leap 15.

    My guess is that there is nothing wrong with the laptop (no need to give it back to the store) and that simply that model is too new for Linux to recognize its quirks out of the box.
    I guess also that playing with the many odd acpi_osi= options might find one that works for you, or reporting a bug as Malcolm suggested in post #3 might trigger a fix for that model sooner rather than later.
    I'll come back if I find something useful over the net.
    Main: Leap 15 Gnome on i7 4720HQ + Geforce GTX960M
    Test: Leap 42.3 (& others) on Core2Duo + GM965

Page 1 of 2 12 LastLast

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
  •