Different device issues happening at the same time

thkim1011 · 2019-08-03 03:27:34

I'm having a really weird issue right now where a lot of my devices are not working properly. Specifically, my sound output, sound input, touchpad, and mouse does not work properly at the moment. I'm absolutely confused as to what's wrong with my sound because I don't see any errors coming from the sound card in journalctl, but does touchpad is logging errors as follows:

Aug 02 20:21:52 thk-arch /usr/lib/gdm-x-session[8687]: (EE) event19 - Synaptics TM3407-002: kernel bug: Touch jump detected and discarded.

As to the mouse, the left click just doesn't work.

I'm almost certain that the issue is not with each of these individual devices, but because of something else, because I did have a similar issue (except only the touchpad and mouse failed to work) when I enabled legacy boot within the bios. I might edit this post later to add more details later because currently my system is actually just unusable.

ewaller · 2019-08-03 13:55:37

As a sanity check, what are the output of uname -a and of pacman -Q linux (Assuming you are running the stock kernel)?

thkim1011 · 2019-08-03 19:47:08

$ uname -a
Linux thk-arch 5.2.5-arch1-1-ARCH #1 SMP PREEMPT Wed Jul 31 08:30:34 UTC 2019 x86_64 GNU/Linux
$ pacman -Q linux
linux 5.2.5.arch1-1

seth · 2019-08-03 20:12:52

Please define "not work properly" - does it mean not at all?
Messing w/ the UEFI/BIOS could fail to handover control over the input devices, but I don't see how that would impact sound. A common link *might* be the usb.

Once you fell able to produce more data, post the outputs of

lsusb
aplay -lL
sudo libinput list-devices # this one requires root permissions one way or another
sudo journalctl -b

You can use https://wiki.archlinux.org/index.php/Pastebin if you eg. only manage to operate the device via ssh.

thkim1011 · 2019-08-03 21:22:57

I've uploaded the outputs here: https://gist.github.com/thkim1011/96fa4 … 92a1c20c21. The keyboard is working well, so I think I'll be able to upload to gist from tty.

By not working, the touchpad's left click works sometimes, and when it does, it seems to hold the clicked state until I right click with my mouse or somehow cancel it. At the same moment, it seems to log the following error.

Aug 02 20:21:52 thk-arch /usr/lib/gdm-x-session[8687]: (EE) event19 - Synaptics TM3407-002: kernel bug: Touch jump detected and discarded.

The audio simply doesn't work. I think the computer is aware of the sound card, and going through https://wiki.archlinux.org/index.php/Pu … leshooting has no effect. Furthermore, I never resolved this issue: https://bbs.archlinux.org/viewtopic.php?id=247702.

EDIT: So I noticed bbswitch wasn't installed from looking through journalctl -b, so I decided to install, but it ended up making gdm not load at all. I used a backup usb to disable gdm, and then it seems like audio is working now from running `speaker-test -t wav -c 6`. The problem now is that my xserver no longer starts, but it produced the following log file: https://gist.github.com/thkim1011/59507 … 316ff4ecdf. The relevant error message from the log seems to be the following.

Fatal server error:
[   744.712] (EE) parse_vt_settings: Cannot open /dev/tty0 (Permission denied)

I still have no idea as to the status of my mouse and touchpad as I cannot start a graphical session at the moment.

EDIT 2: So logically, after seeing the error I found out that /dev/tty0 can be read by the tty group, so I added my user to the tty group, but now, `xinit` just kind of freezes, and I can't find out what's being logged, because I have to force shutdown. This is my .xinitrc

export GDK_BACKEND=x11
exec gnome-session

Currently, I'm suspecting that the xserver might be what's causing the issues, but to be honest, I don't really know what's going on, so I would appreciate some help . lol.

EDIT 3: I'm getting more errors. On `reboot`, I see

[    *] A stop job is running for Bumblebee C Daemon (30s / 1min 30s)
[  942.821426] ACPI Error: Aborting method \_SB.PC10.PGON due to previous error (AE_AML_LOOP_TIMEOUT) (20190509/psparse-529)
[  924.821860] ACPI Error: Aborting method \_SB.PC10.PEG0.PEGP._ON due to previous error (AE_AML_LOOP_TIMEOUT) (20190509/psparse-529)
[  924.822205] ACPI Error: Aborting method \_SB.PC10.PEG0.PEGP._PS0 due to previous error (AE_AML_LOOP_TIMEOUT) (20190509/psparse-529)

Last edited by thkim1011 (2019-08-04 00:37:00)

seth · 2019-08-04 06:56:39

Cut out gnome/gdm, you're likely headed for a wayland session or a wayland/xorg competition.
Instead use startx/xinit to run eg. openbox, from your xorg log, the issue is the "/etc/X11/xorg.conf" you generated what along the disabled nvidia chip drives you into the vesa driver which is the cause for the tty issues (you should remove yourself from the group again)
So: move away the xorg.conf, configure xinitrc to run openbox (icewm, fluxbox, …), run startx and check the mouse behavior.
See https://wiki.archlinux.org/index.php/Xinitrc

The sound issue seems completely unrelated and because of [drummroll…] *pulseaudio* (which is mandatory for gnome only) - check pavuctl on whether it's simply muted somewhere.

thkim1011 · 2019-08-04 19:53:12

My /etc/X11/xorg.conf seems to be empty so I'm not sure how to resolve the issue with the xinit starting. However, I did remove myself from the tty group and now the system doesn't have trouble terminating the Bumblebee daemon and shuts down normally. Also, something that's confusing me right now is that startx seems to not have the issue with /dev/tty0 permissions, but xinit does. In addition, when I add myself to the tty group, xinit and startx behaves the same way, and just freezes without doing anything. I'm not sure if this is opening a wayland session because I made sure that gdm uses xorg with the following /etc/gdm/custom.conf:

# GDM configuration storage

[daemon]
# Uncomment the line below to force the login screen to use Xorg
WaylandEnable=false

[security]

[xdmcp]

[chooser]

[debug]
# Uncomment the line below to turn on debugging
#Enable=true

Again this started happening when I installed bbswitch, which shouldn't have caused a problem if I understand correctly.

Last edited by thkim1011 (2019-08-04 19:53:56)

seth · 2019-08-04 20:03:59

Please post your xinitrc as well as an updated Xorg log

Edit: also

ls /{etc,usr/share}/X11/xorg.conf.d

Last edited by seth (2019-08-04 20:04:56)

thkim1011 · 2019-08-06 23:54:33

$ cat .xinitrc
exec openbox

Xorg log: https://gist.github.com/thkim1011/cf69d … d3e10c8868

$ ls /etc/X11/xorg.conf.d
$ ls /usr/share/X11/xorg.conf.d
10-nvidia-drm-outputclass.conf
10-quirks.conf
40-libinput.conf

Last edited by thkim1011 (2019-08-06 23:54:52)

jasonwryan · 2019-08-06 23:56:03

The first step is to fix your xinitrc so your session is not broken. Read the second note: https://wiki.archlinux.org/index.php/Xinit#xinitrc

seth · 2019-08-07 06:31:23

a) remove the empty xorg.conf to avoid further confusion
b) You're still loading the vesa driver what suggests there's set. off w/ the optimus configuration, did you read https://wiki.archlinux.org/index.php/NVIDIA_Optimus and https://wiki.archlinux.org/index.php/Bumblebee to configure it?
c) purge xf86-video-vesa to get that completely out of the way

thkim1011 · 2019-08-07 21:39:29

I decided to simply remove bumblebee and bbswitch (might come back to this though in a different thread), and it seems like the touchpad and mouse issues are fixed? However, I still have the issue with the audio not being recognized, except that instead of everything being normal despite sound not working, now it explicitly states that the device being used is dummy output.

V1del · 2019-08-07 23:18:56

Make a new thread for the sound issues and post

aplay -lL
sudo fuser -v /dev/snd/*
pacmd list-cards
pacmd list-sinks

mark this one as solved and maybe add something to explicitly mention that this one was about the xorg input device issues. It's usually more tidy to have distinct problems in distinct threads.

Arch Linux

#1 2019-08-03 03:27:34

Different device issues happening at the same time

#2 2019-08-03 13:55:37

Re: Different device issues happening at the same time

#3 2019-08-03 19:47:08

Re: Different device issues happening at the same time

#4 2019-08-03 20:12:52

Re: Different device issues happening at the same time

#5 2019-08-03 21:22:57

Re: Different device issues happening at the same time

#6 2019-08-04 06:56:39

Re: Different device issues happening at the same time

#7 2019-08-04 19:53:12

Re: Different device issues happening at the same time

#8 2019-08-04 20:03:59

Re: Different device issues happening at the same time

#9 2019-08-06 23:54:33

Re: Different device issues happening at the same time

#10 2019-08-06 23:56:03

Re: Different device issues happening at the same time

#11 2019-08-07 06:31:23

Re: Different device issues happening at the same time

#12 2019-08-07 21:39:29

Re: Different device issues happening at the same time

#13 2019-08-07 23:18:56

Re: Different device issues happening at the same time

Board footer