(II) Module glx: vendor="X.Org Foundation" (II) Loading /usr/lib/xorg/modules/extensions/libglx.so (II) Module dbe: vendor="X.Org Foundation" (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so (II) Loading extension XVideo-MotionCompensation (II) Loading extension XFree86-VidModeExtension ABI class: X.Org Server Extension, version 6.0 compiled for 1.12.4, module version = 1.0.0 (II) Module extmod: vendor="X.Org Foundation" (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so If no devices become available, reconfigure udev or disable AutoAddDevices. (II) The server relies on udev to provide the list of input devices. (=) ModulePath set to "/usr/lib/xorg/modules" (WW) The directory "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" $ (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. (=) No monitor specified for screen "Default Screen Section". (=) No device specified for screen "Default Screen Section". (**) |->Screen "Default Screen Section" (0) (=) Using system config directory "/usr/share/X11/" (WW) warning, (EE) error, (NI) not implemented, (?) unknown. (++) from command line, (!!) notice, (II) informational,
Markers: (-) probed, (**) from config file, (=) default setting, To make sure that you have the latest version. Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm270$ Current Operating System: Linux raspberrypi 3.10.27+ #630 PREEMPT Fri $ Build Operating System: Linux 3.2.0-2-mx5 armv7l Debian Or provide a bit more information about your system setup. As the others have already suggested, you can check if the logs contain some other error messages. And the messages in the logs may be still somewhat confusing, sorry about this.Īs for the black screen problem, that's most definitely some unrelated issue. The support for multiple arm platforms is a relatively new feature of fbturbo. And I have not decided yet what would be the best way to get rid of it. However the X server itself also spams the log with this error message as a side effect.
#Raspberry pi startx command not found driver
This kernel module is expected not to be found on the Raspberry Pi, and the driver can handle this situation quite fine. The point is that the fbturbo driver just asks the X server to attempt loading the g2d_23 kernel module (2d acceleration on allwinner chips, which are also supported by the fbturbo driver). But I admit that it is indeed misleading. Does anyone have a idea hor to solve this?Īs the others have mentioned, this warning message is harmless. Mikevdh wrote:it comes with the error "FATAL: Module g2d_23 not found".
0 kommentar(er)
