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. Cheers, Jon On Sat, Aug 22, 2020 at 1:04 PM Hartley Sweeten <[email protected]> wrote: > > 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 about the SD-Card, still have not figured > that out. The SD-Card worked fine on a different BBB. > > I would like to know if there is a way to fix this without reflashing the > board. > > I guess a bigger question is - Does upgrading the console image from > Debian 9.9 to 9.13 actually work? > > Hartley > > On Saturday, August 22, 2020 at 11:28:22 AM UTC-7 [email protected] wrote: > >> 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 <[email protected]> >> 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 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 >>> [ 1.312908] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc >>> handle >>> [ 1.487471] omap_hsmmc 481d8000.mmc: prop pinctrl-0 index 0 invalid >>> phandle >>> [ 1.522392] omap_voltage_late_init: Voltage driver support not added >>> [ 1.529573] PM: Cannot get wkup_m3_ipc handle >>> [ 1.807980] bone_capemgr bone_capemgr: slot #0: No cape found >>> [ 1.839062] bone_capemgr bone_capemgr: slot #1: No cape found >>> [ 1.871759] bone_capemgr bone_capemgr: slot #2: No cape found >>> [ 1.904436] bone_capemgr bone_capemgr: slot #3: No cape found >>> Gave up waiting for root file system device. Common problems: >>> - Boot args (cat /proc/cmdline) >>> - Check rootdelay= (did the system wait long enough?) >>> - Missing modules (cat /proc/modules; ls /dev) >>> ALERT! /dev/mmcblk1p1 does not exist. Dropping to a shell! >>> (initramfs) >>> >>> Is there any way to fix this other than reflashing? >>> >>> 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 [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/beagleboard/960431ee-a19f-4425-b2c5-b06f4ec63229o%40googlegroups.com >>> <https://groups.google.com/d/msgid/beagleboard/960431ee-a19f-4425-b2c5-b06f4ec63229o%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/a55e5f2b-e111-4624-ae1c-41419050a951n%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/a55e5f2b-e111-4624-ae1c-41419050a951n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAG99bkqAMNPGsruTihkOjT9cykvcUycrgc8%3DXj7zGV5yoH%2BwUA%40mail.gmail.com.
