Re: [beagleboard] Re: Beaglebone Black Rebooting Several Times Every Day

[William Hermans]

I do not know what to tell you other than . ..




*william@arm:~$ uptime 23:30:30 up 26 days,  6:34,  1 user,  load average:
0.00, 0.01, 0.05*
This board is also loading it's rootfs via NFS, so it is constantly using
the local network. SO, this has been an ongoing problem for you, and going
on longer than a month ? Well All i can say is that you better get busy and
finding your problem. I suggest you start from a scratch build, and
incrementally install what you need one bit of software at a time until
something starts misbehaving. This is very obviously a software issue, and
despite what you say about having watchdog disabled I'm still of the
opinion that this *has* to be watchdog related. Otherwise you'd be
broadcasting a system wide kernel signal.



On Mon, Oct 13, 2014 at 11:02 PM, Thomas Olofsson 
wrote:

> We still have the same issues with reboots as well. we have had to move
> our project to bbw for now instead. the bbw with the same kernel and no
> reboots for two weeks. The BBB reboots on an average og 1-2 times per 24
> hours independent of load.
>
> No serial messages. No kernel messages, no oops. We have also tried a
> kernel wo watchdog support with no avail...
>
> Any suggestions is highly appreciated at this point..
>
> --Skjortan!
>
> On Mon, Oct 13, 2014 at 8:37 PM, Greg Kelley  wrote:
>
>> Mine is still resetting one to three times a day. I have moved both
>> processes I was running on it (CUPS and weewx) over to my RasPi so it is
>> just sitting idle except for CRON jobs. No events in serial debug logs,
>> just a sudden reset and cold boot restart.
>>
>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/vgeh336p0P4/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Beaglebone Black Rebooting Several Times Every Day

[Thomas Olofsson]

We still have the same issues with reboots as well. we have had to move our
project to bbw for now instead. the bbw with the same kernel and no reboots
for two weeks. The BBB reboots on an average og 1-2 times per 24 hours
independent of load.

No serial messages. No kernel messages, no oops. We have also tried a
kernel wo watchdog support with no avail...

Any suggestions is highly appreciated at this point..

--Skjortan!

On Mon, Oct 13, 2014 at 8:37 PM, Greg Kelley  wrote:

> Mine is still resetting one to three times a day. I have moved both
> processes I was running on it (CUPS and weewx) over to my RasPi so it is
> just sitting idle except for CRON jobs. No events in serial debug logs,
> just a sudden reset and cold boot restart.
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/vgeh336p0P4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: root password BBB ubuntu

[janszymanski12345]

finally solved

On Tuesday, 14 October 2014 14:43:57 UTC+11, janszyma...@gmail.com wrote:
>
> "In theory , there is no difference 
> between theory and practice. But, in practice, there is. "
>
> I have modified the file /etc/ssh/sshd_config according to 
> http://askubuntu.com/questions/469143/how-to-enable-ssh-root-access-on-ubuntu-14-04
> ,
> but still no root access through ssh.
>
> # Package generated configuration file
> # See the sshd_config(5) manpage for details
>
> # What ports, IPs and protocols we listen for
> Port 22
> # Use these options to restrict which interfaces/protocols sshd will bind 
> to
> #ListenAddress ::
> #ListenAddress 0.0.0.0
> Protocol 2
> # HostKeys for protocol version 2
> HostKey /etc/ssh/ssh_host_rsa_key
> HostKey /etc/ssh/ssh_host_dsa_key
> HostKey /etc/ssh/ssh_host_ecdsa_key
> HostKey /etc/ssh/ssh_host_ed25519_key
> #Privilege Separation is turned on for security
> UsePrivilegeSeparation yes
>
> # Lifetime and size of ephemeral version 1 server key
> KeyRegenerationInterval 3600
> ServerKeyBits 1024
>
> # Logging
> SyslogFacility AUTH
> LogLevel INFO
>
> # Authentication:
> LoginGraceTime 120
> #PermitRootLogin without-password
> PermitRootLogin yes
> StrictModes yes
>
> RSAAuthentication yes
> PubkeyAuthentication yes
> #AuthorizedKeysFile%h/.ssh/authorized_keys
>
> # Don't read the user's ~/.rhosts and ~/.shosts files
> IgnoreRhosts yes
> # For this to work you will also need host keys in /etc/ssh_known_hosts
> RhostsRSAAuthentication no
> # similar for protocol version 2
> HostbasedAuthentication no
> # Uncomment if you don't trust ~/.ssh/known_hosts for 
> RhostsRSAAuthentication
> #IgnoreUserKnownHosts yes
>
> # To enable empty passwords, change to yes (NOT RECOMMENDED)
> PermitEmptyPasswords no
>
> # Change to yes to enable challenge-response passwords (beware issues with
> # some PAM modules and threads)
> ChallengeResponseAuthentication no
>
> # Change to no to disable tunnelled clear text passwords
> #PasswordAuthentication yes
>
> # Kerberos options
> #KerberosAuthentication no
> #KerberosGetAFSToken no
> #KerberosOrLocalPasswd yes
> #KerberosTicketCleanup yes
>
> # GSSAPI options
> #GSSAPIAuthentication no
> #GSSAPICleanupCredentials yes
>
> X11Forwarding yes
> X11DisplayOffset 10
> PrintMotd no
> PrintLastLog yes
> TCPKeepAlive yes
> #UseLogin no
>
> #MaxStartups 10:30:60
> #Banner /etc/issue.net
>
> # Allow client to pass locale environment variables
> AcceptEnv LANG LC_*
>
> Subsystem sftp /usr/lib/openssh/sftp-server
>
> # Set this to 'yes' to enable PAM authentication, account processing,
> # and session processing. If this is enabled, PAM authentication will
> # be allowed through the ChallengeResponseAuthentication and
> # PasswordAuthentication.  Depending on your PAM configuration,
> # PAM authentication via ChallengeResponseAuthentication may bypass
> # the setting of "PermitRootLogin without-password".
> # If you just want the PAM account and session checks to run without
> # PAM authentication, then enable this but set PasswordAuthentication
> # and ChallengeResponseAuthentication to 'no'.
> UsePAM yes
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: root password BBB ubuntu

[janszymanski12345]

"In theory , there is no difference 
between theory and practice. But, in practice, there is. "

I have modified the file /etc/ssh/sshd_config according to 
http://askubuntu.com/questions/469143/how-to-enable-ssh-root-access-on-ubuntu-14-04,
but still no root access through ssh.

# Package generated configuration file
# See the sshd_config(5) manpage for details

# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
#ListenAddress 0.0.0.0
Protocol 2
# HostKeys for protocol version 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key
HostKey /etc/ssh/ssh_host_ed25519_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes

# Lifetime and size of ephemeral version 1 server key
KeyRegenerationInterval 3600
ServerKeyBits 1024

# Logging
SyslogFacility AUTH
LogLevel INFO

# Authentication:
LoginGraceTime 120
#PermitRootLogin without-password
PermitRootLogin yes
StrictModes yes

RSAAuthentication yes
PubkeyAuthentication yes
#AuthorizedKeysFile%h/.ssh/authorized_keys

# Don't read the user's ~/.rhosts and ~/.shosts files
IgnoreRhosts yes
# For this to work you will also need host keys in /etc/ssh_known_hosts
RhostsRSAAuthentication no
# similar for protocol version 2
HostbasedAuthentication no
# Uncomment if you don't trust ~/.ssh/known_hosts for 
RhostsRSAAuthentication
#IgnoreUserKnownHosts yes

# To enable empty passwords, change to yes (NOT RECOMMENDED)
PermitEmptyPasswords no

# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
ChallengeResponseAuthentication no

# Change to no to disable tunnelled clear text passwords
#PasswordAuthentication yes

# Kerberos options
#KerberosAuthentication no
#KerberosGetAFSToken no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

X11Forwarding yes
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
#UseLogin no

#MaxStartups 10:30:60
#Banner /etc/issue.net

# Allow client to pass locale environment variables
AcceptEnv LANG LC_*

Subsystem sftp /usr/lib/openssh/sftp-server

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM yes

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: root password BBB ubuntu

[William Hermans]

Sound like someone needs to take their time to learn the OS(es) they're
using. Basically this is Debian  / Ubuntu 101, and you should seek
information / guidance in those channels. And not bother Robert with such
basic questions . . .

This is what I personally think anyway.

On Mon, Oct 13, 2014 at 7:06 PM, Robert Nelson 
wrote:

> On Mon, Oct 13, 2014 at 8:15 PM,   wrote:
> > Robert,
> >
> >  I did again an eMMC flasher and now temppwd works, but still unable to
> > login as root
> >
> > login as: ubuntu
> > ubuntu@192.168.7.2's password:
> > Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.8.13-bone63 armv7l)
> >
> >  * Documentation:  https://help.ubuntu.com/
> > Last login: Tue Oct 14 01:04:07 2014 from 192.168.7.1
> > ubuntu@arm:~$ sudo passwd root
> > [sudo] password for ubuntu:
> > Sorry, try again.
> > [sudo] password for ubuntu:
> > Enter new UNIX password:
> > Retype new UNIX password:
> > passwd: password updated successfully
> > ubuntu@arm:~$ sudo passwd -u root
> > passwd: password expiry information changed.
> > ubuntu@arm:~$
> >
> > login as: root
> > root@192.168.7.2's password:
> > Access denied
> > root@192.168.7.2's password:
>
> Well, did you reconfigure sshd to allow root access? root over ssh is
> a serious security hole and is NOT enabled by default in
> openssh-server..
>
> Couple hints here:
>
> http://lmgtfy.com/?q=ubuntu+allow+root+ssh
>
> Regards,
>
> --
> Robert Nelson
> http://www.rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Does anuone tried F2FS on a 3.8.13* kernel ?

[meino . cramer]

Hi,

does anyone tried the F2fS filesystem with a 3.8.13-* kernel?
Is it useable, good, recommended, ?

Best regards,
mcc


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: root password BBB ubuntu

[Robert Nelson]

