manjaro / mhwd Goto Github PK

Could someone give some hints on this topic that I have open on Manjaro forum? I think that maybe some help directly from the developers would help.

Link:
https://forum.manjaro.org/t/nvidia-gpu-tearing-on-manjaro/715

Thanks!

Hey there

I own a Dell Vostro 5470 and I'm running Manjaro on it. Fresh install, 2 days old. I noticed that my nVidia card was turned on when I booted it up and I noticed bumblebeed had failed to unload the nvidia and nvidia-modeset modules. I then added blacklist nvidia-drm to the /etc/modprobe.d/mhwd-nvidia.conf and it solved the problem.

I'm a developer and I would submit a pull request with the blacklisted module added to the config file, but I can't seem to find the code responsible for adding the modules to that file.

At first I thought this was just a regression in mhwd-db (for catalyst and nvidia).
But then I noticed there really isn't any reverse function to set_modules<proprietary> in the first place.

TL;DR every time I switch back to open driver from proprietary I have to rm /mod*.d/mhwd-gpu.conf

I installed manjaro linux (manjaro-cinnamon-0.8.13.1-x86_64.iso) on a Asus X51RL. This machine has a "Mobility Radeon Xpress 200M" on board.

01:05.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RC410M [Mobility Radeon Xpress 200M] [1002:5a62]
        Subsystem: ASUSTeK Computer Inc. Device [1043:1402]
        Kernel driver in use: radeon
        Kernel modules: radeon

MHWD created a file /etc/X11/mhwd.d/xyz and linked this to /etc/X11/xorg.conf.d/90xyz.conf (sorry for the alias naming, i've deleted both files already). This file forced the xserver to load the module radeon.

The sticking point is (imho) that the xserver needs to have /usr/lib/xorg/modules/drivers/ati_drv.so in place (additionally?) to support this GPU properly. After installing xf86-video-ati my X worked as expected. Without it i just got a black screen.

Kind regards, Jörn

p.s. This was my first shot with manjaro. Good job!

Hi,

Currently when I reinstall my graphics drivers, mhwd seems to overwrite /etc/conf.d/modules
But this file is used in OpenRC to specify the kernel modules.

Could mhwd be changed to use some other config file..

According to arch wiki and manjaro forum discussions, newer intel chips have less screen tearing and other problems. https://wiki.archlinux.org/index.php/intel_graphics Could mhwd check for the intel chip model and take this to account by

• not installing xf86-video-intel and writing any intel related xorg config
• installing microcode
• adding i915 to modules in mkinitcpio.conf?

For skylake, add extra configuration file https://wiki.archlinux.org/index.php/intel_graphics#Skylake_support

If I recall, I believe this is currently a fault of nvidia itself not testing it's drivers against wayland while relying on the older Xorg standard, but just to make sure.

Let's start with the initial issue first. You guys write the compositor configuration to X11 whenever nonfree drivers are selected during installation. This is wrong, and actually broke my touchpad until I noticed the the conflict between KCM and libinput originated from those leftover files in /etc/X11. So I ended up removing those, and then attempted to find the problem... Well, today I had to work through a project with OBS, and realized it wasn't working because of the nvidia drivers (it was actually because it doesn't support wayland, but let's focus on the issue). So I went to install the nonfree drivers like so:

sudo mhwd -a pci nonfree 0300
sudo systemctl enable bumblebeed (yes, I am using a 960M on a rolling release lol. I love this distro)

And during sudo mhwd -a pci nonfree 0300, I got this after a successful install:

/var/lib/mhwd/scripts/mhwd: line 9: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/mhwd: line 10: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/mhwd: line 11: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/mhwd: line 12: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/mhwd: line 13: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 36: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 37: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 38: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 43: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 43: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 48: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 49: /etc/X11/mhwd.d/intel.conf: No such file or directory
sed: can't read /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 60: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 61: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 62: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 63: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 64: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 65: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 71: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 72: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 73: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 74: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 75: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 76: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 82: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 83: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 84: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 85: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 86: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 87: /etc/X11/mhwd.d/intel.conf: No such file or directory
/var/lib/mhwd/scripts/include/0300: line 88: /etc/X11/mhwd.d/intel.conf: No such file or directory
warning: could not find '/etc/X11/mhwd.d/intel.conf'!

So I imagine those files are pretty important for proper driver support, because when I go to launch nvidia settings, this is where things get really interesting:

ERROR: NVIDIA driver is not loaded


ERROR: Error querying enabled displays on GPU 0 (Missing Extension).


ERROR: Error querying connected displays on GPU 0 (Missing Extension).


ERROR: nvidia-settings could not find the registry key file. This file should have been installed along with this driver at /usr/share/nvidia/nvidia-application-profiles-key-documentation. The application profiles will continue to work,
       but values cannot be prepopulated or validated, and will not be listed in the help text. Please see the README for possible values and descriptions.

I saw another nvidia issue, but I wanted to open a proper case for the time being since it isn't just a fault of nvidia drivers (again, my trackpad partially broke. I still can't figure out middle clicks for pasting which is annoying, but it works better than it did before since KCM finally works).

