Optimus? Working or not?

From the terminal logs I see that you have an Alienware M15 R3. Could you provide us your detailed laptops specifications? I have the suspicion that your hardware might not support Optimus at all.

1 Like

Also, this is a long shot - but can you run sudo dpkg --configure -a again?

Also ends in error.

cloudwater@cloudwater-Alienware-15-R3:~$ inxi -F
Host: cloudwater-Alienware-15-R3 Kernel: 5.11.0-27-generic x86_64 bits: 64
Desktop: Gnome 3.38.4 Distro: Zorin OS 16
Type: Laptop System: Alienware product: Alienware 15 R3 v: 1.2.4
serial: <superuser/root required>
Mobo: Alienware model: Alienware 15 R3 v: A00
serial: <superuser/root required> UEFI [Legacy]: Alienware v: 1.2.4
date: 01/25/2018
ID-1: BAT1 charge: 51.8 Wh condition: 73.8/99.0 Wh (75%)
Topology: Quad Core model: Intel Core i7-7820HK bits: 64 type: MT MCP
L2 cache: 8192 KiB
Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800
3: 800 4: 800 5: 800 6: 800 7: 800 8: 800
Device-1: Intel HD Graphics 630 driver: i915 v: kernel
Device-2: NVIDIA GP104BM [GeForce GTX 1080 Mobile] driver: nouveau
v: kernel
Display: x11 server: X.Org 1.20.11 driver: nouveau
resolution: 1920x1080~60Hz
OpenGL: renderer: N/A v: N/A
Device-1: Intel CM238 HD Audio driver: snd_hda_intel
Device-2: NVIDIA GP104 High Definition Audio driver: snd_hda_intel
Sound Server: ALSA v: k5.11.0-27-generic
Device-1: Qualcomm Atheros Killer E2500 Gigabit Ethernet driver: alx
IF: enp60s0 state: down mac: 10:65:30:21:b4:95
Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
driver: ath10k_pci
IF: wlp61s0 state: up mac: 9c:b6:d0:6b:29:3b
Device-3: Qualcomm Atheros type: USB driver: btusb
Local Storage: total: 1.03 TiB used: 8.88 GiB (0.8%)
ID-1: /dev/sda vendor: SK Hynix model: SC311 SATA 128GB size: 119.24 GiB
ID-2: /dev/sdb vendor: HGST (Hitachi) model: HTS721010A9E630
size: 931.51 GiB
ID-1: / size: 116.38 GiB used: 8.88 GiB (7.6%) fs: ext4 dev: /dev/sda5
System Temperatures: cpu: 53.5 C mobo: N/A gpu: nouveau temp: 41 C
Fan Speeds (RPM): N/A
Processes: 278 Uptime: 1h 53m Memory: 15.51 GiB used: 2.88 GiB (18.6%)
Shell: bash inxi: 3.0.38

1 Like

Do you know the refresh rate of your Laptop screen? Is it more than 60?

1 Like

I do not know the refresh rate of the laptop screen. Is there a way for me to find it?

I think... I found the answer.

Error! Bad return status for module build on kernel: 5.11.0-27-generic (x86_64)


It appears Nvidia killed support for the 340 driver at Linux Kernel 5.4

However... This may mean that installing the 5.4 kernel might work.

1 Like

Please type xrandr and show us the output.

1 Like

loudwater@cloudwater-Alienware-15-R3:~$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm
1920x1080 60.03*+ 60.01 59.97 59.96 59.93 48.02
1680x1050 60.00 59.95 59.88
1600x1024 60.17
1400x1050 59.98 60.00
1600x900 59.99 59.94 59.95 59.82
1280x1024 59.95 60.02
1440x900 59.89
1400x900 59.96 59.88
1280x960 60.00 59.99
1440x810 60.00 59.97
1368x768 59.88 59.85
1360x768 59.80 59.96
1280x800 59.99 59.97 59.81 59.91
1152x864 59.97 60.00
1280x720 60.00 59.99 59.86 59.74
1024x768 60.04 60.00 59.95
960x720 60.00
928x696 60.05
896x672 60.01
1024x576 59.95 59.96 59.90 59.82
960x600 59.93 60.00
960x540 59.96 59.99 59.63 59.82
800x600 60.00 60.32 59.96 56.25
840x525 60.01 59.88
864x486 59.92 59.57
800x512 60.17
700x525 59.98
800x450 59.95 59.82
640x512 60.02
720x450 59.89
700x450 59.96 59.88
640x480 60.00 59.94
720x405 59.51 58.99
684x384 59.88 59.85
680x384 59.80 59.96
640x400 59.88 59.98
576x432 60.06
640x360 59.86 59.83 59.84 59.32
512x384 60.00
512x288 60.00 59.92
480x270 59.63 59.82
400x300 60.32 56.34
432x243 59.92 59.57
320x240 60.05
360x202 59.51 59.13
320x180 59.84 59.32
HDMI-3 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-1 disconnected (normal left inverted right x axis y axis)
DP-1-2 disconnected (normal left inverted right x axis y axis)
HDMI-1-2 disconnected (normal left inverted right x axis y axis)

I did some research and it seems that your laptop does not have Optimus at all. But it seems to have a MUX switch. So it means that you can manually switch to your GPU or CPU. I think that's why in your earlier post, you had some options missing in the Nvidia X application.
Also does pressing fn + f7 do anything?

1 Like

EDIT: Before this- follow up on Taha_mcp's post checking about if you have Optimus
/end edit

If you want to try installing the 5.4 kernel on Zorin OS 16...
Run in terminal

sudo apt install linux-generic

Once installed, try installing the Nvidia Driver again.
If successful, then you will need to open /etc/modprobe.d/blacklist-framebuffer.conf As Root and comment out the line with nvidiafb to stop it from being blacklisted.

Nothing happens.

Would it make sense to do this if no Optimus?

This also brings me back to my original question:

Will this cause only on the nvidia card to provide display? I don't really need optimus if I can run the game on the nvidia card.

Yeah you absolutely can, with even better performance! Optimus is only for when you would like to prolong battery life. If battery life is not a concern for you, disabling optimus gives you a small performance boost.

1 Like

Since you have a 1080, I think you can easily use one of the new drivers and you're golden.
You can install it by running this command:
sudo aptitude install nvidia-driver-465 nvidia-settings
Then restart, and you're done! You can now play your games using your 1080 GPU.
The driver version does not matter that much. But the newer ones are generally better.


Seems like the installation was fine except for this last part at the end:

update-initramfs: Generating /boot/initrd.img-5.11.0-27-generic
W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915
Processing triggers for libc-bin (2.31-0ubuntu9.2) ...

These are nothing to worry about. If you get the non-free linux-firmware package, you can usually make it go away. But as they can act as placeholders for an addition to the kernel that has not been made yet, they often go away on their own when the kernel is updated.

Taha_mcp asked me why I was trying to get the nvidia-340 driver installed. My answer was:

My apologies to the O.P...

1 Like

The nvidia-340 came up because of this step:

I go from one thread to another too quickly.
And from one Nvida thread to another...
I should have double-checked that, sorry. At the time, I meant to point out that if you follow the guide, to replace the step where it gives the terminal command to install the driver with the driver version you actually need.
By the time I got back to it, I had forgotten about it.
And it is not unusual that users are looking for Older Versions for older cards on Linux...
A lesson for me - scroll up and get re-acquainted with the thread before opening my mouth.

Understandably difficult when:

How about this part of my first question?

Is it also necessary to implement this change?

1 Like

It is not necessary unless you are experiencing difficulties at boot.
The Grub Parameter nomodeset prevents the system from using the Nvidia card prior to the drivers for the Nvidia card being initiated during boot. This tells the system to use the dedicated graphics at boot, until after the Nvidia drivers are loaded.

What this means is that the system is working properly. Modesetting allows for the Nvidia card to be used during high graphics demand, with the dedicated card being used for lower demand. It saves battery life or power.