Welcome!
Forum users
  • Please read this before asking for help, and don't forget to add Quick System Info to help requests!
  • Please follow the Forum Rules

Current releases
--MX-19.4 release info here
--Migration information to MX-19.4 here
--antiX-19.4 (Grup Yorum) release info here

Important information
-- Spectre and Meltdown vulnerabilities

News
-- MX Linux on social media: here
-- New Forum Features, Marking Solved and Referencing a User: here

Boot with no GUI issue  [Solved]

Post Reply
Message
Author
palacca
Posts: 6
Joined: Mon Sep 13, 2021 6:55 pm

Boot with no GUI issue

#1 Post by palacca »

Hi to everyone,
I'm using antiX19.4 (Debian 10) with 4.9.0-264-antix.1-amd64-smp kernel.
My mobo is Biostar P4M800-M7A rev7.0, with:
Intel Pentium 4 521
Integrated graphics S3 UniChrome Pro

In recent days, when booting the machine it alternates between GUI and not GUI boot. So sometimes I boot the computer and as it ends boot log I get the login page but without GUI, only text based.
If I run runlevel I get "N 5". Here is the boot log when this happened:

Code: Select all

Sun Sep 12 22:02:35 2021: [....] Checking file systems...fsck from util-linux 2.33.1
Sun Sep 12 22:02:35 2021: boot: clean, 341/32768 files, 19187/131072 blocks
Sun Sep 12 22:02:36 2021: homeantiX: clean, 16447/15532032 files, 1467594/62110464 blocks
Sun Sep 12 22:02:36 2021: ??7[ ok 8??done.
Sun Sep 12 22:02:36 2021: [info] Loading kernel module lp.
Sun Sep 12 22:02:36 2021: [info] Loading kernel module ppdev.
Sun Sep 12 22:02:36 2021: [info] Loading kernel module parport_pc.
Sun Sep 12 22:02:36 2021: [info] Loading kernel module loop.
Sun Sep 12 22:02:36 2021: [info] Loading kernel module it87.
Sun Sep 12 22:02:36 2021: [....] Mounting local filesystems...??7[ ok 8??done.
Sun Sep 12 22:02:37 2021: [....] Activating swapfile swap...??7[ ok 8??done.
Sun Sep 12 22:02:37 2021: [....] Cleaning up temporary files...??7[ ok 8??.
Sun Sep 12 22:02:37 2021: [....] Starting Setting kernel variables: sysctl??7[ ok 8??.
Sun Sep 12 22:02:37 2021: [....] Setting up resolvconf...??7[ ok 8??done.
Sun Sep 12 22:02:37 2021: [....] Skip starting firewall: ufw (not enabled)...??7[ ok 8??done.
Sun Sep 12 22:02:38 2021: [....] Configuring network interfaces in background... ??7[ ok 8??done.
Sun Sep 12 22:02:38 2021: [....] Starting RPC port mapper daemon: rpcbind??7[ ok 8??.
Sun Sep 12 22:02:38 2021: [....] Starting NFS common utilities: statd idmapd??7[ ok 8??.
Sun Sep 12 22:02:39 2021: [....] Cleaning up temporary files...??7[ ok 8??.
Sun Sep 12 22:02:39 2021: [....] Setting up ALSA...??7[ ok 8??done.
Sun Sep 12 22:02:39 2021: [....] Setting sensors limits...??7[ ok 8??done.
Sun Sep 12 22:02:39 2021: [....] Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix??7[ ok 8??.
Sun Sep 12 22:02:39 2021: INIT: Entering runlevel: 5
Sun Sep 12 22:02:39 2021: [info] Using makefile-style concurrent boot in runlevel 5.
Sun Sep 12 22:02:39 2021: [....] Setting up console font and keymap...??7[ ok 8??done.
Sun Sep 12 22:02:39 2021: [....] Starting enhanced syslogd: rsyslogd??7[ ok 8??.
Sun Sep 12 22:02:40 2021: [....] Enabling power management...??7[ ok 8??done.
Sun Sep 12 22:02:40 2021: [....] Starting ACPI services: acpid??7[ ok 8??.
Sun Sep 12 22:02:40 2021: [....] Starting anac(h)ronistic cron: anacron??7[ ok 8??.
Sun Sep 12 22:02:40 2021: [....] Starting periodic command scheduler: cron??7[ ok 8??.
Sun Sep 12 22:02:40 2021: [....] Starting system message bus: dbus??7[ ok 8??.
Sun Sep 12 22:02:41 2021: [....] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon??7[ ok 8??.
Sun Sep 12 22:02:41 2021: [....] Starting bluetooth: bluetoothd??7[ ok 8??.
Sun Sep 12 22:02:41 2021: [....] Starting Connection Manager:??7[ ok 8??.
Sun Sep 12 22:02:42 2021: [....] Starting Common Unix Printing System: cupsd??7[ ok 8??.
Sun Sep 12 22:02:42 2021: [....] Starting Bluetooth DUN daemon: dundee??7[ ok 8??.
Sun Sep 12 22:02:43 2021: [....] Starting session management daemon: elogind??7[ ok 8??.
Sun Sep 12 22:02:43 2021: [....] Starting mouse interface server: gpm??7[ ok 8??.
Sun Sep 12 22:02:43 2021: [....] Starting NTP server: ntpd??7[ ok 8??.
Sun Sep 12 22:02:44 2021: [....] Starting oFono Mobile Telephony Daemon: ofonod??7[ ok 8??.
Sun Sep 12 22:02:44 2021: [....] Starting SANE network scanner server: saned??7[ ok 8??.
Sun Sep 12 22:02:45 2021: [....] Starting slim: slim??7[ ok 8??.
Sun Sep 12 22:02:45 2021: [....] Starting OpenBSD Secure Shell server: sshd??7[ ok 8??.
The runlevel seems fine, so does the "Starting slim ... [ok]" log. compared to when computer boots with GUI the boot log seems the same.
What I noticed is that it generally does the "no GUI boot" after I left my pc powered off for a longer time (a few hours).
As a new user I have no more ideas about how to solve, or understand, this issue. Thanks for your time.

palacca
Posts: 6
Joined: Mon Sep 13, 2021 6:55 pm

Re: Boot with no GUI issue

#2 Post by palacca »

Just noticed that after that boot log, when entering no-GUI login, first 2 log lines are added:

Code: Select all

Applying power save settings...done.
VirtualBox Additions disabled, not in a Virtual Machine??7[ ok 8??.
Are power save settings related to the issue, in case how can i disable them? Is there any config file?

User avatar
nXecure
Posts: 108
Joined: Sat Jun 12, 2021 3:41 am

Re: Boot with no GUI issue

#3 Post by nXecure »

Next time you boot into gui, share the

Code: Select all

inxi -Fxz
output. We cannot guess what graphic module is being loaded with the info provided.
antiX Live system enthusiast.
General Live Boot Parameters for antiX/MX.

palacca
Posts: 6
Joined: Mon Sep 13, 2021 6:55 pm

Re: Boot with no GUI issue

#4 Post by palacca »

Code: Select all

System:    Host: antix-palacca Kernel: 4.9.0-264-antix.1-amd64-smp x86_64 bits: 64 
           compiler: gcc v: 8.3.0 Desktop: IceWM 2.7.0 dm: SLiM 
           Distro: antiX-19.4_x64-full Grup Yorum 20 May 2021 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: N/A model: P4M800CE-8237 serial: <superuser required> 
           BIOS: Phoenix v: 6.00 PG date: 03/07/2006 
CPU:       Info: Single Core model: Intel Pentium 4 bits: 64 type: MT 
           arch: Netburst Smithfield rev: 9 cache: L2: 1024 KiB 
           flags: lm nx pae sse sse2 sse3 bogomips: 11168 
           Speed: 2792 MHz min/max: N/A Core speeds (MHz): 1: 2792 2: 2792 
Graphics:  Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] 
           vendor: Biostar Microtech Intl Corp driver: N/A bus-ID: 01:00.0 
           chip-ID: 1106:3344 
           Display: x11 server: X.Org 1.20.4 driver: loaded: openchrome 
           unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz s-dpi: 96 
           OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 compat-v: 3.1 
           direct render: Yes 
Audio:     Device-1: VIA VT8233/A/8235/8237 AC97 Audio vendor: Biostar Microtech Intl Corp 
           driver: snd_via82xx v: kernel bus-ID: 00:11.5 chip-ID: 1106:3059 
           Sound Server-1: ALSA v: k4.9.0-264-antix.1-amd64-smp running: yes 
           Sound Server-2: PulseAudio v: 12.2 running: no 
Network:   Device-1: VIA VT6102/VT6103 [Rhine-II] driver: via-rhine v: N/A port: e400 
           bus-ID: 00:12.0 chip-ID: 1106:3065 
           IF: eth0 state: down mac: 00:16:ec:6d:b5:b7 
           IF-ID-1: usb0 state: unknown speed: N/A duplex: N/A mac: ce:44:b5:84:3d:af 
Bluetooth: Device-1: Samsung GT-I9070 (network tethering USB debugging enabled) type: USB 
           driver: rndis_host v: kernel bus-ID: 1-1:8 chip-ID: 04e8:6864 
           Device-2: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB 
           driver: btusb v: 0.8 bus-ID: 3-1:5 chip-ID: 0a12:0001 
           Report: ID: hci0 rfk-id: 0 state: up address: 00:10:60:A2:17:0D bt-v: 1.1 
           lmp-v: 1.1 sub-v: 20d 
Drives:    Local Storage: total: 298.09 GiB used: 13.51 GiB (4.5%) 
           ID-1: /dev/sda vendor: Hitachi model: HDT725032VLA380 size: 298.09 GiB 
           speed: <unknown> serial: VFJ204R82LKS0H 
Partition: ID-1: / size: 58.04 GiB used: 5.71 GiB (9.8%) fs: ext4 dev: /dev/dm-0 
           mapped: root.fsm 
           ID-2: /boot size: 487.9 MiB used: 50.9 MiB (10.4%) fs: ext4 dev: /dev/sda1 
           ID-3: /home size: 232.21 GiB used: 7.75 GiB (3.3%) fs: ext4 dev: /dev/dm-1 
           mapped: 1.home.fsm 
Swap:      ID-1: swap-1 type: partition size: 1.36 GiB used: 332 KiB (0.0%) priority: -1 
           dev: /dev/dm-2 mapped: swap 
Sensors:   System Temperatures: cpu: 59.0 C mobo: 54.0 C 
           Fan Speeds (RPM): cpu: 9642 fan-2: 0 
           Power: 12v: N/A 5v: N/A 3.3v: N/A vbat: 4.08 
Info:      Processes: 201 Uptime: 1h 32m Memory: 1.89 GiB used: 1.24 GiB (65.4%) 
           Init: SysVinit v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 
           Packages: apt: 1688 Shell: Bash v: 5.0.3 running-in: roxterm inxi: 3.3.06

User avatar
Huckleberry Finn
Qualified MX Guide
Posts: 6503
Joined: Sat Jun 22, 2019 8:35 am

Re: Boot with no GUI issue

#5 Post by Huckleberry Finn »

Graphics: Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro]
vendor: Biostar Microtech Intl Corp driver: N/A
When asking for help, please first: Menu => MX Tools => Quick System Info
.
The output is copied into the clipboard automatically including code tags for the forum
So, please do not manually copy but only paste in your post

User avatar
nXecure
Posts: 108
Joined: Sat Jun 12, 2021 3:41 am

Re: Boot with no GUI issue  [Solved]

#6 Post by nXecure »

Huckleberry Finn wrote: Wed Sep 15, 2021 6:36 am Graphics: Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro]
vendor: Biostar Microtech Intl Corp driver: N/A
This is the normal for VIA chips with openchrome xorg video module. (they are not supported in the linux kernel)

In this very long antiX forum thread, various users study the problems of VIA and SIS based graphic chips.
So much so I had to create a respin with older xorg drivers to better support VIA graphics (older versions means less security updates, but works better).

@palacca, If the openchrome xorg module works most of the time for you, keep it like that. This driver is no longer truly supported.
Next time it doesn't start the graphical interface, try to see if restarting the display manager will start it (login in terminal and run

Code: Select all

sudo service slim restart
or stop and then start)
antiX Live system enthusiast.
General Live Boot Parameters for antiX/MX.

Post Reply

Return to “antiX”