Forum › Forums › New users › New Users and General Questions › Booting from ISO: X server crashes [solved]
- This topic has 6 replies, 5 voices, and was last updated Mar 13-6:34 am by rachelgomez123.
-
AuthorPosts
-
November 27, 2022 at 7:34 pm #94253Member
berndE
Hi everybody,
this is my first try with antix (I’m presently running MX). I downloaded the latest full ISO, put it on a USB stick and booted. The system started, but the X server crashed immediately.
Here is the output:X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
Build Operating System: linux Debian
Current Operating System: Linux antix1 4.9.0-326-antix.1-amd64-smp #1 SMP PREEMPT Fri Aug 26 21:21:08 EEST 2022 x86_64
Kernel command line: BOOT_IMAGE=/antiX/vmlinuz quiet splasht disable=lxF lang=de_DE kbd=de tz=Europe/Berlin
Build Date: 10 November 2021 11:00:13AM
xorg-server 2:1.20.11-1.0nosystemd1 (https://www.debian.org/support)
Current version of pixman: 0.40.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (–) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: “/home/demo/.local/share/xorg/Xorg.0.log”, Time: Fri Nov 25 14:12:54 2022
(==) Using config directory: “/etc/X11/xorg.conf.d”
(==) Using system config directory “/usr/share/X11/xorg.conf.d”
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
(EE)
Fatal server error:
(EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at “/home/demo/.local/share/xorg/Xorg.0.log” for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server errorHere are what I think are the relevant system informations:
System: Kernel: 5.18.0-4mx-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: Xfce 4.16.0
tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.16.1 vt: 7 dm: LightDM 1.26.0
Distro: MX-21.2.1_ahs_x64 Wildflower August 28 2022 base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: <filter>
Mobo: ASUSTeK model: PRIME B450M-A II v: Rev X.0x serial: <filter>
BIOS: American Megatrends v: 3002 date: 03/10/2021
Battery: Message: No system battery data found. Is one present?
Memory: RAM: total: 31.26 GiB used: 1.89 GiB (6.0%)
RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU: Info: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2 rev: 0 cache:
L2: 4 MiB bogomips: 114987
Speed: 2195 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 2195 2: 2195
3: 2195 4: 2195 5: 2194 6: 2196 7: 2196 8: 2196 9: 2196 10: 2195 11: 2196 12: 2155
13: 2479 14: 2193 15: 2196 16: 2196
Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1 bmi2 bpext cat_l3
cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy constant_tsc cpb cpuid cqm cqm_llc
cqm_mbm_local cqm_mbm_total cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists extapic
extd_apicid f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb ibs irperf
lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor movbe msr mtrr mwaitx
nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae pat pausefilter pclmulqdq
pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pni popcnt pse pse36 rapl
rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep sev sev_es sha_ni skinit smap smca
smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp succor svm svm_lock syscall tce topoext
tsc tsc_scale umip v_spec_ctrl v_vmsave_vmload vgif vmcb_clean vme vmmcall wbnoinvd wdt
xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
Graphics: Device-1: NVIDIA GP108 [GeForce GT 1030] vendor: ASUSTeK driver: nvidia v: 510.85.02
bus-ID: 09:00.0 chip-ID: 10de:1d01 class-ID: 0300
Display: x11 server: X.Org 1.20.14 compositor: xfwm4 v: 4.16.1 driver: loaded: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv resolution: 1920×1080~60Hz
s-dpi: 96
System: Kernel: 5.18.0-4mx-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: Xfce 4.16.0
tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.16.1 vt: 7 dm: LightDM 1.26.0
Distro: MX-21.2.1_ahs_x64 Wildflower August 28 2022 base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: <filter>
Mobo: ASUSTeK model: PRIME B450M-A II v: Rev X.0x serial: <filter>
BIOS: American Megatrends v: 3002 date: 03/10/2021
Battery: Message: No system battery data found. Is one present?
Memory: RAM: total: 31.26 GiB used: 1.89 GiB (6.0%)
RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU: Info: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2 rev: 0 cache:
L2: 4 MiB bogomips: 114987
Speed: 2195 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 2195 2: 2195
3: 2195 4: 2195 5: 2194 6: 2196 7: 2196 8: 2196 9: 2196 10: 2195 11: 2196 12: 2155
13: 2479 14: 2193 15: 2196 16: 2196
Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1 bmi2 bpext cat_l3
cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy constant_tsc cpb cpuid cqm cqm_llc
cqm_mbm_local cqm_mbm_total cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists extapic
extd_apicid f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb ibs irperf
lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor movbe msr mtrr mwaitx
nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae pat pausefilter pclmulqdq
pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pni popcnt pse pse36 rapl
rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep sev sev_es sha_ni skinit smap smca
smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp succor svm svm_lock syscall tce topoext
tsc tsc_scale umip v_spec_ctrl v_vmsave_vmload vgif vmcb_clean vme vmmcall wbnoinvd wdt
xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
Graphics: Device-1: NVIDIA GP108 [GeForce GT 1030] vendor: ASUSTeK driver: nvidia v: 510.85.02
bus-ID: 09:00.0 chip-ID: 10de:1d01 class-ID: 0300
Display: x11 server: X.Org 1.20.14 compositor: xfwm4 v: 4.16.1 driver: loaded: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv resolution: 1920×1080~60Hz
s-dpi: 96
OpenGL: renderer: NVIDIA GeForce GT 1030/PCIe/SSE2 v: 4.6.0 NVIDIA 510.85.02
direct render: Yes
OpenGL: renderer: NVIDIA GeForce GT 1030/PCIe/SSE2 v: 4.6.0 NVIDIA 510.85.02
direct render: YesI think it has to do with the nvidia options. Any ideas?
– Bernd
November 27, 2022 at 9:43 pm #94267Moderator
caprea
::You are using the ahs version of MX (kernel 5.18)because this is very recent hardware. antiX per default boots a kernel for old hardware (kernel 4.9)during the live session. If you have downloaded antiX full version there is at least the possibility to choose a more modern kernel (kernel 5.10) on the boot screen.In the advanced options iirc.That’s the first I would try.
November 27, 2022 at 11:37 pm #94276Memberstevesr0
::Hi berndE and caprea,
Just had this same problem for the second time. I had previously solved it <g> as caprea suggested by selecting the “modern” kernel from the “advanced options” menu, which opens a menu that includes a chance to change the kernel selection. Today, I forgot the solution until I found this post
Worked a charm.
Thanks, caprea (and berndE for posting).
stevesr0
November 28, 2022 at 3:00 pm #94327Member
berndE
March 11, 2023 at 4:03 am #101675Memberrab-bits
::On a Dell Inspiron 3582, I have the failed-to-set-IOPL-problem after installing full Antix 22 (live worked fine). Kernel 4.9 works, whereas X will not start with 5.10:
[ 159.419] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
[ 159.419] vesa: Ignoring device with a bound kernel driver
[ 159.419] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 159.419] (EE) Screen 0 deleted because of no matching config section.
[ 159.419] (II) UnloadModule: “vesa”
[ 159.419] (EE) Device(s) detected, but none match those in the config file.
[ 159.419] (EE)
Fatal server error:
[ 159.419] (EE) no screens found(EE)
[ 159.419] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 159.419] (EE) Please also check the log file at “/home/flem/.local/share/xorg/Xorg.0.log” for additional information.
[ 159.419] (EE)
[ 159.465] (EE) Server terminated with error (1). Closing log file.*-display
description: VGA compatible controller
product: GeminiLake [UHD Graphics 600]
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 03
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:128 memory:a0000000-a0ffffff memory:90000000-9fffffff ioport:f000(size=64) memory:c0000-dffff
/March 11, 2023 at 5:57 am #101677Memberrab-bits
::To remove the permission problem I ran:
sudo vesa: Ignoring device with a bound kernel driver
But, then the vesa-driver made problems whan I ran startx:
[ 209.416] (II) LoadModule: “vesa”
[ 209.416] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 209.416] (II) Module vesa: vendor=”X.Org Foundation”
[ 209.416] compiled for 1.20.9, module version = 2.5.0
[ 209.416] Module class: X.Org Video Driver
[ 209.416] ABI class: X.Org Video Driver, version 24.1
[ 209.416] (II) VESA: driver for VESA chipsets: vesa
[ 209.416] (++) using VT number 1[ 209.416] vesa: Ignoring device with a bound kernel driver
[ 209.416] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 209.416] (EE) Screen 0 deleted because of no matching config section.
[ 209.416] (II) UnloadModule: “vesa”
[ 209.416] (EE) Device(s) detected, but none match those in the config file.
[ 209.416] (EE)
Fatal server error:March 13, 2023 at 6:34 am #101904Memberrachelgomez123
::Generating a backtrace when some specific action is making the X server crash (manually)
Start XWin using your normal method.
In a non-X terminal window, run gdb –pid=pidof /usr/bin/XWin, to attach gdb to the running X server.
Type c at the (gdb) prompt, to resume running the X server.
Reproduce your crash.Regards,
Rachel Gomez -
AuthorPosts
- You must be logged in to reply to this topic.