You are not logged in.
Pages: 1
Hello everyone,
This is my first post. I hope I won't make too many mistakes ;)
Please let me know if I do!
I just did a fresh install on my desktop after dropping a new AMD 6700XT into it and I think my GPU has something to do with it not booting since arch ran fine with my nvidia 1030.
I had to use the "nomodeset" Kernel parameter to boot the arch iso for installation.
I checked my fstab just to make sure it has the correct UUID and it does.
while booting I get the following output before it:
[ 0.003619] __common_interrupt: 1.55 No irq handler for vector
[ 0.003619] __common_interrupt: 2.55 No irq handler for vector
[ 0.003619] __common_interrupt: 3.55 No irq handler for vector
[ 0.003619] __common_interrupt: 4.55 No irq handler for vector
[ 0.003619] __common_interrupt: 5.55 No irq handler for vector
[ 0.003619] __common_interrupt: 6.55 No irq handler for vector
[ 0.003619] __common_interrupt: 7.55 No irq handler for vector
[ 0.003619] __common_interrupt: 8.55 No irq handler for vector
[ 0.003619] __common_interrupt: 9.55 No irq handler for vector
[ 0.003619] __common_interrupt: 10.55 No irq handler for vector
Starting version 248-5-arch
/dev/nvme0n1p2: clean, 49451/61014016 files, 4711445/244049585 blocks
I installed mesa, xf86-video-amdgpu, vulkan-radeon (not the git experimental)
There is no blacklisting in /etc/modeprobe.d/ going on.
Other people seem to be booting fine with this GPU.
Thank you in advance for taking time for my problem!
Last edited by MyArchAccount (2021-04-18 08:41:00)
Offline
I had to use the "nomodeset" Kernel parameter to boot the arch iso for installation.
That indicates you have firmware issues . The "No irq handler for vector" is also only solvable in firmware.
What brand & model is your motherboard and which firmware version are you running ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Hello Lone_Wolf,
Thank you for your fast reply!
I'm running a Gigabyte Aorus Master X570 with F30 (09/07/2020)
Offline
[1] shows there are atleast 2 later bios versions for that motherboard .
Incase you have rev 1.1 or rev 1.2 use [2] (although both revisions appear to share the firmware, better doublecheck)
Update the bios , then test again .
arch iso should be able to boot and show text without any special measures.
Welcome to Archlinux forums.
[1] https://www.gigabyte.com/Motherboard/X5 … rt-dl-bios
[2] https://www.gigabyte.com/Motherboard/X5 … rt-dl-bios
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I updated the BIOS to the newest version successfully but now my machine doesn't boot my internal drives any more. It sees them but does not boot them. I checked the BIOS option weather or not there was something going on with boot mode restriction (UEFI only, Legacy only). No luck. It's still no problem to boot the live usb. It's a dual bios board so I switched it into the backup bios which has the stock firmware on it and I get the same result. Not booting my internal drives (Win10 install and Arch).
I'll need some time to figure this out before coming back to the Arch specific problem...
I'll be back!
Thank you for your time!!
Offline
Perhaps check
dmesg | grep firmware # is the linux-firmware package installed?
lspci -k | grep -iA2 'vga\|display\|3d' # is the amdgpu kernel module in use?
Jin, Jîyan, Azadî
Offline
I'm back
Alright...
Could not figure out why the firmware was not booting the internal drives...
I just installed arch a new and now it is loading grub and letting me start the boot process.
I have no idea why the firmware UEFI implementation did not boot my disk before.
It is still not seeing my old Win10 install.
Somehow a new install does some "magic"...
the only output I get now is:
Starting version 248-5-arch
/dev/nvme0n1p2: clean, 44742/61014016 files, 4637698/244049585 blocks
And then it is just frozen again at that point.
The "no irq handler for vector" message is gone now.
I only installed base, linux and linux-firmware this time.
Offline
I'm back
I only installed base, linux and linux-firmware this time.
You need linux-firmware-git from the AUR and mesa-git from the AUR for the screen glitches you get after you have a working graphics cards from installing the linux-firmware-git package.
https://bbs.archlinux.org/viewtopic.php?id=264777
https://bbs.archlinux.org/viewtopic.php?id=265282
Last edited by Cphusion (2021-04-18 07:20:33)
Offline
Thank you Cephusion,
That resolved the issue! I'm happily booted into my arch install now!!
I was under the impression since I got basic text output during the beginning of the boot that it would work to display a tty without linux-firmware-git and mesa-git...
Can somenone explain to me why that was not the case?
Did the system boot after all but I did simply not get any graphical output?
I don't understand why this worked and would very much like to to!
Thanks to everyone who helped!
This was a great first experience of the forum!
Last edited by MyArchAccount (2021-04-18 08:42:15)
Offline
Thank you Cepusion,
Can somenone explain to me why that was not the case?
When you boot from the Arch live media you get the pcieeport driver, I think that's some basic driver good enough for basic display output without needing the
updated firmware. Read post #4 by loqs in the first topic I linked but in short the firmware for the graphics card is not yet in the linux-firmware package from the
default repositories, you didn't need the mesa-git for the graphics to work but to resolve screen glitches that show in the graphical environment. Someone else
here can most likely explain it better and in more detail than me. Also you didn't need to do a fresh reinstall after having switched from an Nvidia graphics card
to an AMD graphics card because it wasn't a problem with your installation but a problem with missing firmware for the graphics card.
Last edited by Cphusion (2021-04-18 09:05:30)
Offline
Pages: 1