bb-bonescript-installer-beta ( 0.5.0-beta5) upgrade fails

156 views
Skip to first unread message

Wally Bkg

unread,
Apr 22, 2016, 6:04:45 PM4/22/16
to BeagleBoard
bb-bonescript-installer-beta upgrade fails:

make: Entering directory '/usr/local/lib/node_modules/bonescript/node_modules/ffi/node_modules/ref/build'
  CXX(target) Release/obj.target/binding/src/binding.o
  SOLINK_MODULE(target) Release/obj.target/binding.node
  COPY Release/binding.node
make: Leaving directory '/usr/local/lib/node_modules/bonescript/node_modules/ffi/node_modules/ref/build'

> seria...@2.0.6 install /usr/local/lib/node_modules/bonescript/node_modules/serialport
> node-pre-gyp install --fallback-to-build

make: Entering directory '/usr/local/lib/node_modules/bonescript/node_modules/serialport/build'
  CXX(target) Release/obj.target/serialport/src/serialport.o
Killed
dpkg: error processing package bb-bonescript-installer-beta (--configure):
 subprocess installed post-installation script returned error exit status 137
Setting up doc-beaglebone-getting-started (1.20151204-2~bpo80+20160421+1) ...
Errors were encountered while processing:
 bb-bonescript-installer-beta
E: Sub-process /usr/bin/dpkg returned an error code (1)

kernel: 4.1.18-ti-r56
Beagleboard.org Debian Image 2016-04-03

Its been pretty solid up to now, all the bonescript examples ( analogWrite() analogRead(), digitalWrite(), digitalRead() attachInterrupt() )seem to work without extraneous error or warning messages.

I've been doing apt-get update,  apt-get upgrade pretty regularly hoping to keep current.

Has a required kernel upgrade come it that doesn't install with apt-get upgrade?

I've been using this system the way I figure a newbie who only wanted bonescript, python, and node-red might do.
I can see how pushing kernel upgrades could rather quickly get you into space issues if confined to the 4GB eMMC, but if its a real dependency not doing so would seem to be a problem.

Robert Nelson

unread,
Apr 22, 2016, 6:32:44 PM4/22/16
to Beagle Board, Wally Bkg
On Fri, Apr 22, 2016 at 5:04 PM, Wally Bkg <wb666...@gmail.com> wrote:
bb-bonescript-installer-beta upgrade fails:

make: Entering directory '/usr/local/lib/node_modules/bonescript/node_modules/ffi/node_modules/ref/build'
  CXX(target) Release/obj.target/binding/src/binding.o
  SOLINK_MODULE(target) Release/obj.target/binding.node
  COPY Release/binding.node
make: Leaving directory '/usr/local/lib/node_modules/bonescript/node_modules/ffi/node_modules/ref/build'

> seria...@2.0.6 install /usr/local/lib/node_modules/bonescript/node_modules/serialport
> node-pre-gyp install --fallback-to-build

make: Entering directory '/usr/local/lib/node_modules/bonescript/node_modules/serialport/build'
  CXX(target) Release/obj.target/serialport/src/serialport.o
Killed
dpkg: error processing package bb-bonescript-installer-beta (--configure):
 subprocess installed post-installation script returned error exit status 137
Setting up doc-beaglebone-getting-started (1.20151204-2~bpo80+20160421+1) ...
Errors were encountered while processing:
 bb-bonescript-installer-beta
E: Sub-process /usr/bin/dpkg returned an error code (1)

kernel: 4.1.18-ti-r56
Beagleboard.org Debian Image 2016-04-03

Its been pretty solid up to now, all the bonescript examples ( analogWrite() analogRead(), digitalWrite(), digitalRead() attachInterrupt() )seem to work without extraneous error or warning messages.

I've been doing apt-get update,  apt-get upgrade pretty regularly hoping to keep current.

Has a required kernel upgrade come it that doesn't install with apt-get upgrade?

Nope...
 

