I915 drm error - Исправление ошибок и поиск оптимальных решений проблем

#1 2021-10-10 13:23:08

itarill: Member; Registered: 2020-06-03; Posts: 30

[solved] boot stuck: i915 drm error

So I set up btrfs in my new arch install on my old laptop. I made an error with some packages and decided to try booting my snapshot before that error in GRUB. My issue is that GRUB is stuck at this step (on LTS kernel):

Bluetooth: hci0: unexpected event for opcode 0xfc2f

On linux kernel it goes one step further:

i915 0000:00:02.0: [drm] *ERROR* Failed to write source OUI.

Now I have absolutely no clue based on my google searches to find how to solve this.

Last edited by itarill (2021-10-13 18:36:13)

#3 2021-10-10 20:50:43

itarill: Member; Registered: 2020-06-03; Posts: 30

Re: [solved] boot stuck: i915 drm error

Thanks for responding
With the nomodeset the boot hands at the Bluetooth message above. With regards to multi-user.target, I cannot edit the snapshots so I don’t really know how I would get about adjusting that…?

#4 2021-10-10 20:51:53

seth: Member; Registered: 2012-09-03; Posts: 35,310

Re: [solved] boot stuck: i915 drm error

the wiki wrote:

…
Alternatively, append one of the following kernel parameters to your bootloader:
systemd.unit=multi-user.target (which roughly corresponds to the old runlevel 3),…

#5 2021-10-10 21:15:55

itarill: Member; Registered: 2020-06-03; Posts: 30

Re: [solved] boot stuck: i915 drm error

seth wrote:

the wiki wrote:

…
Alternatively, append one of the following kernel parameters to your bootloader:
systemd.unit=multi-user.target (which roughly corresponds to the old runlevel 3),…

Thanks — I am kinda new with this.
So with multi-user.target I reach tty and I can login.

gives a single error on top a bunch of interrupts:

platform regulatory.0: Direct firmware load for regulatory.db failed with error -2

Not sure how to continue. But I guess the problem that hinders booting comes after multi-user.target so there was no point checking this anyway.

Last edited by itarill (2021-10-10 21:23:57)

#6 2021-10-11 07:16:17

seth: Member; Registered: 2012-09-03; Posts: 35,310

Re: [solved] boot stuck: i915 drm error

platform regulatory.0: Direct firmware load for regulatory.db failed with error -2

is irrelevant.
The system boots, but you GUI target doesn’t start (properly)

=> what is your graphical target? (some DM, startx/xinit, some wayland session …)
Do you have xf86-video-intel installed? Try to remove it.

#7 2021-10-11 08:12:22

itarill: Member; Registered: 2020-06-03; Posts: 30

Re: [solved] boot stuck: i915 drm error

seth wrote:

platform regulatory.0: Direct firmware load for regulatory.db failed with error -2

is irrelevant.
The system boots, but you GUI target doesn’t start (properly)

=> what is your graphical target? (some DM, startx/xinit, some wayland session …)
Do you have xf86-video-intel installed? Try to remove it.

Right. So my boot messages in order:

Reached target Multi-User System
Started SDDM
Reached target Graphical Interface
i915 drm error
Started Hostname Service
Bluetooth hci unexpected event
915 drm error

I do have xf86-video-intel, I tried removing it as well. In my bios I have the option to disable the nVidia GPU or go with intel, I have tried both settings. I also installed nvidia and nvidia-utils. These yielded no change.

Last edited by itarill (2021-10-11 08:12:43)

#8 2021-10-11 08:19:40

seth: Member; Registered: 2012-09-03; Posts: 35,310

Re: [solved] boot stuck: i915 drm error

Please post a complete system journal covering a failed SDDM start («sudo journalctl -b» for the current one) and your xorg log, https://wiki.archlinux.org/title/Xorg#General

#9 2021-10-11 21:08:34

itarill: Member; Registered: 2020-06-03; Posts: 30

Re: [solved] boot stuck: i915 drm error

Journalctl
Xorg
Xorg.old

Thanks. As an afterthought, you probably need the Xorg.old for troubleshooting.

Last edited by itarill (2021-10-11 21:11:56)

#10 2021-10-11 21:18:38

seth: Member; Registered: 2012-09-03; Posts: 35,310

Re: [solved] boot stuck: i915 drm error

This is a running X11 server and the journal shows SDDM starting and you logging into a plasma session ~10 seconds later?
Also there’s no i915 error and the nvidia chip isn’t utilized at all.

Is this supposed to cover a failing boot/sddm start?

Edit: the old xorg log runs successfully for 2 seconds, whatever starts there (SDDM?) must have insta-crashed.

Last edited by seth (2021-10-11 21:20:44)

#11 2021-10-11 21:38:03

itarill: Member; Registered: 2020-06-03; Posts: 30

Re: [solved] boot stuck: i915 drm error

Should I try switching to another DM?

Sorry, I may have misunderstood previously. This is the journal for the crashed boot attempt:
journal-1

Last edited by itarill (2021-10-11 21:46:10)

#12 2021-10-12 06:42:52

V1del: Forum Moderator; Registered: 2012-10-16; Posts: 18,300

Re: [solved] boot stuck: i915 drm error

No failure there either. Which exact journal command are you invoking? FWIW if you know the date of when the failure happened you can also pass a date and time range to journalctl: https://wiki.archlinux.org/title/System … ing_output

There’s also a chance that the fact you are booting a snapshot confuses journalctl

#13 2021-10-12 06:57:07

seth: Member; Registered: 2012-09-03; Posts: 35,310

Re: [solved] boot stuck: i915 drm error

Oct 11 22:57:44 balu-lenovo systemd-logind[308]: New session c1 of user sddm.
…
Oct 11 22:57:53 balu-lenovo systemd-logind[308]: New session 2 of user balu.

The journal again shows you logging in as «balu» ~10 seconds after SDDM starts.
What happens then is that the sesion runs for ~25 minutes until

Oct 11 23:24:13 balu-lenovo systemd-logind[308]: System is rebooting.

Then plasma does its crash-on-shutdown thing and the journal stops at

Oct 11 23:25:44 balu-lenovo systemd[1]: Reached target System Reboot.
Oct 11 23:25:44 balu-lenovo systemd[1]: Shutting down.
Oct 11 23:25:44 balu-lenovo audit: BPF prog-id=16 op=UNLOAD
Oct 11 23:25:44 balu-lenovo audit: BPF prog-id=15 op=UNLOAD
Oct 11 23:25:44 balu-lenovo audit: BPF prog-id=14 op=UNLOAD
Oct 11 23:25:44 balu-lenovo audit: BPF prog-id=13 op=UNLOAD
Oct 11 23:25:44 balu-lenovo audit: BPF prog-id=12 op=UNLOAD
Oct 11 23:25:44 balu-lenovo audit: BPF prog-id=11 op=UNLOAD
Oct 11 23:25:44 balu-lenovo systemd[1]: Using hardware watchdog 'iTCO_wdt', version 0, device /dev/watchdog
Oct 11 23:25:44 balu-lenovo systemd[1]: Set hardware watchdog to 10min.
Oct 11 23:25:44 balu-lenovo kernel: watchdog: watchdog0: watchdog did not stop!
Oct 11 23:25:44 balu-lenovo systemd-shutdown[1]: Syncing filesystems and block devices.
Oct 11 23:25:44 balu-lenovo systemd-journald[212]: Journal stopped

There was an interactive konsole window and you used it to

Oct 11 22:58:05 balu-lenovo sudo[833]:     balu : TTY=pts/1 ; PWD=/home/balu ; USER=root ; COMMAND=/usr/bin/journalctl -b

There’re again no i915 errors and no indicators of the system failing to boot whatsoever?
Are you somehow switching snapshots between «System doesn’t boot» and «I get the journal»? (the journal shows the current LTS kernel booting…)

#14 2021-10-12 08:06:24

itarill: Member; Registered: 2020-06-03; Posts: 30

Re: [solved] boot stuck: i915 drm error

I’m starting to feel really dumb. This is the snapshot journal, 3rd time’s the charm: https://pastebin.com/z25tR2Ys

Previously, not realizing I have access to tty on a stuck boot I tried snapshot boot -> regular boot -> journal -1 , but I guess it does not work like that.

#15 2021-10-12 09:10:36

seth: Member; Registered: 2012-09-03; Posts: 35,310

Re: [solved] boot stuck: i915 drm error

Oct 12 09:56:26 balu-lenovo sddm[368]: Display server starting...
Oct 12 09:56:26 balu-lenovo sddm[368]: Adding cookie to "/var/run/sddm/{855e0bf9-c9db-4dca-b600-57205bfc6183}"
Oct 12 09:56:26 balu-lenovo sddm[368]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{855e0bf9-c9db-4dca-b600-57205bfc6183} -noreset -displayfd 17
Oct 12 09:56:26 balu-lenovo sddm[368]: Failed to read display number from pipe
Oct 12 09:56:26 balu-lenovo sddm[368]: Display server stopping...
Oct 12 09:56:26 balu-lenovo sddm[368]: Attempt 3 starting the Display server on vt 1 failed
Oct 12 09:56:26 balu-lenovo sddm[368]: Could not start Display server on vt 1

Better
Now we’ll need an xorg log from that run.

One thnig right off the bat is that your crng is late, check https://wiki.archlinux.org/title/Haveged

#16 2021-10-12 21:22:10

itarill: Member; Registered: 2020-06-03; Posts: 30

Re: [solved] boot stuck: i915 drm error

seth wrote:

Oct 12 09:56:26 balu-lenovo sddm[368]: Display server starting...
Oct 12 09:56:26 balu-lenovo sddm[368]: Adding cookie to "/var/run/sddm/{855e0bf9-c9db-4dca-b600-57205bfc6183}"
Oct 12 09:56:26 balu-lenovo sddm[368]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{855e0bf9-c9db-4dca-b600-57205bfc6183} -noreset -displayfd 17
Oct 12 09:56:26 balu-lenovo sddm[368]: Failed to read display number from pipe
Oct 12 09:56:26 balu-lenovo sddm[368]: Display server stopping...
Oct 12 09:56:26 balu-lenovo sddm[368]: Attempt 3 starting the Display server on vt 1 failed
Oct 12 09:56:26 balu-lenovo sddm[368]: Could not start Display server on vt 1
Better
Now we’ll need an xorg log from that run.

One thnig right off the bat is that your crng is late, check https://wiki.archlinux.org/title/Haveged

I need to dive deeper in the Haveged topic. In the meanwhile, I checked the /var/log/Xorg.0.log file while booting the snapshot, and the last mod date as well as the log file time is from this morning from the successful boot before the snapshot was taken (I guess), meaning that it does not get overwritten on booting the snapshot. Can I get around this somehow?

#17 2021-10-12 21:25:36

seth: Member; Registered: 2012-09-03; Posts: 35,310

Re: [solved] boot stuck: i915 drm error

Boot the multi-user.target and try to run «Xorg» instead of SDDM.
If the X11 server doesn’t even make it to writing a log, there’s probably some unresolvable library or something — trying to start the display server process directly will hopefully reveal that.

#18 2021-10-12 22:28:11

itarill: Member; Registered: 2020-06-03; Posts: 30

Re: [solved] boot stuck: i915 drm error

I feel ashamed having other people running around in circles for me
Having no experience with snapshots I did not realize that it is the read only property that prevented my boot to X. Changing that, I can now boot a snapshot. I cannot say for certain if this is an intended feature (ro images unbootable to X), or it is still a bug in my system.

#19 2021-10-13 06:03:09

seth: Member; Registered: 2012-09-03; Posts: 35,310

Re: [solved] boot stuck: i915 drm error

Snapshots should™ only be readoly if you created them passing «-r»

Please always remember to mark resolved threads by editing your initial posts subject — so others will know that there’s no task left, but maybe a solution to find.
Thanks.

Источник

I have been seeing this error ever since I last updated my system packages. I see the following error message every time during boot:

[   11.504795] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request.
[   11.509800] ------------[ cut here ]------------
[   11.509801] i915 0000:00:02.0: Unclaimed read from register 0x235c
[   11.509850] WARNING: CPU: 4 PID: 494 at drivers/gpu/drm/i915/intel_uncore.c:1182 __unclaimed_reg_debug+0x77/0x90 [i915]
[   11.509851] Modules linked in: bnep joydev mousedev intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp kvm_intel iwldvm kvm mac80211 irqbypass snd_hda_codec_hdmi crct10dif_pclmul libarc4 crc32_pclmul snd_hda_codec_conexant ghash_clmulni_intel snd_hda_codec_generic nls_iso8859_1 mei_wdt mei_hdcp iwlwifi aesni_intel nls_cp437 iTCO_wdt btusb snd_hda_intel btrtl crypto_simd vfat btbcm cryptd fat snd_intel_dspcfg btintel glue_helper intel_pmc_bxt wmi_bmof rapl at24 iTCO_vendor_support intel_cstate snd_hda_codec bluetooth snd_hda_core thinkpad_acpi psmouse ecdh_generic snd_hwdep intel_uncore cfg80211 ecc nvram input_leds snd_pcm mei_me pcspkr ledtrig_audio e1000e lpc_ich i2c_i801 tpm_tis tpm_tis_core i2c_smbus snd_timer rfkill mei tpm snd wmi soundcore rng_core evdev battery ac mac_hid usbip_host usbip_core coretemp msr pkcs8_key_parser sg crypto_user ip_tables x_tables ext4 sdhci_pci cqhci serio_raw atkbd sdhci crc32c_generic libps2 crc16 ehci_pci mbcache i8042 jbd2
[   11.509872]  crc32c_intel mmc_core ehci_hcd serio i915 intel_gtt i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core drm agpgart
[   11.509878] CPU: 4 PID: 494 Comm: Xorg Tainted: G        W I       5.8.5-arch1-1 #1
[   11.509878] Hardware name: LENOVO 4236B87/4236B87, BIOS 83ET79WW (1.49 ) 09/05/2016
[   11.509899] RIP: 0010:__unclaimed_reg_debug+0x77/0x90 [i915]
[   11.509900] Code: 48 8b 78 18 4c 8b 77 50 4d 85 f6 74 30 e8 f1 7e 58 ef 45 89 e0 4c 89 e9 4c 89 f2 48 89 c6 48 c7 c7 40 7e 49 c0 e8 8f b1 f5 ee <0f> 0b 83 2d a0 64 21 00 01 5b 5d 41 5c 41 5d 41 5e c3 c3 4c 8b 37
[   11.509901] RSP: 0018:ffffb6198089fd28 EFLAGS: 00010082
[   11.509902] RAX: 0000000000000000 RBX: ffff965446d107e0 RCX: 0000000000000000
[   11.509902] RDX: 0000000000000003 RSI: ffffffffb056ac7f RDI: 00000000ffffffff
[   11.509903] RBP: 0000000000000000 R08: 0000000000000521 R09: 0000000000000004
[   11.509903] R10: 0000000000000000 R11: 0000000000000001 R12: 000000000000235c
[   11.509904] R13: ffffffffc04c00ef R14: ffff96544b06df90 R15: ffff965446d107f8
[   11.509905] FS:  00007fc0db350540(0000) GS:ffff96544e300000(0000) knlGS:0000000000000000
[   11.509906] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   11.509906] CR2: 00007fc0da07d070 CR3: 00000003ef1aa006 CR4: 00000000000606e0
[   11.509907] Call Trace:
[   11.509931]  gen6_read32+0x1da/0x1f0 [i915]
[   11.509952]  i915_reg_read_ioctl+0xc0/0x130 [i915]
[   11.509968]  ? drm_gem_handle_delete+0x73/0x90 [drm]
[   11.509988]  ? intel_uncore_fini_mmio+0xa0/0xa0 [i915]
[   11.509998]  drm_ioctl_kernel+0xb2/0x100 [drm]
[   11.510008]  drm_ioctl+0x208/0x360 [drm]
[   11.510029]  ? intel_uncore_fini_mmio+0xa0/0xa0 [i915]
[   11.510033]  ksys_ioctl+0x82/0xc0
[   11.510035]  __x64_sys_ioctl+0x16/0x20
[   11.510038]  do_syscall_64+0x44/0x70
[   11.510040]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   11.510042] RIP: 0033:0x7fc0dbd08f6b
[   11.510043] Code: 89 d8 49 8d 3c 1c 48 f7 d8 49 39 c4 72 b5 e8 1c ff ff ff 85 c0 78 ba 4c 89 e0 5b 5d 41 5c c3 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 ae 0c 00 f7 d8 64 89 01 48
[   11.510044] RSP: 002b:00007ffeffa77968 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[   11.510045] RAX: ffffffffffffffda RBX: 00007ffeffa77a10 RCX: 00007fc0dbd08f6b
[   11.510045] RDX: 00007ffeffa77a10 RSI: 00000000c0106471 RDI: 000000000000000f
[   11.510046] RBP: 00000000c0106471 R08: 0000000000000000 R09: 000055bf48dc6010
[   11.510046] R10: 00007ffeffb17080 R11: 0000000000000246 R12: 0000000000000000
[   11.510047] R13: 000000000000000f R14: 000055bf48e23b00 R15: 0000000000000003
[   11.510049] ---[ end trace cc066b47ea04e946 ]---

