[SOLVED] Issues with DE's and logging in

xeno_x64 · 2023-06-05 02:23:23

Hi all,

I have bought a new laptop for college( ASUS VivoBook S 15 S3502RA-DB94 ) to replace my previous vivobook. On my previous laptop, arch Linux works flawlessly, gnome and kde, wayland. The new laptop has an AMD apu, so I expected it to be compatible. However, it hasn't been working well.

Here is the output of lscpu and lspci if needed
First installation(kde/wayland) it worked fine for a day, then it refused to connect to wifi, and crashed when I clicked "disconnect" on the network. Rebooting from there would drop me into an unresponsive tty shell.

I have reinstalled Arch dozens of times since. Subsequent installs have not worked. Some installs worked for a few hours, only to crap out a few hours later.
Installing with gnome, kde(both x11 and wayland) never end up working(kde x11 doesn't even get to sddm, just stuck on the systemctl screen).

After a fresh install with kde and wayland, sddm does one of three things:

Is completely unresponsive to clicks typing, etc. ctrl+alt+number for tty either does nothing or brings me to a blank black screen

Is responsive and lets me type my password, but after typing password and pressing enter, it just sits there doing nothing. This is most common. TTY is also unresponsive. If I go to TTY before entering the password, it switches and lets me login, but then proceeds to freeze a few seconds in. I have tried increasing the entropy as the wiki suggests (with rngtools) with no success. I cant really do anything cause TTY doesnt work.

sddm logs me in, but wont connect to wifi, and I cannot run a command on konsole. After pressing enter on a command it goes to a blank newline and does nothing. Other apps are extremly slow to load and eventually kde just freezes.

This journalctl is from when I mistype my password then sddm completely freezes.

This one is one where it lets me in, but wifi doesnt connect and command give out after I try installing kde-network(with usb tethered internet from phone)
^ These aren't what happens every time, but just some examples

When wifi fails to connect, an error along the lines of "no agents supplied" pops up.

I've made sure my /home folder is owned by me, not root
Adding this to sddm didn't work: ExecStartPre=/bin/sleep 5

The issues have been all over and quite inconsistent.

Gnome is more consistent with only 1 fail: Entering the password just leads to endless loading on gdm.
Here is the journalctl of a boot where this happens. I see many errors with gdm and pam, idk what they mean tho.
Here is the journalctl from a boot where I tried to go to TTY but it froze

I also did an Ubuntu install, the system worked until I rebooted, then gdm got really laggy and it wouldnt wake when opening the lid.

Any ideas? I want this laptop to work really badly since my previous one really cant keep up with my workload. Is the laptop just not compatible? Any help is greatly appreciated.

Last edited by xeno_x64 (2023-06-06 01:50:33)

seth · 2023-06-05 06:47:15

The first two journals are the same but they *all* have

Jun 04 17:01:40 alexLaptop kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000
Jun 04 17:01:40 alexLaptop kernel: #PF: supervisor read access in kernel mode
Jun 04 17:01:40 alexLaptop kernel: #PF: error_code(0x0000) - not-present page
Jun 04 17:01:40 alexLaptop kernel: PGD 0 P4D 0 
Jun 04 17:01:40 alexLaptop kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
Jun 04 17:01:40 alexLaptop kernel: CPU: 3 PID: 418 Comm: kworker/3:2 Not tainted 6.3.5-arch1-1 #1 649d963afc0261175aabf0511660febbb7b06177
Jun 04 17:01:40 alexLaptop kernel: Hardware name: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop M3502RA_M3502RA/M3502RA, BIOS M3502RA.301 07/30/2022
Jun 04 17:01:40 alexLaptop kernel: Workqueue: events_long ucsi_init_work [typec_ucsi]
Jun 04 17:01:40 alexLaptop kernel: RIP: 0010:ucsi_acpi_async_write+0x30/0x50 [ucsi_acpi]
Jun 04 17:01:40 alexLaptop kernel: Code: 44 00 00 41 55 49 89 cd 41 54 49 89 d4 55 53 89 f3 e8 d4 3d e6 ff 4c 89 e6 89 df 4c 89 ea 48 03 78 10 48 89 c5 e8 10 ab 99 c9 <49> 8b 04 24 48 89 ef be 01 00 00 00 48 89 45 50 5b 5d 41 5c 41 5d
Jun 04 17:01:40 alexLaptop kernel: RSP: 0018:ffffbbb04146fd80 EFLAGS: 00010246
Jun 04 17:01:40 alexLaptop kernel: RAX: ffffbbb04142af4c RBX: 0000000000000002 RCX: 0000000000000000
Jun 04 17:01:40 alexLaptop kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffbbb04142af4c
Jun 04 17:01:40 alexLaptop kernel: RBP: ffff94b5cfab05a8 R08: 0000000000000000 R09: ffff94b5c6d232a0
Jun 04 17:01:40 alexLaptop kernel: R10: ffffffff8b34f660 R11: 0000000000000014 R12: 0000000000000000
Jun 04 17:01:40 alexLaptop kernel: R13: 0000000000000000 R14: ffff94b5ccfe44b8 R15: 0000000000000000
Jun 04 17:01:40 alexLaptop kernel: FS:  0000000000000000(0000) GS:ffff94b8ce6c0000(0000) knlGS:0000000000000000
Jun 04 17:01:40 alexLaptop kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 04 17:01:40 alexLaptop kernel: CR2: 0000000000000000 CR3: 00000002ea820000 CR4: 0000000000750ee0
Jun 04 17:01:40 alexLaptop kernel: PKRU: 55555554
Jun 04 17:01:40 alexLaptop kernel: Call Trace:
Jun 04 17:01:40 alexLaptop kernel:  <TASK>
Jun 04 17:01:40 alexLaptop kernel:  ? __die+0x23/0x70
Jun 04 17:01:40 alexLaptop kernel:  ? page_fault_oops+0x171/0x4e0
Jun 04 17:01:40 alexLaptop kernel:  ? exc_page_fault+0x7c/0x180
Jun 04 17:01:40 alexLaptop kernel:  ? asm_exc_page_fault+0x26/0x30
Jun 04 17:01:40 alexLaptop kernel:  ? ucsi_acpi_async_write+0x30/0x50 [ucsi_acpi df21e7e67e6c9a1d2fa75024703ff563080062b1]
Jun 04 17:01:40 alexLaptop kernel:  ucsi_exec_command+0x230/0x2e0 [typec_ucsi 55fb9455ba297d8c03da333ca4135a43ec901e42]
Jun 04 17:01:40 alexLaptop kernel:  ucsi_send_command+0x4b/0xe0 [typec_ucsi 55fb9455ba297d8c03da333ca4135a43ec901e42]
Jun 04 17:01:40 alexLaptop kernel:  ucsi_init_work+0x76/0x9d0 [typec_ucsi 55fb9455ba297d8c03da333ca4135a43ec901e42]
Jun 04 17:01:40 alexLaptop kernel:  process_one_work+0x1c7/0x3d0
Jun 04 17:01:40 alexLaptop kernel:  worker_thread+0x51/0x390
Jun 04 17:01:40 alexLaptop kernel:  ? __pfx_worker_thread+0x10/0x10
Jun 04 17:01:40 alexLaptop kernel:  kthread+0xde/0x110
Jun 04 17:01:40 alexLaptop kernel:  ? __pfx_kthread+0x10/0x10
Jun 04 17:01:40 alexLaptop kernel:  ret_from_fork+0x2c/0x50
Jun 04 17:01:40 alexLaptop kernel:  </TASK>
Jun 04 17:01:40 alexLaptop kernel: Modules linked in: snd_soc_dmic snd_acp6x_pdm_dma snd_soc_acp6x_mach snd_sof_amd_rembrandt snd_sof_amd_renoir snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp snd_sof intel_rapl_msr intel_rapl_common snd_sof_utils snd_soc_core joydev edac_mce_amd mousedev snd_hda_codec_realtek mt7921e snd_compress snd_hda_codec_generic mt7921_common ac97_bus snd_hda_codec_hdmi kvm_amd mt76_connac_lib snd_pcm_dmaengine uvcvideo mt76 snd_hda_intel snd_pci_ps kvm snd_rpl_pci_acp6x snd_intel_dspcfg videobuf2_vmalloc irqbypass btusb uvc crct10dif_pclmul snd_intel_sdw_acpi mac80211 snd_acp_pci btrtl crc32_pclmul videobuf2_memops snd_pci_acp6x btbcm polyval_clmulni snd_hda_codec polyval_generic btintel gf128mul videobuf2_v4l2 snd_pci_acp5x snd_hda_core libarc4 btmtk ghash_clmulni_intel hid_multitouch snd_hwdep videodev snd_rn_pci_acp3x sha512_ssse3 asus_nb_wmi bluetooth cfg80211 aesni_intel vfat snd_pcm snd_acp_config asus_wmi ucsi_acpi fat crypto_simd videobuf2_common ledtrig_audio typec_ucsi snd_timer sp5100_tco snd_soc_acpi
Jun 04 17:01:40 alexLaptop kernel:  ecdh_generic cryptd mc rapl sparse_keymap wmi_bmof typec pcspkr snd ccp rfkill snd_pci_acp3x soundcore i2c_piix4 k10temp roles amd_pmf i2c_hid_acpi i2c_hid platform_profile acpi_cpufreq amd_pmc acpi_tad mac_hid crypto_user fuse dm_mod loop bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 amdgpu i2c_algo_bit serio_raw drm_ttm_helper atkbd ttm libps2 drm_buddy vivaldi_fmap gpu_sched nvme drm_display_helper crc32c_intel nvme_core video xhci_pci cec i8042 xhci_pci_renesas nvme_common wmi serio
Jun 04 17:01:40 alexLaptop kernel: CR2: 0000000000000000
Jun 04 17:01:40 alexLaptop kernel: ---[ end trace 0000000000000000 ]---
Jun 04 17:01:40 alexLaptop kernel: RIP: 0010:ucsi_acpi_async_write+0x30/0x50 [ucsi_acpi]
Jun 04 17:01:40 alexLaptop kernel: Code: 44 00 00 41 55 49 89 cd 41 54 49 89 d4 55 53 89 f3 e8 d4 3d e6 ff 4c 89 e6 89 df 4c 89 ea 48 03 78 10 48 89 c5 e8 10 ab 99 c9 <49> 8b 04 24 48 89 ef be 01 00 00 00 48 89 45 50 5b 5d 41 5c 41 5d
Jun 04 17:01:40 alexLaptop kernel: RSP: 0018:ffffbbb04146fd80 EFLAGS: 00010246
Jun 04 17:01:40 alexLaptop kernel: RAX: ffffbbb04142af4c RBX: 0000000000000002 RCX: 0000000000000000
Jun 04 17:01:40 alexLaptop kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffbbb04142af4c
Jun 04 17:01:40 alexLaptop kernel: RBP: ffff94b5cfab05a8 R08: 0000000000000000 R09: ffff94b5c6d232a0
Jun 04 17:01:40 alexLaptop kernel: R10: ffffffff8b34f660 R11: 0000000000000014 R12: 0000000000000000
Jun 04 17:01:40 alexLaptop kernel: R13: 0000000000000000 R14: ffff94b5ccfe44b8 R15: 0000000000000000
Jun 04 17:01:40 alexLaptop kernel: FS:  0000000000000000(0000) GS:ffff94b8ce6c0000(0000) knlGS:0000000000000000
Jun 04 17:01:40 alexLaptop kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 04 17:01:40 alexLaptop kernel: CR2: 0000000000000000 CR3: 00000002ea820000 CR4: 0000000000750ee0
Jun 04 17:01:40 alexLaptop kernel: PKRU: 55555554
Jun 04 17:01:40 alexLaptop kernel: note: kworker/3:2[418] exited with irqs disabled

The pattern doesn't show up a lot, but there's https://forum.manjaro.org/t/system-does … ate/141590 w/ a similar vivobook and https://lore.kernel.org/lkml/cc36fca9-e … @gmx.de/T/ on an Acer system.

https://lore.kernel.org/lkml/2023050700 … ernel.org/ has a possibly related patch but only for zenbooks.
Try to blacklist ucsi_acpi

What kernel does/did ubuntu run?

xeno_x64 · 2023-06-06 02:23:17

Thanks so much! It works now
I blacklisted ucsi_acpi in /etc/modprobe.d/ and it works like a charm now!
The USB-C ports still work(charging, usb, etc) so i'm not missing out on anything.
If it decides to give out again, i'll post again about it.

If you don't mind my asking, what is ucsi_acpi? I understand that its related to USB-C, but after disabling it there is no change to the ports. My previous vivobook does not have ucsi_acpi enabled and it's USB-C works. So what is missing with ucsi_acpi disabled?

seth · 2023-06-06 07:24:24

https://www.usb.org/document-library/us … cification
My guess is that it exposes it to ACPI and judging from https://github.com/torvalds/linux/commi … csi_acpi.c a bit troublesome.
You might want to file a bug at https://bugzilla.kernel.org/ - Product "Drivers", Component "USB" and hand them at least the segment from #2

Arch Linux

#1 2023-06-05 02:23:23

[SOLVED] Issues with DE's and logging in

#2 2023-06-05 06:47:15

Re: [SOLVED] Issues with DE's and logging in

#3 2023-06-06 02:23:17

Re: [SOLVED] Issues with DE's and logging in

#4 2023-06-06 07:24:24

Re: [SOLVED] Issues with DE's and logging in

Board footer