mikevdh
Posts: 15
Joined: Tue Jan 21, 2014 9:56 pm

startx FATAL: Module g2d_23 not found

Wed Jan 22, 2014 8:26 pm

Hi There!

I'm fairly new to linux and the raspberry. I do have some stuff running like servo's. I just started to read the optical sensor of my mouse(want to use it as a camera) and then i came into a problem.
When i want to start "startx" i just get a black screen with a white dash in the screen. When i look at the message before it gives this black screen it comes with the error "FATAL: Module g2d_23 not found". Does anyone have a idea hor to solve this?

Thanks a million!!

gkreidl
Posts: 5759
Joined: Thu Jan 26, 2012 1:07 pm
Location: Germany

Re: startx FATAL: Module g2d_23 not found

Wed Jan 22, 2014 9:33 pm

That's not the real problem you have: we all get this error message but it's not important.
Minimal Kiosk Browser (kweb)
Slim, fast webkit browser with support for audio+video+playlists+youtube+pdf+download
Optional fullscreen kiosk mode and command interface for embedded applications
Includes omxplayerGUI, an X front end for omxplayer

mikevdh
Posts: 15
Joined: Tue Jan 21, 2014 9:56 pm

Re: startx FATAL: Module g2d_23 not found

Mon Jan 27, 2014 7:53 pm

Is there a way to find what the problem is? Some log file or so?

User avatar
DougieLawson
Posts: 34166
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website

Re: startx FATAL: Module g2d_23 not found

Mon Jan 27, 2014 7:57 pm

mikevdh wrote:Is there a way to find what the problem is? Some log file or so?
Ignore it, it doesn't affect normal operation.
Microprocessor, Raspberry Pi & Arduino Hacker
Mainframe database troubleshooter
MQTT Evangelist
Twitter: @DougieLawson

2012-18: 1B*5, 2B*2, B+, A+, Z, ZW, 3Bs*3, 3B+

Any DMs sent on Twitter will be answered next month.

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 20907
Joined: Sat Jul 30, 2011 7:41 pm

Re: startx FATAL: Module g2d_23 not found

Mon Jan 27, 2014 8:52 pm

mikevdh wrote:Hi There!

I'm fairly new to linux and the raspberry. I do have some stuff running like servo's. I just started to read the optical sensor of my mouse(want to use it as a camera) and then i came into a problem.
When i want to start "startx" i just get a black screen with a white dash in the screen. When i look at the message before it gives this black screen it comes with the error "FATAL: Module g2d_23 not found". Does anyone have a idea hor to solve this?

Thanks a million!!
Check out the log file at

/var/log/Xorg.0.log

But I suspect that you have a broken fbturbo driver - did you try compiling it yourself?
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Please direct all questions to the forum, I do not do support via PM.

ssvb
Posts: 112
Joined: Sat May 19, 2012 6:15 pm

Re: startx FATAL: Module g2d_23 not found

Mon Jan 27, 2014 9:44 pm

mikevdh wrote:it comes with the error "FATAL: Module g2d_23 not found". Does anyone have a idea hor to solve this?
As the others have mentioned, this warning message is harmless. But I admit that it is indeed misleading. 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). This kernel module is expected not to be found on the Raspberry Pi, and the driver can handle this situation quite fine. However the X server itself also spams the log with this error message as a side effect. And I have not decided yet what would be the best way to get rid of it. The support for multiple arm platforms is a relatively new feature of fbturbo. And the messages in the logs may be still somewhat confusing, sorry about this.

As for the black screen problem, that's most definitely some unrelated issue. As the others have already suggested, you can check if the logs contain some other error messages. Or provide a bit more information about your system setup.

User avatar
DougieLawson
Posts: 34166
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website

Re: startx FATAL: Module g2d_23 not found

Mon Jan 27, 2014 11:25 pm

ssvb wrote: And I have not decided yet what would be the best way to get rid of it.
Isn't the easy way to have a dummy module that does nothing. the main() routine simply exits with a zero return (depending on what the interface expects).
Microprocessor, Raspberry Pi & Arduino Hacker
Mainframe database troubleshooter
MQTT Evangelist
Twitter: @DougieLawson

2012-18: 1B*5, 2B*2, B+, A+, Z, ZW, 3Bs*3, 3B+

