I noticed some issues with my wifi dongle once I set the usb speed to 1, but I never followed through with getting everything running together.
I get a camera board this weekend so I will be back in there and will update if I find any issues.

Thanks for the suggestions, I’ve been making some progress.
Its been so long since I’ve used computers that requires thinking about and my brain wasn’t in gear. I had the new raspbian download and was installing the old mimo drivers. I have since downloaded all the updated files and rebuilt everything and am at the point where it seems to be a clean boot, finding all the drivers etc, the keyboard is working and I can get into the desktop (need to by a mouse!)

The USB screen however, steadfastly refuses to do much. Basically, it turns green part way through the boot.
I am just in the process of checking that I have done some of the calibration bits detailed in your how to above…

I just added the dwc_otg.speed=1 line to the cmdline.txt file and on the next boot, I got lots of USB errors and the keyboard didn’t work.
Reverting back and removing the line and I am now getting error -71 which I never used to get!

here is where I am at:
running apt-gets made things worse, so I started again from scratch.

build my OS
copied over the modules and firmware directories onto /boot and then copied them into the correct place on the linux partition.

ls /lib/modules
3.6.11+ 3.6.11-mimo+

I have copied across the kernel file and renamed it. For space, i removed the old kernel file and emergency kernel file from the boot partition.

At this point, I can boot up and the keyboard/mouse are detected and i can get to the desktop and things work.
There are some error -71’s on boot up which I assume are the touchpad as the only devices listed in /dev/input/by-id are the mouse and keyboard and the screen appears to be seen at boot and changes to a green screen part way through booting. Trying to add the speed=1 line to fix the errors makes things worse – see below!

Where things go wrong are:

Adding dwc_otg.speed=1 to the cmdline.txt causes errors on the next boot and the system is then unresponsive to keyboard. I can SSH in and remove the speed line and reboot and the keyboard etc starts to work again.

When i copy xorg.conf into the X11 directory, I am no longer able to boot into the desktop.

Any thoughts on these 2 issues?

Also, could you explain ‘when’ and ‘how’ I would expect to see a proper image on the mimo screen.

i.e. does it only show in the desktop? does it only show if you boot without the HDMI connected?

Many thanks,

I have attached the startup message as I am sure you may see something I don’t!

hope you don’t mind me dumping my thoughts here – they may help someone else at some point.
I have just read the entire conversation and picked up on a few things that I had missed.

When adding the speed= to cmdline.txt – it stops my keyboard working and the pi doesn’t boot – however, if i remove the keyboard and mouse, the pi does boot and the touchscreen appears to detect and work, i need to calibrate it – but it is working.

HOWEVER – I still can’t get anything but a green screen from the display!

Hi Ben, I wasn’t able to look at this this weekend, but I’m at work right now so I’ve only skimmed your replies.
The fact that your screen turns to green during boot is a good sign! Now all you should need is a properly configured /etc/X11/xorg.conf file and the screen should work as a display. You won’t see the startup/boot text on the mimo, but about 5 seconds after booting you should see the screen turn green, and then about 10 seconds later it should turn black, followed by the desktop. For me, I had to keep HDMI connected for the pi to turn on.
I’m still pretty new to linux, so the only thing I’ve found yet (through other ppl on the forums) that gets the touchscreen to work is to add the ‘dwc_otg.speed=1’ line, which drops the usb speed from 2.0 to 1,0 (from my understanding) This fixes the error -71s that show up when the touchscreen fails to initialize. For me, all my devices seem to operate correctly, but I could understand why this might cause issues for certain devices.
Currently I don’t know how else to get the touch screen working without that hack, so I’d recommend asking in the forums. There are a lot of smarter people in there 🙂

I just cur the xorg.conf back to the first monitor section and voila, the screen is working.
I’ll try getting the touch screen to work at the same time tomorrow – it will probably mean that I can’t get the keyboard working but ultimately, it won’t have a keyboard connected anyway.

Thanks, I have my Mimo 710 S working with Keyboard, wireless mouse, WiFi. If no one noticed, Option “InvertX” “true” should be False. I loaded the modules and it did not get the Mimo’s touch screen to work until I used the kernel that came with 3.6.11-mimo.tgz