On Mon, Oct 13, 2014 at 8:15 PM,   wrote:
> Robert,
>
>  I did again an eMMC flasher and now temppwd works, but still unable to
> login as root
>
> login as: ubuntu
> ubuntu@192.168.7.2's password:
> Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.8.13-bone63 armv7l)
>
>  * Documentation:  https://help.ubuntu.com/
> Last login: Tue Oct 14 01:04:07 2014 from 192.168.7.1
> ubuntu@arm:~$ sudo passwd root
> [sudo] password for ubuntu:
> Sorry, try again.
> [sudo] password for ubuntu:
> Enter new UNIX password:
> Retype new UNIX password:
> passwd: password updated successfully
> ubuntu@arm:~$ sudo passwd -u root
> passwd: password expiry information changed.
> ubuntu@arm:~$
>
> login as: root
> root@192.168.7.2's password:
> Access denied
> root@192.168.7.2's password:

Well, did you reconfigure sshd to allow root access? root over ssh is
a serious security hole and is NOT enabled by default in
openssh-server..

Couple hints here:

http://lmgtfy.com/?q=ubuntu+allow+root+ssh

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] "You can't brick it"

[William Hermans]

The following is an "EXACT STEPS" txt log i made while setting up g_serial
from Linux, to WIndows. Note, that the Windows driver will be different for
g_multi, but the process is essentially the same.

lsmod
sudo modprobe g_serial
lsmod
ls -la /dev/ttyGS*
sudo nano /etc/inittab
> T1:23:respawn:/sbin/getty -L ttyGS0 115200 vt102
sudo init q <--- This reloads /etc/inittab without having to reboot.
sudo nano /etc/modules
> add g_serial save and exit. If you want the module loaded
automatically at boot.

Windows 7 host:
open start menu
right click computer
select properties
click windows update on lower left side
click check for updates on top left side
After searching windows update should find additional hardware to install.
"ELMO LTD GMAS" device.
Select this update, and install.
open start menu
right click computer
select properties
click device manager top left
expand "Ports(COM & LPT )"
select "ELMO GMAS(COMx)", where "x" is a valid COM port number. For me this
was COM3
rightclick and select properties.
Select the port settings tab on the top
Change Bits per second to 115200
Change Flow control to none
Click ok, and we're done here.
Download, install, then open puTTY ( google is your friend ).
Once open you'll be on the puTTY configuration page.
COnnection type change to serial.
Serial line change to the COMx value listed in device manager ( again for
me COM3 ).
Change speed from 9600 to 115200
Saved session change to your com port number ( COM3 for me )
On the very bottom left click serial.
Change FLow control to none.
Click Session on top left side, make sure all settings are as set above and
click the save button on the far side middle( ish ).
Now on the bottom right click the Open button.
type in valid non root user name on the BBB.
Followed by the usernames passwd.
DOne.

On Mon, Oct 13, 2014 at 6:27 PM, William Hermans  wrote:

> g_serial would not be ssh though. As you most definitely know..
>
> I was actually gong to suggest that he use g_serial( or whatever the
> g_multi equivalent is ). It's mostly foolproof, once one knows how to setup
> puTTY for it.
>
> By the way, puTTY defaults to XON/XOFF COMs I think, and between windows
> and puTTY they're almost never the  same. Until made so. So, check device
> manager to see what windows has set for the serial device, and just make
> sure puTTY is exactly the same.
>
> On Mon, Oct 13, 2014 at 5:04 PM, Robert Nelson 
> wrote:
>
>> On Mon, Oct 13, 2014 at 6:46 PM, William Hermans 
>> wrote:
>> > Robert, it is very unlike there is anything wrong with puTTY. I've been
>> > using it for years, and it's always been rock solid.
>> >
>> > The problem is more likely user error. Meaning this person does not know
>> > enough about Linux to realize that network managers sometimes LOVE to
>> screw
>> > with ones mind. . .  But since there was no mention of a network scan
>> for
>> > alternative DHCP address . . . how could we know.
>>
>> I "think" he might be logging in via putty over serial and then
>> rebooting the beaglebone. But not restarting putty.. It's a virtual
>> usb serial, so when the bbb reboots that usb serial device
>> disconnects. (putty doesn't correct for this..) Then when the bbb
>> comes up again, it reinitailzes the usb flash/ usb networking / usb
>> serial gadgets..
>>
>> Otherwise it works for me..
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> http://www.rcn-ee.com/
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] "You can't brick it"

[William Hermans]

g_serial would not be ssh though. As you most definitely know..

I was actually gong to suggest that he use g_serial( or whatever the
g_multi equivalent is ). It's mostly foolproof, once one knows how to setup
puTTY for it.

By the way, puTTY defaults to XON/XOFF COMs I think, and between windows
and puTTY they're almost never the  same. Until made so. So, check device
manager to see what windows has set for the serial device, and just make
sure puTTY is exactly the same.

On Mon, Oct 13, 2014 at 5:04 PM, Robert Nelson 
wrote:

> On Mon, Oct 13, 2014 at 6:46 PM, William Hermans 
> wrote:
> > Robert, it is very unlike there is anything wrong with puTTY. I've been
> > using it for years, and it's always been rock solid.
> >
> > The problem is more likely user error. Meaning this person does not know
> > enough about Linux to realize that network managers sometimes LOVE to
> screw
> > with ones mind. . .  But since there was no mention of a network scan for
> > alternative DHCP address . . . how could we know.
>
> I "think" he might be logging in via putty over serial and then
> rebooting the beaglebone. But not restarting putty.. It's a virtual
> usb serial, so when the bbb reboots that usb serial device
> disconnects. (putty doesn't correct for this..) Then when the bbb
> comes up again, it reinitailzes the usb flash/ usb networking / usb
> serial gadgets..
>
> Otherwise it works for me..
>
> Regards,
>
> --
> Robert Nelson
> http://www.rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: root password BBB ubuntu

[janszymanski12345]

Robert,

 I did again an eMMC flasher and now temppwd works, but still unable to 
login as root

login as: ubuntu
ubuntu@192.168.7.2's password:
Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.8.13-bone63 armv7l)

 * Documentation:  https://help.ubuntu.com/
Last login: Tue Oct 14 01:04:07 2014 from 192.168.7.1
ubuntu@arm:~$ sudo passwd root
[sudo] password for ubuntu:
Sorry, try again.
[sudo] password for ubuntu:
Enter new UNIX password:
Retype new UNIX password:
passwd: password updated successfully
ubuntu@arm:~$ sudo passwd -u root
passwd: password expiry information changed.
ubuntu@arm:~$

login as: root
root@192.168.7.2's password:
Access denied
root@192.168.7.2's password:


Any hints?

Jan



On Tuesday, October 14, 2014 11:42:01 AM UTC+11, RobertCNelson wrote:
>
> On Mon, Oct 13, 2014 at 7:38 PM,  > 
> wrote: 
> > I'm using the prebuilt image 
> > 
> > Get prebuilt image: 
> > 
> > wget 
> > 
> https://rcn-ee.net/deb/flasher/trusty/BBB-eMMC-flasher-ubuntu-14.04-console-armhf-2014-08-13-2gb.img.xz
>  
> > 
> > 
> > from here http://elinux.org/BeagleBoardUbuntu#Trusty_14.04 
> > Can you provide a link to another one, maybe I will have more luck then? 
>
> That was the "v2014.08" release, user and password where setup as: 
>
>
> https://github.com/RobertCNelson/omap-image-builder/blob/v2014.08/configs/rcn-ee_console_ubuntu_stable_armhf.conf#L26
>  
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.rcn-ee.com/ 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] log-in problems

[Matthew Fleming]

Thank you.  It now requires a login with username and password. Still can't 
use ssh with the "debian" user, though. Password definitely correct. I 
created another user and ssh works with that. Odd.

On Sunday, October 12, 2014 8:02:38 PM UTC-5, RobertCNelson wrote:
>
> On Sun, Oct 12, 2014 at 7:30 AM, Matthew Fleming  > wrote: 
> > Hi, 
> > 
> > I bought a BBB from Adafruit which came with Debian installed. The 
> console 
> > starts up Debian without requiring a username and password. For my 
> > application I need it to, and don't know how to make the change, because 
> > I've never seen a Linux distro that works this way. Also, when I try to 
> ssh 
> > into the BBB, it will not accept a password which I know to be correct. 
> > Would very much appreciate some help with these issues. 
>
> by "console" i think you mean "lxde" window desktop.. that autologin 
> is setup by this line in /etc/lightdm/lightdm.conf 
>
> autologin-user=debian 
>
> For the second ssh thing.. Are you "100%" sure your typing the correct 
> password?  ssh is pretty important in debian/linux, on a stable 
> release like debian, if that where to break, it would be fixed asap.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.rcn-ee.com/ 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: root password BBB ubuntu

[Robert Nelson]

On Mon, Oct 13, 2014 at 7:38 PM,   wrote:
> I'm using the prebuilt image
>
> Get prebuilt image:
>
> wget
> https://rcn-ee.net/deb/flasher/trusty/BBB-eMMC-flasher-ubuntu-14.04-console-armhf-2014-08-13-2gb.img.xz
>
>
> from here http://elinux.org/BeagleBoardUbuntu#Trusty_14.04
> Can you provide a link to another one, maybe I will have more luck then?

That was the "v2014.08" release, user and password where setup as:

https://github.com/RobertCNelson/omap-image-builder/blob/v2014.08/configs/rcn-ee_console_ubuntu_stable_armhf.conf#L26

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: root password BBB ubuntu

[janszymanski12345]

I'm using the prebuilt image 

Get prebuilt image: 

wget 
https://rcn-ee.net/deb/flasher/trusty/BBB-eMMC-flasher-ubuntu-14.04-console-armhf-2014-08-13-2gb.img.xz


from here http://elinux.org/BeagleBoardUbuntu#Trusty_14.04 
Can you provide a link to another one, maybe I will have more luck then?

Jan 


