You are not logged in.
Pages: 1
All of a sudden Arch stopped booting. At first the booting stopped with a message about missing SOF firmware. I installed that but now, at the same spot, after reaching graphical interface target I get the following message:
i801_smbus 0000:00:1f.4: Transaction timeout
i801_smbus 0000:00:1f.4: Failed terminating, the transaction
i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
intel-spi 0000:00:1f.5: invalid resourceThe two problems may or may not be related. Only thing I have done, driver-wise, is that I installed the touchpad drivers as instructed here.
Offline
Now that I tried booting again I have a completely new list of errors. A long dump ending with:
usb 3-5: device descriptor read/64, error -71Then, a few times with almost the same message as in OP, with sometimes missing a line or three.
Offline
Were any other packages installed or updated along with sof-firmware such as linux-firmware or linux?
Offline
Were any other packages installed or updated along with sof-firmware such as linux-firmware or linux?
No. I booted with a stick, cloned the SOF repo and installed it manually without doing anything else in between.
Offline
I misunderstood the issue. When the system first stopped booting, was that the first boot after a kernel or firmware update?
Can you switch to a different tty and log in?
Offline
When the system first stopped booting, was that the first boot after a kernel or firmware update?
No. Only did stuff in the user space.
Can you switch to a different tty and log in?
I don't know. How do I do that? I managed to get in from the installer stick, though.
Offline
Ctrl + Alt + F2 to try and switch tty. You could also try changing the default target to boot into by adding the option from the boot loader.
If those do not work from the installation media, please post the journal of a failed boot. To do that, after chrooting in post the journal of the previous boot to a pastebin.
Offline
You could also try changing the default target to boot into by adding the option from the boot loader.
I managed to switch tty and changed the target to 'rescue'. That target was reached and could log in.
Edit: I set the target by systemctl set-default.
Last edited by Keyboard_Crasher (2021-12-03 01:02:24)
Offline
What display environment starts up when graphical.target is reached? Please post the log for it failing to start up.
Offline
What display environment starts up when graphical.target is reached?
There are no lines between 'Reached target Graphical Interface' and the error messages I posted earlier. I rebooted two times since your last message and the first time the process just froze after that message, and the second time received the same lines as in OP minus the last two.
Please post the log for it failing to start up.
There isn't much to post unless you mean some other log than the one printed on the screen.
Is the boot sequence deterministic? Could the next target be inferred from a list of sequential targets?
Offline
I meant what display environment have you installed and enabled on the system.
For the log either the journal for a boot with issue or the output of dmesg plus the contents of xorg.log.
Offline
Problem solved! I read the X log and found a syntax error in my touchpad configuration file. I copy-pasted the example from here and the example had ellipsis.
...
Lesson learned: never copy-paste stuff from the internet without reading it through. Even if it's from the second best wiki out there.
Thank you very much for helping out!
Offline
Pages: 1