Re: [beagleboard] BBB Wireless frequently drops connection
looks like I have a lot of partially installed packages... debian@BBB:/$ apt-get -f install --dry-run NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: libpci3 libspeechd2 Use 'apt-get autoremove' to remove them. The following extra packages will be installed: chromium-browser Suggested packages: webaccounts-chromium-extension unity-chromium-extension adobe-flashplugin The following packages will be upgraded: chromium-browser 1 upgraded, 0 newly installed, 0 to remove and 84 not upgraded. 133 not fully installed or removed. Inst chromium-browser [53.0.2785.143-0ubuntu1.1307~bpo80+20161016+1] (59.0.3071.109-0ubuntu0.16.04.1289rcnee0~jessie+20170705 rcn-ee.net:repos.rcn-ee.com [armhf]) Conf libssl1.0.0 (1.0.1t-1+deb8u7 Debian:8.10/oldstable, Debian-Security:8/oldstable [armhf]) Conf openssl (1.0.1t-1+deb8u7 Debian:8.10/oldstable, Debian-Security:8/oldstable [armhf]) Conf ca-certificates (20141019+deb8u3 Debian:8.10/oldstable [all]) Conf nodejs (6.14.0-1nodesource1 Node Source:deb.nodesource.com [armhf]) Conf libapt-inst1.5 (1.0.9.8.4 Debian:8.10/oldstable, Debian-Security:8/oldstable [armhf]) Conf libncursesw5 (5.9+20140913-1+deb8u2 Debian:8.10/oldstable [armhf]) Conf libevent-2.0-5 (2.0.21-stable-2+deb8u1 Debian:8.10/oldstable, Debian-Security:8/oldstable [armhf]) Conf libnettle4 (2.7.1-5+deb8u2 Debian:8.10/oldstable [armhf]) Conf libhogweed2 (2.7.1-5+deb8u2 Debian:8.10/oldstable [armhf]) Conf libtasn1-6 (4.2-3+deb8u3 Debian:8.10/oldstable, Debian-Security:8/oldstable [armhf]) Conf libgnutls-deb0-28 (3.3.8-6+deb8u7 Debian:8.10/oldstable [armhf]) Conf libgnutls-openssl27 (3.3.8-6+deb8u7 Debian:8.10/oldstable [armhf]) Conf libkrb5support0 (1.12.1+dfsg-19+deb8u4 Debian:8.10/oldstable [armhf]) Conf libk5crypto3 (1.12.1+dfsg-19+deb8u4 Debian:8.10/oldstable [armhf]) Conf libkrb5-3 (1.12.1+dfsg-19+deb8u4 Debian:8.10/oldstable [armhf]) Conf libgssapi-krb5-2 (1.12.1+dfsg-19+deb8u4 Debian:8.10/oldstable [armhf]) Conf libldap-2.4-2 (2.4.40+dfsg-1+deb8u3 Debian:8.10/oldstable, Debian-Security:8/oldstable [armhf]) Conf libmagic1 (1:5.22+15-2+deb8u3 Debian:8.10/oldstable [armhf]) Conf libxml2 (2.9.1+dfsg1-5+deb8u6 Debian-Security:8/oldstable [armhf]) Conf perl-modules (5.20.2-3+deb8u9 Debian:8.10/oldstable, Debian-Security:8/oldstable [all]) Conf perl (5.20.2-3+deb8u9 Debian:8.10/oldstable, Debian-Security:8/oldstable [armhf]) Conf apache2-bin (2.4.10-10+deb8u11 Debian:8.10/oldstable, Debian-Security:8/oldstable [armhf]) Conf apache2-utils (2.4.10-10+deb8u11 Debian:8.10/oldstable, Debian-Security:8/oldstable [armhf]) Conf apache2-data (2.4.10-10+deb8u11 Debian:8.10/oldstable, Debian-Security:8/oldstable [all]) Conf apache2 (2.4.10-10+deb8u11 Debian:8.10/oldstable, Debian-Security:8/oldstable [armhf]) Conf libatomic1 (4.9.2-10+deb8u1 Debian-Security:8/oldstable [armhf]) Conf libpng12-0 (1.2.50-2+deb8u3 Debian:8.10/oldstable [armhf]) Conf libfreetype6 (2.5.2-3+deb8u2 Debian:8.10/oldstable, Debian-Security:8/oldstable [armhf]) Conf libx11-data (2:1.6.2-3+deb8u1 Debian:8.10/oldstable [all]) Conf libx11-6 (2:1.6.2-3+deb8u1 Debian:8.10/oldstable [armhf]) Conf libcairo2 (1.14.0-2.1+deb8u2 Debian:8.10/oldstable [armhf]) Conf libcups2 (1.7.5-11+deb8u2 Debian:8.10/oldstable [armhf]) Conf libdbus-1-3 (1.8.22-0+deb8u1 Debian:8.10/oldstable [armhf]) Conf libexpat1 (2.1.0-6+deb8u4 Debian:8.10/oldstable, Debian-Security:8/oldstable [armhf]) Conf libgdk-pixbuf2.0-common (2.31.1-2+deb8u7 Debian-Security:8/oldstable [all]) Conf libjasper1 (1.900.1-debian1-2.4+deb8u3 Debian:8.10/oldstable, Debian-Security:8/oldstable [armhf]) Conf libtiff5 (4.0.3-12.3+deb8u5 Debian-Security:8/oldstable [armhf]) Conf libgdk-pixbuf2.0-0 (2.31.1-2+deb8u7 Debian-Security:8/oldstable [armhf]) Conf libnss3 (2:3.26-1+debu8u3 Debian:8.10/oldstable, Debian-Security:8/oldstable [armhf]) Conf libx11-xcb1 (2:1.6.2-3+deb8u1 Debian:8.10/oldstable [armhf]) Conf libxfixes3 (1:5.0.1-2+deb8u1 Debian:8.10/oldstable [armhf]) Conf libxcursor1 (1:1.1.14-1+deb8u1 Debian-Security:8/oldstable [armhf]) Conf libxi6 (2:1.7.4-1+deb8u1 Debian:8.10/oldstable [armhf]) Conf libxrandr2 (2:1.4.2-1+deb8u1 Debian:8.10/oldstable [armhf]) Conf libxtst6 (2:1.2.2-1+deb8u1 Debian:8.10/oldstable [armhf]) Conf chromium-codecs-ffmpeg-extra (59.0.3071.109-0ubuntu0.16.04.1289rcnee0~jessie+20170705 rcn-ee.net:repos.rcn-ee.com [armhf]) Conf chromium-browser (59.0.3071.109-0ubuntu0.16.04.1289rcnee0~jessie+20170705 rcn-ee.net:repos.rcn-ee.com [armhf]) Conf chromium-browser-l10n (59.0.3071.109-0ubuntu0.16.04.1289rcnee0~jessie+20170705 rcn-ee.
Re: [beagleboard] BBB Wireless frequently drops connection
I've cleaned the package cache: sudo apt-get clean and recovered ~400MB "disk" space. debian@BBB:/$ sudo apt install firmware-ti-connectivity Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: chromium-browser : Depends: chromium-codecs-ffmpeg-extra (= 53.0.2785.143-0ubuntu1.1307~bpo80+20161016+1) but 59.0.3071.109-0ubuntu0.16.04.1289rcnee0~jessie+20170705 is to be installed or chromium-codecs-ffmpeg (= 53.0.2785.143-0ubuntu1.1307~bpo80+20161016+1) but it is not going to be installed chromium-browser-l10n : Depends: chromium-browser (>= 59.0.3071.109-0ubuntu0.16.04.1289rcnee0~jessie+20170705) but 53.0.2785.143-0ubuntu1.1307~bpo80+20161016+1 is to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). and of course then this fails without firmware-ti-connectivity installed... debian@BBB:/$ apt install --only-upgrade --dry-run bb-wl18xx-firmware NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: bb-wl18xx-firmware : Depends: firmware-ti-connectivity but it is not going to be installed chromium-browser : Depends: chromium-codecs-ffmpeg-extra (= 53.0.2785.143-0ubuntu1.1307~bpo80+20161016+1) but 59.0.3071.109-0ubuntu0.16.04.1289rcnee0~jessie+20170705 is to be installed or chromium-codecs-ffmpeg (= 53.0.2785.143-0ubuntu1.1307~bpo80+20161016+1) but it is not going to be installed chromium-browser-l10n : Depends: chromium-browser (>= 59.0.3071.109-0ubuntu0.16.04.1289rcnee0~jessie+20170705) but 53.0.2785.143-0ubuntu1.1307~bpo80+20161016+1 is to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). I don't see how chromium (et cetera) is related. Is this a side-effect from my mistake in the previous (huge, aborted) upgrade run? Suggestions on how to *just* upgrade what I need for improved wireless connectivity (this OP)? On Wednesday, March 28, 2018 at 3:51:13 PM UTC-7, ags wrote: > > More specifics: I see lots of stuff (~450MiB) in /var/cache/apt/archives. > Only two are dated today. One is bb-wl18xx-firmware... > > Do I "sudo apt-get clean", or delete everything manually from the > apt/archive (except bb-wl18xx-firmware...) or something else? > > > > On Wednesday, March 28, 2018 at 3:42:01 PM UTC-7, ags wrote: >> >> This is turning into an "apt" tutorial - but searches haven't helped me >> find what I'm looking for. >> >> I have killed the upgrade mis-stream. I think it successfully downloaded >> all the upgradable packages, and ran out of "disk" space while unpacking >> it. I don't know if anything was actually installed. >> >> I still have 0% free on /dev/mmcblkXX >> >> Is there a way to determine if any package was actually upgraded? >> >> Where are the downloaded packages? Can I just delete them presuming they >> were the unintended upgrades, and start again with the correct apt command >> as you provided in a later post >> >> >> On Wednesday, March 28, 2018 at 2:44:06 PM UTC-7, RobertCNelson wrote: >>> >>> On Wed, Mar 28, 2018 at 4:34 PM, ags wrote: >>> > Sorry if this is obvious. The current situation is that I have no >>> "disk" >>> > space left and the upgrade is paused (^Z) after fetching 464 MB. I >>> have >>> > minimal user-installed "stuff" on the system so it appears to have >>> been >>> > filled up with this upgrade attempt. >>> > >>> > I thought I would be installing the "firmware-ti-connectivity" package >>> (for >>> > the first time) and upgrading the "bb-wl18xx-firmware" package to a >>> newer >>> > version. The former seemed OK, but the latter (apparently) pulled in >>> another >>> > 200+ packages. Did I do that incorrectly? >>> >>> Yeah i messed that up, it's "install --only-upgrade" >>> >>> sudo apt install --only-upgrade bb-wl18xx-firmware >>> firmware-ti-connectivity >>> >>> > >>> > Am I to "apt remove --purge" each of the 200+ packages that were >>> > (apparently) pulled in? >>> >>> no, many are just updates to pkgs you already have installed.. >>> >>> > >>> > Still, how do I perform the upgrade to get the possible fix for my >>> > connectivity problem within available disk space? (is it impossible?) >>> >>> i'd kill the upgrade process and do the above >>> >>> Regards, >>> >>> -- >>> Robert Nelson >>> https://rcn-ee.com/ >>> >> -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are
Re: [beagleboard] BBB Wireless frequently drops connection
More specifics: I see lots of stuff (~450MiB) in /var/cache/apt/archives. Only two are dated today. One is bb-wl18xx-firmware... Do I "sudo apt-get clean", or delete everything manually from the apt/archive (except bb-wl18xx-firmware...) or something else? On Wednesday, March 28, 2018 at 3:42:01 PM UTC-7, ags wrote: > > This is turning into an "apt" tutorial - but searches haven't helped me > find what I'm looking for. > > I have killed the upgrade mis-stream. I think it successfully downloaded > all the upgradable packages, and ran out of "disk" space while unpacking > it. I don't know if anything was actually installed. > > I still have 0% free on /dev/mmcblkXX > > Is there a way to determine if any package was actually upgraded? > > Where are the downloaded packages? Can I just delete them presuming they > were the unintended upgrades, and start again with the correct apt command > as you provided in a later post > > > On Wednesday, March 28, 2018 at 2:44:06 PM UTC-7, RobertCNelson wrote: >> >> On Wed, Mar 28, 2018 at 4:34 PM, ags wrote: >> > Sorry if this is obvious. The current situation is that I have no >> "disk" >> > space left and the upgrade is paused (^Z) after fetching 464 MB. I have >> > minimal user-installed "stuff" on the system so it appears to have been >> > filled up with this upgrade attempt. >> > >> > I thought I would be installing the "firmware-ti-connectivity" package >> (for >> > the first time) and upgrading the "bb-wl18xx-firmware" package to a >> newer >> > version. The former seemed OK, but the latter (apparently) pulled in >> another >> > 200+ packages. Did I do that incorrectly? >> >> Yeah i messed that up, it's "install --only-upgrade" >> >> sudo apt install --only-upgrade bb-wl18xx-firmware >> firmware-ti-connectivity >> >> > >> > Am I to "apt remove --purge" each of the 200+ packages that were >> > (apparently) pulled in? >> >> no, many are just updates to pkgs you already have installed.. >> >> > >> > Still, how do I perform the upgrade to get the possible fix for my >> > connectivity problem within available disk space? (is it impossible?) >> >> i'd kill the upgrade process and do the above >> >> Regards, >> >> -- >> Robert Nelson >> https://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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/5e6fc98b-2ae8-4e21-bc60-a9fc2a608bed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] BBB Wireless frequently drops connection
This is turning into an "apt" tutorial - but searches haven't helped me find what I'm looking for. I have killed the upgrade mis-stream. I think it successfully downloaded all the upgradable packages, and ran out of "disk" space while unpacking it. I don't know if anything was actually installed. I still have 0% free on /dev/mmcblkXX Is there a way to determine if any package was actually upgraded? Where are the downloaded packages? Can I just delete them presuming they were the unintended upgrades, and start again with the correct apt command as you provided in a later post On Wednesday, March 28, 2018 at 2:44:06 PM UTC-7, RobertCNelson wrote: > > On Wed, Mar 28, 2018 at 4:34 PM, ags > > wrote: > > Sorry if this is obvious. The current situation is that I have no "disk" > > space left and the upgrade is paused (^Z) after fetching 464 MB. I have > > minimal user-installed "stuff" on the system so it appears to have been > > filled up with this upgrade attempt. > > > > I thought I would be installing the "firmware-ti-connectivity" package > (for > > the first time) and upgrading the "bb-wl18xx-firmware" package to a > newer > > version. The former seemed OK, but the latter (apparently) pulled in > another > > 200+ packages. Did I do that incorrectly? > > Yeah i messed that up, it's "install --only-upgrade" > > sudo apt install --only-upgrade bb-wl18xx-firmware > firmware-ti-connectivity > > > > > Am I to "apt remove --purge" each of the 200+ packages that were > > (apparently) pulled in? > > no, many are just updates to pkgs you already have installed.. > > > > > Still, how do I perform the upgrade to get the possible fix for my > > connectivity problem within available disk space? (is it impossible?) > > i'd kill the upgrade process and do the above > > Regards, > > -- > Robert Nelson > https://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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/88af7cbb-cebe-408e-993c-213eda6dcc44%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] BBB Wireless frequently drops connection
On Wed, Mar 28, 2018 at 4:34 PM, ags wrote: > Sorry if this is obvious. The current situation is that I have no "disk" > space left and the upgrade is paused (^Z) after fetching 464 MB. I have > minimal user-installed "stuff" on the system so it appears to have been > filled up with this upgrade attempt. > > I thought I would be installing the "firmware-ti-connectivity" package (for > the first time) and upgrading the "bb-wl18xx-firmware" package to a newer > version. The former seemed OK, but the latter (apparently) pulled in another > 200+ packages. Did I do that incorrectly? Yeah i messed that up, it's "install --only-upgrade" sudo apt install --only-upgrade bb-wl18xx-firmware firmware-ti-connectivity > > Am I to "apt remove --purge" each of the 200+ packages that were > (apparently) pulled in? no, many are just updates to pkgs you already have installed.. > > Still, how do I perform the upgrade to get the possible fix for my > connectivity problem within available disk space? (is it impossible?) i'd kill the upgrade process and do the above Regards, -- Robert Nelson https://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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYhh9zmUfzKA4Nv5_bx9ZjjNq3Nn3%3Dy8SVeDSiVSdST5Sg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] BBB Wireless frequently drops connection
Sorry if this is obvious. The current situation is that I have no "disk" space left and the upgrade is paused (^Z) after fetching 464 MB. I have minimal user-installed "stuff" on the system so it appears to have been filled up with this upgrade attempt. I thought I would be installing the "firmware-ti-connectivity" package (for the first time) and upgrading the "bb-wl18xx-firmware" package to a newer version. The former seemed OK, but the latter (apparently) pulled in another 200+ packages. Did I do that incorrectly? Am I to "apt remove --purge" each of the 200+ packages that were (apparently) pulled in? Still, how do I perform the upgrade to get the possible fix for my connectivity problem within available disk space? (is it impossible?) On Wednesday, March 28, 2018 at 2:19:40 PM UTC-7, RobertCNelson wrote: > > On Wed, Mar 28, 2018 at 4:13 PM, ags > > wrote: > > I realize there is not an explicit question here... > > > > I have paused (^Z) the upgrade. Can I terminate and reclaim the disk > space, > > or is there another option? > > > > Does the desired package upgrade really require 400+MB of dependencies > to > > also be upgraded? The output looks like all possible upgrades were being > > done. > > Yes, you can recover most of the space 'afterwards'.. > > and use > > sudo apt remove (pkg) --purge > > to cleanup anything you don't use.. > > Regards, > > -- > Robert Nelson > https://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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/fd6a0b34-2c71-4e18-9258-97fbc6b3444b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] BBB Wireless frequently drops connection
On Wed, Mar 28, 2018 at 4:13 PM, ags wrote: > I realize there is not an explicit question here... > > I have paused (^Z) the upgrade. Can I terminate and reclaim the disk space, > or is there another option? > > Does the desired package upgrade really require 400+MB of dependencies to > also be upgraded? The output looks like all possible upgrades were being > done. Yes, you can recover most of the space 'afterwards'.. and use sudo apt remove (pkg) --purge to cleanup anything you don't use.. Regards, -- Robert Nelson https://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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYjTxxeObEo1omsc14c58MoxAkYyAfnh4R4Zp8cVSjH_4w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] BBB Wireless frequently drops connection
I realize there is not an explicit question here... I have paused (^Z) the upgrade. Can I terminate and reclaim the disk space, or is there another option? Does the desired package upgrade really require 400+MB of dependencies to also be upgraded? The output looks like all possible upgrades were being done. On Wednesday, March 28, 2018 at 1:28:18 PM UTC-7, ags wrote: > > Uh oh... > > debian@BBB:~$ sudo apt upgrade bb-wl18xx-firmware firmware-ti-connectivity > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > Calculating upgrade... The following packages were automatically installed > and are no longer required: > > libpci3 libspeechd2 > > Use 'apt-get autoremove' to remove them. > > Done > > The following NEW packages will be installed: > > firmware-ti-connectivity libdrm-common > > The following packages will be upgraded: > > apache2 apache2-bin apache2-data apache2-utils apt apt-transport-https > apt-utils base-files bash > > bb-customizations bb-node-red-installer bb-wl18xx-firmware bind9-host > binutils bluetooth bluez... > > > [... and 200+ more] > > > ...xserver-xorg-video-omap > > 242 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. > > Need to get 464 MB of archives. > > After this operation, 102 MB of additional disk space will be used. > > Do you want to continue? [Y/n] Y > > > Foolishly I accepted - and now I have 0% space available on my eMMC. > > I don't know how to undo this, nor if I will be able to restart without > remediating this. > > > > > On Wednesday, March 28, 2018 at 8:07:55 AM UTC-7, RobertCNelson wrote: >> >> On Wed, Mar 28, 2018 at 9:40 AM, ags wrote: >> > git:/opt/scripts/:[9d965a5f40ae00774c81164f87a450a678ab79f6] >> > >> > eeprom:[A335BNLTBWA51650BBWG0378] >> > >> > model:[TI_AM335x_BeagleBone_Black_Wireless] >> > >> > dogtag:[BeagleBoard.org Debian Image 2016-11-06] >> > >> > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot >> > 2018.03-2-g254339602c]:[location: dd MBR] >> > >> > kernel:[4.4.113-ti-r148] >> >> > pkg:[bb-wl18xx-firmware]:[1.20161020-0rcnee1~bpo80+20161020+1] >> > WARNING:pkg:[firmware-ti-connectivity]:[NOT_INSTALLED] >> >> That's ^ a hint for one of the reason of random dropouts... >> >> sudo apt update >> sudo apt upgrade bb-wl18xx-firmware firmware-ti-connectivity >> >> Regards, >> >> -- >> Robert Nelson >> https://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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/8b38d40b-ffb1-4846-841a-ed240bdd6742%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] BBB Wireless frequently drops connection
Uh oh... debian@BBB:~$ sudo apt upgrade bb-wl18xx-firmware firmware-ti-connectivity Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... The following packages were automatically installed and are no longer required: libpci3 libspeechd2 Use 'apt-get autoremove' to remove them. Done The following NEW packages will be installed: firmware-ti-connectivity libdrm-common The following packages will be upgraded: apache2 apache2-bin apache2-data apache2-utils apt apt-transport-https apt-utils base-files bash bb-customizations bb-node-red-installer bb-wl18xx-firmware bind9-host binutils bluetooth bluez... [... and 200+ more] ...xserver-xorg-video-omap 242 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 464 MB of archives. After this operation, 102 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Foolishly I accepted - and now I have 0% space available on my eMMC. I don't know how to undo this, nor if I will be able to restart without remediating this. On Wednesday, March 28, 2018 at 8:07:55 AM UTC-7, RobertCNelson wrote: > > On Wed, Mar 28, 2018 at 9:40 AM, ags > > wrote: > > git:/opt/scripts/:[9d965a5f40ae00774c81164f87a450a678ab79f6] > > > > eeprom:[A335BNLTBWA51650BBWG0378] > > > > model:[TI_AM335x_BeagleBone_Black_Wireless] > > > > dogtag:[BeagleBoard.org Debian Image 2016-11-06] > > > > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot > > 2018.03-2-g254339602c]:[location: dd MBR] > > > > kernel:[4.4.113-ti-r148] > > > pkg:[bb-wl18xx-firmware]:[1.20161020-0rcnee1~bpo80+20161020+1] > > WARNING:pkg:[firmware-ti-connectivity]:[NOT_INSTALLED] > > That's ^ a hint for one of the reason of random dropouts... > > sudo apt update > sudo apt upgrade bb-wl18xx-firmware firmware-ti-connectivity > > Regards, > > -- > Robert Nelson > https://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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/d4da5b88-3b44-4674-87dc-b4698530f9e6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] BBB Wireless frequently drops connection
On Wed, Mar 28, 2018 at 9:40 AM, ags wrote: > git:/opt/scripts/:[9d965a5f40ae00774c81164f87a450a678ab79f6] > > eeprom:[A335BNLTBWA51650BBWG0378] > > model:[TI_AM335x_BeagleBone_Black_Wireless] > > dogtag:[BeagleBoard.org Debian Image 2016-11-06] > > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot > 2018.03-2-g254339602c]:[location: dd MBR] > > kernel:[4.4.113-ti-r148] > pkg:[bb-wl18xx-firmware]:[1.20161020-0rcnee1~bpo80+20161020+1] > WARNING:pkg:[firmware-ti-connectivity]:[NOT_INSTALLED] That's ^ a hint for one of the reason of random dropouts... sudo apt update sudo apt upgrade bb-wl18xx-firmware firmware-ti-connectivity Regards, -- Robert Nelson https://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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYig14s%3D-Qq_SfFHaE%2BHRmS%3DBB%3DOxZT19MoX3N_eipsuiQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] BBB Wireless frequently drops connection
git:/opt/scripts/:[9d965a5f40ae00774c81164f87a450a678ab79f6] eeprom:[A335BNLTBWA51650BBWG0378] model:[TI_AM335x_BeagleBone_Black_Wireless] dogtag:[BeagleBoard.org Debian Image 2016-11-06] bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2018.03-2-g254339602c]:[location: dd MBR] kernel:[4.4.113-ti-r148] nodejs:[v6.12.2] uboot_overlay_options:[enable_uboot_overlays=1] uboot_overlay_options:[disable_uboot_overlay_audio=1] uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo] uboot_overlay_options:[enable_uboot_cape_universal=1] pkg:[bb-cape-overlays]:[4.4.20180322.0-0rcnee0~jessie+20180322] pkg:[bb-wl18xx-firmware]:[1.20161020-0rcnee1~bpo80+20161020+1] WARNING:pkg:[firmware-ti-connectivity]:[NOT_INSTALLED] groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal netdev i2c admin spi tisdk weston-launch xenomai] cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=UUID=ac4731db-c4db-463f-9129-07e6746b98ba ro rootfstype=ext4 rootwait coherent_pool=1M quiet] dmesg | grep pinctrl-single [1.213389] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568 dmesg | grep gpio-of-helper [1.214406] gpio-of-helper ocp:cape-universal: Allocated GPIO id=0 [1.214632] gpio-of-helper ocp:cape-universal: Allocated GPIO id=1 [1.214800] gpio-of-helper ocp:cape-universal: Allocated GPIO id=2 [1.214945] gpio-of-helper ocp:cape-universal: Allocated GPIO id=3 [1.215094] gpio-of-helper ocp:cape-universal: Allocated GPIO id=4 [1.215487] gpio-of-helper ocp:cape-universal: Allocated GPIO id=5 [1.215648] gpio-of-helper ocp:cape-universal: Allocated GPIO id=6 [1.215793] gpio-of-helper ocp:cape-universal: Allocated GPIO id=7 [1.215947] gpio-of-helper ocp:cape-universal: Allocated GPIO id=8 [1.216094] gpio-of-helper ocp:cape-universal: Allocated GPIO id=9 [1.216249] gpio-of-helper ocp:cape-universal: Allocated GPIO id=10 [1.216393] gpio-of-helper ocp:cape-universal: Allocated GPIO id=11 [1.216585] gpio-of-helper ocp:cape-universal: Allocated GPIO id=12 [1.216738] gpio-of-helper ocp:cape-universal: Allocated GPIO id=13 [1.216878] gpio-of-helper ocp:cape-universal: Allocated GPIO id=14 [1.217004] gpio-of-helper ocp:cape-universal: Allocated GPIO id=15 [1.217147] gpio-of-helper ocp:cape-universal: Allocated GPIO id=16 [1.217280] gpio-of-helper ocp:cape-universal: Allocated GPIO id=17 [1.217436] gpio-of-helper ocp:cape-universal: Allocated GPIO id=18 [1.217567] gpio-of-helper ocp:cape-universal: Allocated GPIO id=19 [1.217702] gpio-of-helper ocp:cape-universal: Allocated GPIO id=20 [1.217839] gpio-of-helper ocp:cape-universal: Allocated GPIO id=21 [1.217970] gpio-of-helper ocp:cape-universal: Allocated GPIO id=22 [1.218102] gpio-of-helper ocp:cape-universal: Allocated GPIO id=23 [1.218240] gpio-of-helper ocp:cape-universal: Allocated GPIO id=24 [1.218415] gpio-of-helper ocp:cape-universal: Allocated GPIO id=25 [1.218564] gpio-of-helper ocp:cape-universal: Allocated GPIO id=26 [1.218701] gpio-of-helper ocp:cape-universal: Allocated GPIO id=27 [1.218835] gpio-of-helper ocp:cape-universal: Allocated GPIO id=28 [1.218976] gpio-of-helper ocp:cape-universal: Allocated GPIO id=29 [1.219113] gpio-of-helper ocp:cape-universal: Allocated GPIO id=30 [1.219610] gpio-of-helper ocp:cape-universal: Allocated GPIO id=31 [1.219786] gpio-of-helper ocp:cape-universal: Allocated GPIO id=32 [1.219928] gpio-of-helper ocp:cape-universal: Allocated GPIO id=33 [1.220076] gpio-of-helper ocp:cape-universal: Allocated GPIO id=34 [1.220212] gpio-of-helper ocp:cape-universal: Allocated GPIO id=35 [1.220350] gpio-of-helper ocp:cape-universal: Allocated GPIO id=36 [1.220498] gpio-of-helper ocp:cape-universal: Allocated GPIO id=37 [1.220639] gpio-of-helper ocp:cape-universal: Allocated GPIO id=38 [1.220650] gpio-of-helper ocp:cape-universal: ready END On Tuesday, March 27, 2018 at 5:06:29 PM UTC-7, RobertCNelson wrote: > > On Tue, Mar 27, 2018 at 5:22 PM, ags > > wrote: > > I’m experiencing random drops of wirelesss connectivity with BBBW. I > have several other wired & wireless SBCs BBB, RPi, etc. and don’t see this > with them. This is my only BBBW though. I believe I’ve experienced it since > first installing - but am not certain. > > > > Symptoms are simply not being able to connect (with ssh or other means) > or having an open ssh session terminated. Sometimes I can re-establish > immediately, sometimes I let ping run for dozens of packets and it is > eventually found back online, and sometimes I have to power-cycle to > (re)gain access. When inaccessible the power and heartbeat leds are > indicating normal operation. > > > > Is this a known issue? Is there a fix? > > > > Running 4.4.11x ti > > Let's check a few things: >
Re: [beagleboard] BBB Wireless frequently drops connection
For what it's worth. The rpi3 does this as well. Granted perhaps not as much. I've used mine as an ap for my phones, and would get dropped connections at random times. Sometimes days, other times hours. On Tue, Mar 27, 2018, 2:06 PM Robert Nelson wrote: > On Tue, Mar 27, 2018 at 5:22 PM, ags wrote: > > I’m experiencing random drops of wirelesss connectivity with BBBW. I > have several other wired & wireless SBCs BBB, RPi, etc. and don’t see this > with them. This is my only BBBW though. I believe I’ve experienced it since > first installing - but am not certain. > > > > Symptoms are simply not being able to connect (with ssh or other means) > or having an open ssh session terminated. Sometimes I can re-establish > immediately, sometimes I let ping run for dozens of packets and it is > eventually found back online, and sometimes I have to power-cycle to > (re)gain access. When inaccessible the power and heartbeat leds are > indicating normal operation. > > > > Is this a known issue? Is there a fix? > > > > Running 4.4.11x ti > > Let's check a few things: > > sudo /opt/scripts/tools/version.sh > > Regards, > > -- > Robert Nelson > https://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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/CAOCHtYi9Nwd%3D4qNf2uFmxVw8YR3zqHKcgwEAyhzCVSn2UYc4Yw%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORpXWrpKSUByDuPAqnbeju1iDwK-%3DAN0%2BiaheEXkHGf6Eg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] BBB Wireless frequently drops connection
On Tue, Mar 27, 2018 at 5:22 PM, ags wrote: > I’m experiencing random drops of wirelesss connectivity with BBBW. I have > several other wired & wireless SBCs BBB, RPi, etc. and don’t see this with > them. This is my only BBBW though. I believe I’ve experienced it since first > installing - but am not certain. > > Symptoms are simply not being able to connect (with ssh or other means) or > having an open ssh session terminated. Sometimes I can re-establish > immediately, sometimes I let ping run for dozens of packets and it is > eventually found back online, and sometimes I have to power-cycle to (re)gain > access. When inaccessible the power and heartbeat leds are indicating normal > operation. > > Is this a known issue? Is there a fix? > > Running 4.4.11x ti Let's check a few things: sudo /opt/scripts/tools/version.sh Regards, -- Robert Nelson https://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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYi9Nwd%3D4qNf2uFmxVw8YR3zqHKcgwEAyhzCVSn2UYc4Yw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] BBB Wireless frequently drops connection
I’m experiencing random drops of wirelesss connectivity with BBBW. I have several other wired & wireless SBCs BBB, RPi, etc. and don’t see this with them. This is my only BBBW though. I believe I’ve experienced it since first installing - but am not certain. Symptoms are simply not being able to connect (with ssh or other means) or having an open ssh session terminated. Sometimes I can re-establish immediately, sometimes I let ping run for dozens of packets and it is eventually found back online, and sometimes I have to power-cycle to (re)gain access. When inaccessible the power and heartbeat leds are indicating normal operation. Is this a known issue? Is there a fix? Running 4.4.11x ti -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/7f32da93-1ce3-47aa-a870-c1d172af658d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
