Only Windows is launching on the system.

132

08-02-2018, 11:14 AM

Hey everyone, I’m running Nebora Linux alongside Windows on two separate SSDs. Recently, after using Windows for a while, I tried booting into my Nebora installation but ran into an issue. The Grub menu appeared normally, yet I received the error "[0.001359] __common_interrupt: 1.55 Nor irq handler for vector" before the screen went dark permanently. I also tested booting other OSes like Arch, Debian, and Ubuntu from a USB stick, but the problem persisted. Could you help figure out what might be causing this or suggest a fix? Hardware specs: CPU – AMD Ryzen 2700x, GPU – AMD Radeon Vega, 64MB RAM, Asus Prime B450-Plus, boot drive – HP EX900 120GB.

Dizconnected

08-02-2018, 11:14 AM #1

B4DBLUE2
Junior Member

08-04-2018, 06:56 PM

Activate CSM in your BIOS and turn off Secure Boot. The single drive split works well for Windows messing with Linux.

B4DBLUE2

08-04-2018, 06:56 PM #2

Activate CSM in your BIOS and turn off Secure Boot. The single drive split works well for Windows messing with Linux.

LouisPizarro
Member

08-11-2018, 07:30 AM

I just attempted it but the issue persists. Additionally, it doesn’t clarify why I’m unable to boot other distributions from an external USB drive.

LouisPizarro

08-11-2018, 07:30 AM #3

I just attempted it but the issue persists. Additionally, it doesn’t clarify why I’m unable to boot other distributions from an external USB drive.

Lorddoom139
Posting Freak

956

08-11-2018, 08:31 AM

This might assist you—see the links provided.

Lorddoom139

08-11-2018, 08:31 AM #4

This might assist you—see the links provided.

Suzi_YT
Junior Member

08-17-2018, 01:47 PM

Sadly, those suggestions didn’t resolve the issue for me. I believe the error isn’t related to my inability to boot into any operating system—others with the same message were still able to start their OS.

Suzi_YT

08-17-2018, 01:47 PM #5

jokertv10
Junior Member

08-17-2018, 03:17 PM

Consider switching to safe mode or removing the GPU driver you used. It might have been a solution in another forum. Also, try resetting the BIOS settings.

jokertv10

08-17-2018, 03:17 PM #6

Consider switching to safe mode or removing the GPU driver you used. It might have been a solution in another forum. Also, try resetting the BIOS settings.

frankyd84
Member

08-18-2018, 12:24 AM

When the first option doesn't work, EasyBCD can be used instead.

frankyd84

08-18-2018, 12:24 AM #7

When the first option doesn't work, EasyBCD can be used instead.

rareeline
Junior Member

08-18-2018, 12:55 AM

Windows quick launch? I’ve seen it activate after every Windows update. Fast startup is often blamed for messing up Linux dual-boot setups. Link

rareeline

08-18-2018, 12:55 AM #8

Windows quick launch? I’ve seen it activate after every Windows update. Fast startup is often blamed for messing up Linux dual-boot setups. Link