STATUS: FAILED BUILD: 1.9_rc1:f9738ec19d3b2864c0bd71b9bb3418d16e922a12 ENVIRONMENT: NUC(Next Unit of Computing) STEPS TO REPRODUCE: Parse dmesg log and all log files in /var/log for keywords like: "error" , "failed" , "cannot", "can't" etc. Filter out the known and invalid errors or errors that appear in certain situations and need to be ignored. EXPECTED OUTCOME: No errors or fails should be present in logs Actual outcome: Log parser found the following error in xorg.log : [1401508.445] (EE) Failed to load module "fbdev" (module does not exist, 0)
Question. Why is this labeled 1.9_rc1? It should be 1.8_rc1, no?
Interesting, what hardware exactly are you using? We have different nuc, also which driver did load? I checked on the 2 different NUC, bith 32 bit and 64 bit 32bit - DC3217IYE Uses the intel x11 graphics driver 64bit - D54250WYK-IDD also uses the intel x11 graphics driver I can see an attempt to use the fbdev module in both cases, but in each case they load OK [1403838.484] (II) LoadModule: "fbdev" [1403838.484] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [1403838.490] (II) Module fbdev: vendor="X.Org Foundation" [1403838.490] compiled for 1.16.3, module version = 0.4.4 [1403838.490] Module class: X.Org Video Driver [1403838.490] ABI class: X.Org Video Driver, version 18.0 Can you confirm if /var/lib/xorg/modules/drivers has the fbdev_drv.so
Just to confirm, I am using the core-image-sato-sdk images downloaded from: http://yocto-ab-master.jf.intel.com/pub/releases/yocto-1.8.rc1/machine
I used an D54250WYK model on 64bit. In /var/lib the xorg directory does not exist, but it can be found in /usr/lib/. Accordingly, I checked in /usr/lib/xorg/modules/drivers for fbdev_drv.so file and it is missing.
(In reply to comment #4) > I used an D54250WYK model on 64bit. > In /var/lib the xorg directory does not exist, but it can be found in > /usr/lib/. Accordingly, I checked in /usr/lib/xorg/modules/drivers for > fbdev_drv.so file and it is missing. Sorry I meant /usr/lib and I am glad you double checked that. Can you please verify what image and MACHINE target you built / used for doing this test? Again as pointed out in an early comment the BUILD of 1.9_rc1 is not really valid for meta-intel. It's important to give as much information up front about the way the build was configured and the target image that you used.
This was tested on core-image-sato-sdk NUC image, 1.8.rc1 release! http://yocto-ab-master.jf.intel.com/pub/releases/yocto-1.8.rc1/machines/nuc/ meta-intel: f9738ec19d3b2864c0bd71b9bb3418d16e922a12 poky: poky-e4cf20fd7bf4ba044f4156a450ae570aa34aa04f
assigning back to sgw
For the NUC image, it only contains the intel_drv X11 Driver, so it will give Error messages for the other display drivers, these messages are OK, part of the problem with the way this was reported I did not see the complete Xorg log which gave me the impression that there was no successful X11 started. I will ask for more complete log output next time. As we move to depreciate the hardware specific BSPs these issues should go away. For now these messages and there will be more than just fbdev possibly modesetting and vesa can be white listed
Error added to whitelist: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=7a4d72dc18ff4ce5b02684026ba1d564a2ab5c41
Verified on latest master