You are not logged in.

Pages: 1

#1 2024-12-17 11:50:29

marq13
Member
Registered: 2024-10-10
Posts: 17

Kernel Log: Warnings for Integrated Intel & Nvidia Graphics

Hi yall, I hope everyone is having an amazing day.

I've been using arch over three months without any breaking issues.
For a past month, after I timeshifted I believe, I started getting a "weird warning-like" message at boot time.
Since I had no issues, and due to the lack of time that I had that/this month, I decided to ignore it.

This morning however I decided to look into it, so the first thing I did is look at the output of dmesg. It appears that the issue is related to the driver for the integrated intel.
That is weird. I remember when I was looking into arch and figuring out everything I need to install it correctly, I never stumbled upon anything driver related for integrated graphics. (Maybe I was too overwhelmed with nvidia). I thought that it was automatically supported because everything worked out of the box.

Here's the output of dmesg for integrated graphics:

[    1.133281] ------------[ cut here ]------------
[    1.133291] i915 0000:00:02.0: [drm] drm_WARN_ON(val == 0xffffffff)
[    1.133349] WARNING: CPU: 6 PID: 187 at drivers/gpu/drm/i915/display/intel_tc.c:740 tgl_tc_phy_init+0x107/0x130 [i915]
[    1.133471] Modules linked in: i915(+) i2c_algo_bit drm_buddy serio_raw ttm atkbd nvme libps2 vivaldi_fmap intel_gtt drm_display_helper crc32c_intel nvme_core spi_intel_pci spi_intel cec nvme_auth video i8042 serio wmi
[    1.133481] CPU: 6 UID: 0 PID: 187 Comm: (udev-worker) Not tainted 6.12.4-arch1-1 #1 7c6e9657ff18c9ac01abfce09529b4cbe186f917
[    1.133483] Hardware name: LENOVO 82K1/LNVNB161216, BIOS H4CN34WW(V2.03) 12/19/2023
[    1.133484] RIP: 0010:tgl_tc_phy_init+0x107/0x130 [i915]
[    1.133575] Code: 48 8b 6f 50 48 85 ed 75 03 48 8b 2f e8 72 9d 81 c5 48 c7 c1 e8 49 9c c0 48 89 ea 48 c7 c7 ee 74 9e c0 48 89 c6 e8 49 e8 f1 c4 <0f> 0b 48 8b 3b e8 0f 64 f9 ff 89 c1 89 c5 c1 e9 1f c1 ed 1f 8d 14
[    1.133576] RSP: 0018:ffffb62740a8f638 EFLAGS: 00010286
[    1.133577] RAX: 0000000000000000 RBX: ffff89a084efdc00 RCX: 0000000000000003
[    1.133578] RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000001
[    1.133579] RBP: ffff89a0821f6880 R08: 0000000000000000 R09: ffffb62740a8f4b8
[    1.133580] R10: ffffffff876b54a8 R11: 0000000000000003 R12: ffff89a0909ec000
[    1.133581] R13: ffff89a0909ec618 R14: 000fffffffe00000 R15: ffff89a0909ec000
[    1.133582] FS:  000079461d690880(0000) GS:ffff89a41fb00000(0000) knlGS:0000000000000000
[    1.133583] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    1.133584] CR2: 00007d9fc2fead90 CR3: 000000011088e003 CR4: 0000000000f70ef0
[    1.133585] PKRU: 55555554
[    1.133585] Call Trace:
[    1.133587]  <TASK>
[    1.133588]  ? tgl_tc_phy_init+0x107/0x130 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.133679]  ? __warn.cold+0x93/0xf6
[    1.133682]  ? tgl_tc_phy_init+0x107/0x130 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.133762]  ? report_bug+0xff/0x140
[    1.133764]  ? console_unlock+0x9d/0x140
[    1.133767]  ? handle_bug+0x58/0x90
[    1.133769]  ? exc_invalid_op+0x17/0x70
[    1.133770]  ? asm_exc_invalid_op+0x1a/0x20
[    1.133772]  ? tgl_tc_phy_init+0x107/0x130 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.133846]  ? tgl_tc_phy_init+0x107/0x130 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.133915]  intel_tc_port_init+0x182/0x230 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.133990]  intel_ddi_init+0xa65/0x1120 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.134082]  ? __pfx_intel_ddi_init+0x10/0x10 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.134166]  intel_bios_for_each_encoder+0x35/0x50 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.134276]  intel_setup_outputs+0x4e1/0xc10 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.134382]  intel_display_driver_probe_nogem+0x14f/0x230 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.134476]  i915_driver_probe+0x3e0/0xb10 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.134555]  local_pci_probe+0x42/0x90
[    1.134557]  pci_device_probe+0x22f/0x270
[    1.134560]  really_probe+0xdb/0x340
[    1.134562]  ? pm_runtime_barrier+0x54/0x90
[    1.134564]  ? __pfx___driver_attach+0x10/0x10
[    1.134566]  __driver_probe_device+0x78/0x110
[    1.134568]  driver_probe_device+0x1f/0xa0
[    1.134570]  __driver_attach+0xba/0x1c0
[    1.134572]  bus_for_each_dev+0x8c/0xe0
[    1.134574]  bus_add_driver+0x112/0x1f0
[    1.134576]  driver_register+0x72/0xd0
[    1.134577]  i915_init+0x23/0x90 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.134649]  ? __pfx_i915_init+0x10/0x10 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.134721]  do_one_initcall+0x58/0x310
[    1.134724]  do_init_module+0x60/0x230
[    1.134725]  init_module_from_file+0x89/0xe0
[    1.134727]  idempotent_init_module+0x11e/0x310
[    1.134728]  __x64_sys_finit_module+0x5e/0xb0
[    1.134730]  do_syscall_64+0x82/0x190
[    1.134732]  ? do_sys_openat2+0x9c/0xe0
[    1.134735]  ? syscall_exit_to_user_mode+0x37/0x1c0
[    1.134736]  ? do_syscall_64+0x8e/0x190
[    1.134738]  ? vfs_statx+0x8d/0x100
[    1.134740]  ? strncpy_from_user+0x24/0x100
[    1.134742]  ? vfs_fstatat+0x8a/0xb0
[    1.134743]  ? __do_sys_newfstatat+0x3c/0x80
[    1.134745]  ? syscall_exit_to_user_mode+0x37/0x1c0
[    1.134746]  ? do_syscall_64+0x8e/0x190
[    1.134748]  ? syscall_exit_to_user_mode+0x37/0x1c0
[    1.134749]  ? do_syscall_64+0x8e/0x190
[    1.134750]  ? do_syscall_64+0x8e/0x190
[    1.134752]  ? clear_bhb_loop+0x25/0x80
[    1.134754]  ? clear_bhb_loop+0x25/0x80
[    1.134755]  ? clear_bhb_loop+0x25/0x80
[    1.134757]  entry_SYSCALL_64_after_hwframe+0x76/0x7e
[    1.134759] RIP: 0033:0x79461de861fd
[    1.134761] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e3 fa 0c 00 f7 d8 64 89 01 48
[    1.134762] RSP: 002b:00007ffe71ef2368 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[    1.134764] RAX: ffffffffffffffda RBX: 00005f3491560ab0 RCX: 000079461de861fd
[    1.134764] RDX: 0000000000000004 RSI: 000079461d68a05d RDI: 0000000000000026
[    1.134765] RBP: 00007ffe71ef2420 R08: 0000000000000001 R09: 00007ffe71ef23b0
[    1.134766] R10: 0000000000000040 R11: 0000000000000246 R12: 000079461d68a05d
[    1.134767] R13: 0000000000020000 R14: 00005f3491561510 R15: 00005f34915630c0
[    1.134768]  </TASK>
[    1.134769] ---[ end trace 0000000000000000 ]---
[    1.134812] ------------[ cut here ]------------
[    1.134813] i915 0000:00:02.0: [drm] drm_WARN_ON(val == 0xffffffff)
[    1.134821] WARNING: CPU: 6 PID: 187 at drivers/gpu/drm/i915/display/intel_tc.c:740 tgl_tc_phy_init+0x107/0x130 [i915]
[    1.134926] Modules linked in: i915(+) i2c_algo_bit drm_buddy serio_raw ttm atkbd nvme libps2 vivaldi_fmap intel_gtt drm_display_helper crc32c_intel nvme_core spi_intel_pci spi_intel cec nvme_auth video i8042 serio wmi
[    1.134934] CPU: 6 UID: 0 PID: 187 Comm: (udev-worker) Tainted: G        W          6.12.4-arch1-1 #1 7c6e9657ff18c9ac01abfce09529b4cbe186f917
[    1.134936] Tainted: [W]=WARN
[    1.134937] Hardware name: LENOVO 82K1/LNVNB161216, BIOS H4CN34WW(V2.03) 12/19/2023
[    1.134937] RIP: 0010:tgl_tc_phy_init+0x107/0x130 [i915]
[    1.135023] Code: 48 8b 6f 50 48 85 ed 75 03 48 8b 2f e8 72 9d 81 c5 48 c7 c1 e8 49 9c c0 48 89 ea 48 c7 c7 ee 74 9e c0 48 89 c6 e8 49 e8 f1 c4 <0f> 0b 48 8b 3b e8 0f 64 f9 ff 89 c1 89 c5 c1 e9 1f c1 ed 1f 8d 14
[    1.135024] RSP: 0018:ffffb62740a8f638 EFLAGS: 00010286
[    1.135025] RAX: 0000000000000000 RBX: ffff89a084efda00 RCX: 0000000000000003
[    1.135026] RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000001
[    1.135026] RBP: ffff89a0821f6880 R08: 0000000000000000 R09: ffffb62740a8f4b8
[    1.135027] R10: ffffffff876b54a8 R11: 0000000000000003 R12: ffff89a0909ec000
[    1.135028] R13: ffff89a0909ec618 R14: 000fffffffe00000 R15: ffff89a0909ec000
[    1.135029] FS:  000079461d690880(0000) GS:ffff89a41fb00000(0000) knlGS:0000000000000000
[    1.135030] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    1.135031] CR2: 00007d9fc2fead90 CR3: 000000011088e003 CR4: 0000000000f70ef0
[    1.135032] PKRU: 55555554
[    1.135032] Call Trace:
[    1.135033]  <TASK>
[    1.135033]  ? tgl_tc_phy_init+0x107/0x130 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.135112]  ? __warn.cold+0x93/0xf6
[    1.135113]  ? tgl_tc_phy_init+0x107/0x130 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.135186]  ? report_bug+0xff/0x140
[    1.135188]  ? console_unlock+0x9d/0x140
[    1.135190]  ? handle_bug+0x58/0x90
[    1.135191]  ? exc_invalid_op+0x17/0x70
[    1.135192]  ? asm_exc_invalid_op+0x1a/0x20
[    1.135194]  ? tgl_tc_phy_init+0x107/0x130 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.135265]  ? tgl_tc_phy_init+0x107/0x130 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.135336]  intel_tc_port_init+0x182/0x230 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.135418]  intel_ddi_init+0xa65/0x1120 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.135511]  ? __pfx_intel_ddi_init+0x10/0x10 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.135593]  intel_bios_for_each_encoder+0x35/0x50 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.135701]  intel_setup_outputs+0x4e1/0xc10 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.135808]  intel_display_driver_probe_nogem+0x14f/0x230 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.135901]  i915_driver_probe+0x3e0/0xb10 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.135978]  local_pci_probe+0x42/0x90
[    1.135980]  pci_device_probe+0x22f/0x270
[    1.135982]  really_probe+0xdb/0x340
[    1.135984]  ? pm_runtime_barrier+0x54/0x90
[    1.135986]  ? __pfx___driver_attach+0x10/0x10
[    1.135988]  __driver_probe_device+0x78/0x110
[    1.135990]  driver_probe_device+0x1f/0xa0
[    1.135992]  __driver_attach+0xba/0x1c0
[    1.135994]  bus_for_each_dev+0x8c/0xe0
[    1.135996]  bus_add_driver+0x112/0x1f0
[    1.135997]  driver_register+0x72/0xd0
[    1.135998]  i915_init+0x23/0x90 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.136072]  ? __pfx_i915_init+0x10/0x10 [i915 32b95dcf04dadb9f37d09e0412929f6c7dd51682]
[    1.136143]  do_one_initcall+0x58/0x310
[    1.136146]  do_init_module+0x60/0x230
[    1.136147]  init_module_from_file+0x89/0xe0
[    1.136149]  idempotent_init_module+0x11e/0x310
[    1.136150]  __x64_sys_finit_module+0x5e/0xb0
[    1.136152]  do_syscall_64+0x82/0x190
[    1.136154]  ? do_sys_openat2+0x9c/0xe0
[    1.136157]  ? syscall_exit_to_user_mode+0x37/0x1c0
[    1.136158]  ? do_syscall_64+0x8e/0x190
[    1.136160]  ? vfs_statx+0x8d/0x100
[    1.136161]  ? strncpy_from_user+0x24/0x100
[    1.136163]  ? vfs_fstatat+0x8a/0xb0
[    1.136164]  ? __do_sys_newfstatat+0x3c/0x80
[    1.136166]  ? syscall_exit_to_user_mode+0x37/0x1c0
[    1.136167]  ? do_syscall_64+0x8e/0x190
[    1.136169]  ? syscall_exit_to_user_mode+0x37/0x1c0
[    1.136170]  ? do_syscall_64+0x8e/0x190
[    1.136171]  ? do_syscall_64+0x8e/0x190
[    1.136172]  ? clear_bhb_loop+0x25/0x80
[    1.136174]  ? clear_bhb_loop+0x25/0x80
[    1.136176]  ? clear_bhb_loop+0x25/0x80
[    1.136177]  entry_SYSCALL_64_after_hwframe+0x76/0x7e
[    1.136179] RIP: 0033:0x79461de861fd
[    1.136180] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e3 fa 0c 00 f7 d8 64 89 01 48
[    1.136181] RSP: 002b:00007ffe71ef2368 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[    1.136182] RAX: ffffffffffffffda RBX: 00005f3491560ab0 RCX: 000079461de861fd
[    1.136182] RDX: 0000000000000004 RSI: 000079461d68a05d RDI: 0000000000000026
[    1.136183] RBP: 00007ffe71ef2420 R08: 0000000000000001 R09: 00007ffe71ef23b0
[    1.136184] R10: 0000000000000040 R11: 0000000000000246 R12: 000079461d68a05d
[    1.136184] R13: 0000000000020000 R14: 00005f3491561510 R15: 00005f34915630c0
[    1.136186]  </TASK>
[    1.136186] ---[ end trace 0000000000000000 ]---

