You are not logged in.
Pages: 1
Hi all, noob here so apologies for any missing context. I'm attempting to install Arch as dual boot alongside an existing Windows installation, but am finding that when I boot with GRUB, I'm met with a frozen Arch login prompt. No input is accepted, including CTRL+ALT+F1,2,etc.
I've followed the installation instructions on the wiki for arch itself, GRUB, and NVIDIA, using `nvidia-open` for the graphics driver. No errors appear with `journalctl` other than the following:
ACPI BIOS Error (bug): Could not resolve symbol [\SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-330)
which I've read can be due to using hardware unsupported by your current drivers. I've already tried the `ibt=off` kernel param with the `nvidia` package and saw the same issue. Am I SOL with my current build?
Thanks in advance for any help. I can also provide additional context if needed, though grabbing actual logs is difficult since I cannot boot into arch itself and am debugging from the live USB alone.
Last edited by BlueSpin (2023-01-17 04:38:44)
Offline
I'm met with a frozen Arch login prompt. No input is accepted
No errors appear with `journalctl`
… errrr …
Do how do you run "journalctl"?
I cannot boot into arch itself and am debugging from the live USB alone
Did you chroot into the installed system?
Otherwise: https://wiki.archlinux.org/title/System … al_to_view
And paste the journal of a boot of the installed system to get us somewhere starting.
(See the 1st link below for "how")
which I've read
on the internet™ - ACPI errors are common because of wonky EFI/BIOS implementations - they're no problem per se.
Offline
Thanks for your reply. I have indeed been running `arch-chroot /mnt` (with the file system mounted at /mnt) from the install media, and running `journalctl` after that point to get the installed system logs.
I appreciate the info on using a pastebin as well. Here's the uploaded journal output: http://0x0.st/o7Rk.txt
Worth noting that GRUB itself seems to be acting strangely too. It shows up as a valid boot option in my BIOS, but when booted, does not show the grub menu and skips directly to loading Arch and kicking me to the frozen login screen mentioned before.
Offline
Jan 15 16:28:21 carterdesktoparch kernel: pci 0000:00:02.0: vgaarb: setting as boot VGA device
Jan 15 16:28:21 carterdesktoparch kernel: pci 0000:00:02.0: vgaarb: bridge control possible
Jan 15 16:28:21 carterdesktoparch kernel: pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
Jan 15 16:28:21 carterdesktoparch kernel: pci 0000:01:00.0: vgaarb: setting as boot VGA device (overriding previous)
Jan 15 16:28:21 carterdesktoparch kernel: pci 0000:01:00.0: vgaarb: bridge control possible
Jan 15 16:28:21 carterdesktoparch kernel: pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=noneThis is a hybrid graphics system, but only the nvidia chip is used.
Is i915 blacklisted?
Is there an output wired to the nvidia chip (if there's only the internal display of a notebook, the answer is "no")
Is there a parallel windows installation (3rd link below)
Chroot into the installed system, edit the mkinitcpio.conf, remove the "kms" HOOK and add "i915" to the MODULES list.
Rebuild the initramfs and see what happens.
Offline
Should I be using Nvidia Optimus then? This is a desktop with an integrated GPU, but I only wish to use the discrete Nvidia chip that I have my display connected to. The wiki mentioned that Optimus is only used for notebooks, so I wasn't sure it applied here.
There is a parallel windows installation, but I have already disabled fast boot, hibernation, and secure boot.
I updated mkinitcpio.conf as you specified and rebuilt initramfs with "mkinitcpio -P". Booting after that freezes at "starting systemd-udevd..." and doesn't reach the login prompt that was displaying before.
Offline
This is a desktop with an integrated GPU, but I only wish to use the discrete Nvidia chip that I have my display connected to.
In that case it would actually advisable to blacklist the i915 module and move the nvidia modules into the initramfs.
https://wiki.archlinux.org/title/Kernel … acklisting ("module_blacklist=i915" kernel parameter)
Though that seemed to have been the case anyway.
The journal stops rather early, though.
Can you boot the multi-user.target (2nd link below) along "nomodeset"?
If booting fails, do NOT reboot w/ the power button, but try to frenetically press ctrl+alt+del.
If that also fails, see https://wiki.archlinux.org/title/Keyboa … el_(SysRq)
Rebooting by cutting power will prevent the journal from getting written and we can't see what's exactly failing.
Offline
That did the trick; thank you! I was able to revert the systemd target change and nomodeset param without issue, so the problem must've been either the i915 module loading and borking the nvidia drivers, or the nvidia drivers not loading early enough in the boot process.
How common is this issue? Is every desktop build that includes an nvidia chip alongside an integrated GPU going to see the same problem? If so, it may be worth mentioning in the wiki. I didn't see these steps noted anywhere across the pages I was referencing.
Thanks again; I appreciate the help.
Offline
How common is this issue?
"recent" - but recently more often, probably because of https://bugzilla.kernel.org/show_bug.cgi?id=216303 which seems to be on the road to be fixed.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
Pages: 1