debian testing: 2016-05-01

[Robert Nelson]

Howdy!

So there's a little something new in this week's snapshot:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2016-05-01

We've now switched from v4.1.x-ti to v4.4.x-ti by default.

hostap/wpasuppliant saw a major upgrade: 2.3 -> 2.5

Board specific documentation:

BBW/BBB = BeagleBoard.org documentation over usb flash

BBG = seeedstudio.com documentation over usb flash

bonescript 0.5.0-beta with more fixes

nodejs v0.12.x

Wireless AP by default:

SSID: BeagleBone (or) BeagleBone-WXYZ

PASS: BeagleBone

Regards,

--

Robert Nelson
https://rcn-ee.com/

[Rick Mann]

> On May 2, 2016, at 07:49 , Robert Nelson <robert...@gmail.com> wrote:
>
> So there's a little something new in this week's snapshot:
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2016-05-01
>
> We've now switched from v4.1.x-ti to v4.4.x-ti by default.

So, if I want to use PRUSS, I need to grab a -bone kernel, right?

> Wireless AP by default:

Ooh!


--
Rick Mann
rm...@latencyzero.com

[Jason Kridner]

On Mon, May 2, 2016 at 10:50 AM Robert Nelson <robert...@gmail.com> wrote:

Howdy!

So there's a little something new in this week's snapshot:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2016-05-01

We've now switched from v4.1.x-ti to v4.4.x-ti by default.

With 4.4, should we be enabling -rt?

 

hostap/wpasuppliant saw a major upgrade: 2.3 -> 2.5

Does this image include the WL183x patches from TI?

 

Board specific documentation:

BBW/BBB = BeagleBoard.org documentation over usb flash

BBG = seeedstudio.com documentation over usb flash

bonescript 0.5.0-beta with more fixes

I'm assuming beta4. I'll try to get the fix in if using the old cape manager to continue using the old functions. All should be working better for the newer kernels.

 

nodejs v0.12.x

Wireless AP by default:

SSID: BeagleBone (or) BeagleBone-WXYZ

When would you not have the -WXYZ?

 

PASS: BeagleBone

Can you summarize connman vs. other configs for the various network connections?

 

Regards,

--

Robert Nelson
https://rcn-ee.com/

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

[Jason Kridner]

On Mon, May 2, 2016 at 3:52 PM Rick Mann <rm...@latencyzero.com> wrote:

> On May 2, 2016, at 07:49 , Robert Nelson <robert...@gmail.com> wrote:
>
> So there's a little something new in this week's snapshot:
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2016-05-01
>
> We've now switched from v4.1.x-ti to v4.4.x-ti by default.

So, if I want to use PRUSS, I need to grab a -bone kernel, right?

If using remoteproc, the -ti kernel should be OK. If you need uio_pruss, then I think you still need -bone. Not sure if there is progress on making this device tree adjustable.

 

> Wireless AP by default:

Ooh!


--
Rick Mann
rm...@latencyzero.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/35D3AB97-FBA4-4EC3-A165-39C2A4E612F0%40latencyzero.com.

[Rick Mann]

> On May 2, 2016, at 13:14 , Jason Kridner <jkri...@beagleboard.org> wrote:
>
>
>
> On Mon, May 2, 2016 at 3:52 PM Rick Mann <rm...@latencyzero.com> wrote:
>
> > On May 2, 2016, at 07:49 , Robert Nelson <robert...@gmail.com> wrote:
> >
> > So there's a little something new in this week's snapshot:
> >
> > http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2016-05-01
> >
> > We've now switched from v4.1.x-ti to v4.4.x-ti by default.
>
> So, if I want to use PRUSS, I need to grab a -bone kernel, right?
>
> If using remoteproc, the -ti kernel should be OK. If you need uio_pruss, then I think you still need -bone. Not sure if there is progress on making this device tree adjustable.

Yeah, sorry. By PRUSS I meant uio_pruss. I depend on a third-party lib that uses that and isn't like to be updated any time soon. I don't have time to learn how to update it right now, given all the other things I have to finish on this project.

--
Rick Mann
rm...@latencyzero.com

[Robert Nelson]

Hi Rick,

by default v4.4.x-ti  (and the rt) will use remoteproc_pruss...

For uio_pruss:

cd /opt/scripts/tools/
git pull
sudo ./update_kernel.sh <OPTIONS>

Mainline (4.1.x lts)[edit]

4.1.x BeagleBone/BeagleBone Black
--bone-kernel --lts-4_1

4.1.x BeagleBone/BeagleBone Black + RT
--bone-rt-kernel --lts-4_1

Mainline (4.4.x lts)[edit]

4.4.x BeagleBone/BeagleBone Black
--bone-kernel --lts-4_4

4.4.x BeagleBone/BeagleBone Black + RT
--bone-rt-kernel --lts-4_4

