http://bugzilla.opensuse.org/show_bug.cgi?id=1188954
Bug ID: 1188954
Summary: black screen on initial X open on Kaveri Radeon R7,
/dev/dri/card0: No such file or directory with
radeon.cik_support=0 amdgpu.cik_support=1
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: mrmazda(a)earthlink.net
QA Contact: qa-bugs(a)suse.de
CC: sndirsch(a)suse.com
Found By: ---
Blocker: ---
Created attachment 851460
--> http://bugzilla.opensuse.org/attachment.cgi?id=851460&action=edit
Xorg.0.log and dmesg
Initial summary:
black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such
file or directory with radeon.cik_support=0 amdgpu.cik_support=1
To reproduce:
1-boot with included on kernel cmdline radeon.cik_support=0
amdgpu.cik_support=1
2-wait for X to fail to start
3-login on a tty
4-systemctl restart xdm
Actual behavior:
1-X fails to start, finding no /dev/dri/card0, leaving login prompt on tty1 on
display screen
2-X starts normally using amdgpu DDX driver
Expected behavior:
1-X starts normally using amdgpu DDX driver
Tested with kernels 5.12.13, 5.11.16, 5.7.11
# inxi -SGIay
System:
Host: asa88 Kernel: 5.12.13-1-default x86_64 bits: 64 compiler: gcc
v: 11.1.1
parameters: BOOT_IMAGE=/boot/vmlinuz root=LABEL=tvgp07stw noresume
ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0
radeon.cik_support=0 amdgpu.cik_support=1 video=1024x768@60
video=1440x900@60 drm.debug=0x1e log_buf_len=1M
Console: tty pts/0 DM: TDM Distro: openSUSE Tumbleweed 20210730
Graphics:
Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASUSTeK driver: amdgpu
v: kernel alternate: radeon bus-ID: 00:01.0 chip-ID: 1002:130f
class-ID: 0300
Display: server: X.org 1.20.12 driver: loaded: vesa
unloaded: fbdev,modesetting alternate: ati
Message: Advanced graphics data unavailable for root.
Info:...inxi: 3.3.06
Comments:
1-without radeon.cik_support=0 amdgpu.cik_support=1 on cmdline, X cannot be
coaxed into using amdgpu DDX driver via /etc/X11/xorg.conf.d/*conf
2-without radeon.cik_support=0 amdgpu.cik_support=1, greeter startup completes
(normally, on first try) using modesetting DIX driver
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1191924
Bug ID: 1191924
Summary: kernel-source.git/README outdated
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: Linux
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: ohering(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
There is a section "Before You Commit -- Things To Check" in
kernel-source.git/README, it will likely not work out of the box.
According to rpm/kernel-binary.spec.in, at least three more packages beside the
obvious gcc/make/patch need to be installed:
BuildRequires: libopenssl-devel
BuildRequires: libelf-devel
BuildRequires: dwarves >= 1.21
Furthermore rapidquilt is not mentioned. It is not strictly required, but one
can hardly live without it.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1190261
Bug ID: 1190261
Summary: Kernel scriptlets: XXX: Only call mokutil if UEFI and
shim are used
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: martin.wilck(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Spin-off from bug 1189841.
From https://github.com/openSUSE/suse-module-tools/pull/33:
@mwilck:
so why not test this? e.g. like this:
if [ "$(mokutil --sb-state 2>/dev/null)" = "SecureBoot enabled" ]; then
...
fi
@hramrach:
???
The part that github displays as context for this comment does not look
relevant
@hramrach hramrach 21 hours ago Member
Right, if you refer to
XXX: Only call mokutil if UEFI and shim are used
then I have no opinion on that.
Should be probably handled in a separate bug and the implications of any
possible check discussed to death.
@hramrach hramrach 21 hours ago Member
Actually, there is the problem that on arm64 you suddenly get from no shim to
shim on SP update without any warning so this is really hairy to get right.
Really deserves a separate bug.
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189826
Bug ID: 1189826
Summary: Severe screen flickering with kernel 5.13.12-1-default
and i915
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: openSUSE Tumbleweed
Status: NEW
Severity: Major
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: javier(a)opensuse.org
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
My laptop's screen flickers so much with 5.13.12 that it renders my laptop
unusable.
One workaround is to close and open the lid. After resuming, it works fine -
there is no flickering.
Booting up from the KDE Live image works fine. I have used the same Tumbleweed
version (20210820) as the one I have installed on my laptop. The only
difference is that I have an encrypted /home partition on my laptop's SSD.
Tested kernels:
5.10.16-1.3: OK
5.11.4-1.3: NON-OK
5.12.12-1: NON-OK
5.13.12-1: NON-OK
KDE Plasma 5.22.4
KDE Frameworks 5.85.0
Qt 5.15.2
See the attachments for more details.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1189283
Bug ID: 1189283
Summary: kernel-obs-build needs af_alg
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: fvogt(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
libkcapi got updated to 1.3.1 (https://build.opensuse.org/request/show/910806)
and apparently gnutls picks that up now and enables support for it.
It seems like that depends on AF_ALG sockets though, which are currently not
enabled in kernel-obs-build (missing af_alg module), so various builds (libzip,
libvirt) fail with
libkcapi - Error: AF_ALG: socket syscall failed (errno: -97)
I'm not sure whether just af_alg is enough, it might need some other modules as
well.
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1188352
Bug ID: 1188352
Summary: Can't enter LUKS password since kernel 5.13 on
Pinebook Pro
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: aarch64
OS: openSUSE Tumbleweed
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: jonasdcdm(a)mailbox.org
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 851029
--> http://bugzilla.opensuse.org/attachment.cgi?id=851029&action=edit
dmesg
Since the upgrade to kernel 5.13 it's no longer possible to enter the LUKS
password on boot. The physical keyboard works fine in GRUB, but the LUKS prompt
won't see it, it doesn't register any key press.
Entering the password via serial console works, and the Pinebook Pro boots to
the desktop, where the physical keyboard works again.
Kernel 5.12.13-1 is still working fine.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1179894
Bug ID: 1179894
Summary: warnings in OBS builds from kernel+initrd about
"Warning: running kernel does not support fscaps"
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: okurz(a)suse.com
QA Contact: qa-bugs(a)suse.de
CC: fvogt(a)suse.com, jslaby(a)suse.com, msuchanek(a)suse.com,
okurz(a)suse.com, thomas.blume(a)suse.com, tiwai(a)suse.com
Depends on: 1178401
Found By: ---
Blocker: ---
+++ This bug was initially created as a clone of Bug #1178401 +++
## Observation
https://build.opensuse.org/build/openSUSE:Factory/images/local/000product:o…
shows repeated warnings about:
```
[ 14s] Warning: running kernel does not support fscaps
[ 14s] Warning: running kernel does not support fscaps
[ 14s] Warning: running kernel does not support fscaps
[ 14s] Warning: running kernel does not support fscaps
[ 14s] Warning: running kernel does not support fscaps
[ 14s] Warning: running kernel does not support fscaps
[ 14s] Warning: running kernel does not support fscaps
[ 14s] Warning: running kernel does not support fscaps
```
## Steps to reproduce
Seemingly reproducible in any build of packages, e.g.
https://build.opensuse.org/public/build/openSUSE:Factory/standard/x86_64/00…
shows the same
## Expected result
Only errors and warnings in the log that I as package/project maintainer can
fix
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1178463
Bug ID: 1178463
Summary: Flood of "usb usb{2,6}-port1: Cannot enable." messages
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: lmb(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 843325
--> https://bugzilla.suse.com/attachment.cgi?id=843325&action=edit
lsusb -vv
With the 5.10.0rc2 kernel from Kernel:HEAD, I'm experiencing a flood of:
...
[ 372.567942] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 374.686509] usb usb6-port1: Cannot enable. Maybe the USB cable is bad?
[ 377.026495] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 378.986503] usb usb6-port1: Cannot enable. Maybe the USB cable is bad?
[ 381.446415] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 383.290504] usb usb6-port1: Cannot enable. Maybe the USB cable is bad?
[ 385.918496] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 387.586478] usb usb6-port1: Cannot enable. Maybe the USB cable is bad?
[ 390.386475] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 391.894454] usb usb6-port1: Cannot enable. Maybe the USB cable is bad?
...
The XPS 13 is connected to a Belkin Thunberbird dock. As far as I can tell,
except for these messages, all USB connected peripherals (keyboard, mouse,
webcam) are working.
Attaching lsusb -vv and dmesg output.
--
You are receiving this mail because:
You are the assignee for the bug.