On Tuesday, October 14, 2014 10:48:18 AM UTC+11, janszyma...@gmail.com 
wrote:
>
> Hi,
>
>  After installing ubuntu console on BBB from here: 
> http://elinux.org/BeagleBoardUbuntu#Trusty_14.04 and connecting with Putty
>
> login as: ubuntu
> ubuntu@192.168.7.2's password:
> Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.8.13-bone63 armv7l)
>
>  * Documentation:  https://help.ubuntu.com/
> Last login: Wed Aug 13 18:11:23 2014 from 192.168.7.1
> ubuntu@arm:~$ sudo passwd root
> [sudo] password for ubuntu:
>
> what is the [sudo] password, root password?
>
> How can I login as root? change password for root?
>
> Jan
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] root password BBB ubuntu

[Robert Nelson]

On Mon, Oct 13, 2014 at 7:18 PM,   wrote:
> Hi,
>
>  I did follow the exact link, but the instruction given do not work.
>
> First question:
> what would i type after: sudo apt-get update, when asked for password?
> (tried nothing, root, ... temppwd - nothing works)

"temppwd" it's been that for over 5 years by default.. You changed something...

>
> login as: ubuntu
> ubuntu@192.168.7.2's password:
> Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.8.13-bone63 armv7l)
>
>  * Documentation:  https://help.ubuntu.com/
> Last login: Wed Aug 13 17:36:43 2014 from 192.168.7.1
> ubuntu@arm:~$ sudo apt-get update
> [sudo] password for ubuntu:
> Sorry, try again.
> [sudo] password for ubuntu:
>
> Second question:
> The instruction at the link says:
>
> Enabling
>
> To actually enable root logins first you have to set a password for the root
> account and then unlock the locked root account. If you don't set a password
> for the root account the passwd command will return
>
> passwd: unlocking the password would result in a passwordless account.
>
> So, rirst execute in a terminal
>
> sudo passwd root
>
> you will prompted for a new Unix password. Write it twice(second for
> confirmation).
>
> Then execute
>
> sudo passwd -u root
>
> to unlock the account. This should return
>
> passwd: password expiry information changed
>
> From theory to reality:
>
>
> ubuntu@arm:~$ sudo passwd root
> [sudo] password for ubuntu:

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] root password BBB ubuntu

[janszymanski12345]

Hi,

 I did follow the exact link, but the instruction given do not work.

First question:
what would i type after: sudo apt-get update, when asked for password? 
(tried nothing, root, ... temppwd - nothing works)

login as: ubuntu
ubuntu@192.168.7.2's password:
Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.8.13-bone63 armv7l)

 * Documentation:  https://help.ubuntu.com/
Last login: Wed Aug 13 17:36:43 2014 from 192.168.7.1
ubuntu@arm:~$ sudo apt-get update
[sudo] password for ubuntu:
Sorry, try again.
[sudo] password for ubuntu:

Second question:
The instruction at the link says:

Enabling 

To actually enable root logins first you have to set a password for the 
root account and then unlock the locked root account. If you don't set a 
password for the root account the passwd command will return 

passwd: unlocking the password would result in a passwordless account.  

So, rirst execute in a terminal 

sudo passwd root

you will prompted for a new Unix password. Write it twice(second for 
confirmation).

Then execute 

sudo passwd -u root 

to unlock the account. This should return 

passwd: password expiry information changed

>From theory to reality:


ubuntu@arm:~$ sudo passwd root
[sudo] password for ubuntu:

 what now?

Jan







On Tuesday, October 14, 2014 11:06:16 AM UTC+11, RobertCNelson wrote:
>
> On Mon, Oct 13, 2014 at 7:01 PM, Robert Nelson  > wrote: 
> > On Mon, Oct 13, 2014 at 6:48 PM,  > 
> wrote: 
> >> Hi, 
> >> 
> >>  After installing ubuntu console on BBB from here: 
> >> http://elinux.org/BeagleBoardUbuntu#Trusty_14.04 and connecting with 
> Putty 
> >> 
> >> login as: ubuntu 
> >> ubu...@192.168.7.2 's password: 
> >> Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.8.13-bone63 armv7l) 
> >> 
> >>  * Documentation:  https://help.ubuntu.com/ 
> >> Last login: Wed Aug 13 18:11:23 2014 from 192.168.7.1 
> >> ubuntu@arm:~$ sudo passwd root 
> >> [sudo] password for ubuntu: 
> >> 
> >> what is the [sudo] password, root password? 
> >> 
> >> How can I login as root? change password for root? 
> > 
> > It's ubuntu, by "default" there is no "root" user.. 
> > 
> > This is the way ubuntu has been since 2006, if you want a root user 
> > you need to enable/create it. 
>
> second link if you would have searched google.. 
>
> http://askubuntu.com/questions/44418/how-to-enable-root-login 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.rcn-ee.com/ 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] root password BBB ubuntu

[Robert Nelson]

On Mon, Oct 13, 2014 at 7:01 PM, Robert Nelson  wrote:
> On Mon, Oct 13, 2014 at 6:48 PM,   wrote:
>> Hi,
>>
>>  After installing ubuntu console on BBB from here:
>> http://elinux.org/BeagleBoardUbuntu#Trusty_14.04 and connecting with Putty
>>
>> login as: ubuntu
>> ubuntu@192.168.7.2's password:
>> Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.8.13-bone63 armv7l)
>>
>>  * Documentation:  https://help.ubuntu.com/
>> Last login: Wed Aug 13 18:11:23 2014 from 192.168.7.1
>> ubuntu@arm:~$ sudo passwd root
>> [sudo] password for ubuntu:
>>
>> what is the [sudo] password, root password?
>>
>> How can I login as root? change password for root?
>
> It's ubuntu, by "default" there is no "root" user..
>
> This is the way ubuntu has been since 2006, if you want a root user
> you need to enable/create it.

second link if you would have searched google..

http://askubuntu.com/questions/44418/how-to-enable-root-login

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] "You can't brick it"

[Robert Nelson]

On Mon, Oct 13, 2014 at 6:46 PM, William Hermans  wrote:
> Robert, it is very unlike there is anything wrong with puTTY. I've been
> using it for years, and it's always been rock solid.
>
> The problem is more likely user error. Meaning this person does not know
> enough about Linux to realize that network managers sometimes LOVE to screw
> with ones mind. . .  But since there was no mention of a network scan for
> alternative DHCP address . . . how could we know.

I "think" he might be logging in via putty over serial and then
rebooting the beaglebone. But not restarting putty.. It's a virtual
usb serial, so when the bbb reboots that usb serial device
disconnects. (putty doesn't correct for this..) Then when the bbb
comes up again, it reinitailzes the usb flash/ usb networking / usb
serial gadgets..

Otherwise it works for me..

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] root password BBB ubuntu

[Robert Nelson]

On Mon, Oct 13, 2014 at 6:48 PM,   wrote:
> Hi,
>
>  After installing ubuntu console on BBB from here:
> http://elinux.org/BeagleBoardUbuntu#Trusty_14.04 and connecting with Putty
>
> login as: ubuntu
> ubuntu@192.168.7.2's password:
> Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.8.13-bone63 armv7l)
>
>  * Documentation:  https://help.ubuntu.com/
> Last login: Wed Aug 13 18:11:23 2014 from 192.168.7.1
> ubuntu@arm:~$ sudo passwd root
> [sudo] password for ubuntu:
>
> what is the [sudo] password, root password?
>
> How can I login as root? change password for root?

It's ubuntu, by "default" there is no "root" user..

This is the way ubuntu has been since 2006, if you want a root user
you need to enable/create it.

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] root password BBB ubuntu

[janszymanski12345]

Hi,

 After installing ubuntu console on BBB from here: 
http://elinux.org/BeagleBoardUbuntu#Trusty_14.04 and connecting with Putty

login as: ubuntu
ubuntu@192.168.7.2's password:
Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.8.13-bone63 armv7l)

 * Documentation:  https://help.ubuntu.com/
Last login: Wed Aug 13 18:11:23 2014 from 192.168.7.1
ubuntu@arm:~$ sudo passwd root
[sudo] password for ubuntu:

what is the [sudo] password, root password?

How can I login as root? change password for root?

Jan

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] "You can't brick it"

[William Hermans]

Robert, it is very unlike there is anything wrong with puTTY. I've been
using it for years, and it's always been rock solid.

The problem is more likely user error. Meaning this person does not know
enough about Linux to realize that network managers sometimes LOVE to screw
with ones mind. . .  But since there was no mention of a network scan for
alternative DHCP address . . . how could we know.

On Mon, Oct 13, 2014 at 1:26 PM, Robert Nelson 
wrote:

> On Mon, Oct 13, 2014 at 3:24 PM, Robert Nelson 
> wrote:
> > On Mon, Oct 13, 2014 at 2:56 PM, Ben McDui  wrote:
> >> "You can't brick it", that is what Gerald says (or was it someone else).
> >
> > Go look up the definition of "bricking", for a device this applies
> > it's turns into a brick and will never load again..
> >
> >> Well, here I am.
> >>
> >> (I posted earlier on this issue, please ignore the post "BBB with
> Ubuntu:
> >> locked out, no SSH response" as it is outdated.)
> >>
> >> SUMMARY: After being flashed with Ubuntu or Debian, BBB does not
> respond to
> >> Serial or SSH session from PuTTY.
> >
> > Sounds like a putty bug to me.. WFM..
> >
> > Give the newest snapshot a try:
> >
> > http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-10-08
>
> btw, i should also mention, unless you tell us what image
> (date-name-etc) you actually tried to flash, i'm just ignoring bug
> reports. ;)
>
> Regards,
>
> --
> Robert Nelson
> http://www.rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone black build kernel

[aka . pavlya]

понедельник, 13 октября 2014 г., 20:08:45 UTC+3 пользователь RobertCNelson 
написал:
>
> On Mon, Oct 13, 2014 at 12:05 PM,  > 
> wrote: 
> > 
> >> 
> >> Umm, cherry pick the commits and apply to the default tree.. 
> >> 
> >> Regards, 
> >> 
> >> -- 
> >> Robert Nelson 
> >> http://www.rcn-ee.com/ 
> > 
> > 
> > Robert, thank you for your advice. 
> > Unfortunately I don't have enough experience in kernel building. But I 
> want 
> > to build it )) 
> > Your script do steps (in general): 
> > 1 Switch to branch (for example 3.8) 
> > 2 Download linux kernel sources 
> > 3 path kernel 
> > 4 build kernel 
> 5 apply patches to KERNEL dir 
> 6 run: ./tools/rebuild.sh 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.rcn-ee.com/ 
>

