On Sun, Feb 28, 2016 at 08:15:55PM -0500, Andrew Cagney wrote:
>
> It turns out this was beginners luck. The pi also, occasionally,
> can't see sd0 early in the boot process.
Might also depend on the USB disk. Here I don't see such issues.
The USB disk appears even before the USB keyboard and
On 02/25/16 14:34, Andrew Cagney wrote:
On 22 February 2016 at 12:46, Andrew Cagney wrote:
On 20 February 2016 at 17:14, Michael van Elst wrote:
andrew.cag...@gmail.com (Andrew Cagney) writes:
so I simply added root=sd0a to /boot/boot.ini's boot
On 22/02/2016 17:46, Andrew Cagney wrote:
>> The USB disk is probably starting too slowly to be recognized at this
>> point. There needs to be some kind of spin-up delay in the kernel to
>> handle this situation.
>
> Ah.
>
> Is there any existing kernel event that would indicate a disk device
>
On 22 February 2016 at 12:46, Andrew Cagney wrote:
> On 20 February 2016 at 17:14, Michael van Elst wrote:
>> andrew.cag...@gmail.com (Andrew Cagney) writes:
>>
>>>so I simply added root=sd0a to /boot/boot.ini's boot line. That resulted in:
>> [...]
andrew.cag...@gmail.com (Andrew Cagney) writes:
>so I simply added root=sd0a to /boot/boot.ini's boot line. That resulted in:
[...]
>use one of: awge0 ld0[a-p] ddb halt reboot
>Should this have worked?
Apparently not, as there is no sd0a boot device.
>However, I get the feeling that there's
I've an odroid-c1 running current. I'm trying to get the root file
system onto a USB disk and, I suspect, missing something obvious.
The default kernel has something like:
config netbsd root on ? type ?
so I simply added root=sd0a to /boot/boot.ini's boot line. That resulted in:
sdmmc1: