On Sat, 25 Apr 2026, at 16:25, Jan Stary wrote:
> On Apr 25 13:12:46, [email protected] wrote:
>> Here is output from the uboot process. It never gets to the part where
>> it's handed over to openbsd. Note that this is after installation from sdmmc
>> the sdmmc card removed and the machine turned on with the usb3 ssd plugged 
>> in.
>
> Is that the same usb port you used during installation?

The sdmmc was used for installation. The destination selected was sd1: the usb3 
ssd.
After installation, halting the machine then unplugging it, the sdmmc card was 
removed.
The usb3 connected ssd was not unplugged/moved. The machine was then powered up.

So, yes it was the same usb port during the installation.

> Have you tried booting with the usb disk in other usb ports?

Yes. Same result in either of the two usb3 ports and either of the two usb2 
ports.

<< snip >>

>>  10.24 Read /config.txt bytes       65 hnd 0x28f
>>  10.02 MESS:00:00:10.029078:0: board: boardrev e04171 otp e04171
>>  10.34 Read /config.txt bytes       65 hnd 0x28f

> And it reads the config.txt from the FAT partition: good.
> (What's in that config.txt? Have you tweaked it?)

No. The config.txt is unmodified. Here's the config.txt :

arm_64bit=1
enable_uart=1
dtoverlay=disable-bt
kernel=u-boot.bin

<< snip >>

>> MMC:   mmc@fff000: 0, mmc@1100000: 1
>> Loading Environment from FAT... Card did not respond to voltage select! : 
>> -110
>> ** Bad device specification mmc 0 **
>> In:    serial,usbkbd
>> Out:   serial,vidconsole
>> Err:   serial,vidconsole
>> Net:   No ethernet found.
>> 
>> starting USB...
>> No USB controllers found
>>        scanning usb for storage devices... 0 Storage Device(s) found
>
> Not good: if no usb devices are found,
> surely it won't boot from your usb disk.

But it must have found it otherwise how do we get this output?
There is no storage plugged in at this stage apart from the usb3-connected ssd

>> Hit any key to stop autoboot:  0 
>> Card did not respond to voltage select! : -110
>
> What card? The removed sdmmc?

Yes.

>> Cannot persist EFI variables without system partition
>> Card did not respond to voltage select! : -110
>> U-Boot> boot
>> Card did not respond to voltage select! : -110
>> U-Boot> setenv bootdelay -2
>> U-Boot> saveenv
>> Saving Environment to FAT... Card did not respond to voltage select! : -110
>> ** Bad device specification mmc 0 **
>> Failed (1)
>> U-Boot> boot
>> Card did not respond to voltage select! : -110
>> U-Boot>

I also have an RPI4 running openbsd off a usb3-connected ssd only and it works 
fine.
ISTR similar 'card did not respond' error messages in the console but somehow 
the uboot still finds and boots OpenBSD.

Reply via email to