I made a number of changes before this, so I don’t know if those changes in combination with the advice on this blog worked together, so I am starting a new SD from scratch. I will link this blog in my next blog. Thanks again.

I recently noticed all the difficulty people are reporting configuring the 720-S it seems like it would be useful to setup a test environment and see what might be tripping them up. I’m in the U.S. on central time so it will be a bit until I have some results but I’m very curious as to why this is happening.

It seems that the speed setting and the /lib firmware & modules mess things up. I’m looking primarily just to use the MIMO w/out the touch screen (for now). With just the modified kernel , the MIMO xorg.conf and a USB cable with a singular male jack I get the boot screen & input on my HDMI. Then I do a startx and the MIMO desktop GUI comes up perfectly on the MIMO as a display but this display does not respond to input. I suspect that if I bought a dual male usb cable that the MIMO monitor may be able to be powered early on in the boot process and obtain input configuration. Can the MIMO be the singular display or is another primary display (hdmi) required to get this all working? Thanks in advance.

We’ve pretty much ruled out the power issue, unless your hub/ac adapter is less than 600ma, especially since your display works. In the original forum, someone found that setting the USB speed to 1.1 speeds would cause the proper screen initialization, but found it would negatively affect some other usb 2.0 devices. So far it’s the only solution to get touch input working that I know of. But I’d love to find a way that didn’t affect the USB speed!
I also found that the pi wouldn’t boot if nothing was plugged into the HDMI port, so I lobbed off the end of a spare HDMI cable and used that to plug in and make the pi think it had a screen plugged in. I think I read later on that you can turn off the HDMI requirement for boot in some setting, but I never actually tried.

Hi ,
Thanks for your kind attention. The next thing I may try since the kernel.img and Xorg.conf work great for the display is to add mouse and keyboard definitions to the Xorg.conf. (I love this stuff but am more on the order of a weekend warrior). Why were mouse and keyboard definitions not included in the posted Xorg.conf?

For me, I never had to include anything in the xorg.conf that listed my keyboard and mouse, they just worked. Someone in the forums was using a bluetooth keyboard and had to add some lines to xorg.conf, but I was using a standard usb keyboard and mouse, and had no issues without adding any lines for them. Hopefully yours just works as well!

Hello Folks
I have just got my Raspberry Pi 3 running Raspian from NOOBS and trying to get Samsung U-70 (no touchscreen) working but stuck at Green Screen. Tried creating xorg.conf and adding in text as suggested in this thread (without the touchscreen part of the text) but still stays green. Any suggestions welcomed please.

Hi Neil,
Sorry I missed this post! I do not have any ideas for you besides reading your dmesg output and making sure the screen is showing up correctly. Beyond that, there are a bazillion reasons it might not be working, most of which are over my head! Perhaps the device id needs to be updated in the xorg.conf? I’m not sure, but if you get it working let us know! Thanks!

Hi!
Thanks for this post. It is a bit dated, but still I tried to compile the github kernel to have usb touch screen support. I have rapsberry pi 3 with latest raspbian distro.

I copy the compiled kernel “Image” in place of kernel7.img, I in fact followed all the steps in the post….. but RPI does not even boot! I have no screen for it except the usb touch screen, so i cannot access any error message…

Any idea? Am I missing something? I’ll look into raspberry system logs stored on the SD card, if any info is there…..
Kernel install is just copying Image in the boot directory? and make modules_install. That’s all? What about the System/map file for example?

Hi Gandji,
Unfortunately I have not tried this with a raspi3, so I’m not sure if there are any other steps required, or if there have been big changes since the last time I tried this. I have been using the raspi foundation touchscreen without issue, so it’s been a while since I tried getting the mimo display to work.
If you have set up your xorg.conf file, try renaming it to something else so the kernel doesnt try to use it and see if you can get any output to the monitors, otherwise, I’m not sure what could be wrong.
I might be able to try and test it myself, but it wouldn’t be a for a while, sorry