Bug 6167 - Crownbay: Failed to load module "fbdev" (module does not exist, 0)
Summary: Crownbay: Failed to load module "fbdev" (module does not exist, 0)
Status: RESOLVED WORKSFORME
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-intel (show other bugs)
Version: 1.6
Hardware: x86 Multiple
: Low normal
Target Milestone: Future
Assignee: Nitin Kamble
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-04-16 12:03 UTC by Stoicescu Cornel
Modified: 2014-04-26 02:30 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Regression (Used to work)
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stoicescu Cornel 2014-04-16 12:03:14 UTC 
Tested with 
meta-intel: db84acfc8d9ed8dccd4a79de39fee337bc729662
poky daisy: a0958261265049904fd78a2ba0198d46e5e65ea9

Using core-image-sato-sdk-crownbay-noemgd.

The following errors are reported in Xorg.log:

| [1317540.050] (EE) Failed to load module "fbdev" (module does not exist, 0)
| [1317541.387] (EE) AIGLX: reverting to software rendering
| [1317541.387] (EE) AIGLX error: dlopen of /usr/lib/dri/swrast_dri32;52;0M35;52;0M.so failed (/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
| [1317541.387] (EE) GLX: could not load software renderer


Note that /usr/lib/dri/swrast_dri.so indeed does not exist (I found a similar issue some time ago where the file existed but the error was the same: bug 1797)
Comment 1 Darren Hart 2014-04-16 23:36:16 UTC 
Tom, this looks to be either that X is using vesa instead and fbdev is just being tried and failing as expected - or - mesa/X aren't including the right packages for the noemgd version.
Comment 2 Tom Zanussi 2014-04-18 20:12:03 UTC 
Yeah, X isn't coming up, looks to be a BSP problem, assigning to maintainer.
Comment 3 Nitin Kamble 2014-04-26 02:30:16 UTC 
This issue is not happening anymore.