I didn't know what to include, so I posted everything, even the CPU registers.

Another thing that caught my eye when looking at the dmesg output, is the nvidia warning message. Here's that part too: (which is not in the boot messages)

[    5.533099] nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
[    5.608761] nvidia-uvm: Loaded the UVM driver, major device number 509.
[    7.277090] [drm] Initialized nvidia-drm 0.0.0 for 0000:02:00.0 on minor 1
[    7.277099] nvidia 0000:02:00.0: [drm] No compatible format found
[    7.277101] nvidia 0000:02:00.0: [drm] Cannot find any crtc or sizes

I really have no idea what to make of this, so I turned over to yall more experienced individuals. How concerned should I be? I mean everything is working just fine, but I want to avoid the issues and have a correctly set up installation, in case I might have highly GPU intensive tasks in the future.

I am using Optimus Manager hybrid mode, so that might contribute to the solution?

Feel free to ask me anything please, whatever might help and be useful.

EDIT: Should I post this on a different subforum?

Last edited by marq13 (2024-12-17 11:53:15)

Offline

#2 2024-12-18 21:36:13

xerxes_
Member
Registered: 2018-04-29
Posts: 855

Re: Kernel Log: Warnings for Integrated Intel & Nvidia Graphics

https://bbs.archlinux.org/viewtopic.php … 0#p2197510
Do you have any system or application crashes - see 'coredumpctl' command?
About tainting kernel by nvidia closed module - don't worry, these are just licenses wars between nvidia and kernel developers, unless you are fan of full openness, then you are using wrong distro.

