I had to use my Raspberry Pi to dump the EDID of my monitor (couldn't get
the BBB to do it), and found a resolution that my monitor and the BBB could
tolerate (720p at 60Hz). I was then able to successfully force the
resolution in uEnv.txt.
Unfortunately, this is not the resolution I wanted to
I received my new BBB Rev C board on Friday, and updated the Debian image
last night after determining that it did not ship with the latest image.
I'm seeing a problem with the Gadget Serial port (the one on the Mini-B USB
port).
I have the USB cable connected to my PC (one of the USB 3.0 ports
I've noticed a difference in behavior between the latest Angstrom Linux
image and the latest Debian image available for the BeagleBone Black when
it comes to enumerating the real-time clocks present when a RTC "Cape" is
"present". [I have the actual clock present by use of a generic breakout
bo
>
> Are you sure rcS is the run-level you are in?
> Try adding a symlink to /etc/rc2.d
>
As far as I can tell from a Google search, rcS is correct for hwclock.sh,
as this is something that needs to be done before Linux displays a login
prompt. (That would match the header in hwclock.sh.) It als
I am very new to systemd. Where would I find the systemd equivalent of the
init.d scripts?
--
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 receiv
I have installed the Debian 7.5 2014-05-14 image onto my BeagleBone Black.
Very early in the boot process, Debian appears to synchronize (or attempt
thereof) the time reported by the omap_rtc device (that would be the RTC
built into the AM3359 processor that gets mapped to /dev/rtc0). This can b
I installed the latest Debian 7.5 image (dated 2014-05-14) onto my
BeagleBone Black, and have hit a brick wall trying to figure out why things
I just did on a Raspberry Pi running Raspbian do not work on this version
of Debian. One of those things is trying to get an init.d script to run on
sta
>
> Are you sure rcS is the run-level you are in?
> Try adding a symlink to /etc/rc2.d
>
Actually, I'm no longer sure that the latest BBB Debian image (Debian 7.5
2014-05-14) is using init.d... it looks like it might be using system
instead.
That and I think the kernel might be synchronizing t
>
> Are you sure rcS is the run-level you are in?
> Try adding a symlink to /etc/rc2.d
>
Actually, I'm not sure the latest BBB Debian image (Debian 7.5 2014-05-14)
is using init.d...
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscr
>
> So we have an init script to get the clock in the 'ball park'
>
That explains the May-ish date that I keep booting up to, instead of what
this dmesg entry implies:
[1.025090] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01
00:00:00 UTC (946684800)
But I am still unclear as
My current monitor (Acer X213H) works poorly with the BBB. It appears as if
the BBB picks an incompatible refresh rate and/or resolution when it boots,
as the screen looks like a CRT TV with HSYNC issues. I tried reading the
EDID to get an idea of the problem, and the BBB was unable. However, ou
I am using a BBB running the new Debian image. I have connected a DS1307
RTC (via a "Tiny RTC I2C modules" breakout board) to I2C2, and have added
"cape_enable=capemgr.enable_partno=BB-BONE-RTC" to uEnv.txt such that my
BBB does see this RTC as /dev/rtc1.
I want to synchronize the system clock
12 matches
Mail list logo