Thank you. 
I'm a little confused. I think I should do "cherry-pick" on the git_kernel 
() stage (git.sh) Is it correct?
P.S.: Sorry for the stupid questions. It is still hard for me.

Best regards,
Yurii
 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: troubleshooting hung up SD card - processes trying to access SD card just hang

[Sebastian H]

It's good to hear that the power down issue is fixed. However, I think I 
wasn't very clear in my last message. The system couldn't do a proper 
shutdown as the SD card had locked up, which resulted in hanging every 
process attempting to access the card or its contents. That's what 
prevented Debian from shutting down (completely unrelated to the power of 
the Beagle not turning off).

I believe the issue I'm seeing is a different version of the one I reported 
on github  with the 3.8.13 
kernel. This may be an issue with just my BBB, the SD card I use or perhaps 
an incompatibility with the both not working together properly. 

For now, I've rolled back to the 3.8.13 kernel as at least there I didn't 
used to have the random reboots the 3.14 kernel is giving me.

On Monday, October 13, 2014 7:09:31 PM UTC+2, RobertCNelson wrote:
>
> On Mon, Oct 13, 2014 at 12:08 PM, Sebastian H  > wrote: 
> > I just managed to cause the issue again by running: 
> > sudo du -s * 
> > while in the main directory of the SD card. So this seems to be 
> connected to 
> > intensive SD card use. 
> > 
> > Again, nothing in the logs that I could identify. Since the shutdown 
> didn't 
> > work as expected I had to cut power. 
>
> Shutdown just got fixed, pushed out as r30, currently building.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.rcn-ee.com/ 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] "You can't brick it"

[Robert Nelson]

On Mon, Oct 13, 2014 at 3:24 PM, Robert Nelson  wrote:
> On Mon, Oct 13, 2014 at 2:56 PM, Ben McDui  wrote:
>> "You can't brick it", that is what Gerald says (or was it someone else).
>
> Go look up the definition of "bricking", for a device this applies
> it's turns into a brick and will never load again..
>
>> Well, here I am.
>>
>> (I posted earlier on this issue, please ignore the post "BBB with Ubuntu:
>> locked out, no SSH response" as it is outdated.)
>>
>> SUMMARY: After being flashed with Ubuntu or Debian, BBB does not respond to
>> Serial or SSH session from PuTTY.
>
> Sounds like a putty bug to me.. WFM..
>
> Give the newest snapshot a try:
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-10-08

btw, i should also mention, unless you tell us what image
(date-name-etc) you actually tried to flash, i'm just ignoring bug
reports. ;)

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] "You can't brick it"

[Robert Nelson]

On Mon, Oct 13, 2014 at 2:56 PM, Ben McDui  wrote:
> "You can't brick it", that is what Gerald says (or was it someone else).

Go look up the definition of "bricking", for a device this applies
it's turns into a brick and will never load again..

> Well, here I am.
>
> (I posted earlier on this issue, please ignore the post "BBB with Ubuntu:
> locked out, no SSH response" as it is outdated.)
>
> SUMMARY: After being flashed with Ubuntu or Debian, BBB does not respond to
> Serial or SSH session from PuTTY.

Sounds like a putty bug to me.. WFM..

Give the newest snapshot a try:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-10-08

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] "You can't brick it"

[Ben McDui]

 

"You can't brick it", that is what Gerald says (or was it someone else).

Well, here I am.
(I posted earlier on this issue, please ignore the post "BBB with Ubuntu: 
locked out, no SSH response" as it is outdated.)

SUMMARY: After being flashed with Ubuntu or Debian, BBB does not respond to 
Serial or SSH session from PuTTY.

*Debian*
Received a BBB Rev C from Adafruit, Debian pre-installed. 

I'm doing everything via USB so far.

Log in with PuTTY serial; BBB displayed the message that it was running 
Debian indeed.

*Ubuntu*

Flash Ubuntu onto eMMC  from uSD (scrupulously following the rules as 
explained on various sites). 

Log in on Ubuntu (SSH 192.168.7.2) and set a root password.

Power down, power up, log in as root, OK.

Change /etc/network/interfaces to change from DHCP to Static IP. Left the 
USB-section untouched.

All of the above exactly as I did before on another BBB.

 

NOW IT GOES WRONG:

Power down, power up, start PuTTY as SSH 192.168.7.2. The window opens, 
steady cursor, no response.

PuTTY Serial, the window opens, steady cursor, no response.

The LEDs show normal behaviour: USR0=heartbeat, USR2 shows slight CPU 
activity.

BBB appears on my PC in Devices and Printers as "Gadget Serial (COM3)".

With Explorer on my PC, I can inspect the eMMC and even open START.htm 
(Firefox starts, the "Getting started" page displays)

 

*Debian* again

Flash Debian onto eMMC.

Power down, power up, start PuTTY with SSH 192.168.7.2. The window opens, 
steady cursor, no response.

PuTTY Serial, the window opens, steady cursor, no response.

The LEDs show normal behaviour: USR0=heartbeat, USR2 shows slight CPU 
activity.

 

*Angstrom*

After this I managed to flash Angstrom successfully, but never did I 
succeed with repeating Ubuntu or Debian flashes.

 

*Note a few things:*

·I did install the extra drivers on the PC as the Getting Started 
page says.

·Flashing Angstrom takes 40 min. During the process, the LEDs flash 
erratically (so it seems, BBB knows better of course).

·Flashing Ubuntu takes <5 min. The LEDs show a neat running light 
that bounces forth and back.

·From previous experience, I expect Angstrom and Debian to appear 
when I make a Serial connection, whereas Ubuntu requires SSH on 192.168.7.2.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Multi camera project BeagleBlack

[ybeagle]

On Friday, September 26, 2014 15:11:29 liyaoshi wrote:
> If I understand correctly
> It should like surround view or adas ?
> and as I know , AM335X don't have isp . while omap3 have it .
> while cvbs signal in . camera module will turn to bt656 or what ever
> digital signal , as usually BT656
> 
> And when you can  catch BT656 digital signal . you can program it to
> overlay or something .
> 
> And about the CVBS out signal . You can NOT generate it by GPIO .

You can generate it just fine with the BeagleBone Black's GPIO. I have done 
composite output with the option to overlay a video stream with the PRUs. 
(sorry no photos or write ups yet; running way behind on that.) The hardware 
is pretty trival for mono. You need to switch between 3 basic voltages with 
enough drive for 75ohm's and have the right termination:
- Sync voltage
- Black level
- White level

Color is a little trickier in that you need to get the phasing right or the 
color shifts around. Think of it as using the BBB as a programmable arbitrary 
wave form generator. At 200MHz on the PRU, that's plenty fast for a signal 
that lives with less then 6MHz of bandwidth. 

As for input, the PRUs should be able to handle it; slap on a analog video to 
BT656 converter chip. Doing either capture or video output is easy. Doing both 
requires scheduling the PRUs so they don't block when access is made outside 
of the PRUSS.

> For Your application .As I think , You should use OMAP3 BB-XM board with
> omap3 soc
> 
> It will have a isp and cvbs out,only problem is it will only have 1 isp
> 
> if you want to get another work with usb .
> 
> 2014-09-26 4:32 GMT+08:00 :
> > Hi all
> > 
> > I and a couple guys are trying to build a system from the BeagleBone Black
> > that uses an IR and color camera for quadcopter video.
> > We have one of each of these cameras
> > 
> > http://dlnmh9ip6v2uc.cloudfront.net/datasheets/Sensors/LightImaging/32KM_s
> > pec.docx.pdf
> > 
> > http://pub.ucpros.com/download/ov7620_ov7120_v1.2whole.pdf?osCsid=g3j4cfse
> > ca1627jv9mc4lans75 http://www.drs.com/products/rsta/PDF/Tamarisk.pdf
> > The end goal is to be able to output a video stream of either (1) the
> > color camera (2) the IR camera (3) a composite video - b/w or color,
> > overlay or other.  It has to be composite video for the quadcopter. (it's
> > a
> > system already setup and we're just doing add-on)
> > Known problems:
> > The BeagleBone Black only has one USB port.  I can probably figure out how
> > to make the IR camera recognizable by the system through the USB port, but
> > the other two are a bit more complicated -- one is purerly analog NTSC and
> > the other has a variety of digital options and a monochrome NTSC
> > backup/test output.  Maybe there's a way to configure the GPIOs to handle
> > this?
> > I'm planning on using OpenCV for the overlay/processing, though I'm not
> > very familiar with it.
> > 
> > Sound crazy?  It is, but that's what we're doing...
> > 
> > --
> > For more options, visit http://beagleboard.org/discuss
> > ---
> > You received this message because you are subscribed to the Google Groups
> > "BeagleBoard" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to beagleboard+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Cross compiling using Eclipse and Ubuntu 64bit 12.04

[mrbarre7612]

I finally got it working. I deleted Eclipse and reinstalled it. I had two 
issues. #1 When I created my project instead of using Cross Toolchain I 
used Linux. In the Derek Molloy video when he creates his project he only 
has the Linux Toolchain listed so not knowing much about Ubuntu or Eclipse 
I followed the video. I also changed the toolchain to gneuabihf. Once I 
made these two changes everything started working. The good news is I 
learned a lot about Ubuntu and Eclipse during the process and now feel more 
comfortable with both products. 



-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Problems with 3.17.0-bone4 when using a TP-LINK MA260 USB GSM modem

[jens . schroer]

Hi,

I would like to use kernel 3.17 on my BBB for various reasons.
I would also like to use a TP-LINK MA260 USB GSM modem with kernel 3.17. 
This combination works fine on my laptop (x86) but becomes problematic with 
the 3.17.0-bone4 kernel.
The error I see is below (together with some dmesg output from just before)
I use a Netgear WNA1100 Wifi USB dongle (Atheros) with the same kernel / 
system without a problem.
I tried the different 3.14 versions and with them my Wifi dongle causes 
kernel Oops but the GSM works fine.
3.17 seems to be the most stable from what I can see so far, but the crash 
for the GSM dongle is a problem.
I would appreciate any idea that I could try to get this working.

Thank you,
Jens

[   67.902244] usb 2-1: SerialNumber: 863745010381099
[   67.917438] usb-storage 2-1:1.0: USB Mass Storage device detected
[   67.926645] scsi host0: usb-storage 2-1:1.0
[   68.670954] usb 2-1: USB disconnect, device number 2
[   69.114465] usb 2-1: new high-speed USB device number 3 using musb-hdrc
[   69.256854] usb 2-1: device v2357 p9000 is not supported
[   69.262438] usb 2-1: New USB device found, idVendor=2357, idProduct=9000
[   69.262448] usb 2-1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=4
[   69.262457] usb 2-1: Product: TP-LINK HSPA+ Modem
[   69.262465] usb 2-1: Manufacturer: TP-LINK, Incorporated
[   69.262473] usb 2-1: SerialNumber: 863745010381099
[   69.275178] usb-storage 2-1:1.2: USB Mass Storage device detected
[   69.282760] scsi host1: usb-storage 2-1:1.2
[   69.287301] qmi_wwan 2-1:1.4: cdc-wdm0: USB WDM device
[   69.288188] qmi_wwan 2-1:1.4 wwan0: register 'qmi_wwan' at usb-musb-hdrc.
1.auto-1, WWAN/QMI device, 36:f7:90:f1:f0:50
[   69.340681] usbcore: registered new interface driver usbserial
[   69.342212] usbcore: registered new interface driver usbserial_generic
[   69.343318] usbserial: USB Serial support registered for generic
[   69.366842] usbcore: registered new interface driver option
[   69.368336] usbserial: USB Serial support registered for GSM modem (1-
port)
[   69.370018] option 2-1:1.0: GSM modem (1-port) converter detected
[   69.370981] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0
[   69.371384] option 2-1:1.1: GSM modem (1-port) converter detected
[   69.373136] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1
[   69.373601] option 2-1:1.3: GSM modem (1-port) converter detected
[   69.381019] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB2
[   70.275715] scsi 1:0:0:0: CD-ROMTP-LINK  MMC Storage  
2.31 PQ: 0 ANSI: 2
[   70.276389] scsi 1:0:0:1: Direct-Access TP-LINK  MMC Storage  
2.31 PQ: 0 ANSI: 2
[   70.283037] sd 1:0:0:1: [sda] Attached SCSI removable disk
[   70.312798] scsi 1:0:0:0: Attached scsi generic sg0 type 5
[   70.313180] sd 1:0:0:1: Attached scsi generic sg1 type 0
[   70.394794] sr 1:0:0:0: [sr0] scsi-1 drive
[   70.394819] cdrom: Uniform CD-ROM driver Revision: 3.20
[   70.396874] sr 1:0:0:0: Attached scsi CD-ROM sr0
[   74.088781] [ cut here ]
[   74.088828] WARNING: CPU: 0 PID: 252 at drivers/usb/musb/musb_host.c:128 
musb_h_tx_flush_fifo+0x7f/0xa4()
[   74.088835] Could not flush host TX2 fifo: csr: 2003
[   74.088841] Modules linked in: sr_mod cdrom sg option usb_wwan usbserial 
qmi_wwan cdc_wdm usbnet omap_sham omap_aes evdev ath9k_htc ath9k_common 
ath9k_hw ath mac80211 cfg80211
[   74.088893] CPU: 0 PID: 252 Comm: ModemManager Not tainted 3.17.0-bone4 
#1
[   74.088939] [] (unwind_backtrace) from [] (show_stack
+0x11/0x14)
[   74.088968] [] (show_stack) from [] (
warn_slowpath_common+0x51/0x6c)
[   74.088983] [] (warn_slowpath_common) from [] (
warn_slowpath_fmt+0x23/0x2c)
[   74.088996] [] (warn_slowpath_fmt) from [] (
musb_h_tx_flush_fifo+0x7f/0xa4)
[   74.089010] [] (musb_h_tx_flush_fifo) from [] (
musb_cleanup_urb+0x3f/0x6c)
[   74.089023] [] (musb_cleanup_urb) from [] (
musb_urb_dequeue+0xd3/0x118)
[   74.089041] [] (musb_urb_dequeue) from [] (unlink1+
0x1b/0xac)
[   74.089054] [] (unlink1) from [] (usb_hcd_unlink_urb+
0x5f/0x8c)
[   74.089068] [] (usb_hcd_unlink_urb) from [] (
usb_kill_urb+0x45/0x94)
[   74.089096] [] (usb_kill_urb) from [] (usb_wwan_close
+0x60/0x74 [usb_wwan])
[   74.089150] [] (usb_wwan_close [usb_wwan]) from [] (
serial_port_shutdown+0x18/0x1c [usbserial])
[   74.089178] [] (serial_port_shutdown [usbserial]) from [<
c037c1c7>] (tty_port_shutdown+0x53/0x5c)
[   74.089194] [] (tty_port_shutdown) from [] (
tty_port_close+0x1d/0x48)
[   74.089216] [] (tty_port_close) from [] (serial_close
+0x24/0x44 [usbserial])
[   74.089236] [] (serial_close [usbserial]) from [] (
tty_release+0xb7/0x378)
[   74.089253] [] (tty_release) from [] (__fput+0x65/
0x144)
[   74.089277] [] (__fput) from [] (task_work_run+0x59/
0x90)
[   74.089293] [] (task_work_run) from [] (
do_work_pending+0x67/0x90)
[   74.089307] [] (do_work_pending) from [] (
work_pending+0x9/0x1a)
[   74.089315] ---[ end trace 4eed54ed60f5b623 ]---
[   75

Re: [beagleboard] Re: Beaglebone Black Rebooting Several Times Every Day

[Greg Kelley]

Mine is still resetting one to three times a day. I have moved both 
processes I was running on it (CUPS and weewx) over to my RasPi so it is 
just sitting idle except for CRON jobs. No events in serial debug logs, 
just a sudden reset and cold boot restart.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] PRU Assembly Questiony.

[Jason Kridner]

On Saturday, October 11, 2014, Brandon I  wrote:

> All pru GPIO are accessible via a single register, so it's one tick,just
> like any other register (two for loading a 32 bit immediate value).
>
> Arm GPIO are never accessible in a single tick since there way outside the
> Pru and have to go over the OCP bus. See
> http://nomel.tumblr.com/post/30006622413/beaglebone-tutorial-accessing-main-memory-from-the-pru


Thanks. There is a wiki linked from http://beagleboard.org/pru you might
want to examine/edit.


>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: troubleshooting hung up SD card - processes trying to access SD card just hang

[Robert Nelson]

On Mon, Oct 13, 2014 at 12:08 PM, Sebastian H  wrote:
> I just managed to cause the issue again by running:
> sudo du -s *
> while in the main directory of the SD card. So this seems to be connected to
> intensive SD card use.
>
> Again, nothing in the logs that I could identify. Since the shutdown didn't
> work as expected I had to cut power.

Shutdown just got fixed, pushed out as r30, currently building..

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone black build kernel

[Robert Nelson]

On Mon, Oct 13, 2014 at 12:05 PM,   wrote:
>
>>
>> Umm, cherry pick the commits and apply to the default tree..
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> http://www.rcn-ee.com/
>
>
> Robert, thank you for your advice.
> Unfortunately I don't have enough experience in kernel building. But I want
> to build it ))
> Your script do steps (in general):
> 1 Switch to branch (for example 3.8)
> 2 Download linux kernel sources
> 3 path kernel
> 4 build kernel
5 apply patches to KERNEL dir
6 run: ./tools/rebuild.sh

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: troubleshooting hung up SD card - processes trying to access SD card just hang

[Sebastian H]

I just managed to cause the issue again by running:
sudo du -s * 
while in the main directory of the SD card. So this seems to be connected 
to intensive SD card use. 

Again, nothing in the logs that I could identify. Since the shutdown didn't 
work as expected I had to cut power.

On Sunday, October 12, 2014 12:08:01 PM UTC+2, Sebastian H wrote:
>
> Early this morning I had this  in my 
> netconsole log. The Beagle was still up and running fine. I unmounted the 
> SD card and ran e2fsck -cvf /dev/mmcblk0p2 which didn't turn up any issues 
> .
>
> Any ideas what this is about? 
>
> On Saturday, October 11, 2014 10:02:45 PM UTC+2, Sebastian H wrote:
>>
>> Hi,
>>
>> After working around the random reboot issue with kernel 3.14.19-ti-r28 
>> by compiling the kernel without watchdog support (details here 
>> ),
>>  
>> I ran into a different issue on my BBB (rev. A5C) today. From what I can 
>> tell, during my overnight backup last night, the SD card somehow locked up 
>> (with user led1 permanently lit) and any process that had tried to access 
>> the SD card was locked up as well.
>> Trying to kill any of the hung processes with "sudo kill pid" wouldn't 
>> work in most cases and only resulted in an unkillable process, because 
>> after I did that, "sudo kill -9 pid" would be useless as well. So I killed 
>> most of the processes with kill -9, but I still ended up with a bunch 
>> completely hosed. 
>>
>> The SD access was completely busted so not even a simple ls command 
>> worked anymore. That would just hang as well and I'd have to kill -9 it. 
>>
>> The rest of the BBB was working just fine, as long as I didn't access the 
>> SD. The CPU was pretty much idle, except for postgresql process that tried 
>> to access the database that is also on the SD, but obviously couldn't 
>> anymore.
>>
>> I also discovered that my eMMC (from which I boot my Debian 7 while the 
>> SD card is used for storage), was almost out of space. That was mostly due 
>> to me installing a number of kernel versions over the last couple of days, 
>> which contributed to a shortage in space. Note that my tmp and log folder 
>> are on a USB drive and thus the system eMMC wasn't completely filled up and 
>> was still working. 
>> While I initially thought the low available memory to be the cause of the 
>> problem, and I certainly wish for that to be the answer, I fear it might be 
>> happening again.
>>
>> I do have netconsole logging running and of course, nothing was in the 
>> log. 
>>
>> The SD card I use is a SanDisk Ultra 32GB Micro SDHC. 
>>
>> So I'm wondering if you have any suggestions on what I can do to gather 
>> more information on the issue, should it arise again? Would I be able to do 
>> some sort of process dump, e.g. of the process handling the SD card? If so, 
>> could anyone point me to information on how that is done and what process I 
>> would have to run it on? I kind of guess that it might be the mmcqd/0 
>> process? That's one I've seen causing an issue on the 3.8.13 kernel where 
>> it randomly froze up and I do recall that on these occasions, the usr LED1 
>> also was always lit. My report of that issue (and the kernel panic details) 
>> can be found here .
>>
>> I appreciate any pointers and assistance you can offer. 
>>
>> Sebastian
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone black build kernel

