search

meefik / linuxdeploy

Install and run GNU/Linux on Android
https://meefik.github.io/linuxdeploy
GNU General Public License v3.0
5.28k stars 680 forks source link

Linuxdeploy fbdev/fbio error in xorg problem #249

Open ljones0 opened 9 years ago

ljones0 commented 9 years ago

Hello all :-)

Might possibly have another issue here btw. Originally I did have a problem with a nonexistant tty0 though that seems to have been solved. However there's a new problem when using the framebuffer. All that seems to happen is the screen flickers rapidly (you can only see a tiny piece of the screen, sometimes a little more). The mouse pointer is visible if I plug a usb mouse into my phone.

Unfortunatly however the end result is always the same - a blank screen. I was able to SSH in however (using username=android;password=changeme) and looked at the /etc/X11/Xorg.0.log file. I found this;

[code] 244.313 FBDEV(0): FBIOBLANK: Invalid argument [/code]

Not sure how to fix this one!

ljones

ljones0 commented 9 years ago

Someone else (russian, translated) is having the same problem or so it seems;

https://translate.google.com/translate?sl=ru&tl=en&js=y&prev=_t&hl=en&ie=ISO-8859-1&u=http%3A%2F%2F4pda.ru%2Fforum%2Flofiversion%2Findex.php%3Ft378043-5480.html&edit-text=

ljones

ljones0 commented 9 years ago

Also noticed the following -- prehaps this is part of the problem (do not know); $ sudo su $ echo 1 > /sys/class/graphics/fb0/blank bash: echo: write error: Invalid argument $ echo 0 > /sys/class/graphics/fb0/blank bash: echo: write error: Invalid argument

ljones

ljones0 commented 9 years ago

Update: after trying again and also choosing the option that stops android in the configuration settings and after running echo 1 > /sys/class/graphics/fb0/blank I eventually do get a screen. This takes several minutes to appear but after this nothing happens, no response to touch, mouse nor anything else. I do see the LXDE desktop and an error message - "No session for pid 1966". Though nothing at all works, no input nothing only way out is to take the battery out of the phone.

I should also mention I'm using a slightly different xorg.conf;

Section "ServerLayout" Identifier "Layout0" Screen "Screen0" InputDevice "touchscreen" "CorePointer" EndSection

Section "InputDevice" Identifier "touchscreen" Option "Device" "/dev/input/event2" #linuxdeploy

Driver "multitouch"

Driver "mtrack"

Driver "evdev" EndSection

Section "Device" Identifier "Card0" Driver "fbdev" Option "fbdev" "/dev/graphics/fb0" #linuxdeploy

Option "Rotate" "CW"

Option "UseFBDev" "true" EndSection

Section "Screen" Identifier "Screen0" Device "Card0" DefaultDepth 24 SubSection "Display" Depth 24 EndSubSection EndSection

That xorg.conf was created by X or Xorg --configure btw.

Also I'm able to get in via another PC and a command line over SSH (the other PC is running putty).

ljones

ljones0 commented 9 years ago

Just a bit more info. I took a picture of the "frozen" display, you can see it here

Incidentally I should also add that that xterm you see I managed to get that to 'run' while the display was completely blank on the phone (this only works btw with the option to stop android in linuxdeploy) I could ssh in and do the following as non-root;

$ export DISPLAY=:0.0 $ xterm

Beyond this though, nothing happens on the phone display. Even if I were (for example) to try to run xclock, i.e.

$ xclock &

and then

$ sudo su $ echo 1 > /sys/class/graphics/fb0/blank

Nothing happens on the phone. Zilch. Though the SSH keeps going and I'm able to use the command line.

ljones

ljones0 commented 9 years ago

One more thing I noticed -- /dev/input/event2 (touchscreen?) seems to be wrong for my device. It does nothing - no response to touching the phone's screen instead I found while in SSH at a command line I could do a cat /dev/input/event3 and see rubbish appear at the command line according to when I touched the phone's display. Though this dosen't seem to fix the 'frozen screen' problem the display dosen't seem to respond on the phone (but yet in SSH) x.x!

ljones

ljones0 commented 9 years ago

Not sure if it helps but here is my xorg log and my dmesg output

ljones

dyharlan commented 9 years ago

use evtest to figure out the touchscreen block and install xorg-input-mtrack or multitouch for touch or if you're courageous enough, use mtev

dyharlan commented 9 years ago

Oh yeah and the pid error actually is I guess normal for arch linux

ljones0 commented 9 years ago

use evtest to figure out the touchscreen block and install xorg-input-mtrack or multitouch for touch or if you're courageous enough, use mtev.

I managed to install those packages though xorg-input-mtrack was called xserver-xorg-input-mtrack in debian.

I ran evtest and got the following results;

Available devices: /dev/input/event0: mtk-kpd /dev/input/event1: ACCDET /dev/input/event2: hwmdata /dev/input/event3: mtk-tpd /dev/input/event4: mtk-tpd-kpd

Of these;

Event0 Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 114 (KEY_VOLUMEDOWN) Event code 115 (KEY_VOLUMEUP) Event code 116 (KEY_POWER) repsonds to the up/down keys and power key, e.g. Event: time 1440539330.018308, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 1 Event: time 1440539330.018315, -------------- SYN_REPORT ------------ Event: time 1440539330.183216, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 0

Event1 Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 114 (KEY_VOLUMEDOWN) Event code 115 (KEY_VOLUMEUP) Event code 122 (KEY_HANGUEL) Event code 163 (KEY_NEXTSONG) Event code 164 (KEY_PLAYPAUSE) Event code 165 (KEY_PREVIOUSSONG) Event code 166 (KEY_STOPCD) Event code 231 (KEY_SEND) This event didn't produce any data at all, didn't respond.

Event2 Supported events: Event type 0 (EV_SYN) Event type 2 (EV_REL) Event code 1 (REL_Y) This event prints this, over and over again continually; Event: time 1440539456.758437, type 2 (EV_REL), code 1 (REL_Y), value 1 Event: time 1440539456.758445, -------------- SYN_REPORT ------------ Event: time 1440539456.818427, type 2 (EV_REL), code 1 (REL_Y), value 1 Event: time 1440539456.818436, -------------- SYN_REPORT ------------ Event: time 1440539456.878362, type 2 (EV_REL), code 1 (REL_Y), value 1 Event: time 1440539456.878370, -------------- SYN_REPORT ------------ Event: time 1440539456.938441, type 2 (EV_REL), code 1 (REL_Y), value 1 etc..

Event3 Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 139 (KEY_MENU) Event code 158 (KEY_BACK) Event code 172 (KEY_HOMEPAGE) Event code 330 (BTN_TOUCH) Creates data when I touch the screen, e.g. Event: time 1440539551.706228, ++++++++++++++ SYN_MT_REPORT ++++++++++++ Event: time 1440539551.706234, -------------- SYN_REPORT ------------ Event: time 1440539551.723978, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1 Event: time 1440539551.723985, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 212 Event: time 1440539551.723990, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 224 Event: time 1440539551.723995, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0

Event4 Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 139 (KEY_MENU) Event code 158 (KEY_BACK) Event code 172 (KEY_HOMEPAGE) This event didn't respond and created no data.

Thats about all I can figure out for now!

ljones