Offline

#3 2024-12-19 10:09:05

marq13
Member
Registered: 2024-10-10
Posts: 17

Re: Kernel Log: Warnings for Integrated Intel & Nvidia Graphics

Hey thanks for reaching out, it is much appreciated.

Not being rude, just asking for clarification to better understand.
How does the thread you linked relate to my issue?
I understand that the person had the same part of dmesg output as mine, but they are working on a different problem right?
I looked at that thread first thing when I was looking for solution, but it looked irrelevant - just a coincidence of a matching dmesg.

xerxes_ wrote:

Do you have any system or application crashes - see 'coredumpctl' command?

Yes I do. Here's the output, I just removed my programs that I coded big_smile

TIME                           PID  UID  GID SIG     COREFILE     EXE                                       SIZE
Thu 2024-10-17 09:58:03 CEST  1995    0    0 SIGSEGV missing      /usr/bin/timeshift-gtk                       -
Thu 2024-10-17 19:42:06 CEST   308    0    0 SIGABRT missing      /usr/lib/systemd/systemd-journald            -
Sun 2024-10-20 17:07:09 CEST   306    0    0 SIGABRT missing      /usr/lib/systemd/systemd-journald            -
Sun 2024-10-20 20:43:07 CEST  2896    0    0 SIGABRT missing      /usr/lib/systemd/systemd-journald            -
Sun 2024-10-20 20:43:07 CEST   588    0    0 SIGABRT missing      /usr/lib/systemd/systemd-logind              -
Mon 2024-10-21 22:27:49 CEST   316    0    0 SIGABRT missing      /usr/lib/systemd/systemd-journald            -
Fri 2024-10-25 09:58:44 CEST   307    0    0 SIGABRT missing      /usr/lib/systemd/systemd-journald            -
Thu 2024-10-31 19:16:22 CET    308    0    0 SIGABRT missing      /usr/lib/systemd/systemd-journald            -
Thu 2024-10-31 23:32:00 CET    308    0    0 SIGABRT missing      /usr/lib/systemd/systemd-journald            -
Mon 2024-11-04 17:48:52 CET    590    0    0 SIGABRT missing      /usr/lib/systemd/systemd-logind              -
Thu 2024-11-14 19:51:27 CET    312    0    0 SIGABRT missing      /usr/lib/systemd/systemd-journald            -
Sun 2024-11-17 16:08:04 CET    307    0    0 SIGABRT missing      /usr/lib/systemd/systemd-journald            -
Sun 2024-11-17 16:08:04 CET    440  979  979 SIGABRT missing      /usr/lib/systemd/systemd-networkd            -
Sun 2024-11-17 16:08:04 CET    408    0    0 SIGABRT missing      /usr/bin/udevadm                             -
Tue 2024-11-19 12:54:34 CET   7697    0    0 SIGSEGV missing      /usr/bin/timeshift-gtk                       -
Thu 2024-11-21 19:09:22 CET    309    0    0 SIGABRT missing      /usr/lib/systemd/systemd-journald            -
Sun 2024-11-24 14:35:06 CET    307    0    0 SIGABRT missing      /usr/lib/systemd/systemd-journald            -
Tue 2024-11-26 00:07:09 CET    307    0    0 SIGABRT missing      /usr/lib/systemd/systemd-journald            -
Thu 2024-11-28 18:24:40 CET    309    0    0 SIGABRT missing      /usr/lib/systemd/systemd-journald            -
Sat 2024-11-30 00:03:57 CET   2580    0    0 SIGABRT missing      /usr/bin/timeshift-gtk                       -
Sun 2024-12-01 17:27:44 CET    309    0    0 SIGABRT missing      /usr/lib/systemd/systemd-journald            -
Tue 2024-12-03 23:59:04 CET    307    0    0 SIGABRT inaccessible /usr/lib/systemd/systemd-journald            -
Thu 2024-12-05 18:11:10 CET    307    0    0 SIGABRT inaccessible /usr/lib/systemd/systemd-journald            -
Mon 2024-12-09 00:22:36 CET    805 1000 1000 SIGSEGV present      /usr/lib/sddm/sddm-helper-start-x11user 234.9K
Wed 2024-12-11 22:58:17 CET    307    0    0 SIGABRT inaccessible /usr/lib/systemd/systemd-journald            -
Mon 2024-12-16 00:07:48 CET   7956 1000 1000 SIGSEGV present      /usr/bin/parsecd                         15.9M
Tue 2024-12-17 13:34:04 CET   7213    0    0 SIGSEGV inaccessible /usr/bin/timeshift-gtk                       -
xerxes_ wrote:

About tainting kernel by nvidia closed module - don't worry, these are just licenses wars between nvidia and kernel developers, unless you are fan of full openness, then you are using wrong distro.

So the dmesg output for nvidia is nothing to worry about? The crtc part?

Thanks again for reaching out.

Offline

#4 2024-12-19 17:54:16

xerxes_
Member
Registered: 2018-04-29
Posts: 855

Re: Kernel Log: Warnings for Integrated Intel & Nvidia Graphics

I linked to concrete post where is question if there is parallel windows installation and if yes then "Disable Windows Fast-Start!".

It is weird that you have so many crashes of systemd-journald. Can you post output of command 'coredumpctl info /usr/lib/systemd/systemd-journald' ?

As for crtc: you can try blacklist i915 in kernel boot parameter, like in this thread: https://bbs.archlinux.org/viewtopic.php?id=279960.

UPDATE:
Also you can try later switcherooctl when you solve your issue: https://bbs.archlinux.org/viewtopic.php?pid=2215424
Nvidia 565.77 driver problems on 6.12 kernels: https://bbs.archlinux.org/viewtopic.php?id=301901

Last edited by xerxes_ (2024-12-19 18:29:44)

Offline

#5 2024-12-19 19:01:07

marq13
Member
Registered: 2024-10-10
Posts: 17

Re: Kernel Log: Warnings for Integrated Intel & Nvidia Graphics

