Bug 93030 - Only mouse cursor visible when using armsoc driver - [drm:fimd_win_mode_set] *ERROR* Invalid panel parameters
Summary: Only mouse cursor visible when using armsoc driver - [drm:fimd_win_mode_set] ...
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/armsoc (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Paul Geary
QA Contact: Paul Geary
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-20 01:18 UTC by Jeremy Huddleston Sequoia
Modified: 2018-08-10 20:40 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeremy Huddleston Sequoia 2015-11-20 01:18:14 UTC
I updated my Samsung Chromebook to Ubuntu 14.04 and ran into an issue described on Ubuntu's bug tracker at https://launchpad.net/ubuntu/+source/xf86-video-armsoc

The system is perfectly usable using fbdev, but if I switch to using armsoc, I run into issues.  Upon starting the X server, I see my mouse pointer on screen.  About 4 seconds later, the lightdm login screen appears.  About 3 seconds after that, the login screen disappears, and only the mouse pointer remains on screen.

dmesg is filled with '[drm:fimd_win_mode_set] *ERROR* Invalid panel parameters' messages

I am experiencing this issue with the version packaged with Ubuntu (0.6.0) as well as current git (ee9f1d96193d4fc2887183b613f209b18a93e718, 1.4.0).

$ uname -a
Linux localhost.localdomain 3.4.0-5-chromebook #5-Ubuntu SMP Wed Feb 20 14:59:17 UTC 2013 armv7l armv7l armv7l GNU/Linux
Comment 1 Jeremy Huddleston Sequoia 2015-11-20 01:20:20 UTC
I messed up the copy of the downstream bug URL.  It should have been:
https://bugs.launchpad.net/ubuntu/+source/xf86-video-armsoc/+bug/1308192
Comment 2 Paul Geary 2015-12-16 13:16:22 UTC
We're struggling to reproduce this issue - could you please provide some more information about your setup?

In particular:
- Which Mali userspace driver version are you using? You can find this out by looking at the name of the /usr/lib/arm-linux-gnueabihf/mali-t62x_* directory.
  
- Are you running Ubuntu in a chroot or natively?

- What Ubuntu version were you running before you updated, and how did you install that? What method did you use to update to 14.04?

Also, could you try a newer kernel version? The latest ChromeOS uses 3.8.11, and armsoc works for us with that, both in a chroot and installed natively. Instructions on installing 14.04 with Linux 3.8.11 on an SD card can be found here: https://community.arm.com/docs/DOC-9494
Comment 3 GitLab Migration User 2018-08-10 20:40:31 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-armsoc/issues/2.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.