Any DMs sent on Twitter will be answered next month.

ssvb
Posts: 112
Joined: Sat May 19, 2012 6:15 pm

Re: startx FATAL: Module g2d_23 not found

Tue Jan 28, 2014 9:56 am

DougieLawson wrote:
ssvb wrote: And I have not decided yet what would be the best way to get rid of it.
Isn't the easy way to have a dummy module that does nothing. the main() routine simply exits with a zero return (depending on what the interface expects).
I'm not sure if it's a good idea, it just looks way too roundabout :) The best solution would be to suppress this error message to the console if the xf86LoadKernelModule() function in the X server fails, but this requires changes on the X server side. It is actually a side effect of the X server executing the "modprobe" program to do the module loading. And modprobe happily prints this exact message "FATAL: Module foobar not found" if you try something like "modprobe foobar".

Perhaps we can parse the "Hardware:" field of /proc/cpuinfo, make a guess about what hardware capabilities are really supposed to be available on this particular device and don't scare the users with the 'XYZ is not found' kind of messages in logs unnecessarily.

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 20907
Joined: Sat Jul 30, 2011 7:41 pm

Re: startx FATAL: Module g2d_23 not found

Tue Jan 28, 2014 11:14 am

Add an extra message saying ignore the previous one if on Raspberry Pi? Cheap and cheerful....
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Please direct all questions to the forum, I do not do support via PM.

mikevdh
Posts: 15
Joined: Tue Jan 21, 2014 9:56 pm

Re: startx FATAL: Module g2d_23 not found

Tue Jan 28, 2014 7:57 pm

This is in my log file

[ 59.163]
X.Org X Server 1.12.4
Release Date: 2012-08-27
[ 59.167] X Protocol Version 11, Revision 0
[ 59.169] Build Operating System: Linux 3.2.0-2-mx5 armv7l Debian
[ 59.171] Current Operating System: Linux raspberrypi 3.10.27+ #630 PREEMPT Fri $
[ 59.172] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm270$
[ 59.177] Build Date: 18 December 2013 05:20:52PM
[ 59.178] xorg-server 2:1.12.4-6+deb7u2 (Julien Cristau <[email protected]>)
[ 59.180] Current version of pixman: 0.29.3
[ 59.181] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 59.182] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 59.189] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jan 28 19:51:14 2014
[ 59.200] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 59.212] (==) No Layout section. Using the first Screen section.
[ 59.212] (==) No screen section available. Using defaults.
[ 59.212] (**) |-->Screen "Default Screen Section" (0)
[ 59.213] (**) | |-->Monitor "<default monitor>"
[ 59.215] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 59.215] (**) | |-->Device "Allwinner A10/A13 FBDEV"
[ 59.215] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 59.215] (==) Automatically adding devices
[ 59.216] (==) Automatically enabling devices
[ 59.253] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 59.253] Entry deleted from font path.
[ 59.274] (WW) The directory "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" $
[ 59.275] Entry deleted from font path.
[ 59.275] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 59.275] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 59.275] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 59.275] (II) Loader magic: 0x1aa7a8
[ 59.276] (II) Module ABI versions:
[ 59.276] X.Org ANSI C Emulation: 0.4
[ 59.276] X.Org Video Driver: 12.1
[ 59.276] X.Org XInput driver : 16.0
[ 59.276] X.Org Server Extension : 6.0
[ 59.277] (II) LoadModule: "extmod"
[ 59.319] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 59.332] (II) Module extmod: vendor="X.Org Foundation"
[ 59.332] compiled for 1.12.4, module version = 1.0.0
[ 59.332] Module class: X.Org Server Extension
[ 59.333] ABI class: X.Org Server Extension, version 6.0
[ 59.333] (II) Loading extension SELinux
[ 59.333] (II) Loading extension MIT-SCREEN-SAVER
[ 59.333] (II) Loading extension XFree86-VidModeExtension
[ 59.333] (II) Loading extension XFree86-DGA
[ 59.333] (II) Loading extension DPMS
[ 59.333] (II) Loading extension XVideo
[ 59.334] (II) Loading extension XVideo-MotionCompensation
[ 59.334] (II) Loading extension X-Resource
[ 59.334] (II) LoadModule: "dbe"
[ 59.335] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 59.339] (II) Module dbe: vendor="X.Org Foundation"
[ 59.339] compiled for 1.12.4, module version = 1.0.0
[ 59.340] Module class: X.Org Server Extension
[ 59.340] ABI class: X.Org Server Extension, version 6.0
[ 59.340] ABI class: X.Org Server Extension, version 6.0
[ 59.340] (II) Loading extension DOUBLE-BUFFER
[ 59.340] (II) LoadModule: "glx"
[ 59.342] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 59.364] (II) Module glx: vendor="X.Org Foundation"
[ 59.364] compiled for 1.12.4, module version = 1.0.0
[ 59.364] ABI class: X.Org Server Extension, version 6.0
[ 59.364] (==) AIGLX enabled
[ 59.365] (II) Loading extension GLX
[ 59.365] (II) LoadModule: "record"
[ 59.366] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 59.370] (II) Module record: vendor="X.Org Foundation"
[ 59.371] compiled for 1.12.4, module version = 1.13.0
[ 59.371] Module class: X.Org Server Extension
[ 59.371] ABI class: X.Org Server Extension, version 6.0
[ 59.371] (II) Loading extension RECORD
[ 59.371] (II) LoadModule: "dri"
[ 59.373] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 59.383] (II) Module dri: vendor="X.Org Foundation"
[ 59.384] compiled for 1.12.4, module version = 1.0.0
[ 59.384] ABI class: X.Org Server Extension, version 6.0
[ 59.384] (II) Loading extension XFree86-DRI
[ 59.384] (II) LoadModule: "dri2"
[ 59.386] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 59.390] (II) Module dri2: vendor="X.Org Foundation"
[ 59.390] compiled for 1.12.4, module version = 1.2.0
[ 59.390] ABI class: X.Org Server Extension, version 6.0
[ 59.390] (II) Loading extension DRI2
[ 59.391] (II) LoadModule: "fbturbo"
[ 59.391] (II) Loading /usr/lib/xorg/modules/drivers/fbturbo_drv.so
[ 59.399] (II) Module fbturbo: vendor="X.Org Foundation"
[ 59.399] compiled for 1.12.4, module version = 0.5.1
[ 59.399] Module class: X.Org Video Driver
[ 59.399] ABI class: X.Org Video Driver, version 12.1
[ 59.400] (II) FBTURBO: driver for framebuffer: fbturbo
[ 59.401] (--) using VT number 7

