LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Laptop and Netbook
User Name
Password
Linux - Laptop and Netbook Having a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).

Notices


Reply
  Search this Thread
Old 10-13-2008, 05:14 PM   #16
phantom_cyph
Senior Member
 
Registered: Feb 2007
Location: The Tropics
Distribution: Slackware & Derivatives
Posts: 2,472

Original Poster
Blog Entries: 1

Rep: Reputation: 128Reputation: 128

Okay...the pathname is:

/lib/modules/2.6.24.5/kernel/drivers/input/touchscreen/mk712.ko

If it's there, why can't modprobe seem to find it?
 
Old 10-13-2008, 05:48 PM   #17
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; Slackware64-current (VM); Debian 12 (VM)
Posts: 8,290
Blog Entries: 61

Rep: Reputation: Disabled
If it's mk712, we've been using the wrong name. Try:
modprobe mk712
 
Old 10-13-2008, 06:42 PM   #18
phantom_cyph
Senior Member
 
Registered: Feb 2007
Location: The Tropics
Distribution: Slackware & Derivatives
Posts: 2,472

Original Poster
Blog Entries: 1

Rep: Reputation: 128Reputation: 128
With two terminals open, one using modprobe, and one showing the touchscreen module directory with the mk712.ko file, modprobe still turns up empty.
 
Old 10-14-2008, 04:42 AM   #19
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; Slackware64-current (VM); Debian 12 (VM)
Posts: 8,290
Blog Entries: 61

Rep: Reputation: Disabled
Mmm, I've no more ideas...The only thing I've had to do regarding modules is installing one for my ethernet connection for Slackware on my laptop. It was the atl2 module. Just downloaded the source, ran make, then copied the resulting atl2.ko to the modules directory.
I'm surprised no one else has contributed to this thread.
 
Old 10-14-2008, 10:45 AM   #20
phantom_cyph
Senior Member
 
Registered: Feb 2007
Location: The Tropics
Distribution: Slackware & Derivatives
Posts: 2,472

Original Poster
Blog Entries: 1

Rep: Reputation: 128Reputation: 128
I wish they would. With just the two of us, we're digging ourselves a deeper hole.
 
Old 10-17-2008, 12:58 PM   #21
phantom_cyph
Senior Member
 
Registered: Feb 2007
Location: The Tropics
Distribution: Slackware & Derivatives
Posts: 2,472

Original Poster
Blog Entries: 1

Rep: Reputation: 128Reputation: 128
Nudge....bump. You can't tell me that out of 300,000 people no one knows something.
 
Old 10-19-2008, 05:04 PM   #22
Glasswlkr
LQ Newbie
 
Registered: Oct 2008
Posts: 16

Rep: Reputation: 0
Hey guys, man I thought I was alone in this one!

I have been battling my Visionplates for some time now. Midori is pretty damn useless, and I have a lot of these things and would also love to get an OS working well.

We should think about starting a central project to house this for anyone like us working on getthing these things working. I know there is very little info on the web, perhaps a central home might attract more random searchers to put a bit more manpower behind things.

So far my progress:
I managed to get DSL running quite nicely. I have wifi and APM/ACPI working nicely with the visionplate hardware, as well as an accelerated X driver for the LynxEM chip in the visionplate.

Everything works great with the exception of touchscreen...

In that regard I have made some progress, but nothing tangible yet.

the DSL kernel comes with the mk712 module compiled into it, and I know for a fact the MK712 is the chip in the visionplate.

DSL also uses KDrive as a slim X server... The reason this is relevant is that there is a project available (originally written for nokia tablets I think) called TSLib. It is designed to run with KDrive.

Anyway, TSLib has builtin support for the MK712 chip (a simple config file change).

I have managed to build and install TSLib on DSL running on the visionplate, unfortunately I am having trouble getting tslib's test apps to talk to the device (they keep looking for /dev/touchscreen/something or /dev/input/event0) both of which appear duds on DSL right now. (even though I have run "modprobe mk712" and it runs successfully, and now mk712 shows as an active module, unfortunately I can't find a device under /dev that's mapped to it... Still struggling here...

