It’s probably you’ll have to tuning several things in Ubuntu 15/16 if you are an owner of a laptop ASUS X series.
If yo get this error on syslog and/or by stderr (a lot of records by second):
printk messages dropped pcieport 0000:1c.5 Receiver Error pcieport 0000:00:1c.5 PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
add pci=nomsi to the /etc/default/grub file:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nomsi"
Also you’ll want control brightness via system keys, if don’t work, try adding acpi_osi=, acpi_backlight=native and intel_idle.max_cstate=1 to the /etc/default/grub file too:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nomsi acpi_osi= acpi_backlight=native intel_idle.max_cstate=1"
Now make an update-grub:
~ $ sudo update-grub
At last, if you experiment disconnections on wireless mode check if your wlan driver is rtl8723be:
~ $ lspci | grep -i wireless 03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter
If yes create a configuration file en /etc/modprobe.d:
~ $ sudo touch /etc/modprobe.d/rtl8723be.conf
And add this:
~ $ sudo echo 'options rtl8723be fwlps=0' > /etc/modprobe.d/rtl8723be.conf
Finally reboot:
~ $ sudo reboot
My first evening with a new Asus laptop away from home was a problem for me. I had one DVD with me to install Ubuntu on a new ssd and it did not work. My extra tools were back home out of reach.
Now months later I’m still batting my head against the wall with this laptop. I finally found the latest driver reported to be certified for Linux and your “Tuning ubuntu on Asus X series” posting on the web. Version 17.04 has not been very useful on this system and I finally gave up thinking it just may have had problems so 17.10 may have cleaned it up a bit.
It did load quicker and some of the slow screen changes were gone as long as I stayed away from Unity. I moved slowly and made just one change at a time. First by adding “pci=nomsi” to the grub file. Your instructions on how to do it worked just fine. Then I loaded the new driver NVIDIA 390.25. That ended all the trash that came across the screen after log off. The first time it took over 20 hours before I held the power button down.
Then I went back to modify the grub file for the screen brightness keys. However following your directions like before would not work. After “sudo -i” followed by my PW then “gedit and then “/etc/default/grub” and enter I received a message about a missing protocol. I’m thinking what in the world would an editing program need a protocol for?
Then I wondered if the driver loaded correctly so I tried “sudo lshw” to verify that it was there and it would not work. About 5 or 6 letters flashed on the screen then screen printing quit. I waited and waited.
Internet browsing seems to be OK. A few small documents in Libre Office Writer were completed without problems. I was surprised when it discovered my printer and attached it for me and printed well.
I still need to manually turn the power off after logging off. And I still have error messages:
watchdog bug soft lockup cpu #6 stuck for 22s! K work[6:1:73]
info rcu sched detected expedited stalls on cpus / tasks: xxxxx 150962 jiffies s: 1245 root 0x40
blocking rcu_node structures:
Oh wireless is not stable. But my terminal will not continue when I attempt “lspci | grep -i wireless” and the lshw will not work either.
Any more ideas that I can try???????
Hi Mike.
I understand you very well, this laptop caused me several headaches. But now actually is working well.
I think your problem can be NVIDIA driver. My laptop is an Asus X556U with Ubuntu 16.04 (I’am waiting for Ubuntu 18.04 en April because I prefer LTS versions) and use “nouveau” driver instead NVIDIA driver:
# dpkg -l| grep xserver-xorg-video-nouveau
ii xserver-xorg-video-nouveau 1:1.0.12-1build2 amd64 X.Org X server — Nouveau display driver
Why?, because I got crashes, sometimes laptop failed on reboot, “strange things”, etc… I don’t play frequently but it could be a problem if you like playing games.
About wireless, did you try to create a custom config in /etc/modprobe for your chip model?