Problem after updating. No internet and X.Org isn't detecting inputs

spicysupreme · 2019-01-08 16:17:57

So after running sudo pacman -Syu earlier today and being in my kde session for a while I rebooted.
I've been booting into the lts kernel I have installed fine but now I have no internet connection and when I run startx, I get into kde but my mouse and keyboard are unresponsive and the monitor size is wrong.
Additionally, the "linux linux" kernel fails to load completely.

loqs · 2019-01-08 16:23:13

What is the output of the following?

pacman -Q linux linux-lts
uname -a

spicysupreme · 2019-01-08 16:27:51

loqs wrote:

What is the output of the following?
pacman -Q linux linux-lts
uname -a

from chroot in my install usb:

linux 4.20.arch1-1
linux-lts 4.19.13-1

Linux archiso 4.20.0-arch1-1-ARCH #1 SMP PREEMPT Mon Dec 24 03:00:40 UTC 2018 x86_64 GNU/Linux

edit: after going into my usb, I can't even boot into the lts kernel anymore

Last edited by spicysupreme (2019-01-08 16:37:15)

spicysupreme · 2019-01-08 16:51:51

Should I just install an earlier kernel?

Trilby · 2019-01-08 17:15:51

spicysupreme wrote:

from chroot in my install usb:

That's not so useful. I'm pretty sure the intent of the question was to ensure the running kernel matched the installed modules which might not be the case if a boot partition was not mounted during an upgrade. Running these commands from a chroot does not address that at all.

spicysupreme wrote:

edit: after going into my usb, I can't even boot into the lts kernel anymore

What errors do you get? What happens? What are the actual symptoms?

Do you have a seperate boot partition? If so, mount it in the live usb and report the output of the following:

file /path/to/mountpoint/vmlinuz-*

spicysupreme · 2019-01-08 17:41:11

Trilby wrote:

spicysupreme wrote:
from chroot in my install usb:
That's not so useful. I'm pretty sure the intent of the question was to ensure the running kernel matched the installed modules which might not be the case if a boot partition was not mounted during an upgrade. Running these commands from a chroot does not address that at all.
spicysupreme wrote:
edit: after going into my usb, I can't even boot into the lts kernel anymore
What errors do you get? What happens? What are the actual symptoms?
Do you have a seperate boot partition? If so, mount it in the live usb and report the output of the following:
file /path/to/mountpoint/vmlinuz-*

It gets stuck on

/dev/sda3: clean 251523/3276800 files, 2502332/13107200 blocks

and will not go anywhere on both kernels.
Yes, the output is:

zsh: no matches found: /path/to/mountpoint/vmlinuz-*

loqs · 2019-01-08 17:50:45

file /path/to/mountpoint/vmlinuz-*

was meant to be amended so the path pointed to the boot partition of the install for instance if from the install media you mount the system's root filesystem at /mnt and the boot filesystem then at /mnt/boot the command should have been

file /mnt/boot/vmlinuz-*

spicysupreme · 2019-01-08 17:55:26

Sorry, the response is now:

/mnt/boot/vmlinuz-linux: Linux kernel x86 boot executable bzImage, version 4.20.0-arch1-1-ARCH (builduser@heftig-29859) #1 SMP PREEMPT Mon Dec 24 03:00:30 UTC 2018, RO-rootFS, swap_dev 0x5, Normal VGA
/mnt/boot/vmlinuz-linux-lts: Linux kernel x86 boot executable bzImage, version 4.19.13-1-lts (builduser@andyrtr) #1 SMP Sun Dec 30 07:38:47 CET 2018, RO-rootFS, swap_dev 0x5, Normal VGA

loqs · 2019-01-08 18:02:52

Well the kernel versions seem to match. Please chroot in from the install media and see if anything is recorded in the journal from these failing boots.

spicysupreme · 2019-01-08 18:25:13

loqs wrote:

Well the kernel versions seem to match. Please chroot in from the install media and see if anything is recorded in the journal from these failing boots.

I'm not really sure what I'm looking for since there's so much information here, but the recent stuff is near the bottom:
https://ptpb.pw/aIkN

loqs · 2019-01-08 18:40:11

Please boot the installed system. When it appears to hang press some keys randomly. Does the boot then continue?

spicysupreme · 2019-01-08 18:43:09

loqs wrote:

Please boot the installed system. When it appears to hang press some keys randomly. Does the boot then continue?

No, it's still stuck

loqs · 2019-01-08 19:03:35

The linux-lts kernel will not use the nvidia drivers it requires the nvidia-lts or nvidia-dkms package.
From the chroot what is the contents of /var/log/pacman.log to see what the update contained. Also

pacman -Qkk &> /tmp/pacman.log # then post the contents of /tmp/pacman.log and then delete it to leave /tmp clean again

spicysupreme · 2019-01-08 19:08:50

loqs wrote:

The linux-lts kernel will not use the nvidia drivers it requires the nvidia-lts or nvidia-dkms package.
From the chroot what is the contents of /var/log/pacman.log to see what the update contained. Also
pacman -Qkk &> /tmp/pacman.log # then post the contents of /tmp/pacman.log and then delete it to leave /tmp clean again

/tmp/pacman.log: https://ptpb.pw/ws5w
/vars/log/pacman.log: https://ptpb.pw/4UpL

seth · 2019-01-08 19:29:52

Jan 07 18:09:19 ArchLinux kernel: nvidia: module license 'NVIDIA' taints kernel.
Jan 07 18:09:19 ArchLinux kernel: Disabling lock debugging due to kernel taint
Jan 07 18:09:19 ArchLinux kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Jan 07 18:09:19 ArchLinux kernel: i915 0000:00:02.0: enabling device (0006 -> 0007)
Jan 07 18:09:19 ArchLinux kernel: nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
Jan 07 18:09:19 ArchLinux kernel: NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:1402)
                                  NVRM: installed in this system is not supported by the 340.107
                                  NVRM: NVIDIA Linux driver release.  Please see 'Appendix
                                  NVRM: A - Supported NVIDIA GPU Products' in this release's
                                  NVRM: README, available on the Linux driver download page
                                  NVRM: at www.nvidia.com.
Jan 07 18:09:19 ArchLinux kernel: nvidia: probe of 0000:01:00.0 failed with error -1
Jan 07 18:09:19 ArchLinux kernel: checking generic (f1000000 130000) vs hw (d0000000 10000000)
Jan 07 18:09:19 ArchLinux kernel: [drm] Replacing VGA console driver
Jan 07 18:09:19 ArchLinux kernel: NVRM: The NVIDIA probe routine failed for 1 device(s).
Jan 07 18:09:19 ArchLinux kernel: NVRM: None of the NVIDIA graphics adapters were initialized!
Jan 07 18:09:19 ArchLinux kernel: [drm] Module unloaded
Jan 07 18:09:19 ArchLinux kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Jan 07 18:09:19 ArchLinux kernel: [drm] Driver supports precise vblank timestamp query.
Jan 07 18:09:19 ArchLinux kernel: [drm] Initialized i915 1.6.0 20180921 for 0000:00:02.0 on minor 0

You seem to have installed the nvidia driver for your GPU afterwards, and you also did partial upgrades:
[2019-01-07 20:28] [PACMAN] Running 'pacman -Sy plasma kde-applications'
[2019-01-07 23:16] [PACMAN] Running 'pacman -Sy ark dolphin dolphin-plugins filelight ffmpegthumbs gwenview kamoso kate kcalc kdenlive kdf kfind kdialog kiten konsole kwrite plasma-desktop'

And a couple of isolated packages afterwards

Run a full upgrade and provide an updated journal.
https://wiki.archlinux.org/index.php/Pa … an_upgrade

spicysupreme · 2019-01-08 19:49:06

Completed upgrade.
Journal: https://ptpb.pw/lW12

seth · 2019-01-08 20:00:13

Jan 08 14:10:53 ArchLinux systemd[1]: boot.mount: Directory /boot to mount over is not empty, mounting anyway.

Smells like trouble.

Jan 08 14:10:58 ArchLinux kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.0615] device (enp3s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.0622] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1415] dhcp4 (enp3s0):   address 192.168.0.14
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1416] dhcp4 (enp3s0):   plen 24
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1416] dhcp4 (enp3s0):   expires in 3600 seconds
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1416] dhcp4 (enp3s0):   nameserver '69.1.30.2'
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1416] dhcp4 (enp3s0):   nameserver '69.1.30.3'
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1416] dhcp4 (enp3s0):   hostname 'ArchLinux'
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1417] dhcp4 (enp3s0):   gateway 192.168.0.1
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1419] dhcp4 (enp3s0): state changed unknown -> bound
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1438] device (enp3s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1452] device (enp3s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1456] device (enp3s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1463] manager: NetworkManager state is now CONNECTED_LOCAL
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1716] manager: NetworkManager state is now CONNECTED_SITE
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1717] policy: set 'Wired connection 1' (enp3s0) as default for IPv4 routing and DNS

You *do* have an internet connection (w/ the lts kernel)

Jan 08 14:10:59 ArchLinux login[379]: pam_tally(login:auth): pam_get_uid; no such user
Jan 08 14:10:59 ArchLinux login[379]: pam_unix(login:auth): check pass; user unknown
Jan 08 14:10:59 ArchLinux login[379]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=tty1 ruser= rhost=
Jan 08 14:11:01 ArchLinux login[379]: FAILED LOGIN 1 FROM tty1 FOR hhihihihihihihihihihihihihohoihmnlknlkh, Authentication failure
Jan 08 14:11:03 ArchLinux login[379]: pam_tally(login:auth): pam_get_uid; no such user

But apparently you're drunken, your keyboard generates spurious input or you've a weird taste for usernames ;-)
Either way, there's no user "hhihihihihihihihihihihihihohoihmnlknlkh".

Did you type this blindly? Is the poblem a black screen?

spicysupreme · 2019-01-08 20:05:34

seth wrote:

Jan 08 14:10:53 ArchLinux systemd[1]: boot.mount: Directory /boot to mount over is not empty, mounting anyway.

Smells like trouble.

Jan 08 14:10:58 ArchLinux kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.0615] device (enp3s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.0622] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1415] dhcp4 (enp3s0):   address 192.168.0.14
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1416] dhcp4 (enp3s0):   plen 24
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1416] dhcp4 (enp3s0):   expires in 3600 seconds
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1416] dhcp4 (enp3s0):   nameserver '69.1.30.2'
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1416] dhcp4 (enp3s0):   nameserver '69.1.30.3'
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1416] dhcp4 (enp3s0):   hostname 'ArchLinux'
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1417] dhcp4 (enp3s0):   gateway 192.168.0.1
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1419] dhcp4 (enp3s0): state changed unknown -> bound
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1438] device (enp3s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1452] device (enp3s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1456] device (enp3s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1463] manager: NetworkManager state is now CONNECTED_LOCAL
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1716] manager: NetworkManager state is now CONNECTED_SITE
Jan 08 14:10:58 ArchLinux NetworkManager[367]: <info>  [1546974658.1717] policy: set 'Wired connection 1' (enp3s0) as default for IPv4 routing and DNS

You *do* have an internet connection (w/ the lts kernel)

Jan 08 14:10:59 ArchLinux login[379]: pam_tally(login:auth): pam_get_uid; no such user
Jan 08 14:10:59 ArchLinux login[379]: pam_unix(login:auth): check pass; user unknown
Jan 08 14:10:59 ArchLinux login[379]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=tty1 ruser= rhost=
Jan 08 14:11:01 ArchLinux login[379]: FAILED LOGIN 1 FROM tty1 FOR hhihihihihihihihihihihihihohoihmnlknlkh, Authentication failure
Jan 08 14:11:03 ArchLinux login[379]: pam_tally(login:auth): pam_get_uid; no such user

But apparently you're drunken, your keyboard generates spurious input or you've a weird taste for usernames ;-)
Either way, there's no user "hhihihihihihihihihihihihihohoihmnlknlkh".

Did you type this blindly? Is the poblem a black screen?

Okay, now that I know that my typing was being input, I blindly typed in my username, password, and startx and managed to get into a functioning kde environment.
However, it still shows that it's loading the kernel, not my Arch login when I boot, perhaps I could just configure x.org to start at boot instead of even dealing with my terminal login?

seth · 2019-01-08 20:11:57

https://wiki.archlinux.org/index.php/In … _early_KMS ?

Pay attention to the /boot path, ensure the boot partition is mouted whenever installing a kernel/running mkinitcpio, check /boot/vmlinuz-* w/ and w/o the boot partition mounted and get rid of the files in the unmounted path (ie. /boot should be empty before mounting the boot partition)

Arch Linux

#1 2019-01-08 16:17:57

Problem after updating. No internet and X.Org isn't detecting inputs

#2 2019-01-08 16:23:13

Re: Problem after updating. No internet and X.Org isn't detecting inputs

#3 2019-01-08 16:27:51

Re: Problem after updating. No internet and X.Org isn't detecting inputs

#4 2019-01-08 16:51:51

Re: Problem after updating. No internet and X.Org isn't detecting inputs

#5 2019-01-08 17:15:51

Re: Problem after updating. No internet and X.Org isn't detecting inputs

#6 2019-01-08 17:41:11

Re: Problem after updating. No internet and X.Org isn't detecting inputs

#7 2019-01-08 17:50:45

Re: Problem after updating. No internet and X.Org isn't detecting inputs

#8 2019-01-08 17:55:26

Re: Problem after updating. No internet and X.Org isn't detecting inputs

#9 2019-01-08 18:02:52

Re: Problem after updating. No internet and X.Org isn't detecting inputs

#10 2019-01-08 18:25:13

Re: Problem after updating. No internet and X.Org isn't detecting inputs

#11 2019-01-08 18:40:11

Re: Problem after updating. No internet and X.Org isn't detecting inputs

#12 2019-01-08 18:43:09

Re: Problem after updating. No internet and X.Org isn't detecting inputs

#13 2019-01-08 19:03:35

Re: Problem after updating. No internet and X.Org isn't detecting inputs

#14 2019-01-08 19:08:50

Re: Problem after updating. No internet and X.Org isn't detecting inputs

#15 2019-01-08 19:29:52

Re: Problem after updating. No internet and X.Org isn't detecting inputs

#16 2019-01-08 19:49:06

Re: Problem after updating. No internet and X.Org isn't detecting inputs

#17 2019-01-08 20:00:13

Re: Problem after updating. No internet and X.Org isn't detecting inputs

#18 2019-01-08 20:05:34

Re: Problem after updating. No internet and X.Org isn't detecting inputs

#19 2019-01-08 20:11:57

Re: Problem after updating. No internet and X.Org isn't detecting inputs

Board footer