Serial connection error (Ubuntu 14.04 LTS)
-
Thanks...progress, I think.
- entering 'modinfo cp210x' gives me a lot of info. So this tells me it's installed.
- I also checked to see if 'modinfo usbserial' will also give me some info. And yes, it does.
This is where I see a problem...
when I execute 'ls /dev/ttyUSB*', I get nothing. (No such file or directory)
The Omega is powered up and turned on. I can access it via wifi... but I can't access it via USB (and it looks like the USB attachment is not being detected).
I'm currently connecting my computer to the USB port of the Extension Dock.
-
@Enrico-Bermudez said: Can you try
ls /dev/tty.USB*. You missed the dot in the command you posted previously.
-
I tried 'ls /dev/tty.USB*' also -- and it didn't any file.
Screenshot immediately below:
Here's where I got the command without the period (from the Getting Started webpage).
By the way, I just switched to the MiniDock, in case there's something wrong with my Extension Dock. Same results when using the MiniDock.
Thanks for the help!
-
@Enrico-Bermudez Oh, that's my mistake. I was so used to the tty naming convention under mac.
/dev/ttyUSB*is correct for Linux.Hmmm, were you able to run
sudo insmod /lib/modules/<kernel-version>/kernel/drivers/usb/serial/usbserial.koline okay? That should have installed the kernel module already...
-
I ran it, but from what I recall, I ran into an error the first time I ever ran it. It says the file exists.
When I ran 'modinfo usbserial', I got information back. So I assume that it's already installed. But to be honest, I don't recall whether it was already installed before I embarked on tinkering with the Omega.
-
@Enrico-Bermudez Can you
cpthe file into/lib/modules/<kernel-version>/kernel/drivers/usb/serial/under a different name, and try toinsmodagain? One possible reason is that theusbserial.kois for a different USB-serial driver, and the current one can't be installed because of a name conflict.
-
Do you mean copy the cp210x.ko into that folder (under a different name) and run insmod again using that file?
-
@Enrico-Bermudez Yup.
-
Same result as the original error message: Invalid module format.
-
@Enrico-Bermudez What happens if you do
insmodwith-fflag?
-
Using -f, I still get the same error "Invalid module format"
-
@Enrico-Bermudez Really strange.. I think i will setup a Ubunt 14.04 installation and try it out myself. I will let you know if I discover anything. Meanwhile, I can confirm that they work on Ubuntu 15.04 and 15.10.
-
@Enrico-Bermudez can you post a photo of your Omega setup?
-
I had a problem in windows where it wouldnt recognise the device, it would power fine though. I had a cheap cable that stopped being able to charge my iphone (with a lightning adapter).
I changed my cable and it started to recognise it. I wonder if the kernel recognises the serial device (as did my winblows machine) but cant access it properly.
Worth a punt
-
@Enrico-Bermudez If the module is present already (i.e. modinfo gives you output), try just "sudo modprobe cp210x". That should make Linux pull in all the dependencies automatically and be easier to deal with than insmod.
(Also worth noting on Ubuntu, when /dev/ttyUSB0 gets created, no user account will have permission to access it. You'll need to use "sudo screen /dev/ttyUSB0 115200" or add yourself to the dialout group with "sudo usermod -a -G dialout [your_user_name]" and then log out and back in again.)
-
@fader , I get an "Exec format error" when I do a modprobe on cp210x
-
@Lazar-Demin , here you go:
-
@Sawyer-McBride , I changed the USB cable, but there was no change in status. The issue persists. Thanks for the tip.
-
@Enrico-Bermudez Are you on 64 bit or 32 bit? If my compilation works I can send you the
.kofile.
-
@Boken-Lin, I'm on a 64-bit machine. (x86_64)