Anyway, I hope I somewhat helped. I'd like to help with the project in the future. It's just I don't know much outside of device trees and kernels.

Thank you for looking over this!

Could, someone explain to me what means each point of the TODO list, I'm not understand:
1 - allow to set the base lib dir
2 - force to remove db config
3 - show detailed info for one config
4 - set architecture from library not from bash
5 - pass ids and bus ids to script
6 - do not remove packages on reinstallation ...
7 - add option similar to pacman --root (this option do not exists on pacman ! )

/build/src/mhwd/mhwd/mhwd.cpp: In function 'int main(int, char**)':
/build/src/mhwd/mhwd/mhwd.cpp:818:84: warning: 'operationType' may be used uninitialized in this function [-Wmaybe-uninitialized]
                     config = mhwd::getDatabaseConfig(&data, (*iter), operationType);
                                                                                    ^
Linking CXX executable mhwd

maybe we should look into it ...

Apart from the vesa fallback issue which I am unable to test and verify on the VGA(bochs_drm) virtual graphics device due to it not permitting TTY switching and locking up during boot for some reason. I have come across the following openSUSE Plymouth bug.

This bug occurs because the DRM driver for the graphics card is not in the initrd.

Since Plymouth has opened /dev/fb0 from userspace, the driver will be unloaded, but the memory region will not be freed. Thus, the DRM driver cannot reserve all of the card's VRAM, and will error out.

The result is a system where X accesses the GPU directly using the VESA driver, and the kernel is unable to display its VTs as /dev/fb0 is already gone.

And:

I suggest dropping framebuffer support in Plymouth.

Almost nobody should see a difference: All modern x86 systems have DRM driver support as far as I can see, and newer ARM devices are also switching to it.
Everybody else will still see a text splash.

Since this is not currently a ./configure option in Plymouth, I suggest simply not packaging /usr/lib64/plymouth/renderers/frame-buffer.so .

While the UEFI boot with bochs_drm locks up BIOS boots and lspci -nnk shows that the bochs-drm kernel driver is not in use. On boot I pressed F3 and changed to Default as plymouth.enable=0 did not seem to help, this time the bochs-drm driver was in use. Switching TTY however does not seem to work still. Tested KaOS to compare, even with vga=0x317(Default must have done something else beyond remove this param) it boots with bochs-drm driver loaded fine and can switch TTY.

Manjaro with F3/Default boots with text, but has a moving horizontal line/progressbar all over the place, I'm not sure if that is a part of Plymouth.

As per my research to solve why Manjaro fails to boot on UEFI based VMs with graphic devices that are not by Intel/AMD/NVIDIA. My most recent thread on the forums points to the problem being 90-mhwd.conf hardcoding the driver to vesa.

If the 3 major GPU vendors mentioned are not available and you would otherwise fallback to vesa, could this please be avoided in the config file and allow X to autodetect and handle the driver itself?

I just bought a Acer E5-521G-871K laptop and install, in dual boot with Windows 8.1, Manjaro XFCE 0.8.13.1 x64 bits with Linux Kernel 3.18.
When I was updating for the first time I notice that only wired networks where recognized and not wireless and in the Net Cafe they have a new router.
I check also if the problem was from the new router but isn't. The wireless network works in Windows 8.1.
So I go to Manjaro Settings Manager and notice that the Broadcom wireless driver wasn't installed (see image 1).
I saw that there exist a linux kernel module for Broadcom: linux318-broadcom-wl 6.30.223.248-1 so if I install this I get the problem solved ?
I have this linux module installed linux318-ndiswrapper 1.59-11, so it will conflict with linux318-broadcom-wl 6.30.223.248-1 if I install it ?
I check by typing in a terminal window: lspci -k and I have the kernel module loaded and in use for Broadcom and the wireless network doesn't work. (see image 2)

Thanks in advance

can we publish a gpumatrix (gpus supported by mhwd)

Surely this software's copyright is not held by the FSF, and surely it wasn't written only in 2007.

Please fix the copyright information in the source code's license headers. The GPLv3 is copyright 2007 by the FSF, but not this program.

💣 HOW TO REPRODUCE:

