Ubuntu won't boot without nomodeset on Thinkpad T570 (intel)
Clash Royale CLAN TAG#URR8PPP up vote
2
down vote
favorite
I was running Ubuntu 17.10, and after upgrading the packages, the system stopped booting. Grub displays fine but after pressing enter, I see "_" at the top left of the screen, and shortly after that the screen goes totally black (when I'd expect prompt for my encrypted drive password).
So far I've tried:
- downgrading grub to version before the upgrade
- previous kernel
- upgrading to 18.04
- testing Ubuntu 18.04 and Mint ISO installers, which also don't boot
- testing newest Fedora ISO, which boots and works fine (including proper graphics drivers and external monitors)
Adding nomodeset makes it possible to boot, but is less than ideal because then xorg uses generic drivers that are slow, and don't allow me to use external monitors.
I was also able to boot once without nomodeset, and it booted ok, but froze after couple of seconds with red artifacts. I can't reproduce that anymore, there's just the blank screen.
With no splash screen, the last message I see is:
[drm] memory usable by graphics device = 4096M
switching to inteldrmfb from EFI VGA
Then, there's the infinite blank screen.
I have a Thinkpad T570 with Intel Graphics.
Being a Linux user since 2005, and having spent hours on this -- I'm not sure what else to try. Any help would be greatly appreciated.
boot drivers grub2 intel-graphics thinkpad
asked Mar 18 at 12:43
Matt
215
add a comment |Â
up vote
2
down vote
favorite
I was running Ubuntu 17.10, and after upgrading the packages, the system stopped booting. Grub displays fine but after pressing enter, I see "_" at the top left of the screen, and shortly after that the screen goes totally black (when I'd expect prompt for my encrypted drive password).
So far I've tried:
- downgrading grub to version before the upgrade
- previous kernel
- upgrading to 18.04
- testing Ubuntu 18.04 and Mint ISO installers, which also don't boot
- testing newest Fedora ISO, which boots and works fine (including proper graphics drivers and external monitors)
Adding nomodeset makes it possible to boot, but is less than ideal because then xorg uses generic drivers that are slow, and don't allow me to use external monitors.
I was also able to boot once without nomodeset, and it booted ok, but froze after couple of seconds with red artifacts. I can't reproduce that anymore, there's just the blank screen.
With no splash screen, the last message I see is:
[drm] memory usable by graphics device = 4096M
switching to inteldrmfb from EFI VGA
Then, there's the infinite blank screen.
I have a Thinkpad T570 with Intel Graphics.
Being a Linux user since 2005, and having spent hours on this -- I'm not sure what else to try. Any help would be greatly appreciated.
boot drivers grub2 intel-graphics thinkpad
asked Mar 18 at 12:43
Matt
215
Did you check askubuntu.com/questions/162075/… ?
– ubfan1
Mar 18 at 15:43
@ubfan1 yes, and none of the workarounds mentioned here: wiki.ubuntu.com/X/Troubleshooting/BlankScreen#How_It_Works works. Only nomodeset does the trick. I also can't really check any of the logs, because it happens before my filesystem gets mounted (I'm sure about that, because it's encrypted and it happens before asking for password)
– Matt
Mar 18 at 17:47
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I was running Ubuntu 17.10, and after upgrading the packages, the system stopped booting. Grub displays fine but after pressing enter, I see "_" at the top left of the screen, and shortly after that the screen goes totally black (when I'd expect prompt for my encrypted drive password).
So far I've tried:
- downgrading grub to version before the upgrade
- previous kernel
- upgrading to 18.04
- testing Ubuntu 18.04 and Mint ISO installers, which also don't boot
- testing newest Fedora ISO, which boots and works fine (including proper graphics drivers and external monitors)
Adding nomodeset makes it possible to boot, but is less than ideal because then xorg uses generic drivers that are slow, and don't allow me to use external monitors.
I was also able to boot once without nomodeset, and it booted ok, but froze after couple of seconds with red artifacts. I can't reproduce that anymore, there's just the blank screen.
With no splash screen, the last message I see is:
[drm] memory usable by graphics device = 4096M
switching to inteldrmfb from EFI VGA
Then, there's the infinite blank screen.
I have a Thinkpad T570 with Intel Graphics.
Being a Linux user since 2005, and having spent hours on this -- I'm not sure what else to try. Any help would be greatly appreciated.
boot drivers grub2 intel-graphics thinkpad
asked Mar 18 at 12:43
Matt
215
I was running Ubuntu 17.10, and after upgrading the packages, the system stopped booting. Grub displays fine but after pressing enter, I see "_" at the top left of the screen, and shortly after that the screen goes totally black (when I'd expect prompt for my encrypted drive password).
So far I've tried:
- downgrading grub to version before the upgrade
- previous kernel
- upgrading to 18.04
- testing Ubuntu 18.04 and Mint ISO installers, which also don't boot
- testing newest Fedora ISO, which boots and works fine (including proper graphics drivers and external monitors)
Adding nomodeset makes it possible to boot, but is less than ideal because then xorg uses generic drivers that are slow, and don't allow me to use external monitors.
I was also able to boot once without nomodeset, and it booted ok, but froze after couple of seconds with red artifacts. I can't reproduce that anymore, there's just the blank screen.
With no splash screen, the last message I see is:
[drm] memory usable by graphics device = 4096M
switching to inteldrmfb from EFI VGA
Then, there's the infinite blank screen.
I have a Thinkpad T570 with Intel Graphics.
Being a Linux user since 2005, and having spent hours on this -- I'm not sure what else to try. Any help would be greatly appreciated.
boot drivers grub2 intel-graphics thinkpad
boot drivers grub2 intel-graphics thinkpad
asked Mar 18 at 12:43
Matt
215
asked Mar 18 at 12:43
Matt
215
edited Mar 18 at 18:01
asked Mar 18 at 12:43
Matt
215
asked Mar 18 at 12:43
Matt
215
asked Mar 18 at 12:43
Matt
215
215
Did you check askubuntu.com/questions/162075/… ?
– ubfan1
Mar 18 at 15:43
@ubfan1 yes, and none of the workarounds mentioned here: wiki.ubuntu.com/X/Troubleshooting/BlankScreen#How_It_Works works. Only nomodeset does the trick. I also can't really check any of the logs, because it happens before my filesystem gets mounted (I'm sure about that, because it's encrypted and it happens before asking for password)
– Matt
Mar 18 at 17:47
add a comment |Â
Did you check askubuntu.com/questions/162075/… ?
– ubfan1
Mar 18 at 15:43
@ubfan1 yes, and none of the workarounds mentioned here: wiki.ubuntu.com/X/Troubleshooting/BlankScreen#How_It_Works works. Only nomodeset does the trick. I also can't really check any of the logs, because it happens before my filesystem gets mounted (I'm sure about that, because it's encrypted and it happens before asking for password)
– Matt
Mar 18 at 17:47
Did you check askubuntu.com/questions/162075/… ?
– ubfan1
Mar 18 at 15:43
Did you check askubuntu.com/questions/162075/… ?
– ubfan1
Mar 18 at 15:43
@ubfan1 yes, and none of the workarounds mentioned here: wiki.ubuntu.com/X/Troubleshooting/BlankScreen#How_It_Works works. Only nomodeset does the trick. I also can't really check any of the logs, because it happens before my filesystem gets mounted (I'm sure about that, because it's encrypted and it happens before asking for password)
– Matt
Mar 18 at 17:47
@ubfan1 yes, and none of the workarounds mentioned here: wiki.ubuntu.com/X/Troubleshooting/BlankScreen#How_It_Works works. Only nomodeset does the trick. I also can't really check any of the logs, because it happens before my filesystem gets mounted (I'm sure about that, because it's encrypted and it happens before asking for password)
– Matt
Mar 18 at 17:47
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
The problem turned out to be faulty RAM. I've sent it to Lenovo, and after three weeks they sent it back. Ubuntu boots properly now.
answered Mar 21 at 16:14
Matt
215
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
The problem turned out to be faulty RAM. I've sent it to Lenovo, and after three weeks they sent it back. Ubuntu boots properly now.
answered Mar 21 at 16:14
Matt
215
add a comment |Â
up vote
1
down vote
accepted
The problem turned out to be faulty RAM. I've sent it to Lenovo, and after three weeks they sent it back. Ubuntu boots properly now.
answered Mar 21 at 16:14
Matt
215
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
The problem turned out to be faulty RAM. I've sent it to Lenovo, and after three weeks they sent it back. Ubuntu boots properly now.
answered Mar 21 at 16:14
Matt
215
The problem turned out to be faulty RAM. I've sent it to Lenovo, and after three weeks they sent it back. Ubuntu boots properly now.
answered Mar 21 at 16:14
Matt
215
edited May 1 at 13:10
answered Mar 21 at 16:14
Matt
215
answered Mar 21 at 16:14
Matt
215
answered Mar 21 at 16:14
Matt
215
215
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1016985%2fubuntu-wont-boot-without-nomodeset-on-thinkpad-t570-intel%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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
Did you check askubuntu.com/questions/162075/… ?
– ubfan1
Mar 18 at 15:43
@ubfan1 yes, and none of the workarounds mentioned here: wiki.ubuntu.com/X/Troubleshooting/BlankScreen#How_It_Works works. Only nomodeset does the trick. I also can't really check any of the logs, because it happens before my filesystem gets mounted (I'm sure about that, because it's encrypted and it happens before asking for password)
– Matt
Mar 18 at 17:47