| Summary: | Errors in Xorg log: (EE) Failed to load module "modesetting" for distro-less build | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Stefan Stanacar <sstncr> | ||||
| Component: | graphics | Assignee: | Laurentiu Palcu <laurentiu.palcu> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | Medium+ | CC: | meta.mr.watcher, meta.watcher, ross.burton, sgw | ||||
| Version: | 1.6 | ||||||
| Target Milestone: | 1.6 | ||||||
| Hardware: | x86 | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||
| Attachments: |
|
||||||
Tested with latest, on a Ubuntu 12.04 machine and this cannot be reproduced. Please confirm that this is still reproducible on Fedora 19. Yup it is. openembedded-core revision used is master:1dbd65b4d14319e784a66776c1e9943d0179d3ee Tested a qemuarm core-image-sato image built from the same commit in a Fedora 19 running in a virtual machine. The image booted in graphics mode just fine... I compared the Xorg.0.log file with the one attached to this bug and the differences are irrelevant. The modesetting error appears in the log too but it doesn't affect the image booting into graphics mode. At this point, I have no other data to proceed further... The issue might be host related but it's just a supposition. Oh wait, I never said that graphics mode doesn't work. X starts just fine, it's just that error message about modesetting never appears in Xorg.log in poky builds. At this point it does look like a host issue (given that the ABs are all F19 and my build was F19 and nobody else reported this). Looking at the NUC Xorg log I have to hand, X will attempt to autoload fbdev, modesetting and intel drivers on Intel HW. If those don't exist you'll get warnings. I suspect we can just whitelist these... (need to replicate on further hardware to verify that's the full pattern) So the poky qemuarm image I grabbed from the autobuilder has a xorg.conf, whereas the oe-core qemuarm log you provided doesn't. Two questions: 1) why this file is in one but not the other, as it's part of oe-core 2) should we whitelist this error as the normal autoprobing behaviour is fine, and that error should really be a warning. Root-caused this due to FILESOVERRIDES containing an empty element. http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=ross/override&id=f9124cbf0fe6459d427cbc2e233265eac7b951cc is a potential fix. An alternative solution was taken where DISTRO="" becomes "nodistro" thus the overrides don't get messed up. Integrated in oe-core b7279f99639774674da806d37d252f388f33055f. Marked as Verified. |
Created attachment 1607 [details] Xorg.0.log Build Configuration: BB_VERSION = "1.21.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Fedora-19" TARGET_SYS = "arm-oe-linux-gnueabi" MACHINE = "qemuarm" DISTRO_VERSION = "oe-core.0" TUNE_FEATURES = "armv5 thumb dsp" TARGET_FPU = "soft" meta = "master:0636093711547957a8f5b25322bd3e0da367cfc4" - build qemuarm core-image-sato from openembedded-core master (with no distro set) - boot image - check /var/log/Xorg.0.log root@qemuarm:~# grep '(EE)' /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [679480.849] (EE) Failed to load module "modesetting" (module does not exist, 0) Log attached. The same image config with DISTRO="poky" doesn't have the error message in the log.