pop-os / linux Goto Github PK
View Code? Open in Web Editor NEWThis project forked from torvalds/linux
Pop!_OS fork of https://launchpad.net/ubuntu/+source/linux
License: Other
This project forked from torvalds/linux
Pop!_OS fork of https://launchpad.net/ubuntu/+source/linux
License: Other
Linux kernel ============ There are several guides for kernel developers and users. These guides can be rendered in a number of formats, like HTML and PDF. Please read Documentation/admin-guide/README.rst first. In order to build the documentation, use ``make htmldocs`` or ``make pdfdocs``. The formatted documentation can also be read online at: https://www.kernel.org/doc/html/latest/ There are various text files in the Documentation/ subdirectory, several of them using the reStructuredText markup notation. Please read the Documentation/process/changes.rst file, as it contains the requirements for building and running the kernel, and information about the problems which may result by upgrading your kernel.
Distribution
Pop OS! 20.04 LTS
Related Application and/or Package Version
linux-image-5.15.5-76051505-generic:
Instalado: 5.15.5-76051505.202111250933~1638201579~20.04~09f1aa7
Candidato: 5.15.5-76051505.202111250933~1638201579~20.04~09f1aa7
Tabela de versão:
*** 5.15.5-76051505.202111250933~1638201579~20.04~09f1aa7 1001
1001 http://ppa.launchpad.net/system76/pop/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
brave-browser:
Instalado: 1.32.113
Candidato: 1.32.113
Tabela de versão:
*** 1.32.113 500
500 https://brave-browser-apt-release.s3.brave.com stable/main amd64 Packages
100 /var/lib/dpkg/status
1.32.106 500
500 https://brave-browser-apt-release.s3.brave.com stable/main amd64 Packages
1.31.91 500
500 https://brave-browser-apt-release.s3.brave.com stable/main amd64 Packages
1.31.88 500
500 https://brave-browser-apt-release.s3.brave.com stable/main amd64 Packages
1.31.87 500
500 https://brave-browser-apt-release.s3.brave.com stable/main amd64 Packages
1.30.89 500
500 https://brave-browser-apt-release.s3.brave.com stable/main amd64 Packages
1.30.87 500
500 https://brave-browser-apt-release.s3.brave.com stable/main amd64 Packages
1.30.86 500
500 https://brave-browser-apt-release.s3.brave.com stable/main amd64 Packages
microsoft-edge-stable:
Instalado: 96.0.1054.34-1
Candidato: 96.0.1054.34-1
Tabela de versão:
*** 96.0.1054.34-1 100
100 /var/lib/dpkg/status
Issue/Bug Description:
The pages randomly flicker as if they were flashing
the issue occurs in the following situations:
The following applications display this issue:
Occurs in the following kernel:
Steps to reproduce
Expected behavior:
The page will not flicker
Other Notes:
sometimes the whole page flickers, sometimes only the bottom
does not occur in full screen videos
i wasn't able to record or screenshot the flickering unfortunately
the issue might be present in Chromium or other derivatives that i haven't tested (Vivaldi, Opera, Ungoogled Chromium, Chrome).
This is a Thinkpad T460p running vanilla PopOS (few extensions but no other customisation) 20.04LTS fully updated.
The 5.8 kernel update came through Pop Shop as per usual, installed, rebooted and the screen goes straight to powersave. The laptop does not boot (no net/ssh access or dhcp request).
The laptop boots again if I remove the "quiet" option from the kernel line (either at boot or at the entry in /boot/efi/loader/entries).
No idea why but this is very weird. Thanks.
Dmesg output (after quiet disabled, not of failed boot).
https://pastebin.com/VS3nK4ct
Distribution (run cat /etc/os-release
):
NAME="Pop!_OS"
VERSION="21.10"
Related Application and/or Package Version (run apt policy $PACKAGE NAME
):
Issue/Bug Description:
Pop!_OS freezes on every attempt to reboot or shutdown. First it shows a screen with a blinking cursor and then freezes.
Steps to reproduce (if you know):
Expected behavior:
Other Notes:
I would appreciate any suggestion on investigation the issue
Hi there,
this is an issue since we moved to 5.13 (currently 5.13.0-7620) for ThinkPads (which use acpi-call-dkms)
Info:
Linux weywot 5.13.0-7620-generic #20~1634827117~21.04~874b071-Ubuntu SMP Fri Oct 29 15:06:55 UTC x86_64 x86_64 x86_64 GNU/Linux
NAME="Pop!_OS"
VERSION="21.04"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 21.04"
VERSION_ID="21.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=hirsute
UBUNTU_CODENAME=hirsute
LOGO=distributor-logo-pop-os
acpi-call-dkms:
Installed: 1.1.0-6
Candidate: 1.1.0-6
Version table:
*** 1.1.0-6 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu hirsute/universe i386 Packages
100 /var/lib/dpkg/status
With acpi-call.ko provided by the dkms package above in /usr/lib/modules/5.13.0-7620-generic/extra/
, we get this output when tlp
starts, or when tlp-stat
is issued:
Nov 01 10:57:22 weywot kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000
Nov 01 10:57:22 weywot kernel: #PF: supervisor instruction fetch in kernel mode
Nov 01 10:57:22 weywot kernel: #PF: error_code(0x0010) - not-present page
Nov 01 10:57:22 weywot kernel: PGD 0 P4D 0
Nov 01 10:57:22 weywot kernel: Oops: 0010 [#3] SMP NOPTI
Nov 01 10:57:22 weywot kernel: CPU: 4 PID: 23603 Comm: tpacpi-bat Tainted: G S D OE 5.13.0-7620-generic #20~1634827117~21.04~874b071-Ubuntu
Nov 01 10:57:22 weywot kernel: Hardware name: LENOVO 20FW003KMC/20FW003KMC, BIOS R07ET93W (2.33 ) 05/31/2021
Nov 01 10:57:22 weywot kernel: RIP: 0010:0x0
Nov 01 10:57:22 weywot kernel: Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
Nov 01 10:57:22 weywot kernel: RSP: 0018:ffffae3fc90ffdf0 EFLAGS: 00010246
Nov 01 10:57:22 weywot kernel: RAX: 0000000000000000 RBX: ffff977884b8c6c0 RCX: 0000000000000003
Nov 01 10:57:22 weywot kernel: RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff97798f8bb500
Nov 01 10:57:22 weywot kernel: RBP: ffffae3fc90ffe08 R08: 0000000000000003 R09: 0000000000000000
Nov 01 10:57:22 weywot kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
Nov 01 10:57:22 weywot kernel: R13: 0000000000000000 R14: ffffffffffffffea R15: ffff97798f8bb500
Nov 01 10:57:22 weywot kernel: FS: 00007f506b9402c0(0000) GS:ffff977fa1500000(0000) knlGS:0000000000000000
Nov 01 10:57:22 weywot kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 01 10:57:22 weywot kernel: CR2: ffffffffffffffd6 CR3: 000000024b9a6006 CR4: 00000000003706e0
Nov 01 10:57:22 weywot kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Nov 01 10:57:22 weywot kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Nov 01 10:57:22 weywot kernel: Call Trace:
Nov 01 10:57:22 weywot kernel: proc_reg_llseek+0x4e/0x80
Nov 01 10:57:22 weywot kernel: ? __fdget_pos+0x17/0x50
Nov 01 10:57:22 weywot kernel: ksys_lseek+0x84/0xc0
Nov 01 10:57:22 weywot kernel: __x64_sys_lseek+0x1a/0x20
Nov 01 10:57:22 weywot kernel: do_syscall_64+0x61/0xb0
Nov 01 10:57:22 weywot kernel: ? exit_to_user_mode_prepare+0x37/0xb0
Nov 01 10:57:22 weywot kernel: ? syscall_exit_to_user_mode+0x27/0x50
Nov 01 10:57:22 weywot kernel: ? do_syscall_64+0x6e/0xb0
Nov 01 10:57:22 weywot kernel: ? irqentry_exit_to_user_mode+0x9/0x20
Nov 01 10:57:22 weywot kernel: ? irqentry_exit+0x19/0x30
Nov 01 10:57:22 weywot kernel: ? exc_page_fault+0x8f/0x170
Nov 01 10:57:22 weywot kernel: ? asm_exc_page_fault+0x8/0x30
Nov 01 10:57:22 weywot kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae
Nov 01 10:57:22 weywot kernel: RIP: 0033:0x7f506bb7a75b
Nov 01 10:57:22 weywot kernel: Code: c3 66 0f 1f 44 00 00 48 8b 15 69 98 00 00 f7 d8 64 89 02 b8 ff ff ff ff eb b8 0f 1f 44 00 00 f3 0f 1e fa b8 08 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 39 98 00 00 f7 d8
Nov 01 10:57:22 weywot kernel: RSP: 002b:00007ffd01c02588 EFLAGS: 00000246 ORIG_RAX: 0000000000000008
Nov 01 10:57:22 weywot kernel: RAX: ffffffffffffffda RBX: 0000559baf430c80 RCX: 00007f506bb7a75b
Nov 01 10:57:22 weywot kernel: RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000000000000003
Nov 01 10:57:22 weywot kernel: RBP: 0000559baf495a40 R08: 00007ffd01c02530 R09: 00000000ffffffff
Nov 01 10:57:22 weywot kernel: R10: 0000000000000004 R11: 0000000000000246 R12: 0000559baf4742a0
Nov 01 10:57:22 weywot kernel: R13: 00007ffd01c02780 R14: 0000559baf4743f0 R15: 0000559baf550d10
Nov 01 10:57:22 weywot kernel: Modules linked in: acpi_call(OE) dm_crypt bnep btusb uvcvideo btrtl btbcm btintel videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 bluetooth videobuf2_common videodev ecdh_generic ecc mc snd_hda_codec_hdmi snd_ctl_led iwlmvm snd_hda_codec_realtek intel_rapl_msr snd_hda_codec_generic me>
Nov 01 10:57:22 weywot kernel: raid6_pq libcrc32c raid1 raid0 multipath linear system76_io(OE) system76_acpi(OE) hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid mmc_block i915 i2c_algo_bit rtsx_pci_sdmmc drm_kms_helper crct10dif_pclmul crc32_pclmul syscopyarea sysfillrect ghash_clmulni_intel sysimgblt fb_s>
Nov 01 10:57:22 weywot kernel: CR2: 0000000000000000
Nov 01 10:57:22 weywot kernel: ---[ end trace f92188f3a4474e28 ]---
Nov 01 10:57:22 weywot kernel: RIP: 0010:0x0
Nov 01 10:57:22 weywot kernel: Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
Nov 01 10:57:22 weywot kernel: RSP: 0018:ffffae3fc2957eb0 EFLAGS: 00010246
Nov 01 10:57:22 weywot kernel: RAX: 0000000000000000 RBX: ffff977884b8c6c0 RCX: 0000000000000001
Nov 01 10:57:22 weywot kernel: RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff97797cf63b00
Nov 01 10:57:22 weywot kernel: RBP: ffffae3fc2957ec8 R08: 0000000000000003 R09: 0000000000000000
Nov 01 10:57:22 weywot kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
Nov 01 10:57:22 weywot kernel: R13: 0000000000000000 R14: ffffffffffffffea R15: ffff97797cf63b00
Nov 01 10:57:22 weywot kernel: FS: 00007f506b9402c0(0000) GS:ffff977fa1500000(0000) knlGS:0000000000000000
Nov 01 10:57:22 weywot kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 01 10:57:22 weywot kernel: CR2: ffffffffffffffd6 CR3: 000000024b9a6006 CR4: 00000000003706e0
Nov 01 10:57:22 weywot kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Nov 01 10:57:22 weywot kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Nov 01 10:57:23 weywot kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000
Nov 01 10:57:23 weywot kernel: #PF: supervisor instruction fetch in kernel mode
Nov 01 10:57:23 weywot kernel: #PF: error_code(0x0010) - not-present page
Nov 01 10:57:23 weywot kernel: PGD 0 P4D 0
and that repeats for the other 3 CPU cores.
The fix is to clone, compile and use acpi-call from here: https://github.com/mkottman/acpi_call.
There is more info here: https://gist.github.com/roadkell/9e98db6656e28fbbf1bf51082040f67f
I have an HP 15 da-1071ne with Pop_OS! 21.04 (kernel 5.13) installed on it (no dual boot).
The keyboard function keys: Brightness up/down, Airplane mode do not work at all, closing the lid toggles airplane mode and mute LED does not even work.
I believe that this issue is on the kernel level.
Using evtest:
Available devices:
/dev/input/event0: Lid Switch
/dev/input/event1: Power Button
/dev/input/event2: Power Button
/dev/input/event3: AT Translated Set 2 keyboard
/dev/input/event4: SynPS/2 Synaptics TouchPad
/dev/input/event5: Video Bus
/dev/input/event6: Video Bus
/dev/input/event7: HP Wireless hotkeys
/dev/input/event8: HP TrueVision HD Camera: HP Tru
/dev/input/event9: HDA Intel PCH Mic
/dev/input/event10: HDA Intel PCH Headphone
/dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3
/dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7
/dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8
/dev/input/event14: HDA Intel PCH HDMI/DP,pcm=9
/dev/input/event15: HDA Intel PCH HDMI/DP,pcm=10
/dev/input/event16: HP WMI hotkeys
Testing event 16 (HP WMI hotkeys): No output for the mentioned keys.
Testing event 3 (AT Translated Set 2 keyboard):
#Brightness up/down yield the following (both the same):
Event: time 1630657967.702964, type 4 (EV_MSC), code 4 (MSC_SCAN), value ab
Event: time 1630657967.702964, -------------- SYN_REPORT ------------
#Closing the lid then reopening it yields the following:
Event: time 1630658208.483290, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9c
Event: time 1630658208.483290, type 1 (EV_KEY), code 96 (KEY_KPENTER), value 0
Event: time 1630658208.483290, -------------- SYN_REPORT ------------
Event: time 1630658211.288732, type 4 (EV_MSC), code 4 (MSC_SCAN), value d8
Event: time 1630658211.288732, -------------- SYN_REPORT ------------
Event: time 1630658211.298740, type 4 (EV_MSC), code 4 (MSC_SCAN), value d8
Event: time 1630658211.298740, -------------- SYN_REPORT ------------
Event: time 1630658212.041279, type 4 (EV_MSC), code 4 (MSC_SCAN), value d7
Event: time 1630658212.041279, type 1 (EV_KEY), code 238 (KEY_WLAN), value 1
Event: time 1630658212.041279, -------------- SYN_REPORT ------------
Event: time 1630658212.051527, type 4 (EV_MSC), code 4 (MSC_SCAN), value d7
Event: time 1630658212.051527, type 1 (EV_KEY), code 238 (KEY_WLAN), value 0
Event: time 1630658212.051527, -------------- SYN_REPORT ------------
Event: time 1630658212.058783, type 4 (EV_MSC), code 4 (MSC_SCAN), value e3
Event: time 1630658212.058783, type 1 (EV_KEY), code 143 (KEY_WAKEUP), value 1
Event: time 1630658212.058783, -------------- SYN_REPORT ------------
Event: time 1630658212.069128, type 4 (EV_MSC), code 4 (MSC_SCAN), value e3
Event: time 1630658212.069128, type 1 (EV_KEY), code 143 (KEY_WAKEUP), value 0
Event: time 1630658212.069128, -------------- SYN_REPORT ------------
Update: same scancodes are appearing on windows too.
Update 2: I think the issue is that HP WMI hotkeys on Linux does not support my laptop model, I hope that this driver gets updated to support my laptop model.
Distribution:
NAME="Pop!_OS"
VERSION="20.10"
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 20.10"
VERSION_ID="20.10"
VERSION_CODENAME=groovy
UBUNTU_CODENAME=groovy
I have a problem with evdi-dkms package:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up evdi-dkms (1.7.0+dfsg-1ubuntu1) ...
Removing old evdi-1.7.0+dfsg DKMS files...
------------------------------
Deleting module version: 1.7.0+dfsg
completely from the DKMS tree.
------------------------------
Done.
Loading new evdi-1.7.0+dfsg DKMS files...
Building for 5.11.0-7612-generic
Building initial module for 5.11.0-7612-generic
ERROR (dkms apport): kernel package linux-headers-5.11.0-7612-generic is not supported
Error! Bad return status for module build on kernel: 5.11.0-7612-generic (x86_64)
Consult /var/lib/dkms/evdi/1.7.0+dfsg/build/make.log for more information.
dpkg: error processing package evdi-dkms (--configure):
installed evdi-dkms package post-installation script subprocess returned error exit status 10
Errors were encountered while processing:
evdi-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
Regards
Lenovo P53s connected to Lenovo Thunderbolt 3 Dock. After kernel upgrade to 5.11 the external monitors no longer function and the below error is repeated as long as the dock is connected.
kernel: [ 299.813141] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
This happens on both 5.11-7612 and 5.11-7614. I found mention of the same issue in the RedHat bugtracker for the 5.11 kernel if that helps.
Recently I took an i7 10th notebook and installed windows 10 and pop_os on dualboot.
On w10 everything is working correctly, but on pop_os I'm facing some issues.
When I put a headphone on 2.5mm jack nothing happens, I've tried all similar problems solution, nothing works.
But in one of the solutions I realised that I could change the audio output selection (on PulseAudio painel) to headphones even if it's marked with (unplugged). Doing that, the audio goes correctly to the headphones.
The Problem is in jack's plug-in/plug-out detection.
Some env data:
$ lspci -vvvv | grep -A 10 -i audio
00:1f.3 Audio device: Intel Corporation Device 02c8 (prog-if 80)
DeviceName: Onboard - Sound
Subsystem: Realtek Semiconductor Co., Ltd. Device 11bc
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 141
Region 0: Memory at b2c18000 (64-bit, non-prefetchable) [size=16K]
Region 4: Memory at b2000000 (64-bit, non-prefetchable) [size=1M]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
$ amixer
Simple mixer control 'Master',0
Capabilities: pvolume pvolume-joined pswitch pswitch-joined
Playback channels: Mono
Limits: Playback 0 - 87
Mono: Playback 70 [80%] [-12.75dB] [on]
Simple mixer control 'Headphone',0
Capabilities: pvolume pswitch
Playback channels: Front Left - Front Right
Limits: Playback 0 - 87
Mono:
Front Left: Playback 87 [100%] [0.00dB] [on]
Front Right: Playback 87 [100%] [0.00dB] [on]
Simple mixer control 'Speaker',0
Capabilities: pvolume pswitch
Playback channels: Front Left - Front Right
Limits: Playback 0 - 87
Mono:
Front Left: Playback 0 [0%] [-65.25dB] [off]
Front Right: Playback 0 [0%] [-65.25dB] [off]
Simple mixer control 'Bass Speaker',0
Capabilities: pswitch
Playback channels: Front Left - Front Right
Mono:
Front Left: Playback [off]
Front Right: Playback [off]
Simple mixer control 'PCM',0
Capabilities: pvolume
Playback channels: Front Left - Front Right
Limits: Playback 0 - 255
Mono:
Front Left: Playback 255 [100%] [0.00dB]
Front Right: Playback 255 [100%] [0.00dB]
Simple mixer control 'Mic Boost',0
Capabilities: volume
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 3
Front Left: 0 [0%] [0.00dB]
Front Right: 0 [0%] [0.00dB]
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [off]
Simple mixer control 'IEC958',1
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]
Simple mixer control 'IEC958',2
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]
Simple mixer control 'IEC958',3
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]
Simple mixer control 'IEC958',4
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]
Simple mixer control 'Capture',0
Capabilities: cvolume cswitch
Capture channels: Front Left - Front Right
Limits: Capture 0 - 63
Front Left: Capture 54 [86%] [23.25dB] [on]
Front Right: Capture 54 [86%] [23.25dB] [on]
Simple mixer control 'Auto-Mute Mode',0
Capabilities: enum
Items: 'Disabled' 'Enabled'
Item0: 'Disabled'
Simple mixer control 'Internal Mic Boost',0
Capabilities: volume
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 3
Front Left: 0 [0%] [0.00dB]
Front Right: 0 [0%] [0.00dB]
$ aplay -l
**** Lista de Dispositivos PLAYBACK Hardware ****
placa 0: PCH [HDA Intel PCH], dispositivo 0: ALC256 Analog [ALC256 Analog]
Dispositivo secundário: 1/1
Dispositivo secundário #0: subdevice #0
placa 0: PCH [HDA Intel PCH], dispositivo 3: HDMI 0 [HDMI 0]
Dispositivo secundário: 1/1
Dispositivo secundário #0: subdevice #0
placa 0: PCH [HDA Intel PCH], dispositivo 7: HDMI 1 [HDMI 1]
Dispositivo secundário: 1/1
Dispositivo secundário #0: subdevice #0
placa 0: PCH [HDA Intel PCH], dispositivo 8: HDMI 2 [HDMI 2]
Dispositivo secundário: 1/1
Dispositivo secundário #0: subdevice #0
placa 0: PCH [HDA Intel PCH], dispositivo 9: HDMI 3 [HDMI 3]
Dispositivo secundário: 1/1
Dispositivo secundário #0: subdevice #0
placa 0: PCH [HDA Intel PCH], dispositivo 10: HDMI 4 [HDMI 4]
Dispositivo secundário: 1/1
Dispositivo secundário #0: subdevice #0
$ aplay -L
default
Playback/recording through the PulseAudio sound server
surround21
2.1 Surround output to Front and Subwoofer speakers
surround40
4.0 Surround output to Front and Rear speakers
surround41
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50
5.0 Surround output to Front, Center and Rear speakers
surround51
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
null
Discard all samples (playback) or generate zero samples (capture)
samplerate
Rate Converter Plugin Using Samplerate Library
speexrate
Rate Converter Plugin Using Speex Resampler
jack
JACK Audio Connection Kit
oss
Open Sound System
pulse
PulseAudio Sound Server
upmix
Plugin for channel upmix (4,6,8)
vdownmix
Plugin for channel downmix (stereo) with a simple spacialization
sysdefault:CARD=PCH
HDA Intel PCH, ALC256 Analog
Default Audio Device
front:CARD=PCH,DEV=0
HDA Intel PCH, ALC256 Analog
Front speakers
surround21:CARD=PCH,DEV=0
HDA Intel PCH, ALC256 Analog
2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=PCH,DEV=0
HDA Intel PCH, ALC256 Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=PCH,DEV=0
HDA Intel PCH, ALC256 Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=PCH,DEV=0
HDA Intel PCH, ALC256 Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=PCH,DEV=0
HDA Intel PCH, ALC256 Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=PCH,DEV=0
HDA Intel PCH, ALC256 Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
hdmi:CARD=PCH,DEV=0
HDA Intel PCH, HDMI 0
HDMI Audio Output
hdmi:CARD=PCH,DEV=1
HDA Intel PCH, HDMI 1
HDMI Audio Output
hdmi:CARD=PCH,DEV=2
HDA Intel PCH, HDMI 2
HDMI Audio Output
hdmi:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 3
HDMI Audio Output
hdmi:CARD=PCH,DEV=4
HDA Intel PCH, HDMI 4
HDMI Audio Output
dmix:CARD=PCH,DEV=0
HDA Intel PCH, ALC256 Analog
Direct sample mixing device
dmix:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Direct sample mixing device
dmix:CARD=PCH,DEV=7
HDA Intel PCH, HDMI 1
Direct sample mixing device
dmix:CARD=PCH,DEV=8
HDA Intel PCH, HDMI 2
Direct sample mixing device
dmix:CARD=PCH,DEV=9
HDA Intel PCH, HDMI 3
Direct sample mixing device
dmix:CARD=PCH,DEV=10
HDA Intel PCH, HDMI 4
Direct sample mixing device
dsnoop:CARD=PCH,DEV=0
HDA Intel PCH, ALC256 Analog
Direct sample snooping device
dsnoop:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Direct sample snooping device
dsnoop:CARD=PCH,DEV=7
HDA Intel PCH, HDMI 1
Direct sample snooping device
dsnoop:CARD=PCH,DEV=8
HDA Intel PCH, HDMI 2
Direct sample snooping device
dsnoop:CARD=PCH,DEV=9
HDA Intel PCH, HDMI 3
Direct sample snooping device
dsnoop:CARD=PCH,DEV=10
HDA Intel PCH, HDMI 4
Direct sample snooping device
hw:CARD=PCH,DEV=0
HDA Intel PCH, ALC256 Analog
Direct hardware device without any conversions
hw:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Direct hardware device without any conversions
hw:CARD=PCH,DEV=7
HDA Intel PCH, HDMI 1
Direct hardware device without any conversions
hw:CARD=PCH,DEV=8
HDA Intel PCH, HDMI 2
Direct hardware device without any conversions
hw:CARD=PCH,DEV=9
HDA Intel PCH, HDMI 3
Direct hardware device without any conversions
hw:CARD=PCH,DEV=10
HDA Intel PCH, HDMI 4
Direct hardware device without any conversions
plughw:CARD=PCH,DEV=0
HDA Intel PCH, ALC256 Analog
Hardware device with all software conversions
plughw:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Hardware device with all software conversions
plughw:CARD=PCH,DEV=7
HDA Intel PCH, HDMI 1
Hardware device with all software conversions
plughw:CARD=PCH,DEV=8
HDA Intel PCH, HDMI 2
Hardware device with all software conversions
plughw:CARD=PCH,DEV=9
HDA Intel PCH, HDMI 3
Hardware device with all software conversions
plughw:CARD=PCH,DEV=10
HDA Intel PCH, HDMI 4
Hardware device with all software conversions
usbstream:CARD=PCH
HDA Intel PCH
USB Stream Output
$ lsmod | grep -i snd
snd_sof_pci 20480 0
snd_sof_intel_hda_common 69632 1 snd_sof_pci
snd_soc_hdac_hda 24576 1 snd_sof_intel_hda_common
snd_sof_intel_hda 20480 1 snd_sof_intel_hda_common
snd_sof_intel_byt 20480 1 snd_sof_pci
snd_sof_intel_ipc 20480 1 snd_sof_intel_byt
snd_sof 106496 4 snd_sof_pci,snd_sof_intel_hda_common,snd_sof_intel_byt,snd_sof_intel_ipc
snd_sof_xtensa_dsp 16384 1 snd_sof_pci
snd_hda_ext_core 28672 3 snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_sof_intel_hda
snd_soc_acpi_intel_match 32768 2 snd_sof_pci,snd_sof_intel_hda_common
snd_soc_acpi 16384 2 snd_sof_pci,snd_soc_acpi_intel_match
snd_soc_core 245760 3 snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hda
snd_hda_codec_hdmi 61440 1
snd_compress 24576 1 snd_soc_core
ac97_bus 16384 1 snd_soc_core
snd_pcm_dmaengine 16384 1 snd_soc_core
snd_hda_codec_realtek 118784 1
snd_hda_codec_generic 81920 1 snd_hda_codec_realtek
ledtrig_audio 16384 3 snd_hda_codec_generic,snd_hda_codec_realtek,snd_sof
snd_hda_intel 53248 6
snd_intel_dspcfg 24576 3 snd_hda_intel,snd_sof_pci,snd_sof_intel_hda_common
snd_hda_codec 131072 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek,snd_soc_hdac_hda
snd_hda_core 90112 9 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_sof_intel_hda
snd_hwdep 20480 1 snd_hda_codec
snd_pcm 106496 8 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_sof,snd_sof_intel_hda_common,snd_soc_core,snd_hda_core,snd_pcm_dmaengine
snd_seq_midi 20480 0
snd_seq_midi_event 16384 1 snd_seq_midi
snd_rawmidi 36864 1 snd_seq_midi
snd_seq 69632 2 snd_seq_midi,snd_seq_midi_event
snd_seq_device 16384 3 snd_seq,snd_seq_midi,snd_rawmidi
snd_timer 36864 2 snd_seq,snd_pcm
snd 90112 25 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi
soundcore 16384 1 snd
$ inxi -Fxz
System: Kernel: 5.4.0-7634-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4
Distro: Pop!_OS 20.04 LTS base: Ubuntu 20.04 LTS Focal
Machine: Type: Laptop System: Positivo Bahia - VAIO product: VJFE42F11X-XXXXXX v: N/A serial: <filter>
Mobo: Positivo Tecnologia SA model: VJFE-CL v: 11155298 serial: <filter>
UEFI: Positivo Tecnologia SA v: 1.019.X date: 03/14/2020
Battery: ID-1: BAT0 charge: 41.6 Wh condition: 41.6/41.6 Wh (100%) model: Comet Lake Li-ion Battery
status: Full
CPU: Topology: Quad Core model: Intel Core i7-10510U bits: 64 type: MT MCP arch: Kaby Lake rev: C
L2 cache: 8192 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 36799
Speed: 900 MHz min/max: 400/4900 MHz Core speeds (MHz): 1: 874 2: 867 3: 869 4: 873 5: 858 6: 896
7: 856 8: 848
Graphics: Device-1: Intel UHD Graphics vendor: nCipher Security driver: i915 v: kernel bus ID: 00:02.0
Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.0.8 direct render: Yes
Audio: Device-1: Intel vendor: Realtek driver: snd_hda_intel v: kernel bus ID: 00:1f.3
Sound Server: ALSA v: k5.4.0-7634-generic
Network: Device-1: Intel Wireless-AC 9462 driver: iwlwifi v: kernel port: 5000 bus ID: 00:14.3
IF: wlo1 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel
port: 3000 bus ID: 02:00.0
IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter>
IF-ID-1: br-ebf28174cdd4 state: down mac: <filter>
IF-ID-2: docker0 state: down mac: <filter>
Drives: Local Storage: total: 931.51 GiB used: 15.61 GiB (1.7%)
ID-1: /dev/sda vendor: Crucial model: CT1000BX500SSD1 size: 931.51 GiB temp: 29 C
Partition: ID-1: / size: 447.28 GiB used: 15.51 GiB (3.5%) fs: ext4 dev: /dev/sda7
ID-2: swap-1 size: 9.77 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-0
Sensors: System Temperatures: cpu: 35.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info: Processes: 356 Uptime: 47m Memory: 7.62 GiB used: 2.50 GiB (32.7%) Init: systemd runlevel: 5
Compilers: gcc: 9.3.0 Shell: zsh v: 5.8 inxi: 3.0.38
$ pacmd list-cards
1 card(s) available.
index: 0
name: <alsa_card.pci-0000_00_1f.3>
driver: <module-alsa-card.c>
owner module: 7
properties:
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xb2c18000 irq 141"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-0000:00:1f.3"
sysfs.path = "/devices/pci0000:00/0000:00:1f.3/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "02c8"
device.form_factor = "internal"
device.string = "0"
device.description = "Áudio interno"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
input:analog-stereo: Entrada de Estéreo analógico (priority 65, available: unknown)
output:analog-stereo: Saída de Estéreo analógico (priority 6500, available: unknown)
output:analog-stereo+input:analog-stereo: Duplex estéreo analógico (priority 6565, available: unknown)
output:analog-surround-40: Saída de Surround analógico 4.0 (priority 1200, available: unknown)
output:analog-surround-40+input:analog-stereo: Saída de Surround analógico 4.0 + Entrada de Estéreo analógico (priority 1265, available: unknown)
output:hdmi-stereo: Saída de Digital Stereo (HDMI) (priority 5900, available: no)
output:hdmi-stereo+input:analog-stereo: Saída de Digital Stereo (HDMI) + Entrada de Estéreo analógico (priority 5965, available: no)
output:hdmi-surround: Saída de Digital Surround 5.1 (HDMI) (priority 800, available: no)
output:hdmi-surround+input:analog-stereo: Saída de Digital Surround 5.1 (HDMI) + Entrada de Estéreo analógico (priority 865, available: no)
output:hdmi-surround71: Saída de Digital Surround 7.1 (HDMI) (priority 800, available: no)
output:hdmi-surround71+input:analog-stereo: Saída de Digital Surround 7.1 (HDMI) + Entrada de Estéreo analógico (priority 865, available: no)
output:hdmi-stereo-extra1: Saída de Digital Stereo (HDMI 2) (priority 5700, available: no)
output:hdmi-stereo-extra1+input:analog-stereo: Saída de Digital Stereo (HDMI 2) + Entrada de Estéreo analógico (priority 5765, available: no)
output:hdmi-surround-extra1: Saída de Digital Surround 5.1 (HDMI 2) (priority 600, available: no)
output:hdmi-surround-extra1+input:analog-stereo: Saída de Digital Surround 5.1 (HDMI 2) + Entrada de Estéreo analógico (priority 665, available: no)
output:hdmi-surround71-extra1: Saída de Digital Surround 7.1 (HDMI 2) (priority 600, available: no)
output:hdmi-surround71-extra1+input:analog-stereo: Saída de Digital Surround 7.1 (HDMI 2) + Entrada de Estéreo analógico (priority 665, available: no)
output:hdmi-stereo-extra2: Saída de Digital Stereo (HDMI 3) (priority 5700, available: no)
output:hdmi-stereo-extra2+input:analog-stereo: Saída de Digital Stereo (HDMI 3) + Entrada de Estéreo analógico (priority 5765, available: no)
output:hdmi-surround-extra2: Saída de Digital Surround 5.1 (HDMI 3) (priority 600, available: no)
output:hdmi-surround-extra2+input:analog-stereo: Saída de Digital Surround 5.1 (HDMI 3) + Entrada de Estéreo analógico (priority 665, available: no)
output:hdmi-surround71-extra2: Saída de Digital Surround 7.1 (HDMI 3) (priority 600, available: no)
output:hdmi-surround71-extra2+input:analog-stereo: Saída de Digital Surround 7.1 (HDMI 3) + Entrada de Estéreo analógico (priority 665, available: no)
output:hdmi-stereo-extra3: Saída de Digital Stereo (HDMI 4) (priority 5700, available: no)
output:hdmi-stereo-extra3+input:analog-stereo: Saída de Digital Stereo (HDMI 4) + Entrada de Estéreo analógico (priority 5765, available: no)
output:hdmi-surround-extra3: Saída de Digital Surround 5.1 (HDMI 4) (priority 600, available: no)
output:hdmi-surround-extra3+input:analog-stereo: Saída de Digital Surround 5.1 (HDMI 4) + Entrada de Estéreo analógico (priority 665, available: no)
output:hdmi-surround71-extra3: Saída de Digital Surround 7.1 (HDMI 4) (priority 600, available: no)
output:hdmi-surround71-extra3+input:analog-stereo: Saída de Digital Surround 7.1 (HDMI 4) + Entrada de Estéreo analógico (priority 665, available: no)
output:hdmi-stereo-extra4: Saída de Digital Stereo (HDMI 5) (priority 5700, available: no)
output:hdmi-stereo-extra4+input:analog-stereo: Saída de Digital Stereo (HDMI 5) + Entrada de Estéreo analógico (priority 5765, available: no)
output:hdmi-surround-extra4: Saída de Digital Surround 5.1 (HDMI 5) (priority 600, available: no)
output:hdmi-surround-extra4+input:analog-stereo: Saída de Digital Surround 5.1 (HDMI 5) + Entrada de Estéreo analógico (priority 665, available: no)
output:hdmi-surround71-extra4: Saída de Digital Surround 7.1 (HDMI 5) (priority 600, available: no)
output:hdmi-surround71-extra4+input:analog-stereo: Saída de Digital Surround 7.1 (HDMI 5) + Entrada de Estéreo analógico (priority 665, available: no)
off: Desligado (priority 0, available: unknown)
active profile: <output:analog-stereo+input:analog-stereo>
sinks:
alsa_output.pci-0000_00_1f.3.analog-stereo/#0: Áudio interno Estéreo analógico
sources:
alsa_output.pci-0000_00_1f.3.analog-stereo.monitor/#0: Monitor of Áudio interno Estéreo analógico
alsa_input.pci-0000_00_1f.3.analog-stereo/#2: Áudio interno Estéreo analógico
ports:
analog-input-internal-mic: Microfone interno (priority 8900, latency offset 0 usec, available: unknown)
properties:
device.icon_name = "audio-input-microphone"
analog-input-mic: Microfone (priority 8700, latency offset 0 usec, available: no)
properties:
device.icon_name = "audio-input-microphone"
analog-output-speaker: Alto-falantes (priority 10000, latency offset 0 usec, available: unknown)
properties:
device.icon_name = "audio-speakers"
analog-output-headphones: Fones de ouvidos (priority 9900, latency offset 0 usec, available: no)
properties:
device.icon_name = "audio-headphones"
hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-3: HDMI / DisplayPort 4 (priority 5600, latency offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-4: HDMI / DisplayPort 5 (priority 5500, latency offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
Distribution (run cat /etc/os-release
):
NAME="Pop!_OS"
VERSION="21.10"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 21.10"
VERSION_ID="21.10"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=impish
UBUNTU_CODENAME=impish
LOGO=distributor-logo-pop-os
Related Application and/or Package Version (run apt policy $PACKAGE NAME
):
gnome-shell:
Installed: 40.5-1ubuntu2pop0~1633630918~21.10~91d3049
Candidate: 40.5-1ubuntu2pop0~1633630918~21.10~91d3049
Version table:
*** 40.5-1ubuntu2pop0~1633630918~21.10~91d3049 1001
1001 http://apt.pop-os.org/release impish/main amd64 Packages
100 /var/lib/dpkg/status
40.5-1ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu impish/main amd64 Packages
Issue/Bug Description:
The screen keeps going to black and powering off my external monitor after a very short window (30 seconds?) and there's no way to configure the time-out nor stop it from doing so.
Steps to reproduce (if you know):
Expected behavior:
Other Notes:
I have configured my power settings not to dim any displays when inactive and to go to blank after 10 minutes. Nothing is being observed properly.
This is also exacerbating pop-os/pop#2074, making computing on this a drag.
I have had this issue for about two months and I was already quite desperate:
My internal laptop screen stopped working when using Pop!_OS. It started on 20.10 and continued after updating to 21.04. Finally someone pointed out, that it was about the time, when you updated your linux kernel.
So with version 5.11.0-7620-generic I have the issue (I also tried previous 5.11.0-something-generic, dont remember the number, but didn't worked either). Then I tried to boot with old kernel from 20.04 (5.8.0-7642-generic) and the issue is gone.
So what happenes:
Hi,
I've Pop!_OS 21.04 running on lemp10 and pipewire+pulseaudio installed. It has been working flawlessly for months. I use my computer attached to an LG (27UN880) monitor and use the audio output of the monitor. Recently, I started to have no audio issues and the only way to fix it is to restart the computer. I see the following output in kernel logs:
[Sal Kas 9 16:59:14 2021] snd_hda_intel 0000:00:1f.3: azx_get_response timeout, switching to polling mode: last cmd=0x20470740
[Sal Kas 9 16:59:15 2021] snd_hda_intel 0000:00:1f.3: No response from codec, disabling MSI: last cmd=0x20470740
[Sal Kas 9 16:59:16 2021] snd_hda_intel 0000:00:1f.3: azx_get_response timeout, switching to single_cmd mode: last cmd=0x20470740
[Sal Kas 9 16:59:16 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 16:59:33 2021] azx_single_send_cmd: 165 callbacks suppressed
[Sal Kas 9 17:01:06 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 17:01:07 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 17:01:20 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 17:04:51 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 17:04:52 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 17:04:57 2021] azx_single_send_cmd: 325 callbacks suppressed
[Sal Kas 9 17:05:34 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 17:05:34 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 17:05:48 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 17:25:04 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 17:25:04 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 17:25:09 2021] azx_single_send_cmd: 325 callbacks suppressed
[Sal Kas 9 17:27:34 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 17:27:34 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 17:27:39 2021] azx_single_send_cmd: 325 callbacks suppressed
[Sal Kas 9 17:33:04 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 17:33:04 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 17:33:09 2021] azx_single_send_cmd: 325 callbacks suppressed
[Sal Kas 9 17:36:03 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 17:36:03 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 17:36:08 2021] azx_single_send_cmd: 325 callbacks suppressed
[Sal Kas 9 17:44:00 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 17:44:00 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 17:44:14 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 17:50:09 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 17:50:09 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 17:50:14 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 18:02:35 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 18:02:36 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 18:02:41 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 18:06:24 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 18:06:24 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 18:06:38 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 18:06:47 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 18:06:47 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 18:07:01 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 18:07:42 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 18:07:42 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 18:07:47 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 18:22:18 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 18:22:19 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 18:22:25 2021] azx_single_send_cmd: 348 callbacks suppressed
[Sal Kas 9 18:22:26 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 18:22:40 2021] azx_single_send_cmd: 499 callbacks suppressed
[Sal Kas 9 18:24:35 2021] kauditd_printk_skb: 143 callbacks suppressed
[Sal Kas 9 18:26:13 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 18:26:18 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 18:30:46 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 18:30:46 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 18:30:51 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 18:30:56 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 18:30:56 2021] azx_single_send_cmd: 496 callbacks suppressed
[Sal Kas 9 18:32:28 2021] azx_single_send_cmd: 142 callbacks suppressed
[Sal Kas 9 18:32:28 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 18:32:33 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 18:36:48 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 18:36:49 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 18:37:02 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 18:37:45 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 18:37:45 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 18:37:50 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 18:50:19 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 18:50:19 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 18:50:24 2021] azx_single_send_cmd: 325 callbacks suppressed
[Sal Kas 9 19:06:37 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 19:06:38 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 19:06:42 2021] azx_single_send_cmd: 358 callbacks suppressed
[Sal Kas 9 19:12:47 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 19:12:47 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 19:12:52 2021] azx_single_send_cmd: 325 callbacks suppressed
[Sal Kas 9 19:17:05 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 19:17:05 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 19:17:10 2021] azx_single_send_cmd: 325 callbacks suppressed
[Sal Kas 9 19:30:11 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 19:30:11 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 19:30:16 2021] azx_single_send_cmd: 325 callbacks suppressed
[Sal Kas 9 19:32:41 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 19:32:42 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 19:32:46 2021] azx_single_send_cmd: 325 callbacks suppressed
[Sal Kas 9 19:41:16 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 19:41:17 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 19:41:21 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 19:50:38 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 19:50:39 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 19:50:43 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 19:57:32 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 19:57:32 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 19:57:37 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 20:05:32 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 20:05:32 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 20:05:37 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 20:24:56 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 20:24:56 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 20:25:01 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 20:27:57 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 20:27:58 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 20:28:03 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 20:40:31 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 20:40:32 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 20:40:37 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 20:46:22 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 20:46:23 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 20:46:30 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 20:46:36 2021] azx_single_send_cmd: 20 callbacks suppressed
[Sal Kas 9 20:46:49 2021] azx_single_send_cmd: 142 callbacks suppressed
[Sal Kas 9 20:46:49 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 20:47:13 2021] azx_single_send_cmd: 348 callbacks suppressed
[Sal Kas 9 20:47:19 2021] azx_single_send_cmd: 199 callbacks suppressed
[Sal Kas 9 20:47:19 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 20:47:24 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 20:47:32 2021] azx_single_send_cmd: 30 callbacks suppressed
[Sal Kas 9 20:51:44 2021] azx_single_send_cmd: 140 callbacks suppressed
[Sal Kas 9 20:51:44 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 20:51:52 2021] azx_single_send_cmd: 353 callbacks suppressed
[Sal Kas 9 20:52:36 2021] azx_single_send_cmd: 142 callbacks suppressed
[Sal Kas 9 20:52:36 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 20:52:43 2021] azx_single_send_cmd: 348 callbacks suppressed
[Sal Kas 9 20:53:50 2021] azx_single_send_cmd: 142 callbacks suppressed
[Sal Kas 9 20:53:51 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 20:54:06 2021] azx_single_send_cmd: 347 callbacks suppressed
[Sal Kas 9 20:54:50 2021] azx_single_send_cmd: 143 callbacks suppressed
[Sal Kas 9 20:54:50 2021] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -5
[Sal Kas 9 20:55:06 2021] azx_single_send_cmd: 347 callbacks suppressed
The following commands (taken from) seem to reconnect the audio output w/o a restart:
# echo 1 > '/sys/bus/pci/devices/0000:00:1f.3/remove'
# echo 1 > /sys/bus/pci/rescan
I don't think I had this issue for a while and believe that it started recently. Can't tell exactly. Could this be happening because of a kernel issue introduced with one of the latest updates?
$ uname -r
5.13.0-7620-generic
Distribution (run cat /etc/os-release
):
21.10
Related Application and/or Package Version (run apt policy $PACKAGE NAME
):
Sound
Issue/Bug Description:
From : https://lore.kernel.org/all/[email protected]/
Gigabyte TRX40 Aorus Master is equipped with two USB-audio devices,
a Realtek ALC1220-VB codec (USB ID 0414:a001) and an ESS SABRE9218 DAC
(USB ID 0414:a000). The latter serves solely for the headphone output
on the front panel while the former serves for the rest I/Os (mostly
for the I/Os in the rear panel but also including the front mic).
Both chips do work more or less with the unmodified USB-audio driver,
but there are a few glitches. The ALC1220-VB returns an error for an
inquiry to some jacks, as already seen on other TRX40-based mobos.
However this machine has a slightly incompatible configuration, hence
the existing mapping cannot be used as is.
Meanwhile the ESS chip seems working without any quirk. But since
both audio devices don't provide any specific names, both cards appear
as "USB-Audio", and it's quite confusing for users.
This patch is an attempt to overcome those issues:
The specific mapping table for ALC1220-VB is provided, reducing the
non-working nodes and renaming the badly chosen controls.
The connector map isn't needed here unlike other TRX40 quirks.
For both USB IDs (0414:a000 and 0414:a001), provide specific card
name strings, so that user-space can identify more easily; and more
importantly, UCM profile can be applied to each.
Steps to reproduce (if you know):
Play something, no sound produced. Sound system shows two usb sound cards with the same name, and outputs are not working
Expected behavior:
Sound
Other Notes:
Distribution (run cat /etc/os-release
):
NAME="Pop!_OS"
VERSION="20.10"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 20.10"
VERSION_ID="20.10"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=groovy
UBUNTU_CODENAME=groovy
LOGO=distributor-logo-pop-os
Linux pop-os 5.8.0-7642-generic pop-os/pop#47161400714920.10~82fb226-Ubuntu SMP Tue Feb 23 02:59:01 UTC x86_64 x86_64 x86_64 GNU/Linux
CVE-2021-3493 is exploitable on the latest version of pop os.
It is patched in Ubuntu
This vulnerability can easily be reproduced with the steps given in this article:
https://ssd-disclosure.com/ssd-advisory-overlayfs-pe/
RGB lights not working with 5.15.5 kernel, it lights on at laptop start and immediately turn of when pop os kicks in, it works on 5.13.
How did you upgrade to 21.10? (Fresh install / Upgrade)
Upgrade
Related Application and/or Package Version (run apt policy $PACKAGE NAME
):
Not specific that I can see, beyond system boot with kernel 5.15.5.
Issue/Bug Description:
Upon boot since upgrade to System76's kernel 5.15.5, I get the following two lines of notification at boot before it gets to a GUI. It still allows boot & function seems normal, so I'm not sure if it's a grave issue that needs addressing,* but just so the team knows.
The lines are:
[[amount of boot time in seconds]] sd 1:0:0:0 [sda] Asking for cache data failed
[[amount of boot time in seconds]] sd 1:0:0:0 [sda] Assuming drive cache: write through
Steps to reproduce (if you know):
Boot my old IC2D T9900/GeForce 9400M/9600M GT laptop with kernel 5.15.5.
Expected behavior:
Boot with no warnings.
Other Notes:
This may or may not be related to the SATA-reading difficulties with kernels 5.15.0 through 5.15.2, which were resolved in Ubuntu's kernel 5.15.3 and System76's kernels 5.15.4 and 5.15.5, as described in (closed) issue pop-os/beta#273. This drive cache warning did not happen in kernel 5.15.4 or previous, though I occasionally get USB warnings in all kernels (and USB works in all ways I can test, upon bootup).
*For System76 team members: Feel free to let me know if this is not a concern in running the system, and if that's the case, close the issue.
@pop-os/engineering @pop-os/quality-assurance - please perform the following on any machines you have access to, when you have time:
lspci -nn | grep Network
How did you upgrade to 21.10? (Fresh install / Upgrade)
Fresh install, all packages up to date at time of post
Related Application and/or Package Version (run apt policy $PACKAGE NAME
):
zfsutils-linux:
Installed: 2.0.6-1ubuntu2
Candidate: 2.0.6-1ubuntu2
Issue/Bug Description:
When installing zfs utils the following error is received
modprobe: FATAL: Module zfs not found in directory /lib/modules/5.15.0-76051500-generic
zfs-import-scan.service is a disabled or a static unit, not starting it.
Following this zfs volumes seem mounted but their contents appear missing
Steps to reproduce (if you know):
sudo apt install zfsutils-linux
Expected behavior:
Kernel module loads and I can access zfs volumes
Other Notes:
Works when I load the old 5.13.0-7260 kernel, I can then mount and access zfs volumes.
zfs module is present at /lib/modules/5.13.0-7620-generic/kernel/zfs
There is no /lib/modules/5.15.0-76051500-generic/kernel/zfs
Having converted Chromebook Pixel 2 which have bdw-rt5677
module.
Ubuntu 21.10 works flawlessly.
Pop!_OS not seeing module, showing dummy output. snd_intel_dspcfg.dsp_driver=2
in kernel parameters, as suggested in arch wiki, doesn't changed much.
dmesg: https://gist.github.com/theLastOfCats/11edeadf7f5147138cd256ccb7a1fb42
thelastofcats@pop-os:~$ uname -a
Linux pop-os 5.15.8-76051508-generic #202112141040~1639505278~21.10~0ede46a SMP Tue Dec 14 22:38:29 U x86_64 x86_64 x86_64 GNU/Linux
thelastofcats@pop-os:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
I'm using a "Lenovo X1 Carbon 7th Gen" laptop, and the latest kernel update to version 5.4.0-37 broke my audio, and causes failures when waking the system up from sleep.
This is related to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697
Seems like you have to update the version of linux-firmware
to at least 1.187
to fix this, but of course i don't know that for sure.
Hello PopOS developers,
Please let me bend your ears with an issue regarding the recent kernel 5.15.5 upgrade.
I have been using Pop!OS 20.04LTS peacefully. Everything had run perfectly until Pop Shop upgraded my system to kernel 5.15.5 a few hours ago. Since then, my laptop fans have been running non-stop even at no load, which had not occurred before. My laptop has been running pretty quietly with the previous kernel 5.13. I'm sensitive to fan noise, so the 5.15.5 kernel is disrupting my work a little bit.
My laptop: Dell Precision 7560, Intel i7-11800H (8 cores), nVidia RTX A4000, 32GB RAM.
I wanted to roll back to kernel 5.13. Unfortunately, I have accidentally hit the apt autoremove
which removed the 5.13 and left me with no option for going back to where my system performed as I loved to.
Could you please let me know if there is any plan in place to address this issue?
Furthermore, is it possible to have an option to disable kernel upgrade in Pop Shop?
Thanks for the great OS. I hope my issue gets your attention.
$ uname -a
Linux precision 5.15.5-76051505-generic #202111250933~1638201579~20.04~09f1aa7-Ubuntu SMP Tue Nov 30 02: x86_64 x86_64 x86_64 GNU/Linux
Distribution (run cat /etc/os-release
):
$ cat /etc/os-release
NAME="Pop!_OS"
VERSION="20.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 20.04 LTS"
VERSION_ID="20.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
LOGO=distributor-logo-pop-os
This is on 21.04 (system details at the end).
Lot's of edits on this sorry, but I put things together as it goes.
Once the EFI stub is read, it takes a while to load the kernel. Normally this starts right away, it takes a good 8-10 seconds from EFI stub: Loaded initrd from command line option to actually load it and get started the boot process. With 5.13 this was instant.
Like a timeout, but actually these are the two oops.
From sudo reboot
to POST screen it takes under 10 seconds in 5.13, but over 27 seconds in 5.15.5. The time added is between the OS finishing and the laptop restarting (before POST). Which links to the next item
The process appears to be completed as usual (some output, I'll check later for details), the screen goes off, power button goes off, but keyboard backlight stays on, keyboard LEDs stay on and the fans stay on. I need to keep the power button for 4 seconds to turn off.
Same behaviour when suspending to RAM. Obviously there is no waking up from it as the power button is irresponsive, opening the lid won't change anything and only thing left to do is hold the power button for a hard power off and then restart as normal.
All of the above are resolved once VT-d is disabled in the bios. So something in this kernel doesn't agree with my laptop's (or CPU) VT-d. I will keep it disabled and keep testing (although I will need it back on for my VM's).
NAME="Pop!_OS"
VERSION="21.04"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 21.04"
VERSION_ID="21.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=hirsute
UBUNTU_CODENAME=hirsute
LOGO=distributor-logo-pop-os
Linux weywot 5.15.5-76051505-generic #202111250933~1638201579~21.04~09f1aa7-Ubuntu SMP Tue Nov 30 02: x86_64 x86_64 x86_64 GNU/Linux
I am using Pop!_OS 20.04 LTS on a Haswell Intel(R) Core(TM) i7-4710HQ CPU.
After updating to kernel 5.8 a couple of days ago, the system constantly crashes on any heavier GPU load. As soon as a race starts in SuperTuxKart, the following happens 100% of the time:
[ 288.066977] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd, in Xorg [1571]
[ 288.066978] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 288.066979] Please file a _new_ bug report at https://gitlab.freedesktop.org/drm/intel/issues/new.
[ 288.066979] Please see https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs for details.
[ 288.066979] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 288.066980] The GPU crash dump is required to analyze GPU hangs, so please always attach it.
[ 288.066980] GPU crash dump saved to /sys/class/drm/card0/error
[ 288.067604] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 288.169353] i915 0000:00:02.0: [drm] Xorg[1571] context reset due to GPU hang
[ 291.138874] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd, in Xorg [1571]
[ 291.138955] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 291.242212] i915 0000:00:02.0: [drm] Xorg[1571] context reset due to GPU hang
[ 297.030397] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd, in Xorg [1571]
[ 297.030448] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[ 297.131629] i915 0000:00:02.0: [drm] Xorg[1571] context reset due to GPU hang
After this, the GPU is reset, all apps are closed and the login screen is started again. This crash can also happen randomly anywhere, but very rarely. However, full load always triggers it.
This problem is exactly the same as shown in this bug report:
https://gitlab.freedesktop.org/drm/intel/-/issues/2024
It seems that this problem was introduced by the newer kernel in Pop. There is a proposed fix (& 0) in the thread. It seems that more and more people will be affected as kernels of 5.7 and above are rolling out in various distributions.
Pop OS! 20.10
Kernel:
Linux pop-os 5.11.0-7612-generic #13161721575720.10~97a8d1a-Ubuntu SMP Thu Apr 1 21:09:17 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Wireless card:
Wireless-AC 9260
Linux Firmware info:
Package: linux-firmware
Version: 1.196+system76161737605820.10~eb867cb
Priority: optional
Section: misc
Maintainer: Ubuntu Kernel Team [email protected]
Installed-Size: 687 MB
Provides: atmel-firmware
Conflicts: atmel-firmware
Breaks: linux-firmware-raspi2 (<= 1.20190819-0ubuntu2), linux-firmware-snapdragon (<= 1.2-0ubuntu1)
Replaces: atmel-firmware, linux-firmware-snapdragon (<= 1.2-0ubuntu1), linux-restricted-common
Download-Size: 159 MB
APT-Manual-Installed: no
APT-Sources: http://ppa.launchpad.net/system76/pop/ubuntu groovy/main amd64 Packages
Description: Firmware for Linux kernel drivers
This package provides firmware used by Linux kernel drivers.
As stated in the title. Reboots do not fix the issue. When playing music in the background and system freezes, music continues playing but everything else becomes unresponsive. Mouse movement is possible while the system is frozen but UI is not responsive for a few seconds. After it unfreezes, all mouse and keyboard actions that were done during the "frozen time" appear as nothing has happend. One could also say that system lags occasionally.
Info:
Linux pop-os 5.3.0-7648-generic #41~1586789791~19.10~9593806-Ubuntu SMP Mon Apr 13 17:50:40 UTC x86_64 x86_64 x86_64 GNU/Linux
Edit_1: Is there any other information that I should append?
Edit_2: Added more details.
After a recent update to the 5.11 kernel, I noticed that the bcmwl-kernel-source wireless driver stopped working. Attempting to reinstall, I noticed the following message during the dkms build:
ERROR (dkms apport): kernel package linux-headers-5.11.0-7612-generic is not supported
This also caused the system76-dkms and system76-io-dkms packages to discontinue working on my system.
I ended up tracking this down to a missing /usr/src/linux-headers-5.11.0-7612-generic/include/generated/autoconf.h file. I tried manually reinstalling linux-headers-5.11.0-7612-generic, which includes the file, but for some reason autoconf.h refuses to install to the destination folder. I had to manually extract it from the .deb and copy it to the destination, after which the dkms modules all build and appear to function correctly.
I suspect this a deb packaging issue, but it's not clear to me how this file is being excluded from installation. I've seen a number of somewhat similar bug reports for broken drivers/firmware that may be linked to this.
➜ ~ ls /dev/{ashmem,binder}
ls: não foi possível acessar '/dev/binder': Arquivo ou diretório inexistente
/dev/ashmem
Software:
Pop!_OS 21.10 (The error was already present before the update to 21.10)
Gnome 40.4.0 on X11
Hardware:
Gaze16
i7-11800H
GeForce RTX 3050 Ti Mobile
Issue/Bug Description:
When I try to shutdown or reboot the PC it just hangs. After some time I have a black screen with a single error being printed forever.
Steps to reproduce (if you know):
Expected behavior:
Correctly shutting down. I don't like to shut it down with the power button every time.
Other Notes:
It might be related to #99, not sure
Distribution (run cat /etc/os-release
):
NAME="Pop!_OS"
VERSION="21.04"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 21.04"
VERSION_ID="21.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=hirsute
UBUNTU_CODENAME=hirsute
LOGO=distributor-logo-pop-os
Related Application and/or Package Version (run apt policy $PACKAGE NAME
):
linux-image-5.15.5-76051505-generic:
Installed: 5.15.5-76051505.202111250933~1638201579~21.04~09f1aa7
Candidate: 5.15.5-76051505.202111250933~1638201579~21.04~09f1aa7
Version table:
*** 5.15.5-76051505.202111250933~1638201579~21.04~09f1aa7 1001
1001 http://ppa.launchpad.net/system76/pop/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
linux-modules-5.15.5-76051505-generic:
Installed: 5.15.5-76051505.202111250933~1638201579~21.04~09f1aa7
Candidate: 5.15.5-76051505.202111250933~1638201579~21.04~09f1aa7
Version table:
*** 5.15.5-76051505.202111250933~1638201579~21.04~09f1aa7 1001
1001 http://ppa.launchpad.net/system76/pop/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
Issue/Bug Description:
The newest kernel seems to rename all webcam/video peripherals to "Video Capture X", the name is not given sequentially and is the same number across devices.
As an example my Elgato Camlink 4K and Trust HD Webcam gets renamed to "Video Capture 3" while my Avermedia LGP2 gets renamed to "Video Capture 4" on any computer with pop os it gets connected to.
I suspect the kernels built in video4linux2 module for some reason sets the ID_V4L_PRODUCT value to "Video Capture X" instead of the name of the device (ID_MODEL?)
Steps to reproduce (if you know):
Update to Kernel 5.15.5-76051505 and reboot to use it.
Switching back to the older kernel will fix the device names again.
Expected behavior:
Video devices to be named normally like this
Other Notes:
I had a laptop that was not fully updated yet and updated everything except the kernel packages and rebooted to see if it was a kernel problem or not before taking the pictures, it turned out to only happen in the new kernel and not the old kernel when i tested.
To make the issue worse, the kernel seems to not dynamically create the names "Video Capture 1", "Video Capture 2", etc.
The name seems to be hard coded for the devices as several devices will appear as "Video Capture 3" for instance on my desktop computer which has multiple cameras connected.
Example image from discord, showing how confusing it will look for the end user to select the "correct" device to use
Hopefully this will be enough info to get this corrected 😃
Hi all
I got POP OS 20.10 on a Razer Blade 15 Advanced 2020 laptop with NVIDIA Graphics. Kernel 5.8.x and earlier working fine no issues. However on newer 5.11.x my laptop freezes on the login screen. Cannot switch to TTY terminal and no keys work apart from power button. I posted thread on PopOS on Reddit and one guy tried to help by asking me to disable 2 DKMS modules I have running which were Razer backlight module and VirtualBox. Even after removing the modules from 5.11.x it still froze.
Cannot post log as once it freezes a restart into old kernel causes logs to be over written.
This is a big issue as POP 21.04 will be running 5.11.x and I cant upgrade as it freezes.
Though my OS is KDE Neon, I'm using Pop!_OS PPA, and the kernel is 5.4.0-7634-generic
, which was from Pop!_OS, so I figured I should report it here.
I recently updated my KDE Neon to 20.04, and audio from the motherboard doesn't get detected. It does, however, detect the one from the GPU.
$ inxi -A
Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio driver: snd_hda_intel
Device-2: NVIDIA GP106 High Definition Audio driver: snd_hda_intel
Device-3: Huawei UVC Camera type: USB driver: snd-usb-audio,uvcvideo
Sound Server: ALSA v: k5.4.0-7634-generic
Before running # alsa force-reload
, $ pacmd list-cards
only detects 2 audio I/O.
$ pacmd list-cards
2 card(s) available.
index: 0
name: <alsa_card.pci-0000_01_00.1>
driver: <module-alsa-card.c>
owner module: 7
properties:
alsa.card = "2"
alsa.card_name = "HDA NVidia"
alsa.long_card_name = "HDA NVidia at 0xdf080000 irq 17"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-0000:01:00.1"
sysfs.path = "/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2"
device.bus = "pci"
device.vendor.id = "10de"
device.vendor.name = "NVIDIA Corporation"
device.product.id = "10f1"
device.product.name = "GP106 High Definition Audio Controller"
device.string = "2"
device.description = "GP106 High Definition Audio Controller"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no)
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: unknown)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no)
output:hdmi-stereo-extra3: Digital Stereo (HDMI 4) Output (priority 5700, available: no)
output:hdmi-surround-extra3: Digital Surround 5.1 (HDMI 4) Output (priority 600, available: no)
output:hdmi-surround71-extra3: Digital Surround 7.1 (HDMI 4) Output (priority 600, available: no)
off: Off (priority 0, available: unknown)
active profile: <output:hdmi-stereo-extra1>
sinks:
alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1/#0: GP106 High Definition Audio Controller Digital Stereo (HDMI 2)
sources:
alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1.monitor/#0: Monitor of GP106 High Definition Audio Controller Digital Stereo (HDMI 2)
ports:
hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: yes)
properties:
device.icon_name = "video-display"
device.product.name = "GF276
"
hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-3: HDMI / DisplayPort 4 (priority 5600, latency offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
index: 1
name: <alsa_card.usb-Ruision_UVC_Camera_20200416-02>
driver: <module-alsa-card.c>
owner module: 8
properties:
alsa.card = "1"
alsa.card_name = "UVC Camera"
alsa.long_card_name = "Ruision UVC Camera at usb-0000:00:14.0-12, high speed"
alsa.driver_name = "snd_usb_audio"
device.bus_path = "pci-0000:00:14.0-usb-0:12:1.2"
sysfs.path = "/devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.2/sound/card1"
udev.id = "usb-Ruision_UVC_Camera_20200416-02"
device.bus = "usb"
device.vendor.id = "12d1"
device.vendor.name = "Huawei Technologies Co., Ltd."
device.product.id = "4321"
device.product.name = "UVC Camera"
device.serial = "Ruision_UVC_Camera_20200416"
device.form_factor = "webcam"
device.string = "1"
device.description = "UVC Camera"
module-udev-detect.discovered = "1"
device.icon_name = "camera-web-usb"
profiles:
input:mono-fallback: Mono Input (priority 1, available: unknown)
input:multichannel-input: Multichannel Input (priority 1, available: unknown)
off: Off (priority 0, available: unknown)
active profile: <input:mono-fallback>
sources:
alsa_input.usb-Ruision_UVC_Camera_20200416-02.mono-fallback/#1: UVC Camera Mono
ports:
analog-input: Analog Input (priority 10000, latency offset 0 usec, available: unknown)
properties:
multichannel-input: Multichannel Input (priority 0, latency offset 0 usec, available: unknown)
properties:
And after running # alsa force-reload
:
$ pacmd list-cards
3 card(s) available.
index: 0
name: <alsa_card.pci-0000_01_00.1>
driver: <module-alsa-card.c>
owner module: 7
properties:
alsa.card = "2"
alsa.card_name = "HDA NVidia"
alsa.long_card_name = "HDA NVidia at 0xdf080000 irq 17"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-0000:01:00.1"
sysfs.path = "/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2"
device.bus = "pci"
device.vendor.id = "10de"
device.vendor.name = "NVIDIA Corporation"
device.product.id = "10f1"
device.product.name = "GP106 High Definition Audio Controller"
device.string = "2"
device.description = "GP106 High Definition Audio Controller"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no)
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: unknown)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no)
output:hdmi-stereo-extra3: Digital Stereo (HDMI 4) Output (priority 5700, available: no)
output:hdmi-surround-extra3: Digital Surround 5.1 (HDMI 4) Output (priority 600, available: no)
output:hdmi-surround71-extra3: Digital Surround 7.1 (HDMI 4) Output (priority 600, available: no)
off: Off (priority 0, available: unknown)
active profile: <output:hdmi-stereo-extra1>
sinks:
alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1/#0: GP106 High Definition Audio Controller Digital Stereo (HDMI 2)
sources:
alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1.monitor/#0: Monitor of GP106 High Definition Audio Controller Digital Stereo (HDMI 2)
ports:
hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: yes)
properties:
device.icon_name = "video-display"
device.product.name = "GF276
"
hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-3: HDMI / DisplayPort 4 (priority 5600, latency offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
index: 1
name: <alsa_card.usb-Ruision_UVC_Camera_20200416-02>
driver: <module-alsa-card.c>
owner module: 8
properties:
alsa.card = "1"
alsa.card_name = "UVC Camera"
alsa.long_card_name = "Ruision UVC Camera at usb-0000:00:14.0-12, high speed"
alsa.driver_name = "snd_usb_audio"
device.bus_path = "pci-0000:00:14.0-usb-0:12:1.2"
sysfs.path = "/devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.2/sound/card1"
udev.id = "usb-Ruision_UVC_Camera_20200416-02"
device.bus = "usb"
device.vendor.id = "12d1"
device.vendor.name = "Huawei Technologies Co., Ltd."
device.product.id = "4321"
device.product.name = "UVC Camera"
device.serial = "Ruision_UVC_Camera_20200416"
device.form_factor = "webcam"
device.string = "1"
device.description = "UVC Camera"
module-udev-detect.discovered = "1"
device.icon_name = "camera-web-usb"
profiles:
input:mono-fallback: Mono Input (priority 1, available: unknown)
input:multichannel-input: Multichannel Input (priority 1, available: unknown)
off: Off (priority 0, available: unknown)
active profile: <input:mono-fallback>
sources:
alsa_input.usb-Ruision_UVC_Camera_20200416-02.mono-fallback/#1: UVC Camera Mono
ports:
analog-input: Analog Input (priority 10000, latency offset 0 usec, available: unknown)
properties:
multichannel-input: Multichannel Input (priority 0, latency offset 0 usec, available: unknown)
properties:
index: 2
name: <alsa_card.pci-0000_00_1f.3>
driver: <module-alsa-card.c>
owner module: 29
properties:
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xdf220000 irq 128"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-0000:00:1f.3"
sysfs.path = "/devices/pci0000:00/0000:00:1f.3/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "a170"
device.product.name = "100 Series/C230 Series Chipset Family HD Audio Controller"
device.form_factor = "internal"
device.string = "0"
device.description = "Built-in Audio"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
input:analog-stereo: Analog Stereo Input (priority 65, available: no)
output:analog-stereo: Analog Stereo Output (priority 6500, available: no)
output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (priority 6565, available: no)
output:analog-surround-21: Analog Surround 2.1 Output (priority 1300, available: no)
output:analog-surround-21+input:analog-stereo: Analog Surround 2.1 Output + Analog Stereo Input (priority 1365, available: no)
output:analog-surround-40: Analog Surround 4.0 Output (priority 1200, available: no)
output:analog-surround-40+input:analog-stereo: Analog Surround 4.0 Output + Analog Stereo Input (priority 1265, available: no)
output:analog-surround-41: Analog Surround 4.1 Output (priority 1300, available: no)
output:analog-surround-41+input:analog-stereo: Analog Surround 4.1 Output + Analog Stereo Input (priority 1365, available: no)
output:analog-surround-50: Analog Surround 5.0 Output (priority 1200, available: no)
output:analog-surround-50+input:analog-stereo: Analog Surround 5.0 Output + Analog Stereo Input (priority 1265, available: no)
output:analog-surround-51: Analog Surround 5.1 Output (priority 1300, available: no)
output:analog-surround-51+input:analog-stereo: Analog Surround 5.1 Output + Analog Stereo Input (priority 1365, available: no)
output:iec958-stereo: Digital Stereo (IEC958) Output (priority 5500, available: unknown)
output:iec958-stereo+input:analog-stereo: Digital Stereo (IEC958) Output + Analog Stereo Input (priority 5565, available: no)
off: Off (priority 0, available: unknown)
active profile: <output:iec958-stereo>
sinks:
alsa_output.pci-0000_00_1f.3.iec958-stereo/#1: Built-in Audio Digital Stereo (IEC958)
sources:
alsa_output.pci-0000_00_1f.3.iec958-stereo.monitor/#2: Monitor of Built-in Audio Digital Stereo (IEC958)
ports:
analog-input-front-mic: Front Microphone (priority 8500, latency offset 0 usec, available: no)
properties:
device.icon_name = "audio-input-microphone"
analog-input-rear-mic: Rear Microphone (priority 8200, latency offset 0 usec, available: no)
properties:
device.icon_name = "audio-input-microphone"
analog-input-linein: Line In (priority 8100, latency offset 0 usec, available: no)
properties:
analog-output-lineout: Line Out (priority 9000, latency offset 0 usec, available: no)
properties:
analog-output-headphones: Headphones (priority 9900, latency offset 0 usec, available: no)
properties:
device.icon_name = "audio-headphones"
iec958-stereo-output: Digital Output (S/PDIF) (priority 0, latency offset 0 usec, available: unknown)
properties:
Is there a way to do fix this so that I don't have to run # alsa force-reload
every boot. I can have it autorun, but I'd prefer to have this fixed.
Here's my system info:
I am required to use bcmwl-kernel-source to enable networking on a 2011 MacBook Pro. After the latest kernel upgrade to 5.11 the networking was broken and failed to load. When attempting to uninstall the package: bcmwl-kernel-source it would not properly uninstall and would not install. The following error occurred: failed to install bcmwl-kernel-source
Error while installing package:
installed bcmwl-kernel-source
package post-installation script
subprocess returned error exit
status 10
I was able to revert back to kernel 5.8 to regain the networking.
How did you upgrade to 21.10? (Fresh install / Upgrade)
Upgrade from 21.04.
Related Application and/or Package Version (run apt policy $PACKAGE NAME
):
Not sure which one would that be.
Issue/Bug Description:
After upgrade the suspend feature stopped to work. Laptop either restarts on wake or becomes totally unresponsive.
Steps to reproduce (if you know):
Expected behavior:
It suspends and wakes up like before.
Other Notes:
I did initially suspect it was because of forcing cgroups v1 as per pop-os/beta#289 my other issue but reverting that change didn't fix the suspend.
I tried live usb with Kubuntu 21.10 and it did work fine. I may try live USB of PopOS 21.10 (I believe you have one?) to verify.
Happy to provide additional information. I planned to reinstall my machine back to 21.04 but decided to postpone by a day or two in case you'd like to get some more information about the problem or have some advice.
On the darp6 running fully updated 20.04, when I plug into ethernet, I get "Connecting..." for a while before it gives up. @brs17 has confirmed the same behavior on galp4.
Distribution (run cat /etc/os-release
): Pop!_OS 21.04
Related Application and/or Package Version (run apt policy $PACKAGE NAME
):
linux-modules-5.11.0-7620-generic:
Installed: 5.11.0-7620.21~1624379747~21.04~3abeff8
Candidate: 5.11.0-7620.21~1624379747~21.04~3abeff8
Version table:
*** 5.11.0-7620.21~1624379747~21.04~3abeff8 1001
1001 http://ppa.launchpad.net/system76/pop/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
Issue/Bug Description:
Whenever I reboot my computer, I am unable to connect to my network via ethernet. After running journalctl -xe
I found the culprit to be the r8169 driver.
Steps to reproduce (if you know):
Expected behavior:
r8169 0000:04:00.0 enp4s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100)
Other Notes:
modprobe r8169
here.r8169-dkms
and run rmmod r8169 && modprobe r8168
after installationlspci
:04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
ip link show
:1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether 18:c0:4d:2f:b0:7d brd ff:ff:ff:ff:ff:ff
Linux versions < 5.6 have overheating/throttling issues on Asus TUF laptops, which just recently had the fixes approved. Can this be added early on to the Pop OS kernel to improve gaming performance?
https://patchwork.kernel.org/patch/11292813/
https://patchwork.kernel.org/patch/11292815/
There is a continuing issue with intel based motherboards and their display ports which causes the system to hang when setting the frame buffer.
So far no boot options have been found to fix the issue.
Unplug one of the displays until the system starts to boot.
master_focal has been rebased in ff6e79e
Distribution (run cat /etc/os-release
):
Pop!_OS 21.04.
Related Application and/or Package Version (run apt policy $PACKAGE NAME
):
Linux kernel.
Issue/Bug Description:
Show-stopping graphic glitches with pinkish horizontal lines blurring the bottom half of the screen, as if this part of the screen could not be refreshed properly. The system is not usable in that state.
Relevant error log: pop-os kernel:
pop-os kernel: i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
I was not able to extract more specific logs.
Steps to reproduce (if you know):
Boot the machine. Every hour or so, the bug occurs, making the machine unusable expect by rebooting.
Expected behavior:
No issue at all on 5.13.
Other Notes:
lspci
> 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
I also have an NVIDIA GPU but not using it (nouveau.modeset=1
and no proprietary driver used either).
The lemp10/darp7 are sometimes not powering off after shutting down (this happens ~4/5 times, but not every time.) When this happens, journalctl indicates the shutdown process is finishing:
Mar 30 14:31:53 pop-os systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Mar 30 14:31:53 pop-os systemd[1]: Reached target Shutdown.
Mar 30 14:31:53 pop-os systemd[1]: Reached target Final Step.
Mar 30 14:31:53 pop-os systemd[1]: systemd-poweroff.service: Succeeded.
Mar 30 14:31:53 pop-os systemd[1]: Finished Power-Off.
Mar 30 14:31:53 pop-os systemd[1]: Reached target Power-Off.
Mar 30 14:31:53 pop-os systemd[1]: Shutting down.
Mar 30 14:31:53 pop-os systemd-shutdown[1]: Syncing filesystems and block devices.
Mar 30 14:31:53 pop-os systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Mar 30 14:31:53 pop-os systemd-journald[513]: Journal stopped
-- Reboot --
Mar 30 14:41:50 pop-os kernel: Linux version 5.11.0-7612-generic (buildd@lgw01-amd64-052) (gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #13~1616168001~20.10~cf74746-Ubuntu SMP Mon Mar 29 17:37:00 UTC (Ubuntu 5.11.0-7612.13~1616168001~20.10~cf74746-generic 5.11.7)
Mar 30 14:41:50 pop-os kernel: Command line: initrd=\EFI\Pop_OS-47ff7a17-79d7-421f-91ee-67f6bd9b0973\initrd.img root=UUID=47ff7a17-79d7-421f-91ee-67f6bd9b0973 ro quiet loglevel=0 systemd.show_status=false splash
The LCD turns off, but the power LED remains solid green, and pushing the power button doesn't turn the machine back on. I'm able to recover from this by holding down the power button until the power LED turns off.
It seems like an EC reset is needed to power on again when this state is reached; I have to wait a second after powering off before it will power on again. I had one case where I had the system plugged in, and it did power off eventually, turning the power LED to orange; but the system wouldn't power on again until I unplugged for a few seconds. If I try to power on without an EC reset, the power LED turns green for a second, then goes back to its previous state.
This seems like it might involve the EC, but I'm starting the issue here because if I downgrade to our previous 5.8 kernel, once I'm booted from that kernel, the system powers off as expected again. Also, the last lemp10 firmware update was nearly two months ago, and I know the issue hasn't been occurring for that long; it just started in the past day or two as we released new kernels (and unfortunately took some time to notice and then narrow down.) This is not happening on the galp5.
I recently disconnected my laptop from my desktop setup and noticed on 20.04lts that my touchpad gestures changed.
Previously scrolling up and down only required two fingers to do so. Now it suddenly requires three to do that same action. I looked in the settings and when I disable the two-finger scrolling it of course disables this functionality in totality.
I also noticed that right clicks no require three fingers as well. My first suspicion is that I installed something that messed with this. My first guess was KDE Plasma, but I have since run timeshift to roll back before I installed KDE and the issue persists.
Happy to try out any possible solutions or gather additional information that could be helpful.
Hello everyone,
after updating to Linux 5.11, Pop!_OS on my Dell Latitude E5270 fails to start up due to a bunch of general protection faults caused by dell_wmi related stuff. I've done a bit of research on the problem and Arch users using similar Dell notebooks also had that issue, which for them got fixed by 5.11.11.
I'm currently running an rc of 5.12 from Ubuntu's Kernel PPA and everything except changing the display brightness works.
I've attached an excerpt from journalctl with the errors, if there's anything I can test (or copy from system logs) for you, tell me. :)
5.8 worked completely fine (even the display brightness).
Thank you very much in advance.
Issue: My WiFi + Bluetooth modules are added into the Ubuntu 20.04 5.4 kernel .. but none of those working in pop OS.
Expected solution: Please add those module from default Ubuntu 5.4 lts kernel. rtw88(8723DE)
Device info :
Os: Pop-OS 20.04 beta (Upgrade 19.10)
Model- HP-da0326tu
Wireless module- Realtek RTL8723DE .
Processor: Intel i3-7100U
RAM-8 GB
How did you upgrade to 21.10? (Fresh install / Upgrade)
Upgraded from 20.04 to 21.10
Dell XPS 15 9550 Laptop
Issue/Bug Description:
Previously had Pop OS 20.04 installed and had no screen flickering, I recently tried the Pop OS 21.10 beta and I'm getting a fair number of screen flickering incidents while using the laptop, the most recent is a severe flickering when taking a screenshot to submit this bug.
Steps to reproduce (if you know):
General use of the computer - nothing intensive like gaming on the 960m GPU. Most recent example, using flameshot to take a screenshot of the terminal.
Expected behavior:
No Flickering while using the laptop.
Distribution (run cat /etc/os-release):
Pop!_OS 21.04.
Kernel Release(uname -r):
5.15.5-76051505-generic
Kernel Version(uname -v):
#202111250933163820157921.04~09f1aa7-Ubuntu SMP Tue Nov 30 02:
Device Info (lsusb):
Bus 001 Device 002: ID 2357:010c TP-Link TL-WN722N v2/v3 [Realtek RTL8188EUS]
Issue/Bug Description:
WiFi reconnecting frequently after Kernel upgrade. Reverted to old Kernel (5.13.0-7620-generic) and it works fine!
Dmesg : dmesg.log
Extracted dmesg releated to wifi.
[ 9.929401] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 9.929888] ee1004 0-0050: 512 byte EE1004-compliant SPD EEPROM, read-only
[ 9.930054] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 9.934841] mei_me 0000:00:16.0: enabling device (0000 -> 0002)
[ 9.943250] input: MSI WMI hotkeys as /devices/virtual/input/input13
[ 9.943469] Chip Version Info: CHIP_8188E_Normal_Chip_TSMC_D_CUT_1T1R_RomVer(0)
[ 9.947472] Bluetooth: Core ver 2.22
[ 9.947485] NET: Registered PF_BLUETOOTH protocol family
[ 9.947486] Bluetooth: HCI device and connection manager initialized
[ 9.947488] Bluetooth: HCI socket layer initialized
[ 9.947489] Bluetooth: L2CAP socket layer initialized
[ 9.947491] Bluetooth: SCO socket layer initialized
[ 9.951426] Intel(R) Wireless WiFi driver for Linux
[ 9.951726] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[ 9.961079] iwlwifi 0000:00:14.3: WRT: Overriding region id 0
[ 9.961083] iwlwifi 0000:00:14.3: WRT: Overriding region id 1
[ 9.961084] iwlwifi 0000:00:14.3: WRT: Overriding region id 2
[ 9.961086] iwlwifi 0000:00:14.3: WRT: Overriding region id 3
[ 9.961087] iwlwifi 0000:00:14.3: WRT: Overriding region id 4
[ 9.961089] iwlwifi 0000:00:14.3: WRT: Overriding region id 6
[ 9.961090] iwlwifi 0000:00:14.3: WRT: Overriding region id 8
[ 9.961091] iwlwifi 0000:00:14.3: WRT: Overriding region id 9
[ 9.961092] iwlwifi 0000:00:14.3: WRT: Overriding region id 10
[ 9.961093] iwlwifi 0000:00:14.3: WRT: Overriding region id 11
[ 9.961094] iwlwifi 0000:00:14.3: WRT: Overriding region id 15
[ 9.961095] iwlwifi 0000:00:14.3: WRT: Overriding region id 16
[ 9.961096] iwlwifi 0000:00:14.3: WRT: Overriding region id 18
[ 9.961098] iwlwifi 0000:00:14.3: WRT: Overriding region id 19
[ 9.961099] iwlwifi 0000:00:14.3: WRT: Overriding region id 20
[ 9.961100] iwlwifi 0000:00:14.3: WRT: Overriding region id 21
[ 9.961102] iwlwifi 0000:00:14.3: WRT: Overriding region id 28
[ 9.961325] iwlwifi 0000:00:14.3: loaded firmware version 46.6b541b68.0 9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm
[ 9.965458] EEPROM ID = 0x8129
[ 9.981156] FAT-fs (nvme0n1p2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 9.981612] FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 9.992708] usbcore: registered new interface driver r8188eu
[ 10.053947] RAPL PMU: hw unit of domain package 2^-14 Joules
[ 10.053948] RAPL PMU: hw unit of domain dram 2^-14 Joules
[ 10.053948] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[ 10.053949] RAPL PMU: hw unit of domain psys 2^-14 Joules
[ 10.059707] input: CUST0001:00 04F3:30FA Mouse as /devices/pci0000:00/0000:00:15.2/i2c_designware.1/i2c-2/i2c-CUST0001:00/0018:04F3:30FA.0001/input/input14
[ 10.066806] input: CUST0001:00 04F3:30FA Touchpad as /devices/pci0000:00/0000:00:15.2/i2c_designware.1/i2c-2/i2c-CUST0001:00/0018:04F3:30FA.0001/input/input16
[ 10.079819] hid-multitouch 0018:04F3:30FA.0001: input,hidraw0: I2C HID v1.00 Mouse [CUST0001:00 04F3:30FA] on i2c-CUST0001:00
[ 10.132467] r8188eu 1-2:1.0 wlx503eaaee9d39: renamed from wlan0
[ 10.149582] iwlwifi 0000:00:14.3: Detected Intel(R) Wireless-AC 9560 160MHz, REV=0x318
[ 10.155783] thermal thermal_zone2: failed to read out thermal zone (-61)
[ 10.177058] Adding 4193784k swap on /dev/mapper/cryptswap. Priority:-2 extents:1 across:4193784k SSFS
[ 10.177515] input: gpio-keys as /devices/platform/ACPI0011:00/gpio-keys.3.auto/input/input17
[ 10.177724] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
[ 10.189042] usbcore: registered new interface driver btusb
[ 10.189845] Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015
[ 10.190863] Bluetooth: hci0: Device revision is 2
[ 10.190866] Bluetooth: hci0: Secure boot is enabled
[ 10.190867] Bluetooth: hci0: OTP lock is enabled
[ 10.190868] Bluetooth: hci0: API lock is enabled
[ 10.190869] Bluetooth: hci0: Debug lock is disabled
[ 10.190870] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 10.195504] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi
[ 10.208734] iwlwifi 0000:00:14.3: base HW address: c8:b2:9b:c1:42:ba
[ 10.257022] intel_tcc_cooling: Programmable TCC Offset detected
[ 10.267210] intel_rapl_common: Found RAPL domain package
[ 10.267213] intel_rapl_common: Found RAPL domain core
[ 10.267214] intel_rapl_common: Found RAPL domain uncore
[ 10.267215] intel_rapl_common: Found RAPL domain dram
[ 10.267216] intel_rapl_common: Found RAPL domain psys
[ 10.277369] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[ 10.281997] iwlwifi 0000:00:14.3 wlo1: renamed from wlan0
[ 10.303574] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
[ 10.303729] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 10.324312] pci 0000:01:00.0: Removing from iommu group 1
[ 10.338156] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 10.338159] Bluetooth: BNEP filters: protocol multicast
[ 10.338163] Bluetooth: BNEP socket layer initialized
[ 10.487012] Generic FE-GE Realtek PHY r8169-0-300:00: attached PHY driver (mii_bus:phy_addr=r8169-0-300:00, irq=MAC)
[ 10.687141] r8169 0000:03:00.0 enp3s0: Link is Down
[ 10.890705] R8188EU: Firmware Version 11, SubVersion 1, Signature 0x88e1
[ 11.263294] MAC Address = 50:3e:aa:ee:9d:39
[ 11.601362] Bluetooth: hci0: Waiting for firmware download to complete
[ 11.601829] Bluetooth: hci0: Firmware loaded in 1373361 usecs
[ 11.601862] Bluetooth: hci0: Waiting for device to boot
[ 11.615835] Bluetooth: hci0: Device booted in 13662 usecs
[ 11.616128] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-17-16-1.ddc
[ 11.617867] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 11.620871] Bluetooth: hci0: Firmware revision 0.1 build 166 week 30 2021
[ 11.679947] Bluetooth: hci0: MSFT filter_enable is already on
[ 11.692377] NET: Registered PF_ALG protocol family
[ 12.600931] rfkill: input handler disabled
[ 12.837037] R8188EU: INFO indicate disassoc
[ 13.227329] R8188EU: INFO sta recv deauth reason code(9) sta:d8:38:fc:35:d8:f8, ignore = 0
[ 13.231040] R8188EU: INFO indicate disassoc
[ 15.177565] R8188EU: INFO sta recv deauth reason code(9) sta:d8:38:fc:35:db:c8, ignore = 0
[ 15.178331] R8188EU: INFO sta recv deauth reason code(9) sta:d8:38:fc:35:db:c8, ignore = 0
[ 15.182999] R8188EU: INFO indicate disassoc
[ 19.211041] R8188EU: INFO indicate disassoc
[ 21.903552] Bluetooth: RFCOMM TTY layer initialized
[ 21.903558] Bluetooth: RFCOMM socket layer initialized
[ 21.903562] Bluetooth: RFCOMM ver 1.11
[ 22.096002] rfkill: input handler enabled
[ 22.601457] R8188EU: INFO sta recv deauth reason code(9) sta:d8:38:fc:35:db:c8, ignore = 0
[ 22.606993] R8188EU: INFO indicate disassoc
[ 24.298984] R8188EU: INFO assoc success
[ 25.081824] rfkill: input handler disabled
[ 25.333784] IPv6: ADDRCONF(NETDEV_CHANGE): wlx503eaaee9d39: link becomes ready
[ 55.581614] R8188EU: INFO indicate disassoc
[ 59.275001] R8188EU: INFO indicate disassoc
[ 66.570726] R8188EU: INFO sta recv deauth reason code(9) sta:d8:38:fc:35:d8:f8, ignore = 0
[ 66.575006] R8188EU: INFO indicate disassoc
[ 68.521387] R8188EU: INFO sta recv deauth reason code(9) sta:d8:38:fc:35:db:c8, ignore = 0
[ 68.523056] R8188EU: INFO indicate disassoc
[ 70.479152] R8188EU: INFO sta recv deauth reason code(9) sta:d8:38:fc:35:db:c8, ignore = 0
[ 70.483019] R8188EU: INFO indicate disassoc
[ 72.425644] R8188EU: INFO sta recv deauth reason code(9) sta:d8:38:fc:35:db:c8, ignore = 0
[ 72.427036] R8188EU: INFO indicate disassoc
[ 74.049471] R8188EU: INFO assoc success
[ 94.312191] R8188EU: INFO sta recv deauth reason code(6) sta:d8:38:fc:35:db:c8, ignore = 0
[ 94.314664] R8188EU: INFO indicate disassoc
[ 95.964334] R8188EU: INFO assoc success
Hey System76 team,
I'm having a major issue since installing a clean version of Pop 20.10 onto my desktop PC earlier this month. Once or twice per day, my system will "hard lock" requiring a power cycle. I'm unable to pin down a culprit as I'm doing different things each time.
This is my audio/video production rig, so you can imagine it's a bit of a problem to have.
CPU: AMD Ryzen 9 3900X
GPU: 1x Radeon RX 6800 XT, 1x Radeon RX 6800
RAM: 32GB G.Skill Trident Z @ 3400MHz
OS: Pop OS 20.10
Kernel: 5.11.0-7612-generic
GNOME version: 3.38.3
Please help, thank you for being awesome!
CLEVO NH5X and possibly NH7X series
Looks like there is a possible hacky work around.
see:
Can someone at system76 reach out to Clevo to see if they can fix this issue?
I tried re-compiling the kernel/modules with the fix, but got about as far as sudo make install && sudo reboot -h
and had it stall on boot up.
Not sure if system76 sells the NH58HPQ, but that is the version I was using.
Just figured I'd let y'all know
This is a bug because installing Microsoft Edge on linux is commits treason in the linux kernel.
Commiting treason in linux immediatly bricks one's computer.
OS: Ubuntu 20.04.2 LTS
Kernel: 5.11.0-7612.13~1617215757~20.04~97a8d1a
Hardware: Lemur Pro 9
Processor: i7-10510U
The system will randomly freeze and require hard reboot after a few minute. Ubuntu's official 5.8 kernel works without any issue.
Hello,
I have a Titan XP and GTX970, when I start PopOS only the screen on Titan XP work, the screen on GTX970 not working, I took the iso with Nvidia driver
Thanks for help
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.