[SOLVED] Lost video after enabling Wake On Lan in BIOS
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am unsure which forum this should be posted into. I think the issue is a change I made in the BIOS resulting in no video/no reboot after powering off then on, but it could be a coincidental hardware failure. Please move if this is not best place. (Also thought I had already posted this, but can't find it, so hope it is not a duplicate)
-------------------
Well, I managed to pull the pin on a grenade. I was trying to solve a connectivity issue, and was following this wiki
Ztcoracat, thanks for yours. There is no way to get into BIOS without video. When power turned on, fans spin, but absolutely no video output, no beeps, no lights by eth cable on back of computer with or without hitting BIOS boot key (F12). Mobo light on at all times, and when pressed, the case power key lights up, but nothing further except the fans coming on and staying on.
I have no idea whether this is as a result of my BIOS change, or whether it is a purely co-incidental hardware issue. Now trying to trouble shoot the latter, so any ideas welcome.
I have no idea whether this is as a result of my BIOS change, or whether it is a purely co-incidental hardware issue.
Are you suspicious that your GPU died?
I'm thinking that if you have your Ubuntu install disk try booting that up and set it to nomodset mode, download and install the drivers and etc.
Thanks for all the great suggestions, however here is an update:
This just keeps careening around. Decided to try a SVGA cable and it works fine. Gets video to monitor, so looks like either the video card DVI circuit, the DVI cable, or the DVI port/circuit in the monitor has gone toes up. Will buy another DVI cable tomorrow and see if that is it. In the meantime, will continue with the SVGA.
That's the good(?) news. The bad is that it has stopped dual booting and will only boot into Windows. So either,
the previously unused, but 2 year old SSD has crashed (it does not show up in Windows file explorer), or
the bootloader isn't facilitating a dual boot.
The former seems the less likely (plus I am unsure how to test a SSD), so I suspect the bootloader?
With this information, any modifications to priorities in the last three posts, or should I try to troubleshoot the bootloader?
Last edited by Odyssey1942; 11-20-2018 at 04:35 PM.
Thanks for all the great suggestions, however here is an update:
This just keeps careening around. Decided to try a SVGA cable and it works fine. Gets video to monitor, so looks like either the video card DVI circuit, the DVI cable, or the DVI port/circuit in the monitor has gone toes up. Will buy another DVI cable tomorrow and see if that is it. In the meantime, will continue with the SVGA.
That's the good(?) news. The bad is that it has stopped dual booting and will only boot into Windows. So either,
the previously unused, but 2 year old SSD has crashed (it does not show up in Windows file explorer), or
the bootloader isn't facilitating a dual boot.
The former seems the less likely (plus I am unsure how to test a SSD), so I suspect the bootloader?
With this information, any modifications to priorities in the last three posts, or should I try to troubleshoot the bootloader?
You can 're-install Grub' with your Ubuntu CD/DVD.
UPDATE: By pressing F12 during the boot process that now results in a Windows boot, a screen comes up:
Boot mode is set to UEFI with Legacy OPROM, secure boot off
-----
UEFI:
Windows Boot Mgr (if selected, boots into Windows)
Ubuntu (if selected boots into Grub Screen and I select Ubuntu, it boots into UM18.04).
The good news is that (1) the SSD seems to be OK and (2) the grub screen is still there, bad news is that the computer does not boot into the Grub screen.
The other good news is that it narrows down what needs to be fixed, i.e., booting directly into the grub screen. How do I do this?
If I read this correctly you say you select a boot order with F12. That order selects the drive/loader the bios knows about. To change default then change default hard drive order in bios.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.