Regards, 

[Rick Mann]

Thanks, Robert. Is that better than just apt-getting a particular kernel? I guess it's a bit easier, and always pulls down the latest?


--
Rick Mann
rm...@latencyzero.com

[Robert Nelson]

On Mon, May 2, 2016 at 3:11 PM, Jason Kridner <jkri...@gmail.com> wrote:

On Mon, May 2, 2016 at 10:50 AM Robert Nelson <robert...@gmail.com> wrote:

Howdy!

So there's a little something new in this week's snapshot:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2016-05-01

We've now switched from v4.1.x-ti to v4.4.x-ti by default.

With 4.4, should we be enabling -rt?

Good point, we were going to try that again, just did:

   25  cd /opt/scripts/tools/

   26  git pull

   27  sudo ./update_kernel.sh --ti-rt-channel --lts-4_4

debian@beaglebone:~$ uname -r

4.4.8-ti-rt-r22

So far, usb networking/flash/serial seem to work fine on my linux box.. (with 4.1.x-rt serial would fail).. I'll test windows 10 in a bit..

NM... it just hardlocked while typing this email... back to non-rt and more testing. ;)

 

 

hostap/wpasuppliant saw a major upgrade: 2.3 -> 2.5

Does this image include the WL183x patches from TI?

Nope, not yet..  I'm watching this tree for patches:

http://git.ti.com/gitweb/?p=wilink8-wlan/hostap.git;a=summary

R8.7_RC14 just showed up a little bit ago..

 

 

Board specific documentation:

BBW/BBB = BeagleBoard.org documentation over usb flash

BBG = seeedstudio.com documentation over usb flash

bonescript 0.5.0-beta with more fixes

I'm assuming beta4. I'll try to get the fix in if using the old cape manager to continue using the old functions. All should be working better for the newer kernels.

Correct beta4, but i need to fix

[   22.276862] bone_capemgr bone_capemgr: part_number 'univ-emmc', version 'N/A'

[   22.276896] bone_capemgr bone_capemgr: slot #4: override

[   22.276911] bone_capemgr bone_capemgr: Using override eeprom data at slot 4

[   22.276927] bone_capemgr bone_capemgr: slot #4: 'Override Board Name,00A0,Override Manuf,univ-emmc'

[   22.464473] of_resolve_phandles: Could not find symbol 'pruss'

[   22.470418] bone_capemgr bone_capemgr: slot #4: Failed to resolve tree

and stick a pruss node in the default dtb to make things happy for cape-universal...

 

 

nodejs v0.12.x

Wireless AP by default:

SSID: BeagleBone (or) BeagleBone-WXYZ

When would you not have the -WXYZ?

On initial first bootup.  Connman is so fast, wifi is already up before our boot script has time to generate the ssh key's..  After our key's are generated the ssid get's changed..

And on the x15, when you stick a usb wifi adapter is shows "BeagleBone".. ;)

 

 

PASS: BeagleBone

Can you summarize connman vs. other configs for the various network connections?

Connman is used by default for:

eth0/wlan0

/etc/network/interfaces is ignored except for the the usb0 values which are used by the boot script to setup the usb0 network...

*Connman could be used for usb0, but there is no way to reserve "192.168.7.2"...

Regards,

[Robert Nelson]

Eh, it's the same, as it also calls apt.. It just looks at these references for the latest of each branch:

https://rcn-ee.net/repos/latest/jessie-armhf/

Regards,

[Robert Nelson]

r23 fixes this with a quick hack.. (remoteproc_pruss hasn't been merged in ti's v4.4.x as of today yet..) SO the cape-universal overlay will load..

Regards,

[William Hermans]

Robert,

Nodejs 4.x is possible on these images yet ?

I was considering getting a Jessie image and backing out of systemd, then attempting to install Nodejs 4.x lts on it.

 However if these images are not yet capable of Nodejs 4.x . . . then moving onward to a jessie image does not make so much sense for us.

--

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYiArySkARUbwFkqFmoQcs-vPgnu6beoJYDLKCSEq_vGjg%40mail.gmail.com.

[William Hermans]

By "installling" I mean I'll be compiling my own Nodejs 4.x from source, and creating a package.

[Robert Nelson]

On Mon, May 2, 2016 at 7:49 PM, William Hermans <yyr...@gmail.com> wrote:

By "installling" I mean I'll be compiling my own Nodejs 4.x from source, and creating a package.

There's only one deb* package in the base install that can't handle nodejs v4.x.

bb-bonescript-installer-beta

remove that, then just change:

 /etc/apt/sources.list

deb https://deb.nodesource.com/node_0.12 jessie main

#deb-src https://deb.nodesource.com/node_0.12 jessie main

to

deb https://deb.nodesource.com/node_4.x jessie main

#deb-src https://deb.nodesource.com/node_4.x jessie main

