#StackBounty: #16.04 #drivers #nvidia #graphics #screen Screen Rendering Issues

Bounty: 50

I have a laptop with a NVIDIA Corporation GM108M [GeForce 940MX] (rev a2) graphics card, using NVIDIA Driver Version: 381.22.

Recently I have been having issues with the screen rendering on all programs. For instance, when typing into a web test box (like this) the characters are not getting displayed until either a delay or losing focus.
Also if I double click on a word (to highlight it) the edges goes blue (to show word is selected) but the middle part under the mouse cursor does not.

As the example below, double click on the word highlight and only the left couple of characters have highlighted, the area under the mouse is uneffected.
enter image description here


Get this bounty!!!

#StackBounty: #linux #drivers #devices #device-tree #mips How to debug a driver failing to bind to a device on Linux?

Bounty: 50

I am trying to figure out why the following device is not setup to its driver on my Creator CI20. For reference I am using a Linux kernel v4.13.0 and doing the compilation locally:

make ARCH=mips ci20_defconfig
make -j8 ARCH=mips CROSS_COMPILE=mipsel-linux-gnu- uImage

From the running system I can see:

ci20@ci20:~# find /sys | grep rng
/sys/firmware/devicetree/base/jz4780-cgu@10000000/rng@d8
/sys/firmware/devicetree/base/jz4780-cgu@10000000/rng@d8/compatible
/sys/firmware/devicetree/base/jz4780-cgu@10000000/rng@d8/name
/sys/bus/platform/drivers/jz4780-rng
/sys/bus/platform/drivers/jz4780-rng/bind
/sys/bus/platform/drivers/jz4780-rng/unbind
/sys/bus/platform/drivers/jz4780-rng/uevent

So the device is seen by the kernel at runtime, now the missing piece is why the driver is never binded ? I would have expected something like this:

/sys/bus/platform/drivers/jz4780-rng/100000d8.rng

I did find some other posts explaining how to debug a running system, such as:

While the information is accurate on those posts, it is not very helpful for me. Since I am building locally my kernel (I added printk in the probe function of jz4780-rng driver), my question is instead:

  • what option should I turn on at compile time so that the kernel prints an accurate information on its failure to call the probe function for the jz4780-rng driver ?
  • In particular how do I print the complete list of the tested bus/driver for driver_probe_device ?

I am ok to add printk anywhere in the code to debug this. The question is rather: which function is traversing the device tree and calling the probe/init function ?

For reference:

$ dtc -I fs -O dts /sys/firmware/devicetree/base | grep -A 1 rng
              rng@d8 {
                      compatible = "ingenic,jz4780-rng";
              };

compatible string is declared as:

cgu: jz4780-cgu@10000000 {
    compatible = "ingenic,jz4780-cgu", "syscon";
    reg = <0x10000000 0x100>;

    clocks = <&ext>, <&rtc>;
    clock-names = "ext", "rtc";

    #clock-cells = <1>;

    rng: rng@d8 {
        compatible = "ingenic,jz4780-rng";
    };
};

And in the driver as:

static const struct of_device_id jz4780_rng_dt_match[] = {
    {
        .compatible = "ingenic,jz4780-rng",
    },
    { },
};
MODULE_DEVICE_TABLE(of, jz4780_rng_dt_match);

static struct platform_driver jz4780_rng_driver = {
    .driver     = {
        .name   = "jz4780-rng",
        .of_match_table = jz4780_rng_dt_match,
    },
    .probe      = jz4780_rng_probe,
    .remove     = jz4780_rng_remove,
};
module_platform_driver(jz4780_rng_driver);

Update1:

When I build my kernel with CONFIG_DEBUG_DRIVER=y, here is what I can see:

# grep driver_probe_device syslog
Sep  6 10:08:07 ci20 kernel: [    0.098280] bus: 'platform': driver_probe_device: matched device 10031000.serial with driver ingenic-uart
Sep  6 10:08:07 ci20 kernel: [    0.098742] bus: 'platform': driver_probe_device: matched device 10033000.serial with driver ingenic-uart
Sep  6 10:08:07 ci20 kernel: [    0.099209] bus: 'platform': driver_probe_device: matched device 10034000.serial with driver ingenic-uart
Sep  6 10:08:07 ci20 kernel: [    0.106945] bus: 'platform': driver_probe_device: matched device 1b000000.nand-controller with driver jz4780-nand
Sep  6 10:08:07 ci20 kernel: [    0.107282] bus: 'platform': driver_probe_device: matched device 134d0000.bch with driver jz4780-bch
Sep  6 10:08:07 ci20 kernel: [    0.107470] bus: 'platform': driver_probe_device: matched device 16000000.dm9000 with driver dm9000
Sep  6 10:08:07 ci20 kernel: [    0.165618] bus: 'platform': driver_probe_device: matched device 10003000.rtc with driver jz4740-rtc
Sep  6 10:08:07 ci20 kernel: [    0.166177] bus: 'platform': driver_probe_device: matched device 10002000.jz4780-watchdog with driver jz4740-wdt
Sep  6 10:08:07 ci20 kernel: [    0.170930] bus: 'platform': driver_probe_device: matched device 1b000000.nand-controller with driver jz4780-nand

But only:

# grep rng syslog
Sep  6 10:08:07 ci20 kernel: [    0.166842] bus: 'platform': add driver jz4780-rng
Sep  6 10:08:42 ci20 kernel: [   54.584451] random: crng init done

As a side note, the rng toplevel node: cgu is not referenced here, but there is a jz4780-cgu driver.


Update2:

If I move the rng node declaration outside the toplevel cgu node, I can at least see some binding happening at last:

# grep rng /var/log/syslog 
Sep  6 10:30:57 ci20 kernel: [    0.167017] bus: 'platform': add driver jz4780-rng
Sep  6 10:30:57 ci20 kernel: [    0.167033] bus: 'platform': driver_probe_device: matched device 10000000.rng with driver jz4780-rng
Sep  6 10:30:57 ci20 kernel: [    0.167038] bus: 'platform': really_probe: probing driver jz4780-rng with device 10000000.rng
Sep  6 10:30:57 ci20 kernel: [    0.167050] jz4780-rng 10000000.rng: no pinctrl handle
Sep  6 10:30:57 ci20 kernel: [    0.167066] devices_kset: Moving 10000000.rng to end of list
Sep  6 10:30:57 ci20 kernel: [    0.172774] jz4780-rng: probe of 10000000.rng failed with error -22
Sep  6 10:31:32 ci20 kernel: [   54.802794] random: crng init done

Using:

    rng: rng@100000d8 {
        compatible = "ingenic,jz4780-rng";
    };

I can also verify:

# find /sys/ | grep rng
/sys/devices/platform/10000000.rng
/sys/devices/platform/10000000.rng/subsystem
/sys/devices/platform/10000000.rng/driver_override
/sys/devices/platform/10000000.rng/modalias
/sys/devices/platform/10000000.rng/uevent
/sys/devices/platform/10000000.rng/of_node
/sys/firmware/devicetree/base/rng@100000d8
/sys/firmware/devicetree/base/rng@100000d8/compatible
/sys/firmware/devicetree/base/rng@100000d8/status
/sys/firmware/devicetree/base/rng@100000d8/reg
/sys/firmware/devicetree/base/rng@100000d8/name
/sys/bus/platform/devices/10000000.rng
/sys/bus/platform/drivers/jz4780-rng
/sys/bus/platform/drivers/jz4780-rng/bind
/sys/bus/platform/drivers/jz4780-rng/unbind
/sys/bus/platform/drivers/jz4780-rng/uevent


Get this bounty!!!

#StackBounty: #drivers #kernel #intel-graphics #fan "Solution" to Intel Graphics Screen Tearing/Flickering Causes Excessive F…

Bounty: 200

Several users (one, two, three, four, five) have reported that Intel graphics cards cause severe screen tearing/flickering on Ubuntu >= 16.10. The oft-proposed “solution” is to add the boot parameter i915.enable_rc6=0.

However, while fixing the screen flickering/tearing, this “solution” causes the fan to run constantly (as in it never, ever turns off) and at an excessively high speed. I am posting this question to see if anyone has a remedy to the fan issue (or, in the alternative, to the flickering/tearing issue but without causing the fan issue).

For completeness, I am running Ubuntu 16.10/17.04/17.10 using kernel 4.11.0-10-generic on a Lenovo 910 (Kabylake) and my graphics card is VGA compatible controller: Intel Corporation Device 5916 (rev 02).

Note: I just confirmed that this problem still exists with the upstream kernel (v4.13.0-041300rc4). Reverting the kernel to the 16.04 LTS kernel fixes the screen tearing, but that is just a workaround. I recently (09.03.2017) tried the default Debian install with kernel 4.9.0-3-amd64, and there is no screen flickering (though the screen is rotated 90 degrees).

Note 2: Using the boot parameter i915.enable_rc6=0 leads to system degredation over extended use. I tried to watch a streaming video for 3 hours and the machine starting acting sluggish and unresponsive.

Note 3: I filed a bug report.


Get this bounty!!!

#StackBounty: #drivers #sound #pulseaudio #speakers How to fix Bang and Olufsen Audio for HP laptops?

Bounty: 500

I’m trying to install bang and olufsen drivers, or HP hd audio driver, as only 2 of the 4 speakers work and the 2 amps don’t work in ubuntu

lspci -v | grep -i audio
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
    Subsystem: Hewlett-Packard Company Broadwell-U Audio Controller
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)
    Subsystem: Hewlett-Packard Company Wildcat Point-LP High Definition Audio Controller

The volume is terrible. Is there any way to fix this?

The speakers work perfectly on the pre-installed Windows 8.


Get this bounty!!!

#StackBounty: #drivers #usb #dell #17.04 #xps Getting Dell DA100 adapter working on Dell XPS 13 9360 running Ubuntu 17.04

Bounty: 50

I recently bought a Dell XPS13 9360 with Ubuntu (with Unity) 16.04. I also bought a DA100 USB3 (ethernet, USB and video) adapter.

While running 16.04 the adapter worked fine. When I upgraded to 17.04 (probably not “officially supported” but…) the adapter stopped working.

Dell have released an update to driver for the DA100, but unhelpfully they are only in “Windows OS” format.

I’ve tried using the updated drivers from Displaylink, but they have not worked.

I’ve taken a output of usb-devices before, and after installing the drivers. I’ve also dumped the driver install outputs.

They’re all available in the logfiles in this Dropbox share.

  1. usb-devices-probe-before-install-drivers.log
  2. install-da100-drivers.log
  3. usb-devices-probe-after-install-drivers.log

Has anyone gotten the Dell DA100 adapter working on a XPS 13 9360 running Ubuntu 17.04 Gnome 3?


Get this bounty!!!

#StackBounty: #windows-10 #audio #drivers #asus-laptop #realtek No Audio output devices is installed in ASUS IN SEARCH INCREDIBLE A555L…

Bounty: 50

enter image description here

Asus in search in incredible A555L i installed audio drivers but not working . I tried allot but i cant find solution. i given to asus service center they are solved issue but its worked only one day again audio drivers is gone.I struggled allot would you please anyone help me..i’ll appreciate them

Device Manager
enter image description here

But if i restart my laptop sometimes its working audio drivers and some times not working i don’t understand what is the issue .. i’m getting mad with this…. audio drivers

enter image description here


Get this bounty!!!

#StackBounty: #windows-10 #audio #drivers #asus-laptop #realtek No Audio output devices is installed in asus windows 10

Bounty: 50

enter image description here

Asus in search in incredible A555L i installed audio drivers but not working . i tried allot but i cant find solution. i gave to asus service centre its worked only one day agian audio drivers gone. i struggled allot would you please anyone help me..i’ll appreciate

Device Manager
enter image description here

But if i restart my laptop sometimes its working audio drivers and some times not working i don’t understand what is the issue .. i’m getting mad with this…. audio drivers

enter image description here


Get this bounty!!!

#StackBounty: #drivers #usb #gamepad Antimicro not detecting Controller input after install RetroPi

Bounty: 50

Antimicro was working fine until after I install RetroPi. It can detect there’s a controller, but it can’t detect the controller input. I’ve tried on both a USB flight stick and a xbox one s controller. The controllers work with other games and programs including JSTest but not antimicro.

squirel@TREEPC:~$ sudo antimicro 
"sni-qt/10081" WARN  12:24:00.455 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE 
Virtual pointer found with id=4.
Changing mouse acceleration for device with id=4
Using XTest as the event generator.

squirel@TREEPC:~$ lsusb 
Bus 002 Device 005: ID 0955:cf08 NVidia Corp. SHIELD Tablet
Bus 002 Device 006: ID 045e:02ea Microsoft Corp. 
Bus 002 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 001 Device 003: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


Get this bounty!!!

#StackBounty: #drivers #kernel #brightness ddccontrol is not working, but it used to work

Bounty: 100

I want to change my monitor (Dell S2216H) brightness with commands

ddccontrol -p -r 0x10 -w 53

This command used to work on 16.10 now it doesn’t, but gives this output

robing for available monitors.......
Detected monitors :
No monitor supporting DDC/CI available.
If your graphics card need it, please check all the required kernel 
modules are loaded (i2c-dev, and your framebuffer driver).

Output of ddccontrol -p is same

ddccontrol version 0.4.2
Copyright 2004-2005 Oleg I. Vdovikin (oleg@cs.msu.su)
Copyright 2004-2006 Nicolas Boichat (nicolas@boichat.ch)
This program comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of this program under the terms of the GNU General Public License.

Probing for available monitors.......
Detected monitors :
No monitor supporting DDC/CI available.
If your graphics card need it, please check all the required kernel 
modules are loaded (i2c-dev, and your framebuffer driver).

Output of i2cdetect -l

i2c-3   unknown     i915 gmbus dpc                      N/A
i2c-1   unknown     i915 gmbus vga                      N/A
i2c-6   unknown     DPDDC-D                             N/A
i2c-4   unknown     i915 gmbus dpb                      N/A
i2c-2   unknown     i915 gmbus panel                    N/A
i2c-0   unknown     i915 gmbus ssc                      N/A
i2c-5   unknown     i915 gmbus dpd                      N/A

Here is the output of ddcontrol -p when it used to work at pastebin

It stopped working while I was doing this process described by Jacob Vlijm, But after that I’ve gone through multiple fresh installs but It never worked, the only thing that seems to be different now is I’m running 17.04 but I distinctly remember it working on 16.10 and then failing on fresh installs of 16.10


More info

I2C dev interface – The Linux Kernel Archives

Linux Framebuffer Drivers

What are DPDDC-B/C i2c devices?


Ultimately I’m trying to achieve this but ddccontrol needs to work for that


Get this bounty!!!

#StackBounty: #16.04 #drivers #sound Sound stopped working after upgrading from 14.04 to 16.04

Bounty: 50

My notebook is a Dell Inspiron 15 Gaming. My Ubuntu’s version is xenial.

After upgrading from Ubuntu 14.04 to 16.04; the computer could not detect the sound card anymore… Also, alsamixer was not working neither…

I tried to do somethings: reinstall alsa utils; installed some drivers manually (oem-audio-hda-daily-Its-xenial-dkms).

Now the sound card is detected, the alsamixer works, when the computer starts it makes the initialization sound, but after I login there is no more sound…

When I open the sound configurations menu; there is nothing to choose as ‘sound output’, before, when the sound card was not detected, there was the option ‘dummy output’.

I really don’t know what to do anymore, it’s the first time I am trying to use Linux in my PC, so I don’t understand half of what people say in the forums where I am searching for an answer…


Get this bounty!!!