[aka . pavlya]

>
> Umm, cherry pick the commits and apply to the default tree.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.rcn-ee.com/ 
>

Robert, thank you for your advice.
Unfortunately I don't have enough experience in kernel building. But I want 
to build it ))
Your script do steps (in general):
1 Switch to branch (for example 3.8)
2 Download linux kernel sources
3 path kernel
4 build kernel
. other steps

And now  should I  "cherry-pick" the commits manualy or should I  overwrite 
building script(s)?
I will appreciate very much for you  if you can find a little time to 
answer my question.

Best regards,
Yurii

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Please I am in need of help with my BBB to boot to command line

[onyinyenwajagu]

I am new in this, I just got BBB for robotics research, I first booted in 
default and it was working, i now installed ubuntu by flashing which i 
don't know that it will erase the default eMMC, after the flashing, i was 
trying to boot the BBB, it will boot now without the SD card, but it will 
not boot to the command terminal, it will bring this message tty1, 
username:[password is tempdd], usb 196192.168.7.2  and it will remain 
there. I followed the installation in window OS to write the SD card 
written by Nelson in wiki, but i got error message when i wanted to install 
win32disk imager that the code requires elevation. So i ignored the error 
and wrote to the SD card.
 
Please can Nelson or any one help me to get the BBB to boot well, I am in 
fixed, i cannot even boot the default because it has been erased.
I apppreciate every help I can get so that i can continue with my research.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Beaglebone Black: Bonescript not compiled nor running under Cloud9

[leonardjowers]

Thanks. I'm new with BBB and was pulling what hair I have left out.


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBB is not working well

[onyinyenwajagu]

 I flashed the eMMC and after the 4LEDs comes on when I booted from SD 
card, the BBB now boot without SD card but it cannot boot to command 
terminal for me to login, it will bring message tty1, sername:[password is 
tempdd], usb1192.168.7.2. I have lost the default eMMC, I follwed the 
instruction in Nelson wiki to write to the SD card in windows OS, but i got 
a message while installing win32diskimage that the code requires elevation, 
and it couldn't installed as it should, but i went ahead to write to the SD 
card which installed, Later I insert the SD card in the BBB and it boots 
until the 4 LEDs are not fliclkering but the booting will bring the message 
tty1, sername:[password is tempdd], usb1192.168.7.2 and will remain like 
that.
Please i need every help to fix this so that I can use the board for the 
project I am working on. I really appreciate.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB with Ubuntu: locked out, no SSH response

[kang . yatze]

Update 12 october 2014:
I flashed Debian, latest image, and had the same results. The flash did 
take place, given the specific Debian related files I can see on the eMMC 
(through the file browser).

Op vrijdag 10 oktober 2014 16:30:28 UTC+2 schreef BenMcDui:
>
> I'm stuck.
> After I flash Angstrom, I get serial access as expected.
> After I flash Ubuntu (various versions, including the latest 
> BBB-eMMC-flasher-ubuntu-14.04-console-armhf-2014-08-13-2gb.img, I am locked 
> out. That is: no serial (as expected, I had this with my earlier BBB) but 
> also no SSH to 192.168.7.2 either.
>
> *What went before, very briefly: (all via USB)*
> Power up out of the box, serial on Angstrom OK.
> Flash Ubuntu, power down, power up, SSH access on 192.168.7.2  OK. (user 
> ubuntu, pwd temppwd) 
> Insert root password, power off, power on, SSH access, root login OK
> Modify /etc/network/interfaces for Static IP:
>
> #auto eth0 
> #iface eth0 inet dhcp 
>
> # == 
> # static IP
> auto eth0 
> iface eth0 inet static 
>   address 192.168.0.134 
>   netmask 255.255.255.0 
>   gateway 192.168.0.1 
>   dns-nameservers 213.46.228.196 62.179.104.196
>
> This is exactly what I did with my earlier BBB.
> After this change, power down, power up.
> NO ACCESS via USB. Not in serial mode, not with SSH to 192.168.7.2 or 
> 192.168.0.134
>
> I reflashed several time forth an back to Angstrom, but the result is 
> always: Serial on Angstrom yes, SSH on Ubuntu no.
>
> I can see the BBB as thumb drive with my file browser on the PC, all the 
> files from the uSD seem to be copied to eMMC.
>
> I can open START.htm on the BBB from my file browser, Firefox starts, the 
> "getting started" page is displayed.
>
> Anyone?  Thanks!
>
>
>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] password problems

[mgflem]

Hi,

Sorry for the following, but I'm a complete newbie with this thing. I think 
the one I have is running debian. When I try to ssh into it, it will not 
accept the password for the 'debian' user, which I know is correct. OTOH, 
when I am using the console, it logs in as this user without asking for a 
password. I have tried changing /etc/inittab to specify a different initial 
runlevel (the default was 2, not sure why) but this did not help. I'd like 
to  require a password for log in to the console and accept the correct 
password by ssh.

Thanks much,

Matthew Fleming

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Trouble setting static IP on update (9/4) Angstrom image

[cl]

John Stoner  wrote:
> [-- text/plain, encoding quoted-printable, charset: UTF-8, 48 lines --]
> 
> On Monday, October 13, 2014 4:19:01 AM UTC-5, c...@isbd.net wrote:
> >
> > John Stoner > wrote: 
> > > and the flash worked, but now the /etc/network/interfaces file is gone. 
> > I 
> > > made a new one. It looks like this: 
> > > 
> > > root@beaglebone:~# cat /etc/network/interfaces 
> > > iface eth0 inet static 
> > >  address 192.168.7.4 
> > >  netmask 255.255.255.0 
> > >  gateway 192.168.7.1 
> > > 
> > > (I added the gateway line when it didn't work without it.) 
> > > 
> > > I can still get to my board via USB, which is fine as a backup, but for 
> > my 
> > > application i need to get a static IP over eth0. Is Angstrom not using 
> > > /etc/network/interfaces anymore? My network is set up to use 
> > 192.168.7.*. 
> > > 
> > > If I can't use that file how do I set a static IP? 
> > > 
> > I'd not be happy having the ethernet connection on the same subnet as 
> > the USB one, I think that might be confusing things. 
> >
> >  
> OK. If my usb subnet isn't defined in /etc/network/interfaces, where is it 
> defined? I'd probably rather change that than my network, for various 
> reasons.
> 
A quick Google suggests it's set in /etc/udhcpd.conf on some BBBs but
mine running Debian has it in /etc/network/interfaces:-

# Ethernet/RNDIS gadget (g_ether)
# ... or on host side, usbnet and random hwaddr
# Note on some boards, usb0 is automaticly setup with an init script
iface usb0 inet static
address 192.168.7.2
netmask 255.255.255.0
network 192.168.7.0
gateway 192.168.7.1


-- 
Chris Green
·

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Do some one have some beagle bone?

[Travis Estep]

Even though it comes in a Make kit and costs $89, every Radio Shack in my area 
had penny of them in stock.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Trouble setting static IP on update (9/4) Angstrom image

[John Stoner]

On Monday, October 13, 2014 4:19:01 AM UTC-5, c...@isbd.net wrote:
>
> John Stoner > wrote: 
> > and the flash worked, but now the /etc/network/interfaces file is gone. 
> I 
> > made a new one. It looks like this: 
> > 
> > root@beaglebone:~# cat /etc/network/interfaces 
> > iface eth0 inet static 
> >  address 192.168.7.4 
> >  netmask 255.255.255.0 
> >  gateway 192.168.7.1 
> > 
> > (I added the gateway line when it didn't work without it.) 
> > 
> > I can still get to my board via USB, which is fine as a backup, but for 
> my 
> > application i need to get a static IP over eth0. Is Angstrom not using 
> > /etc/network/interfaces anymore? My network is set up to use 
> 192.168.7.*. 
> > 
> > If I can't use that file how do I set a static IP? 
> > 
> I'd not be happy having the ethernet connection on the same subnet as 
> the USB one, I think that might be confusing things. 
>
> -- 
> Chris Green 
> · 
>
>  
OK. If my usb subnet isn't defined in /etc/network/interfaces, where is it 
defined? I'd probably rather change that than my network, for various 
reasons.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Do some one have some beagle bone?

[Richard St-Pierre]

Andrea:  You can find BeagleBone Black , cases, cape and more in stock at 
Logic Supply (US or EU). 
http://www.logicsupply.com/solutions/form-factor/beaglebone-black/   
 http://www.logicsupply.eu/beaglebone-black/

On Friday, October 10, 2014 7:11:22 AM UTC-4, Andrea Campanella wrote:
>
> My company is seracing for beaglebones, so, if you guy have a beaglebone 
> on the desk taking dust, we will pay for that. 
>
>
> Thanks.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] GPIO0_4 with beaglebone black

[Alberto Potenza]

Dear all,

it looks like I cannot take control of pin gpio0_4 (P9, 18).
I tried to export it by doing 
echo 4 > export
in
/sys/class/gpio
but it doesn't work: I cannot set it as output and move its value and I 
cannot set it as input to check values.
By doing:
cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pins
I see
pin 86 (44e10958) 0062 pinctrl-single
which means that it is in I2C1 configuration.
I tried to modify the uEnv.txt to disable I2C1 (even if I think that it 
should be not implemented by default ) and the I tried to export it again 
but...nothing.
I also tried to write a dts file and convert it in dtbo (here the text)

/dts-v1/;
/plugin/;

/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";

/* identification */
part-number = "GPIO";
version = "00A0";

exclusive-use = "P9.18"; /* Digital Input 0 gpio0_4 */


fragment@0 {
   target = <&am33xx_pinmux>;
   __overlay__ {
end_stop_pins: pinmux_end_stop_pins{
pinctrl-single,pins = <
0x158 0x37 /* P9_18 = Check dig ok */
>;
 };
   };
};

fragment@1 {
   target = <&ocp>;
   __overlay__ {
#address-cells = <1>;
#size-cells = <1>;
gpio_keys {
compatible = 
"gpio-keys";
pinctrl-names = 
"default";
pinctrl-0 = 
<&end_stop_pins>;
#address-cells = <1>;
#size-cells = <0>;
   };
};
   };
};

