No login screen after Ubuntu 18.04 update
After the upgrade from Ubuntu 18.04 to 18.04.1, when booting instead of going from grub menu to the purple login page, it goes directly to tty1.
The current kernel is 4.15.0-33 and I've already tried to boot with every kernel version from 33 to 29.
Also the systemctl status gdm3 command gives the active status.
Output of dmesg --level=err,warn:
Output of lspci -knn | feel -i VGA -A3:
00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b)
Subsystem: ASUSTeK Computer Inc. Haswell-ULT
Integrated Graphics Controller [1043:16cd]
Kernel driver in use: i915
Kernel modules: i915
18.04 gdm tty
edited Jan 20 at 14:50
karel
59k13128149
asked Aug 25 '18 at 11:24
QuestionerQuestioner
84
add a comment |
After the upgrade from Ubuntu 18.04 to 18.04.1, when booting instead of going from grub menu to the purple login page, it goes directly to tty1.
The current kernel is 4.15.0-33 and I've already tried to boot with every kernel version from 33 to 29.
Also the systemctl status gdm3 command gives the active status.
Output of dmesg --level=err,warn:
Output of lspci -knn | feel -i VGA -A3:
00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b)
Subsystem: ASUSTeK Computer Inc. Haswell-ULT
Integrated Graphics Controller [1043:16cd]
Kernel driver in use: i915
Kernel modules: i915
18.04 gdm tty
edited Jan 20 at 14:50
karel
59k13128149
asked Aug 25 '18 at 11:24
QuestionerQuestioner
84
Welcome to Ask Ubuntu! Add the output ofdmesg --level=err,warnto your post.
– abu_bua
Aug 25 '18 at 11:37
Done, I don't know why the Imgur quality I so low tough.
– Questioner
Aug 25 '18 at 11:50
Add the output oflspci -knn | grep -i vga -A3, post as plain text.
– abu_bua
Aug 25 '18 at 12:09
add a comment |
After the upgrade from Ubuntu 18.04 to 18.04.1, when booting instead of going from grub menu to the purple login page, it goes directly to tty1.
The current kernel is 4.15.0-33 and I've already tried to boot with every kernel version from 33 to 29.
Also the systemctl status gdm3 command gives the active status.
Output of dmesg --level=err,warn:
Output of lspci -knn | feel -i VGA -A3:
00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b)
Subsystem: ASUSTeK Computer Inc. Haswell-ULT
Integrated Graphics Controller [1043:16cd]
Kernel driver in use: i915
Kernel modules: i915
18.04 gdm tty
edited Jan 20 at 14:50
karel
59k13128149
asked Aug 25 '18 at 11:24
QuestionerQuestioner
84
After the upgrade from Ubuntu 18.04 to 18.04.1, when booting instead of going from grub menu to the purple login page, it goes directly to tty1.
The current kernel is 4.15.0-33 and I've already tried to boot with every kernel version from 33 to 29.
Also the systemctl status gdm3 command gives the active status.
Output of dmesg --level=err,warn:
Output of lspci -knn | feel -i VGA -A3:
00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b)
Subsystem: ASUSTeK Computer Inc. Haswell-ULT
Integrated Graphics Controller [1043:16cd]
Kernel driver in use: i915
Kernel modules: i915
18.04 gdm tty
18.04 gdm tty
edited Jan 20 at 14:50
karel
59k13128149
asked Aug 25 '18 at 11:24
QuestionerQuestioner
84
edited Jan 20 at 14:50
karel
59k13128149
asked Aug 25 '18 at 11:24
QuestionerQuestioner
84
edited Jan 20 at 14:50
karel
59k13128149
edited Jan 20 at 14:50
karel
59k13128149
edited Jan 20 at 14:50
karel
59k13128149
59k13128149
asked Aug 25 '18 at 11:24
QuestionerQuestioner
84
asked Aug 25 '18 at 11:24
QuestionerQuestioner
84
asked Aug 25 '18 at 11:24
QuestionerQuestioner
84
84
Welcome to Ask Ubuntu! Add the output ofdmesg --level=err,warnto your post.
– abu_bua
Aug 25 '18 at 11:37
Done, I don't know why the Imgur quality I so low tough.
– Questioner
Aug 25 '18 at 11:50
Add the output oflspci -knn | grep -i vga -A3, post as plain text.
– abu_bua
Aug 25 '18 at 12:09
add a comment |
Welcome to Ask Ubuntu! Add the output ofdmesg --level=err,warnto your post.
– abu_bua
Aug 25 '18 at 11:37
Done, I don't know why the Imgur quality I so low tough.
– Questioner
Aug 25 '18 at 11:50
Add the output oflspci -knn | grep -i vga -A3, post as plain text.
– abu_bua
Aug 25 '18 at 12:09
Welcome to Ask Ubuntu! Add the output of
dmesg --level=err,warn to your post.– abu_bua
Aug 25 '18 at 11:37
Welcome to Ask Ubuntu! Add the output of
dmesg --level=err,warn to your post.– abu_bua
Aug 25 '18 at 11:37
Done, I don't know why the Imgur quality I so low tough.
– Questioner
Aug 25 '18 at 11:50
Done, I don't know why the Imgur quality I so low tough.
– Questioner
Aug 25 '18 at 11:50
Add the output of
lspci -knn | grep -i vga -A3, post as plain text.– abu_bua
Aug 25 '18 at 12:09
Add the output of
lspci -knn | grep -i vga -A3, post as plain text.– abu_bua
Aug 25 '18 at 12:09
add a comment |
1 Answer
1
active
oldest
votes
First, eliminate a possible disk file system problem...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode
- choose Root access
- at the # prompt, type
sudo fsck -f /
- repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted
- open a
terminalwindow - type
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
Next, eliminate a possible video subsystem problem...
At the GRUB menu, hit the e key, and edit the line that contains "splash quiet" to "splash quiet nomodeset", hit ctrl-x to continue booting. See if it will fully boot, even if the video display isn't at the correct resolution. If it boots, do one of the following...
1. Eliminate a possible wayland problem...
Boot to recovery mode, and choose root access. Then type:
sudo mount -o rw,remount /
In terminal...
cd /etc/gdm3# change directory
sudo pico custom.conf# edit this file
Find and change:
#WaylandEnable=false
To this:
WaylandEnable=false
Save the file.
sudo dpkg-reconfigure gdm3# select gdm3 DM
Select gdm3 and OK.
reboot# reboot the computer
2. Update/reinstall the current nouveau/Nvidia video drivers.
Update #1:
While trying the wayland fix, errors indicated a gdm3 problem. Reinstalling gdm3 resolved the problem.
answered Aug 25 '18 at 13:51
heynnemaheynnema
18.8k22155
fsck gives no errors, splash quiet is "quiet splash" in my file so I wrote "quiet splash nomodeset" and after ctrl+x the result is always the tty
– Questioner
Aug 25 '18 at 14:17
@Questioner what about the wayland fix and the video drivers?
– heynnema
Aug 25 '18 at 14:23
While doing the Wayland part, doing "sudo dpkg-reconfigure gdm3" gives: "gdm3 is ruined or not completely installed". Edit: That message made me think and so doing this steps I've solved the problem! 1- reedit custom.conf leaving #WaylandEnable=false 2- rebooted in normal mode 3- from tty1: sudo apt install gdm3 That's it, maybe the update broke gdm3
– Questioner
Aug 25 '18 at 14:40
@Questioner ah, there's your problem. Do "sudo apt-get update" and "sudo apt-get install gdm3" and "reboot". Please see the update to my answer, and accept it if it was helpful.
– heynnema
Aug 25 '18 at 14:45
Yes, already said in the edit
– Questioner
Aug 25 '18 at 14:50
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1068809%2fno-login-screen-after-ubuntu-18-04-update%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
First, eliminate a possible disk file system problem...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode
- choose Root access
- at the # prompt, type
sudo fsck -f /
- repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted
- open a
terminalwindow - type
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
Next, eliminate a possible video subsystem problem...
At the GRUB menu, hit the e key, and edit the line that contains "splash quiet" to "splash quiet nomodeset", hit ctrl-x to continue booting. See if it will fully boot, even if the video display isn't at the correct resolution. If it boots, do one of the following...
1. Eliminate a possible wayland problem...
Boot to recovery mode, and choose root access. Then type:
sudo mount -o rw,remount /
In terminal...
cd /etc/gdm3# change directory
sudo pico custom.conf# edit this file
Find and change:
#WaylandEnable=false
To this:
WaylandEnable=false
Save the file.
sudo dpkg-reconfigure gdm3# select gdm3 DM
Select gdm3 and OK.
reboot# reboot the computer
2. Update/reinstall the current nouveau/Nvidia video drivers.
Update #1:
While trying the wayland fix, errors indicated a gdm3 problem. Reinstalling gdm3 resolved the problem.
answered Aug 25 '18 at 13:51
heynnemaheynnema
18.8k22155
fsck gives no errors, splash quiet is "quiet splash" in my file so I wrote "quiet splash nomodeset" and after ctrl+x the result is always the tty
– Questioner
Aug 25 '18 at 14:17
@Questioner what about the wayland fix and the video drivers?
– heynnema
Aug 25 '18 at 14:23
While doing the Wayland part, doing "sudo dpkg-reconfigure gdm3" gives: "gdm3 is ruined or not completely installed". Edit: That message made me think and so doing this steps I've solved the problem! 1- reedit custom.conf leaving #WaylandEnable=false 2- rebooted in normal mode 3- from tty1: sudo apt install gdm3 That's it, maybe the update broke gdm3
– Questioner
Aug 25 '18 at 14:40
@Questioner ah, there's your problem. Do "sudo apt-get update" and "sudo apt-get install gdm3" and "reboot". Please see the update to my answer, and accept it if it was helpful.
– heynnema
Aug 25 '18 at 14:45
Yes, already said in the edit
– Questioner
Aug 25 '18 at 14:50
add a comment |
First, eliminate a possible disk file system problem...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode
- choose Root access
- at the # prompt, type
sudo fsck -f /
- repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted
- open a
terminalwindow - type
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
Next, eliminate a possible video subsystem problem...
At the GRUB menu, hit the e key, and edit the line that contains "splash quiet" to "splash quiet nomodeset", hit ctrl-x to continue booting. See if it will fully boot, even if the video display isn't at the correct resolution. If it boots, do one of the following...
1. Eliminate a possible wayland problem...
Boot to recovery mode, and choose root access. Then type:
sudo mount -o rw,remount /
In terminal...
cd /etc/gdm3# change directory
sudo pico custom.conf# edit this file
Find and change:
#WaylandEnable=false
To this:
WaylandEnable=false
Save the file.
sudo dpkg-reconfigure gdm3# select gdm3 DM
Select gdm3 and OK.
reboot# reboot the computer
2. Update/reinstall the current nouveau/Nvidia video drivers.
Update #1:
While trying the wayland fix, errors indicated a gdm3 problem. Reinstalling gdm3 resolved the problem.
answered Aug 25 '18 at 13:51
heynnemaheynnema
18.8k22155
fsck gives no errors, splash quiet is "quiet splash" in my file so I wrote "quiet splash nomodeset" and after ctrl+x the result is always the tty
– Questioner
Aug 25 '18 at 14:17
@Questioner what about the wayland fix and the video drivers?
– heynnema
Aug 25 '18 at 14:23
While doing the Wayland part, doing "sudo dpkg-reconfigure gdm3" gives: "gdm3 is ruined or not completely installed". Edit: That message made me think and so doing this steps I've solved the problem! 1- reedit custom.conf leaving #WaylandEnable=false 2- rebooted in normal mode 3- from tty1: sudo apt install gdm3 That's it, maybe the update broke gdm3
– Questioner
Aug 25 '18 at 14:40
@Questioner ah, there's your problem. Do "sudo apt-get update" and "sudo apt-get install gdm3" and "reboot". Please see the update to my answer, and accept it if it was helpful.
– heynnema
Aug 25 '18 at 14:45
Yes, already said in the edit
– Questioner
Aug 25 '18 at 14:50
add a comment |
First, eliminate a possible disk file system problem...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode
- choose Root access
- at the # prompt, type
sudo fsck -f /
- repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted
- open a
terminalwindow - type
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
Next, eliminate a possible video subsystem problem...
At the GRUB menu, hit the e key, and edit the line that contains "splash quiet" to "splash quiet nomodeset", hit ctrl-x to continue booting. See if it will fully boot, even if the video display isn't at the correct resolution. If it boots, do one of the following...
1. Eliminate a possible wayland problem...
Boot to recovery mode, and choose root access. Then type:
sudo mount -o rw,remount /
In terminal...
cd /etc/gdm3# change directory
sudo pico custom.conf# edit this file
Find and change:
#WaylandEnable=false
To this:
WaylandEnable=false
Save the file.
sudo dpkg-reconfigure gdm3# select gdm3 DM
Select gdm3 and OK.
reboot# reboot the computer
2. Update/reinstall the current nouveau/Nvidia video drivers.
Update #1:
While trying the wayland fix, errors indicated a gdm3 problem. Reinstalling gdm3 resolved the problem.
answered Aug 25 '18 at 13:51
heynnemaheynnema
18.8k22155
First, eliminate a possible disk file system problem...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode
- choose Root access
- at the # prompt, type
sudo fsck -f /
- repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted
- open a
terminalwindow - type
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
Next, eliminate a possible video subsystem problem...
At the GRUB menu, hit the e key, and edit the line that contains "splash quiet" to "splash quiet nomodeset", hit ctrl-x to continue booting. See if it will fully boot, even if the video display isn't at the correct resolution. If it boots, do one of the following...
1. Eliminate a possible wayland problem...
Boot to recovery mode, and choose root access. Then type:
sudo mount -o rw,remount /
In terminal...
cd /etc/gdm3# change directory
sudo pico custom.conf# edit this file
Find and change:
#WaylandEnable=false
To this:
WaylandEnable=false
Save the file.
sudo dpkg-reconfigure gdm3# select gdm3 DM
Select gdm3 and OK.
reboot# reboot the computer
2. Update/reinstall the current nouveau/Nvidia video drivers.
Update #1:
While trying the wayland fix, errors indicated a gdm3 problem. Reinstalling gdm3 resolved the problem.
answered Aug 25 '18 at 13:51
heynnemaheynnema
18.8k22155
edited Aug 25 '18 at 14:47
answered Aug 25 '18 at 13:51
heynnemaheynnema
18.8k22155
answered Aug 25 '18 at 13:51
heynnemaheynnema
18.8k22155
answered Aug 25 '18 at 13:51
heynnemaheynnema
18.8k22155
18.8k22155
fsck gives no errors, splash quiet is "quiet splash" in my file so I wrote "quiet splash nomodeset" and after ctrl+x the result is always the tty
– Questioner
Aug 25 '18 at 14:17
@Questioner what about the wayland fix and the video drivers?
– heynnema
Aug 25 '18 at 14:23
While doing the Wayland part, doing "sudo dpkg-reconfigure gdm3" gives: "gdm3 is ruined or not completely installed". Edit: That message made me think and so doing this steps I've solved the problem! 1- reedit custom.conf leaving #WaylandEnable=false 2- rebooted in normal mode 3- from tty1: sudo apt install gdm3 That's it, maybe the update broke gdm3
– Questioner
Aug 25 '18 at 14:40
@Questioner ah, there's your problem. Do "sudo apt-get update" and "sudo apt-get install gdm3" and "reboot". Please see the update to my answer, and accept it if it was helpful.
– heynnema
Aug 25 '18 at 14:45
Yes, already said in the edit
– Questioner
Aug 25 '18 at 14:50
add a comment |
fsck gives no errors, splash quiet is "quiet splash" in my file so I wrote "quiet splash nomodeset" and after ctrl+x the result is always the tty
– Questioner
Aug 25 '18 at 14:17
@Questioner what about the wayland fix and the video drivers?
– heynnema
Aug 25 '18 at 14:23
While doing the Wayland part, doing "sudo dpkg-reconfigure gdm3" gives: "gdm3 is ruined or not completely installed". Edit: That message made me think and so doing this steps I've solved the problem! 1- reedit custom.conf leaving #WaylandEnable=false 2- rebooted in normal mode 3- from tty1: sudo apt install gdm3 That's it, maybe the update broke gdm3
– Questioner
Aug 25 '18 at 14:40
@Questioner ah, there's your problem. Do "sudo apt-get update" and "sudo apt-get install gdm3" and "reboot". Please see the update to my answer, and accept it if it was helpful.
– heynnema
Aug 25 '18 at 14:45
Yes, already said in the edit
– Questioner
Aug 25 '18 at 14:50
fsck gives no errors, splash quiet is "quiet splash" in my file so I wrote "quiet splash nomodeset" and after ctrl+x the result is always the tty
– Questioner
Aug 25 '18 at 14:17
fsck gives no errors, splash quiet is "quiet splash" in my file so I wrote "quiet splash nomodeset" and after ctrl+x the result is always the tty
– Questioner
Aug 25 '18 at 14:17
@Questioner what about the wayland fix and the video drivers?
– heynnema
Aug 25 '18 at 14:23
@Questioner what about the wayland fix and the video drivers?
– heynnema
Aug 25 '18 at 14:23
While doing the Wayland part, doing "sudo dpkg-reconfigure gdm3" gives: "gdm3 is ruined or not completely installed". Edit: That message made me think and so doing this steps I've solved the problem! 1- reedit custom.conf leaving #WaylandEnable=false 2- rebooted in normal mode 3- from tty1: sudo apt install gdm3 That's it, maybe the update broke gdm3
– Questioner
Aug 25 '18 at 14:40
While doing the Wayland part, doing "sudo dpkg-reconfigure gdm3" gives: "gdm3 is ruined or not completely installed". Edit: That message made me think and so doing this steps I've solved the problem! 1- reedit custom.conf leaving #WaylandEnable=false 2- rebooted in normal mode 3- from tty1: sudo apt install gdm3 That's it, maybe the update broke gdm3
– Questioner
Aug 25 '18 at 14:40
@Questioner ah, there's your problem. Do "sudo apt-get update" and "sudo apt-get install gdm3" and "reboot". Please see the update to my answer, and accept it if it was helpful.
– heynnema
Aug 25 '18 at 14:45
@Questioner ah, there's your problem. Do "sudo apt-get update" and "sudo apt-get install gdm3" and "reboot". Please see the update to my answer, and accept it if it was helpful.
– heynnema
Aug 25 '18 at 14:45
Yes, already said in the edit
– Questioner
Aug 25 '18 at 14:50
Yes, already said in the edit
– Questioner
Aug 25 '18 at 14:50
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1068809%2fno-login-screen-after-ubuntu-18-04-update%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Welcome to Ask Ubuntu! Add the output of
dmesg --level=err,warnto your post.– abu_bua
Aug 25 '18 at 11:37
Done, I don't know why the Imgur quality I so low tough.
– Questioner
Aug 25 '18 at 11:50
Add the output of
lspci -knn | grep -i vga -A3, post as plain text.– abu_bua
Aug 25 '18 at 12:09