[ 59.409] (WW) Falling back to old probe method for fbturbo
[ 59.409] (II) Loading sub module "fbdevhw"
[ 59.409] (II) LoadModule: "fbdevhw"
[ 59.411] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 59.414] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 59.414] compiled for 1.12.4, module version = 0.0.2
[ 59.414] ABI class: X.Org Video Driver, version 12.1
[ 59.415] (II) FBTURBO(0): using /dev/fb0
[ 59.415] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 59.416] (II) FBTURBO(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 16/16
[ 59.416] (==) FBTURBO(0): Depth 16, (==) framebuffer bpp 16
[ 59.416] (==) FBTURBO(0): RGB weight 565
[ 59.416] (==) FBTURBO(0): Default visual is TrueColor
[ 59.417] (==) FBTURBO(0): Using gamma correction (1.0, 1.0, 1.0)
[ 59.417] (II) FBTURBO(0): hardware: BCM2708 FB (video memory: 533kB)
[ 59.417] (**) FBTURBO(0): Option "fbdev" "/dev/fb0"
[ 59.417] (**) FBTURBO(0): Option "SwapbuffersWait" "true"
[ 59.419] (II) FBTURBO(0): processor: ARM1176
[ 59.419] (II) FBTURBO(0): checking modes against framebuffer device...
[ 59.419] (II) FBTURBO(0): checking modes against monitor...
[ 59.424] (--) FBTURBO(0): Virtual size is 656x416 (pitch 656)
[ 59.424] (**) FBTURBO(0): Built-in mode "current"
[ 59.424] (==) FBTURBO(0): DPI set to (96, 96)
[ 59.424] (II) Loading sub module "fb"
[ 59.424] (II) LoadModule: "fb"
[ 59.426] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 59.439] (II) Module fb: vendor="X.Org Foundation"
[ 59.439] compiled for 1.12.4, module version = 1.0.0
[ 59.440] ABI class: X.Org ANSI C Emulation, version 0.4
[ 59.441] (EE) FBTURBO(0): FBIOBLANK: Operation not permitted
[ 59.462] (II) FBTURBO(0): using backing store heuristics
[ 59.479] (II) FBTURBO(0): can't load 'g2d_23' kernel module
[ 59.480] (II) FBTURBO(0): failed to enable the use of sunxi display controller

