Got my first BBB last week, installed latest Debian. USB Hot Plug was
completely hosed in Kernel 3.8 so I upgraded to 3.16 (latest non-rc
version). Currently running CUPS print services (including Airprint) and
weewx. It appears that the BBB is rebooting three or four times between
10pm and 1am
I am booting straight from eMMC that I flashed, no uSD and no serial
interface. I have disabled cups and weewx from starting and removed the
external USB HUB and changed the power supply to another 5v 2a. I can tell
it has rebooted by looking at syslog for ntpdate 'step time server' events.
My
I have downgraded the kernel from 3.16.0-bone2 to 3.15.10-bone8 and so far
no reboots in the last 3 hours. If I get a full 24 hr cycle without
reboots, I'll blame it on 3.16.0 and try to re-attach ext USB HUB, weather
data logger, printer, and enable cups and weewx and see how far I get this
ti
Plug on both power supplies is correct size and fit nice and snug.
On Thursday, September 4, 2014 5:46:22 AM UTC-4, PLyttle wrote:
>
>
> Maybe check your power plug. There are many plugs that fit the socket on a
> BBB, but some do not provide a reliable connection. The one you should be
> using
Instead of rebooting 10 to 12 times it only rebooted 3 times in syslog, at
6:24pm and 11:06pm and 12:03am. Still random reboots though with nothing in
USB and sitting idle. Not so sure it's a kernel issue at this point, could
be hardware related but willing to try another kernel to see what happ
I just downgraded to 3.14.17-bone8 so let's see how that works. Will watch
syslog for 24 hrs and see if it reboots.
On Wednesday, September 3, 2014 12:28:04 PM UTC-4, RobertCNelson wrote:
>
>
> Thanks for the report, please let us know how v3.15.x react's too..
> I'm currently chasing a few othe
Thanks for the suggestion, if I get reboots with 3.14.17 I'll try the usb
power and if that doesn't work I'll go back to 3.8 although I had USB hot
plug issues with that version.
On Thursday, September 4, 2014 6:49:16 AM UTC-4, lisarden wrote:
>
> power the board by USB, remove the wall adapter
element14
purchased from an online vendor.
On Thursday, September 4, 2014 7:04:52 AM UTC-4, Greg Kelley wrote:
>
> Thanks for the suggestion, if I get reboots with 3.14.17 I'll try the usb
> power and if that doesn't work I'll go back to 3.8 although I had USB hot
>
2014 12:59:41 PM UTC-4, Greg Kelley wrote:
>
> BBB ran for 6 hours and just rebooted at 12:30pm so I now have it powered
> through the USB port with a 5v1a power supply instead of through the main
> power plug. If this reboots my last attempt will be to downgrade back to
> 3.8 and
Hi Robert, I reflashed the original distro and it ran for about a half hour
and rebooted so I have determined it is a hardware issue, (probably a
grounding problem according to the vendor so perhaps there is a QC issue at
element14) so I have returned the element14 BBB to the vendor for a refund
in at power up and would not recognize any USB devices hot plugged into the
Hub. Not a problem with 3.14, 3.15, 3.16 when I was testing.
On Thursday, September 4, 2014 2:28:58 PM UTC-4, RobertCNelson wrote:
>
> On Thu, Sep 4, 2014 at 1:26 PM, Greg Kelley > wrote:
>
> Greg, please
Update: I received my new BBB - a CurcuitCo version from Adafruit on
Tuesday. On Wednesday I got it set up almost identical to the other one I
sent back. It has 3.14.17-bone8 kernel. It rebooted/reset on Thursday at
2:15am and the physical ethernet port was down, so I had to connect via the
USB
Hi Robert, I just checked around and a Debug Cable (34M8872 FTDI
TTL-232R-3V3) is $42 on eBay. I don't mind spending some time
troubleshooting this but not willing to go out and invest in pieces and
parts. I do have two Serial to USB cables to connect to some HAM Radio
gear, but not the right h
Robert, apt-get couldn't find linux-image-3.14.17-ti-r19, will go check on
your site and get install-me.sh
On Friday, September 12, 2014 11:43:14 AM UTC-4, Greg Kelley wrote:
>
> Hi Robert, I just checked around and a Debug Cable (34M8872 FTDI
> TTL-232R-3V3) is $42 on eBay
Robert,
I think part of the reason ntp and dhcpclient aren't getting network
connections at boot is because they are set at S03 in init and wicd is set
at S06 and is last to get going. It appears that eth0 is not coming up
until wicd loads?
Also, the install-me.sh failed at the end with final
15 minutes so I
can tell when it's resetting).
On Friday, September 12, 2014 12:35:31 PM UTC-4, RobertCNelson wrote:
>
> On Fri, Sep 12, 2014 at 11:27 AM, Greg Kelley > wrote:
>
> Correct, wicd set's up eth0, that's how we got the 11-12 second bootup
> time. Ot
Robert,
I just made a note to myself to comment out the backup commands in your
install-me script file (so that should leave enough space in uboot) before
I run it.
On Friday, September 12, 2014 1:23:35 PM UTC-4, RobertCNelson wrote:
>
> On Fri, Sep 12, 2014 at 12:08 PM, Greg Kelley &
p 12, 2014 at 1:37 PM, Greg Kelley > wrote:
> > Robert,
> >
> > I just made a note to myself to comment out the backup commands in your
> > install-me script file (so that should leave enough space in uboot)
> before I
> > run it.
>
> With the direction
7 AM UTC-4, RobertCNelson wrote:
>
> On Fri, Sep 12, 2014 at 8:37 AM, Greg Kelley > wrote:
>
> BTW, that "3.14.x" isn't being worked on... If you have a new "testnig"
> image:
>
> sudo apt-get update
> sudo apt-get install linux-image-3.14.17-ti-r19
daily reset
times being so close, but there is nothing is syslog except cron.hourly
until the new boot sequence starts.
On Saturday, September 13, 2014 7:25:57 AM UTC-4, Greg Kelley wrote:
>
> Update: I installed 3.14.17-ti-r19 yesterday about 3pm and set eth0 to
> auto so it comes up ear
ptember 13, 2014 8:14:05 AM UTC-4, Greg Kelley wrote:
>
> Update: the BBB just reset again at 7:49am. That's interesting, because it
> reset twice yesterday at almost the same times 7:35am and 8:13am and today
> at 7:13am and 7:49am. cron daily runs at 6:25am and I have no cto
n Saturday, September 13, 2014 8:14:05 AM UTC-4, Greg Kelley wrote:
>
> Update: the BBB just reset again at 7:49am. That's interesting, because it
> reset twice yesterday at almost the same times 7:35am and 8:13am and today
> at 7:13am and 7:49am. cron daily runs at 6:25am and I have
rial debug cable that I'll use maybe two
days to capture data that might or might not shed light on the issue.
On Saturday, September 13, 2014 8:14:05 AM UTC-4, Greg Kelley wrote:
>
> Update: the BBB just reset again at 7:49am. That's interesting, because it
> reset twice yesterd
William,
I'm not using any I/O at this time. Setting this up in steps. First was to
get it running as a CUPS and weewx Server like my RasPi. I can 'play' with
it later once it's stable. Found a cable on eBay for $6 shipped from CA
using PL303HX claims 3.3v TTL.
Also, no resets since 3pm yester
I have now been running 22 hours without a reset - this is a first.
Yesterday at 3:17pm I changed out power supplies. I also killed wicp. So
now I'm suspicious of wicp as the culprit. I added 'auto eth0' in
/etc/network/interfaces since I'm hard wire connected and wicp was bringing
up eth0 far
Update: I changed power supplies back to the 5v2a and removed wicd
yesterday at 3:20pm. Ran fine until 8:42am and reset after 16hrs. This
time, it didn't bring up eth0 and was unreachable. I pulled the power and
powered back up, booted normally. Interesting thing is that syslog only
shows the s
One other note, current Debian distro that comes with BBB has ntpdate
installed. I have removed ntpdate and installed ntp in it's place.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
I just changed over to the Switching Power Supply and eth0 failed to come
up on boot. I hit the reset button and a reboot brought it up. So now it
seems there are eth0 issues as well as resets. Going from bad to worse.
--
For more options, visit http://beagleboard.org/discuss
---
You received
I had a total of 5 resets yesterday one at 8am, 5pm, 9pm, 10pm, 11pm using
a switching power supply. Maybe I should go back to the cheapo power supply
as I was only resetting once or twice a day with that one. I'll wait and
see what Thomas comes up with before ordering the serial debug cable. On
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://beag
t;
>
> On Monday, October 13, 2014 1:37:18 PM UTC-5, 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
Update to Reboot Issue:
OK I did two things at once which from my old Beta Tester days is a no-no
since you can't figure out which change made a difference. But
I updated the kernel to 3.14.23-ti-r34
Then I did an apt-get update/upgrade and I noticed that dbus got upgraded
in the process.
our experiences
(even if they are silly noob mistakes) all has merit in forming a picture
of the issue that we as a group can evaluate and perhaps discover a
solution. That's one of the great things about discussion forums such as
this.
On Tuesday, November 18, 2014 7:45:27 PM UTC-5, William H
Yes, first Unix then Linux.
Let's split mouse turds by the halves, shall we?
On Wednesday, November 19, 2014 11:05:02 AM UTC-5, William Hermans wrote:
>
> Seems I hit a nerve, however I'm fairly sure that Linux has only been
> around since 91 so . . .
>
> Maybe you mean UNIX.
>
>
--
For more o
@Wulf: I see this is your first contribution to our ongoing discussion of
BBB random booting.
And your comment has what to do with this thread?
I am free to express my opinion of M$ products AFAIK, and many many years
of unfortunate experiences has molded my viewpoint, but that's a topic for
a
I concur as I have been up and running three days now with no random
reboots, so I consider this issue resolved.
Thanks Robert C,
Signing Off, Over and Out
On Wednesday, November 19, 2014 4:18:23 PM UTC-5, RobertCNelson wrote:
>
>
> Out side of v3.8.x it should be fixed with:
>
> v3.14.23-ti-
36 matches
Mail list logo
