X.org failure preventing boot, Intel graphics
ryan...@ryantate.com
Hash: SHA512
Putting Qubes 3.2 on an a X.1 Carbon 5th gen with Intel 620 graphics, I hit X11 issues with the installer ("X Startup failed, falling back to text mode") but managed to install via a Kickstart file. My understanding and hope was that X issues would be easier to resolve on an installed system.
Now when Qubes tries to boot the result, unsurprisingly, is an X server error, "no screens found (EE)." Then the boot proceeds but hangs after "Started Accounts Service," which I believe is related to the X failure, based on some Googling around.
Booting into the install DVD, [Troubleshooting/Rescue a Qubes system], I was able to mount the filesystem and obtain a more detailed log, pasted below, which clarifies this to "Screen(s) found, but none have a usable configuration."
Maybe my Intel graphics are too new for this X?
Is there any way to install a newer X without being able to actually boot into Qubes?
Or should I try installing Intel graphics drivers directly somehow? (Intel offers them at: https://01.org/linuxgraphics/downloads/2017q1-intel-graphics-stack-recipe)
In prior posts in this group I have read suggestions of trying different Kernels. But when I select Advanced options from the Qubes boot screen, I only get one option. Is there another kernel install method I should be trying?
Thanks for any help.
Xorg.9.log:
[ 14.202]
X.Org X Server 1.18.3
Release Date: 2016-04-04
[ 14.202] X Protocol Version 11, Revision 0
[ 14.202] Build Operating System: 4.4.9-300.fc23.x86_64
[ 14.202] Current Operating System: Linux dom0 4.4.14-11.pvops.qubes.x86_64 #1 SMP Tue Jul 19 01:14:58 UTC 2016 x86_64
[ 14.202] Kernel command line: placeholder root=/dev/mapper/qubes-root ro rd.luks.uuid=luks-71a413ff-2178-4a3b-9c47-2b8a1dbaa373 rd.lvm.lv=qubes/root rd.lvm.lv=qubes/swap i915.preliminary_hw_support=1 rd.driver.pre=scsi_dh_rdac rhgb quiet
[ 14.202] Build Date: 30 June 2016 11:04:38PM
[ 14.202] Build ID: xorg-x11-server 1.18.3-3.fc23
[ 14.202] Current version of pixman: 0.34.0
[ 14.203] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 14.203] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 14.203] (==) Log file: "/var/log/Xorg.9.log", Time: Wed May 24 17:25:07 2017
[ 14.204] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 14.204] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 14.205] (==) No Layout section. Using the first Screen section.
[ 14.205] (==) No screen section available. Using defaults.
[ 14.205] (**) |-->Screen "Default Screen Section" (0)
[ 14.205] (**) | |-->Monitor "<default monitor>"
[ 14.206] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 14.206] (==) Automatically adding devices
[ 14.206] (==) Automatically enabling devices
[ 14.206] (==) Automatically adding GPU devices
[ 14.206] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 14.206] (==) FontPath set to:
catalogue:/etc/X11/fontpath.d,
built-ins
[ 14.206] (==) ModulePath set to "/usr/lib64/xorg/modules"
[ 14.206] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 14.206] (II) Loader magic: 0x81ce00
[ 14.206] (II) Module ABI versions:
[ 14.206] X.Org ANSI C Emulation: 0.4
[ 14.206] X.Org Video Driver: 20.0
[ 14.206] X.Org XInput driver : 22.1
[ 14.206] X.Org Server Extension : 9.0
[ 14.206] (--) using VT number 2
[ 14.206] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 14.210] (--) PCI:*(0:0:2:0) 8086:5916:17aa:224f rev 2, Mem @ 0xeb000000/16777216, 0x60000000/268435456, I/O @ 0x0000e000/64, BIOS @ 0x????????/131072
[ 14.210] (II) LoadModule: "glx"
[ 14.211] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[ 14.222] (II) Module glx: vendor="X.Org Foundation"
[ 14.222] compiled for 1.18.3, module version = 1.0.0
[ 14.222] ABI class: X.Org Server Extension, version 9.0
[ 14.222] (==) AIGLX enabled
[ 14.222] (==) Matched intel as autoconfigured driver 0
[ 14.222] (==) Matched modesetting as autoconfigured driver 1
[ 14.222] (==) Matched fbdev as autoconfigured driver 2
[ 14.223] (==) Matched vesa as autoconfigured driver 3
[ 14.223] (==) Assigned the driver to the xf86ConfigLayout
[ 14.223] (II) LoadModule: "intel"
[ 14.223] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
[ 14.225] (II) Module intel: vendor="X.Org Foundat
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJZJmIMAAoJEEkbtfGeQYQR9cAP/3Oc9PWLBAVCyH/vVYP81fGH
VOH7EeXYCBFvHzLIyr2g03JOdYS09mX6fTTOnuEWGKb+lIOjRYdLbGk2T0pw40KN
w5QxwKdXXJ4H4PTJjcTKN0yUv29q5/9foRPIwlQGtrCnHY3ZvYV4tLMsWYFnwibR
2JWxhwwwoiGU8bOEzcgu0T8CJ4qMVkN8Gqx5ZW+4DiN/3EOEXao2qvcoSmU54hEk
o0QriWrvSVjF9cuFN1+/bWrBGxFPDvLQkNu+3fPHubjYnc1KT1SfBgY6EGmi2UHy
TDSdP8jFwr8zd1Q4Gxfa+f7461dO2AaBn85XvmgNw0exu1JSbqYTc8bdDL+o/BS1
ZWVDMPugB3LKnyfMkoXErK95ljRsUOrdX74uMyrVItfiMmyOW9jWXsh3bSCP4aoR
6Pz1S6ydEfeK9ChVsVjkeEMoXDjUK+LABZEYXYWDuvh43njuRX3GOxyqH+R/R9MS
/NJVoU3Pb76cfCnJAsd4o7+c1qA8mJ+KfW5lSLlz3ch3S9q1pB7OX4cFebUaGcQh
sY6BGGbJ2RbfX0wrg4xfqY8+o+ZcQ5vGj0iI8Yw8mO8lZIFVBM3DNVsSkSH84eNt
+DyahBO/RY/KpNQuWYVf9lg7qhYpzPamXHrMsNimIe/r8rChpVVmzY2Jahc+lyjK
7Y/3AVbYd9s92i9Xe55e
=lOdr
-----END PGP SIGNATURE-----
ryan...@ryantate.com
Hash: SHA512
[ 14.225] compiled for 1.18.0, module version = 2.99.917
[ 14.225] Module class: X.Org Video Driver
[ 14.225] ABI class: X.Org Video Driver, version 20.0
[ 14.225] (II) LoadModule: "modesetting"
[ 14.225] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[ 14.226] (II) Module modesetting: vendor="X.Org Foundation"
[ 14.226] compiled for 1.18.3, module version = 1.18.3
[ 14.226] Module class: X.Org Video Driver
[ 14.226] ABI class: X.Org Video Driver, version 20.0
[ 14.226] (II) LoadModule: "fbdev"
[ 14.226] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
[ 14.226] (II) Module fbdev: vendor="X.Org Foundation"
[ 14.226] compiled for 1.17.99.901, module version = 0.4.3
[ 14.226] Module class: X.Org Video Driver
[ 14.226] ABI class: X.Org Video Driver, version 20.0
[ 14.226] (II) LoadModule: "vesa"
[ 14.226] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[ 14.227] (II) Module vesa: vendor="X.Org Foundation"
[ 14.227] compiled for 1.17.99.901, module version = 2.3.2
[ 14.227] Module class: X.Org Video Driver
[ 14.227] ABI class: X.Org Video Driver, version 20.0
[ 14.227] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 14.227] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[ 14.227] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[ 14.227] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
[ 14.227] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 14.227] (II) FBDEV: driver for framebuffer: fbdev
[ 14.227] (II) VESA: driver for VESA chipsets: vesa
[ 14.238] (EE) open /dev/dri/card0: No such file or directory
[ 14.238] (WW) Falling back to old probe method for modesetting
[ 14.238] (EE) open /dev/dri/card0: No such file or directory
[ 14.238] (II) Loading sub module "fbdevhw"
[ 14.238] (II) LoadModule: "fbdevhw"
[ 14.238] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[ 14.238] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 14.238] compiled for 1.18.3, module version = 0.0.2
[ 14.238] ABI class: X.Org Video Driver, version 20.0
[ 14.238] (EE) open /dev/fb0: No such file or directory
[ 14.238] (WW) Falling back to old probe method for fbdev
[ 14.238] (II) Loading sub module "fbdevhw"
[ 14.238] (II) LoadModule: "fbdevhw"
[ 14.238] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[ 14.238] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 14.238] compiled for 1.18.3, module version = 0.0.2
[ 14.238] ABI class: X.Org Video Driver, version 20.0
[ 14.238] (EE) open /dev/fb0: No such file or directory
[ 14.239] (EE) Screen 0 deleted because of no matching config section.
[ 14.239] (II) UnloadModule: "modesetting"
[ 14.239] (EE) Screen 0 deleted because of no matching config section.
[ 14.239] (II) UnloadModule: "fbdev"
[ 14.239] (II) UnloadSubModule: "fbdevhw"
[ 14.239] (II) Loading sub module "vbe"
[ 14.239] (II) LoadModule: "vbe"
[ 14.239] (II) Loading /usr/lib64/xorg/modules/libvbe.so
[ 14.239] (II) Module vbe: vendor="X.Org Foundation"
[ 14.239] compiled for 1.18.3, module version = 1.1.0
[ 14.239] ABI class: X.Org Video Driver, version 20.0
[ 14.239] (II) Loading sub module "int10"
[ 14.239] (II) LoadModule: "int10"
[ 14.239] (II) Loading /usr/lib64/xorg/modules/libint10.so
[ 14.242] (II) Module int10: vendor="X.Org Foundation"
[ 14.242] compiled for 1.18.3, module version = 1.0.0
[ 14.242] ABI class: X.Org Video Driver, version 20.0
[ 14.242] (II) VESA(0): initializing int10
[ 14.244] (EE) VESA(0): V_BIOS address 0x80a40 out of range
[ 14.244] (II) UnloadModule: "vesa"
[ 14.244] (II) UnloadSubModule: "int10"
[ 14.244] (II) Unloading int10
[ 14.244] (II) UnloadSubModule: "vbe"
[ 14.244] (II) Unloading vbe
[ 14.244] (EE) Screen(s) found, but none have a usable configuration.
[ 14.244] (EE)
Fatal server error:
[ 14.244] (EE) no screens found(EE)
[ 14.244] (EE)
Please consult the Fedora Project support
at http://wiki.x.org
for help.
[ 14.244] (EE) Please also check the log file at "/var/log/Xorg.9.log" for additional information.
[ 14.244] (EE)
[ 14.246] (EE) Server terminated with error (1). Closing log file.
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJZJmN3AAoJEEkbtfGeQYQRjo0P/A7SZE5T1l5ac/fjFcijozkC
A6rVt27VlS6WQ0cU2My7dk3IwniqWzIvR2NvlxkjDkuvNwIdpplnV9KWGhX+DTMz
MfAFkyUNhCIR8rDKlPRMXnV3M4b2/r5WBCWuxThsevK9FELTxPK+4W+IJztxLdFE
yHiPS5y+k9OSoGOja0tOUGXGz0XxFtmTvG/g3vtVL4lxDQUbFHJopkXHzoVG44xM
uN5gBjKHBteamvgZ/GszlmF78xLqjZBcXw73vN9do1z2MKsXoQQUFC5eB/vF28QX
t+Xr10Cjdj14XNJoVSnoJ/NPuatBoBt+v25VODkNLQhewKxhpYx5M6FExfZjnEaz
IC77p0zYpvCNN/kWAa0GxFM5BP3og8n6OuuRywZCha/WuW0DfLHctB/aaAaYvqc/
z8teS/Qk45D1IEULubat+BZVlkzOp63I3aZqdgqa3JkXHU6lt/jk7yWPDn87FkEq
PQUZ8ZB/PDMjLOkrlrlyNnaRqpOhANrrh2/WWNU1u/8EzWZGpWOsIGgin1pEdT/s
FLdK8Igl7JJ6vPgSTXWCZV4c5FeEqejJN6TDCZ9LhElBA6yTGG7kKXS5pSB+wMGA
AdBMC7HG16wK2D86DxTt6j4RdHGkNokmo+jjAHhtb3SejYdCs35OzX7do/0U+tfe
1MbynEkmBfbdAowxqMjX
=k50x
-----END PGP SIGNATURE-----
Ryan Tate
>
> Maybe my Intel graphics are too new for this X?
So I am wondering if this is really about Xorg, since presumably this has the same X server as Qubes 3.2 dom0, which is also fedora 23.
Could this somehow be specific to Xen or Qubes?
I plan to continue to invest time in this, so if anyone has an idea what my next investigative step should be, do let me know. Thanks for reading….
Ryan Tate
>
> So I made a fedora 23 live usb and was able to boot into fine on the same system. No X issues, full GUI.
>
Newer kernels also seem to work. My testing:
qubes3.2 kernel 4.4.14-11 graphics-no wifi-untested (fedora23)
fedora23 kernel 4.2.3-300 graphics-yes wifi-no
fedora24 kernel 4.5.5-300 graphics-yes wifi-no
fedora25 kernel 4.8.6-300 graphics-yes wifi-yes
Any clue how to get Qubes dom0 booting into a different kernel, without being able to actually boot into dom0 (just the boot welcome screen)?
I don’t think I’ll be able to get the NIC working given the above results but I could copy a different kernel onto /boot from removable media (certainly from rescue mode in CD). Then I imagine I’d need to change not just grub settings but also Xen settings somewhere? Bit out of my depth.
Thanks for any pointers.
Ryan Tate
>
> Ah, it turns out I was able to boot when using same fedora but different (older) kernel (4.2.3).
cooloutac
you might have to build your own iso after all man.
Vít Šesták
1. Boot in rescue mode.
2. chroot
3. systemctl mask lightdm # this will prevent X from starting
4. Boot in Qubes (without X11)
5. Update kernel using qubes-dom0-update, ideally to the one from current-testing (e.g., qubes-dom0-update --enablerepo=qubes-dom0-current-testing kernel.
I am not 100% sure with the commands etc., I am writing them by heart.
Alternatively, you could try booting Qubes with kernel from Fedora 25. I don't recommend using it this way (Qubes adds some hardening for kernel), but it might be useful for booting in Qubes in order to install newer kernel from repositories.
Regards,
Vít Šesták 'v6ak'
Ryan Tate
> On May 27, 2017, at 3:35 AM, Vít Šesták <groups-no-private-mail--con...@v6ak.com> wrote:
>
> Are you able to connect the laptop via ethernet? If so, you might try something like?
>
> 1. Boot in rescue mode.
> 2. chroot
> 3. systemctl mask lightdm # this will prevent X from starting
> 4. Boot in Qubes (without X11)
> 5. Update kernel using qubes-dom0-update, ideally to the one from current-testing (e.g., qubes-dom0-update --enablerepo=qubes-dom0-current-testing kernel.
1. I booted, waited for it to hang, then hit Ctrl-Alt-F2 (or technically Ctlr-Alt-Fn-F2 on this machine)
2. Luckily was able to get text login from there. Logged in as root.
3. I found `systemctl mask lightdm` did not do the trick, nor did removing and masking display-manager. What seemed to work was `systemctl set-default multi-user.target`. Anyway, in the end I was trying all three and my recollection is that only when I tried all three did the boot proceed to the end without needing to be interrupted. NOTE, there was *always* an X server error — I think this is due to how the Qubes installer works, I am guessing it launches X independent of Fedora — but with these settings the rest of the boot proceeded.
(In my mind, letting the boot go to the end maximized the chance of being able to update and salvage the system. In the end, I don’t know if any of this was necessary; it’s possible the below would have worked simply from hitting Ctrl-Alt-F2.)
4. su user
qvm-create -t fedora-23 -n netvm --label purple
qubes-prefs default-netvm netvm
qubes-prefs updatevm netvm
qvm-start netvm
5. At this point I plugged in a USB-Ethernet adapter. Netvm was showing no connection via curl. I found my Ethernet controller via lspci and assigned to the netvm via (sudo?) `qvm-pci -a netvm 00:1f.6`. This was sufficient; I did not need to assign USB for whatever reason. Only at this point was I able to successfully run a curl to remote server within the netvm.
6. I was getting just "failed to synchronize cache for repo” errors when trying to run the qubes-dom0-update commands. So on a lark I tried `qvm-run netvm 'yum upgrade' -p` and installed everything suggested.
7. sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
(Worked!)
8. Reboot
9. Qubes launched into X to finish setup. Yay. I got some kind of error twice but retrying eventually fixed. When I clicked Finished Configuration button in the lower right, I was booting into text again, so I reverted all my prior changes:
rm /etc/systemd/system/lightdm.service
rm /etc/systemd/system/display-manager.service
ln -s /usr/lib/systemd/system/lightdm.service /etc/systemd/system/lightdm.service
ln -s /usr/lib/systemd/system/lightdm.service /etc/systemd/system/display-manager.service
systemctl set-default graphical.target
reboot
10. Qubes launches! At this point I struggle mightily to get the USB-Ethernet working again, including by deleting my old netvm to make sure it wouldn’t interefere with sys-net, making sure sys-net has the same ethernet controller (yup), turning on sys-usb, resetting sys-net. I never did get it working but meanwhile I’m waiting for the weird Lenovo mini-ethernet adapter to come so I can just use the ethernet port.
11. However in the meantime it turns out I have wifi! Success.
Eager for 4.0 but in the meantime I have a nice running Qubes.
Vít Šesták
Regards,
Vít Šesták 'v6ak'
Ryan Tate
> On Jun 10, 2017, at 2:39 AM, Vít Šesták <groups-no-private-mail--con...@v6ak.com> wrote:
>
> Good to hear it helps. Fronm “without being able to actually boot into Qubes?”, I wrongly assumed you are unable to switch to a different tty.