xerxes_ wrote:

I linked to concrete post where is question if there is parallel windows installation and if yes then "Disable Windows Fast-Start!".

Oh okay... I understand. I have only Arch on my machine though. Previously I had a dual boot with Ubuntu and Win10, but I don't think it matters now.

xerxes_ wrote:

It is weird that you have so many crashes of systemd-journald.

Yeah that was super odd to me too.

Here additional output for coredumpctl:

❯ coredumpctl info /usr/lib/systemd/systemd-journald

           PID: 308 (systemd-journal)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Thu 2024-10-17 19:42:06 CEST (2 months 2 days ago)
  Command Line: /usr/lib/systemd/systemd-journald
    Executable: /usr/lib/systemd/systemd-journald
 Control Group: /system.slice/systemd-journald.service
          Unit: systemd-journald.service
         Slice: system.slice
       Boot ID: 9699f5be34f54e7fb541bdf3b43528ae
    Machine ID: b665c883c4a84307870af8003e5f6c1d
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.systemd-journal.0.9699f5be34f54e7fb541bdf3b43528ae.308.1729186926000000.zst (missing)
       Message: Process 308 (systemd-journal) of user 0 dumped core.

           PID: 306 (systemd-journal)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Sun 2024-10-20 17:07:09 CEST (1 month 29 days ago)
  Command Line: /usr/lib/systemd/systemd-journald
    Executable: /usr/lib/systemd/systemd-journald
 Control Group: /system.slice/systemd-journald.service
          Unit: systemd-journald.service
         Slice: system.slice
       Boot ID: 6e0f427872e8435099259dc48def68b6
    Machine ID: b665c883c4a84307870af8003e5f6c1d
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.systemd-journal.0.6e0f427872e8435099259dc48def68b6.306.1729436829000000.zst (missing)
       Message: Process 306 (systemd-journal) of user 0 dumped core.

           PID: 2896 (systemd-journal)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Sun 2024-10-20 20:43:07 CEST (1 month 29 days ago)
  Command Line: /usr/lib/systemd/systemd-journald
    Executable: /usr/lib/systemd/systemd-journald
 Control Group: /system.slice/systemd-journald.service
          Unit: systemd-journald.service
         Slice: system.slice
       Boot ID: 6e0f427872e8435099259dc48def68b6
    Machine ID: b665c883c4a84307870af8003e5f6c1d
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.systemd-journal.0.6e0f427872e8435099259dc48def68b6.2896.1729449787000000.zst (missing)
       Message: Process 2896 (systemd-journal) of user 0 dumped core.

           PID: 316 (systemd-journal)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Mon 2024-10-21 22:27:49 CEST (1 month 28 days ago)
  Command Line: /usr/lib/systemd/systemd-journald
    Executable: /usr/lib/systemd/systemd-journald
 Control Group: /system.slice/systemd-journald.service
          Unit: systemd-journald.service
         Slice: system.slice
       Boot ID: 446bf13345314b6eaedce1caf428a35c
    Machine ID: b665c883c4a84307870af8003e5f6c1d
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.systemd-journal.0.446bf13345314b6eaedce1caf428a35c.316.1729542469000000.zst (missing)
       Message: Process 316 (systemd-journal) of user 0 dumped core.

           PID: 307 (systemd-journal)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Fri 2024-10-25 09:58:44 CEST (1 month 25 days ago)
  Command Line: /usr/lib/systemd/systemd-journald
    Executable: /usr/lib/systemd/systemd-journald
 Control Group: /system.slice/systemd-journald.service
          Unit: systemd-journald.service
         Slice: system.slice
       Boot ID: fc6382aa11894e49844270a007e8e78e
    Machine ID: b665c883c4a84307870af8003e5f6c1d
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.systemd-journal.0.fc6382aa11894e49844270a007e8e78e.307.1729843124000000.zst (missing)
       Message: Process 307 (systemd-journal) of user 0 dumped core.

           PID: 308 (systemd-journal)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Thu 2024-10-31 19:16:22 CET (1 month 18 days ago)
  Command Line: /usr/lib/systemd/systemd-journald
    Executable: /usr/lib/systemd/systemd-journald
 Control Group: /system.slice/systemd-journald.service
          Unit: systemd-journald.service
         Slice: system.slice
       Boot ID: deef7e5014b240f3af210a1403f00d98
    Machine ID: b665c883c4a84307870af8003e5f6c1d
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.systemd-journal.0.deef7e5014b240f3af210a1403f00d98.308.1730398582000000.zst (missing)
       Message: Process 308 (systemd-journal) of user 0 dumped core.

           PID: 308 (systemd-journal)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Thu 2024-10-31 23:32:00 CET (1 month 18 days ago)
  Command Line: /usr/lib/systemd/systemd-journald
    Executable: /usr/lib/systemd/systemd-journald
 Control Group: /system.slice/systemd-journald.service
          Unit: systemd-journald.service
         Slice: system.slice
       Boot ID: 86f63454566f45c0b3b2d126c504f0ee
    Machine ID: b665c883c4a84307870af8003e5f6c1d
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.systemd-journal.0.86f63454566f45c0b3b2d126c504f0ee.308.1730413920000000.zst (missing)
       Message: Process 308 (systemd-journal) of user 0 dumped core.

           PID: 312 (systemd-journal)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Thu 2024-11-14 19:51:27 CET (1 month 4 days ago)
  Command Line: /usr/lib/systemd/systemd-journald
    Executable: /usr/lib/systemd/systemd-journald
 Control Group: /system.slice/systemd-journald.service
          Unit: systemd-journald.service
         Slice: system.slice
       Boot ID: 9fc88b2aa8504a38bc72c1c0cd780903
    Machine ID: b665c883c4a84307870af8003e5f6c1d
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.systemd-journal.0.9fc88b2aa8504a38bc72c1c0cd780903.312.1731610287000000.zst (missing)
       Message: Process 312 (systemd-journal) of user 0 dumped core.

           PID: 307 (systemd-journal)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Sun 2024-11-17 16:08:04 CET (1 month 1 day ago)
  Command Line: /usr/lib/systemd/systemd-journald
    Executable: /usr/lib/systemd/systemd-journald
 Control Group: /system.slice/systemd-journald.service
          Unit: systemd-journald.service
         Slice: system.slice
       Boot ID: ff0eb8a2850544bf984e9475b2bb0803
    Machine ID: b665c883c4a84307870af8003e5f6c1d
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.systemd-journal.0.ff0eb8a2850544bf984e9475b2bb0803.307.1731856084000000.zst (missing)
       Message: Process 307 (systemd-journal) of user 0 dumped core.

           PID: 309 (systemd-journal)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Thu 2024-11-21 19:09:22 CET (4 weeks 0 days ago)
  Command Line: /usr/lib/systemd/systemd-journald
    Executable: /usr/lib/systemd/systemd-journald
 Control Group: /system.slice/systemd-journald.service
          Unit: systemd-journald.service
         Slice: system.slice
       Boot ID: cfdfee36217749a182ca6daba5721c2a
    Machine ID: b665c883c4a84307870af8003e5f6c1d
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.systemd-journal.0.cfdfee36217749a182ca6daba5721c2a.309.1732212562000000.zst (missing)
       Message: Process 309 (systemd-journal) of user 0 dumped core.

           PID: 307 (systemd-journal)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Sun 2024-11-24 14:35:06 CET (3 weeks 4 days ago)
  Command Line: /usr/lib/systemd/systemd-journald
    Executable: /usr/lib/systemd/systemd-journald
 Control Group: /system.slice/systemd-journald.service
          Unit: systemd-journald.service
         Slice: system.slice
       Boot ID: e7b0ec532485445fbc8cafd35c8bdc52
    Machine ID: b665c883c4a84307870af8003e5f6c1d
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.systemd-journal.0.e7b0ec532485445fbc8cafd35c8bdc52.307.1732455306000000.zst (missing)
       Message: Process 307 (systemd-journal) of user 0 dumped core.

           PID: 307 (systemd-journal)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Tue 2024-11-26 00:07:09 CET (3 weeks 2 days ago)
  Command Line: /usr/lib/systemd/systemd-journald
    Executable: /usr/lib/systemd/systemd-journald
 Control Group: /system.slice/systemd-journald.service
          Unit: systemd-journald.service
         Slice: system.slice
       Boot ID: aad95640b9fe4a7aa35e9320135941e3
    Machine ID: b665c883c4a84307870af8003e5f6c1d
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.systemd-journal.0.aad95640b9fe4a7aa35e9320135941e3.307.1732576029000000.zst (missing)
       Message: Process 307 (systemd-journal) of user 0 dumped core.

           PID: 309 (systemd-journal)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Thu 2024-11-28 18:24:40 CET (3 weeks 0 days ago)
  Command Line: /usr/lib/systemd/systemd-journald
    Executable: /usr/lib/systemd/systemd-journald
 Control Group: /system.slice/systemd-journald.service
          Unit: systemd-journald.service
         Slice: system.slice
       Boot ID: eb4c470671bd4544a3d994fdaf6a7272
    Machine ID: b665c883c4a84307870af8003e5f6c1d
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.systemd-journal.0.eb4c470671bd4544a3d994fdaf6a7272.309.1732814680000000.zst (missing)
       Message: Process 309 (systemd-journal) of user 0 dumped core.

           PID: 309 (systemd-journal)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Sun 2024-12-01 17:27:43 CET (2 weeks 4 days ago)
  Command Line: /usr/lib/systemd/systemd-journald
    Executable: /usr/lib/systemd/systemd-journald
 Control Group: /system.slice/systemd-journald.service
          Unit: systemd-journald.service
         Slice: system.slice
       Boot ID: 75174367e070477293e46fcee8fd817e
    Machine ID: b665c883c4a84307870af8003e5f6c1d
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.systemd-journal.0.75174367e070477293e46fcee8fd817e.309.1733070463000000.zst (missing)
       Message: Process 309 (systemd-journal) of user 0 dumped core.

           PID: 307 (systemd-journal)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Tue 2024-12-03 23:59:04 CET (2 weeks 1 day ago)
  Command Line: /usr/lib/systemd/systemd-journald
    Executable: /usr/lib/systemd/systemd-journald
 Control Group: /system.slice/systemd-journald.service
          Unit: systemd-journald.service
         Slice: system.slice
       Boot ID: 92c7e9eaa9c542bcbbd5960958749321
    Machine ID: b665c883c4a84307870af8003e5f6c1d
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.systemd-journal.0.92c7e9eaa9c542bcbbd5960958749321.307.1733266744000000.zst (inaccessible)
       Message: Process 307 (systemd-journal) of user 0 dumped core.

           PID: 307 (systemd-journal)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Thu 2024-12-05 18:11:10 CET (2 weeks 0 days ago)
  Command Line: /usr/lib/systemd/systemd-journald
    Executable: /usr/lib/systemd/systemd-journald
 Control Group: /system.slice/systemd-journald.service
          Unit: systemd-journald.service
         Slice: system.slice
       Boot ID: d2a0ddac22d74148bc3e4ed9ec25ee73
    Machine ID: b665c883c4a84307870af8003e5f6c1d
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.systemd-journal.0.d2a0ddac22d74148bc3e4ed9ec25ee73.307.1733418670000000.zst (inaccessible)
       Message: Process 307 (systemd-journal) of user 0 dumped core.

           PID: 307 (systemd-journal)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Wed 2024-12-11 22:58:17 CET (1 week 0 days ago)
  Command Line: /usr/lib/systemd/systemd-journald
    Executable: /usr/lib/systemd/systemd-journald
 Control Group: /system.slice/systemd-journald.service
          Unit: systemd-journald.service
         Slice: system.slice
       Boot ID: ce16261266574e43b0276bc4fd3ec4a2
    Machine ID: b665c883c4a84307870af8003e5f6c1d
      Hostname: archlinux
       Storage: /var/lib/systemd/coredump/core.systemd-journal.0.ce16261266574e43b0276bc4fd3ec4a2.307.1733954297000000.zst (inaccessible)
       Message: Process 307 (systemd-journal) of user 0 dumped core.