• Using a laptop with a BCM43228 wifi controller, try to install Manjaro using Calamares.

🔥 RESULT:

• The installation never ends at the step "configure the hardware".

🔍 RELEVANT DETAILS:

• In the UEFI, disabling the wifi card makes the installation to end without problems.
• Also reported in the Manjaro forum.

🔦 WORK AROUND:

1. In the application "Terminal" enter:
   sudo nano /usr/lib/calamares/modules/mhwdcfg/main.py

2. Delete the lines:

for id in self.identifier['net']:
                self.configure(b, id)

Hello,
without libhd intstalled mhwd will error out ..

...
https://github.com/manjaro/mhwd/blob/master/libmhwd/CMakeLists.txt#L16
https://github.com/manjaro/mhwd/blob/master/libmhwd/CMakeLists.txt#L20
...

but nothing checks to see the lib is around..

Hello,

On Manjaro XFCE x64 17.0.5 fresh install.
MHWD not install config file for Intel HD Graphic for what ?
I had to create the file myself on 3 laptop.
Intel Card tested : Skylake / Kaby Lake / Apollo Lake.

Cordialy

I tested Manjaro XFCE on a few computers (with intel and radeon video), and I noticed some tearing.
Video in VLC played without tearing, and moving windows didn't produced tearing.
But moving the zoomed image in Viewnior, and scrolling in Firefox (and video playing from websites) produce tearing.
I added the following line to the driver options in the MHWD generated driver config file:
Option "TearFree" "True"

It solved the problem on all computers.
But a newbie cannot edit the config file. Why doesn't MHWD add this option by default?

Similar to issue #37, mhwd is not removing the nvidia proprietary driver properly.
Maybe a similar solution to manjaro/mhwd-db#9 could solve this.

After removing the proprietary driver (testet with video-nvidia-340xx) mhwd should restore nouveau if installed (usually yes, because the driver is not conflicting as a package).
Instead, nvidia module is still getting loaded, causing errors on boot, since modules are no longer installed:

cat /etc/modules-load.d/mhwd-gpu.conf
##
## Generated by mhwd - Manjaro Hardware Detection
##

nvidia

Dsiplay manager fails to start because nouveau remains blacklisted, even after removing nvidia with mhwd:

[root@manjaro /]# cat /etc/modprobe.d/mhwd-gpu.conf
##
## Generated by mhwd - Manjaro Hardware Detection
##
blacklist nouveau
blacklist ttm
blacklist drm_kms_helper
blacklist drm

Forum thread here.

In case of sddm, it's not possible to login to TTY because it keeps trying to spawn a new instance but fails, the only solution to fix a machine in this state is to boot with live media and use chroot to manually edit the files from above...

EDIT: just to add another general manjaro-settings mhwd issue: when installing a driver or removing one it is not possible to reboot/shutdown/log out from the menu (tested on KDE), only through command line makes this possible. So a simple "Do you want to restart now?" prompt after installing a driver with manjaro-settings would help users who don't know how to restart the system.

The current version of mhwd-kernel (v0.6.1-2) adds the r8168 modules to the output of the installed kernels.

This has been introduced with e5c31e6 and works with an earlier commit.

Running mwhd-kernel -li gives following output:

Output at master (e5c31e6):

Currently running: 4.15.0-1-MANJARO (linux415)
The following kernels are installed in your system:
   * linux414
   * linux414-r8168
   * linux415
   * linux415-r8168

Output at master^ (a30ba8b):

Currently running: 4.15.0-1-MANJARO (linux415)
The following kernels are installed in your system:
   * linux414
   * linux415

I have an eGPU setup where I can boot using a GTX 960 or Intel HD Graphics. I had a problem where I couldn't boot into Manjaro after plugging in the eGPU, and after some hunting, finally found a hacky solution outlined here in the Manjaro forums

Even though this problem affects people with eGPUs, I think it might be the same if plugging out a GPU from a desktop and then trying to start it with Intel integrated graphics...

So is there a better solution to this issue, rather than having to run the above steps mentioned in the forum post? Also, is this commit relevant?

Thanks for the great work!

When I install a new kernel from the mhwd-kernel module, the os-probe is not run, so that in the grub menu the Windows entries are not available. Running update-grub manually solves the problem.

As I recently installed Manjaro on a laptop with hybrid Intel/Nvidia graphics I found out that with the drivers included in the bumblebee one, I couldn't run optirun/primusrun to enable my nvidia GPU.

This however only required a small fix to sort it self out.
Namely I just moved the 90-mhwd.conf symlink the driver puts in /etc/X11/xorg.conf.d/.
After that. xorg recalibrated itself on next reboot and optirun/primusrun worked again.

