Lost my desktop

bushy · April 05, 2019, 01:15:26 AM

This is what I got from systemctl
UNIT LOAD ACTIVE SUB DESCRIPTION
● systemd-backlight@backlight:intel_backlight.service loaded failed failed Load/Save Screen Backlight Brightness of backlight:intel_backlight
● systemd-journal-flush.service loaded failed failed Flush Journal to Persistent Storage

LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.

2 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

Here's what I finally got from journalctl

Code Select

-- Logs begin at Thu 2019-04-04 16:00:31 EDT, end at Thu 2019-04-04 19:55:38 EDT. --
Apr 04 18:05:46 guy-pc systemd[1039]: Listening on Sound System.
Apr 04 18:05:46 guy-pc systemd[1039]: Listening on GnuPG network certificate management daemon.
Apr 04 18:05:46 guy-pc systemd[1039]: Starting D-Bus User Message Bus Socket.
Apr 04 18:05:46 guy-pc systemd[1039]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 04 18:05:46 guy-pc systemd[1039]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Apr 04 18:05:46 guy-pc systemd[1039]: Reached target Paths.
Apr 04 18:05:46 guy-pc systemd[1039]: Listening on GnuPG cryptographic agent and passphrase cache.
Apr 04 18:05:46 guy-pc systemd[1039]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Apr 04 18:05:46 guy-pc systemd[1039]: Reached target Timers.
Apr 04 18:05:46 guy-pc systemd[1039]: Listening on D-Bus User Message Bus Socket.
Apr 04 18:05:46 guy-pc systemd[1039]: Reached target Sockets.
Apr 04 18:05:46 guy-pc systemd[1039]: Reached target Basic System.
Apr 04 18:05:46 guy-pc systemd[1039]: Reached target Default.
Apr 04 18:05:46 guy-pc systemd[1039]: Startup finished in 140ms.
Apr 04 18:05:46 guy-pc systemd[1039]: Started D-Bus User Message Bus.
Apr 04 18:05:48 guy-pc dbus-daemon[1058]: [session uid=1000 pid=1058] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.6' (uid=1000 pid=1086 comm="/usr/bin/openbox --config-file /home/guy/.config/o")
Apr 04 18:05:48 guy-pc systemd[1039]: Starting Virtual filesystem service...
Apr 04 18:05:48 guy-pc dbus-daemon[1058]: [session uid=1000 pid=1058] Successfully activated service 'org.gtk.vfs.Daemon'
Apr 04 18:05:48 guy-pc systemd[1039]: Started Virtual filesystem service.
Apr 04 18:05:48 guy-pc systemd[1039]: Starting Sound Service...
Apr 04 18:05:49 guy-pc systemd[1039]: Started Sound Service.
Apr 04 18:05:49 guy-pc dbus-daemon[1058]: [session uid=1000 pid=1058] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.14' (uid=1000 pid=1100 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Apr 04 18:05:49 guy-pc systemd[1039]: Starting Virtual filesystem service - disk device monitor...
Apr 04 18:05:50 guy-pc dbus-daemon[1058]: [session uid=1000 pid=1058] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Apr 04 18:05:50 guy-pc systemd[1039]: Started Virtual filesystem service - disk device monitor.
Apr 04 18:05:50 guy-pc dbus-daemon[1058]: [session uid=1000 pid=1058] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.14' (uid=1000 pid=1100 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Apr 04 18:05:50 guy-pc systemd[1039]: Starting Virtual filesystem service - digital camera monitor...
Apr 04 18:05:50 guy-pc dbus-daemon[1058]: [session uid=1000 pid=1058] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Apr 04 18:05:50 guy-pc systemd[1039]: Started Virtual filesystem service - digital camera monitor.
Apr 04 18:05:50 guy-pc dbus-daemon[1058]: [session uid=1000 pid=1058] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.14' (uid=1000 pid=1100 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Apr 04 18:05:50 guy-pc systemd[1039]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
Apr 04 18:05:50 guy-pc dbus-daemon[1058]: [session uid=1000 pid=1058] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Apr 04 18:05:50 guy-pc systemd[1039]: Started Virtual filesystem service - GNOME Online Accounts monitor.
Apr 04 18:05:50 guy-pc dbus-daemon[1058]: [session uid=1000 pid=1058] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.14' (uid=1000 pid=1100 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Apr 04 18:05:50 guy-pc systemd[1039]: Starting Virtual filesystem service - Apple File Conduit monitor...
Apr 04 18:05:50 guy-pc gvfs-afc-volume-monitor[1222]: Volume monitor alive
Apr 04 18:05:50 guy-pc dbus-daemon[1058]: [session uid=1000 pid=1058] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Apr 04 18:05:50 guy-pc systemd[1039]: Started Virtual filesystem service - Apple File Conduit monitor.
Apr 04 18:05:50 guy-pc dbus-daemon[1058]: [session uid=1000 pid=1058] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.14' (uid=1000 pid=1100 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Apr 04 18:05:50 guy-pc systemd[1039]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
Apr 04 18:05:50 guy-pc dbus-daemon[1058]: [session uid=1000 pid=1058] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Apr 04 18:05:50 guy-pc systemd[1039]: Started Virtual filesystem service - Media Transfer Protocol monitor.
Apr 04 18:29:01 guy-pc pulseaudio[1153]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Apr 04 18:29:01 guy-pc pulseaudio[1153]:       after 17 requests (17 known processed) with 0 events remaining.
Apr 04 18:29:01 guy-pc systemd[1039]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE
Apr 04 18:29:01 guy-pc systemd[1039]: pulseaudio.service: Failed with result 'exit-code'.
Apr 04 18:29:01 guy-pc systemd[1039]: run-rpc_pipefs.mount: Succeeded.
Apr 04 18:29:01 guy-pc systemd[1039]: pulseaudio.service: Service RestartSec=100ms expired, scheduling restart.
Apr 04 18:29:01 guy-pc systemd[1039]: pulseaudio.service: Scheduled restart job, restart counter is at 1.
Apr 04 18:29:01 guy-pc systemd[1039]: Stopped Sound Service.
Apr 04 18:29:01 guy-pc systemd[1039]: Starting Sound Service...
Apr 04 18:29:01 guy-pc pulseaudio[2993]: W: [pulseaudio] pid.c: Stale PID file, overwriting.
Apr 04 18:29:01 guy-pc systemd[1039]: Started Sound Service.
Apr 04 18:30:31 guy-pc systemd[1039]: Stopped target Default.
Apr 04 18:30:31 guy-pc systemd[1039]: Stopping Virtual filesystem service - disk device monitor...
Apr 04 18:30:31 guy-pc systemd[1039]: Stopping Virtual filesystem service - digital camera monitor...
Apr 04 18:30:31 guy-pc systemd[1039]: Stopping Virtual filesystem service - Apple File Conduit monitor...
Apr 04 18:30:31 guy-pc systemd[1039]: Stopping Virtual filesystem service...
Apr 04 18:30:31 guy-pc systemd[1039]: Stopping Sound Service...
Apr 04 18:30:31 guy-pc systemd[1039]: Stopping Virtual filesystem service - GNOME Online Accounts monitor...
Apr 04 18:30:31 guy-pc systemd[1039]: Stopping Virtual filesystem service - Media Transfer Protocol monitor...
Apr 04 18:30:31 guy-pc systemd[1039]: Stopping D-Bus User Message Bus...
Apr 04 18:30:31 guy-pc systemd[1039]: run-user-1000-gvfs.mount: Succeeded.
Apr 04 18:30:31 guy-pc systemd[1039]: gvfs-daemon.service: Main process exited, code=killed, status=15/TERM
Apr 04 18:30:31 guy-pc systemd[1039]: gvfs-udisks2-volume-monitor.service: Main process exited, code=killed, status=15/TERM
Apr 04 18:30:31 guy-pc systemd[1039]: gvfs-udisks2-volume-monitor.service: Succeeded.
Apr 04 18:30:31 guy-pc systemd[1039]: Stopped Virtual filesystem service - disk device monitor.
Apr 04 18:30:31 guy-pc systemd[1039]: gvfs-gphoto2-volume-monitor.service: Main process exited, code=killed, status=15/TERM
Apr 04 18:30:31 guy-pc systemd[1039]: gvfs-gphoto2-volume-monitor.service: Succeeded.
Apr 04 18:30:31 guy-pc systemd[1039]: Stopped Virtual filesystem service - digital camera monitor.
Apr 04 18:30:31 guy-pc systemd[1039]: gvfs-goa-volume-monitor.service: Main process exited, code=killed, status=15/TERM
Apr 04 18:30:31 guy-pc systemd[1039]: gvfs-goa-volume-monitor.service: Succeeded.
Apr 04 18:30:31 guy-pc systemd[1039]: Stopped Virtual filesystem service - GNOME Online Accounts monitor.
Apr 04 18:30:31 guy-pc systemd[1039]: gvfs-afc-volume-monitor.service: Main process exited, code=killed, status=15/TERM
Apr 04 18:30:31 guy-pc systemd[1039]: gvfs-afc-volume-monitor.service: Succeeded.
Apr 04 18:30:31 guy-pc systemd[1039]: Stopped Virtual filesystem service - Apple File Conduit monitor.
Apr 04 18:30:31 guy-pc systemd[1039]: dbus.service: Succeeded.
Apr 04 18:30:31 guy-pc systemd[1039]: Stopped D-Bus User Message Bus.
Apr 04 18:30:31 guy-pc systemd[1039]: gvfs-mtp-volume-monitor.service: Main process exited, code=killed, status=15/TERM
Apr 04 18:30:31 guy-pc systemd[1039]: gvfs-mtp-volume-monitor.service: Succeeded.
Apr 04 18:30:31 guy-pc systemd[1039]: Stopped Virtual filesystem service - Media Transfer Protocol monitor.
Apr 04 18:30:31 guy-pc systemd[1039]: gvfs-daemon.service: Succeeded.
Apr 04 18:30:31 guy-pc systemd[1039]: Stopped Virtual filesystem service.
Apr 04 18:30:31 guy-pc systemd[1039]: pulseaudio.service: Succeeded.
Apr 04 18:30:31 guy-pc systemd[1039]: Stopped Sound Service.
Apr 04 18:30:31 guy-pc systemd[1039]: Stopped target Basic System.
Apr 04 18:30:31 guy-pc systemd[1039]: Stopped target Paths.
Apr 04 18:30:31 guy-pc systemd[1039]: Stopped target Sockets.
Apr 04 18:30:31 guy-pc systemd[1039]: gpg-agent-extra.socket: Succeeded.
Apr 04 18:30:31 guy-pc systemd[1039]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Apr 04 18:30:31 guy-pc systemd[1039]: dbus.socket: Succeeded.
Apr 04 18:30:31 guy-pc systemd[1039]: Closed D-Bus User Message Bus Socket.
Apr 04 18:30:31 guy-pc systemd[1039]: gpg-agent-ssh.socket: Succeeded.
Apr 04 18:30:31 guy-pc systemd[1039]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Apr 04 18:30:31 guy-pc systemd[1039]: gpg-agent.socket: Succeeded.
Apr 04 18:30:31 guy-pc systemd[1039]: Closed GnuPG cryptographic agent and passphrase cache.
Apr 04 18:30:31 guy-pc systemd[1039]: gpg-agent-browser.socket: Succeeded.
Apr 04 18:30:31 guy-pc systemd[1039]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 04 18:30:31 guy-pc systemd[1039]: dirmngr.socket: Succeeded.
Apr 04 18:30:31 guy-pc systemd[1039]: Closed GnuPG network certificate management daemon.
Apr 04 18:30:31 guy-pc systemd[1039]: Stopped target Timers.
Apr 04 18:30:31 guy-pc systemd[1039]: pulseaudio.socket: Succeeded.
Apr 04 18:30:31 guy-pc systemd[1039]: Closed Sound System.
Apr 04 18:30:31 guy-pc systemd[1039]: Reached target Shutdown.
Apr 04 18:30:31 guy-pc systemd[1039]: systemd-exit.service: Succeeded.
Apr 04 18:30:31 guy-pc systemd[1039]: Started Exit the Session.
Apr 04 18:30:31 guy-pc systemd[1039]: Reached target Exit the Session.
Apr 04 18:30:31 guy-pc systemd[1040]: pam_unix(systemd-user:session): session closed for user guy