Maybe look at the .zst archives?

xerxes_ wrote:

As for crtc: you can try blacklist i915 in kernel boot parameter.

I don't think I would be wanting to do that because of my hybrid setup. My integrated graphics is using the i915 kernel driver.

❯ lspci -v

00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) (prog-if 00 [VGA controller])
	Subsystem: Lenovo Device 3a5b
	Flags: bus master, fast devsel, latency 0, IRQ 141
	Memory at 6102000000 (64-bit, non-prefetchable) [size=16M]
	Memory at 4000000000 (64-bit, prefetchable) [size=256M]
	I/O ports at 5000 [size=64]
	Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: i915
	Kernel modules: i915, xe

optimus-manager --status:

❯ optimus-manager --status

Optimus Manager (Client) version 1.5

Current GPU mode : hybrid
GPU mode requested for next login : no change
GPU at startup : nvidia

Note : the startup mode for the current boot was set to "hybrid" with a kernel parameter. Kernel parameters override the value above.

Temporary config path: no

Here's my systemd-boot entry configuration too:

❯ cat /boot/loader/entries/arch.conf

title Arch-Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=PARTUUID=a315f42f-555e-4a11-8c39-54f5576b3d76 rw nvidia-drm.modeset=1 optimus-manager.startup=hybrid

Hope you don't mind me sending you more things, I'm just trying to help you understand my setup better.

