New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#3274 - An error is reported at each start-up phase #8146
Comments
Same problem with 21.02.1
|
Same problem with 22.03.3
|
In debian all that stuff is in the I would get the firmware-linux-nonfree deb file and unpack it (dpkg -x) then find the file being complained about and put it in Multiple reports of the firmware from the link in the error message don't actually work since they are "raw" without some header they need for the kernel loader. The debian files have this header added so they actually work. As far as I could glean from 10 minutes on Google... If it has license issues it will never be in a release build, that would be breaking the license terms. End user obtaining the correct file and placing it where it needs to be ironically does not break the license terms (it always has to be a manual extra step for the end user, even if it's in a package somewhere). It might also work to drop the file(s) on your installation to the proper location |
Tried to download from debian sid package, this does not help to get rid of this messages
|
Suspect something with overlay not being up before hotplug tries to load the firmware, thus putting it on the writable part of the filesystem may not provide it early enough. Therefore it may have to be built into the readonly section of the image using the Similar to having the firmware in initrd on a normal linux distro vs on some filesystem mounted later (in this case not a separate mount but the overlay mount). Those can have the same sort of problems except systemd/udev might re-run some hotplug hooks after later mounts to smooth over the problem. Does it work if you rmmod/insmod after fully booted and the overlay is mounted? Sometimes i915 doesn't like to unload and reload after boot depending what's using it, or for other reasons. If so you could then put the rmmod/insmod into the startup commands (init) script which runs after overlay is ready as a workaround to avoid having to compile a custom image. |
I have x86_64 ext4 efi combined image, so as AFAIK there is no readable\writeable parts.
lsmod / rmmod / insmod / modprobe says there is no such module named i915 - what I am doing wrong?
|
I see it fail twice, once at 3.4 seconds and again when it would attempt to use it at power management timeout (~60s). I doubt it's trying a load the second time, only saying it's not there from 3.4s attempt. Not sure why it's not an apparent module. |
KLGIT886:
1.Error log:
[ 63.368179] i915 0000:00:02.0: Failed to load DMC firmware i915/glk_dmc_ver1_04.bin. Disabling runtime power management.
[ 63.379745] i915 0000:00:02.0: DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
2.Problem:Sometimes the power is suddenly cut off and the machine crashes
3.System information:
Intel(R) Celeron(R) J4105 CPU @ 1.50GHz : 4 Core 4 Thread
OpenWrt R20.7.20 / LuCI Master (git-20.191.45716-b73d3a4)
4.I tried to use the graphics driver to the kernel.The mistake did not disappear.In addition, I swiped in the latest firmware compiled by others.The problem remains
I tried to upgrade the kernel to 5.4.56, which did not solve the problem.Please help me
The text was updated successfully, but these errors were encountered: