[SOLVED] Two problems with X

Post Reply
magnum_pi
Posts: 198
Joined: Tue Mar 05, 2013 6:37 am
languages_spoken: English, Japanese, French, Irish
ODROIDs: U2, X2, XU, U3
Contact:

[SOLVED] Two problems with X

Unread post by magnum_pi » Tue Dec 23, 2014 10:59 am

When I got my C1 + Linux emmc, X was working fine. Then I ran the odroid utility and selected the 'Rebuild xorg DDX' option as part of a general update. Afterwards, X stopped working. The X log contained:

Code: Select all

[  2597.946] (WW) Falling back to old probe method for armsoc
[  2597.946] (II) No BusID or DriverName specified - opening /dev/dri/card0
[  2597.946] (II) Got BusID platform:mali_drm:00
[  2597.947] (II) Opened DRM
[  2597.947] (II)    DeviceName is [/dev/dri/card0]
[  2597.947] (II)    bus_id is [platform:mali_drm:00]
[  2597.947] (II)    DriverName is [mali_drm]
[  2597.947] (II)    version is [2.1.1]
[  2597.947] (II) Screen:0,  CRTC:-1
[  2597.947] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[  2597.947] (II) ARMSOC(0): Creating default Display subsection in Screen section
        "Default Screen" for depth/fbbpp 24/32
[  2597.947] (**) ARMSOC(0): Depth 24, (--) framebuffer bpp 32
[  2597.947] (==) ARMSOC(0): RGB weight 888
[  2597.947] (==) ARMSOC(0): Using gamma correction (1.0, 1.0, 1.0)
[  2597.947] (==) ARMSOC(0): Default visual is TrueColor
[  2597.947] (II) No BusID or DriverName specified - opening /dev/dri/card0
[  2597.948] (II) Got BusID platform:mali_drm:00
[  2597.948] (II) Opened DRM
[  2597.948] (II)    DeviceName is [/dev/dri/card0]
[  2597.948] (II)    bus_id is [platform:mali_drm:00]
[  2597.948] (II)    DriverName is [mali_drm]
[  2597.948] (II)    version is [2.1.1]
[  2597.948] (II) ARMSOC(0): Chipset: Mali
[  2597.948] (**) ARMSOC(0): Option "Debug" "false"
[  2597.948] (II) ARMSOC(0): Buffer Flipping is Enabled
[  2597.948] (II) ARMSOC(0): Setting the video modes ...
[  2597.948] (EE) ARMSOC(0): ERROR: Cannot get KMS resources
[  2597.949] (II) UnloadModule: "armsoc"
[  2597.949] (EE) Screen(s) found, but none have a usable configuration.
[  2597.949] (EE) 
Fatal server error:
[  2597.949] (EE) no screens found(EE) 
There's also a core dump in /etc/X11/:

Code: Select all

# file core
core: ELF 32-bit LSB  core file ARM, version 1 (SYSV), SVR4-style, from '/usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt'
I don't think that the odroid utility made any changes to the xorg.conf, but I copied over the xorg.conf.failsafe file and restarted the lightdm service. This did start X alright, but it has various warnings and an error:

Code: Select all

[  2846.278] (++) using VT number 7
[  2846.279] (WW) Falling back to old probe method for vesa
[  2846.279] (EE) No devices detected.
...
[  2846.283] (II) FBDEV: driver for framebuffer: fbdev
[  2846.283] (++) using VT number 7
[  2846.283] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
[  2846.283] (WW) xf86OpenConsole: setsid failed: Operation not permitted
[  2846.284] (WW) Falling back to old probe method for vesa
[  2846.284] (WW) Falling back to old probe method for modesetting
[  2846.284] (WW) Falling back to old probe method for fbdev
...
[  2846.286] (II) FBDEV(0): using default device
[  2846.286] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
...
[  2846.351] (EE) AIGLX: reverting to software rendering
[  2846.365] (II) AIGLX: Loaded and initialized swrast
I think that the AIGLX message might have been in the logs before I started changing anything. The reason I did the update was that I thought maybe there was some hardware accelerated X for the board. Anyway, maybe I shouldn't have run that option in the odroid utility program on C1 :(

Anyway, as I said, X kind of works, but there are two problems:

* screen background is always black instead of having normal wallpaper (even in apps, like lxterminal)
* screen locks and it doesn't ever accept my password (It seems that I can put in any value and the screen briefly shows the outline of my open windows and then goes back to lock screen)

I'd really like to know what I have to do to back out of the changes that the odroid utility made. The "armsoc" log file that was made mentions putting things in /usr/lib/xorg/modules/drivers. I deleted the armsoc* files there and went back to my old xorg. It does allow X to start, but I now see:

Code: Select all

[  3298.299] (II) LoadModule: "armsoc"
[  3298.301] (WW) Warning, couldn't open module armsoc
[  3298.302] (II) UnloadModule: "armsoc"
[  3298.302] (II) Unloading armsoc
[  3298.302] (EE) Failed to load module "armsoc" (module does not exist, 0)
Neither does it fix the black background problem (not sure about screensaver lock problem yet). It also stops OpenGL/ES2 from working.

I looked at the armsoc.sh code and it seems that there are two problems:

* odroid C was not properly recognised (though sometimes it is; it seems that sometimes the BOARD variable is just not set)
* it blindly overwrote my xorg.conf without making a backup

I can't see anything else in the scripts that might help me.

I'm hoping that all I need is a proper xorg.conf from the original linux image. Any chance you could post that for me? Thanks...
Last edited by magnum_pi on Mon Jan 05, 2015 1:34 am, edited 1 time in total.

User avatar
odroid
Site Admin
Posts: 29398
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Contact:

Re: Two problems with X

Unread post by odroid » Tue Dec 23, 2014 11:17 am

ddx rebuilding option and armsoc are not working on C1 yet.

This is my xorg.conf

Code: Select all

# X.Org X server configuration file for xfree86-video-mali

Section "Device"
        Identifier      "Mali-Fbdev"
        Driver          "mali"
        Option          "fbdev"         "/dev/fb0"
        Option          "DRI2"            "true"
        Option          "DRI2_PAGE_FLIP"  "false"
        Option          "DRI2_WAIT_VSYNC" "false"
        Option          "UMP_CACHED"      "true"
        Option          "UMP_LOCK"        "false"
        Option          "SWCursor"        "true"
        Option          "HWCursor"        "false"

EndSection

Section "ServerFlags"
        Option          "NoTrapSignals" "true"
        Option          "DontZap"       "false"
        Option          "BlankTime"     "0"
        Option          "StandbyTime"   "0"
        Option          "SuspendTime"   "0"
        Option          "OffTime"       "0"
EndSection

Section "DRI"
        Mode            0666
EndSection
I think you may need to install the OS image again.

magnum_pi
Posts: 198
Joined: Tue Mar 05, 2013 6:37 am
languages_spoken: English, Japanese, French, Irish
ODROIDs: U2, X2, XU, U3
Contact:

Re: Two problems with X

Unread post by magnum_pi » Tue Dec 23, 2014 11:32 am

Thanks. You beat me to it :)
I remembered that I had the torrent mirror site still running, so I used the lubuntu image and mounted it via loopback to get the "official" xorg.conf. It seems to be exactly the same as yours.

I tried it out and the black screen & no OpenGL/ES2 problems are solved. Thank you.

I still have no idea why the odroid-utility.sh script sometimes fails to set the BUILD (and other) configuration variables... I think perhaps they should make sure that the variable is set before doing something potentially irreversible...

Anyway, since I have the original image mounted I can also see the armsoc files that the utility also overwrote. Hopefully I won't have to reinstall after all.

Thanks for the quick response...

mdrjr
Site Admin
Posts: 11698
Joined: Fri Feb 22, 2013 11:34 pm
languages_spoken: english, portuguese
ODROIDs: -
Location: Brazil
Contact:

Re: Two problems with X

Unread post by mdrjr » Tue Dec 23, 2014 12:31 pm

Hi magnum_pi,

Thank you for reporting that.. just fixed it! https://github.com/mdrjr/odroid-utility ... 3294e4d86e

Post Reply

Return to “Issues”

Who is online

Users browsing this forum: No registered users and 2 guests