Last edited by marq13 (2024-12-19 19:11:17)

Offline

#6 2024-12-19 19:15:06

marq13
Member
Registered: 2024-10-10
Posts: 17

Re: Kernel Log: Warnings for Integrated Intel & Nvidia Graphics

xerxes_ wrote:

Also you can try later switcherooctl when you solve your issue: https://bbs.archlinux.org/viewtopic.php?pid=2215424

Will do. Is it some new tech? Are you using it without problems etc?

xerxes_ wrote:

Nvidia 565.77 driver problems on 6.12 kernels: https://bbs.archlinux.org/viewtopic.php?id=301901

I see. Thanks for the heads up!

Offline

#7 2024-12-19 19:48:31

seth
Member
Registered: 2012-09-03
Posts: 60,896

Re: Kernel Log: Warnings for Integrated Intel & Nvidia Graphics

Don#t blacklist i9415 if there's no crtc on the nvidia chip - you'll end up w/o any display.

You just want to know about the messages, there's no specific functional problem?
nvidia says: this is a proprietary driver and the kernel has mixed feeligns about that and also there's not monitor attached to it.

The intel warning is recorded at https://gitlab.freedesktop.org/drm/i915 … sues/10679 and https://github.com/torvalds/linux/blob/ … _tc.c#L740 looks power related.
The full context might be helpful (ie. the entire journal of the boot)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#8 2024-12-19 21:33:59

marq13
Member
Registered: 2024-10-10
Posts: 17

Re: Kernel Log: Warnings for Integrated Intel & Nvidia Graphics

Hey seth, thanks for reaching out! It is much appreciated.

seth wrote:

You just want to know about the messages, there's no specific functional problem?

Yes and no. Everything is working smoothly display wise, except for rare black screen after sleep or at sddm login which I workaround by switching to tty1 and back to tty2. It doesn't really bother me.
However I am/was concerned if I set up my "graphics" correctly, so that if I may have some high GPU intensive tasks in the future, everything works great. (I guess I could just test it myself.)
I've been on this setup for 3 months without any breaking issues, but with recent discoveries I didn't know what to make of this and if I really set everything as intended.

Like I said, I believe I got the intel warning after timeshifting once, so that is where my concern originates. + After digging further and finding out the nvidia warning I wanted to consult with more experienced people.

But it appears that it is nothing to be worried about?

seth wrote:

Nice catch. Thanks for linking these.

seth wrote:

The full context might be helpful (ie. the entire journal of the boot)

Here you go: journalctl -b
This is the journal from fresh boot and I filtered a bit of the output for privacy reasons, but I don't think it makes a difference. If you really need it I will post it.

The only interesting thing that I can see starts at the line 1628. Could it be that rootless Xorg is not working as intended with optimus-manager?
And also the super long 1502 line that I don't know what to make of lol.

Let me know what y'all think.

Last edited by marq13 (2024-12-19 21:36:27)

Offline

#9 2024-12-19 23:10:12

seth
Member
Registered: 2012-09-03
Posts: 60,896

Re: Kernel Log: Warnings for Integrated Intel & Nvidia Graphics