paxmark1 · April 05, 2019, 05:46:33 AM

Looking closer at you top, your LXQT and openbox programs are up and running.

I should have thought of this earlier, just try Ctl-Alt-F7 in the terminal

Is your video card an Intel that is part of the computer? I see i915 in top. What is the kernel.

systemctl Back light is a common thing to see - especially if you are on a - not a poroblem
Journaling not started - because /var/log/journal not started But after you made the file - it did start. The journal you see is from after you enabled it.

If you turn off your computer, and then turn it back on you will be able to see the journal from the beginning.

You stated you are in tty4 via the Ctl-Alt-F4. If you logged in as root you do not need sudo before the commands. If you are logged in with your user name, you will need sudo command blah before some. Ctl-Alt-F7 will take you to the graphics (if it is running) it will not if it is not running.

another command is systemd-analyze blame | less ## that will show what things are slowing down the boot.

bushy · April 05, 2019, 06:12:30 AM

Rebooted and logged in as root. executing Ctl-Alt-F7 snapped the cursor to the beginning of the command line, it just sits there blinking. Using the enter key brings me to a new functional command line.
This is a low end lenovo 110s laptop, its all Intel. Kernal is 5.0.5

Output of systemd-analyze: 1.355s dev-mmcblk0p2.device is where Sparky lives.

