You are not logged in.
EDIT: Solved at last!
Added "initcall_blacklist=simpledrm_platform_driver_init"
To kernel parameters
Hardware: chromebook 3100 2 in 1
CPU is N4000
iGPU(only): UHD Graphics 600
No dGPU
Full uefi rom is flashed(sea bios)
After I updated to kernel 6.10 and rebooted the boot process hangs for a while on
Load/Save RF Kill Switch StatusBefore completely stopping on
Reached target Bluetooth SupportI can boot successfully by setting nomodeset
However this results in a significant decline in graphical performance along with not being able to adjust resolution or brightness
Is there anything I can do?
EDIT: here is a pastebin of dmesg https://0x0.st/Xf3h.txt
EDIT2: I updated firmware/bios to no avail
Last edited by animated (2024-07-30 22:53:18)
Offline
do you have dmesg/journalctl output?
edit: i think i found a related issue: https://www.linuxquestions.org/question … 175702697/
Last edited by Wheatley1901 (2024-07-29 03:18:40)
Offline
do you have dmesg/journalctl output?
Yes, dmesg is here https://0x0.st/Xf3h.txt
And for that related issue, I do not have a spare linux ISO flashed at the moment to try it, but my dmesg showed a repeating error at the end
sof-audio-pci-intel-apl 0000:00:0e.0: ASoC: error at snd_soc_dai_hw_params on iDisp2 Pin: -22Offline
odd, I don't think i have any idea of what's going on here, oops
Offline
Have you tried downgrading to an older kernel version to see if the issue goes away? e.g. 6.9.10.
If you haven't cleared your pacman cache, you should still have a copy of older versions in /var/cache/pacman/pkg/ that you can install with pacman -U
Ryzen 7 9850X3D | AMD 7800XT | KDE Plasma
Offline
Have you tried downgrading to an older kernel version to see if the issue goes away? e.g. 6.9.10.
This works, but is there a better way? This just seems like such a band aid fix, should I report this as a bug somewhere?
Offline
I seem to be having a similar issue. After updating, I get stuck when booting. In my case it stops with "Bluetooth: hci0 Firmware Version: ...". Disabling bluetooth via `sudo systemctl disable bluetooth.service` helped in my case.
Offline
Edit: @animated
Boot w/o nomodeset, reboot w/ the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) (you'll have to enable it w/ the kernel commandline parameter, use the entire REISUB sequence) or by frenetically pressing ctrl+alt+del or a SHORT push on the power button.
Then boot w/ nomodeset and from there please post your complete system journal for the previous boot:
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st and also the output of "lspci -nn"
i915 doesn't even show up in your dmesg
Last edited by seth (2024-07-30 12:23:58)
Online
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.stand also the output of "lspci -nn"
i915 doesn't even show up in your dmesg
I waited 15 minutes on this boot before repeatedly pressing the power button
https://0x0.st/XOoF.txt
lspci -nn output here
https://0x0.st/XOHq.txt
Offline
Jul 30 16:02:40 AdmiralArAlaniARCH kernel: pci 0000:00:02.0: [8086:3185] type 00 class 0x038000 PCIe Root Complex Integrated Endpoint
Jul 30 16:02:40 AdmiralArAlaniARCH kernel: pci 0000:00:02.0: BAR 0 [mem 0x90000000-0x90ffffff 64bit]
Jul 30 16:02:40 AdmiralArAlaniARCH kernel: pci 0000:00:02.0: BAR 2 [mem 0x80000000-0x8fffffff 64bit pref]
Jul 30 16:02:40 AdmiralArAlaniARCH kernel: pci 0000:00:02.0: BAR 4 [io 0x1000-0x103f]Chip is there, but still no sign of the i915 module, but
Jul 30 16:02:40 AdmiralArAlaniARCH kernel: [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0
Jul 30 16:02:40 AdmiralArAlaniARCH kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
Jul 30 16:02:43 AdmiralArAlaniARCH kernel: sysfs: cannot create duplicate filename '/bus/platform/devices/simple-framebuffer.0'Try to add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters and if that doesn't work, from the "nomodeset" boot try to "modprobe -v i915" and look for errors.
Edit: if there're no errors check "lspci -k" to see whether the module bound to the device.
Last edited by seth (2024-07-30 21:43:25)
Online
Try to add "initcall_blacklist=simpledrm_platform_driver_init"
This did the trick, thank you for the knowledge and the speedy response.
Edit: you have solved both of my two forum posts on here, kudos!
Last edited by animated (2024-07-30 22:57:09)
Offline
What does the journal now look like? Does i915 now show up?
You probably want to add it to the initramfs.
The collision happened because of
Jul 30 16:02:43 AdmiralArAlaniARCH kernel: coreboot: could not register framebuffer
Jul 30 16:02:43 AdmiralArAlaniARCH kernel: framebuffer coreboot8: probe with driver framebuffer failed with error -17the framebuffer_coreboot module
=> We actually had this before https://bbs.archlinux.org/viewtopic.php?id=295923
Online