On Thu, Feb 4, 2021 at 5:00 PM Hartley Sweeten wrote:
>
> Hello,
>
> I just did an 'apt update' and see that bb-cape-overlays has been updated.
>
> $ apt-mark showhold
> bb-cape-overlays
>
> $ apt list --upgradable -a
> Listing... Done
> bb-cape-overlays/unknown 4.14.20201221.0-0~stretch+20201221
Hello,
I just did an 'apt update' and see that bb-cape-overlays has been updated.
$ apt-mark showhold
bb-cape-overlays
$ apt list --upgradable -a
Listing... Done
bb-cape-overlays/unknown 4.14.20201221.0-0~stretch+20201221 armhf
[upgradable from: 4.4.20190610.0-0rcnee0~stretch+20190610]
Yeah That worked!!! After 2-3 months I can finally update this stupid
thing.
Here's the full boot from J1. I don have a couple questions at the end.
U-Boot SPL 2018.01-2-g9aa111a004 (Jan 20 2018 - 12:45:29)
Trying to boot from MMC2
U-Boot 2018.01-2-g9aa111a004 (Jan 20 2018 -
OK, I did the hold on the bb-cape-overlays.
Running the 'sudo apt upgrade' now. I'll let you know how it goes shortly.
It it fails to boot again to you want the full serial port log?
Hartley
On Friday, October 23, 2020 at 5:08:43 PM UTC-7, RobertCNelson wrote:
>
> I bet it's bb-cape-overlays,
I bet it's bb-cape-overlays, just lock it:
sudo apt-mark hold bb-cape-overlays
Regards,
On Fri, Oct 23, 2020 at 6:50 PM Hartley Sweeten wrote:
>
> Here's the rest. This is all before the 'apt upgrade'.
>
> Starting kernel ...
>
> [0.00] Booting Linux on physical CPU 0x0
> [
Here's the rest. This is all before the 'apt upgrade'.
Starting kernel ...
[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 4.9.105-ti-r114 (root@a5-imx6q-wandboard-2gb)
(gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP PREEMPT Fri
Aug 17 11:05:53 UTC
On Fri, Oct 23, 2020 at 6:20 PM Hartley Sweeten wrote:
>
> Here is the uBoot output before I do an 'apt upgrade'
>
> U-Boot SPL 2018.01-2-g9aa111a004 (Jan 20 2018 - 12:45:29)
> Trying to boot from MMC2
>
>
> U-Boot 2018.01-2-g9aa111a004 (Jan 20 2018 - 12:45:29 -0600), Build:
>
Here is the uBoot output before I do an 'apt upgrade'
U-Boot SPL 2018.01-2-g9aa111a004 (Jan 20 2018 - 12:45:29)
Trying to boot from MMC2
U-Boot 2018.01-2-g9aa111a004 (Jan 20 2018 - 12:45:29 -0600), Build:
jenkins-github_Bootloader-Builder-32
CPU : AM335X-GP rev 2.1
I2C: ready
DRAM:
The serial cable is plugged in. What do you want me to do?
On Friday, October 23, 2020 at 4:15:43 PM UTC-7, RobertCNelson wrote:
>
> On Fri, Oct 23, 2020 at 5:58 PM Hartley Sweeten > wrote:
> >
> > I tried adding the UUID (found with blkid) to my uEnv.txt. Same result.
> >
> > 1) Install
On Fri, Oct 23, 2020 at 5:58 PM Hartley Sweeten wrote:
>
> I tried adding the UUID (found with blkid) to my uEnv.txt. Same result.
>
> 1) Install SDcard image
> 2) Boot
> 3) sudo apt update
> 4) sudo apt upgrade
> 5) Reboot, system hangs
>
> It does change the message:
>
> Begin: Running
OK, another annoyance...
I jut reinstalled my SDcard image and the UUID changed.
The last install (that broke after the apt upgrade) was
0159e561-b327-492f-a73a-b188b2217267.
After this install its now 60fc6cad-2e3f-408d-a2f8-5f2320240203.
Is it possible that something during the apt upgrade
I tried adding the UUID (found with blkid) to my uEnv.txt. Same result.
1) Install SDcard image
2) Boot
3) sudo apt update
4) sudo apt upgrade
5) Reboot, system hangs
It does change the message:
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root file system device.
Robert,
I really can't remember what the original image file was that I started
with. I only have the /etc/dogtag info.
The image "file" I am using is one I created using the
/opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh
script. This was done after installing the
On Fri, Oct 23, 2020 at 4:12 PM Hartley Sweeten wrote:
>
> Ok, this happened again. I forgot that an 'apt upgrade' breaks my setup.
>
> I reinstalled my default image on the BBB. For reference:
>
> ~$ cat /etc/dogtag
> BeagleBoard.org Debian Image 2018-01-21
Can you share the "file" name of this
Ok, this happened again. I forgot that an 'apt upgrade' breaks my setup.
I reinstalled my default image on the BBB. For reference:
~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2018-01-21
~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux
Robert,
Glad to... How?
I know I can edit /boot/uEnv.txt to remove the "quiet" but the board is not
booting...
How do I remove it from uBoot?
Hartley
On Sunday, August 23, 2020 at 9:13:23 AM UTC-7 RobertCNelson wrote:
> On Sat, Aug 22, 2020 at 5:15 PM Hartley Sweeten
> wrote:
> >
> > Hi
On Sat, Aug 22, 2020 at 5:15 PM Hartley Sweeten wrote:
>
> Hi Robert,
>
> Quick background on this.
>
> I have a "standard" image I use that is based on the Console Debian 9 image.
> I usually keep it pretty up-to-date but have not updated it since Debian 9.9.
>
> I was trying to update it to
Hi Robert,
Quick background on this.
I have a "standard" image I use that is based on the Console Debian 9
image. I usually keep it pretty up-to-date but have not updated it since
Debian 9.9.
I was trying to update it to the latest Debian 9.13 using apt
update/upgrade. This has always worked
Let's see your serial boot log from j1 header to see where it's getting
stick..
On Sat, Aug 22, 2020, 3:35 PM jonnymo wrote:
> Could you post the strange message you are seeing regarding the uSD card?
>
> For me, going from 9.9 to 9.13 and beyond, I would just do a reflash of
> the image.
>
>
Could you post the strange message you are seeing regarding the uSD card?
For me, going from 9.9 to 9.13 and beyond, I would just do a reflash of the
image.
Which rev of BBB do you have? Rev B or Rev C?
Robert is the master of this so I would think his suggestions would clear
the issue.
Hi Jon,
I have already seen that post. It doesn't help since it requires reflashing
the board.
I had another board that I did the same 'apt update/upgrade' on and had the
same problem.
BTW, If have not been able to get that board to reflash, it keeps giving me
some strange error message
This may help:
https://forum.digikey.com/t/beablebone-black-boot-issue-dev-mmcblk1p1-does-not-exist/7717
Cheers,
Jon
On Sat, Aug 22, 2020 at 10:47 AM Hartley Sweeten
wrote:
> Hello all,
>
> I had an old Debian 9.9 console image on my BBB and did an apt upgrade
> that bumped it to Debian
Hello all,
I had an old Debian 9.9 console image on my BBB and did an apt upgrade that
bumped it to Debian 9.13. Now the board does not boot.
If I hook up a serial console I see it keeps stopping at:
Starting kernel ...
[0.001033] clocksource_probe: no matching clocksources found
[
23 matches
Mail list logo