but nothing: it is always
pin 86 (44e10958) 0062 pinctrl-single

and I cannot move it.

Any idea?

Thanks for your help.

Alberto

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Document object?

[Richard Markham]

If I want to display a var in a webpage, do I need a document object so I 
can use the getElementById method?

Do I need jsdom? 

Is there another way to show the value of a variable within a webpage?

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Bonescript document object

[Richard Markham]

If I want to display a var in a webpage, do I need a document object so I 
can use the getElementById method?

Do I need jsdom? 

Is there another way to show the value of a variable within a webpage?


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Beaglebone Black Rebooting Several Times Every Day

[Sebastian H]

Searching around a bit, I wonder if an old u-boot version might have 
anything to do with it? From what I can tell, I'm still using an u-boot 
release from 2013.07 . Should I be updating this? If so, what would be the 
safest way to do so?
In /boot/uboot/tools, I noticed a couple of scripts (bootloader_update, 
update and update_boot_files). Would any of these work or should I get a 
more recent version?

On Monday, October 13, 2014 12:23:29 PM UTC+2, Sebastian H wrote:
>
> @Micka:
> I'm not sure how to check for increased memory usage as it's completely 
> unpredictable when it's going to reboot. Is there some kind of logging I 
> can enable for memory usage so it would get logged to my netconsole?
> As for logs, the netconsole log has nothing before the reboot occurs (just 
> like the previous reports on this thread, including the one from 
> RobertCNelson). Here 's the kernel log from 
> when it booted up after the sudden reboot.
> I also checked the syslog and there's nothing out of the ordinary in it. 
> It appears as if some killed the power for a second and the system just 
> boots up again.
> Is there any other log I could look for?
>
> @lisarden: 
> How would I go about checking the PMIC? Looking at the kernel log from the 
> boot I can only see this:
> [5.761536] sr_init: No PMIC hook to init smartreflex
> [5.767135] sr_init: platform driver register failed for SR
> I've also checked my past kernel logs and it's always the same line.
>
> Checking the kernel config, I'm not seeing any obvious setting to enable. 
> Can you point me in the correct direction?
>
> Thanks to both of you for your replies.
>
> On Monday, October 13, 2014 10:55:40 AM UTC+2, Mickae1 wrote:
>>
>> Did you check if memory usage is increasing ? Log file ?
>>
>> Micka,
>>
>> On Mon, Oct 13, 2014 at 10:49 AM, Sebastian H  wrote:
>>
>>> For the record, even with the watchdog package removed, my BBB rebooted 
>>> on me again after just 7 hours of uptime. :-(
>>> Here 's the kernel config I used. 
>>> Searching for watchdog, there are only two entries. This is the one still 
>>> enabled:
>>> CONFIG_OMAP_REMOTEPROC_WATCHDOG=y
>>> Should I disable that as well? 
>>>
>>> On Sunday, October 12, 2014 6:29:26 PM UTC+2, Sebastian H wrote:

 The issue still happened even using the kernel compiled without any 
 watchdog support. The netconsole log didn't include any details. It just 
 rebooted again without any indication why. That was about 24 hours after 
 the last restart. 
 I still had the watchdog package installed (but with even the software 
 watchdog disabled in the kernel, I didn't think it would do anything). 
 Well, I now removed that, but I'm not convinced that it did cause the 
 reboot.
  

 On Thursday, October 9, 2014 5:54:40 PM UTC+2, Sebastian H wrote:
>
> I switched over from kernel 3.8.13 to 3.14.19-ti-r28 (compiled with 
> netconsole support)  and after a little over 24 hours uptime, my BBB 
> rebooted without any entries in the netconsole log or any logs on the BBB 
> that I could find. 
>
> Did anyone have any luck in troubleshooting this issue any further? 
>
> In the meantime, I guess I'll try your suggestion of disabling the 
> watchdog for now.
>
>
> On Thursday, September 18, 2014 11:48:22 AM UTC+2, William Hermans 
> wrote:
>>
>> Short term, you can disable the hardware watchdog in kernel config. 
>> That should temporarily fix your problem, and if it does not . . . 
>> bigger 
>> mystery.
>>
>> Long term, it would be good to figure out what is triggering the 
>> watchdog. strace on the watchdog PID will not work - I tested this 
>> myself.
>>
>> The only one thing I can think of off hand is perhaps modifying the 
>> watchdog module to output a debug message before rebooting the system. 
>> As 
>> to which process triggered a shutdown, and why. If possible . . .
>>
>> Will research more tomorrow it is very late ( actually early ) here.
>>
>> On Thu, Sep 18, 2014 at 12:57 AM, Thomas Olofsson  
>> wrote:
>>
>>>
 Forget about claiming its a hardware issue. Because it is not. 
 We've had two beaglebone blacks for close to a year, and a half now. 
 Both 
 are rock solid, running off barrel jack power, or USB( one of each ).

 Ok well just stating facts that bbw is not rebooting and BBB is 
>>> with the same kernel
>>>
>>> Ok i would be happy to stop guessing and actually find the problem. 
>>> Could you give me some real advise on HOW to use the serial module 
>>> appropriately. i do have it connected to the serial console and i have 
>>> event built a kernel with verbosed debugging on i am just not seeing 
>>> anything. 
>>>
>>> So if you would like any information or dumps or whatev

Re: [beagleboard] Re: Beaglebone Black Rebooting Several Times Every Day

[Sebastian H]

@Micka:
I'm not sure how to check for increased memory usage as it's completely 
unpredictable when it's going to reboot. Is there some kind of logging I 
can enable for memory usage so it would get logged to my netconsole?
As for logs, the netconsole log has nothing before the reboot occurs (just 
like the previous reports on this thread, including the one from 
RobertCNelson). Here 's the kernel log from 
when it booted up after the sudden reboot.
I also checked the syslog and there's nothing out of the ordinary in it. It 
appears as if some killed the power for a second and the system just boots 
up again.
Is there any other log I could look for?

@lisarden: 
How would I go about checking the PMIC? Looking at the kernel log from the 
boot I can only see this:
[5.761536] sr_init: No PMIC hook to init smartreflex
[5.767135] sr_init: platform driver register failed for SR
I've also checked my past kernel logs and it's always the same line.

Checking the kernel config, I'm not seeing any obvious setting to enable. 
Can you point me in the correct direction?

Thanks to both of you for your replies.

On Monday, October 13, 2014 10:55:40 AM UTC+2, Mickae1 wrote:
>
> Did you check if memory usage is increasing ? Log file ?
>
> Micka,
>
> On Mon, Oct 13, 2014 at 10:49 AM, Sebastian H  > wrote:
>
>> For the record, even with the watchdog package removed, my BBB rebooted 
>> on me again after just 7 hours of uptime. :-(
>> Here 's the kernel config I used. 
>> Searching for watchdog, there are only two entries. This is the one still 
>> enabled:
>> CONFIG_OMAP_REMOTEPROC_WATCHDOG=y
>> Should I disable that as well? 
>>
>> On Sunday, October 12, 2014 6:29:26 PM UTC+2, Sebastian H wrote:
>>>
>>> The issue still happened even using the kernel compiled without any 
>>> watchdog support. The netconsole log didn't include any details. It just 
>>> rebooted again without any indication why. That was about 24 hours after 
>>> the last restart. 
>>> I still had the watchdog package installed (but with even the software 
>>> watchdog disabled in the kernel, I didn't think it would do anything). 
>>> Well, I now removed that, but I'm not convinced that it did cause the 
>>> reboot.
>>>  
>>>
>>> On Thursday, October 9, 2014 5:54:40 PM UTC+2, Sebastian H wrote:

 I switched over from kernel 3.8.13 to 3.14.19-ti-r28 (compiled with 
 netconsole support)  and after a little over 24 hours uptime, my BBB 
 rebooted without any entries in the netconsole log or any logs on the BBB 
 that I could find. 

 Did anyone have any luck in troubleshooting this issue any further? 

 In the meantime, I guess I'll try your suggestion of disabling the 
 watchdog for now.


 On Thursday, September 18, 2014 11:48:22 AM UTC+2, William Hermans 
 wrote:
>
> Short term, you can disable the hardware watchdog in kernel config. 
> That should temporarily fix your problem, and if it does not . . . bigger 
> mystery.
>
> Long term, it would be good to figure out what is triggering the 
> watchdog. strace on the watchdog PID will not work - I tested this myself.
>
> The only one thing I can think of off hand is perhaps modifying the 
> watchdog module to output a debug message before rebooting the system. As 
> to which process triggered a shutdown, and why. If possible . . .
>
> Will research more tomorrow it is very late ( actually early ) here.
>
> On Thu, Sep 18, 2014 at 12:57 AM, Thomas Olofsson  
> wrote:
>
>>
>>> Forget about claiming its a hardware issue. Because it is not. We've 
>>> had two beaglebone blacks for close to a year, and a half now. Both are 
>>> rock solid, running off barrel jack power, or USB( one of each ).
>>>
>>> Ok well just stating facts that bbw is not rebooting and BBB is with 
>> the same kernel
>>
>> Ok i would be happy to stop guessing and actually find the problem. 
>> Could you give me some real advise on HOW to use the serial module 
>> appropriately. i do have it connected to the serial console and i have 
>> event built a kernel with verbosed debugging on i am just not seeing 
>> anything. 
>>
>> So if you would like any information or dumps or whatever i am happy 
>> to provide that.
>>
>>
>>  -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google 
>> Groups "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, 
>> send an email to beagleboard...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard"

[beagleboard] Re: Trouble setting static IP on update (9/4) Angstrom image

[cl]

John Stoner  wrote:
> and the flash worked, but now the /etc/network/interfaces file is gone. I 
> made a new one. It looks like this:
> 
> root@beaglebone:~# cat /etc/network/interfaces
> iface eth0 inet static
>  address 192.168.7.4
>  netmask 255.255.255.0
>  gateway 192.168.7.1
> 
> (I added the gateway line when it didn't work without it.) 
> 
> I can still get to my board via USB, which is fine as a backup, but for my 
> application i need to get a static IP over eth0. Is Angstrom not using 
> /etc/network/interfaces anymore? My network is set up to use 192.168.7.*. 
> 
> If I can't use that file how do I set a static IP?
> 
I'd not be happy having the ethernet connection on the same subnet as
the USB one, I think that might be confusing things.

-- 
Chris Green
·

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Beaglebone Black Rebooting Several Times Every Day

[Maxim Podbereznyy]

I remember that once it was suggested to check the reboot reason from the
pmic. Definitely your issues are because of some hardware faults in the
pmic
13 Окт 2014 г. 12:55 пользователь "Micka"  написал:

> Did you check if memory usage is increasing ? Log file ?
>
> Micka,
>
> On Mon, Oct 13, 2014 at 10:49 AM, Sebastian H  wrote:
>
>> For the record, even with the watchdog package removed, my BBB rebooted
>> on me again after just 7 hours of uptime. :-(
>> Here 's the kernel config I used.
>> Searching for watchdog, there are only two entries. This is the one still
>> enabled:
>> CONFIG_OMAP_REMOTEPROC_WATCHDOG=y
>> Should I disable that as well?
>>
>> On Sunday, October 12, 2014 6:29:26 PM UTC+2, Sebastian H wrote:
>>>
>>> The issue still happened even using the kernel compiled without any
>>> watchdog support. The netconsole log didn't include any details. It just
>>> rebooted again without any indication why. That was about 24 hours after
>>> the last restart.
>>> I still had the watchdog package installed (but with even the software
>>> watchdog disabled in the kernel, I didn't think it would do anything).
>>> Well, I now removed that, but I'm not convinced that it did cause the
>>> reboot.
>>>
>>>
>>> On Thursday, October 9, 2014 5:54:40 PM UTC+2, Sebastian H wrote:

 I switched over from kernel 3.8.13 to 3.14.19-ti-r28 (compiled with
 netconsole support)  and after a little over 24 hours uptime, my BBB
 rebooted without any entries in the netconsole log or any logs on the BBB
 that I could find.

 Did anyone have any luck in troubleshooting this issue any further?

 In the meantime, I guess I'll try your suggestion of disabling the
 watchdog for now.


 On Thursday, September 18, 2014 11:48:22 AM UTC+2, William Hermans
 wrote:
>
> Short term, you can disable the hardware watchdog in kernel config.
> That should temporarily fix your problem, and if it does not . . . bigger
> mystery.
>
> Long term, it would be good to figure out what is triggering the
> watchdog. strace on the watchdog PID will not work - I tested this myself.
>
> The only one thing I can think of off hand is perhaps modifying the
> watchdog module to output a debug message before rebooting the system. As
> to which process triggered a shutdown, and why. If possible . . .
>
> Will research more tomorrow it is very late ( actually early ) here.
>
> On Thu, Sep 18, 2014 at 12:57 AM, Thomas Olofsson 
> wrote:
>
>>
>>> Forget about claiming its a hardware issue. Because it is not. We've
>>> had two beaglebone blacks for close to a year, and a half now. Both are
>>> rock solid, running off barrel jack power, or USB( one of each ).
>>>
>>> Ok well just stating facts that bbw is not rebooting and BBB is with
>> the same kernel
>>
>> Ok i would be happy to stop guessing and actually find the problem.
>> Could you give me some real advise on HOW to use the serial module
>> appropriately. i do have it connected to the serial console and i have
>> event built a kernel with verbosed debugging on i am just not seeing
>> anything.
>>
>> So if you would like any information or dumps or whatever i am happy
>> to provide that.
>>
>>
>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google
>> Groups "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to beagleboard...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Beaglebone Black Rebooting Several Times Every Day

[Micka]

Did you check if memory usage is increasing ? Log file ?

Micka,

On Mon, Oct 13, 2014 at 10:49 AM, Sebastian H  wrote:

> For the record, even with the watchdog package removed, my BBB rebooted on
> me again after just 7 hours of uptime. :-(
> Here 's the kernel config I used. Searching
> for watchdog, there are only two entries. This is the one still enabled:
> CONFIG_OMAP_REMOTEPROC_WATCHDOG=y
> Should I disable that as well?
>
> On Sunday, October 12, 2014 6:29:26 PM UTC+2, Sebastian H wrote:
>>
>> The issue still happened even using the kernel compiled without any
>> watchdog support. The netconsole log didn't include any details. It just
>> rebooted again without any indication why. That was about 24 hours after
>> the last restart.
>> I still had the watchdog package installed (but with even the software
>> watchdog disabled in the kernel, I didn't think it would do anything).
>> Well, I now removed that, but I'm not convinced that it did cause the
>> reboot.
>>
>>
>> On Thursday, October 9, 2014 5:54:40 PM UTC+2, Sebastian H wrote:
>>>
>>> I switched over from kernel 3.8.13 to 3.14.19-ti-r28 (compiled with
>>> netconsole support)  and after a little over 24 hours uptime, my BBB
>>> rebooted without any entries in the netconsole log or any logs on the BBB
>>> that I could find.
>>>
>>> Did anyone have any luck in troubleshooting this issue any further?
>>>
>>> In the meantime, I guess I'll try your suggestion of disabling the
>>> watchdog for now.
>>>
>>>
>>> On Thursday, September 18, 2014 11:48:22 AM UTC+2, William Hermans wrote:

 Short term, you can disable the hardware watchdog in kernel config.
 That should temporarily fix your problem, and if it does not . . . bigger
 mystery.

 Long term, it would be good to figure out what is triggering the
 watchdog. strace on the watchdog PID will not work - I tested this myself.

 The only one thing I can think of off hand is perhaps modifying the
 watchdog module to output a debug message before rebooting the system. As
 to which process triggered a shutdown, and why. If possible . . .

 Will research more tomorrow it is very late ( actually early ) here.

 On Thu, Sep 18, 2014 at 12:57 AM, Thomas Olofsson 
 wrote:

>
>> Forget about claiming its a hardware issue. Because it is not. We've
>> had two beaglebone blacks for close to a year, and a half now. Both are
>> rock solid, running off barrel jack power, or USB( one of each ).
>>
>> Ok well just stating facts that bbw is not rebooting and BBB is with
> the same kernel
>
> Ok i would be happy to stop guessing and actually find the problem.
> Could you give me some real advise on HOW to use the serial module
> appropriately. i do have it connected to the serial console and i have
> event built a kernel with verbosed debugging on i am just not seeing
> anything.
>
> So if you would like any information or dumps or whatever i am happy
> to provide that.
>
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google
> Groups "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to beagleboard...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Beaglebone Black Rebooting Several Times Every Day

[Sebastian H]

For the record, even with the watchdog package removed, my BBB rebooted on 
me again after just 7 hours of uptime. :-(
Here 's the kernel config I used. Searching 
for watchdog, there are only two entries. This is the one still enabled:
CONFIG_OMAP_REMOTEPROC_WATCHDOG=y
Should I disable that as well? 

On Sunday, October 12, 2014 6:29:26 PM UTC+2, Sebastian H wrote:
>
> The issue still happened even using the kernel compiled without any 
> watchdog support. The netconsole log didn't include any details. It just 
> rebooted again without any indication why. That was about 24 hours after 
> the last restart. 
> I still had the watchdog package installed (but with even the software 
> watchdog disabled in the kernel, I didn't think it would do anything). 
> Well, I now removed that, but I'm not convinced that it did cause the 
> reboot.
>  
>
> On Thursday, October 9, 2014 5:54:40 PM UTC+2, Sebastian H wrote:
>>
>> I switched over from kernel 3.8.13 to 3.14.19-ti-r28 (compiled with 
>> netconsole support)  and after a little over 24 hours uptime, my BBB 
>> rebooted without any entries in the netconsole log or any logs on the BBB 
>> that I could find. 
>>
>> Did anyone have any luck in troubleshooting this issue any further? 
>>
>> In the meantime, I guess I'll try your suggestion of disabling the 
>> watchdog for now.
>>
>>
>> On Thursday, September 18, 2014 11:48:22 AM UTC+2, William Hermans wrote:
>>>
>>> Short term, you can disable the hardware watchdog in kernel config. That 
>>> should temporarily fix your problem, and if it does not . . . bigger 
>>> mystery.
>>>
>>> Long term, it would be good to figure out what is triggering the 
>>> watchdog. strace on the watchdog PID will not work - I tested this myself.
>>>
>>> The only one thing I can think of off hand is perhaps modifying the 
>>> watchdog module to output a debug message before rebooting the system. As 
>>> to which process triggered a shutdown, and why. If possible . . .
>>>
>>> Will research more tomorrow it is very late ( actually early ) here.
>>>
>>> On Thu, Sep 18, 2014 at 12:57 AM, Thomas Olofsson  
>>> wrote:
>>>

> Forget about claiming its a hardware issue. Because it is not. We've 
> had two beaglebone blacks for close to a year, and a half now. Both are 
> rock solid, running off barrel jack power, or USB( one of each ).
>
> Ok well just stating facts that bbw is not rebooting and BBB is with 
 the same kernel

 Ok i would be happy to stop guessing and actually find the problem. 
 Could you give me some real advise on HOW to use the serial module 
 appropriately. i do have it connected to the serial console and i have 
 event built a kernel with verbosed debugging on i am just not seeing 
 anything. 

 So if you would like any information or dumps or whatever i am happy to 
 provide that.


  -- 
 For more options, visit http://beagleboard.org/discuss
 --- 
 You received this message because you are subscribed to the Google 
 Groups "BeagleBoard" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to beagleboard...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.