Presently, the timeout for detecting my USB drive on restart is not long enough. It times out, looks for the sd card (which is not installed), then goes into a loop.
Powering off the Pi at this point and turning it back on gets me a complete boot, presumably because the drive is fully powered up at that point (?).
What’s the easiest way to increase the timeout value?
did you try Jan/11 stable version.
I … don’t think so?
~]$ sudo rpi-eeprom-update
[sudo] password for $USER:
BCM2711 detected
Dedicated VL805 EEPROM detected
BOOTLOADER: up-to-date
CURRENT: Thu Sep 3 12:11:43 PM UTC 2020 (1599135103)
LATEST: Thu Sep 3 12:11:43 PM UTC 2020 (1599135103)
FW DIR: /lib/firmware/raspberrypi/bootloader/stable
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000138a1
I’m on the stable branch, but it says the last update was in September…
External USB drives can be slow to power on. The best solution for that, is to use an external drive that with it’s own power source, so it’s “always” turned on.
I don’t know how you guys mount things in ARM but, can’t you use something like x-systemd.mount-timeout=XX flag to make that longer?
Should work the same on ARM.
That won’t work if the system is located on the device.
This is a USB device problem - the device is probably flawed - have you tried to exchange it?
Another cause could be as @Strit points out - the power consumption of the USB device.
I’ve read in other forums that there are some boards with USB not working correctly (probably driver/kernel related) and require a command before reboot to stop the USB controller so it works after the reboot. Otherwise you need to power down and then power up for it to work. Can’t remember the command right now.
@johntdavis84 I have no clue why you choose not test the pieeprom-2021-01-11 with rpi-eeprom-git from the beta folder when you had the chance in another thread to see if it solved your issue. Since then it has been promoted yesterday to stable and I have pushed rpi-eeprom-git-20210114-1 to the unstable branch when the mirrors sync.
I am asking again along with @Rip2 to try the pieeprom-2021-01-11 image and see if it fixes your issue.
[ray@pi4 ~]$ sudo rpi-eeprom-update
BCM2711 detected
VL805 firmware in bootloader EEPROM
BOOTLOADER: up-to-date
CURRENT: Mon Jan 11 03:44:33 PM UTC 2021 (1610379873)
LATEST: Mon Jan 11 03:44:33 PM UTC 2021 (1610379873)
FW DIR: /lib/firmware/raspberrypi/bootloader/stable
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000138a1@Darksky , sorry for not replying clearly over on the other thread. I got distracted by the NVME-drive interface board I bought being a complete piece of garbage (including, apparently, having a dead 5V power input).
My, er, Pi Time was devoted to trying to straighten that out–including having to buy a new enclosure for the NVME drive and figure out how to return the thing I had already, and then I was sick enough of the whole thing not to wanna mess with it a while.
More than that, I’m confused by the output of rpi-eeprom-update I’m currently getting.
~]$ sudo rpi-eeprom-update
[sudo] password for panoptitom:
BCM2711 detected
Dedicated VL805 EEPROM detected
BOOTLOADER: up-to-date
CURRENT: Thu Sep 3 12:11:43 PM UTC 2020 (1599135103)
LATEST: Thu Sep 3 12:11:43 PM UTC 2020 (1599135103)
FW DIR: /lib/firmware/raspberrypi/bootloader/stable
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000138a1
My reading of this is that it’s telling me I’m up-to-date on the stable branch, even though I’ve got a version of the EEPROM and boot loader from September 3.
I wonder if my mirror hasn’t updated yet.
~]$ pacman-mirrors --get-branch
arm-stable
I’m using only one mirror, to try to avoid any issues with going out of sync: https://mirror.dacentec.com/manjaro/arm-stable/$repo/$arch
I remember there being a page I could go to in order to check mirror statuses, but now I can’t find it.
EDIT:
~]$ pacman-mirrors --status
Local mirror status for arm-stable branch
Mirror #1 - - 00:28 United_States Index of /manjaro
Those dashes are in red in my console. I think I need to switch mirrors…
Install rpi-eeprom-git 20210114-1 in the unstable branch and do an eeprom upgrade:
sudo rpi-eeprom-update -a # Flashes eeprom
reboot
sudo rpi-eeprom-update -r # Remove temp files in /boot
sudo rpi-eeprom-update # Check your status
Reboot again to test your drive.
Thanks. I’ll try this later today, if the mirror I’m on doesn’t update by the time I’m ready to mess with the Pi again.
I just checked it at repo.manjaro.org, and my mirror is definitely out of date.
I thought I was eliminating potential conflicts by restricting myself to 1 mirror, but maybe that was a bad idea, after all…
You will have a long wait. This package version I said above is only in the unstable branch.
Ah. I suspected that after I replied. Thanks for clarifying.
I don’t mind trying something from the unstable branch, but it’ll be at least tonight before I can.
Thanks again for your help, and for all the time you spend pushing these updates.
stable version Jan/16 updated.
Looks like the Jan 11image that got promoted to stable in git was not stable after all. This is the reason I tried to say in another thread why I did not like to have a git package unless it had a fix with some issue someone was having. They introduce or fix things and cause issues some where else they have to fix. I also noticed with the latest Jan 16 they put in stable it is tagged with BETA.
I just do not like putting out a package that could possibly break some one’s install.
Anyway the latest git is pushed to the unstable branch when the mirrors sync.
rpi-eeprom-git 20210116-1
[ray@pi4 ~]$ sudo rpi-eeprom-update -r
Removing temporary files from previous EEPROM update
[ray@pi4 ~]$
[ray@pi4 ~]$ sudo rpi-eeprom-update
BCM2711 detected
VL805 firmware in bootloader EEPROM
BOOTLOADER: up-to-date
CURRENT: Sat Jan 16 02:10:13 PM UTC 2021 (1610806213)
LATEST: Sat Jan 16 02:10:13 PM UTC 2021 (1610806213)
FW DIR: /lib/firmware/raspberrypi/bootloader/stable
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000138a1
[ray@pi4 ~]$Good afternoon,
Sorry I dropped off the edge of the world. I got distracted by just how unstable my drive enclosure turned out to be, and had to find something to replace it with before the power-drop induced drive crashes ate my data or ruined the hardware.
I ended up replacing the enclosure, and now I’m not having any trouble with the USB drive getting power from the Pi on boot, even without the beta EEPROM.