or will I have to
drop it?
Best, Dan.
On Tuesday, July 6, 2021 at 8:37:23 AM UTC-7 Jason Kridner wrote:
> Please visit forum.beagleboard.org/c/general/.
>
> Previous announcement:
> https://groups.google.com/g/beagleboard/c/gXb9lqT0yfM/m/88diLWRZDgAJ
>
--
For more opti
for the pointers.
On Fri, Sep 11, 2020 at 9:47 AM Dan and Ann Barber
wrote:
> Thanks for the help! I really appreciate it! I'll check out a powered hub
>
> On Thursday, September 10, 2020 at 10:55:10 AM UTC-7
> robert.sty...@gmail.com wrote:
>
>> If it is drawing too much current, I
Thanks for the help! I really appreciate it! I'll check out a powered hub
On Thursday, September 10, 2020 at 10:55:10 AM UTC-7
robert.sty...@gmail.com wrote:
> If it is drawing too much current, I suggest a powered hub between BBB and
> HDD
>
> The HDD is USB 2.0 which means max 500mA, but BBB
I have a WD 2TB external USB drive. It mounts fine on my linux laptop. When
I plug it into the beagleboneblack, it times out. Any help would be
appreciated!
lsusb finds the device:
Bus 001 Device 003: ID 1058:2626 Western Digital Technologies, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux
similar to yours, using 8-bits of data and a bunch of latches.
Good to know someone else has had success with this.
One last question. How are you sharing the data with the HDMI frame
buffer?
Cheers, Dan
On Thu, Nov 21, 2019 at 9:44 AM Tomas Espeleta
wrote:
> Thanks Dan!
> Yep, I creat
Very neat Tomas!
A PRU is capturing the write to the video memory? Are you reading the data
in via a parallel interface or serializing it?
Cheers, Dan
On Wednesday, November 20, 2019 at 9:19:44 AM UTC-7, Tomas Espeleta wrote:
>
> Helllo Guys,
> I just wanted to share the first st
Hi Stuart,
I tried to use the PocketBeagle with the battery and also found the extra
current draw. Ultimately I communicated with Octavo and got the following
reply. The OSD3358-SM SiP used on the pocketbeagle internally connects the
LDO1 regulator to both the RTC clock input (VDDS_RTC) as
be a useful
addition to the SBC world.
Cheers, Dan
On Saturday, July 6, 2019 at 10:16:22 AM UTC-6, João Manoel wrote:
>
> Hi Dan,
>
> thank you to share your project, really nice :)
>
> I saw that you used the standard pocketbeagle. I also noticed that you are
> the author of
Although it isn't the 4.3" CAPE, I have gotten a generic and inexpensive
2.8" ILI9348-based SPI display to work with the Pocketbeagle (and
Beaglebone black). It seems reasonably fast although I'm sure not as fast
as the parallel display. I haven't yet gotten the built-in TSC2046
resistive
-
-rw-r- 1 root shadow 1045 Apr 10 00:49 shadow
-rw--- 1 root root960 Feb 7 23:56 shadow-
Dan
On Wed, 10 Apr 2019 at 17:38, Dennis Lee Bieber
wrote:
> On Wed, 10 Apr 2019 03:53:49 -0700 (PDT), Dan Sloane
> declaimed the
> following:
>
> >Hi - do you think this
Hi - do you think this process would work for recovering /etc/passwd when,
despite typing it three times (change, confirm, into notes), my new debian
user password isn't accepted.
Single user mode on BBB seems non-trivial and I'd rather not start again
with my config.
Thanks,
Dan
Your PRU isn't running code so remoteproc has nothing to control. Either
the firmware file is missing from /lib/firmware or it isn't valid code.
On Sunday, March 10, 2019 at 10:27:40 AM UTC-6, gw wrote:
>
>
> [ 1864.134156] remoteproc remoteproc1: powering up 4a334000.pru
> [ 1864.134336]
Programming PRUs is a bit of a moving target as the mechanisms have changed
and evolved and a lot of documentation is out-of-date. I used some of
Mark's stuff and well as the cut method too.
I'm not using the scratchpad but I did write an application that moves data
between PRUs using a
Yes, T11 is connected to P2.12 on pocketbeagle.
On Monday, February 25, 2019 at 7:47:15 AM UTC-7, Hans Leeuw wrote:
>
> Dear community,
>
> Does anyone know if one of the pins on the pocket beagle connects to the
> start button pin pmic_PB_in? Also called T11 as I can see it in the
>
Also, it has been EONS since I've seen a netcom.com address. That's cool :).
On Fri, Feb 15, 2019 at 2:54 AM Dan Hammans wrote:
> You guys are great. I'm going out of town for the weekend so I've ordered
> a couple of the parts suggested to give it a try. Should be here when I get
You guys are great. I'm going out of town for the weekend so I've ordered a
couple of the parts suggested to give it a try. Should be here when I get
back.
Thanks!
Dan
On Thu, Feb 14, 2019 at 1:20 PM Mala Dies wrote:
> Hello,
>
> While reviewing this info. you provided, an optocoup
, I was going to try and talk to an electrical
engineer friend of mine to see what he thought of the situation. What do
you think?
Thanks,
Dan
On Wed, Feb 13, 2019 at 8:17 PM Mala Dies wrote:
> Hey Man,
>
> Seth here. Did you ever figure out the issue w/ setting up a GPIO pin to
> co
What does /var/log/auth.log say on subsequent login attempts? That does
sound odd.
You could also run tcpdump to at least get an idea if it’s being refused
outright vs more of a ssh protocol problem.
On Sun, Feb 10, 2019 at 3:16 PM Chris Green wrote:
> Robert Nelson wrote:
> > On Sun, Feb 10,
LEDs, and other circuitry. I am sure you know
> how to do things. I was trying to latch on to learn more. Sorry.
>
> On Saturday, February 9, 2019 at 11:19:47 PM UTC-6, Dan Hammans wrote:
>>
>> Hi Seth, I really appreciate the reply.
>>
>> I was afraid of that. My
on while
> the board has power.
>
> Seth
>
> P.S. Try UART instead at 3.3v. This may help.
>
> On Saturday, February 9, 2019 at 2:58:12 AM UTC-6, Dan Hammans wrote:
>>
>> I'm not sure that I understand the difference between the Beagleboard
>> forum and the Be
I'm not sure that I understand the difference between the Beagleboard forum
and the Beaglebone forum, but thought I would try posting here as well.
I have a Beaglebone Blue connected to a GPS module via the GPS micro JST
connector. I selected this one because it has +5v, which is what is needed
Sounds like software. Can you get DNS resolution? That’s the first thing
I’d check.
On Wed, Feb 6, 2019 at 9:55 AM Vince Seiferd wrote:
> I am testing a new (to me) cape on Beaglebone Black which worked for two
> days. The image is run on SDCARD. Suddenly I could not access the web on
> the
to challenge the clock down.
>
> After reading the datasheet of the PMIC, I would like to add a resistor to
> charge it and add a capacitor as needed.
> http://www.ti.com/lit/ds/symlink/tps65217.pdf
>
> 2019年2月3日日曜日 1時55分29秒 UTC+9 Dan Julio:
>>
>> IIRC, the pock
IIRC, the pocketbeagle can see current spikes over 200 mA from the battery
while it is booting, although it takes less power after it is booted and
idling. Probably one of two things is happening. The battery voltage
droops and either its own protection circuitry cuts off the power or the
It should be possible to move to the Pocketbeagle. I moved a moderately
complex application from the black to the pocketbeagle. I use GPIO, both
SPIs, I2C and USB. Here's what I found (4.14-based beaglebone debian
distro):
1. SPI and I2C devices should be ok providing you are using the
To close this thread out, I heard back from Octavo systems. The OSD3358-SM
SiP used on the pocketbeagle internally connects the LDO1 regulator (I
misspoke above) to both the RTC clock input (VDDS_RTC) as well as the VDDS
input. The extra current is taken by the connection to the VDDS power
I have done some further research. It seems that the tps65217.c mfd driver
in the kernel sets the OFF bit (bit 7) in the PMIC STATUS register (offset
0xA) in order to make sure it shuts down all output voltages (including the
RTC 1.8V supply from LDO2) when the system executes a power-down.
Hey Fred,
Here are some answers to your questions:
1. I have attached a LiPo battery from a Pentax camera that has a built-in
10K thermistor and I put a 75k resistor across the T signal and ground on
the pocketbeagle. I also added a 10 uF electrolytic cap between Vbatt and
ground on the
Thanks for those helpful pointers, Jason. I will dig in.
It definitely stops charging for me and as you see in the response to Fred,
I definitely see it charging while the system is booted. Could some other
piece of code tell the driver to disable charging on the way down?
--
For more
to 4.2v.
Thanks, Dan
--
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 beagleboar
Thanks very much for your help Robert, this is exactly what I was looking
for.
Cheers,
Dan
On Wednesday, January 24, 2018 at 12:29:57 PM UTC-5, RobertCNelson wrote:
>
> On Wed, Jan 24, 2018 at 11:20 AM, Dan Tian <dt...@bluerover.ca
> > wrote:
> > Hi,
> > I
.
Any input would be much appreciated.
Thanks,
Dan
--
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, sen
I meant in the onboard EEPROM...
On Thursday, October 19, 2017 at 8:38:27 AM UTC-4, Dan Brown wrote:
>
> I have noticed that both of my PocketBeagles have unique MACs that do not
> move with the SD card when connecting via USB. (I tried switching the
> cards between PBs and t
I have noticed that both of my PocketBeagles have unique MACs that do not
move with the SD card when connecting via USB. (I tried switching the
cards between PBs and the MACs stay with the boards. Could it be something
in the onboard flash?
On Wednesday, October 18, 2017 at 5:23:54 PM UTC-4,
U4 is a USBLC6-2.
As for the I2C pullups, I forgot to add to this board as I have them on
another. I'll add here too...
On Wednesday, October 11, 2017 at 11:42:43 PM UTC-4, Graham wrote:
>
> Dan:
>
> What is the part number for your U4 ?
>
> You are going to have to ad
If you are just trying to hook up a quick and dirty connection, then tie 15
and 13 together for grounding the ID pin. Then you will tie 5 and 7
together so the CPU understands there is a USB port in use and it is
powered. Your USB connector connects then to pins 7, 9, 11, and 15. Pin
15 is
to gnd on the connector
> There is a Vin(7) and Vbus(5). One of those are not used for the +5
> connection? So +5 goes to pin Vout(13)
>
> Is Vin used when the power is flowing into the PB from the USB?
>
> Thanks
> Andy
>
>
> On Tue, Oct 10, 2017 a
I don't have an account on github. I don't have any issue with the library
being made available there. Make things alot easier for people to find I'd
think! Make sure to upload the second (smaller) version.
Dan
On Sunday, October 8, 2017 at 7:27:03 PM UTC-4, Jason Kridner wrote
On the expansion connectors, the +5V from the built-in USB port is
connected to the pins labeled VOUT on the back. GND labels ground pins.
On Saturday, October 7, 2017 at 3:05:43 PM UTC-4, Andy Bushnell wrote:
>
> Which pins are to +5 and gnd?
>
> Thanks!
> Andy
>
>>
>>>
--
For more
On the expansion connectors, the +5V from the built-in UBS port is
connected to the pins labeled VOUT on the back. GND labels ground pins.
On Saturday, October 7, 2017 at 3:05:43 PM UTC-4, Andy Bushnell wrote:
>
> Which pins are to +5 and gnd?
>
> Thanks!
> Andy
>
>
>>>
--
For more
Try this version then please?
On Tuesday, October 3, 2017 at 3:50:38 PM UTC-4, Dan Brown wrote:
>
> While working with the PocketBeagle, I created a library for Eagle with a
> part for the Board Outline, Headers and Bottom Legend. (All taken from the
> Eagle design files and me
While working with the PocketBeagle, I created a library for Eagle with a
part for the Board Outline, Headers and Bottom Legend. (All taken from the
Eagle design files and messaged a bit...)
I am attaching it here!
It was created in Eagle version 7.7.
--
For more options, visit
, September 29, 2017 at 10:01:15 AM UTC-4, Dan Brown wrote:
>
> I have added a USB Type A connector to my Pocket Beagle. When I plug a
> Kingston 8GB Flash Key into the port and boot the PocketBeagle, I can see
> that the device is sort of detected, but I never get access
>
>
> I am going with pins facing down. For me, I want the PocketBeagle on the
top for access to the power button and leds. I will have capes/scarfs
below.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google
I have installed my headers on the bottom. They do not fit on top. I also
figure that this is best so I can heatsink the Octavo chip if needed.
On Friday, September 29, 2017 at 8:05:14 AM UTC-4, Giulio Moro wrote:
>
> I got myself a PocketBeagle and I realized that I cannot fit headers on
>
I have added a USB Type A connector to my Pocket Beagle. When I plug a
Kingston 8GB Flash Key into the port and boot the PocketBeagle, I can see
that the device is sort of detected, but I never get access to the Flash.
In /var/log/messages I see the following block:
Sep 28 12:08:19 beaglebone
Thanks so much for your help Robert!
I will upgrade my kernel and give it a try.
Thanks!
Dan
> On Sep 18, 2017, at 3:13 PM, Robert Nelson <robertcnel...@gmail.com> wrote:
>
> On Mon, Sep 18, 2017 at 2:08 PM, Dan Tian <dt...@bluerover.ca> wrote:
>> Hi Robert,
>&
both wifi tether and connect to a
second AP at the same time? This is actually why I am exploring the wifi direct
option, from my understanding it is peer to peer wifi which is different from
tether mode. Hopefully my explanation makes sense to you.
Thanks again!
Dan
> On Sep 18, 2017, at 1
Hi all,
I noticed that the wifi chip on BBB wireless WL1835 from TI supports wifi
direct, I am wondering if anyone has any success configuring and setting up
a wifi direct link between BBB wireless and a PC? I have searched online
but couldn't find much information regarding this. Thanks in
Hello
I'm interested in using the precise time sync over wifi features of the
WL1835MOD, but it appears the pin necessary to make this work (GPIO11 on
the WL1835MOD) is not connected to anything on the BBBW. This may be a
silly question, but is there any chance that it could be made available
And another:
[ 569.776621] Unable to handle kernel paging request at virtual address
01010241
[ 569.784293] pgd = c0004000
[ 569.787164] [01010241] *pgd=
[ 569.790986] Internal error: Oops: 5 [#1] PREEMPT SMP ARM
[ 569.796572] Modules linked in: ctr ccm usb_f_acm u_serial usb_f_ecm
Well, I'm out till Monday so, how about?
linux-image-3.14.40-ti-r62
linux-image-4.1.0-rc1-bone0
both are in the repo, via apt-get..
Thanks. I'll take a look. I'm trying 3.8 for the moment. Is there a feature
matrix somewhere? In terms of what peripherals work on which kernels?
Dan
Similar problem with 3.14.38-ti-r60
Unable to handle kernel paging request at virtual address 0101020d
[ 7574.437128] pgd = c0004000
[ 7574.443300] [0101020d] *pgd=
[ 7574.448344] Internal error: Oops: 817 [#1] PREEMPT SMP ARM
[ 7574.454121] Modules linked in: ctr ccm usb_f_acm u_serial
Got a kernel panic on Jessie running kernel 3.14.39-ti-r61:
BBB rev C.
TP-Link TL WN722N.
Wall wart power.
No capes.
Is there anywhere else I should post this?
[ 439.103374] Unable to handle kernel paging request at virtual address
01010241
[ 439.111041] pgd = c0004000
[ 439.113910]
Here's another, from different BBB with the same setup:
[Apr29 23:08] hrtimer: interrupt took 387492 ns
[Apr29 23:15] INFO: task kworker/0:1:15 blocked for more than 120 seconds.
[ +0.006971] Tainted: G O 3.14.39-ti-r61 #1
[ +0.017714] echo 0
[ +8.711840] [ cut here ]
[ +0.004777] kernel BUG at mm/slab.c:2919!
[ +0.004088] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
[ +0.005940] Modules linked in: ctr ccm usb_f_acm u_serial usb_f_ecm
g_multi usb_f_mass_storage usb_f_rndis u_ether libcomposite arc4
Robert, is there a 3.14 kernel you consider stable? Have you tested the
previous one (3.14.38-ti-r60) much?
We also want compatibility with the Logicsupply UWN-200 (MediaTek MT7601)
adaptor, but it looks like we may be better off with kernel 3.8 for that.
Thanks,
Dan
--
For more options
Another:
[ 65.549033] Unable to handle kernel paging request at virtual address
0101020d
[ 65.556700] pgd = c0004000
[ 65.562498] [0101020d] *pgd=
[ 65.567712] Internal error: Oops: 805 [#1] PREEMPT SMP ARM
[ 65.573493] Modules linked in: ctr ccm usb_f_acm u_serial usb_f_ecm
On Wednesday, April 29, 2015 at 3:08:05 PM UTC-7, RobertCNelson wrote:
DOes the opps go away
when it's not plugged in?
Hard to tell because it's intermittent. I'm currently trying to trigger it
with the wifi adaptor still plugged in. I got two panics in a row and now I
can't reproduce
There's a patch
https://github.com/beagleboard/image-builder/commit/0b7dcfbd5ddd852116288c80106f20e1af5c4987
that appears to address this issue.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
,
Dan
--
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
:
##make sure, these tools are installed: dosfstools rsync
#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v2.sh
*How can I add multiple DT's to /etc/default/capemgr ? (Sytax for CAPE= 1 2
3 ...)*
Thanks,
Dan.
On Thursday, 6 March 2014 23:58:54 UTC+2, RobertCNelson wrote:
On Thu, Mar 6
, check your gatway with route -n
Best, Dan.
--
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
on the board.
Thank you
Dan G
On Thu, Aug 14, 2014 at 1:52 PM, Gerald Coley ger...@beagleboard.org
wrote:
EEPROM is write protected. So, it should not have been corrupted unless
you were messing with that.
It is possible that it could have died, but it is not something I have
ever seen. I
)
Is there a way to determine if this is a hardware error with the I2C bus,
or an EEPROM that needs to be reloaded?
BBB
PCBrevB5
No capes
Thanks
Dan G.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
Thanks for the WinSCP info. Using it I can now see what's on my BBB.
Seems to be a drag and drop operation from left half(PC) of screen to right
half(BBB) of screen.
On Tuesday, August 5, 2014 2:11:52 PM UTC-4, tdli...@gmail.com wrote:
On Sunday, August 3, 2014 10:20:39 AM UTC-4, dan perry
Well I have tried using PuTTY with 192.168.7.2 and SSH and clicking on open.
I then get: login as:
and I type in root and hit enter.
then root@beaglebone: # pops up and
then I type in yes and hit enter.
But from then on all I get is a string of Y's down the left side of the
screen.
I got the
I looked up Samba on the internet but haven't figured out exactly what it
does or how to use it.
Thanks though, I'll keep trying.
On Monday, August 4, 2014 7:49:57 PM UTC-4, William Hermans wrote:
Lost, You can install, setup, and use Samba on the BBB. So for instance if
you're using
1.5 years later, thank you.
On Friday, December 28, 2012 10:44:13 AM UTC-8, steve.ch...@googlemail.com
wrote:
I appear to have fixed the problem I was having. In Jan's bit map of the
Debug Configuration dialogue there is no reference to the executable in
the text box called Remote Absolute
how do i enable cape support with debian 3.14.4-bone4 ?
--
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
On Fri, Apr 11, 2014 at 11:23 AM, John Syn john3...@gmail.com wrote:
Just remove the part that does setenv mmcdev 0
If I do this, can I still boot from sdcard by holding the user boot button?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you
also, I dont have this: setenv mmcdev 0
On Sat, Apr 12, 2014 at 3:50 PM, dan danden...@gmail.com wrote:
On Fri, Apr 11, 2014 at 11:23 AM, John Syn john3...@gmail.com wrote:
Just remove the part that does setenv mmcdev 0
If I do this, can I still boot from sdcard by holding the user boot
How about the reverse, I want to boot from emmc WHILE and SD card is
inserted. Previously I had used the boot button, now I want to undo that.
On Wednesday, April 9, 2014 12:44:02 PM UTC-6, Gerald wrote:
Same as before. You need to hold the boot button down to force it to boot
from SD.
I booted an image on sdcard by pressing the user/boot button. I then
flashed the image to the emmc, which works fine. The system boots properly
from emmc when there is no sdcard inserted, but if I insert an sdcard I can
no longer boot from emmc.
I have insterted an sdcard without boot flag
contents to /dev/sd1/uEnv.txt
mmcdev=1
bootpart=1:2
mmcroot=/dev/mmcblk1p2 ro
- and when you reboot, the microSD should not cause a hang, but appear in
the file system.
At least this works for me.
On 4/10/2014 5:28 PM, Dan Denson wrote:
I booted an image on sdcard by pressing
:05 PM, dan wrote:
so I found a usb adapter. I made a bootable primary partition, 64MB,
formatted vfat, and made a file uEnv.txt, no go. Still hangs at boot.
mmcdev=1
bootpart=1:2
mmcroot=/dev/mmcblk1p2 ro
On Thu, Apr 10, 2014 at 6:56 PM, dan danden...@gmail.com wrote:
Chad, it's
Try a Wandboard as an alternative to the Beagle Bone Black until supply
catches up with demand:
http://www.wandboard.org/
If you are looking to go into production there is a path forward with
Wandboard (7-10 lifespan and supply guarantee)
On Tuesday, February 11, 2014 8:13:47 AM UTC-6,
Ulf, does your kernel patch interrupt data streams? In other words, for
example, if I'm running a webcam and I hotplug another device, will data
transfers from the webcam be affected?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are
, and then
re-plug it after boot in order to see it again.
Any ideas on what might be happening here? Any hints?
Thanks,
Dan
[dmesg log of a working connect]
[ 90.017824] usb usb1: usb wakeup-resume
[ 90.017930] usb usb1: usb auto-resume
[ 90.017980] hub 1-0:1.0: hub_resume
[ 90.018090] hub 1-0
Awesome, I'm getting the installation to boot properly now. Thank you very
much!
On Sunday, December 22, 2013 7:49:23 AM UTC-7, RobertCNelson wrote:
On Sat, Dec 21, 2013 at 6:02 PM, Dan Paulat dpa...@gmail.comjavascript:
wrote:
I have been using Angstrom for a little while now, and now
On Sunday, December 22, 2013 7:49:23 AM UTC-7, RobertCNelson wrote:
On Sat, Dec 21, 2013 at 6:02 PM, Dan Paulat dpa...@gmail.comjavascript:
wrote:
I have been using Angstrom for a little while now, and now am attempting
to
install Ubuntu 13.10 on my BeagleBoard-xM using the following
On 11/20/2013 8:23 AM, selsin...@gmail.com wrote:
On 19/11/13 18:34, Mike Bremford wrote:
The .dtbo's distributed with Robert's 3.12 kernel binary exhibit the symptoms I
described, but no I haven't compiled from DTS source (because I haven't been
able to find them). That said: yep, that
is that it takes about two *minutes* for a login prompt to
show up over my ftdi serial line. The console logging from the kernel stops
after about ten seconds, then nothing for a long time, then finally the
prompt comes up.
Thanks,
Dan
--
For more options, visit http://beagleboard.org/discuss
---
You
a system that can work over wired or wireless
ethernet. Am I in for bootup problems later on when I add eth0 back in?
Thanks to both of you!
Dan
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard
Thanks. Any plans to get it into the upstream kernel?
--
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
HI, Jesper, Fernando,
I did see that. But it was not the distribution I used. The box I was using
was old and fell apart. I'll be back in three weeks and put a newer Ubuntu
box together and use that tool chain. Sounds like the right one.
Best, Dan.
--
For more options, visit http
86 matches
Mail list logo