So I propose to NOT create this symlink in the first place on these setups.
Mine was an Intel HD 4000 / Nvidia GTX 820M setup, but I bet many have the same issue.

i installed manjaro on my desktop after having no problems with oit on my laptop
but mhwd only offers catalyst, ati and vesa drivers and autoconfiguring any of those breaks my system in some way or another on xorg start

also amdgpu is not even listed or available (even though the mhwd-amdgpu package is installed)
and i installed and configured it manually

maybe it is because my graphics card is a R9 390 but it is detected as a R9 290

i suspect for what i want to do using amdgpu-pro wouild be the best but that is not supported and the package conflicts with mhwd (which would break the system)

PS: if i have time i can try to replicate the issues with ati and catalyst drivers after using the autoconfiguration feature

It's kind of difficult to remove nonfree drivers on manjaro...
After removing video-catalyst I was needed to reinstall xf86-video-ati, xorg-server
and delete line in /etc/modprobe.d/mhwd-gpu.conf blacklist radeon
I think this all supposed to be automated. At least removing radeon from blacklist...

All kernels 4.4 and below are unaffected, this is likely a small oversite but:
acpi_toshiba handle is missing, this is used by all APU and mCPU laptops made by Toshiba and other brands that use the acpi_toshiba kernel flag... this is quite a serious issue as without the acpi_toshiba flag set in the kernel the laptop forces the processor to run at full speed constantly which they are not intended to do... a Toshiba C50d laptop will reach 72'c "Idling" on desktop due to this issue, same on the other 4 Satellites ive tested it on aswell. Downgrading to 4.4 solved the serious issue (* auto-heat shutdowns constantly, it froze 5 times due to the heat issue simply in the time it takes to install a lower kernel version :/ *)
Idle desktop Temp with 4.4 Kernels and below = 44'c
Idle desktop Temp with 4.5 Kernel and above = 72~'C, GPU causes vga_Leakage errors, System freezes due to temprature, General severe overheating issues.

As I reported on the forums, xorg-server (and I think xorg-server-common?) aren't restored/checked when I install video-ati after video-catalyst uninstall.

Hello @philmmanjaro !
I found out that if I boot with a non-Manjaro kernel I cannont install a Manjaro kernel with mhwd-kernel -i

~ >>> mhwd-kernel -li                                                          
Currently running: 4.15.18-1-ck (linux415)
The following kernels are installed in your system:
   * linux414
~ >>> sudo mhwd-kernel -i linux417                                             
:: Synchronizing package databases...
 core                     143.4 KiB   567K/s 00:00 [######################] 100%
 extra                   1723.2 KiB   690K/s 00:02 [######################] 100%
 community                  4.6 MiB   690K/s 00:07 [######################] 100%
 multilib                 178.2 KiB   696K/s 00:00 [######################] 100%
error: no targets specified (use -h for help)
~ >>>                                       

If I boot with a Manjaro kernel I'm able to install with mhwd-kernel -i

eugen@mjro Linux 4.17.0-1-MANJARO x86_64 Tue Apr 24 12:31:26 CEST 2018
~ >>> sudo mhwd-kernel -i linux414                                             
[sudo] password for eugen: 
:: Synchronizing package databases...
 core                     143.4 KiB   223K/s 00:01 [######################] 100%
 extra                   1723.0 KiB   267K/s 00:06 [######################] 100%
 community                  4.6 MiB   281K/s 00:17 [######################] 100%
 multilib                 178.2 KiB   326K/s 00:01 [######################] 100%
resolving dependencies...
looking for conflicting packages...

Packages (2) linux414-4.14.35-1  linux414-headers-4.14.35-1

Total Installed Size:  161.68 MiB

:: Proceed with installation? [Y/n] 

Request: I think a notification which makes the user understand that they should boot with a Manjaro kernel would be nice if the check for running a Manjaro kernel fails.

@FadeMind pointed at this line:
https://github.com/manjaro/mhwd/blob/master/scripts/mhwd-kernel#L86

The forum discussion was here.

@philmmanjaro
when I was trying to install manjaro xfce 16.06.1 to my new PC which is using nvidia GTX 1070 displaycard, the liveCD failed to startX. Its seems that the Kernel / Mhwd doesn't recognize the GPU.

I think this could be resolved with the latest driver from nvidia.

can you please kindly add the support of nvidia 367.27 driver to mhwd?
http://www.nvidia.com/download/driverResults.aspx/104284/en-us
https://www.archlinux.org/packages/extra/x86_64/nvidia/

Thank you very much!