Dec 19 21:32:58 archlinux sddm-helper-start-x11user[709]: "[24] ERROR: Xorg pre-start setup error\nTraceback (most recent call last):\n  File \"/usr/lib/python3.12/site-packages/optimus_manager/xorg.py\", line 367, in _write_xorg_conf\n    with open(filepath, 'w') as f:\n         ^^^^^^^^^^^^^^^^^^^\nPermissionError: [Errno 13] Permission denied: '/etc/X11/xorg.conf.d/10-optimus-manager.conf'\n\nThe above exception was the direct cause of the following exception:\n\nTraceback (most recent call last):\n  File \"/usr/lib/python3.12/site-packages/optimus_manager/hooks/pre_xorg_start.py\", line 52, in main\n    configure_xorg(config, requested_mode)\n  File \"/usr/lib/python3.12/site-packages/optimus_manager/xorg.py\", line 29, in configure_xorg\n    _write_xorg_conf(xorg_conf_text)\n  File \"/usr/lib/python3.12/site-packages/optimus_manager/xorg.py\", line 371, in _write_xorg_conf\n    raise XorgSetupError(\"Cannot write Xorg conf at %s\" % str(filepath)) from e\noptimus_manager.xorg.XorgSetupError: Cannot write Xorg conf at /etc/X11/xorg.conf.d/10-optimus-manager.conf\n"
Dec 19 21:32:58 archlinux sddm-helper-start-x11user[709]: "[25] INFO: Removing /etc/X11/xorg.conf.d/10-optimus-manager.conf (if present)\n"
Dec 19 21:32:58 archlinux sddm-helper-start-x11user[709]: "Traceback (most recent call last):\n"
Dec 19 21:32:58 archlinux sddm-helper-start-x11user[709]: "  File \"/usr/lib/python3.12/site-packages/optimus_manager/xorg.py\", line 367, in _write_xorg_conf\n"
Dec 19 21:32:58 archlinux sddm-helper-start-x11user[709]: "    with open(filepath, 'w') as f:\n"
Dec 19 21:32:58 archlinux sddm-helper-start-x11user[709]: "         ^^^^^^^^^^^^^^^^^^^\n"

Get rid of optimus manager entirely.
Your Ampere chip is eligible for https://wiki.archlinux.org/title/PRIME# … Management and 

Dec 19 21:32:53 archlinux kernel: nvidia 0000:02:00.0: [drm] Cannot find any crtc or sizes

there're no outputs attached to the nvidia GPU anyway, so you want to run this in hybrid mode (the default prime setup) anyway and "prime-run" games.

Please afterwards post your Xorg log, https://wiki.archlinux.org/title/Xorg#General and whether this has any impact on the "rare black screen after sleep"

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#10 2024-12-20 10:08:55

marq13
Member
Registered: 2024-10-10
Posts: 17

Re: Kernel Log: Warnings for Integrated Intel & Nvidia Graphics

You think optimus manager was a bad choice?

Sure I will switch to PRIME as I see that most people use it, and because it is the official method by NVIDIA. But could we first discuss what do you think of switcherooctl that xerxes_ linked?

Also to confirm, you want me to send you the Xorg log after switching to PRIME or?

EDIT: I didn't know the default setting for PRIME is hybrid, I thought it is only integrated GPU then you just run whichever apps you want on discrete with prime-run.

Last edited by marq13 (2024-12-20 10:14:52)

Offline

#11 2024-12-20 15:17:37

seth
Member
Registered: 2012-09-03
Posts: 60,896

Re: Kernel Log: Warnings for Integrated Intel & Nvidia Graphics

I thought it is only integrated GPU then you just run whichever apps you want on discrete with prime-run.

That *is* the "hybrid" setting wrt optimus manager.
prime-run is a simple script that just steers the environment into running on the nvidia GPU.

Anything else is completely pointless:
You cannot run on "nvidia only" because you need the IGP as VGA hub as the nvidia GPU hasn't any outputs attached.
You could run on "intel only" but that's equivalent to running w/o invoking prime-run (as the GPU will power down when not used)

There isn't, with absolutely no approach, any kind of magic that figures "oh, I should run this process on the GPU. Oh, that process can be left to the IGP"
Afaiu steam will look for and default to the GPU, but that's a selection explicitly programmed into steam - for the most part *you* will have to select what to run stuff on.

switcheroo is gnome-specific bumblebee whic itself was superseded by prime.

Also to confirm, you want me to send you the Xorg log after switching to PRIME or?

Yes.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#12 2024-12-20 22:03:00

marq13
Member
Registered: 2024-10-10
Posts: 17

Re: Kernel Log: Warnings for Integrated Intel & Nvidia Graphics

Thank you for the clear explanation; it really clarified the topic.

How difficult is it to set up PRIME?
I won’t have the time this weekend, but I plan to dedicate time next week to set everything up.
Is it okay if we wait until then? I’ll share the Xorg log with you once I’m done.

Offline

#13 2024-12-20 22:07:18

seth
Member
Registered: 2012-09-03
Posts: 60,896

Re: Kernel Log: Warnings for Integrated Intel & Nvidia Graphics

"Not" - it's the out of the box solution.
Make sure to remove optimus-manager and residual configs and post your xorg log and report on remaining issues w/ the setup.
Also your problem so your solution runs at your pace.
So Merry Fucking Christmas wink

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#14 2024-12-21 08:59:43

marq13
Member
Registered: 2024-10-10
Posts: 17

Re: Kernel Log: Warnings for Integrated Intel & Nvidia Graphics

Alrighty, will do as you say!

I like the holiday spirit loll cool

Offline

Pages: 1

Board footer

Powered by FluxBB