Can't boot to live USB

Machba · January 27, 2019, 7:59pm

This seems to be a recurring theme in the forum but I’m not seeing an issue with the same problems as I’m receiving.
I’m trying out netrunner for a potential replacement to Windows (Newbie Alert!). I created a bootable USB using Rufus from the netrunner-desktop-1901-64bit.iso file.

When trying to boot to USB, selecting the “Netrunner Desktop Live (amd64)” boot process, a curser appears in the top left corner of the screen for a few seconds, the screen goes blank, and then the system just hangs and does nothing. I’ve waited up to 30 minutes on this.

When trying to boot to USB, selecting the "“Netrunner Desktop Live (amd64failsafe)” boot process the boot process starts and runs to the point in the attached image, then nothing. (It may be important to note, the logitech reference on the last two lines does not appear until I physically move the mouse)

Any suggestions on what I should be doing to get this to progress past this point?

starbuck · January 27, 2019, 8:22pm

Hi Machba,

can you try using Win32 disk imager for the USB just to see if it makes a difference:
https://sourceforge.net/projects/win32diskimager/files/latest/download

Machba · January 27, 2019, 9:15pm

Formatted USB drive, rewrote image using Win32DiskImager.

No benefit with either boot process, same results, same hang point on “failsafe” process.

AJSlye · January 28, 2019, 1:35am

Did you turn off secure boot in your uefi?

leszek · January 28, 2019, 9:02am

So from the photo it looks like it successfully booted into the live system (despite it printing some stuff after the prompt regarding virtualbox).
I have to assume from this that simply the Xorg (graphical user interface) is not coming up.
To help debug this problem a bit more can you try accessing the file /var/log/Xorg.0.log which might give us a hint.

You can print this files content with
cat /var/log/Xorg.0.log
that you enter at the prompt. The important lines are the ones with (EE) at front as this is an indicator for an error.

If you still see the kernel messages about virtualbox and your usb logitech devices. Just hit enter and it should show you the prompt

user@debian:~$

This is where you can enter commands.

Machba · January 28, 2019, 11:37am

Thank you for the suggestion. I see nowhere in the system BIOS a setting for “boot security”. There is a security section in the BIOS which allows for setting passwords and such, but these settings are all disabled.

Machba · January 28, 2019, 11:39am

Thank you, I will try this later today. It seems I’ve corrupted my USB drive whilst copying another variant to try.

AJSlye · January 28, 2019, 1:07pm

I just realized from your output that you have a dual GPU setup.

Intel® G965 Express Chipset Family (Intel® GMA X3000)
and
Radeon RX 560 Series

The output of the following would also be useful:
lspci -k
journalctl -p err -b

Machba · January 28, 2019, 8:41pm

Ok, results as follows:

cat /var/log/Xorg.0.log – “No such file or directory”

journalctrl -p err -b – “No journal files were opened due to insufficient permissions”

lspci -k – output results regarding display adapter in following image: (I have 5 more images of output but was unable to attach them.)

AJSlye · January 28, 2019, 9:10pm

None of that was video, that only showd the ATI HDMI audio part (driver).

Please don’t paste screen shots, lets pipe the output to a txt file:

lspci -k >> lspci.txt

try using:

sudo journalctrl -p err -b >> booterrorlog.txt

If it’s available inxi -G would be helpful.

Machba · January 29, 2019, 12:21am

I was really hoping that by following the commands above somehow the .txt file(s) would magically be written to my flash drive so I could retrieve it and post the details here. But they weren’t magically written to my flash drive and, being a newbie to linux, I don’t know enough to do that just yet. So, my solution was to try installing on my laptop instead of going back and forth trying to figure out how to write a file to the flash drive.

The good news, I have a working netrunner system on my laptop. The bad news, we learned nothing about why it didn’t install on my PC.

Thank you very much for your help. Hopefully, next time I visit the forum I’ll be able to work with your instructions to aid in the process. But, my goal here is to get a semi-working linux system I can work with where I can learn the intricacies of Linux as needed. Hoping, netrunner meets that criteria.

leszek · January 29, 2019, 9:40am

So no Xorg.0.log. Interesting so it tried not even starting.