Code Select

          1.384s systemd-rfkill.service
          1.355s dev-mmcblk0p2.device
          1.306s acpi-support.service
          1.078s NetworkManager-wait-online.service
           908ms udisks2.service
           477ms keyboard-setup.service
           443ms ModemManager.service
           385ms exim4.service
           382ms avahi-daemon.service
           372ms systemd-udev-trigger.service
           368ms wpa_supplicant.service
           363ms rtkit-daemon.service
           306ms NetworkManager.service
           304ms systemd-journald.service
           298ms upower.service
           285ms alsa-restore.service
           283ms atd.service
           269ms systemd-logind.service
           256ms networking.service
           254ms lightdm.service
           250ms pppd-dns.service
           200ms systemd-journal-flush.service
           193ms rsyslog.service
           175ms user@1000.service
           171ms user@0.service
           171ms lm-sensors.service
           160ms ntp.service
           153ms systemd-timesyncd.service
           137ms polkit.service
           115ms systemd-modules-load.service
           106ms systemd-fsck@dev-disk-by\x2duuid-966F\x2d1F1E.service
           101ms systemd-udevd.service
           100ms run-rpc_pipefs.mount
            92ms systemd-tmpfiles-setup.service
            92ms sys-kernel-debug.mount
            89ms dev-mqueue.mount
            89ms ufw.service
            88ms sys-fs-fuse-connections.mount
            85ms dev-hugepages.mount
            84ms ifupdown-wait-online.service
            82ms kmod-static-nodes.service
            74ms colord.service
            72ms systemd-remount-fs.service
            71ms systemd-update-utmp.service
            67ms dev-disk-by\x2duuid-09af5015\x2df67a\x2d4cbf\x2dbab5\x2d24c2177c87c7.swap
            62ms plymouth-start.service
            60ms rpcbind.service
            54ms systemd-sysctl.service
            52ms boot-efi.mount
            49ms console-setup.service
            48ms systemd-user-sessions.service
            47ms nfs-config.service
            43ms systemd-tmpfiles-setup-dev.service
            41ms systemd-sysusers.service
            40ms systemd-random-seed.service
            39ms user-runtime-dir@0.service
            33ms plymouth-read-write.service
            32ms user-runtime-dir@1000.service
            30ms hddtemp.service
            25ms systemd-backlight@backlight:intel_backlight.service
            21ms systemd-update-utmp-runlevel.service
            14ms rc-local.service
             7ms ifupdown-pre.service
             5ms plymouth-quit-wait.service

bushy · April 05, 2019, 06:23:59 AM

Had to use pastebin for the current output of journalctl:
https://pastebin.com/rV2uVEm1

paxmark1 · April 05, 2019, 05:44:16 PM

I looked at the output, nothing looks off.

It's been awhile since I used the tools before systemd. A simpler way of getting your logs would have been
"dmesg | less" ## the output is piped to less which displays one screens worth of data and then hitting the space bar shows you the next page.

My last best guess is that it is the 5.05 kernel messing with something. Possibly your Intel gpu. You see much more of this with Nvidia. Please tell me you do not have a hybrid Bumblebee -Nvidia Optimus gpu.

Correct me if I am wrong. 1. You do get a grub screen
2. You are able to go to a virtual terminal from the flashing "-" in the left upper portion of you monitor. You are not able at all to get into your desktop environment LXQT

If you are not able to get into the grub screen, then it is more difficult to get into a different lower kernel,
If you still do get a grub screen select the advanced options below the first default option and select a kernel from the 4.1x series Without the grub2 screen coming on the only other option would be to use the live version of Sparky to try and fix it or to chroot into it to fix. I have not had to use that much and maybe others can help.

If an earlier kernel does not work , my last options then would be - in the virtual terminal as root

apt update
apt full-upgrade
dpkg --configure -a