ssvb
Posts: 112
Joined: Sat May 19, 2012 6:15 pm

Re: startx FATAL: Module g2d_23 not found

Tue Jan 28, 2014 8:11 pm

mikevdh wrote:This is in my log file

[ 59.416] (==) FBTURBO(0): Depth 16, (==) framebuffer bpp 16
[ 59.416] (==) FBTURBO(0): RGB weight 565
[ 59.416] (==) FBTURBO(0): Default visual is TrueColor
[ 59.417] (==) FBTURBO(0): Using gamma correction (1.0, 1.0, 1.0)
[ 59.417] (II) FBTURBO(0): hardware: BCM2708 FB (video memory: 533kB)
[ 59.417] (**) FBTURBO(0): Option "fbdev" "/dev/fb0"
[ 59.417] (**) FBTURBO(0): Option "SwapbuffersWait" "true"
[ 59.419] (II) FBTURBO(0): processor: ARM1176
[ 59.419] (II) FBTURBO(0): checking modes against framebuffer device...
[ 59.419] (II) FBTURBO(0): checking modes against monitor...
[ 59.424] (--) FBTURBO(0): Virtual size is 656x416 (pitch 656)
The 656x416 screen resolution seems to be rather unusual. What kind of monitor do you use and how do you connect it to the Raspberry Pi? Do you have a proper framebuffer console before running startx? Something like the penguin logo in the top left corner and text messages scrolling on the screen when the system is booting up.

User avatar
DougieLawson
Posts: 34166
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website

Re: startx FATAL: Module g2d_23 not found

Tue Jan 28, 2014 9:28 pm

jamesh wrote:Add an extra message saying ignore the previous one if on Raspberry Pi? Cheap and cheerful....
LOL
It won't be the first time that option has been used rather than fixing the real bug.
Microprocessor, Raspberry Pi & Arduino Hacker
Mainframe database troubleshooter
MQTT Evangelist
Twitter: @DougieLawson

2012-18: 1B*5, 2B*2, B+, A+, Z, ZW, 3Bs*3, 3B+

Any DMs sent on Twitter will be answered next month.

mikevdh
Posts: 15
Joined: Tue Jan 21, 2014 9:56 pm

Re: startx FATAL: Module g2d_23 not found

Wed Jan 29, 2014 7:32 pm

ssvb wrote:
mikevdh wrote:This is in my log file

[ 59.416] (==) FBTURBO(0): Depth 16, (==) framebuffer bpp 16
[ 59.416] (==) FBTURBO(0): RGB weight 565
[ 59.416] (==) FBTURBO(0): Default visual is TrueColor
[ 59.417] (==) FBTURBO(0): Using gamma correction (1.0, 1.0, 1.0)
[ 59.417] (II) FBTURBO(0): hardware: BCM2708 FB (video memory: 533kB)
[ 59.417] (**) FBTURBO(0): Option "fbdev" "/dev/fb0"
[ 59.417] (**) FBTURBO(0): Option "SwapbuffersWait" "true"
[ 59.419] (II) FBTURBO(0): processor: ARM1176
[ 59.419] (II) FBTURBO(0): checking modes against framebuffer device...
[ 59.419] (II) FBTURBO(0): checking modes against monitor...
[ 59.424] (--) FBTURBO(0): Virtual size is 656x416 (pitch 656)
The 656x416 screen resolution seems to be rather unusual. What kind of monitor do you use and how do you connect it to the Raspberry Pi? Do you have a proper framebuffer console before running startx? Something like the penguin logo in the top left corner and text messages scrolling on the screen when the system is booting up.
i had a monitor connected, normal one hdmi input. Now i have my mac connected and use ssh and thats works but not with startx. The startx problem happens with a monitor or when i have it connected with my mac over ssh. I tested my ssh connection with xeyes etc and that works.

ssvb
Posts: 112
Joined: Sat May 19, 2012 6:15 pm