One thing you can try is starting the login manager manually by entering

sudo systemctl start sddm

and see what happens. Maybe even the /var/log/Xorg.0.log will appear even

Machba · January 29, 2019, 1:42pm

Running sudo systemctl start sddm returns me to the command prompt, no error, no output. Subsequently running cat /var/log/Xlog.0.log returns the same output - no such file or directory

Is there a command to invoke the gui from the command prompt? Maybe if that generates an error we would have more information. And, if it didn’t, that seems to be what is not working here. I would be fine with starting at the command line.

leszek · January 29, 2019, 2:32pm

This is exactly what you tried out by starting sddm

Can you enter
systemctl status sddm
to see if it lists any errors.

Also
sudo journalctl -u sddm
helps.

Machba · January 30, 2019, 12:36am

Output below, sorry still don’t know how to copy a text file to a flash drive from the prompt.

leszek · January 30, 2019, 12:57am

Quick tutorial:

sudo dmesg

after you plugged in your usb stick should tell you how the dev name of the stick is like /dev/sdc or /dev/sdb or /dev/sde or … and lists also partitions on this stick like /dev/sdc1
To mount this partition of the usb stick you can use the command

sudo mount /dev/sdc1 /mnt

Usb stick contents should appear under /mnt directory then and you can copy stuff to it.
To unmount type in
sudo umount /mnt

Regarding the issue itself. Sddm seems to be running and is not complaining.
Though strange that there is no Xorg.0.log which only can mean Xorg might be not running.
So can you check with the command
ps aux | grep Xorg
if it is the case.

Machba · February 1, 2019, 12:06pm

Output of:

ps aux | grep Xorg

user 1616 0.0 0.0 6060 888 tty1 S+ 11:49 0:00 grep Xorg

leszek · February 1, 2019, 2:40pm

So Xorg isn’t really running.
It does not make much sense to me.

Can you run
startx
in the terminal. It should try force start Xorg without the login manager. That should fail I guess and you get an error message that could help us knowing what is going on.

Machba · February 3, 2019, 12:45am

startx - No error.

I first stopped sddm, in order to avoid an error due to conflict. The X window system loaded with what appear to be all features available.

I tried again, rebooted afresh and did not stop sddm this time. X window system started with what appear to be all features available. Mouse action was abhorrent though, very slow, hard to use.

Xorg.0.log was now available through the console window accessed through the system menus. Pasted below for your review. (from first run with sddm stopped - truncated to allow for pasting within character limits)