If it still fails, try to re-install. Try to stay with a lower kernel.

bushy · April 05, 2019, 11:18:51 PM

I do get the Grub menu, I had tried 4.* kernals , I do get a terminal tty4, I have no idea what Bumblebee etc means.
I will try your suggestions using apt and dpkg commands. If all else fails I will re-install.

I can't say enough that I truly appreciate all your help. The timestamp on my reply doesn't coincide with my local time, Is it your time? Are you in Europe

bushy · April 06, 2019, 12:16:16 AM

Looks like I came to the end of the road. The laptop doesn't have an ethernet post, wireless isn't working, I have a USB NIC but it's not working as well. So I will do a re-install.

Thanks again to anyone and everyone that offered some suggestions and help.

kanliot · April 06, 2019, 06:10:06 AM

Quote from: paxmark1 on April 05, 2019, 05:44:16 PM

If it still fails, try to re-install. Try to stay with a lower kernel.

I take it you mean use "pinning" to stick to an older kernel? https://wiki.debian.org/AptPreferences

I'm asking because I don't know, if I wanted to go back to a previous kernel, how would I do that? I always only see one kernel in grub.

lami07 · April 06, 2019, 09:02:04 AM

Have you tried blacklisting or removing Intel driver? This way your system will boot using modesetting driver.

bushy · April 06, 2019, 03:57:44 PM

I set everything aside and haven't tried re-installing yet, was about to do that and decided to check if there were anymore posts. Glad I did I will try what you suggest. I don't know how to blacklist but will start googling.

bushy · April 06, 2019, 05:17:23 PM

I edited grub's kernal command line removing quiet splash and added modprobe.blacklist=8086:22b1
Nothing changed, still no desktop. I am assuming it didn't work because executing lspci -nn outputs the Intel video controller on the second line.

Code Select