Re: startx FATAL: Module g2d_23 not found

Wed Jan 29, 2014 8:42 pm

mikevdh wrote:i had a monitor connected, normal one hdmi input. Now i have my mac connected and use ssh and thats works but not with startx. The startx problem happens with a monitor or when i have it connected with my mac over ssh. I tested my ssh connection with xeyes etc and that works.
Before trying anything with startx, it is a good idea to make sure that the monitor is correctly detected and usable with the framebuffer console. If I understand you correctly, you never had it working even in the framebuffer console, but only connected to the board remotely using ssh. My guess is that your Raspberry Pi gets somehow confused by the EDID data from your monitor.

Please try to check http://elinux.org/RPiconfig#Video_mode_options and tweak the 'config.txt' file on the sdcard until you get some proper picture on screen after the board is booted. And also try to make sure that it is using the correct native resolution of your monitor. Your monitor should be able to show the information about the current video mode somewhere in its OSD menu. And on the Raspberry Pi, you can run 'fbset' command (even in the ssh session) to get the information about the current screen resolution as seen from the Raspberry Pi side. These two should normally match.

After you get the basic framebuffer working, the X server should become usable too. Good luck.

rocketshape
Posts: 1
Joined: Wed Mar 19, 2014 10:38 am

Re: startx FATAL: Module g2d_23 not found

Wed Mar 19, 2014 10:40 am

hey i just got the same error on starting the raspberry.
fixed it by using an other usb-charger - maybe there wasn't enough power to keep the driver running...

chrisfcarroll
Posts: 2
Joined: Tue Apr 15, 2014 10:29 am

Re: startx FATAL: Module g2d_23 not found

Tue Apr 15, 2014 10:38 am

If you're using x remotely over ssh then you don't want to run startx. You want to
1) Have an X Server running on your Mac or PC
2)

Code: Select all

ssh -X ipaddress -l pi
And then you can e.g.

Code: Select all

midori &
from the command line.

texy
Forum Moderator
Forum Moderator
Posts: 5146
Joined: Sat Mar 03, 2012 10:59 am
Location: Berkshire, England

Re: startx FATAL: Module g2d_23 not found

Tue Apr 15, 2014 3:00 pm

That is not related to the message. g2d_23 not found is due to an allwinner drivers issue, but is not required or used by the Pi, so just ignore it.

regards,
Texy
Various male/female 40- and 26-way GPIO header for sale here ( IDEAL FOR YOUR PiZero ):
https://www.raspberrypi.org/forums/viewtopic.php?f=93&t=147682#p971555

GreatLeader_Technus
Posts: 15
Joined: Thu May 29, 2014 7:43 am

Re: startx FATAL: Module g2d_23 not found

Thu May 29, 2014 8:25 pm

So its a power deficiency problem? Here I thought it was that I destroyed my PI or the OS was corrupted..... :lol:

anandjbhatt
Posts: 1
Joined: Sun Mar 08, 2015 7:24 am

Re: startx FATAL: Module g2d_23 not found

Sun Mar 08, 2015 11:35 am

I got the same error when i connect my raspberry pi with windows and connect it through raspberry pi...Above given solution i can not find out the solution...i get only command window on raspberry...could not get the desktop window using startx...
The below message i got when i logged in.


[email protected] ~ $ startx


X.Org X Server 1.12.4
Release Date: 2012-08-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-2-mx5 armv7l Debian
Current Operating System: Linux raspberrypi 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015 armv7l
Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=592 bcm2708_fb.fbheight=448 bcm2709.boardrev=0xa21041 bcm2709.serial=0x543333e2 smsc95xx.macaddr=B8:27:EB:33:33:E2 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p6 rootfstype=ext4 elevator=deadline rootwait
Build Date: 11 February 2015 09:31:17PM
xorg-server 2:1.12.4-6+deb7u6 (Julien Cristau <[email protected]>)
Current version of pixman: 0.33.1
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 16 20:20:42 2015
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
FATAL: Module g2d_23 not found.




Please help me.
Thanks in advance.

texy
Forum Moderator
Forum Moderator
Posts: 5146
Joined: Sat Mar 03, 2012 10:59 am
Location: Berkshire, England

Re: startx FATAL: Module g2d_23 not found

Sun Mar 08, 2015 1:54 pm

