usb serial quits early on quad

I am following all instructions in the manual for usb serial from linux PC to Udoo. I am using udoobuntu 2.0 minimal edition.

It seems to work when it boots but it quits before I can login. Using minicom I get:

(SNIPPED)

Code:

[    3.130526] init: mounted-proc main process (119) terminated with status 1
[   10.927096] NET: Registered protocol family 10
[   12.554004] ov5640_read_reg:write reg error:reg=300a
[   12.603421] ERROR: v4l2 capture: slave not found!
[   12.612184] ERROR: v4l2 capture: slave not found!
[ OK ]ding cpufreq kernel modules...       
 * CPUFreq Utilities: Setting ondemand CPUFreq governor...         * CPU0...         * CPU1...
[ OK ]  * CPU2...         * CPU3...       
[ OK ]rting Postfix Mail Transport Agent postfix       
[ OK ]ting sysfs variables...       

It always stops at "sysfs variables..." and minicom says "offline" in the status bar.

On the client side I am using debian stable jessie. Anybody have any ideas?

 

Just confirmed it's doing the same thing in windows 7 too.

 

So now I connect to the HDMI and when I boot I see the Udoo logo but then no text console. I seem to remember there was a text console when I first installed Ubuntu minimal... could this be a bug caused by an update?

As it stands the only way I can access it is by ssh.

EDIT: this was with the serial USB OTG port not connected.

 

Have you enabled HDMI via UENV?

 

I haven't touched uEnv.txt but isn't that only for displays? The serial USB should still work without touching it right?

 

Also just to be sure... the USB serial driver has *nothing* to do with firewalls right? I ask because I've seen firewire using IP addresses.

 

If you mean USB direct connection then it has everything to do with firewalls/network. It is creating a network connection. If you disable incoming connections with a firewall it will not work. What firewall settings did you do?

 

For a reference how the USB direct connection is setup you could have a look at the following Neo documentation page (I could not find the Quad equivalent so it could not apply!) http://www.udoo.org/docs-neo/Hardware_Reference/PC_USB_interface.html

 

OK I think I know what happened now. The default rules for UFW are corrupt or something. The first time I enabled ufw it locked me out of ssh even on reboot so I added these rules:

Code:

### tuple ### allow any 22 0.0.0.0/0 any 0.0.0.0/0 in
-A ufw-user-input -p tcp --dport 22 -j ACCEPT

As soon as I enable UFW it is locking me out until I reboot now. Then it let me in but without ufw enabled. Here is what it does before locking me out of ssh:

Code:

root@udoo:/home/sombunall# ufw default deny incoming
Default incoming policy changed to 'deny'
(be sure to update your rules accordingly)
root@udoo:/home/sombunall# ufw default allow outgoing
Default outgoing policy changed to 'allow'
(be sure to update your rules accordingly)
root@udoo:/home/sombunall# ufw allow ssh
Skipping adding existing rule
root@udoo:/home/sombunall# ufw allow samba
Skipping adding existing rule
root@udoo:/home/sombunall# ufw enable
ERROR: problem running ufw-init
modprobe: FATAL: Module nf_conntrack_ftp not found.
modprobe: FATAL: Module nf_nat_ftp not found.
modprobe: FATAL: Module nf_conntrack_netbios_ns not found.
iptables-restore: line 4 failed
iptables-restore: line 77 failed
iptables-restore: line 30 failed
iptables-restore: line 37 failed

Problem running '/etc/ufw/before.rules'
Problem running '/etc/ufw/after.rules'
Problem running '/lib/ufw/user.rules'

I wonder what the heck is wrong?

 

This is the last thing I see in logs before I have to reboot:

Code:

Feb  7 00:38:48 localhost kernel: [  118.809610] ip_tables: (C) 2000-2006 Netfilter Core Team

 

I think it's related to this bug:

https://github.com/dnschneid/crouton/issues/815

Will have to fix it myself I guess and pretend Udoo is an openVZ VM? Is that what you guys do?

 

This depends on your firewall configuration, not on UDOO, I guess

 

Marking thread as solved and linking to ufw thread:

http://www.udoo.org/forum/threads/anyone-succesufuly-run-ufw-in-udoobuntu-minimal-2-1-2.6490/

 

I'm not I get what you mean, anyway I've removed the SOLVED tag following your post.

 

Ok here's why I think it's solved. You have USB serial which Waltervl says goes through the network driver. I don't know how it works exactly but I think it must use IP header only since it uses no TCP/UDP ports. At one point before I made any configuration changes but only installed ufw and enabled it, the udoo *would* boot but then as soon as ufw turned on it would block the serial console (and all other servers like ssh and samba) before it is completely done booting. Therefore this is a firewall problem. I posted in the other thread about what I've done about it so far. Also if anybody knows how USB serial works network-wise please enlighten me because I searched the internet and failed.

link about raw IP header: http://www.zytrax.com/tech/protocols/tcp.html

 

ALSO! Reply # 6:

https://www.udoo.org/forum/threads/no-hdmi-after-some-config-change.7137/#post-27426