Page: 1, 2, 3  Next

Cannot boot since kernel 5.14.0-15.1-liquorix-amd64
Mono
Status: Contributor
Joined: 21 Jun 2012
Posts: 115
Reply Quote
After kernel 5.14.0-15.1 he bootup hangs on some new splash screen with 3 dots. Keyboard is unresponsive and the numpad/capslock lights often don't work. I can't get to a console.

Looking at the journalctl logs there are no strange messages when this happens.

I am on Debian Sid.

:: Code ::
$ inxi -bxx
System:
  Host: ronin Kernel: 5.14.0-15.1-liquorix-amd64 x86_64 bits: 64
  compiler: gcc v: 10.3.0 Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 wm: xfwm
  dm: LightDM Distro: Debian GNU/Linux bookworm/sid
Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX B350-F GAMING v: Rev X.0x
  serial: <superuser required> UEFI-[Legacy]: American Megatrends v: 5603
  date: 07/28/2020
CPU:
  Info: Quad Core AMD Ryzen 5 1500X [MT MCP] arch: Zen speed: 2881 MHz
  min/max: 1550/3500 MHz
Graphics:
  Device-1: NVIDIA GM206 [GeForce GTX 950] vendor: eVga.com. driver: nvidia
  v: 470.74 bus-ID: 09:00.0 chip-ID: 10de:1402
  Device-2: NVIDIA GK208B [GeForce GT 730] vendor: eVga.com. driver: nvidia
  v: 470.74 bus-ID: 0a:00.0 chip-ID: 10de:1287
  Display: x11 server: X.Org 1.20.11 compositor: xfwm4 driver:
  loaded: nvidia resolution: 1: 1600x1200~75Hz 2: 1280x960~60Hz s-dpi: 96
  OpenGL: renderer: NVIDIA GeForce GTX 950/PCIe/SSE2 v: 4.6.0 NVIDIA 470.74
  direct render: Yes
Network:
  Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
  port: e000 bus-ID: 04:00.0 chip-ID: 8086:1539
Drives:
  Local Storage: total: 1.26 TiB used: 287.69 GiB (22.3%)
Info:
  Processes: 321 Uptime: 36m Memory: 23.42 GiB used: 4.13 GiB (17.7%)
  Init: systemd v: 249 runlevel: 5 Compilers: gcc: 11.2.0 alt: 10/11
  Packages: 2410 apt: 2387 flatpak: 14 snap: 9 Shell: Bash v: 5.1.8
  running-in: xfce4-terminal inxi: 3.3.07


< Edited by Mono :: Nov 21, 21, 8:35 >

Back to top
rooots
Status: Interested
Joined: 17 May 2020
Posts: 43
Reply Quote
Please provide the output of inxi -bxz.

Have you tried updating to the latest 5.14.0-19.2-liquorix-amd64?
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 931
Reply Quote
Yes, it is strange that you're reporting an issue for an old kernel. Either way, I think you're reporting an issue for a known bug that was fixed:

:: Code ::
linux-liquorix (5.14-21) unstable; urgency=medium

  * force enable CONFIG_FB_SIMPLE
  * update version to 5.14.0-16.4

 -- Steven Barrett <steven@liquorix.net>  Wed, 03 Nov 2021 16:35:46 -0500

linux-liquorix (5.14-20) unstable; urgency=medium

  * enable fbdev triple buffering
  * disable logo support entirely
  * update version to 5.14.0-16.3

 -- Steven Barrett <steven@liquorix.net>  Wed, 03 Nov 2021 16:26:16 -0500

linux-liquorix (5.14-19) unstable; urgency=medium

  * backport framebuffer configuration from Ubuntu/Debian
  * update version to 5.14.0-16.2

 -- Steven Barrett <steven@liquorix.net>  Wed, 03 Nov 2021 09:56:11 -0500

linux-liquorix (5.14-18) unstable; urgency=medium

  * merge 5.14.16
  * backport upcoming CPU vulnerability mitigation updates
   - x86: change default to spec_store_bypass_disable=prctl spectre_v2_user=prctl
   - x86: deduplicate the spectre_v2_user documentation
  * update version to 5.14.0-16.1

 -- Steven Barrett <steven@liquorix.net>  Tue, 02 Nov 2021 14:31:59 -0500

linux-liquorix (5.14-17) unstable; urgency=medium

  * merge 5.14.15
  * update version to 5.14.0-15.1

 -- Steven Barrett <steven@liquorix.net>  Wed, 27 Oct 2021 17:15:49 -0500


Stable updates to the Kconfig settings for SimpleFB changed, requiring a few tweaks to get some systems to print output again. This is most likely the issue you have, but again, I'm surprised you're reporting an issue for an old unsupported/deprecated kernel.
Back to top
Mono
Status: Contributor
Joined: 21 Jun 2012
Posts: 115
Reply Quote
I can't boot any Liquorix kernel after 5.14-15.1, including 5.14.0-19.2

The default Sid 5.15 kernel works, but not Liquorix. I have been waiting to see if it resolves itself but no luck. Either I get a buggy console splash screen or I get a cursor in the upper left but no response to input.

:: Code ::
$ inxi -bxz
System:
  Kernel: 5.15.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 11.2.0
  Desktop: Xfce 4.16.0 Distro: Debian GNU/Linux bookworm/sid
Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX B350-F GAMING v: Rev X.0x
  serial: <filter> UEFI-[Legacy]: American Megatrends v: 5603
  date: 07/28/2020
CPU:
  Info: Quad Core AMD Ryzen 5 1500X [MT MCP] arch: Zen speed: 3756 MHz
  min/max: 1550/3500 MHz
Graphics:
  Device-1: NVIDIA GM206 [GeForce GTX 950] vendor: eVga.com. driver: nvidia
  v: 495.44 bus-ID: 09:00.0
  Device-2: NVIDIA GK208B [GeForce GT 730] vendor: eVga.com. driver: N/A
  bus-ID: 0a:00.0
  Display: x11 server: X.Org 1.20.11 driver: loaded: nvidia resolution:
  1: 1600x1200~75Hz 2: 1280x960~60Hz
  OpenGL: renderer: NVIDIA GeForce GTX 950/PCIe/SSE2 v: 4.6.0 NVIDIA 495.44
  direct render: Yes
Network:
  Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
  port: e000 bus-ID: 04:00.0
Drives:
  Local Storage: total: 1.26 TiB used: 53.33 GiB (4.1%)
Info:
  Processes: 278 Uptime: 3h 13m Memory: 23.48 GiB used: 6.65 GiB (28.3%)
  Init: systemd runlevel: 5 Compilers: gcc: 11.2.0 Packages: 2414
  Shell: Bash v: 5.1.8 inxi: 3.3.07

Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 931
Reply Quote
Ok well, there's quite a few things you can do at this point.

1) Just try booting without the splash screen and enable the most verbose kernel log mode. So add nosplash loglevel=7 to your kernel boot parameters. That by itself may reveal what the issue is.

2) You can run sudo journalctl -k -b -1 to look at logs from your previous boot. Is there anything interesting in there that's not in your other boots?

3) I see that you have two GPUs installed. Maybe some strange interaction between the proprietary nvidia driver and having two drivers on 5.15 is causing your system issues? I can easily see the driver deciding to try booting with the uninitialized card rather than the one you intended if not configured properly. So a dumb solution may be to simply remove the unused card, if you don't actually use it. That will greatly reduce the surface area of boot issues on your system.

4) Is there something different in /var/log/Xorg.0.log? You said you get a blinking cursor, but consider we don't know what stage of boot you're at, is it actually Xorg that has failed here? Maybe the nvidia driver is simply not installed on the Liquorix kernel and that's why you the classic blinking cursor that's indicative of that.
Back to top
rooots
Status: Interested
Joined: 17 May 2020
Posts: 43
Reply Quote
Picking up #3 of the previous answer, I'd suggest giving the latest NV driver of your distribution (is there such thing for debian?) a go instead of the prop NV driver. Under Ubuntu, I was never really happy with the "original" NV driver.
Back to top
Mono
Status: Contributor
Joined: 21 Jun 2012
Posts: 115
Reply Quote
nvidiafb is crashing:

:: Code ::
Nov 22 08:28:50 ronin kernel: nvidiafb: Unable to detect display type...
Nov 22 08:28:50 ronin kernel: ...Using default of CRT
Nov 22 08:28:50 ronin kernel: nvidiafb: Unable to detect which CRTCNumber...
Nov 22 08:28:50 ronin kernel: ...Defaulting to CRTCNumber 0
Nov 22 08:28:50 ronin kernel: nvidiafb: Using CRT on CRTC 0
Nov 22 08:28:50 ronin systemd-udevd[415]: Worker [435] terminated by signal 11 (SEGV)
Nov 22 08:28:50 ronin kernel: divide error: 0000 [#1] PREEMPT SMP NOPTI
Nov 22 08:28:50 ronin kernel: CPU: 3 PID: 435 Comm: systemd-udevd Not tainted 5.15.0-3.2-liquorix-amd64 #1  liquorix 5.15-2.1~sid
Nov 22 08:28:50 ronin kernel: Hardware name: System manufacturer System Product Name/ROG STRIX B350-F GAMING, BIOS 5603 07/28/2020
Nov 22 08:28:50 ronin kernel: RIP: 0010:nvGetClocks+0x1ad/0x2c0 [nvidiafb]
Nov 22 08:28:50 ronin kernel: Code: 0f 84 a4 00 00 00 3d 30 03 00 00 0f 84 99 00 00 00 8b 8a 04 05 00 00 0f b6 c5 31 d2 41 0f af c1 44 0f b6 c9 c1 e9 10 83 e>
Nov 22 08:28:50 ronin kernel: RSP: 0018:ffffc900010d7858 EFLAGS: 00010246
Nov 22 08:28:50 ronin kernel: RAX: 0000000000000000 RBX: ffff8882105a2418 RCX: 0000000000000000
Nov 22 08:28:50 ronin kernel: RDX: 0000000000000000 RSI: ffffc900010d7884 RDI: ffff8882105a2418
Nov 22 08:28:50 ronin kernel: RBP: ffff8882105a2510 R08: ffffc900010d7880 R09: 0000000000000000
Nov 22 08:28:50 ronin kernel: R10: 00000000002e18c8 R11: 0000000000000068 R12: 0000000000062570
Nov 22 08:28:50 ronin kernel: R13: 000000000000000e R14: 0000000000000010 R15: 0000000000000008
Nov 22 08:28:50 ronin kernel: FS:  00007f8d8d29b8c0(0000) GS:ffff8886168c0000(0000) knlGS:0000000000000000
Nov 22 08:28:50 ronin kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 22 08:28:50 ronin kernel: CR2: 0000564a517e91f8 CR3: 00000001e1774000 CR4: 00000000003506e0
Nov 22 08:28:50 ronin kernel: Call Trace:
Nov 22 08:28:50 ronin kernel:  <TASK>
Nov 22 08:28:50 ronin kernel:  NVCalcStateExt+0x1bb/0x910 [nvidiafb]
Nov 22 08:28:50 ronin kernel:  ? __slab_free+0x121/0x340
Nov 22 08:28:50 ronin kernel:  ? kmem_cache_alloc_trace+0x2a6/0x410
Nov 22 08:28:50 ronin kernel:  ? kmem_cache_alloc_trace+0x2a6/0x410
Nov 22 08:28:50 ronin kernel:  nvidiafb_set_par+0x46c/0x9f0 [nvidiafb]
Nov 22 08:28:50 ronin kernel:  fbcon_init+0x27c/0x530
Nov 22 08:28:50 ronin kernel:  visual_init+0xcc/0x130
Nov 22 08:28:50 ronin kernel:  do_bind_con_driver.isra.0+0x1c2/0x2d0
Nov 22 08:28:50 ronin kernel:  do_take_over_console+0x116/0x1a0
Nov 22 08:28:50 ronin kernel:  do_fbcon_takeover+0x5c/0xd0
Nov 22 08:28:50 ronin kernel:  register_framebuffer+0x1e4/0x310
Nov 22 08:28:50 ronin kernel:  nvidiafb_probe.cold+0x789/0x80a [nvidiafb]
Nov 22 08:28:50 ronin kernel:  local_pci_probe+0x45/0x90
Nov 22 08:28:50 ronin kernel:  ? pci_match_device+0xdf/0x140
Nov 22 08:28:50 ronin kernel:  pci_device_probe+0x100/0x1c0
Nov 22 08:28:50 ronin kernel:  really_probe.part.0+0xb8/0x2b0
Nov 22 08:28:50 ronin kernel:  __driver_probe_device+0x90/0x120
Nov 22 08:28:50 ronin kernel:  driver_probe_device+0x1e/0xe0
Nov 22 08:28:50 ronin kernel:  __driver_attach+0xaf/0x190
Nov 22 08:28:50 ronin kernel:  ? __device_attach_driver+0x100/0x100
Nov 22 08:28:50 ronin kernel:  bus_for_each_dev+0x7c/0xd0
Nov 22 08:28:50 ronin kernel:  bus_add_driver+0x11a/0x1c0
Nov 22 08:28:50 ronin kernel:  driver_register+0x8f/0xf0
Nov 22 08:28:50 ronin kernel:  ? nvidiafb_setcolreg+0x300/0x300 [nvidiafb]
Nov 22 08:28:50 ronin kernel:  do_one_initcall+0x9e/0x270
Nov 22 08:28:50 ronin kernel:  ? load_module+0x26c6/0x2a00
Nov 22 08:28:50 ronin kernel:  ? security_kernel_post_read_file+0x38/0x60
Nov 22 08:28:50 ronin kernel:  ? kmem_cache_alloc_trace+0x2a6/0x410
Nov 22 08:28:50 ronin kernel:  do_init_module+0x5c/0x270
Nov 22 08:28:50 ronin kernel:  __x64_sys_finit_module+0xac/0x100
Nov 22 08:28:50 ronin kernel:  do_syscall_64+0x3b/0x90
Nov 22 08:28:50 ronin kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xae
Nov 22 08:28:50 ronin kernel: RIP: 0033:0x7f8d8d74c5e9
Nov 22 08:28:50 ronin kernel: Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0>
Nov 22 08:28:50 ronin kernel: RSP: 002b:00007ffef65e0f08 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Nov 22 08:28:50 ronin kernel: RAX: ffffffffffffffda RBX: 0000564a51814030 RCX: 00007f8d8d74c5e9
Nov 22 08:28:50 ronin kernel: RDX: 0000000000000000 RSI: 00007f8d8d8f8eed RDI: 0000000000000010
Nov 22 08:28:50 ronin kernel: RBP: 0000000000020000 R08: 0000000000000000 R09: 0000564a5180b3f0
Nov 22 08:28:50 ronin kernel: R10: 0000000000000010 R11: 0000000000000246 R12: 00007f8d8d8f8eed
Nov 22 08:28:50 ronin kernel: R13: 0000000000000000 R14: 0000564a516ee330 R15: 0000564a51814030
Nov 22 08:28:50 ronin kernel:  </TASK>
Nov 22 08:28:50 ronin kernel: Modules linked in: snd_hda_codec_realtek intel_rapl_msr snd_hda_codec_generic intel_rapl_common ledtrig_audio snd_hda_codec_hdm>
Nov 22 08:28:50 ronin kernel: ---[ end trace 381aa40e3aff9ffc ]---
Nov 22 08:28:50 ronin kernel: RIP: 0010:nvGetClocks+0x1ad/0x2c0 [nvidiafb]
Nov 22 08:28:50 ronin kernel: Code: 0f 84 a4 00 00 00 3d 30 03 00 00 0f 84 99 00 00 00 8b 8a 04 05 00 00 0f b6 c5 31 d2 41 0f af c1 44 0f b6 c9 c1 e9 10 83 e>
Nov 22 08:28:50 ronin kernel: RSP: 0018:ffffc900010d7858 EFLAGS: 00010246
Nov 22 08:28:50 ronin kernel: RAX: 0000000000000000 RBX: ffff8882105a2418 RCX: 0000000000000000
Nov 22 08:28:50 ronin kernel: RDX: 0000000000000000 RSI: ffffc900010d7884 RDI: ffff8882105a2418




The last lines of the log are from me pressing ctrl-alt-del more than 7 times. It tries to reboot, but I guess it fails for some reason. I have also been getting a crash dump on my screen just before shutting down, but that has been happening longer than this bug.
Back to top
rooots
Status: Interested
Joined: 17 May 2020
Posts: 43
Reply Quote
Ok...I see I was a bit imprecise here. I did mean that I'm using the proprietary NV driver, but the "tested" version which comes in the Ubuntu repos, instead of the one that can be downloaded from the NV website. The latter usually is more recent but did not play well several times I tried. Have you tried connecting your display to another DP/HDMI port and checked what happens if you try to boot with only one of your GPUs installed?

I have never used the "free" NV driver because it usually did not support latest-gen GPUs well.

By the way - there's a more recent version for you mobo BIOS dated 2021/08/09 that you may want to check. Probably won't solve your issue but probably won't hurt either ;-)
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 931
Reply Quote
It does look like your framebuffer is confused. This line right here:
:: Code ::
Nov 22 08:28:50 ronin kernel: nvidiafb: Unable to detect display type...
Nov 22 08:28:50 ronin kernel: ...Using default of CRT
Nov 22 08:28:50 ronin kernel: nvidiafb: Unable to detect which CRTCNumber...
Nov 22 08:28:50 ronin kernel: ...Defaulting to CRTCNumber 0
Nov 22 08:28:50 ronin kernel: nvidiafb: Using CRT on CRTC 0


I highly recommend removing the unused nvidia GPU from your system and seeing if that helps.

Another option is to add blacklist nvidiafb to your /etc/modprobe.d/blacklist.conf file. You'll still be able to boot, but your system will fallback to a super generic framebuffer at 640x480 until your desktop can initialize. You can also just add it temporarily to your kernel boot parameters with module_blacklist=nvidiafb before committing it to your filesystem.
Back to top
Mono
Status: Contributor
Joined: 21 Jun 2012
Posts: 115
Reply Quote
I need both cards to display on 3 monitors. Linux does have a problem where nvidia detects monitors but doesn't communicate them properly to xorg on some ports, so I can't get my 3rd monitor working with a desktop environment.

I will update the BIOS, but that update only seems to matter for windows 11.
Back to top
Display posts from previous:   
Page: 1, 2, 3  Next
All times are GMT - 8 Hours