Bloody Linux
I have recently warmed to Linux.
I then immediately went off it again.
I tried to install a touchscreen. According to the webosphere it was going to be a relatively easy job. Sure it involved manually editting a few config files here and there, but no worries there.
Sadly it doesn't work.
Partially because the touchscreen isn't the model that has working Linux drivers, its a variant, so you have to download slightly different drivers for it, that have the same name, and there's no version info.
Partially because it took me a while to figure out which configuration file I was editting, (no, not XF86Config, \etc\X11\xorg.conf don't you know).
But mostly because the bloody board has jumpers on it that switch it between Windows compatability mode and Linux compatability mode, and I don't have the required diamond-edged drill bit, or ridiculously tiny alun keys that I need to break the bloody case open and remove said jumper.
A colleague, many moons ago, did get the touch screen working with the evil windows jumper in place. He doesn't remember how, and I can't figure it out, so after three days I'm doing something that I've never done before.... I'm giving up.
For an engineer to give up it typically involves threats to his/her family and an automatic weapon. Sadly, I simply can't afford to spend any more time on it.
This makes me sad and angry.
I've written an email to the manufacturers of the robot concerned explaining that the screen simply isn't responding to configuration requests, (annoyingly it is sending out info when you touch it, but I have no way of translating that info into a mouse pointer.) I'm actually begninning to think it would be easier to reverse engineer the protocol and write a decent driver for it myself.
I then immediately went off it again.
I tried to install a touchscreen. According to the webosphere it was going to be a relatively easy job. Sure it involved manually editting a few config files here and there, but no worries there.
Sadly it doesn't work.
Partially because the touchscreen isn't the model that has working Linux drivers, its a variant, so you have to download slightly different drivers for it, that have the same name, and there's no version info.
Partially because it took me a while to figure out which configuration file I was editting, (no, not XF86Config, \etc\X11\xorg.conf don't you know).
But mostly because the bloody board has jumpers on it that switch it between Windows compatability mode and Linux compatability mode, and I don't have the required diamond-edged drill bit, or ridiculously tiny alun keys that I need to break the bloody case open and remove said jumper.
A colleague, many moons ago, did get the touch screen working with the evil windows jumper in place. He doesn't remember how, and I can't figure it out, so after three days I'm doing something that I've never done before.... I'm giving up.
For an engineer to give up it typically involves threats to his/her family and an automatic weapon. Sadly, I simply can't afford to spend any more time on it.
This makes me sad and angry.
I've written an email to the manufacturers of the robot concerned explaining that the screen simply isn't responding to configuration requests, (annoyingly it is sending out info when you touch it, but I have no way of translating that info into a mouse pointer.) I'm actually begninning to think it would be easier to reverse engineer the protocol and write a decent driver for it myself.
