11:56 a.m.
Dear Fellow Fedora users,
I have installed and tried to boot the 6.6.X kernels in fedora and now the latest one
6.7.3 one and
have not seen a successful boot of such a kernel. I have had to delete the kernels every
time I try them.
$ sudo dnf remove kernel-core-6.7.3-200.fc39.x86_64
Dependencies resolved.
================================================================================
Package Arch Version Repository Size
================================================================================
Removing:
kernel-core x86_64 6.7.3-200.fc39 @updates 66 M
Removing dependent packages:
kernel x86_64 6.7.3-200.fc39 @updates 0
kernel-modules x86_64 6.7.3-200.fc39 @updates 57 M
kernel-modules-core x86_64 6.7.3-200.fc39 @updates 32 M
kernel-modules-extra x86_64 6.7.3-200.fc39 @updates 2.4 M
Transaction Summary
================================================================================
Remove 5 Packages
Freed space: 157 M
Is this ok [y/N]: y
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Erasing : kernel-modules-extra-6.7.3-200.fc39.x86_64 1/5
Running scriptlet: kernel-modules-extra-6.7.3-200.fc39.x86_64 1/5
Erasing : kernel-6.7.3-200.fc39.x86_64 2/5
Running scriptlet: kernel-6.7.3-200.fc39.x86_64 2/5
Erasing : kernel-modules-6.7.3-200.fc39.x86_64 3/5
Running scriptlet: kernel-modules-6.7.3-200.fc39.x86_64 3/5
Erasing : kernel-modules-core-6.7.3-200.fc39.x86_64 4/5
Running scriptlet: kernel-core-6.7.3-200.fc39.x86_64 5/5
Erasing : kernel-core-6.7.3-200.fc39.x86_64 5/5
Running scriptlet: kernel-core-6.7.3-200.fc39.x86_64 5/5
Verifying : kernel-6.7.3-200.fc39.x86_64 1/5
Verifying : kernel-core-6.7.3-200.fc39.x86_64 2/5
Verifying : kernel-modules-6.7.3-200.fc39.x86_64 3/5
Verifying : kernel-modules-core-6.7.3-200.fc39.x86_64 4/5
Verifying : kernel-modules-extra-6.7.3-200.fc39.x86_64 5/5
Removed:
kernel-6.7.3-200.fc39.x86_64
kernel-core-6.7.3-200.fc39.x86_64
kernel-modules-6.7.3-200.fc39.x86_64
kernel-modules-core-6.7.3-200.fc39.x86_64
kernel-modules-extra-6.7.3-200.fc39.x86_64
Complete!
olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ sudo lspci
00:00.0 PCI bridge: Intel Corporation Device 4c53 (rev 01)
00:02.0 VGA compatible controller: Intel Corporation RocketLake-S GT1 [UHD Graphics 730]
(rev 04)
00:04.0 Signal processing controller: Intel Corporation Device 4c03 (rev 01)
00:08.0 System peripheral: Intel Corporation Device 4c11 (rev 01)
00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal Controller
00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller
00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM
00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi
00:15.0 Serial bus controller: Intel Corporation Comet Lake PCH Serial IO I2C Controller
#0
00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller
00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller
00:1b.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #21 (rev f0)
00:1c.0 PCI bridge: Intel Corporation Device 06bc (rev f0)
00:1f.0 ISA bridge: Intel Corporation H470 Chipset LPC/eSPI Controller
00:1f.3 Audio device: Intel Corporation Device f1c8
00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller
00:1f.5 Serial bus controller: Intel Corporation Comet Lake PCH SPI Controller
02:00.0 Non-Volatile memory controller: KIOXIA Corporation NVMe SSD Controller BG4
(DRAM-less)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 2600 (rev 21)
olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ sudo lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader
Controller
Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$
$ xrandr
Screen 0: minimum 16 x 16, current 1600 x 900, maximum 32767 x 32767
HDMI-2 connected primary 1600x900+0+0 (normal left inverted right x axis y axis) 440mm x
250mm
1600x900 59.95*+
1152x864 59.96
1024x768 59.92
800x600 59.86
640x480 59.38
320x240 59.52
1440x900 59.89
1280x800 59.81
1152x720 59.97
960x600 59.63
928x580 59.88
800x500 59.50
768x480 59.90
720x480 59.71
640x400 59.95
320x200 58.96
1368x768 59.88
1280x720 59.86
1024x576 59.90
864x486 59.92
720x400 59.55
640x350 59.77
When booting the kernels I tried to see where they were stopping, the boot showed loading
the usb mouse/keyboard combination, but showed disabled. I tried booting with regular usb
mouse and keyboard and the same thing happens, the kernel does not boot. Secure boot is
on. Do not know what to do to get the newer kernels to boot. I dont create a bugzilla
because I no longer use the email that was associated with bugzilla. The newer kernels do
work on raspberry pi though, so it may be related to the hardware? with secure boot and
signed kernels, I cannot seem to find what is going on.
Is there a BIOS setting I can try? RAID ON/RAID OFF, running on nvme0 internel disk. Was
running on a solid state disk(SSD) before.
Best Regards,
Antonio
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
12:48 p.m.
olivares33561 composed on 2024-02-08 17:56 +0000):
I have installed and tried to boot the 6.6.X kernels in fedora and
now the latest one 6.7.3 one and
have not seen a successful boot of such a kernel. I have had to delete the kernels every
time I try them.
...
$ sudo lspci
00:00.0 PCI bridge: Intel Corporation Device 4c53 (rev 01)
00:02.0 VGA compatible controller: Intel Corporation RocketLake-S GT1 [UHD Graphics 730]
(rev 04)
00:04.0 Signal processing controller: Intel Corporation Device 4c03 (rev 01)
00:08.0 System peripheral: Intel Corporation Device 4c11 (rev 01)
00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal
Controller
00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller
00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM
00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi
00:15.0 Serial bus controller: Intel Corporation Comet Lake PCH Serial IO I2C Controller
#0
00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller
00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller
00:1b.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #21 (rev f0)
00:1c.0 PCI bridge: Intel Corporation Device 06bc (rev f0)
00:1f.0 ISA bridge: Intel Corporation H470 Chipset LPC/eSPI Controller
00:1f.3 Audio device: Intel Corporation Device f1c8
00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller
00:1f.5 Serial bus controller: Intel Corporation Comet Lake PCH SPI Controller
02:00.0 Non-Volatile memory controller: KIOXIA Corporation NVMe SSD Controller BG4
(DRAM-less)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 2600 (rev 21)
olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ sudo lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader
Controller
Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
...
When booting the kernels I tried to see where they were stopping, the
boot showed loading the usb mouse/keyboard combination, but showed disabled. I tried
booting with regular usb mouse and keyboard and the same thing happens, the kernel does
not boot. Secure boot is on. Do not know what to do to get the newer kernels to boot. I
dont create a bugzilla because I no longer use the email that was associated with
bugzilla. The newer kernels do work on raspberry pi though, so it may be related to the
hardware? with secure boot and signed kernels, I cannot seem to find what is going on.
Is there a BIOS setting I can try? RAID ON/RAID OFF, running on
nvme0 internel disk. Was running on a solid state disk(SSD) before.
I have same GPU as you, maybe same CPU, running F39 on NVME, though not with
secure boot. I have no such trouble as yet with any kernel since 6.5:
# inxi -C --vs --zl --hostname
inxi 3.3.33-00 (2024-02-06)
CPU:
Info: 6-core model: 11th Gen Intel Core i5-11400 bits: 64 type: MT MCP
cache: L2: 3 MiB
Speed (MHz): avg: 809 min/max: 800/4400 cores: 1: 800 2: 800 3: 800 4: 800
5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 910 12: 801
# inxi -GSaz
System:
Kernel: 6.6.13-200.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.40-13.fc39 clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz root=LABEL=tm8p15f39 noresume
audit=0 ipv6.disable=1 net.ifnames=0 consoleblank=0 preempt=full
mitigations=off
Desktop: TDE (Trinity) v: R14.1.1 tk: Qt v: 3.5.0 wm: Twin v: 3.0
with: kicker vt: 7 dm: 1: TDM 2: XDM Distro: Fedora Linux 39 (Thirty Nine)
Graphics:
Device-1: Intel RocketLake-S GT1 [UHD Graphics 730] vendor: ASUSTeK
driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21
ports: active: DP-1,HDMI-A-1,HDMI-A-2 empty: HDMI-A-3 bus-ID: 00:02.0
chip-ID: 8086:4c8b class-ID: 0300
Display: x11 server: X.Org v: 1.20.14 compositor: Twin v: 3.0 driver: X:
loaded: modesetting dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 3600x2640 s-dpi: 120 s-size: 762x558mm (30.00x21.97")
s-diag: 944mm (37.18")
Monitor-1: DP-1 pos: primary,bottom-l model: Acer K272HUL serial: <filter>
built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2
size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
max: 2560x1440 min: 720x400
Monitor-2: HDMI-A-1 mapped: HDMI-1 pos: top-left model: NEC EA243WM
serial: <filter> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
max: 1920x1200 min: 640x480
Monitor-3: HDMI-A-2 mapped: HDMI-2 pos: top-right model: Dell P2213
serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes:
max: 1680x1050 min: 720x400
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast surfaceless: drv: iris x11: drv: iris
inactive: gbm,wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 23.3.3 glx-v: 1.4
direct-render: yes renderer: Mesa Intel Graphics (RKL GT1)
device-ID: 8086:4c8b memory: 29.48 GiB unified: yes
#
What does your kernel cmdline contain? What exactly does "do not boot" mean?
GUI
login greeter is not reached? No login prompt available on any of the vttys? Does
appending nomodeset to the linu line after striking the E key at the boot menu
enable "boot" to complete?
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
8:16 a.m.
Dear Sir,
will give it a try with nomodeset added to kernel line and see if that gets me through.
Otherwise I will report back.
Questions were replied inline.
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
On Thursday, February 8th, 2024 at 12:48 PM, Felix Miata <mrmazda(a)earthlink.net>
wrote:
olivares33561 composed on 2024-02-08 17:56 +0000):
> I have installed and tried to boot the 6.6.X kernels in fedora and now the latest
one 6.7.3 one and
> have not seen a successful boot of such a kernel. I have had to delete the kernels
every time I try them.
...
> $ sudo lspci
> 00:00.0 PCI bridge: Intel Corporation Device 4c53 (rev 01)
> 00:02.0 VGA compatible controller: Intel Corporation RocketLake-S GT1 [UHD Graphics
730] (rev 04)
> 00:04.0 Signal processing controller: Intel Corporation Device 4c03 (rev 01)
> 00:08.0 System peripheral: Intel Corporation Device 4c11 (rev 01)
> 00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal
Controller
> 00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller
> 00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM
> 00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi
> 00:15.0 Serial bus controller: Intel Corporation Comet Lake PCH Serial IO I2C
Controller #0
> 00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller
> 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller
> 00:1b.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #21 (rev f0)
> 00:1c.0 PCI bridge: Intel Corporation Device 06bc (rev f0)
> 00:1f.0 ISA bridge: Intel Corporation H470 Chipset LPC/eSPI Controller
> 00:1f.3 Audio device: Intel Corporation Device f1c8
> 00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller
> 00:1f.5 Serial bus controller: Intel Corporation Comet Lake PCH SPI Controller
> 02:00.0 Non-Volatile memory controller: KIOXIA Corporation NVMe SSD Controller BG4
(DRAM-less)
> 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 2600 (rev 21)
> olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ sudo lsusb
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
> Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader
Controller
> Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
...
> When booting the kernels I tried to see where they were stopping, the boot showed
loading the usb mouse/keyboard combination, but showed disabled. I tried booting with
regular usb mouse and keyboard and the same thing happens, the kernel does not boot.
Secure boot is on. Do not know what to do to get the newer kernels to boot. I dont create
a bugzilla because I no longer use the email that was associated with bugzilla. The newer
kernels do work on raspberry pi though, so it may be related to the hardware? with secure
boot and signed kernels, I cannot seem to find what is going on.
> Is there a BIOS setting I can try? RAID ON/RAID OFF, running on nvme0 internel disk.
Was running on a solid state disk(SSD) before.
I have same GPU as you, maybe same CPU, running F39 on NVME, though not with
secure boot. I have no such trouble as yet with any kernel since 6.5:
# inxi -C --vs --zl --hostname
inxi 3.3.33-00 (2024-02-06)
CPU:
Info: 6-core model: 11th Gen Intel Core i5-11400 bits: 64 type: MT MCP
cache: L2: 3 MiB
Speed (MHz): avg: 809 min/max: 800/4400 cores: 1: 800 2: 800 3: 800 4: 800
5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 910 12: 801
# inxi -GSaz
System:
Kernel: 6.6.13-200.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.40-13.fc39 clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz root=LABEL=tm8p15f39 noresume
audit=0 ipv6.disable=1 net.ifnames=0 consoleblank=0 preempt=full
mitigations=off
Desktop: TDE (Trinity) v: R14.1.1 tk: Qt v: 3.5.0 wm: Twin v: 3.0
with: kicker vt: 7 dm: 1: TDM 2: XDM Distro: Fedora Linux 39 (Thirty Nine)
Graphics:
Device-1: Intel RocketLake-S GT1 [UHD Graphics 730] vendor: ASUSTeK
driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21
ports: active: DP-1,HDMI-A-1,HDMI-A-2 empty: HDMI-A-3 bus-ID: 00:02.0
chip-ID: 8086:4c8b class-ID: 0300
Display: x11 server: X.Org v: 1.20.14 compositor: Twin v: 3.0 driver: X:
loaded: modesetting dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 3600x2640 s-dpi: 120 s-size: 762x558mm (30.00x21.97")
s-diag: 944mm (37.18")
Monitor-1: DP-1 pos: primary,bottom-l model: Acer K272HUL serial: <filter>
built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2
size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
max: 2560x1440 min: 720x400
Monitor-2: HDMI-A-1 mapped: HDMI-1 pos: top-left model: NEC EA243WM
serial: <filter> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
max: 1920x1200 min: 640x480
Monitor-3: HDMI-A-2 mapped: HDMI-2 pos: top-right model: Dell P2213
serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes:
max: 1680x1050 min: 720x400
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast surfaceless: drv: iris x11: drv: iris
inactive: gbm,wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 23.3.3 glx-v: 1.4
direct-render: yes renderer: Mesa Intel Graphics (RKL GT1)
device-ID: 8086:4c8b memory: 29.48 GiB unified: yes
#
What does your kernel cmdline contain?
olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ inxi -C --vs --zl
--hostname
bash: inxi: command not found...
Install package 'inxi' to provide command 'inxi'? [N/y] y
* Waiting in queue...
* Loading list of packages....
The following packages have to be installed:
freeipmi-1.6.11-1.fc39.x86_64 IPMI remote console and system management software
hddtemp-0.3-0.54.beta15.fc39.x86_64 Hard disk temperature tool
inxi-3.3.31-1.fc39.noarch A full featured system information script
ipmitool-1.8.19-4.fc39.x86_64 Utility for IPMI control
lm_sensors-3.6.0-14.fc39.x86_64 Hardware monitoring tools
perl-Cpanel-JSON-XS-4.37-4.fc39.x86_64 JSON::XS for Cpanel, fast and correct serializing
perl-JSON-XS-1:4.03-11.fc39.x86_64 JSON serializing/de-serializing, done correctly and
fast
perl-Types-Serialiser-1.01-9.fc39.noarch Simple data types for common serialization
formats
perl-XML-Dumper-0.81-47.fc39.noarch Perl module for dumping Perl objects from/to XML
perl-XML-Parser-2.46-15.fc39.x86_64 Perl module for parsing XML documents
perl-common-sense-3.7.5-14.fc39.x86_64 "Common sense" Perl defaults
wmctrl-1.07-35.fc39.x86_64 Command line tool to interact with an X Window Manager
Proceed with changes? [N/y] y
* Waiting in queue...
* Waiting for authentication...
* Waiting in queue...
* Downloading packages... Failed to install packages: Cannot download
Packages/i/inxi-3.3.31-1.fc39.noarch.rpm: All mirrors were tried; Last error: Status code:
404 for
https://mirror.umd.edu/fedora/linux/updates/39/Everything/x86_64/Packages...
(IP: 128.8.207.141)
olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ grubby --info=DEFAULT
grep: /boot/grub2/grubenv: Permission denied
olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ sudo grubby --info=DEFAULT
[sudo] password for olivares:
index=0
kernel="/boot/vmlinuz-6.7.4-200.fc39.x86_64"
args="ro rootflags=subvol=root rhgb quiet"
root="UUID=8ff57a6b-2a55-4e9d-870d-855d68d35bee"
initrd="/boot/initramfs-6.7.4-200.fc39.x86_64.img"
title="Fedora Linux (6.7.4-200.fc39.x86_64) 39 (Workstation Edition)"
id="146af94111b0438ea94534f851a76045-6.7.4-200.fc39.x86_64"
olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$
What exactly does "do not boot" mean? GUI
login greeter is not reached? No login prompt available on any of the
vttys?
booting just hangs do not reach GUI
Does
appending nomodeset to the linu line after striking the E key at the
boot menu
enable "boot" to complete?
will try nomodeset to line and report back.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
--
Best Regards,
Antonio
11:21 a.m.
Dear fedora users,
On Tuesday, February 13th, 2024 at 8:16 AM, olivares33561 via users
<users(a)lists.fedoraproject.org> wrote:
Dear Sir,
will give it a try with nomodeset added to kernel line and see if that gets me through.
Otherwise I will report back.
Questions were replied inline.
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
On Thursday, February 8th, 2024 at 12:48 PM, Felix Miata mrmazda(a)earthlink.net wrote:
> olivares33561 composed on 2024-02-08 17:56 +0000):
>
> > I have installed and tried to boot the 6.6.X kernels in fedora and now the
latest one 6.7.3 one and
> > have not seen a successful boot of such a kernel. I have had to delete the
kernels every time I try them.
>
> ...
>
> > $ sudo lspci
> > 00:00.0 PCI bridge: Intel Corporation Device 4c53 (rev 01)
> > 00:02.0 VGA compatible controller: Intel Corporation RocketLake-S GT1 [UHD
Graphics 730] (rev 04)
> > 00:04.0 Signal processing controller: Intel Corporation Device 4c03 (rev 01)
> > 00:08.0 System peripheral: Intel Corporation Device 4c11 (rev 01)
> > 00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal
Controller
> > 00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host
Controller
> > 00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM
> > 00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi
> > 00:15.0 Serial bus controller: Intel Corporation Comet Lake PCH Serial IO I2C
Controller #0
> > 00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller
> > 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller
> > 00:1b.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #21 (rev
f0)
> > 00:1c.0 PCI bridge: Intel Corporation Device 06bc (rev f0)
> > 00:1f.0 ISA bridge: Intel Corporation H470 Chipset LPC/eSPI Controller
> > 00:1f.3 Audio device: Intel Corporation Device f1c8
> > 00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller
> > 00:1f.5 Serial bus controller: Intel Corporation Comet Lake PCH SPI Controller
> > 02:00.0 Non-Volatile memory controller: KIOXIA Corporation NVMe SSD Controller
BG4 (DRAM-less)
> > 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 2600 (rev
21)
> > olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ sudo lsusb
> > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
> > Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card
Reader Controller
> > Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth
> > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>
> ...
>
> > When booting the kernels I tried to see where they were stopping, the boot
showed loading the usb mouse/keyboard combination, but showed disabled. I tried booting
with regular usb mouse and keyboard and the same thing happens, the kernel does not boot.
Secure boot is on. Do not know what to do to get the newer kernels to boot. I dont create
a bugzilla because I no longer use the email that was associated with bugzilla. The newer
kernels do work on raspberry pi though, so it may be related to the hardware? with secure
boot and signed kernels, I cannot seem to find what is going on.
>
> > Is there a BIOS setting I can try? RAID ON/RAID OFF, running on nvme0 internel
disk. Was running on a solid state disk(SSD) before.
>
> I have same GPU as you, maybe same CPU, running F39 on NVME, though not with
> secure boot. I have no such trouble as yet with any kernel since 6.5:
> # inxi -C --vs --zl --hostname
> inxi 3.3.33-00 (2024-02-06)
> CPU:
> Info: 6-core model: 11th Gen Intel Core i5-11400 bits: 64 type: MT MCP
> cache: L2: 3 MiB
> Speed (MHz): avg: 809 min/max: 800/4400 cores: 1: 800 2: 800 3: 800 4: 800
> 5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 910 12: 801
> # inxi -GSaz
> System:
> Kernel: 6.6.13-200.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
> v: 2.40-13.fc39 clocksource: tsc avail: hpet,acpi_pm
> parameters: BOOT_IMAGE=/boot/vmlinuz root=LABEL=tm8p15f39 noresume
> audit=0 ipv6.disable=1 net.ifnames=0 consoleblank=0 preempt=full
> mitigations=off
> Desktop: TDE (Trinity) v: R14.1.1 tk: Qt v: 3.5.0 wm: Twin v: 3.0
> with: kicker vt: 7 dm: 1: TDM 2: XDM Distro: Fedora Linux 39 (Thirty Nine)
> Graphics:
> Device-1: Intel RocketLake-S GT1 [UHD Graphics 730] vendor: ASUSTeK
> driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21
> ports: active: DP-1,HDMI-A-1,HDMI-A-2 empty: HDMI-A-3 bus-ID: 00:02.0
> chip-ID: 8086:4c8b class-ID: 0300
> Display: x11 server: X.Org v: 1.20.14 compositor: Twin v: 3.0 driver: X:
> loaded: modesetting dri: iris gpu: i915 display-ID: :0 screens: 1
> Screen-1: 0 s-res: 3600x2640 s-dpi: 120 s-size: 762x558mm (30.00x21.97")
> s-diag: 944mm (37.18")
> Monitor-1: DP-1 pos: primary,bottom-l model: Acer K272HUL serial: <filter>
>
> built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2
> size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
> max: 2560x1440 min: 720x400
> Monitor-2: HDMI-A-1 mapped: HDMI-1 pos: top-left model: NEC EA243WM
> serial: <filter> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
>
> size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
> max: 1920x1200 min: 640x480
> Monitor-3: HDMI-A-2 mapped: HDMI-2 pos: top-right model: Dell P2213
> serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
>
> size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes:
> max: 1680x1050 min: 720x400
> API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
> device: 1 drv: swrast surfaceless: drv: iris x11: drv: iris
> inactive: gbm,wayland
> API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 23.3.3 glx-v: 1.4
> direct-render: yes renderer: Mesa Intel Graphics (RKL GT1)
> device-ID: 8086:4c8b memory: 29.48 GiB unified: yes
> #
>
> What does your kernel cmdline contain?
olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ inxi -C --vs --zl
--hostname
bash: inxi: command not found...
Install package 'inxi' to provide command 'inxi'? [N/y] y
* Waiting in queue...
* Loading list of packages....
The following packages have to be installed:
freeipmi-1.6.11-1.fc39.x86_64 IPMI remote console and system management software
hddtemp-0.3-0.54.beta15.fc39.x86_64 Hard disk temperature tool
inxi-3.3.31-1.fc39.noarch A full featured system information script
ipmitool-1.8.19-4.fc39.x86_64 Utility for IPMI control
lm_sensors-3.6.0-14.fc39.x86_64 Hardware monitoring tools
perl-Cpanel-JSON-XS-4.37-4.fc39.x86_64 JSON::XS for Cpanel, fast and correct serializing
perl-JSON-XS-1:4.03-11.fc39.x86_64 JSON serializing/de-serializing, done correctly and
fast
perl-Types-Serialiser-1.01-9.fc39.noarch Simple data types for common serialization
formats
perl-XML-Dumper-0.81-47.fc39.noarch Perl module for dumping Perl objects from/to XML
perl-XML-Parser-2.46-15.fc39.x86_64 Perl module for parsing XML documents
perl-common-sense-3.7.5-14.fc39.x86_64 "Common sense" Perl defaults
wmctrl-1.07-35.fc39.x86_64 Command line tool to interact with an X Window Manager
Proceed with changes? [N/y] y
* Waiting in queue...
* Waiting for authentication...
* Waiting in queue...
* Downloading packages... Failed to install packages: Cannot download
Packages/i/inxi-3.3.31-1.fc39.noarch.rpm: All mirrors were tried; Last error: Status code:
404 for
https://mirror.umd.edu/fedora/linux/updates/39/Everything/x86_64/Packages...
(IP: 128.8.207.141)
olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ grubby --info=DEFAULT
grep: /boot/grub2/grubenv: Permission denied
olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ sudo grubby --info=DEFAULT
[sudo] password for olivares:
index=0
kernel="/boot/vmlinuz-6.7.4-200.fc39.x86_64"
args="ro rootflags=subvol=root rhgb quiet"
root="UUID=8ff57a6b-2a55-4e9d-870d-855d68d35bee"
initrd="/boot/initramfs-6.7.4-200.fc39.x86_64.img"
title="Fedora Linux (6.7.4-200.fc39.x86_64) 39 (Workstation Edition)"
id="146af94111b0438ea94534f851a76045-6.7.4-200.fc39.x86_64"
olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$
What exactly does "do not boot" mean? GUI
> login greeter is not reached? No login prompt available on any of the vttys?
booting just hangs do not reach GUI
Does
> appending nomodeset to the linu line after striking the E key at the boot menu
> enable "boot" to complete?
will try nomodeset to line and report back.
> --
> Evolution as taught in public schools is, like religion,
> based on faith, not based on science.
>
> Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
>
> Felix Miata
> --
Best Regards,
Antonio
--
Finally I have successfully booted a kernel > 6.5.12-300.fc39.x86_64 on Fedora. Thanks
to all who have helped and provided things to try. I added nomodeset to line, I guess I
will have to add it to grub and make it permanent so I do not have problems.
olivares@fedora:~$ uname -a
Linux fedora 6.7.4-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Feb 5 22:21:14 UTC 2024
x86_64 GNU/Linux
olivares@fedora:~$
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
12:04 p.m.
olivares33561 via users composed on 2024-02-13 12:21 (UTC-0500):
Finally I have successfully booted a kernel >
6.5.12-300.fc39.x86_64 on Fedora. Thanks to all who have helped and provided things to
try. I added nomodeset to line, I guess I will have to add it to grub and make it
permanent so I do not have problems.
olivares@fedora:~$ uname -a
Linux fedora 6.7.4-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Feb 5 22:21:14 UTC 2024
x86_64 GNU/Linux
olivares@fedora:~$
Nomodeset is never a proper *solution*. It's designed as a troubleshooting
parameter and workaround to allow graphical mode system administration and log
access. It kills performance. It disables displays other than the first. It
usually reduces the screen resolution to something less than the display's ideal
native mode.
<https://web.archive.org/web/20230203110609/https://en.opensuse.org/SDB:No...
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
12:18 p.m.
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
On Tuesday, February 13th, 2024 at 12:04 PM, Felix Miata <mrmazda(a)earthlink.net>
wrote:
olivares33561 via users composed on 2024-02-13 12:21 (UTC-0500):
> Finally I have successfully booted a kernel > 6.5.12-300.fc39.x86_64 on Fedora.
Thanks to all who have helped and provided things to try. I added nomodeset to line, I
guess I will have to add it to grub and make it permanent so I do not have problems.
> olivares@fedora:~$ uname -a
> Linux fedora 6.7.4-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Feb 5 22:21:14 UTC
2024 x86_64 GNU/Linux
> olivares@fedora:~$
Nomodeset is never a proper solution. It's designed as a troubleshooting
parameter and workaround to allow graphical mode system administration and log
access. It kills performance. It disables displays other than the first. It
usually reduces the screen resolution to something less than the display's ideal
native mode.
https://web.archive.org/web/20230203110609/https://en.opensuse.org/SDB:No...
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
--
Dear Sir,
If I remove nomodeset from the grub cmdline, the boot hangs and does not proceed. If I
keep it, there is no sound. I have encountered problems before on other machine(s) where
sound does not work on one kernel, but an update makes it work again(using hdmi). But
here I am inexperienced with nomodeset parameter. I am happy that I can boot the new
kernel, but the sound is not there, maybe a newer kernel can make it work, but I am unsure
of what to expect. It is strange that these things happened, because before for two or
three years it worked flawlessly.
Best Regards,
Antonio
1:29 p.m.
olivares33561 composed on 2024-02-13 18:18 (UTC):
Felix Miata wrote:
> olivares33561 composed on 2024-02-13 12:21 (UTC-0500):
> > Finally I have successfully booted a kernel >
6.5.12-300.fc39.x86_64 on Fedora. Thanks to all who have helped and provided things to
try. I added nomodeset to line, I guess I will have to add it to grub and make it
permanent so I do not have problems.
> > olivares@fedora:~$ uname -a
> > Linux fedora 6.7.4-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Feb 5 22:21:14 UTC
2024 x86_64 GNU/Linux
> > olivares@fedora:~$
> Nomodeset is never a proper solution. It's designed as a
troubleshooting
> parameter and workaround to allow graphical mode system administration and log
> access. It kills performance. It disables displays other than the first. It
> usually reduces the screen resolution to something less than the display's ideal
> native mode.
>
>
https://web.archive.org/web/20230203110609/https://en.opensuse.org/SDB:No...
If I remove nomodeset from the grub cmdline, the boot hangs and does
not proceed. If I keep it, there is no sound. I have encountered problems before on
other machine(s) where sound does not work on one kernel, but an update makes it work
again(using hdmi). But here I am inexperienced with nomodeset parameter. I am happy that
I can boot the new kernel, but the sound is not there, maybe a newer kernel can make it
work, but I am unsure of what to expect. It is strange that these things happened,
because before for two or three years it worked flawlessly.
I suggest you report a bug that 6.6 and 6.7 kernels are not bootable without using
nomodeset, while 6.5 kernels work as expected without nomodeset.
https://docs.fedoraproject.org/en-US/quick-docs/bugzilla-file-a-bug/
You may try again to install inxi. If it fails again you may install directly from
upstream: https://smxi.org/docs/inxi-installation.htm#inxi-manual-install
Inxi is merely a perl script that collects and formats data that facilitates
troubleshooting and solving bugs.
Once your kernel problem is solved, your sound problem may solve itself, as your
issue is apparently graphics-related, to which HDMI sound is coupled.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
10:42 a.m.
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
On Tuesday, February 13th, 2024 at 1:29 PM, Felix Miata <mrmazda(a)earthlink.net>
wrote:
olivares33561 composed on 2024-02-13 18:18 (UTC):
> Felix Miata wrote:
> > olivares33561 composed on 2024-02-13 12:21 (UTC-0500):
> > > Finally I have successfully booted a kernel > 6.5.12-300.fc39.x86_64 on
Fedora. Thanks to all who have helped and provided things to try. I added nomodeset to
line, I guess I will have to add it to grub and make it permanent so I do not have
problems.
> > > olivares@fedora:~$ uname -a
> > > Linux fedora 6.7.4-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Feb 5
22:21:14 UTC 2024 x86_64 GNU/Linux
> > > olivares@fedora:~$
> > Nomodeset is never a proper solution. It's designed as a troubleshooting
> > parameter and workaround to allow graphical mode system administration and log
> > access. It kills performance. It disables displays other than the first. It
> > usually reduces the screen resolution to something less than the display's
ideal
> > native mode.
> >
> >
https://web.archive.org/web/20230203110609/https://en.opensuse.org/SDB:No...
> If I remove nomodeset from the grub cmdline, the boot hangs and does not proceed. If
I keep it, there is no sound. I have encountered problems before on other machine(s) where
sound does not work on one kernel, but an update makes it work again(using hdmi). But here
I am inexperienced with nomodeset parameter. I am happy that I can boot the new kernel,
but the sound is not there, maybe a newer kernel can make it work, but I am unsure of what
to expect. It is strange that these things happened, because before for two or three years
it worked flawlessly.
I suggest you report a bug that 6.6 and 6.7 kernels are not bootable without using
nomodeset, while 6.5 kernels work as expected without nomodeset.
https://docs.fedoraproject.org/en-US/quick-docs/bugzilla-file-a-bug/
You may try again to install inxi. If it fails again you may install directly from
upstream: https://smxi.org/docs/inxi-installation.htm#inxi-manual-install
Inxi is merely a perl script that collects and formats data that facilitates
troubleshooting and solving bugs.
Once your kernel problem is solved, your sound problem may solve itself, as your
issue is apparently graphics-related, to which HDMI sound is coupled.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
--
Bug Submitted:
https://bugzilla.redhat.com/show_bug.cgi?id=2264223
Output of inxi command
olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ inxi -C --vs --zl
--hostname
inxi 3.3.32-00 (2024-01-30)
CPU:
Info: 6-core model: 11th Gen Intel Core i5-11400 bits: 64 type: MT MCP
cache: L2: 3 MiB
Speed (MHz): avg: 799 min/max: 800/4400 cores: 1: 800 2: 800 3: 800 4: 800
5: 800 6: 800 7: 800 8: 800 9: 800 10: 799 11: 800 12: 800
Hope bug is not trashed or marked not a bug. I would not have tried nomodeset if it was
not suggested. Upon successful booting without using nomodeset maybe sound comes back.
Best Regards,
Antonio
Best Regards,
Antonio
8:33 a.m.
On Wed, Feb 14, 2024 at 12:42 PM olivares33561 via users <
users(a)lists.fedoraproject.org> wrote:
[...]
Bug Submitted:
https://bugzilla.redhat.com/show_bug.cgi?id=2264223
Output of inxi command
olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ inxi -C
--vs --zl --hostname
inxi 3.3.32-00 (2024-01-30)
CPU:
Info: 6-core model: 11th Gen Intel Core i5-11400 bits: 64 type: MT MCP
cache: L2: 3 MiB
Speed (MHz): avg: 799 min/max: 800/4400 cores: 1: 800 2: 800 3: 800 4:
800
5: 800 6: 800 7: 800 8: 800 9: 800 10: 799 11: 800 12: 800
Hope bug is not trashed or marked not a bug. I would not have tried
nomodeset if it was not suggested.
Upon successful booting without using nomodeset maybe sound comes back.
From the journalctl output, you have
Feb 15 10:12:18 fedora kernel: Hardware name: Dell Inc. XPS
8940/0K3CM7, BIOS 2.4.0 12/08/2021
You appear to be missing multiple "critical" updates:
https://www.dell.com/support/home/en-us/product-support/product/xps-8940-...
You should be able to install the updates by booting with nomodeset
and using fwupdtool (see fwupdtool --help).
11:07 a.m.
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
On Friday, February 16th, 2024 at 8:33 AM, George N. White III <gnwiii(a)gmail.com>
wrote:
On Wed, Feb 14, 2024 at 12:42 PM olivares33561 via users
<users(a)lists.fedoraproject.org> wrote:
>
> [...]
>
> Bug Submitted:
> https://bugzilla.redhat.com/show_bug.cgi?id=2264223
>
> Output of inxi command
> olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ inxi -C --vs --zl
--hostname
> inxi 3.3.32-00 (2024-01-30)
> CPU:
> Info: 6-core model: 11th Gen Intel Core i5-11400 bits: 64 type: MT MCP
> cache: L2: 3 MiB
> Speed (MHz): avg: 799 min/max: 800/4400 cores: 1: 800 2: 800 3: 800 4: 800
> 5: 800 6: 800 7: 800 8: 800 9: 800 10: 799 11: 800 12: 800
>
> Hope bug is not trashed or marked not a bug. I would not have tried nomodeset if it
was not suggested.
> Upon successful booting without using nomodeset maybe sound comes back.
From the journalctl output, you have
Feb 15 10:12:18 fedora kernel: Hardware name: Dell Inc. XPS 8940/0K3CM7, BIOS 2.4.0
12/08/2021
You appear to be missing multiple "critical" updates:
https://www.dell.com/support/home/en-us/product-support/product/xps-8940-...
You should be able to install the updates by booting with nomodeset and using fwupdtool
(see fwupdtool --help).
Updated BIOS, still same situation.
System still hangs.
Best Regards,
Antonio
11:23 a.m.
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
On Friday, February 16th, 2024 at 11:07 AM, olivares33561 via users
<users(a)lists.fedoraproject.org> wrote:
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
On Friday, February 16th, 2024 at 8:33 AM, George N. White III gnwiii(a)gmail.com wrote:
> On Wed, Feb 14, 2024 at 12:42 PM olivares33561 via users
users(a)lists.fedoraproject.org wrote:
>
> > [...]
> >
> > Bug Submitted:
> > https://bugzilla.redhat.com/show_bug.cgi?id=2264223
> >
> > Output of inxi command
> > olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ inxi -C --vs --zl
--hostname
> > inxi 3.3.32-00 (2024-01-30)
> > CPU:
> > Info: 6-core model: 11th Gen Intel Core i5-11400 bits: 64 type: MT MCP
> > cache: L2: 3 MiB
> > Speed (MHz): avg: 799 min/max: 800/4400 cores: 1: 800 2: 800 3: 800 4: 800
> > 5: 800 6: 800 7: 800 8: 800 9: 800 10: 799 11: 800 12: 800
> >
> > Hope bug is not trashed or marked not a bug. I would not have tried nomodeset
if it was not suggested.
>
> > Upon successful booting without using nomodeset maybe sound comes back.
>
> From the journalctl output, you have
>
> Feb 15 10:12:18 fedora kernel: Hardware name: Dell Inc. XPS 8940/0K3CM7, BIOS 2.4.0
12/08/2021
>
> You appear to be missing multiple "critical" updates:
>
>
https://www.dell.com/support/home/en-us/product-support/product/xps-8940-...
>
> You should be able to install the updates by booting with nomodeset and using
fwupdtool (see fwupdtool --help).
Updated BIOS, still same situation.
System still hangs.
Best Regards,
Antonio
--
After updating BIOS to version 2.16 latest, the system still hangs.
....
Feb 16 11:09:28 fedora kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
Feb 16 11:09:28 fedora kernel: CPU: 4 PID: 498 Comm: (udev-worker) Not tainted
6.7.4-200.fc39.x86_64 #1
Feb 16 11:09:28 fedora kernel: Hardware name: Dell Inc. XPS 8940/0K3CM7, BIOS 2.16.0
11/02/2023
Feb 16 11:09:28 fedora kernel: RIP: 0010:icl_aux_pw_to_phy.isra.0+0x35/0x40 [i915]
Feb 16 11:09:28 fedora kernel: Code: 76 08 0f b6 d2 48 8d 04 52 f6 41 11 01 48 89 fb 48 8b
16 48 8d 04 c2 0f b6 70 14 8d 46 fa 0f 45 f0 e8 7f ed ff ff 48 89 df 5b <8b> 70 7c
e9 d3 93 fe ff 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90
Feb 16 11:09:28 fedora kernel: RSP: 0018:ffffadc50198fa30 EFLAGS: 00010246
Feb 16 11:09:28 fedora kernel: RAX: 0000000000000000 RBX: ffff9133cdf6c000 RCX:
ffffffffc080de98
Feb 16 11:09:28 fedora kernel: RDX: 0000000000000000 RSI: 0000000000000003 RDI:
ffff9133cdf6c000
Feb 16 11:09:28 fedora kernel: RBP: ffff9133c1deb560 R08: ffffffffc087cfb1 R09:
0000000000000000
Feb 16 11:09:28 fedora kernel: R10: 0000000000000001 R11: 0000000000000100 R12:
ffff9133cdf6cb08
Feb 16 11:09:28 fedora kernel: R13: 0000000000000001 R14: ffff9133c26080c0 R15:
ffff9133c2608000
Feb 16 11:09:28 fedora kernel: FS: 00007f8a9a813980(0000) GS:ffff913519900000(0000)
knlGS:0000000000000000
Feb 16 11:09:28 fedora kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 16 11:09:28 fedora kernel: CR2: 000000000000007c CR3: 000000010df38004 CR4:
0000000000770ef0
Feb 16 11:09:28 fedora kernel: PKRU: 55555554
Feb 16 11:09:28 fedora kernel: Call Trace:
Feb 16 11:09:28 fedora kernel: <TASK>
Feb 16 11:09:28 fedora kernel: ? __die+0x23/0x70
Feb 16 11:09:28 fedora kernel: ? page_fault_oops+0x171/0x4e0
Feb 16 11:09:28 fedora kernel: ? __intel_display_power_get_domain.part.0+0x52/0x70
[i915]
Feb 16 11:09:28 fedora kernel: ? ktime_get+0x3c/0xa0
Feb 16 11:09:28 fedora kernel: ? exc_page_fault+0x7f/0x180
Feb 16 11:09:28 fedora kernel: ? asm_exc_page_fault+0x26/0x30
Feb 16 11:09:28 fedora kernel: ? icl_aux_pw_to_phy.isra.0+0x35/0x40 [i915]
Feb 16 11:09:28 fedora kernel: icl_aux_power_well_disable+0x39/0x1d0 [i915]
Feb 16 11:09:28 fedora kernel: intel_power_domains_sanitize_state+0x91/0xb0 [i915]
Feb 16 11:09:28 fedora kernel: intel_display_driver_probe_nogem+0x163/0x210 [i915]
Feb 16 11:09:28 fedora kernel: i915_driver_probe+0x707/0xbe0 [i915]
Feb 16 11:09:28 fedora kernel: local_pci_probe+0x42/0xa0
Feb 16 11:09:28 fedora kernel: pci_device_probe+0xc7/0x240
Feb 16 11:09:28 fedora kernel: really_probe+0x19b/0x3e0
Feb 16 11:09:28 fedora kernel: ? __pfx___driver_attach+0x10/0x10
Feb 16 11:09:28 fedora kernel: __driver_probe_device+0x78/0x160
Feb 16 11:09:28 fedora kernel: driver_probe_device+0x1f/0x90
Feb 16 11:09:28 fedora kernel: __driver_attach+0xd2/0x1c0
Feb 16 11:09:28 fedora kernel: bus_for_each_dev+0x85/0xd0
Feb 16 11:09:28 fedora kernel: bus_add_driver+0x116/0x220
Feb 16 11:09:28 fedora kernel: driver_register+0x59/0x100
Feb 16 11:09:28 fedora kernel: i915_init+0x22/0xc0 [i915]
Feb 16 11:09:28 fedora kernel: ? __pfx_i915_init+0x10/0x10 [i915]
Feb 16 11:09:28 fedora kernel: do_one_initcall+0x58/0x320
Feb 16 11:09:28 fedora kernel: do_init_module+0x60/0x240
Feb 16 11:09:28 fedora kernel: __do_sys_init_module+0x17f/0x1b0
Feb 16 11:09:28 fedora kernel: ? __seccomp_filter+0x32c/0x4f0
Feb 16 11:09:28 fedora kernel: do_syscall_64+0x61/0xe0
Feb 16 11:09:28 fedora kernel: ? syscall_exit_to_user_mode+0x2b/0x40
Feb 16 11:09:28 fedora kernel: ? do_syscall_64+0x70/0xe0
Feb 16 11:09:28 fedora kernel: ? __count_memcg_events+0x42/0x90
Feb 16 11:09:28 fedora kernel: ? count_memcg_events.constprop.0+0x1a/0x30
Feb 16 11:09:28 fedora kernel: ? handle_mm_fault+0xa2/0x360
Feb 16 11:09:28 fedora kernel: ? do_user_addr_fault+0x304/0x670
Feb 16 11:09:28 fedora kernel: ? exc_page_fault+0x7f/0x180
Feb 16 11:09:28 fedora kernel: entry_SYSCALL_64_after_hwframe+0x6e/0x76
Feb 16 11:09:28 fedora kernel: RIP: 0033:0x7f8a9b1fe94e
Feb 16 11:09:28 fedora kernel: Code: 48 8b 0d e5 14 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66
2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d b2 14 0c 00 f7 d8 64 89 01 48
.....
updating attachment
https://bugzilla.redhat.com/show_bug.cgi?id=2264223
Best Regards,
Antonio
6:34 p.m.
On 2/16/24 09:23, olivares33561 via users wrote:
Feb 16 11:09:28 fedora kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
Feb 16 11:09:28 fedora kernel: CPU: 4 PID: 498 Comm: (udev-worker) Not tainted
6.7.4-200.fc39.x86_64 #1
Feb 16 11:09:28 fedora kernel: Hardware name: Dell Inc. XPS 8940/0K3CM7, BIOS 2.16.0
11/02/2023
Feb 16 11:09:28 fedora kernel: RIP: 0010:icl_aux_pw_to_phy.isra.0+0x35/0x40 [i915]
Feb 16 11:09:28 fedora kernel: Code: 76 08 0f b6 d2 48 8d 04 52 f6 41 11 01 48 89 fb 48
8b 16 48 8d 04 c2 0f b6 70 14 8d 46 fa 0f 45 f0 e8 7f ed ff ff 48 89 df 5b <8b> 70
7c e9 d3 93 fe ff 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90
Feb 16 11:09:28 fedora kernel: RSP: 0018:ffffadc50198fa30 EFLAGS: 00010246
Feb 16 11:09:28 fedora kernel: RAX: 0000000000000000 RBX: ffff9133cdf6c000 RCX:
ffffffffc080de98
Feb 16 11:09:28 fedora kernel: RDX: 0000000000000000 RSI: 0000000000000003 RDI:
ffff9133cdf6c000
Feb 16 11:09:28 fedora kernel: RBP: ffff9133c1deb560 R08: ffffffffc087cfb1 R09:
0000000000000000
Feb 16 11:09:28 fedora kernel: R10: 0000000000000001 R11: 0000000000000100 R12:
ffff9133cdf6cb08
Feb 16 11:09:28 fedora kernel: R13: 0000000000000001 R14: ffff9133c26080c0 R15:
ffff9133c2608000
Feb 16 11:09:28 fedora kernel: FS: 00007f8a9a813980(0000) GS:ffff913519900000(0000)
knlGS:0000000000000000
Feb 16 11:09:28 fedora kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 16 11:09:28 fedora kernel: CR2: 000000000000007c CR3: 000000010df38004 CR4:
0000000000770ef0
Feb 16 11:09:28 fedora kernel: PKRU: 55555554
Feb 16 11:09:28 fedora kernel: Call Trace:
Feb 16 11:09:28 fedora kernel: <TASK>
Feb 16 11:09:28 fedora kernel: ? __die+0x23/0x70
Feb 16 11:09:28 fedora kernel: ? page_fault_oops+0x171/0x4e0
Feb 16 11:09:28 fedora kernel: ? __intel_display_power_get_domain.part.0+0x52/0x70
[i915]
Feb 16 11:09:28 fedora kernel: ? ktime_get+0x3c/0xa0
Feb 16 11:09:28 fedora kernel: ? exc_page_fault+0x7f/0x180
Feb 16 11:09:28 fedora kernel: ? asm_exc_page_fault+0x26/0x30
Feb 16 11:09:28 fedora kernel: ? icl_aux_pw_to_phy.isra.0+0x35/0x40 [i915]
Feb 16 11:09:28 fedora kernel: icl_aux_power_well_disable+0x39/0x1d0 [i915]
Feb 16 11:09:28 fedora kernel: intel_power_domains_sanitize_state+0x91/0xb0 [i915]
Feb 16 11:09:28 fedora kernel: intel_display_driver_probe_nogem+0x163/0x210 [i915]
Feb 16 11:09:28 fedora kernel: i915_driver_probe+0x707/0xbe0 [i915]
An oops with a page fault in the i915 display driver relating to power
management. Somehow triggered by udev.
No idea what would cause that, but it explains why nomodeset works.
11:36 p.m.
Samuel Sieb composed on 2024-02-16 16:34 (UTC-0800):
On 2/16/24 09:23, olivares33561 via users wrote:
...
> Feb 16 11:09:28 fedora kernel: ?
__intel_display_power_get_domain.part.0+0x52/0x70 [i915]
> Feb 16 11:09:28 fedora kernel: ? ktime_get+0x3c/0xa0
> Feb 16 11:09:28 fedora kernel: ? exc_page_fault+0x7f/0x180
> Feb 16 11:09:28 fedora kernel: ? asm_exc_page_fault+0x26/0x30
> Feb 16 11:09:28 fedora kernel: ? icl_aux_pw_to_phy.isra.0+0x35/0x40 [i915]
> Feb 16 11:09:28 fedora kernel: icl_aux_power_well_disable+0x39/0x1d0 [i915]
> Feb 16 11:09:28 fedora kernel: intel_power_domains_sanitize_state+0x91/0xb0 [i915]
> Feb 16 11:09:28 fedora kernel: intel_display_driver_probe_nogem+0x163/0x210 [i915]
> Feb 16 11:09:28 fedora kernel: i915_driver_probe+0x707/0xbe0 [i915]
An oops with a page fault in the i915 display driver relating to
power
management. Somehow triggered by udev.
No idea what would cause that, but it explains why nomodeset works.
So perhaps intel_pstate= kernel cmdline appendages are worth trying?:
https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt 31%
down from top of file. I'd go first for hwp_only, next no_hwp, then ???
https://www.kernel.org/doc/html/v4.19/admin-guide/pm/intel_pstate.html
Has a BIOS upgrade already been checked for?
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
11:55 a.m.
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
On Friday, February 16th, 2024 at 11:36 PM, Felix Miata <mrmazda(a)earthlink.net>
wrote:
Samuel Sieb composed on 2024-02-16 16:34 (UTC-0800):
> On 2/16/24 09:23, olivares33561 via users wrote:
...
> > Feb 16 11:09:28 fedora kernel: ?
__intel_display_power_get_domain.part.0+0x52/0x70 [i915]
> > Feb 16 11:09:28 fedora kernel: ? ktime_get+0x3c/0xa0
> > Feb 16 11:09:28 fedora kernel: ? exc_page_fault+0x7f/0x180
> > Feb 16 11:09:28 fedora kernel: ? asm_exc_page_fault+0x26/0x30
> > Feb 16 11:09:28 fedora kernel: ? icl_aux_pw_to_phy.isra.0+0x35/0x40 [i915]
> > Feb 16 11:09:28 fedora kernel: icl_aux_power_well_disable+0x39/0x1d0 [i915]
> > Feb 16 11:09:28 fedora kernel: intel_power_domains_sanitize_state+0x91/0xb0
[i915]
> > Feb 16 11:09:28 fedora kernel: intel_display_driver_probe_nogem+0x163/0x210
[i915]
> > Feb 16 11:09:28 fedora kernel: i915_driver_probe+0x707/0xbe0 [i915]
> An oops with a page fault in the i915 display driver relating to power
> management. Somehow triggered by udev.
> No idea what would cause that, but it explains why nomodeset works.
So perhaps intel_pstate= kernel cmdline appendages are worth trying?:
https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt 31%
down from top of file. I'd go first for hwp_only, next no_hwp, then ???
https://www.kernel.org/doc/html/v4.19/admin-guide/pm/intel_pstate.html
Has a BIOS upgrade already been checked for?
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
--
Dear Sir,
Tried out
intel_pstate=hwp_only
and
intel_pstate=no_hwp
and none of these worked. Still same situation. Bios has been updated and I have to use
nomodeset as kernel parameter to successfully boot. Maybe another kernel 6.7.5 coming
soon will fix the situation?
was not able to capture kernel output of journalctl :(
Best Regards,
Antonio
8:09 a.m.
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
On Wednesday, February 21st, 2024 at 11:55 AM, olivares33561 via users
<users(a)lists.fedoraproject.org> wrote:
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
On Friday, February 16th, 2024 at 11:36 PM, Felix Miata mrmazda(a)earthlink.net wrote:
> Samuel Sieb composed on 2024-02-16 16:34 (UTC-0800):
>
> > On 2/16/24 09:23, olivares33561 via users wrote:
>
> ...
>
> > > Feb 16 11:09:28 fedora kernel: ?
__intel_display_power_get_domain.part.0+0x52/0x70 [i915]
> > > Feb 16 11:09:28 fedora kernel: ? ktime_get+0x3c/0xa0
> > > Feb 16 11:09:28 fedora kernel: ? exc_page_fault+0x7f/0x180
> > > Feb 16 11:09:28 fedora kernel: ? asm_exc_page_fault+0x26/0x30
> > > Feb 16 11:09:28 fedora kernel: ? icl_aux_pw_to_phy.isra.0+0x35/0x40
[i915]
> > > Feb 16 11:09:28 fedora kernel: icl_aux_power_well_disable+0x39/0x1d0
[i915]
> > > Feb 16 11:09:28 fedora kernel:
intel_power_domains_sanitize_state+0x91/0xb0 [i915]
> > > Feb 16 11:09:28 fedora kernel:
intel_display_driver_probe_nogem+0x163/0x210 [i915]
> > > Feb 16 11:09:28 fedora kernel: i915_driver_probe+0x707/0xbe0 [i915]
>
> > An oops with a page fault in the i915 display driver relating to power
> > management. Somehow triggered by udev.
>
> > No idea what would cause that, but it explains why nomodeset works.
>
> So perhaps intel_pstate= kernel cmdline appendages are worth trying?:
>
> https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt 31%
> down from top of file. I'd go first for hwp_only, next no_hwp, then ???
>
> https://www.kernel.org/doc/html/v4.19/admin-guide/pm/intel_pstate.html
>
> Has a BIOS upgrade already been checked for?
> --
> Evolution as taught in public schools is, like religion,
> based on faith, not based on science.
>
> Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
>
> Felix Miata
> --
Dear Sir,
Tried out
intel_pstate=hwp_only
and
intel_pstate=no_hwp
and none of these worked. Still same situation. Bios has been updated and I have to use
nomodeset as kernel parameter to successfully boot. Maybe another kernel 6.7.5 coming soon
will fix the situation?
was not able to capture kernel output of journalctl :(
Best Regards,
Antonio
--
Dear all,
booted new kernel 6.7.5* and it also oops. Have to use nomodeset in order to boot it.
Feb 22 07:54:11 fedora kernel: Hardware name: Dell Inc. XPS 8940/0K3CM7, BIOS 2.16.0
11/02/2023
Feb 22 07:54:11 fedora kernel: RIP: 0010:icl_aux_pw_to_phy.isra.0+0x35/0x40 [i915]
Feb 22 07:54:11 fedora kernel: Code: 76 08 0f b6 d2 48 8d 04 52 f6 41 11 01 48 89 fb 48 8b
16 48 8d 04 c2 0f b6 70 14 8d 46 fa 0f 45 f0 e8 7f ed ff ff 48 89 df 5b <8b> 70 7c
e9 d3 93 fe ff 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90
Feb 22 07:54:11 fedora kernel: RSP: 0018:ffffbae0418c3a78 EFLAGS: 00010246
Feb 22 07:54:11 fedora kernel: RAX: 0000000000000000 RBX: ffff9ae54b8d8000 RCX:
ffffffffc0b96e98
Feb 22 07:54:11 fedora kernel: RDX: 0000000000000000 RSI: 0000000000000003 RDI:
ffff9ae54b8d8000
Feb 22 07:54:11 fedora kernel: RBP: ffff9ae549b14360 R08: ffffffffc0c05fb1 R09:
0000000000000000
Feb 22 07:54:11 fedora kernel: R10: 0000000000000001 R11: 0000000000000100 R12:
ffff9ae54b8d8b08
Feb 22 07:54:11 fedora kernel: R13: 0000000000000001 R14: ffff9ae5423630c0 R15:
ffff9ae542363000
Feb 22 07:54:11 fedora kernel: FS: 00007f99ff652980(0000) GS:ffff9ae6998c0000(0000)
knlGS:0000000000000000
Feb 22 07:54:11 fedora kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 22 07:54:11 fedora kernel: CR2: 000000000000007c CR3: 000000010baa4004 CR4:
0000000000770ef0
Feb 22 07:54:11 fedora kernel: PKRU: 55555554
Feb 22 07:54:11 fedora kernel: Call Trace:
Feb 22 07:54:11 fedora kernel: <TASK>
Feb 22 07:54:11 fedora kernel: ? __die+0x23/0x70
Feb 22 07:54:11 fedora kernel: ? page_fault_oops+0x171/0x4e0
Feb 22 07:54:11 fedora kernel: ? exc_page_fault+0x7f/0x180
Feb 22 07:54:11 fedora kernel: ? asm_exc_page_fault+0x26/0x30
Feb 22 07:54:11 fedora kernel: ? icl_aux_pw_to_phy.isra.0+0x35/0x40 [i915]
Feb 22 07:54:11 fedora kernel: icl_aux_power_well_disable+0x39/0x1d0 [i915]
Feb 22 07:54:11 fedora kernel: intel_power_domains_sanitize_state+0x91/0xb0 [i915]
Feb 22 07:54:11 fedora kernel: intel_display_driver_probe_nogem+0x163/0x210 [i915]
Feb 22 07:54:11 fedora kernel: i915_driver_probe+0x707/0xbe0 [i915]
Feb 22 07:54:11 fedora kernel: local_pci_probe+0x42/0xa0
Feb 22 07:54:11 fedora kernel: pci_device_probe+0xc7/0x240
Feb 22 07:54:11 fedora kernel: really_probe+0x19b/0x3e0
Feb 22 07:54:11 fedora kernel: ? __pfx___driver_attach+0x10/0x10
Feb 22 07:54:11 fedora kernel: __driver_probe_device+0x78/0x160
Feb 22 07:54:11 fedora kernel: driver_probe_device+0x1f/0x90
Feb 22 07:54:11 fedora kernel: __driver_attach+0xd2/0x1c0
Feb 22 07:54:11 fedora kernel: bus_for_each_dev+0x85/0xd0
Feb 22 07:54:11 fedora kernel: bus_add_driver+0x116/0x220
Feb 22 07:54:11 fedora kernel: driver_register+0x59/0x100
Feb 22 07:54:11 fedora kernel: i915_init+0x22/0xc0 [i915]
Feb 22 07:54:11 fedora kernel: ? __pfx_i915_init+0x10/0x10 [i915]
Feb 22 07:54:11 fedora kernel: do_one_initcall+0x58/0x320
Feb 22 07:54:11 fedora kernel: do_init_module+0x60/0x240
Feb 22 07:54:11 fedora kernel: __do_sys_init_module+0x17f/0x1b0
Feb 22 07:54:11 fedora kernel: ? __seccomp_filter+0x32c/0x4f0
Feb 22 07:54:11 fedora kernel: do_syscall_64+0x61/0xe0
Feb 22 07:54:11 fedora kernel: ? ksys_read+0x6f/0xf0
Feb 22 07:54:11 fedora kernel: ? syscall_exit_to_user_mode+0x2b/0x40
Feb 22 07:54:11 fedora kernel: ? do_syscall_64+0x70/0xe0
Feb 22 07:54:11 fedora kernel: ? exc_page_fault+0x7f/0x180
Feb 22 07:54:11 fedora kernel: entry_SYSCALL_64_after_hwframe+0x6e/0x76
Feb 22 07:54:11 fedora kernel: RIP: 0033:0x7f9a0003d94e
Feb 22 07:54:11 fedora kernel: Code: 48 8b 0d e5 14 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66
2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d b2 14 0c 00 f7 d8 64 89 01 48
....
Best Regards,
Antonio
6:16 p.m.
On Thu, Feb 8, 2024 at 1:56 PM olivares33561 via users <
users(a)lists.fedoraproject.org> wrote:
Dear Fellow Fedora users,
I have installed and tried to boot the 6.6.X kernels in fedora and now the
latest one 6.7.3 one and
have not seen a successful boot of such a kernel. I have had to delete
the kernels every time I try them.
Have you tried watching the boot messages (either press <Esc> or edit the
command line in the GRUB2 menu
by pressing "e" and removing the "rhgb quiet")?
I assume you can boot an older kernel. You may get some error messages for
failed boots using journalctl.
$ sudo dnf remove kernel-core-6.7.3-200.fc39.x86_64
Dependencies resolved.
================================================================================
Package Arch Version Repository
Size
================================================================================
Removing:
kernel-core x86_64 6.7.3-200.fc39 @updates
66 M
Removing dependent packages:
kernel x86_64 6.7.3-200.fc39 @updates
0
kernel-modules x86_64 6.7.3-200.fc39 @updates
57 M
kernel-modules-core x86_64 6.7.3-200.fc39 @updates
32 M
kernel-modules-extra x86_64 6.7.3-200.fc39 @updates
2.4 M
Transaction Summary
================================================================================
Remove 5 Packages
Freed space: 157 M
Is this ok [y/N]: y
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing :
1/1
Erasing : kernel-modules-extra-6.7.3-200.fc39.x86_64
1/5
Running scriptlet: kernel-modules-extra-6.7.3-200.fc39.x86_64
1/5
Erasing : kernel-6.7.3-200.fc39.x86_64
2/5
Running scriptlet: kernel-6.7.3-200.fc39.x86_64
2/5
Erasing : kernel-modules-6.7.3-200.fc39.x86_64
3/5
Running scriptlet: kernel-modules-6.7.3-200.fc39.x86_64
3/5
Erasing : kernel-modules-core-6.7.3-200.fc39.x86_64
4/5
Running scriptlet: kernel-core-6.7.3-200.fc39.x86_64
5/5
Erasing : kernel-core-6.7.3-200.fc39.x86_64
5/5
Running scriptlet: kernel-core-6.7.3-200.fc39.x86_64
5/5
Verifying : kernel-6.7.3-200.fc39.x86_64
1/5
Verifying : kernel-core-6.7.3-200.fc39.x86_64
2/5
Verifying : kernel-modules-6.7.3-200.fc39.x86_64
3/5
Verifying : kernel-modules-core-6.7.3-200.fc39.x86_64
4/5
Verifying : kernel-modules-extra-6.7.3-200.fc39.x86_64
5/5
Removed:
kernel-6.7.3-200.fc39.x86_64
kernel-core-6.7.3-200.fc39.x86_64
kernel-modules-6.7.3-200.fc39.x86_64
kernel-modules-core-6.7.3-200.fc39.x86_64
kernel-modules-extra-6.7.3-200.fc39.x86_64
Complete!
olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ sudo lspci
00:00.0 PCI bridge: Intel Corporation Device 4c53 (rev 01)
00:02.0 VGA compatible controller: Intel Corporation RocketLake-S GT1 [UHD
Graphics 730] (rev 04)
00:04.0 Signal processing controller: Intel Corporation Device 4c03 (rev
01)
00:08.0 System peripheral: Intel Corporation Device 4c11 (rev 01)
00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH
Thermal Controller
00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host
Controller
00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM
00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi
00:15.0 Serial bus controller: Intel Corporation Comet Lake PCH Serial IO
I2C Controller #0
00:16.0 Communication controller: Intel Corporation Comet Lake HECI
Controller
00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller
00:1b.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #21
(rev f0)
00:1c.0 PCI bridge: Intel Corporation Device 06bc (rev f0)
00:1f.0 ISA bridge: Intel Corporation H470 Chipset LPC/eSPI Controller
00:1f.3 Audio device: Intel Corporation Device f1c8
00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller
00:1f.5 Serial bus controller: Intel Corporation Comet Lake PCH SPI
Controller
02:00.0 Non-Volatile memory controller: KIOXIA Corporation NVMe SSD
Controller BG4 (DRAM-less)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 2600
(rev 21)
olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ sudo lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card
Reader Controller
Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$
$ xrandr
Screen 0: minimum 16 x 16, current 1600 x 900, maximum 32767 x 32767
HDMI-2 connected primary 1600x900+0+0 (normal left inverted right x axis y
axis) 440mm x 250mm
1600x900 59.95*+
1152x864 59.96
1024x768 59.92
800x600 59.86
640x480 59.38
320x240 59.52
1440x900 59.89
1280x800 59.81
1152x720 59.97
960x600 59.63
928x580 59.88
800x500 59.50
768x480 59.90
720x480 59.71
640x400 59.95
320x200 58.96
1368x768 59.88
1280x720 59.86
1024x576 59.90
864x486 59.92
720x400 59.55
640x350 59.77
When booting the kernels I tried to see where they were stopping, the boot
showed loading the usb mouse/keyboard combination, but showed disabled. I
tried booting with regular usb mouse and keyboard and the same thing
happens, the kernel does not boot. Secure boot is on. Do not know what to
do to get the newer kernels to boot. I dont create a bugzilla because I no
longer use the email that was associated with bugzilla. The newer kernels
do work on raspberry pi though, so it may be related to the hardware?
with secure boot and signed kernels, I cannot seem to find what is going
on.
Is there a BIOS setting I can try? RAID ON/RAID OFF, running on nvme0
internel disk. Was running on a solid state disk(SSD) before.
Best Regards,
Antonio
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
--
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
--
George N. White III
3:28 p.m.
On 2/8/24 09:56, olivares33561 via users wrote:
I have installed and tried to boot the 6.6.X kernels in fedora and
now the latest one 6.7.3 one and
have not seen a successful boot of such a kernel. I have had to delete the kernels every
time I try them.
Edit the boot command line to remove "rhgb" and "quiet". Then you can
see where it's getting stuck.
Since you said "nomodeset" lets it boot, what is your graphics chipset?
4:06 p.m.
Samuel Sieb composed on 2024-02-14 13:28 (UTC-0800):
olivares33561 wrote:
> I have installed and tried to boot the 6.6.X kernels in fedora
and now the latest one 6.7.3 one and
> have not seen a successful boot of such a kernel. I have had to delete the kernels
every time I try them.
Edit the boot command line to remove "rhgb" and
"quiet". Then you can
see where it's getting stuck.
Since you said "nomodeset" lets it boot, what is your graphics chipset?
I already indicated in thread, his, as indicated in OP, is identical to mine:
Device-1: Intel RocketLake-S GT1 [UHD Graphics 730] vendor: ASUSTeK
driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21
I can't as yet reproduce, but thread hasn't shown much about his software
configuration, which more than likely differs, with me using TDE/TDM and F39's
ancient Xorg 1.20.14, on NVME/EXT4, and with no Fedora bootloader installed.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
7:25 p.m.
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
On Wednesday, February 14th, 2024 at 4:06 PM, Felix Miata <mrmazda(a)earthlink.net>
wrote:
Samuel Sieb composed on 2024-02-14 13:28 (UTC-0800):
> olivares33561 wrote:
> > I have installed and tried to boot the 6.6.X kernels in fedora and now the
latest one 6.7.3 one and
> > have not seen a successful boot of such a kernel. I have had to delete the
kernels every time I try them.
> Edit the boot command line to remove "rhgb" and "quiet". Then
you can
> see where it's getting stuck.
I have done that plenty of times, taken
pictures but to no avail, it did not make a difference. I had to revert to old kernel to
get successful boot.
Thanks to Felix's suggestion I was able to boot the kernel, but the one difference in
my machine secure boot is enabled. When booting the screen/menu is hidden and I cannot
press e to edit the command line to boot. So I appeneded nomodeset to the kernel line
removing rhgb and quiet from it.
> Since you said "nomodeset" lets it boot, what is your
graphics chipset?
I already indicated in thread, his, as indicated in OP, is identical to mine:
Device-1: Intel RocketLake-S GT1 [UHD Graphics 730] vendor: ASUSTeK
driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21
I can't as yet reproduce, but thread hasn't shown much about his software
configuration, which more than likely differs, with me using TDE/TDM and F39's
ancient Xorg 1.20.14, on NVME/EXT4, and with no Fedora bootloader installed.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
--
Using gnome with wayland enabled. Can send/appened output of neofetch later if
needed/desired.
Thanks to all for helping.
Best Regards,
Antonio
7:56 p.m.
olivares33561 composed on 2024-02-15 01:25 (UTC):
>> Edit the boot command line to remove "rhgb" and
"quiet". Then you can
>> see where it's getting stuck.
I have done that plenty of times, taken pictures but to no avail, it
did not make a difference. I had to revert to old kernel to get successful boot.
Thanks to Felix's suggestion I was able to boot the kernel, but
the one difference in my machine secure boot is enabled. When booting the screen/menu is
hidden and I cannot press e to edit the command line to boot. So I appeneded nomodeset to
the kernel line removing rhgb and quiet from it.
Using gnome with wayland enabled. Can send/appened output of
neofetch later if needed/desired.
Let's see how far along your boot gets before the hang. Instead of using nomodeset
in place of "rhgb" and "quiet", remove them and add simply a 3. If you
land a
shell prompt, then the problem is in the GUI somewhere (GDM or Wayland or ???). If
you are able to login, try:
startx /usr/bin/icewm
If you get a command not found error, do:
sudo dnf install icewm
and try again.
Also you should be able to access the journal from a prior unadulterated boot
attempt either the same way, or having used nomodeset, which may have needed
clues. IOW, try to boot normally into a lockup, then on the immediately following
boot, use nomodeset (or if it works, 3) and login. Then:
sudo journalctl -b -1 > somefile.txt
Then attach somefile.txt to your bug report.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
10:24 a.m.
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
On Wednesday, February 14th, 2024 at 7:56 PM, Felix Miata <mrmazda(a)earthlink.net>
wrote:
olivares33561 composed on 2024-02-15 01:25 (UTC):
> > > Edit the boot command line to remove "rhgb" and
"quiet". Then you can
> > > see where it's getting stuck.
> I have done that plenty of times, taken pictures but to no avail, it did not make a
difference. I had to revert to old kernel to get successful boot.
> Thanks to Felix's suggestion I was able to boot the kernel, but the one
difference in my machine secure boot is enabled. When booting the screen/menu is hidden
and I cannot press e to edit the command line to boot. So I appeneded nomodeset to the
kernel line removing rhgb and quiet from it.
> Using gnome with wayland enabled. Can send/appened output of neofetch later if
needed/desired.
Let's see how far along your boot gets before the hang. Instead of using nomodeset
in place of "rhgb" and "quiet", remove them and add simply a 3. If
you land a
shell prompt, then the problem is in the GUI somewhere (GDM or Wayland or ???). If
you are able to login, try:
startx /usr/bin/icewm
If you get a command not found error, do:
sudo dnf install icewm
and try again.
Also you should be able to access the journal from a prior unadulterated boot
attempt either the same way, or having used nomodeset, which may have needed
clues. IOW, try to boot normally into a lockup, then on the immediately following
boot, use nomodeset (or if it works, 3) and login. Then:
sudo journalctl -b -1 > somefile.txt
Then attach somefile.txt to your bug report.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
--
Dear Sir,
Thank you for all your advice. The machine stalled. Did not boot.
output of neofetch.
olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ neofetch
.',;::::;,'. olivares@fedora
.';:cccccccccccc:;,. ---------------
.;cccccccccccccccccccccc;. OS: Fedora Linux 39 (Workstation Editi
.:cccccccccccccccccccccccccc:. Host: XPS 8940
.;ccccccccccccc;.:dddl:.;ccccccc;. Kernel: 6.7.4-200.fc39.x86_64
.:ccccccccccccc;OWMKOOXMWd;ccccccc:. Uptime: 2 mins
.:ccccccccccccc;KMMc;cc;xMMc:ccccccc:. Packages: 2698 (rpm)
,cccccccccccccc;MMM.;cc;;WW::cccccccc, Shell: bash 5.2.26
:cccccccccccccc;MMM.;cccccccccccccccc: Resolution: 1600x900
:ccccccc;oxOOOo;MMM0OOk.;cccccccccccc: DE: GNOME 45.4
cccccc:0MMKxdd:;MMMkddc.;cccccccccccc; WM: Mutter
ccccc:XM0';cccc;MMM.;cccccccccccccccc' WM Theme: Adwaita
ccccc;MMo;ccccc;MMW.;ccccccccccccccc; Theme: Adwaita [GTK2/3]
ccccc;0MNc.ccc.xMMd:ccccccccccccccc; Icons: Adwaita [GTK2/3]
cccccc;dNMWXXXWM0::cccccccccccccc:, Terminal: gnome-terminal
cccccccc;.:odl:.;cccccccccccccc:,. CPU: 11th Gen Intel i5-11400 (12) @ 4.
:cccccccccccccccccccccccccccc:'. GPU: Intel RocketLake-S GT1 [UHD Graph
.:cccccccccccccccccccccc:;,.. Memory: 2414MiB / 7509MiB
'::cccccccccccccc::;,.
olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$
Will try to attach output of journaltcl command to bugzilla.
Best Regards,
Antonio
1:52 p.m.
On 2/15/24 08:24, olivares33561 via users wrote:
Thank you for all your advice. The machine stalled. Did not boot.
But what is the last thing on the screen when it stalls?
Will try to attach output of journaltcl command to bugzilla.
You need to follow the instructions to get the journal output of the
*previous* boot that didn't work.
2:02 p.m.
olivares33561 users composed on 2024-02-15 16:24 (UTC):
...
I have another suggestion. Instead of appending 3 in place of " rhgb" and "
quiet"
or " nomodeset", append " noresume", either with or without "
3".
Another to try: " enforcing=0"
Do any of these bring a shell prompt or login screen?
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
2 p.m.
same CPU and GPU here.
secure boot is off
no bugs
====
have you loaded the setup defaults after bios update ?
I wonder if a selinux relabeling would help ?
if so:
in an terminal:
sudo touch /.autorelabel;
and
a reboot (with a running kernel)
and
then with the faulty kernel again
6:18 p.m.
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
On Friday, February 16th, 2024 at 2:00 PM, old sixpack13 <sixpack13(a)online.de>
wrote:
same CPU and GPU here.
secure boot is off
Secure Boot on
no bugs
====
have you loaded the setup defaults after bios update ?
No
I wonder if a selinux relabeling would help ?
if so:
in an terminal:
sudo touch /.autorelabel;
and
a reboot (with a running kernel)
Can give it a try next Monday and report back.
and
then with the faulty kernel again
--
Thank you for sharing your advice. On Monday I shall try it and report back.
Best Regards,
Antonio
6:29 p.m.
On 2/16/24 12:00, old sixpack13 wrote:
same CPU and GPU here.
secure boot is off
no bugs
====
have you loaded the setup defaults after bios update ?
I wonder if a selinux relabeling would help ?
if so:
in an terminal:
sudo touch /.autorelabel;
and
a reboot (with a running kernel)
and
then with the faulty kernel again
There's no indication of an selinux problem. How would that be relevant
when a different kernel boots fine?
112
days inactive
126
days old
25 comments
5 participants
participants (5)
-
Felix Miata -
George N. White III -
old sixpack13 -
olivares33561 -
Samuel Sieb