I've been using this system the way I figure a newbie who only wanted bonescript, python, and node-red might do.
I can see how pushing kernel upgrades could rather quickly get you into space issues if confined to the 4GB eMMC, but if its a real dependency not doing so would seem to be a problem.


Odd, was this the iot or lxqt or console image?

if you do : dpkg --list | pastebinit

we can compare against:


From a fresh 2016-04-03 iot image i'm seeing:

debian@beaglebone:~$ cat /etc/dogtag 
BeagleBoard.org Debian Image 2016-04-03
debian@beaglebone:~$ uname -r
4.1.18-ti-r56
debian@beaglebone:~$ sudo apt-get update ; sudo apt-get upgrade

Reading state information... Done

Calculating upgrade... Done
The following packages will be upgraded:
  bb-bonescript-installer-beta bb-wl18xx-firmware connman
  doc-beaglebone-getting-started libmraa0 linux-libc-dev openssh-client
  openssh-server openssh-sftp-server tiomapconf upm
11 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 15.6 MB of archives.
After this operation, 63.5 kB of additional disk space will be used.
Do you want to continue? [Y/n] y

0% [Working]
0% [Waiting for headers] [Waiting for headers]
Get:1 http://repos.rcn-ee.com/debian/ jessie/main libmraa0 armhf 0.9.5-git20160420-0rcnee1~bpo80+20160420+1 [408 kB]
Get:2 http://security.debian.org/ jessie/updates/main openssh-sftp-server armhf 1:6.7p1-5+deb8u2 [33.2 kB]
Get:3 http://httpredir.debian.org/debian/ jessie-updates/main linux-libc-dev armhf 3.16.7-ckt25-2 [1,004 kB]
Get:4 http://security.debian.org/ jessie/updates/main openssh-server armhf 1:6.7p1-5+deb8u2 [324 kB]
Get:5 http://repos.rcn-ee.com/debian/ jessie/main upm armhf 0.5.1-git20160410-0rcnee1~bpo80+20160410+1 [12.3 MB]
Get:6 http://security.debian.org/ jessie/updates/main openssh-client armhf 1:6.7p1-5+deb8u2 [643 kB]
Get:7 http://repos.rcn-ee.com/debian/ jessie/main bb-bonescript-installer-beta all 0.5.0~beta4-1rcnee2~bpo80+20160421+1 [4,062 B]
Get:8 http://repos.rcn-ee.com/debian/ jessie/main doc-beaglebone-getting-started all 1.20151204-2~bpo80+20160421+1 [17.2 kB]
Get:9 http://repos.rcn-ee.com/debian/ jessie/main connman armhf 1.32-git20160418-0rcnee1~bpo80+20160418+1 [307 kB]
Get:10 http://repos.rcn-ee.com/debian/ jessie/main bb-wl18xx-firmware all 1.20160413-0rcnee1~bpo80+20160413+1 [48.1 kB]
Get:11 http://repos.rcn-ee.com/debian/ jessie/main tiomapconf armhf 1.72.0-git20160414-1~bpo80+20160414+1 [535 kB]
Fetched 15.6 MB in 29s (529 kB/s)
Preconfiguring packages ...
(Reading database ... 52946 files and directories currently installed.)
Preparing to unpack .../libmraa0_0.9.5-git20160420-0rcnee1~bpo80+20160420+1_armhf.deb ...
Unpacking libmraa0:armhf (0.9.5-git20160420-0rcnee1~bpo80+20160420+1) over (0.9.5-git20160302-0rcnee1~bpo80+20160302+1) ...
Preparing to unpack .../upm_0.5.1-git20160410-0rcnee1~bpo80+20160410+1_armhf.deb ...
Unpacking upm:armhf (0.5.1-git20160410-0rcnee1~bpo80+20160410+1) over (0.5.1-git20160302-0rcnee6~bpo80+20160302+1) ...
Preparing to unpack .../bb-bonescript-installer-beta_0.5.0~beta4-1rcnee2~bpo80+20160421+1_all.deb ...
Unpacking bb-bonescript-installer-beta (0.5.0~beta4-1rcnee2~bpo80+20160421+1) over (0.5.0~beta3-0rcnee1~bpo80+20160226+1) ...
Preparing to unpack .../doc-beaglebone-getting-started_1.20151204-2~bpo80+20160421+1_all.deb ...
Unpacking doc-beaglebone-getting-started (1.20151204-2~bpo80+20160421+1) over (1.20151204-1~bpo80+20151207+1) ...
Preparing to unpack .../openssh-sftp-server_1%3a6.7p1-5+deb8u2_armhf.deb ...
Unpacking openssh-sftp-server (1:6.7p1-5+deb8u2) over (1:6.7p1-5+deb8u1) ...
Preparing to unpack .../openssh-server_1%3a6.7p1-5+deb8u2_armhf.deb ...
Unpacking openssh-server (1:6.7p1-5+deb8u2) over (1:6.7p1-5+deb8u1) ...
Preparing to unpack .../openssh-client_1%3a6.7p1-5+deb8u2_armhf.deb ...
Unpacking openssh-client (1:6.7p1-5+deb8u2) over (1:6.7p1-5+deb8u1) ...
Preparing to unpack .../connman_1.32-git20160418-0rcnee1~bpo80+20160418+1_armhf.deb ...
Unpacking connman (1.32-git20160418-0rcnee1~bpo80+20160418+1) over (1.31-git20160309-0rcnee1~bpo80+20160309+1) ...
Preparing to unpack .../linux-libc-dev_3.16.7-ckt25-2_armhf.deb ...
Unpacking linux-libc-dev:armhf (3.16.7-ckt25-2) over (3.16.7-ckt25-1) ...
Preparing to unpack .../bb-wl18xx-firmware_1.20160413-0rcnee1~bpo80+20160413+1_all.deb ...
Unpacking bb-wl18xx-firmware (1.20160413-0rcnee1~bpo80+20160413+1) over (1.20160310-0rcnee2~bpo80+20160310+1) ...
Preparing to unpack .../tiomapconf_1.72.0-git20160414-1~bpo80+20160414+1_armhf.deb ...
Unpacking tiomapconf (1.72.0-git20160414-1~bpo80+20160414+1) over (1.72.0-git20150828-1~bpo80+20151023+1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for systemd (215-17+deb8u4rcnee1~bpo80+20160313+1) ...
Processing triggers for dbus (1.8.20-0+deb8u1) ...
Setting up libmraa0:armhf (0.9.5-git20160420-0rcnee1~bpo80+20160420+1) ...
Setting up upm:armhf (0.5.1-git20160410-0rcnee1~bpo80+20160410+1) ...
Setting up bb-bonescript-installer-beta (0.5.0~beta4-1rcnee2~bpo80+20160421+1) ...
bb-bonescript-installer:npm: [2.15.0]
bb-bonescript-installer:node: [v0.12.13]
bb-bonescript-installer:Installing: bonescript-0.5.0-beta4 (for bonescript)
[0m sys...@0.2.6: wanted: {"node":">=0.6.11 <0.11.0"} (current: {"node":"0.12.13","npm":"2.15.0"})

> s...@0.2.0 install /usr/local/lib/node_modules/bonescript/node_modules/spi
> node-gyp rebuild

[0Gmake: Entering directory '/usr/local/lib/node_modules/bonescript/node_modules/spi/build'
[0G  CXX(target) Release/obj.target/_spi/src/spi_binding.o
[0G../src/spi_binding.cc: In member function ‘void Spi::full_duplex_transfer(v8::Isolate*, const v8::FunctionCallbackInfo<v8::Value>&, char*, char*, size_t, uint32_t, uint16_t, uint8_t)’:
../src/spi_binding.cc:199:3: warning: missing initializer for member ‘spi_ioc_transfer::cs_change’ [-Wmissing-field-initializers]
   };
   ^
../src/spi_binding.cc:199:3: warning: missing initializer for member ‘spi_ioc_transfer::tx_nbits’ [-Wmissing-field-initializers]
../src/spi_binding.cc:199:3: warning: missing initializer for member ‘spi_ioc_transfer::rx_nbits’ [-Wmissing-field-initializers]
../src/spi_binding.cc:199:3: warning: missing initializer for member ‘spi_ioc_transfer::pad’ [-Wmissing-field-initializers]
[0G  SOLINK_MODULE(target) Release/obj.target/_spi.node
  COPY Release/_spi.node
make: Leaving directory '/usr/local/lib/node_modules/bonescript/node_modules/spi/build'
 

> i...@0.2.1 install /usr/local/lib/node_modules/bonescript/node_modules/i2c
> node-gyp rebuild
[0Gmake: Entering directory '/usr/local/lib/node_modules/bonescript/node_modules/i2c/build'
  CXX(target) Release/obj.target/i2c/src/i2c.o
[0G  SOLINK_MODULE(target) Release/obj.target/i2c.node
[0G  COPY Release/i2c.node
make: Leaving directory '/usr/local/lib/node_modules/bonescript/node_modules/i2c/build'

> ep...@0.1.17 install /usr/local/lib/node_modules/bonescript/node_modules/epoll
> node-gyp rebuild

make: Entering directory '/usr/local/lib/node_modules/bonescript/node_modules/epoll/build'
  CXX(target) Release/obj.target/epoll/src/epoll.o
[0G  SOLINK_MODULE(target) Release/obj.target/epoll.node
  COPY Release/epoll.node
make: Leaving directory '/usr/local/lib/node_modules/bonescript/node_modules/epoll/build'
> r...@1.3.2 install /usr/local/lib/node_modules/bonescript/node_modules/ffi/node_modules/ref
> node-gyp rebuild

make: Entering directory '/usr/local/lib/node_modules/bonescript/node_modules/ffi/node_modules/ref/build'
  CXX(target) Release/obj.target/binding/src/binding.o
SOLINK_MODULE(target) Release/obj.target/binding.node
  COPY Release/binding.node
make: Leaving directory '/usr/local/lib/node_modules/bonescript/node_modules/ffi/node_modules/ref/build'

> f...@2.0.0 install /usr/local/lib/node_modules/bonescript/node_modules/ffi
> node-gyp rebuild

make: Entering directory '/usr/local/lib/node_modules/bonescript/node_modules/ffi/build'
  CC(target) Release/obj.target/ffi/deps/libffi/src/prep_cif.o
  CC(target) Release/obj.target/ffi/deps/libffi/src/types.o
  CC(target) Release/obj.target/ffi/deps/libffi/src/raw_api.o
  CC(target) Release/obj.target/ffi/deps/libffi/src/java_raw_api.o
  CC(target) Release/obj.target/ffi/deps/libffi/src/closures.o
  CC(target) Release/obj.target/ffi/deps/libffi/src/arm/ffi.o
../deps/libffi/src/arm/ffi.c: In function ‘ffi_prep_args’:
../deps/libffi/src/arm/ffi.c:72:10: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
    && vi < ecif->cif->vfp_nargs && vfp_type_p (*p_arg))
          ^
../deps/libffi/src/arm/ffi.c: In function ‘ffi_prep_incoming_args_SYSV’:
../deps/libffi/src/arm/ffi.c:335:10: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
    && vi < cif->vfp_nargs && vfp_type_p (*p_arg))
          ^
../deps/libffi/src/arm/ffi.c: In function ‘layout_vfp_args’:
../deps/libffi/src/arm/ffi.c:750:17: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   for (i = 0; i < cif->nargs; i++)
                 ^
  CC(target) Release/obj.target/ffi/deps/libffi/src/arm/sysv.o
  AR(target) Release/obj.target/deps/libffi/libffi.a
  COPY Release/libffi.a
  CXX(target) Release/obj.target/ffi_bindings/src/ffi.o
  CXX(target) Release/obj.target/ffi_bindings/src/callback_info.o
  CXX(target) Release/obj.target/ffi_bindings/src/threaded_callback_invokation.o
  SOLINK_MODULE(target) Release/obj.target/ffi_bindings.node
  COPY Release/ffi_bindings.node
make: Leaving directory '/usr/local/lib/node_modules/bonescript/node_modules/ffi/build'

> seria...@2.0.6 install /usr/local/lib/node_modules/bonescript/node_modules/serialport
> node-pre-gyp install --fallback-to-build

make: Entering directory '/usr/local/lib/node_modules/bonescript/node_modules/serialport/build'
  CXX(target) Release/obj.target/serialport/src/serialport.o
  CXX(target) Release/obj.target/serialport/src/serialport_unix.o
  CXX(target) Release/obj.target/serialport/src/serialport_poller.o
  SOLINK_MODULE(target) Release/obj.target/serialport.node
  COPY Release/serialport.node
  COPY /usr/local/lib/node_modules/bonescript/node_modules/serialport/build/Release/node-v14-linux-arm/serialport.node
  TOUCH Release/obj.target/action_after_build.stamp
make: Leaving directory '/usr/local/lib/node_modules/bonescript/node_modules/serialport/build'
bones...@0.5.0-beta4 /usr/local/lib/node_modules/bonescript
├── sys...@0.2.6
├── s...@0.2.0 (bind...@1.2.1)
├── win...@2.1.1 (cy...@1.0.3, stack...@0.0.9, ey...@0.1.8, isst...@0.1.2, pkg...@0.3.1, as...@1.0.0, col...@1.0.3)
├── exp...@4.13.4 (escap...@1.0.3, utils...@1.0.0, cookie-s...@1.0.6, met...@1.1.2, range-...@1.0.3, fr...@0.3.0, va...@1.0.1, pars...@1.3.1, array-...@1.1.1, et...@1.7.0, conten...@1.0.1, merge-de...@1.0.1, path-to...@0.1.7, coo...@0.1.5, content-d...@0.5.1, serve-...@1.10.2, de...@1.1.0, on-fi...@2.3.0, finalh...@0.4.1, q...@4.0.0, de...@2.2.0, proxy...@1.0.10, se...@0.13.1, typ...@1.6.12, acc...@1.2.13)
├── i...@0.2.1 (bind...@1.2.1, re...@0.1.3, under...@1.8.2, coffee...@1.9.1)
├── sock...@1.4.5 (has-b...@0.1.7, de...@2.2.0, socket.i...@2.2.6, engi...@1.6.8, socket.i...@0.4.0, socket.i...@1.4.5)
├── ep...@0.1.17 (bind...@1.2.1, n...@2.2.1)
├── f...@2.0.0 (bind...@1.2.1, ref-s...@1.0.2, de...@2.2.0, n...@2.2.1, r...@1.3.2)
└── seria...@2.0.6 (bind...@1.2.1, s...@0.1.7, as...@0.9.0, de...@2.2.0, n...@2.0.9, opti...@0.6.1)
[2Kbb-bonescript-installer:Installed
Setting up doc-beaglebone-getting-started (1.20151204-2~bpo80+20160421+1) ...
Setting up openssh-client (1:6.7p1-5+deb8u2) ...
Setting up openssh-sftp-server (1:6.7p1-5+deb8u2) ...
Setting up openssh-server (1:6.7p1-5+deb8u2) ...
Setting up connman (1.32-git20160418-0rcnee1~bpo80+20160418+1) ...
Setting up linux-libc-dev:armhf (3.16.7-ckt25-2) ...
Setting up bb-wl18xx-firmware (1.20160413-0rcnee1~bpo80+20160413+1) ...
Setting up tiomapconf (1.72.0-git20160414-1~bpo80+20160414+1) ...
Processing triggers for libc-bin (2.19-18+deb8u4) ...
debian@beaglebone:~$ node js --version
v0.12.13
debian@beaglebone:~$ /usr/bin/npm --version
2.15.0
debian@beaglebone:~$ 

Regards,

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

Wally Bkg

unread,
Apr 22, 2016, 6:56:51 PM4/22/16
to BeagleBoard, wb666...@gmail.com


On Friday, April 22, 2016 at 5:32:44 PM UTC-5, RobertCNelson wrote:
Has a required kernel upgrade come it that doesn't install with apt-get upgrade?

Nope...
 

I've been using this system the way I figure a newbie who only wanted bonescript, python, and node-red might do.
I can see how pushing kernel upgrades could rather quickly get you into space issues if confined to the 4GB eMMC, but if its a real dependency not doing so would seem to be a problem.


Odd, was this the iot or lxqt or console image?

Sorry that I forgot to mention that it was an lxqt image.
 

if you do : dpkg --list | pastebinit

we can compare against:


I will do this as soon as my repeat upgrade attempt either finishes or fails 

From a fresh 2016-04-03 iot image i'm seeing:

debian@beaglebone:~$ cat /etc/dogtag 
BeagleBoard.org Debian Image 2016-04-03
debian@beaglebone:~$ uname -r
4.1.18-ti-r56
debian@beaglebone:~$ sudo apt-get update ; sudo apt-get upgrade

Reading state information... Done

Calculating upgrade... Done
The following packages will be upgraded:
  bb-bonescript-installer-beta bb-wl18xx-firmware connman
  doc-beaglebone-getting-started libmraa0 linux-libc-dev openssh-client
  openssh-server openssh-sftp-server tiomapconf upm
11 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 15.6 MB of archives.
After this operation, 63.5 kB of additional disk space will be used.
Do you want to continue? [Y/n] y

Interesting, I only had two updates today:
bb-bonescript-installer-beta
doc-beaglebone-getting-started

I recall these happened last time (yesterday?)
connman openssh-client openssh-server openssh-sftp-server

The others, particularly bb-wl18xx-firmware I don't recall happening.
 
Ill follow-up with the pastebinit when when the current upgrade finishes.

Robert Nelson

unread,
Apr 22, 2016, 7:04:21 PM4/22/16
to Beagle Board, Wally Bkg
On Fri, Apr 22, 2016 at 5:56 PM, Wally Bkg <wb666...@gmail.com> wrote:


On Friday, April 22, 2016 at 5:32:44 PM UTC-5, RobertCNelson wrote:
Has a required kernel upgrade come it that doesn't install with apt-get upgrade?

Nope...
 

I've been using this system the way I figure a newbie who only wanted bonescript, python, and node-red might do.
I can see how pushing kernel upgrades could rather quickly get you into space issues if confined to the 4GB eMMC, but if its a real dependency not doing so would seem to be a problem.


Odd, was this the iot or lxqt or console image?

Sorry that I forgot to mention that it was an lxqt image.

Okay, i'll check that quickly. .;)
 
 

if you do : dpkg --list | pastebinit

we can compare against:


I will do this as soon as my repeat upgrade attempt either finishes or fails 

From a fresh 2016-04-03 iot image i'm seeing:

debian@beaglebone:~$ cat /etc/dogtag 
BeagleBoard.org Debian Image 2016-04-03
debian@beaglebone:~$ uname -r
4.1.18-ti-r56
debian@beaglebone:~$ sudo apt-get update ; sudo apt-get upgrade

Reading state information... Done

Calculating upgrade... Done
The following packages will be upgraded:
  bb-bonescript-installer-beta bb-wl18xx-firmware connman
  doc-beaglebone-getting-started libmraa0 linux-libc-dev openssh-client
  openssh-server openssh-sftp-server tiomapconf upm
11 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 15.6 MB of archives.
After this operation, 63.5 kB of additional disk space will be used.
Do you want to continue? [Y/n] y

Interesting, I only had two updates today:
bb-bonescript-installer-beta

^ this was a major upgrade beta3->beta4.. the problem, npm behind the scenes does a lot of crap.. (i hate npm)
 
doc-beaglebone-getting-started

this was a symlink update, nothing more.

 
I recall these happened last time (yesterday?)
connman openssh-client openssh-server openssh-sftp-server

The others, particularly bb-wl18xx-firmware I don't recall happening.

these were last week...
 
 
Ill follow-up with the pastebinit when when the current upgrade finishes.

Wally Bkg

unread,
Apr 22, 2016, 8:04:39 PM4/22/16
to BeagleBoard, wb666...@gmail.com
On Friday, April 22, 2016 at 6:04:21 PM UTC-5, RobertCNelson wrote:



Sorry that I forgot to mention that it was an lxqt image.

Okay, i'll check that quickly. .;)
 
 

if you do : dpkg --list | pastebinit

we can compare against:


I did the pastebinit, but where does the 440395 come from?  I've never used pastebinit before. 

Robert Nelson

unread,
Apr 22, 2016, 8:16:58 PM4/22/16
to Beagle Board, Wally Bkg
You need to have the network connected...  by "|" (or'ing) it with pastebinit binary it'll get uploaded..

Regards,

Wally Bkg

unread,
Apr 23, 2016, 7:14:58 PM4/23/16
to BeagleBoard, wb666...@gmail.com
I have pastebinit install and it apt-get install pastebinit says its the latest version.

piping dpkg --list to pastebinit (dpkg --list | pastebinit) returns:

I am connected to the network.  I'm missing something here.
Do I need to make an account there or something?

Jason Kridner

unread,
Apr 25, 2016, 8:16:09 AM4/25/16
to BeagleBoard, wb666...@gmail.com
Do we know why this said beta5, not beta4?
--
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/fe1bef10-0ebd-41f8-896d-36aa2f63d6e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Wally Bkg

unread,
Apr 25, 2016, 10:04:38 AM4/25/16
to BeagleBoard
I'm very confused by what is going on with these npm updates being trigged by apt-get upgrades.  But I got the bb-bonescript-installer-beta upgrade to apparently install by doing:
apt-get purge bb-bonescript-installer-beta
apt-get install bb-bonescript-installer-beta

The cloud9 bonescript examples seem to work, I've simple prototype circuits wired up to test the basics: analogRead(). analogWrite(), digitalWrite(), digitalRead(), & attachInterrupt().

The 192.168.7.2/bone101/Support/bone101/ interactive tutorial page doesn't work and the "Navigation" pane on the left side of the page doesn't render and I never get the "your beaglebone is connected" banner.

Robert Nelson

unread,
Apr 25, 2016, 10:13:26 AM4/25/16
to Beagle Board
cd /var/lib/cloud9/
git pull

Regards,

Wally Bkg

unread,
Apr 25, 2016, 10:19:58 AM4/25/16
to BeagleBoard
On Monday, April 25, 2016 at 9:04:38 AM UTC-5, Wally Bkg wrote:

The 192.168.7.2/bone101/Support/bone101/ interactive tutorial page doesn't work and the "Navigation" pane on the left side of the page doesn't render and I never get the "your beaglebone is connected" banner.

I've noticed that the "testing" images all seem to be a single partition (ext4) on the SD card.  Is it possible BEAGLEBONE 41MB partition that mounts via Linux File-Stor Gadget is actually the fat partition in the 4GB eMMC (Jessie with a 3.8.x kernel and less the correctly working bonescript version)?  Maybe this explains why the localhost bone101 page doesn't work right.

Robert Nelson

unread,
Apr 25, 2016, 10:28:07 AM4/25/16
to Beagle Board
That virtual "fat" partition is provided by the "doc-beaglebone-getting-started" package...

-rw-r--r-- 1 root root 40M Dec  7 17:04 /var/cache/doc-beaglebone-getting-started/beaglebone-getting-started-2015-12-04.img

the bone101 Navigation issue on the left hand side can be fixed via:

cd /var/lib/cloud9/
git pull

Regards,

Wally Bkg

unread,
Apr 25, 2016, 10:29:36 AM4/25/16
to BeagleBoard
Thanks!  
This fixes it.  Any way this could be made to happen automatically as part of an apt-get bonescript upgrade?
  

Robert Nelson

unread,
Apr 25, 2016, 11:00:12 AM4/25/16
to Beagle Board
Right now it's a git repo that supports 3 separate projects.. There is talk of converting it to a deb package..

Regards,
Reply all
Reply to author
Forward
0 new messages