then

apt-get update ; apt-get upgrade

* v4.x fixes:

spi: https://github.com/jadonk/bonescript/pull/126

i2c: something like:

https://github.com/RobertCNelson/bonescript/commit/4a3027d846f4350c7840030d8d9a6872f84da037

i2c was used in ii2.js so that needs to be rewritten...

Regards,

[William Hermans]

Thanks Robert.

I probably would not need  SPI or I2C, as I'd implement my own library. Which is really very easy, as nodejs has a filesystem class object.

I'll give this a go later as we're busy out doors taking care of spring things today . . .

--

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYhFQOWVKOixHZDCbEOasms3yxXCtNWDRwGbdt_QHgVnmg%40mail.gmail.com.

[Wally Bkg]

Happy to report that this is the first image in a while that has booted correctly on my A5A BBB with the USB "gadget" Ethernet.   I'm concerned my particular board has USB hardware issues, but that is a problem for another day.

The START.htm link worked, the simple flash the LEDs bonescript button on the bonescript101 page worked, and cloud9 webpage launched.  Node-red seems to work, but still no nod-red-node-beaglebone.  These "extra" nodes would seem to be really welcome by newbies.

But, when I tried the fade.js example in cloud9 I got an error:

ocp:P9_14_pinmux was not found under /sys/devices/platform/ocp

While I'm helping my newbie friend,  I've kind of taken on a role as newbie "out of the box" experience QA/QC tester.

If you don't want this feedback, I'll stop posting about it.

I only need one working system for him (and a clone of it for me), the BBG with lxqt image 2016-04-03 and all upgrades and a few fixes from this forum seems more than good enough at this point.

Down the road I'd like to use this old BBB for a PRU project, but I'm a long way from being ready to start on this, maybe by then things will have settled down to one "best supported" way to use the PRU, all this remoteproc vs. uio_pruss makes my head spin, but if I had to choose at the moment I'd pick uio_pruss based on what I've found out so far.

[William Hermans]

So far the image seems good, but perhaps a little large for a console image.

william@beaglebone:~$ sudo df -h /
Filesystem      Size  Used Avail Use% Mounted on
/dev/mmcblk0p1  1.7G  319M  1.2G  21% /

This is with systemd ripped out and sysv in place. So maybe a bit of stuff that is no longer needed.

One thing I will complain about though. I do not like all the http redirects in the apt repo's file. Firstly, because I have no idea what that is an alias for, and secondly, I'd prefer to keep everything stock. At minimum, using redirects is not stock. Regardless where they point to. At least security updates are stock, otherwise I would not be so polite here ;)

So far so good though, and Robert, I will attempt to pull in my own sources for Nodejs 4.2.x, and compile like I normally do. I guess I'll find out first hand whether that will work or not. Meaning, I wont pull the source in from the debian repo's I'll get them directly from Nodejs's git . . .

 

--

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/61404e99-cbd0-41d5-bd33-33e153853dbf%40googlegroups.com.

[Robert Nelson]

On Wed, May 4, 2016 at 2:56 PM, William Hermans <yyr...@gmail.com> wrote:

So far the image seems good, but perhaps a little large for a console image.

william@beaglebone:~$ sudo df -h /
Filesystem      Size  Used Avail Use% Mounted on
/dev/mmcblk0p1  1.7G  319M  1.2G  21% /

This is with systemd ripped out and sysv in place. So maybe a bit of stuff that is no longer needed.

One thing I will complain about though. I do not like all the http redirects in the apt repo's file. Firstly, because I have no idea what that is an alias for, and secondly, I'd prefer to keep everything stock. At minimum, using redirects is not stock. Regardless where they point to. At least security updates are stock, otherwise I would not be so polite here ;)

Here is the details:

http://httpredir.debian.org/

based on your ip, it "could" find a faster connection.

For users in Europe it's been a big help..

So far so good though, and Robert, I will attempt to pull in my own sources for Nodejs 4.2.x, and compile like I normally do. I guess I'll find out first hand whether that will work or not. Meaning, I wont pull the source in from the debian repo's I'll get them directly from Nodejs's git . . .

Regards,

[Robert Nelson]

On Wed, May 4, 2016 at 10:39 AM, Wally Bkg <wb666...@gmail.com> wrote:

Happy to report that this is the first image in a while that has booted correctly on my A5A BBB with the USB "gadget" Ethernet.   I'm concerned my particular board has USB hardware issues, but that is a problem for another day.

The START.htm link worked, the simple flash the LEDs bonescript button on the bonescript101 page worked, and cloud9 webpage launched.  Node-red seems to work, but still no nod-red-node-beaglebone.  These "extra" nodes would seem to be really welcome by newbies.

But, when I tried the fade.js example in cloud9 I got an error:

ocp:P9_14_pinmux was not found under /sys/devices/platform/ocp

Yeah, anything talking via pwm to pins needs some patches..

https://github.com/derekmolloy/boneDeviceTree/blob/master/docs/BeagleboneBlackP9HeaderTable.pdf

 

While I'm helping my newbie friend,  I've kind of taken on a role as newbie "out of the box" experience QA/QC tester.

If you don't want this feedback, I'll stop posting about it.

I only need one working system for him (and a clone of it for me), the BBG with lxqt image 2016-04-03 and all upgrades and a few fixes from this forum seems more than good enough at this point.

Down the road I'd like to use this old BBB for a PRU project, but I'm a long way from being ready to start on this, maybe by then things will have settled down to one "best supported" way to use the PRU, all this remoteproc vs. uio_pruss makes my head spin, but if I had to choose at the moment I'd pick uio_pruss based on what I've found out so far.

Regards,

[Robert Nelson]

On Wed, May 4, 2016 at 3:22 PM, Robert Nelson <robert...@gmail.com> wrote:

On Wed, May 4, 2016 at 2:56 PM, William Hermans <yyr...@gmail.com> wrote:

So far the image seems good, but perhaps a little large for a console image.

william@beaglebone:~$ sudo df -h /
Filesystem      Size  Used Avail Use% Mounted on
/dev/mmcblk0p1  1.7G  319M  1.2G  21% /

This is with systemd ripped out and sysv in place. So maybe a bit of stuff that is no longer needed.

One thing I will complain about though. I do not like all the http redirects in the apt repo's file. Firstly, because I have no idea what that is an alias for, and secondly, I'd prefer to keep everything stock. At minimum, using redirects is not stock. Regardless where they point to. At least security updates are stock, otherwise I would not be so polite here ;)

Here is the details:

http://httpredir.debian.org/

based on your ip, it "could" find a faster connection.

For users in Europe it's been a big help..

Blah...

https://lists.debian.org/debian-project/2016/04/msg00012.html

When there is a response - and there isn't always - it's usually "nobody
currently maintains httpredir, sorry".

So, it appears as if currently nobody has time or the energy to take
care of httpredir.debian.org properly.

https://lists.debian.org/debian-project/2016/04/msg00018.html

So it was good for a year...

https://lists.debian.org/debian-devel-announce/2015/05/msg00003.html

yuck..

Regards,

[William Hermans]

Here is the details:

http://httpredir.debian.org/

based on your ip, it "could" find a faster connection.

For users in Europe it's been a big help..

Ah, ok so something new in the "debian way" world. 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...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYhDm6FV9WxvQJ3%2ByHsJEoRTt3TE9SWP668BpKKp6_w5pA%40mail.gmail.com.

[William Hermans]

Blah...

https://lists.debian.org/debian-project/2016/04/msg00012.html

When there is a response - and there isn't always - it's usually "nobody
currently maintains httpredir, sorry".

So, it appears as if currently nobody has time or the energy to take
care of httpredir.debian.org properly.

https://lists.debian.org/debian-project/2016/04/msg00018.html

So it was good for a year...

https://lists.debian.org/debian-devel-announce/2015/05/msg00003.html

yuck..

Regards,

 Heh, this is why I do not like non standard stuff . . .funny this sort of thing happens very rarely though . . .

--

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYjsmRmAxvQLk%2BmPe_09mZuzTk5%2B%3Dhn6%2BvRi9-3_4OJB8g%40mail.gmail.com.

[William Hermans]

So I'm, prepping to make my own "production" image; prior to installing a ton of development tools, and figured I'd point a few things out. Most this is for Robert when he gets around to worrying about all this, if it all. But there is nothing stopping anyone else form using this information.

Trim out uneeded cruft:

william@beaglebone:~$ sudo apt-get install ncdu
william@beaglebone:~$ cd /

william@beaglebone:/$ sudo ncdu

. . . And then navigate around in ncdu to find uneeded large files, and directories.

