- October 19, 2014 at 4:30 pm #2805
My display looks fine as far as colors and resolution.
When I boot the pre-configured SD card image (1.6) I can get to the desktop and start the calibration utility, but I am not able to click the cross hairs with my stylus. It eventually times out and goes to the terminal session.
I purchased a pre-built screen from KickStarter. No assembly was required.
What do I need to do to get the screen replaced?
Also, the instructions that were on the site that detailed the manual installation, were not very clear. Example:
** Disable the FrameBuffer Driver: ** (That file did not exist on the system. Can’t comment out something that does not exist. 99-fbturbo.conf)
** sudo sh -c ‘echo “sudo /bin/sh /etc/X11/Xsession.d/xinput_calibrator_pointercal.sh” >> /etc/xdg/lxsession/LXDE/autostart’ ** (This command errored out after multiple cut and paste attempts)
** ls -l /dev/input/event* + cat /proc/bus/input/devices ** You never tell us what we are looking for? What am I trying to get from these two commands you have us run?
Maybe the commands were not working because the touch capability of my screen is broke. Not sure.
Please let me know how to proceed.
– Damon Downing
firstname.lastname@example.orgOctober 19, 2014 at 6:01 pm #2807
To help you, I need some information;
Are you using the image of our website or did you install the drivers manually?
Does the touchscreen work within the console?
Can you show me the output of;
dmesg cat /etc/modules/
The other issues, I cant help with out see what you entered and the error messages.;
99-fbturbo.conf does not exist. If possible, can you show me what you entered to edit this file? you can use
historyto see your previous commands.
** sudo sh -c ‘echo “sudo /bin/sh /etc/X11/Xsession.d/xinput_calibrator_pointercal.sh” >> /etc/xdg/lxsession/LXDE/autostart’ ** There is a note under the text of this code “When copying and pasting the last line above, you will need to confirm that all the quotes get copied correctly” Are you also able to show me what you entered for this? and the error message.
** ls -l /dev/input/event* + cat /proc/bus/input/devices **
I have added some more info here… so it should help. You should still do some investigation on your part as I have no idea what you have connected to your Pi.
A file handle is created for each input device currently connected and can change depending on what is connected and how many input devices are connected.
If you have a keyboard and mouse connected, there should be 3 files. One for the keyboard, one for the mouse and the last one for the touchscreen. If you have just a keyboard connected, there would be two. One for the keyboard and one for the touchscreen.
To see what file handle is used for the touchscreen, view the file below.pi@raspberrypi ~ $ cat /proc/bus/input/devices
Look for ADS7846 Touchscreen and within the same section you should see H: Handlers= followed by an eventnumber. This will tell you what file under /dev/input/ is used for the touchscreen.
Going forward, use the input event number associated to your touchscreen in the commands below.October 19, 2014 at 6:07 pm #2812
I just noted that you used the pri-configured image.
The last image had some bugs.
We have uploaded a new one.
Please try this new image.October 20, 2014 at 3:56 pm #2826
For the Dmesg request:
For CAT /etc/modules request:
For the cat /proc/bus/input/devices request:
++ sudo sh -c ‘echo “sudo /bin/sh /etc/X11/Xsession.d/xinput_calibrator_pointercal.sh” >> /etc/xdg/lxsession/LXDE/autostart’ ERROR
++ ** ls -l /dev/input/event* + cat /proc/bus/input/devices **
I have nothing else plugged in. I am using SSH to access the device. The screen does not accept touch screen response, and can’t calibrate either. I can’t test calibration from the console because the sudo command does not work. Probably due to not recognizing the touch screen capabilities at all.
The image you had me download is exactly the same as I was using last night. I restored your image and tested again with the same results. The results I provided tonight are with the new image you had me download.
Let me know what other information I can provide. Thanks.
– Damon Downing
email@example.comOctober 22, 2014 at 7:11 pm #2835
I tested it
sudo sh -c ‘echo “sudo /bin/sh /etc/X11/Xsession.d/xinput_calibrator_pointercal.sh” >> /etc/xdg/lxsession/LXDE/autostart’
and it works.
You need to make sure that after you paste it in, you change the commas back to inverted commas.
In saying that, if you have downloaded the image then this would already be configured.
Does the calibration screen that runs before X windows work?
What about Evtest, do you get any feedback? You can run it with;
If it isnnt installed, you can install it with;
sudo apt-get install evtestOctober 25, 2014 at 3:15 pm #2847
I have pasted the exact text in:
pi@rasp-temp ~ $ sudo sh -c ‘echo “sudo /bin/sh /etc/X11/Xsession.d/xinput_calibrator_pointercal.sh” >> /etc/xdg/lxsession/LXDE/autostart’
-bash: /etc/xdg/lxsession/LXDE/autostart’: Permission denied
pi@rasp-temp ~ $
I am in the US. Are you sure your image does not have a different keyboard loaded for another country. Britain or something?
I pasted it in directly from this forum using your exact text. See above. Same issue.
I can’t run EVTEST right now as the last firmware that was released makes the screen stop working. See my other new thread I started. I did try to run EVTEST, but it only see 0 as my mouse, 1 as my keyboard, 2 does not exist.
It acts like it does not see the touchscreen mechanism at all.
– Damon DowningOctober 25, 2014 at 3:42 pm #2849
Once you get the drivers working again, re-run evtest
After you select your touchscreen, you should see some data being printed to the terminal whenever you press the touchscreen.October 25, 2014 at 4:45 pm #2851
OK. I just ran the EVTEST. I get no chance in the numbers on the screen when touching the display with the stylus:
pi@rasp-test ~ $ evtest /dev/input/event1
Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: “ADS7846 Touchscreen”
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 330 (BTN_TOUCH)
Event type 3 (EV_ABS)
Event code 0 (ABS_X)
Event code 1 (ABS_Y)
Event code 24 (ABS_PRESSURE)
Testing … (interrupt to exit)October 26, 2014 at 11:07 am #2853
- You must be logged in to reply to this topic.