Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Can you help me understand? I bought a new motherboard in 2014 (MSI). At the time I had no troubles installing pretty much any distro. After a Manjaro fail last fall, I installed Windows - mostly for work. Now I want to have a dual boot setup. After installing new versions, Grub2 won't load the Linux install (tried 3 distros), but loads Windows fine. I have an old OpenSuse disk and it installed just fine. So my question is why? Is there some advance in linux that makes my system obsolete? Would a new motherboard solve the problem? Thanks.
Using an install disk, linux (Debian, MX, Manjaro, Mageia, Tumbleweed) installs successfully. Upon restart and every time afterward, choosing the distro or distro Safe mode leads to an attempted start, blank screen, computer restart, and back to the bootloader menu. This cycle repeats as long as I keep trying either option. HOWEVER, when I choose Windows 10, it starts right away and runs perfectly. Same thing with OpenSuse 13.2. All Secure Boot options are disable in BIOS.
Motherboard: MSI A78M-E35
BIOS: E7721AMS v30.6
Just in case it might be helpful:
Boot Override
- SATA2: HL-DT-ST DVDRAM GH22N550
- UEFI: Builtin EFI Shell
- SATA1: ST1000DM003-ISB102
- WD 1600BEVExternal 1.02
- UEFI: WD 1600BEVExternal 1.02
There are some issues with some distros. Early "atom" chips didn't have opcodes (CMOOV?). In my dad's case, ubuntu would fail, debian would not. There's also 64 bit versus 32 bit (" lm " in /proc/cpuinfo and it's 64 bit capable). And various other CPU "extras" that might be default for many distros and not available on your hardware. Media extensions, virtualization, and such. Theres also many firmware's that need loading and might not be installed by default. Debian buster needed some amdgpu firmware (firmware-amd-graphics) or it didn't activate the external monitor (not part of the laptop) to login on. Granted that I start with minimal installs and not curated experiences.
at the grub menu press e for edit and add nomodeset to the end of the line that begins with linux. What is your video card?
One last question: Editing within Grub doesn't save the change. I have to edit every time I go in. Is there a command to Save? Otherwise, do I use the terminal to edit and save?
But many distros will overwrite this file (new kernel version / upgrade / and other instances). So there's some /etc/default/grub to have certain things happen when a new grub.cfg is auto-[re]generated (update-grub). YMMV.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.