[   219.985]    NumberOfBanks: 1
[   219.985]    MemoryModel: 6
[   219.985]    BankSize: 0
[   219.985]    NumberOfImages: 5
[   219.985]    RedMaskSize: 8
[   219.985]    RedFieldPosition: 16
[   219.985]    GreenMaskSize: 8
[   219.985]    GreenFieldPosition: 8
[   219.985]    BlueMaskSize: 8
[   219.985]    BlueFieldPosition: 0
[   219.985]    RsvdMaskSize: 0
[   219.985]    RsvdFieldPosition: 0
[   219.985]    DirectColorModeInfo: 0
[   219.985]    PhysBasePtr: 0xb0000000
[   219.985]    LinBytesPerScanLine: 7680
[   219.985]    BnkNumberOfImagePages: 5
[   219.985]    LinNumberOfImagePages: 5
[   219.985]    LinRedMaskSize: 8
[   219.985]    LinRedFieldPosition: 16
[   219.985]    LinGreenMaskSize: 8
[   219.985]    LinGreenFieldPosition: 8
[   219.985]    LinBlueMaskSize: 8
[   219.985]    LinBlueFieldPosition: 0
[   219.985]    LinRsvdMaskSize: 0
[   219.985]    LinRsvdFieldPosition: 0
[   219.985]    MaxPixelClock: 400000000
[   219.985] 
[   219.985] (II) VESA(0): Total Memory: 768 64KB banks (49152kB)
[   219.985] (II) VESA(0): <default monitor>: Using hsync range of 30.00-83.00 kHz
[   219.985] (II) VESA(0): <default monitor>: Using vrefresh range of 55.00-75.00 Hz
[   219.985] (II) VESA(0): <default monitor>: Using maximum pixel clock of 215.00 MHz
[   219.985] (WW) VESA(0): Unable to estimate virtual size
[   219.985] (II) VESA(0): Not using built-in mode "1400x1050" (no mode of this name)
[   219.985] (II) VESA(0): Not using built-in mode "1280x1024" (no mode of this name)
[   219.985] (II) VESA(0): Not using built-in mode "1280x960" (no mode of this name)
[   219.985] (II) VESA(0): Not using built-in mode "1024x768" (no mode of this name)
[   219.985] (II) VESA(0): Not using built-in mode "800x600" (no mode of this name)
[   219.986] (II) VESA(0): Virtual size is 1920x1080 (pitch 1920)
[   219.986] (**) VESA(0): *Built-in mode "1920x1080"
[   219.986] (**) VESA(0): *Built-in mode "640x480"
[   219.986] (**) VESA(0): Display dimensions: (510, 290) mm
[   219.986] (**) VESA(0): DPI set to (95, 94)
[   219.986] (**) VESA(0): Using "Shadow Framebuffer"
[   219.986] (II) Loading sub module "shadow"
[   219.986] (II) LoadModule: "shadow"
[   219.986] (II) Loading /usr/lib/xorg/modules/libshadow.so
[   219.986] (II) Module shadow: vendor="X.Org Foundation"
[   219.986]    compiled for 1.20.3, module version = 1.1.0
[   219.986]    ABI class: X.Org ANSI C Emulation, version 0.4
[   219.986] (II) Loading sub module "fb"
[   219.986] (II) LoadModule: "fb"
[   219.987] (II) Loading /usr/lib/xorg/modules/libfb.so
[   219.994] (II) Module fb: vendor="X.Org Foundation"
[   219.994]    compiled for 1.20.3, module version = 1.0.0
[   219.994]    ABI class: X.Org ANSI C Emulation, version 0.4
[   219.994] (II) UnloadModule: "radeon"
[   219.994] (II) Unloading radeon
[   219.994] (II) Loading sub module "int10"
[   219.994] (II) LoadModule: "int10"
[   219.995] (II) Loading /usr/lib/xorg/modules/libint10.so
[   219.995] (II) Module int10: vendor="X.Org Foundation"
[   219.995]    compiled for 1.20.3, module version = 1.0.0
[   219.995]    ABI class: X.Org Video Driver, version 24.0
[   219.995] (II) VESA(0): initializing int10
[   220.003] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[   220.003] (II) VESA(0): VESA BIOS detected
[   220.003] (II) VESA(0): VESA VBE Version 3.0
[   220.003] (II) VESA(0): VESA VBE Total Mem: 49152 kB
[   220.003] (II) VESA(0): VESA VBE OEM: AMD ATOMBIOS
[   220.003] (II) VESA(0): VESA VBE OEM Software Rev: 15.50
[   220.003] (II) VESA(0): VESA VBE OEM Vendor: (C) 1988-2010, Advanced Micro Devices, Inc.
[   220.003] (II) VESA(0): VESA VBE OEM Product: POLARIS21
[   220.003] (II) VESA(0): VESA VBE OEM Product Rev: 01.00
[   220.004] (II) VESA(0): virtual address = 0x7ff68ce24000, VGAbase = 0x7ff690299000
        physical address = 0xb0000000, size = 50331648
