You are not logged in.
Pages: 1
Hello Guys,
So, I'm trying to install Arch and I get this weird error,
"ACPI BIOS Error (bug): could not resolve symbol [\_SB.PCI0.GFX0.D02._BCL], AE_NOT_FOUND (20211217/psaargs-330)
ACPI Error: Aborting method \_SB.PCI0.PEG0.PEGP.DD02._BCL due to pervious error (AE_NOT_FOUND) (20211217/psparse-529)"
picture here
Thank you!
Offline
Does it prevent you from installing?
If not, go ahead and do the install.
If you have problems after that then come back here.
Offline
Does it prevent you from installing?
If not, go ahead and do the install.
If you have problems after that then come back here.
Yes it does prevent me from installing. if you look closely at the bottom of the picture you will find that it gives me a different shell from the Arch ISO one.
Offline
https://www.google.com/search?client=fi … hlinux.org
"rootfs site:bbs.archlinux.org"
Offline
https://www.google.com/search?client=fi … hlinux.org
"rootfs site:bbs.archlinux.org"
Already tried searching that, got no where sadly
Offline
As the picture you provided, the main problem is mounting the disk "ARCH_202207" instead of ACPI. Because the installation continued after the ACPI error (did not interrupted). Could you please provide the result of 'fdisk -l' or a disk list (with label and disk format)?
Offline
As the picture you provided, the main problem is mounting the disk "ARCH_202207" instead of ACPI. Because the installation continued after the ACPI error (did not interrupted). Could you please provide the result of 'fdisk -l' or a disk list (with label and disk format)?
The prompt shown in the picture does not have "fdisk" or "lsblk", the usb drive is also not shown in /dev/disk/by-id/.
Offline
I've tried to do enter installation with USB unmounted after the beep.
I think the problem may be about USB mounting.
[postimg.cc/rDnZnxRm]
Last edited by Prms-Prmt (2022-08-27 10:19:17)
Offline
I've tried to do enter installation with USB unmounted after the beep.
I think the problem may be about USB mounting.
[postimg.cc/rDnZnxRm]
Well, I cannot mount the usb drive as it is not really shown in the "/dev/disk/by-*/*".
in your screenshot the ISO is mounted successfully. mine does not.
Offline
Maybe you can use another USB port or USB drive? It could be about USB support issues. Or do you have any other methods to check USB mounting (like Rescue Disk or Another Computer)?
By the way, I unmounted the usb halfway installing and then mount it back quickly.
Last edited by Prms-Prmt (2022-08-27 10:30:16)
Offline
Maybe you can use another USB port or USB drive? It could be about USB support issues. Or do you have any other methods to check USB mounting (like Rescue Disk or Another Computer)?
By the way, I unmounted the usb halfway installing and then mount it back quickly.
I tried connecting another USB drive and also all tried all the ports, did not show up at all at "/dev/disk/by-*/*".
Offline
maybe https://www.cnblogs.com/eshizhan/archiv … 34822.html will be helpful for you.
via https://bbs.archlinux.org/viewtopic.php … 6#p1027586
Last edited by Prms-Prmt (2022-08-27 10:42:33)
Offline
maybe https://www.cnblogs.com/eshizhan/archiv … 34822.html will be helpful for you.
via https://bbs.archlinux.org/viewtopic.php … 6#p1027586
Checked them, did not help. Thank you though!
Offline
How did you create the installation USB? And How did you boot?
And could you please provide the result of 'ls /dev'?
Last edited by Prms-Prmt (2022-08-27 11:20:04)
Offline
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
How did you create the installation USB? And How did you boot?
And could you please provide the result of 'ls /dev'?
made the Installation drive using Rufus in windows, using both DD and ISO modes.
"ls /dev" output:
Offline
I tired everything in the #Troubleshooting, still nothing.
Offline
That includes renaming the iso to exactly ARCH_202207.iso then rewriting the usb stick with rufus ?
You are sure you renamed the label for the usb medium in windows to exactly ARCH_202207 ?
Last edited by Lone_Wolf (2022-08-27 12:05:41)
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 agree with Lone_Wolf, and also you could try Ventoy under Windows.
Check https://www.ventoy.net/en/index.html
Offline
That includes renaming the iso to exactly ARCH_202207.iso then rewriting the usb stick with rufus ?
Renaming the ISO file itself before DDing it into the usb?
the article said:
"try renaming your USB medium to ARCH_YYYYMM so Arch can find it. "
I renamed the ISO file to ARCH_202207 before DDing it om the USB, still same issue. it is not the USB i tired it on other devices, works fine.
Offline
I agree with Lone_Wolf, and also you could try Ventoy under Windows.
Check https://www.ventoy.net/en/index.html
Tried it already
Offline
Pages: 1