I recently bought an ASUS FX505DD Gaming laptop for the purpose of installing Linux as my daily driver but of course the system is set up in a Dual Boot Environment with Secure Boot Disabled for Compatibility Purposes with Win32 Applications. A noteworthy heads-up is that i am not keen or that experienced with Linux atm as i am actively using/replacing it for developmental purposes also as i am a freshman at my university.
Now my problem is, trying to go to various forums especially here in devtalk nvidia forums, i came across two forum posts with almost the same system setup as mine but trying various fixes or configurations would just lead to a black screen, blinking cursor or a login lock-up.
I tried this configuration from another nvidia forum post suggested by the user ‘generix’ but no luck as i am stuck in a black screen and had to open tty and revert it back to ‘Option “AllowEmptyInitialConfiguration”’
You were on the right track but you missed the threads about the systems with a bug:
for unknown reasons, if the amd gpu is configured by bios to use less than 2GB of vram, the internal monitor fails to be turned on. Some user had success with connecting and external monitor (which then works), log in and then enable the internal monitor in gnome control center.
You could also try this:
Thanks! I haven’t tried the first option yet since i cannot get an output to an external display but the second option got me into the desktop environment with nvidia-settings working as it should. Though the 4th line/bullet didn’t work for me as i don’t use Gnome Desktop Environment/Gnome Display Manager as i use KDE Plasma on Ubuntu 19.10. Terminal didn’t find any directories being specified.
What should i do next? Re-generate a new nvidia bug report?
cp: cannot stat '/home/username/.config/monitors.xml': No such file or directory
Hi ! I have similar problem.
but solution doesn’t work for me.
When I run :
DISPLAY=:0 XAUTHORITY=/run/user/1000/gdm/Xauthority xrandr --auto
I get this error:
xrandr: Configure crtc 4 failed
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 21 (RRSetCrtcConfig)
Value in failed request: 0x0
Serial number of failed request: 56
Current serial number in output stream: 56
The same error if I run: xrandr --auto , but in the last 2 lines 55 is the code.
And also, I havent this path /var/lib/gdm/.config/monitors.xml
I only have until /var/lib/gdm3 , but without .config , and I search with 'find . -iname “monitors.xml” ’ into /var/lib and nothing found.
I have ubuntu 18.04 on laptop asus fx705dt (amd ryzen 7 + amd radeon rx vega 10 + nvidia gtx 1650)
Yes! Thanks, the file indeed got generated after a reboot and the display is working as it should it be as it is able to display the login screen without blindly logging in everytime in a black screen. providers.txt (3.61 KB)
Also, how do i limit the framerate according to the refresh rate of my monitor and/or power manage my nvidia graphics card as it uses quite a lot of battery power at standby. How do i resolve this? Create a new thread? or what sources should i go through to be able to resolve the excessive power consumption?
Running glxgears returns a value of
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
37265 frames in 5.0 seconds = 7452.871 FPS
35005 frames in 5.0 seconds = 7000.869 FPS
33474 frames in 5.0 seconds = 6694.800 FPS
34142 frames in 5.0 seconds = 6828.344 FPS
34602 frames in 5.0 seconds = 6920.322 FPS
33468 frames in 5.0 seconds = 6693.599 FPS
34114 frames in 5.0 seconds = 6822.366 FPS
When the integrated graphics for AMD is being used, the framerate is capped at 120Hz
Normally, this can be achieved by enabling prime sync using the kernel parameter
but I suspect this is so far only implemented in the intel driver. You would have to poke the amdgpu people for that.
Regarding overall power consumption, the linux driver takes a long time to throttle down (~40sec). What’s the output of nvidia-smi after idling for that time?
Yes, it’s the same, just add it to the grub config like you did with the nouveau parameter.
Power states look normal, to save power when on battery, you can only switch back to amd, running sudo prime-select intel
Hi, it seems like nvidia-drm kernel module is already being loaded upon bootup so therefore i don’t need to add nvidia-drm.modeset=1 in my kernel parameters anymore?
Also, quick question. Should nvidia-smi be able to communicate with the nvidia driver if nvidia prime is currently set at the Intel profile?
Just curious as i asked my buddy to execute sudo nvidia-smi while the intel profile is currently selected, it returned an error that nvidia-smi cannot communicate with the driver as long as the intel profile was selected which what one would expect. Therefore my question is, if nvidia-smi cannot communicate with my nvidia graphics card and not display an output, then the driver is working properly and using the integrated graphics instead of the performance-based nvidia card?
I am still able to fetch data from nvidia-smi even if prime-select is already selected for the intel profile
nvidia-drm is always loaded, modeset=1 is an option for it.
sudo cat /sys/module/nvidia_drm/parameters/modeset
should return ‘Y’ if enabled.
Whether or not nvidia-smi displays something when switched to intel depends on the method used to turn off the nvidia gpu, i.e. on the Ubuntu version. Older versions used bbswitch to completely turn it off, then nvidia-smi returns nothing. Newer versions use runtime suspending, then nvidia-smi will wake up the gpu.