[   220.738] (II) VESA(0): Setting up VESA Mode 0x1D4 (1920x1080)
[   220.739] (II) VESA(0): VBESetVBEMode failed, mode set without customized refresh.
[   221.093] (==) VESA(0): Default visual is TrueColor
[   221.123] (==) VESA(0): Backing store enabled
[   221.123] (==) VESA(0): DPMS enabled
[   221.123] (II) Initializing extension Generic Event Extension
[   221.123] (II) Initializing extension SHAPE
[   221.124] (II) Initializing extension MIT-SHM
[   221.124] (II) Initializing extension XInputExtension
[   221.124] (II) Initializing extension XTEST
[   221.125] (II) Initializing extension BIG-REQUESTS
[   221.125] (II) Initializing extension SYNC
[   221.126] (II) Initializing extension XKEYBOARD
[   221.126] (II) Initializing extension XC-MISC
[   221.126] (II) Initializing extension SECURITY
[   221.127] (II) Initializing extension XFIXES
[   221.127] (II) Initializing extension RENDER
[   221.127] (II) Initializing extension RANDR
[   221.128] (II) Initializing extension COMPOSITE
[   221.129] (II) Initializing extension DAMAGE
[   221.129] (II) Initializing extension MIT-SCREEN-SAVER
[   221.129] (II) Initializing extension DOUBLE-BUFFER
[   221.130] (II) Initializing extension RECORD
[   221.130] (II) Initializing extension DPMS
[   221.130] (II) Initializing extension Present
[   221.131] (II) Initializing extension DRI3
[   221.131] (II) Initializing extension X-Resource
[   221.131] (II) Initializing extension XVideo
[   221.131] (II) Initializing extension XVideo-MotionCompensation
[   221.132] (II) Initializing extension SELinux
[   221.132] (II) SELinux: Disabled on system
[   221.132] (II) Initializing extension GLX
[   221.132] (II) AIGLX: Screen 0 is not DRI2 capable
[   223.214] (II) IGLX: Loaded and initialized swrast
[   223.214] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[   223.214] (II) Initializing extension XFree86-VidModeExtension
[   223.214] (II) Initializing extension XFree86-DGA
[   223.215] (II) Initializing extension XFree86-DRI
[   223.215] (II) Initializing extension DRI2
[   223.521] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[   223.521] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[   223.521] (II) LoadModule: "evdev"
[   223.522] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[   223.535] (II) Module evdev: vendor="X.Org Foundation"
[   223.535]    compiled for 1.20.1, module version = 2.10.6
[   223.535]    Module class: X.Org XInput Driver
[   223.535]    ABI class: X.Org XInput driver, version 24.1
[   223.535] (II) Using input driver 'evdev' for 'Power Button'
[   223.539] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 20 paused 0
[   223.539] (**) Power Button: always reports core events
[   223.539] (**) evdev: Power Button: Device: "/dev/input/event1"
[   223.539] (--) evdev: Power Button: Vendor 0 Product 0x1
[   223.539] (--) evdev: Power Button: Found keys
[   223.539] (II) evdev: Power Button: Configuring as keyboard
[   223.539] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event1"
[   223.539] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[   223.539] (**) Option "xkb_rules" "evdev"
[   223.539] (**) Option "xkb_model" "pc105"
[   223.539] (**) Option "xkb_layout" "us"
[   223.541] (II) config/udev: Adding input device Sleep Button (/dev/input/event0)
[   223.541] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[   223.541] (II) Using input driver 'evdev' for 'Sleep Button'
[   223.545] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 21 paused 0
[   223.545] (**) Sleep Button: always reports core events
[   223.545] (**) evdev: Sleep Button: Device: "/dev/input/event0"
[   223.545] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[   223.545] (--) evdev: Sleep Button: Found keys
[   223.545] (II) evdev: Sleep Button: Configuring as keyboard
[   223.545] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2/event0"
[   223.545] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 7)
[   223.545] (**) Option "xkb_rules" "evdev"
[   223.546] (**) Option "xkb_model" "pc105"
[   223.546] (**) Option "xkb_layout" "us"
[   223.547] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=3 (/dev/input/event7)
[   223.547] (II) No input driver specified, ignoring this device.
[   223.547] (II) This device may have been added with another device file.
[   223.548] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=7 (/dev/input/event8)
[   223.548] (II) No input driver specified, ignoring this device.
[   223.548] (II) This device may have been added with another device file.
[   223.549] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=8 (/dev/input/event9)
[   223.549] (II) No input driver specified, ignoring this device.
[   223.549] (II) This device may have been added with another device file.
[   223.550] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=9 (/dev/input/event10)
[   223.550] (II) No input driver specified, ignoring this device.
[   223.550] (II) This device may have been added with another device file.
[   223.550] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=10 (/dev/input/event11)
[   223.551] (II) No input driver specified, ignoring this device.
[   223.551] (II) This device may have been added with another device file.
[   223.552] (II) config/udev: Adding input device Logitech Performance MX (/dev/input/event5)
[   223.552] (**) Logitech Performance MX: Applying InputClass "evdev pointer catchall"
[   223.552] (II) Using input driver 'evdev' for 'Logitech Performance MX'
[   223.557] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 22 paused 0
[   223.557] (**) Logitech Performance MX: always reports core events
[   223.557] (**) evdev: Logitech Performance MX: Device: "/dev/input/event5"
[   223.557] (--) evdev: Logitech Performance MX: Vendor 0x46d Product 0x101a
[   223.557] (--) evdev: Logitech Performance MX: Found 20 mouse buttons
[   223.557] (--) evdev: Logitech Performance MX: Found scroll wheel(s)
[   223.557] (--) evdev: Logitech Performance MX: Found relative axes
[   223.557] (--) evdev: Logitech Performance MX: Found x and y relative axes
[   223.557] (II) evdev: Logitech Performance MX: Configuring as mouse
[   223.557] (II) evdev: Logitech Performance MX: Adding scrollwheel support
[   223.557] (**) evdev: Logitech Performance MX: YAxisMapping: buttons 4 and 5
[   223.557] (**) evdev: Logitech Performance MX: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[   223.557] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.1/usb3/3-2/3-2:1.2/0003:046D:C52B.0005/0003:046D:101A.0006/input/input12/event5"
[   223.557] (II) XINPUT: Adding extended input device "Logitech Performance MX" (type: MOUSE, id 8)
[   223.557] (II) evdev: Logitech Performance MX: initialized for relative axes.
[   223.558] (**) Logitech Performance MX: (accel) keeping acceleration scheme 1
[   223.558] (**) Logitech Performance MX: (accel) acceleration profile 0
[   223.558] (**) Logitech Performance MX: (accel) acceleration factor: 2.000
[   223.558] (**) Logitech Performance MX: (accel) acceleration threshold: 4
[   223.560] (II) config/udev: Adding input device Logitech Performance MX (/dev/input/mouse0)
[   223.560] (II) No input driver specified, ignoring this device.
[   223.560] (II) This device may have been added with another device file.
[   223.561] (II) config/udev: Adding input device Microsoft MicrosoftÂ® Digital Media Pro Keyboard (/dev/input/event2)
[   223.561] (**) Microsoft MicrosoftÂ® Digital Media Pro Keyboard: Applying InputClass "evdev keyboard catchall"
[   223.561] (II) Using input driver 'evdev' for 'Microsoft MicrosoftÂ® Digital Media Pro Keyboard'
[   223.566] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 23 paused 0
[   223.566] (**) Microsoft MicrosoftÂ® Digital Media Pro Keyboard: always reports core events
[   223.566] (**) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard: Device: "/dev/input/event2"
[   223.566] (--) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard: Vendor 0x45e Product 0xb0
[   223.566] (--) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard: Found keys
[   223.566] (II) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard: Configuring as keyboard
[   223.566] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2:1.0/0003:045E:00B0.0001/input/input5/event2"
[   223.566] (II) XINPUT: Adding extended input device "Microsoft MicrosoftÂ® Digital Media Pro Keyboard" (type: KEYBOARD, id 9)
[   223.566] (**) Option "xkb_rules" "evdev"
[   223.566] (**) Option "xkb_model" "pc105"
[   223.566] (**) Option "xkb_layout" "us"
[   223.568] (II) config/udev: Adding input device Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control (/dev/input/event3)
[   223.568] (**) Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: Applying InputClass "evdev keyboard catchall"
[   223.568] (II) Using input driver 'evdev' for 'Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control'
[   223.573] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 24 paused 0
[   223.573] (**) Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: always reports core events
[   223.573] (**) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: Device: "/dev/input/event3"
[   223.573] (--) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: Vendor 0x45e Product 0xb0
[   223.573] (--) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: Found 1 mouse buttons
[   223.573] (--) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: Found scroll wheel(s)
[   223.573] (--) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: Found relative axes
[   223.573] (II) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: Forcing relative x/y axes to exist.
[   223.573] (--) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: Found absolute axes
[   223.573] (II) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: Forcing absolute x/y axes to exist.
[   223.573] (--) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: Found keys
[   223.573] (II) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: Configuring as mouse
[   223.573] (II) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: Configuring as keyboard
[   223.573] (II) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: Adding scrollwheel support
[   223.573] (**) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: YAxisMapping: buttons 4 and 5
[   223.573] (**) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[   223.574] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2:1.1/0003:045E:00B0.0002/input/input6/event3"
[   223.574] (II) XINPUT: Adding extended input device "Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control" (type: KEYBOARD, id 10)
[   223.574] (**) Option "xkb_rules" "evdev"
[   223.574] (**) Option "xkb_model" "pc105"
[   223.574] (**) Option "xkb_layout" "us"
[   223.574] (II) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: initialized for relative axes.
[   223.574] (WW) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: ignoring absolute axes.
[   223.574] (**) Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: (accel) keeping acceleration scheme 1
[   223.574] (**) Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: (accel) acceleration profile 0
[   223.574] (**) Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: (accel) acceleration factor: 2.000
[   223.575] (**) Microsoft MicrosoftÂ® Digital Media Pro Keyboard Consumer Control: (accel) acceleration threshold: 4
[   223.576] (II) config/udev: Adding input device Microsoft MicrosoftÂ® Digital Media Pro Keyboard System Control (/dev/input/event4)
[   223.576] (**) Microsoft MicrosoftÂ® Digital Media Pro Keyboard System Control: Applying InputClass "evdev keyboard catchall"
[   223.576] (II) Using input driver 'evdev' for 'Microsoft MicrosoftÂ® Digital Media Pro Keyboard System Control'
[   223.581] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 25 paused 0
[   223.581] (**) Microsoft MicrosoftÂ® Digital Media Pro Keyboard System Control: always reports core events
[   223.581] (**) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard System Control: Device: "/dev/input/event4"
[   223.581] (--) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard System Control: Vendor 0x45e Product 0xb0
[   223.581] (--) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard System Control: Found absolute axes
[   223.581] (II) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard System Control: Forcing absolute x/y axes to exist.
[   223.581] (--) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard System Control: Found keys
[   223.581] (II) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard System Control: Forcing relative x/y axes to exist.
[   223.581] (II) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard System Control: Configuring as mouse
[   223.581] (II) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard System Control: Configuring as keyboard
[   223.581] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2:1.1/0003:045E:00B0.0002/input/input7/event4"
[   223.581] (II) XINPUT: Adding extended input device "Micros
oft MicrosoftÂ® Digital Media Pro Keyboard System Control" (type: KEYBOARD, id 11)
[   223.581] (**) Option "xkb_rules" "evdev"
[   223.581] (**) Option "xkb_model" "pc105"
[   223.581] (**) Option "xkb_layout" "us"
[   223.581] (II) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard System Control: initialized for relative axes.
[   223.581] (WW) evdev: Microsoft MicrosoftÂ® Digital Media Pro Keyboard System Control: ignoring absolute axes.
[   223.582] (**) Microsoft MicrosoftÂ® Digital Media Pro Keyboard System Control: (accel) keeping acceleration scheme 1
[   223.582] (**) Microsoft MicrosoftÂ® Digital Media Pro Keyboard System Control: (accel) acceleration profile 0
[   223.582] (**) Microsoft MicrosoftÂ® Digital Media Pro Keyboard System Control: (accel) acceleration factor: 2.000
[   223.582] (**) Microsoft MicrosoftÂ® Digital Media Pro Keyboard System Control: (accel) acceleration threshold: 4
[   223.583] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
[   223.583] (II) No input driver specified, ignoring this device.
[   223.583] (II) This device may have been added with another device file.

leszek · February 3, 2019, 12:04pm

Very interesting. So Xorg is running just fine and I don’t see any errors in the log you attached.
So that means somehow the login manager sddm is not coming up or trying to start Xorg.

I guess the /var/log/sddm.log is empty aswell? (You need to access it with sudo cat /var/log/sddm.log)