A 24Megabyte file ?!
22.4MiB [##########]  libicudata.so.52.1

william@beaglebone:/$ sudo apt-get remove libicu52
. . .
After this operation, 28.9 MB disk space will be freed.
Do you want to continue? [Y/n]

william@beaglebone:/$ sudo apt-get purge --auto-remove libicu52

--- /usr/share --------------------------------------------------------------------------------------------------------
                        /..
   36.6MiB [##########] /locale
   15.2MiB [####      ] /doc
    7.2MiB [#         ] /man

--- /lib --------------------------------------------------------------------------------------------------------------
                        /..
   68.4MiB [##########] /modules

--- /var/cache --------------------------------------------------------------------------------------------------------
                        /..
   40.5MiB [##########] /apt
 

A lot of cruft in these 3 locations. Much, of it can be removed, but must be careful what you remove in /lib/modules. If you do not know what to remove, then do not touch anything . . .

[William Hermans]

@Robert,

/lib/firmware no longer exists ?

[Robert Nelson]

On Wed, May 4, 2016 at 6:04 PM, William Hermans <yyr...@gmail.com> wrote:

@Robert,

/lib/firmware no longer exists ?

I'm guessing you have the "console" image?

Correct, it's pretty empty..

(no firmware is required to "flash" the eMMC, that's the console's main requirement)

Regards,

[William Hermans]

I'm guessing you have the "console" image?

Correct, it's pretty empty..

(no firmware is required to "flash" the eMMC, that's the console's main requirement)

Regards,

So if i want to use this as a production image i need to mkdir /lib/firmware/ and then bb.org-overlay git, install and all that ? I really do not want the IoT image . . . I did not check it at all, but I'm sure it's full of stuff I'd never use.

--

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYhi5tgpLOmixjB5_fVCZHi_%2BTvWmk2dDSvqt3M%2BcCm2XQ%40mail.gmail.com.

[Robert Nelson]

On Wed, May 4, 2016 at 6:12 PM, William Hermans <yyr...@gmail.com> wrote:

I'm guessing you have the "console" image?

Correct, it's pretty empty..

(no firmware is required to "flash" the eMMC, that's the console's main requirement)

Regards,

So if i want to use this as a production image i need to mkdir /lib/firmware/ and then bb.org-overlay git, install and all that ? I really do not want the IoT image . . . I did not check it at all, but I'm sure it's full of stuff I'd never use.

What you saying, i need to package bb.org-overlay.. ;)

sudo apt-get install git-core device-tree-compiler build-essential

git clone https://github.com/beagleboard/bb.org-overlays
cd ./bb.org-overlays

./install.sh

[William Hermans]

bone-debian-8.4-console-armhf-2016-05-01-2gb.img.xz

Is the image I have. Supposed to be the standalone sdcard image.

What you saying, i need to package bb.org-overlay.. ;)

sudo apt-get install git-core device-tree-compiler build-essential

git clone https://github.com/beagleboard/bb.org-overlays
cd ./bb.org-overlays

./install.sh

No, what I'm saying is that we( I ) Just had a major version change, and something that used to be in place, is no longer in place. It's confusing. All I really need to know is *if* I want use overlays, where do they go, and I believe you just answered my question. Which is pretty much exactly like upgrading from 3.8.x( for me ), except /lib/firmware needs to be created.

Debian's "Firmware" page seemed to indicate that also, but you know how doc's can be sometimes.

--

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYh_5uognX%3DnQtYwJeVcQBLfmrJakBooKH9Qor_K7bxo%2BA%40mail.gmail.com.

[Robert Nelson]

On Wed, May 4, 2016 at 6:22 PM, William Hermans <yyr...@gmail.com> wrote:

bone-debian-8.4-console-armhf-2016-05-01-2gb.img.xz

Is the image I have. Supposed to be the standalone sdcard image.

What you saying, i need to package bb.org-overlay.. ;)

sudo apt-get install git-core device-tree-compiler build-essential

git clone https://github.com/beagleboard/bb.org-overlays
cd ./bb.org-overlays

./install.sh

No, what I'm saying is that we( I ) Just had a major version change, and something that used to be in place, is no longer in place. It's confusing. All I really need to know is *if* I want use overlays, where do they go, and I believe you just answered my question. Which is pretty much exactly like upgrading from 3.8.x( for me ), except /lib/firmware needs to be created.

Debian's "Firmware" page seemed to indicate that also, but you know how doc's can be sometimes.

both the iot & lxqt images ship those.

The console does not..  (right now it would have to include git-core/device-tree-compiler/build-essentials) which just add more weight..

Regards,

[William Hermans]

both the iot & lxqt images ship those.

The console does not..  (right now it would have to include git-core/device-tree-compiler/build-essentials) which just add more weight..

Regards,

--

Robert Nelson
https://rcn-ee.com

So question. Would precompiling the device tree binaries, then creating /lib/firmware, and placing the binaries in that directory not work ? No this is not a smart ass question - But I do think it would work, just not sure why it's not being done already.

As far as adding weight, I totally get it. Jessie seems to be heavier by nature because . . .
william@beaglebone:~$ cd /usr/share/locale/
william@beaglebone:/usr/share/locale$ sudo rm -r uk fr cs pl de vi nl sv ru es ja da it zh_CN ca hu tr eo id sl pt_BR bg fi sk pt
william@beaglebone:/usr/share/locale$ cd ../doc
william@beaglebone:/usr/share/doc$ sudo rm -r ./*
william@beaglebone:/usr/share/locale$ cd ../man/
william@beaglebone:/usr/share/man$ sudo rm -r ./*

Only netted me around 50MB. Image is still at 242MB, and it's getting pretty close to being as lean as I'd want it to be. Well I could gain another 40M from apt cache, and perhaps 40M from removing modules . . . But that's still 160M in size .  . . way larger than Wheezy.

Anyway, do I need you to package anything up for me ? No . . . I just wanted to make sure /lib/firmware was still correct for Jessie. Especially since I've ripped out systemd, and was unsure if there was another mechanism for device tree overlays, or not.

--

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYg8DxgUU-R-cYTj93zHP8cZ1Gy6S_g10tn8GM9c7T9GWQ%40mail.gmail.com.

[Robert Nelson]

On Wed, May 4, 2016 at 6:40 PM, William Hermans <yyr...@gmail.com> wrote:

both the iot & lxqt images ship those.

The console does not..  (right now it would have to include git-core/device-tree-compiler/build-essentials) which just add more weight..

Regards,

--

Robert Nelson
https://rcn-ee.com

So question. Would precompiling the device tree binaries, then creating /lib/firmware, and placing the binaries in that directory not work ? No this is not a smart ass question - But I do think it would work, just not sure why it's not being done already.

Correct, that's one reason why the shipped "./dtc-overlay.sh" is in the repo, so you can build the cross-dtc. 

 

As far as adding weight, I totally get it. Jessie seems to be heavier by nature because . . .
william@beaglebone:~$ cd /usr/share/locale/
william@beaglebone:/usr/share/locale$ sudo rm -r uk fr cs pl de vi nl sv ru es ja da it zh_CN ca hu tr eo id sl pt_BR bg fi sk pt
william@beaglebone:/usr/share/locale$ cd ../doc
william@beaglebone:/usr/share/doc$ sudo rm -r ./*
william@beaglebone:/usr/share/locale$ cd ../man/
william@beaglebone:/usr/share/man$ sudo rm -r ./*

Only netted me around 50MB. Image is still at 242MB, and it's getting pretty close to being as lean as I'd want it to be. Well I could gain another 40M from apt cache, and perhaps 40M from removing modules . . . But that's still 160M in size .  . . way larger than Wheezy.

DEBUG_INFO is enabled by default with the kernel now, so the modules are bigger..

Anyway, do I need you to package anything up for me ? No . . . I just wanted to make sure /lib/firmware was still correct for Jessie. Especially since I've ripped out systemd, and was unsure if there was another mechanism for device tree overlays, or not.

rsync/patch has a few dependices cut them out..

 

Regards,

[William Hermans]

rsync/patch has a few dependices cut them out..

I'm not sure what you mean, but if you mean systemd deps . . . this how is how removed systemd. Pretty much like http://without-systemd.org/wiki/index.php/How_to_remove_systemd_from_a_Debian_jessie/sid_installation but slightly modified.

william@beaglebone:~$ sudo apt-get update
william@beaglebone:~$ sudo apt-get install sysvinit-core sysvinit-utils
william@beaglebone:~$ sudo cp /usr/share/sysvinit/inittab /etc/inittab

william@beaglebone:~$ sudo su
root@beaglebone:/home/william# echo -e 'Package: systemd\nPin: release *\nPin-Priority: -1' > /etc/apt/preferences.d/systemd
root@beaglebone:/home/william# echo -e '\n\nPackage: *systemd*\nPin: release *\nPin-Priority: -1' >> /etc/apt/preferences.d/systemd
root@beaglebone:/home/william# reboot

william@eee-pc:~$ ssh william@bbb
william@beaglebone:~$ sudo apt-get remove --purge --auto-remove systemd

--

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYghr%2Bmcjuhm3_BMedj%2BqbpJ3QTD7%2BfHCKzXoEntcfY4cA%40mail.gmail.com.

[Robert Nelson]

On Wed, May 4, 2016 at 6:54 PM, William Hermans <yyr...@gmail.com> wrote:

rsync/patch has a few dependices cut them out..

I'm not sure what you mean, but if you mean systemd deps . . . this how is how removed systemd. Pretty much like http://without-systemd.org/wiki/index.php/How_to_remove_systemd_from_a_Debian_jessie/sid_installation but slightly modified.

no if you remove rsync and patch, that will allow you to remove a few more large dependices..

Regards,

[William Hermans]

no if you remove rsync and patch, that will allow you to remove a few more large dependices..

Regards,

Ah, ok thanks :) Not sure I'll need either on the development image, but I may as well remove them now and reinstall later if needed.

--

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYiTUQomnzFXRzv1svrODDm7QDHNc%3D5NHy7vFpHZ63b6bQ%40mail.gmail.com.

[William Hermans]

william@beaglebone:~$ sudo apt-get remove --purge --auto-remove rsync patch
[sudo] password for william:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  patch* rsync*
0 upgraded, 0 newly installed, 2 to remove and 2 not upgraded.
After this operation, 809 kB disk space will be freed.

Well, maybe not so large ;)

[Robert Nelson]

On Wed, May 4, 2016 at 7:03 PM, William Hermans <yyr...@gmail.com> wrote:

william@beaglebone:~$ sudo apt-get remove --purge --auto-remove rsync patch
[sudo] password for william:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  patch* rsync*
0 upgraded, 0 newly installed, 2 to remove and 2 not upgraded.
After this operation, 809 kB disk space will be freed.

Well, maybe not so large ;)

humm, thought they pulled in python-minimal, guess not..

Regards,

[William Hermans]

Anyway, yeah I do appreciate it Robert, but that one thing just didn't pan out heh. In the end, I do like to have as small an image as possible, but it only matters to a point. Meaning, I'll try, and perhaps even try too hard to get my image small, but it's not super important once I'm feeling pretty good about not having too much dead weight around. 242M is really not all that large, and it'll get bigger too once I have Nodejs compiled and installed. I think ~400M-500M would still be a pretty deal.

--

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYhPy6vxTFwoor4%3D4U429R4it69xbGgA3fCn8O8yDZK7yQ%40mail.gmail.com.

[Wally Bkg]

FYI.

On the my BBB with the 2016-05-01 lxqt testing image

I'd not apt-get installed anything.

I did: 

sudo apt-get update

sudo apt-get upgrade

There were 5 packages to be upgraded:

bb-bonescript-installer-beta c9-core-installer libssl1.0.0 openssl rcnee-access-point

The bb-bonescript-installer-beta upgrade failed.

Killed appeared after the line CXX(target) Release/obj.target/.../epoll.o

[Robert Nelson]

Fire up memtester on your board:

debian@beaglebone:~$ sudo memtester 200

memtester version 4.3.0 (32-bit)

Copyright (C) 2001-2012 Charles Cazabon.

Licensed under the GNU General Public License version 2 (only).

pagesize is 4096

pagesizemask is 0xfffff000

want 200MB (209715200 bytes)

got  200MB (209715200 bytes), trying mlock ...locked.

Loop 1:

Regards,

[Wally Bkg]

Its been running for several hours and has completed four loops, I'll leave it running overnight and follow-up if it prints anything but "OK",

However, at this point  it doesn't look like this is the problem.

Something seems rotten in apt-get land.

[William Hermans]

Well . . . I'm in the middle (  or something ) of compiling Node 4.2.6 from Node.org sources . . . so far so good, but it's been compiling for the last 2-3 hours . . .

In the mean time I'm dorking around with the rpi3 that came in today, and seriously considering using it as an armv7 build system. I'm still not fond of the original rpi's but these things have some serious spunk. Still I'm a bit miffed that it seems we're forced to use "raspbian". The main contention, how does one load the needed board files, etc . . .

Did i ever mention I hate non standard things ? Particularly Debian . . .

--

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/0ba44f13-079a-4bb2-a700-cad3a034c12b%40googlegroups.com.

[William Hermans]

Err, that should read: Particularly non standard Debian. Debian is fine( great ), until people start screwing around it . . .

[William Hermans]

william@beaglebone:~/node$ wget http://nodejs.org/dist/v4.2.6/node-v4.2.6.tar.gz
william@beaglebone:~/node$ tar xzvf node-v4.2.6.tar.gz
william@beaglebone:~/node$ cd node-v4.2.6
william@beaglebone:~/node/node-v4.2.6$ ./configure --without-snapshot
william@beaglebone:~/node/node-v4.2.6$ make
william@beaglebone:~/node/node-v4.2.6$ ./node -e 'console.log("Testing . . .");'
Testing . . .
william@beaglebone:~/node/node-v4.2.6$ ./node -v
v4.2.6
william@beaglebone:~/node/node-v4.2.6$ uname -a
Linux beaglebone 4.4.8-ti-r22 #1 SMP Wed Apr 27 22:23:10 UTC 2016 armv7l GNU/Linux

[William Hermans]

Arrrr . . . depends . . .

$ sudo apt-get install build-essential automake autoconf libtool pkg-config libcurl4-openssl-dev intltool libxml2-dev libgtk2.0-dev libnotify-dev libglib2.0-dev libevent-dev libssl-dev checkinstall python wget

[Rick Mann]

Is gtk required? What if I'm just making a server with no display?

> To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORp-oUKGYASMF29UNHGtS7gV9CRy%2BnqY0Nsii7b-oc_5pQ%40mail.gmail.com.

> For more options, visit https://groups.google.com/d/optout.

--
Rick Mann
rm...@latencyzero.com

[William Hermans]

No Rick gtk is not required. Most of these dependencies came directly off the Nodejs github readme.md

 for Nodejs v0.10.35, and I have not changed these dependencies in my notes since ( around 2 years ago or whatever ).

Anyway, if you look at the list of actual packages required by my small list here, and you start seeing all kinds of garbage like xwindows stuff, etc. You realize that package maintainers are either delinquent in maintaining a proper dependency list, *OR* these maintainers actually use these libraries because they already know them.

Anyway, this was compiled on a console image that started out at just under 200M in size. ssh . . .

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CFB4BBFC-4740-4646-9673-A5C6F719A46C%40latencyzero.com.

[William Hermans]

william@beaglebone:~$ df -h /

Filesystem      Size  Used Avail Use% Mounted on

/dev/mmcblk0p1  1.7G 1004M  536M  66% /

Thats also why I recommend to anyone who will listen. That they should create two different beaglebone images when developing.

• One production image with only te bare minimum installed for the given project.
• One development image with all the necessary dev packages installed. Like this one here that bloated from less than 200M to 1004M . . .

Two main reasons.

Why would you want to boat a production system needlessly. It can impact performance.

• It's a potential added security risk. As the more you have installed, the more that is potentially exploitable. Merely a potential concern, and not necessarily fact.
  

[Wally Bkg]

On Friday, May 6, 2016 at 12:58:33 AM UTC-5, William Hermans wrote:

william@beaglebone:~$ df -h /
Filesystem      Size  Used Avail Use% Mounted on
/dev/mmcblk0p1  1.7G 1004M  536M  66% /

Thats also why I recommend to anyone who will listen. That they should create two different beaglebone images when developing.

• One production image with only te bare minimum installed for the given project.
• One development image with all the necessary dev packages installed. Like this one here that bloated from less than 200M to 1004M . . .

Two main reasons.

Why would you want to boat a production system needlessly. It can impact performance.

• It's a potential added security risk. As the more you have installed, the more that is potentially exploitable. Merely a potential concern, and not necessarily fact.

I'll argue the opposite unless you have enough customer volume to have a technical support department behind you.

For most of my working career my product was generally a custom system for a specific purpose and six instances would be a raging success, but the systems were located on all three coasts.  Having the development and deployment  images be the same has definite advantages when trying to troubleshoot/repair issues  via a phone call to the users, and prevents "missing pieces" if rushing out to the remote site -- not quite so big an issue now that about everything is available via Google & github, but most of these systems were on an isolated network for security.

I only worry about image size if it forces the next cost increment in capacity, but in these days or $10-20 32GB uSD cards its not worth much of my time to worry about keeping it small.   If you need to stay in the eMMC then its important, but in the short life of the Beaglebone Black its already doubled once and likely will again at the next major revision.

[William Hermans]

I'll argue the opposite unless you have enough customer volume to have a technical support department behind you.

For most of my working career my product was generally a custom system for a specific purpose and six instances would be a raging success, but the systems were located on all three coasts.  Having the development and deployment  images be the same has definite advantages when trying to troubleshoot/repair issues  via a phone call to the users, and prevents "missing pieces" if rushing out to the remote site -- not quite so big an issue now that about everything is available via Google & github, but most of these systems were on an isolated network for security.

I only worry about image size if it forces the next cost increment in capacity, but in these days or $10-20 32GB uSD cards its not worth much of my time to worry about keeping it small.   If you need to stay in the eMMC then its important, but in the short life of the Beaglebone Black its already doubled once and likely will again at the next major revision.

This is why I'd have a "test jig" to duplicate exactly what's going on. If you control the hardware, and software. You should not need a large technical support group to figure the problem out. Then when you find the problem locally, you test locally on an exact production system by installing an apt package, if needed for the situation.

--
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.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/4e38ddce-56e8-4a49-a0db-d150d0db6b1d%40googlegroups.com.

[Robert Nelson]

now fixed:

sudo apt-get update ; sudo apt-get install bb-cape-overlays

Regards,

[William Hermans]

now fixed:

sudo apt-get update ; sudo apt-get install bb-cape-overlays

Regards,

--

Robert Nelson
https://rcn-ee.com/

Thanks Robert, but it was not my intention to create more work for you . . . after all the bb.org-overlay git is there and is pretty self explanatory. Simply having a /lib/firmware directory on the image would have eliminated my questions all together ;)

--

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYjzVv3Zxihj9ffNW-OptfbrVvceKDso4TQRuW0_9v_LNg%40mail.gmail.com.

[Rick Mann]

> On May 6, 2016, at 08:31 , Robert Nelson <robert...@gmail.com> wrote:
>
> now fixed:
>
> sudo apt-get update ; sudo apt-get install bb-cape-overlays

Handy, thanks!


--
Rick Mann
rm...@latencyzero.com

[William Hermans]

Robert,

Do you have any tips to help this console image boot up faster ? Keep in mind I'm running sysv . . .

--
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.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/DB08629B-AB5F-47A7-9967-FA8BEADFFC48%40latencyzero.com.