anandjbhatt wrote:I got the same error when i connect my raspberry pi with windows and connect it through raspberry pi...Above given solution i can not find out the solution...i get only command window on raspberry...could not get the desktop window using startx...
The below message i got when i logged in.


[email protected] ~ $ startx


X.Org X Server 1.12.4
Release Date: 2012-08-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-2-mx5 armv7l Debian
Current Operating System: Linux raspberrypi 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015 armv7l
Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=592 bcm2708_fb.fbheight=448 bcm2709.boardrev=0xa21041 bcm2709.serial=0x543333e2 smsc95xx.macaddr=B8:27:EB:33:33:E2 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p6 rootfstype=ext4 elevator=deadline rootwait
Build Date: 11 February 2015 09:31:17PM
xorg-server 2:1.12.4-6+deb7u6 (Julien Cristau <[email protected]>)
Current version of pixman: 0.33.1
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 16 20:20:42 2015
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
FATAL: Module g2d_23 not found.




Please help me.
Thanks in advance.
Hi,
as explained above, please ignore the 2gd error message - it is NOT stopping X from running, just ignore it.
Is the reason why you cannot see X Windows is that you are SSH'ing in to the Pi, because that is only for CLI interface, not X.
You will need to use VNC, eg tightvnc, in order to see the X desktop remotely.
Hope this helps,
Texy
Various male/female 40- and 26-way GPIO header for sale here ( IDEAL FOR YOUR PiZero ):
https://www.raspberrypi.org/forums/viewtopic.php?f=93&t=147682#p971555

natkuhn
Posts: 3
Joined: Tue Mar 10, 2015 2:06 am

Re: startx FATAL: Module g2d_23 not found

Tue Mar 10, 2015 12:14 pm

I know that this is a cosmetic issue, but for anyone who is interested, the “FATAL: Module g2d_23 not found” error is solved on https://learn.adafruit.com/adafruit-pit ... rry-pi/faq. I was able to fix it using their suggestion:

Code: Select all

sudo mv /usr/share/X11/xorg.conf.d/99-fbturbo.conf ~

santhoshm
Posts: 1
Joined: Sat Apr 04, 2015 10:51 am

Re: startx FATAL: Module g2d_23 not found

Sat Apr 04, 2015 11:14 am

Hello All,

I am new to Rapsberry Pi forum.
I had similar problem in opening the GUI of Pi from another remote machine.

It worked for me with the below workaround.,

On the raspberry :

Enable remote access modifying /etc/lightdm/lightdm.conf

[XDMCPServer]
enabled=true


restart lightdm
sudo service lightdm restart

On the Remote Machine :

Establish session with Pi using the below command,
ssh -X [email protected]<server_ip>

After Successful Login, invoke 'startlxde-pi',
][email protected]~$ startlxde-pi

And there you go, Rapberry Pi GUI will be available for you.
Please Find screen shot attached.

Cheers,
Santhosh M
Attachments
Screenshot_Raspberry_RemoteGUI.jpg
Raspberry Pi GUI
Screenshot_Raspberry_RemoteGUI.jpg (32.02 KiB) Viewed 76405 times

buzibal
Posts: 1
Joined: Sun Apr 12, 2015 4:59 pm

Re: startx FATAL: Module g2d_23 not found

Sun Apr 12, 2015 5:26 pm

Thnx for the workaround. startx worked not. What is the difference?

ravi.zombie
Posts: 1
Joined: Tue Feb 25, 2014 10:30 pm
Contact: ICQ

Re: startx FATAL: Module g2d_23 not found

Tue Apr 28, 2015 7:10 am

I had faced the similar issue, but my case was different(may be)

Config: raspberry pi B 2
sd card : 8GB

Reason: I later found out that the /home/pi directory was full 100% (almost 3GB owing to storage of some media files on desktop, while doing a camera prototype and had to click more videos and pics)

Solution: I deleted all the media files and freed up the space.
> startx # worked just fine after that.

may be could see if there is enough space for creation of other files in the SD card.

pintushaw
Posts: 1
Joined: Thu Aug 20, 2015 6:54 am

Re: startx FATAL: Module g2d_23 not found

Thu Aug 20, 2015 6:56 am

Thanx. I had same problem. Removing the download archives solved the problems.
eg: sudo apt-get clean.

Return to “Raspbian”