00:00.0 Host bridge [0600]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register [8086:2280] (rev 35)
00:02.0 VGA compatible controller [0300]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35)
00:0b.0 Signal processing controller [1180]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller [8086:22dc] (rev 35)
00:12.0 SD Host controller [0805]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SD Controller [8086:2296] (rev 35)
00:13.0 SATA controller [0106]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SATA Controller [8086:22a3] (rev 35)
00:14.0 USB controller [0c03]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller [8086:22b5] (rev 35)
00:1a.0 Encryption controller [1080]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine [8086:2298] (rev 35)
00:1b.0 Audio device [0403]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller [8086:2284] (rev 35)
00:1c.0 PCI bridge [0604]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 [8086:22c8] (rev 35)
00:1c.1 PCI bridge [0604]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #2 [8086:22ca] (rev 35)
00:1c.2 PCI bridge [0604]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 [8086:22cc] (rev 35)
00:1f.0 ISA bridge [0601]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU [8086:229c] (rev 35)
00:1f.3 SMBus [0c05]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx SMBus Controller [8086:2292] (rev 35)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] (rev 01)
03:00.0 Network controller [0280]: Intel Corporation Intel Dual Band Wireless-AC 3165 Plus Bluetooth [8086:3166] (rev 99)

lami07 · April 06, 2019, 08:30:51 PM

Install inxi and post results of inxi -Fxx

bushy · April 06, 2019, 10:32:31 PM

Code Select

System:    Host: guy-pc Kernel: 5.0.5-sparky-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 Console: tty 4 dm: LightDM 
           Distro: SparkyLinux 5.7 (Nibiru) base: Debian buster/sid 
Machine:   Type: Laptop System: LENOVO product: 80WG v: Lenovo ideapad 110S-11IBR serial: YD029W2T Chassis: type: 10 
           v: Lenovo ideapad 110S-11IBR serial: YD029W2T 
           Mobo: LENOVO model: Kant v: SDK0J91216 WIN serial: YD029W2T UEFI: LENOVO v: 4HCN10WW date: 02/22/2017 
Battery:   ID-1: BAT1 charge: 24.7 Wh condition: 24.9/32.7 Wh (76%) volts: 8.3/7.6 model: Intel SR 1 Harris Beach 
           serial: 123456789 status: Discharging 
CPU:       Topology: Dual Core model: Intel Celeron N3060 bits: 64 type: MCP arch: Airmont rev: 4 L1 cache: 56 KiB 
           L2 cache: 1024 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 6400 
           Speed: 749 MHz min/max: 480/2480 MHz Core speeds (MHz): 1: 716 2: 480 
Graphics:  Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics vendor: Lenovo driver: i915 
           v: kernel bus ID: 00:02.0 chip ID: 8086:22b1 
           Display: tty server: X.org 1.20.3 driver: modesetting unloaded: fbdev,vesa tty: 170x48 
           Message: Advanced graphics data unavailable in console for root. 
Audio:     Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio vendor: Lenovo 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:2284 
           Sound Server: ALSA v: k5.0.5-sparky-amd64 
Network:   Device-1: Intel Dual Band Wireless-AC 3165 Plus Bluetooth driver: iwlwifi v: kernel port: 1040 bus ID: 03:00.0 
           chip ID: 8086:3166 
           IF: wlan0 state: up mac: 3c:f8:62:8b:d0:c1 
Drives:    Local Storage: total: 256.18 GiB used: 18.05 GiB (7.0%) 
           ID-1: /dev/mmcblk0 model: HBG4e size: 29.12 GiB serial: 0x3056052c 
           ID-2: /dev/sda vendor: TCSunBow model: N8 120GB size: 111.79 GiB speed: 6.0 Gb/s serial: 2018030900010 temp: 49 C 
           ID-3: /dev/sdb type: USB model: USB DISK 3.0 size: 115.27 GiB serial: 070859C2327D2706 
Partition: ID-1: / size: 24.35 GiB used: 10.90 GiB (44.8%) fs: ext4 dev: /dev/mmcblk0p2 
           ID-2: swap-1 size: 3.96 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/mmcblk0p3 
Sensors:   System Temperatures: cpu: 36.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 191 Uptime: 3h 39m Memory: 1.80 GiB used: 353.4 MiB (19.2%) Init: systemd v: 241 runlevel: 5 default: 2 
           Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.2 running in: tty 4 inxi: 3.0.32

lami07 · April 06, 2019, 10:49:46 PM

Inxi confirmed you are running modesetting. No luck here. I guess now would be good time for reinstallation.

bushy · April 06, 2019, 11:50:35 PM

Will do Thanks