Open arvindautar opened 9 months ago
Some of the logs were not collected because they are 0 bytes in size. Additionally, the gathering of certain logs was not possible due to the inability to utilize the su
command for elevated permissions.
Could you please be more precise with your bug report?
What exactly were the symptoms? Also, since I believe your system is running now: What did you do to get to this point?
After installing Vanilla OS Orchid, the system encounters critical boot errors, including ACPI, PCI routing, cryptsetup, and Bluetooth errors. These errors prevent consistent booting. Occasionally, the system boots successfully.
Symptoms:
Boot Errors:
ACPI: Speculative return stack overflow and sleep state overrides. PCI: Errors indicating the inability to derive routing for PCI INT A. Cryptsetup: Failures related to invalid arguments. Bluetooth: UUID addition failures. Initramfs Prompt:
The system halts at the initramfs prompt, failing to locate or recognize the root filesystem. Intermittent Successful Boots:
Occasionally, the system boots successfully without errors.
This looks to me like severe hardware or driver issues.
No problems with VanillaOS Kinetic; I have moved to Fedora 39/40 without any issues. This is definitely an Orchid problem.
Hi !
First of congratulations on this beautiful release of VanillaOS Orchid, I really like what you guys have done!
After a recent installation of Vanilla OS Orchid, the system experienced a series of critical boot errors and system malfunctions. Initially, upon rebooting the system, several errors were reported, including a speculative return stack overflow, ACPI errors, PCI routing issues, and errors related to device-mapper, Bluetooth, and cryptsetup functionalities. These errors presented a considerable challenge in reaching the operating system's desktop environment or command line interface.
Subsequently, a reboot led the system to halt at the initramfs prompt, indicating a failure to locate or recognize the root filesystem, which could be due to the aforementioned errors impacting device recognition or encryption mechanisms managed by cryptsetup.
Interestingly, after an additional reboot attempt, the system booted successfully without any apparent errors, suggesting intermittent issues possibly related to hardware compatibility, kernel bugs, or misconfigurations affecting system stability and boot processes.
Please see the attached logs.tar.gz and pictures I took.
logs.tar.gz