Central error: Fatal server error: *********************** [ 14214.335] (WW) Falling back to old probe method for fbdev [ 14214.336] (II) Loading sub module fbdevhw [ 14214.336] (II) LoadModule: fbdevhw [ 14214.337] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so [ 14214.375] (II) Module fbdevhw: vendor=X.Org Foundation [ 14214.375] compiled for 1.15.1, module version = 0.0.2 [ 14214.376] ABI class: X.Org Video Driver, version 15.0 [ 14214.376] (EE) open /dev/fb0: No such file or directory [ 14214.377] (EE) No devices detected. [ 14214.377] (EE) Fatal server error: [ 14214.378] (EE) no screens found(EE) [ 14214.387] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 14214.388] (EE) Please also check the log file at /var/log/Xorg.0.log for additional information. [ 14214.389] (EE) *********************** Note: these machines are mounted in our hardware rack and have no monitor attached.
The ERL has no display, so running an image with Xorg on it doesn't make sense. Using an image without the i965 driver on a MinnowBoardMax, also doesn't make sense. Can you clarify what error you are reporting here? Which BSP? Which image? etc.
Hello Darren, This error is catched by the log parser we have when doing automated testing and I want to improve our filters so that I whitelist the irrelevant messages, that is why I log them as bugs. The parser cought "Fatal server error" in Xorg log for Minnowboard and Edgerouter BSPs, commit 1.7.RC4 (ccf5a4d2342c4fd40e4e0b332ea7e34e0bf175d4.)
Without specific image and BSP information, we can't move forward. It's always best to provide as much context as possible in the bug since people, not just me, reading the bug (this is a public bz) will not know what you are doing in QA. It also saves on the back and forth. It appears you are running sato-sdk on the ERL, that doesn't make sense. Either whitelist the Xorg errors, or don't run an Xorg image on the router. You said MinnowBoard, did you mean MinnowBoard or MinnowBoard Max? (the naming can be confusing unfortunately - even if you got it right :-) Which BSP?
Hello Darren, The machines are EdgeRouter and MinnowBoard. Links: http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7.rc4/machines/edgerouter/ http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7.rc4/machines/minnow/ Files used by test-remote-image script are the kernel bin file, manifest and tar.gz. Image type core-image-sato-sdk for both, if you think that is the cause of the errors then I will whitelist them so they don't show up on our next run.
In my opinion, building sato for ERL doesn't make any sense at all. Testing it, less so. For minnow, this is a problem. That build should boot to X using EFIFB and fbdev. I suggest: * Whitelisting this error for the Edge Router Light * Renaming this bug to be Minnow specific
I agree with Darren's last comment. This isn't valid for the ERL, and make it minnowmax specific. Once that is done, you'll also need to change the assignee, since I have no minnow* boards here.
Changing the name to Minnow only.
Nitin: who handles the Minnow board bugs ?
(In reply to comment #8) > Nitin: who handles the Minnow board bugs ? That would be me - or at least, they get assigned to me :-)
So to clarify, is this reported against minnowboard max or against minnow (v1)? If minnowboardmax, you should be using intel-corei7-64, not minnow. If minnow (v1), I believe this should work for fb even without a screen. Please verify which hardware and BSP we are reporting here. Is the log shared in the opening report from this hardware?
Hello Darren, The board is Minnowboard v1, and BSP core-image-sato-sdk-minnow.
MinnowBoard v1 has reached new feature EOL, FW development is done as are new hardware features. If you feel EXCEEDINGLY strongly about an issue please re-open it for discussion but be aware that we are recommending individuals migrate to the MAX platform.