Anyway, if anyone has any further input on that I would love to hear it!

I have a cheap mass hosting account, I can host a site for the short term with a forum and blog that we could use to centralize our visionplate development. Or if someone else wants to do that I don't care, I think it would be a good idea to centralize our work though, looks like there are a few of us out there fighting with these things, and I would love to get a working image (So if others get their hands on one of these, a simple image to the CF card and it's working).

The reason I like DSL is it is nicely built to work on the CF card without trashing the flash (using unionfs and ramdrive and such) it runs in minimal memory quite nicely, and once we get this all working I can easily build a mydsl extension for the visionplate, one single file, so that anyone can use a stock out of box dsl installation to the CF card, and add the visionplate.dsl file to their mydsl folder, and BAM working visionplate OS

Anyway lets keep this discussion going!

This is the first active conversation I have found for these things in months! (I have been working on mine since like July 2008)
 
Old 10-20-2008, 01:21 PM   #23
barmalei
LQ Newbie
 
Registered: Oct 2008
Posts: 9

Rep: Reputation: 0
Which version of DSL are you using? Before trying to get the touchscreen working under X you should be able to see it in /proc/bus/input/devices from command line.

You also need evdev together with mk712. Can you try doing
Code:
modprobe evdev
and then
Code:
cat /proc/bus/input/devices
and see if you have the touchscreen enabled?

I've seen a report that there is something with the MK712 driver in the recent kernels. I've had troubles trying to get the touchscreen recognized by the 2.6.25 (I think?) kernel under Slitaz. Everything worked except the touchscreen... BTW, Slitaz also uses KDrive.

I then found a report of somebody getting a working DSL on the Visionplate. Here is the link:

http://forum.puppyrus.org/index.php?...b&topic=320.30

I've tried Puppy Linux, specifically puppy-4.00-k2.6.21.7-seamonkey.iso. I got the touchscreen partially working, although with different drivers. The guy from the Russian forums used usbtouchscreen and on my Visionplate it had no effect so I used mk712.ko instead. I said "partially" because it's still weird - taps would register in the active window if I had tapped outside before. Probably, this can be further investigated but I didn't have time to finish everything properly.

The posts are in Russian but #35 has a working xorg.conf. Could probably use Google language tools or Babel to get an idea about the rest. Basically, the story is that you need a full Xorg install. It's not much use for you since you are trying to use kdrive but my attempts thus far have meant that you need a full Xorg together with evtouch to get the touchscreen to work under X.

I'm travelling at the moment and won't be able to access my Visionplate till early next week. I was planning on documenting everything once I got everything in order.

In the meantime, I can give the rough steps from the top of my head if there is any interest. Also I can help with the Russian forum if you have questions as I speak the language.

Last edited by barmalei; 10-21-2008 at 09:31 PM.
 
Old 10-21-2008, 09:48 AM   #24
Glasswlkr
LQ Newbie
 
Registered: Oct 2008
Posts: 16

Rep: Reputation: 0
I didn't know about enabling evdev. I ran modprobe evdev, and now the /dev/input/event0 and event1 are active (on the mouse and keyboard) but event2 and event3 are dead (invalid device error)

I don't have /proc/bus/input/devices at all (I don't even have /proc/bus/input)

I unloaded evdev and mk712, then loaded them in order, made no difference... I don't have /dev/touchscreen or /dev/ts or /dev/input/touchscreen or any of that... Not sure where mk712 is loading. I know that the mk712 module accepts parameters for io address, and irq and such, perhaps those need to be manually specified?

Anyone have any ideas there?

I am using DSL 4.4 I believe. It's a 2.4 Kernel.

I don't mind installing a full Xorg if that's what's needed, I am a bit concerned about the additional memory usage though.

I took a look at that thread you sent, I am eager to give that a try.

The main reason I gravitated to TSLib is it lists native support for mk712 as well as it comes with a calibration tool and whatnot.

I would love to hear your steps you used to get it to work, you (And the people in that russian thread) are the only people I have ever seen that have gotten this thing to work in linux and have some useful info available...

Did you ever get around the long boot time issue with any version of linux? DSL runs nice and fast and is stable, but it takes like a good 2 minutes to boot (As do every other linux distro I try) yet midori booted in like 10-15 seconds easy... (but midori is useless unfortunately lol)

Anyway any further information you can post would be GREATLY appreciated!

Thanks!
 
Old 10-21-2008, 06:29 PM   #25
barmalei
LQ Newbie
 
Registered: Oct 2008
Posts: 9

Rep: Reputation: 0
Sorry, I assumed it was a 2.6 kernel. Moreover, I confused DSL with Puppy Linux - my apologies. I don't have a way to try a 2.4 kernel until next week so just some some conjectures is all I can offer.

I'd venture to say you've got a resource conflict. Under 2.6 kernel in my case the touchscreen is registered on irq 10 as /dev/input/mouse1 (or /dev/input/event2) with both external USB keyboard and USB mouse connected before boot. Can you unload the mk712 once you boot with the keyboard and mouse attached and post a
Code:
cat /proc/interrupts
? If something grabs the irq 10 initially and the touchscreen can't get it when it's initialized by the kernel, then the kernel has to be told to reserve the interrupt 10 on boot. I think you are right about that. Not sure how to do it at the moment - will have to look it up.

It is possible to create the /dev/ts node for the touchscreen manually in order to get tslib working. It's not a problem that you don't have it at the moment because the equivalent node /dev/event2 is already there. The problem that has to be dealt with first, however, is to resolve the resource conflict (or at least this is what I think is happening) and get the touchscreen set up so that you get a response when you read from /dev/event2.

I see your point about using kdrive instead of Xorg. You seem to be pretty happy with kdrive's performance. I wish things were a little faster with Xorg - light programs such as terminal etc, load fast enough but the browser would take good 15-20 seconds to load. I didn't have time to look into that yet but I remember the Russian guy who got it working complaining about sluggishness. Could be something to do with the generic vesa driver, perhaps native Lynx makes a difference.

Boot time sounds about the same in my case as well. One reason I believe is that the default DSL kernel is built for the widest possible range of hardware. On the other hand Midori is optimised in this respect so there is one area in speed improvement - a kernel recompilation specifically for Visionplate hardware should help a little. Midori is also stripped down to a bare minimun - i.e. no hotplug (not sure about this one, though. Just don't remember seeing it there) or any other extra stuff.

Anyway, that's already a long post. I'll have to get my thoughts together and make another post with what I remember from the process. Should be able to do that shortly so please bear with me...

Last edited by barmalei; 10-22-2008 at 08:15 AM.
 
Old 10-21-2008, 08:19 PM   #26
barmalei
LQ Newbie
 
Registered: Oct 2008
Posts: 9

Rep: Reputation: 0
Forgot one thing... I've managed to get the touchscreen to respond with the mk712 module while the Russian forums talk about the usbtouchscreen module instead. Perhaps not all Visionplates are created equal and there might be some differences in hardware. My steps work for the mk712 but it's certainly possible to apply the same ideas with the usbtouchscreen module in case mk712 doesn't work out. In addition, all I've said applies to Puppy Linux and kernel 2.6, not Damn Small Linux which is 2.4 based.

Last edited by barmalei; 10-22-2008 at 08:11 AM.
 
Old 10-22-2008, 06:58 AM   #27
Glasswlkr
LQ Newbie
 
Registered: Oct 2008
Posts: 16

Rep: Reputation: 0
Awesome! Thanks for the feedback so far!

I will try this all out and post back my results within a day or two (have to work late tonight likely won't have a chance to touch the visionplate until tomorrow)

Thanks!
 
Old 10-22-2008, 07:47 AM   #28
Glasswlkr
LQ Newbie
 
Registered: Oct 2008
Posts: 16

Rep: Reputation: 0
Ok I had a few minutes this morning and couldn't resist...

Ok I did a fresh reboot from powered off with mouse/keyboard attached to usb (exactly how I normally boot it).

Once up, I checked if mk712 was loading on boot, it was not (I haven't done that yet as I don't have it working).

I checked /proc/interrupts and it shows irq 10 is free.

I do modprobe evdev

Then check /proc/interrupts (still nothing on irq 10)

Then modprove mk712

and check /proc/interrupts (it now shows mk712_touchscreen on irq 10)

tried cat /dev/input/event2
(no such device)

tried cat on all the other inputs, got the mouse on input0 and keyboard on input1

Tried all the mouse and mice ones under /dev/input as well, nothing on them (except mice points at the mouse).

Tried rebooting with the mouse disconnected only the keyboard hooked up.

Unloaded mk712

reloaded mk712

checked interrupts again

It still shows mk712_touchscreen on irq10

Check all the /dev/input/event files again, nothing on event0 (now it is no such device) event1 still has keyboard, event2 has no such device as well.

Not sure where to go from here
 
Old 10-22-2008, 09:35 AM   #29
barmalei
LQ Newbie
 
Registered: Oct 2008
Posts: 9

Rep: Reputation: 0
Hmm, looks similar to what I had with the recent 2.6.25 kernel. The mk712 module would load without errors but that's about it. I think this is a mk712 module issue, which can only be resolved by someone who knows how to change the driver to get it to cooperate.

Well, I should be able to post my Puppy steps shortly and hope at least something will be workable.
 
Old 10-22-2008, 10:21 PM   #30
barmalei
LQ Newbie
 
Registered: Oct 2008
Posts: 9

Rep: Reputation: 0
Okay, here comes... Please bear in mind that this is based on my memory so some things/names might be not exact but you should have an idea of what I'm trying to convey. Feel free to point out inconsistencies and I'll edit/correct them.

1. Downolad and install Puppy Linux 4.0 on a CF card.

Download a puppy-4.00-k2.6.21.7-seamonkey.iso from:

http://distro.ibiblio.org/pub/linux/...ns/puppylinux/

There are several ways to install. I had to use a separate machine for this. Burned the ISO on a CD and booted it. There is an install script which you need to run from the menu ('System Utilities'??). I had a CF reader connected to USB and wanted to do an install using a "CF wich will be used as a hard drive" option but the script died. I ended up doing an "Install to HD" option with the CF card used as hard drive. I've used a 2.5 IDE-to-CF adapter similar to this one:

http://www.addonics.com/products/fla...ad44midecf.asp

Since I had one lying around and it was less hustle for me to do that then to troubleshoot the install script. I already had one full partition with ext2 filesystem on the CF card before attempting to put the card with the adapter into the helper notebook.

I hope the installation process works for you and you won't need an adapter. The script asks some basic questions about partitions and does formatting and copying but I've found that a pre-formatted ext2
partition works better for the script. Besides, when GRUB is invoked as a last step during the installation it's straightforward to setup it to /dev/hda since this is how it'll be when the card is in the Visionplate.

2. Stick the CF with the installed Puppy into the Visionplate and boot with the mouse and keyboard attached.

I had a USB hub attached to one of the ports. Comes in handy for a USB ethernet adapter or using a flash drive for some extra files (see #4). Make sure you pick Xorg during the boot. Puppy will create a xorg.conf, wich will need to be edited later.

3. Open the terminal and
Code:
modprobe evdev && modprobe mk712
Do a
Code:
cat /proc/bus/input/devices
and look for the "Touchscreen MK712 section". There should be a line that looks something
like H: Handlers=mouse1 event2. If you see it, the /dev/input/event2 will be your touchscreen device node. Usually, that is the default with USB and keyboard attached. To confirm kill X with Crtl-Alt-Backspace and do a
Code:
cat /dev/input/event2
and tap on the screen a couple of times. You should see some binary garbage characters, which is a good thing and means that the touchscreen is responding. Ctrl+C quits the cat command and
Code:
xwin
gets you back to X.

4. Download evtouch-0.8.7.tar.gz (link at the bottom of the page) from:

http://www.conan.de/touchscreen/evtouch.html#config%22.

For #4 through #6 I basically followed the instructions for evtouch installation from the link just above. You can either download the file and untar it directly on the Visionplate if you have networking set up or use another computer and copy it to a USB flash drive and then connect the drive to the hub and mount it on the Visionplate (that's what I did).

5. Untar the evtouch-0.8.7.tar.gz somewhere and copy evtouch_drv.so to /usr/lib/xorg/modules/input/


6. Edit /etc/X11/xorg.conf and add the following (it's a good idea to make a backup copy of xorg.conf first just in case):

a. Add the following line to the section "ServerLayout"

Code:
InputDevice "touchscreen0" "CorePointer"
b. Add a new InputDevice section with the following text
Code:
Section "InputDevice"
	Identifier "touchscreen0"
	Driver "evtouch"
	Option "DeviceName" "touchscreen"
	Option "Device" "/dev/input/event2"
	Option "SwapX" "false" ## default false
	Option "SwapY" "true"
	Option "MinX" "152"
	Option "MinY" "224"
	Option "MaxX" "4031"	
	Option "MaxY" "4001" 
	Option "ReportingMode" "Raw"
	Option "SendCoreEvents" "On" 
EndSection
Note the second option statement uses event2 node as an argument and it has to be the same as shown by cat /proc/bus/input/devices in #3. You will have to change event2 to whatever eventX showed up as the touchscreen. Also note the SwapY "true" option. With "false" I initially had Y-axis movements reversed and the cursor would move okay along X-axis but in the opposite direction vertically. You can change back to "false" if that happens to you with the current "true" option.

7. Kill X with Ctrl-Alt-Backspace and run it again with

Code:
xwin
(This assumes you already have the edits in xorg.conf so X is run with the new options)

8. Feel free to experiment with other evtouch options - everything is documented on the homepage.

9. You can make the touchscreen modules to load on every boot. Just edit /etc/rc.d/rc.local and add the necessary commands there

Code:
modprobe evdev
modprobe mk712
Now, by all means it's not the end. This just gets the touchscreen to respond but things need to improve to work perfectly. I already mentioned the touchscreen weirdness. Curious if anybody else would experience similar behavior.

Another thing to watch out for is that unlike udev, hotplug in Puppy assigns device nodes depending what peripherals are connected at boot time. This means that if you disconnect your mouse and keyboard and boot, your touchscreen will default to /dev/input/event0 but the xorg.conf will still be set up to use /dev/input/event2. One way to get around this is to use different xorg configurations as per below (see #(10))

http://www.murga-linux.com/puppy/vie...fc4292217e07e1

Okay, now let the fun begin - looking forward to hear some good news!

Last edited by barmalei; 10-22-2008 at 11:10 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
touchscreen driver (or get it running somehow) Bodo Linux - Hardware 2 12-02-2009 11:28 AM
Trouble connecting serial touchscreen driver VDTDriver Linux - Hardware 0 07-07-2008 10:34 AM
Need Hitachi CM813 plus Monitor FC6 Driver (can't code) Person_1873 Linux - Hardware 6 01-05-2008 05:26 AM
Touchscreen driver on suse 10.3 ph73nt SUSE / openSUSE 2 12-21-2007 07:00 AM
Touchscreen driver bob755 Mandriva 3 02-19-2007 06:12 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Laptop and Netbook

All times are GMT -5. The time now is 08:52 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration