[Ubuntu-x-swat] [Bug 2002432] Re: X11 not started during boot (intel: waited 2020 ms for i915.ko driver to load)

2023-03-12 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.laun

[Ubuntu-x-swat] [Bug 2002432] Re: X11 not started during boot (intel: waited 2020 ms for i915.ko driver to load)

2023-01-11 Thread Daniel van Vugt
If the original problem is still present then please follow the instructions in comment #3. If it is not still present then we can close the bug. I am also skeptical that you need to create any i915.conf or xorg.conf files because it sounds like those were the cause of the bug. -- You received t

[Ubuntu-x-swat] [Bug 2002432] Re: X11 not started during boot (intel: waited 2020 ms for i915.ko driver to load)

2023-01-11 Thread Marian Minar
Hello Daniel, Thanks you for you attention. During night I fixed the issue. I decided to update from 22.04 -> 22.10 Ubuntu. Then I added settings of module in conf file /etc/modprobe.d/i915.conf and automatically generated /etc/X11/xorg.conf file. I will send them later. Other hand was troubles

[Ubuntu-x-swat] [Bug 2002432] Re: X11 not started during boot (intel: waited 2020 ms for i915.ko driver to load)

2023-01-10 Thread Daniel van Vugt
Please also remember to delete /root/xorg.conf.new -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/2002432 Title: X11 not started during boot (intel: waited 2020 ms for i915.k

[Ubuntu-x-swat] [Bug 2002432] Re: X11 not started during boot (intel: waited 2020 ms for i915.ko driver to load)

2023-01-10 Thread Daniel van Vugt
Also your logs are all from recovery mode so that explains why there's no working graphics driver there. Can you provide a log from a non-recovery boot? Try: journalctl -b-1 > prevboot1.txt journalctl -b-2 > prevboot2.txt journalctl -b-3 > prevboot3.txt and attach the resulting text files