Menu
The Intel® PRO Wireless 3945ABG network cards are commonly used in various laptops ranging from HP to Dell. These drivers are in the non-free section and thus are not included with Debian or Debian remixes by default. Installing Wireless ipw3945 drivers in Debian: Open a terminal and type sudo su. Sep 04, 2018 How to get eGalax TouchScreen film (0eef) working in Linux for Raspberry Pi – Black God. I’ve documented egalax linux with photos here on Google Drive https: In the case of Itronix and most other devices using the Touchkit driverthe correct driver is touchit Then calibrate the screen using the egalax linux tab CategoryHardware Touchscreen last edited The first step in getting this done is.
![]()
Hi all,Some of you might remember about me trying to get my touch screen working with a Raspberry Pi. The idea is to use this touch screen as a terminal for my home automation system.I eventually got it to work, but it turned out the RPi lacked the horsepower to make this a success.
Navigating was painfully slow, so I decided to try something else and turned the RPi into an XBMC machine.So then I tried an, a and a. All those were powerful enough to do what I wanted them to do, some even came with Android pre-installed. But they also all failed me, because they were not able to feed the touch screen a proper video signal, so it didn't work. As it turned out, these things works great with a recent tv or monitor, as long as you've got a HDMI interface. My touch screen has only got VGA and DVI, and a converter didn't work. Trust me, I tried several.So then I decided to bite the bullet and I bought new mini-ITX board with a recent Intel Atom on it (J1900) and 4GB of RAM.
I still had a leftover Intel SSD drive laying around, so I was able to set up a completely silent mini-PC. The whole idea was to put Linux on it, AND an Android emulator, which could then run the Android app of my home automation on it. That would be sweet.So I started by putting the most recent version of Linux Mint (XFCE) on it.
That all went pretty smooth. The touch screen was even detected out of the box. The only problem is, the calibration is way off.
I remembered this from the RPi setup, and I got the 'xinputconfiguration' utility working. But, as opposed to with the RPi, even after calibration, the screen still is not usable.
Bummer.I figured maybe the drivers weren't very recent. So I checked the eGalax website, and found pretty recent drivers for this model. But now the challenge is getting this driver installed. I was already stumped on page 3, where it tells me to use 'make menuconfig' to install and remove a couple of things befor I can install the driver. Whatever I've tried so far hasn't worked. How can I do this?I would really appreciate it if somebody in the know could have a at this and give me a few pointers. In the ZIP file you'll find a file called 'EETIeGTouchLinuxProgrammingGuidev2.5f.PDF' in the /Guide directory which is a how-to for installing this driver.Thanks a lot!
Still no further. Whenever I type the command 'make menuconfig', I get the message: 'make:. There is no rule to make target 'menuconfig'.
Stopped'I tried Googling, but came up empty. The only thing I could find was, but didn't understand the solution. I did figure that it had something to do with 64bit vs 32bit, so then I installed 32bit Xubuntu. Unfortunately with the same result.I'm now seriously considering purchasing a Windows 8 licence, but this seems such a stupid cost since this system will only be used for one thing. Then again, my time is not limitless and it's clear I'm trying something above my understanding here.I would love to be able to find some sort of course which could explain the in-depths of Linux more to me. So far I've never found one. It can't all be trial and error for sure?
I actually did do a Linux course for two years, but that emphasized on the desktop use, while I know the real power is in the command line and that's what I'm more interested in. Everytime I try this, it ends the same: I'm in awe about the long command line functions, with often lots of parameters and flags.
Every time I think then: 'how does someone know and remember this? How does someone put such long commands together? There must be a system to it?' But so far, I've never been able to untangle that system.I read an interview with Linus Torvalds last month, in which he says the desktop really is the only market where Linux still plays second (or third) fiddle and he still believes this may change in the future. Well Linus, I'm not saying it's got to become 'Apple-simple', but it does need to become simpler than this for this to succeed.
I consider myself a power user, but this is really above my understanding (and I hate it! Whenever I type the command 'make menuconfig', I get the message: 'make:.
There is no rule to make target 'menuconfig'. Stopped'From vague memories - been quite a while since I built anything using make, but IIRC that'd mean that there's no section in the makefile that describes what is supposed to be done in the case make is called with the argument 'menuconfig'. Might be that your makefile's been mangled.As to those impressive command lines - you know and remember what you use.Over time you find and learn what various tools there are and what they in general do, switch details and detailed behaviour is found in the man-pages.Often, at least for me, the long command lines are grown in stages, ie run first part and see what you get out, figure out what is needed to process that output further into the next stage, tack on that command, rinse and repeat until you have the wanted final output. It's programming, only that the stages are stacked horizontally and separated by pipes ( )rather than vertically and by newlines.the various command line programs are essentially the same as functions in a programming language.The shell, just like plain C, offers some basic functionality for loops, comditionals etc, but the power to do much, without a lot of effort/coding, lies in the function libraries / command line programs. Well Linus, I'm not saying it's got to become 'Apple-simple', but it does need to become simpler than this for this to succeed.You are NOT struggling with 'the Desktop' here.
Rather, you are trying to do embedded systems development without being familiar with the development environment, in the same way that I might were I trying do do this same task on a Microsoft platform.Cheers#362476 - 10:30 Re: Some Linux help needed please: trying to configure a touch screencarpal tunnelRegistered: Posts: 14192Loc: Canada. I would love to be able to find some sort of course which could explain the in-depths of Linux more to me.Simple: Visit site and click on the Training tab. Also has a solid curriculum of their own, as do some other Linux vendors.Your local book store probably has a dozen or so introductory volumes for Linux and Linux Development as well.Cheers#362477 - 10:43 Re: Some Linux help needed please: trying to configure a touch screencarpal tunnelRegistered: Posts: 14192Loc: Canada.
So I just now downloaded the 'driver' (not really a 'driver', by the way) package from to have a look.It's HORRID!! The instructions given are incredibly complex for something so simple. Like they were translated from one language to another, to a third, and finally to English.And even allowing for Lost In Translation effects, they're just so bizarre in what they want one to do. This isn't Linux, this is just a company with clueless developers or doc writers.I don't see why they have you reconfiguring the kernel in the first place, since their package doesn't actually include a kernel driver or code - it appears to just use stuff that is already built-into your kernel.My sympathies to you.
Good Luck!#362478 - 10:47 Re: Some Linux help needed please: trying to configure a touch screencarpal tunnelRegistered: Posts: 2608Loc: Bruges, Belgium. Well Linus, I'm not saying it's got to become 'Apple-simple', but it does need to become simpler than this for this to succeed.You are NOT struggling with 'the Desktop' here. Rather, you are trying to do embedded systems development without being familiar with the development environment, in the same way that I might were I trying do do this same task on a Microsoft platform.Ah, so this isn't something simple to do for a Linux savvy person after all? Thanks Mark, that makes me feel better about myself! So I just now downloaded the 'driver' (not really a 'driver', by the way) package from to have a look.It's HORRID!! The instructions given are incredibly complex for something so simple.
Like they were translated from one language to another, to a third, and finally to English.And even allowing for Lost In Translation effects, they're just so bizarre in what they want one to do. This isn't Linux, this is just a company with clueless developers or doc writers.I don't see why they have you reconfiguring the kernel in the first place, since their package doesn't actually include a kernel driver or code - it appears to just use stuff that is already built-into your kernel.My sympathies to you. Good Luck!Well, that's my hope out the window right there. If even you can't put this into layman's terms me for, then I guess I'm totally screwed.Oh well, Windows 8 licence here I come I guess.
The manual says.6-1-2 Kernel source patch If your Linux kernel version is 3.8.0 upwards and using resistive or SCAP touch controller, please comment the following RED section in your source code.u/SourceCode/drivers/hid/hid-core.c.switch (hdev-vendor) /.case USBVENDORIDDWAV:.//. These are handled by usbtouchscreen. Hdev-type is probably. HIDTYPEUSBNONE, but we say!HIDTYPEUSBMOUSE to match. usbtouchscreen.//.if ((hdev-product USBDEVICEIDEGALAXTOUCHCONTROLLER hdev-product USBDEVICEIDDWAVTOUCHCONTROLLER) &&hdev-type!= HIDTYPEUSBMOUSE)return true;break;./Ugh.
You don't really want to do that.There's a whole mess of stuff that their 'instructions' leave out, such as learning to configure, rebuild, and install the modified kernel and modules afterwards.The entire section is bogus anyway - there's a way to achieve what that 'patch' does without actually patching anything. What they are struggling to do, is to tell the kernel not to manage their device, as they instead want to (quite sensibly) do it all from the application code instead. Their problem is, they know about as much about Linux development as you do. Next to nothing - no offence intended, to you anyway.Gimme a sec or two to look up the simple method for this.#362480 - 11:09 Re: Some Linux help needed please: trying to configure a touch screencarpal tunnelRegistered: Posts: 2608Loc: Bruges, Belgium.
![]()
The manual says:6-1-2 Kernel source patch If your Linux kernel version is 3.8.0 upwards and using resistive or SCAP touch controller, please comment the following RED section in your source code./SourceCode/drivers/hid/hid-core.cbool hidignore(struct hiddevice.hdev)-switch (hdev-vendor) /.case USBVENDORIDDWAV:.//. These are handled by usbtouchscreen. Hdev-type is probably.
HIDTYPEUSBNONE, but we say!HIDTYPEUSBMOUSE to match. usbtouchscreen. I don't know if this makes any difference, but when I used the 'xinputconfiguration' with the Raspberry Pi, after the calibration of the screen, the screen already worked as it should. In Mint, even after the calibration procedure, it still doesn't work. (the cursor does not follow the movements of my finger, it goes haywire)Mint probably has a lot more 'stuff' installed that the RPi system, which means a lot more stuff that can go wrong.What kernel version does the RPi use? Command: uname -rAnd similarly, what version is your Mint using: same command!Cheers#362484 - 11:25 Re: Some Linux help needed please: trying to configure a touch screencarpal tunnelRegistered: Posts: 2608Loc: Bruges, Belgium.
Note: These days, if I wanted a (single) touchscreen interface for something around the home, I would probably just purchase a 5' Android smartphone from China for under $100 and use that. Maybe even write a custom app for it.The advantages are huge: built-in wifi, USB OTG port, battery backup, rich GUI and development environment, etc.Cheers#362486 - 11:30 Re: Some Linux help needed please: trying to configure a touch screencarpal tunnelRegistered: Posts: 2608Loc: Bruges, Belgium. Note: These days, if I wanted a (single) touchscreen interface for something around the home, I would probably just purchase a 5' Android smartphone from China for under $100 and use that. Maybe even write a custom app for it.The advantages are huge: built-in wifi, USB OTG port, battery backup, rich GUI and development environment, etc.CheersI know and I agree.
I can control my home automation with my phone, that's not the issue.It's just that I already bought this screen several years ago (before being able to control it with my phone), with the intention of implementing it into my living room. Even cut a hole in the wall especially for it. It's been 5 years now, and I would really like to start using it. # /usr/local/bin $ rebindtouchscreen.sh+ USBTOUCHSCREEN=/sys/bus/hid/drivers/usbtouchscreen+ HID=/sys/bus/hid/drivers/hid-generic+ modprobe hid-generic+ modprobe usbtouchscreen+ ' -d /sys/bus/hid/drivers/hid-generic -a -e /sys/bus/hid/drivers/usbtouchscreen/unbind '+ exit 0Okay, so the script didn't find the device. I wondered if it would or not.If you can still set it up on the RPi board, that would be useful to help puzzle out the basics for me. Once set up there, post the output from this:ls -lF /sys/bus/hid/drivers/.And maybe do the same for the Mint system first.
EDIT: do this on the Mint system before issuing that command:modprobe usbtouchscreen hid-genericEdited by mlord ( 12:17)#362491 - 12:26 Re: Some Linux help needed please: trying to configure a touch screenold handRegistered: Posts: 739Loc: Toronto, Ontario, Canada. I already bought this screen several years ago. It's been 5 years now. Perhaps you could imagine you had never bought that five year old technology touch screen.What would you be buying today, instead?Buy that, move on.I don't think I would buy it today if that is what you mean. But back in the days when I bought it, smartphones were almost non-existent, let alone anybody could predict what their possibilities would be in the future.
Controlling the home automation)But now the house is finally coming together, and this is one of those things on the 'to do' list. Hardly imperative, since I can command my home automation with my phone and iPad as said.
But I have it, it cost me 600 euro back in the days and I would like to be able to use it now. It will add an additional level of comfort. Besides, it's been sitting in my wall for years now and everybody that comes in bugs me with a 'hell, did you get that thing to work already?' Well Linus, I'm not saying it's got to become 'Apple-simple', but it does need to become simpler than this for this to succeed.You are NOT struggling with 'the Desktop' here. Rather, you are trying to do embedded systems development without being familiar with the development environment, in the same way that I might were I trying do do this same task on a Microsoft platform.CheersI disagree. He's trying to install a driver which is a reasonable exercise for the desktop. I know you could install a Windows driver no problem.
The fact that Linux sometimes requires compilation of kernel modules etc makes Linux a difficult proposition for many. To be user friendly, the command line should not be required for simple tasks like this.Even if this particular driver is a mess that shouldn't really come into it. Maybe they shouldn't be pushing the user to do this low level 'development' just to get a driver/hardware working. He's trying to install a driver which is a reasonable exercise for the desktop. I know you could install a Windows driver no problem. The fact that Linux sometimes requires compilation of kernel modules etc makes Linux a difficult proposition for many.
To be user friendly, the command line should not be required for simple tasks like this.Even if this particular driver is a mess that shouldn't really come into it. Maybe they shouldn't be pushing the user to do this low level 'development' just to get a driver/hardware working.Well, yes, that was what I meant. The Linux desktop itself isn't harder at all than a Windows one. Some things are even easier, like installing programs (with the help of the repositories). But when it comes to installing drivers or hardware that is not supported out of the box it's often not so simple, unfortunately. There seem to be multiple ways of doing the same thing, which may be a good thing if you're really techie, but it scares normal users away. There really should be a uniform way of installing drivers in Linux too.
Mark will probaby now say 'there is', but the problem is there are always loopholes to do it in a different way, so the uniformity is compromised. (and sloppy programmers like the ones that made the driver for my touch screen get away easy). IMO they should develop a truly uniform way to do this, and also make it impossible to do it otherwise. But I don't know if this is even possible anymore due to the open nature of Linux.That said, this whole endevour has given me the opportunity (or better: a new reason ) to tinker with a Linux distro I've never used before (in this case Mint).
I must say I really like it. It's got a pretty familiar feeling to it and all I've tried (well, with the exception of getting that friggin' touch screen working) works really well.
I think I'll play around with it some more.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |