tag:blogger.com,1999:blog-6965286.post8011311213239936632..comments2023-09-01T09:16:56.368+01:00Comments on Simons Blog: Raspberry Pi (RPi) kernel build for eGalax touchscreen supportSimonhttp://www.blogger.com/profile/09076917888981267534noreply@blogger.comBlogger35125tag:blogger.com,1999:blog-6965286.post-22642242229320133702015-02-07T16:53:38.046+00:002015-02-07T16:53:38.046+00:00First off (my noob mstake) DO NOT apt-get upgrade ...First off (my noob mstake) DO NOT apt-get upgrade && update. It will jack up you hacked kernel.<br /><br />hey all,<br />Quick update. If your GPIO's no longer work after modding your kernel, try this:<br /><br />gpio -v<br /><br />If that returns "not found", then you have to reinstall wiringPi.<br /><br />Search that term, follow the simple directions and things will work again.<br /><br />Hope it helps.Andy Seredyhttps://www.blogger.com/profile/10140785349935793185noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-47645682277195678372015-02-07T13:30:00.668+00:002015-02-07T13:30:00.668+00:00Thanks for putting up your Kernal Guys. Though I t...Thanks for putting up your Kernal Guys. Though I think I did something wrong. After I replaced the Kernel and FM/mod folders, Everything booted up fine, and I was able to use my touch screen just fine, but when I tried to execute some shell scripts which controlled the Pi's GPIOs I was given "Command not found" errors, so I tried to chmod +x them (again)... didn't work... <br /><br />Then I made the biggest noob move of all.. I tried an update/upgrade... now everything is effed. haha. USB input devices are detected, but dont work.. Everything (mouse, keyboard, touchscreen). <br /><br />Curiously, my rootFS is on a USB drive, and that works fine. Guess I'll start from scratch. Cheers,<br /><br />PS. I tried AUX's kernel on a rPi B+Andy Seredyhttps://www.blogger.com/profile/10140785349935793185noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-54584598264377006582015-02-04T19:26:01.559+00:002015-02-04T19:26:01.559+00:00Hello everybody.
For the lucky ones who has a RPI ...Hello everybody.<br />For the lucky ones who has a RPI 2 like me, here is the kernel to enable eGalax touchscreen.<br />You must have 3.18.5-rebase kernel.<br />https://1fichier.com/?7uwem02si9Chrishttps://www.blogger.com/profile/07387001243617431907noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-29746109177124444822015-02-02T09:05:30.707+00:002015-02-02T09:05:30.707+00:00For those who wants the kernel for last version of...For those who wants the kernel for last version of rasbian (february 2015) : 3.18.5, here is mine :<br />https://1fichier.com/?tg19bswby2Chrishttps://www.blogger.com/profile/07387001243617431907noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-76195558854298976242015-01-22T06:30:15.111+00:002015-01-22T06:30:15.111+00:00Thanks simon ,
I have started a thread with Raspi...Thanks simon ,<br /><br />I have started a thread with Raspi forums ,<br />I did some additional troubleshooting and just wanted to mention it , that the touchscreen works with ubuntu 14.04 , so i tried things on comparison basis ..<br /><br />when i did dmesg | grep -i usb on raspi it returns .<br />[ 3.471379] usb 1-1.4: Product: USB TouchController<br />[ 3.484165] usb 1-1.4: Manufacturer: eGalax Inc.<br />[ 3.736826] usb 1-1.2: new low-speed USB device number 5 using dwc_otg<br />[ 3.889922] usb 1-1.2: New USB device found, idVendor=1a2c, idProduct=0c21<br />[ 3.899177] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0<br /><br />when i did the same on ubuntu 14.04 <br /><br />[ 5138.037116] usb 2-1.2: Product: USB TouchController<br />[ 5138.037119] usb 2-1.2: Manufacturer: eGalax Inc.<br />[ 5138.084038] input: eGalax Inc. USB TouchController as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input10 .<br /><br />Thanks .deepeshhttps://www.blogger.com/profile/18104429053013341063noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-57408237622262360132015-01-22T06:29:15.346+00:002015-01-22T06:29:15.346+00:00This comment has been removed by the author.deepeshhttps://www.blogger.com/profile/18104429053013341063noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-2165577195946163072015-01-21T09:24:10.308+00:002015-01-21T09:24:10.308+00:00deepesh, its so long ago that I would be surprised...deepesh, its so long ago that I would be surprised if the instructions will work for today's Raspbian. <br /><br />lsusb should list if the touchscreen is plugged in and the driver is recognised.<br /><br />if the driver is working properly, when you touch the screen you will see the LED on the USB module come on and go off, if it comes on and stays on then the USB driver is not consuming the events from the touchscreen.<br /><br />Apart from this, I'd recommend starting a thread on the raspberry pi forums, as someone else will probably be able to help you. http://www.raspberrypi.org/Simonhttps://www.blogger.com/profile/09076917888981267534noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-5212391507135692792015-01-21T08:50:36.291+00:002015-01-21T08:50:36.291+00:00Hi I have been trying your article ,finally i was ...Hi I have been trying your article ,finally i was able to complete the tutorial , but the touch does not seem to work , is thier a way to troubleshoot or check if the galaxy touchscreen drivers are loaded .deepeshhttps://www.blogger.com/profile/18104429053013341063noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-30179340284772131932014-07-31T12:30:47.937+01:002014-07-31T12:30:47.937+01:00Hi,
Excellent tutorial indeed and I was able to ge...Hi,<br />Excellent tutorial indeed and I was able to get the touchscreen working with RaspberryPi. Thanks!<br /><br />A query I have is, can I change the "double click" functionality of Raspbian into a single click like most touch screen OS. Let me know if any of you have figured a way to do this. :-)<br />Thanks & Regards,<br />Nachikethnachihttps://www.blogger.com/profile/16350115820833267064noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-4251442419105585862014-06-10T09:00:25.674+01:002014-06-10T09:00:25.674+01:00John
boot-partition-uuid needs to be replaced wit...John<br /><br />boot-partition-uuid needs to be replaced with the uuid from your own boot partition, which looks like 561d7033-c329-634e-9b5d-52dd5e9d1d0c according to your error.<br /><br />I've never used NOOBS so I'm not familiar with the layout, so I'm afraid I can be no help there.<br /><br />Also if "sudo apt-get install package" cant find package, then you can use sudo apt-cache search package to find the proper name for the package (maybe the version number has changed). Search will return any partial matches Simonhttps://www.blogger.com/profile/09076917888981267534noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-35659624635259601592014-06-08T16:59:46.895+01:002014-06-08T16:59:46.895+01:00Well I got it to work using gnueabihf -
"ma...Well I got it to work using gnueabihf - <br /><br />"make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf-"<br /><br />It's compiling!!! I'm documenting my progress - Thank you for trying to help so far Simon and thank you again for your guide. <br /><br />Although for some reason I'm having an issue with the NOOBS SDHC card.... I try to move the kernel.img and I'm just getting this error.. <br /><br />ubuntu@ubuntu:~/raspberrypi/tools/mkimage$ sudo rm /media/boot-partition-uuid/kernel.img<br />rm: cannot remove ‘/media/boot-partition-uuid/kernel.img’: No such file or directory<br />ubuntu@ubuntu:~/raspberrypi/tools/mkimage$ sudo mv kernel.img /media/boot-partition-uuid/ <br />mv: cannot move ‘kernel.img’ to ‘/media/boot-partition-uuid/’: Not a directory<br /><br /><br /><br />I don't have a /media/boot-partition-uuid/ anywhere... All I find is SETTINGS in /boot/ ~ But I also cannot access the NOOBS in the SDHC..<br /><br />I try to enter the volume and it says "unable to access "4.2 GB volume" Device /dev/loop1 is already mounted at '/Media/ubuntu/561d7033-c329-634e-9b5d-52dd5e9d1d0c" Anonymoushttps://www.blogger.com/profile/08259378991758761329noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-8041455545770889642014-06-08T14:12:08.557+01:002014-06-08T14:12:08.557+01:00When I try to cross-compile (granted im using ubun...When I try to cross-compile (granted im using ubuntu 14.04 64bit with 32libs) i get this error still using your guide.. <br /><br />ubuntu@ubuntu:~/raspberrypi/linux$ make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi<br />make: /usr/bin/arm-linux-gnueabigcc: Command not found<br /> CHK include/generated/uapi/linux/version.h<br /> CHK include/generated/utsrelease.h<br />make[1]: `include/generated/mach-types.h' is up to date.<br /> CC kernel/bounds.s<br />/bin/sh: 1: /usr/bin/arm-linux-gnueabigcc: not found<br />make[1]: *** [kernel/bounds.s] Error 127<br />make: *** [prepare0] Error 2<br /><br /><br /><br />and still with gnueabi;<br /><br />ubuntu@ubuntu:~/raspberrypi/linux$ sudo apt-get install git-core gcc-4.6-arm-linux-gnueabi<br />Reading package lists... Done<br />Building dependency tree <br />Reading state information... Done<br />E: Unable to locate package gcc-4.6-arm-linux-gnueabi<br />E: Couldn't find any package by regex 'gcc-4.6-arm-linux-gnueabi'<br />Anonymoushttps://www.blogger.com/profile/08259378991758761329noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-22129332605320553092014-06-08T03:38:08.924+01:002014-06-08T03:38:08.924+01:00This comment has been removed by the author.Anonymoushttps://www.blogger.com/profile/08259378991758761329noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-43877560100216707612014-06-07T22:03:39.999+01:002014-06-07T22:03:39.999+01:00John, These instructions are for cross compile onl...John, These instructions are for cross compile only, so they wont work running from your pi.<br /><br />You need to get a copy of ubuntu installed onto an old pc and then follow the instructions.<br /><br />xinputcalibrator will not work until you get the updated kernel built and installed.<br /><br />You might find further help by asking on the raspberry pi forums. (and you're welcome to ask here for more too)Simonhttps://www.blogger.com/profile/09076917888981267534noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-75611348183920331602014-06-07T19:41:24.557+01:002014-06-07T19:41:24.557+01:00I got the 99-calibration.conf to save but it still...I got the 99-calibration.conf to save but it still says no calibratable devices are found in xinput_calibratorAnonymoushttps://www.blogger.com/profile/08259378991758761329noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-53454825698641340762014-06-07T17:05:04.229+01:002014-06-07T17:05:04.229+01:00This comment has been removed by the author.Anonymoushttps://www.blogger.com/profile/08259378991758761329noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-89627754225257275802014-06-07T17:03:33.966+01:002014-06-07T17:03:33.966+01:00This comment has been removed by the author.Anonymoushttps://www.blogger.com/profile/08259378991758761329noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-22851721940785266452014-06-07T13:17:48.338+01:002014-06-07T13:17:48.338+01:00Hi John,
My article is on cross-compiling - so bu...Hi John,<br /><br />My article is on cross-compiling - so building the kernel on another linux machine running ubuntu and then copying the files across to the pi.<br /><br />What does the error message say exactly? if you are already root user then you don't need to use sudo at the start of the commands.Simonhttps://www.blogger.com/profile/09076917888981267534noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-37651514330176478922014-06-06T22:21:46.005+01:002014-06-06T22:21:46.005+01:00This comment has been removed by the author.Anonymoushttps://www.blogger.com/profile/08259378991758761329noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-48872878147105816032014-04-17T07:18:02.507+01:002014-04-17T07:18:02.507+01:00Wow thanks a lot it worked!! I also figured out t...Wow thanks a lot it worked!! I also figured out that it was not me making mistakes with my own kernel. It turns out my problem was the case that I had my screen in was causing the touch panel to detect a touch. Just had to move the screen away from touching the case and works great now.Anonymoushttps://www.blogger.com/profile/09803954319755930460noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-14657676875836439802014-04-15T08:54:25.101+01:002014-04-15T08:54:25.101+01:00Brock,
I have uploaded the contents of my firmwar...Brock,<br /><br />I have uploaded the contents of my firmware and modules directory, and also the kernel to dropbox. Simply remove and replace your /lib/modules and /lib/firmware with the ones in this archive. The matching kernel is also in the /boot directory<br /><br />https://dl.dropboxusercontent.com/u/7297788/eGalax-touch-firmware.tar.gzSimonhttps://www.blogger.com/profile/09076917888981267534noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-46574509616103517402014-04-11T21:07:03.392+01:002014-04-11T21:07:03.392+01:00could you please leave a link to download the work...could you please leave a link to download the working firmware? Seems that I have same problem now of cursor staying at top of screen.Anonymoushttps://www.blogger.com/profile/09803954319755930460noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-9148866173842019692014-04-06T07:56:59.329+01:002014-04-06T07:56:59.329+01:00I was able to get it working by copying over my ol...I was able to get it working by copying over my old firmware files to the new firmware folder made in your tutorial.Anonymoushttps://www.blogger.com/profile/09803954319755930460noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-33378166516298594662014-04-05T20:44:06.188+01:002014-04-05T20:44:06.188+01:00Yes I have all my deviced plugged into a powered u...Yes I have all my deviced plugged into a powered usb hub, and the wifi and controller work fine on the origional kernel but when i recompile with your instructions the wifi no longer worksAnonymoushttps://www.blogger.com/profile/09803954319755930460noreply@blogger.comtag:blogger.com,1999:blog-6965286.post-69437724275248168252014-04-05T11:51:00.749+01:002014-04-05T11:51:00.749+01:00Brock,
It was a firmware issue, because reverting...Brock,<br /><br />It was a firmware issue, because reverting back the firmware fixed it.<br /><br />For your problem, are you using a USB hub to power your touchscreen USB? If not then I've found it draws too much power, and makes operation unstable. A USB hub, or a USB +5v injector lead fixes this.Simonhttps://www.blogger.com/profile/09076917888981267534noreply@blogger.com