Re: [beagleboard] Re: debian: test images (2014-01-16)
Ah, that's very helpful, thanks.
Ideally I was hoping to use the RTS signal though. From what I had read
that seemed to be the standard for UART RS485 mode in the Linux kernel, but
looking into the omap_serial driver it looks like it wasn't implemented (on
3.8 at least).
On Wednesday, January 22, 2014 3:36:08 AM UTC-5, Mickae1 wrote:
>
> Hi,
>
> About the RS485 support on the BBB, you have to modify the driver omap
> serial and control the gpio that you want. But if you want a quick
> solution, i already made a patch for that :)
>
> You just need to :
>
> git clone git://github.com/RobertCNelson/linux-dev.git
> cd linux-dev/
> git checkout origin/am33x-v3.8 -b tmp
>
> in the linux-dev folder, you have the KERNEL folder. You just need to put
> the file in the patches/omap folder and edit the patch.sh :
> :
>
> ${git} "${DIR}/patches/omap/000X-omap-rs485-support.patch"
>
>
> in the linux-dev folder :
> cp system.sh.sample system.sh
> edit the file system.sh:
>
> be sure that you have :
> ##For TI: OMAP3/4/AM35xx
> ZRELADDR=0x80008000 <== uncomment !
>
> the correct path to your sdcard :
> MMC=/dev/sdc
>
>
>
> to build the kernel , you just need to use this command : ./build_kernel.sh
>
> to install the new kernel to your sdcard : ./tools/install_kernel.sh
>
>
>
>
> On Tue, Jan 21, 2014 at 10:52 PM, Alexander Hiam
>
> > wrote:
>
>> Yeah I noticed that. I was hoping to go the ioctl route because I'm
>> working on a cape that gives the option of RS232 or RS485 on UART4, so the
>> runtime switching would be great.
>>
>> Hopefully I'm just doing something stupid, but I can't get it to work
>> through ioctl. I've tried in both C and Python on an Angstrom image with
>> 3.8, this testing image, and an old Angstrom with 3.2 on the original BB.
>> The tests I'm trying are here:
>> https://gist.github.com/alexanderhiam/8548894
>>
>> On all three bones the C ioctl() call raise errno 25. On the two with 3.8
>> the Python ioctl() call raises 'IOError: [Errno 25] Inappropriate ioctl for
>> device' and on the bone with 3.2 it raises 'IOError: [Errno 22] Invalid
>> argument'.
>>
>> I was under the impression that you had to enable the RS485 ioctl
>> settings when building the kernel, but I can't remember where I got that
>> idea and I haven't actually tried it yet :p
>>
>> Perhaps I should start a new thread for this one...
>>
>> -Alex
>>
>>
>> On Tuesday, January 21, 2014 3:49:38 PM UTC-5, RobertCNelson wrote:
>>
>>> On Tue, Jan 21, 2014 at 2:33 PM, Robert Nelson
>>> wrote:
>>> > On Tue, Jan 21, 2014 at 2:14 PM, Alexander Hiam
>>> wrote:
>>> >> Thanks Robert, I just booted it for the first time and so far so
>>> good. I see
>>> >> that there's still no ioctl for RS485 mode on the UARTs though. Is
>>> there a
>>> >> reason RS485 support isn't enabled on the BB kernel builds?
>>> >
>>> > There is no module for "rs485" you need to call the omap-serial driver
>>> > with the proper ioctls
>>> >
>>> > https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
>>> stable.git/tree/Documentation/serial/serial-rs485.txt?id=
>>> refs/tags/v3.8.13
>>>
>>> Looks like you can enable it on boot time too..
>>> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
>>> stable.git/tree/Documentation/devicetree/bindings/serial/
>>> rs485.txt?id=refs/tags/v3.8.13#n28
>>>
>>> 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...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-16)
On Monday, January 20, 2014 8:48:50 PM UTC-5, RobertCNelson wrote: > > > Yes. Definitely! I need both WLAN and ETH, also connman seems more > > established. Finally, connman has better dbus integration for interface > > configuration. > > Does the version of connman (1.15) we have in the repo right now work > for the dual wlan/eth situation? > No, apparently not! Once I configured the wifi for connman and restarted the service, it hung for a minute, then panic'd: root@beaglebone:/var/lib/connman# systemctl restart connman.service [15841.027741] INFO: task wpa_supplicant:515 blocked for more than 60seconds . [15841.035254] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [15841.043567] wpa_supplicant D c045aae7 0 515 1 0x [15841.050462] Kernel panic - not syncing: hung_task: blocked tasks [15841.056860] [] (unwind_backtrace+0x1/0x8a) from [] ( panic+0x51/0x148) [15841.065512] [] (panic+0x51/0x148) from [] (watchdog+ 0x14f/0x194) [15841.073718] [] (watchdog+0x14f/0x194) from [] ( kthread+0x67/0x74) [15841.082011] [] (kthread+0x67/0x74) from [] ( ret_from_fork+0x11/0x34) [15841.090550] drm_kms_helper: panic occurred, switching back to text console After rebooting, ethernet comes up, but the wifi doesn't. According to syslog, it does try to authenticate but times out. This is a rtl8192cu based USB Wifi adapter (EDIMax), which I never have seen work reliably, so this many not be a connman issue. -W. -- 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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-16)
Hi,
About the RS485 support on the BBB, you have to modify the driver omap
serial and control the gpio that you want. But if you want a quick
solution, i already made a patch for that :)
You just need to :
git clone git://github.com/RobertCNelson/linux-dev.git
cd linux-dev/
git checkout origin/am33x-v3.8 -b tmp
in the linux-dev folder, you have the KERNEL folder. You just need to put
the file in the patches/omap folder and edit the patch.sh :
:
${git} "${DIR}/patches/omap/000X-omap-rs485-support.patch"
in the linux-dev folder :
cp system.sh.sample system.sh
edit the file system.sh:
be sure that you have :
##For TI: OMAP3/4/AM35xx
ZRELADDR=0x80008000 <== uncomment !
the correct path to your sdcard :
MMC=/dev/sdc
to build the kernel , you just need to use this command : ./build_kernel.sh
to install the new kernel to your sdcard : ./tools/install_kernel.sh
On Tue, Jan 21, 2014 at 10:52 PM, Alexander Hiam wrote:
> Yeah I noticed that. I was hoping to go the ioctl route because I'm
> working on a cape that gives the option of RS232 or RS485 on UART4, so the
> runtime switching would be great.
>
> Hopefully I'm just doing something stupid, but I can't get it to work
> through ioctl. I've tried in both C and Python on an Angstrom image with
> 3.8, this testing image, and an old Angstrom with 3.2 on the original BB.
> The tests I'm trying are here:
> https://gist.github.com/alexanderhiam/8548894
>
> On all three bones the C ioctl() call raise errno 25. On the two with 3.8
> the Python ioctl() call raises 'IOError: [Errno 25] Inappropriate ioctl for
> device' and on the bone with 3.2 it raises 'IOError: [Errno 22] Invalid
> argument'.
>
> I was under the impression that you had to enable the RS485 ioctl settings
> when building the kernel, but I can't remember where I got that idea and I
> haven't actually tried it yet :p
>
> Perhaps I should start a new thread for this one...
>
> -Alex
>
>
> On Tuesday, January 21, 2014 3:49:38 PM UTC-5, RobertCNelson wrote:
>
>> On Tue, Jan 21, 2014 at 2:33 PM, Robert Nelson
>> wrote:
>> > On Tue, Jan 21, 2014 at 2:14 PM, Alexander Hiam
>> wrote:
>> >> Thanks Robert, I just booted it for the first time and so far so good.
>> I see
>> >> that there's still no ioctl for RS485 mode on the UARTs though. Is
>> there a
>> >> reason RS485 support isn't enabled on the BB kernel builds?
>> >
>> > There is no module for "rs485" you need to call the omap-serial driver
>> > with the proper ioctls
>> >
>> > https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
>> stable.git/tree/Documentation/serial/serial-rs485.txt?id=
>> refs/tags/v3.8.13
>>
>> Looks like you can enable it on boot time too..
>> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
>> stable.git/tree/Documentation/devicetree/bindings/serial/
>> rs485.txt?id=refs/tags/v3.8.13#n28
>>
>> 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/groups/opt_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/groups/opt_out.
000X-omap-rs485-support.patch
Description: Binary data
Re: [beagleboard] Re: debian: test images (2014-01-16)
Yeah I noticed that. I was hoping to go the ioctl route because I'm working on a cape that gives the option of RS232 or RS485 on UART4, so the runtime switching would be great. Hopefully I'm just doing something stupid, but I can't get it to work through ioctl. I've tried in both C and Python on an Angstrom image with 3.8, this testing image, and an old Angstrom with 3.2 on the original BB. The tests I'm trying are here: https://gist.github.com/alexanderhiam/8548894 On all three bones the C ioctl() call raise errno 25. On the two with 3.8 the Python ioctl() call raises 'IOError: [Errno 25] Inappropriate ioctl for device' and on the bone with 3.2 it raises 'IOError: [Errno 22] Invalid argument'. I was under the impression that you had to enable the RS485 ioctl settings when building the kernel, but I can't remember where I got that idea and I haven't actually tried it yet :p Perhaps I should start a new thread for this one... -Alex On Tuesday, January 21, 2014 3:49:38 PM UTC-5, RobertCNelson wrote: > > On Tue, Jan 21, 2014 at 2:33 PM, Robert Nelson > > > wrote: > > On Tue, Jan 21, 2014 at 2:14 PM, Alexander Hiam > > > > wrote: > >> Thanks Robert, I just booted it for the first time and so far so good. > I see > >> that there's still no ioctl for RS485 mode on the UARTs though. Is > there a > >> reason RS485 support isn't enabled on the BB kernel builds? > > > > There is no module for "rs485" you need to call the omap-serial driver > > with the proper ioctls > > > > > https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/Documentation/serial/serial-rs485.txt?id=refs/tags/v3.8.13 > > > Looks like you can enable it on boot time too.. > > https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/Documentation/devicetree/bindings/serial/rs485.txt?id=refs/tags/v3.8.13#n28 > > > 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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-16)
On Tue, Jan 21, 2014 at 2:33 PM, Robert Nelson wrote: > On Tue, Jan 21, 2014 at 2:14 PM, Alexander Hiam > wrote: >> Thanks Robert, I just booted it for the first time and so far so good. I see >> that there's still no ioctl for RS485 mode on the UARTs though. Is there a >> reason RS485 support isn't enabled on the BB kernel builds? > > There is no module for "rs485" you need to call the omap-serial driver > with the proper ioctls > > https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/Documentation/serial/serial-rs485.txt?id=refs/tags/v3.8.13 Looks like you can enable it on boot time too.. https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/Documentation/devicetree/bindings/serial/rs485.txt?id=refs/tags/v3.8.13#n28 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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-16)
On Tue, Jan 21, 2014 at 2:14 PM, Alexander Hiam wrote: > Thanks Robert, I just booted it for the first time and so far so good. I see > that there's still no ioctl for RS485 mode on the UARTs though. Is there a > reason RS485 support isn't enabled on the BB kernel builds? There is no module for "rs485" you need to call the omap-serial driver with the proper ioctls https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/Documentation/serial/serial-rs485.txt?id=refs/tags/v3.8.13 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/groups/opt_out.
[beagleboard] Re: debian: test images (2014-01-16)
Thanks Robert, I just booted it for the first time and so far so good. I see that there's still no ioctl for RS485 mode on the UARTs though. Is there a reason RS485 support isn't enabled on the BB kernel builds? -Alex On Thursday, January 16, 2014 4:42:34 PM UTC-5, RobertCNelson wrote: > > Thanks for everyone who tested 2014-01-10... So here we go, round two... > > First, for tracking please report all bugs to: > http://bugs.elinux.org/projects/debian-image-releases > > Fixes: > 3.8.13-bone35 -> 3.8.13-bone36 > * uvc camera backport > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8ca5d2d8e58df7235b77ed435e63c484e123fede > > * config sync with last Angstrom, missing a few modules, thumb2 enabled.. > > lxde: autostart of screensaver disabled (pegged cpu to 100%) > /opt/scripts/ now a git repo, easier to pull in board tweaks for > bootup scripts.. > * including a kernel update script under > /opt/scripts/tools/update_kernel.sh > Chromium updated to 32.0.1700.76 with webrtc enabled. > 4gb image, dropped from 3750Mb to 3700Mb, should work with more 4GB cards. > /var/lib/cloud9/node_modules/bonescript/ nodejs dependicy now installed > > Know Issues: > wicd: can only handle eth0 or wlan0, not both at the same time.. > > Questions? Should we switch to connman? > > To test: > apt-get remove wicd-* --purge > apt-get install connman > (no good gui with connman) > > Does your "cape" work? > > Does your wifi adapter work? Are we missing it's firmware? > > So go forward and test the first "beta" release. There are 3 files on > the web server, depending on what you want to do. Using the same > standard procedure found here: > http://elinux.org/Beagleboard:Updating_The_Software > > http://rcn-ee.net/deb/testing/2014-01-16/ > > 7cda65ef9971d8d770a84c00b8863c1e > BBB-eMMC-flasher-debian-7.3-2014-01-16-2gb.img.xz > c84011db191151986d14fe73e43f5f4d bone-debian-7.3-2014-01-16-4gb.img.xz > 05ed49c8fe4555081f83f5be61b2b75b debian-7.3-lxde-armhf-2014-01-16.tar.xz > > An eMMC "flasher" which can be installed to any 2GB or greater microSD > card. [BBB-eMMC-flasher-debian-7.3-2014-01-16-2gb.img.xz] > > > http://rcn-ee.net/deb/testing/2014-01-16/BBB-eMMC-flasher-debian-7.3-2014-01-16-2gb.img.xz > > > It takes about 10-15 Minutes to dd microSD (2GB), 15 minutes to flash > eMMC (look for full 4 LED's) > > 4GB standalone image that can be flashed to any 4GB or greater. > [bone-debian-7.3-2014-01-16-4gb.img.xz] > > > http://rcn-ee.net/deb/testing/2014-01-16/bone-debian-7.3-2014-01-16-4gb.img.xz > > > It takes about 20-30 Minutes to dd microSD (4GB) > > Finally one of my classic "setup_sdcard.sh". > [debian-7.3-console-armhf-2014-01-16.tar.xz] > > > http://rcn-ee.net/deb/testing/2014-01-16/debian-7.3-console-armhf-2014-01-16.tar.xz > > > Note for users who use my classic "setup_sdcard.sh" script, here is > the magic options to get the beaglebone project files + systemd. > > sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot bone > --beagleboard.org-production --enable-systemd > > To "rebuild" > git clone git://github.com/beagleboard/image-builder.git > cd image-builder > git checkout bb.org-v2014.01.16 -b tmp > ./beagleboard.org_image.sh > > Go Test! > > -- > 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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-16)
On Mon, Jan 20, 2014 at 12:43 PM, Robert Nelson wrote: > On Sun, Jan 19, 2014 at 12:01 AM, Mark Grosen wrote: > > * Add /sbin and /usr/sbin to the default PATH > > Are you thinking system-wide or just the first user? > > As i'm looking at /etc/profile > > if [ "`id -u`" -eq 0 ]; then > PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" > else > PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games" > fi > export PATH > > Thinking of using sed to change... > > from: > PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games" > to: > > PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games" > > I would make it system-wide. Given this is for embedded systems, I think any user is going to want access to the "if*" and "iw*" commands as well as i2c utilities (IMHO) > > * Enable the EXTRA_GROUPS options in /etc/adduser.conf and add i2c to the > > EXTRA_GROUPS > > Sounds good, added: > > https://github.com/beagleboard/image-builder/commit/47a74f654dddcf21e5327c76216b6a8bb6dfbcec > > Thanks! On a related note, it would be convenient if the spidev devices were in the same or similar group. > > * Add a way to identify the build version (or tell me how). I see > > /etc/os-release but it does not have a RCN build identifier in it > > I can't really touch /etc/os-release, as any stable update might blow > that away... > > But i set it up similar to Angstrom: > > debian@beaglebone:~$ cat /etc/dogtag > BeagleBoard.org BeagleBone Debian Image 2014-01-16 > Ooops, missed that one in my grep'ing around - just what I was looking for. Thanks. Mark > > 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/groups/opt_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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-16)
On Mon, Jan 20, 2014 at 7:39 PM, wrote: > On Thursday, January 16, 2014 4:42:34 PM UTC-5, RobertCNelson wrote: >> >> Know Issues: >> wicd: can only handle eth0 or wlan0, not both at the same time.. >> >> Questions? Should we switch to connman? > > > Yes. Definitely! I need both WLAN and ETH, also connman seems more > established. Finally, connman has better dbus integration for interface > configuration. Does the version of connman (1.15) we have in the repo right now work for the dual wlan/eth situation? apt-get remove wicd-* --purge apt-get install connman reboot 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/groups/opt_out.
[beagleboard] Re: debian: test images (2014-01-16)
On Thursday, January 16, 2014 4:42:34 PM UTC-5, RobertCNelson wrote: > > Know Issues: > wicd: can only handle eth0 or wlan0, not both at the same time.. > > Questions? Should we switch to connman? Yes. Definitely! I need both WLAN and ETH, also connman seems more established. Finally, connman has better dbus integration for interface configuration. Please switch! -W. -- 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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-16)
Also i've tried to run a QT5 Application on my BBB with the debian 16-01 image and i get this on dmesg: [ 1443.245075] idr_remove called for id=154920 which is not allocated. [ 1443.245197] [] (unwind_backtrace+0x1/0x8a) from [] (idr_remove+0xc5/0x120) [ 1443.245275] [] (idr_remove+0xc5/0x120) from [] (drm_ctxbitmap_free+0x1b/0x24) [ 1443.245334] [] (drm_ctxbitmap_free+0x1b/0x24) from [] (drm_rmctx+0x31/0xa0) [ 1443.245389] [] (drm_rmctx+0x31/0xa0) from [] (drm_ioctl+0x1d9/0x28a) [ 1443.245655] [] (drm_ioctl+0x1d9/0x28a) from [] (do_vfs_ioctl+0x3b9/0x402) [ 1443.245716] [] (do_vfs_ioctl+0x3b9/0x402) from [] (sys_ioctl+0x33/0x44) [ 1443.245777] [] (sys_ioctl+0x33/0x44) from [] (ret_fast_syscall+0x1/0x46) Is it related to the image? cheers On Mon, Jan 20, 2014 at 8:18 PM, André Prado wrote: > Hello Robert, > > Actually i am getting this on my BBB > > [ 35.411609] gen_ndis_query_resp: RNDIS_OID_GEN_RCV_NO_BUFFER > [ 35.415247] gadget: rndis reqa1.01 v i l4096 > [ 35.415517] gadget: rndis req21.00 v i l36 > [ 35.419242] gadget: rndis reqa1.01 v i l4096 > [ 35.419537] gadget: rndis req21.00 v i l36 > [ 35.424241] gadget: rndis reqa1.01 v i l4096 > [ 35.424513] gadget: rndis req21.00 v i l36 > [ 35.424593] gen_ndis_query_resp: RNDIS_OID_GEN_RCV_NO_BUFFER > [ 35.427242] gadget: rndis reqa1.01 v i l4096 > [ 35.427597] gadget: rndis req21.00 v i l36 > [ 35.431237] gadget: rndis reqa1.01 v i l4096 > [...] > [ 218.851550] gadget: rndis reqa1.01 v i l4096 > [ 226.351896] gadget: rndis req21.00 v i l12 > [ 226.355432] gadget: rndis reqa1.01 v i l4096 > [ 233.852707] gadget: rndis req21.00 v i l12 > [ 233.855267] gadget: rndis reqa1.01 v i l4096 > > > > My output for the xinput --list is this: > Unable to connect to X server > > I saw Mika's thread here on BB Groups and he played a little bit with the > touchscreen device driver, in order to play with it myself in your debian > distro what should i do? What are you using to build Debian? Yocto? > Buildroot? Could you give me a light? Hehe > > Thanks so much for your effort. > > > Cheers > > > > > > On Mon, Jan 20, 2014 at 6:51 PM, Robert Nelson wrote: > >> On Mon, Jan 20, 2014 at 7:06 AM, André Prado >> wrote: >> > Hello i've also flashed my BBB with the lastest Debian image and >> everything >> > is working fine. >> > >> > My LCD4 Cape from 4D Systems works "almost" fine, seems to have a >> glitch in >> > the touchscreen "click", it's probably callibration. >> >> Yeah, right now there is no calibration going on. I'm working on that >> this week, i just have the lcd3/lcd4 (and a newer lcd7 being shiped) >> >> With the 4D Systems, what is the output of: >> >> xinput --list >> >> 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/groups/opt_out. >> > > > > -- > Att > André > -- Att André -- 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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-16)
Hello Robert, Actually i am getting this on my BBB [ 35.411609] gen_ndis_query_resp: RNDIS_OID_GEN_RCV_NO_BUFFER [ 35.415247] gadget: rndis reqa1.01 v i l4096 [ 35.415517] gadget: rndis req21.00 v i l36 [ 35.419242] gadget: rndis reqa1.01 v i l4096 [ 35.419537] gadget: rndis req21.00 v i l36 [ 35.424241] gadget: rndis reqa1.01 v i l4096 [ 35.424513] gadget: rndis req21.00 v i l36 [ 35.424593] gen_ndis_query_resp: RNDIS_OID_GEN_RCV_NO_BUFFER [ 35.427242] gadget: rndis reqa1.01 v i l4096 [ 35.427597] gadget: rndis req21.00 v i l36 [ 35.431237] gadget: rndis reqa1.01 v i l4096 [...] [ 218.851550] gadget: rndis reqa1.01 v i l4096 [ 226.351896] gadget: rndis req21.00 v i l12 [ 226.355432] gadget: rndis reqa1.01 v i l4096 [ 233.852707] gadget: rndis req21.00 v i l12 [ 233.855267] gadget: rndis reqa1.01 v i l4096 My output for the xinput --list is this: Unable to connect to X server I saw Mika's thread here on BB Groups and he played a little bit with the touchscreen device driver, in order to play with it myself in your debian distro what should i do? What are you using to build Debian? Yocto? Buildroot? Could you give me a light? Hehe Thanks so much for your effort. Cheers On Mon, Jan 20, 2014 at 6:51 PM, Robert Nelson wrote: > On Mon, Jan 20, 2014 at 7:06 AM, André Prado > wrote: > > Hello i've also flashed my BBB with the lastest Debian image and > everything > > is working fine. > > > > My LCD4 Cape from 4D Systems works "almost" fine, seems to have a glitch > in > > the touchscreen "click", it's probably callibration. > > Yeah, right now there is no calibration going on. I'm working on that > this week, i just have the lcd3/lcd4 (and a newer lcd7 being shiped) > > With the 4D Systems, what is the output of: > > xinput --list > > 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/groups/opt_out. > -- Att André -- 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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-16)
On Mon, Jan 20, 2014 at 3:35 PM, Michael wrote: > Hi Robert, > > thanks for the quick response. I will give it a try. > >> I made the mistake of using "https://"; in the git clone, this broke both >> wheezy/jessie due to a missing ca certificate.. > > I "fixed" this temporary by adding "--no-check-certificate" behind the > "wget" commands in the script... An even better fix is to add "ca-certificates" by default. ;) Then it just works... 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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-16)
Hi Robert, thanks for the quick response. I will give it a try. I made the mistake of using "https://"; in the git clone, this broke both > wheezy/jessie due to a missing ca certificate.. I "fixed" this temporary by adding "--no-check-certificate" behind the "wget" commands in the script... Best regards, Michael Am Montag, 20. Januar 2014 22:20:54 UTC+1 schrieb RobertCNelson: > > On Mon, Jan 20, 2014 at 3:08 PM, Michael > > wrote: > > Hi Robert, > > > > many thanks for your work! > > > > I used the "setup_sdcard.sh" with > > "/rootfs/wheezy/debian-7.3-console-armhf-2014-01-17.tar.xz" and the boot > > time is reduced very much compared to the 2014-01-10 package (now only > about > > 10 seconds including Ethernet with systemd). > > Isn't systemd awesome for that! ;) > > > > > One thing: The "gadget"-drivers are not automatically loaded. I only can > > bring up everything with executing > > "/boot/uboot/tools/scripts/beaglebone-black-g-ether-load.sh" but I have > to > > do this after every start up. > > How can I enable this by default? > > Sorry the "2014-01-17" release is broken, so it became an un-release, > i'm waiting for my v3.13.0 release for the beagle/beagle-xm to finish > before i push out a good "2014-01-20/21".. > > It's easy to fix via, just > > sudo mkdir -p /opt/scripts/ > sudo chown -R debian:debian /opt/scripts/ > git clone git://github.com/RobertCNelson/boot-scripts /opt/scripts/ > > I made the mistake of using "https://"; in the git clone, this broke > both wheezy/jessie due to a missing ca certificate.. > > 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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-16)
On Mon, Jan 20, 2014 at 3:08 PM, Michael wrote: > Hi Robert, > > many thanks for your work! > > I used the "setup_sdcard.sh" with > "/rootfs/wheezy/debian-7.3-console-armhf-2014-01-17.tar.xz" and the boot > time is reduced very much compared to the 2014-01-10 package (now only about > 10 seconds including Ethernet with systemd). Isn't systemd awesome for that! ;) > > One thing: The "gadget"-drivers are not automatically loaded. I only can > bring up everything with executing > "/boot/uboot/tools/scripts/beaglebone-black-g-ether-load.sh" but I have to > do this after every start up. > How can I enable this by default? Sorry the "2014-01-17" release is broken, so it became an un-release, i'm waiting for my v3.13.0 release for the beagle/beagle-xm to finish before i push out a good "2014-01-20/21".. It's easy to fix via, just sudo mkdir -p /opt/scripts/ sudo chown -R debian:debian /opt/scripts/ git clone git://github.com/RobertCNelson/boot-scripts /opt/scripts/ I made the mistake of using "https://"; in the git clone, this broke both wheezy/jessie due to a missing ca certificate.. 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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-16)
Hi Robert, many thanks for your work! I used the "setup_sdcard.sh" with "/rootfs/wheezy/debian-7.3-console-armhf-2014-01-17.tar.xz" and the boot time is reduced very much compared to the 2014-01-10 package (now only about 10 seconds including Ethernet with systemd). One thing: The "gadget"-drivers are not automatically loaded. I only can bring up everything with executing "/boot/uboot/tools/scripts/beaglebone-black-g-ether-load.sh" but I have to do this after every start up. How can I enable this by default? Best regards, Michael Am Montag, 20. Januar 2014 21:51:09 UTC+1 schrieb RobertCNelson: > > On Mon, Jan 20, 2014 at 7:06 AM, André Prado > > > wrote: > > Hello i've also flashed my BBB with the lastest Debian image and > everything > > is working fine. > > > > My LCD4 Cape from 4D Systems works "almost" fine, seems to have a glitch > in > > the touchscreen "click", it's probably callibration. > > Yeah, right now there is no calibration going on. I'm working on that > this week, i just have the lcd3/lcd4 (and a newer lcd7 being shiped) > > With the 4D Systems, what is the output of: > > xinput --list > > 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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-16)
On Mon, Jan 20, 2014 at 7:06 AM, André Prado wrote: > Hello i've also flashed my BBB with the lastest Debian image and everything > is working fine. > > My LCD4 Cape from 4D Systems works "almost" fine, seems to have a glitch in > the touchscreen "click", it's probably callibration. Yeah, right now there is no calibration going on. I'm working on that this week, i just have the lcd3/lcd4 (and a newer lcd7 being shiped) With the 4D Systems, what is the output of: xinput --list 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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-16)
On Sat, Jan 18, 2014 at 5:35 AM, Alexandru Csete wrote: > > Hi Robert, > > Thanks for the updated images. I have tried them on Beaglebone black > (eMMC-flasher) and white (SD card) and both seem to run fine. > > > >> Questions? Should we switch to connman? >> >> To test: >> apt-get remove wicd-* --purge >> apt-get install connman >> (no good gui with connman) > > I prefer connman but as long as it is so easy to replace wicd with connman I > really don't mind. > > >> Does your "cape" work? > > My LCD3 Rev A2 cape works on Beaglebone Black (didn't try on white). > > My audio cape Rev A works (recognized, didn't try to play or record audio) > on both Beaglebone black and white but I noticed that HDMI audio disappears > from proc/asound/cards when this cape is mounted. This might be normal. > > DVI-D with Audio cape doesn't work on either Beaglebone black or white. To > be honest I'm not exactly sure if the cape works as I have got it second > hand and never tried it before. I think all the dvd-d's have a bad eeprom setup, as neither of my 2 auto-detect either.. Really need to set something up for them.. 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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-16)
On Sun, Jan 19, 2014 at 12:01 AM, Mark Grosen wrote: > Robert, > > I tried this new build on a BBB with good success. I used the > setup_sdcard.sh approach on an 8GB SD card. WiFi works with a cheapo > Rosewill USB dongle: > > [ 15.015308] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw.bin > [ 15.015468] usbcore: registered new interface driver rtl8192cu > > I am using the 3.13 kernel: > > Linux markbbb 3.13.0-rc8-bone4 #1 SMP Tue Jan 14 16:22:05 UTC 2014 armv7l > GNU/Linux > > I have an I2C 8x8 LED matrix scrolling continuously, so i2c is good. > > Running headless so no report on HDMI. > > A couple small requests/suggestions: > > * Add /sbin and /usr/sbin to the default PATH Are you thinking system-wide or just the first user? As i'm looking at /etc/profile if [ "`id -u`" -eq 0 ]; then PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" else PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games" fi export PATH Thinking of using sed to change... from: PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games" to: PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games" > * Enable the EXTRA_GROUPS options in /etc/adduser.conf and add i2c to the > EXTRA_GROUPS Sounds good, added: https://github.com/beagleboard/image-builder/commit/47a74f654dddcf21e5327c76216b6a8bb6dfbcec > * Add a way to identify the build version (or tell me how). I see > /etc/os-release but it does not have a RCN build identifier in it I can't really touch /etc/os-release, as any stable update might blow that away... But i set it up similar to Angstrom: debian@beaglebone:~$ cat /etc/dogtag BeagleBoard.org BeagleBone Debian Image 2014-01-16 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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-16)
Hello i've also flashed my BBB with the lastest Debian image and everything is working fine. My LCD4 Cape from 4D Systems works "almost" fine, seems to have a glitch in the touchscreen "click", it's probably callibration. On Sat, Jan 18, 2014 at 9:35 AM, Alexandru Csete wrote: > > Hi Robert, > > Thanks for the updated images. I have tried them on Beaglebone black > (eMMC-flasher) and white (SD card) and both seem to run fine. > > > > > Questions? Should we switch to connman? > > > > To test: > > apt-get remove wicd-* --purge > > apt-get install connman > > (no good gui with connman) > > I prefer connman but as long as it is so easy to replace wicd with connman > I really don't mind. > > > > Does your "cape" work? > > My LCD3 Rev A2 cape works on Beaglebone Black (didn't try on white). > > My audio cape Rev A works (recognized, didn't try to play or record audio) > on both Beaglebone black and white but I noticed that HDMI audio disappears > from proc/asound/cards when this cape is mounted. This might be normal. > > DVI-D with Audio cape doesn't work on either Beaglebone black or white. To > be honest I'm not exactly sure if the cape works as I have got it second > hand and never tried it before. > > Alex > > -- > 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/groups/opt_out. > -- Att André -- 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/groups/opt_out.
[beagleboard] Re: debian: test images (2014-01-16)
Hi Robert, Thanks for the updated images. I have tried them on Beaglebone black (eMMC-flasher) and white (SD card) and both seem to run fine. > Questions? Should we switch to connman? > > To test: > apt-get remove wicd-* --purge > apt-get install connman > (no good gui with connman) I prefer connman but as long as it is so easy to replace wicd with connman I really don't mind. > Does your "cape" work? My LCD3 Rev A2 cape works on Beaglebone Black (didn't try on white). My audio cape Rev A works (recognized, didn't try to play or record audio) on both Beaglebone black and white but I noticed that HDMI audio disappears from proc/asound/cards when this cape is mounted. This might be normal. DVI-D with Audio cape doesn't work on either Beaglebone black or white. To be honest I'm not exactly sure if the cape works as I have got it second hand and never tried it before. Alex -- 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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-16)
Robert, I tried this new build on a BBB with good success. I used the setup_sdcard.sh approach on an 8GB SD card. WiFi works with a cheapo Rosewill USB dongle: [ 15.015308] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw.bin [ 15.015468] usbcore: registered new interface driver rtl8192cu I am using the 3.13 kernel: Linux markbbb 3.13.0-rc8-bone4 #1 SMP Tue Jan 14 16:22:05 UTC 2014 armv7l GNU/Linux I have an I2C 8x8 LED matrix scrolling continuously, so i2c is good. Running headless so no report on HDMI. A couple small requests/suggestions: * Add /sbin and /usr/sbin to the default PATH * Enable the EXTRA_GROUPS options in /etc/adduser.conf and add i2c to the EXTRA_GROUPS * Add a way to identify the build version (or tell me how). I see /etc/os-release but it does not have a RCN build identifier in it Thanks much for your work on this. Mark On Thu, Jan 16, 2014 at 1:43 PM, Robert Nelson wrote: > On Thu, Jan 16, 2014 at 3:42 PM, Robert Nelson > wrote: > > Thanks for everyone who tested 2014-01-10... So here we go, round two... > > > > First, for tracking please report all bugs to: > > http://bugs.elinux.org/projects/debian-image-releases > > > > Fixes: > > 3.8.13-bone35 -> 3.8.13-bone36 > > * uvc camera backport > > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8ca5d2d8e58df7235b77ed435e63c484e123fede > > * config sync with last Angstrom, missing a few modules, thumb2 enabled.. > > > > lxde: autostart of screensaver disabled (pegged cpu to 100%) > > /opt/scripts/ now a git repo, easier to pull in board tweaks for > > bootup scripts.. > > * including a kernel update script under > /opt/scripts/tools/update_kernel.sh > > Chromium updated to 32.0.1700.76 with webrtc enabled. > > 4gb image, dropped from 3750Mb to 3700Mb, should work with more 4GB > cards. > > /var/lib/cloud9/node_modules/bonescript/ nodejs dependicy now installed > > > > Know Issues: > > wicd: can only handle eth0 or wlan0, not both at the same time.. > > > > Questions? Should we switch to connman? > > > > To test: > > apt-get remove wicd-* --purge > > apt-get install connman > > (no good gui with connman) > > > > Does your "cape" work? > > > > Does your wifi adapter work? Are we missing it's firmware? > > > > So go forward and test the first "beta" release. There are 3 files on > > the web server, depending on what you want to do. Using the same > > standard procedure found here: > > http://elinux.org/Beagleboard:Updating_The_Software > > > > http://rcn-ee.net/deb/testing/2014-01-16/ > > > > 7cda65ef9971d8d770a84c00b8863c1e > > BBB-eMMC-flasher-debian-7.3-2014-01-16-2gb.img.xz > > c84011db191151986d14fe73e43f5f4d bone-debian-7.3-2014-01-16-4gb.img.xz > > 05ed49c8fe4555081f83f5be61b2b75b debian-7.3-lxde-armhf-2014-01-16.tar.xz > > > > An eMMC "flasher" which can be installed to any 2GB or greater microSD > > card. [BBB-eMMC-flasher-debian-7.3-2014-01-16-2gb.img.xz] > > > > > http://rcn-ee.net/deb/testing/2014-01-16/BBB-eMMC-flasher-debian-7.3-2014-01-16-2gb.img.xz > > > > It takes about 10-15 Minutes to dd microSD (2GB), 15 minutes to flash > > eMMC (look for full 4 LED's) > > > > 4GB standalone image that can be flashed to any 4GB or greater. > > [bone-debian-7.3-2014-01-16-4gb.img.xz] > > > > > http://rcn-ee.net/deb/testing/2014-01-16/bone-debian-7.3-2014-01-16-4gb.img.xz > > > > It takes about 20-30 Minutes to dd microSD (4GB) > > > > Finally one of my classic "setup_sdcard.sh". > > [debian-7.3-console-armhf-2014-01-16.tar.xz] > > > > > http://rcn-ee.net/deb/testing/2014-01-16/debian-7.3-console-armhf-2014-01-16.tar.xz > > Doh! > > > http://rcn-ee.net/deb/testing/2014-01-16/debian-7.3-lxde-armhf-2014-01-16.tar.xz > > I'll get this form letter correct one of these weeks... > > 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/groups/opt_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/groups/opt_out.
[beagleboard] Re: debian: test images (2014-01-16)
On Thu, Jan 16, 2014 at 3:42 PM, Robert Nelson wrote: > Thanks for everyone who tested 2014-01-10... So here we go, round two... > > First, for tracking please report all bugs to: > http://bugs.elinux.org/projects/debian-image-releases > > Fixes: > 3.8.13-bone35 -> 3.8.13-bone36 > * uvc camera backport > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8ca5d2d8e58df7235b77ed435e63c484e123fede > * config sync with last Angstrom, missing a few modules, thumb2 enabled.. > > lxde: autostart of screensaver disabled (pegged cpu to 100%) > /opt/scripts/ now a git repo, easier to pull in board tweaks for > bootup scripts.. > * including a kernel update script under /opt/scripts/tools/update_kernel.sh > Chromium updated to 32.0.1700.76 with webrtc enabled. > 4gb image, dropped from 3750Mb to 3700Mb, should work with more 4GB cards. > /var/lib/cloud9/node_modules/bonescript/ nodejs dependicy now installed > > Know Issues: > wicd: can only handle eth0 or wlan0, not both at the same time.. > > Questions? Should we switch to connman? > > To test: > apt-get remove wicd-* --purge > apt-get install connman > (no good gui with connman) > > Does your "cape" work? > > Does your wifi adapter work? Are we missing it's firmware? > > So go forward and test the first "beta" release. There are 3 files on > the web server, depending on what you want to do. Using the same > standard procedure found here: > http://elinux.org/Beagleboard:Updating_The_Software > > http://rcn-ee.net/deb/testing/2014-01-16/ > > 7cda65ef9971d8d770a84c00b8863c1e > BBB-eMMC-flasher-debian-7.3-2014-01-16-2gb.img.xz > c84011db191151986d14fe73e43f5f4d bone-debian-7.3-2014-01-16-4gb.img.xz > 05ed49c8fe4555081f83f5be61b2b75b debian-7.3-lxde-armhf-2014-01-16.tar.xz > > An eMMC "flasher" which can be installed to any 2GB or greater microSD > card. [BBB-eMMC-flasher-debian-7.3-2014-01-16-2gb.img.xz] > > http://rcn-ee.net/deb/testing/2014-01-16/BBB-eMMC-flasher-debian-7.3-2014-01-16-2gb.img.xz > > It takes about 10-15 Minutes to dd microSD (2GB), 15 minutes to flash > eMMC (look for full 4 LED's) > > 4GB standalone image that can be flashed to any 4GB or greater. > [bone-debian-7.3-2014-01-16-4gb.img.xz] > > http://rcn-ee.net/deb/testing/2014-01-16/bone-debian-7.3-2014-01-16-4gb.img.xz > > It takes about 20-30 Minutes to dd microSD (4GB) > > Finally one of my classic "setup_sdcard.sh". > [debian-7.3-console-armhf-2014-01-16.tar.xz] > > http://rcn-ee.net/deb/testing/2014-01-16/debian-7.3-console-armhf-2014-01-16.tar.xz Doh! http://rcn-ee.net/deb/testing/2014-01-16/debian-7.3-lxde-armhf-2014-01-16.tar.xz I'll get this form letter correct one of these weeks... 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/groups/opt_out.