The system still kind of works but the rendering performance seems reduced and noticeably sluggish. There are some more

[drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request.

messages (but without the backtrace) popping up in dmesg. This is on Arch Linux with

- kernel 5.8.5
- mesa 20.1.6
- libdrm 2.4.102

Источник

Печать

Страницы: [1] Вниз

Тема: drm:intel_dp_start_link_train [i915]] ERROR failed to get link status (Прочитано 747 раз)

0 Пользователей и 1 Гость просматривают эту тему.

perlamut

Ubuntu 16.04 64
Всем здравствуйте, с недавних пор прри загрузке и при выключении системы, на черном фоне вылазит текст с какой то ошибкой. вроде как ничего страшного но я уже 2 раза реинсталил систему так как слетала загрузка и не грузилось даже в рекавери, то есть выбор рекавери делаю в загрузчике, а после этого идет загрузка и зависание на определенном этапе. первый раз поставил пакет, вернее удалил, второй раз оно зависло само по себе, снова реинстальнулся. в общем суть в том что щас поставил ось, настроил, и сттараюсь не трогать, пусть работает пока может. Погуглив что за ошибка вылезла, ничего толком найти не смог. Взял лог отсюда, /var/log/kern.log
в никсах не силен, помогите выявить что это и как убрать

Dec 26 18:59:34 LUTER kernel: [ 3.891535] aufs 4.15-20180219 Dec 26 18:59:34 LUTER kernel: [ 3.984118] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 4.573004] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 4.686036] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 4.688293] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 4.797637] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 4.799895] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 4.930554] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 4.932827] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 5.207544] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 5.209801] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 5.299408] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 5.301677] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 5.430592] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 5.432859] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 5.705939] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 5.708228] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 5.799419] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 5.801696] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 5.930739] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 5.932995] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 5.955602] random: crng init done Dec 26 18:59:34 LUTER kernel: [ 5.955602] random: 7 urandom warning(s) missed due to ratelimiting Dec 26 18:59:34 LUTER kernel: [ 6.207060] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 6.209334] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 6.299682] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 6.301950] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 6.430497] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 6.432901] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 6.706676] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 6.709048] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 6.799430] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 6.801700] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 6.930847] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 6.933115] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 7.208281] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 7.210549] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 7.299299] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 7.301568] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 7.430326] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 7.432458] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 7.708289] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 7.710560] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 7.799435] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 7.801691] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 7.930346] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 7.932369] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 8.207246] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 8.209504] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 8.299048] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 8.301315] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 8.430586] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 8.432855] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 8.706293] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 8.708400] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 8.798966] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 8.801234] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 8.924700] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 8.926769] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 9.194662] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 9.196921] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 9.282564] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 9.284833] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 9.413362] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 9.415631] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Dec 26 18:59:34 LUTER kernel: [ 9.506006] EXT4-fs (nvme0n1p5): mounted filesystem with ordered data mode. Opts: (null) Dec 26 18:59:34 LUTER kernel: [ 9.682381] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status Dec 26 18:59:34 LUTER kernel: [ 9.684055] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful
здесь https://darkfess.ru/%D1%83%D0%B4%D0%B0%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5-intel-linux-graphics-installer-%D1%83%D1%81%D1%82%D0%B0%D0%BD%D0%BE%D0%B2%D0%BA%D0%B0-ltsenablementstack-ubuntu-14-04-3/ человек посетовал на дрова интела, может у меня тоже это, но я не хочу сломать систему снова. кто может помочь?

« Последнее редактирование: 30 Декабря 2018, 13:10:39 от Aleksandru »

perlamut

uname -a Linux hysterics 4.15.0-43-generic #46~16.04.1-Ubuntu SMP Fri Dec 7 13:31:08 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
заметил что если грузиться с другим ядром, 4.6.4 например. этой ошибки нет.

Печать

Страницы: [1] Вверх

Источник

Description

Igor Osminin

2021-02-23 15:19:46 UTC

Created attachment 222759 [details]
Log

Hi. On a laptop with Intel HD Graphics 5500, after waking up from sleep mode, I got some error messages (the system continues to work after that):

Feb 23 16:43:29 freebsd kernel: [drm ERROR :fw_domain_wait_ack_clear] render: timed out waiting for forcewake ack to clear.
Feb 23 16:43:29 freebsd kernel: drmn1: Failed to idle engines, declaring wedged!

Also, I attach all /var/log/messages for today's date.

Comment 1

Igor Osminin

2021-02-23 19:12:37 UTC

After that, the graphics is drawn very slowly. This is especially noticeable when dragging windows or viewing web pages through the browser.

Comment 2

Igor Osminin

2021-03-01 10:30:10 UTC

Today the error appeared again, on FreeBSD 13.0-BETA 4. In /var/log/messages, everything is the same.

Comment 3

Dave Cottlehuber

2021-03-06 08:43:32 UTC

can you post any sysctls, loader.conf tunables that might be related? and for history, which pkg versions are installed?

Comment 4

Igor Osminin

2021-03-06 09:05:40 UTC

Hi, David. The pkg version I have is 1.16.3.
Contents of /boot/loader.conf related to the i915 driver:

i915kms_load="YES"
drm.i915.enable_rc6=0
drm.i915.semaphores="1"
drm.i915.enable_fbc="1"
kern.vt.fb.default_mode="1600x900"

$ sysctl compat.linuxkpi
compat.linuxkpi.i915_enable_dpcd_backlight: 0
compat.linuxkpi.i915_enable_dp_mst: 1
compat.linuxkpi.i915_guc_log_level: -1
compat.linuxkpi.i915_enable_guc: 0
compat.linuxkpi.i915_edp_vswing: 0
compat.linuxkpi.i915_nuclear_pageflip: 0
compat.linuxkpi.i915_verbose_state_checks: 1
compat.linuxkpi.i915_mmio_debug: 0
compat.linuxkpi.i915_disable_display: 0
compat.linuxkpi.i915_invert_brightness: 0
compat.linuxkpi.i915_force_reset_modeset_test: 0
compat.linuxkpi.i915_load_detect_test: 0
compat.linuxkpi.i915_prefault_disable: 0
compat.linuxkpi.i915_fastboot: -1
compat.linuxkpi.i915_enable_ips: 1
compat.linuxkpi.i915_disable_power_well: 0
compat.linuxkpi.i915_alpha_support: 1
compat.linuxkpi.i915_enable_psr: 0
compat.linuxkpi.i915_enable_hangcheck: 1
compat.linuxkpi.i915_error_capture: 1
compat.linuxkpi.i915_reset: 2
compat.linuxkpi.i915_vbt_sdvo_panel_type: -1
compat.linuxkpi.i915_panel_use_ssc: -1
compat.linuxkpi.i915_lvds_channel_mode: 0
compat.linuxkpi.i915_enable_fbc: 0
compat.linuxkpi.i915_enable_dc: -1
compat.linuxkpi.i915_modeset: -1
compat.linuxkpi.drm_edid_firmware: 
compat.linuxkpi.drm_drm_fbdev_overalloc: 100
compat.linuxkpi.drm_fbdev_emulation: 1
compat.linuxkpi.drm_timestamp_precision_usec: 20
compat.linuxkpi.drm_vblankoffdelay: 5000
compat.linuxkpi.drm_poll: 1
compat.linuxkpi.drm_edid_fixup: 6
compat.linuxkpi.drm_debug: 0
compat.linuxkpi.drm_dp_aux_i2c_transfer_size: 16
compat.linuxkpi.drm_dp_aux_i2c_speed_khz: 10
compat.linuxkpi.debug: 0

Comment 6

Igor Osminin

2021-03-15 07:45:30 UTC

(In reply to Patricio Villar from comment #5)
Hi, Patricio. Yes, it's the same problem. In 13.0-RC1, this occurred twice, before that, it happened more often. Now, in 13.0-RC2, I have not encountered this yet (updated yesterday).

Comment 7

Patricio Villar

2021-03-15 13:13:12 UTC

(In reply to Igor Osminin from comment #6)
Cool! That means it wasn't just my impression or a coincidence. So far it haven't happened here on 13.0-RC2 either.

Comment 8

Patricio Villar

2021-04-05 19:46:07 UTC

How's it going for you lately?
Sadly, in my case it's gone completely backwards. Resuming from suspend is really broken right now on both 13.0-RC4 and 13.0-RC5. It's a real shame, and I'm afraid it's gonna make it to 13.0-RELEASE :(

Comment 9

Mark Linimon

2021-04-06 05:36:16 UTC

(In reply to Patricio Villar from comment #8)
> Resuming from suspend is really broken right now on both 13.0-RC4 and 13.0-RC5.

Hmm.  I have been doing some updates around the house.  This laptop (a Dell Latitude E5430) is on RC4 and it suspends ok.  I have the following set, if it matters:

  hw.acpi.lid_switch_state=S3

I will check the other laptop, which is on RC5, later.

So, this is puzzling.

Comment 10

Patricio Villar

2021-04-06 17:57:27 UTC

(In reply to Mark Linimon from comment #9)
Thanks for replying!
I think this problem is very hardware-specific after all, as I have Intel HD Graphics 5500 just like Igor Osminin (who first reported the issue).
And I have "hw.acpi.lid_switch_state=S3" too, but don't think it's related to this bug really.

Comment 13

eaosfu

2021-10-17 04:34:36 UTC

(In reply to Patricio Villar from comment #11)

I just tried on my thinkpad t450 running:

13.0-RELEASE-p4
gpu-firmware-kmod-g20210330
drm-fbsd13-kmod-5.4.144.g20210908

I manually ran through several cycles of suspend/resume with firefox playing a youtube video. I never locked the screen during these cycles and thus never wedged the gpu.

I then tried running through several cycles of suspend/resume again except this time the only program I'd run before triggering suspend is i3-lock. This time, I reliable wedge the gpu on the second resume.

Comment 15

Graham Perrin

2022-12-31 10:50:05 UTC

Things seem to be fixed in parallel bug 253801, so, with no recent feedback here, I think it's time to close both reports. 

If a new bug report is required, probably better to make it 'Ports & Packages' (not base system). Thanks. 

graphics/drm-510-kmod

<https://www.freshports.org/graphics/drm-510-kmod/>

Источник

I’m getting this kernel error on 5.19 and 6.0 all the time, is there anything that can be done to mitigate it. Seems like it’s a i915 driver problem. The screen frequently goes black.

------------[ cut here ]------------
i915 0000:00:02.0: drm_WARN_ON(new_crtc_state->do_async_flip && !plane->async_flip)
WARNING: CPU: 4 PID: 1565 at drivers/gpu/drm/i915/display/intel_display.c:7505 intel_atomic_check+0x2947/0x2fe0 [i915]
Modules linked in: tun snd_usb_audio snd_usbmidi_lib usbhid snd_rawmidi hid_logitech_hidpp uhid veth nf_conntrack_netlink xt_nat xt_tcpudp ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs nft_chain_nat xt_MASQUERADE vxlan ip6_udp_tunnel udp_tunnel nft_log nft_limit ipt_REJECT nf_reject_ipv4 xt_limit xt_NFLOG nfnetlink_log xt_physdev xt_conntrack xt_mark xt_multiport xt_addrtype xt_comment nft_compat nf_tables ip_set nfnetlink iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c br_netfilter bridge stp llc ctr ccm cmac algif_hash algif_skcipher af_alg snd_seq_dummy snd_hrtimer snd_seq snd_seq_device overlay qrtr bnep snd_ctl_led snd_soc_skl_hda_dsp binfmt_misc snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_sof_probes nls_ascii nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek snd_soc_dmic snd_hda_codec_generic mei_hdcp intel_rapl_msr snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence
 x86_pkg_temp_thermal snd_sof_intel_hda intel_powerclamp snd_sof_pci coretemp snd_sof_xtensa_dsp snd_sof kvm_intel snd_sof_utils snd_soc_hdac_hda btusb snd_hda_ext_core btrtl snd_soc_acpi_intel_match snd_soc_acpi kvm btbcm iwlmvm snd_soc_core btintel btmtk irqbypass snd_compress snd_intel_dspcfg snd_intel_sdw_acpi intel_cstate bluetooth mac80211 snd_hda_codec intel_uncore snd_hda_core iTCO_wdt snd_hwdep intel_pmc_bxt libarc4 serio_raw pcspkr efi_pstore soundwire_bus jitterentropy_rng iTCO_vendor_support mei_me wmi_bmof iwlwifi snd_pcm watchdog sha512_ssse3 mei sha512_generic snd_timer uvcvideo drbg ansi_cprng videobuf2_vmalloc videobuf2_memops ucsi_acpi processor_thermal_device_pci_legacy cfg80211 videobuf2_v4l2 typec_ucsi processor_thermal_device ecdh_generic processor_thermal_rfim videobuf2_common ecc roles processor_thermal_mbox processor_thermal_rapl typec intel_rapl_common intel_soc_dts_iosf thinkpad_acpi nvram platform_profile ledtrig_audio snd soundcore rfkill
 int3403_thermal soc_button_array int340x_thermal_zone ac evdev int3400_thermal intel_pmc_core acpi_tad acpi_thermal_rel intel_hid acpi_pad sparse_keymap v4l2loopback(OE) videodev mc msr parport_pc ppdev lp parport fuse configfs efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic dm_crypt dm_mod hid_sensor_custom hid_sensor_hub hid_generic intel_ishtp_hid hid i915 drm_buddy crc32_pclmul i2c_algo_bit crc32c_intel drm_display_helper ghash_clmulni_intel cec nvme rc_core nvme_core ttm t10_pi xhci_pci drm_kms_helper crc64_rocksoft_generic crc64_rocksoft crc_t10dif xhci_hcd crct10dif_generic aesni_intel i2c_i801 intel_ish_ipc crct10dif_pclmul crc64 crypto_simd usbcore drm psmouse thunderbolt cryptd i2c_smbus intel_ishtp usb_common crct10dif_common wmi button battery video
CPU: 4 PID: 1565 Comm: Xorg Tainted: G        W  OE     5.19.0-2-amd64 #1  Debian 5.19.11-1
Hardware name: LENOVO 20XW003GUS/20XW003GUS, BIOS N32ET80W (1.56 ) 08/29/2022
RIP: 0010:intel_atomic_check+0x2947/0x2fe0 [i915]
Code: 4c 8b 67 50 4d 85 e4 75 03 4c 8b 27 e8 42 e6 e5 cd 48 c7 c1 80 c1 b4 c0 4c 89 e2 48 c7 c7 0b c6 b6 c0 48 89 c6 e8 5d d4 11 ce <0f> 0b c7 45 a0 ea ff ff ff e9 9e de ff ff 49 8b 47 08 48 8b 88 90
RSP: 0018:ffffa8e5c1d6fbb8 EFLAGS: 00010286
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffff8f36ee29 RDI: 00000000ffffffff
RBP: ffffa8e5c1d6fc60 R08: 0000000000000000 R09: 0000000100bda3eb
R10: ffffa8e5c1d6fa58 R11: ffffffff8fabfd28 R12: ffff9c48c1b433d0
R13: ffffffffc0400ed0 R14: 0000000000000000 R15: ffff9c49a42f1800
FS:  00007fd13281fa80(0000) GS:ffff9c4c0f700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000022a80162a000 CR3: 0000000128634004 CR4: 0000000000770ee0
PKRU: 55555554
Call Trace:
 <TASK>
 drm_atomic_check_only+0x5b1/0xa20 [drm]
 drm_atomic_nonblocking_commit+0x13/0x60 [drm]
 drm_atomic_helper_page_flip+0x60/0xd0 [drm_kms_helper]
 drm_mode_page_flip_ioctl+0x573/0x5d0 [drm]
 ? drm_mode_cursor2_ioctl+0x10/0x10 [drm]
 drm_ioctl_kernel+0xb2/0x140 [drm]
 drm_ioctl+0x224/0x3e0 [drm]
 ? drm_mode_cursor2_ioctl+0x10/0x10 [drm]
 __x64_sys_ioctl+0x87/0xc0
 do_syscall_64+0x38/0xc0
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fd1322ffe9b
Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1b 48 8b 44 24 18 64 48 2b 04 25 28 00
RSP: 002b:00007ffc0b2255b0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000559f70456b50 RCX: 00007fd1322ffe9b
RDX: 00007ffc0b225640 RSI: 00000000c01864b0 RDI: 000000000000000d
RBP: 00007ffc0b225640 R08: 000000000019c78d R09: 0000559f7041f010
R10: 0000000000000003 R11: 0000000000000246 R12: 00000000c01864b0
R13: 000000000000000d R14: 0000559f70458630 R15: 000000000019c78d
 </TASK>
---[ end trace 0000000000000000 ]---

This is from version 20210818-1 of firmware-misc-nonfree from Debian 11 — Bookworm

❯ modinfo i915
filename:       /lib/modules/5.19.0-2-amd64/kernel/drivers/gpu/drm/i915/i915.ko
license:        GPL and additional rights
description:    Intel Graphics
author:         Intel Corporation
author:         Tungsten Graphics, Inc.
import_ns:      DMA_BUF

asked Aug 17, 2022 at 18:24

Evan CarrollEvan Carroll

25.6k37 gold badges143 silver badges253 bronze badges

This does seem like a driver bug; in fact, it might be fixed by this page flip patch series. This patch series was merged for 5.19, so upgrading to any 5.19 kernel will allow you to check whether the warnings you’re getting disappear. (In Debian, the 5.19 kernel series is currently packaged in experimental.)

It might be a firmware bug too, although that seems less likely here. If this is the case, you’ll need to wait for an update to the firmware package.

answered Aug 17, 2022 at 19:18

Stephen KittStephen Kitt

388k51 gold badges996 silver badges1095 bronze badges

Источник

View previous topic :: View next topic

Author

Message

Black
Tux’s lil’ helper

Joined: 10 Dec 2002
Posts: 147
Location: Québec, Canada

Posted: Sun May 30, 2021 12:13 pm Post subject: [SOLVED] Intel graphics, no signal once kernel loads i915

Edit 2021/06/02 I’m marking this as [SOLVED], but the solution is less-than-ideal at this time. I ended up using git-sources-5.13_rc4 rather than gentoo-sources for the kernel, meaning that I’m now running a development kernel that is not considered stable. I haven’t had any issue so far, but I’m still setting up that PC. I will try gentoo-sources 5.14 as soon as it is released. ———- With my computer reaching 10 years old, I decided to get a new one. Since I don’t do gaming, I settled for an Intel Core i5 with integrated graphics. I followed the handbook and all is fine. However, I follow the Intel graphics, and this is where the issue appears. I build the the i915 driver in-kernel. Upon booting, as soon as the kernel activates the driver, the screen goes blank and displays «no signal». I tried on both the VGA port and the HDMI port. I have not even installed Xorg yet. The computer does keep on booting (I can ssh into it), but without any display is not very useful. If I add «nomodeset» in the grub config, then I do get the display, but then I won’t be able to get Xorg. Intel Core i5 10500 (10th generation) Motherboard Asus Prime H510M-A/CSM I can find a few posts with identical problem, such as here, but the solution is usually «disable legacy rom» in the computer’s bios (there’s no such thing in my computer’s bios), or, in the case above, downgrade the kernel to 5.2, which is no longer available in Gentoo. As a troubleshooting step, I tried the Ubuntu install — it gets the same problem. I can get it to «work» by using the «safe graphics» option (which is really only nomodeset). It then gets into Xorg using fbdev, but I’m locked in a 1980×1024 resolution, and cannot use my second monitor to extend the desktop. Even a Windows 7 install disk only gets as far as «Starting Windows» with a red bar at the top, then freezes there. (That’s the start of the install in the case of Windows — I can’t even install it, not that I want to.) Worst-case scenario, I could use fbdev, as long as I can change the resolution and extend to a second (and third) monitor — the motherboard has a VGA, HDMI, and DisplayPort connector. But obviously, I’d rather use that Intel GPU… Edit: can’t seem to get to put large data (such as dmesg or the kernel config) here, will have to use pastebin I guess. I’ll get to it later today. I’ve got kids to feed at this time. Last edited by Black on Wed Jun 02, 2021 10:04 am; edited 1 time in total

alamahant
Advocate

Joined: 23 Mar 2019
Posts: 3304

Posted: Sun May 30, 2021 12:23 pm Post subject:

Probably you need also

Code:

sys-kernel/linux-firmware

Sure enough

Quote:

Installation

Firmware

Systems using Skylake, Broxton or newer Intel graphics will need to install additional firmware[1] from sys-kernel/linux-firmware package:

root #emerge —ask sys-kernel/linux-firmware

Otherwise errors such as the following might be visible in dmesg:

kernel: i915 0000:00:02.0: Direct firmware load for i915/skl_dmc_ver1_27.bin failed with error -2

kernel: i915 0000:00:02.0: Failed to load DMC firmware [https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling runtime power management.

Also better do keep the i915 as module so that upon loading it can call on the needed firmware also.

Code:

CONFIG_DRM_I915=m

CONFIG_DRM_I915_FORCE_PROBE=»*»

CONFIG_DRM_I915_CAPTURE_ERROR=y

CONFIG_DRM_I915_COMPRESS_ERROR=y

CONFIG_DRM_I915_USERPTR=y

CONFIG_DRM_I915_GVT=y

CONFIG_DRM_I915_GVT_KVMGT=m

CONFIG_DRM_I915_FENCE_TIMEOUT=10000

CONFIG_DRM_I915_USERFAULT_AUTOSUSPEND=250

CONFIG_DRM_I915_HEARTBEAT_INTERVAL=2500

CONFIG_DRM_I915_PREEMPT_TIMEOUT=640

CONFIG_DRM_I915_MAX_REQUEST_BUSYWAIT=8000

CONFIG_DRM_I915_STOP_TIMEOUT=100

CONFIG_DRM_I915_TIMESLICE_DURATION=1

CONFIG_SND_HDA_I915=y

If you dont configure i915 as module then you will need to build the firmware also into the kernel.

Also you need

Code:

VIDEO_CARDS=»intel i965 iris»

in

make.conf
_________________

Black
Tux’s lil’ helper

Joined: 10 Dec 2002
Posts: 147
Location: Québec, Canada

Posted: Sun May 30, 2021 1:02 pm Post subject:

Quite right, I do need linux-firmware. I do have it, but forgot to mention it.

I’ll try loading as a module, but given that this is what the Ubuntu install disk does and it doesn’t work for it, I don’t have much hope.

I got a bit more info posted on pastebin:

dmesg

Kernel config

emerge —info:

Code:

Portage 3.0.18 (python 3.8.9-final-0, default/linux/amd64/17.1, gcc-10.2.0, glibc-2.32-r7, 5.10.27-gentoo x86_64)

=================================================================

System uname: Linux-5.10.27-gentoo-x86_64-Intel-R-_Core-TM-_i5-10500_CPU_@_3.10GHz-with-glibc2.2.5

KiB Mem: 32692572 total, 32504208 free

KiB Swap: 33554428 total, 33554428 free

Timestamp of repository gentoo: Sat, 29 May 2021 18:00:01 +0000

Head commit of repository gentoo: 8272e99d3d6c3bcaf48d9dabeeecc5a03a1c897a

sh bash 5.1_p8

ld GNU ld (Gentoo 2.35.2 p1) 2.35.2

app-shells/bash: 5.1_p8::gentoo

dev-lang/perl: 5.32.1::gentoo

dev-lang/python: 3.8.9_p2::gentoo, 3.9.4_p1::gentoo

sys-apps/baselayout: 2.7::gentoo

sys-apps/openrc: 0.42.1-r1::gentoo

sys-apps/sandbox: 2.23::gentoo

sys-devel/autoconf: 2.69-r5::gentoo

sys-devel/automake: 1.16.3-r1::gentoo

sys-devel/binutils: 2.35.2::gentoo

sys-devel/gcc: 10.2.0-r5::gentoo

sys-devel/gcc-config: 2.4::gentoo

sys-devel/libtool: 2.4.6-r6::gentoo

sys-devel/make: 4.3::gentoo

sys-kernel/linux-headers: 5.10::gentoo (virtual/os-headers)

sys-libs/glibc: 2.32-r7::gentoo

Repositories:

gentoo

location: /var/db/repos/gentoo

sync-type: rsync

sync-uri: rsync://rsync.gentoo.org/gentoo-portage

priority: -1000

sync-rsync-verify-jobs: 1

sync-rsync-verify-metamanifest: yes

sync-rsync-verify-max-age: 24

sync-rsync-extra-opts:

ACCEPT_KEYWORDS=»amd64″

ACCEPT_LICENSE=»* -@EULA»

CBUILD=»x86_64-pc-linux-gnu»

CFLAGS=»-march=native -O2 -pipe»

CHOST=»x86_64-pc-linux-gnu»

CONFIG_PROTECT=»/etc /usr/share/gnupg/qualified.txt»

CONFIG_PROTECT_MASK=»/etc/ca-certificates.conf /etc/env.d /etc/gconf /etc/gentoo-release /etc/sandbox.d /etc/terminfo»

CXXFLAGS=»-march=native -O2 -pipe»

DISTDIR=»/var/cache/distfiles»

ENV_UNSET=»CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY GOBIN GOPATH PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR»

FCFLAGS=»-march=native -O2 -pipe»

FEATURES=»assume-digests binpkg-docompress binpkg-dostrip binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles ipc-sandbox merge-sync multilib-strict network-sandbox news parallel-fetch pid-sandbox preserve-libs protect-owned qa-unresolved-soname-deps sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr»

FFLAGS=»-march=native -O2 -pipe»

GENTOO_MIRRORS=»http://gentoo.mirrors.tera-byte.com/ https://mirror.csclub.uwaterloo.ca/gentoo-distfiles/»

LANG=»en_US.utf8″

LDFLAGS=»-Wl,-O1 -Wl,—as-needed»

MAKEOPTS=»-j13″

PKGDIR=»/var/cache/binpkgs»

PORTAGE_CONFIGROOT=»/»

PORTAGE_RSYNC_OPTS=»—recursive —links —safe-links —perms —times —omit-dir-times —compress —force —whole-file —delete —stats —human-readable —timeout=180 —exclude=/distfiles —exclude=/local —exclude=/packages —exclude=/.git»

PORTAGE_TMPDIR=»/var/tmp»

USE=»acl alsa amd64 berkdb bzip2 cdr cli crypt dri dvd fortran gdbm iconv ipv6 libglvnd libtirpc logrotate multilib ncurses nls nptl openmp pam pcre readline seccomp split-usr ssl tcpd unicode xattr zlib» ABI_X86=»64″ ADA_TARGET=»gnat_2018″ ALSA_CARDS=»ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci» APACHE2_MODULES=»authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias» CALLIGRA_FEATURES=»karbon sheets words» COLLECTD_PLUGINS=»df interface irq load memory rrdtool swap syslog» CPU_FLAGS_X86=»mmx mmxext sse sse2″ ELIBC=»glibc» GPSD_PROTOCOLS=»ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock greis isync itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 timing tsip tripmate tnt ublox ubx» INPUT_DEVICES=»libinput» KERNEL=»linux» LCD_DEVICES=»bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text» LIBREOFFICE_EXTENSIONS=»presenter-console presenter-minimizer» LUA_SINGLE_TARGET=»lua5-1″ LUA_TARGETS=»lua5-1″ OFFICE_IMPLEMENTATION=»libreoffice» PHP_TARGETS=»php7-3 php7-4″ POSTGRES_TARGETS=»postgres10 postgres11″ PYTHON_SINGLE_TARGET=»python3_8″ PYTHON_TARGETS=»python3_8″ RUBY_TARGETS=»ruby26″ USERLAND=»GNU» VIDEO_CARDS=»fbdev» XTABLES_ADDONS=»quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq proto steal rawnat logmark ipmark dhcpmac delude chaos account»

Unset: CC, CPPFLAGS, CTARGET, CXX, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, LINGUAS, PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, RUSTFLAGS

lspci:

Code:

00:00.0 Host bridge: Intel Corporation Device 9b53 (rev 03)

00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (rev 03)

00:14.0 USB controller: Intel Corporation Device 43ed (rev 11)

00:14.2 RAM memory: Intel Corporation Device 43ef (rev 11)

00:15.0 Serial bus controller [0c80]: Intel Corporation Device 43e8 (rev 11)

00:16.0 Communication controller: Intel Corporation Device 43e0 (rev 11)

00:17.0 SATA controller: Intel Corporation Device 43d2 (rev 11)

00:1c.0 PCI bridge: Intel Corporation Device 43bc (rev 11)

00:1f.0 ISA bridge: Intel Corporation Device 4388 (rev 11)

00:1f.3 Audio device: Intel Corporation Device f0c8 (rev 11)

00:1f.4 SMBus: Intel Corporation Device 43a3 (rev 11)

00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 43a4 (rev 11)

00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (14) I219-V (rev 11)

01:00.0 Non-Volatile memory controller: Kingston Technology Company, Inc. A2000 NVMe SSD (rev 03)

alamahant
Advocate

Joined: 23 Mar 2019
Posts: 3304

Posted: Sun May 30, 2021 1:29 pm Post subject:

Your firmware is NOT loading

Code:

0.490151] —[ end trace 45ecc57aeda36326 ]—

[ 0.490576] i915 0000:00:02.0: Direct firmware load for i915/kbl_dmc_ver1_04.bin failed with error -2

[ 0.490577] i915 0000:00:02.0: [drm] Failed to load DMC firmware i915/kbl_dmc_ver1_04.bin. Disabling runtime power management.

[ 0.490577] i915 0000:00:02.0: [drm] DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915

Please build i915 as module.

ie

Code:

CONFIG_DRM_I915=m

plz see also the above posts.
_________________

Black
Tux’s lil’ helper

Joined: 10 Dec 2002
Posts: 147
Location: Québec, Canada

Posted: Sun May 30, 2021 2:29 pm Post subject:

Right again about the firmware. I’ve been banging my head on this for almost a week now, and I missed that.

So I’ve added that filename to the firmware load, as well as loading i915 as a module. I need to enable these:

KVM

VFIO_MDEV

VFIO_MDEV_DEVICE

in order to enable:

CONFIG_DRM_I915_GVT_KVMGT=m

Still no screen. Out of the entire dmesg, there’s this that stands out:

Code:

[ 1.622224] ————[ cut here ]————

[ 1.622225] i915 0000:00:02.0: drm_WARN_ON(!IS_PLATFORM(dev_priv, INTEL_TIGERLAKE) && !IS_PLATFORM(dev_priv, INTEL_ROCKETLAKE))

[ 1.622266] WARNING: CPU: 10 PID: 626 at drivers/gpu/drm/i915/intel_pch.c:123 intel_pch_type+0x893/0x950 [i915]

[ 1.622266] Modules linked in: i915(+) x86_pkg_temp_thermal efivarfs

[ 1.622269] CPU: 10 PID: 626 Comm: udevd Not tainted 5.10.27-gentoo #8

[ 1.622270] Hardware name: ASUS System Product Name/PRIME H510M-A, BIOS 0820 04/27/2021

[ 1.622292] RIP: 0010:intel_pch_type+0x893/0x950 [i915]

[ 1.622293] Code: 4c 8b 67 50 4d 85 e4 75 03 4c 8b 27 e8 d6 70 42 ca 48 c7 c1 b0 1d 2d c0 4c 89 e2 48 c7 c7 2b 9f 2f c0 48 89 c6 e8 04 b6 90 ca <0f> 0b e9 19 f9 ff ff 48 8b 7b 18 4c 8b 67 50 4d 85 e4 75 03 4c 8b

[ 1.622293] RSP: 0018:ffffb19fc1107b88 EFLAGS: 00010282

[ 1.622294] RAX: 0000000000000000 RBX: ffffa1b586500000 RCX: 00000000ffffdfff

[ 1.622295] RDX: 00000000ffffffea RSI: 00000000ffffdfff RDI: 0000000000000001

[ 1.622295] RBP: ffffa1b581041000 R08: ffffffff8b530ac8 R09: 0000000000000003

[ 1.622296] R10: ffffffff8b450ae0 R11: 3fffffffffffffff R12: ffffa1b580fa9650

[ 1.622296] R13: 0000000000004380 R14: ffffa1b5865006c8 R15: ffffa1b586500808

[ 1.622297] FS: 00007ffb29e1d740(0000) GS:ffffa1bcbc480000(0000) knlGS:0000000000000000

[ 1.622297] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

[ 1.622298] CR2: 00007f8577f80018 CR3: 000000010501e001 CR4: 00000000003706e0

[ 1.622298] Call Trace:

[ 1.622320] intel_detect_pch+0x56/0x2f0 [i915]

[ 1.622342] i915_driver_probe+0x28c/0xc40 [i915]

[ 1.622344] ? __kernfs_new_node+0x15b/0x1c0

[ 1.622346] local_pci_probe+0x3d/0x70

[ 1.622348] ? _cond_resched+0x11/0x40

[ 1.622349] pci_device_probe+0xc2/0x170

[ 1.622351] ? sysfs_do_create_link_sd+0x5b/0xb0

[ 1.622352] really_probe+0xd8/0x410

[ 1.622353] driver_probe_device+0x4a/0xa0

[ 1.622354] device_driver_attach+0x9c/0xb0

[ 1.622355] __driver_attach+0x6f/0x100

[ 1.622356] ? device_driver_attach+0xb0/0xb0

[ 1.622357] bus_for_each_dev+0x75/0xc0

[ 1.622358] bus_add_driver+0x106/0x1b0

[ 1.622359] driver_register+0x86/0xd0

[ 1.622360] ? 0xffffffffc03c5000

[ 1.622381] i915_init+0x58/0x6b [i915]

[ 1.622383] do_one_initcall+0x3f/0x1b0

[ 1.622384] ? _cond_resched+0x11/0x40

[ 1.622386] ? kmem_cache_alloc_trace+0x3a/0x190

[ 1.622387] do_init_module+0x57/0x230

[ 1.622388] __do_sys_finit_module+0xa0/0xe0

[ 1.622389] do_syscall_64+0x33/0x40

[ 1.622390] entry_SYSCALL_64_after_hwframe+0x44/0xa9

[ 1.622391] RIP: 0033:0x7ffb29f785c9

[ 1.622392] 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 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 6f 18 0c 00 f7 d8 64 89 01 48

[ 1.622393] RSP: 002b:00007fff07ba1a18 EFLAGS: 00000206 ORIG_RAX: 0000000000000139

[ 1.622394] RAX: ffffffffffffffda RBX: 000055ed8ede0960 RCX: 00007ffb29f785c9

[ 1.622394] RDX: 0000000000000000 RSI: 00007ffb2a052ab5 RDI: 0000000000000008

[ 1.622395] RBP: 0000000000020000 R08: 0000000000000000 R09: 000055ed8edc6b20

[ 1.622395] R10: 0000000000000008 R11: 0000000000000206 R12: 00007ffb2a052ab5

[ 1.622396] R13: 0000000000000000 R14: 000055ed8edd7300 R15: 000055ed8ede0960

[ 1.622396] —[ end trace 6f5001b47a8535ad ]—

[ 1.622787] checking generic (4000000000 300000) vs hw (6000000000 1000000)

[ 1.622787] checking generic (4000000000 300000) vs hw (4000000000 10000000)

[ 1.622788] fb0: switching to inteldrmfb from EFI VGA

[ 1.622824] Console: switching to colour dummy device 80×25

[ 1.622839] i915 0000:00:02.0: vgaarb: deactivate vga console

[ 1.623506] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem

[ 1.623765] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)

[ 1.624484] i915 0000:00:02.0: [drm] *ERROR* crtc 51: Can’t calculate constants, dotclock = 0!

[ 1.624486] i915 0000:00:02.0: [drm] *ERROR* crtc 72: Can’t calculate constants, dotclock = 0!

Black
Tux’s lil’ helper

Joined: 10 Dec 2002
Posts: 147
Location: Québec, Canada

Posted: Sun May 30, 2021 2:31 pm Post subject:

Code:

i915 0000:00:02.0: drm_WARN_ON(!IS_PLATFORM(dev_priv, INTEL_TIGERLAKE) && !IS_PLATFORM(dev_priv, INTEL_ROCKETLAKE))

I’ll have to dig it out, but I seem to remember seeing «Comet Lake» come up at some point for my GPU.

Jaglover
Watchman

Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana

Posted: Sun May 30, 2021 2:34 pm Post subject:

Your firmware loading is not showstopper, there is a crash in your dmesg. My suggestion is switching to latest stable kernel, which is currently 5.12.8. (Ignore Gentoo testing flag, it is stable at kernel.org) _________________ My Gentoo installation notes. Please learn how to denote units correctly!

Black
Tux’s lil’ helper

Joined: 10 Dec 2002
Posts: 147
Location: Québec, Canada

Posted: Sun May 30, 2021 3:13 pm Post subject:

Same thing with 5.12.8…

pietinger
Moderator

Joined: 17 Oct 2006
Posts: 2401
Location: Bavaria

Posted: Sun May 30, 2021 3:34 pm Post subject:

My recommendation would be: Put all fixed in your (newest) kernel (5.10.41 or 5.12.: a.) Drivers for GPU + b.) (newest = ~amd64) Firmware for GPU described in https://wiki.gentoo.org/wiki/Intel c.) (newest = ~amd64) Microcode for CPU described in https://forums.gentoo.org/viewtopic-t-1065464.html — or — chapter «NEW method without initram-fs/disk» https://wiki.gentoo.org/wiki/Intel_microcode Can you use the DisplayPort ? (I would prefer it before HDMI).

Jaglover
Watchman

Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana

Posted: Sun May 30, 2021 3:52 pm Post subject:

Here’s what I think. This is brand new hardware, correct? Nothing has been proved working on it, Ubuntu, older Windows, all fail, correct? If the above is true then it may be a hardware issue. I don’t know about Windows 10, is there some trial version or something you can try and install? All hardware manufacturers make sure their product works with Windows. If yours does not then it is warranty time. _________________ My Gentoo installation notes. Please learn how to denote units correctly!

Black
Tux’s lil’ helper

Joined: 10 Dec 2002
Posts: 147
Location: Québec, Canada

Posted: Sun May 30, 2021 4:08 pm Post subject:

I was missing the microcode, but it did not change anything. As far as I can tell, the latest versions of the firmware and microcode are already what’s coming down from emerge. Jaglover, yes, this is brand new hardware. Windows 7 failed, but reading on the net it might be «normal», being an old OS. I’m currently downloading a trial version of Windows (didn’t know that existed!). If that fails then I agree with you, and I’ll claim warranty. Maybe I should have gone for a Gigabyte instead of Asus…

Jaglover
Watchman

Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana

Posted: Sun May 30, 2021 5:02 pm Post subject:

I stopped using Asus 6-7 years ago, after several negative experiences. Maybe it was just bad luck. Anyhow, older versions of Intel all work without microcode and firmware, some features are missing but the basic functionality is there. KMS and DRI definitely works without, while yours is crashing. I’m not sure if this is the motherboard or CPU causing this … or even a faulty RAM … _________________ My Gentoo installation notes. Please learn how to denote units correctly!

Black
Tux’s lil’ helper

Joined: 10 Dec 2002
Posts: 147
Location: Québec, Canada

Posted: Mon May 31, 2021 12:51 pm Post subject:

The Windows 10 Trial at least goes further than Windows 7. I get to a «full windowing» system, but this is most likely the equivalent of fbdev. At this time I can’t get Windows to install because it complains about missing media driver. I’ve fed it every driver from the motherboard’s CD, but the message remains unhelpful as to which driver is missing exactly. I’ll get back to it later today. For now, I have this thing called «work» to do. Apparently, that’s what makes money appear magically in my bank account. Another thing I’ll try is to set up my boot partition for BIOS, rather than UEFI — if I can’t disable «Legacy BIOS», might as well try using it. I’ll report back once I get the chance to try it out.

Jaglover
Watchman

Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana

Posted: Mon May 31, 2021 12:55 pm Post subject:

Is this CPU listed as supported by mobo firmware? Is there a BIOS upgrade perhaps for this CPU? Out of curiosity, what is the PCI ID of graphics? Is it listed as supported in kernel driver database? _________________ My Gentoo installation notes. Please learn how to denote units correctly!

Black
Tux’s lil’ helper

Joined: 10 Dec 2002
Posts: 147
Location: Québec, Canada

Posted: Mon May 31, 2021 1:15 pm Post subject:

Yes, the motherboard supports «Intel® Socket LGA1200 for 11th Gen Intel® Core™ Processors & 10th Gen Intel® Core™, Pentium® Gold and Celeron® Processors».

PCI ID:

Code:

00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 630 [8086:9bc8] (rev 03)

I do find that ID in the kernel drive database:

Code:

vendor: 8086 («Intel Corporation»), device: 9bc8 («CometLake-S GT2 [UHD Graphics 630]»), class: 03 («Display controller»)

lspci -v:

Code:

00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (rev 03) (prog-if 00 [VGA controller])

DeviceName: Onboard — Video

Subsystem: ASUSTeK Computer Inc. UHD Graphics 630

Flags: bus master, fast devsel, latency 0, IRQ 137

Memory at 6000000000 (64-bit, non-prefetchable) [size=16M]

Memory at 4000000000 (64-bit, prefetchable) [size=256M]

I/O ports at 3000 [size=64]

Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]

Capabilities: [40] Vendor Specific Information: Len=0c <?>

Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00

Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-

Capabilities: [d0] Power Management version 2

Capabilities: [100] Process Address Space ID (PASID)

Capabilities: [200] Address Translation Service (ATS)

Capabilities: [300] Page Request Interface (PRI)

Kernel driver in use: i915

Kernel modules: i915

alamahant
Advocate

Joined: 23 Mar 2019
Posts: 3304

Posted: Mon May 31, 2021 1:34 pm Post subject:

Have you tried with Clear Linux live cd https://cdn.download.clearlinux.org/releases/34640/clear/clear-34640-live-desktop.iso ? _________________

Black
Tux’s lil’ helper

Joined: 10 Dec 2002
Posts: 147
Location: Québec, Canada

Posted: Mon May 31, 2021 1:35 pm Post subject:

alamahant wrote:

Have you tried with Clear Linux live cd

https://cdn.download.clearlinux.org/releases/34640/clear/clear-34640-live-desktop.iso

?

I have not (never heard of that one before), but I’m downloading the iso now!

alamahant
Advocate

Joined: 23 Mar 2019
Posts: 3304

Posted: Mon May 31, 2021 1:38 pm Post subject:

Since it is Intel platform optimized you have a better chance for its recognizing your hardware. Please use Fedora Media Writer or Rufus to create the usb stick. _________________

Jaglover
Watchman

Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana

Posted: Mon May 31, 2021 1:46 pm Post subject:

Unless it has some special patch for kernel which is not accepted upstream I doubt it would be any different. If this was my computer the last thing to try would be reset the BIOS to make sure there is no corruption and if this does not help then mobo is the first suspect. Only because I believe Intel does test their CPU’s thoroughly, while Asus may not have that rigorous quality control. My 2¢. _________________ My Gentoo installation notes. Please learn how to denote units correctly!

Black
Tux’s lil’ helper

Joined: 10 Dec 2002
Posts: 147
Location: Québec, Canada

Posted: Mon May 31, 2021 1:55 pm Post subject:

Jaglover wrote:

Is there a BIOS upgrade perhaps for this CPU?

Forgot to answer that one: yes, there was a BIOS update, which I did apply 2 days ago, hoping it would resolve the issue.

I’ll try resetting the BIOS. I also agree that the mobo is suspect. I will need to provide evidence using Windows, ’cause of course they’ll say Linux is not supported. Or I eat the price of a new motherboard and throw this one in the dumpster.

Jaglover
Watchman

Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana

Posted: Mon May 31, 2021 2:08 pm Post subject:

This mobo is still useful for headless purposes, and it will work with add-on graphics. Since this is a new purchase you should not have issues returning it, most sellers wouldn’t dispute it. _________________ My Gentoo installation notes. Please learn how to denote units correctly!

Black
Tux’s lil’ helper

Joined: 10 Dec 2002
Posts: 147
Location: Québec, Canada

Posted: Mon May 31, 2021 4:12 pm Post subject:

I’ve managed to install Windows 10, with the graphic drivers, and it works without any problem. I’ll still try Clear Linux and resetting the BIOS, but it might look like my other option is to get a separate nVidia GPU, which I wanted to avoid in the first place because support is 3 to 5 years; that’s the main issue with my old/current computer, which is now 9 years. The official nVidia drivers no longer support it, and nouveau has its own issue. (Note that I don’t mean to delve into this issue here — I just wanted to voice why I’m trying to avoid nVidia). As for returning the mobo without evidence of defectiveness, I did not purchase it at a big box place, so they’ll retake it but with a restocking fee. I went there because big-box-place sells only pre-made computers with unknown components. Plus they charge you for Windows. Anyway, I’ll report back here once I have more info to provide. Thanks everyone! (But if anyone has anything else to suggest, please do!)

Black
Tux’s lil’ helper

Joined: 10 Dec 2002
Posts: 147
Location: Québec, Canada

Posted: Mon May 31, 2021 4:57 pm Post subject:

As expected, Clear Linux has the same behavior on this system. I also tried resetting the BIOS — no luck.

Jaglover
Watchman

Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana

Posted: Mon May 31, 2021 5:27 pm Post subject:

Can’t recall why I excluded Asus from my shopping list, I remember it had something to do with Windows-only-supported mentality. My personal ban on Asus will stand. You can get AMD graphics, it does not have to be nVidia. _________________ My Gentoo installation notes. Please learn how to denote units correctly!

Black
Tux’s lil’ helper

Joined: 10 Dec 2002
Posts: 147
Location: Québec, Canada

Posted: Mon May 31, 2021 5:30 pm Post subject:

I used to take Asus when I first started building my own PC. 9 years ago I switched to Gigabyte, but I don’t recall why — I thought it was just because I liked it better, but Windows-only support might have been it. I’m banning Asus from now on as well.

Display posts from previous:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Источник

#1 2021-10-10 13:23:08

[solved] boot stuck: i915 drm error

#3 2021-10-10 20:50:43

Re: [solved] boot stuck: i915 drm error

#4 2021-10-10 20:51:53

Re: [solved] boot stuck: i915 drm error

#5 2021-10-10 21:15:55

Re: [solved] boot stuck: i915 drm error

#6 2021-10-11 07:16:17

Re: [solved] boot stuck: i915 drm error

#7 2021-10-11 08:12:22

Re: [solved] boot stuck: i915 drm error

#8 2021-10-11 08:19:40

Re: [solved] boot stuck: i915 drm error

#9 2021-10-11 21:08:34

Re: [solved] boot stuck: i915 drm error

#10 2021-10-11 21:18:38

Re: [solved] boot stuck: i915 drm error

#11 2021-10-11 21:38:03

Re: [solved] boot stuck: i915 drm error

#12 2021-10-12 06:42:52

Re: [solved] boot stuck: i915 drm error

#13 2021-10-12 06:57:07

Re: [solved] boot stuck: i915 drm error

#14 2021-10-12 08:06:24

Re: [solved] boot stuck: i915 drm error

#15 2021-10-12 09:10:36

Re: [solved] boot stuck: i915 drm error

#16 2021-10-12 21:22:10

Re: [solved] boot stuck: i915 drm error

#17 2021-10-12 21:25:36

Re: [solved] boot stuck: i915 drm error

#18 2021-10-12 22:28:11

Re: [solved] boot stuck: i915 drm error

#19 2021-10-13 06:03:09

Re: [solved] boot stuck: i915 drm error

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> perlamut

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> perlamut

perlamut

perlamut